Hi, my problem is, I can't get into fastboot.
What I have done?
Wanted to unlock and flash TWRP. Found this tutorial from https://www.youtube.com/watch?time_continue=238&v=3oSycujvmP8 and it worked good, unlocked the phone, flashed the twrp as boot and bootet into twrp. Than the problem begin, I couldn't find the original boot.img. Ok, afterall I released, that it was in the images.zip which was in the fastboot files. Anyway, after not founding the boot.img I said, ähhh, just flash everything to the original and lets leave it like this. I downloaded the fastboot image, yes, the right one 9.5.11 I think it was AA and in TWRP I clicked flash_all. It went through, with some errors I think and now the device boots, and boots, the circles going round and round. The Problem, I press volume + and power button, it reboots, tells me it is unlocked and than again the circles loading. Don't think I can get into fastboot.
Any idea how to solve it?
Boot into recovery with volume - and power button. Then boot into fastboot. And better do a wipe or format data.
I get now into fastboot, also twrp, done a format data, now the data parttion is also available, but still, tried now again flash_all and this time there were no errors, but still, it reboots and the circles going round and round for minutes.
that is so strange, a flash-all.bat should flash everything to normal, to original, shouldn't why it is not booting afterwards
Just use the MSM tool to put the stock ROM back on to the phone. It bypasses fastboot and bootloader and replaces everything.
van houd is right.
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
Related
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.
Hi! My Oneplus One is stuck in boot (the oneplus logo).
I can get into fastboot but not recovery. I have followed some softbrick guides and the problem that I have is that even after flashing twrp as recovery I cant get into recovery. when I try to start it to recovery (volume up + power) I only get to the oneplus logo again. and when I use "fastboot boot twrp.img" the backlight comes on but the fastboot image stays, fastboot doesnt recognize it from this point so i have to restart it into fastboot mode again.
i have tried to flash the factory images, but nothing seems to change.
I dont know what to do, pls help..
After flashing recovery from fastboot, do NOT issue the reboot command. Press and hold the power button till phone powers off. If you issue the reboot command from fastboot, custom recovery will be lost. Also, don't know which twrp version you are trying to flash, but I would suggest flashing 2.8.6.0 first, then after you know you can get into recovery, you can flash another version.
Additionally, to boot to recovery you have to hold
volume down + power
volume up + power brings you to fastboot
Last but not least,
fastboot boot twrp.img
does not boot the recovery which is on your device, but the recovery image which is located inside your fastboot folder on your pc.
kenboyles72 said:
After flashing recovery from fastboot, do NOT issue the reboot command. Press and hold the power button till phone powers off. If you issue the reboot command from fastboot, custom recovery will be lost. Also, don't know which twrp version you are trying to flash, but I would suggest flashing 2.8.6.0 first, then after you know you can get into recovery, you can flash another version.
Click to expand...
Click to collapse
Ok, I did not know that the reboot command removes the custom recovery. Im almost certain that i've tried just powering down and trying recovery before too tho.
I was trying to flash twrp 3.0.0.0 so i'll try 2.8.6.0 asap
AcmE85 said:
Additionally, to boot to recovery you have to hold
volume down + power
volume up + power brings you to fastboot
Last but not least,
fastboot boot twrp.img
does not boot the recovery which is on your device, but the recovery image which is located inside your fastboot folder on your pc.
Click to expand...
Click to collapse
oops, i ofcourse ment that i try to get to recovery by volume down+power, and i know fastboot boot twrp.img boots from the .img on the computer, i just think its peculiar that nothing happens.
nothing has really happend after this, so i still need help.
summary: bump
I don't really get what you say. Perhaps i don't experiences before. @kenboyles72 is correct, official ROM may delete custom recovery (you can change the setting). Then @AcmE85 gives you an option, but it does not work.
Here is my option:
1. download any custom rom. The best idea is as minimum MB as possible. (Flash ROM directly from your PC)
2. flash your recovery, do NOT reboot. (fastboot flash recovery rec.img)
3. flash your ROM. (fastboot flash zip rom.zip)
Let's see if this would help you.
I had some issues a while back, where I was caught in a bootloop and flashing another rom. So I followed this guide, https://www.reddit.com/r/oneplus/comments/31sf0x/guide_how_to_return_from_oxygenos_to_stock_cm11s . You can skip flashing the userdata.img to keep all data on sdcard. Also you can substitute flashing twrp recovery img for stock recovery. I myself went ahead and flashed all stock just to make sure everything booted correctly, then went into dev options and disabled update cm recovery, booted back to fastboot and flashed twrp 2.8.6.0. Evey thing worked like a charm.
Flasing stock rom did not affect anything noticeably.. phone is still stuck in boot/fastboot
Just to confirm, have you tried either/both of these:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
I have followed the return to stock guide, but not the unbrick, since my phone is softbricked, not hardbricked.
I have followed this guide tho, to no avail https://m.reddit.com/r/oneplus/wiki/devices/one/brickguide
the strange thing is that i didnt cause this. The phone started randomly overheating and one time it just never booted up.
Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.
bump
xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.
Hello everyone,
I have accidentally messed up a TF700 device that my grandma received from a friend. Now I am stuck in a loop, when the device boots up directly into recovery. In recovery, I can connect with adb and reboot to bootloader with fastboot mode, where I see the three icons and I can connect with fastboot, I can even boot the stock ROM, which works fine now, because /data has been wiped.
I have been looking for recovery blob on Asus website, but it looks like Asus has totally cut off the device support, I can not find anything.
Because I have been doing lots of nasty things to the tablet, by following a guide for flashing the TF201 (long story including wrong model name on the device sticker ) the easiest solution is probably to flash the original recovery, bootloader and ROM. Does anyone has by accident the recovery blob for Bootloader 1.00e ww_epad-10.6.1.14.10-20130801 a03 ?
Or is there any other solution for the loop? The problem is that in the recovery, I can not do almost anything, no partition can be mounted, I have probably flashed recovery for TF201.
Thank you.
Yes, best would be if you reflash the Asus firmware, then start from scratch.
Geab the zip here https://www.androidfilehost.com/?fid=817550096634791660
Extract it until you see the system blob (called simply "blob"), move it to your fastboot directory and flash it in fastboot:
fastboot flash system blob
Reboot
That returns you to a stock system.
Then flash the latest TWRP, format /data, then flash your Katkiss rom of choice
Good luck
Sent from my Pixel 2 using Tapatalk
This is awesome, thank you for such quick reply. Just one more question, is it OK to flash US recovery if there is WW version bootloader? Just to be sure not to scew it even more
Yes, flash away. The bootloader is the same for WW and US, just some wifi modules are different, I think.
That firmware is US anyway and it includes the bootloader, so you'll have a US BL afterwards
Sent from my Pixel 2 using Tapatalk
OK, sounds good then
I have tried downloading the archive now several times and no matter what program I use for unpacking, I always get error. May I ask you please to verify that the file is alright?
hornmich19 said:
OK, sounds good then
I have tried downloading the archive now several times and no matter what program I use for unpacking, I always get error. May I ask you please to verify that the file is alright?
Click to expand...
Click to collapse
Works fine for me. Downloaded it and it opened without problem. Try this link, uploaded the same file here: https://www.dropbox.com/s/tz1lcspqayhs7ug/US_epad-user-10.6.1.14.10.zip?dl=0
No I just can not extract it
7-zip, winrar, gzip tried and I always get CRC error. I can however open it to see what files are inside, but not extract the blob to flash it. So maybe there was a little misunderstanding.
So Good news (partially), I have managed to find on the Internet similar package with WW. Extracted the blob and flashed to system partition. But nothing has changed, it is still booting right to recovery (FlatLine CWM)
Strange thing is, in recovery, I can not mount any partition.
Another strange thing is that in the fastboot mode, there is no blue progress bar as it used to be before I damaged it. Also it does not respond to any reboot commands. I have to do hard reset.
Any idea to try out, please?
Mhhh, maybe you have to go the super clean route.
Run these commands one after the other, letting every single one finish. Some are very fast, some take a bit longer
fastboot erase misc
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot flash system blob
fastboot reboot
If it hangs at any of the commands (30 min or more does not return to prompt) just reboot with the buttons and continue with the next command.
Good luck
Awesome, I have some progress here, thanks to you. After formating the other partitions, the fastboot screen finally started to react and the blue progressbar appeared and the blob has been flashed.
After that, I have rebooted the tablet and it was stuck on the ASUS splash screen. When I rebooted to fastboot again, and tried recovery, I got Dead Android image instead. So there was no recovery image on the partition. When I tried to select cold boot to Android, I gets stuck again. So I have at least flashed TWRP recovery back again and I can boot to that recovery.
Also it looks like, despite of what was the archive name, I have now US bootloader and not WW anymore
So how to ged rid of the ASUS splash screen now? I suspect there is no kernel and RAMdisk on the boot partition now, since I have formated it, right?
I have tried flashing the JB kernel linked in the thread here https://forum.xda-developers.com/showthread.php?t=1919961 but without any result. However I am not 100% sure about the android version.
Or maybe this is a good time to flash completely different ROM?
Ok, step-by-step...
Strange though that it did not boot after flashing the blob... hope you do not have something else going on.
The Asus blob contains everything: Every partition is reflashed with stock software so everything should be in place. The dead Android is the stock recovery showing that it cannot find anything to flash. That is perfectly normal and healthy.
Yes, do not try to piece the system together, flash a full rom now (after formatting /data in TWRP).
https://forum.xda-developers.com/tr.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
I would recommend one of the KatKiss roms, the latest is here:
https://forum.xda-developers.com/transformer-tf700/development/rom-t3457417
Hello and sorry for not replying long. The baby at home was sick so I didn't have time to play with the tablet.
I have flashed the ROM you linked and the tablet finally is booting and working :victory: Or so far it looks like that
Thank you so much for your asistance here, I learned a lot on this journey.
For whatever it is worth, I just had a sudden occurrence of a similar problem. Im still using this tablet on an almost daily basis and one day it started a boot loop. When I tried the RCK it would show TWRP and then bootloop again. Followed the 'simple clean' steps and reflashed twrp and clean version of KatKiss and now good to go! Thanks @berndblb for the refresher course in fastboot commands.....
My note 6 pro suddenly started doing boot loop. I tried to revive it by flashing stock firmware but nothing seems to help. It has unlocked bootloader, with TWRP installed. This is what I tried:
Put phone in fastboot mode, I do see the fastboot image.
Computer recognizes the phone. 'fastboot devices' shows correct device.
Using MI Flash tool to flash 10.3.6 global fastboot image. It takes about 160 seconds to flash all the partitions. The phone will reboot at the the end of the flash. Flash tool doesn't say "successful" though. Its status is still "flashing".
No other errors. When the phone restarts, it is still stuck in the boot loop. Interesting thing is, if I press volume + button and power button, I see TWRP flash for a quick second on the screen then boot again. Looks like the recovery image wasn't flashed properly.
Looked at the logs. Nothing strange. Also tried to run 'flash-all.bat' in a command line (not sure if we are supposed to do that), but all the fastboot flash commands look OK.
Anything else I can do to revive this phone?