So, I thought I'd see what Jelly Bean was like on the Galaxy S. I have had CM9 on there for a while.
Thought I'd be sensible and do a Nandroid backup - never done that before but seems like a sensible thing.
It all backs up fine. So I reboot the phone and it's in a boot loop. I also can't use the three button combo to get back to recoverly - only the three button download combo works.
What is going on? I only did a backup!
Just to add the complete set of steps. I have the latest stable CM9 installed already.
Boot into recovery.
Select backup/restore.
Select backup.
Wait for backup to finish.
Back one screen.
Reboot phone.
magneze said:
Just to add the complete set of steps. I have the latest stable CM9 installed already.
Click to expand...
Click to collapse
Try flashing the ICS semaphore kernel from My Android Collections to recover
xsenman said:
Try flashing the ICS semaphore kernel from My Android Collections to recover
Click to expand...
Click to collapse
I reflashed using stock 2.3.6 and Odin and then I could restore from the Nandroid backup.
Bit weird all in all. I could understand this if I had flashed or restored something, but I just did the backup!
magneze said:
I reflashed using stock 2.3.6 and Odin and then I could restore from the Nandroid backup.
Bit weird all in all. I could understand this if I had flashed or restored something, but I just did the backup!
Click to expand...
Click to collapse
Its possible when you reboot phone, your new settings might have taken effect that were there earlier . ( Normally for a complete change of ROM, you need to wipe before and after flashing a ROM, failing to do so, can have some effect when phone is rebooted. )
Related
Hi, I have rooted my phone and have s off. I've purchased rom manager and installed clockworkmod 3 and have backed up my phone.
When I try to flash the latest cyanogenMod Nightly I run into problems.
The phone gets wiped and updates and then it gets stuck at the Tmobile my touch splash screen. I've left it there for 10 minutes and still no cyanogen.
Any help is greatly appreciated
Thanks
Also I'm able to go back into recovery mode and restore my backup. So my phone is currently back in stock rom.
AnroidGuy2011 said:
Hi, I have rooted my phone and have s off. I've purchased rom manager and installed clockworkmod 3 and have backed up my phone.
When I try to flash the latest cyanogenMod Nightly I run into problems.
The phone gets wiped and updates and then it gets stuck at the Tmobile my touch splash screen. I've left it there for 10 minutes and still no cyanogen.
Any help is greatly appreciated
Thanks
Click to expand...
Click to collapse
If you successfully backed up your phone you are not using Clockwork ROM Recovery 3.x. It's a well known fact that that Recovery image has problems backing up Nandroids, or restoring them for that matter.
What color was the text when you were in recovery? Orange or green?
Its Green, so I have clockworkMod Recovery 2.5.1.2
So I need to update to the 3.x and I should be good?
Also to do a successfull back up of my nandroid I go to "backup and restore" and then select "backup"?
Thanks again for your help
AnroidGuy2011 said:
Its Green, so I have clockworkMod Recovery 2.5.1.2
So I need to update to the 3.x and I should be good?
Also to do a successfull back up of my nandroid I go to "backup and restore" and then select "backup"?
Thanks again for your help
Click to expand...
Click to collapse
if you are wanting CM7 yes you need to flash Clockwork ROM 3.0 via the Fastboot ADB commands. If you are wanting your phone to work you can flash of any of the other ROMS as of right now.
Clockwork ROM 3.x will not do nandroid back ups in it's current state. As Gingerbread comes closer to being an official or RC i'm sure they make sure it can do nandroids. nor will 2.x do nandroids of CM7. but to answer your question you are correct.
AnroidGuy2011 said:
Its Green, so I have clockworkMod Recovery 2.5.1.2
So I need to update to the 3.x and I should be good?
Also to do a successfull back up of my nandroid I go to "backup and restore" and then select "backup"?
Thanks again for your help
Click to expand...
Click to collapse
You are correct. See my thread here For the easiest way to install 3.0.0.5. And yes you can use Rom Manager for backups while on 2.5.1.2 but Rom Manager isnt compatable with flashing or backups for 3.0.0.5. You must use recovery.
TrueBlue_Drew said:
You are correct. See my thread here For the easiest way to install 3.0.0.5. And yes you can use Rom Manager for backups while on 2.5.1.2 but Rom Manager isnt compatable with flashing or backups for 3.0.0.5. You must use recovery.
Click to expand...
Click to collapse
This is good. Every time I try to answer a thread, you seem to beat me to it.
Thanks for the help
neidlinger said:
Clockwork ROM Recovery 3.x. It's a well known fact that that Recovery image has problems backing up Nandroids, or restoring them for that matter.
Click to expand...
Click to collapse
I rooted, made a back up with Clockwork ROM Recovery 3.x. , flashed CM7 and everything was fine. Then I flashed Kernel_2.6.32.27grankin01-CM-GB-OC-v0.09 and when I unlocked the screen everything started force closing on a black screen. I locked the screen again, powered off and on again then it got stuck on the splash screen. I restored my back up and it's stuck on splash screen still. Then I tried to flash Kernel 2.6.32.21grankin010OC0v0.05 thinking my back-up might need a stock kernel. I am a super noob at this, I have successfully flashed roms to my tab before, but I've only been learning about this for about a month. I've been searching and searching but can't seem to find a solution. Am I screwed?
igrillem said:
I rooted, made a back up with Clockwork ROM Recovery 3.x. , flashed CM7 and everything was fine. Then I flashed Kernel_2.6.32.27grankin01-CM-GB-OC-v0.09 and when I unlocked the screen everything started force closing on a black screen. I locked the screen again, powered off and on again then it got stuck on the splash screen. I restored my back up and it's stuck on splash screen still. Then I tried to flash Kernel 2.6.32.21grankin010OC0v0.05 thinking my back-up might need a stock kernel. I am a super noob at this, I have successfully flashed roms to my tab before, but I've only been learning about this for about a month. I've been searching and searching but can't seem to find a solution. Am I screwed?
Click to expand...
Click to collapse
IMHO opinion you are not screwed.
When flashing custom Kernels you need to have a program like SetCPU so you can govern the CPU speed. To fast of a speed or to slow of a speed and it will not boot correctly. You need to flash a different version of CM7 than you are using now, via the recovery screen. make sure to wipe the handset first. that should reset the Kernel to one that Zinx knows works with the phone.
As well i wouldn't recommend flashing kernels with Nightlies. They are unstable as it. and you need to make sure the kernel is compatible with Nightly you are using. And you can over clock them to 1.5Ghrzf from w/ in the ROM.
neidlinger said:
make sure to wipe the handset first. that should reset the Kernel to one that Zinx knows works with the phone.
Click to expand...
Click to collapse
HHHmmm I'm glad I never forget this step on the toilet! Thanks for the help!
Hello. i am new to the android family
i have a nexus s GT-9020T
i have rooted my phone but without setting the clockworkmod reovery.
today i was playing with the rom manager and downloaded one of the rom from the list. after installation i was unable to start the phone only seeing the google logo with the unlock logo.
i went back into the recovery by typing flash recovery recovery.img etc.
run a restore and restart the phone but still not work
my nexus s is 2.3.4 by the way.
please assist
What "restore" did you run?
Go here: http://forum.xda-developers.com/showthread.php?t=1056062
And download the full rom:
Model: i9020T
Full Rom: GRJ22, KD1
That'll revert your Nexus S to the latest completely stock 2.3.4
Then you can flash recovery again and go back to clockwork mod and go flash another rom or whatever.
Remember when you're flashing a new rom you need to wipe data and cache and dalvik cache.
i run an restore from the backup that i made before installing the new rom using clockwork mod recovery, its part of the option when installing the rom using the rom manager * click box - backup * etc something like that
sheunghko said:
i run an restore from the backup that i made before installing the new rom using clockwork mod recovery, its part of the option when installing the rom using the rom manager * click box - backup * etc something like that
Click to expand...
Click to collapse
Next time don't use Rom Manager to make backups or flash roms. It's stupid and can get you issues like you're having.
Anyways, try wiping data and cache then restoring the backup, do it in Clockwork Recovery.
Let it boot, first boot always takes a while, 5-10 minutes. If you see the boot animation freeze, stop and restart, then yeah it's screwed up, otherwise, just let it is.
If still not working from your backup, do what I said in previous reply, just restore to stock 2.3.4 then re flash clockwork mod and start over with the rom you want to flash.
thank your nxt. i have found the real problem. it was not my backup problem or the rom that u provided. it was the version of my clockwork mod recovery. i was using an 2.x.x.x to restore the phone which is why it doesn't work. everything work fine now after i flashed with an 3.x.x.x and restore the phone. one question thou, where can i always find the newest clockwork mod recovery release ? thank you very much
sheunghko said:
thank your nxt. i have found the real problem. it was not my backup problem or the rom that u provided. it was the version of my clockwork mod recovery. i was using an 2.x.x.x to restore the phone which is why it doesn't work. everything work fine now after i flashed with an 3.x.x.x and restore the phone. one question thou, where can i always find the newest clockwork mod recovery release ? thank you very much
Click to expand...
Click to collapse
http://mirrorbrain.cyanogenmod.com/cm/recoveries/
Or just use ROM Manager to get the latest.
That's the only thing I use ROM Manager for... getting the latest Recovery.
thanks again nxt. if you don't mind really ...i have one more question. i know the phone intend to uninstall clockwork mod recovery once its restarted. i know there is command type into the cmd to avoid the phone uninstall the clockworkmod reovery and make it permanent in another word. I didn't run those command when i root my phone because i don't know if its good to make it permanent like.... hmmm like if there will be a 2.3.5 coming next month..just saying ok... with a permanent unofficial recovery will cause a problem?
sheunghko said:
thanks again nxt. if you don't mind really ...i have one more question. i know the phone intend to uninstall clockwork mod recovery once its restarted. i know there is command type into the cmd to avoid the phone uninstall the clockworkmod reovery and make it permanent in another word. I didn't run those command when i root my phone because i don't know if its good to make it permanent like.... hmmm like if there will be a 2.3.5 coming next month..just saying ok... with a permanent unofficial recovery will cause a problem?
Click to expand...
Click to collapse
Are you running custom ROM? If you are, it's already made to not revert back to stock recovery. If you leave it stock recovery you'll get notifications for firmware updates by Google, but remember that applying those to a rooted phone might screw things up too.
the blue one is stock recovery right?
sheunghko said:
the blue one is stock recovery right?
Click to expand...
Click to collapse
Don't remember. It should only have like 3-4 options.
thanks again nxt. no i am not running an custom rom. i mean not yet. i planed to try one from the rom manager download section then my phone couldn't start after installation and now i have restored my phone from my backup using the clockwork mod recovery 3.x.x.x.
I'm sorry in advance if it has been asked already.
Do I need to perform any wipes before restoring a backup? I'm currently on CM7.2 RC1 and made a backup of it and want to switch to Defy+ CM9 build for a while then go back to CM7.2. Last time I did it (restored CM7 backup after installing CM9) it just stuck on Boot logo and couldn't move on so I had to start from scratch (new installation). Any guides just mention clicking on restore and that's all. Thanks in advance for an answer!
Can anyone help me? I did as I wrote (switched for a while to CM9 GB build from CM7.2 FROYO) then wanted to restore CM7 backup, tried both with and without wipes (data, cache, dalvik) but it just gets stuck on boot logo and won't move on. What am I doing wrong?
You don't need to do a wipe for restoring a nandroid..
I assume you're using the same recovery with which you made the backup..
neo.ank said:
You don't need to do a wipe for restoring a nandroid..
I assume you're using the same recovery with which you made the backup..
Click to expand...
Click to collapse
Thanks for an answer! I made a backup with CM7 (froyo) recovery and was restoring with the one that was installed along with CM9 (gb). So that was the cause?
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
MarcinRN said:
I'm sorry in advance if it has been asked already.
Do I need to perform any wipes before restoring a backup? I'm currently on CM7.2 RC1 and made a backup of it and want to switch to Defy+ CM9 build for a while then go back to CM7.2. Last time I did it (restored CM7 backup after installing CM9) it just stuck on Boot logo and couldn't move on so I had to start from scratch (new installation). Any guides just mention clicking on restore and that's all. Thanks in advance for an answer!
Click to expand...
Click to collapse
Why don't you try Dual Boot...
refer to the below mentionedlink:
http://forum.xda-developers.com/showthread.php?t=1364659
However, to install CM9 I'm not sure if someone uploaded itsnandroid backup. Please note that to use the backup and restore youcan only use a Nandroid backup as ROM.zip file can not be restored.
What I understand from your post is that you have CM9 rom in zipformat; if this is the case then you can only install it usingInstall from SD card option from Custom Recovery.
---------- Post added at 11:09 PM ---------- Previous post was at 11:09 PM ----------
neo.ank said:
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
Click to expand...
Click to collapse
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
neo.ank said:
You flashed the CM9 ROM through recovery.. right??
ROM's do not change recovery.. Its the same for both..
Click to expand...
Click to collapse
Yes, i flashed CM9 through recovery.
Rajneeshgadge17 said:
Why don't you try Dual Boot...
refer to the below mentionedlink:
http://forum.xda-developers.com/showthread.php?t=1364659
However, to install CM9 I'm not sure if someone uploaded itsnandroid backup. Please note that to use the backup and restore youcan only use a Nandroid backup as ROM.zip file can not be restored.
What I understand from your post is that you have CM9 rom in zipformat; if this is the case then you can only install it usingInstall from SD card option from Custom Recovery.
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
Click to expand...
Click to collapse
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
MarcinRN said:
Yes, i flashed CM9 through recovery.
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
Click to expand...
Click to collapse
Technically, you haven't done anything wrong. What I've learnt from my experience and posts, this is one heck of a weird phone.
Might be a chance your backup is corrupted or incomplete (highly unlikely bt I've seen it in a device)
Or some other glitch which m nt sure of..
Sent from my MB526 using Tapatalk 2
Wiping data removes Custom recovery. If the new ROM has aCustom recovery then only it appears otherwise we have to reinstallthe Custom recovery.
Click to expand...
Click to collapse
Well as I said..this phone definitely acts senseless sometimes.. a data wipe in my case didn't remove the recovery or bootmenu.
Even reported it in the app thread..
Sent from my MB526 using Tapatalk 2
neo.ank said:
Technically, you haven't done anything wrong. What I've learnt from my experience and posts, this is one heck of a weird phone.
Might be a chance your backup is corrupted or incomplete (highly unlikely bt I've seen it in a device)
Or some other glitch which m nt sure of..
Click to expand...
Click to collapse
It was second time it failed to restore a backup I was trying to do the same a while ago and was unsuccesfull too. Seems like my phone is cursed
Thanks for trying anyway!
MarcinRN said:
Yes, i flashed CM9 through recovery.
I think you got me wrong. I was using CM 7.2 Froyo build and made a backup of it through recovery. Then I installed CM9 GB build (wiped data, installed rom, kernel, gapps) and have been using it for a while then I wanted to switch back to my CM7.2 backup (went to the recovery, choosed restore) and it said restoring was succesfull but when I rebooted it just stuck on bootlogo and couldn't move on. Any idea what am I doing wrong?
Click to expand...
Click to collapse
Now, I understand your issue.
Try using below mentioned steps:
1. Boot into latest/custom recovery;
2. Wipe data/cache;
3. Restore the complete Nandroid backup;
4. Now from advance wipe dalvik cache and battery logs;
5. Now reboot the phone.
Please use above mentioned steps and share the results.
Hope this helps!!
Also try to install latest clockwordmod backup.
check this website for more detail http://www.clockworkmod.com/
@MarcinRN
I think your problem is kernel related, if you switch to CM7 from CM9 with GB-Kernel you must restore the froyo-kernel for CM7.
RATTAR said:
@MarcinRN
I think your problem is kernel related, if you switch to CM7 from CM9 with GB-Kernel you must restore the froyo-kernel for CM7.
Click to expand...
Click to collapse
That's the problem. You can find the kernels on epsy's site. Flash the kernel and restore the nand (there are also options in advanced restore if it still doesn't work, don't know if you need them)
Sent from my MB525 using XDA
Thanks guys I'll try it next time. However, I read somewhere that backup contains kernel too, don't know how much true is in that.
I am running Stock-Rooted with the Faux123 Kernel and I recently got a notification from GooManager that there was a Gapps update so I ran the update. Now every time I reboot, I get the Android is Upgrading dialog. I know this is usually done when you wipe Cache or install another rom but this is happening on every reboot now. ALso, I keep losing sound as well. Does anyone know how I can fix this issue or should I backup everything and load the factory image? I did do a nandroid backup but I the backup was corrupted so I cannot load that. I do have one other backup but that was from back in August. I know that I should of made a more recent backup but I did not.
BTW: I have Clockworkmod as my recovery and this has nothing to do with the Faux123 kernel as I have been using the same version for months without any issues.
Thanks
OK I did have a sooner backup - 10/09 right before the 4.1.2 update but it was made using TWRP and now I use ClockWorkMod. So can I restore a TWRP backup using CWM or do I need to reinstall TWRP and then restore?
comhack said:
I am running Stock-Rooted with the Faux123 Kernel
Click to expand...
Click to collapse
Errm, that's not very stock....
I can't be the only one who read the title and got happy thinking 4.2 was rolling out..
Misleading title is misleading.
I thought the same, though it's only the 7th.
Im having 2 issues with phillys recovery n not sure wut im doin wrong. I did a backup and when I restored it gapps forceclosed and phone wouldnt let me do anything. Secondly ive tried doing he create custom rom. It flashs fine but wont pass bootloader s4 screen. Need help. Would love to be able to make a flashable rom with my ultra slim rom n possibly have my xposed tweets built in.
TeamBlaze
Got backup to work. But still unable to get custom rom aka update.zip to get past bootloader. Anyone kno how to fix this.
TeamBlaze
If you're talking about the update.zip made from Titanium, it is NOT a custom ROM.
It is simply a backup of your applications (and some settings) you can use to flash after flashing a ROM to 're-load' all your stuff.
If you get your current ROM configured the way you like it you can then create a nandroid to restore it later if that is what you want. And without any info on what version of Android you're on, what ROM you're on, or what version of the recovery you're on there is no way to tell you where to go from here.
leaderbuilder said:
If you're talking about the update.zip made from Titanium, it is NOT a custom ROM.
It is simply a backup of your applications (and some settings) you can use to flash after flashing a ROM to 're-load' all your stuff.
If you get your current ROM configured the way you like it you can then create a nandroid to restore it later if that is what you want. And without any info on what version of Android you're on, what ROM you're on, or what version of the recovery you're on there is no way to tell you where to go from here.
Click to expand...
Click to collapse
No. From philz touch recovery. In the custom backups you can selete create a custom rom from backup and I can't get tht to flash right after makin. Clean install n everything.
TeamBlaze
yotaking said:
No. From philz touch recovery. In the custom backups you can selete create a custom rom from backup and I can't get tht to flash right after makin. Clean install n everything.
TeamBlaze
Click to expand...
Click to collapse
Never tried that (make ROM from recovery in philz) myself.
I just make and restore loads of backups using Philz and TWRP. I consider a full backup (complete image(s) of all phone partitions) to be my ROM(s).
I would bet that with what you're doing that if, after you flash your custom made zip (and before rebooting) you stayed in recovery and then flashed (install zip) of the same recovery, rebooted back to recovery and flashed the kernel it may work.
Rebooting the recovery (or a battery pull) often clears out hangs.
Did you tried enabling se linux context from backup settings?
Sent from my GT-I9505 using xda app-developers app
do you have 4.3 compatability checked off?
same issue
yotaking said:
Im having 2 issues with phillys recovery n not sure wut im doin wrong. I did a backup and when I restored it gapps forceclosed and phone wouldnt let me do anything. Secondly ive tried doing he create custom rom. It flashs fine but wont pass bootloader s4 screen. Need help. Would love to be able to make a flashable rom with my ultra slim rom n possibly have my xposed tweets built in.
TeamBlaze
Click to expand...
Click to collapse
I had similair issues with philz. idid a very improtnact nandroid backup and when iwent ot restore it didnt work. I definately like TWRp the best. Best UI and never any issues for me.
androidaddicted said:
I had similair issues with philz. idid a very improtnact nandroid backup and when iwent ot restore it didnt work. I definately like TWRp the best. Best UI and never any issues for me.
Click to expand...
Click to collapse
I like twrp as well but dnt wrk on 4.3
TeamBlaze
dewrust said:
do you have 4.3 compatability checked off?
Click to expand...
Click to collapse
Conito11 said:
Did you tried enabling se linux context from backup settings?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Imma look into these
TeamBlaze