So i rooted my phone sometimes ago, and it worked fine at first but after some reboots it is now stuck at Redmi logo and would boot to fastboot mode after a while. Now i want to share my experience so people can be more careful, i may be a newbie but i do want to help people too.
So here's what my phone is using, CorvusOS 7.0 and SiLonT kernel and no more modifications other than that. Now i have read stuff online that some people have experienced bootloops and some can't boot to the OS they rooted their device with magisk. I have also read that dirty flash may solve the problem. But if you're already facing this problem maybe you can try these methods below:
Method 1: probably the easiest one, wipe the Dalvik and the cache
1. Reboot to your custom recovery
2. Go to advanced wipe (location and UI may differs between custom recoveries)
3. Simply tick Dalvik and cache and untick anything else
4. Reboot
Method 2: uninstalling magisk (this will unroot your device)
1. Download magisk uninstaller.zip (if you didn't downloaded it already from the start. Also make sure the uninstaller is the same version as your magisk version, idk what will happen if you do it with a different version but just in case )
2. Reboot to your custom recovery
3. And simply just flash/install the magisk uninstaller.zip, this will delete all magisk's files
4. Wipe Dalvik and cache (just in case)
5. Reboot
Method 3: dirty flash (for custom ROMs)
1. Uninstall magisk (follow method 2)
2. Get/download your custom ROM you are using (make sure it's the same ROM and version as the ROM you're using rn)
3. Flash it without wiping anything
4. Wipe Dalvik and cache (just in case, again)
5. Reboot
Method 4: reinstall/install your ROM, for custom ROMs users (I'm sorry i am not experienced with XiaomiFlashTool so i can't tell you how to flash stock ROM)
1. Backup all data cause this will erase all your data
2. Reboot to recovery
3. Uninstall magisk (follow method 2)
4. Wipe system, data, cache, Dalvik (the usual stuff you would wipe before installing a custom a ROM)
5. Install your chosen ROM
6. Wipe Dalvik and cache (just in case)
7. Reboot
If those methods above doesn't work you can try searching a tutorial on flashing the stock ROM on the internet, but if you still didn't manage to get your phone boot to the OS again then i am sorry to say that you have to take your phone to the nearest repair center.
So, what's the cause of this problem?
Well, it's simple, every human make mistakes, At least once. So it is normal to make mistakes. The developers are humans too so it is normal for them to make mistakes too, so instead blaming them we should support them and give them advice. But on the other side you may did a mistake too, probably a similar mistake that i did. Like maybe you did something wrong according to the tutorial, or you flashed an incompatible version of magisk, and etc. So from now on always ask if it's compatible, whether it's about magisk versions, ROM compatibility, kernel compatibility, recovery compatibility, and etc. And always double check just in case.
If i did something wrong tell me down below and I'll fix it as soon as possible.
Peace.
One quick little note: i fixed my device by doing a dirty flash (method 3) just to let you know
Edit: Phone won't boot after uninstalling magisk*, that was supposed to be title. Sorry I just realized sometimes ago
This happens to me all the time when flashing Android 11 ROMS. Curiously this doesn't happen when flashing Android 10 ROMs. I also never had this issue with TWRP, only OrangeFox.
But it could be other things too. For example, Xiaomi.eu 12.5 always go into a bootloop here, and trying to go back to any other ROM after flashing it leads to a boot loop. The fix is to flash disabled vbmeta if you're flashing xiaomi.eu 12.5. That might be the fix for A11 roms too but I never tried.
More than once it happened to me too that no matter what I did the phone would be stuck in bootloops with any ROM, any recovery. In that case, flashing stock rom via fastboot fixed the issue.
Related
Hello everyone, I have a problem with my xperia S, any help would be greatly appreciated! Let's start from the beginning, I'll try to be brief :
So, I flashed TWRP recovery using the app "RASHR" (I was using the Pure AOSP Lollipop rom when doing this, if it can help), which caused my phone to always boot the recovery and nothing else. I managed to flash the rom again (I made sure to wipe using "factory reset" and "dalvik cache" before installing), and it seemd to work perfectly, but then I rebooted the phone, and got stuck at the sony logo, no recovery available.
I flashed TWRP recovery (stock-6.1.A.0.452-twrp-2.4.0.0.elf) using flashtool, then tried to install another rom (Paranoid Android, found on this thread : http://forum.xda-developers.com/showthread.php?t=2573345). The first boot was successful, but as soon as I reboot the phone, I'm stuck in a bootloop again, with a little difference : when the sony logo appears, the led becomes pink for a few seconds. No access to recovery. Then the led lights off, the logo disappears, and the phone reboots. Again and again. I just reinstalled the same recovery and tried to wipe and fix permissions, but it does not solve the bootloop, and I don't know what to do...
Could it be possible that "rashr" did a bad install of TWRP and corrupted my recovery/bootloader partition or something ?
EDIT : I reinstalled Pure AOSP Lollipop, and now for some reason, no boot loop anymore... I don't understand why, but as long as it works... problem solved !
LegatoExia said:
Hello everyone, I have a problem with my xperia S, any help would be greatly appreciated! Let's start from the beginning, I'll try to be brief :
So, I flashed TWRP recovery using the app "RASHR" (I was using the Pure AOSP Lollipop rom when doing this, if it can help), which caused my phone to always boot the recovery and nothing else. I managed to flash the rom again (I made sure to wipe using "factory reset" and "dalvik cache" before installing), and it seemd to work perfectly, but then I rebooted the phone, and got stuck at the sony logo, no recovery available.
I flashed TWRP recovery (stock-6.1.A.0.452-twrp-2.4.0.0.elf) using flashtool, then tried to install another rom (Paranoid Android, found on this thread : http://forum.xda-developers.com/showthread.php?t=2573345). The first boot was successful, but as soon as I reboot the phone, I'm stuck in a bootloop again, with a little difference : when the sony logo appears, the led becomes pink for a few seconds. No access to recovery. Then the led lights off, the logo disappears, and the phone reboots. Again and again. I just reinstalled the same recovery and tried to wipe and fix permissions, but it does not solve the bootloop, and I don't know what to do...
Could it be possible that "rashr" did a bad install of TWRP and corrupted my recovery/bootloader partition or something ?
EDIT : I reinstalled Pure AOSP Lollipop, and now for some reason, no boot loop anymore... I don't understand why, but as long as it works... problem solved !
Click to expand...
Click to collapse
You flashed the TWRP in wrong way. You need to flash it by this method.
Mirhawk said:
You flashed the TWRP in wrong way. You need to flash it by this method.
Click to expand...
Click to collapse
Hello, and thanks for the answer ! After a few days using the Pure AOSP rom and rebooting several times without any problem, I just got a bootloop again yesterday, forcing me to reflash my rom to be able to use the phone again... will your method (including your tutorial in your signature, which I'm trying as I write this) solve the problem once and for all ? It's a real pain to redownload all my apps again and again and again because of those bootloops =(
Edit : finished following your tutorials, everything seems to work for the moment, hope it will stay stable this time... thanks for your help )
LegatoExia said:
Hello, and thanks for the answer ! After a few days using the Pure AOSP rom and rebooting several times without any problem, I just got a bootloop again yesterday, forcing me to reflash my rom to be able to use the phone again... will your method solve the problem once and for all ? It's a real pain to redownload all my apps again and again and again because of those bootloops =(
Click to expand...
Click to collapse
What did You do before the bootloop was caused? Did You try to flash the TWRP again?
Mirhawk said:
What did You do before the bootloop was caused? Did You try to flash the TWRP again?
Click to expand...
Click to collapse
No, I didn't, I was too afraid of creating another problem xD I just used the phone normally, installed apps from the play store, the last one being nova launcher (but I rebooted a few times after that without any issue)., things like that.
But after applying your tutorials to flash the Lollipop Pure AOSP rom, I think the problems were caused by :
1) a wrong recovery and/or flashing method : previously I used "stock-6.1.A.0.452-twrp-2.4.0.0.elf" which I flashed directly via flashtools with the phone in fastboot mode with the command "fastboot flash boot xxxxxx.elf". And although I didn't reinstall it after flashing the ROM, I suppose it left something in the recovery partition that caused the bootloop... ?
2) the fact that I didn't flash any "boot.img" at all before installing the ROM... inf fact, I didn't even knew it was necessary !
3) a bad ROM installation procedure : wipe, flash rom, gapps and SuperSU and THEN wiping cache and dalvik, restart
4) all of the above (!)
Anyways, after doing it "the right way", everything seems to work correctly for the moment. After installing the ROM, I followed your recovery tutorial using "openrecovery-twrp-2.8.5.0-LT26i.img", hope I did the right thing this time, hahah. Thank you again for your help !
LegatoExia said:
No, I didn't, I was too afraid of creating another problem xD I just used the phone normally, installed apps from the play store, the last one being nova launcher (but I rebooted a few times after that without any issue)., things like that.
But after applying your tutorials to flash the rom AND the recovery, I think the problems were caused by :
1) a wrong recovery and/or flashing method : previously I used "stock-6.1.A.0.452-twrp-2.4.0.0.elf" which I flashed directly via flashtools with the phone in fastboot mode with the command "fastboot flash boot xxxxxx.elf". And although I didn't reinstall it after flashing the ROM, I suppose it left something in the recovery partition that caused the bootloop... ?
2) the fact that I didn't flash any "boot.img" at all before installing the ROM... inf fact, I didn't even knew it was necessary !
3) a bad ROM installation procedure : wipe, flash rom, gapps and SuperSU and THEN wiping cache and dalvik, restart
4) all of the above (!)
Anyways, after doing it "the right way", everything seems to work correctly for the moment. Thank you again for your help !
Click to expand...
Click to collapse
Glad that it is worked for You. Yes, You did somethings wrong, which caused You bootloop, better explained as below:
1) The "stock-6.1.A.0.452-twrp-2.4.0.0.elf" is the stock kernel of ICS version of Xperia S. So if You flash it with a ROM, Your ROM won't boot.
See, each ROM consist of two main parts, one the kernel and other the is the remaining of ROM(apaps, data etc.) A ROM is compatible only with certain kernels, and if wrong kernel is used with a ROM, the ROM won't boot. This is what You were doing, using a stock kernel on non stock based ROM.
2) This essentially doesn't lead to boot loop. This step needs to be done sometimes if You occur a error while flashing ROM via TWRP sometimes.
3) Yes, this sometimes does cause issue, the procedure is always for a clean flash, -Wipe system, wipe data, wipe cache and wipe dalvik cache. Flash ROM and immediately wipe cache and dalvik cache.
Mirhawk said:
Glad that it is worked for You. Yes, You did somethings wrong, which caused You bootloop, better explained as below:
1) The "stock-6.1.A.0.452-twrp-2.4.0.0.elf" is the stock kernel of ICS version of Xperia S. So if You flash it with a ROM, Your ROM won't boot.
See, each ROM consist of two main parts, one the kernel and other the is the remaining of ROM(apaps, data etc.) A ROM is compatible only with certain kernels, and if wrong kernel is used with a ROM, the ROM won't boot. This is what You were doing, using a stock kernel on non stock based ROM.
2) This essentially doesn't lead to boot loop. This step needs to be done sometimes if You occur a error while flashing ROM via TWRP sometimes.
3) Yes, this sometimes does cause issue, the procedure is always for a clean flash, -Wipe system, wipe data, wipe cache and wipe dalvik cache. Flash ROM and immediately wipe cache and dalvik cache.
Click to expand...
Click to collapse
Okay, now I understand ! There are so many roms, kernels and things like that on the internet, it was quite confusing...
Thanks again good sir, your help was a precious time saver =D
LegatoExia said:
Okay, now I understand ! There are so many roms, kernels and things like that on the internet, it was quite confusing...
Thanks again good sir, your help was a precious time saver =D
Click to expand...
Click to collapse
can you please tell me how did you get out of the boot loop to begin with? i can't do anything...
Frostymoon said:
can you please tell me how did you get out of the boot loop to begin with? i can't do anything...
Click to expand...
Click to collapse
I guess You are on stock firmware and flashed the "stock-6.1.A.0.452-twrp-2.4.0.0.elf" or the twrp.img file via fastboot directly. Flash the DoomKernel from here via flashtool as kernel and it will work with stock and have recovery too. Use the blue coloured "Download Now" button and the extension of file is .elf.
My Xperia ZL won't allow me to install a custom ROM.
Here are the steps I've taken.
1. Updated to 10.6.... (Lollipop fw) via Flashtool
2. Boots correctly, everything seems to work.
3. Flashed boot.img from Paranoid Android and went into TWRP to flash the ROM zip (wiped cache, system and data before).
Did step 3 to test the same for OmniRom too.
4. Phone boots, shows Bootanimation, shows Optimizing apps, then hangs after finish and does step 4 again.
Please help me, I could install custom ROMs on the device before, suddenly it does not work anymore.
Note: EVERYTHING works fine with Stock. Flashed stock ftf multiple times and tried these steps.
Thanks for your help
It seems to be a Bootloop. Try below steps;
1. Through TWRP wipe (system+cache+dalvic cache+data+android secure)
2. Install ROM.zip
3. Wipe cache+dalvic cache+data
4. Reboot
Hope the above steps helps you
Regards,
hitman-xda
@hitman-xda I've tried these steps, except for android secure.
What is that partition and what does it do?
Cannot find it in Advanced Wipe of TWRP.
Thanks
It is the mysterious part. Actually no one knows about it. Some says, it contains secured links/data of some apps.
If you are clean flashing ROM, that's means you have to wipe everything except storage part. That's the reason I mentioned it.
If you can't find it, just leave it
@hitman-xda So I've already done what you suggested, with no luck.
Guess I'm stuck on stock till someone helps me
Thanks for your reply
did you install de correct kernel?
maybe you should wipe everything, install the correct kernel and after that, install the custom ROM
i don't now if it will work, but at least try
I did fastboot flash boot boot.img (got it from ROM zip)
Then erased everything and flashed ROM.
No luck
Does that Paranoid Android was built for your phone?
Your phone loops from 'optimizing apps' , that means your phone is unable to load dalvic/art for the apps.
Also check weather PA ROM can be flashed over lollipop, if not then you have to downgrade an then try the same procedure.
Also you can download stock kernel with recovery, flash it and then directly try to flash your respective ROM.
Usually ROM.zip contains kernel and get flashed during installation of zip, just the thing is they can be flashable over some selective android versions.
After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
RDChase said:
Try this:
1. Wipe cache, dalvic cache, data, system
2. Install CM13 again, along with your gapps(google apps if you didn't know, custom ROMs never come with them, optional)
3. Boot it, it should work
You cannot switch ROMs without wiping data. Bad things happen.
You must clean flash when:
1. Switching between a stock ROM to a custom ROM
2. Downgrading Android versions (5.1 to 5.0)
3. Switching custom ROMs (I.E. CM13 to AICP)
4. When the ROM's thread warns to (switching keys)
5. Switching between nightly builds and stable.
When you're updating nightlies, you shouldn't have to though.
Click to expand...
Click to collapse
Just did it, it still seems to be booting like it previously was. Wiped cache, dalvic, data, and system and then installed CM13 and gapps. Still booting as I write this.
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
RDChase said:
Since that failed, check your download, make sure nothings bad. If its bad, redownload, if not, idk.
If you post your recovery logs, or what the console says, that will help me figure out what's going on.
Also, is your phone the triband model (l710t)?
Are you flashing anything else at the same time?
The more info you give, the better.
Click to expand...
Click to collapse
I've kind of given up at this point. Even CM12 doesn't work. The only thing that seems to work is the stock rom. My phone is the regular SPH-L710 model. I didn't even know the L710t was a thing.
I have the same problem, and sometimes it boot in the system setup mode, but the sensor is not working, i can turn on airplane mode, reboot or power off, and sensor works, what happend i dont know((
ovil101 said:
After flashing TWRP with Odin, I boot into recovery and wipe the dalvik cache. I then go to install the CM13 zip file, and it works. I wipe Dalvik again and reboot in the os. This is where it just shows the CM boot screen infinitely. Nothing else. What is up. I am using the latest TWRP and CM13 release.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
1vankill1 said:
http://forum.xda-developers.com/showthread.php?t=2755793
helped)))
Click to expand...
Click to collapse
That just seems to be a stock rom.
yes it stock rom, after it was installed, I was able to install 13 cm
Hello,
I don't know why my lg g3 phone doesn't want boot on custom rom.
I have the LG G3 d855 model, 16gb memory and here are my procedure to install every custom rom :
1. Flash Stock ROM using LGUP (the version of the firmware is not important but the possibility to root is)
2. Install KingRoot and get root
3. Install AutoREC and enter to the recovery
8. Flash Recovery TWRP 3.1.0-2
9. Reboot to the new recovery
10. ADVANCED WIPE (wipe cache, dalvik cache, data and SYSTEM)
11. Flash baseband 21C
12. Flash CUSTOM rom
13. Wipe cache and dalvik cache
14. Flash Gapp
15. Wipe cache and dalvik cache
16. Reboot
I think I did nothing bad...
but the phone does not start and it stays at the initial logo screen (not the LG logo, but the custom rom logo). I waited over 10 minutes to boot but nothing. Even though I install the identical rom again or install an anoter rom, each time the same issue.
This happens with all custom rom (xenonhd, resurrection remix, and now lineageOS)
I can use and boot on stock rom but each time I want to install a custom rom, my phone doesn't want to boot. The phone display stays at the initial rom logo screen.
It seems that I am alone to have this problem.
I don't know why and I search everywhere to find out the solution...
PS : My phone never restart by itself. I never have bootloop with my phone when I using stock rom and same with custom rom..
The problem is the boot with a custom rom. The phone don't want to boot and stay on logo loading...
Any suggestion may be help.
Thank you.
1. Once you installed TWRP you don't have to go back to stock to switch roms. From then on you can just download zips and flash them.
2. You need to delete everything (including system) except internal and external storage ( so you can still flash the zip for xceed, otherwise you will delete it). Remember that you will lose all your apps including your data with it. You can backup them with titanium backup tho. Pictures and video's will still be there as they are stored on the internal or external storage.
3. You also need to flash the GAPPS package after flashing rom, for xceed (7.1.1), pick nano (ARM)
4. Wipe cache and dalvik after flashing and reboot.
5. Make a backup before you do so !!!!!!
Good luck.
Jornwitt said:
1. Once you installed TWRP you don't have to go back to stock to switch roms. From then on you can just download zips and flash them.
2. You need to delete everything (including system) except internal and external storage ( so you can still flash the zip for xceed, otherwise you will delete it). Remember that you will lose all your apps including your data with it. You can backup them with titanium backup tho. Pictures and video's will still be there as they are stored on the internal or external storage.
3. You also need to flash the GAPPS package after flashing rom, for xceed (7.1.1), pick nano (ARM)
4. Wipe cache and dalvik after flashing and reboot.
5. Make a backup before you do so !!!!!!
Good luck.
Click to expand...
Click to collapse
Hello,
1. I think that but with specific rom, some people tell us to flash stock rom before flashing a custom rom. eMMC bug related ?
2. Deleting the system changes nothing because the system is wiped when I flash the rom, right ?
3. if the rom boot first then I will install Gapps. Else, I don’t install because the rom doesn’t want to boot.
1. Well .. I've been switching between fulmics,xceed,rr, .. etc without any problem so no, there is no need to go back to stock everytime.
2. Try it, you won't be able to boot until you flash a new rom, but it could help. That's why you take a backup in the first place. It is more 'clean' and if you don't try it you won't know.
3. Sometimes you have to flash gapps directly after the rom or you will be in for a bad time if you do afterwards.
Once you have TWRP recovery installed it's the easiest thing ever to flash a new rom. Make sure your zip files are downloaded okay. Download the MD3 to check it. Try to download via MEGA app or so, because browsers downloads tend to have errors sometimes.
Apart from that. Don't root via kingroot. They have had some suspicious cases where malware was installed on the phone when rooting.
If nothing's works. Go back to full stock through KDZ, root wit your PC, install TWRP via autorec, go to recovery, wipe everything, install modem 21C, install rom and gapps, wipe cache, reboot. Don't try anything other than that.
I have the same problem
Jornwitt said:
1. Well .. I've been switching between fulmics,xceed,rr, .. etc without any problem so no, there is no need to go back to stock everytime.
2. Try it, you won't be able to boot until you flash a new rom, but it could help. That's why you take a backup in the first place. It is more 'clean' and if you don't try it you won't know.
3. Sometimes you have to flash gapps directly after the rom or you will be in for a bad time if you do afterwards.
Once you have TWRP recovery installed it's the easiest thing ever to flash a new rom. Make sure your zip files are downloaded okay. Download the MD3 to check it. Try to download via MEGA app or so, because browsers downloads tend to have errors sometimes.
Apart from that. Don't root via kingroot. They have had some suspicious cases where malware was installed on the phone when rooting.
If nothing's works. Go back to full stock through KDZ, root wit your PC, install TWRP via autorec, go to recovery, wipe everything, install modem 21C, install rom and gapps, wipe cache, reboot. Don't try anything other than that.
Click to expand...
Click to collapse
Hello,
I have a question.
Can you give me a gapp 100% compatible with all custom rom with android 7.1.2, because i think opengapp are not reliable. Maybe the gapp will cause my issue and the rom won't boot.
Can i use this one https://forum.xda-developers.com/on...isited-slim-gapps-6-0-7-0-unofficial-t3462088 ?
I always use PICO version of gapp
Thank
Hi everyone,
I recently made a fresh install of the latest OOS ROM on my Onplus 5T (OOS 9.0.8). After reinstalling all the apps and data I tried to root the phone. My bootloader was already unlocked, so I just went on to flash TWRP (first tried the official TWRP 3.3.1 dumpling, and then the 3.3.1 blu_spark version). Then I tried to flash Magisk via TWRP (tried versions 19.2, 19.3, 19.4), and every time I try to reboot I get stuck on a black screen with the cyan led on, and I have to uninstall Magisk in order to reboot on the phone. Also the phone is encrypted, and I have a the Microsoft Intune Portal app installed to use some work apps, but I don't know if that can be the source of the problem.
If you have any idea on how to successfully flash Magisk, that would be amazing.
Thanks in advance :good:
I use the same version of ROM and magisk I use is canary build . Working fine. (even its not canary build I also can boot successfully)
you might need to check if some apps you install might cause this.
my recommendation is clear /data and starts fresh then root it before installing any apps. to see if it working fine or not.
also after you flash magisk do you try to wipe cache, dalvik-cache?
and how long are you waiting for its to boot? normally it would take more time than normal boot (without magisk)
Just connect to to ADB and delete vendor.. recovery.. rom.. radio.. antennaa.. ect everything. Get yourself a stock full rom and flash that through ADB. Then flash custom recovery, custom rom, gapps, custom kernel, magisk. thats it. find stock rom on manufacturers data server. I did this to a different phone I had but this is the way to 100% fix everything... by purging the phone to nothing. You can however do a twrp backup before doing so.
Thanks for the input, I will try first to reflash the ROM and root before installing any apps, and see if it works in order to avoid the long process of restoring all my data. I do wipe cache/dalvik cache before and after every flash. If that doesn't work I will try another time a clean flash and tell you if it worked.
I just reflashed the ROM and right after I flashed Magisk 19.3, then rebooted and it worked. Not sure what the issue was but the problem is now resolved. Thanks guys for the advice.