Another Bootloop Thread - Eee Pad Transformer Q&A, Help & Troubleshooting

com.google.gapps kept crashing so I decided to flash rayman's CM10 v6 rom over b5. Now I'm stuck on the CM10 logo. Cold boot doesn't work, Apx to cold boot doesn't work, and I can get back to recovery but flashing the rom again and/or wiping cache, wiping davlik and factory reset still didn't work.
EasyRecovery appeared to work at first but then at the stage where my device is supposed to reboot it started throwing me a 'device not found' error and it of course continued to be stuck in the bootloop.
What should I do?
EDlT:Easyflasher worked, but I lost all my data

Apparently the same issue
Well, apparently I'm having the same problem as Devour, I have the Team Rogue Recovery installed into my device and tried to install many different OS but always results into being stuck in the OS boot. I also wiped everything, cold boot but always end up with the OS boot stucked.
Does anyone can help?

Related

[Q] Note 10.1 Wifi Automatically boots into Recovery

So I tried to install Android Revolution HD 9.0 today, and after installation, I got stuck in a boot loop. Then I tried factory resets and cache partion wipes and multiple reinstalls and now it automatically boots into recovery.
Prior, I had a stock ROM, but it was rooted, but I was plagued with issuse such as random reboots and half the time on reboot, it would be stuck in a boot loop.
Can anyone help me out here?
I'm still fairly new to android modding beyond following instructions for installing CWM/Custom ROMs, so take that into consideration.
Factory reset or wipe phone in CWM and flash a new stock rom via Odin .
jje
Done and done. Thanks for the help!

[Q] Motorola Defy getting stuck at boot menu

Hello,
I successfully installed cyanogenmod 7.2 on my Motorola Defy MB525 using the instructions from the cyanogenmod wiki "Install CM for jordan" (can't post link yet).
After a while, I wanted to install gapps, so I installed it from Bootmenu. After this, the phone was always booting to boot menu and I didn't know how to make it boot into the system, so I changed the "Boot" option default to something like "Normal", I think.
Now when starting the phone, all I see is the Google logo which stays there indefinitely.
I can still boot to BootMenu and tried a number of times to wipe data/factory reset, wipe cache, wipe dalvik cache, and re-install the cyanogenmod7.2 zip, but it still can't get out of the infinite loop.
I found out that a posible solution would be to flash an image with RSD Lite, but it seems kind of tricky and I would rather leave it as a last resort.
Any ideas?
Thanks
I managed to unbrick my phone eventually.
Tried to use RSD Lite with several images, but it would give an error and then the application would crash and leave my bootloader corrupt. I tried all the schemes I could find including: loading the image from root of C:, disabling UAC, etc., but nothing worked.
Then I tried sbf_flash on Linux with the same image, and it worked like a charm, no errors, and my phone was up and running again.
So for anyone else who may encounter this problem, I warmly recommend using sbf_flash, it is incredibly simple to use.
sltrv said:
Hello,
I successfully installed cyanogenmod 7.2 on my Motorola Defy MB525 using the instructions from the cyanogenmod wiki "Install CM for jordan" (can't post link yet).
After a while, I wanted to install gapps, so I installed it from Bootmenu. After this, the phone was always booting to boot menu and I didn't know how to make it boot into the system, so I changed the "Boot" option default to something like "Normal", I think.
Now when starting the phone, all I see is the Google logo which stays there indefinitely.
I can still boot to BootMenu and tried a number of times to wipe data/factory reset, wipe cache, wipe dalvik cache, and re-install the cyanogenmod7.2 zip, but it still can't get out of the infinite loop.
I found out that a posible solution would be to flash an image with RSD Lite, but it seems kind of tricky and I would rather leave it as a last resort.
Any ideas?
Thanks
Click to expand...
Click to collapse

[Q] Stuck in cyanogenmod boot loop

I installed cyanogenmod a few days ago and it was working fine. I installed a font changing app, and it needed to reboot to work. When it tried to reboot, it got stuck on the cyanogenmod boot screen. I booted to recovery and did a factory reset, wiped dalvin cache to no avail. I found a stock Rom for my phone, but Odin doesn't seem to see it when I go into downloading mode. Am I doing something wrong? What should I do next?
Just reflash CM.

Stuck in Bootloop

Hi,
I tried flashing my second ROM in my moto G. While clearing cache/data, my phone restarted automatically after the wipe.
Then I flashed the ROM but it seems to be stuck in loop for more tham 15 min.
Any suggestions or help.
And I cant get to recovery. As soon as I enter into recovery and twerp wallpaper shows up the phone reboots again.
prthmshetty said:
Hi,
I tried flashing my second ROM in my moto G. While clearing cache/data, my phone restarted automatically after the wipe.
Then I flashed the ROM but it seems to be stuck in loop for more tham 15 min.
Any suggestions or help.
And I cant get to recovery. As soon as I enter into recovery and twerp wallpaper shows up the phone reboots again.
Click to expand...
Click to collapse
I tried to reflash the recovery TWERP and installed cyanogen, first rom again because the same problem persisted when I tried to install another rom.
BTW while flashing recovery i got an error stating that the partitions are mismatched.

[Help] Flashed Franco Kernel over CM13 Stock and ended in bootloop

Hi, so short story is.
1. I had a backup of my stock rom that i did using twrp.
2. I flashed Franco Kernel for COS 13 downloaded from his website (https://kernels.franco-lnx.net/OnePlusOne/6.0.1/anyKernel/)
3. When i flashed i performed a Wipe dalvik cache from recovery
4. Reboted phone, and started optimizing apps but suddenly it rebooted.
5. Started optimizing apps but when it showed optimizing app 1 of 103 the phone keept restarting.
6. I decided to restore my backup made from TWRP, but then phone got stuck and restated everytime from the CYANOGENOS logo.
7. Since it was not booting, i decided to install from fastboot a clean CM13.
8. Flashed, finished and then the phone restarted, but heeey, again stuck in the CYANOGENOS Logo and restarting when the logo shows up.
9. I freak out and I don't know what to do.
So far:
fastboot is working
Cyanogen Recovery is Working ( tried the wipe from that, but still no luck)
When I plug the device directly to my PC, it shows "QHSUSB_BULK", but as i say: fastboot and COS recovery are working.
Can you guys help me, please
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
leokook said:
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
Click to expand...
Click to collapse
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Mr.Ak said:
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Click to expand...
Click to collapse
Lesson learned.

Categories

Resources