Database Info

Bootloop after flashing stock rom in yureka plus

I was running cm14.1 nightly build(7.1.1) on my yu yureka plus, when i came across the "android n data toggle fix" on xda. I flashed that zip and since then my phone gave erratic reboots. So I tried to restore to an nandroid backup took a week ago but no luck. So I tried to flash resurrection remix 5.6, which sent my phone into a bootloop, but it started up as i plugged the phone into my PC (weird). Then I tried to hard reset the devices numerous time, even removed the battery for 5 min but still no luck. Next I flashed the official stock rom (cm12.1) via fastboot. It loaded up pretty quickly, but when i reached the welcome screen, it sent the phone into a reboot and got stuck again in bootloop. I tried several roms but no luck. I even flashed official modem, appsboot, hyp etc partitions multiple time and even reflashed the recovery (even tried different versions, including stock). PLease Help

romeovictor said:
I was running cm14.1 nightly build(7.1.1) on my yu yureka plus, when i came across the "android n data toggle fix" on xda. I flashed that zip and since then my phone gave erratic reboots. So I tried to restore to an nandroid backup took a week ago but no luck. So I tried to flash resurrection remix 5.6, which sent my phone into a bootloop, but it started up as i plugged the phone into my PC (weird). Then I tried to hard reset the devices numerous time, even removed the battery for 5 min but still no luck. Next I flashed the official stock rom (cm12.1) via fastboot. It loaded up pretty quickly, but when i reached the welcome screen, it sent the phone into a reboot and got stuck again in bootloop. I tried several roms but no luck. I even flashed official modem, appsboot, hyp etc partitions multiple time and even reflashed the recovery (even tried different versions, including stock). PLease Help
Click to expand...
Click to collapse
After flashing stock via fastboot, have you tried booting to recovery and factory resetting then wiping cache and Dalvik/ART cache? Try flashing the stock kernel if you're using stock ROM. If you're using a CM ROM then flash the CM stock kernel for your model.
Sent from my SM-S903VL using Tapatalk

ok so here's what happened
After I used fastboot image to flash the stock rom (i believe stock kernel is present in the rom too, since it has a boot.img), it took 10 minutes to boot upto the welcome page and then rebooted. I wiped cache and dalvik cache too and retried the process, but no luck

Droidriven said:
After flashing stock via fastboot, have you tried booting to recovery and factory resetting then wiping cache and Dalvik/ART cache? Try flashing the stock kernel if you're using stock ROM. If you're using a CM ROM then flash the CM stock kernel for your model.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
ok so here's what happened
After I used fastboot image to flash the stock rom (i believe stock kernel is present in the rom too, since it has a boot.img), it took 10 minutes to boot upto the welcome page and then rebooted. I wiped cache and dalvik cache too and retried the process, but no luck

Thanks for your reply dude
Anyways, the problem is solved.
The problem was never with the device, rather it was the battery that was faulty. When I kept the device plugged in to PC, it worked for sometime and when I pulled the wire out, it shut itselft down. Same was the case when I tried to multitask when connected to PC. But when I connected it to wall charger, it allowed me to multitask . Hope to buy a replacement battery soon.
Once again, thank you for your reply

Bootloop with 6.x.x and 7.x.x ROMs

My bootloader is unlocked.
Using FlashTool 0.9.18.6, I flashed "Sony Xperia L C2105 15.3.A.1.17 Generic DE" - FTF, which I downloaded from:
https://forum.xda-developers.com/xperia-l/general/sony-xperia-l-flashable-ftfs-locked-t2560642
Downloaded CM11 from FreeXperia's thread, from that I extracted boot.img and using FlashTool flashed it.
Downloaded CM12.1 from Oliver's thread and moved it into my external sdcard. Using CWM, did a clean wipe (dalvik, cache, data and system), and flashed the zip.
ROM installed and was working fine.
Downloaded CM13 from Oliver's thread and moved it into my external sdcard.
Enabled USB debugging.
Downloaded TWRP 3.0.2-0, from:
https://dl.twrp.me/taoshan/twrp-3.0.2-0-taoshan.img.html
Rebooted into bootloader using adb. And flashed TWRP, using fastboot:
"fastboot flash boot twrp.img"
Rebooted into recovery. The interface was flickering non-stop and the left part was overlapping over the right part and vice-versa, but I managed to factory reset and wipe my dalvik, cache, data, system, sdcard and android secure.
Then I flashed CM13 from my external sdcard.
No errors.
Wiped dalvik, cache and my external sdcard.
Rebooted.
Bootloop.
Rebooted into CM Recovery.
Factory Reset and wiped cache.
Rebooted.
Bootloop.
I have also tested 7.x.x (CM14 and Resurrection Remix) and it also gets me in a bootloop until the battery reaches 0%.
The problem started with Beta 2 of CM13 (anything before it works fine), after I flashed it almost a year ago. I also made a post there at that time about my problem:
"I'm not certain if this is the right thread to ask, and I don't think this qualifies as a bug report, I'm just asking for some help as my phone is stuck on the boot logo forever until the battery runs out (from 90-100% to 0%).
I've previously used CM11, CM12.1 and the previous beta 1 of CM13, but after flashing beta 2 a couple days ago it's just stuck on trying to boot.
The recovery I'm using is TWRP 3.0.2. I wiped my phone completely(the system, sdcard, cache etc). After that I connected my phone to my PC, while on recovery, and copied the ROM zip and GAPPS zip to my external sdcard. I disconnected my phone from the PC. Flashed the ROM and after that GAPPS (Open GApps Platform: ARM / 6.0 / pico). The logs didn't show any error so I wiped the dalvik cache and rebooted the phone. The phone went into the boot logo and now is just stuck there, I waited ~5 hours and it still didn't fully boot after an hour or so the battery ran out. So I decided to do everything again, charging the phone to 100%, wiping the phone completely 10 times(for reasons) and flashing everything the same way(I also downloaded the ROM from a different mirror, and tested both zips for any errors), this time I left it overnight, keeping the charger connected and in the morning it was still stuck on the boot logo. The third time I tried a different GAPPS package(A-GAPPS) and the same result. Can anyone provide some help? Maybe I'm just missing something or being really stupid. I'm sorry for being such a bother."
https://forum.xda-developers.com/xperia-l/orig-development/rom-cyanogenmod-13-0-t3254779/page20
I made this thread in hope of finding out what's causing this. Any help is appreciated.

It's been almost a year and I still have this problem with newer ROMs. Does nobody have any suggestions, anything at all? Is more information required? I'd be happy to give/do anything*, if it would mean getting these ROMs working.
The only error I've noticed is that after flashing LineageOS 14.1, if I try a fully factory reset through the default "Android Recovery" it will fail and I'll get "E: format_volume: failed to open /persist/footer" (This doesn't happen if I do a factory reset through TWRP).

Bootloop due to data partition

I have been using lineage OS 14 jgcaap ROM (https://forum.xda-developers.com/oneplus-one/development/cyanogenmod-14-0-t3464337) from few months now.
Yesterday, my phone battery died while I was out. When I tried to boot it again after charging it is stuck on lineage OS logo even though the phone is fully charged by now. I didn't install any app recently or do anything with system partitions.
I went to twrp cleared cache, dalvik and system. Reflashed the ROM but still bootloop. Then I backedup data partition and cleared data as well. This time phone booted properly. So I restored data partition but then again it went into loop. Now if I clear the data partition the phone boots but if I restore the data partition there is bootloop. But I have some important data in messages, offline note taking app and whatsapp which I don't want to use.
Is there any other way to boot with all data intact or Is there any way to restore data from twrp nandroid data backup after I boot with cleared data?

1pratham said:
I have been using lineage OS 14 jgcaap ROM (https://forum.xda-developers.com/oneplus-one/development/cyanogenmod-14-0-t3464337) from few months now.
Yesterday, my phone battery died while I was out. When I tried to boot it again after charging it is stuck on lineage OS logo even though the phone is fully charged by now. I didn't install any app recently or do anything with system partitions.
I went to twrp cleared cache, dalvik and system. Reflashed the ROM but still bootloop. Then I backedup data partition and cleared data as well. This time phone booted properly. So I restored data partition but then again it went into loop. Now if I clear the data partition the phone boots but if I restore the data partition there is bootloop. But I have some important data in messages, offline note taking app and whatsapp which I don't want to use.
Is there any other way to boot with all data intact or Is there any way to restore data from twrp nandroid data backup after I boot with cleared data?
Click to expand...
Click to collapse
Try dirty flashing the rom.

Mr.Ak said:
Try dirty flashing the rom.
Click to expand...
Click to collapse
same problem here, with RR 5.8.5. With dirty flash nothing has been solved.

paolone919191 said:
same problem here, with RR 5.8.5. With dirty flash nothing has been solved.
Click to expand...
Click to collapse
Replace battery.

My battery lasts more than 25 hours, and even if I connect my phone to the wall plug it stay in bootloop. The only Rom that gave me this problem was RR.

paolone919191 said:
My battery lasts more than 25 hours, and even if I connect my phone to the wall plug it stay in bootloop. The only Rom that gave me this problem was RR.
Click to expand...
Click to collapse
You mean you don't have this issue when you flash other rom? That's quite impossible. This issue is of battery only.

With cm13 this issue doesn't appear

Repalcing the battery is the only solution....
Mr.Ak said:
Try dirty flashing the rom.
Click to expand...
Click to collapse
..time for changing battery

paolone919191 said:
With cm13 this issue doesn't appear
Click to expand...
Click to collapse
Strange.Anyway,your best bet is replacing battery.

Is there a way to enable the bootlog?

I have a quite similar issue: yesterday i restarted my Opo after activating Xposed and after reboot, the phone stuck in the lock screen (nothing works, touch ecc...). I've done a Nandroid with TWRP and after that i've made a wipe data (data partition only): now the phone starts and works as well, but if I restore the data partition it stucks in lock screen like before. Is it a battery problem too? I can upload the dmesg.log if needed.

[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.

SM-920F stuck in bootloop when trying to restore in TWRP

1.Your bootloader status if applicable
2. Rom name with complete baseband/date/version
3. Kernel name
4. Any Mods you are using
5.If you are using Custom Rom, your flashing style i.e dirty/clean or you wiped anything else in specific
6. If you used any guide, link to the guide
7. Root status
8. Your exact problem
9. Any method you tried that failed
10.Any other detail you think would be necessary
1. Unlocked
2.Nemesis [ROM][7.0][DQB7][06/03] Link here!
3. Linux 3.10.x
4. Installed S7 edge battery. guide here!
5. Clean wiped (dalvik, cache, data, system)
6. No particular guide, just random posts through search.
7. Rooted
8. I restore a backup in TWRP and after restore, I get stuck in boot screen (Samsung logo).
9. I've tried wiping several times and restoring different backups. The only way to bypass this boot loop is to do a clean install with no restore. This means flashing everything from the beginning again. I flashed latest TWRP to 10.1.1-0 thinking it might be a issue with bad TWRP. No results.
10. This issue began when I installed S7 edge battery into S6. I would get stuck in bootloop and in TWRP cannot restore my backups so I had to clean install a rom to bypass bootloop. Today I fully discharged and recharged it to calibrate my battery and when booting got stuck in bootloop again. Still can't restore backup in TWRP, so looks like I'll have to do clean install again. Its frustrating cause it feels the slightest change will corrupt my rom and I have no choice but to reflash everything and spend hrs setting everything up. Searched for hours and still couldn't find a answer.

rifek4 said:
ROM releated issue, you cannot pass that if you don't know which files corrupt... Only you can try wipe dalvik then cache and maybe data... But I don't wish good future to working that XD
Click to expand...
Click to collapse
I came from a Lineage 14.1 build before this and I couldn't even restore backup without hanging in boot screen