Hi Everyone,
At the moment, I cannot get my LG G2X to boot into Cyanogen Mod. I cannot get it to boot into recovery mode. I cannot get it to do anything but sit at the second LG logo. This is a problem.
If I allow it to boot with no special button-pressing, it will get to the second LG logo, and stall there until the battery runs out. If I hold the VOLUME DOWN and POWER buttons, it will get as far as the first (white) LG logo and stall there (holding VOLUME DOWN and POWER for a full 60 seconds).
History:
A few weeks ago, I had flashed my G2X and installed CyanogenMod 7 (specifically 7.2.0) from here: http://download.cyanogenmod.com/?type=stable&device=p999. I accomplished this through the excellent One-Click NvFlasher ClockWorkMod provided by TGA_Gunnman (found here: http://forum.xda-developers.com/showthread.php?t=1056847). Once in a while, I would have to clear the caches after a reboot, but that was my biggest problem, and one I was prepared to live with. Until now.
Things I've tried:
Most fixes start with reflashing CWM. I did that, using the aforementioned One-Click NvFlasher ClockWorkMod tool. It stalls as follows:
Code:
===============================================================
===============================================================
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
External SD Support by Koushik Dutta
Version 5.0.2.0
===============================================================
===============================================================
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c20824360c4d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: CWM-5020.img
- 65536/3563520 bytes sent
-------------------------------------------------------------------------------------
...and won't do anything else.
So, for whatever reasons, it will not send CWM-5020.img. To check, I tried nvflash.exe directly. Same general result. I tried with a different file (recovery-clockwork-5.0.2.0-p999.img), same result. I also tried the advice here: http://forum.xda-developers.com/showthread.php?t=1590523&highlight=bricked+help and tried to wipe out my partitions. While that tool runs successfully, it does not change the results with One-Click NvFlasher ClockWorkMod
Summary:
Can't boot. Can't boot into recovery. Can't flash the ROM.
Any ideas? Anyone?
Thanks!
I forgot to add: when I unplug from the one-click updater, I get the following error message:
Code:
sending file: CWM-5020.img
- 65536/3563520 bytes sentdata send failed NvError 0x30012
command failure: partition download failed
===============================================================
===============================================================
*****Once nvflash has completed successfully then hit any key to close.*****
****If any step failed then repeat the process****
For when my partitions are messed up
http://forum.xda-developers.com/showthread.php?p=17258229
Sent from my LG-P999 using Tapatalk 2
djvoleur said:
For when my partitions are messed up
http://forum.xda-developers.com/showthread.php?p=17258229
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, djvoleur, but when I try that, I get this:
Code:
.\nvflash.exe
--bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --setbct --odm
data 0xC8000 --configfile android_fastboot_emmc_full.cfg --create --bl fastboot.
bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c20824360c4d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
\ 888548/888548 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: MBR
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: EB1
creating partition: LNX
creating partition: EB2
creating partition: DRM
creating partition: EB3
creating partition: UDA
creating partition: EB4
creating partition: UDB
failed executing command 12 NvError 0x120002
command failure: create failed (bad data)
bootloader status: fatal failure to read / write to mass storage (code: 9) messa
ge: nverror:0x42008 (0x19042008) flags: 0
So it seems that this doesn't help. I scanned through the thread and didn't see anything that seemed like it might address this issue.
It may be driver related. Reinstall drivers then follow the instructions to resurrect your phone.
Core Memory said:
It may be driver related. Reinstall drivers then follow the instructions to resurrect your phone.
Click to expand...
Click to collapse
Would you recommend reinstalling both the LG USB drivers and the ATX drivers for nVidia? (I'm probably going to do both anyway.)
I've forced a reinstall of the NVIDIA USB Boot-recovery driver, using the same files included in the one-click recovery tool. After that, I attempted to run the tool and had the same failure listed above (command failure: partition download failed). For laughs, I tried djvoleur's solution as well, and got the same error again. So it doesn't seem to be a driver issue.
When you do the NVFlash recovery, did you take out the battery, hold the up and down volume buttons in, while holding the buttons in plug in the usb cable, while holding the buttons in run the recovery until it is completed.
Just for ****s, try flashing twrp. I also have another idea, but I can't get it set-up tonight.
Sent from my LG-P999 using xda premium
Core Memory said:
When you do the NVFlash recovery, did you take out the battery, hold the up and down volume buttons in, while holding the buttons in plug in the usb cable, while holding the buttons in run the recovery until it is completed.
Click to expand...
Click to collapse
Yes. The battery was out the whole time. Held the buttons down, plugged in the USB cable, ran recovery, recovery stalls at 65536 bytes. Held it for about five minutes, just to make sure.
Волк said:
Just for ****s, try flashing twrp. I also have another idea, but I can't get it set-up tonight.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Same result as each of the others: stalls at 65536 bytes sent. I don't think it's an issue with any of the actual recovery mods, at this point. I think it's something wrong with getting data onto my phone, perhaps?
How about trying to update the phone with one of the KDZ updates? Use Emergency mode. There's an offline updater which uses an http server to fool the LG updater into not accessing the LG update website then doing the update. It runs with a VB script which does everything. I once used that with the V21Y_00.kdz file when my phone wouldn't restore.
http://forum.xda-developers.com/showthread.php?t=1601918
http://forum.xda-developers.com/showpost.php?p=22189294&postcount=30
Core Memory said:
How about trying to update the phone with one of the KDZ updates? Use Emergency mode. There's an offline updater which uses an http server to fool the LG updater into not accessing the LG update website then doing the update. It runs with a VB script which does everything. I once used that with the V21Y_00.kdz file when my phone wouldn't restore.
http://forum.xda-developers.com/showthread.php?t=1601918
http://forum.xda-developers.com/showpost.php?p=22189294&postcount=30
Click to expand...
Click to collapse
Tried this. First tried the second link (the all in one with the offline web server). That didn't work because the zipfile with the webserver and other software had a virus which specifically infected the web server.
Followed the directions in the first post, then. These seem to presume that you can get to USB debugging mode (which I can't, because the phone won't boot). Got as far as Step 3 in that post. When I click on "Upgrade Start" I should get a pop-up for "Select Country & Language". I do not. Instead, it starts the LG Mobile Support Tool directly. (I should mention at this point that I'm on WIndows 7, if it matters). The updater checks the connection with the phone, and finds an acceptable connection. Since it was supposed to go into the Updater anyway, I hit "Start Updating". After a while, this fails with some sort of connection problem with the phone. I've tried re-running the LG Updater under several conditions (in Upgrade mode, not in Upgrade mode, etc.). No luck.
Doesn't seem like this is a solution I can get to work. Should I try something else?
The virus warning is false. Disconnect from the internet and/or turn off your wireless connection then run it. Also, if it stalls, let it wait.
If it doesn't continue within 10 minutes, try it again.
---------- Post added at 11:51 AM ---------- Previous post was at 11:46 AM ----------
Also, I made sure that all of the applications in the substitute web-server update package were allowed to run as administrator before I ran the script. If that doesn't work, try running the apps individually without the script in the order they're required to be initiated which is in the instructions that come with that package.
Core Memory said:
The virus warning is false. Disconnect from the internet and/or turn off your wireless connection then run it. Also, if it stalls, let it wait.
If it doesn't continue within 10 minutes, try it again.
---------- Post added at 11:51 AM ---------- Previous post was at 11:46 AM ----------
Also, I made sure that all of the applications in the substitute web-server update package were allowed to run as administrator before I ran the script. If that doesn't work, try running the apps individually without the script in the order they're required to be initiated which is in the instructions that come with that package.
Click to expand...
Click to collapse
I'm having exactly the same problem as that person right now. Using the offline update, I got up to "Normal MTK Upgrade start" but then the program crashed right afterwards. It also doesn't help that the phone keeps on rebooting. For the online update, I can get up to 32% before the phone reboots and I have to restart the update process.
mbamg said:
I'm having exactly the same problem as that person right now. Using the offline update, I got up to "Normal MTK Upgrade start" but then the program crashed right afterwards. It also doesn't help that the phone keeps on rebooting. For the online update, I can get up to 32% before the phone reboots and I have to restart the update process.
Click to expand...
Click to collapse
If it got to 32%, it has installed the baseband, that gets installed first then the Android. Try doing a restore/recovery of just Android that's compatible with the baseband.
Have you tried running the flash with the battery in? I know all the instructions say take the battery out, but im having similar issues with my phone, and once the phone is recognized in Device manager in APX mode, insert the battery, then run the flash. That seemed to work for me.
Core Memory said:
How about trying to update the phone with one of the KDZ updates? Use Emergency mode. There's an offline updater which uses an http server to fool the LG updater into not accessing the LG update website then doing the update. It runs with a VB script which does everything. I once used that with the V21Y_00.kdz file when my phone wouldn't restore.
http://forum.xda-developers.com/showthread.php?t=1601918
http://forum.xda-developers.com/showpost.php?p=22189294&postcount=30
Click to expand...
Click to collapse
Nothing will work in this Case i try all most everything. I thnk 99% Partition or Flash Chip is Damaged
See Reports:
While try with KDZ File
Trying to Flash Recovery
Code:
===============================================================
===============================================================
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
External SD Support by Koushik Dutta
Version 5.0.2.0
===============================================================
===============================================================
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c208240ff9497
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: CWM-5020.img
- 65536/3563520 bytes sent
Recovery Stock
Code:
===============================================================
===============================================================
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
External SD Support by Koushik Dutta
Version 5.0.2.0
===============================================================
===============================================================
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c208240ff9497
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: CWM-5020.img
- 65536/3563520 bytes sent
Phone Information
Code:
Nvflash started
rcm version 0X20001
System Information:
[COLOR="Red"] [B]chip name: unknown[/B][/COLOR]
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c208240ff9497
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
Rad Flash
Code:
[R&D Test Tools Log File]
00:54:52 : Start fn_StartUpgrade
00:54:52 : Extract kdz file
00:55:01 : kdz decrypt Success
00:55:05 : Extract file Success.
00:55:05 : LGMobileDL Load.
00:55:05 : Port = -1
00:55:05 : Connection check start.
00:55:05 : Port(or Device) Not Found!
00:55:07 : Finish All test
So to Flash with KDZ ect u need phone on Recovery mode and phone will not steep into recovery mode with vol - + Power
All we have is boot Recovery mode and phone hang on SW Upgrade Please Wait
I Try to Format partition manually via NVFlash but same thing its hang
Best Regards from me i am giving up after 2 days working on it, For me its simply Hardware Problem
In my experience when that happened to me.... It was my firewall/virus scanner. Try disabling those before attempting another flash.
Related
Hey guys,
I was tired and on accidentally put the most recent clockwork recovery onto my G-tab when i was reinstalling the Vegantab 5.1 Rom.
After the install it rebooted into a black screen that said "Magic Number Mismatch:" in red.
I have used NVflash before and I went ahead and reinstalled clockwork v08 Bekit.
I got this message:
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>nvflash --bl boot
loader.bin --download 9 clockwork.img
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x171440424380b1d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: nand
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 928945/928945 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: clockwork.img
| 3862528/3862528 bytes sent
clockwork.img sent successfully
Even after this the device still gives me the "Magic Number Mismatch:" message.
I read the other threads and none of those solutions worked, nor did most of them apply to me since I can't even boot into clockwork.
any help would be appreciated
You will need to flash the "recovery partition" using nvflash.
Sent from my VEGAn-TAB-v1.0.0B5.1 using Tapatalk
Thanks man! That did the trick.
From there i was able to reflash the older version of clockwork and my ROM.
Hi
I have an Asus TF101 B60 Transformer and have been pretty happy with it until...ICS! I know there are a multitude of solutions out there on unbricking the unit, but I've tried a number of them and have run into one problem or another trying to apply them. I will outline my current issues and maybe someone can point me to some other options.
Here's the initial problem and steps taken so far:
1. Transformer did it's automatic (prompted) update to ICS
2. Shortly after I started experiencing frequent freezes
3. Next was no response at all...bricked
4. I tried a number of fixes with nvflash and finally one of the sites provided a number of downloads to use nvflash to restore the system (XDA File Server)
5. All was fine and dandy until last week when another "auto" update (yes, I did confirm to do the update) and now I'm bricked again
6. Using the set of files that intially worked I now get to the "Waiting for bootloader to initialize" message and that's as far as it gets.
This initally worked - NVFLASH_ICS_9.2.1.21_US_NOROOT.7z (from XDA File Server)
Last ICS update bricked it again...tried to nvflash the rom again.
When that failed I tried this one - NVFLASH_ICS_9.2.1.24_US_NOROOT.7z (also from XDA File Server)
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x038062404420f197
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 2
device config fuse: 0
sdram config strap: 2
sending file: transformer.bct
- 4080/4080 bytes sent
transformer.bct sent successfully
odm data: 0x300d8011
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
waiting for bootloader to initialize
That's as far as she gets.
Any help would be appreciated!
Hi there
Go download the latest update ZIP from ASUS in your case, this would be Version V9.2.1.24(US).
Inside the .zip, there will be another .zip, open it.
Unpack the "blob" file.
Download Wheelie for windows: http://androidroot.mobi/2012/05/31/wheelie-for-windows-beta/
Unzip it.
Put the "blob" file into the same folder as wheelie.
Drag the blob file on "blobunpack.exe"
Then run reflash_sbkv1.bat
This will install the latest US ICS update on your device.
NOTE: THIS WILL WIPE EVERYTHING ON YOUR TABLET
Yep, do exactly that and you'll be all set.
Thanks
Thanks much!!! Nice quick reply!
I will give this a try and then report back!
H
Well, it got to:
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 1.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x252309607293186455
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
And that's as far as it gets now. Doesn't like bootloader it seems.
I was just wondering if anyone would see that the solution didn't work for me. In the interim I have contacted ASUS about RMA'ing this as I think it's still in warranty. I sure would hate to do that as I KNOW that there is a solution out there that will work, but I do need the help to find it.
Thanks
HS
hshevitz said:
I was just wondering if anyone would see that the solution didn't work for me. In the interim I have contacted ASUS about RMA'ing this as I think it's still in warranty. I sure would hate to do that as I KNOW that there is a solution out there that will work, but I do need the help to find it.
Thanks
HS
Click to expand...
Click to collapse
Hi there.
Do you have access to a linux computer?
If not, set up a virtual machine (ubuntu works) or download the image and boot from it.
Download blobtools from androidroots repo and compile it.
Unpack the blob.
Download wheelie for linux.
Put the blob files inside the wheelie folder.
run reflash_sbk1.sh
If you need more detailed instructions please post here.
Hello,
I got the same issue as hshevitz, but I'm using SBKv2
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x253608503293194433
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
Nothing more after 10min, 1h or 3h
Do we have a way to know what's going on or why it hangs ?
Thanks,
PS : I have an Asus TF101 B80 Transformer
Try different PC to use the nvflash. Install fresh drivers and proceed with the right steps. Sometimes PC do acting up as much as our transformer.
I have a problem with my g2x that can't be turned up, it stuck when I flash the NVflash "G2X_V21E_00_NVFlash". I did get through once then it's error again. Then I followed the same instruction but I have no idea why I can't pass through. I hope people can help me with this and tell me how or experience that they had it and solved it. Anyway, thank before the hand, I'm really appreciated your help.
Here the message I got when I tried to flash the NVFlash with G2X_V21E_00_NVFlash.
"C:\Users\Free\Desktop\Download\Software\Android\LG G2X\G2X_V21E_00_NVFlash>.\nvf
lash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --set
bct --odmdata 0xC8000 --configfile android_fastboot_emmc_full.cfg --create --bl
fastboot.bin --go
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x033c20c143e0b5d7
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
sending file: E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct
- 4080/4080 bytes sent
E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct sent successfully
odm data: 0xc8000
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
\ 888548/888548 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize"
Did you try doing it with the battery out and holding the volume buttons down until it gets past the bootloader?
Sent from my LG-P999
I did but it never go pass through it. It just stop at the " waiting for bootloader to initialize ". I tired dozen of time but it never works.
When I use nvflash for flashing clockworkmod, I know it's not identical to what you are doing but it should be close enough, I use these instructions and it has always worked:
===== STEP 1 - Flashing ClockworkMod Recovery 5.0.2.0:
download the 5.0.2.0 clockworkmod recovery image
place recovery-clockwork-5.0.2.0-p999.img in C:\G2x\NVFlash
Unplug everything
remove the battery
Hold Vol Up/Down (and keep them held)
Insert USB cable
open command prompt
execute the following commands:
Code:
navigate to folder with nvflash.exe in it at command prompt, for me cd g2x\nvflash
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-clockwork-5.0.2.0-p999.img
You should see it send a bunch of files to the device and the phone screen should say "S/W Upgrade - Please wait while upgrading...". You can let go of the volume buttons at this point. Once the files are sent and the program is finished running in the command window, you CAN just pull the USB cord or be safe and just wait a few extra minutes, however it will still say "upgrading.
Click to expand...
Click to collapse
Hope that helps somehow....
kuhla said:
When I use nvflash for flashing clockworkmod, I know it's not identical to what you are doing but it should be close enough, I use these instructions and it has always worked:
Hope that helps somehow....
Click to expand...
Click to collapse
I have no idea it's still not working any thank for your replying.
Maybe try re installing the LG and APX drivers?
Sent from my LG-P999
Hello, everyone~
First, sorry for my poor English, I really have no idea about my tablet.
I bricked my XOOM (MZ605) when I try to use RSD update to ICS. Now, there is nothing showed on my screen (blank screen), no matter I pushed Vol + or/and Vol - with Power button. And also there is no respone when I connected standard USB cable. But it's also very strange, I could charge the battary, but I assume the tablet also use energy, because it will be charged for such a while after I disconncet it several hours.
I made one "factory cable", and finally it was recognized as APX device. I update the driver for device, and now it was recognized as "NVIDIA USB boot-recovery driver for Mobile Devices",
Then go to command line, and type:
Code:
nvflash --sync
It showed:
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x02804045440022d7
macrovision: disabled
hdcp: enabled
sbk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
command failure: no bootloader was specified
And then I tried another command as:
Code:
nvflash --getpartitiontable pt.txt
It showed same result as above.
Another command:
Code:
nvflash -r --getpartitiontable pt.txt
It showed:
Code:
Nvflash started
[resume mode]
failed exectuing command 19 NvError 0x120002
command failure: get partition table failed (bad command)
or most times stuck at the line of "[resume mode]"
Lastyly I tried:
Code:
nvflash --bl bootloader.bin
(Note: I download this bootloader.bin from one post, and also try ASUS transformer's bootloader.bin)
It always showed:
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x02804045440022d7
macrovision: disabled
hdcp: enabled
sbk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 0
sdram config strap: 0
command failure: no bootloader was specified
I also tried other commands, but it showed something like "BCT not found". I guess maybe I damaged my bootloader and the bct file. It really makes me crazy......:crying:
Does anyone could help me on this issue? Or anybody could tell me is there any hope I could unbrick my XOOM?
Many thanks.
Dose anyone have any suggestion? Thanks.
Why did you use an Asus boot loader on a Motorola Xoom? Does not make sense!
Sent from my Xoom using xda premium
Many thanks for your kindly reply.
Actually, I just download the nvflash program to try to unbrick my xoom. And I googled bootloader.bin and mz600, then I found one, but it's not work.
Still, any suggestion? Thanks again.
Sent from my ZTE U970 using xda app-developers app
keep getting messages like===============================================================
===============================================================
One Click ClockWorkMod Recovery Flash for T-Mobile G2x
EXT4 Internal SD Support by TeamWhiskey
Version 4.0.1.5
===============================================================
===============================================================
Nvflash started
rcm version 0X20001
System Information:
chip name: unknown
chip id: 0x20 major: 1 minor: 3
chip sku: 0xf
chip uid: 0x037c710643412257
macrovision: disabled
hdcp: enabled
sbk burned: false
dk burned: false
boot device: emmc
operating mode: 3
device config strap: 0
device config fuse: 17
sdram config strap: 0
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: fastboot.bin
/ 1024992/1024992 bytes sent
fastboot.bin sent successfully
waiting for bootloader to initialize
bootloader failed NvError 0x0
command failure: bootloader download failed
===============================================================
===============================================================)
have attempted several variants 20 times or so each. same result. Am I straight up root blocked at this point or is there some other evil magic I could perhaps attempt>? -Cheers, -G
Are you holding the volume buttons down the whole time or letting them go after the computer recognizes the device as a nvidia boot device?
Also, what version of Windows are you on?
Also, have you tried installing the 5.0.2.0 version of CWM?
Also, try using volk's Batch Cleanup Tool. I've had success with it when regular nvflash didn't work.
Sent from my LG-P999 using xda app-developers app
Moved to proper forum.