Database Info

[Q]Stuck in bootloop with deleted OS, abd not working.

Hey all,
I have a big problem with my TF700.
I wanted to root my device after unlocking the bootloader through the app, but by being dumb I managed to delete the OS in TWRP (thought it was factory reset) and now I'm in big trouble.
The only thing the tablet loads now is the TWRP 2.2.1 recovery. (TWRP came with a root-package, I didn't install it myself.)
Since I can't load an OS that is apparently deleted, I'm stuck with using the (latest) SDK to get the stock rom back on the tablet.
The problem is, it doesn't work, at all. The device is recognised by my (Win7) PC and the 'adb devices' command gives me the ID and 'recovery'.
If I try to push the ROM to the Sdcard folder (or any folder, for that matter) It gives me a "protocol error" with no other explanation.
If I try to sideload it it is stuck on "Waiting for device".
I tried the 'shell' command, just to see what that does, but it also gives me an error.
Other commands can also give the the "error: closed" message.
Since both of those commands don't work, I can't get anything on this tablet, since I can't get this version of TWRP to mount an external (micro) SDcard, the option simply isn't there.
Can anyone help me with this, of has my tablet been reduced to an expensive paperweight?

That's the problem with packages - you don't really know what's in it...
What root package did you use?
You have a very outdated recovery installed. I'm guessing here, since you didn't post your bootloader version and that's the first thing we need to know!
Can you still get into the bootloader?
Boot with Power and Volume Down buttons until you see the tiny script and post your bootloader version. Should be something like 10.6.1.....
Do NOT do anything else in recovery at this point!!!! If it is incompatible with your bootloader you could hard brick!
Once we know if you have fastboot access and what your bootloader version is, we can help you to flash the correct recovery in fastboot. With that installed it's a piece of cake to get you up and running.
But be patient! Don't do anything else you're not quite sure of!

*Update Below*
I believe the culprit was the 'Install recovery' method "Scott's Recovery install tool"
I tried a few but most didn't do anything. Every tool I tried comes from the xda forums and checked youtube videos explaining the steps.
If I boot using Volume down + power, nothing extra happens. I just see in the left hand corner "this device is unlocked", since I unlocked the bootloader using the ASUS app.
If I use the command adb reboot bootloader, it goes to TWRP 2.2.1.
Does this imply that I also deleted the bootloader?
Update: I deleted all drivers and software regarding the tablet from my PC and I installed the adb setup package from these forums and reinstalled the (universal?) driver package. This turned out to be a newer version of adb, and I actually managed to push a file to the tablet with no problems. I am reluctant to try anything else at the moment, since this whole ordeal had given me quite the scare (and the desire to learn more about this all)
Can anyone help me revive my tablet?

FooYoungHi said:
*Update Below*
I believe the culprit was the 'Install recovery' method "Scott's Recovery install tool"
I tried a few but most didn't do anything. Every tool I tried comes from the xda forums and checked youtube videos explaining the steps.
If I boot using Volume down + power, nothing extra happens. I just see in the left hand corner "this device is unlocked", since I unlocked the bootloader using the ASUS app.
If I use the command adb reboot bootloader, it goes to TWRP 2.2.1.
Does this imply that I also deleted the bootloader?
Update: I deleted all drivers and software regarding the tablet from my PC and I installed the adb setup package from these forums and reinstalled the (universal?) driver package. This turned out to be a newer version of adb, and I actually managed to push a file to the tablet with no problems. I am reluctant to try anything else at the moment, since this whole ordeal had given me quite the scare (and the desire to learn more about this all)
Can anyone help me revive my tablet?
Click to expand...
Click to collapse
Ok, good - you got adb working. The adb command to boot into the bootloader is
Code:
adb reboot-bootloader
Note the hyphen
Also I wonder if you pushed Power and Volume Down long enough. You should feel the tablet vibrate twice, then see some tiny script and 3 icons appear. That would be the bootloader menu and in it, you are in fastboot mode by default.
The next step would be to check if you have a fastboot connection.
The command for that is
Code:
fastboot devices
Read my guide on flashing a custom recovery and rom very carefully and follow the steps outlined to get TWRP 2.8.0.1 on your tablet.
Ask any questions you may have in that thread.
http://forum.xda-developers.com/showthread.php?t=2688891
Edit: Sorry, forgot that we have to determine your bootloader version first. So use the button combination or the adb command to boot into it and post it. Don't worry. I don't think you did anything to the bootloader - it's not that easy to mess it up...

Unfortunately, the adb code doesn't work, with or without the hyphen. The device will reboot, but will return to TWRP.
I've held down the Volume down+power button for more than a minute witout result. The device will just reboot after a while for as long as I'm holding it. I do see the screen flicker for a second.
I've also noticed, that after I push a file to the tablet, that after a reboot it loses the data I just moved.
After booting TWRP, when I look in the command line of TWRP, it tells me that it can't mount the 'system' , 'data' and 'cache' forders. (tw_mount)
And it specifically mentions (multiple times) that the /data folder failed to mount, giving the message "No such file or directory"
It seems I really managed to F'ed it up good...

My "force-boot-to-bootloader" kernel module might help you unbrick. Read this guide very carefully before you do anything:
http://forum.xda-developers.com/transformer-tf700/help/guide-t2853546

You people are my new heroes!
The last guide did the trick. The stock firmware is installed and I'm currently updating and installing all the apps.
Thank you all só much, you really saved me a ton of frustration.

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.

Arrrrg did I brick the thing, stuck on HTC screen after using TWRP.

So I got somebody to help me out with the $25 on Sunshine, S-off, unlocked, rooted. I go to Google Play and get TWRP and go to "TWRP install" select my phone type, the newest build and I install it, says it installed fine and asked to boot into recovery mode which just takes me to a triangle and an exclamation point. I vol -/+ power to restart and it sticks me on the "HTC" boot up screen, I vol + and power with a quick transition to vol - to try and do a factory reset and start over again and it won't even allow me to do that. Now what? Did I brick it? Does anybody have a link that'll get me out of this mess and get a custom rom flashed on here?
Thank you!

I'm still at it trying to get an older version of TWRP on it via ADB which I installed on my Mac but I can't get the Mac to recognize the M8 so I am messing something up along the way. Does anybody know how to get this done?

I always do my best to document my progress so that it's solved for the next person that has an issue. I'm still stuck and have tried installing the SDK tools on both Mac and Windows and I can't get ADB to pick up the device in fastboot mode on either. I'm typing this on a Linux machine, I guess I could try it from here for fun but I'm guessing there's some other issue going on. I'm just trying to figure out how to get TWRP flashed on at this point so I can get out of my soft brick issue.

Tucson85743 said:
I always do my best to document my progress so that it's solved for the next person that has an issue. I'm still stuck and have tried installing the SDK tools on both Mac and Windows and I can't get ADB to pick up the device in fastboot mode on either. I'm typing this on a Linux machine, I guess I could try it from here for fun but I'm guessing there's some other issue going on. I'm just trying to figure out how to get TWRP flashed on at this point so I can get out of my soft brick issue.
Click to expand...
Click to collapse
While phone is in fastboot, you need to use fastboot commands, adb won't work. Connect phone to pc while in fastboot mode then try typing in "fastboot devices" and hit enter. If it shows you device S/N then you are good to go. To flash recovery you normally use "fastboot flash recovery recovery.img" assuming you renamed the twrp file to recovery.img
If you cant get that to work, you might try looking for the RUU file for your device to reset your device back to completely stock firmware and start over.
Hope this helps!
Sent from my A0001 using XDA Free mobile app

Klown80 said:
While phone is in fastboot, you need to use fastboot commands, adb won't work. Connect phone to pc while in fastboot mode then try typing in "fastboot devices" and hit enter. If it shows you device S/N then you are good to go. To flash recovery you normally use "fastboot flash recovery recovery.img" assuming you renamed the twrp file to recovery.img
If you cant get that to work, you might try looking for the RUU file for your device to reset your device back to completely stock firmware and start over.
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
That was a HUGE help actually and this is way easier on my Linux box. It's communicating in fastboot but won't boot into TWRP when I go to recovery yet. I'm trying to fastboot a custom rom to it now to see if that works but am having some issues thus far but will keep at it.
****Edit So I think it was the version of TWRP I was using that was the issue this entire time. I tried 2.8.7 which caused the issues, then to flash 2.8.3 and 2.7.0.1 to try and get something to recover from with no luck and finially I used fastboot on Linux to get 2.8.0.0 on it and it's going into recovery find from that.
****Edit 2.0 I have TWRP working but can't wipe or install and keep getting an error "twrp unable to mount /system" so I need to address that somehow, how sure what the issue is but I'm worn out on it so any help or ROM suggestions to use from here would be amazing!
****Edit 3.0 After retrying with 2.8.7 and it not working at all I tried with 2.8.0.1 and had the same issue so I went up to 2.8.0.2 and that fixed it now I just need to find the right rom to download and flash.
****Edit 4.0 Okay I am all set and figured out the issues and have SlimKat running on it now. Thanks for that little nudge in the right direction!

After update, flashed twrp, now booting straight into twrp

So today my new One Plus 6 arrived. I tested it out for a bit made sure everything seemed to be working ok.
Then I unlocked bootloader, flashed twrp, magisk, all without issue. (I followed a guide I found on google) While setting everything up, I noticed that there was an update avaliable. So I installed that and got a message that the update will remove root. I thought "ok, i'll just have to do that again after. Update installed, rebooted device to recovery and realize TWRP is also gone after the update. So then I rebooted again to the bootloader and do fastboot devices command on my pc. Phone is there. Next I do the fastboot flash boot twrp.img command.
Sending.. Writing.. Finished... But I was still on the bootloader on the phone. I tried it a couple more times with no result. Restarted the phone only to boot into TWRP now. I thought to myself "hmm I'm not sure that's what's supposed to happen" but I continued to flash twrp.zip anyway. Rebooted the device.. TWRP booted again. Tried rebooting a couple more times with the same result.
Now, maybe this is where I messed things up more seriously. I'll also mention I foolishly didn't perform a backup on TWRP before doing all this. Not sure what to do, I flashed magisk as well. And I tried rebooting system, then when that didn't work I think I rebooted "slot B' for some reason.... After that it would only show the oneplus boot animation for a seemingly indefinite period of time.
I found I could get int the bootloader menu by holding vol up and power. Tried flashing TWRP, seemed to work on my computer's end but didn't boot recovery on phone. I rebooted into recovery from bootloader menu, brought me to endless oneplus boot animation again. Selecting start on the boot loader booted to TWRP. From there I rebooted back to slot A. Now it boots straight into TWRP.
I'm not sure what went wrong. I've rooted, installed various roms, etc on previous devices. Never had any issues before. But as I'm sure you can tell I don't really know what I'm doing. Does anyone have any advice? Thanks.

Your not supposed to fastboot flash the twrp, youre supposed to fastboot boot it. Just reflash stock boot.img and you'll be good

usernameisausername said:
I'm not sure what went wrong. I've rooted, installed various roms, etc on previous devices. Never had any issues before. But as I'm sure you can tell I don't really know what I'm doing. Does anyone have any advice? Thanks.
Click to expand...
Click to collapse
A number of things work differently on this phone. Don't assume any of your previous knowledge transfers over. There is a steep learning curve.
Stay away from random guides on Google. There are reliable guides here that, if you follow them to the letter, will keep you out of trouble.

fastboot flash boot [.IMG]
Is the issue. Should be
fastboot boot [.IMG]
On www.twrp.me/Devices you'll find the OnePlus 6 plus a corresponding how-to, directly from the source.
Your best bet:
1. Download the full ROM zip from either OnePlus directly or one of the links here on XDA.
2. Download latest TWRP files from twrp.me
3. fastboot boot [.IMG]
4. If in TWRP, connect to your PC and send the ROM over to your phone (MTP should work I think. Else, just ADB push it)
5. Flash the ROM in TWRP as you would flash any other ROM.
6. Should work, your system is now back to stock (also recovery). Let it boot once to be sure and then retry magisk but with the right fastboot commands.
To flash TWRP permanently, move the installer.zip you find on TWRP.me to your phone, fastboot boot the .IMG and flash the installer.zip in recovery.
Let me know if it worked

schwarzerfleck said:
4. If in TWRP, connect to your PC and send the ROM over to your phone (MTP should work I think. Else, just ADB push it))
Click to expand...
Click to collapse
MTP is disabled on most versions of twrp including official. There is an unofficial version with MTP working though it's a bit wonky.

iElvis said:
MTP is disabled on most versions of twrp including official. There is an unofficial version with MTP working though it's a bit wonky.
Click to expand...
Click to collapse
Yeah that's why I suggested the ADB push

schwarzerfleck said:
Yeah that's why I suggested the ADB push
Click to expand...
Click to collapse
So I'm having the same issue as OP currently and am somewhat a noob to this. I'm stuck booting into recovery, how do I adb push to the phone? its not showing up in adb devices at all

Eilermoon said:
So I'm having the same issue as OP currently and am somewhat a noob to this. I'm stuck booting into recovery, how do I adb push to the phone? its not showing up in adb devices at all
Click to expand...
Click to collapse
If you have USB debugging enabled, it's probably a driver problem. Windows 10 has issue with driver signatures and there's a setting that needs to be disabled. Do a search as it's been discussed (I use a Mac so I'm not certain what).

iElvis said:
If you have USB debugging enabled, it's probably a driver problem. Windows 10 has issue with driver signatures and there's a setting that needs to be disabled. Do a search as it's been discussed (I use a Mac so I'm not certain what).
Click to expand...
Click to collapse
Thanks for the info! If anyone has a source for this, that'd be awesome

Trying to boot into TWRP recovery

I'm trying to install lineage OS 16 on my Sony Xperia Tablet Z LTE, in order for it to be up to date and able to use modern apps. I'm really not that tech savvy, but this far I've managed to unlock the bootloader, root the device and I believe I've managed to flash the recovery drive with the TWRP file meant for my device. I tried to flash the recovery from my windows PC, but every time I received "Failed "remote command not allowed" despite the device being unlocked at the bootloader and it is an A partition. So instead I went ahead and rooted the device and afterward flashed the tablet from the official TWRP app. At the end of the flash, I got "Flash completed successfully" which leads me to believe that I've flashed it correctly.
Now the issue is that no matter what I try, I can't boot into recovery mode. Every time I try, it just boots up regularly. I've tried via ADB terminal, through the TWRP app, and physically with the power button+volume down button, but everytime I get the same result.
This has me wondering, could I just download the Lineage image to my device and flash it directly to the boot partition or would this not work? Also what could be the reason I can't boot into recovery mode?
Sorry if this is not the forum for this topic, i just can't imagine who else would be able to advise me on this

luka0954 said:
I'm trying to install lineage OS 16 on my Sony Xperia Tablet Z LTE, in order for it to be up to date and able to use modern apps. I'm really not that tech savvy, but this far I've managed to unlock the bootloader, root the device and I believe I've managed to flash the recovery drive with the TWRP file meant for my device. I tried to flash the recovery from my windows PC, but every time I received "Failed "remote command not allowed" despite the device being unlocked at the bootloader and it is an A partition. So instead I went ahead and rooted the device and afterward flashed the tablet from the official TWRP app. At the end of the flash, I got "Flash completed successfully" which leads me to believe that I've flashed it correctly.
Now the issue is that no matter what I try, I can't boot into recovery mode. Every time I try, it just boots up regularly. I've tried via ADB terminal, through the TWRP app, and physically with the power button+volume down button, but everytime I get the same result.
This has me wondering, could I just download the Lineage image to my device and flash it directly to the boot partition or would this not work? Also what could be the reason I can't boot into recovery mode?
Sorry if this is not the forum for this topic, i just can't imagine who else would be able to advise me on this
Click to expand...
Click to collapse
Just to be sure, do you have USB debugging enabled?

Droidriven said:
Just to be sure, do you have USB debugging enabled?
Click to expand...
Click to collapse
I do, and of course I went and enabled it again after I bootloaded the device

Droidriven said:
Just to be sure, do you have USB debugging enabled?
Click to expand...
Click to collapse
You said you tried volume down+power, on most devices, that is the combination to boot into bootloader mode, fastboot mode or download mode, depending on the device. Volume up+power is generally the combination to boot into recovery mode. This doesn't seem to be your issue though. Are you sure you flashed TWRP to the correct partition? If your device is an A/B partitioned device, you may have flashed to one of these partitions when you needed to flash to the other partition.
Try flashing a copy of your stock recovery then see if that repairs the recovery partition and allows stock recovery to boot. If it works correctly after flashing stock recovery, you may not be flashing TWRP correctly or the actual flash might be being blocked by something that you're overlooking. Are you certain that your bootloader is unlocked?