Related
Hello, It's Honor 5x.
Everytime I install a custom rom after finishing installing, Rom's boot logo appears then restarts, and keep restarting without doing anything.
I tried cyanogenmod 13 'downloaded their latest official rom' and tried AOSP-CAF But still have the same issue.
All I do is taking a backup, Then wiping all data, system and cache then flashing the zip.
How can I fix this?
Forgot to mention, I was getting error 7 while flashing the zip but fixed it by editing script file.
Any thoughts?
iAhMedZzz said:
Any thoughts?
Click to expand...
Click to collapse
make sure boot img is correct and being pushed correctly, just my thoughts, don't own the device
Must I have stock MM update installed before installing any MM custom rom ?
So here is my situation: I have a 3GB kenzo model with 6.3.24 EU ROM and ZCX TWRP 3.0.0-0. Of course bootloader in unlocked. Since the TWRP is pretty old, I updated it to RedWolf V3.1.
What I did:
Wipe: Dalvik/System/Data/Cache
Install Beta 7.9.22 or Stable 8.5.6.0 Kenzo firmware (tried with both)
Install RR image: RR-N-v5.8.5-20170924-kenzo-Final.zip
Install open gapps ARM64 7.1 (or not)
Wipe caches (also tried without wiping it)
Reboot
Bootloop
I know the first boot can take some time, so I let it run for 30+ minutes, still, only bootloop happened. Tried it a couple times, changing firmware, wiping caches at the end, ditching gapps etc. Images checked for md5 checksum on the phone, they are not corrupted. I was able to restore the EU ROM, but I really want to try out ResurrectionRemix. What could possibly the problem be?
Same here...i flash all nougat rom and got bootloop..now i stay in mm only...:C
Reflash newest stock image, than hack the emmc bootloader of it and try again
reemar said:
Reflash newest stock image, than hack the emmc bootloader of it and try again
Click to expand...
Click to collapse
So you mean to flash the latest stock ROM, won't it remove TWRP and lock the bootloader? And how to "hack" the emmc bootloader? Sorry, I'm a newbie
Just wait for at least 15 minutes after flashing
DdroidTHEGAMER said:
Just wait for at least 15 minutes after flashing
Click to expand...
Click to collapse
What do you mean, wait in TWRP for 15 minutes or when booting up the OS? As I said, I waited for 30+ minutes while it booted up.
Try installing ROM without flashing the firmware
Minions007 said:
Try installing ROM without flashing the firmware
Click to expand...
Click to collapse
That was the first thing I did (I didn't know a firmware was needed so I only flashed the RR ROM). Same bootloop
You could try to format data partition. Then wipe system,data,cache,dalvik cache and internal partition. After that Copy actually firmware, rom and opengapps arm64 pico in internal memory (Download all files again. Maybe archiv was damaged). Then flash firmware, rom, gapps and do wipe Cache/dalvik and reboot. Then report.
SpeRator said:
You could try to format data partition. Then wipe system,data,cache,dalvik cache and internal partition. After that Copy actually firmware, rom and opengapps arm64 pico in internal memory (Download all files again. Maybe archiv was damaged). Then flash firmware, rom, gapps and do wipe Cache/dalvik and reboot. Then report.
Click to expand...
Click to collapse
Did it, same result. Wiped everything, copied zips to internal storage, flashed from there and boom, bootloop
Hmm strange. You could test a good modified rom of rr.
Try this Rom:
https://www.androidfilehost.com/?fid=673791459329049490
And these Gapps:
https://www.androidfilehost.com/?fid=673791459329049438
If it all not Work, you have to flash actually official Rom to restore all with edl.
I have the exact same problem. Cant flash any ROM without getting bootloop. The bootloop though isnt a standard one, i think. I get the logo of the ROM and the phone starts to give Tiny vibrations in regular periods of time. I also left the phone for a long time hoping it'll eventualy boot. No luck. Tried flashing stock ROM with miflashtool and edl. Didnt help as well. I wonder if it could be the fault of any previous roms i had installed.
Twrp:
-are you sure you are not in read mode? Change to writemode.
-All relevant partitions mounted?
SpeRator said:
Twrp:
-are you sure you are not in read mode? Change to writemode.
-All relevant partitions mounted?
Click to expand...
Click to collapse
Changed to writemode.. default options selected in the mounts screen.
unable to flash any Nougat roms- stuck in boot animation.
is it because the bootloader was unlocked unofficially via lollipop fastboot ROM 7.1.8??
All right, got it working.
I flashed the latest official MIUI ROM with the official flashing tool with the option "clear all". Then I had to open the bootloader again, then flash TWRP, then flash RR, and it works! Looks like something was wrong with the previous installation, the clearing everything did the job.
Were your bootloader unlocked officially?
aldhi said:
Were your bootloader unlocked officially?
Click to expand...
Click to collapse
Unlocked Unofficially via this method https://www.youtube.com/watch?v=2FmaCdnLi58
tonyrulez said:
So here is my situation: I have a 3GB kenzo model with 6.3.24 EU ROM and ZCX TWRP 3.0.0-0. Of course bootloader in unlocked. Since the TWRP is pretty old, I updated it to RedWolf V3.1.
What I did:
Wipe: Dalvik/System/Data/Cache
Install Beta 7.9.22 or Stable 8.5.6.0 Kenzo firmware (tried with both)
Install RR image: RR-N-v5.8.5-20170924-kenzo-Final.zip
Install open gapps ARM64 7.1 (or not)
Wipe caches (also tried without wiping it)
Reboot
Bootloop
I know the first boot can take some time, so I let it run for 30+ minutes, still, only bootloop happened. Tried it a couple times, changing firmware, wiping caches at the end, ditching gapps etc. Images checked for md5 checksum on the phone, they are not corrupted. I was able to restore the EU ROM, but I really want to try out ResurrectionRemix. What could possibly the problem be?
Click to expand...
Click to collapse
Backup all of your data from internal storage and flash latest fastboot developer ROM and setup it. This will fix all issues regarding ROMs, zips, bootloops and firmware and any other. After that flash latest ZCX recovery as RedWolf recovery causes problems for flashing ROMs and zips as per my experiance. Then simply flash RR and gapps and boot and wait for 15 minutes and till then don't restart device.
hi i tryed to convert my redmi note 4x to global when flashing with mi flash tool i did it without clean and after that firmware finish installing but got stuck in bootloop now i flashed twrp and tryed to flash custom rom but again bootloop when i check my storage it shows 9gb now when its actual is 32gb i think i disturbed partitions any solution available?
Are you able to boot into TWRP?? If not flash TWRP first using fastboot.
Once you have access to TWRP boot into it and perform a full wipe (System + Data + Cache + Dalvik + Internal Storage). Perform a format too after wipe to be on the safer side. Now copy a custom ROM or MIUI ROM to your Internal Storage or SD card through a computer. Once copied install your ROM.
If you flashed custom ROM flash Gapps after flashing ROM. Reboot.
If you flashed MIUI, flash lazyflasher after that(or phone will be stuck at MI logo). Reboot.
You can find download links for lazyflasher here on XDA or you can google it too.
ArK96 said:
Are you able to boot into TWRP?? If not flash TWRP first using fastboot.
Once you have access to TWRP boot into it and perform a full wipe (System + Data + Cache + Dalvik + Internal Storage). Perform a format too after wipe to be on the safer side. Now copy a custom ROM or MIUI ROM to your Internal Storage or SD card through a computer. Once copied install your ROM.
If you flashed custom ROM flash Gapps after flashing ROM. Reboot.
If you flashed MIUI, flash lazyflasher after that(or phone will be stuck at MI logo). Reboot.
You can find download links for lazyflasher here on XDA or you can google it too.
Click to expand...
Click to collapse
awais_666 said:
hi i tryed to convert my redmi note 4x to global when flashing with mi flash tool i did it without clean and after that firmware finish installing but got stuck in bootloop now i flashed twrp and tryed to flash custom rom but again bootloop when i check my storage it shows 9gb now when its actual is 32gb i think i disturbed partitions any solution available?
Click to expand...
Click to collapse
@ArK96 is right but the only thing i suggest is to, flash miui and lazyflasher first so as to properly set up the initial firmware, and partitioning. After miui boots properly, you can do anything you want. :highfive:
ArK96 said:
Are you able to boot into TWRP?? If not flash TWRP first using fastboot.
Once you have access to TWRP boot into it and perform a full wipe (System + Data + Cache + Dalvik + Internal Storage). Perform a format too after wipe to be on the safer side. Now copy a custom ROM or MIUI ROM to your Internal Storage or SD card through a computer. Once copied install your ROM.
If you flashed custom ROM flash Gapps after flashing ROM. Reboot.
If you flashed MIUI, flash lazyflasher after that(or phone will be stuck at MI logo). Reboot.
You can find download links for lazyflasher here on XDA or you can google it too.
Click to expand...
Click to collapse
thank you for a quick reply yes i am able to go into twrp and i did format system data cache dalvik and internal storage and after wipe did format too but still stuck at same issue and when i open the internal storage in my computer it shows only 9gb storage
MyNameIsRage said:
@ArK96 is right but the only thing i suggest is to, flash miui and lazyflasher first so as to properly set up the initial firmware, and partitioning. After miui boots properly, you can do anything you want. :highfive:
Click to expand...
Click to collapse
ok so the normal global firmware will do? i didnt do with lazyflasher but will do it now
awais_666 said:
ok so the normal global firmware will do? i didnt do with lazyflasher but will do it now
Click to expand...
Click to collapse
you mean the global rom? yes the one you downloaded from en.miui.com
MyNameIsRage said:
you mean the global rom? yes the one you downloaded from en.miui.com
Click to expand...
Click to collapse
yes thats the one downloading now thank you guys for quick response ill update once done
@MyNameIsRage thank you for correcting me.
Yes. Please do flash MIUI and lazy first. Looks like you messed up your partitions.
Peace.
hey guys i tryed the following method luckily now storage is shown as 23 gb but when i flash miui rom in twrp the process doesnt complete its like the process bar goes till 95 percent and after that it keeps flashing but nothing happening i left the phone like this for 2 hours for 2 times but nothing happened am i doing something wrong here
awais_666 said:
hey guys i tryed the following method luckily now storage is shown as 23 gb but when i flash miui rom in twrp the process doesnt complete its like the process bar goes till 95 percent and after that it keeps flashing but nothing happening i left the phone like this for 2 hours for 2 times but nothing happened am i doing something wrong here
Click to expand...
Click to collapse
After flashing MIUI and lazy you flashed MIUI again is that what you are saying?
ArK96 said:
After flashing MIUI and lazy you flashed MIUI again is that what you are saying?
Click to expand...
Click to collapse
nop i formatted everything and then install miui rom for redmi note 4x which doesnt finish installing
awais_666 said:
nop i formatted everything and then install miui rom for redmi note 4x which doesnt finish installing
Click to expand...
Click to collapse
Go here and download the Global Stable worldwide release version firmware.
Boot into twrp wipe and format everything. Also after that reflash TWRP again using fastboot.
Once reflashed boot into TWRP and again perform a full wipe and format, then install the downloaded firmware zip. After that reboot TWRP and try flashing MIUI.
ArK96 said:
Go here and download the Global Stable worldwide release version firmware.
Boot into twrp wipe and format everything. Also after that reflash TWRP again using fastboot.
Once reflashed boot into TWRP and again perform a full wipe and format, then install the downloaded firmware zip. After that reboot TWRP and try flashing MIUI.
Click to expand...
Click to collapse
cool will try that in a while just a quick question i read somewhere that do the same process with red wolf recovery rather then twrp does that make any difference
awais_666 said:
cool will try that in a while just a quick question i read somewhere that do the same process with red wolf recovery rather then twrp does that make any difference
Click to expand...
Click to collapse
Yes. Red wolf is more MIUI friendly, it is made with OTA survival in mind. But your issue is that the ROM is not getting flashed. You can try what I said above about TWRP reflash, if it doesn't work you can go ahead and try redwolf. REDWOLF is nothing but modded TWRP, base code is still TWRP.
ArK96 said:
Yes. Red wolf is more MIUI friendly, it is made with OTA survival in mind. But your issue is that the ROM is not getting flashed. You can try what I said above about TWRP reflash, if it doesn't work you can go ahead and try redwolf. REDWOLF is nothing but modded TWRP, base code is still TWRP.
Click to expand...
Click to collapse
hey mate finally i got time to do the procedure i flashed the kernel that you told and on top of it the firmware and lazyflasher it went through in just few minutes and was all done and working perfectly now thanks alot
awais_666 said:
hey mate finally i got time to do the procedure i flashed the kernel that you told and on top of it the firmware and lazyflasher it went through in just few minutes and was all done and working perfectly now thanks alot
Click to expand...
Click to collapse
Good job mate.
I am using the kenzo version with 3gb ram.
I am currently on resurrection remix rom 6.1 and am updating the rom via dirty flashing it. I thought about rooting the rom via magisk flash and was thinking if the device can be updated after rooting it. If yes then how?
I don't understand the question if you are asking about if you can update with magisk, yes you can, I think you have to reflash magisk after updating the rom.
Tatoh said:
I don't understand the question if you are asking about if you can update with magisk, yes you can, I think you have to reflash magisk after updating the rom.
Click to expand...
Click to collapse
Sry.
I am talking about updating my rom. Can i update it once i have rooted it? Cause i read magisk does some changes in the boot sector and i don't want that while updating my rom(via dirty flashing) causing it to bootloop.
Varun Sharda said:
Sry.
I am talking about updating my rom. Can i update it once i have rooted it? Cause i read magisk does some changes in the boot sector and i don't want that while updating my rom(via dirty flashing) causing it to bootloop.
Click to expand...
Click to collapse
yes, you can update your ROM without any problems after root it's with magisk, don't worry it's won't cause bootloop or anything, if you want to update ROM , just flash ROM , gapps , wipe cache and dalvik cache then reboot.
Zasnizas said:
yes, you can update your ROM without any problems after root it's with magisk, don't worry it's won't cause bootloop or anything, if you want to update ROM , just flash ROM , gapps , wipe cache and dalvik cache then reboot.
Click to expand...
Click to collapse
Thanks you very much
Varun Sharda said:
Thanks you very much
Click to expand...
Click to collapse
one more things I forgot to tell you , you don't need to reflash magisk after flashing update rom coz twrp will automatically flash magisk after flashing rom. however you need to flash magisk again if you make a clean flash .
Typical disclaimer, etc etc.
You nuke your phone, I'm not paying for it
Thanks to @zefie for converting the kdz to a zip.
The zip
The anti-root removal
I flashed the zip in TWRP, rebooted to the OS, and was unrooted.
Reboot into the bootloader, and flashed TWRP.
Rebooted into recovery, flashed the lucye anti root removal, then rebooted into recovery again, and flashed Magisk.
Phone has been fine since Thursday.
Did you flash this dirty or clean?
I flashed it. Works GREAT. Dirty flashed.
Here's what I did...
-Flashed this zip
-Flashed Eliminator74 twrp image https://forum.xda-developers.com/lg-g6/development/twrp-t3828254 (you'll need to change from .zip to .img in TWRP)
-Rebooted to recovery
-Flashed antiroot removal zip
-rebooted to recovery
-Flashed magisk
-rebooted to system
-be patient
Can you please post a link to eliminator74 twrp build? I'm not sure if I have that one...
Link to his thread
jjohn7293 said:
Can you please post a link to eliminator74 twrp build? I'm not sure if I have that one...
Click to expand...
Click to collapse
Here's a link to his thread https://forum.xda-developers.com/lg-g6/development/twrp-t3828254
monark88 said:
I flashed it. Works GREAT. Dirty flashed.
Here's what I did...
-Flashed this zip
-Flashed Eliminator74 twrp image https://forum.xda-developers.com/lg-g6/development/twrp-t3828254 (you'll need to change from .zip to .img in TWRP)
-Rebooted to recovery
-Flashed antiroot removal zip
-rebooted to recovery
-Flashed magisk
-rebooted to system
-be patient
Click to expand...
Click to collapse
Dirty from 21B worked fine for me
Dirty flash from 20A worked perfectly.
FYI: This ROM has the recovery image removed, so if you already have TWRP, flashing this won't remove TWRP. No need to reinstall TWRP.
I actually started having bad idle drain. Flashed LOS for now, will go back to stock soon. If anyone else notices idle drain, please do let us know.
Thank you!
Only wiped caches
Dirty flashed over 20A
Reboot to recovery
Flashed anti root removal tool
Reboot to recovery
Flashed Magisk 17.3
Wiped caches again
Reboot to system
Showed Android is updating screen
All is well so far!
Still running 17A [rooted]... think dirty flashing this will be alright? Been looking for a good time to update.
Coming from 20A, battery life has been about the same- maybe even a bit better. All's well.
MetalMan2 said:
Still running 17A [rooted]... think dirty flashing this will be alright? Been looking for a good time to update.
Click to expand...
Click to collapse
Go for it. Be sure to install Magisk for root. SuperSU (if you happen to be using it) doesn't work anymore.
gl;hf
BeardKing said:
Coming from 20A, battery life has been about the same- maybe even a bit better. All's well.
Go for it. Be sure to install Magisk for root. SuperSU (if you happen to be using it) doesn't work anymore.
gl;hf
Click to expand...
Click to collapse
Thanks for instilling confidence. It all seems to have worked out just fine. :good:
Time will tell how battery life and what-not compares to 17A.
MetalMan2 said:
Thanks for instilling confidence. It all seems to have worked out just fine. :good:
Time will tell how battery life and what-not compares to 17A.
Click to expand...
Click to collapse
Good to hear. :good:
US997 14a to 21c (Keeping Root)
I'm using the US997 still on 14a (rooted, TWRP installed) would I need to (CLEAN) flash up to 17a and then the 21c? After that flash the anti-root and flash an updated version of Magisk? (currently stuck on v16.4) Can't find my stock boot image to update. Only got the phone back in October and stopped all updates before I unlocked the bootloaded, installed TWRP and used Magisk to get root. I had a hard time finding a version of TWRP with a kernel that worked for my phone (Melina v3.2.1-0) would I have to update that also? Was waiting to see the highest update I could get without losing root. Anyone done this? Any help would be greatly appreciated.
My wife and I both have G6 phones. On mine, I dirty flashed this over 20A with absolutely no problem. My sequence was: flash Eliminator74 TWRP, reboot to recovery, flash 21C zip, reboot to recovery, flash lucye anti-root, reboot to recovery, flash Magisk, wipe cache and Dalvik, reboot to system. I'm guessing I really didn't need those extra reboots but it felt safer. Phone is perfectly stable.
On my wife's phone it was another matter. Her data partition was encrypted, due to the phone having been reimaged by LG during warranty repair. I'd rooted it but never decrypted it. None of the default ways to decrypt it worked, so I was forced to format /data. I thought that would do it, but the resulting installation was unstable, and wouldn't get through setup successfully without continually looping, freezing, and returning to start. Finally I realized it was probably flashing over the LG factory image that caused the problem. I wiped /system and started over, and had much better results.
LPMatt said:
Thank you!
Only wiped caches
Dirty flashed over 20A
Reboot to recovery
Flashed anti root removal tool
Reboot to recovery
Flashed Magisk 17.3
Wiped caches again
Reboot to system
Showed Android is updating screen
All is well so far!
Click to expand...
Click to collapse
MetalMan2 said:
Thanks for instilling confidence. It all seems to have worked out just fine. :good:
Time will tell how battery life and what-not compares to 17A.
Click to expand...
Click to collapse
So I tried this coming from 17A.
When I reboot to recovery on the first go I have the Oreo bootloader screen and it goes into the white reset menu. All encryption is enabled again.
I have to fastboot bootloader, install TWRP recovery, wipe/format and then restore my 17A to recover the phone.
What steps did you take MetalMan2?
Malezar said:
So I tried this coming from 17A.
When I reboot to recovery on the first go I have the Oreo bootloader screen and it goes into the white reset menu. All encryption is enabled again.
I have to fastboot bootloader, install TWRP recovery, wipe/format and then restore my 17A to recover the phone.
What steps did you take MetalMan2?
Click to expand...
Click to collapse
This probably won't help, but are you using this version of TWRP?
BeardKing said:
This probably won't help, but are you using this version of TWRP?
Click to expand...
Click to collapse
Yep. Just downgraded the bootloader back to 17a through it.
Malezar said:
What steps did you take MetalMan2?
Click to expand...
Click to collapse
I exactly followed LPMatt's list which you quoted.
Still no problems. Pretty sure the battery life is less than 17A, but I think we all know that and for me it's "good enough".
How to remove root checker?