Database Info

Help, Goes straight to TWRP on startup

Hello Everyone,
I am a Noob, Yes. Please help. I was trying to install TWRP onto my TF300T. I installed it Via ADB. Had it installed with my stock ROM. I tried to do a backup so I could flash CM10. It said it wasn't mounted. I tried again and then it reboot and now goes straight to TWRP. I can get my device on ADB via the cmd screen but it says that the device is attached in recovery and my serial number is now 01233456789ABCD. Have I completely bricked my tablet? Is there anything I can do? I have been searching the forums for literally hours and am at wits end. Any suggestions would be appreciated. Sorry if this has been gone over time and time again but I can't figure it out. Please help. Thanks
Marc

To add,
When I try to do anything via fastboot it just hangs waiting for device. I can't get it to go to the fastboot page on my tablet, it just goes straight to the TWRP page.

Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...

splashg said:
Let me guess... You were on the Asus 4.2.1 OTA release, and installed TWRP 2.4.4.0-JB...
Click to expand...
Click to collapse
Yes, that would be correct. So I managed to reset the device and cold boot back to a working device. Now i'm still wanting to flash a custom recovery and change ROMS to cyanogenmod (had it on my S1 and loved it) but am a bit nervous. How do I reset my partition and clear the old TWRP and flash a working version of CWR via fastboot or a version of TWRP that will work with my OTA rom. I thought I had done quite a bit of research before hand but am feeling a bit overwhelmed now. I don't want to go through another twelve hours of trying every trick I can find on the internet to unbrick my device.
Thanks

Just a few other things to add. So now when i have my device connected to my computer in normal function i can recognize it when I enter adb devices on my cmd prompt. Then I do the fastboot reboot bootloader which it then sends it into the fastboot screen. type in adb devices and it doesn't recognize the device anymore. I try the commands to install the cwm recovery.img and my cmd screen goes through the normal steps saying it's completed it. Then i try to reboot the device through fastboot and it freezes on the bootload screen with the green box no longer flashing on the rck box. Hold power button for six seconds to reboot and i have a working device again. So now i'm lost. How do I reset everything so I can start over, repartition so I can flash a custom recovery and carry on. any help is appreciated.

I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.

splashg said:
I don't know how you got yours back, even the bootloader cold-booting linux won't go into the OS for me.
That said, AFAIK, TWRP 2.4.4.0-4.2 or 2.5.0.0-4.2 are the only ones that will work with the 4.2.1 OTA update. Let me know if you somehow manage to get either on there because I can't seem to flash anything.
Click to expand...
Click to collapse
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.

lomoski said:
I tried flashing the new correct version of TWRP. it just freezes on the rck tab of the bootloader. It goes through the process on fastboot on my cmd prmt but does nothing on the tablet end. At least I have a working device on 4.2.1 just frustrating that TW didn't state that there is a 4.2 version not just a JB version. So now I can't get OTA updates and can't flash any custom or stock ROM's. So I'm permanently stuck with 4.2 but it's better than being stuck with a brick I guess. This isn't my first time rooting, flashing or working with ADB and fastboot. Did my research before flashing the custom recovery and thought I followed TW's steps very accurately. I hope that they update their site to stop a large number of people soft or hard bricking their devices. I at least can hold out hope that someone will figure out how to re install the bootloader. There has to be a fix as the rest of my device works so the motherboard isn't shot. Good luck. Let me know if anything or anyone figures it out.
Click to expand...
Click to collapse
I finally gave up, sent mine in today, it will cost but what the hell, i want my tablet in working order. I've tried the remedies myself, to no avail.
So off to ASUS.

Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.

steveb05 said:
Let me know what they end up charging you. I did a service request on-line, but haven't heard back yet.
Click to expand...
Click to collapse
I won't know how much it will cost until the unit is in their hands. I initiated my RMA online as well, they told me i will be contacted by phone after they examine it, I'm prepared to invest another 100 bucks as i got the unit for $299. I'll be hesitant to go much higher. I will post a number when i hear from them, if they haven't replied back to you.

I've got the same problem on my TF300T.
I'm going to try to get it working.
Not entirely sure what caused it, since I had used encryption in cm10.1 prior to flashing Asus stock 4.2.1.
BTW, I've been able to get back to fastboot by running adb reboot bootloader when TWRP is loaded.
Update: Seems to be that new 10.6.x.x bootloader... gotta love Asus :-/
--- Update II----
I can't flash anything in fastboot anymore :-/

Oneplus One bootloop with Linux

Apologies if something similar has already been posted on here already. I have had a look, but can't seem to find anything.
I was trying to root my oneplus one this evening, and was following a very useful link here....
https://forums.oneplus.net/threads/like-a-boss-how-to-root-your-oneplus-one.58493/
....and got to the bit that says "sudo fastboot oem unlock" - waited a minute, and the phone rebooted showing the android and 1+ logo. But before anything else happens it turns itself off, then back on again. And continues to do this indefinitely. I can get it into fastboot mode, but not recovery. When it is in fastboot mode the pc doesn't recognise it. Something obviously isn't right, but I'm not sure what. I'm guessing something is possibly corrupt.
What I think I need to do is firstly, get the pc to recognise the phone somehow. Secondly, install a recovery on to it and thirdly, flash a rom. I've been scratching my head all night trying to work out how to get the phone recognised, and Googling like a teenager who's just discovered porn is available on the Internet.
Is there anybody out there who is familiar with Linux who can possibly walk me through what I need to get my phone working again?
Thanks for taking the time to read this, and for any help that may be offered.

[SOLVED] I think my I may have bricked my tablet

I had the Katkiss 5.1.1 ROM and decided to go with the KatKiss 6.0 ROM. I did a backup to an external card using TWPR. Since I was going from 5.1 to 6.0, I decided to format/data before flashing the ROM. I left the room and came back to see that my daughter reset the tablet. Now it seems to have been stuck in a boot loop similar to what happened in this thread:
https://forum.xda-developers.com/transformer-tf300t/help/softbricked-tf300t-trying-to-flash-to-t3508565
But I can't even get into the recovery. It'll get to the TEAMWIN screen and restart and it won't stop. I can't even shut it off to stop it. I've been searching for a solution and found this link:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
However fastboot says there is no device, but I may be using it wrong. Has anyone had this problem before? Does anyone know how to fix this? Any help would be appreciated

the_KEV said:
However fastboot says there is no device, but I may be using it wrong. Has anyone had this problem before? Does anyone know how to fix this? Any help would be appreciated
Click to expand...
Click to collapse
Really bad luck!
Hopefully you can reach fastboot. Then follow step by step the instruction in post #2 in the first link of your post to get back on stock rom JB 4.2. Good luck!

Am I supposed to be on a certain screen in order for me to use fastboot?

the_KEV said:
Am I supposed to be on a certain screen in order for me to use fastboot?
Click to expand...
Click to collapse
I don't know what is your knowledge in general, but the post I recommended above gives you all what you need. All erasing steps are based on "Buster99" and have been used several times successfully.
Minimal ADB & Fastboot allows your PC to communicate with your device via a DOS window on your PC. Therefore the USB driver must be installed. USB Debugging on your device must be activated. Hopefully you can start the "Fastboot USB download protocol" via "Power on"/ "Vol down" in the left corner above of the device display.

I'm sorry, I might not have been clear enough... I saw your post with the instructions, I was asking if the tablet should be on a certain screen because the only screen I can get to is where it asks if you want to boot to recovery, android or wipe data. I was wondering if this where I should be on the tablet when attempting this fix. Thanks

OK I got it!! Thanks a lot ebonit. My problem was that I couldn't find the USB drivers to install. I don't remember where I saw it but it said they get installed when you install ASUS Sync. So I did and followed the directions and it worked. Thanks a lot!!

the_KEV said:
OK I got it!! Thanks a lot ebonit. My problem was that I couldn't find the USB drivers to install. I don't remember where I saw it but it said they get installed when you install ASUS Sync. So I did and followed the directions and it worked. Thanks a lot!!
Click to expand...
Click to collapse
Congratulations! You are welcome!

Fastboot issue.

So I got my phone fully working minus getting into fast boot to flash TWRP (though I already have it).
This is the rundown of what happened (mind you I was drunk).
I went to change the fastboot image after drinking like 10ish or so beer not really sure anymore. Anyways I tried flashing it through TWRP. Later I realize how silly it was but it doesn't let me into fastboot anymore. (found this out later when I went to update TWRP.)
I am looking for a relatively way safe way to fix it as I'm sure I am not the first.
Some Advice on how to fix as I really don't wanna risk bricking it would be fantastic.
Thank you,

Shinobi_warrior said:
So I got my phone fully working minus getting into fast boot to flash TWRP (though I already have it).
This is the rundown of what happened (mind you I was drunk).
I went to change the fastboot image after drinking like 10ish or so beer not really sure anymore. Anyways I tried flashing it through TWRP. Later I realize how silly it was but it doesn't let me into fastboot anymore. (found this out later when I went to update TWRP.)
I am looking for a relatively way safe way to fix it as I'm sure I am not the first.
Some Advice on how to fix as I really don't wanna risk bricking it would be fantastic.
Thank you,
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/tool-oneplusrecovery-tool-v1-0-restore-t2991851

Maybe It's a driver issue I am having. Because what happens more specifically is fastboot menu vibrates a few times and goes to teh charging screen and doesn't allow me to flash anything (mind you this previously worked) I don't believe it is a driver issue though. Simply put I am unable to get into adb without loading the os and when the os is loaded It hangs on waiting for device. I tried manually flashing the stock logo.bin with no success..
Not sure if maybe im missing something here. Like my fastboot loads a little penguin on it instead of the stock image and then vibrates a **** load then loads the battery charger.

Shinobi_warrior said:
Maybe It's a driver issue I am having. Because what happens more specifically is fastboot menu vibrates a few times and goes to teh charging screen and doesn't allow me to flash anything (mind you this previously worked) I don't believe it is a driver issue though. Simply put I am unable to get into adb without loading the os and when the os is loaded It hangs on waiting for device. I tried manually flashing the stock logo.bin with no success..
Not sure if maybe im missing something here. Like my fastboot loads a little penguin on it instead of the stock image and then vibrates a **** load then loads the battery charger.
Click to expand...
Click to collapse
Are you able to boot into twrp? If yes,then flash this firmware.It should solve any firmware corrupt issues,i.e. you should be able to boot into fastboot again.

Thank you, YES this is exactly what I needed/looking for.
.

You have fixed/saved the Day confirmed now.

Google update bricked phone

Afternoon all.
This morning I had one of the usual messages on my pixel 2 about having to restart the phone to install the update. I did so but now I can't boot the phone. I'm in the bootloader, with the following options and consequences
start > causes phone to restart instantly
restart bootloader > restart instantly
download mode > restart instantly with "ERROR: Operation Denied"
recovery mode> restart instantly with "ERROR: LoadImageAndAuth Failed: Device Error"
Barcode > works
power off > works
I've not tinckered with the phone in any way and have only installed official updates when prompted. I'm trying to get up to date with everything again, and have downloaded adb. "adb devices" doesn't show anything, however "fastboot devices" will display my device. I've tried the unlock "fastboot flashing unlock" command but get "FAILED (remote: 'Flashing Unlock is not allowed')"
Is my phone bricked? It's a few weeks out of warranty.... any help is greatly appreciated.

Hello mate, deffo not a good look with a locked bootloader. Just wondering, as you said it boots to recovery does it throw you to bootloader screen with the yellow warning at the bottom or the proper recovery screen? If you get the proper recovery screen have you tried the press power/vol up button together combo to get to the full recovery menu?

junglism93 said:
Hello mate, deffo not a good look with a locked bootloader. Just wondering, as you said it boots to recovery does it throw you to bootloader screen with the yellow warning at the bottom or the proper recovery screen? If you get the proper recovery screen have you tried the press power/vol up button together combo to get to the full recovery menu?
Click to expand...
Click to collapse
Thanks for the reply. Nope I can only get to the screen with the little android robot on his back... and the options stated above
Like I said my computer can see it using the fastboot command, but not adb.

thermomonkey said:
Thanks for the reply. Nope I can only get to the screen with the little android robot on his back... and the options stated above
Like I said my computer can see it using the fastboot command, but not adb.[/QUOTE
Fair enough, as recovery was working I thought you may be able to use the button combo to get to the full recovery and try an ota.img via sideload but as you say ADB is dead thats probably not gonna work anyway (forgot it's ADB sideload, been a while since I've used it)
Anyway, I'd be inclined to try my luck with the warranty if you ain't already as it's a only a few weeks out of date, always worth a call and chance your arm with them just in case.
Good luck
Click to expand...
Click to collapse

junglism93 said:
thermomonkey said:
Thanks for the reply. Nope I can only get to the screen with the little android robot on his back... and the options stated above
Like I said my computer can see it using the fastboot command, but not adb.[/QUOTE
Fair enough, as recovery was working I thought you may be able to use the button combo to get to the full recovery and try an ota.img via sideload but as you say ADB is dead thats probably not gonna work anyway (forgot it's ADB sideload, been a while since I've used it)
Anyway, I'd be inclined to try my luck with the warranty if you ain't already as it's a only a few weeks out of date, always worth a call and chance your arm with them just in case.
Good luck
Click to expand...
Click to collapse
Yeah I'll re-attack. They were sure it was a hardware issue and wanted to charge me to repair it. I'm quite sure it's their update that's done it though!
I can't believe they've designed the phone this way though? It doesn't seem very well thought out.
Click to expand...
Click to collapse

thermomonkey said:
junglism93 said:
Yeah I'll re-attack. They were sure it was a hardware issue and wanted to charge me to repair it. I'm quite sure it's their update that's done it though!
I can't believe they've designed the phone this way though? It doesn't seem very well thought out.
Click to expand...
Click to collapse
Make you right, don't see how it can be a hardware issue tbh. In case it's of any bearing I remember reading something online about someone having this happen, luckily they were unlocked and flashing a fresh bootloader image to both slots cleared the error and got them back in the game. Might be worth searching that error message online, might give you some ammo so to speak.
Edit: found the article here
https://support.google.com/pixelphone/forum/AAAAb4-OgUsHtb-5BNtncg?hl=sl
Click to expand...
Click to collapse

junglism93 said:
thermomonkey said:
Make you right, don't see how it can be a hardware issue tbh. In case it's of any bearing I remember reading something online about someone having this happen, luckily they were unlocked and flashing a fresh bootloader image to both slots cleared the error and got them back in the game. Might be worth searching that error message online, might give you some ammo so to speak.
Edit: found the article here
https://support.google.com/pixelphone/forum/AAAAb4-OgUsHtb-5BNtncg?hl=sl
Click to expand...
Click to collapse
Thanks again. Has this happened to anyone else before? i.e. just restarting when told to by the normal google updates and the phone is suddenly bricked?? Seems silly and it's totally put me off buying another pixel device!
Click to expand...
Click to collapse

If you search loadimageandauth error in XDA search you'll find a few threads on it, was just doing that myself. Seems to point at a bootloader issue from what I've skimmed over so far which would tie in with that link I posted.
I'm not put off the pixels by these things, in the grand scale of things it's a very low average of devices it happens on so I guess you've just been unlucky. This is my 2nd pixel device ( had the pixel prior to this pixel 2) and most likely won't be my last pixel device.
Good luck with having another crack at the warranty