Related
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.
Hi everyone, for Christmas my screen was crushed by a car .
The screen is completely destroyed (both touch screen & display screen).
However the phone is booting, so I can put it in recovery mod (I rooted the phone and I have clockworkmod).
After many trials, I succeeded in having adb connecting to my phone in blind mode.
I did this:
Code:
adb mount /data
adb pull /data /a_backup_folder
adb mount /system
adb pull /system /another_backup_folder
... and copied back my SD to my computer. I plan to buy another Desire and to revert the instruction by issuing a push for the data & system. This is:
Code:
adb mount /data
adb push /a_backup_folder /data
adb mount /system
adb push /another_backup_folder /system
Will it work ? Or is the system in sync with the flashed firmware ?
Can I selectively push some of the folders (namely applications, and the whole data). I hope to get back my settings, contacts etc...
I'm afraid I cannot do a whole lot more, since I do everything in blind mode.
Any advice on this ?
Thank you !
Just make a nandroid, should be able to restore as long as you don't have a different screen version (AMOLED to SLCD) but not 100% sure.
TheGhost1233 said:
Just make a nandroid, should be able to restore as long as you don't have a different screen version (AMOLED to SLCD) but not 100% sure.
Click to expand...
Click to collapse
Thank you for your suggestion.
Can I do it even if I do not have a screen ? I've tried to launch it but I fear it needs busybox (it says that it cannot find nc) and I think I do not have it (and don't know how to put it without the screen).
What are the supplementary steps that nandroid does ?
This is for CWM 2.5.0.7.
Sorry mist the part that you have to do everything blind, when in recovery press 5 times down on the volume rocker and then 2 times on the OJ let it sit for 10 min, should be done sooner but i don't know how to check if it's finished. After 10 min press once again on the OJ, your phone should reboot and in the Clockwork folder on the SD card should be a backup folder with a folder with the current date and time of the back up.
Unfortunately it did not work.
It did the steps as provided, and indeed the phone rebooted, but there is no clockworkmod folder on the sd card.
Is there any way to do a similar operation with adb ? This would be easier since when I'm in adb shell, I can type from the PC .
Try installing amon ra recovery. You should be able to do it. This is what the amon ra thread says:
Scripts available via adb :
* Nandroid v2.2.1 : enter "nandroid-mobile.sh" to start.
Explenation: http://forum.xda-developers.com/showpost.php?p=3046976&postcount=1
I think that this is what you are looking for
Use the command below to find out what partitions each mtd is for (I don't remember)
cat /process/mtd
Then backup with
cat /dev/mtd/mtdx > /sdcard/mtd.img
(Replacing x with whatever number)
Get all the partitions you need, boot, cache, data and system. Then flash to your new phone from fastboot.
fastboot flash boot mtdx.img
You might want to get hold of a tool called unyaffs and take a look inside the images you make to check its all ok before you bin your old phone or send it back.
mercianary said:
Use the command below to find out what partitions each mtd is for (I don't remember)
cat /process/mtd
Then backup with
cat /dev/mtd/mtdx > /sdcard/mtd.img
(Replacing x with whatever number)
Get all the partitions you need, boot, cache, data and system. Then flash to your new phone from fastboot.
fastboot flash boot mtdx.img
You might want to get hold of a tool called unyaffs and take a look inside the images you make to check its all ok before you bin your old phone or send it back.
Click to expand...
Click to collapse
Ok the first step worked, but unyaffs does not want to open my imgs.
The size are as follow:
Code:
3*145*728 boot.img
3*145*728 boot_ro.img
41*943*040 cache.img
41*943*040 cache_ro.img
655*360 misc.img
655*360 misc_ro.img
4*718*592 recovery.img
4*718*592 recovery_ro.img
262*144*000 system.img
262*144*000 system_ro.img
154*796*032 userdata.img
154*796*032 userdata_ro.img
which seems good (I also made images from the mtdXro). However I should be able to extract userdata and system from my understanding. I tried with unyaffs both on linux and on windows, on both I get a segmentation fault.
Do I have a way to verify that theses images are good ? I do not want to trash the new phone I will buy with a faulty image...
Flash the same rom from recovery on your new phone, then flash the data image from fastboot, if it works the first boot should take a while as it builds the cache. If it doesn't work just clear data and it wont have done any damage to your new phone.
You will have to zip the data image before you fastboot flash it because it's too big for fastboot to receive.
If you have s-off on your old phone I would flash amon-ra recovery from fastboot then use the nandroid script over adb.
As long as you don't try to flash the recovery you backed up I don't think there's any chance of damaging your new phone doing this.
Ok the final solution was to use the new phone (rooted and with clockworkmod) as a reference.
I did the same backup sequence on the two phones, and have been able to restore the backup on the new phone.
Thank you everyone for your help !
Glad you got it sorted...don't drop your phone under a car again.
Sent from my HTC Desire using XDA App
Long story short im a newb, im sorry for creating a new thread but ive exhausted my efforts looking for a solution to the problem im having. When the problem occured i had restored my original cwm backup that i created when first rooting my phone. I then did a factory wipe and reinstalled cwm and flashed my recovery. I went to install cm9 4-4-12 and i got a pop up that firmware update was available i clicked update system now and got sent to cwm recovery. Every time since then i cannot reboot into the android os, pulling battery. It doesnt matter what i do, ive tried to use a flash recovery zip i found in another thread to exit boot loop. Ive also tried restoring my original back ups and my recent back ups. I have the android sdk installed but having trouble getting adb to work not sure if i should go about trying to fix the recovery or trying to restore phone to its original state either way i think i need to get adb working before i can do either one. Any help is appreciated and im sorry if im wasting your time.
Did you try wipe cache, wipe dalvik cache, factory reset before flashing CM9?
Yes. The order i took was Wipe data/factory reset> Wipe cache partition> wipe dalvic cache> installed cm9 zip> installed gaps zip. still nothing got adb to work not doing much with it i know it has root access and when i got the state of the device it came up as unknown although im pretty sure im in recovery mode.
ok a few question and maybe a step by step to help you since i had a same promblem with a bad flash of CM9
1A. Can you boot into Recovery ? if not i can help you reflash your phone with the Kdz files took me forever to get it to work but i finilly found all the files needed.
1B. if it does boot into recovery run adb devices ... does it show the phone in recovery mode ? in the list.
If so then you can Download the following 6 files Dropbox Down link its not mine but was posted in another Nitro Recovery topic i will give credits once i re go threw the topic to see the poster
- recovery.img
- system.img
- baseband.img
- boot.img
- firmware.img
- pushall.bat
in your CWM recovery go to mounts or it may be under advanced and turn on usb mass storage and as long as all of those files are in your adb folder you can run the pushall.bat and it will place them on your sdcard.
After that turn off usb mass storage and run adb devices again to make sure you phone is still showing up. If so run these commands
Adb shell
****** notice the SU command isnt used here**** cant get super user in recovery but it will still let you run the commands and i can confirm it does work
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p8
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
dd if=/sdcard/firmware.img of=/dev/block/mmcblk0p1
dd if=/sdcard/system.img of=/dev/block/mmcblk0p27
dd if=/sdcard/baseband.img of=/dev/block/mmcblk0p14
You won't be able to issue a reboot command, so just hold power down on your phone til it's off and hold the volume down button so that it comes back up in factory data reset mode. You will want to pull your sdcard at this time if you don't want your data erased.
Hit power twice and your phone should go through its reset process and (hopefully!) come back up in a working (and rooted) AT&T "stock" rom
if not then try to follow this for the CM9 Adb Drivers Wiki for CM adb drivers i know its a little work but it dose the trick then go back up to the previous step and try that to get to stock rooted
i dont think i left anything out but i can help with anything else i know if that doesnt get you back up and running.
Credits to ???? for the drop box link with the godly files for our nitro
and to Malnilion for his guide on unbricking the nitro
edit: re-ran superoneclick for run and it worked! I should be good from here
Got everything to work. Wait spoke to soon tried to reinstall firmware update again got the same problem. oh well guess i should done fw update before installing cwm. Thanks for the help i should be able to repete this problem in the case of another brick... which just occured.
So after going through the process of unbricking my phone a second time my phone was rebooted into software update screen. Updating firmware then software and did not have to go through factory reset. Strange...
I pushed all images to my device via adb,but ota update gets an error when trying to install. At least its not bricked. Anyone know of another method?
Sent from my LG-P930 using XDA
lg nitro in recovery loop
toki, I tried your fix, but, it comes up /sdcard/boot.img is not found. any suggestions?
Tokie the dropbox links are not working
reverendyummypants said:
toki, I tried your fix, but, it comes up /sdcard/boot.img is not found. any suggestions?
Click to expand...
Click to collapse
re push the img file back to the sdcard
adb push boot.img /sdcard/ make sure that he boot.img file is in the same folder as your adb and then try the dd command for it it happened to me once
EdwinXVS said:
Tokie the dropbox links are not working
Click to expand...
Click to collapse
im uploading to my own dropbox bare with me ill posyt a live link as soon as it ready guys
cwm recovery loop
_Tokie, retried. still dd command cannot be done. file not found. The files ARE IN the adb folder. Not sure what else to do.
when you type adb push boot.img /sdcard/ what does it say ? i dont see why it will do the rest and not that one
dd: can't open sdcard\boot.img : no such file or directory
i was asking about when you pushed the boot.img to teh sdcard... if yyou want i can look at it threw teamviewer total up to you ... if you deside that pm me then info for it
Just take the SD card out and into your computer (assuming you have a card reader) and copy the files to it manually.
drumist said:
Just take the SD card out and into your computer (assuming you have a card reader) and copy the files to it manually.
Click to expand...
Click to collapse
im going to assume that he is booting into CWM its thats the case with teh usb cable hooked to the computer he can turn on mass storage from the CWM and just tranfer it that way .. if he doesnt have a reader .. i just dont see why its not copying the boot image
I'm sorry. The files are on the sdcard. When it comes time for the dd command, i get that error which i recently posted.
If you're in CWM you have to ensure your sdcard is mounted. I have got caught up on this step as well lol
Thank you to all that helped! XDA is awesome! Everything is back to normal. It also helps to have the right / or \ lol
My HTC One M8 from AT&T got stuck in a boot loop after I unlocked it, put a custom recovery on it, and then tried to put a custom ROM on it.
I tried to put InsertCoin on there and it got stuck in a boot loop for some reason.
I got the SDK kit and tried doing a adb push my NANDroid I did originally (before trying the ROM) and so I have my NANDroid backup.
I just can't push anything to my SDCard because it keeps saying "adb shell ls /mnt/sdcard/" no such file or directory exists
same thing with "adb shell ls /sdcard/" no such file or directory exists.
I have my NANDroid backup (before the soft brick) and, a new ROM (Viper One M8 2.3.0)
so how do I "adb push" a file onto a filesystem that I have no access to?
adb push viperOne.zip /sdcard says "protocol failure"
It's as if I have no rights to push anything.
When I try to "install from .zip" it says "unable to mount SDCard"
Is there anything we can do to push? Is it because i'm not successfully rooted?
technocrat7 said:
My HTC One M8 from AT&T got stuck in a boot loop after I unlocked it, put a custom recovery on it, and then tried to put a custom ROM on it.
I tried to put InsertCoin on there and it got stuck in a boot loop for some reason.
I got the SDK kit and tried doing a adb push my NANDroid I did originally (before trying the ROM) and so I have my NANDroid backup.
I just can't push anything to my SDCard because it keeps saying "adb shell ls /mnt/sdcard/" no such file or directory exists
same thing with "adb shell ls /sdcard/" no such file or directory exists.
I have my NANDroid backup (before the soft brick) and, a new ROM (Viper One M8 2.3.0)
so how do I "adb push" a file onto a filesystem that I have no access to?
adb push viperOne.zip /sdcard says "protocol failure"
It's as if I have no rights to push anything.
When I try to "install from .zip" it says "unable to mount SDCard"
Is there anything we can do to push? Is it because i'm not successfully rooted?
Click to expand...
Click to collapse
The recovery does not require root as root is a thing for the Android system. You could always try doing adb sideload and using the command 'adb sideload viperOne.zip', that will sideload the ROM to your device and flash it. An alternative thing to try would be going into the 'Mount' section of your recovery and checking /system, /data, /cache & /boot and re-attempting it. If all else fails then you could attempt to do 'Format data' from the wiping section (take note these are for TWRP, not so sure about CWM).
Also all you need is the 'platform-tools' folder of the sdk. Lastly I would only recommend doing the 'Format data' option after you've tried everything else. If you don't really care about losing your pictures, music, etc then you don't really need to avoid it.
S1L3nTShaDoWz said:
The recovery does not require root as root is a thing for the Android system. You could always try doing adb sideload and using the command 'adb sideload viperOne.zip', that will sideload the ROM to your device and flash it. An alternative thing to try would be going into the 'Mount' section of your recovery and checking /system, /data, /cache & /boot and re-attempting it. If all else fails then you could attempt to do 'Format data' from the wiping section (take note these are for TWRP, not so sure about CWM).
Also all you need is the 'platform-tools' folder of the sdk. Lastly I would only recommend doing the 'Format data' option after you've tried everything else. If you don't really care about losing your pictures, music, etc then you don't really need to avoid it.
Click to expand...
Click to collapse
When trying ADB Sideload, it would always get to 64% and then fail.
Also if I go to "wipe factory data" through philZ, then what will that do?
This all happened when I put InsertCoin on it.
I don't know much about AT&T device as this is more of an Int'l GSM forum and I don't use recovery other than TWRP.
But ... this is basic things that should work for any device when you don't have an external sdcard. If you have one, just put the ROM.zip on it and install in recovery.
If there is no sdcard, Push the ROM.zip to internal sdcard
Put a ROM.zip in your adb/fastboot folder
Put your device in recovery then check the data is mounted
(TWRP - mount - data checked, other recovery maybe - mount & storage - mount data)
Then adb push it to internal sdcard
command : adb push ROM.zip /data/media/0/
That worked, thank you!
And it should be the same no?
I heard TWRP and PhilZ 6 were pretty much the same. I actually heard better things about PhilZ than TWRP
technocrat7 said:
That worked, thank you!
And it should be the same no?
I heard TWRP and PhilZ 6 were pretty much the same. I actually heard better things about PhilZ than TWRP
Click to expand...
Click to collapse
No comparison ... I prefer to try on my own and decide which is better rather then just swallow what people said.
And I like the simplicity of TWRP ... so it's personal preference, that's all that I can say
That's what I would've said too.
But the way you made it sound in your other post made it sound like TWRP can do more than PhilZ or something
I personally like Philz better, but yeah
technocrat7 said:
But the way you made it sound in your other post made it sound like TWRP can do more than PhilZ or something
Click to expand...
Click to collapse
Not that ... I said that I only use TWRP because the step that I mentioned is correct for TWRP but I'm not so sure for other recovery ... that's why I put the word "maybe" there.
(TWRP - mount - data checked, other recovery maybe - mount & storage - mount data)
Oh I see, and yeah it was pretty much the same. It worked
Hi there,
Last friday I broke my lcd screen, it simply does not turn on anymore. Tomorrow an UPS employe will pick up my device and ship it to OP for repair.
My device: Oneplus 3 running TWRP recovery and rooted LineageOS. Adb is enabled in dev settings.
So now I am trying to create a nandroid backup to easily restore my system and data when I get my phone back since OP will reset it ...
I had this genious idea to boot into recovery and create a backup using adb but I ran into a problem.
I have to unlock my device in order to create the backup :/
adb console:
> D:\Desktop\Fastboot+ADB\Win32>adb backup -f backupbeforerepair --twrp system data boot
> Now unlock your device and confirm the backup operation.
So now I am hoping any of you will come up with another genious idea or a workaround so I can create this damn backup
Thanks alot in advance!
If anyone else would ever find himself in the same situation as me I was able to create the backup by doing the following:
You can use open recovery script in TWRP. See http://wiki.rootzwiki.com/OpenRecoveryScript
If you have the file
/cache/recovery/openrecoveryscript
then TWRP will process it when it starts.
If the file contains
backup BSDO myBackup
then the boot (kernel), system, and data partitions will be backed up in compressed format and named myBackup.
So, on your PC, create the openrecoveryscript file, boot into recovery, use ADB to push the file to /cache/recovery/openrecoveryscript then reboot back into recovery. That should trigger the backup process.
Note, the backup will be written to the default location TWRP for backups.
Click to expand...
Click to collapse