Database Info

I tried to Root and CyanogendMod my phone and fail - Stuck at boot

Hi guys,
I decided to root my Nexus S with Nexus root toolkit, and then I tried to install CyanogendMod 10.
Then, it rebooted, and now when booting it stuck at a moving circle with the CyanogendMod text in it. after 30 minutes I had to remove the battery to shut it down.
Now I can access to the Fastboot mode (bootloader version I9020XXLC2)
it says Lock State : unlocked. But a recovery shows a robot on it's back with an exclamation mark on top of it during some minutes and then it try to but normally again and get stuck at the circle.
Update :
thanks to http://forum.xda-developers.com/showthread.php?t=1069032
I can now access to download mode, and I'll try to do something with ODIN, I'm on my way to tutorials.
And it's still recognize in windows as : Android ADB Interface in the computer management window (but no USB hard drive in the computer menu).
Any suggestion to help me out ?
ps : as you can guess, I'm quite a beginner, and may not get the meaning of all technical word in flashing phones.
Thanks for reading.

DO NOT use Odin for things like that. Think of Odin as a last resort thing rather than a tool you can use daily.
The Nexus line of phones is super easy to deal with.
Flash your recovery using fastboot.exe while in bootloader mode.
http://wiki.cyanogenmod.com/wiki/Fastboot#Flash_Custom_Recovery.img
Download for recovery (rightmost column):
http://www.clockworkmod.com/rommanager
Once that is done, boot to recovery, and wipe data + flash your prefered ROM.
Edit: Apple pie is awesome.

polobunny said:
DO NOT use Odin for things like that.
Edit: Apple pie is awesome.
Click to expand...
Click to collapse
Yes they are awesome indeed.
And I saw your message after I did use Odin, and saved my phone.
I regret having use a nuclear bomb to cure my little bug, but I'm relieved having solve my problem.
Now I'm back on rooting & stuff and I won't forget to back things up first.

Tartopom said:
Yes they are awesome indeed.
And I saw your message after I did use Odin, and saved my phone.
I regret having use a nuclear bomb to cure my little bug, but I'm relieved having solve my problem.
Now I'm back on rooting & stuff and I won't forget to back things up first.
Click to expand...
Click to collapse
At least nothing is broken. That's the problem with Odin. It's easy to mess things up more than they are already. The Nexus line, and more precisely the Nexus S is a near bulletproof thing when used with the recommended tools-> ADB, fastboot and CWM. It's so rare you'll need to resort to Odin you might as well not recommend it.

polobunny said:
At least nothing is broken. That's the problem with Odin. It's easy to mess things up more than they are already. The Nexus line, and more precisely the Nexus S is a near bulletproof thing when used with the recommended tools-> ADB, fastboot and CWM. It's so rare you'll need to resort to Odin you might as well not recommend it.
Click to expand...
Click to collapse
I get you, but the thing is din is damn easy to use, once you get all the correct files.
I'm a basic user, and the link you posted, I hardly get the message in it, and now I'm fighting against my lazyness to find some fastboot solution for a 64bit windows.
Because : Never give up, never surrender! I'll understand how to root that thing and how to install my mod!
or I'll die trying.
But I'll rather succeed tbh.

Tartopom said:
I get you, but the thing is din is damn easy to use, once you get all the correct files.
I'm a basic user, and the link you posted, I hardly get the message in it, and now I'm fighting against my lazyness to find some fastboot solution for a 64bit windows.
Because : Never give up, never surrender! I'll understand how to root that thing and how to install my mod!
or I'll die trying.
But I'll rather succeed tbh.
Click to expand...
Click to collapse
Fastboot is actually really easy to use, just as is ADB.
You need your ADB drivers to be installed properly.
Then to install something via fastboot it's pretty much
fastboot recovery recovery.img
fastboot bootloader bootloader.img
fastboot radio radio.img
And so on. Doesn't get much easier than telling fastboot which partition to write to then which file. Once all is said and done, you switch to your custom recovery to flash stuff and voilà!

polobunny said:
Fastboot is actually really easy to use, just as is ADB.
You need your ADB drivers to be installed properly.
Then to install something via fastboot it's pretty much
fastboot recovery recovery.img
fastboot bootloader bootloader.img
fastboot radio radio.img
And so on. Doesn't get much easier than telling fastboot which partition to write to then which file. Once all is said and done, you switch to your custom recovery to flash stuff and voilà!
Click to expand...
Click to collapse
You're helping me not giving up, I'll help you to understand the gap between your knowledge and ease, and mine :
On your link : wiki.cyanogenmod.com/wiki/Fastboot#Flash_Custom_Recovery.img I'm stuck at the second point.
I found one fastboot for x64 through rootzwiki.com/topic/4551-guide-making-fastboot-work-on-64-bit-windows-7-systems but now I don't know how that new tool work, and I can't even launch it
But I remember how to launch a command script and basically that's all.

Tartopom said:
You're helping me not giving up, I'll help you to understand the gap between your knowledge and ease, and mine :
On your link : wiki.cyanogenmod.com/wiki/Fastboot#Flash_Custom_Recovery.img I'm stuck at the second point.
I found one fastboot for x64 through rootzwiki.com/topic/4551-guide-making-fastboot-work-on-64-bit-windows-7-systems but now I don't know how that new tool work, and I can't even launch it
But I remember how to launch a command script and basically that's all.
Click to expand...
Click to collapse
You need to make sure you have installed the ADB drivers for your phone. I highly recommend using the PDANet for Android drivers as they support a lot of phones.
http://junefabrics.com/android/
Then you need to use fastboot. There's no fastboot for Windows 7 64bit or 32bit and so on. There's one fastboot for Windows and it works with all newest platforms, so you don't need a specific one.
Here's a package containing fastboot and adb instead of download the whole Android SDK tools
http://dottech.org/downloads/adb_fastboot_and_other_tools.zip
Then you're pretty much ready to go.

polobunny said:
You need to make sure you have installed the ADB drivers for your phone. I highly recommend using the PDANet for Android drivers as they support a lot of phones.
http://junefabrics.com/android/
Then you need to use fastboot. There's no fastboot for Windows 7 64bit or 32bit and so on. There's one fastboot for Windows and it works with all newest platforms, so you don't need a specific one.
Here's a package containing fastboot and adb instead of download the whole Android SDK tools
http://dottech.org/downloads/adb_fastboot_and_other_tools.zip
Then you're pretty much ready to go.
Click to expand...
Click to collapse
Damn I'm a genius!
I discovered the same thing almost on my own
Thanks a lot mate ! Lost of apple and pie for you, you deserve it very much.
The difficulty is, with the sdk the fastboot command has to be launch in platform-tools folder, not the tool folder.
Yeah yeah yeah I know, it's writen almost everywhere, but I didn't saw that earlier and wasted hours to make it work.

Tartopom said:
Damn I'm a genius!
I discovered the same thing almost on my own
Thanks a lot mate ! Lost of apple and pie for you, you deserve it very much.
The difficulty is, with the sdk the fastboot command has to be launch in platform-tools folder, not the tool folder.
Yeah yeah yeah I know, it's writen almost everywhere, but I didn't saw that earlier and wasted hours to make it work.
Click to expand...
Click to collapse
Bravo, you're getting there. You'll be an adb master in no time.

At least you are now a user that knows how to use fastboot and fix issues that arise from flashing ROMs and relying on automated stuff.
Besides actual hardware issues most issues people have on their device are by some automated form of something. Tool kits/ROM manager and so on. All of which can be fixed up right away with fastboot and a basic understanding of what you're doing.
So now you're better off. All nexus devices work the same way as well.

[Q] Unable to return to install recovery / return to stock

Trouble here - sending HOX in for warranty replacement, already received new phone (original could not connect to 4g/lte, only edge) and am unable to run RUU to return to stock
bootloader screen info:
tampered/relocked
s-on
hboot - 1.09
on 1.85
I can boot into phone and use it, but when connecting to pc, get driver error 10 (cannot start) - however, when i plug in new phone, the driver works fine. This driver issues has occurs on multiple pc's - if it wasn't for this, I would be fine. Phone is still rooted. Also, I can browse files on phone when using disk mode, but when charge only, the "my htc" driver says it cannot start - this is preventing me from using any toolkits/running RUU, which I desperately need to do for warranty purposes. This means it is not recognized by adb/fastboot.
Cannot boot into recovery - tried installing through rom manager (says recovery flashed, but just goes back to bootloader when choosing recovery)
Please, let me know what other info you need - I've tried to be complete in my description, but that doesn't mean I was
I have searched forums, but haven't found my particular issue addressed - being unable to install/boot into recovery or connect to PC properly to return to stock

I saw Rom manager and I thought eek... Flash twrp

a box of kittens said:
I saw Rom manager and I thought eek... Flash twrp
Click to expand...
Click to collapse
I have tried installing twrp - it was installed, but now the folder is gone - CWM was a second choice, and ROM manager was a last ditch effort in attempting to install a recovery - ROM manager even says that CWM is installed, but agian, when in bootloader and choosing recovery, it just boots back into bootloader. That's the root (no pun intended - or was it of the problem - I am unable to boot into recovery at all, nor can I use fastboot when connected to pc due to driver error - the same driver that functions properly when connecting my replacement phone.

futureprimate said:
I have tried installing twrp - it was installed, but now the folder is gone - CWM was a second choice, and ROM manager was a last ditch effort in attempting to install a recovery - ROM manager even says that CWM is installed, but agian, when in bootloader and choosing recovery, it just boots back into bootloader. That's the root (no pun intended - or was it of the problem - I am unable to boot into recovery at all, nor can I use fastboot when connected to pc due to driver error - the same driver that functions properly when connecting my replacement phone.
Click to expand...
Click to collapse
Just download goo.im hit menu install open recovery then install.
Sent from my One X using Tapatalk 2

Kole_Ackerson said:
Just download goo.im hit menu install open recovery then install.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I've attempted to install recovery with goo manager as well - it states that recovery script is installed, but when attempting to boot into recovery, it just jumps back to the bootloader - that is what has got me biting my nails. Any ideas as to why I can't boot into recovery despite the fact that goo manager states that twrp was installed?

Finally able to kind of use fastboot - was able to reboot phone using fastboot, but cannot flash recovery image. When I use fastboot to look for devices I get this:
C:\oneX>fastboot devices
|÷cl≈═?/?π┌?╨
ñ fastboot
Not a typo - I get the mysterious message. Just some more info in case anyone can assist.

I'm willing to bet something on the phone is damaged, probably the miniUSB port. You're getting garbage because the phone can't communicate properly.

iElvis said:
I'm willing to bet something on the phone is damaged, probably the miniUSB port. You're getting garbage because the phone can't communicate properly.
Click to expand...
Click to collapse
Interesting thought - I had considered that, but I can connect in other ways (disk drive, etc.) as well as using fastboot to reboot into hboot - so I had discounted that possibility. I suppose I should not have....
That's why this is so frustrating - I can do some things, but not others - and I still don't understand why I am unable to flash a custom recovery, even just using goo manager or similar tool. Why would that be affected by my miniUSB port?
I have 4 days to send this one back for warranty (as stated earlier - I have the replacement already) - I'll probably pull my hair out trying until then :cyclops:
Thanks for the responses so far folks!

1.85, so AT&T right? AT&T seems pretty lax about checking bootloader, root, etc. for warranty returns. There have even been a few folks on here that sent phones running CM10 and other custom ROMs for warranty repair, with no issues. It seems you are on the stock ROM at least. Just make sure you go through AT&T, and not HTC (which are much more strict).

futureprimate said:
That's why this is so frustrating - I can do some things, but not others - and I still don't understand why I am unable to flash a custom recovery, even just using goo manager or similar tool. Why would that be affected by my miniUSB port?
Click to expand...
Click to collapse
You're right, the port would not affect any of that.
Still, something on your phone is corrupted. This is the same phone that could not connect to LTE? That suggests you've probably got hardware gremlins in there somewhere.
As redpoint said, don't worry about being rooted on the return. AT&T doesn't seem to care.

iElvis said:
You're right, the port would not affect any of that.
Still, something on your phone is corrupted. This is the same phone that could not connect to LTE? That suggests you've probably got hardware gremlins in there somewhere.
As redpoint said, don't worry about being rooted on the return. AT&T doesn't seem to care.
Click to expand...
Click to collapse
Well good gravy then it is through Att - - thanks for putting an alleged gentleman's mind at ease.
Although I have to say, this makes for a good case study all around - it truly is bizarre how some things seem to work while others don't -
at this point I'll just focus on clearing all personal data - no wipes seem to work either .
Again - thanks to the damn fine XDA community for the support - it's inspired me to figure out solutions on my own, while still knowing that there are fine folks willing to offer assistance in a pinch.
It's a good lesson that is repeated here often - do the research first! You learn a lot by breaking things

futureprimate said:
Well good gravy then it is through Att - - thanks for putting an alleged gentleman's mind at ease.
Although I have to say, this makes for a good case study all around - it truly is bizarre how some things seem to work while others don't -
at this point I'll just focus on clearing all personal data - no wipes seem to work either .
Again - thanks to the damn fine XDA community for the support - it's inspired me to figure out solutions on my own, while still knowing that there are fine folks willing to offer assistance in a pinch.
It's a good lesson that is repeated here often - do the research first! You learn a lot by breaking things
Click to expand...
Click to collapse
You can't flash recovery with a locked bootloader and S-ON (you relocked already judging by OP)... You can run the RUU from within bootloader, while in fastboot after it has been relocked and the RUU will flash stock recovery (assuming ofcourse fastboot driver works as it seems not to be). Good Luck!

exad said:
You can't flash recovery with a locked bootloader and S-ON (you relocked already judging by OP)... You can run the RUU from within bootloader, while in fastboot after it has been relocked and the RUU will flash stock recovery (assuming ofcourse fastboot driver works as it seems not to be). Good Luck!
Click to expand...
Click to collapse
Good advice, but the damn fastboot driver appears to be the rub - thought I had it, but now I get an error from the RUU regarding the charge (below %30 -- but it's fully charged of course). So all sorts of weirdness!

TWRP recovery will not install on ME301T

Hello all.
FIrst, I am not new to this. Just let me get that out in the open. I've done custom ROMs and recoveries on four devices including two HTCs. However I'm new to Asus and this is my first tablet.
So, what is going on is that I have an Asus Memo Pad ME301T. It is rooted, bootloader is unlocked (confirmation appears in upper left corner at boot). However, it will not install the TWRP recovery when I try to push it from my PC. I try to choose the recovery icon on the bootloader, and it shows the fallen android with an error message when it tries to open. I have followed the directions and executed the proper commands from the platform-tools folder in the Android SDK. I thought maybe I could try downloading the BLOB file directly to the device's emulated sdcard and installing it via a terminal command, however I do not know what commands I should use from a terminal emulator. I'm sure it's something simple I'm missing. I am trying to install the TWRP 2.5.0 recovery because it seems to have the highest success rate, and I am currently on the 10.6.1.15.ww stock ROM.
If someone familiar with these tablets could go through the process with me, step by step, one more time (don't just link me to a thread unless it's clear, concise, and exactly what you would do in this situation) or provide the commands so I can try it from the terminal within the tablet, I would appreciate it. When I've had problems in the past it's been something simple most of the time or an extra step I need to do so hopefully one of you can tell me what I'm missing.
Thanks!

asilaydyingdl said:
Hello all.
FIrst, I am not new to this. Just let me get that out in the open. I've done custom ROMs and recoveries on four devices including two HTCs. However I'm new to Asus and this is my first tablet.
So, what is going on is that I have an Asus Memo Pad ME301T. It is rooted, bootloader is unlocked (confirmation appears in upper left corner at boot). However, it will not install the TWRP recovery when I try to push it from my PC. I try to choose the recovery icon on the bootloader, and it shows the fallen android with an error message when it tries to open. I have followed the directions and executed the proper commands from the platform-tools folder in the Android SDK. I thought maybe I could try downloading the BLOB file directly to the device's emulated sdcard and installing it via a terminal command, however I do not know what commands I should use from a terminal emulator. I'm sure it's something simple I'm missing. I am trying to install the TWRP 2.5.0 recovery because it seems to have the highest success rate, and I am currently on the 10.6.1.15.ww stock ROM.
If someone familiar with these tablets could go through the process with me, step by step, one more time (don't just link me to a thread unless it's clear, concise, and exactly what you would do in this situation) or provide the commands so I can try it from the terminal within the tablet, I would appreciate it. When I've had problems in the past it's been something simple most of the time or an extra step I need to do so hopefully one of you can tell me what I'm missing.
Thanks!
Click to expand...
Click to collapse
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh

lj50036 said:
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh
Click to expand...
Click to collapse
Exactly. I open a command line on the folder, renamed the file to twrp.blob, and then I I am using the following:
ADB devices
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
I think the problem is really simple though. I think for some reason, the tablet and the computer are not communicating via fastboot. I.e. the info is not actually getting through the USB cable to the tablet when in fastboot. I have android debugging enabled and all that good stuff. So my assumption is this is a driver issue or an extra step needs done on the tablet to get the communication working. All drivers did install properly according to the PC. Maybe it's even the USB port on the tablet itself and I need to exchange it. But I can transfer files like it's a media device, so I doubt that's it.
Any thoughts?
***UPDATE***I checked settings in SuperuserSU and it turns out I did not have root enabled at boot. Enabled it and it connected to the PC as "fastboot". Commands are still not getting sent to the device. Whenever I try to send the blob, it always says "0 KB" and the device just freezes. Perhaps I need a different command or fastboot on the PC isn't initializing correctly? Or maybe there is a setting on my device that needs tweaked yet?
Thoughts?

I think I know what the problem is. Someone using the TF300T tablet had the exact same problem I'm having. Turned out it was their rooting method. I used KingoROOT despite a few murmurs of it causing issues because I was looking for results quickly not a quality job like I should have been. SuperuserSU has been behaving weirdly, as well as my USB android keyboard and a few other quirks in the OS since I did the root, so it makes sense. I will have to use the KingoROOT app and undo the root, and retry with motochopper. KingoROOT must not have rooted all directories. If that doesn't work, I will probably have to do a full restore to stock settings by re-installing a stock Asus ROM and start fresh.

lj50036 said:
So you are trying to install twrp from fastboot ?
What command are you using ?
Thx Josh
Click to expand...
Click to collapse
Did more work and research. I did actually have the improper drivers installed. I installed them from Asus, so that is fixed. But the problem remained. After further research, it came down to version builds and numbers. I am using a version of Asus' firmware that isn't compatible with the operations I'm trying to perform. I am using version 10.6.1.15. TWRP 2.5.0.0 and newer can NOT be installed on any Asus tablet running anything less than 10.6.1.27. There is something about the bootloader, encryption or a security setting that prevents data from being pushed via a fastboot command. So I now have a Christmas project, which is update to a newer version of Asus firmware.
I found my solution here, in a thread filled with people having the exact same issue:
http://forum.xda-developers.com/showthread.php?t=2179874&page=3
And directions for the fix here:
http://forum.xda-developers.com/showthread.php?t=2187982
Hope my work helps someone else.

No operating system found.

Totally new to xda forum, and pretty much a noob. Nexus 5 (US model). I was trying to unroot my Nexus 5. I bought it from a friend who had rooted it using TWRP, and it was running CM. Anyway, I managed to completely wipe the operating system ... completely. It will boot using the power/volume down configuration, but when I try to start the phone, it says, "No operating system found." All the threads I have been reading (yes, I have done a lot of reading), assume a couple of things: 1) that the phone can get into Settings/Developer Mode; and, 2) that my PC finds my phone when I plug it in. I have tried the adb and fastboot driver downloads, and wound up with some weird app that was almost impossible to uninstall off my PC. Ten-something or other. I tried doing the flash-all thing, but got a message that there was no such command. Can anyone help me, either directly, or by links to what I need? Once again, I have no operating system on this phone. Thanks.

There's a cool tool kit called wugs nexus toolkit that will help some http://forum.xda-developers.com/showthread.php?t=1766475
Sent from my Nexus 5 using Tapatalk
---------- Post added at 01:04 AM ---------- Previous post was at 12:59 AM ----------
Also, here's mostly all the roms stock & custom here: http://forum.xda-developers.com/goo...dex-google-nexus-5-roms-kernels-mods-t2475401
Did you say you can still get into recovery? Because there's an unroot rom thats flashable somewhere... Itd take you to stock everything.....
Sent from my Nexus 5 using Tapatalk

I second that recommendation. With a caveat. Wugfresh's Nexus Root Toolkit is a superb piece of programming which should enable you to set up your PC with all the necessary drivers and also let you specify the ROM you want to install, download it for you, and install it. You should obviously take the latest MMB29V.
But...
I see that you've done a lot of reading, and I understand that Android is initlally hard to grasp, but please don't (a) think you'll never understand it and (b) think that NRT is the answer to all your problems - it isn't. There are lots of reports of people saying "NRT has broken my phone" either because the've used it incorrectly or because they've used it before Wug has had a chance to update it to cater for all the latest tweaks that Google have introduced (particularly on Marshmallow root). If you're careful, set up your drivers properly, and install the correct version for your phone (Hammerhead MMB29V), NRT should give you back a working phone. But after that, read more, and investigate manual update methods, which are particularly useful for installing the monthly security updates without losing your data or waiting for the OTA (over-the-air) rollout from Google.

In fastboot, but can't flash operating system
dahawthorne said:
I second that recommendation. With a caveat. Wugfresh's Nexus Root Toolkit is a superb piece of programming which should enable you to set up your PC with all the necessary drivers and also let you specify the ROM you want to install, download it for you, and install it. You should obviously take the latest MMB29V.
But...
I see that you've done a lot of reading, and I understand that Android is initlally hard to grasp, but please don't (a) think you'll never understand it and (b) think that NRT is the answer to all your problems - it isn't. There are lots of reports of people saying "NRT has broken my phone" either because the've used it incorrectly or because they've used it before Wug has had a chance to update it to cater for all the latest tweaks that Google have introduced (particularly on Marshmallow root). If you're careful, set up your drivers properly, and install the correct version for your phone (Hammerhead MMB29V), NRT should give you back a working phone. But after that, read more, and investigate manual update methods, which are particularly useful for installing the monthly security updates without losing your data or waiting for the OTA (over-the-air) rollout from Google.
Click to expand...
Click to collapse
I'm in the fastboot mode, and I can get into TWRP, but I can't get my PC to recognize the phone. I've followed every rabbit trail I can find, but the phone doesn't show up. The USB ports are fine, and all the USB drivers are up to date. This is what is on my phone screen:
FASTBOOT MODE
PRODUCT NAME - hammerhead
VARIANT - hammerhead D820(E) 32GB
HW VERSION - rev. 11
BOOTLOADER VERSION - HHZ12k
The rest is serial number and so forth. I can get into TWRP, but can't ADB Sideload because the phone is not showing up. Giving me an error 43.

" I've followed every rabbit trail"
Have you followed this one?
"Wugfresh's Nexus Root Toolkit"

kakid56 said:
Totally new to xda forum, and pretty much a noob. Nexus 5 (US model). I was trying to unroot my Nexus 5. I bought it from a friend who had rooted it using TWRP, and it was running CM. Anyway, I managed to completely wipe the operating system ... completely. It will boot using the power/volume down configuration, but when I try to start the phone, it says, "No operating system found." All the threads I have been reading (yes, I have done a lot of reading), assume a couple of things: 1) that the phone can get into Settings/Developer Mode; and, 2) that my PC finds my phone when I plug it in. I have tried the adb and fastboot driver downloads, and wound up with some weird app that was almost impossible to uninstall off my PC. Ten-something or other. I tried doing the flash-all thing, but got a message that there was no such command. Can anyone help me, either directly, or by links to what I need? Once again, I have no operating system on this phone. Thanks.
Click to expand...
Click to collapse
Yup use wugfresh toolkit ... download the factory image https://developers.google.com/android/nexus/images#hammerhead
and boot into bootloader.. then u knw what to do

kakid56 said:
I'm in the fastboot mode, and I can get into TWRP, but I can't get my PC to recognize the phone. I've followed every rabbit trail I can find, but the phone doesn't show up. The USB ports are fine, and all the USB drivers are up to date. This is what is on my phone screen:
FASTBOOT MODE
PRODUCT NAME - hammerhead
VARIANT - hammerhead D820(E) 32GB
HW VERSION - rev. 11
BOOTLOADER VERSION - HHZ12k
The rest is serial number and so forth. I can get into TWRP, but can't ADB Sideload because the phone is not showing up. Giving me an error 43.
Click to expand...
Click to collapse
I don't disagree with the NRT suggestion but am confused. Sorry if I'm missing something obvious. When you are in the bootloader, do you get a cmd response from "fastboot devices" (no quotes in the command)? ADB doesn't work from the bootloader as you probably know, but since you identify as a noob, thought I'd throw it out there. You can flash the system using fastboot commands if your PC recognizes (part of the confusion) the device in fastboot. If not, then you do need to get the drivers set up. If you just need adb/fastboot drivers, I recommend this which I used recently when NRT didn't seem to have the SDK version I needed for my N9 to sideload the latest OTA. Since it installs at the system level, you can place flashable files at the root of C rather than in a specific platform-tools folder. I'm on Windows 10; don't know if that makes any difference for this minimal install. As far as the flash-all. bat not working, that's not uncommon; the files can be extracted and flashed separately.
Sent from my Nexus 9 using Tapatalk

Won't upgrade Factory Software, Wont enter recovery. Hangs on boot

First off, my tablet isn't bricked. I can boot it up fine. But when I try to install the factory downloaded software it just hangs on boot indefinitely. Similar things happens if I try to enter recovery. It goes fine until I have to press Volume ^, then it just freezes and I have to hold down the power key for 10 seconds. I've searched around and all I can find is threads from people stuck in a boot loop. Any help appreciated

A little more information. This tablet has been sitting for a while because it was such a disappointment. Before I decided I was fed up with it, it looks like I unlocked and rooted it. Iooks like I may have also tried to install Clockwork Mod on it. Trying to fix it has reminded me of why I stopped using it in favor of my nexus 7. The UI feels like it was designed specifically to make people not want to use tablets.

The problem probably is the How.
And unfortunately you don't give us any info on that.
Why do want to flash stock if you hate it so much?
If you have CM on there you should have a custom recovery installed.
Which one?
What's the bootloader version?
And lastly, you can boot into fastboot mode? The screen with the 3 icons?
If yes, almost anything is fixable.
But you need to give us more info.

berndblb said:
The problem probably is the How.
And unfortunately you don't give us any info on that.
Why do want to flash stock if you hate it so much?
If you have CM on there you should have a custom recovery installed.
Which one?
What's the bootloader version?
And lastly, you can boot into fastboot mode? The screen with the 3 icons?
If yes, almost anything is fixable.
But you need to give us more info.
Click to expand...
Click to collapse
@berndblb. Thanks for the reply. It has been so long since I did anything with this tablet that I completely forgot what I had been doing since the last time I was trying to make up for it deficiencies. I seem to have gotten everything sorted. Uninstalled then reinstalled Busybox & Supersu. Then used TWRP's apk to re-install custom recovery 3.0. Install said it failed, but when I booted into the bootloader I could actually make a selection, instead of it hanging indefinitely while it tried to load the recovery. Win for me I guess. Finally able to make a backup which always feels good. The whole point of this is to install a custom ROM so that my tablet becomes more than a really expensive coffee table decoration.
The current install on my device is. Android 4.1.1, Kernel 3.1.1, & build 10.4.4.23-20121171
Any suggestions on moving forward and a recommendation on a clean ROM would be appreciated. But I can always take the time to read as well.

RussTdesign said:
@berndblb. Thanks for the reply. It has been so long since I did anything with this tablet that I completely forgot what I had been doing since the last time I was trying to make up for it deficiencies. I seem to have gotten everything sorted. Uninstalled then reinstalled Busybox & Supersu. Then used TWRP's apk to re-install custom recovery 3.0. Install said it failed, but when I booted into the bootloader I could actually make a selection, instead of it hanging indefinitely while it tried to load the recovery. Win for me I guess. Finally able to make a backup which always feels good. The whole point of this is to install a custom ROM so that my tablet becomes more than a really expensive coffee table decoration.
The current install on my device is. Android 4.1.1, Kernel 3.1.1, & build 10.4.4.23-20121171
Any suggestions on moving forward and a recommendation on a clean ROM would be appreciated. But I can always take the time to read as well.
Click to expand...
Click to collapse
The first thing you should have done is upgrade your bootloader to the latest version. I would not actually use TWRP 3.0 for anything at this point if I were you. I have no idea if TWRP 3.0 works with that ancient JB 4.1 BL you got there, but I would not chance it. As a matter of fact, since you have to flash either stock rom or just the bootloader (and for both you use your recovery) I would highly recommend you flash an older TWRP version that is compatible with your BL. That combo - BL and recovery - is nothing you want to screw around with. You should go back to TWRP 2.4.1 or so.
TWRP Manager forced the latest TWRP version (developed for MM roms) on you and that's why I hate these apps! They do not check for compatibility at all....The proper way to flash a recovery is in fastboot and in fastboot only.
so I am going to give you a bunch of links and a general plan of attack, but you will have to do a fair share of reading.
First things is: Get fastboot working on your PC!!!!!! The first part of this guide I wrote way back tells you how: http://forum.xda-developers.com/showthread.php?t=2688891
Once you got that working flash TWRP 2.4.1 - instructions on how to are in the same thread. Reboot the tablet, then boot into TWRP.
Now flash the latest bootloader (Packaged with a slightly younger TWRP version from here: http://forum.xda-developers.com/transformer-tf700/general/firmware-10-6-14-10-twrp-t2867157
Reboot the tablet, then boot back into TWRP.
Now you again need to update your recovery to a version you can use with a current rom. I'd recommend this baby and it comes in a zip you can flash in your current recovery: http://forum.xda-developers.com/tra...overy-kang-twrp-tf700t-2-8-x-xarea51-t3049395
Flash the Kang recovery, then reboot and boot back into TWRP.
Format your data partition in TWRP. It takes an hour or so but it does a great job of leaving you with a clean slate for the new rom and is required before you flash a major change (which you are doing in any case).
Now you are ready to flash a rom.
I am going to recommend a really old one and a really new one. There are plenty of others to choose from in the Development section, but none of them is still under active development.
CROMi-X Resurrected. Based on Asus stock anno JB 4.2.1 but modded and fine tuned to the gills. LMK still puts out an update now and then, but those are more fine tunings of the fine tuning. Very slight changes - nothing major is going to happen here anymore. But it's a very stable and well working rom for those that actually like the Asus interface. http://forum.xda-developers.com/tra...pment/cromi-x-5-4-resurrected-tweaks-t3273515
KatshMallow by Timudru. Yeah, Android MarshMallow for the TF700. Most Android users are still dreaming about MM and you can rock it on this ancient machine. And it's a beauty, just absolutely unbelievable what Tim has cooked up for this hardware. Trust me! Fantastic rom! http://forum.xda-developers.com/transformer-tf700/development/rom-t3282166
For both of them you should convert your data partition to f2fs which you can do in recovery. Instructions are here: http://forum.xda-developers.com/tra.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
Actually, for CROMI-X Resurrected you don't have to do this - it's build into the rom installer.
You could try to short cut all this and just flash a new bootloader/recovery combo in your current TWRP 3.0. Maybe it works. Maybe it hardbricks your tablet. Nothing worse than trying to do something substantial (like flashing a bootloader) in an incompatible recovery....
Ok, now I shut up and let you read.
Have fun!

@berndblb thank you so much. I really appreciate you taking the time to help me out with this. This isn't my first time to the rodeo, but I'm def not ever going to ride in the pros. Trying to install a custom rom an this tablet has really shown my how much I don't know. I'm going to follow your instructions. I will get back later and let you know how it goes.

RussTdesign said:
@berndblb This isn't my first time to the rodeo, but I'm def not ever going to ride in the pros. Trying to install a custom rom an this tablet has really shown my how much I don't know. I'm going to follow your instructions..
Click to expand...
Click to collapse
I could tell. That's why you got the self-help version
I know how it feels. After 3 years I am fairly proficient on this device. But I still felt like a total n00b when I got the first Nexus! :cyclops:
So much of this stuff is so device specific... takes a while to sink your teeth into.
Enjoy.

berndblb said:
I could tell. That's why you got the self-help version
I know how it feels. After 3 years I am fairly proficient on this device. But I still felt like a total n00b when I got the first Nexus! :cyclops:
So much of this stuff is so device specific... takes a while to sink your teeth into.
Enjoy.
Click to expand...
Click to collapse
I have fast boot running and back-checked it via the fastboot devices. I downloaded twrp-2.4.1.0-tf700t.blob. the tried to load it. I keep getting a FAILED( command write failed (Invalid Argument)). Any thoughts

Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html

berndblb said:
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Click to expand...
Click to collapse
Got fastboot running properly on my work computer with windows 7. I've gotten everything installed up to formatting the data partition. Doing that now. Super stressful & hard not to mess with it while it makes its way through a hour long process.

What did the trick to get fastboot working?

berndblb said:
Plenty. Unfortunately Windows is very finicky with fastboot...
If push comes to shove you may want to try a Linux live CD or distribution and I'll add a link later, but try this first: and try "fastboot reboot" to see if you can execute anything.
Sure you got the original cable?
Reboot pc and tablet
Try a different USB port
Connect the tablet booted into fastboot and check the entry in Device Manager for problems.
Now we're getting desperate....
Boot into Android, check if you have a data connection by push/pulling a small file which you put into the same directory.
adb devices
adb push filename /sdcard/
adb pull /sdcard/filename
adb reboot-bootloader
Then see if you can do anything in fastboot.
http://www.transformerforums.com/fo...t/46090-guide-adb-fastboot-linux-live-cd.html
Click to expand...
Click to collapse
Looks like I got it sorted. Decided on going with the KatKiss rom. And the performance is night and day. Thanks so much for all your help. Next time I will probably do more reading before I try anything more... But then again I tell myself I will read the instructions before I start assembling ikea furniture & never do. So only time will tell. Anyway. Thanks again.

berndblb said:
What did the trick to get fastboot working?
Click to expand...
Click to collapse
Installing it on a different computer. This one runs windows 7. My laptop runs windows 8.1, could be as simple as that. But who knows.