Database Info

CM13 accidental brick

First of all: I made a thread about bricking my Moto G earlier, but since this is a new issue (and a new Android version) I thought it would be better to make a new thread
So as some of you might have noticed yesterday there was the first release of CM13 for the Moto G and if you had nightlies enabled (like me) you'd just get it as a normal update, except for having to install the new Gapps of course. The problem is I didn't notice that it was CM13 until it was too late... First thing that happened was of course that my Google Play Services we're not working anymore. I tired flashing Gapps for 5.1 but it said that I used the Gapps for the wrong Android version. So I looked in the settings and noticed that I had Android 6.0 . Now I tried flashing OpenGapps for Android 6.0, which worked, but as soon as I booted Android it told me something like "Setup Assistant stopped working" over and over again, so I tried reverting to my latest CM12.1 backup I had, which was a bad idea... My phone was stuck in a bootloop and everytime I tried wiping my phone (except for internal storage) it rebooted when wiping data. Reflashing TWRP didn't help, so I tried flashing stock Android with mfastboot and it got to the point where it was optimizing apps but after that it just did the same thing again (classic boot loop).
Here's my question: How can I get TWRP working again and install CM13 (again if possible without wiping my internal storage or at least being able to back some files up) ?

Can u access TWRP?

Andus1988 said:
Can u access TWRP?
Click to expand...
Click to collapse
Yes I can, flashing and wiping works, except when trying to wipe data

Then don't wipe data?! Wiping data isn't necessary every time!

Andus1988 said:
Then don't wipe data?! Wiping data isn't necessary every time!
Click to expand...
Click to collapse
I know but if I only wipe dalvik, cache and system it didn't work.
Now I tried booting into TWRP and it shows the "no command" screen :'(

I'll write u a PM

I have the same problem would be nice if someone have a solution.

Guys i have a similar problem here, i got the latest update downloaded (cm-13.0-20151207-NIGHTLY-peregrine.zip) and when i clicked on update, the phone went black and nothing work now, i cannot get into fastboot or anything else, it only show "qhsusb_bulk" when I plugged in to the computer, any help??? i would really appreciate it .

[Q] Stuck on boot loop and cannot flash other ROM

Hello i recently use SlimLP rom until suddenly it was stuck on boot loop . I thought that it must be the problem of the custom ROM and i try to flash other ROM but it seems that i can't proceed to the procedure of wipe data/factory reset because it kept restarting after i checked that option . wiping dalvik cache is fine though . I also did format/data on my solo attempt to fix it but still it won't work.After reading some forum I decided to flash stock firmware but it kept failing on Odin . anyone know what might be the problem of this ? Did I just hardbricked my tab to the point of can't be repaired ? thanks in advance

Try to delete everything in data manually through twrp file manager (Advanced->File Manager)

john99ap said:
Try to delete everything in data manually through twrp file manager (Advanced->File Manager)
Click to expand...
Click to collapse
Im using CWM recovery T.T

iqbaladeee said:
Im using CWM recovery T.T
Click to expand...
Click to collapse
Then, install the latest common twrp by Andi from here: http://andi34.github.io/recoveries_tab2.html
and try it (first try also to wipe data with twrp)

iqbaladeee said:
Hello i recently use SlimLP rom until suddenly it was stuck on boot loop . I thought that it must be the problem of the custom ROM and i try to flash other ROM but it seems that i can't proceed to the procedure of wipe data/factory reset because it kept restarting after i checked that option . wiping dalvik cache is fine though . I also did format/data on my solo attempt to fix it but still it won't work.After reading some forum I decided to flash stock firmware but it kept failing on Odin . anyone know what might be the problem of this ? Did I just hardbricked my tab to the point of can't be repaired ? thanks in advance
Click to expand...
Click to collapse
I can't change my rom, wipe / format doesn't work. Nothing changed after flashing with Odin.
16 GB Tab 2 have a known faulty EMMC (MAG2GA). It can happen, that your EMMC get “read only”, so you can’t perform any write actions (also you can’t format) anymore.
From the EMMC data sheet:
5.1.7 End of Life Management:
The end of device life time is defined when there is no more available reserved block for bad block management in the device. When the device reaches to end of its life time, device shall change its state to permanent write protection state. In this case, write operation is not allowed any more but read operation are still allowed.
But, reliability of the operation can not be guaranteed after end of life.
On a faulty EMMC firmware it happens a lot faster.
What are the symptoms?
Uninstalled apps and deleted files are back after a rebootFormating the storage doesn’t work (after reboot the old rom and apps are back)You can flash whatever you like via Odin - it showes “passed” but after reboot nothing changed (e.g. still no StockRom or still the old Recovery you had previously installed)… there might be some more, but only to mention some …
In most cases, the issue can be fixed by a EMMC firmware update, but you need someone who’s able to do it (possible via ISP, nothing you can do esylie at home yourself). In some bad cases you need to find someone who can replace your EMMC.
source: http://andi34.github.io/faq.html

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.

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

Lg e975 ROM sudden shutdown while on battery

Hi guys!
A few weeks ago I've flashed my LG e975 for the first time, my ROM of choice being NitrogenOS. Everything was ok for a few weeks, then out of nowhere my phone started shutting down when I turned on wifi, after that, it wouldn't even load the ROM without the charger plugged in, even tho the battery was fully charged.
While being in recovery, the phone works OK being on the battery not on the charger, so my guess was I somehow ****ed the ROM, so I reflashed the latest version of NitrogenOS to nu succes. So, I went on and flashed other ROMs and even restored the STOCK backup I've done beforehand, but the problem persists.
TL;DR Current state:
- LG e975
- Kernel: 3.40
- Bootloader: MAKOZ30f
- Recovery: TWRP 3.0.2-0
- Phone works ok on battery when in recovery/bootloader
- Phone shutdowns on battery when booting ROM
- Phone boots ROM and works ok when on charger
- Battery level shown in ROM is 30% less shown in recovery
Any suggestions?

deaun said:
Hi guys!
A few weeks ago I've flashed my LG e975 for the first time, my ROM of choice being NitrogenOS. Everything was ok for a few weeks, then out of nowhere my phone started shutting down when I turned on wifi, after that, it wouldn't even load the ROM without the charger plugged in, even tho the battery was fully charged.
While being in recovery, the phone works OK being on the battery not on the charger, so my guess was I somehow ****ed the ROM, so I reflashed the latest version of NitrogenOS to nu succes. So, I went on and flashed other ROMs and even restored the STOCK backup I've done beforehand, but the problem persists.
TL;DR Current state:
- LG e975
- Kernel: 3.40
- Bootloader: MAKOZ30f
- Recovery: TWRP 3.0.2-0
- Phone works ok on battery when in recovery/bootloader
- Phone shutdowns on battery when booting ROM
- Phone boots ROM and works ok when on charger
- Battery level shown in ROM is 30% less shown in recovery
Any suggestions?
Click to expand...
Click to collapse
Sounds like it might be a kernel problem.
Try a different ROM or keep your ROM but try a different custom kernel, if any are available for your device.
You can also try backing up the data and apps that you want to keep then boot to TWRP and factory reset the device.
Or, try a clean flash of your ROM by booting to TWRP and selecting the Wipe option, then select advanced wipes, then select: system, data, cache and dalvik cache(do not select internal storage or any other partition on your list), then swipe the slider to perform the wipe. Then reboot to system and restore your backed up data and apps.
Then go back to home screen in TWRP and select the Install option and flash your ROM+Gapps then reboot to system and restore yoyr data and apps.
Sent from my LGL84VL using Tapatalk