Hi there.
I'm in desperate need of help with my Nexus S. After updating CM it wont boot at all.
Earlier on, I've updated between 10.x releases using the CM Updater. I've done a backup using TWRP and then just clicked the latest stable and the phone has automatically updated, without any problems at all.
After much consideration I decided to go ahead and updated to the M6 version of CM11 for the Nexus S. This release was listed under "stable" releases (which is somewhat confusing, as it isn't a stable release?) in the CM Updater.
First I did a backup with TWRP and then I went ahead and selected the M6 release from the CM Updater. This is where I now know (via #cyanogenmod) that I did something wrong. I shouldn't have updated from a 10.x release to a 11.x release without wiping. However, there was no such information in the CM Updater and the release was listed under "Stable", so I never gave wiping a thought.
However, the phone reobooted and started updating, but displayed some errors that i didn't have time to write down.
Then it just rebooted and hung at the google logo. I waited for 15 minutes, and it was still just displaying the Google logo. So, I went into TWRP and restored the backup I did. after that the phone rebooted and it still hung at the Google logo. I pulled the battery again and went into TWRP and did a factory reset and tried rebooting. The phone hung at the Google logo again. This is when I did a factory reset AND restored my backup. STILL, the phone hangs at the Google logo.
What should I do? Is my trusted Nexus S gone forever?
8fold said:
Hi there.
I'm in desperate need of help with my Nexus S. After updating CM it wont boot at all.
Earlier on, I've updated between 10.x releases using the CM Updater. I've done a backup using TWRP and then just clicked the latest stable and the phone has automatically updated, without any problems at all.
After much consideration I decided to go ahead and updated to the M6 version of CM11 for the Nexus S. This release was listed under "stable" releases (which is somewhat confusing, as it isn't a stable release?) in the CM Updater.
First I did a backup with TWRP and then I went ahead and selected the M6 release from the CM Updater. This is where I now know (via #cyanogenmod) that I did something wrong. I shouldn't have updated from a 10.x release to a 11.x release without wiping. However, there was no such information in the CM Updater and the release was listed under "Stable", so I never gave wiping a thought.
However, the phone reobooted and started updating, but displayed some errors that i didn't have time to write down.
Then it just rebooted and hung at the google logo. I waited for 15 minutes, and it was still just displaying the Google logo. So, I went into TWRP and restored the backup I did. after that the phone rebooted and it still hung at the Google logo. I pulled the battery again and went into TWRP and did a factory reset and tried rebooting. The phone hung at the Google logo again. This is when I did a factory reset AND restored my backup. STILL, the phone hangs at the Google logo.
What should I do? Is my trusted Nexus S gone forever?
Click to expand...
Click to collapse
Follow this Step :
1.Go to TWRP and wipe everything leaving storage(Internal Storage)
2.Then Reboot recovery
3.Then restore ur TWRP Backup.(Make sure ur twrp backup is healthy )
4.Wipe cache & dalvik (Optional)
5.Reboot system.
Ur device should boot now.
If I may add, the M6 is a bit buggy, a more recent nightly is more stable.. or choose an M5, M4 or other snapshot if you prefer them..
rakeshbro said:
Follow this Step :
1.Go to TWRP and wipe everything leaving storage(Internal Storage)
2.Then Reboot recovery
3.Then restore ur TWRP Backup.(Make sure ur twrp backup is healthy )
4.Wipe cache & dalvik (Optional)
5.Reboot system.
Ur device should boot now.
Click to expand...
Click to collapse
Thanks! I wiped:
Cache
Dalvik Cache
System
Android Secure
The only thing I left out was External Storage. Then I restored my backup. After rebooting the phone hangs at the Google logo, once again. I wont get further than that.
8fold said:
Thanks! I wiped:
Cache
Dalvik Cache
System
Android Secure
The only thing I left out was External Storage. Then I restored my backup. After rebooting the phone hangs at the Google logo, once again. I wont get further than that.
Click to expand...
Click to collapse
Did u reboot recovery after wiping?
Otherwise u will be stuck on google logo.
Related
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 .
About two weeks ago just before CyanogenMod's announcement of its closure I updated my Moto G2015 (1GB) to the latest nightly, which was CM14.1 released on the 25th of December, with its corresponding GAPPS version also released on the 25th of December (ARM, android 7.1, Full)
Yesterday the 7th of January my Google Apps decided that they didn't want to open, at first I thought it was just updating and since my battery was low I plugged in my device, I later realised that my device randomly went to a boot loop and stayed there. I grew impatient so I restarted the phone and went to the Recovery Mode (To Re-Flash the ROM), but to my annoyance the recovery (TWRP) just stayed on the 'Teamwin' logo forever, it would randomly go black then return to that logo. infuriated I turned on my phone and went to backup/reset and clicked 'factory reset'. it annoyingly booted me into recovery to reset the device, which of course I couldn't do.
Now the simple answer would have been for me to go and wipe the cache and data from 'google play services' and or 'launcher3' but I did, either it always shows 'calculating' preventing me from clicking 'manage space' or clearing 'cache' or when it did finally show, after I did click the button for the cache and or data to be cleared it would say 'calculating', and a quick check would discover that nothing was actually cleared.
Kind Regards, and Thank You to any help recieved,
NotSoGreat
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
acejavelin said:
Boot TWRP or CWM Recovery (not sure if it's still called CWM Recovery now that LineageOS has replaced it) with the command 'fastboot boot recovery.img' but replace recovery.img with your actual recovery image filename. If TWRP won't boot wait, sometimes a theme or corruption in the TWRP directory on internal storage can pause the startup of TWRP by several minutes, if that still fails boot CWMR and remove the TWRP directory or wipe internal storage.
Once you can get TWRP to boot properly, backup everything (MPT works in TWRP) and wipe and reflash, should be good to go.
Click to expand...
Click to collapse
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
NotSoGreat said:
Thanks for the reply, what you're saying makes sense and would probably work, but I found a simpler work around. I'm actually annoyed I didn't do it earlier.
So simply put, I downloaded my stock recovery which worked and then I just factory reset my device from there, that reset the CM14.1 ROM and let my Google Apps work again. Now about the recovery, I'm a bit skeptical about Re Flashing it, but I think I'll try it next weekend and post the results.
Click to expand...
Click to collapse
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
I'll try now.
acejavelin said:
Have you tried it since you wiped? It might just work now that the reset wiped internal storage...
Click to expand...
Click to collapse
Right, so I reinstalled and flashed the latest version TWRP, when I opened into it, it took about 1 minute before it opened up, it ran a quick operation that I just glimpsed, it looked like it was wiping cache and user data, my phone was rebooted and I was right, my phone had been reset for the second time today (I'm almost a pro at reinstalling all my apps). I rebooted into the recovery and Look and Behold, it was working.
Thanks slot for your help and time.
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).
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.
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