I am trying to restore my S7 using the nvflash method as posted by illdill and I am getting the following error after the boot loader is downloaded successfully:
failed executing command 31 NvError 0x120002
command failure: writedeviceraw failed (bad data)
Any ideas?
Thanks
I believe this is the read only error that people have been talking about before. I was wondering if I formatted all the partitions if this would help to re-write the .img files. Anyone out there with a clue about NVFlash?
Well, hello guys i bought a Motorola Milestone from a friend yesterday.
And I'm that annoying kid that will probably step on your lawn again and again, but i apologize in advance for my stupid questions that will probably come after this.
But i have been at it for about 6-7 hours googling bouncing around to you youtube.
I was up halfway through the night yesterday to find a way to flash my phone with Cyna cyanogenmod.com
And through tutorials wiki.cyanogenmod.com/wiki/Motorola_Droid:_Full_Update_Guide
When i get to step:
9. Once it is selected, hit Start and wait for it to finish flashing the device.
10/28/11 12:18:51 New Log Started For Software Download.
10/28/11 12:18:55 00000de0 Phone.cpp 450 0 ERROR Generic failure when sending command.
10/28/11 12:18:55 00000de0 Phone.cpp 1556 0 ERROR GetPhoneID failed: ERROR.
10/28/11 12:19:01 The FlashLog key is turned off.
10/28/11 12:19:02 Multi upgrade started for 1 phones
10/28/11 12:19:02 [Device ID: 0] Flashing phone.
10/28/11 12:19:02 ERROR: Phone[0000]: Phone is not compatible with multi-interface super-file. - on device ID 0.
10/28/11 12:19:02 ERROR: Flash failure: Phone[0000]: Phone is not compatible with multi-interface super-file. (Error Code: 3b),
Detailed Error Details: Direction of the Error=No Direction, Command Value=0, Code Group Number=No Codegroup - on device ID 0.
10/28/11 12:19:02 [Device ID: 0] Phone[0000]: Phone is not compatible with multi-interface super-file.
10/28/11 12:19:03 Multi upgrade finished.
I get this error through searching someone said it was a bug place the *.sbf file in C:\, My documents i tried that same error.
I tried different versions of RSD lite i tried patching the pst_flash.ini file.
After i got shutdown here i tried to push a recovery image through my computer using recovery.img.
adb shell
adb flash_image bla bla bla
i get the error access denied.
Is there any ****ing way to give my telephone a custom rom or change my default Androd bootloader recovery for rom managers?
After a while i found this, i tho to myself was the bootloader locked the whole ****ing time?
ausdroid.net/2011/06/14/an-update-on-motorolas-locked-boot-loader-situation/
ausdroid.net/2011/04/27/confirmation-motorola-to-unlock-bootloaders-for-future-android-devices
If some kind soul out there could spread some light on my issues i will be in your debt forever.
P.S sorry for all the f*cks D.S
The Droid and Milestone are very similar, but have important differences. The Milestone has a locked bootloader, while the Droid doesn't. When it comes to rooting the Milestone and installing a custom ROM, steer clear of instructions for the Droid. It'll get you nowhere.
http://www.droid-developers.org/wiki/CyanogenMod_4_Milestone_FAQ
http://android.doshaska.net/cm7
One day my battery was empty and then i charged it. it failed many times to startup. i got error about SDcard crashed or something like that. then i shut down it. then it didnt start. no fastboot. no CWM. nothing. but it is going APX mode. and i tried to use nvflash to restore. but error. here is the error.
.................................................. ............
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
command failure: create failed (bad data)
bootloader status: failed to create the partition (code: 10) message: nverror:0x
42000 (0x37042000) flags: 0
Press any key to continue . . .
It stops like this. Can anyone help me please. my DS is not starting up, no boot, no CWM i cant use anything other than nvflash. please help me? is there any other method to restore using APX mode.
First of all, I have no gripes with the toolbox. It is a wonderful and easy to use tool.
I now have another TP that was originally stuck on the HP logo. After trying several things include using the tpdebrick and webosdoctor, I now get stuck on 8% webosdoctor. So, I could finally get to the usb recovery symbol, I decided to try the toolbox. Here are the errors I get on the various menu selections:
Install Android - Failed - Problem w/ ugchange -ay
Reflash A6 - works
Complete Data Reset - Failed - Error: Invalid partition info: end-gap greater than 1 percent of mmc
Resize Android Volumes - Failed - Problem w/ ugchange -ay
Repair Android Volumes - Failed - rc=5: ugchange -ay
I'm guessing it relates back to the 8% issue, and the toobox is n/a for helping this situation. If someone is familiar with the 8% issue and has basic instructions for a remedy, that would be much appreciated.
Edit: I found an " xda 8%" thread regarding typing in some commands. So far, that has not worked, but I'm still trying. It did not work because every command I entered, said it failed or other failures. I did read something about starting off with this command
lvm.static pvcreate /dev/mmcblk0p14
and running the commands again. My battery is low, so I'll advise tomorrow.
golfnut22 said:
First of all, I have no gripes with the toolbox. It is a wonderful and easy to use tool.
I now have another TP that was originally stuck on the HP logo. After trying several things include using the tpdebrick and webosdoctor, I now get stuck on 8% webosdoctor. So, I could finally get to the usb recovery symbol, I decided to try the toolbox. Here are the errors I get on the various menu selections:
Install Android - Failed - Problem w/ ugchange -ay
Reflash A6 - works
Complete Data Reset - Failed - Error: Invalid partition info: end-gap greater than 1 percent of mmc
Resize Android Volumes - Failed - Problem w/ ugchange -ay
Repair Android Volumes - Failed - rc=5: ugchange -ay
I'm guessing it relates back to the 8% issue, and the toobox is n/a for helping this situation. If someone is familiar with the 8% issue and has basic instructions for a remedy, that would be much appreciated.
Edit: I found an " xda 8%" thread regarding typing in some commands. So far, that has not worked, but I'm still trying. It did not work because every command I entered, said it failed or other failures. I did read something about starting off with this command
lvm.static pvcreate /dev/mmcblk0p14
and running the commands again. My battery is low, so I'll advise tomorrow.
Click to expand...
Click to collapse
Well, that did not work either. I have posted my error messages in case anyone can recognize what the problem is and what I may do to correct.
C:\Program Files\Palm, Inc>novacom open TTY://
[email protected]:/# lvm.static pvcreate
/dev/mmcblk0p14
lvm.static pvcreate /dev/mmcblk0p14
/dev/mmcblk0p14: lseek 31228690432 failed: Invalid
argument
/dev/mmcblk0p14: lseek 31228690432 failed: Invalid
argument
WARNING: Volume group store is not consistent
Can't initialize physical volume "/dev/mmcblk0p14" of
volume group "store" wit
hout -ff
[email protected]:/#
[email protected]:/# lvm.static vgscan --
ignorelockingfailure
lvm.static vgscan --ignorelockingfailure
Reading all physical volumes. This may take a
while...
/dev/mmcblk0p14: lseek 31228690432 failed: Invalid
argument
/dev/mmcblk0p14: lseek 31228690432 failed: Invalid
argument
Volume group "store" inconsistent
/dev/mmcblk0p14: lseek 31228690432 failed: Invalid
argument
WARNING: Inconsistent metadata found for VG store -
updating to use version 9
/dev/mmcblk0p14: lseek 31228690432 failed: Invalid
argument
Automatic metadata correction failed
[email protected]:/#
Thanks
Why not just start TPtoolbox, then start your Touchpad, (fully charged), with power+volume up, (to get the USB symbol), and then connect to your pc.
There is no WebOS in this.
1 Android Install – 2016
A) Have novacom installed
To load TPToolbox, you will need novacom to be installed on your PC.
You can download novacom drivers from: http://downloads.codefi.re/jcsullins/webos/novacom
Or, you can download and run a java-based "universal installer" from http://123haynes.github.io/universal-novacom-installer
B) Put the Touchpad into webOS recovery mode and connect via USB cable to PC
NOTE: Even if webOS is removed, webOS recovery will still exist as it's built into the bootloader.
If you have moboot already installed, just select "webOS recovery" there.
B)
Or, power the Touchpad off via webOS, then with the Touchpad is off, hold VolumeUp (closest to Power) and Power until you see the USB symbol.
Or, hold Power+Home until the screen changes (about 10 secs) and then start holding the VolumeUp button until you see the big USB symbol.
C) Run the script provided with TPToolbox
Extract the contents of the TPToolbox zip file from above.
Navigate to the tptoolbox_v42 directory that was extracted from the zip.
On Windows, run the batch file named tptb_v42_win.bat
C) Copy three files (ROM, Gapps and Recovery) when and where TPToolbox asks and then select "yes" when asked to confirm the install details.
https://www.androidfilehost.com/?w=files&flid=9776
Carey4782 said:
Why not just start TPtoolbox, then start your Touchpad, (fully charged), with power+volume up, (to get the USB symbol), and then connect to your pc.
There is no WebOS in this.
1 Android Install – 2016
A) Have novacom installed
To load TPToolbox, you will need novacom to be installed on your PC.
You can download novacom drivers from: http://downloads.codefi.re/jcsullins/webos/novacom
Or, you can download and run a java-based "universal installer" from http://123haynes.github.io/universal-novacom-installer
B) Put the Touchpad into webOS recovery mode and connect via USB cable to PC
NOTE: Even if webOS is removed, webOS recovery will still exist as it's built into the bootloader.
If you have moboot already installed, just select "webOS recovery" there.
B)
Or, power the Touchpad off via webOS, then with the Touchpad is off, hold VolumeUp (closest to Power) and Power until you see the USB symbol.
Or, hold Power+Home until the screen changes (about 10 secs) and then start holding the VolumeUp button until you see the big USB symbol.
C) Run the script provided with TPToolbox
Extract the contents of the TPToolbox zip file from above.
Navigate to the tptoolbox_v42 directory that was extracted from the zip.
On Windows, run the batch file named tptb_v42_win.bat
C) Copy three files (ROM, Gapps and Recovery) when and where TPToolbox asks and then select "yes" when asked to confirm the install details.
https://www.androidfilehost.com/?w=files&flid=9776
Click to expand...
Click to collapse
Thanks for the response, but it would not work. I had already tried that. It indicated "Failed" on every command except the A6 one. However, I do have some good news. I found another thread that had a different set of 8% stuck commands that allowed me to get to 12% on webos. While researching methods, I do remember seeing more commands when you get stuck at 12%, but I decided to try the TPToolbox again. Toolbox would not allow me to do a complete data reset for some reason, however, it would allow me to install android, which I did and it now has LP on it. I don't think I have full use of the storage. According to the model number, it looks like it should be a 32gb. But when I ran the 32gb commands in novaterm, it said there was not enough space so I change to the 16gb and it took it. After running installing LP, the settings shows I have 11gb available which seems low, but may be ok if in fact it is a 16gb. Anyway, it is working now.
SO, i have a 1st gen Moto X, the 2013 model. Verizon if that matters.
I havent used it in a while, and it was working when i replaced it. I decided to tinker with it a bit a few months ago, and was trying an unlock method i found online, and appear to have bricked it in the process. I figured, no big deal, and tossed it in a cabinet and figured i'd come back to it later. Well now is later. I'd like to get the thing working so my daughter might be able to play with it.
It wont power on, if you connect it to power, either USB or a wall plug, it does nothing, no charging indicator, nothing. I cant power it on, cant fastboot, cant get to recovery, nothing.
In my attempts to restore it, i've got the moto drivers and whatnot installed, and my Windows laptop will recognise it and add it to device manager, as "Qualcomm HS-USB QDLoader 9008 (COMx)". Which makes be believe there is hope.
I tried the procedure here: https://forum.xda-developers.com/moto-x/general/how-to-resurrecting-bricked-moto-x-t2629057, with no success, i get an error while it's trying to get an handshake from the device.
Code:
C:\Users\war\Desktop\MotoX Recovery\blankflash\blankflash>qflash -com7 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloader_singleimage.bin -v -o
Motorola qflash Utility version 1.3
COMPORT :COM7
RAMLOADER :MPRG8960.hex
type is 0x21
7 mbn file name MSM8960_bootloader_singleimage.bin type 33
verbose mode on
Motorola qflash dll version 1.6
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
EOF_REC
Sleeping for 3s
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
Still no data, giving up!
sdl_hello() - Failed to receive ACK
sdl_hello() - Invalid response: 7e030003331b7e
sdl_hello() - This is a NAK response from ROM code, which means the device has been reset back to blank flash mode. Usually this is caused by power supply issues. Please try again with battery eliminator if it persists
I've had no luck finding a way around that.
If i hold the power button for 10 seconds, while plugged into my PC's usb port, the green indicator light behind the speaker lights up for a second, and then goes out. Same deal if I try to do power+vol-up or vol-down.
Any suggestion that might help me move this along? If i can get it to fastboot, or a recovery image, I think I can get it from there.
Thanks!
That's obsolete, and won't work for your lastest bootloader. See next thread. And don't flash Moto at random next time)
Thanks for the response. I'll give that thread a look!