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
Related
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.
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
"""I recently updated my TF300T to JellyBean 4.2.1. That worked fine. I then wanted to see if I could root this version. I tried 4-5 different custom recoveries, including multiple TWRP and CWM versions. Although they were able to boot to the custom recovery, they could never mount any of the data on the tablet, so I wasn't able to flash any custom roms or root my device. Anyway, I finally installed the latest CWM for the TF300 on JellyBean (6.0.3.1 or something). I still could not mound any tablet data from the recovery. Although installing any of this on a brand new 4.2.1 was incredibly stupid, it gets worse...
I thought that maybe if I did a "wipe data" on the device I would be able to mount it. I then got stuck in a situation in which the tablet would only boot to CWM recovery. I didn't even press the volume key- it would simply go directly to the recovery. This was useless, to say the least, as I could not flash anything or do anything from this.
I then found a way to actually boot into my transformer- I used my PC and typed "adb reboot-bootloader". This gave me the option to cold boot and get into the tablet like normal. However, any subsequent reboots or power-offs would require PC intervention and a cold boot in order to boot into the tablet. This wasn't convenient, although I admin it is much better than where I am now.
I tried multiple times to flash a new recovery, and the same CWM stays on the system. I cannot for the life of me get this stinkin CWM recovery off my device! I ended up trying to wipe my system again, and now I'm absolutely stuck. I can only boot into recovery if I don't do anything on the PC. I can get into fastboot by using a PC, but that's about it. I can't boot into the system after fastboot, and recovery has no rights to change any files.
I can run commands to write new recovery, system, etc using adb, and it sends the file, "writes" it unrealistically fast, and then just says OK as if it was complete. The screen on the tablet doesn't change at all during this, other than the fact that the blinking box for the Fastboot options becomes solid. I have let it sit there for 10-15 minutes and it simply does nothing. (The last attempt was "fastboot -i 0x0B05 flash system blob" where the blob file was the one from the most recent stock firmware download from ASUS.com.) I then have to manually reboot the tablet using the power button, and the whole cycle starts over again.""" I didn't feel like writing all this out so I'm plagiarizing; kill me if you like. I did exactly what he did and got things working the way he did.
Recently though I wiped my hard drive to start a clean windows 7 from scratch and I can't figure out how to get the drivers installed on my computer. As Asus hasn't published them from what I can find and I haven't gotten the android sdk manager to do anything past flashing cmd prompt for a millionth of a second. I basically just need help with the drivers, so any help would be very appreciated. I haven't found anything so far looking through the forums that has helped by the way. I haven't been able to find any threads with solutions yet...
I used the asus pc sync package for the tf300t from asus's website since the tf300tg did not want to download, in any case that with the new google sdk works for me.
Also I noticed issues using anything but twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob when it comes to mounting and backups this is the only one that i tried that worked so far.
Hello everyone,
While trying to update TWRP on my Prime I was not paying enough attention and went backwards from 2.7 to 2.6.3.0 and have no OS now.
I can boot into recovery which would be great except I can not seem to get it to mount or recognize my SD card to load a ROM from that.
I can get it into Fastboot mode by typing "adb reboot bootloader" and I can send commands to it while in Fastboot mode, but I can not seem to find a way to send an OS to it through that mode. I have tried loading a ROM by flashing it through Fastboot, but I get errors that "archive does not contain 'android-info.txt" and "archive does not contain 'android-product.txt."
Bummed right now as I had been running KATKISS and liking it and was going to try out Zombi-Pop which is when I was trying to update TWRP and everything fell apart on me.
Any help would be greatly appreciated.
I did find this thread:
http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495/post54965562#post54965562
Mine boots straight into recovery, but I can get it back to fast boot by connecting it to my computer, opening a command prompt, and typing "adb reboot fastboot" which takes me to fastboot. I was going to follow the directions in the thread but the SKU I have is WW_epad-10.6.1.27.1-20130711 and I don't see that on the list for the firmware. I think that is because I had run the "upgrade tf201 to tf300" a long time back when I was putting CROMBI-kk on it from this thread:
http://forum.xda-developers.com/showthread.php?t=2773812
A little more info as I am searching around and trying things. If I try to flash a twrp.blob to it, the computer says it is successful, but there is no blue bar on the table, the tablet is unresponsive, and the computer doesn't see it anymore. I can long press the power button which boots the table straight into recovery and reconnects it to the computer. I can then run "adb reboot bootloader" which restarts the tablet and puts it into fast boot mode.
Skates97 said:
A little more info as I am searching around and trying things. If I try to flash a twrp.blob to it, the computer says it is successful, but there is no blue bar on the table, the tablet is unresponsive, and the computer doesn't see it anymore. I can long press the power button which boots the table straight into recovery and reconnects it to the computer. I can then run "adb reboot bootloader" which restarts the tablet and puts it into fast boot mode.
Click to expand...
Click to collapse
Get yourself into fastboot mode.
Now follow the instructions here http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
But where he says to get the TF300 firmware etc get the TF201 instead.
flumpster said:
Get yourself into fastboot mode.
Now follow the instructions here http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
But where he says to get the TF300 firmware etc get the TF201 instead.
Click to expand...
Click to collapse
I'll try it. One more question, on the Asus site it lists a bunch of different firmware for the TF201. In my bootloader it lists it as the "WW_epad-10.6.1.27.1-20130711" which I think is from when I made the TF201 to TF300 change.
So... any idea which firmware I would download, or is there a way of getting that information from my tablet without actually getting past Fastboot? It was purchased in the US so I was guessing the latest one for a US SKU?
Thanks
Edit: Should I use the blob from the HairyBean bootloader that I had previously installed?
Fixed
Thank you so much for pointing me to that thread.
I tried the latest US firmware off the Asus site 10_4_2_18 and it installed but when trying to reboot I just got the dead Android guy with the red triangle. So, I reset it and went back into Fastboot and tried the procedure with the blob from the Tf201 to TF300 zip and it booted up to the HairyBean recovery but still a no go on anything any further. So, I guess third times the charm. I reset and went back into Fastboot and ran the procedure with the 10_4_2_17 firmware from the Asus site and that one worked. I am back up and running, just need to work my way back up the line so I can give Zombi-pop another try.
Again, thank you for pointing me in the right direction!
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 !