this is a brand new unit that was recieved yesterday and applied newest OTA update.
I have tried the steps from norgi and that did not work for altnerative steps to get recovery . The screen stays stuck on entering Nv flash mode. I am pretty upset at viewsonic for disabling recovery in their new OTA. Without being able to flash any roms, I am left with no choice but to return it to amazon which will suck. I have put over 4hours into getting recovery to load off my sd cards and it simply will not load. My mistake for updating to OTA but there has to be a alternative way to get into recovery!!?? is there? any help appreciated
First off, don't worry. It's very unlikely that you bricked it.
Second, I honestly doubt that VS would have borked recovery on purpose (because how would they be able to do future updates without it?).
Questions: can you link to the post you tried, and the steps you went through to get to the point you are at now? That would help with troubleshooting. If you can get to APX mode, you should be able to get recovery back. Trust me, I've done some really nasty things to my device and I haven't bricked it (yet).
My only concern is that you might have a device that has a different partition structure , which means that nvflash might mess it up. I know that bekit himself had this issue, a few weeks back. We don't know why this is, or how many devices out there are affected.
roebeet said:
First off, don't worry. It's very unlikely that you bricked it.
Second, I honestly doubt that VS would have borked recovery on purpose (because how would they be able to do future updates without it?).
Questions: can you link to the post you tried, and the steps you went through to get to the point you are at now? That would help with troubleshooting. If you can get to APX mode, you should be able to get recovery back. Trust me, I've done some really nasty things to my device and I haven't bricked it (yet).
My only concern is that you might have a device that has a different partition structure , which means that nvflash might mess it up. I know that bekit himself had this issue, a few weeks back. We don't know why this is, or how many devices out there are affected.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=878751
I didnt brick it, the device turns off/on when it gets stuck on entering nv flash mode when I hard reboot holding down power for 10sec. I followed all the steps. Downloaeded the files, updated the drivers successfully. It never reads my SD card from the computer no matter what I do though. So i have to coopy it to the HD and manuelly copy it over? Could that be it.
I read your twitter post to viewsonic yesterday about they telling us that adobe HASN'T approved flash for tegra two devices. Let me tell you it is a crock of ****. The elocity a7 plays flash perfectly out the box without any hiccups.
http://www.youtube.com/watch?v=5CvY8jzyCWI . I hate when company promise something and cant delivery so they feel the need to lie and make up some lame excuse. I appreciate your efforts rohbeet. It's frustrating to put 4+hours of work into something I paid 400bucks with to not have it work. Im not a total n00b...I've flashed/rooted my evo/hero and wii successfully with no issues. So I hardly doubt Im doing something wrong... but who knows?
stugots101 said:
this is a brand new unit that was recieved yesterday and applied newest OTA update.
I have tried the steps from norgi and that did not work for altnerative steps to get recovery . The screen stays stuck on entering Nv flash mode. I am pretty upset at viewsonic for disabling recovery in their new OTA. Without being able to flash any roms, I am left with no choice but to return it to amazon which will suck. I have put over 4hours into getting recovery to load off my sd cards and it simply will not load. My mistake for updating to OTA but there has to be a alternative way to get into recovery!!?? is there? any help appreciated
Click to expand...
Click to collapse
Wrong section, try general. Getting old digging through all these questions to find something. No disrespect Roebeet, you the man round here.
Benblanko81 said:
Wrong section, try general. Getting old digging through all these questions to find something. No disrespect Roebeet, you the man round here.
Click to expand...
Click to collapse
How is it the wrong section? I am trying to flash my unit, and load a rom
stugots101 said:
http://forum.xda-developers.com/showthread.php?t=878751
I didnt brick it, the device turns off/on when it gets stuck on entering nv flash mode when I hard reboot holding down power for 10sec. I followed all the steps. Downloaeded the files, updated the drivers successfully. It never reads my SD card from the computer no matter what I do though. So i have to coopy it to the HD and manuelly copy it over? Could that be it.
I read your twitter post to viewsonic yesterday about they telling us that adobe HASN'T approved flash for tegra two devices. Let me tell you it is a crock of ****. The elocity a7 plays flash perfectly out the box without any hiccups.
http://www.youtube.com/watch?v=5CvY8jzyCWI . I hate when company promise something and cant delivery so they feel the need to lie and make up some lame excuse. I appreciate your efforts rohbeet. It's frustrating to put 4+hours of work into something I paid 400bucks with to not have it work. Im not a total n00b...I've flashed/rooted my evo/hero and wii successfully with no issues. So I hardly doubt Im doing something wrong... but who knows?
Click to expand...
Click to collapse
No worries. So, if I'm reading this right -- you had the device clean stock (?), then it ran the OTA update automatically when you connected Wifi (I assume it loaded 3053, btw) and then it rebooted into recovery and then what? Did it flash correctly at least once? But now, if you try to get into recovery, what happens? Nothing?
And then you tried ngorgi's nvflash trick but that's not working, I assume? How far do you get? Windows 64 bit user? APX drivers working? What do you see when you type "nvflash --bl bootloader.bin --download 9 clockwork.img"? Any errors? Sorry about the questions but the details are still hazy. I think the hardest thing about nvflash is getting the USB drivers working, especially if you are running Windows 64-bit.
I cant even get into recovery... Thats the problem. When i hit power L+R volume i get the viewsonic splash screen then it goes all black. And stays black until i hard reboot.
When i ran his workaround,, i got the whole way through. Ran CMD file, it download, flashed... apppear successfull. But the screen stays in "entering nv flash recovery"
'
Correct 3053
stugots101 said:
I cant even get into recovery... Thats the problem. When i hit power L+R volume i get the viewsonic splash screen then it goes all black. And stays black until i hard reboot.
When i ran his workaround,, i got the whole way through. Ran CMD file, it download, flashed... apppear successfull. But the screen stays in "entering nv flash recovery"
'
Correct 3053
Click to expand...
Click to collapse
That isn't how you enter recovery.
v+ and power = recovery
v- and power =apx/nvflash
If you hold + and -, it goes into apx, hence the black screen.
BTW, handling flash isn't the same as being approved by adobe. I bet elocity isn't approved yet either. The gtablet handles flash perfectly.
These are my results:
Code:
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x1714400944400297
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
| 928956/928956 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: recovery.img
| 3862528/3862528 bytes sent
recovery.img sent successfully
And I also see the "Entering nvflash recovery mode".
It sounds like nvflash is working for you. If you want to throw caution to the wind, you might want to go one step further and try to completely flash your device's partition structure. I have a post here:
http://forum.xda-developers.com/showthread.php?t=861950
It's basically the last resort before throwing in the towel and returning it.
rothnic said:
That isn't how you enter recovery.
v+ and power = recovery
v- and power =apx/nvflash
If you hold + and -, it goes into apx, hence the black screen.
Click to expand...
Click to collapse
I think I used to press both, initially. It might actually work that way, but using just vol down is easier.
Maybe I'm misunderstanding, but he said he can't get into recovery. Not apx. If you hold both, you can't get into recovery.
Ok i did the volume + and power and it is sitting on the detect recovery key pressed booting recovery image screen for about 4minutes now? Is that normal
stugots101 said:
Ok i did the volume + and power and it is sitting on the detect recovery key pressed booting recovery image screen for about 4minutes now? Is that normal
Click to expand...
Click to collapse
Ok, that's what it should say before it boots to recovery, but that is way too long.
Have you tried flashing clockwork with nvflash?
rothnic said:
Maybe I'm misunderstanding, but he said he can't get into recovery. Not apx. If you hold both, you can't get into recovery.
Click to expand...
Click to collapse
My bad, you are correct! I was so busy looking at APX mode that the answer was right in front of me. Yes, it sounds like he's just using the wrong key combo for recovery.
Here I am, looking at the most complicated solution. D-oh! EDIT: Uh oh, never mind....
stugots101 said:
Ok i did the volume + and power and it is sitting on the detect recovery key pressed booting recovery image screen for about 4minutes now? Is that normal
Click to expand...
Click to collapse
Yeah, that's way too long. Recovery might still be borked - should take 5-10 seconds.
I just did the nvlfash command and
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>nvfl
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: 0x171411884060c317
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: 0x108
sending file: bootloader.bin
| 933404/933404 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: clockwork.img
\ 393216/3862528 bytes sentdata send failed NvError 0x30012
command failure: partition download failed
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>
Still sits on the detect recovery key pressed screen
Well, it could be that your efforts to fix recovery might have broken recovery. I would go with my suggestion earlier, if you can't get the clockwork.img to work. Or, try part9.img (that's the original recovery image).
stugots101 said:
I just did the nvlfash command and
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>nvfl
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: 0x171411884060c317
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: 0x108
sending file: bootloader.bin
| 933404/933404 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
sending file: clockwork.img
\ 393216/3862528 bytes sentdata send failed NvError 0x30012
command failure: partition download failed
C:\Program Files (x86)\NVIDIA Corporation\tegra_froyo_20101105>
Still sits on the detect recovery key pressed screen
Click to expand...
Click to collapse
Ok, yeah that means you are using the bootloader.bin from the nvidia folder. You need to use one of the gtablet ones. Try the bootloader.bin from the tnt update.zip.
im good now! it works. Rohbeet was right, i think i broke it, trying to fix it, but then uninstalled everything and started from scratch. Thanks for the excellent help!
stugots101 said:
im good now! it works. Rohbeet was right, i think i broke it, trying to fix it, but then uninstalled everything and started from scratch. Thanks for the excellent help!
Click to expand...
Click to collapse
It was broken because you used the wrong bootloader. That is why it says flash failed. Make sure you take note or next time you try to nvflash you will have the same trouble all over again.
For us poor uneducated folk out here.. which method got you up and running...
stugots101 said:
im good now! it works. Rohbeet was right, i think i broke it, trying to fix it, but then uninstalled everything and started from scratch. Thanks for the excellent help!
Click to expand...
Click to collapse
Related
(if anyone can, please change these to links. I'm not allowed to post links yet since I'm a new user)
First, download the froyo image from:
developer DOT nvidia DOT com SLASH tegra SLASH downloads
Then, download this and merge it with the folder that the Nvidia tools install to (you'll have to overwrite 2 files).
www DOT dropbox DOT com SLASH s SLASH wrcd87u1iy31u4e SLASH nvflash_gtablet_2010110500.zip
Download Clockwork Recovery, get the recovery.img file from the update.zip, rename it to clockwork.img, and move it into the Nvidia folder.
android DOT d3xt3r01 DOT tk SLASH cyanogen SLASH harmony SLASH root SLASH ClockworkMod_Gtab_v08.zip
Connect the G-Tab to your computer via USB and power it on while holding Vol - (NOT +!). The screen will go on for a few seconds then turn off. The tablet's not off, it's just in APX mode.
Go to Device Manager and install the drivers for it (they're in theNvidiaFolder\usbpcdriver).
Open a command prompt in the nvidia folder and enter "nvflash --bl bootloader.bin --download 9 clockwork.img"
It should do it's thing and if it goes fine, you'll get your recovery back!
You are the man!!!! I am back in business. I was on the right track, but you figured it out and I am a happy camper.
Anything you need, let me know (except girls, currency, drugs)
Quick question, Now that I have NVFlash setup and working, is there a simple way using NVFlash to take a snapshot of my Tablet so I have a backup image if I need to restore?
brookfield said:
Quick question, Now that I have NVFlash setup and working, is there a simple way using NVFlash to take a snapshot of my Tablet so I have a backup image if I need to restore?
Click to expand...
Click to collapse
You could try this: http://tosh-ac100.wetpaint.com/page/Backup+and+Restore and just use bekit's bootloader.bin.
ngorgi said:
Then, download this and merge it with the folder that the Nvidia tools install to (you'll have to overwrite 2 files).
www DOT dropbox DOT com SLASH s SLASH wrcd87u1iy31u4e SLASH nvflash_gtablet_2010110500.zip
Click to expand...
Click to collapse
I'm a little confused. This says download the file, but overwrite two files?
I have downloaded and installed the first thing. Now i have downloaded the second file but not sure what to overwrite.
You need to unzip the files into the same directory. When you do it will ask you to overwrite 2files binloader is one of them
Ok, I know that I am missing something here. I have unzipped the "nvflash" file to this directory (C:\Program Files\NVIDIA Corporation\tegra_froyo_20101105).
I am never asked to overwrite anything. Is this the "NVIDIA tools" folder mentioned in post 1?
Sorry this is so hard for my small brain.
EDIT:Nevermind, I figured it out anyway. Thanks
I'm confused as what you mean by get your recovery back. Did you have a problem where it was overwritten?
No, for some reason it just goes away. Not sure why. When you hold power + "vol +", it should boot to recovery, but it just boots to CM.
Anyway, this was a lifesaver for sure today. Thanks for your help everyone!
Thanks, that helped a lot - works fine!
T.
I hate this tablet. I got the unit today and installed the OTA update and doing so i disabled clockword recovery. I followed these steps and got it to work from cmd and it went through the downloading process. My tablet is stuck on entering nvflash recovery mode. When i reboot and try the recovery it goes black again. I am positive I did it correctly and got the confirmation screen at the end of cmd.
I had the same issue... could not boot into recovery or the rom... right after installing clockwork .12
I had to take my unit back and get a new one...
What version of the clockworkMod image do you use to FLASH into the recovery Partition. I did not use the latest, You may need to try the 2.5.1.3 (That is what I used and it works).
Thanks!
ngorgi,
I just wanted to give you a big thanks... I had borked my g tab till I ran through your walkthrough.
Thank you so much!
-Lil'
Glad to see this actually helped a few people out
Now I may be wrong here (and if I am, PLEASE correct me), but I've come to the conclusion that this device is simply UNBRICKABLE. I've had my recovery disappear, had the magic value mismatch error, even had the device freeze in Nvflash mode where I had to wait for the batteries to drain before I could restart and I've been able to fix it EVERY TIME. Nvflash is too awesome.
FWIW, this is the only method that would work for me getting clockword to install on a fresh out of the box unit....I tried the sticky and it would show me the ! for a brief second and then reboot...
thanks!
HELP recovery problem
nvflash --bl bootloader.bin --download 9 cwm254recovery.img
bootloader.bin sent succesfully
sending file: cwm254recovery.img
-851968/4026368 bytes sentdata send failed NvError 0x30012
command failure: partition dowload failed
Click to expand...
Click to collapse
HELP!!!!!!!!!!!!!!!!!!!!!!!!
haltol said:
nvflash --bl bootloader.bin --download 9 cwm254recovery.img
HELP!!!!!!!!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Try doing:
nvflash --bl bootloader.bin --getpartitiontable mypt.text --go
To get you partition table and check the .text to confirn that part9 is SOS.
Jim
I am not so sure. One of my GTablets will no longer boot. I have to use nvflash to boot it. Battery drain, reset button inside, nvflash stock rom, TnT-light...whatever, the tablet will not boot. Nvflash and format parition 2 and I can get it to proceed into booting. I can nvflash bekits recovery and install roms or kernels.....reboot or power off and it will not come up until I nvflash "force" it to boot.
So i am not so sure they are completely unbrickable...just hard to do so. Mine started with the magic value mismatch error.
ngorgi said:
Glad to see this actually helped a few people out
Now I may be wrong here (and if I am, PLEASE correct me), but I've come to the conclusion that this device is simply UNBRICKABLE. I've had my recovery disappear, had the magic value mismatch error, even had the device freeze in Nvflash mode where I had to wait for the batteries to drain before I could restart and I've been able to fix it EVERY TIME. Nvflash is too awesome.
Click to expand...
Click to collapse
Sent from my Viewsonic 10" GTab...
help Got a brick.
Got a brick. I can not get into the APX mode.
Hold down Volume (-) and power while booting - did not work. May have other options?
There seems to be no way for me to flash back to stock recovery. So I was wondering if any of you have sent your G2x for replacements with CWM and never had an issue with them saying something. Which I doubt they would...but who knows.
Thanks
flexnix said:
There seems to be no way for me to flash back to stock recovery. So I was wondering if any of you have sent your G2x for replacements with CWM and never had an issue with them saying something. Which I doubt they would...but who knows.
Thanks
Click to expand...
Click to collapse
The 1st phone I sent back to T-Mo still had CWM installed. T-Mo never refused the phone. But you never know.
Have you tried option no.3 of One-Click ClockworkMod 4.0.0.2 NvFlasher by Gunnman to return the original boot loader back?
yeah i second that !!
one click nvflash it dum dum..
to b on the safe side.
bluedart said:
One-Click ClockworkMod 4.0.0.2 NvFlasher by Gunnman
Click to expand...
Click to collapse
This is the end-all-be-all of recovery flashing. Use it. Love it.
Hello everybody, I am very new to this and I am trying to install the Eagles blood 4.0.4 ROM. When I get to the step where you use the "one click recovery flasher" I get the "boot loader failed" error below. I get the S/W upgrade on the screen but when I hold the vol down + power i get the box with the lid open and the arrow like its updating instead of the blue LG logo. I have tried it a few times and i get the same thing. What am I doing wrong? Thanks for the help.
===============================================================
===============================================================
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: 0x033c208241415197
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
===============================================================
===============================================================
*****Once nvflash has completed successfully then hit any key to close.*****
****If any step failed then repeat the process****
Press any key to continue . . .
flexnix said:
There seems to be no way for me to flash back to stock recovery. So I was wondering if any of you have sent your G2x for replacements with CWM and never had an issue with them saying something. Which I doubt they would...but who knows.
Thanks
Click to expand...
Click to collapse
Try this method it worked for me before:
http://forum.xda-developers.com/showthread.php?t=1248644
Good luck
OK, 2 things. 1. There's a bat file you can use just search for recovery and you'll find plenty of posts. 2. In all honesty no carrier really cares. They only look for things like that if it's something it would cause an error for. If your screen went or the your phone just stopped booting then your good. They won't think to do it. I sell phones and when someone brought there's in for a replacement because of a defective battery I didn't think to see if rooted. Well low and behold it was. Samsung stratosphere. What did it boot to? Odin. Boy was I mad. Shows just how much we pay attention to stuff like that. Unless it goes to tech support and the run a system diag youll be fine.
Sent from my LG-P999 using XDA
Hi,
I have a BB0 eeepad. So, I've tryied to change kernel, After doing that, my eeepad continue rebooting, stucking on the Eeepad first screen (before the asus logo). CWM is not accessible, if I try to power on in apx mode, the tablet does that correctly. I have installed the correct driver using your tutorial (video) but i get the following error:
rcm version 0X4
Command send failed (usb write failed)
If I try to get into CWM, i get the double icon screen, wipe data or android. If i choose wipe, it works, but the tf101 won't boot. If i choose android, the screen show me "cold booting android" and it get freezed...
Could you help me ?
Thank you
Boot into recovery, you have to press Volume UP before the option to 'wipe' or 'cold boot' comes up to get into recovery. I have a feeling you aren't doing that.
Nope, i did it, but in this case, it continues to reboot in loop... (Same as wipe data)
You have a BBO so APX mode is not gonna do anything for you.
So Vol down plus power button till you see words at top left
Immediately push Vol up within 5 sec to get into recovery.
If you wait too long you get the cold boot/wipe data option.
So you're saying even pushing Vol up within the 5 sec don't work?
baseballfanz said:
You have a BBO so APX mode is not gonna do anything for you.
So Vol down plus power button till you see words at top left
Immediately push Vol up within 5 sec to get into recovery.
If you wait too long you get the cold boot/wipe data option.
So you're saying even pushing Vol up within the 5 sec don't work?
Click to expand...
Click to collapse
Yep, Immediately Reboot over and over again...
can you or not acces to cwm? if you can your device is not fully bricked
wich version of cwm recovery do you have?
I have the same issue, I have a B70, I have CWM Version v5.5.0.4, and can access it. I can get in to APX mode, and tried the NVFlash with the hopes I was one of the lucky B70's but got the same message:
rcm version 0X4
Command send failed (usb write failed)
I can get in to the cold boot screen, but I ONLY have the wipe data option, I do not have the Android logo option. Any help would be appreciated with this... I was definitely not trying to hijack this thread, but I really didn't think it was necessary to post a new thread for the same issue.
I get stuck on the Eee Pad startup logo. I can see the tablet in Device Manager as Asus TFP Device, but cannot get ADB serial to recognize it.
If you have no recovery, and you cannot get into your ROM, and you are SBK2..hang it up, you FUBARed your tab..sell it to someone who needs some hardware maybe? Try to RMA it to Asus, who knows- and then go sign the petition to release the SBK2 and this problem would not inconvenience you or Asus any longer when this happens..
Sorry guys
magnumrt562 said:
I have the same issue, I have a B70, I have CWM Version v5.5.0.4, and can access it. I can get in to APX mode, and tried the NVFlash with the hopes I was one of the lucky B70's but got the same message:
rcm version 0X4
Command send failed (usb write failed)
I can get in to the cold boot screen, but I ONLY have the wipe data option, I do not have the Android logo option. Any help would be appreciated with this... I was definitely not trying to hijack this thread, but I really didn't think it was necessary to post a new thread for the same issue.
I get stuck on the Eee Pad startup logo. I can see the tablet in Device Manager as Asus TFP Device, but cannot get ADB serial to recognize it.
Click to expand...
Click to collapse
You need to put working adb. try with a linux livecd or whatever you can, with that version of cwm recovery you will need some commands to be able to acces a microsd card and reflash the device
I'll send to Asus... Let it try...
But no, I've no access to CWM...
Antjac said:
I'll send to Asus... Let it try...
But no, I've no access to CWM...
Click to expand...
Click to collapse
You more than likely voided your warranty by flashing or rooting your device BTW..so good luck getting Asus to cooperate (fooling them)
Unfortunatlly, i've not other choice... (except if NvFlash's team find a solution for B70+)...
Wait and see...
When I try to get adb to recognize the tablet, it runs for a second, then lists attached devices , but no serial #. It does not say no devices or anything... is there any hope I can push a rom?
magnumrt562 said:
When I try to get adb to recognize the tablet, it runs for a second, then lists attached devices , but no serial #. It does not say no devices or anything... is there any hope I can push a rom?
Click to expand...
Click to collapse
That is supposed to happen, you need to execute adb shell to get a shell or adb push file /sdcard/ to push a file to the sdcard
I have the exact same thing, upgraded to ics, all worked ok, rooted, all ok for 2 day then nothing after a reboot, cant nvflash vol+ & power doesnt find any options bar stock if i recover goes to dead android with ! then asus logo and nothing. So it seems the issue is with the upgrade but as most of us rooted we may have a problem, mind you i did the wipe and recovery so it may have erased evidence.
If anyone is selling a TF101 I would love to buy one...
I forgot my TF101 on top of the car and ran it over, still works but the housing and lcd digitizer are dead >.<
Please email or pm me if interested
Well, good news...
As I said, I've sent my TF101 to Asus (to Czech Republic). I said my Tablet was bricked by updating to the ICS rom (That's not wrong in fact...).
So no problem, they flashed my tablet and sent it back. I've received it yesterday, everything is OK
Hi all,
I have a bricked TF101 (SBK v2) that I am trying to recover. There are numerous threads for this which I have tried following but keep hitting brick walls and as these threads tend to be in the development section, I am currently unable to post in them for advice.
I have tried a few differing programs to try and recover the device including "Oneclickrecovery", "BRK_Rootkit" and "Easyflasher"
Easy flasher (0.8.3b) seems to give the best results so far so I'm going to try and continue with this.
When running through the steps I get the following on the tablet screen:
Entering nvflash recovery mode nv3p server
chipvid: 12345678912344
!!!!!phone update sucess!!!!!
and the following from Easyflasher:
EasyFlasher for TF101 - By [email protected]
Using SBK2
---------------------------------------------------------------------------------------------------------------------------
Flashing Asus stock zip
>Extracting files.. please wait..
>Extracting blob archive..
>Blob extracted!
>Blob size 533946.73828125kb
Running Wheelie..
>Tablet is now ready for Nvflash
>Extracting from blob...
>Cleaning up before flashing...
>Checking file sizes
>SOS size 4184kb
>APP size 524288kb
>EBT size 1420.6171875kb
>LNX size 4054kb
Done!
However each time I reboot the device goes straight back in to APX mode. I have seen from the thread that different folks had different outcomes with different versions of easyflasher, but I cannot locate where to download different versions.
I am currently in the UK but the device was purchased in the US but I get the same results when trying to use any of the WW or US stock ROM update versions.
Any help locating different versions of easyflasher or any other advice you guys might have would be very well received as I now have a sore forehead from banging it on my desk.
Thanks for your time,
dhehir
reinstall recovery with easy flasher and after it finish power nadh olf button down.
vietchinh said:
reinstall recovery with easy flasher and after it finish power nadh olf button down.
Click to expand...
Click to collapse
Thanks vietchinh,
I have tried this, just keeps going back to APX mode each time.
Have you tried just a straight forward NVFLASH ROM ?
http://xdafileserver.nl/index.php?dir=Asus/Asus+Transformer+(TF101)/STOCK+ROMS/ICS+.27
The ROMs linked above will return your tablet to 100% Stock so you would need to root and flash custom recovery afterwards, but it would determine whether or not it is a hardware fault or just a bad luck combination of your custom ROM / Recovery
Just extract the NVFLASH ROM, enter APX Mode, plug the tablet into the PC and run the .bat file to flash, once it reboots it should be 100% stock
*Detection* said:
Have you tried just a straight forward NVFLASH ROM ?
The ROMs linked above will return your tablet to 100% Stock so you would need to root and flash custom recovery afterwards, but it would determine whether or not it is a hardware fault or just a bad luck combination of your custom ROM / Recovery
Just extract the NVFLASH ROM, enter APX Mode, plug the tablet into the PC and run the .bat file to flash, once it reboots it should be 100% stock
Click to expand...
Click to collapse
That link above did the trick for me! 3 months later and your post saved my device!
After installing TEAMEOS 4.2.1 (Jelly Bean) and not liking the performance and lockups, I tried to go back to the stock using first Rogue XM recovery (and didn't like it ever) and then TWRP 2.3.2.3. I tried a variety of things from different forums, but my tf101 eventually would only go into APX mode. No matter what, the screen would always remain black and I would see the device show APX in devices on my windows 7.
I tried EasyRecovery (this one didn't seem to do anything), OneRecover, direct nvflash, and nothing worked. I kept trying even more suggestions and doing the same things over and over as some people suggested worked for them (duh), and still nothing worked.
After countless hours of searching, trying different things, your easy suggestion was all I needed!
I have a C10 serial tf101 (US stock firmware).
Thanks a million!
--Eli
morroyoki said:
That link above did the trick for me! 3 months later and your post saved my device!
After installing TEAMEOS 4.2.1 (Jelly Bean) and not liking the performance and lockups, I tried to go back to the stock using first Rogue XM recovery (and didn't like it ever) and then TWRP 2.3.2.3. I tried a variety of things from different forums, but my tf101 eventually would only go into APX mode. No matter what, the screen would always remain black and I would see the device show APX in devices on my windows 7.
I tried EasyRecovery (this one didn't seem to do anything), OneRecover, direct nvflash, and nothing worked. I kept trying even more suggestions and doing the same things over and over as some people suggested worked for them (duh), and still nothing worked.
After countless hours of searching, trying different things, your easy suggestion was all I needed!
I have a C10 serial tf101 (US stock firmware).
Thanks a million!
--Eli
Click to expand...
Click to collapse
haha Great! Well, at least you picked up some knowledge on your journey
Now you know you can play around with anything you want and always be able to get back to stock when you're done
btw, give Team EOS3 #81 combined with K.A.T Kernel #69 a shot
That is JellyBean 4.1.2 and the fastest and most stable ROM for the TF101 imo
*Detection* said:
haha Great! Well, at least you picked up some knowledge on your journey
Now you know you can play around with anything you want and always be able to get back to stock when you're done
btw, give Team EOS3 #81 combined with K.A.T Kernel #69 a shot
That is JellyBean 4.1.2 and the fastest and most stable ROM for the TF101 imo
Click to expand...
Click to collapse
Hello,
I have a very similar problem with my TF101 since few months. Like "dhehir", it is always in APX mode, EasyFlasher seems to works (it displays the three lines
"Entering nvflash recovery mode nv3p server
chipvid: 12345678912344
!!!!!phone update sucess!!!!!", EasyFlasher stops at the partition 7.
The link puposed by *Detection* doesn't work, do you know where I can find it ?
Thanks,
Erev
erevlis said:
Hello,
I have a very similar problem with my TF101 since few months. Like "dhehir", it is always in APX mode, EasyFlasher seems to works (it displays the three lines
"Entering nvflash recovery mode nv3p server
chipvid: 12345678912344
!!!!!phone update sucess!!!!!", EasyFlasher stops at the partition 7.
The link puposed by *Detection* doesn't work, do you know where I can find it ?
Thanks,
Erev
Click to expand...
Click to collapse
Here you go
Code:
https://mega.co.nz/#!YZlVESKS!PVP6ixECCgapstRiD9bY9zxbWC5ctjBGvWSI1k09JhE
*Detection* said:
Here you go
Code:
https://mega.co.nz/#!YZlVESKS!PVP6ixECCgapstRiD9bY9zxbWC5ctjBGvWSI1k09JhE
Click to expand...
Click to collapse
Thanks a lot !
I'll run it tonight.
*Detection* said:
Here you go
Code:
https://mega.co.nz/#!YZlVESKS!PVP6ixECCgapstRiD9bY9zxbWC5ctjBGvWSI1k09JhE
Click to expand...
Click to collapse
Snif.... it doesn't work .
During the process, I have the same issue I had with EasyFlasher :
The proces stop at the line :
"
........
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
"
Nothing else, only a blinking cursor on the next line.
The tablet displays "Entering NvFlash recorery mode / Nv3p server
Chip Uid 037...
"
And then nothing appends. (I have waitted about 30 minutes)
Perharps it's a hardware issue :/
Are you running the flashing program as Admin? (Right click > Run as Administrator)
And which version of Windows are you running?
Ive found 32bit Windows 7 to have best compatibility for this sorta thing
I have tried this (as admin, W7 32-bit) and it runs through creating all 15 partitions, then formatting all 15 partitions, the tablet screen shows the Chip UID and then nothing else happens.
I have left it for over an hour and still nothing. The cmd window just shows Formatting Partition 15 Done! and the tablet screen remains the same.
Turn off tablet, and then still won't turn on in anything other than APX mode.
Ideas?
toweliechaos said:
I have tried this (as admin, W7 32-bit) and it runs through creating all 15 partitions, then formatting all 15 partitions, the tablet screen shows the Chip UID and then nothing else happens.
I have left it for over an hour and still nothing. The cmd window just shows Formatting Partition 15 Done! and the tablet screen remains the same.
Turn off tablet, and then still won't turn on in anything other than APX mode.
Ideas?
Click to expand...
Click to collapse
Hmm, I know it does take a long time using NVFLASH, but you should see the progress bar after the partition sections have finished it starts sending the files across, there is one partition that takes a super long time to complete though
Have you tried a different machine ?
Maybe set it going and leave it overnight in case it manages to complete whatever it's getting stuck on
*Detection* said:
Hmm, I know it does take a long time using NVFLASH, but you should see the progress bar after the partition sections have finished it starts sending the files across, there is one partition that takes a super long time to complete though
Have you tried a different machine ?
Maybe set it going and leave it overnight in case it manages to complete whatever it's getting stuck on
Click to expand...
Click to collapse
I tried EasyFlasher and left it running for hours and hours (when I previously thought it was stuck at partition 10) and it coompleted - but with no change in behaviour.
I then tried NVFlash again and left it over night - again the same result. Everything seems to 'work' in that it completes without errors but still the tablet won't turn on in anything other than APX mode.
I have tried to get the device registered as an ADB device and after spending a long time yesterday upgrading the SDK tools, I managed to get it showing in Device Manager as an ADB device and working correctly. However, running adb.exe I still cannot get it to 'show' as a device, even after running adb kill-server and adb start-server. I always get "error: device not found".
This is so frustrating as the device is clearly turning on and off but I can't seem to get it to be anything other than an APX mode.
A shot in the dark, but have you checked to see if the Volume Up button is stuck in ?
That would make it boot in APX mode each time
Quite simple to take the plastic bezel surround off and get to the micro switch under the volume rocker, just 2 screws near the port, then use a plastic flat thing to unclip the bezel
*Detection* said:
A shot in the dark, but have you checked to see if the Volume Up button is stuck in ?
That would make it boot in APX mode each time
Quite simple to take the plastic bezel surround off and get to the micro switch under the volume rocker, just 2 screws near the port, then use a plastic flat thing to unclip the bezel
Click to expand...
Click to collapse
Tried that, as expected the buttons are fine. Nothing stuck, all operating as it should.
Currently sitting in a semi-morgue state (the tablet, not me) with me having run out of ideas...
:crying:
No further suggestions?
It seems a waste to let this one die when it surely must be salvageable?
*Detection* said:
Have you tried just a straight forward NVFLASH ROM ?
(...) (I can't post the link .. it doesn't matter anyway) (...)
The ROMs linked above will return your tablet to 100% Stock so you would need to root and flash custom recovery afterwards, but it would determine whether or not it is a hardware fault or just a bad luck combination of your custom ROM / Recovery
Just extract the NVFLASH ROM, enter APX Mode, plug the tablet into the PC and run the .bat file to flash, once it reboots it should be 100% stock
Click to expand...
Click to collapse
Hi. I'm quite new here (in fact, this is my first post).
I've had an ASUS TF101 for a while now. I haven't used it in a while, and i believe that caused the batery to fully drain - as a result, i couldn't get it even to re-charge with the wall charger, much less to boot. I am now trying to revive it, so have been doing some research on the net, and reached as far here. I am able to connect it in APX mode, and tried running nvflash as above indicated (following the later posted correct link). However the bootloader doesn't seem to want to initialize. Below is what I've gotten:
C:\Users\Miguel Dias Pinheiro\Desktop\NVFLASH_ICS_9.2.1.27_WW_NOROOT>cd C:\Users
\Miguel Dias Pinheiro\Desktop\NVFLASH_ICS_9.2.1.27_WW_NOROOT\
C:\Users\Miguel Dias Pinheiro\Desktop\NVFLASH_ICS_9.2.1.27_WW_NOROOT>"nvflash.ex
e" --bct transformer.bct --setbct --configfile flash.cfg --create --bl blob.EBT
--odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 4
chip sku: 0x8
chip uid: 0x0388924041ff3457
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: 0
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
And that's it, it has been like this for about one hour now - is it normal to take this long.
By the way, the tablet screen is all black, nothing on it.
Can someone help me beyond this? Thanks!
I used motochop and got the phone rooted successfully but then my inexperience got the best of me when I tried to use safestrap to flash a 4.3 ROM. Looking back, I realize this was a terrible idea. I am now stuck at fastboot. This is the screen I get
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
I've scoured just about every thread in every forum I can find by searching, unless I'm missing something. I've tried flashing recovery and 4.1.2 using Razr HD Utility and I keep getting stuck right back here. I've tried pwr+volup, pwr+voldwn, and all 3. I've tried so many things, I'm honestly losing track of what I've done. Most threads end in something that requires USB Debugging but I can't even get into android. I'm just stuck at fastboot. I apologize in advance for possibly needing my hand held. I've rooted devices before, but I've never tried any motorolas so I'm not used to having things not go smoothly.
How can I get out of fastboot so I can use my phone again?!
same problem
zsarazan said:
I used motochop and got the phone rooted successfully but then my inexperience got the best of me when I tried to use safestrap to flash a 4.3 ROM. Looking back, I realize this was a terrible idea. I am now stuck at fastboot. This is the screen I get
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
I've scoured just about every thread in every forum I can find by searching, unless I'm missing something. I've tried flashing recovery and 4.1.2 using Razr HD Utility and I keep getting stuck right back here. I've tried pwr+volup, pwr+voldwn, and all 3. I've tried so many things, I'm honestly losing track of what I've done. Most threads end in something that requires USB Debugging but I can't even get into android. I'm just stuck at fastboot. I apologize in advance for possibly needing my hand held. I've rooted devices before, but I've never tried any motorolas so I'm not used to having things not go smoothly.
How can I get out of fastboot so I can use my phone again?!
Click to expand...
Click to collapse
I am having the same problem but i didn't root phone, just tried to flash stock rom after root failed, and says battery ok. Otherwise i've been bricked
zsarazan said:
I used motochop and got the phone rooted successfully but then my inexperience got the best of me when I tried to use safestrap to flash a 4.3 ROM. Looking back, I realize this was a terrible idea. I am now stuck at fastboot. This is the screen I get
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
I've scoured just about every thread in every forum I can find by searching, unless I'm missing something. I've tried flashing recovery and 4.1.2 using Razr HD Utility and I keep getting stuck right back here. I've tried pwr+volup, pwr+voldwn, and all 3. I've tried so many things, I'm honestly losing track of what I've done. Most threads end in something that requires USB Debugging but I can't even get into android. I'm just stuck at fastboot. I apologize in advance for possibly needing my hand held. I've rooted devices before, but I've never tried any motorolas so I'm not used to having things not go smoothly.
How can I get out of fastboot so I can use my phone again?!
Click to expand...
Click to collapse
Did you figure out the solution? Pretty simple... can just hold vol down and power for 10+ seconds and release
STuGGG said:
I am having the same problem but i didn't root phone, just tried to flash stock rom after root failed, and says battery ok. Otherwise i've been bricked
Click to expand...
Click to collapse
sooo... with the phone plugged in ... i repeat plugged in .. hold both volumes and power buttons at the same time until you get the boot menu.. then select either recovery or bp tools.. the tools option will let it charge at least.. recovery will get you going to where you really need to flash a rom or wipe data/cache so you can fix the bootloop hopfully .. good luck
i am in this exact same situation and have tried using rsd lite to flash the stock boot but the xml file has the "get-var" line in it and if i edit out then it says im in the wrong format...im a flash tool operator for a local shop here and i work on everyones phones in this area and now i have ppl messagin me thru email because my OWN PERSONAL phone is bricked haha this is not a good thing for me im sure i lose business because im missing something minor im sure
Topic Starter message have a Battery Low message
It may lock a firmware uploading process ))
hi I'm gaurang patel from Surat india, and I'm face this same pro b but Im findione
zsarazan said:
I used motochop and got the phone rooted successfully but then my inexperience got the best of me when I tried to use safestrap to flash a 4.3 ROM. Looking back, I realize this was a terrible idea. I am now stuck at fastboot. This is the screen I get
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
etMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected
I've scoured just about every thread in every forum I can find by searching, unless I'm missing something. I've tried flashing recovery and 4.1.2 using Razr HD Utility and I keep getting stuck right back here. I've tried pwr+volup, pwr+voldwn, and all 3. I've tried so many things, I'm honestly losing track of what I've done. Most threads end in something that requires USB Debugging but I can't even get into android. I'm just stuck at fastboot. I apologize in advance for possibly needing my hand held. I've rooted devices before, but I've never tried any motorolas so I'm not used to having things not go smoothly.
How can I get out of fastboot so I can use my phone again?!
Click to expand...
Click to collapse
Hi I'm gaurang patel from Surat in india,
And I face same prob than I'm trying to finding master of it after 4 month Im findout that man and now my droid RAZR start good
But in that case in my RAZR when I power on it it will going in fastbootmenu
But than run boot menu and normal restart
So if u HV prob than reply me on my gmail account
AP Fastboot, locked bootloader, Flash Failure
Hi all,
I am experiencing similar problem.
I have a Droid Razr Maxx HD from Verizon.
When i power on normally by pressing the power button, phone comes up into the AP Fastboot Flash Mode
Device is LOCKED. Status Code: 0
Batter OK
...
Fastboot Reason: Flash Failure
I can start the phone by powering up into the boot menu, then selecting Normal Powerup.
Phone power's up just fine after that.
Anybody know how to fix this problem?
Some info on my system:
System Version: 182.46.15.Verizon.en.US
Model: DROID RAZR MAXX HD
Android Version: 4.4.2
Baseband Verson: VANQUISH_bp_100731.020.64.21p
Kernel Version: 3.4.42-gdb361ac
Build Number: KDA20.62-15
If i could get a dump of firmware same version and try to flash, would that fix the problem?
Anybody have that?
I am noob to this site and hope I am in the right place, please excuse if not.
kjob said:
Hi all,
I am experiencing similar problem.
I have a Droid Razr Maxx HD from Verizon.
When i power on normally by pressing the power button, phone comes up into the AP Fastboot Flash Mode
Device is LOCKED. Status Code: 0
Batter OK
...
Fastboot Reason: Flash Failure
I can start the phone by powering up into the boot menu, then selecting Normal Powerup.
Phone power's up just fine after that.
Anybody know how to fix this problem?
Some info on my system:
System Version: 182.46.15.Verizon.en.US
Model: DROID RAZR MAXX HD
Android Version: 4.4.2
Baseband Verson: VANQUISH_bp_100731.020.64.21p
Kernel Version: 3.4.42-gdb361ac
Build Number: KDA20.62-15
If i could get a dump of firmware same version and try to flash, would that fix the problem?
Anybody have that?
I am noob to this site and hope I am in the right place, please excuse if not.
Click to expand...
Click to collapse
flash anything with fastboot and it will go away. grab your firmware from sbf droid devs if need be and just flash one part (or all if you want).
bweN diorD said:
flash anything with fastboot and it will go away. grab your firmware from sbf droid devs if need be and just flash one part (or all if you want).
Click to expand...
Click to collapse
Thanks for the reply.
The problem i am having is that my phone is not rooted, so I can't just flash any prior version rom onto it. I have not been able to find the matching firmware version to reflash exactly the same version (182.46.15...) i have back onto my phone. Would you know where I could find the matching ROM? Someone had suggested getting a dump of the ROMS from an existing phone. Is that possible?
kjob said:
Thanks for the reply.
The problem i am having is that my phone is not rooted, so I can't just flash any prior version rom onto it. I have not been able to find the matching firmware version to reflash exactly the same version (182.46.15...) i have back onto my phone. Would you know where I could find the matching ROM? Someone had suggested getting a dump of the ROMS from an existing phone. Is that possible?
Click to expand...
Click to collapse
i didnt realize the sbf want out yet, just looked, its not, sorry.
oops, just looked some more and remembered @SamuriHL posted it here.
just grab one of the img files out of the sbf and flash it.
We're lucky it's back at all. It was down for a few days. Hasn't been updated in quite a while which is depressing cause there's an FXZ I'd like to get my hands on.
To get out of the fastboot screen after a failed flashing attempt (several actually) i only had to use fastboot app (that came with motopocalypse) on my computer and write in console "fastboot continue", then the phone rebooted and started normally.
I still had the locked bootloader then.
gaurangpatel39 said:
Hi I'm gaurang patel from Surat in india,
And I face same prob than I'm trying to finding master of it after 4 month Im findout that man and now my droid RAZR start good
But in that case in my RAZR when I power on it it will going in fastbootmenu
But than run boot menu and normal restart
So if u HV prob than reply me on my gmail account
Click to expand...
Click to collapse
I was looking for the solution for my phone, but after reading this post in english I broke my phone. I didn't understand a single word and he want us to contact him for solution.
Motorola droid razr hd model xt 926
how i fix this problem plz help any body
AP Fastboot Flash Mode (S)
10.9B(*) (sha-1e9f557, 2013-05-25 01:04:26)
eMMC Info: Size 16GB
Device is LOCKED. Status Code: 0
Battery Low
Transfer Mode:
USB Connected
Failed to hab check for boot: 0x56
Fastboot Reason: Boot Failure
usb connected