Hello,
I have this very annoying thing:
+ tried CM11 but that worked not Ok for me.
+ reverted to CM 10.1, 10.1.3, with the correct 4.2.2. Gapps; did factory wipe, cache wipe, dalvik wipe
rebooted and it then worked (native), I got into the trenshbucket.
Then I restored with Titanium Backup, which worked always good on 10.1.3
When I do a reboot after that, the logo keeps spinning and doesn't go further with the booting.
Searched this forum and used google, but no solution found.
Can someone please help me with this, cause I am going bunkers ......
Thanks a lot!
Regards
Kees
Related
Hi
I have a galaxy s i9000
I just flashed my first rom, cyanogenmod 7, and it worked well.
then I flashed google apps (through clockworkmod -> install zip from sdcard), and from this point when my phone boots up, it goes in to a loop between the cyanogenmod boot screen and the google start screen ("touch the android to begin").
I tried going back in to recovery and wiping data + cache partition + dalvik cache, and reflashing just the cyanogenmod, but I can't get rid of the google apps screen and the boot-loop.
does anyone please know how I can recover from this??
Thank you
I have a Verizon Galaxy Nexus (rooted stock 4.0.4). I decided I would test out Clockworkmod touch recovery before doing anything too serious with it. So, I made a backup, rebooted, deleted an app, went back to recovery, and restored my backup. But, while it was restoring my data, it suddenly stopped and said "Error while restoring /data!" I rebooted and, after waiting through a really long boot, it booted into a semi-reset version of my phone. All of the apps claim to be installed but will not start.
So, thinking it could be a touch recovery issue, I flashed an older version of clockworkmod recovery and tried restoring after clearing my data, cache, factory reset, and Dalvik cache. Still, the exact same thing happened. I also tried restoring older backups, but the exact same thing happened.
What is going on, and what should I do? Thank you for your time.
Please, guys. I need help. I have no clue what to do.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
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.
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.
I had CM13 on my Oneplus 3, and saw that there was an update. Turns out it was for CM14 and it wiped out my recovery(after further googling, I found out that it's a known issue - http://forum.xda-developers.com/oneplus-3/help/boot-recovery-cm14-1-nightly-official-t3497425). So I flashed the custom TWRP recovery from that.
Then I proceeded to flash my last working update of CM13, and the ARM64 6.0 Nano GApps immediately after. I then wiped my dalvic cache and rebooted. It started booting up and the preparing apps screen started loading. But when it finished and I was at the phone setup screen(the screen you get when you first buy a phone and have to choose language, wifi etc), it shows me an error named - "unfortunately the process android.process.media has stopped one plus 3 boot"
I looked the error up online and all results are to go into settings and modify google sync settings, or delete gallery cache etc. But I never even get to reach that point to try it. I flashed CM14 and ARM64 7.1 Nano Gapps to see if maybe that would work, but got the same error. Then I downloaded the last snapshot from CM site with their recovery, but same error.
Can anyone please help me?
SOLVED: I wiped everything except Internal Storage from afvanced wipe of TWRP and reflashed CM13 along with Gapps. Now the phone booted up fine and I'll restore my apps using titanium backup.
Hello,
Glad you found your way.
Thread closed.
Regards
Vatsal,
Forum Moderator.