hi there,
i used crDroidAndroid-8.1-20180606-riva-v4.3 but there were color problems i didnt know 2 fix so i decided 2 flash a new rom resp. a newer version but no custom rom boots up.
when it tries 2 boot is freezes at the boot screen, then screen switches off and nothing happens. i can go 2 fastboot and recovery.
sometimes it boots up but after a few seconds it freezes 2.
i tried different roms and recoveries but nothing works.
i foolishly wiped internal storage once but then i flashed the stock rom again which boots up. then i unlocked the bootloader and flashed a custom recovery and a rom again but the same error is there (no booting up)
anyone got a solution for this problem? no unbricking suggestions plz
edit: im in the wrong thread i think. i wanted 2 post it in "Guides, News, & Discussion". cant delete it. sry for that
logs
so i managed 2 create logs while booting up.
1) https://pastebin.com/cgrX2DA1
2) https://pastebin.com/r7DmcN46
3) https://pastebin.com/0pwXyuys
4) https://pastebin.com/S41FG2SQ
1) is 1st part of the log while booting with no success to boot into the os.
2) is 2nd part of the log while booting with no success to boot into the os.
3) is 1st part of the log while booting with successful boot into the os.
4) is 2nd part of the log while booting with successful boot into the os.
i also tried 2 log "cat /proc/last_kmsg > /sdcard/last_kernel_message_log.txt"
and "dmesg > /sdcard/kernel_boot_log.txt" via terminal in linux but it only sais file or directory not found.
i hope sum1 can give me sum help now.
so i did this https://en.miui.com/thread-3921604-1-1.html but it doesnt help. as i expected.
any1? i can post more information if necessary. just say which and perhaps how ;D
cmon guys. i can impossibly b the only 1 who faces this problem.
i dont think its a hardware thing cause stock rom and android 7.1.2 (viper os) work. maybe a vendor problem? could flash another vendor img solve this problem? can sum1 send me his?
i got sum more logs after flashing rr 7.0:
logcat 1st part: https://pastebin.com/EBZAgbhF
logcat 2nd part: https://pastebin.com/qaMFrvxi
dmesg: https://pastebin.com/Gg8bYkJy
cheers
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
NaAnBcEhEuL9A8K7 said:
Fastboot flash latest miui 10 stable using mi flash tool and use the rom after setting up. Then flash custom recovery and do a full wipe.
This works for most cases.
Click to expand...
Click to collapse
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
daemonicvs said:
thx for ur answer but i tried this already. does not work on android 8 and 9 roms
Click to expand...
Click to collapse
Well it worked for me.
Which custom rom you want to use?
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
daemonicvs said:
well, it doesnt matter 2 me. the main thing is that it works =D rr, aex, crdroid..
Click to expand...
Click to collapse
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
NaAnBcEhEuL9A8K7 said:
Crdroid is my choice because aex and rr are very early builds. I like pixel experience but the devs not updating it so crdroid or havoc os.
Like i said use Xiaomi flash tool and flash miui 10 stable via fastboot method(there are 3 options in the bottom select flash all instead of flash and lock to avoid unlocking the bootloader again), don't flash anything else, setup and use the phone, flash recovery wipe all and format, install rom, don't flash gapps yet, boot into rom and see if its fixed.
Use vendor based recovery, if using batik recovery you have to flash batik recovery again after format.
This is my solution.
Click to expand...
Click to collapse
i did it several times before but 2 b safe i did it again like that:
i flashed riva_global_images_V10.1.1.0.NCKMIFI_20181029.0000.00_7.1_global_f444c158ed.tgz using XIAOMI-TOOL-MiFlash-for-Linux-by-IceMan-master. im on linux mint 18.3. i have 4 options:
flash_all_lock.sh
flash_all_lock_crc.sh
flash_all_except_data_storage.sh
flash_all.sh
i chose flash_all.sh
i booted into the stock rom and set it up, enabled dev options and adb.
then i switched it off, went into bootloader, flashed twrp-3.2.3-0-riva.img via fastboot.
after that i entered twrp, flashed OrangeFox-R8.3-riva.zip and rebooted into recovery
i wiped everything except external sd and usb otg (i dont have these)
after a reboot intorecovery i formatted data then rebooted in recovery
i flahed crDroidAndroid-9.0-20181002-riva-v5.0.zip
then reboot into system
no success as i expected! wtf is wrong wtf. this cant b true!
but thank u very much for ur efforts! perhaps i would try 2 restore a vendor img from sum1 which rom does work. i know its a great demand but could u send me urs? ;D i dont know if there r sum personal info..
best regards
Don't give up there might be a solution.
Pray to God for some help.
:good:
---------- Post added at 01:23 PM ---------- Previous post was at 12:59 PM ----------
Currently I am using Xiaomi.eu beta rom. You can check their website for all the features. Its smooth, stable and can update without needing to got the recovery:victory:
This should work for you because unlike other roms this is based on miui for riva. That means you will get updates till Xiaomi ditches support for riva.
I recommend you use this rom over the global rom until you fix the problem with your phone.
Some things missing:
Choice of region is limited( India is not available)
There is no custom kernel available for miui oreo as of now.
Magisk safetynet not passed
If you're going flash this rom you need to be on latest global beta fastboot rom and need a recovery that supports oreo base.
I use batik recovery base oreo.
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
daemonicvs said:
yes. i cant b the only 1 facing this problem...!? really. i cant!
thx anyway
Click to expand...
Click to collapse
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
NaAnBcEhEuL9A8K7 said:
Maybe you can be the only one facing this problem.
Try joing telegram community maybe your problem will get fixed from there.
Click to expand...
Click to collapse
theres no difference between my device and yours... everybody must have this problem ;/
daemonicvs said:
theres no difference between my device and yours... everybody must have this problem ;/
Click to expand...
Click to collapse
Did you try edl method?
NaAnBcEhEuL9A8K7 said:
Did you try edl method?
Click to expand...
Click to collapse
yes. i could flash the stock rom this way but the problem is not solved this way
daemonicvs said:
yes. i could flash the stock rom this way but the problem is not solved this way
Click to expand...
Click to collapse
At least you have to try.
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
Did you flash lazy flasher?
Eddyb299 said:
I just unlocked my 5a today tried aosp rremix, pixel ex, no luck. the phone won't boot up. plus excno ept "TWRP-Oreo-Riva-STREBLE-Mod-sjcbank" no other recovery works. tried normal twrp orangefox, no luck.
Click to expand...
Click to collapse
dont u have 2 wait 2 weeks or so till bootloader is unlocked?
what exactly do u mean with won't boot up? bootloop? or stuck at boot logo?
after flashing a custom recovery, did u boot directly into the system or did u try 2 boot into recovery? sometimes the stock recovery overwrites the custom 1 when stock rom boots up
my problem is solved. i remembered that i made a full nandroid backup with twrp before i flashed a new rom and the problem appeared. so i restored everything i backed up with twrp (incl cust) and voila, rom booted up. and i can wipe system and data and flash every rom i wanna and it still boots up \o/
i really could have tried it earlier but i didnt think of this untill yesterday ;D
well, thx for ur efforts anyway buddy @NaAnBcEhEuL9A8K7
cheers
Related
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
I have the same problem, it comes back to recovery all the time and we can tell you about it, some help please
---------- Post added at 09:59 PM ---------- Previous post was at 09:43 PM ----------
Hi, I've come back, hahaha, I installed resurrection remix 7.1, previous all the wipes and reboot in bootloader I gave start and started, great.
I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings
CypherPotato said:
I had this problem trying to install the rom ViperOS. I solved it with one of these steps:
- Boot into Fastboot, select "Start" with volume Keys.
- Flash "boot.img" directly from the zip that is ROM, do this using a PC.
- If you're using stock rom, reflash boot.img
Greetings
Click to expand...
Click to collapse
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.
SuperUtilisateur said:
Does not work for me.
I have flash boot.ini Atomic-OS-1.5 and OCT-N-WEEKLY ...
My phone boot always in recovery
regards
Sry for my bad english.
Click to expand...
Click to collapse
Have you tried to boot from Fastboot?
Yes, it works once...
But if I have to restart it (or turn off and start with the power button), the phone boot always in recovery.
It is then necessary to restart fastboot then press "start".
Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
Try do a full reset through fastboot and then try installing whatever you need through fastboot and recovery. Much more reliable han ota installs/updates
Haxorkat said:
Hey guys, hello there. I need a little help over here.
The other day I made the mistake to install an OTA on my rooted Moto G5 (dual SIM). I had the stock image, TWRP & unlocked bootloader. Of course it failed to install the OTA, but the weird thing is that it always boots to TWRP recovery. No matter if I choose to reboot completely or to boot to system from the TWRP reboot menu, it always goes back to TWRP.
Tried a few things, but none of them worked. Mainly I remember trying the "fastboot oem fb_mode_clear" and did nothing. I didn't try this solution even though problem looks similar. Mainly I didn't want to have to unlock the bootloader and install recovery all over again.
Later I discovered that if I go to the bootloader and hit START from there, boots into OS. So it is functional.
Anyway, I installed Atomic OS ROM thinking I'll get rid of the problem and gain a custom ROM, and everything works, but the problem stays. If I reboot the phone, I have to do TWRP -> Bootloader -> System in order to get it to the OS.
Anyone has any idea on how to fix it?
Click to expand...
Click to collapse
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings
grosobart said:
install resurrection remix and lock with the update of the security patch as we know, then install via fastboot the original firmware, after rebooting install resurrection and now bootea normalmally greetings
Click to expand...
Click to collapse
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
It always says that
As long as it says at the end
Write OK
It flashed successfully
OK,
After flash,
boots automatically into recovery ...
--
I tried with various boot.img. (linéage, AOSP, OctOS, ... )
Does not work ..
I started (into fastboot), I was errors. (Process stopped)
I just restored my phone ( https://mirrors.lolinet.com/firmware/moto/cedric/official/RETAIL/ )
... boot correctly.
Never mind ...
thank you all
SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
https://forum.xda-developers.com/g5/how-to/fyi-recovered-g5-xt-1676-to-stock-t3626088
try this first, regards
SuperUtilisateur said:
>writing 'boot'...
>(bootloader) Image not signed or corrupt
Does not work.
Maybe because of the model? (XT1676)
--
Click to expand...
Click to collapse
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect
Moto G5 boots to TWRP
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Backing up Gigs of data is a huge pain. Even if I have to copy to my pc. So, just something that's less cumbersome.
Noel Carson said:
I have the same issue. But the suggestions posted wouldn't help me. I have the stock ROM and I'm rooted with Magisk using TWRP recovery. I want to keep the stock ROM and don't want to go through the trouble of backing my data again. So, I was wondering if there was any work around. Would flashing the stock ROM, Boot and recovery without deleting user data partition help??
Click to expand...
Click to collapse
rajibahmed said:
Back up your stuff. By cloud or other means. Then reset and load your back up on boot or boot setup
Click to expand...
Click to collapse
Read the faq section (2nd post) - answer is there
https://forum.xda-developers.com/g5/development/official-twrp-3-1-1-0-moto-g5-t3699737
grosobart said:
you should flash the correct firmware on your device and it should work, I did it several times and it works perfect
Click to expand...
Click to collapse
Anyone get the stock for 16gb/2gb version?
I was buy this phone a few days ago with ubl already. I think that was great because i don't need to unlock the bootloader by myself. Since this my first xiaomi phone, unlocking the bootloader may gave me headache. But when i tried to flash twrp, i face a problem that adb said "FAILED (remote: Requested download size is more than max allowed)". At the same time, in fastboot screen shown "press anykey to shutdown". Is somebody here know what must i do? I was spend at least six days looking for solution on internet.. but, still no luck. Hope someone here will help. Any suggestions will so appreciated.
-Sorry for my bad English
Additional info:
On me, isn't driver or port or my windows 10 problem like some people saying since i can run any fastboot commands (flashing twrp too) with another xiaomi phone.
Check this thread
https://forum.xda-developers.com/re...uide-fix-locking-bootloader-fake-ubl-t3833631
deathbearer said:
Check this thread
https://forum.xda-developers.com/re...uide-fix-locking-bootloader-fake-ubl-t3833631
Click to expand...
Click to collapse
Sorry for late replying.. Actually, i though fake UBL is not the problem since my device can bind mi account. I do research for 2 weeks and find nothing can solved this problem
Kratos-mgc said:
Sorry for late replying.. Actually, i though fake UBL is not the problem since my device can bind mi account. I do research for 2 weeks and find nothing can solved this problem
Click to expand...
Click to collapse
Get this zip : https://files.orangefox.website/OrangeFox-Stable/whyred/
Extract it.. find recovery.img and put it in your fastboot folder, run 'fastboot boot recovery.img'.. now, after going to recovery the device will show up as storage in Windows, and put the orange fox zip in internel memory and flash it with booted recovery....
DKWxda said:
Get this zip : https://files.orangefox.website/OrangeFox-Stable/whyred/
Extract it.. find recovery.img and put it in your fastboot folder, run 'fastboot boot recovery.img'.. now, after going to recovery the device will show up as storage in Windows, and put the orange fox zip in internel memory and flash it with booted recovery....
Click to expand...
Click to collapse
Thanks.. Downloading file right now. I thought i've done that before with older version of OrangeFox without luck. Have try with Official TWRP and RedWolf too with same result. But, will try with latest version like you said :highfive:
Kratos-mgc said:
Thanks.. Downloading file right now. I thought i've done that before with older version of OrangeFox without luck. Have try with Official TWRP and RedWolf too with same result. But, will try with latest version like you said :highfive:
Click to expand...
Click to collapse
Np .. post here what happened..
DKWxda said:
Np .. post here what happened..
Click to expand...
Click to collapse
Sure
DKWxda said:
Np .. post here what happened..
Click to expand...
Click to collapse
Same as before.. fail either. What should i gonna do now?
Actually, my phone already had twrp installed with custom rom too after 2 weeks use time. I can't find solution for my problem so i do unusually step (or you can say frustrating step). Do test point things and flash rom like usual. But, before i replace stock recovery with twrp and rename it like stock one. After that, just start flashing and when it finish, boot to recovery directly and flash magisk plus no verity. Then i got twrp and root.. But, still can't flash anything from fastboot, even flashing with miflash. Just curious what exactly the problem is. I know can repeat the same step just in case i got problem to boot and somehow can't boot to twrp too. But, you know.. that takes lot of time to do
I don't know if ur problem is solved by now, i think you should flash latest dev firmware, that might be the key, have you ever done that after the problem? You should use twrp to do that tho.. and pls take note, every firmware is not supported by everry recovery, but i trust orange fox, and don't try to downgrade firmware too, check always if the cutom rom support the firmware you gonna flash and also check ARB value...
Edit: what does this mean
replace stock recovery with twrp and rename it like stock one
i accidently flash the custom rom but now i dont have the original rom backup :crying::cryinglz help any body can upload the twrp system ,vendor and any other things required to restore the original rom :angel::angel:
redmi 6 pro indian version or atleast english version plz
edit : twrp sakura
Accidently... Good one.
https://mirom.ezbox.idv.tw/en/phone/sakura/roms-cn-developer/
coolek33 said:
Accidently... Good one.
https://mirom.ezbox.idv.tw/en/phone/sakura/roms-cn-developer/
Click to expand...
Click to collapse
will i be able to flash the stock rom because i tried indian version but it wont work twrp sakura
also which one shall i download fastboot or recovery ?
If you want to flash it in recovery/twrp choose recovery one. If you want to flash it via fastboot from pc choose fastboot. It's obvious. Both will lock your bootloader after flash but they will boot normally.
coolek33 said:
If you want to flash it in recovery/twrp choose recovery one. If you want to flash it via fastboot from pc choose fastboot. It's obvious. Both will lock your bootloader after flash but they will boot normally.
Click to expand...
Click to collapse
1) lol is there a way to not to lock my bootloader again because if it fails then all is left is fastboot??
2) and also twrp will be removed or shall i flash twrp again or will it brick my device ??
3) or i need to wait 15 days and unlock my device again??
man lot of questions
4) my mi account has unlock permission so do i need to permission again because right now i am using custom rom to keep my phone alive.:crying:
these questions will raise to all if they did the same mistake some more questions but lets see these first
also thanks man you are wonderful helper
If you unlocked your BL once on this device there will be no waiting counter. It will unlock right away. Unless you unlocked it couple days ago. There is a limitation for one account to unlock one device in month. So you will be have to wait till one month pass or unlock with redmi 6pro toolkit like I did. It skipped this limitation somehow. Anyways did you wiped data before or after flashing custom rom? What rom have you flashed? Is it booting is it usable? If not. Try wiping data in advance wipe in twrp first to solve booting problems.
coolek33 said:
If you unlocked your BL once on this device there will be no waiting counter. It will unlock right away. Unless you unlocked it couple days ago. There is a limitation for one account to unlock one device in month. So you will be have to wait till one month pass or unlock with redmi 6pro toolkit like I did. It skipped this limitation somehow. Anyways did you wiped data before or after flashing custom rom? What rom have you flashed? Is it booting is it usable? If not. Try wiping data in advance wipe in twrp first to solve booting problems.
Click to expand...
Click to collapse
i flashed
crdroid rom from redmi 6 pro forums
bootable
kk i will try advanced wipe
also that redmi6 pro tool kit u mentioned is it mi unlock tool if not plz send me the link plz
also thanks i will contact you when something went wrong
also when i flashed custom rom it shows installing unconditionally why
also the restore function is not working is it the twrp fault or the rom
it doesn't boot says boots on logo and then shows the boot animation waits for 5 min and boots twrp again automatically why???(when i try to restore the crdroid rom not to mentioned i tried flashing resurrection os but goes on boot loop )
When flashing custom ROM different from miui you should wipe dalvick, cache, data and system before flash. Then flash RR or something else gapps and boot.
Here's the toolkit If you need it
https://androidfilehost.com/?fid=5862345805528054436
coolek33 said:
Here's the toolkit If you need it
https://androidfilehost.com/?fid=5862345805528054436
Click to expand...
Click to collapse
found this site
https://mi-globe.com/rom-builder/
Ethical Hacker|Youtuber said:
found this site
https://mi-globe.com/rom-builder/
Click to expand...
Click to collapse
lol man that unlock tool did the trick i flashed the above rom from the mi globe rom and my phone got locked again i open the tool and then i unlocked the phone and boom it got unlocked but remember that when u unlock ur data will be deleted and always keep the backup of ur twrp image
after unlock and the login id and pass that pass u will need to enter the phone startup otherwise just boot to fastboot and then bypass account
man finally back to miui without any bugs with root man what else we want
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me
Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.
Hello,
I installed lineage os 17.1 but my wifi, bluetooth and hotspot are not working. In "About Phone" section, it is showing both wifi and bluetooth mac address as unavailable.
I also reflashed stock rom, but now, same issue is happening there. So I reflashed lineage os 17.1. Please help me!!!!.
@sunnyraj84348
gurbir3178 said:
Hello,
I installed lineage os 17.1 but my wifi, bluetooth and hotspot are not working. In "About Phone" section, it is showing both wifi and bluetooth mac address as unavailable.
I also reflashed stock rom, but now, same issue is happening there. So I reflashed lineage os 17.1. Please help me!!!!.
@sunnyraj84348
Click to expand...
Click to collapse
Try flashing another kernel
venu dinesh said:
Try flashing another kernel
Click to expand...
Click to collapse
Can you please give me a link to any tutorial?
gurbir3178 said:
Can you please give me a link to any tutorial?
Click to expand...
Click to collapse
Note: backup anytype of data in external storage
I AM NOT RESPONSIBLE FOR DAMAGE OF YOUR DEVICE
Wipe all except micro SD card..
Flash rom- gapps(if required)- magisk ( if required) - kernel ( try inferno kernel available in xda redmi 5a forums) reboot.. if you bypassed bootloader flash appender.zip for applying blocks .. use orange fox recovery for best results.. and custom rom work only in nougat firmware
gurbir3178 said:
Can you please give me a link to any tutorial?
Click to expand...
Click to collapse
t.me/Redmi_5a telegram link
Ask any questions there.. answers available soon
venu dinesh said:
Note: backup anytype of data in external storage
I AM NOT RESPONSIBLE FOR DAMAGE OF YOUR DEVICE
Wipe all except micro SD card..
Flash rom- gapps(if required)- magisk ( if required) - kernel ( try inferno kernel available in xda redmi 5a forums) reboot.. if you bypassed bootloader flash appender.zip for applying blocks .. use orange fox recovery for best results.. and custom rom work only in nougat firmware
Click to expand...
Click to collapse
Thanks I will try that. One more qustion. Will that kernel be booted as default? Or like in linux I have to choose kernel?
gurbir3178 said:
Thanks I will try that. One more qustion. Will that kernel be booted as default? Or like in linux I have to choose kernel?
Click to expand...
Click to collapse
It will be booted automatically.. there are many kernel available but u can choose one kernel to flash at once if you want to use another kernel you have to flash the rom again flashing kernel is as like flashing zips.
Do not flash 2 kernel in one rom. You will be held in bootloop
venu dinesh said:
It will be booted automatically.. there are many kernel available but u can choose one kernel to flash at once if you want to use another kernel you have to flash the rom again flashing kernel is as like flashing zips.
Do not flash 2 kernel in one rom. You will be held in bootloop
Click to expand...
Click to collapse
ok thanks.
venu dinesh said:
Note: backup anytype of data in external storage
I AM NOT RESPONSIBLE FOR DAMAGE OF YOUR DEVICE
Wipe all except micro SD card..
Flash rom- gapps(if required)- magisk ( if required) - kernel ( try inferno kernel available in xda redmi 5a forums) reboot.. if you bypassed bootloader flash appender.zip for applying blocks .. use orange fox recovery for best results.. and custom rom work only in nougat firmware
Click to expand...
Click to collapse
No Bro. Its not working. Same problem.
I also face the same problem when I flash lineages is 17.1,so now I am stock miui 11 don't have problems all works fine.I don't know in which way u flash stock ROM,Don't flash via recovery, I never done that ,try to flash it via fastboot tools use fastboot ROM
also face the same problem when I flash lineages is 17.1,so now I am stock miui 11 don't have problems all works fine.I don't know in which way u flash stock ROM,Don't flash via recovery, I never done that ,try to flash it via fastboot tools use fastboot ROM
Lak dj said:
I also face the same problem when I flash lineages is 17.1,so now I am stock miui 11 don't have problems all works fine.I don't know in which way u flash stock ROM,Don't flash via recovery, I never done that ,try to flash it via fastboot tools use fastboot ROM
Click to expand...
Click to collapse
Solution: Flash persist.img from orangefox recovery.
Steps:
1. Boot to Orangefox Recovery.
2. Select persist.img file (Downloaded previously in phone)
3. Select "Persist partition" before swiping.
4. Swipe and then reboot.
gurbir3178 said:
Solution: Flash persist.img from orangefox recovery.
Steps:
1. Boot to Orangefox Recovery.
2. Select persist.img file (Downloaded previously in phone)
3. Select "Persist partition" before swiping.
4. Swipe and then reboot.
Click to expand...
Click to collapse
I have a little confusion, can I get a perfect guideline or a perfect installation method
Lak dj said:
I have a little confusion, can I get a perfect guideline or a perfect installation method
Click to expand...
Click to collapse
Flash latest orange fox recovery first. Then boot into it. and follow the steps. Can you tell your problem in more detail?
gurbir3178 said:
Flash latest orange fox recovery first. Then boot into it. and follow the steps. Can you tell your problem in more detail?
Click to expand...
Click to collapse
Bro I need a clear flashing method
Lak dj said:
Bro I need a clear flashing method
Click to expand...
Click to collapse
I don't understand your problem. You can ask more here... t.me/Redmi_5a
gurbir3178 said:
I don't understand your problem. You can ask more here... t.me/Redmi_5a
Click to expand...
Click to collapse
Bro my doubt is when to flash the persist IMG, either while flashing along withthe ROM or after the ROM flashed
Lak dj said:
Bro my doubt is when to flash the persist IMG, either while flashing along withthe ROM or after the ROM flashed
Click to expand...
Click to collapse
after flashing rom.
gurbir3178 said:
after flashing rom.
Click to expand...
Click to collapse
Okay thanks for your help ,I'll try and I will reply if I face any issue,I check the link that u provide I am facing the error "Your not Authorized to Access the Content"