I rooted someone's phone earlier and first tried to flash AmonRA 1.5.2. It wouldn't load into recovery, so I flashed 1.2.3. That one worked, but wanted a newer one, so I went with God Speed. I made a backup and then flashed a 2.1 ROM. I was then showing him how to do a nandroid backup and restore and it wouldn't restore. I made another backup of the new ROM and tried to restore it. Still wouldn't restore. I then flashed AmonRA 1.6.2 and tried the same thing. Still would not restore. Everything works fine on my phone and they are both w/Google phones. I also copied his sdcard to my computer and reformatted his sdcard. Still would not work. Any ideas or suggestions.
'Wouldn't restore' is kind of vague. Did it appear to restore but not? Did the restore fail, and if so, what message came up?
try to rename the nandroid and make sure you phone is plugged into the wall or pc when restoring.
fixxxer2008 said:
try to rename the nandroid and make sure you phone is plugged into the wall or pc when restoring.
Click to expand...
Click to collapse
He'll only need to rename it if he already renamed it and put spaces in it. Plugging it into the wall won't make a difference unless the screen is shutting down due to power issues during the restore.
Two reasons why I asked for further clarification on what happens during a restore attempt.
smw6180 said:
He'll only need to rename it if he already renamed it and put spaces in it. Plugging it into the wall won't make a difference unless the screen is shutting down due to power issues during the restore.
Two reasons why I asked for further clarification on what happens during a restore attempt.
Click to expand...
Click to collapse
i dunno but that always worked for me. i had a message that said restore via adb.
fixxxer2008 said:
i dunno but that always worked for me. i had a message that said restore via adb.
Click to expand...
Click to collapse
restore via adb always happens when a nandroid has been renamed and has a space in it. I'm not saying that's the ONLY reason, but it's the only time I've ever seen or heard of it.
let me look at the copies on my computer.
The error I get is to do it via adb. But I didn't rename it or anything. All I did was
1. Flash the recovery
2. Reboot into recovery
3. Perform Nandroid Backup (just the basic nand backup)
4. Installed DC2.07 as that was what I had on my computer
5. Rebooted and let it load
6. Rebooted into recovery
7. tried to restore and I get the error about performing it via adb
Tried the same routine everytime I flashed a new recovery
Edit:Just checked the nandroid backups---There are no spaces
&RoidRage said:
let me look at the copies on my computer.
The error I get is to do it via adb. But I didn't rename it or anything. All I did was
1. Flash the recovery
2. Reboot into recovery
3. Perform Nandroid Backup (just the basic nand backup)
4. Installed DC2.07 as that was what I had on my computer
5. Rebooted and let it load
6. Rebooted into recovery
7. tried to restore and I get the error about performing it via adb
Tried the same routine everytime I flashed a new recovery
Edit:Just checked the nandroid backups---There are no spaces
Click to expand...
Click to collapse
Interesting. Then I'd try what fixxer said and plug it into the wall before trying the restore.
I will try that tomorrow
sandboxlove said:
hi there
i actually had the same problem today but then i learned (through a search...woah!!) that there is an newer ra, and after an update it worked like a beaut. perhaps your recovery is outdated...or maybe the nandroid is corrupted?
good luck!
Click to expand...
Click to collapse
I'm pretty sure 1.6.2 is the newest which is what is on there now. I've read of other peoples problems and solutions and tried what i rememebered, but it happened with every one I tried.
&RoidRage said:
I'm pretty sure 1.6.2 is the newest which is what is on there now. I've read of other peoples problems and solutions and tried what i rememebered, but it happened with every one I tried.
Click to expand...
Click to collapse
You're not on an ext4 filesystem are you? If so, you'll want godspeed (toast's version of the 1.6.2 recovery image). I believe it handles ext4 restores whereas the original 1.6.2 doesn't (if I remember correctly).
smw6180 said:
You're not on an ext4 filesystem are you? If so, you'll want godspeed (toast's version of the 1.6.2 recovery image). I believe it handles ext4 restores whereas the original 1.6.2 doesn't (if I remember correctly).
Click to expand...
Click to collapse
No, I did partition it to see if that would help, but only converted it to ext3. But I did not try nand+ext. I had him register with the site and will direct him to this thread.
Nandroid Restore
Yeah, i'm the one having this problem. I'm new to modding phones and not for sure what to do. &RoidRage is trying to help me out, if anyone else can that's figure it out that would be great.
Anytime I received the the "via adb" error, it was due to their not being enough memory on the sd card. I found you typically will need a little over 1 GB on the card remaining to do anything: Restore, or backup.
Hope that helps.
And make sure your battery is charged.
Related
I have been browsing google for an answer to this problem but nothing I have found has seemed to help, so I suppose I'll ask and see if anyone else has had this problem had knows what to do.
I try to run a nandroid backup from cyanogen's recovery, it simply keeps making dots and will easily fill up a screen.
Furthermore, i try and do a "nandroid-mobile.sh -b" and it hangs on the data.img part for in excess of 20 minutes.
Any ideas what I can try to get nandroid to work again? It has failed to work both on the last version of SuperD and on the newest which I updated last night (1.11?)
I suppose I could try a full wipe and reinstall, but I haven't donated for the full Titanium backup yet... and restoring is a pain until I do that.
Is there anything besides a wipe that I could try?
Thanks
Tylerspilker said:
I have been browsing google for an answer to this problem but nothing I have found has seemed to help, so I suppose I'll ask and see if anyone else has had this problem had knows what to do.
I try to run a nandroid backup from cyanogen's recovery, it simply keeps making dots and will easily fill up a screen.
Furthermore, i try and do a "nandroid-mobile.sh -b" and it hangs on the data.img part for in excess of 20 minutes.
Any ideas what I can try to get nandroid to work again? It has failed to work both on the last version of SuperD and on the newest which I updated last night (1.11?)
I suppose I could try a full wipe and reinstall, but I haven't donated for the full Titanium backup yet... and restoring is a pain until I do that.
Is there anything besides a wipe that I could try?
Thanks
Click to expand...
Click to collapse
I have the same issue using Amon Ra's recovery with Nandroid.
I end up pulling the battery and rebooting.
Take a look in your Nandroid backup folder on your SD card....you will see files that are several GB in size.
The nandroid appears to get stuck in a loop.
I have not had a successful nandroid backup made since CM-Recovery. I might go back to it but Amon Ra has a lot more stuff.
I reverted over to Amon Ra recovery from the JF+ Cyan one, and did a full wipe and restore of everything and nandroid was working well after.
Not sure what happened, but its all peachy now. I donated to Titanium backup, and it is the best app I have used... makes me want to switch Roms daily now!
Tylerspilker said:
I reverted over to Amon Ra recovery from the JF+ Cyan one, and did a full wipe and restore of everything and nandroid was working well after.
Not sure what happened, but its all peachy now. I donated to Titanium backup, and it is the best app I have used... makes me want to switch Roms daily now!
Click to expand...
Click to collapse
Which Amon_Ra? I had the same issue on 1.5.x and 1.6.2.
Still no joy on nandroid or BART.
I created a Nandroid backup of the stock Nexus S Rom. This includes the latest OTA GRH78 that just got pushed out today 12/22/10. This is 100% stock.
Link: http://www.mediafire.com/?ontvvh8z9h9lb7a
WARNING: This will wipe everything on your phone
Requirements:
-Clockwork recovery or other custom recovery
-The nandroid backup from here http://www.mediafire.com/?ontvvh8z9h9lb7a
-Transfer cable, to transfer contents of downloaded file to phone's internal memory
Instructions:
1. Download nandroid file from link provided above
2. Extract the .zip file on your computer
3. Move the folder "2010-12-22.21.06.07" to the clockworkmod/backup/ directory of your phones internal storage
Note: if you have never used nandroid you wont have the directory clockworkmod/backup on your phones internal storage, so you will have to manually create those folders, then put the folder "2010-12-22.21.06.07" in the new folders you created
4. Now go into your clockwork recovery manager, you can do this by typing in "adb reboot recovery" if you have adb setup on your computer, and the phone is connected. Or while the phone is turned off hold the volume up+power to get into bootloader mode, then go down to "recovery" by using the volume up/volume down keys to scroll up or down, then press the power button to launch it, and this will launch the recovery manager
5. Once your in clockwork mod recovery select "backup and restore"
6. Then click "restore"
7. Now you should be able to choose and select "2010-12-22.21.06.07"
8. Clockwork will now restore this nandroid backup
9. Reboot system
Note: This version of android build "GRH78" will make sure you have the stock recovery manager everytime you reboot the phone. So after doing this, after you reboot you will no longer have clockwork mod.
Edit: According to xda member Luxferro the new update introduced /etc/install-recovery which may have not been in 2.3, but anyways, it runs this on bootup, and if the MD5 of the recovery doesn't match what is expected, it reflashes the stock recovery back over, so if you dont want the stock recovery to be flashed everytime you boot if your on clockwork or another non stock rom, just rename it to prevent it from running on boot. And for those of you who want to return your phone back to stock this nandroid will do that for you since it also flashes the stock recovery.
Video on how to unroot the nexus s and return to stock
http://theunlockr.com/2011/01/20/how-to-unroot-the-nexus-s/
Video via xda member dcogen
will this method rest the phone and erase phone info?
yungfresh said:
will this method rest the phone and erase phone info?
Click to expand...
Click to collapse
yes this will erase everything, this is meant for people who want to go back to stock.
I unlocked the bootloader and flashed clockword mod only. I didn't flash any custom roms. If I do this method, will it lock the bootloader and remove clockword mod?
yungfresh said:
I unlocked the bootloader and flashed clockword mod only. I didn't flash any custom roms. If I do this method, will it lock the bootloader and remove clockword mod?
Click to expand...
Click to collapse
No, this will not touch the bootloader, or the recovery. The phone bootloader will stay unlocked, and the recovery manager will stay in tact.
Hi there, your "stock" nandroid is screwed up.
I just tried it right now and TONS of apps are missing from the market with your nandroid.
PayPal, NYTimes, aFile, Fios Mobile Remote, TONS of stuff that I had are gone from the Market.
I pulled out my SIM card, and still all missing.
I restored my Nandroid of my current system, and they're all back in the Market.
nxt said:
Hi there, your "stock" nandroid is screwed up.
I just tried it right now and TONS of apps are missing from the market with your nandroid.
PayPal, NYTimes, aFile, Fios Mobile Remote, TONS of stuff that I had are gone from the Market.
I pulled out my SIM card, and still all missing.
I restored my Nandroid of my current system, and they're all back in the Market.
Click to expand...
Click to collapse
Hmm, very odd. Anyone else having this issue?
Sent from my Nexus S using XDA App
momohammed20 said:
No, this will not touch the bootloader, or the recovery. The phone bootloader will stay unlocked, and the recovery manager will stay in tact.
Click to expand...
Click to collapse
so... for people that want to fully return to stock:
apply this update. go to fastboot mode and then do a fastboot oem lock. this will reset the phone and recovery partition to full stock.
you can check this by rebooting into recovery and now the recovery will be stock.
I don't think his nandroid file is messed up, there's a different market version its now 2.13 not 2.12 like on the previous build. I think that has something to do with it
Now I'm having a problem with everytime I reboot the phone I lose clockworkmod recovery an I got to reflash it with rom manager. I don't lose root tho but I lost it when I did his nandroid an had to reroot
momohammed20 said:
Hmm, very odd. Anyone else having this issue?
Click to expand...
Click to collapse
Yup. I tried it, and I'm missing those apps as well.
Yes, me too. I lost many of the apps available in the market and the ability to go into recovery.
*Facepalm
These apps were missing from the Nexus S originally on day 1... Lol.
It's how Android market works. New builds don't get full market support. You need to wait for Google to update their system to allow the new build to get copy protected apps from the market.
Will this wipe my sd card?
I just checked and I don't have those apps either in market, and I'm on stock.
Sent from my Nexus S using XDA App
Sigh! You're not supposed to have those apps.
It's not an issue with this nandroid, it's an issue with every single new version / update to android on any phone. You will always have missing apps until Google adds the build number to its servers.
Other than that, thanks a lot for posting this OP! Saved me a huge pain in the ass getting updated -_-
Yes, maybe the apps issue is an issue with the server not updating yet, but have you noticed any problem with the clockwork recovery not functioning after reboot?
My recovery reverted to 3e recovery after flashing this. Clockwork is gone. No problem though, I wanted clockwork gone.
Now how do we root without flashing clockwork ?
I will try to investigate the recovery issue. But some people wanted to go back to stock recovery, and were not able to with the stock recoveries floating around, so that's pretty odd that this nandroid takes you back to stock recovery.
Sent from my Nexus S using XDA App
bogdi1988 said:
so... for people that want to fully return to stock:
apply this update. go to fastboot mode and then do a fastboot oem lock. this will reset the phone and recovery partition to full stock.
you can check this by rebooting into recovery and now the recovery will be stock.
Click to expand...
Click to collapse
Really? That's interesting. Has anyone actually done this and confirmed it restores stock recovery? Easy fix for something that's been vexing quite a few people the last few days.
How long till the Market "fixes" itself and updates to 2.1.2 so the missing apps appear on the market?
Hey Everyone,
I was just testing CM7 but I kept getting black screens after I locked the screen, so I went back to CWM and restored. The restore went fine but when I pressed 'Reboot phone now' it went into a bootloop. I then pulled the battery and tried wiping everything and restoring again. No success, still bootlooping.
So...any ideas?
<Edit> I flashed CWM with NVFlash (i have no idea why i did that) so now im on an older version of CWM and it cannot find my backups.
Martin9630 said:
Hey Everyone,
I was just testing CM7 but I kept getting black screens after I locked the screen, so I went back to CWM and restored. The restore went fine but when I pressed 'Reboot phone now' it went into a bootloop. I then pulled the battery and tried wiping everything and restoring again. No success, still bootlooping.
So...any ideas?
<Edit> I flashed CWM with NVFlash (i have no idea why i did that) so now im on an older version of CWM and it cannot find my backups.
Click to expand...
Click to collapse
maybe u stored ur restore in the External SD...and it is not able to find it...maybe u can try to install ROM manager and flash the latest CWM via the ROM manager...did u try tht?
I cannot boot into my phone. The only thing I can access is my the old CWM that i got through NVFlash. Restoring worked but still bootlooped when I had the newer CWM.
Martin9630 said:
I cannot boot into my phone. The only thing I can access is my the old CWM that i got through NVFlash. Restoring worked but still bootlooped when I had the newer CWM.
Click to expand...
Click to collapse
As far as I remember....i think if u have stored your backup in the internal SD...then nvflash will do a wipe/....so u dont find it....do u have a backup in the computer which can be loaded to the EXTSD card and then try the restore....
Just a silly question:if u have restored....which backup u restored to???
Hey there. Thanks for your care and input. I've managed to fix my phone.
It happened to be that the CM7 I installed converted my phone to EXT4, I downloaded the EXT3 converter and now it's working.
Don't worry, your input is not wasted! I will still hit that thanks button.
Martin9630 said:
Hey there. Thanks for your care and input. I've managed to fix my phone.
It happened to be that the CM7 I installed converted my phone to EXT4, I downloaded the EXT3 converter and now it's working.
Don't worry, your input is not wasted! I will still hit that thanks button.
Click to expand...
Click to collapse
I appreciate this gesture mate....
I have tried this numerous times still no result.
Cm 10.1.3 works perfectly fine. But once i flash it with my Titanium backup update.zip file. There will be errors, and after i reboot it, it iwll just get stuck at the spinning blue circle. I have tried everything, from apps+data to only app data. Nothing works.
I would have to factory reset and reflash it again.
I use clockworks mod recovery.
My phone is a odin rooted Galaxy S3 Lte (i9305)
Shinny123 said:
I have tried this numerous times still no result.
Cm 10.1.3 works perfectly fine. But once i flash it with my Titanium backup update.zip file. There will be errors, and after i reboot it, it iwll just get stuck at the spinning blue circle. I have tried everything, from apps+data to only app data. Nothing works.
I would have to factory reset and reflash it again.
I use clockworks mod recovery.
My phone is a odin rooted Galaxy S3 Lte (i9305)
Click to expand...
Click to collapse
use recovery to flash roms not TB, its much more reliable.. i think the problem is because of apps and data you trying to restore with the update.zip. i know you use tb because you want to restore your apps+data easily while flashing new rom, but tb seems to give problems with this method
MaHo_66 said:
use recovery to flash roms not TB, its much more reliable.. i think the problem is because of apps and data you trying to restore with the update.zip. i know you use tb because you want to restore your apps+data easily while flashing new rom, but tb seems to give problems with this method
Click to expand...
Click to collapse
Nah, i didnt flash my rom with tb, i flashed it with recovery. Then once everything was done, i would go back into recovery and flash the update.zip file
Shinny123 said:
Nah, i didnt flash my rom with tb, i flashed it with recovery. Then once everything was done, i would go back into recovery and flash the update.zip file
Click to expand...
Click to collapse
yes i see, but that seems to be the problem ''restoring apps, data with tb'' and from what i know it occurs that this sometimes gives errors, fc's and bootloops like in your case
MaHo_66 said:
yes i see, but that seems to be the problem ''restoring apps, data with tb'' and from what i know it occurs that this sometimes gives errors, fc's and bootloops like in your case
Click to expand...
Click to collapse
So is there no way to go through with this? Maybe export my backups to another software or something? or am i supposed to start fresh?
Shinny123 said:
So is there no way to go through with this? Maybe export my backups to another software or something? or am i supposed to start fresh?
Click to expand...
Click to collapse
you could try to export your backups (only data) to pc temporary and after having flashed the rom with full wipe, install the apps again and put the backups manually in corresponding directories and see how that is gonna work out. I gave up on TB because of this problem and usually i always start fresh with new flashed roms. I only put my personal files on pc and put it back manually after rom install.
MaHo_66 said:
you could try to export your backups (only data) to pc temporary and after having flashed the rom with full wipe, install the apps again and put the backups manually in corresponding directories and see how that is gonna work out. I gave up on TB because of this problem and usually i always start fresh with new flashed roms. I only put my personal files on pc and put it back manually after rom install.
Click to expand...
Click to collapse
Thanks so much, I dont really need all my apps to be backed up, just important ones, has the manual method worked out for you?
Shinny123 said:
Thanks so much, I dont really need all my apps to be backed up, just important ones, has the manual method worked out for you?
Click to expand...
Click to collapse
yes, most of the times works fine but cant guarantee it will work with every app, i guess has something to do with permissions i.m.h.o
Is it possible to retrieve data from a soft bricked phone (failed to mount /system (invalid argument))?
I was so absent minded that I actually copied out a TB backup from 2013 (I probably saved it into another folder) into my computer instead of the latest copy. I am hoping to be able to retrieve my latest TB backup copy from the internal SD.
Before disaster happened, was already rooted with custom rom on JB 4.3.
What happened:
Tried to update from 4.3 to 4.4 through Odin but halfway got stuck at boot.img.
Unplugged and tried to reset but phone was stuck in the screen - firmware upgrade encountered an issue... ......
Flashed a kernel found in this forum to get it out of that screen.
Managed to get into recovery (android recovery instead of CWM) and there was an error with mounting /system, /data and some others which I can't recall.
So I tried flashing 4.4 again and finally after multiple attempts including changing ports and cables was the flash was successful.
Then I rooted and tried to restore my backups which was when I realised that I have the old backup files instead.
Couldn't find my latest backup anywhere which is why I'm here.
Any advice would be very much appreciated.
Thanks all for viewing.
netty88 said:
Is it possible to retrieve data from a soft bricked phone (failed to mount /system (invalid argument))?
I was so absent minded that I actually copied out a TB backup from 2013 (I probably saved it into another folder) into my computer instead of the latest copy. I am hoping to be able to retrieve my latest TB backup copy from the internal SD.
Before disaster happened, was already rooted with custom rom on JB 4.3.
What happened:
Tried to update from 4.3 to 4.4 through Odin but halfway got stuck at boot.img.
Unplugged and tried to reset but phone was stuck in the screen - firmware upgrade encountered an issue... ......
Flashed a kernel found in this forum to get it out of that screen.
Managed to get into recovery (android recovery instead of CWM) and there was an error with mounting /system, /data and some others which I can't recall.
So I tried flashing 4.4 again and finally after multiple attempts including changing ports and cables was the flash was successful.
Then I rooted and tried to restore my backups which was when I realised that I have the old backup files instead.
Couldn't find my latest backup anywhere which is why I'm here.
Any advice would be very much appreciated.
Thanks all for viewing.
Click to expand...
Click to collapse
I'm not quite sure what you are trying to say, your phone is able to boot but you can't find backups that were stored on your internal SD before flashing 4.4? Have you tried looking for them with Total Commander? (Or any other file manager with root access).
ArkThompson said:
I'm not quite sure what you are trying to say, your phone is able to boot but you can't find backups that were stored on your internal SD before flashing 4.4? Have you tried looking for them with Total Commander? (Or any other file manager with root access).
Click to expand...
Click to collapse
It was soft bricked for awhile and then I managed to flash a rom successfully so afterwards it was able to boot. Actually it seems like my entire phone was wiped because I couldn't find traces of anything with a file manager.
netty88 said:
It was soft bricked for awhile and then I managed to flash a rom successfully so afterwards it was able to boot. Actually it seems like my entire phone was wiped because I couldn't find traces of anything with a file manager.
Click to expand...
Click to collapse
Is /data/media/0 empty?
ArkThompson said:
Is /data/media/0 empty?
Click to expand...
Click to collapse
Yup, empty. I meant that it was all there before I flashed 4.4 but I saved the wrong backups and after flashing I couldn't find them anymore.
netty88 said:
Yup, empty. I meant that it was all there before I flashed 4.4 but I saved the wrong backups and after flashing I couldn't find them anymore.
Click to expand...
Click to collapse
Odin probably formats the main partitions when it flashes a ROM. I had something similar happen after flashing 4.3 to recover from a softbrick. Did you ever make a nandroid backup or did you only use TB? Also, if you lost your contacts you could check whether they were also saved onto your sim card.
ArkThompson said:
Odin probably formats the main partitions when it flashes a ROM. I had something similar happen after flashing 4.3 to recover from a softbrick. Did you ever make a nandroid backup or did you only use TB? Also, if you lost your contacts you could check whether they were also saved onto your sim card.
Click to expand...
Click to collapse
Nandroid is the one that is saved as update.zip?
netty88 said:
Nandroid is the one that is saved as update.zip?
Click to expand...
Click to collapse
No, you make them using a custom recovery and they are a series of .tar, .img or .win files.
ArkThompson said:
No, you make them using a custom recovery and they are a series of .tar, .img or .win files.
Click to expand...
Click to collapse
I did make a nandroid backup but it couldn't be found after the soft brick recovered
netty88 said:
I did make a nandroid backup but it couldn't be found after the soft brick recovered
Click to expand...
Click to collapse
If you don't have any backups on your external SD then you might be out of luck unfortunately.
ArkThompson said:
If you don't have any backups on your external SD then you might be out of luck unfortunately.
Click to expand...
Click to collapse
I did suspect that... Just wanted to be sure. But thanks so much for your help