Related
I have a friend who was trying to root the B80 transformer before he knew that it was not yet rootable and it appears to be bricked. It loads to the sus splash screen, and then stops and stays on the screen. Is there any way to unbrick it at this point via an sd card or anything, or is he just stuck until root access is achieved? The reset combos do not restore to factory settings.
If he has to wait until a root relase is published, will he be able to get root access since it sticks on the splash screen, or does he now own a $500 paper weight?
jthensley said:
I have a friend who was trying to root the B80 transformer before he knew that it was not yet rootable and it appears to be bricked. It loads to the sus splash screen, and then stops and stays on the screen. Is there any way to unbrick it at this point via an sd card or anything, or is he just stuck until root access is achieved? The reset combos do not restore to factory settings.
If he has to wait until a root relase is published, will he be able to get root access since it sticks on the splash screen, or does he now own a $500 paper weight?
Click to expand...
Click to collapse
Yeah probably
no possibilities at all?
throw an update file from the asus website onto a microsd card where the instructions tell you to and boot to recovery, should solve your problem
transformer b80 bricked - have i tried everything? help!
i have the same problem. I have a transformer tf101 with dock - b80 and its bricked. I tried i million options but starting to lose all hope. My story:
I was succesfull in unrooting it with razorclaw (had to downgrade to .19 first), then tried to install ClockWorkMod to make a backup before trying to flash GnuFabio's Revolver on it.
However, using several instructions (e.g. http://eeepadhacks.net/transformer-hacks/how-to-install-clockwork-recovery-3-1-0-1-and-backuprestore-roms-on-eeepad-transformer/, <-- yes at that time I hadnt figured out that it doesnt work on b80, I wish i had)(e.g.http://forum.xda-developers.com/showthread.php?t=1185104 and some other methods) i failed to install clockworkmod. Then i tried the Acer Recovery Installer (indicating that it shouldinstall clockworkmod). That failed too, but since then i am unable to start the tablet. When i turn it on, it stays on the first screen (eee pad, Asus and NVidea logos).
I can enter the bootloader WW_epad-8.6.6.19-20111101 by pressing Power and VOL_DOWN. After doing nothing for5 secs it will give me the option to choose the cold-boot (which doenst work!!) or to hit VOL_DOWN and then WIPE DATA. I have wiped all data, the Wipe is succesful, but no auto-reboot. I have to manually reboot by holding POWER for a while, however that didnt sole the problem.
entering RCK mode (power and VOL-DOWN, then VOL-UP) gives me the android logo with gear weels spinning, followed by the android logo and the yellow exclamation mark on its stomach. I have tried several files on the MicroSD but they all gave the same result (yellow exclamation mark).
images on the MicroSD i tried:
new Asus firmware (zipped on the root of the MicroSD, in the Asus folder as indicated on Asus website and even extracted on the root of the MicroSD);
recovery-3.1.0.1-solarnz-R3-240511-1908.zip (that from http://www.addictivetips.com/mobile/root-install-clockworkmod-recovery-on-asus-transformerhoneycomb-3-1/)
Revolver_TF_3.11_gnufabio.zip
EP101_SDUPDATE.zip (http://www.tabletroms.com/index.php/2011/05/30/asus-transformer-)
and some other
So now i tried the ASUS Transformer Root ToolKit V7.1 Universal (Windows) (http://forum.xda-developers.com/showthread.php?t=1185104 but that doesnt work: although being able to go into in APX mode (proven by showing up under USB controllers in windows settings ) it says "bootloader could not be loaded to pad"..
I think it has something to do with not being able to run ADB as it should. Checking it via the Root Toolkit says "ADB is not working or communicating with your pad". I tried to run ADB using the idiots' guide (http://forum.xda-developers.com/showthread.php?t=1071584&page=5, using the latest SDK(4.0.3. Api 15), drivers, etc, but end up with the no found devices attached (i tried this while the pad is in APX mode and when stuck on the home screen).
i understand that NV Flash doesnt work for the b80 either (it doesnt, it says:
"nvflash.exe"--bct transformer.bct --setbct --configfile flash.cfg --create --bl bootloader.bin --odmdata 0x300d8011 -sbk 0x1682ccd8 0x8a11a43ea 0xa532eeb6 0xecfe1d98 --go
Nvflash started
rcm version 0x4
Command send failed (usb write failed)
i also tried letting the battery drain, or holding POWER for over a minute, to no avail.
after this the pad disconnects from windows (hearing the beep as if usb is disconnected).
so...... what the heck should i do now to unbrick the damn thing .any help would be truly appreciated.
You need to get the Asus file from the website, unzip and extract it, and pull ONLY the file (for example WW_epad-user-8.6.5.21.zip) and place it in your root of your MicroSD card. You can also copy this file and rename it EP101_SDUPDATE.zip as well to be safe, have two copies of it on the SDcard.
You did not do this if you kept it extracted in the 'asus folder', it needs to be DIRECTLY ON THE MicroSD card..ONLY OFFICIAL ASUS FILES ARE GOING TO WORK.
Reboot into recovery, and please see my link in my signature for instructions on how to do all of this. Please read it entirely you should be able to do everything you need, including unbrick it.
If you are unwilling to do this I will purchase bricked TF's for $200 each.
[solved]
you sir are a god amongst men. I nearly threw myself off the 11th floor after bricking my b80 tf101, your trick with naming the 'sdupdate101' or whatever saved my life.
I wish there was more than a thank you button
liam
just to clarify I matched my serial number with identical firmware on asus website. double copied .zip to root and named one EP101_SDUPDATE.zip, Booted holding volume down and power, activated rdk and 5 minutes later was back in action.
Just to reiterate, the yellow triangle means something is wrong and you need to try something else...
Glad to hear it You should still read my guide it will help you keep from bricking it (FOR REAL NExt TIME ) be safe!
B80 bricked - HELP
luna_c666 said:
Glad to hear it You should still read my guide it will help you keep from bricking it (FOR REAL NExt TIME ) be safe!
Click to expand...
Click to collapse
hi all,
i've a big problem with my tf101g b80.
yesterday, after successfully rooting my TF, i started to install the gnufabio rom, but something has gone wrong.
i think probably a bad rom download...
now, i can acces the recovery (vol- & power) but after a while (i read the 8.6.5.21 version) and after pressing the vol+, o can see only tha android with some gears for few seconds and a yellow exclamation point.
as described, i downloaded the original 8.6.6.23 rom from asus website, copied the zip to a 2Gb sd card and renamed ep101_sdupdate.zip, but i can't install this rom.
i see ever the yellow exclamation point!
I'm desperate...!!!
(and the nvflash isn't update for the B80)
ANY IDEAS?!?!?!
demorodavi said:
hi all,
i've a big problem with my tf101g b80.
yesterday, after successfully rooting my TF, i started to install the gnufabio rom, but something has gone wrong.
i think probably a bad rom download...
now, i can acces the recovery (vol- & power) but after a while (i read the 8.6.5.21 version) and after pressing the vol+, o can see only tha android with some gears for few seconds and a yellow exclamation point.
as described, i downloaded the original 8.6.6.23 rom from asus website, copied the zip to a 2Gb sd card and renamed ep101_sdupdate.zip, but i can't install this rom.
i see ever the yellow exclamation point!
I'm desperate...!!!
(and the nvflash isn't update for the B80)
ANY IDEAS?!?!?!
Click to expand...
Click to collapse
My guess is that the TF101G has a different naming convention for its update-files than the regular TF101, but let me be absolutely clear about this: I'm only guessing.
josteink said:
My guess is that the TF101G has a different naming convention for its update-files than the regular TF101, but let me be absolutely clear about this: I'm only guessing.
Click to expand...
Click to collapse
the strange is the code of the FW: 8.6.5.21 may be for the tf101 w/o "G".
i don't know why this fw is on my tablet!
i tried to change it by the 8.6.6.23 but nothing happens.
and now it can't boot (stay in the eee pad - asus - nvidia logos) and can't turn off!!!
demorodavi said:
hi all,
i've a big problem with my tf101g b80.
yesterday, after successfully rooting my TF, i started to install the gnufabio rom, but something has gone wrong.
i think probably a bad rom download...
now, i can acces the recovery (vol- & power) but after a while (i read the 8.6.5.21 version) and after pressing the vol+, o can see only tha android with some gears for few seconds and a yellow exclamation point.
as described, i downloaded the original 8.6.6.23 rom from asus website, copied the zip to a 2Gb sd card and renamed ep101_sdupdate.zip, but i can't install this rom.
i see ever the yellow exclamation point!
I'm desperate...!!!
(and the nvflash isn't update for the B80)
ANY IDEAS?!?!?!
Click to expand...
Click to collapse
Did u extract the zip? Not just rename the zip. Read carefully the instruction.
Sent from my Transformer TF101 using Tapatalk
demorodavi said:
hi all,
i've a big problem with my tf101g b80.
yesterday, after successfully rooting my TF, i started to install the gnufabio rom, but something has gone wrong.
i think probably a bad rom download...
now, i can acces the recovery (vol- & power) but after a while (i read the 8.6.5.21 version) and after pressing the vol+, o can see only tha android with some gears for few seconds and a yellow exclamation point.
as described, i downloaded the original 8.6.6.23 rom from asus website, copied the zip to a 2Gb sd card and renamed ep101_sdupdate.zip, but i can't install this rom.
i see ever the yellow exclamation point!
I'm desperate...!!!
(and the nvflash isn't update for the B80)
ANY IDEAS?!?!?!
Click to expand...
Click to collapse
Did you mean the stock android recovery menu or CWM?
8.6.5.X are firmware builds for TF101, 8.6.6.X are builds for the TF101G.
If you have CWM installed still try pulling your microSD and booting to recovery, insert the microSD and install the upate.
If you do not have CWM, have you tried pullling the microSD and then hold VOL DOWN and POWER until the screen goes blank, and then continue holding until the small text appears so you can do a hard reset?
thanks all
thanks to all,
vf1 said:
Did u extract the zip? Not just rename the zip. Read carefully the instruction.
Click to expand...
Click to collapse
Obviously I did not...
EXTRACT the zip inside, NOT RENAME it.
Sorry and thanks for help!
Ok, I swear I have read 100 pages of similar problems, but it looks like everyone else is able to get into apx mode at least to run nvflash or easy flasher.
1. Turn on xformer with power button - stuck at Asus Eee Pad screen
2. Try to boot into recovery with vol - + power;
- volume up to enter recovery, ded android with an exclamation
- volume down to choose between 'wipe' and 'cold boot' both result in getting stuck at Asus screen
3. Plug in xformer, hold power and vol +; nothing. Never shows up in device manager and it doesn't beep or anything like the ones in all the videos do.
I really just want to get up and running at the very least, as I handle all of my businesses billing through my xformer, but my ultimate goal is to get on the HD-ROM.
I have downloaded the newest firmware from asus, have all the drivers installed (I think), have tried booting into recovery with one, some or all of the new software on the sdcard.
Any more ideas I can try? Do you just have to hold your mouth right to get it into apx mode? I have held those buttons so much I think I'm getting Nintendo thumb!!!
Thanks all!
nobody?
Throw something at me! What update.zip file do I put on the sd card? I have tried putting the newest asus update.zip on there with both its original name and the update.zip name. still comes up with a dead android and an exclamation point.
Download a firmware from Asus, rename it to EP101_SDUPDATE.zip
Put it on the root of your sd card and boot into recovery, hopefully it will flash it and let you boot up.
As for NVFlash, make sure you install teh APX driver.
Still won't get past about a second or two of trying to boot with EP101_SDUPDATE.zip on the sd card. Think I'm stuck, or is there something else I need to try?
Thanks!!
..Do the apx process and try using brks tool......just dont flash touch recovery! I couldnt get the drivers to show but still managed to nvflash recovery using the tool. Its install solarnz external sd recovery so you can put a rom zip onto micro sd.
My issue was after doing this normal on off reboot kept booting to recovery and i had to cold boot into the rom.
I tried the wheelie beta and it has ended up wiping the tf completely.....so dont do that lol. Its still a soft brick as i could still nvflash recovery but decided that aslongs its wiped of root etc id just send it to asus.
If brks tool flashes for you then id try nvflashing prime and see if that works.......i think it will but i ran out of time and patience this morning to do it......at your own risk of course.
scottyf79 said:
..Do the apx process and try using brks tool......just dont flash touch recovery! I couldnt get the drivers to show but still managed to nvflash recovery using the tool. Its install solarnz external sd recovery so you can put a rom zip onto micro sd.
My issue was after doing this normal on off reboot kept booting to recovery and i had to cold boot into the rom.
I tried the wheelie beta and it has ended up wiping the tf completely.....so dont do that lol. Its still a soft brick as i could still nvflash recovery but decided that aslongs its wiped of root etc id just send it to asus.
If brks tool flashes for you then id try nvflashing prime and see if that works.......i think it will but i ran out of time and patience this morning to do it......at your own risk of course.
Click to expand...
Click to collapse
i am the same issue by flashed the touch CWM and window wont able to reconigzed my TF as a APX device
i tried many drivers it still not able to work.
how can i get back to normal CWM? i dont have havy roms or update.zip in internal roms.. and Touch CWM wont able to recongized Removerable sdcard
god~~
The root and backup option should flash you an external recovery.
While tablet reboots hold down volume up and power until reboot stops.
Then try brks tool again and select root and backup.......during the process it may ask if you want to back up but its not worth while as i dont think theres anything to backup. You should end up with ext micro sd recovery.
As i said id look for the prime rom thread and download the nv flash version and see if it works first.
If asus restore the wiped TF without question and everything goes ok il let you know as it may be worth wiping it with wheelie nv recovery and just RMA.
I just simply CAN'T get it into apx mode. I've installed, uninstalled and reinstalled the drivers. Trying to flash ep101_sdupdate.zip still just results in an error. crap.
Hold Volume-UP BEFORE holding power, then hold power for 5 secs (Still holding vol-up( doing this all while connected. It should show in device manager.
Couldnt get Tf to show in device manager either no matter what.
I know it may not seem as though its in apx but if it has stopped rebooting when you do v up and power then it seems it is......
Seems to be an issue thats starting to become more common and very difficult to fix properly.
PC will just not recognise the TF.
Hmm - sorry i couldnt help more but id still try nv flashing Prime and if you can get to a blank screen using volume up and power without the TF rebooting theres a chance its in apx.
Best of luck dude.......
scottyf79 said:
Couldnt get Tf to show in device manager either no matter what.
I know it may not seem as though its in apx but if it has stopped rebooting when you do v up and power then it seems it is......
Seems to be an issue thats starting to become more common and very difficult to fix properly.
PC will just not recognise the TF.
Hmm - sorry i couldnt help more but id still try nv flashing Prime and if you can get to a blank screen using volume up and power without the TF rebooting theres a chance its in apx.
Best of luck dude.......
Click to expand...
Click to collapse
same case for me~~~just cant install the driver
You all can try running Puppy or DSL (damn small linux) in a virtual box on your windows pc. Comes with drivers included and only is a 200/60 Mb download.
Got so frustrated with it I just went and bought a tf-300
c3poman said:
Got so frustrated with it I just went and bought a tf-300
Click to expand...
Click to collapse
no better way to fix it than that
nice one
Yea, I like it pretty good so far. Volume is WAY louder on the 300, even though there is only one speaker. The screen also gets darker, which is nice if you watch tv or browse the interwebs in the bed. Also, wifi reception is great. Haven't tried gps yet, but I'm sure it is improved.
It did get really laggy, but I did a factory reset and it seemed to clear out the cobwebs.
Thanks for y'all's help! I'm still going to try to unbrick that tf-101 and sell it or something. Hate to have a $400 paperweight...
People will buy bricked ones on Ebay for a reduced price, just clarify that it is in fact bricked.
My Transformer started rebooting any time I copied anything to the internal SDCard and now will not boot the android os at all. I need to know how to put a new rom on the /sdcard/ and flash it. I can not get the android developers kit to load on my windows computer but i have a second computer that has Ubuntu on it that i think i can use. Can i get step by step instructions on how to do this ubuntu. I have tried everything i can think of and nothing worked. if this does not work then i guess i will need to RMA the unit but it is rooted and i dont know if asus will throw a fit over it. If anyone has any ideas i would be very grateful of the help. Also the rom i want to flash to is megatrons.
Thanks
have u tried cold booting from linux to see if you can get back in to Android?
volume down + power then release both when rck option shows at the top of the screen. you should get 2 options but if you leave it for a few seconds it will auto cold boot.
If that works you can try the fix recovery bootloop feature in my PERI tool, cold-booting whenever you need to reboot the tf. (In my signature)
Well I got it figured out. Unbricked my Transformer on Sunday
Sent from my PC36100 using XDA
Ok, so i've read up that your able to fastboot a new recovery, but i havnt been able to find a link with a stock recovery kernel.
Basically im not entirely sure if i infact DID unlock my bootloader tbh.
Bootloader (1.00 e) released by "WW_epad-10.4.4.20-20121026" A03
The story is i've bought it some while ago of course, and its been lieing around on the table for a few months.. Basically busy life and other ****. Yesterday i looked at it and was, oh right! Turn it on, and it bootloop on me, apparently common issue with a JB version. herpaderpa on android but fck that..
And when i use a update file on the sd card, i cant install that to update the stock firmware due to the dead droid with the triangle..
From what i can gather around, if i have fastboot option, then its unlocked ? Yes, no ?
If so, could anyone give a hint as to whut the duck i've missed when reading the big full guide thread on the infinity Im starting to become rather desperat. Never had this kind of behaviour with my android devices before, Sure a goofed usb driver for fastboot here and there.. But never a dead droid with triangle..
SOLUTION :
Follow this chaps guide http://forum.xda-developers.com/showthread.php?t=1755576
using his alternative method, and at step 2.
DO AS HE WRITES! Using upper case letters on the file your moving to the sd card, EP201_768_SDUPDATE.zip as such! It works!
My droid kept showing up dead, untill i changed to upper case letters... Then the darn thing came to life!
The dead android is the stock recovery telling you it could not apply an update. If you tap the power button you might even get an error message, but I am not sure if that works only after you activated the recovery using the bootloader menu.
If your device is unlocked, you can install an unofficial recovery or kernel, and it will display "The device is UnLocked" in the upper left corner when you turn it on. Caution: People have reported that locked devices still allow "fastboot erase", but not "fastboot flash".
_that said:
The dead android is the stock recovery telling you it could not apply an update. If you tap the power button you might even get an error message, but I am not sure if that works only after you activated the recovery using the bootloader menu.
If your device is unlocked, you can install an unofficial recovery or kernel, and it will display "The device is UnLocked" in the upper left corner when you turn it on. Caution: People have reported that locked devices still allow "fastboot erase", but not "fastboot flash".
Click to expand...
Click to collapse
In that case, how can i go about bringing my tablet out of this infernal boot thing? I've tried flashing the twrp kernel, but i dont see any change, when i sent the flash it dit get a blue bar on the bootloader indicated full. So i assumed it could send the loader..
Basically i just want to firmware upgrade with the latest stock firmware, But i tried dumping the file on an sd card, and then go into the bootloader But it did not recognize it and start an update. also i couldnt go into the RCK selection, due to the dead droid.
What exactly did you do, exactly which file(s) did you try to flash, and what exactly happened? And does "I couldn't go into the RCK selection" mean that you never see the bootloader menu, that it doesn't work, or that you don't know how to use it?
Ok, basically, when i start the pad, it never goes beyon the ASUS screen.
Im able to get into the bootloader, here i have 4 icons, RCK, Android, USB, Wipe Data.
When i select RCK it brings the dead droid after a droid thats working.
If i enter USB i can use fastboot. What i've tried here is to do the http://www.teamw.in/project Twrp recovery using http://forum.xda-developers.com/showthread.php?t=1833212 guide *** Custom Recovery Installation ***
However i dont think that it ever was sent to the tablet. Not sure.
I know how to move around in bootloader power + volume down = mennu, then tap the volume to switch between icons, and the other volume to select.
Power + other volume = AXP iirc in stead of bootlaoder.
Did not try to flash any files when the dead droid thing / bootloop started. I basically did an OTA update iirc to a newer version a good while ago. And then life became fcked for me for a periode so playing with the tablet wasnt really an option for enjoyment. It then drained of battery of course, and here now after having it charged up. i realise about this odd bootloop for one of the older droid software versions.
theorion said:
Basically im not entirely sure if i infact DID unlock my bootloader tbh.
Click to expand...
Click to collapse
_that said:
If your device is unlocked, you can install an unofficial recovery or kernel, and it will display "The device is UnLocked" in the upper left corner when you turn it on.
Click to expand...
Click to collapse
Do you already know if your device is unlocked?
_that said:
Do you already know if your device is unlocked?
Click to expand...
Click to collapse
No, it does not say unlocked any where
theorion said:
No, it does not say unlocked any where
Click to expand...
Click to collapse
OK, that explains why installing TWRP didn't work.
Now if you would describe in detail what you did to install the latest firmware, maybe someone could tell you why that didn't work.
Did you unzip the downloaded firmware update once (the result being another zip file)?
The unzipped zip is what you have to put on your sd card. Then the recovery should recognize it when you boot.
If that does not work, try to rename the unzipped zip: EP201_768_SDUPDATE.zip
and put that file into the root of you sd card.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD
1. Downloaded ASUS Transformer Pad TF700T Firmware: V10.6.1.14.8 Only for WW SKU (Android 4.2.1) from the TF700F download page selecting android as os.
2. Have a 2gb microsd, i formated as fat 32, using all standard alocation and stuff with windows' own formatting tool.
3. I unzipped the downloaded ZIP file so i have a WW_epad-user-10.6.1.14.8.zip that now contains a meta-inf folder, and a blob file.
4. renamed the zip file to ep201_768_sdupdate.zip, however i did use lowercase... Could that be the issue ? Basically i presumed that the uppercase was only to make people aware of a change.
5. boot the device using the power + volume, and enter recovery mode.
6. Dead droid..
Update as i was writing this, i thought, though it wasn't said specificly, i renamed the EP201_768_SDUPDATE to uppercase, and decided to give that a go.. Now the droid is working its ass off...
F**** i feel like a complete bloddy retard! Gawd i hope it works now then...
And its alive... OMG! If only i had renamed the darn file to uppercase, i would have fixed it using the guides... 2 days ago, before i even resorted to open a post.. Thanks guys! Though i realised my own damn fault, your desire to aid regardless are bloddy brilliant!
theorion said:
And its alive... OMG! If only i had renamed the darn file to uppercase, i would have fixed it using the guides... 2 days ago, before i even resorted to open a post.. Thanks guys! Though i realised my own damn fault, your desire to aid regardless are bloddy brilliant!
Click to expand...
Click to collapse
Oh yeah, Linux is case sensitive alright. Get the case wrong and it has no idea what you talkin' bout Willis.
My device is not unlocked or rooted. It was up to date on the OTA updates then one day it would not boot. I have tried to flash the most current ASUS stock ROM to recover it using the SD card. I renamed the extracted file as EP201_768_SDUPDATE.zip and tried to use that from RCK. It appeared to work but then stuck in a rapid boot loop. I also re-tried the process doing a Wipe Data first with the same exact result. Fastboot sees the device but doesn't appear to accept me trying to send it anything. ADB does not see the device and I know my windows drivers worked fine, I have transferred files using the USB cable often. Do I have any other options?
Sorry man, but that looks like the end of the road for your tablet.
You've tried everything available to you with a locked bootloader. You can't do anything in fastboot - you just won't get past the locked bootloader. Believe me we have tried! There's a thread on the Transformer Forums where I and a few other guys tried everything we could think of to get past it. No dice...
Give the microSD method a few more tries, and then start shopping for a new one....
Sent from my Nexus 5X using Tapatalk