This may be a noob question.... So I renamed one of my nand backups and now I get an error when restoring.... "Error : run 'nandroid-mobile.sh restore' via adb!"
Any ideas?
Cleetis said:
This may be a noob question.... So I renamed one of my nand backups and now I get an error when restoring.... "Error : run 'nandroid-mobile.sh restore' via adb!"
Any ideas?
Click to expand...
Click to collapse
how charged on your battery ? i get that when my battery is low
I'd say battery as well. Also remember not to put any funky characters when you rename
~ I'm a fungi
My battery is at 98%. I named the backup "Stock FroYo". Without the quotes. Should I rename it again?
Thanks guys!
If your file was something like BCDS-20110104-1014 then you should rename it BCDS-20110104-1014namehere Important thing to do is to keep the original file name and whatever you add must have no spaces in it.
Or, as others have suggested, it could be low battery. You can move the log to your sdcard in recovery or run it from adb to get more info on the exact error.
Cleetis said:
My battery is at 98%. I named the backup "Stock FroYo". Without the quotes. Should I rename it again?
Thanks guys!
Click to expand...
Click to collapse
I_don't_use_spaces_just_underscores. But I do rename the whole. Typically by rom name,date,version,etc
~ I'm a fungi
Yes I believe its the space. Had the same issue.
Sent from my PC36100 using XDA App
Thanks guys! Sorry for the noob problem as I'm sure it was. I have only had my EVO rooted as of this past weekend. I guess I should have known about not having spaces.... That was it! I renamed it without the spaces and booted right up!
Thanks everyone!
You saved me! lol
Cleetis said:
Thanks guys! Sorry for the noob problem as I'm sure it was. I have only had my EVO rooted as of this past weekend. I guess I should have known about not having spaces.... That was it! I renamed it without the spaces and booted right up!
Thanks everyone!
You saved me! lol
Click to expand...
Click to collapse
Happy it worked.
Don't forget to post your questions in the q&a section for the future
sent from my manila carbon rom
Sorry about that! Will do though. From here on out.
Clint
Related
Because AdFree is not working on Desire:
I've made hosts file which is compilation of two lists and some manual additions (for correct blocking of admob). So I decided to share with my list. Use it if You want to. Please tell me if this forum is wrong for that list.
Sorry for the n00b question but how do you install this?
Nice one mate. You've just reminded me I needed to redo my hosts file after installing Modaco Froyo, and I might as well use yours as it'll be more up to date than mine.
Ghisy said:
Sorry for the n00b question but how do you install this?
Click to expand...
Click to collapse
ditto this, instructions for us noobies?
unzip the host file
than enter recovery
adb-windows shell mount /system
adb-windows shell mv /system/etc/hosts /sdcard/backuphost
adb push c:\hosts /system/etc
that should wrok if you unziped hosts.zip to c:\ and if something goes wrong you have your original hosts file backed up in /sdcard/backuphost
hope this helps
p.s. i didn't try this
did everything, and adfree is still not working in froyo...
Thanks anyway!
Edit: Now, Adfree FCs!
Edit 2: I did it again and it worked!
Could someone please create a zip file, that can be falshed through clockworkmod recovery? This would be fantastic.
Try this, mate. [Click!]
dnlgee said:
Try this, mate. [Click!]
Click to expand...
Click to collapse
Thanks dnlgee I put it in my repo on ROM Manager
This is great, thanks for sharing - it seems to work great. I might go back to a stock hosts though - I like to block ads when browsing, but I feel bad about doing it for ad-supported applications. That's just me though
shawe_ewahs said:
Thanks dnlgee I put it in my repo on ROM Manager
Click to expand...
Click to collapse
No worries, just checked your repo, there's a lot of stuff there haha.
dnlgee said:
No worries, just checked your repo, there's a lot of stuff there haha.
Click to expand...
Click to collapse
Yes, trying to do thinks more easy for all people
Thank you. I have been looking for this for a long time
Great work, it worked a charm until I changed to a new rom, went to use it again and it was gone from the downloads in Rom Manager.
Big thanks.
Panic over, It was saved as a download on my SD card, Rom Manager flashed it again from the saved location no problem.
Love it.
danbst said:
Your stuff is gone from Rom Manager it seems mate.
Would I be right in assuming I can put this on my card renamed as update.zip (if I need to?)
Use rom manager to boot into recovery and flash it manually?
Great work BTW, it worked a charm until I changed to a new rom, went to use it again and as I say it was gone.
Big thanks.
Click to expand...
Click to collapse
You don't need to rename the zip file if you're using ROM Manager, but yes you should be able to install this through the manager.
If you can't download it through the ROM Manager report, my link is always online and will be updated when possible.
Sent from my HTC Desire using Tapatalk
Just a confused question;
If we have a rooted device, what's the reason for having to use the recovery menu? Can you not simply overwrite the file?
Thanks
Yea you can, provided you reboot into recovery and mount the system, then pull or push the device back into the system.
Either way you need to boot into recovery as there's no root method that fully allows read/write access for the Desire at the moment.
Psy-Blade said:
Just a confused question;
If we have a rooted device, what's the reason for having to use the recovery menu? Can you not simply overwrite the file?
Thanks
Click to expand...
Click to collapse
It should work like this. Unfortunatelly you can't mount system partition as read/write. That is because system is blocking this in some way.
Sent from my HTC Desire using XDA App
Another quick one:
I used the zip file which people are using in the rom manager. I rebooted into clockwork and selected apply update from zip and selected the file. Appears I broke the system though lol .
Is this not the right way of doing it?
Also how do you type commands in the recovery? :S
dnlgee said:
Try this, mate. [Click!]
Click to expand...
Click to collapse
Link dead ??!! "File does not exist. Make sure you specified correct file name."
Hey guys!
I have a DHD with 4ext recovery,S-OFF and MIUI ROM. So i have a problem. I want to acess recovery trought bootloader. It's supposed to vol.down until appear recovery. With SD-CARD off the phone i can access recovery without any problem, with SD-CARD on the phone this is the message that appears to me (attach).
If i say "No" the only option i have it's to power down. My doubt is, if i say "Yes" i don't mess things up :/
Thank you all. I'm not sure if it is the right place to post. Please move it if it's wrong.
(Sorry for my english)
You have pd98img file on your SD card. Either delete it or move it somewhere elde
marsdta said:
You have pd98img file on your SD card. Either delete it or move it somewhere elde
Click to expand...
Click to collapse
Hey man, that's it!
Thank You so Much!
Best Regards!
(The topic can be closed now )
Yeah, some things are really that simple
I'm wondering why you didn't delete it before? Normally the How-To's say that!
DN41
DN41 said:
Yeah, some things are really that simple
I'm wondering why you didn't delete it before? Normally the How-To's say that!
DN41
Click to expand...
Click to collapse
It was a friend of my brother that made to my DHD root, installed a recovery and put new radio and that stuff... He forgot to remove that file!
No problem! Thanks anyway for come here DN41
No problem sir, it was a pleasure
So tell him that he shouldn't forget to remove the zip
DN41
Sent from my DHD @ ARHD 7.0.0
DN41 said:
No problem sir, it was a pleasure
So tell him that he shouldn't forget to remove the zip
DN41
Sent from my DHD @ ARHD 7.0.0
Click to expand...
Click to collapse
BTW DN41 i left you a PM!
Best Regards!
CLOSED
For one thing, you didn't backup the system.img... aka the most important part of a nandroid.
This is my signature.
13leed1t0ut said:
Like a smart man I made a nandroid backup before trying a new ROM, didn't like it, tried to restore.
"Ooops... something went wrong!
Please check the recovery log!"
Using Amon RA-supersonic-v2.3
Log is attached
Thanks in advance!
Click to expand...
Click to collapse
It looks like it didnt recognize the MD5sum(the code givin to the nandroid package)did you change recoveries or turn off the phone before it was done backing up?
For one thing, you didn't backup the system.img... aka the most important part of a nandroid.
Click to expand...
Click to collapse
Yea thats why i asked about it not finishing the backup.
death-by-soap said:
For one thing, you didn't backup the system.img... aka the most important part of a nandroid.
This is my signature.
Click to expand...
Click to collapse
Im looking in the folder.... Its there.
Is it a bad thing that I renamed it?
EDIT: renamed the nandroid, not system.img
I think it is bad, cause when I did that, it said the same thing
Sent from my PC36100 using xda app-developers app
bennyboy78 said:
I think it is bad, cause when I did that, it said the same thing
Click to expand...
Click to collapse
could you ever fix it?
13leed1t0ut said:
Im looking in the folder.... Its there.
Is it a bad thing that I renamed it?
EDIT: renamed the nandroid, not system.img
Click to expand...
Click to collapse
You can't rename the whole nand,you can add to the end after an underscore.You corrupted the backup.
13leed1t0ut said:
could you ever fix it?
Click to expand...
Click to collapse
No. Above my post is why.
Sent from my PC36100 using xda app-developers app
Diablo67 said:
You can't rename the whole nand,you can add to the end after an underscore.You corrupted the backup.
Click to expand...
Click to collapse
Alright, thanks for the help anyways.
Any reason you killed the first post? Other people may have the same issue and could have read about it in this thread instead of posting a new one. Lots of people are comfortable reading but not posting...
koker93 said:
Any reason you killed the first post? Other people may have the same issue and could have read about it in this thread instead of posting a new one. Lots of people are comfortable reading but not posting...
Click to expand...
Click to collapse
It was due to the nandroid being corrupted.
For those asking, Do not rename a nandroid unless you add an underscore to the end and only add up to 4 characters to the end. Otherwise your recovery can't restore it.
5+0+4+9 = S+O+A+P
Ok so you accidentally tried to Odin or CWM the wrong file to your phone. Well the good news is that if you can get into CWM with access to the sdcard(s) or access ADB we can fix it. If the phone won't power on at all, you can't access cwm with sdcard(s), ADB or Odin you are unfortunately out of luck. You will need to get it repaired by Sprint or send it off for a jtag repair.
Disclaimer: I am not responsible for anything that happens to your phone. You do this at your own risk.
If you don't own the E4GT do not use this guide because if your partitions are not the same as ours you will brick your phone.
If by chance you can get into Odin mode and your computer can see the phone go buy a lottery ticket J/K. All you have to do is download a full tar and Odin it back on. I won't go into details for that as it is well documented. Or you can still use this zip if you prefer.
I have automated the process of the restore. What this zip will do is flash the Agat 0.5.4 source kernel so you have cwm. It will flash the FH13 boot.bin, hidden.img, param.lfs and Sbl.bin. It will wipe Cache and Dalvik also.
This will not flash the modem, wipe data or replace system. So after you use this zip if your modem is also hosed flash a modem zip from CWM. Once you have recovered the phone you can flash whatever you want back on the phone.
Download CWM Odin Restore To FH13: http://d-h.st/3yZ
Copy the zip file to your phone and flash in custom recovery.
If you don't have access to the sdcard(s) but do have access to ADB proceed to the second post.
If you need some direct assistance you can PM me and I will work with you when possible.
You only have ADB access
For this method you will need CWM, ADB, Root and the image files to restore.
If you don't have ADB installed I have attached it to this post. I have also provided a link to the FH13 image files.
If you don't have ADB, extract the ADB directory to the root of C:. So you should see C:\ADB
You need to know where your ADB directory is located. If you used step 1 ADB it is C:\ADB. If you installed it on your own you should know where to find it.
Extract the images.zip into the ADB directory. You should now have the Images folder in the ADB folder.
Boot into CWM and attach your phone to the computer.
Open a command prompt and change directory to the ADB directory cd C:\ADB (or wherever your directory is).
Type adb push Images /tmp and hit enter.
You should see something like 6 files pushed. 0 files skipped.8465 KB/s (19271020 bytes in 2.223s).
Type adb shell and hit enter.
This part is critical. Make sure it is typed exactly or you can/will destroy your phone.
Copy and paste or type the following commands. If you copy and paste make sure you don't copy any leading or trailing spaces. Hit enter after each command.
You can skip any of the following commands if you know you don't need them. For example, if you know you only installed the Sbl.bin then you only need to enter that command. I have provided them all to cover all of the needs. If you are not sure just do them all.
dd if=/tmp/boot.bin of=/dev/block/mmcblk0p0
dd if=/tmp/hidden.img of=/dev/block/mmcblk0p12
dd if=/tmp/param.lfs of=/dev/block/mmcblk0p4
dd if=/tmp/Sbl.bin of=/dev/block/mmcblk0p2
dd if=/tmp/zImage of=/dev/block/mmcblk0p5
dd if=/tmp/zImage of=/dev/block/mmcblk0p6
You should see something like 2560+0 records in, 2560+0 records out, 1310720 bytes (1.3MB) copied, 0.265521 seconds, 4.7MB/s after each command.
Reboot your phone and it should boot up.
If it still doesn't boot something didn't take and we will need to work one on one.
Download the Images.zip: http://d-h.st/8gY
The bootloader restore has been proven to work on one phone so far. Thanks to pjkingphd for testing and confirming that it works.
great share!thanks for the tutorial.
crawrj said:
Please sticky this thread.
Click to expand...
Click to collapse
Hopefully this will be done.
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
Crawrj my man.
Tappin' Typin'
md5 sums might be nice. Don't want bricked phones due to bad downloads.
Sent from my Galaxy Nexus using xda app-developers app
times_infinity said:
md5 sums might be nice. Don't want bricked phones due to bad downloads.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
But then we wouldn't have anyone to test this... would we..
Great tutorial crawrj
Sent from my SPH-D710 using Xparent Blue Tapatalk 2
Very nice. Thank you.
times_infinity said:
md5 sums might be nice. Don't want bricked phones due to bad downloads.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
If the md5 is not right it will say so when you try to restore in cwm. It won't restore if they don't match. But I can throw up md5 for the sbl.
Sent from my SPH-D710 using xda premium
MD5 added. Sticky this please.
I have now automated the restore process in a zip file. You must be able to copy the zip file to the phone for it to work. I have flashed it about a dozen times but I would like to get a few brave testers to try it on your phone for me. Make sure you do a backup first! I have moved the manual commands to post two and revamped the instructions.
+1
Sticky or move to original development.
Sent from my piece of crap Zio until i get my E4GT back from Samsung, using XDA Premium app
Thread stuck. Thank you for helping out the community. :highfive:
jayharper08 said:
Thread stuck. Thank you for helping out the community. :highfive:
Click to expand...
Click to collapse
Thank you sir :highfive:
Sooo... uhm ,,, say I know a certain someone who botched their custom boot logo and has been lazy..... and has the draw failure start up...
This would restore that to stock without any other ramifications except for a kernel swap, correct??
Edit: Guess after a day Ill just assume yes and hope it cant brake anything....
PhAkEer said:
Sooo... uhm ,,, say I know a certain someone who botched their custom boot logo and has been lazy..... and has the draw failure start up...
This would restore that to stock without any other ramifications except for a kernel swap, correct??
Edit: Guess after a day Ill just assume yes and hope it cant brake anything....
Click to expand...
Click to collapse
Yeah this will fix you up. Once you get recovered you can flash whatever you want back on. Since you are an advanced user if you have a particular setup that you want to restore, just pull those files from the tar and place them in the Images folder of the zip.
You never can be too sure.. Lol I just always expect the one time I make an assumption will be regretted.
Good idea btw... And thanks.
And Ive actually been meaning to flash a param.lfs..... I have like 4 OCs it just they are all the way on my backup backup card ...(see my level of sloth ?!?!?!)
PhAkEer said:
You never can be too sure.. Lol I just always expect the one time I make an assumption will be regretted.
Good idea btw... And thanks.
And Ive actually been meaning to flash a param.lfs..... I have like 4 OCs it just they are all the way on my backup backup card ...(see my level of sloth ?!?!?!)
Click to expand...
Click to collapse
LOL nice. Let me know how it turns out.
crawrj said:
LOL nice. Let me know how it turns out.
Click to expand...
Click to collapse
Good as gold, as expected. I did end up only using the param.lfs but Im sure the rest will work great when I need it =)
Thanks again.... Itd been a long time since I last saw that sweet , sweeet gaudi_bootimage.jpg
Sent from my SPH-D710 using xda premium
I had a backup of stock before root but when i tried to back up to it today it gave me a md5 mismatch so i couldnt back up to it. From what I seen in beaups thread that I need to be on a stock rom and stock kernal for his s-off method to work. Is there a stock rom that I could flash to use the s-off method?
I'd like this answered as well. I think andy's stock rom near the bottom of the page works, but I haven't had a confirmation yet. Also wondering if odex versus deodexed versions matter.
Same boat im in just waiting for somebody to say which one we can use when we are already rooted and unlocked. I dont know how my md5's mismatched on my stock before root backup but I can't go back to it so Im kinda stuck here until we get a answer.
Aggies1288 said:
Same boat im in just waiting for somebody to say which one we can use when we are already rooted and unlocked. I dont know how my md5's mismatched on my stock before root backup but I can't go back to it so Im kinda stuck here until we get a answer.
Click to expand...
Click to collapse
Just heard andy's bonestock works trying it myself to confirm.
EDIT: Downloading the 1.1 download not the newest. Under old downloads. I would think the more stock the better.
cstrife999 said:
Just heard andy's bonestock works trying it myself to confirm.
EDIT: Downloading the 1.1 download not the newest. Under old downloads. I would think the more stock the better.
Click to expand...
Click to collapse
Just tried v1.0a..... No dice.
I'd test 1.1 but for some reason it won't let me copy the zip over to my phone... Keeps saying the device has stopped working or has been disconnected. Tried many different USB ports.... Going to have to bluetooth it which is going to take even more time...
cstrife999 said:
I'd test 1.1 but for some reason it won't let me copy the zip over to my phone... Keeps saying the device has stopped working or has been disconnected. Tried many different USB ports.... Going to have to bluetooth it which is going to take even more time...
Click to expand...
Click to collapse
Im downloading 1.1 now. Ill get back with y'all on how it went.
Aggies1288 said:
Im downloading 1.1 now. Ill get back with y'all on how it went.
Click to expand...
Click to collapse
I found VZW_Stock_Rooted_deodex from Andy
Trying that now..
mcampos7 said:
I found VZW_Stock_Rooted_deodex from Andy
Trying that now..
Click to expand...
Click to collapse
This is what I've been on since launch day. Curious if this will work.
m4rk0358 said:
This is what I've been on since launch day. Curious if this will work.
Click to expand...
Click to collapse
Actually I'm having more problems with this than I did trying it on 1.0a and NOS...
I'm trying to find my nandroid of stock rooted but I think it was on a drive that failed.
Linux boot, next???
mcampos7 said:
Actually I'm having more problems with this than I did trying it on 1.0a and NOS...
I'm trying to find my nandroid of stock rooted but I think it was on a drive that failed.
Linux boot, next???
Click to expand...
Click to collapse
Yea i got made fun of when using that lol...
SUPER MEGA ULTIMATE DISCLAIMER: IIRC = IF I REMEMBER CORRECTLY. I AM NOT RESPONSIBLE IF THIS DOESN'T WORK/SCREWS UP YOUR DEVICE/BRICKS/ETC. YOU ARE WARNED. THIS WORKED FOR ME IN THE PAST WITH MY GALAXY NEXUS BACKUPS USING CWMTOUCH 6.0.3.6 AND 6.0.4.3.
YOU ARE WARNED.
I HAVE NEVER USED TWRP FOR BACKUPS. IT IS A MERE SUGGESTION THAT THIS METHOD WILL WORK WITH SIMILAR RESULTS. I HAVE NEVER BROWSED A BACKUP FOR TWRP. ANY ATTEMPT YOU MAKE USING A TWRP BACKUP IS OF YOUR OWN COGNIZANCE. YOU HAVE BEEN WARNED.
YOU ARE WARNED.
YOU ARE WARNED.
IIRC: If you have an md5 mismatch while trying to restore in a recovery, try this process:
IF YOU HAVE A BACKUP I HIGHLY SUGGEST STORING THE BACKUP FILE ON YOUR DESKTOP JUST IN CASE!!!!
Boot into whatever ROM you're on ATM.
Browse to your ClockworkMod (or TWRP backup must have an accessible folder for it's backups) using a Root file explorer, which I happen to use "Root Explorer" and open the backup file you just made.
Inside of that will be a nandroid.md5.
Delete that file and reboot into recovery, and try restoring again.
SUPER MEGA ULTIMATE DISCLAIMER: IIRC = IF I REMEMBER CORRECTLY. I AM NOT RESPONSIBLE IF THIS DOESN'T WORK/SCREWS UP YOUR DEVICE/BRICKS/ETC. YOU ARE WARNED. THIS WORKED FOR ME IN THE PAST WITH MY GALAXY NEXUS BACKUPS USING CWMTOUCH 6.0.3.6 AND 6.0.4.3.
YOU ARE WARNED.
YOU ARE WARNED.
YOU ARE WARNED.
This method did work for me several times on several backups, but root and S-Off being so new, I cannot attest that it works for the One. YOU ARE WARNED**!!
cstrife999 said:
Yea i got made fun of when using that lol...
Click to expand...
Click to collapse
For using what? Linux? NOS?
mcampos7 said:
For using what? Linux? NOS?
Click to expand...
Click to collapse
The sojo app called my issues dumb lol. It's hard to get frustrated when humor is involved with the errors.
cstrife999 said:
The sojo app called my issues dumb lol. It's hard to get frustrated when humor is involved with the errors.
Click to expand...
Click to collapse
Looks like we may have to flash the boot.img that they are talking about in the s-off thread anybody have a guide for doing that?
I take it nobody tried deleting the nandroid.md5?
rmaccamr said:
I take it nobody tried deleting the nandroid.md5?
Click to expand...
Click to collapse
I just tried looking for where the nandroid file was. I went to my sdcard on root explorer then to clockworkmod and didn't find any of my backups there. Is there another spot that i need to look in to do that?
Aggies1288 said:
I just tried looking for where the nandroid file was. I went to my sdcard on root explorer then to clockworkmod and didn't find any of my backups there. Is there another spot that i need to look in to do that?
Click to expand...
Click to collapse
If using CWM, they will be under the /data/clockworkmod/backup directory, not /sdcard/clockworkmod/backup.
I tried the odex stock rom, but it won't flash... Anybody have this issue?
santod040 said:
If using CWM, they will be under the /data/clockworkmod/backup directory, not /sdcard/clockworkmod/backup.
Click to expand...
Click to collapse
Ok i found it it was under /data/media/clockworkmod/backup but i dont see any files inside of that that are a md5 file im going to look in the data.ext4.tar file and the system.ext4.tar.a. Does any of those ring a bell? i see the boot.img, data.ext4.tar.a, recovery.img, system.ext4.tar.a, and system.ext4.tar.b. Thats all the files inside the backup i made before i rooted.