Okay, I have done something wrong.
I had a stock transformer. I am using Linux and am trying to root and install recovery, with the idea being to flash a custom ROM after successful root.
I am using wheelie with NVflash. I was attempting to install a CWM blob. It was saying that it was written, but when I would boot into recovery, it only has the cold boot/wipe data options.
So this is where I screwed up.
I had seen it said that with NVflash it is almost unbrickable so I wasn't being as attentive as I should have been. With all the out-of-date rooting methods and firmware update exploit fixes, I had reading about this for hours.
So anyway, I was stupidly cut/past a command that was originally for windows and just ran it like a dummy. I thought it was extra config info and didn't look carefully. It looked like it was part of the recovery install instructions, but I should have been more careful. The command looks, on further examination, like a wipe/flash firmware, which fails because there was nothing to write in that directory, I believe.
Code:
./nvflash -r --bct transformer.bct --setbct --configfile flash.cfg --create --odmdata 0x300d8011 --sync
it formated a bunch of partitions and ended with this error
Code:
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
file not found: blob.EBT
failed executing command 2147483647 NvError 0x4
command failure: create failed
I tried to install recovery again, but I get messages like this:
Code:
[email protected]:~/android/transformer/root/wheelie$ ./nvflash -r --download 5 recovery-clockwork-5.8.3.4-tf101.img.SOS
Nvflash started
[resume mode]
sending file: recovery-clockwork-5.8.3.4-tf101.img.SOS
| 4360192/4360192 bytes sent
recovery-clockwork-5.8.3.4-tf101.img.SOS sent successfully
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: Bootloader not found (code: 27) message: nverror:0x8 (0x8) flags: 0
[email protected]:~/android/transformer/root/wheelie$ ./nvflash -r --go
Nvflash started
[resume mode]
command failure: go failed
(bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
I downloaded an update from Asus, US_epad-user-9.2.1.24.zip, which matches my old build, unpacked the blob, and have tried to run the ./reflash script. But it just hangs as you see here.
Code:
[email protected]:~/android/transformer/root/wheelie$ ./wheelie -2 --bct transformer.bct --bl bootloader.bin --odm 0x300d8011
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: 0x37c708542bff297
[=] 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 %
[!] Done - your device should now be ready for nvflash
[email protected]:~/android/transformer/root/wheelie$ ./reflash_sbkv2.sh
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
I then have to turn off the tablet to regain the APX connection.
This is might be TMI, but I haven't used any of these Tegra tools before, and would like to fix this thing as I just bought it for my wife this weekend...
Thanks!
Edit: .21 ICS, and C30 tf101.
Update: I was originally using the all-in-one package from wheelie. I downloaded nvflash by itself and made a new wheelie directory with the new nvflash files replacing those that were in the all-in-one. I also reunpacked the blob. Now when I run the ./reflash command, I now get
Code:
$ ./reflash_sbkv2.sh
File recovery.img is missing!
File boot.img is missing!
File system.img is missing!
One or more files are missing. Read documentation and provide the necessary files to continue!
which seems better, I suppose. I am tempted to just try and get those files from a custom rom and see what happens. Although I will try and wait to see if anyone has some advice. My shots in the dark haven't been very helpful so far...still I feel like it looks more promising...
update2 My overconfidence and impatience got the best of me. I tracked down a system, recovery and boot.omg that was in Prime!2.1 (HC) and then added it to the wheelie2 directory. It began to run, but then still hung at the same spot.
I decided to reboot my computer, and I also saw that maybe I did not need (as you can see above) intialize wheelie before reflashing. So I cd to wheelie2 and ran the ./reflash etc.
It wrote and the TRansformer automatically rebooted and showed the gears and now there is at least working Honeycomb (which is 10 times better than the OTA ICS she had.) I am not sure if it was intializing wheelie that gave me the problems or a bad nvflash or did my workstation need a reboot (unlikely, but still...)
Thanks for listening for what is now no goddam reason!
I already had a try on this on another forum:
hxxp://www(dot)transformerforums.com/forum/asus-transformer-help/25176-settings-stopped-working-tf101.html
(can't post links yet)
I have a TF101G ( sn:C20KAS035896) from a friend, everytime he went in to the settings it says: "settings stopped working"
I tried a factory reset, (from stock recovery menu), got it to reset, but now i cant get through the "first-time-setup-wizard":
at step 3 it asks to connect to a WiFi network, I select one, it asks for a password, but when I enter it and press ok it says "Unfortunately settings stopped working". After a few seconds it starts again at step one of the wizard..
I figured out it is a WW version.
So, what do I best try next?
After reading some here, i guess I get a alternative recovery and use that to flash a new stock rom onto the tablet.
But could you point me to the right posts and methods, because I'm not sure which is the right one.
http://forum.xda-developers.com/showthread.php?t=1552303
Then this you were looking for ? It is with recovery 3.2.0.1 us or ww stock rooted full rom edition
good luck
It might be. It seems to be a link to a zip file. The contents looks like the contents of a standard firmware file. Only the blob part is much smaller, and there is a system folder which isnt in the standard firmware update.
But I don't know what to do with it..
I was thinking maybe wolfs method 3 could help me out?
hxxp://forum(dot)xda-developers.com/showthread.php?t=1622628
(can't post links yet)
But i'm still strugling with adb though..
When i run "adb devices" I think it should list my TF101 but it doesn't
After some more reading and trying, I've come to the conclusion I can't get adb to connect to the device.
I also have an android phone: a HTC desire, which I can get to connect with adb. But the asus is stuck at the "first-time-setup-wizard" (as I explained above)..
Though I can see the device in windows explorer (win 7 64bit), and the 2 mounted drives "Internal storage" and "SD Card"
I can get it into apx mode, but nvflash doesn't work for my version of the device its a TF101G sn:C20KAS035896
What could i try next?
I want to flash the stock rom, as mine seems to be broken, and I cant use adb
EDIT:
Just found out about wheelie, should that tool be able to do what I want?
androidroot(dot)mobi/2012/05/27/introducing-wheelie-nvflash-for-asus-transformer-tf101-b70/
My device isnt explicitly listed, and EasyFlasher a tool based on wheelie says it doesnt work for my device.. So should it work or not?
Do I need linux for this? I cygwin ok?
EDIT2:
As I understand it, I probably have a Secure Boot Key that isn't version 1 or 2?
There is a sbk detection tool, but afaik it only works on mac, and I don't have a mac available..
I have tried the windows beta version of wheelie, and the output i get is the following:
reflash_sbkv2.bat
Code:
J:\TF101\wheelie>reflash_sbkv2.bat
J:\TF101\wheelie>cd J:\TF101\wheelie\
J:\TF101\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl bootloader.bin --o
dm 0x300d8011
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: 0x305242034059367191
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
J:\TF101\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct --configfile fl
ash.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
failed executing command 11 NvError 0x30012
command failure: create failed
J:\TF101\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
command failure: go failed
And for the sbkv1 version the same:
Code:
J:\TF101\wheelie>reflash_sbkv1.bat
J:\TF101\wheelie>cd J:\TF101\wheelie\
J:\TF101\wheelie>"wheelie.exe" -1 --bct transformer.bct --bl bootloader.bin --o
dm 0x300d8011
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: 0x305242034059367191
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
J:\TF101\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct --configfile fl
ash.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
failed executing command 11 NvError 0x30012
command failure: create failed
J:\TF101\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
command failure: go failed
Am I overlooking something here?
Should I get adb working with my tablet in its current state?
Or do I have to return the tablet to ASUS?
Same problem here
Hello frydac, I'm having the same problem as you.
Did you find a way to fix it yet?
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".
Someone deleted the files from the tablet when I restart glue on boot, tried to recover with nvflash but is giving error
reading config file ./boot/purelinux.cfg
Writing Boot Image ./images/linux.img
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: '.\images\bootloader.bin'.
Using BCT: '.\images\transformer.bct'.
----------------------------------------
[=] Chip UID: 0x299648565018420119
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
Nvflash started
[resume mode]
connection failed NvError 0x30011
Nvflash started
[resume mode]
connection failed NvError 0x30011
HELP ME PLEASE
AJUDEM-ME POR FAVOR
Code:
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
Try EasyFlasher to bring it back to stock, it supports both SBK types.
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.