Here is what I've done.
I have an Asus transformer pad TF300T with android OS. I updated it to the latest Jelly Bean 4.2.1. I then installed all the drivers, adb, apex required. I downloaded fastboot and CWM v6.0.3.2.
I unlocked it no problem. I used fastboot to install CWM,no problem there as well. Then I put the root.zip file to the sdcard.
Then I rebooted to CWM to flash it, but CWM couldn't mount the sdcard.
Then, with stupidity, I chose the wipe data option. <=== that's when the problem started.
So now, I have an asus pad which can't boot the android OS.
When it boots it automatically goes to CWM and can't do nothing with it (because obviously it can't mount the internal Sdcard and the external one as well). Can't use fastboot or adb (computer doesn't recognize the pad). I don't have the basic menu RCK, ANDROID, USB, WIPE when I press POWER + VOLUME DOWN.
I tried NVflash (i know doesn't work with TF300T JB but had to try), I tried to reinstall it with the original asus firmware with a micro sdcard but none worked. Tried everything (on windows vista/7 and on ubuntu). Don't what else to do.
So basically, i have an ASUS transformer pad TF300T bricked, not rooted, with android Jelly Bean 4.2.1 and CWM v6.0.3.2
I read many similar threads on many forums but I thought it would be better If I explain my situation so I could get a better answer.
PS: I know I wasn't careful enough before doing this, It's my responsibility and I acknowledge that. I unlocked my pad so I knew there were some risks.
So please Help Me!!!!
Thank you in advance.
but if you can help me
Flash stock rom
Guide on how to do that + download stock rom from here - click here
You should be fine after flashing stock rom. :highfive:
hard bricked I guess
You should be fine after flashing stock rom. :highfive:[/QUOTE]
First of all, thank you for replying to thread, I appreciate it. This procedure seems really great but like I can't have the RCK menu and that my computer only recognize my devise through apx mode, it doesn't work. Well it looks like I m in a no win senario on this one. I guess I'll send it back to Asus for a software repair. Even though I unlocked it, I think I found a work around so it won't cost much, and since (from what I've heard) I l'm in Europe I have better chances to have it repaired for almost nothing.
TF300T almost bricked
khajj16 said:
Here is what I've done.
I have an Asus transformer pad TF300T with android OS. I updated it to the latest Jelly Bean 4.2.1. I then installed all the drivers, adb, apex required. I downloaded fastboot and CWM v6.0.3.2.
I unlocked it no problem. I used fastboot to install CWM,no problem there as well. Then I put the root.zip file to the sdcard.
Then I rebooted to CWM to flash it, but CWM couldn't mount the sdcard.
Then, with stupidity, I chose the wipe data option. <=== that's when the problem started.
So now, I have an asus pad which can't boot the android OS.
When it boots it automatically goes to CWM and can't do nothing with it (because obviously it can't mount the internal Sdcard and the external one as well). Can't use fastboot or adb (computer doesn't recognize the pad). I don't have the basic menu RCK, ANDROID, USB, WIPE when I press POWER + VOLUME DOWN.
I tried NVflash (i know doesn't work with TF300T JB but had to try), I tried to reinstall it with the original asus firmware with a micro sdcard but none worked. Tried everything (on windows vista/7 and on ubuntu). Don't what else to do.
So basically, i have an ASUS transformer pad TF300T bricked, not rooted, with android Jelly Bean 4.2.1 and CWM v6.0.3.2
I read many similar threads on many forums but I thought it would be better If I explain my situation so I could get a better answer.
PS: I know I wasn't careful enough before doing this, It's my responsibility and I acknowledge that. I unlocked my pad so I knew there were some risks.
So please Help Me!!!!
Thank you in advance.
but if you can help me
Click to expand...
Click to collapse
Hi, I had the same situation with mine just the day before yesterday! I've been ready to put it in the garbage
BUT I solved with a few simple steps : (provided that you have Android sdk installed, if not download and install it
with administrative rights)
1) go in the subdirectory Android\android-sdk\platform-tools where you can see fastboot.exe and adb.exe
2) connect your tabled frozen in the bad CWM, it must be recognized if you have the correct driver installed
(if not ask me how to)
3) do this command : adb -d reboot-bootloader
4) it should reboot and magically it shows you RCK & Android (if you try Android the tablet boot correctly)
5) do this command : fastboot erase recovery , and the bad CWM wil be wiped (fastboot need the right driver installed or you'll see ..waiting..)
6) only in case it's not enough step 5) do also fastboot erase boot
reboot and you'll have yr tablet back to life :laugh:
aldossir said:
Hi, I had the same situation with mine just the day before yesterday! I've been ready to put it in the garbage
BUT I solved with a few simple steps : (provided that you have Android sdk installed, if not download and install it
with administrative rights)
1) go in the subdirectory Android\android-sdk\platform-tools where you can see fastboot.exe and adb.exe
2) connect your tabled frozen in the bad CWM, it must be recognized if you have the correct driver installed
(if not ask me how to)
3) do this command : adb -d reboot-bootloader
4) it should reboot and magically it shows you RCK & Android (if you try Android the tablet boot correctly)
5) do this command : fastboot erase recovery , and the bad CWM wil be wiped (fastboot need the right driver installed or you'll see ..waiting..)
6) only in case it's not enough step 5) do also fastboot erase boot
reboot and you'll have yr tablet back to life :laugh:
Click to expand...
Click to collapse
Hi aldossir! Thank you for answering . Like you have been in the same situation I will follow your instructions to the letter.
1) I do have the SDK tools, fastboot and adb as well
2) My computer doesn't recognize the device when under the bad CWM. I have the drivers but I guess they aren't the correct ones. So, if you don't mind I'll ask you for instructions and for a link toward the correct ones so I can install them.
For steps 3 to 6, I'll see about that once I get my device recognized.
Note: I will use windows vista to do this. However, if you advices me that it is preferable to use Windows 7, I'll do it.
In the meantime, I will recharge my tablet.
Thank you again.
khajj16 said:
Here is what I've done.
I have an Asus transformer pad TF300T with android OS. I updated it to the latest Jelly Bean 4.2.1. I then installed all the drivers, adb, apex required. I downloaded fastboot and CWM v6.0.3.2.
I unlocked it no problem. I used fastboot to install CWM,no problem there as well. Then I put the root.zip file to the sdcard.
Then I rebooted to CWM to flash it, but CWM couldn't mount the sdcard.
Then, with stupidity, I chose the wipe data option. <=== that's when the problem started.
So now, I have an asus pad which can't boot the android OS.
When it boots it automatically goes to CWM and can't do nothing with it (because obviously it can't mount the internal Sdcard and the external one as well). Can't use fastboot or adb (computer doesn't recognize the pad). I don't have the basic menu RCK, ANDROID, USB, WIPE when I press POWER + VOLUME DOWN.
I tried NVflash (i know doesn't work with TF300T JB but had to try), I tried to reinstall it with the original asus firmware with a micro sdcard but none worked. Tried everything (on windows vista/7 and on ubuntu). Don't what else to do.
So basically, i have an ASUS transformer pad TF300T bricked, not rooted, with android Jelly Bean 4.2.1 and CWM v6.0.3.2
I read many similar threads on many forums but I thought it would be better If I explain my situation so I could get a better answer.
PS: I know I wasn't careful enough before doing this, It's my responsibility and I acknowledge that. I unlocked my pad so I knew there were some risks.
So please Help Me!!!!
Thank you in advance.
but if you can help me
Click to expand...
Click to collapse
I dont know if it is your case or not... but I beleave was in your same condition, the only recovery able to read and write our device memory is the last twrp (openrecovery-twrp-2.4.4.0-tf300t-4.2.blob) on my device with the same problem I was able to restore the system from the backup...
now you have an other problem... if you dont have any backup to restore i dont know what you can do, the recovery work fine but i wasn't able to install any CM10.1 but i'm confident you can install a stock version....
I hope my suggestion can help you, good luck and of coure all the procedure are at your risk
lk2l said:
I dont know if it is your case or not... but I beleave was in your same condition, the only recovery able to read and write our device memory is the last twrp (openrecovery-twrp-2.4.4.0-tf300t-4.2.blob) on my device with the same problem I was able to restore the system from the backup...
now you have an other problem... if you dont have any backup to restore i dont know what you can do, the recovery work fine but i wasn't able to install any CM10.1 but i'm confident you can install a stock version....
I hope my suggestion can help you, good luck and of coure all the procedure are at your risk
Click to expand...
Click to collapse
Well I'll try but without the correct fastboot or adb drivers, it's going to be difficult. But it's worth a try. And about the "of course the procedure at your risk", I guess it can't get any worse, can it? ^^
Anyway ty
...mmm maybe my reply was not the clear, you are right...
I dont think it can be wrost, I'm sure this must not be done if you have ICS (4.0)...
I update my tf300t to JB 4.2.1 and after that I unlock the bootloader with the asus tool (from asus site), and installed the CWM 6.0.2.3 using fastboot, at this point the tablet work correctly but recovery was unable to read the sd card (internal and external). I tried to install other version of cwm and TWRP recovery, at the end found the TWRP dedicate for who has done the update to 4.2.1, installed and after done the backup, I try to install CM10.1 and all the system was not able to boot over at the asus screen, fortunatly the backup works fine I restored it and now it's back to normal (+ root lol)
I think the 4.2 bootloader need some specific rom... in any case for the moment it's fine.
now I will explain better witch procedure I followed
1) to have the correct driver for fastboot you can install asus PC sync from the asus website
2)download fastboot from internet and extract to c:\fastboot\
3)download from goo.im openrecovery-twrp-2.4.4.0-tf300t-4.2.blob and put in the fastboot directory
4)boot the tf300t holding power + volume down and connect at the pc
5)open command prompt (run cmd.exe) and navigate to c:\fastboot\
6) to know if the device is connected correctly use the command "fastboot devices" it should show you a string with numbers and letters
7)to install the recovery use the command fastboot -i 0x0B05 flash recovery openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
8)Reboot with the command fastboot -i 0x0B05 reboot-bootloader
Now you have the TWRP 4.2.2.0 specific for the bootloader 4.2 with this you can install rom and try to restore the system, in case if you dont find any other solution i can try to share my system back-up. but I can't garanty it will work at 100% (maybe 98% )
I hope I was more cleare than before lol
let me know if it works for you.
sorry if I didn't put direct link but this is my second post and I cant insert any link until post n°10...
TF300TL software brick solved!
aldossir said:
Hi, I had the same situation with mine just the day before yesterday! I've been ready to put it in the garbage
BUT I solved with a few simple steps : (provided that you have Android sdk installed, if not download and install it
with administrative rights)
1) go in the subdirectory Android\android-sdk\platform-tools where you can see fastboot.exe and adb.exe
2) connect your tabled frozen in the bad CWM, it must be recognized if you have the correct driver installed
(if not ask me how to)
3) do this command : adb -d reboot-bootloader
4) it should reboot and magically it shows you RCK & Android (if you try Android the tablet boot correctly)
5) do this command : fastboot erase recovery , and the bad CWM wil be wiped (fastboot need the right driver installed or you'll see ..waiting..)
6) only in case it's not enough step 5) do also fastboot erase boot
reboot and you'll have yr tablet back to life :laugh:
Click to expand...
Click to collapse
You saved my device health, the steps you describe worked flawlessly for my ASUS Tranformer pad TF300TL (4G) LTE software brick, thank you very much!!! :laugh: :good: I am a new user and I want to bring my knowledge to the next level with XDA
i have similar situation
i have similar situation with my tf300t but i can't connect to fastboot tool. my device is stock to asus logo and i just can connect to apx mode please help
This should fix it
Link to my thread--> http://forum.xda-developers.com/showthread.php?p=45120193#post45120193
Hope it helps!
I can't connect to fastboot mode. Any help about that?
Sent from my GT-N7100 using xda app-developers app
Fixed my problem and got my RCK back
aldossir said:
Hi, I had the same situation with mine just the day before yesterday! I've been ready to put it in the garbage
BUT I solved with a few simple steps : (provided that you have Android sdk installed, if not download and install it
with administrative rights)
1) go in the subdirectory Android\android-sdk\platform-tools where you can see fastboot.exe and adb.exe
2) connect your tabled frozen in the bad CWM, it must be recognized if you have the correct driver installed
(if not ask me how to)
3) do this command : adb -d reboot-bootloader
4) it should reboot and magically it shows you RCK & Android (if you try Android the tablet boot correctly)
5) do this command : fastboot erase recovery , and the bad CWM wil be wiped (fastboot need the right driver installed or you'll see ..waiting..)
6) only in case it's not enough step 5) do also fastboot erase boot
reboot and you'll have yr tablet back to life :laugh:
Click to expand...
Click to collapse
The above works to get RCK back. Perfect many thanks.
Related
Hi everyone,
Well I'm in that freak out stage.... where I am sure some of you have been.
Heres my issue...
I have a transformer prime that;
I just unrooted using Vipermod
Then did a factory reset
Now I am stuck in CWM recovery
I attempted to do a restore but after it gets done it brings me back into the recovery
I attempted to ADB but the command prompt opens and closes right away ( I assume from not being in USB debugging, which I cant get into without a rom)
I have no rom's currently downloaded into the prime as I just wiped everything in there as well.
Please i'll gladly pay $5 to anyone who can fix this without it breaking more (hard bricking if I havent already done so)
AHHH please guys help, I'm afraid it will run out of battery soon then I'll be royally screwedddd
anyone?
are you on windows 7?
yes windows 7 professional sp 1 32bit . to reiterate I am stuck in Clockwork mod Recovery without root, and with no roms on the internal SD. I have access to one restore that works but after it completes it reboots back in recovery.
birchnick10 said:
yes windows 7 professional sp 1 32bit . to reiterate I am stuck in Clockwork mod Recovery without root, and with no roms on the internal SD. I have access to one restore that works but after it completes it reboots back in recovery.
Click to expand...
Click to collapse
Turn on your tablet, let it boot into CWM.
Open cmd, cd to the directory with adb (for example cd C:\android), then copy this line of text below and right click > paste in the command prompt window.
adb shell dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=1 count=13
Click to expand...
Click to collapse
That should get you out of CWM into Android, assuming your restore works fine.
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
can i fastboot push a rom to the internal sd card or better yet can i install a rom from the external SD card via Clockwork mod recovery?
birchnick10 said:
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
Click to expand...
Click to collapse
Navigate to %android sdk folder%\extras\google\usb_driver, open android_winusb.inf and copy the following in the sections
"Google.NTx86" and "Google.NTamd64"
; TF201
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D01&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_0B05&PID_4D03&MI_02
;
; Fastboot for all projects
%SingleBootLoaderInterface% = USB_Install, USB\VID_0B05&PID_4DAF
Click to expand...
Click to collapse
Save the file and then try running the adb command I gave again.
Says error device not found. I appreciate the help keep it coming it's keeping my hope alive. I really hope this isnt truly hard bricked.
I cant get ADB to read the transformer prime. When I type adb devices nothing shows up . it starts the daemon successfully but then doesn't show the tfp.
Thank you again for helping. I am honestly going to pay who ever finds the true fix. This stress sucks
birchnick10 said:
Says error device not found. I appreciate the help keep it coming it's keeping my hope alive. I really hope this isnt truly hard bricked.
I cant get ADB to read the transformer prime. When I type adb devices nothing shows up . it starts the daemon successfully but then doesn't show the tfp.
Thank you again for helping. I am honestly going to pay who ever finds the true fix. This stress sucks
Click to expand...
Click to collapse
Try the instructions here. Try using this only as a last-ditch resort.
it wont shut off either... i tried both of the above mentions and cant get adb to recognize the prime
Attempted both and stuck at recovery loop without root. any more ideas? is it possible to flash rom from external sd? or is there a recovery I could fastboot rhat has this feature?
Attempted both and neither work. I need to somehow get usb debugging enabled while in clockwork mod. Or figure out a way to install a rom via external SD card while in CWM. Any more help is appreciated!
birchnick10 said:
Attempted and got error device not found.
I have uninstalled the transformer drivers and also installed the universal drivers as said in other threads.
I assume to use ADB i need usb debugging on for it to read??
My issue is I cant get into any rom so turning on usb debugging is a no go.
Click to expand...
Click to collapse
No adb debugging is needed in cwm. Even without any ROM installed. Recovery is different from Android.
Try to long press power (at least ten seconds) to hard reboot, and see if it changes something in device detection.
Did a hard reset and it boots me back into Recovery.
I was able to get a new rom into the internal SD via the emergency/backup.zip method but after it completes and I do a reboot it just boots right back into recovery again.
Any help please is apprecaited.
$5 bounty for a fix via paypal
Oh joy. This one is a spaghetti western in the making.
Okay. Question first : Does Windows 7 RECOGNISE the device in any way shape or form. To find out if this can be done, you need to power up the device and hold the power and volume down buttons, DO NOT press volume up when it suggests a kernel image. If you get three icons, hit vol down once and up once, then plug the USB cable into the PC and the tablet.
If it sees "Something", you've a chance. Download the naked universal USB driver from the dev forum, install it and have your device pick it up on the windows computer. I'm assuming from your comments that you've GOT a working fastboot and adb so I'm going to skip the instructions on that.
If you do have a something, and it's recognised, hit fastboot -i 0x0b05 reboot, if it reboots of it's own accord at this point, you can confirm you have working ADB and Fastboot access. From there you've a few choices. My personal preference would be to ADB push a rom down -after- doing a rebuild of the recovery image via fastboot (I really recommend TWRP for this bit).
http://forum.xda-developers.com/showthread.php?p=26093546#post26093546 - This post here which I wrote will explain how to flash TWRP from fastboot access, presuming you can get it. Once that step is done, wipe EVERYTHING from TWRP, and I mean the whole nine yards, including /system. Raze the memory down to only things it can't actually nuke. Once that's done, reboot to fastboot protocol, get a ROM pushed via ADB and install from inside TWRP.
That -should- get you back in business. Though judging by the tangle you're in, I make no promises.
ADB wont recognize the device. I have installed and uninstalled the drivers about 5 times.
It wont boot into fastboot - just goes directly into Clockwork Mod recovery. Even while holding power and volume down text comes up that says looking for asus recovery. then says clockwork recovery and boots directly into that.
The only way I can get anything into the internal SD card is with MasterZen88's Emergency script tool that puts any 1 file into the internal SD card as backup.zip
It was unrooted prior to all of this as well.
*cringe*
If ADB isn't working -at all- and it's not using the naked USB drivers to get you any kind of workable access. You're starting to smell very much like a hard brick scenario. I'm honestly not sure if there's a way out of that. A lot of the solutions for unbricking absolutely require that the device is able to talk to the outside world, if it's not and the ADB shell is essentially telling you it's talking to dead air, you're in a world of pain.
It's a long shot but it may be worth speaking to ASUS to see if they are willing to, for a fee, restore your tablet to factory settings. Though I can't imagine that will be cheap or simple. If you are able to get an RMA or a means of getting ASUS to poke it, make sure to take photos. Their techies appear to have the worst case of butterfingers in the world.
Go over Pandaball's suggestion, because that's really the last step I can think of before contacting ASUS
Hello guys, I'm here because my TF201 seems to be bricked ...
I know, there is a lot of threads about this kind of problems, but I can't succeed to solve mine by reading hundred of threads.
I explain what's happened :
My TF201 has an unlocked bootloader (by asus method), root, and has a CWM (CWM-based Recovery v5.5.0.4). I was on the lattest ICS build (9.4.2.15). Since october, i know that JB was on TF201, but not mine. So I decide to download the lattest Stock JB version from Asus website and to place it into my SDcard. I reboot my TF201 in recovery (holding down the volume button, then up), I've done a backup. After this backup, I've done a factory reset and I install the new ROM from my SDcard. Maybe I should not do this ... But now, my tablet stay on the bootscreen (Asus EEE pad logo). I can always access to the recovery, so I tried to factory reset and restore my previous backup ... But it didn't work, my tablet still bricked.
So, I went to google, i've read lots of threads for trying to understand whats happened to my TF201. I've read some thread on XDA forum too.
I've tried every solutions proposed, and anyone work.
I've read some articles about ADB. I installed it, but the problems is that my TF201 can't be detected by my computer (Running Win8 64). I installed drivers from here : http://forum.xda-developers.com/showthread.php?t=1379875
But, still nothing, impossible to show my device when I write "adb devices" or "fastboot devices" in windows cmd.
I'm a little bit desesperate, so i came here for writting this thread, hopping that someone could help me to unbrick my TF201 without send it back to Asus (wich cost me hundreds of euros).
I'm going in front of some questions that i've read in other thread :
No i've not TWRP recovery installed.
I haven't got a nvFlash.
Thanks for reading this thread and for your help !
Sincerelly,
Thrakka.
PS : I'm really sorry for my bad english, don't blame me ^^
You can access recovery?
Then you are not bricked.
Why not flash a custom rom?
Garret said:
You can access recovery?
Then you are not bricked.
Why not flash a custom rom?
Click to expand...
Click to collapse
Primarily because he has cwm recovery and jellybean bootloader. He does not know how to set up his drivers on his computer for fastboot to install the correct recovery for his bootloader.
to the OP, go here http://forum.xda-developers.com/showthread.php?t=1615990 and figure out how to get twrp for jellybean on your prime. TWRP supports flashing roms from the microsd slot so you dont need to push one to your sd. also if you need help getting the naked drivers to work on your prime go the link http://forum.xda-developers.com/showthread.php?t=1426502 that pertains to others putting it on the prime. they will be more help than the galaxy naked drivers users. FORGET ABOUT CWM!!! IT IS NOT SUPPORTED ON PRIME FOR JELLYBEAN
@ Garret
Yes I can access to recovery, but for flashing a new rom, I need to access my internal SDcard ... But infortunatelly, now I can't.
A thing that I don't understand is when I restore my ICS backup, it doesn't work ...
@ Whycali
I'm gonna try your advice this afternoon.
But how can I install TWRP on my prime without access ... I'm will try with your links ... Hoping succeed ...
I'll give you the results in the evening.
Sincerely,
Thrakka.
I can access to the fastboot mode, but impossible to flash anything ...
I've taken all driver for the prime on my computer, install them.
the command "fastboot devices" work, i can see my prime : 00000 fastboot
but when I try the command "fastboot -i 0x0b05 flash recovery twrp.blob" from www{dot}teamw.in/project/twrp2/93, the result : error: cannot load 'twrp.blob' : No error.
I can't understand.
The directory "/platform-tools" from the ADT is in the PATH variable, and the file "twrp.blob" is in the same directory. Two ways for the fastboot command to find it, but it can't succeed ...
Same problem when I want to create my own nvflash blob file (tuto from androidroot.mobi/t3_nvflash/) with the command "fastboot -i 0x0b05 flash staging ebtblob.bin", the result is the same : error: cannot load 'ebtblob.bin' : No error.
I can't see my mistake ... Could you help me ?
Sincerely,
Thrakka.
PS : as i'm a new member, I can't post direct link to other site where I found tutos, sorry ...
Thrakka said:
I can access to the fastboot mode, but impossible to flash anything ...
I've taken all driver for the prime on my computer, install them.
the command "fastboot devices" work, i can see my prime : 00000 fastboot
but when I try the command "fastboot -i 0x0b05 flash recovery twrp.blob" from www{dot}teamw.in/project/twrp2/93, the result : error: cannot load 'twrp.blob' : No error.
I can't understand.
The directory "/platform-tools" from the ADT is in the PATH variable, and the file "twrp.blob" is in the same directory. Two ways for the fastboot command to find it, but it can't succeed ...
Same problem when I want to create my own nvflash blob file (tuto from androidroot.mobi/t3_nvflash/) with the command "fastboot -i 0x0b05 flash staging ebtblob.bin", the result is the same : error: cannot load 'ebtblob.bin' : No error.
I can't see my mistake ... Could you help me ?
Sincerely,
Thrakka.
PS : as i'm a new member, I can't post direct link to other site where I found tutos, sorry ...
Click to expand...
Click to collapse
on your pc you need to run the command from the same directory that contains the file you wish to transfer. easiest way to do this is to place the blob in the folder where your fastboot application is then hold shift and right click inside the folder. from the menu that opens choose open command window here. from there run your fastboot commands.
---------- Post added at 12:37 PM ---------- Previous post was at 12:02 PM ----------
hey, hold up and check your pm. Do not install TWRP for jb if you are still on the ICS bootloader.
you can check which bootloader version of twrp to install by where the nvidia logo is on the bootscreen. bottom center needs ics twrp. bottom right needs Jellybean twrp. By all means if you are still with ics finish the nvflash backups first.
867-810 Eecuri
Little update for the post :
I succeed all this steps, I've TWRP for ics now.
I'm looking for an ICS Rom for install it.
What could I do if I want to have a JB ROM ?
Thrakka said:
Little update for the post :
I succeed all this steps, I've TWRP for ics now.
I'm looking for an ICS Rom for install it.
What could I do if I want to have a JB ROM ?
Click to expand...
Click to collapse
Follow the instructions fully in the second post of the androwook thread for upgrading from ics.
All problem are solved !
Thanks Whycali for your precious help !
I've installed the AndroWook ROM, and it's a real pleasure !
Good Job man, I was travelling, just saw you made it
Thank you Garret ;D
It was not as bad as i was thinking before posting this thread !
Just compatilibity problem between a JB rom with ICS bootloader and ICS recovery ^^
senior member, can you help me with this problem ?
http://forum.xda-developers.com/showthread.php?t=2263137
Help with tf201
Hey all,
To start I have a bricked tf201. i was following a Youtube tutorial to update my twrp. i followed the instruction diligently. I was running CM 10.1 on the tf201. After the Install I rebooted and now it boot loops. if i hold vol down + pwr button it looks for revovery kernel and then fails. if i hold Vol up + pwr button it vibrates and black screen assuming this is apx mode. i followed ever tutorial on apx and i can't get anything to work. is there any hope for this tablet? Thanks in advance!
bricked tf201 too
bucknerspc said:
Hey all,
To start I have a bricked tf201. i was following a Youtube tutorial to update my twrp. i followed the instruction diligently. I was running CM 10.1 on the tf201. After the Install I rebooted and now it boot loops. if i hold vol down + pwr button it looks for revovery kernel and then fails. if i hold Vol up + pwr button it vibrates and black screen assuming this is apx mode. i followed ever tutorial on apx and i can't get anything to work. is there any hope for this tablet? Thanks in advance!
Click to expand...
Click to collapse
I have the same issue. Only a black screen on VolUP+Power or The Device is unlocked on VolDown+Power. I can't do anything, the usb driver is not reconize and fastboot or adb shows anything. Please any help to recovery?
Thanks in advance
Another Bricked tf201
Aduniel said:
I have the same issue. Only a black screen on VolUP+Power or The Device is unlocked on VolDown+Power. I can't do anything, the usb driver is not reconize and fastboot or adb shows anything. Please any help to recovery?
Thanks in advance
Click to expand...
Click to collapse
Hello Aduniel: I have essentially the same issue with my tf201. It seems to be hard bricked? (My guess.) If I reboot with Volume Down and Power button, I get a message "This device is Unlocked" in upper left of screen. Also large lettering in center of the screen, "ASUS" and "nNidea Tegra 3" in the lower right.
If I boot with Volume Up and Power button, I get a blank, black screen. (APX mode).
I have set up ADB and naked drivers on a notebook running Windows 7. When I try to connect via fastboot, I get a message <waiting for device>. But it does not connect.
I was wondering if you managed to get your tablet working since Nov. 2013? If so, what did you have to do? I need to know if there is any hope, or have I shot myself in the foot, as they say.
Cheers man,
Jim
Hard Brick TF201
JRKirkey said:
Hello Aduniel: I have essentially the same issue with my tf201. It seems to be hard bricked? (My guess.) If I reboot with Volume Down and Power button, I get a message "This device is Unlocked" in upper left of screen. Also large lettering in center of the screen, "ASUS" and "nNidea Tegra 3" in the lower right.
If I boot with Volume Up and Power button, I get a blank, black screen. (APX mode).
I have set up ADB and naked drivers on a notebook running Windows 7. When I try to connect via fastboot, I get a message <waiting for device>. But it does not connect.
I was wondering if you managed to get your tablet working since Nov. 2013? If so, what did you have to do? I need to know if there is any hope, or have I shot myself in the foot, as they say.
Cheers man,
Jim
Click to expand...
Click to collapse
Hello Jim,
I have the same problem.
I kan also do APX mode but nothing wil work.
If i type apd devices: there is nothing displayed.
Also when I try to flash, it says: waiting for device.
I only once had connection with easyflasher and it saw the TF201: Chipuid: 0x98243044050469391, but later one nothing happend.
I waited for 45 minutes and stil, nothing was done.
I hve been disperate, so can anyone help us, Plaese.
Th TF201 is now dead since oktober 2013, ppfffffffffffffffffffff
Thanks. greetings 5079
Hello everyone, been a lurker for some time, but have never needed to post before until today. I'm accustomed to rooting and installing custom roms but I've never had anywhere close to as much difficulty as Im having with this tf201. Heres the situation:
Not sure if you'd call this bricked, as I have total access to fastboot, adb, and CWM Recovery (version 5.8.3.4 touch btw). However my most recent attempt ended with totally wiping from the volume down+power menu (whatever its called). I can not turn the tablet off, as it automatically boots to the asus splash screen (and goes no further, naturally). It is unlocked, and my drivers do work (both fastboot and adb recognize the device), but I can not flash or push anything to the sdcard (with adb its a protocol failure, with fastboot I get "sending zip....OKAY writing zip....FAILED [remote : [FileOperationFailed]]) Don't know if it needs to be said, but I also can't simply drop the file on the sd card as if it were a media storage device as "my computer" does not recognize that it is connected (Oh I am using the naked universal drivers from http://forum.xda-developers.com/showthread.php?t=1998650 )
So yeah, Im at a loss as it seems like no one has had this particular problem before (also my connector cable works fine, so its not that). Any help would, of course, be greatly appreciated.
EDIT: On the tablet after trying to flash with fastboot it returns "Failed to process command flash:zip error (0x30003)"
Really? Not a single person has any idea? Could really use some help here...
GrimAgent said:
Really? Not a single person has any idea? Could really use some help here...
Click to expand...
Click to collapse
You do not flash zips with fastboot.
First of all tell me where your "NVIDIA" logo is when you first power on, bottom center or bottom right?
The nvidia logo is in the bottom center of the "EEE PC Splash"
This is going to sound stupid, but did you verify the MD5 before you tried to flash it?
GrimAgent said:
The nvidia logo is in the bottom center of the "EEE PC Splash"
Click to expand...
Click to collapse
You are still on the ICS bootloader if NVIDIA is bottom center.
Go here http://www.teamw.in/project/twrp2/93 and follow the instructions for "Download - Recovery Image / Fastboot Method (using ICS or JB Asus bootloader)"
You will need to get the ICS blob file. Never flash the wrong recovery for what bootloader you are on or you can brick your device.
If you get it working and you want to upgrade to Jellybean bootloader there is instructions in post 2 of the Hairybean Rom thread. "Upgrade instructions for ICS"
edit.. to make it a bit easier for you.
Get this file http://techerrata.com/file/twrp2/tf201/openrecovery-twrp-2.4.4.0-tf201-ICS.blob
Rename it to twrp.blob
Place the twrp.blob in the same folder as your fastboot exe
Go into fastboot and type
fastboot -i 0x0b05 flash recovery twrp.blob
Wait for it to finish and then type
fastboot -i 0x0B05 reboot
see if that works.
Damn, I had a feeling it was the bootloader issue that I messed up. I went searching all over for how to find out which one I had once I realized my potential mistake. Gonna give these steps a try
I just tried all your steps, twrp is on there and I was able to push both cm10 and gapps onto the tablet, but now the zips I pushed to the sd card arent showing up in TWRP...
GrimAgent said:
I just tried all your steps, twrp is on there and I was able to push both cm10 and gapps onto the tablet, but now the zips I pushed to the sd card arent showing up in TWRP...
Click to expand...
Click to collapse
If you now have twrp on there you dont need to push a file. Place the file on an external SD card on the root and plug it in before starting prime.
When going into TWRP go into install and select external SD. Pick your rom and then flash it.
Thanks a lot flumpster, everything's good now and Ive got cyanogen up and running smoothly. You've brought my tablet back to life and Ive learned a valuable lesson
This happened to me a while ago but I am revisiting the problem now. In the recovery menu, I think I accidentally erased all the portions and that is where I got my problem. If I boot into the tablet, it doesn't go past the Eee pad splash screen. If I try to enter recovery it just gets to entering recovery image and is stuck there and same for fastboot. Is there anyway to fix this by sideloading or something or did I brick my device?
HuskyHamburger said:
This happened to me a while ago but I am revisiting the problem now. In the recovery menu, I think I accidentally erased all the portions and that is where I got my problem. If I boot into the tablet, it doesn't go past the Eee pad splash screen. If I try to enter recovery it just gets to entering recovery image and is stuck there and same for fastboot. Is there anyway to fix this by sideloading or something or did I brick my device?
Click to expand...
Click to collapse
If you can enter the bootloader, the OS, recovery or you have your nvflash backups then you have a chance.
If you can access none of these then you are hard bricked.
Tried Ubuntu Dual Boot: bootloop/brick; but fastboot, apx, and adb access OK
Posting here because: there are varios "bricked" threads - none with exact problem as I find.
I have/had: Asus Transformer Prime tf201, ICS
Bootloader „DE_epad-9.4.2.21-201203023“ A03
Rooted with motochopper
My Problem: Tried to install to Ubuntu Dual Boot using this: https://docs.google.com/document/d/1WfYcgH3FETUAGRbt_aBE5_J21CvTvXunVBdmfcCmtLA/edit?pli=1
after I had seen this video (link from descriptions) https://www.youtube.com/watch?v=QB9u6OKgop4.
Didn't work out since I could not do this step: "Mount the micro SD-card in Better Terminal on your TF201 by typing this..."
But I continued despite the bad signs!
Then, after using Fastboot to flash the .blob from above → bootloop.
And: no nvflash installed; yes stupid me, I know.
Then tried a lot, searched XDA and Androidforums -can't quite remember all.
Edit: Also tried Urkel's Fresh start.
Only: After trying to flash a stock ASUS ROM via Fastboot I could not even enter the recovery.
(Read later that you should NEVER do this in this state: http://forum.xda-developers.com/showthread.php?t=1514088,
I might even have taken the wrong version to do so.)
Also tried installing a TWRP recovery, but it didn't work.
It doesn't even perform its bootloop anymore, it is simply
stuck on the first screen showing the EEE logo and „device unlocked“.
Then I found http://www.transformerforums.com/fo...nbrick-your-tf201-using-method-hopefully.html
and managed to get to the point where I am now:
Access via Fastboot, ADB and APX (I also have a Win7 64bit partition on my Laptop, but since in ADB the prime doesn't show up I only use Linux 32bit).
Recovery: ClockworkMod Recovery v5.8.2.0 working.
BUT the problem is: error: can't mount /sdcard
Tried formatting via CWMR, it does something (no output) but can't mount /sdcard or /data anyway later.
It seems that I can push file via ADB: did so with a Cyanogenmod.zip to /sdcard, pushed successful,
but since I can't mount via CWMR its useless. After Rebooting the prime no changes.
I wanted to install Ubuntu to learn with it – guess is have learned a lot by bricking my pad...
I really love my prime, we used to cuddle and had a nice time. But now since it doesn't respond properly anymore I feel empty and sad.
Does anybody have a clue how to revive it? Thank you.
AnotherBrickInTheWall said:
Posting here because: there are varios "bricked" threads - none with exact problem as I find.
I have/had: Asus Transformer Prime tf201, ICS
Bootloader „DE_epad-9.4.2.21-201203023“ A03
Rooted with motochopper
My Problem: Tried to install to Ubuntu Dual Boot using this: https://docs.google.com/document/d/1WfYcgH3FETUAGRbt_aBE5_J21CvTvXunVBdmfcCmtLA/edit?pli=1
after I had seen this video (link from descriptions) https://www.youtube.com/watch?v=QB9u6OKgop4.
Didn't work out since I could not do this step: "Mount the micro SD-card in Better Terminal on your TF201 by typing this..."
But I continued despite the bad signs!
Then, after using Fastboot to flash the .blob from above → bootloop.
And: no nvflash installed; yes stupid me, I know.
Then tried a lot, searched XDA and Androidforums -can't quite remember all.
Edit: Also tried Urkel's Fresh start.
Only: After trying to flash a stock ASUS ROM via Fastboot I could not even enter the recovery.
(Read later that you should NEVER do this in this state: http://forum.xda-developers.com/showthread.php?t=1514088,
I might even have taken the wrong version to do so.)
Also tried installing a TWRP recovery, but it didn't work.
It doesn't even perform its bootloop anymore, it is simply
stuck on the first screen showing the EEE logo and „device unlocked“.
Then I found http://www.transformerforums.com/fo...nbrick-your-tf201-using-method-hopefully.html
and managed to get to the point where I am now:
Access via Fastboot, ADB and APX (I also have a Win7 64bit partition on my Laptop, but since in ADB the prime doesn't show up I only use Linux 32bit).
Recovery: ClockworkMod Recovery v5.8.2.0 working.
BUT the problem is: error: can't mount /sdcard
Tried formatting via CWMR, it does something (no output) but can't mount /sdcard or /data anyway later.
It seems that I can push file via ADB: did so with a Cyanogenmod.zip to /sdcard, pushed successful,
but since I can't mount via CWMR its useless. After Rebooting the prime no changes.
I wanted to install Ubuntu to learn with it – guess is have learned a lot by bricking my pad...
I really love my prime, we used to cuddle and had a nice time. But now since it doesn't respond properly anymore I feel empty and sad.
Does anybody have a clue how to revive it? Thank you.
Click to expand...
Click to collapse
Shoot me an email here [email protected]
We can get you going and than post our finding back here to help everyone out...
Thx Josh
Hey Everybody!
I am new to this forum, looking for a way to root my trekstor Surftab breeze 9.6 Quad. I already tried out the recommended tools, unfortunately none of them worked out. Is anyone of you aware of a method rooting the tab? Or did anyone already rooted it?
First ofall I am looking for a way to move files and apps to the external sd and delete pre-installed apps. Farther, if possible and available, a custom rom would be pretty amazing.
I'm only familiar to nexus root toolkit on my old nexus 4, otherwise I'm a newbie in rooting.
Maybe there's some of you able to help me. If necessary, I will look up more information on the tablet.
Lucas
Maybe as an Update:
Trying to build a working adb connection using the andorid sdk tools, the surftab is not listed as a device in "adb devices"
Anyone out there who can help me with the tablet?
Alright, new update for today.
I was able to get a driver running and the root-toolkits like KingoRoot, KingRoot, One Click root etc. noticed the device, I even was able to start the rooting, but all of those tools said "Root failed" or "Your device is soild to root".
Looks like those one click solution aren't able to root the surftab. I also tried towelroot and framaroot, both without any success.
I am still looking for help
If you are still interested, I successfully dumped whole eMMC memory from this tablet, so I can send you, for example, the boot partition. You can try patch it with Magisk
The magic
Yes, if it's not difficult for you, you can share the firmware. I will be grateful
Hi!
I attached xz-compressed stock boot.img for you!
Also, I have full eMMC dump, but:
recovery partition data are not usable (overwritten by uncompatible recovery image during mine tests)
no data partition
no platform bootloader partitions mmc0boot0 and mmc0boot1
Trekstor-Surftab-Breeze-9.6-ST96416-1-emmc-dump.dd.xz [1.12 GB]
Decompress and use kpartx tool (need force to ignore omitted data partition)
I have this tablet rooted now, so you can ask me for anything about it.
With love for all open source,
petabeda
Just one thing: fastboot boot is not supported here, so If you are afraid, flash modified boot.img to recovery partition with fastboot flash recovery boot.img for test (adb reboot and then adb reboot recovery
You will lost your recovery, but, at least, no bricked device in case of error (recovery is actually second boot partition)
petabeda said:
Just one thing: fastboot boot is not supported here, so If you are afraid, flash modified boot.img to recovery partition with fastboot flash recovery boot.img for test (adb reboot and then adb reboot recovery
You will lost your recovery, but, at least, no bricked device in case of error (recovery is actually second boot partition)
Click to expand...
Click to collapse
I have two surftab tablets. One version of the SIM card is fully functional. Another wifi version will not load. When loading, the orange logo at the moment of "collection" freezes. If there is, you can go into recovery even factory reset.
But nothing changes. I believe that the EMMC resource has been exhausted and therefore this behavior.
and to be honest, I don’t know how to write the partition. Since only the adb sideload command is available in recovery mode. Apparently, it is impossible to overwrite the firmware except through the programmer.
Until that time, I could not even pull out the firmware. Since there was no root access
Thank you for your help. As a thank you, I will give you a link to a tool to repair the Nexus 7 bootloader. Through a vulnerability in the tegra cpu. As I understand it, I use this method to hack the nintendo switch. I personally bought 4 nexus 2012 on the secondary market and one of them was able to restore in this way. They of them had a damaged eMMC other power controller. And even with a soldering station, I could not replace it because there is no suitable frame for the reball. In general, nexus are not bad, but there is very little disk space for installing google services and GAPPS are useless. And it is difficult to change partition. And it makes no sense because of the available firmware.
I see, you can''t unlock bootloader, because your device is not bootable at all. So, there is no way to get into fastboot mode?
We are anti e-waste fighters giving second chances!
The first photo is the available recovery menu. Where after choosing a factory reset, nothing changes. And through the adb update, only sideload mode is available.
The factory partition is not corrupted as the restore completes successfully. But the download fails. And not just does not occur, but freezes as in the screenshot above. Most likely a hardware problem eMMC.
Earlier, I saw something similar, for example, in Asus Zenpad, if turn off or connect the camera incorrectly, then the download stops. But here animation is stuck.
I don't know how to check eMMC exactly.
logs files is empty
And with recovery, no commands are available (like adb or fasboot)
There is a one way how to diagnose/repair/have fun with that Trekstor tablet - If you could and want to disassemble it:
have your tablet powered off
disassemble the tablet
carefully disconnect FFC cables (display and digitizer)
remove mainboard screws
at back side in the center of the board, there are three testpoints.......yes you are thinking right, these are actually 1.8V UART signals and GND
Connect these signals to your serial converter (in my case, Raspberry Pi), be careful and talk with the same loundnesses
Don''t power on the tablet, only plug usb cable, tablet will try boot and run healthd (charging mode with battery animation)
Your console will show you the magic (PBL/SBL) bootloader messages and Linux log and event, maybe, the console (though no root), lalalal (/dev/ttyFIQ0)
Wish you luck
After that, if everything goes well, you should be able to use reboot fastboot command to get fastboot mode !