Database Info

Magic Number Mismatch

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.

Cannot get to recovery mode

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.

nvflash on ASUS Transformer Prime TF201

Hi everyone,
The forum gods want me to post here first instead of in the developer forums.
I'm trying to backup my Asus Transformer Prime per the instructions here:
instructions: http://androidroot.mobi/t3_nvflash/
thread: http://forum.xda-developers.com/showthread.php?t=1774352&page=36
I've gotten up to the step of being able to bootstrap into nvflash after booting in APX mode using wheelie. Going on to "What Next?", I'm unable to backup my device partitions using nvflash. I get the following error:
Vazul tf201_nvflashpack # ./nvflash --resume --rawdeviceread 0 2944 bricksafe.img
Nvflash started
[resume mode]
failed executing command 30 NvError 0x120004
command failure: readdeviceraw failed
My device is rooted and unlocked. I'm running commands on my computer from root, so I don't think it's a permissions problems. I'm running Mint Linux 13. I've tried multiple times, so it's not a one-time thing. I'm using nvflash for Linux downloaded from the androidroot website (nvflash.tar.bz2). Any ideas? much thanks in advance for the help!
Output from wheelie:
Vazul tf201_nvflashpack # ./wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x98243046501521928
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash

I am getting the same error on mine too.

Same error for me
It took a lot of effort to find a copy of nvflash for ics, but now I find that it does not work and returns the above error.
Russ

tinnymarlin said:
Hi everyone,
The forum gods want me to post here first instead of in the developer forums.
I'm trying to backup my Asus Transformer Prime per the instructions here:
instructions: http://androidroot.mobi/t3_nvflash/
thread: http://forum.xda-developers.com/showthread.php?t=1774352&page=36
I've gotten up to the step of being able to bootstrap into nvflash after booting in APX mode using wheelie. Going on to "What Next?", I'm unable to backup my device partitions using nvflash. I get the following error:
Vazul tf201_nvflashpack # ./nvflash --resume --rawdeviceread 0 2944 bricksafe.img
Nvflash started
[resume mode]
failed executing command 30 NvError 0x120004
command failure: readdeviceraw failed
My device is rooted and unlocked. I'm running commands on my computer from root, so I don't think it's a permissions problems. I'm running Mint Linux 13. I've tried multiple times, so it's not a one-time thing. I'm using nvflash for Linux downloaded from the androidroot website (nvflash.tar.bz2). Any ideas? much thanks in advance for the help!
Output from wheelie:
Vazul tf201_nvflashpack # ./wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x98243046501521928
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
Click to expand...
Click to collapse
I got the same thing. maybe the nvflash problem. It just display "bad command".

[Q] Attempting root with 2.3.4 <php?t=1048274>+<php?t=1327599>

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.

(Help) Recovering a bricked Asus Transformer (Got the nvflash files)

I sold my Asus Transformer Infinity TF700 to someone a while ago. I had unlocked and saved my nvflash files. Two months passed and the buyer told me his wife somehow wiped the tablet. I thought it would be easy recovering the device so I told him to send it to me.
I followed this post http://forum.xda-developers.com/showpost.php?p=32796329&postcount=189 and on the first step when I send the command to the terminal "wheelie --blob blob.bin" it gets stuck on "Sending bootloader".
Waiting for device in APX mode...
[=] Chip UID: 0x98282857691354638
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Click to expand...
Click to collapse
Any help would be appreciated.

coolerthannos said:
I sold my Asus Transformer Infinity TF700 to someone a while ago. I had unlocked and saved my nvflash files. Two months passed and the buyer told me his wife somehow wiped the tablet. I thought it would be easy recovering the device so I told him to send it to me.
I followed this post http://forum.xda-developers.com/showpost.php?p=32796329&postcount=189 and on the first step when I send the command to the terminal "wheelie --blob blob.bin" it gets stuck on "Sending bootloader".
Any help would be appreciated.
Click to expand...
Click to collapse
Check that if your operating system correctly loading the APX drivers and the tablet is recognized by the system as an APX device. Myabe try a different usb port. I've got problems similar to this when my windows somehow not loaded correctly the APX driver.
Need to completely remove the drivers and reinstall!

bosstom said:
Check that if your operating system correctly loading the APX drivers and the tablet is recognized by the system as an APX device. Myabe try a different usb port. I've got problems similar to this when my windows somehow not loaded correctly the APX driver.
Need to completely remove the drivers and reinstall!
Click to expand...
Click to collapse
Did all that, reinstalled the drivers, changed the usb ports and it got recognized every time as a APX device no issues there and also tried it in linux mint, no go there either .

I would like to add that in windows I am getting a different Chip UID. Has the blob file gotten corrupted somehow? I got the rest of the files using this blob file last time and it worked fine. How much time should sending bootloader take?
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2bbd0434160e
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Click to expand...
Click to collapse

coolerthannos said:
I would like to add that in windows I am getting a different Chip UID. Has the blob file gotten corrupted somehow? I got the rest of the files using this blob file last time and it worked fine. How much time should sending bootloader take?
Click to expand...
Click to collapse
The sending should take a couple of seconds!

bosstom said:
The sending should take a couple of seconds!
Click to expand...
Click to collapse
It takes forever .

OMG, I am stuck in the very same situation! (But I am on a TF300TG.)
I was playing around with some recoveries and ICS stock ROMs and put all my faith into nvflash. Latter one I already used once or twice to make sure it was working.
After updating to the newest ICS available for my TF300TG, I installed twrp (the one for ICS), booted up the Stock ROM (which worked), booted in TWRP recovery, wiped all data. Rebooted into APX, and now I am stuck there since then.
Code:
g:\somePath\>wheelie.exe --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0xXYZ (it shows the right ID, just cropped it for my privacy...)
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
Any ideas?

forcemaker said:
OMG, I am stuck in the very same situation! (But I am on a TF300TG.)
I was playing around with some recoveries and ICS stock ROMs and put all my faith into nvflash. Latter one I already used once or twice to make sure it was working.
After updating to the newest ICS available for my TF300TG, I installed twrp (the one for ICS), booted up the Stock ROM (which worked), booted in TWRP recovery, wiped all data. Rebooted into APX, and now I am stuck there since then.
Code:
g:\somePath\>wheelie.exe --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0xXYZ (it shows the right ID, just cropped it for my privacy...)
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
Any ideas?
Click to expand...
Click to collapse
At least yours say sending file: 100% mine doesn't even come up .

OMG (again)!
I found in the Transformer Prime forum (here: http://forum.xda-developers.com/showpost.php?p=33234684&postcount=51) the solution to my problem.
It is:
Code:
wheelie -r --blob blob.bin
After that my screen is back on and wheelie completed its process.
Code:
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0xXYZ (still my private ID)
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x5
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash

forcemaker said:
OMG (again)!
I found in the Transformer Prime forum (here: http://forum.xda-developers.com/showpost.php?p=33234684&postcount=51) the solution to my problem.
It is:
Code:
wheelie -r --blob blob.bin
After that my screen is back on and wheelie completed its process.
Code:
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0xXYZ (still my private ID)
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x5
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
Click to expand...
Click to collapse
Thanks man it worked but now it gets stuck on the second sending file and on the tablet it shows "Entering NvFlash recovery mode / Nv3p Server"
Waiting for device in APX mode...
[=] Chip UID: 0x98282857691354638
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x5
[+] Sending bootloader...
Sending file: 100 %
Click to expand...
Click to collapse
Any more help would be apperciated.

Anyone?

coolerthannos said:
Thanks man it worked but now it gets stuck on the second sending file and on the tablet it shows "Entering NvFlash recovery mode / Nv3p Server"
Any more help would be apperciated.
Click to expand...
Click to collapse
Hi!
You really should tell us the command that you are using after "wheelie -r --blob blob.bin"!
As far as I can tell from the output you posted that you are trying to use "wheelie" a second time, which isn't right.
I do use(1) these commands to do a "nvflash" based restore to the "Android 4.0 Bootloader":
Code:
[B]wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
[/B]nvflash --resume --download 14 factory-config.img
nvflash --resume --download 7 unlock-token.img
... where I usually do not need to use the last 2 commands. The first 2 are doing fine most of the time!
The file names I used (e.g. "bricksafe.img") are valid for me, it depends on how you have named the files during backup.
(1) "I do use" means that this works for me. I expect it to work for you, too, but I take no responsibility for the usual bad boys (bricks, nuclear war, ...)

forcemaker said:
Hi!
You really should tell us the command that you are using after "wheelie -r --blob blob.bin"!
As far as I can tell from the output you posted that you are trying to use "wheelie" a second time, which isn't right.
I do use(1) these commands to do a "nvflash" based restore to the "Android 4.0 Bootloader":
Code:
[B]wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
[/B]nvflash --resume --download 14 factory-config.img
nvflash --resume --download 7 unlock-token.img
... where I usually do not need to use the last 2 commands. The first 2 are doing fine most of the time!
The file names I used (e.g. "bricksafe.img") are valid for me, it depends on how you have named the files during backup.
(1) "I do use" means that this works for me. I expect it to work for you, too, but I take no responsibility for the usual bad boys (bricks, nuclear war, ...)
Click to expand...
Click to collapse
Sorry I meant it gets stuck on the first command which is wheelie -r blob blob.bin. It sends the BCT but when it starts sending the bootloader it shows 100% but it doesn't say "[!] Done - your device should now be ready for nvflash" like your wheelie command does.
And on my device this is displayed, "Entering NvFlash recovery mode / Nv3p Server" with the Asus logo in the middle and the powered by nvidia tegra at the right. But nothing happens and the device doesn't enter NvFlash recovery mode.
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2bbd0434160e
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x5
[+] Sending bootloader...
Sending file: 100 %
Click to expand...
Click to collapse

coolerthannos said:
Sorry I meant it gets stuck on the first command which is wheelie -r blob blob.bin. [...]
Click to expand...
Click to collapse
Please, if you quote the command that you have used (specially after being asked for it!) it would really be good to quote the whole thing exactly the way you entered it in the console. Because now I have to guess if you entered "wheelie -r blob blob.bin" which is the wrong syntax (AFAIK), or if you were only too lazy to write/quote it completely.
I guess it is the latter one.
coolerthannos said:
It sends the BCT but when it starts sending the bootloader it shows 100% but it doesn't say "[!] Done - your device should now be ready for nvflash" like your wheelie command does.
And on my device this is displayed, "Entering NvFlash recovery mode / Nv3p Server" with the Asus logo in the middle and the powered by nvidia tegra at the right. But nothing happens and the device doesn't enter NvFlash recovery mode.
Click to expand...
Click to collapse
Did you try this:
Code:
[COLOR=Red]wheelie -r --blob blob.bin[/COLOR]
# wait until it reached 100% and a few seconds more
# then press Ctrl+C to terminate wheelie
[COLOR=Red]wheelie --blob blob.bin[/COLOR]
# execute it a second time, without "-r"
If this doesn't work: your device says that it was "Entering NvFlash recovery mode / Nv3p Server" which I expect to be already where you want it to be.
Try either:
terminate wheelie by Ctrl+C, then (try to) continue with the neccessary nvflash commands
OR
keep wheelie running, open a new console window/command prompt/cmd.exe and execute the nvflash commands in the new window.
On the one hand I expect both ideas to be "safe" as I read often enough that nvflash cannot be "disabled" or "altered" or "removed" at all
on the other hand I did not try this scenario and cannot garantuee anything. Your risk, but if it was my device, I would most likely try it.
Honestly, I am out of ideas. ATM I can only think of trying or reinstalling different APX drivers? Earlier you wrote:
Did all that, reinstalled the drivers, changed the usb ports and it got recognized every time as a APX device no issues there and also tried it in linux mint, no go there either
Click to expand...
Click to collapse
But back then you didn't use "wheelie" with the "-r" option.

forcemaker said:
Please, if you quote the command that you have used (specially after being asked for it!) it would really be good to quote the whole thing exactly the way you entered it in the console. Because now I have to guess if you entered "wheelie -r blob blob.bin" which is the wrong syntax (AFAIK), or if you were only too lazy to write/quote it completely.
I guess it is the latter one.
Click to expand...
Click to collapse
Yeah sorry was a little bit distracted so i quoted the command wrong here but I was putting it right in the command terminal.
forcemaker said:
Did you try this:
Code:
[COLOR=Red]wheelie -r --blob blob.bin[/COLOR]
# wait until it reached 100% and a few seconds more
# then press Ctrl+C to terminate wheelie
[COLOR=Red]wheelie --blob blob.bin[/COLOR]
# execute it a second time, without "-r"
If this doesn't work: your device says that it was "Entering NvFlash recovery mode / Nv3p Server" which I expect to be already where you want it to be.
Click to expand...
Click to collapse
It says "Waiting for device in APX mode". Nothing happens .
forcemaker said:
Try either:
terminate wheelie by Ctrl+C, then (try to) continue with the neccessary nvflash commands
OR
keep wheelie running, open a new console window/command prompt/cmd.exe and execute the nvflash commands in the new window.
On the one hand I expect both ideas to be "safe" as I read often enough that nvflash cannot be "disabled" or "altered" or "removed" at all
on the other hand I did not try this scenario and cannot garantuee anything. Your risk, but if it was my device, I would most likely try it.
Click to expand...
Click to collapse
Also tried everything you wrote but it still isn't responding. Whenever I try and keep the wheelie window open and try nvflash commands it gives communication error but when I close the wheelie window and try the command again nothing happens. It just shows "Nvflash v1.5.66719 started [resume mode]"
./nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
Nvflash v1.5.66719 started
[resume mode]
Click to expand...
Click to collapse
forcemaker said:
Honestly, I am out of ideas. ATM I can only think of trying or reinstalling different APX drivers? Earlier you wrote:
But back then you didn't use "wheelie" with the "-r" option.
Click to expand...
Click to collapse
I don't think these are drivers issues as I am trying it in linux now. Same issue on my brother's pc. I guess I'll have to try something else. This tablet doesn't want to get restored. I think it wants to remain bricked :laugh:.

If someone has the same issue and has somehow recovered his tablet please let me know.