So I posted a thread few days ago but this case is different
Phone's rooted and have TWRP 3.0.2.1-ashyx, I flashed Aryamod note 7 for my a500h
everything went fine and after that flashed the patch wiped dalvik restarted and it boots to TWRP and its stuck on this loop
Is there any workaround?
What causes this TWRP loop ?
MJ999 said:
So I posted a thread few days ago but this case is different
Phone's rooted and have TWRP 3.0.2.1-ashyx, I flashed Aryamod note 7 for my a500h
everything went fine and after that flashed the patch wiped dalvik restarted and it boots to TWRP and its stuck on this loop
Is there any workaround?
What causes this TWRP loop ?
Click to expand...
Click to collapse
PM me if you're interested in an update with possible reboot fix.
For now just reflash twrp with auto-reboot on.
Related
I rooted my phone and installed the cyan fox rom in December and it was working flawlessly, but yesterday it would randomly shut down and then get stuck in a boot loop or wouldn't boot up. So i installed a stock rom and there are no problems with that. Today I installed cyanogen mod on now the problem is coming up again. I have tried wiping dalvik cache, factory resting and that doesn't seem to do much.
Razorbrick said:
I rooted my phone and installed the cyan fox rom in December and it was working flawlessly, but yesterday it would randomly shut down and then get stuck in a boot loop or wouldn't boot up. So i installed a stock rom and there are no problems with that. Today I installed cyanogen mod on now the problem is coming up again. I have tried wiping dalvik cache, factory resting and that doesn't seem to do much.
Click to expand...
Click to collapse
Install Stock Rom again or ask in Cyanogenmod community
Recovery
What recovery are you using? Is it the latest version?
Was on cloudy's latest gpro2 rom with dorimatrix 4.8.1, updated to 4.9 and wiped cache and dalvic cache and upon first boot everything I would click force closed after a minute or so so I attempted rebooting. It would then go into a bootloop. I adb rebooted into recovery, wiped the caches, and flashed 4.8.1. It now did the same thing as it did before, followed by a bootloop when I rebooted it. Decided to try flashing to a different rom, so I did a complete backup and sent over the latest CM11 nightly. Wiped all and flashed, and now I'm bootlooping at the CM screen with no recovery access.
I remembered when I was already bootlooping that I needed to flash the 4.2.2 partitions to use an AOSP roms. A little too late huh. Now I'm stuck at the CM bootanimation and no ADB. Are my only options to use mobile odin and start over from or can you guys come up with something else?
mejorguille said:
Was on cloudy's latest gpro2 rom with dorimatrix 4.8.1, updated to 4.9 and wiped cache and dalvic cache and upon first boot everything I would click force closed after a minute or so so I attempted rebooting. It would then go into a bootloop. I adb rebooted into recovery, wiped the caches, and flashed 4.8.1. It now did the same thing as it did before, followed by a bootloop when I rebooted it. Decided to try flashing to a different rom, so I did a complete backup and sent over the latest CM11 nightly. Wiped all and flashed, and now I'm bootlooping at the CM screen with no recovery access.
I remembered when I was already bootlooping that I needed to flash the 4.2.2 partitions to use an AOSP roms. A little too late huh. Now I'm stuck at the CM bootanimation and no ADB. Are my only options to use mobile odin and start over from or can you guys come up with something else?
Click to expand...
Click to collapse
Fixed it... realized I still had recovery active, booted into it with the button combo, wiped, installed cloudy pro, all is good.
My phone came with version 66.77.... (MIUI 6) from the reseller.
I have installed TWRP, rooted the device using adb and then flashed 5.9.24. So far so good.
After some time i decided to try AOSP ROM. I made a backup in TWRP and then flashed AOSP using TWRP. No problems so far (cleared cache, dalvik etc)
Then I wanted to revert back to 5.9.24. I cleared cache dalvik etc, and then I cannot remember anymore if i have reflashed 5.9.24 or restored the backup made previously from TWRP, the thing I wasn't able to boot into recovery anymore. The phone was stuck on the teamwin logo if booted into recovery but normal boot was working fine.
Then i reflashed twrp using adb.
After doing that, my phone was still stuck on the teamwin logo when booting into recovery, but with normal booting i was getting infinite boot loops at Mi logo screen.
After several ours of tries, i was able to solve the normal booting problem by flashing the stock recovery (so the phone is now back on the 5.9.24 - and working fine) but when I try to flash twrp using adb the same symptoms as before:
- Recovery boot - stuck on teamwin logo screen
- Normal boot - boot loops
I already tried to flash via Updater app, Flashify and Windroid nothing worked.
Can anyone help me to get this custom recovery working, please?
Thanks
Regards,
Nick
lukke04 said:
My phone came with version 66.77.... (MIUI 6) from the reseller.
I have installed TWRP, rooted the device using adb and then flashed 5.9.24. So far so good.
After some time i decided to try AOSP ROM. I made a backup in TWRP and then flashed AOSP using TWRP. No problems so far (cleared cache, dalvik etc)
Then I wanted to revert back to 5.9.24. I cleared cache dalvik etc, and then I cannot remember anymore if i have reflashed 5.9.24 or restored the backup made previously from TWRP, the thing I wasn't able to boot into recovery anymore. The phone was stuck on the teamwin logo if booted into recovery but normal boot was working fine.
Then i reflashed twrp using adb.
After doing that, my phone was still stuck on the teamwin logo when booting into recovery, but with normal booting i was getting infinite boot loops at Mi logo screen.
After several ours of tries, i was able to solve the normal booting problem by flashing the stock recovery (so the phone is now back on the 5.9.24 - and working fine) but when I try to flash twrp using adb the same symptoms as before:
- Recovery boot - stuck on teamwin logo screen
- Normal boot - boot loops
I already tried to flash via Updater app, Flashify and Windroid nothing worked.
Can anyone help me to get this custom recovery working, please?
Thanks
Regards,
Nick
Click to expand...
Click to collapse
Tried this: http://en.miui.com/thread-152550-1-1.html?mobile=2
Sent from my 2014817 using Tapatalk
timberwolf60 said:
Tried this: http://en.miui.com/thread-152550-1-1.html?mobile=2
Sent from my 2014817 using Tapatalk
Click to expand...
Click to collapse
i saw the request of the message but i am not using a custom recovery on my phone,i use a custom dev rom made by miui france.
i think some china dev rom comes rooted by default with custom installer updater and gapps like mine.
i think twrp is not fully compatible with this device yet.
Have you try with sp flash tool method ?
http :// en.miui.com/forum.php?mod=viewthread&tid=156838&extra=page%3D4&mobile=2
I just installed TWRP for the first time ever. I used the Flashify App from the Play Store, installed it and gave it root permissions and just selected the TWRP image on the phones internal store. Seemed to work just fine and did not have to plug my phone into a computer
I recntly bought 16GB UK version that came with 5.1 and OTA updated it to the most recent MM (sorry didin't note its exact number). I then succesfully flashed TWRP 3.0.2-r1 and tried to factory reset it but it gave me a lot of errors, so I restarted TWRP and tried again - successfuly. I then tried to flash GtrCrafts ROM (here) and it flashed succesfuly but stuck on boot animation for nearly half an hour so I rebooted back to TWRP and tried again - with the same effect. I then tried Marshmallux - and exactly the same problem happened. Today I flashed Resurrection Remix and everything was perfectly fine - happy that my phone "resurrected" I tried flashing stock based ROMs (same as before) and they kept stucking on boot animation again. After all I downloaded stock firmware (XT1562_LUX_RETEU_6.0_MPD24.65-18.1_cid7_subsidy-DEFAULT_CFC.xml) and flashed it with fastboot - the only problem was I couldn't flash bootloader.img, but just skipped that and flashed the rest - after the long few minutes my phone booted into system, so I thought it's finally OK, but no - I first checked if TWRP is still there but rebooting into recovery just left me with black screen so I flashed TWRP again (same version) and after this... I couldn't reboot into system (from TWRP menu) - it just kept rebooting TWRP on and on, so I turned my phone off, booted into bootloader and from bootloader - into system, with success. Trying to flash stock-based ROMs brought all the same problems back so I just gave up for now and wondering what could be wrong and is it fixable. Why would CM based RR flash and boot fine but not Marshmallux and GtfCraft's one? Anyone had the same issues or knows what's wrong? Could it be TWRP problem, phones problem, or a jinx?
Thanks.
Try flashing stock rom with rsdlite
Sent from my XT1562 using XDA-Developers mobile app
pijes said:
Try flashing stock rom with rsdlite
Sent from my XT1562 using XDA-Developers mobile app
Click to expand...
Click to collapse
I just realised OP messed instructions in this thread - http://forum.xda-developers.com/moto-x-play/general/guide-how-to-flash-factory-image-return-t3261486
I'll try again with proper ones...
OK, flashing stock firmware fixed all issues.
I installed TWRP 3.1.1 using the ODIN patched version and was successful. I had let the system boot into the samsung original stock from where you see "HI" then I rebooted it into TWRP to attempt flashing and I got the /data partition couldn't be wiped. So I ran some of the other repair functions in TWRP and that appear to have fixed it. I then flashed with the latest LineageOS, Gsap, and Magistk20. When it boots up the LineageOS I'm stuck on the Lineage Splash screen. I've let it run over night and it has't changed anything. Any advice?
I recommend trying to wipe the system and reinstall LineageOS with flashing Magisk. If the same problem occurs. Just wipe the system and flash LineageOS without installing Magisk.
secretwolf98 said:
I recommend trying to wipe the system and reinstall LineageOS with flashing Magisk. If the same problem occurs. Just wipe the system and flash LineageOS without installing Magisk.
Click to expand...
Click to collapse
Here's how I think I fixed it.
booted into TWRP
advanced wipe, Factory reset
booted it into TWRP
Flashed the LineageOS
boot into LineageOS
boot it into TWRP
flashed the Gapps.
I'm up and running now. I tried different iterations and It really bothered me because it worked fine on another one. I was also at time flashing it with SuperSU and other times with Magisk. It didn't matter which one I used it got stuck on the LineageOS splash screen.
dizzymon said:
Here's how I think I fixed it.
booted into TWRP
advanced wipe, Factory reset
booted it into TWRP
Flashed the LineageOS
boot into LineageOS
boot it into TWRP
flashed the Gapps.
I'm up and running now. I tried different iterations and It really bothered me because it worked fine on another one. I was also at time flashing it with SuperSU and other times with Magisk. It didn't matter which one I used it got stuck on the LineageOS splash screen.
Click to expand...
Click to collapse
By the way, it's called the boot animation. The splash screen is like the Samsung screen that says powered by Android.
Possible corrupted file
secretwolf98 said:
By the way, it's called the boot animation. The splash screen is like the Samsung screen that says powered by Android.
Click to expand...
Click to collapse
So far you're quite correct I personally have three SM-T580's and they all seem to work just a little bit different. Might I suggest doing an MD5 Sumcheck? The device shouldn't be getting into a bootloop unless there was something wrong with the files, or the device.