Database Info

Unbrickable tf300t

Hello everyone. I am new around here and totally new with android devices. I got my tf300t, installed twrp and flashed to the newest android version. Then my dad suddendly pressed something like restore to the manufactory setting and after that it rebooted and just keep booting with teamwin logo. I can not access twrp recovery mod, it is just in boot loop. I managed to get adb to work, but no fastboot since it does not boot into recovery mode. When I am in adb I can browse the device but the adb reboot bootloader does not work at all. It just hangs there. I can not power off the device because it does not let me, I can not boot into recovery mode with powerbutton and volume down button. After a long power button press it only reboots. I even tried with hard reset button but still the same. Could You please help me somehow? I really need that device for school and I would like to get back into the stock android. Thank you so much for any help.
//edit : I also forget to mention, when I execute adb deviced it shows:
List of devices attached
0123456789ABCDEF recovery
Also the device is unlocked.

Did you tried: adb reboot recovery ?
Did you tried to flash recovery again?
Be sure to use the right recovery for your bootloader. Did you upgraded bootloader to latest ASUS one? One then you're able to flash current recoveries like TWRP like 2.8.5.0 oder 2.8.7.0.
Edit: Also take a look here -> http://droidmodderx.com/prime/?page_id=74

Hello sir. Thank you for answering. I tried adb reboot recovery and it just hangs to be executed... But the tablet is still flashing the teamwin logo. I have the same bootloop as the guy on youtube called Francis Domingo and video called Samsung s5 stuck at TWRP Recovery boot loop (unfortunately I can not add link here).
//edit: Thank you for the link. It look like I have to use option 1a. Is it safe to use that command and I will not make it even more bricked? Thank you so much
//edit2: Now I just realized how to turn off the device to stop from rebooting. I just long pressed power button and up volume button and after the screen went black I kept holding the up volume button. I didn't work with down volume button or if I stopped holding the up volume button after black screen it rebooted again.
//edit3 : Let's say if I get to the twrp mode with option 1a from the link, what do I have to do next to get back to the stock rom (I think it was something like 4.0.3) ? Thank you

What the guy does in 1a is wiping mmcblk0p3.
Afaik mmcblk0p3 is the staging partition. That would be my guess anyway if you had access to fastboot. Usally when you can't boot into recovery, something is wrong in staging. I got the same problem 2 days ago. In this case you usually wipe staging partition via fastboot.
Since you got no fastboot access, you have to try with adb.
After cleaning the staging partition you can flash any recovery you want back again.
The recovery must be flashed to mmcblk0p4 <- 4!!! is the recovery partition. (but you should wipe mmcblk0p3 (3!!!) before)
So I would say, try what solution 1a suggests.
Edit: You can go back to stock android if you want, but there is no reason for this. My advice would be to unlock and root your device, upgrade to latest boot loader (which is done by upgrading to latest stock rom), then flash TWRP 2.8.5.0 and then a useful ROM on top. I'm using the one from timduru which is very nice. You can find it here: http://forum.xda-developers.com/transformer-tf300t/development/rom-t2932783

Thank you for the answer. Could you please write a step by step to get out of brick and to get the stock version, because the newer one I installed was many times slower. The reason why I would like to have step by step is because I don't wanna mess it even more than it is. Thank you so much.
//the stock rom was much more faster than the one I have installed, I mean... the boot time wad unbelievable slow, same with responses and wifi problem. If there is any other faster rom than stock I would be happy but I don't wanna mess with any bugs or slow boot speed and I can not wait minutes until it boots.

Hm, try the Option 1a from the link.
If done, boot into current recovery. Tell me which version and which recovery do you have.
Top on this we can decide what to do to flash a good ROM.

I had the exact same thing happen to me yesterday. Option #1 worked for me.
I did the steps from option #1 and powered down using the volume up + power. I then tried to boot into TWRP recovery, which only reproduced the same issue.
I redid the option #1 steps, and this time powered down using the power + volume down. I powered back up normally, and it rebooted normally into the ROM.
The tablet now works normally, and I can also boot back into TWRP recovery with no issues.
Thanks for the thread and the link.

Thank you so much Catscratch! After I executed both command from option 1a I can get into the screen, where it shows three options: RCK, Android, Wipe Data
In the top left corner, there is written:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.27.5-20130902" A03
Starting Fastboot USB download protocol
The tablet can boot into the last ROM but as I said, I would like to have the faster and less buggy rom than this. When I open the settings and click about button there is written: CyanongenMod: 12.1-20150814-NIGHTLY-tf300t and Android version 5.1.1.
If I start RCK it just brings me back to the loop, but now I have fastboot available as it said above and I can list the fastboot devices on computer, which I couldn't before. Should I just execute this command from the computer "fastboot -i 0x0B05 flash system blob" and then "fastboot reboot" or should I download ROM from asus.com/Tablets/ASUS_Transformer_Pad_TF300T/HelpDesk_Download/ -> OS Android -> Firmware and now I don't know which should I choose: If JP or CN or WW or US or TW (Probably US right?). After that should I execute "fastboot -i 0x0B05 flash recovery firmware.img" and then "fastboot reboot" ? Or which ROM should I download to make it even faster and less buggy than stock ROM? Thank you so much again, You saved my tablet
//After I unzipped downloaded US ROM there is no img file. If I remember right the img file is only recovery to reflash the actual one and then when I start the twrp recovery I will select zip file with rom right?

OK, first of all to continue...I assume you got root access. (I think you should have, because you already got CM installed)
Next. Downloads.
Download: https://twrp.me/devices/asusTF300T.html
Also Download ROM+SuperSU: http://forum.xda-developers.com/transformer-tf300t/development/rom-t2932783
And GApps: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
Push all files to sdcard with "adp push" or in CM. Like you want.
Flash TWRP. (you can skip this step if you already got TWRP 2.8.5.0 or higher version). You don't need latest one.
fastboot -i 0x0b05 flash recovery twrp.img
fastboot reboot
- or -
adb reboot recovery
Now, go into recovery and wipe everything:
- cache
- dalvik
- system
- data
After that flash ZIPs from sdcard. (use "add more zips" option)
1. ROM
2. Gapps
3. SuperSU
Next: Wipe cache and dalvik again (only these two).
Reboot and wait. First boot can take some minutes.

Thank you so much again. Everything work perfectly The rom looks a lot faster than the older one I had there. No issues yet at all. Just awesome. Thank you so much. Really appreciate your kindness and help. You have a nice day !

Thanks. Have fun with your tf300.

Shield tablet wont boot beyond fastboot menu :'(

I hope you guys can help me, i have been wandering around blogs forums to find a fix to this issue but to no avail. I got my replacement tablet about a few month ago. I decide to keep the old one and install custom rom on it. The old one is still usable now, but the replacement tablet is dead to me. One day i restart the repl tablet and it just stucked at the fastboot menu. When i choose to go into recovery mode. Nothing happened except a blink of message said that cold linux booting failed. So i try to unlock bootloader to flash it using adb command. Now it wont let me unlock boot loader giving me an error same as the guy here ( i cant paste an outside link here, google : Shield Tablet (LTE) won't boot beyond fastboot, fastboot OEM)
Ps : sorry for bad english im from Malaysia and also im tech newbie

flash the official firmware, you shouldn't need the the bootloader unlocked to flash a signed nvidia package.
this should replace your recovery and system and get you up and running again.
if not, perhaps your NAND is corrupted or damaged.

DreadApex said:
flash the official firmware, you shouldn't need the the bootloader unlocked to flash a signed nvidia package.
this should replace your recovery and system and get you up and running again.
if not, perhaps your NAND is corrupted or damaged.
Click to expand...
Click to collapse
I have downloaded the firmware 3.1.1 2.3gb, but it still required me to unlock bootloader to use this command
Fastboot flash recovery recovery. Img
Fastboot flash boot boot. img
Fastboot flash system. Img
........
Would appreciate if you guys can guide me in this matter

RaybenBB said:
I have downloaded the firmware 3.1.1 2.3gb, but it still required me to unlock bootloader to use this command
Fastboot flash recovery recovery. Img
Fastboot flash boot boot. img
Fastboot flash system. Img
........
Would appreciate if you guys can guide me in this matter
Click to expand...
Click to collapse
Hi,
The "fastboot oem unlock" command don't work?

Elpatii said:
Hi,
The "fastboot oem unlock" command don't work?
Click to expand...
Click to collapse
Nope, also cant detect device using adb devices command. Tried same command in the other shield tablet, work just fine. Its not driver problem.
Tried fastboot oem unlock, and somehow it ask me on the shield to unlock or not, choose unlock and this error occured
(bootloader) Showing Options on Display.
(bootloader) Use device keys for selection.
(bootloader) erasing userdata...
FAILED (remote: (Unknown error code))
finished. total time: 3.736s

Maybe that you can flash the stock image from NVIDIA (https://developer.nvidia.com/shield-open-source)

Elpatii said:
Maybe that you can flash the stock image from NVIDIA
Trying to flash that one, still it require me to unlock bootloader. I think my chipset was damaged or fried. Have escalate this issue to nvdia, and it seems they want to do a replacement
Click to expand...
Click to collapse

RaybenBB said:
Maybe that you can flash the stock image from NVIDIA
Trying to flash that one, still it require me to unlock bootloader. I think my chipset was damaged or fried. Have escalate this issue to nvdia, and it seems they want to do a replacement
Click to expand...
Click to collapse
I think that's the best solution for now!

Bootloader relocked, no recovery or OS. Cant unlock bootloader.

So, i got my hands on what i was told hard bricked device. i have no idea what has happened to the device before. first thing i got my hands on it and it did boot to OPO logo. so no hard brick. more like soft brick. tried go to recovery but i cant. it wont go how much i try. booting in to fastboot gives only black screen but my pc will see it (qualcomm hs 6008 etc) where i am able to use oneplus recovery tool and install stock cm11s firmware to it. it goes thru and gives green but device wont boot BUT now i can get to fastboot mode. now it says fastboot mode instead of black screen. running fastboot oem device-info gives this result:
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
This tells me its tampered but relocked. running fastboot oem unlock says OKAY but just reboots my phone (i thing it should go to recovery to unlock it but it does not) after rebooting i cannot get to fastboot mode anymore. just black screen again and i need to run recoverytool again and same results on device-info so it was not unlocked.
ill try to add as much info as i can:
because i cant even get to stock recovery i cant access adb.
Drivers are ok (win 10 test mode etc)
recovery tool does something but cant fix.
flashing anything via fastboot wont write because locked BL
tried toolkits but same errors as commands manually
tried many unbrick guides but no luck (CM or ColorOS)
took boot.img from cm someone suggested but because of that lock i cant flash or boot it at all.
hoping someone could help me. i see much topics about same problem but no solution anywhere...

https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Maybe this will help
Or after getting fastboot to work, format every partition and reflash COS.

C4SCA said:
https://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
Maybe this will help
Or after getting fastboot to work, format every partition and reflash COS.
Click to expand...
Click to collapse
actually tried that already but no luck. tried again now and no luck still. stuck on 1+ boot logo.
cant format partitions because its locked. (Device not unlocked cannot flash or erase)
restoring coloros or cm12 does not fix bootloop

migidid said:
actually tried that already but no luck. tried again now and no luck still. stuck on 1+ boot logo.
cant format partitions because its locked. (Device not unlocked cannot flash or erase)
restoring coloros or cm12 does not fix bootloop
Click to expand...
Click to collapse
After these steps can u enter recovery? Tried to factory reset via recovery?

No i still cannot get to recovery no matter what i try. i never could. i can get to cm fastboot and coloros fastboot but no recovery at all. its like its missing. ive been tinkering with this phone for almost a week so ive been trying many times and many combinations but nope.

migidid said:
So, i got my hands on what i was told hard bricked device. i have no idea what has happened to the device before. first thing i got my hands on it and it did boot to OPO logo. so no hard brick. more like soft brick. tried go to recovery but i cant. it wont go how much i try. booting in to fastboot gives only black screen but my pc will see it (qualcomm hs 6008 etc) where i am able to use oneplus recovery tool and install stock cm11s firmware to it. it goes thru and gives green but device wont boot BUT now i can get to fastboot mode. now it says fastboot mode instead of black screen. running fastboot oem device-info gives this result:
"(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
This tells me its tampered but relocked. running fastboot oem unlock says OKAY but just reboots my phone (i thing it should go to recovery to unlock it but it does not) after rebooting i cannot get to fastboot mode anymore. just black screen again and i need to run recoverytool again and same results on device-info so it was not unlocked.
ill try to add as much info as i can:
because i cant even get to stock recovery i cant access adb.
Drivers are ok (win 10 test mode etc)
recovery tool does something but cant fix.
flashing anything via fastboot wont write because locked BL
tried toolkits but same errors as commands manually
tried many unbrick guides but no luck (CM or ColorOS)
took boot.img from cm someone suggested but because of that lock i cant flash or boot it at all.
hoping someone could help me. i see much topics about same problem but no solution anywhere...
Click to expand...
Click to collapse
I also have the same problem what to do? if your problem is solved tell me how to do?

please help if you fixed this..Same thing is happing to me...

phillipmckinnish said:
please help if you fixed this..Same thing is happing to me...
Click to expand...
Click to collapse
You're not being able to boot into fastboot mode and device is bricked?

Same here but I can't boot into recovery or fastboot or anything...

If you have Linux PC try ubports might fix things then reinstall whatever os you feel like
https://ubuntu-touch.io/get-ut

Asus Padfone 2 semi bricked (Invalid Kernel message) help

Hi all,
I try to explain all and I try to be brief:
- Asus Padfone 2 with lastest stock rom and update
- Rooted with Towelroot apk
- Have a TWRP recovery that haven't any backup mode, so I want to install a CWM recovery to do a backup of my phone in case I need to format it
- tried with flashing from the recovery: I had signature error.
- tried to flash the lastest TWRP recovery for the Padfone 2: disaster
Now I'm stuck at boot, with Asus Logo and Invalid Kernel message. Can't boot recovery or the stock rom.
I can't flash the recovery with fastboot flash or adb sideload, I have a signature error.
Cannot even flash an unlocked boot.img, same problem. If I try to use "fastboot boot boot.img" it works, but after 30 seconds it automatically reboot before Windows (7, 64bit) install the MTP USB drivers.
I can't do anything, I recently resurrect the Padfone and the tablet and I already killed it.
Help please

UP

UP

Found a Solution?!!?!
Baboo85 said:
Hi all,
I try to explain all and I try to be brief:
- Asus Padfone 2 with lastest stock rom and update
- Rooted with Towelroot apk
- Have a TWRP recovery that haven't any backup mode, so I want to install a CWM recovery to do a backup of my phone in case I need to format it
- tried with flashing from the recovery: I had signature error.
- tried to flash the lastest TWRP recovery for the Padfone 2: disaster
Now I'm stuck at boot, with Asus Logo and Invalid Kernel message. Can't boot recovery or the stock rom.
I can't flash the recovery with fastboot flash or adb sideload, I have a signature error.
Cannot even flash an unlocked boot.img, same problem. If I try to use "fastboot boot boot.img" it works, but after 30 seconds it automatically reboot before Windows (7, 64bit) install the MTP USB drivers.
I can't do anything, I recently resurrect the Padfone and the tablet and I already killed it.
Help please
Click to expand...
Click to collapse
hi. did u find a way to flash a kernell on ur phone?
i have the same problem
help me by sending a mail to [email protected] plzzzzzzzzzzzz

manjalab said:
hi. did u find a way to flash a kernell on ur phone?
i have the same problem
help me by sending a mail to [email protected] plzzzzzzzzzzzz
Click to expand...
Click to collapse
Hi, yes I do, but honestly I don't remember.
I saved all the necessary so I think I should recall the procedure if I open that RAR file.
Now I have a BlackView BV7000Pro destroyed, worst than the Padfone (but still it turns on, it reboot immediately after the logo).
I'm a killer

manjalab said:
hi. did u find a way to flash a kernell on ur phone?
i have the same problem
help me by sending a mail to [email protected] plzzzzzzzzzzzz
Click to expand...
Click to collapse
Ok I didn't save anything. I remember something like flashing the original bootloader and recovery of the Padfone or something like that, using adb and fastboot.
Then I flashed a custom recovery and then the ROM.
I remember that it was more easy once done than reading the procedure. I deep searched on Google many different phrases about it.
Sorry I can't help anymore, I couldn't find anything (notes, files, etc).

Im trying to install TWRP without sucess.. but why?
using: fastboot oem device-info
the device status is:
bootloader tampered: false
bootloader unlocked: true
bootloader authorized: false
i did through fastboot mode:
fastboot erase cash
fastboot erase system
fastboot erase boot
fastboot erase recovery
fastboot erase userdata
and then:
fastboot flash recovery twrp-2.8.1.0-A68.img
that looks like right install, but at end, do not work. Always back to screen recovery options to select, recovery or exit to the system. But, when choosing recovery, the device just turn off .
At the first time i'd had install custom recovery CWM and use Tari's rom. That's nice but, have some problems with consuming battery and instability.
I want to install new rom's
---------- Post added at 12:19 PM ---------- Previous post was at 12:15 PM ----------
Rom Android Oreo for Asus Padfone 2
i'd found out in that website install new rom's like as Oreo.
But I'm in difficult to install TWRP here.
https://android8root.pro/como-fazer-root-asus-padfone-2/
Rom's for:
5.0 Lollipop
6.0 Marshmallow
7,0 – 7.1 Nougat
8.0 Oreo
Android P
CWM does not work because do not accept to flash the file of system over 1Gb
The Padfone is really one of the most useful mobiles phones i have pleaser to own. But unfortunately, old rom's are a source of difficulties to work with app's of today.

Phone keeps booting into csc fastboot mode

Hello. Today, my wife's phone stopped responding to anything out of blue. I did a forced reboot (Vol down + power) and it rebooted and worked fine for a bit. Seeing as Android 10 was out, I dled fota file and flashed it via recovery from SD card, like I usually do. It flashed successfully and then rebooted. Once it booted, after a few seconds it hanged and became unresponsive again. Forced reboot once again, except this time it booted into a fastboot mode on its own and here lies there problem:
- going through an option to get into recovery mode doesn't help as it goes back into fastboot mode again
- rebooting through cmd doesn't help either
- pressing start just returns to fastboot mode
- shutting it down through an option in fastboot and then turning it on still yields the same result.
Basically, whenever phone turns on, it goes into a fastboot mode whether you want it or not.
Has this happened to anyone else? Any idea how to fix it?
Upd:
Code:
(bootloader) has-slot:system:yes
(bootloader) current-slot:a
(bootloader) has-slot:boot:yes
(bootloader) slot-retry-count:b:6
(bootloader) slot-unbootable:b:yes
(bootloader) slot-successful:b:yes
(bootloader) slot-retry-count:a:7
(bootloader) slot-unbootable:a:no
(bootloader) slot-successful:a:yes
(bootloader) slot-count:2
Seems like update failed to flash into slot B and it's not bootable

Okay, so I fixed it.
I flashed service/raw fw through fastboot, commenting out userdata formatting part of the flashall_aft script (fastboot -w). After this, I was able to access recovery mode. In recovery mode, I flashed build 16.1220.1909.194 and then 17.1810.1910.63 from my SD card and phone came alive, while retaining all the data.
Perhaps, this information will help someone who will encounter the same situation.

can u provide links for service /raw fw and how did u flashed it.
My Asus ZS630KL is stuck at fastboot mode neither rebooting to recovery works nor flashing custom boot or stock boot works. how to flash back stock rom in fastboot mode.

DAMONDARK said:
can u provide links for service /raw fw and how did u flashed it.
My Asus ZS630KL is stuck at fastboot mode neither rebooting to recovery works nor flashing custom boot or stock boot works. how to flash back stock rom in fastboot mode.
Click to expand...
Click to collapse
Sure. You can get RAW one here. Unzip, cd to the folder and launch flashall_aft script in cmd. There a bash script in the folder in case you have a Unix system. Script will output "Download_PASS" when it's done. Do not disconnect your phone before then.
Note, by default, this will wipe your userdata partition. You can prevent that my commenting out/removing line 264 in the script. However, note, if you don't wipe userdata partition, until you upgrade to the firmware that you currently have, the phone won't boot.
If your final firmware is latest one, with Android 10 (build 17.1810.1910.63), you will have to first update to 16.1220.1909.194. Links to both are in my previous post. I advice to flash desired firmware through Recovery -> Install update from SD card, though adb sideload should work just as well.

I'm thinking that "service/raw fw" is what is called a "fastboot rom" with Xiaomi?
Asus does not provide these themselves somewhere?
Or only for internal use?
Now I don't have a problem with my Z6 currently, but like to be prepared, like a good Boy Scout.

DAMONDARK, I wrote a more detailed guide if you need it. Click
cobben, ASUS does not provide those RAW firmwares to the public themselves. My guess is they are distributed internally for the use by service centers and alike and some ASUS workers upload them for public use. It's basically a set of tools along with signed images of all partitions to flash a full firmware to a specific device.
Images being signed (unlike images extracted via payload_dumper), device will accept them even without unlocked bootloader.
Not sure what this kind of firmware is called for Xiaomi

Ok, that is basically the same as the fastboot ROM with Xiaomi.
Xiaomi provides these publicly for anyone to use.
They have a Windows tool for this.
Requires unlocked bootloader, but bootloader can be relocked with no consequences.
Then there are other traps with Xiaomi, ARB primarily.
An incremental upgrade to a new major Android version is bound to cause some problems for some users, at best.
There should be a publically available way to restore the device to a known state.

cobben said:
Ok, that is basically the same as the fastboot ROM with Xiaomi.
Xiaomi provides these publicly for anyone to use.
They have a Windows tool for this.
Requires unlocked bootloader, but bootloader can be relocked with no consequences.
Then there are other traps with Xiaomi, ARB primarily.
An incremental upgrade to a new major Android version is bound to cause some problems for some users, at best.
There should be a publically available way to restore the device to a known state.
Click to expand...
Click to collapse
They did provide a zip to go back to latest Android 9 build which is WW-16.1220.1909.194. It can be found here
In most cases, the above should be enough. If your bootloader is unlocked, you don't really need service fw, you can just flash images dumped by payload_dumper from any zip of a build from ASUS website.
Additionally, service firmware does provide a lock script, which supposedly locks the bootloader but erases userdata. I have not tested if it actually re-locks bootloader.