My EVO died. Sprint replaced it with a new one. I am trying to restore my old system. I had done a nand backup, copied it to my PC. I have now copied it back to my sdcard. Rerooted my new EVO (with simple root) and flashed recovery. When I try to restore the nand backup, I get the following from the recovery log:
Restore BCDS-20100809-1819 ?
Press Power to confirm,
any other key to abort.
Restoring : .
nandroid-mobile v2.2.1
Searching for backup directories, matching BCDS-20100809-1819, to delete or restore
or compress
Looking for the latest backup, will display other choices!
Error: no backups found
Error : run 'nandroid-mobile.sh restore' via adb!
Any ideas what I could be doing wrong? I restored the whole /nandroid directory. In recovery, I get a phone with a red triangle with a red exclamation point overlayed. Also at bottom "Build : not set". Saw neither of these on my last EVO recovery. It is supposed to be amon-RA recovery.
Please help.
Figured it out. My serial number changed of course. Had to get a sub-directory under nandroid with the new serial number. Restored fine.
Still don't understand, I get a phone with a red triangle with a red exclamation point overlayed. Also at bottom "Build : not set". Saw neither of these on my last EVO recovery.
Nandroid backs up my phone, however when i try restoring i get a error that ends with .sh. My recovery says build not set.... What should i flash to fix thid
Sent from my PC36100 using XDA App
What recovery are you using?I don't think you can fix it by flashing something. Recovery is above radio level so you might be in for some adb and fastboot commands. Get your man pants on bcuz you are going on a wild ride..... Haha sorry I am bored.
But seriously what recovery are you using?
Dk
U should probably try flashing the lastest version of the recovery you're currently using... your backups should be unaffected by this, and make sure u have more than 40% battery when trying to restore a nandroid thru Among RA, it likes to give an error "run adb command" or sumtin like that, when the battery is low
xhazyx said:
U should probably try flashing the lastest version of the recovery you're currently using... your backups should be unaffected by this, and make sure u have more than 40% battery when trying to restore a nandroid thru Among RA, it likes to give an error "run adb command" or sumtin like that, when the battery is low
Click to expand...
Click to collapse
And post the full error message.
Have you renamed your recovery image? If you have, make sure there are no spaces in the name. You need to have under_scores
Sent from my PC36100 using XDA App
Thread moved to Q&A.
Ok guys, when i go into recovery it says BUILD: not set
I can flash and wipe with no problem, its only the nandroid restore that breaks.
On top of the recovery screen it says Android System Recovery. There is green writing..
If i goto nandroid then restore i get this error
Error : run 'nandroid-mobile.sh restore' via adb!
ok well i updated to the newest recovery.
How can i format my SD card and make sure its formatted correctly?
Ok, well i connected my phone via usb and pulled up disk drive.
I formatted my SD card using fat32 via windows explorer.
I backed up a rom I was on, tried restoring, and still getting the same error lol
I tried formatting my EXT filesystem of the sd card via recovery
i get a error
Error : Run 'wipe ext' via adb!
here is a log:
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\HHK>cd ..
C:\Users>cd ..
C:\>cd android
C:\android>adb devices
List of devices attached
HT05THL06921 recovery
C:\android>adb shell
/ # su
su
/sbin/sh: su: not found
/ # nandroid-mobile.sh restore
nandroid-mobile.sh restore
nandroid-mobile v2.2.1
Using G1 keyboard, enter a directory name substring and then <CR>
to find matches or just <CR> to accept default:
Using string to search for matching backup directories
error: unable to mount /sdcard, aborting
/ #
google is your friend. perhaps you should have tried running the nandroid-mobile.sh before doing all that wiping.
http://lmgtfy.com/?q=Error+:+run+'nandroid-mobile.sh+restore'+via+adb!
your last post indicates why you may not have run the .sh...
try using: sudo (not su) ... same command long form/short form kinda thing
Im not quite following you. The only wipes that work for me are data / dalvik / cache.
The wiping of the EXT file system errored out the same way?
What im not understanding is its saying unable to mount SD card.
When im in AMON while the usb is plugged in, if i hit usb ms toggle, my computer pops up with a new drive... i can go into it and view my files?
Why is it erroring out on mounting is the question maybe thats why this is all erroring out
OK the problem has been fixed.
I copied my sd contents to my computer.
booted into recovery and partioned the Sd card
then i created the EXT filesystem
then i did a ext repair
then i converted the ext2 to ext3
Bam im working now
sfld said:
Ok guys, when i go into recovery it says BUILD: not set
I can flash and wipe with no problem, its only the nandroid restore that breaks.
On top of the recovery screen it says Android System Recovery. There is green writing..
If i goto nandroid then restore i get this error
Error : run 'nandroid-mobile.sh restore' via adb!
Click to expand...
Click to collapse
you may have already gotten this, but as your using RA recovery you'll get that error if your battery is below i believe 30%....
Low battery. Try charging your battery first. Hope that helps.
Need some advice else will return phone to service center if unable to DIY to fix.
Have a D855 here. Phone is stock, not rooted. During file transfer, it frozen and rebooted into a white screen asking for "Enter pin/password to decrypt storage". Don't recall setting a pin thus have no clue what to input. Phone started making clicking sound after 10 seconds.
Did a VolDown+Power to entry Factory Reset but return with "e:failed to mount /cache (unknown error 150)"
Able to hold VolDown and enter Download Mode but as I have a Mac here, not sure which tool to execute. Can I recover with *.kdz?
Same error here:
E: failed to mount sdcard / Unknown error 150
when I try to find a .zip/.tot in recovery menu. I am ioroot'ed and am just trying to get a deodexed rom. I have Jasmine v2 and Stock. Both are on sdcard and internal card.
I am not sure how else to flash these ROMS another way, ie tethered. I was playing with LGFlash Tool but did not know what .dll file I needed to put first before the "S/W" which I would have guessed to be the .tot(Jasmine 2 or Stock). I just didnt touch it. I'm pretty sure I'll figure that in time but the error 150 is a big ?
I did boot into recovery with ROM Toolbox, but this happened before I unrooted and rerooted and had that same prob. Now I am on a mission..
*wanted to add mine: Verizon VS985-10B
Thanks
Rich
kdz test mode in flashtool cse, if you enter dowload
I am not sure what that means. Kind of a newbe with LGFlashTool, and rooting LG,
What are: kdz & cse? I looked everywhere when I open LGFlashTool.
I have a 64gig(58 actually) sdcard. Thinking it might be that? The card read/writes fines on G3 and pc. I can't see how it is formatted in properties. should it be fat32?
Oh man!.. I just saw another app called "LG Flash Tool" , not "LGFlashTool"..lol.. NOW those letters make sense...whew...
Will see if that works then figure out the Unknown error 150
Thanks
Hi all,
I had been using CyanogenMod 13.x on my Nexus 5x and was interested in trying out Copperhead OS 14.x. Before I embarked on this journey, I did a backup using my usual method:
1. Reboot into TWRP
2. Use
Code:
adb pull /dev/block/mmcblk0 backup.img
to copy the disk to my hard drive
I proceeded to install Copperhead OS from its factory image files. I decided it wasn't for me, and I attempted the following to restore my backup:
1. Reboot into TWRP
2. Use
Code:
adb push backup.img /dev/black/mmcblk0
This brought me to the "enter your passcode to decrypt the disk" prompt. I entered my passcode, and it failed with the following message:
The password you entered is correct, but unfortunately your data is corrupt
Click to expand...
Click to collapse
So I assumed that something went wrong with the backup, and I decided to use the same restoration method using a different, known-good backup.img file. I know that this older backup.img file is good because I used it 100% successfully just 3 weeks ago. Unfortunately, this backup is also now failing with the same message.
The thing I don't understand is what could have changed that is now preventing my older backup from working on the same phone? My understanding of /dev/block/mmcblk0 is that writing to it should have cleared anything that may have changed while I had Copperhead OS installed.
Any advice would be most helpful. Thanks in advance!
In an attempt to unroot my OP3 I managed to (almost?) brick it. Fastboot still works so I could flash back TWRP which I already had replaced by the stock recovery. Also I have a backup available on the phone which I hoped to be able to restore. And here is where my problem comes in: I cannot choose any partition to restore because there are none and hence the restore fails with "No partitions selected for restore.".
What can I do now? Originally I was trying to sideload the current Oxygen OS using the stock recovery but that didn't work. Any ideas?
simu_lacrum said:
In an attempt to unroot my OP3 I managed to (almost?) brick it. Fastboot still works so I could flash back TWRP which I already had replaced by the stock recovery. Also I have a backup available on the phone which I hoped to be able to restore. And here is where my problem comes in: I cannot choose any partition to restore because there are none and hence the restore fails with "No partitions selected for restore.".
What can I do now? Originally I was trying to sideload the current Oxygen OS using the stock recovery but that didn't work. Any ideas?
Click to expand...
Click to collapse
Your not bricked at all. Just stuck with a phone without OS I think? Why does ADB sideload not work? Do you get the "cannot read" error? Use adb push file directory then manually flash it with twrp. Make sure you are in the latest one from Bluspark!
Yes, I'm stuck with a phone without OS. I did get the "cannot read" error but I don't know why because all the necessary files were in the very same directory from where I issued the adb commands. Where do i find or define an adb push file directory? Currently I habe TWRP 3.0.3-0. installed. Will that be sufficient?
Please keep in mind that I've also lost my partition information. adb sideload alfeady didn't work before that because of the "cannot read" error. Still I don't know what's the reason for that error.
Here you will find everything you need to recover your phone:
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700