Database Info

Stubborn boot loop

Ok, so my OPO got into a boot loop. I was running latest SlimKat weekly when suddenly during web browsing session the device rebooted itself and got into a boot loop. Well then I booted into TWRP recovery and wiped all the caches (cache, dalvik) and still no use. Then I did a factory reset and still I got a boot loop. Next thing I installed latest 3 SlimKat weeklys (had them on sd card) with factory resets between them and still the boot loop was there. Then the next few hours I spent installing stock roms from fastboot (22R, 25R, 30O, 33R) and still all I got was the boot loop.
Next morning I booted the device to recovery and did a factory reset and restarted (with 30O rom inside this time). Suddenly the device booted all the way to the Android and I was able to install few apps. Then I installed Whatsapp and launched the app. After the SMS confirmation the device rebooted again and proceeded to a boot loop. I turned the device off and let it settle for about 10 minutes. Then I booted in to the recovery and did the factory reset again and was able to boot all the way to the home screen again! Then after some more app installations came the reboot and boot loop.
Since then I haven't got past the boot animation.
In short terms:
- Was running latest SlimKat weekly
- Reboot and boot loop during normal web browsing
- Did factory reset, didn't help
- Installed stock roms from fastboot (22R, 25R, 30O, 33R), didn't help
What is your opinion? Could there be some hardware issue causing the reboot?
Video: https://www.youtube.com/watch?v=ChC58GHbSW4&list=UUHbkAIAVULcCb2pGa2lKIiQ
Sometimes device reboots before the actual CM boot animation, sometimes it reboots during the CM boot animation (usually straight after factory reset or flash from fastboot).

I think the hardware is faulty. I got my device to boot with the official AOSP rom and I even managed to install few apps. The device always reboots or completely shuts down when there is something more intensive going on, like downloading file from web site and installing app at the same time. I will try to investigate cpu and battery temperatures after work today.

[Q] New type of Boot logo hang issue

I am getting a hang on the bootlogo
This happened after installing the OTA for 44S. if I boot reboot the phone 20 or 30 times I can get past it.
TWRP works fine. if you pay close attention when booting into recovery you see the 1+ logo, and just before TWRP loads the screen goes slightly brighter.
When booting into system, you usually see the 1+ logo, and then the screen goes slightly dimmer. Just after this the logo should change into the rotating animation.. This is where my phone hangs. Just after it goes dimmer but before the logo starts to animate.
Now here is the weird part. I've done all the tricks, returning to stock 44s deleting all the partitions and re creating them, deleting cache, dalvik, flashing a persist.img or manually creating that partition, etc etc. after many days of crying and swearing I flashed stock 38R. it boots 100% of the time. I flashed Calkulins 44S rom, back to hanging on boot. I then restored ONLY the boot partition from 38R, and my phone boots 100%
I can't stay on 38R boot/kernel as I have the jumpy touch screen and a few other bugs which 44S fixes.
Does anyone have any ideas?
In a nutshell, 44S boot hangs 95% of the time.
38R boot image works all the time for booting (but I need the bug fixes from 44S)
(working kernel: 3.4.0-cyanogenmod-g33fa374 [email protected] #1 mon Oct 6 11:03:38 PDT 2014)

Try using this return to stock tool by OnePlus, it'll take you back to 38R with a full wipe. Don't do anything else to the phone other than letting it boot up. Then grab the 44S OTA from here and flash it.
Transmitted via Bacon

timmaaa said:
Try using this return to stock tool by OnePlus, it'll take you back to 38R with a full wipe. Don't do anything else to the phone other than letting it boot up. Then grab the 44S OTA from here and flash it.
Transmitted via Bacon
Click to expand...
Click to collapse
Ok I tried that and it didn't work. after installing the 44S update OTA it hung on the first boot, i rebooted and it worked, i rebooted again and it hung for the next 6 tries, #7 it worked... I flashed the 38R boot image, and it boots every time. flash back the 44S boot image and it hangs on boot.
What else is in the Boot.img as well as the kernel. if it possible to have *just* the kernel? or when you flash a kernel does it update other things? I am thinking if I can flash the 38R Boot.img and then put *just* the 44S kernel over the top of that?

artymarty said:
Ok I tried that and it didn't work. after installing the 44S update OTA it hung on the first boot, i rebooted and it worked, i rebooted again and it hung for the next 6 tries, #7 it worked... I flashed the 38R boot image, and it boots every time. flash back the 44S boot image and it hangs on boot.
What else is in the Boot.img as well as the kernel. if it possible to have *just* the kernel? or when you flash a kernel does it update other things? I am thinking if I can flash the 38R Boot.img and then put *just* the 44S kernel over the top of that?
Click to expand...
Click to collapse
I'm pretty sure the boot.img is only the kernel. Not sure why your device doesn't want to boot 44S, it's a really weird one. It fully wiped your device, including user data, right?
Transmitted via Bacon

timmaaa said:
I'm pretty sure the boot.img is only the kernel. Not sure why your device doesn't want to boot 44S, it's a really weird one. It fully wiped your device, including user data, right?
Transmitted via Bacon
Click to expand...
Click to collapse
Oh I wiped and formatted it so well Timmaaaa, the paint started coming off!
I'm not the only one with the problem, I found a thread in the oneplus website forum that a staff member had posted with that 38R recovery zip that basically said they had so many support claims about boot logo hangs they were going to ignore them all and to just run that recovery procedure as it fixes them all. There are a lot of posts saying "hooray! It fixed it!" followed by "the phone said there was an OTA update to 44S which I installed and now it's not working again"
Such a great phone apart from stupid bugs like this and God awful support. Apparently if you run colour OS it doesn't hang, but who wants to run that?

[Q] LG G3 is constantly rebooting into TWRP, can't get a normal boot

Guys I'm freaking out, I installed TWRP while on 4.4.2 and then later tried to install the OTA Lollipop update. My phone rebooted into TWRP, and now it won't stop. Even normal reboot option continues to reboot it into TWRP.
I tried flashing another ROM, I tried factory resetting from the TWRP menu, I tried rebooting to recovery then rebooting normally, nothing is working.
Please, what can I do?

MaliciousBanjo said:
Guys I'm freaking out, I installed TWRP while on 4.4.2 and then later tried to install the OTA Lollipop update. My phone rebooted into TWRP, and now it won't stop. Even normal reboot option continues to reboot it into TWRP.
I tried flashing another ROM, I tried factory resetting from the TWRP menu, I tried rebooting to recovery then rebooting normally, nothing is working.
Please, what can I do?
Click to expand...
Click to collapse
So your completely formatting system and then flashing a custom rom? That should fix it if not just follow my back to stock guide.
Sent from my iPhone using Tapatalk

I found your back to stock guide, you're sure it will work? I'm trembling in anticipation here because the .TOT file is going to take 5-6 hours to download, and I've got work really early in the morning. If it doesn't work I have no idea what I'm going to do.

http://lgg3root.com/lg-g3-root/how-to-unrootunbrick-lg-g3/. link to unbrick.
or try this. i just had bootloop and nothing worked except this
Found this on AndroidCentral: Saved my life – it got my phone back to original. Hope this helps others.
*****************************************************************************************************************
What worked for me was from the TWRP terminal command was to type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
then hit enter
type
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
then hit enter and reboot.

I was able to fix the phone a few nights ago; I was on the road and never had a decent internet connection to update.
The return to stock method ended up working. Although, the process failed about six times before finally going through.

Help: CM 12.1 Nexus 5 stuck in bootloop and freezes on TWRP load screen

I've got quite a peculiar problem with my Nexus 5.
Last night, I left my phone on charge. It was working normally and the software was functional etc. However, once I woke up, the phone was constantly restarting itself, and wouldn't load past the boot animation. I tried to load up fastboot to enter the TWRP recovery, however, the phone froze on the load screen. I should also add that my custom boot animation was replaced by the CyanogenMod mascot.
This problem has never occurred before, and I really haven't got a clue how to fix it. I tried to use WugFresh's NRT to flash a factory image of Android 6, however, the command terminal indicated that each process had failed. This did not restore the phone to its original condition.
I should also point out that I have been running a CM 12.1 nightly, which has been very stable and I have been using this nightly, without major problems (bar the infrequent system UI crashes) for a couple of months. It is obviously rooted and I have a Nandroid backup, which I can't access for aforementioned reasons.
Please could you help me with resurrecting my phone? I would be happy to clarify and elaborate upon any point of information.
Kind regards,
Sami

Have you tried manually wiping cache in fastboot or manually flashing a stock ROM in fastboot mode?

audit13 said:
Have you tried manually wiping cache in fastboot or manually flashing a stock ROM in fastboot mode?
Click to expand...
Click to collapse
I actually have tried to flash stock Android ROMs, from KitKat to Marshmallow, however, this didn't work as there was a 'write failure' and CyanogenMod wasn't removed. I did erase the cache, but to no luck.

Sounds like the memory module on the phone is defective. I had a Nexus 5 that would constantly re-lock the bootloader after I reboot. I had another N5 where the bootloader remains unlocked and a full wipe in recovery would finish in about 3 seconds which is far too short.
I could only solve both problems by replacing the motherboard.

SM-G610F Soft Brick happens after TWRP flash

Hello people,
I just tried flashing TWRP to my J7 Prime phone. Odin flash was successful and I could boot into recovery. I followed through normal procedure(data format and no-verity-opt-encrypt flashed). I did not flash any other zips and when i tried to boot back into System my phone didn't get through the Galaxy Prime logo. It wouldn't even show the boot animation. Before this happened, I did root my phone and everything was fine, I accidentally deleted google play once and also wanted to flash stock firmware so I did. After I flashed the stock firmware, when I wanted to root it again it would work after flashing magisk and booting into the system but after some time passes the apps one by one would begin to freeze and at last no app would even load. When i try to reboot at this point, the phone wouldn't boot back into the system anymore. It would get past the Samsung logo but the boot animation wouldn't even play as i was stuck in a black screen. I tried to restore with TWRP then, (Only restoring Boot, System and Data but I didn't wipe anything on the system before restoring. I think that this might be the issue but I just recently got into rooting.) but when i rebooted to use my phone it wouldn't get past the Samsung logo. The Samsung J7 Prime logo would show up, then 1-2 seconds pass and then reboot. This was a loop.
I was able to reflash stock firmware and get it to work normally. Since I can't risk bricking the phone as I can't get a new one after this experience I didn't flash anything again. Because after i restored with TWRP back then and now my phone bricking just because of a TWRP flash I think if I just give it some more tries (even with difference in procedure) it might just get hard bricked. I think flashing firmware so often might brick it. I really don't know but I can't risk bricking this phone.
The phone right now is OK. I just want to learn why this might happen, what would cause this and how to fix this. I will not flash anything because again I can't risk getting this phone bricked.
Just getting some information for me is enough as I am also curious about this problem,
Thank you.