When trying to perform a nand restore I get the following message
Error : run 'nandroid-mobile.sh restore' via adb!
What does it mean? I've successfully run a few backups today and it's only just started doing this.
Do I input that command into terminal emulator?
Bennji said:
When trying to perform a nand restore I get the following message
Error : run 'nandroid-mobile.sh restore' via adb!
What does it mean? I've successfully run a few backups today and it's only just started doing this.
Do I input that command into terminal emulator?
Click to expand...
Click to collapse
You're most likely running ThunderG-v1.1.0 custom recovery and you have an ext4 partition on your SD card. An update to ThunderG-v1.2 should fix your issue.
Related
please help me I got in my phone custom recovery 1.2.1 but when I go to the backup/restore and select nand restore it asks me : Create Nandroid backup? ... and when i confirm it: it says: Performing backup............... and after some minutes: Error : Run "nandroid-mobile.sh" via adb!. help me! and one more thing when i try to connect my phone to pc via adb shell it cannot "find device"
xperiment914 said:
please help me I got in my phone custom recovery 1.2.1 but when I go to the backup/restore and select nand restore it asks me : Create Nandroid backup? ... and when i confirm it: it says: Performing backup............... and after some minutes: Error : Run "nandroid-mobile.sh" via adb!. help me! and one more thing when i try to connect my phone to pc via adb shell it cannot "find device"
Click to expand...
Click to collapse
the problem lies in the recovery itself 1.2.1 has backup prob so try 1.2 or earlier which works smooth for backup or rather clockwork just chk this thread http://forum.xda-developers.com/showthread.php?t=1038338
all files provided in 1 link easy to find just download and off you go
xperiment914 said:
please help me I got in my phone custom recovery 1.2.1 but when I go to the backup/restore and select nand restore it asks me : Create Nandroid backup? ... and when i confirm it: it says: Performing backup............... and after some minutes: Error : Run "nandroid-mobile.sh" via adb!. help me! and one more thing when i try to connect my phone to pc via adb shell it cannot "find device"
Click to expand...
Click to collapse
hi there.
what's happening is that you probably need to "re-wipe" your phone. that happened to me yesterday. The 'recovery menu' doesn't clean things very well on P500, so usually i don't rely on it and prefer to use ADB
So, connect the phone to the PC and follow the usual procedure to manually clean the /system folder. If you don't know exactly how it's done, search for "adb clean" or something like that.
On (very) short terms:
- get Android SDK (browse for it on google)
- boot your phone into recovery mode
- connect usb
- run 'adb start-server' or 'adb devices' (usually the 2nd does the start server automatically)
- run 'adb shell'
- run the command 'rm -rf /system/*
- run 'exit'
You can also clean your dalvik cache. I would strongly advise you, if you use the EXT4 partition, to clean it up too.
Since I use Linux, i'm not very aware of how it's done in Windows, but mainly, I backup the EXT4 partition into a folder in my computer, then i clean it up - i think you can clean it with adb too, by mounting it with 'mount -a' - it requires some linux basic commands and i guess you will find a better tutorial around.
Thank you clockwork mode Works perfectly
Sent from my LG-P500 using XDA App
Where I'm at:
I read, and followed the instructions at Viewsonic Gtablet for Dummies.
I have a version 1.2 Gtab. I installed Clockworkmod v3.0.2.8. I backed up my ROM. I repartitioned to 2048m. I installed from internal SD card the Calking+Clemsen Froyo version 8 (got the message that the install was successful). I went into mounts and storage and mounted everything. I rebooted, and the Gtab went right back into Clockwork Mod, with everything unmounted.
I tried restoring my old version. I got the message that the restore worked. When I rebooted, it booted back into Clockworkmod. I installed Cyanogenmod 7, Vegan-tab, and Beasty's2, with the same result. I can't get out of Clockwork.
I've spent the past 3 hours combing through the forums here, and I can't find a solution. What am i doing wrong?
Thanks for your time.
Revy.
See this thread.
Thanks, I posted in that thread. Looks like the same problem, now I just need to figure out how to wipe the Misc partition. So far, I can't even locate it.
You won't be able to wipe the misc partition using any of the CWM menus.
Put the gTab into recovery mode, connect the USB cable to it and then run that adb command line on your desktop in a CMD window.
Thanks for the help.
I ended up just reflashing. Installed the latest clockwork, put in the Caulken Clemsen Froyo, and everything is working like a charm.
Thanks again.
Ok, somehow i've stuck myself in the same problem again. I'd love to learn how to use my computers command prompt to fix this. I booted into recovery mode (I have no other choice, everything I try boots into recovery mode)
I opened up the command prompt at typed
C:\> adb shell erase_image misc
and I got the message that 'adb' was not a recognized command. I tried to switch directories to where the gTab was located (J but couldnt change directories.
How the frell do I use that command from my PC to a USB connected gTab?
That's happened to me 2 times before, and the only way I know how to get it back to normal is to nvflash.
Revyloution said:
I opened up the command prompt at typed
C:\> adb shell erase_image misc
and I got the message that 'adb' was not a recognized command.
Click to expand...
Click to collapse
You've a) not installed adb or b) the location where adb is installed is not in the PATH. See this thread.
In future, don't select "Reboot Recovery" in CWM. If you want the reboot into recovery mode to work correctly, install CWM-4.0.1.5.
You can also wipe the misc partition using nvflash. First, change to the directory where nvflash and the bootloader.bin file are. Then, find out the partition number for the MISC partition. Most commonly it is 7; but, on some gTabs it is 6.
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --getpartitiontable partition.txt[/B]
Look through partition.txt for MSC. Assuming MSC is partition no. 7, wipe it like this:
Code:
C:\SOME\PATH> [B].\nvflash -r --format_partition 7 --go[/B]
The gTab should automatically reboot if you've used the correct bootloader.bin (1.1 or 1.2). However, I strongly recommend the adb method.
Ah. in that other thread, and here, I didnt see any mention of loading a program called adb. Ill find it, and add it to my new bag of Android tools.
Thanks.
So my rooted view sudden rebooted on its own into a loop and ended up booting into CM recovery by itself. But it recovery I get this message at the bottom
E:unknown misc partition fs_type "ext4"
I've tried recovery, reinstalling roms, even unrooting. Nothing will work. It'll always go back to the recovery screen with that message. Can my view be salvaged? Or is it gone?
jigz23 said:
So my rooted view sudden rebooted on its own into a loop and ended up booting into CM recovery by itself. But it recovery I get this message at the bottom
E:unknown misc partition fs_type "ext4"
I've tried recovery, reinstalling roms, even unrooting. Nothing will work. It'll always go back to the recovery screen with that message. Can my view be salvaged? Or is it gone?
Click to expand...
Click to collapse
I'm having the same issue. Did you ever get it figured out?
jigz23 said:
So my rooted view sudden rebooted on its own into a loop and ended up booting into CM recovery by itself. But it recovery I get this message at the bottom
E:unknown misc partition fs_type "ext4"
I've tried recovery, reinstalling roms, even unrooting. Nothing will work. It'll always go back to the recovery screen with that message. Can my view be salvaged? Or is it gone?
Click to expand...
Click to collapse
Could be a sign of a degrading internal memory, but is is extremely unlikely that a solid state memory device would fail like that.
You could try reformatting the internal sd via your pc while in CWM, and installing your RUU after that, provided you can see the internal drive.
Sent from my HTC Flyer P510e using XDA Premium HD app
Run these adb commands while in CWM when connected to pc , see if it helps :
adb remount
adb shell rm -rf /system/sd/dalvik-cache
adb shell format DATA:
adb shell format SYSTEM:
adb shell format CACHE:
adb shell format MISC:
Warning: THIS WILL ERASE ALL USER DATA. DO AT YOUR OWN RISK.
Then run your RUU and you should be back in working order.
Sent from my HTC Flyer P510e using XDA Premium HD app
mhkabir98 said:
Run these adb commands while in CWM when connected to pc , see if it helps :
adb remount
adb shell rm -rf /system/sd/dalvik-cache
adb shell format DATA:
adb shell format SYSTEM:
adb shell format CACHE:
adb shell format MISC:
Warning: THIS WILL ERASE ALL USER DATA. DO AT YOUR OWN RISK.
Then run your RUU and you should be back in working order.
Sent from my HTC Flyer P510e using XDA Premium HD app
Click to expand...
Click to collapse
This has been a looong time but I figured it was worth a try. I did all these commands and run into trouble once I get to the adb shell format data:. I get an error message saying "/sbin/sh: format: not found"
jigz23 said:
This has been a looong time but I figured it was worth a try. I did all these commands and run into trouble once I get to the adb shell format data:. I get an error message saying "/sbin/sh: format: not found"
Click to expand...
Click to collapse
I get the same thing
Long story short, ended up flashing a bad rom without backing up my current rom due to lack of storage space Just ordered a micro sd card from Amazon. Currently unable to boot phone due to not having a rom. Downloaded Android SDK and have been trying to sideload the .zip in CWM recovery but I get an "adb server is out of date. killing..." followed by "Daemon started successfully..." "device not found" Running Mac OS and I'm stuck on what to do at this point. Help?
I've been using in Terminal:
cd desktop
cd Android (Placed adb into this folder to make it easier to find)
./adb
./adb sideload Synergy.zip
LGeX said:
Long story short, ended up flashing a bad rom without backing up my current rom due to lack of storage space Just ordered a micro sd card from Amazon. Currently unable to boot phone due to not having a rom. Downloaded Android SDK and have been trying to sideload the .zip in CWM recovery but I get an "adb server is out of date. killing..." followed by "Daemon started successfully..." "device not found" Running Mac OS and I'm stuck on what to do at this point. Help?
I've been using in Terminal:
cd desktop
cd Android (Placed adb into this folder to make it easier to find)
./adb
./adb sideload Synergy.zip
Click to expand...
Click to collapse
You might have to do a system restore of the stock image. If you want to do this I can PM you some info.
Need help as well
DarkMenace said:
You might have to do a system restore of the stock image. If you want to do this I can PM you some info.
Click to expand...
Click to collapse
Could I please get some help with this as well. Trying to do a sideload as well, since I formatted the whole system and lost all of the ROMS I would normally install from the system SD.
Hi all,
this is my first message.
I would like to root my Sony Xperia Sola and I'm using Root_with_Restore_by_Bin4ry_v31.
When i launch the command (with runme.bat) "adb backup -f stuff\mysettings.ab com.android.settings" in the smartphone not appears the confirmation.
In the log of "adb logcat" i get this error: "adb unable to launch full backup confirmation" (i obtain a zero lenght file on my pc). Same for the restore comand.
I've already activated debug usb ecc
The command "Adb devices" return that it's all ok.
To root my phone I've to make a backup and then to restore the file "special.ab"
I think that I can make the backup directly in the smartphone with the backup app (without adb.exe) , but Is there any way to restore the special.ab file manually without adb? Or is there a solution to use correctly adb backup/restore with Sola?
marco_tv said:
Hi all,
this is my first message.
I would like to root my Sony Xperia Sola and I'm using Root_with_Restore_by_Bin4ry_v31.
When i launch the command (with runme.bat) "adb backup -f stuff\mysettings.ab com.android.settings" in the smartphone not appears the confirmation.
In the log of "adb logcat" i get this error: "adb unable to launch full backup confirmation" (i obtain a zero lenght file on my pc). Same for the restore comand.
I've already activated debug usb ecc
The command "Adb devices" return that it's all ok.
To root my phone I've to make a backup and then to restore the file "special.ab"
I think that I can make the backup directly in the smartphone with the backup app (without adb.exe) , but Is there any way to restore the special.ab file manually without adb? Or is there a solution to use correctly adb backup/restore with Sola?
Click to expand...
Click to collapse
Flash the .10 firmware first,then Root using Bin4ry's Method,then flash .54 firmware again.done
wow
I spend many hours to solve this problem. I've just download "Root_with_Restore_by_Bin4ry_v9_4" and now it's all ok!!
Before this i used Root_with_Restore_by_Bin4ry_v31.
In the tutorial was indicated to press 1 in the start screen of Binary. Perhaps it was referring to the old version of Bin4ry. The old version (Root_with_Restore_by_Bin4ry_v9_4) have only two choices. The new version (Root_with_Restore_by_Bin4ry_v31) have four choices.
I hope this can help other people with this problem.
I dont why but sometimes when i flash firmware, it gives error