Database Info

[Q] I can't boot into recovery mode after rooting

Hey all,
I used the "root your phone with Ubuntu" guide from the Nexus S Development forum, and then did a "fastboot oem lock" but when I try to reboot into recovery mode, the phone just sticks at the Google logo. I never see the /!\ icon to proceed further to install the 2.3.2 update manually.
I tried an "adb reboot recovery" to see if that would get me into recovery, but no luck there either, it just sits at the Google logo.
I have to remove the battery in order to boot the phone properly.
I'm curious how to proceed.

cormyn said:
Hey all,
I used the "root your phone with Ubuntu" guide from the Nexus S Development forum, and then did a "fastboot oem lock" but when I try to reboot into recovery mode, the phone just sticks at the Google logo. I never see the /!\ icon to proceed further to install the 2.3.2 update manually.
I tried an "adb reboot recovery" to see if that would get me into recovery, but no luck there either, it just sits at the Google logo.
I have to remove the battery in order to boot the phone properly.
I'm curious how to proceed.
Click to expand...
Click to collapse
you need to flash a recovery via fastboot.
Download the clockwork recovery recovery-clockwork-3.0.0.0-crespo.img image, and save it to the ..\android-sdk-windows\tools directory
renamed it to recovery.img
then type...
fastboot flash recovery recovery.img
and hit enter
Click to expand...
Click to collapse

simms22 said:
you need to flash a recovery via fastboot.
Click to expand...
Click to collapse
There's a new version of CWM to flash...that one you're linking is causing issues to people trying to apply updates. CWM is now 3.0.0.5
http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img

distortedloop said:
There's a new version of CWM to flash...that one you're linking is causing issues to people trying to apply updates. CWM is now 3.0.0.5
http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Click to expand...
Click to collapse
fixed it, thanks!

simms22 said:
you need to flash a recovery via fastboot.
Click to expand...
Click to collapse
Huh, I thought the recovery reset itself... Thanks for the info.

Ah, drag, I had already locked my nexus back up, and unlocking it is going to wipe the phone all over again.
I think if I'm going to wipe my phone anyway, I'll just wipe it back to factory and leave the phone unrooted... Too much hassle with the internal SD getting wiped every time.

cormyn said:
Huh, I thought the recovery reset itself... Thanks for the info.
Click to expand...
Click to collapse
Only after a successful reboot to the normal system, and only if you're on 2.3.1 or greater, and only if you've not renamed the /etc/install-recovery.sh file.
cormyn said:
Ah, drag, I had already locked my nexus back up, and unlocking it is going to wipe the phone all over again.
I think I'm just going to unroot my phone. Too much hassle with the internal SD getting wiped every time.
Click to expand...
Click to collapse
Yeah, that sucks. I don't relock my bootloader.

Incidentally, I had flashed a recovery, it was called recovery-clockwork-herring.img as suggested in the original "root your nexus s with ubuntu" guide. Maybe someone should tell that author to suggest a newer/better recovery.

cormyn said:
Incidentally, I had flashed a recovery, it was called recovery-clockwork-herring.img as suggested in the original "root your nexus s with ubuntu" guide. Maybe someone should tell that author to suggest a newer/better recovery.
Click to expand...
Click to collapse
Use this one: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img

Thanks for the info, distortedloop. I think I'm just going to factory wipe and leave my phone unrooted for a while.
... assuming of course that a factory reset will get me back to a place where I can install OTA updates, or a recovery mode where I can manually install update.zip files?

distortedloop said:
Use this one: http://koush.tandtgaming.com/recoveries/recovery-clockwork-3.0.0.5-crespo.img
Click to expand...
Click to collapse
i was using the older CW recovery 3.0.0.0 also, so i just decided to flash version 3.0.0.5. since im at work, i cant fastboot it to my phone. i did it via the terminal emulator on my phone. 1st time i got a bunch of out of space errors so i booted into recovery just to check, and it was gone. nothing there. so i rebooted and tried it again via terminal. 2nd time was a success. to flash the recovery in the terminal emulator, download the recovery and put it on the root of your sd card and rename it recovery.img . now open the terminal and type...
su(press enter)
flash_image recovery /sdcard/recovery.img(press enter)
reboot recovery(press enter)

well, apparently a factory wipe was a bad move, 'cause now the phone rebooted and is stuck at the Google logo, like it's trying to get back into the recovery.

cormyn said:
Thanks for the info, distortedloop. I think I'm just going to factory wipe and leave my phone unrooted for a while.
... assuming of course that a factory reset will get me back to a place where I can install OTA updates, or a recovery mode where I can manually install update.zip files?
Click to expand...
Click to collapse
Factory reset won't remover the su binary and symlinks it makes. Factory reset only wipes the /data partition, not the /system one.
An oem lock, then oem unlock might, but I'm not sure...that definitely wipes the sdcard, though, unlike a factory reset does, so back that up first!
There's some thread on here someplace about how to completely remove root.

Pulled the battery, went back into bootloader mode, did a 'fastboot oem unlock', then flashed the crespo 3.0.5 img, and then 'fastboot oem lock' and the phone reboots properly.
Thanks again!

[Q] Frozen on boot screen after 2.3.3

Hi All,
I have a Nexus S with a strange problem. It was originally stock, with no ROM mods at all, I then applied the SU patch get root happening - all worked fine for months.
I then manually applied the 2.3.3 update about 1 week ago. All working fine with no issues.
Today however, i've come to check my phone to find it 'frozen' on the boot screen.
Thinking it was just another lovely OS glitch, I battery pulled, to find it turned into an endless Nexus S boot loop. I booted into recovery, wiped the cache. Same Issue. I Booted into recover a gain, did a factory data reset. Same issue. I booted in recovery again and re-applied the 2.3.3 update which was on my memory from the previous update. Same issue.
The phone seems to either freeze during boot, or go into and endless loop.
Ideas? - The only other thing that i thought would be to do a bootloader unlock to wipe EVERYTHING... but im not sure if its worth it.

Why not? You can lock it back with fastboot oem lock command.

If you can get into clockwork recovery, you have access to adb, so be sure to use adb pull to grab everything off your sdcard before doing something drastic like a oem unlock to wipe the phone.
Also, have you tried booting the phone while plugged into your computer with adb running? Use "adb logcat" to collect as much of the boot process as you can and it might give a clue as to what is going wrong.
Another "almost last resort" option would be to apply the FULL 2.3.3 update, the one that overwrites your system folder instead of patching it. You can push it to the sdcard with adb while in clockwork, but remember to use mounts and storage menu to mount the sdcard.

distortedloop said:
If you can get into clockwork recovery, you have access to adb, so be sure to use adb pull to grab everything off your sdcard before doing something drastic like a oem unlock to wipe the phone.
Click to expand...
Click to collapse
Sadly, it was a locked bootloader, so had no luck with that
distortedloop said:
Also, have you tried booting the phone while plugged into your computer with adb running? Use "adb logcat" to collect as much of the boot process as you can and it might give a clue as to what is going wrong.
Click to expand...
Click to collapse
As above, no permission to run recovery image.
distortedloop said:
Another "almost last resort" option would be to apply the FULL 2.3.3 update, the one that overwrites your system folder instead of patching it. You can push it to the sdcard with adb while in clockwork, but remember to use mounts and storage menu to mount the sdcard.
Click to expand...
Click to collapse
Couldn't get in as i had no ADB access.
In any case, i did a OEM unlock, and still had similar boot issues. The OS would boot, but despite flashing a custom clockwork recovery, it wouldn't get from BootLoad thru to Recovery. It also still had random hangs on boot.
I performed a fastboot flashall and also a fastboot erase boot and recovery. Leaving the phone totally empty.
I then re-loaded a rooted 2.3.3 with latest Clockwork and all worked fine. I've also updated radio to B3 - seems to work flawlessly.
I can only think something was screwy with the boot/recovery sections - very weird but all appears to work fine now.
Many thanks for the help.

g33k84 said:
distortedloop said:
Also, have you tried booting the phone while plugged into your computer with adb running? Use "adb logcat" to collect as much of the boot process as you can and it might give a clue as to what is going wrong.
Another "almost last resort" option would be to apply the FULL 2.3.3 update, the one that overwrites your system folder instead of patching it. You can push it to the sdcard with adb while in clockwork, but remember to use mounts and storage menu to mount the sdcard.
Click to expand...
Click to collapse
As above, no permission to run recovery image.
Couldn't get in as i had no ADB access.
Click to expand...
Click to collapse
You don't need recovery access to use adb. We might be miscommunicating, and it doesn't matter much since you've already nuked the phone, but what I was suggesting was a regular boot while trying to adb logcat the phone. I've used this technique to document the startup process in the past. Adb access loads up fairly soon in the process. If your phone wasn't even getting that far, of course it wouldn't work, but wanted to clear up what I was suggesting with that particular paragraph.

[Q] Could not mount /data ! Phone Stuck!

I flashed a CM based ROM, and decided to get back to Slimkat. Opened my recovery ( Philz CWM ) wiped everything, and now tried to restore my nandroid ! And suddenly Im on Can't mount /sdcard ! I can't even flash a new ROM or do anything, I get stuck on Google's boot logo if I want to get to the ROM.
Let's note that I had no USB debug checked as I was only checking out the newly flashed ROM. So am I literally in a dead situation? Anyone please may help ?

Ensifolk said:
I flashed a CM based ROM, and decided to get back to Slimkat. Opened my recovery ( Philz CWM ) wiped everything, and now tried to restore my nandroid ! And suddenly Im on Can't mount /sdcard ! I can't even flash a new ROM or do anything, I get stuck on Google's boot logo if I want to get to the ROM.
Let's note that I had no USB debug checked as I was only checking out the newly flashed ROM. So am I literally in a dead situation? Anyone please may help ?
Click to expand...
Click to collapse
Clean fastboot install :/ Solved the issue for me

try and format cache. If still no luck, fastboot flash cache cache.img

rootSU said:
try and format cache. If still no luck, fastboot flash cache cache.img
Click to expand...
Click to collapse
Can I still fastboot even if I have no USB debugging enabled? The phone will interact with the commands normally? ( Since as I mentioned before I flashed the ROM only to check out and played with no settings at all, didnt know this is going to happen )

Ensifolk said:
Can I still fastboot even if I have no USB debugging enabled?
Click to expand...
Click to collapse
fastboot commands are done in the bootloader. USB debugging is an Android setting. The 2 are not related even in the slightest.

rootSU said:
fastboot commands are done in the bootloader. USB debugging is an Android setting. The 2 are not related even in the slightest.
Click to expand...
Click to collapse
Thank you sir ! Im sorry to go further saying that I have never used fastboot even thought this is my third nexus device, the regular way of me having a Nexus is using a toolkit on day one to Unlock/Root and then the rest is always done to me on a Recovery !
I am currently downloading the Factory Image to flash it via fastboot ( There are instructions on how to do that ) But will delete everything on my phone.
Is there a way I can save myself right now without any loss? Via fastboot commands? And how can I do it? ( Im really sorry for taking your time and mixing my inexperience )
You'd be a life saver hehe

Ensifolk said:
Thank you sir ! Im sorry to go further saying that I have never used fastboot even thought this is my third nexus device, the regular way of me having a Nexus is using a toolkit on day one to Unlock/Root and then the rest is always done to me on a Recovery !
I am currently downloading the Factory Image to flash it via fastboot ( There are instructions on how to do that ) But will delete everything on my phone.
Is there a way I can save myself right now without any loss? Via fastboot commands? And how can I do it? ( Im really sorry for taking your time and mixing my inexperience )
You'd be a life saver hehe
Click to expand...
Click to collapse
Dont flash the entire factory image.
just use the
fastboot flash cache cache.img
Then you won't wipe the device.
This is why not to use toolkits. fastboot is essential basic knowledge and using toolkits means you dont get to learn it

rootSU said:
Dont flash the entire factory image.
just use the
fastboot flash cache cache.img
Then you won't wipe the device.
This is why not to use toolkits. fastboot is essential basic knowledge and using toolkits means you dont get to learn it
Click to expand...
Click to collapse
You are totally right about that I should learn about it ! Hahaha. Okay, I opened a command promt and I am in the bootloader, where should I get the cache.img from? And should I place it in a certain folder? cause apparently I tried doing this command and it didn't work, I guess i have to get the cache.img from somewhere ( Im really sorry mate...Thanks again )

Ensifolk said:
You are totally right about that I should learn about it ! Hahaha. Okay, I opened a command promt and I am in the bootloader, where should I get the cache.img from? And should I place it in a certain folder? cause apparently I tried doing this command and it didn't work, I guess i have to get the cache.img from somewhere ( Im really sorry mate...Thanks again )
Click to expand...
Click to collapse
Have a read of the "how to flash a factory image" thread in general. Just remember, dont follow it blindly as you'll flash the whole factory image.

rootSU said:
Have a read of the "how to flash a factory image" thread in general. Just remember, dont follow it blindly as you'll flash the whole factory image.
Click to expand...
Click to collapse
Promise this is the last question I hope. I am actually on that page. I have downloaded the factory image BUT when I extract it via Winrar I only get a one file as an output (hammerhead-kot49h-factory-02006b99)
EDIT: I renamed the extracted file to .zip and extracted again, now I have the files displayed on that page...Trying to figure out now how to flash the cache.img

Ensifolk said:
Promise this is the last question I hope. I am actually on that page. I have downloaded the factory image BUT when I extract it via Winrar I only get a one file as an output (hammerhead-kot49h-factory-02006b99)
Click to expand...
Click to collapse
Extract it again.

Ensifolk said:
Promise this is the last question I hope. I am actually on that page. I have downloaded the factory image BUT when I extract it via Winrar I only get a one file as an output (hammerhead-kot49h-factory-02006b99)
Click to expand...
Click to collapse
Its a .tar file. Extract it again

...

I successfully flashed cache.img But the problem is still there in my recovery, can't mound /sdcard
Think I have to flash the whole factory image ? :-/

Ensifolk said:
I successfully flashed cache.img But the problem is still there in my recovery, can't mound /sdcard
Think I have to flash the whole factory image ? :-/
Click to expand...
Click to collapse
Maybe. Can you mount /data?
If so you can adb pull your photos etc off there from data/media/0 - otherwise no such luck
You can find instructions here if you need: http://forum.xda-developers.com/showthread.php?t=2534010

Ensifolk said:
I successfully flashed cache.img But the problem is still there in my recovery, can't mound /sdcard
Think I have to flash the whole factory image ? :-/
Click to expand...
Click to collapse
I think you'v nothing to loose by flashing the whole factory image. If /sdcard can't be mounted in this situation, I think that's because you did (or a toolkit) did something wrong and break it. I don't think that you'll be able to save anything.
(It's my point of view. Maybe somebody else has an idea ?)

rootSU said:
Maybe. Can you mount /data?
If so you can adb pull your photos etc off there from data/media/0 - otherwise no such luck
You can find instructions here if you need: http://forum.xda-developers.com/showthread.php?t=2534010
Click to expand...
Click to collapse
I cannot mount /data even after flashing cache.img - Hence I think I am dead by this stage and I can no more recover whatever I have on the phone. Factory image flashing then ?

Yep, I would

And there we go, I did it, phone back to life. Thank you guys ! A LOT! Appreciated ! pretty much !
Allow me to recall the scenario : I was on Slimkat, decided to try Mahdi Rom ( CM Based ), Backup before flashing, flashed, wanted to revert back. And this can't mount /sdcard there. No idea what could be it...
What recovery you guys recommend me to use ? - Lesson I learned today? I should know how to use fastboot and ditch the Toolkit galore.

Well, seems that you did'nt do anything wrong. Maybe a problem with the rom or something else occur.
Next time, maybe, do a backup and, then, copy it to your computer
For the recovery, I use CWM 6.0.0.4

[Q] Help - Rooting gone wrong

So I got the HTC One s and try to root it with the following instruction: http://forum.xda-developers.com/showthread.php?t=1583427&__utma=248941774.997411949.1390324490.1394471756.1396118873.6&__utmb=248941774.2.10.1396118873&__utmc=248941774&__utmx=-&__utmz=248941774.1394471756.5.2.utmcsr=feedburner|utmccn=Feed:%20xda-developers/ShsH%20(xda-developers)|utmcmd=feed&__utmv=-&__utmk=25799614
As I thought that Step 3 was only there to install the Superuser.apk i just skipped it (mistake no. 1) and wiped the whole thing (without making a backup --> mistake no. 2) and tried to install the Maximus HD Rom which as I am still S-On of course didnt work. So I wiped again but really careless and made mistake no. 3: wiping the whole thing instead of just a few partitions like system, cache,....
So now I have my device S-On, theres really nothing on it exept TWRP but there (and in other recoverys I tried) the USB mout doesnt work so I cant get a new rom on it So I tried to push it through fastboot but I cant find a fitting command.
Any advice what I can do to either get the USB work in the recoverys or push it through fastboot and which rom works without S-Off?
If you need further infos Id like to give those!

Akkordinator said:
So I got the HTC One s and try to root it with the following instruction: http://forum.xda-developers.com/showthread.php?t=1583427&__utma=248941774.997411949.1390324490.1394471756.1396118873.6&__utmb=248941774.2.10.1396118873&__utmc=248941774&__utmx=-&__utmz=248941774.1394471756.5.2.utmcsr=feedburner|utmccn=Feed:%20xda-developers/ShsH%20(xda-developers)|utmcmd=feed&__utmv=-&__utmk=25799614
As I thought that Step 3 was only there to install the Superuser.apk i just skipped it (mistake no. 1) and wiped the whole thing (without making a backup --> mistake no. 2) and tried to install the Maximus HD Rom which as I am still S-On of course didnt work. So I wiped again but really careless and made mistake no. 3: wiping the whole thing instead of just a few partitions like system, cache,....
So now I have my device S-On, theres really nothing on it exept TWRP but there (and in other recoverys I tried) the USB mout doesnt work so I cant get a new rom on it So I tried to push it through fastboot but I cant find a fitting command.
Any advice what I can do to either get the USB work in the recoverys or push it through fastboot and which rom works without S-Off?
If you need further infos Id like to give those!
Click to expand...
Click to collapse
TWRP has ADB Sideload feature. Means you can flash zips using adb. Of course you can flash a roms this but keep in mind you have to flash the kernel (boot.img) manually immediately after flashing the rom.zip. When flashed Rom.zip by using ADB sideload method make SURE that you direct go into fastboot mode and flash the kernel (fastboot flash boot boot.img) (you can extract the boot.img from your rom.zip)
May be a compatible rom this time? But you're lucky -> Infact you already deleted everything you won't have to perform a wipe before flashing lol

LS.xD said:
Of course you can flash a roms
Click to expand...
Click to collapse
Ok, but I dont know with which command (fastboot flash what? or adb?)

You can use adb sideload as followed:
Start TWRP -> advanced -> ADB sideload + swipe to activate it. Connect your phone to the computer. Open "CMD Commandline" and type "adb sideload ROMNAME.zip"
Of course "ROMNAME" has to match the zip you want to flash. Thats it
In twrp go to "REBOOT" -> "fastboot"
When fastboot usb is ready use CMD commandline again and type "fastboot flash boot boot.img"
Then you can boot android

I whished I could. As I start ADB sideload it keeps doing nothing at all until I abort it. What I think is important to know is that it is then:
"E:Unable to mout '/internal_sd'
E:Unable to mount storage.", which I think is the problem.

Flash Stock recovery And perform "factory Reset + clear storage" that will fix your storage. Then flash twrp Version 2.7 again and do what I suggested to flash the Rom
Sent from my beloved HTC One S using (most time buggy) Tapatalk

Did the exact thing which removes the mounting error, but this has no effect on the sideload (or usb mount). Still not working.

Akkordinator said:
Did the exact thing which removes the mounting error, but this has no effect on the sideload (or usb mount). Still not working.
Click to expand...
Click to collapse
Can you acces your sdcard by twrp? Lot of poeple here has sd card bug yet and it was fixed everytime.
You're facing sdcard bug.
This is how to solve:
1. Flash stock recovery
2. reboot to bootloader and perform "factory reset + clear storage" (While in bootloader NOT in recovery)
3. Flash custom recovery again
4. Reboot recovery - mount usb storage - copy ROM.zip to sdcard // adb sideload rom
7. NOW boot android (Not at any time before! Even there is no system installed)
Please just repeat it.

LS.xD said:
Can you acces your sdcard by twrp? Lot of poeple here has sd card bug yet and it was fixed everytime.
Click to expand...
Click to collapse
I can acces it in TWRP (of course only a TWRP folder in it). Tried the repeating progress over and over but nothing changes. And USB-OTG isnt able to mount.
Thanks for your patient help!

Akkordinator said:
I can acces it in TWRP (of course only a TWRP folder in it). Tried the repeating progress over and over but nothing changes. And USB-OTG isnt able to mount.
Thanks for your patient help!
Click to expand...
Click to collapse
In case you can acces the storage in twrp its related to windows or drivers. What windows version you are running?

LS.xD said:
In case you can acces the storage in twrp its related to windows or drivers. What windows version you are running?
Click to expand...
Click to collapse
It was windows! Tried it on the other computer with win7 instead of 8.1 and I finally got a connection!
Thanks so much!!!

[Q] TF 700 only boots into TWRP - please advise this NOOB!

Greetings -
I have an unlocked TF700 (twrp v 2.5.0.0) and I was running cromi-x. it began to crash a lot so i tried to flash a new rom and i must've done something wrong because now the tablet will not boot up. I can get into twrp and perform the options listed (install, backup, restore, wipe, mount, settings, advanced, reboot) but nothing seems to help. I haven't played with this in probably 6 months so i'm not sure where to start. Navigating these forums is like reading latin to me. I'm sure there is an explanation for this but I can't find it. Can some one link me to an existing thread if this has been discusses previously or help me out? I can't seem to get anything working on this and it's driving me crazy. I know I need to provide extra information to help identify this issue but i'm not sure what that info that is. Any help would be appreciated!
Also, I've tried a factory reset from twrp as well and it gives me the following messages
E:unable to mount '/external_sdcard
Updating partition details...
E:Mount: Unable to find partition, for path '/'
When I reboot following this, it takes me directly to TWRP.
I'm guessing my tablet can't find my SD card? Maybe that's an easy fix?
Thanks everyone for looking at this and thanks for anyone that takes some time to educate me.

Most if all: Do not do anything desperate anymore. Your tablet is savable at this point but close to being bricked! Wait for help, I have to go to work now, but will be back tonight.
In the meantime write up a list of things you did as good as you can remember, find your bootloader version and post that.

berndblb said:
Most if all: Do not do anything desperate anymore. Your tablet is savable at this point but close to being bricked! Wait for help, I have to go to work now, but will be back tonight.
In the meantime write up a list of things you did as good as you can remember, find your bootloader version and post that.
Click to expand...
Click to collapse
Thank you for the reply. My bootloader is "<1.00 e> released by 10.6.1.14.8-20130514"
It also says "key driver not found" immediately before the bootloader data upon turn on

Ok, good start. Now - what's you situation exactly? Can you boot into the bootloader or is recovery the only thing accessible right now?

berndblb said:
Ok, good start. Now - what's you situation exactly? Can you boot into the bootloader or is recovery the only thing accessible right now?
Click to expand...
Click to collapse
I can enter the bootloader (hold power on and volume down correct?) and it displays RCK, android and wipe data options. It only takes me to recovery tho.

Hoggs17 said:
I can enter the bootloader (hold power on and volume down correct?) and it displays RCK, android and wipe data options. It only takes me to recovery tho.
Click to expand...
Click to collapse
Please try to be very specific. When you enter the bootloader, does it stay there or does it automatically, without your interaction, boot into TWRP?
Did you use the Wipe Data option from the bootloader or do a Factory Reset from the Settings menu?
Do you have fastboot setup on your PC?
If not, find the instructions to setup fastboot here: http://forum.xda-developers.com/showthread.php?t=2688891
You will need it.

berndblb said:
Please try to be very specific. When you enter the bootloader, does it stay there or does it automatically, without your interaction, boot into TWRP?
Did you use the Wipe Data option from the bootloader or do a Factory Reset from the Settings menu?
Do you have fastboot setup on your PC?
If not, find the instructions to setup fastboot here: http://forum.xda-developers.com/showthread.php?t=2688891
You will need it.
Click to expand...
Click to collapse
When i enter the bootloader, it stays on the screen. If i reboot without entering the bootloader, it goes directly into TWRP. I am not sure if i used the wipe data option or the factory reset (it has been probably 6 months). I will install fastboot on my PC now.

Interesting.
I assume you do not have any data on the tablet you need to preserve, right?
Once you got fastboot setup and "fastboot devices" returns the serial number we'll clear your misc partition (just in case) and fastboot erase your data partition. I think after that you should be able to boot the rom.
Actually, remind me, what was the last thing you flashed? Did you update TWRP already or are you still on 2.5.0?

berndblb said:
Interesting.
I assume you do not have any data on the tablet you need to preserve, right?
Once you got fastboot setup and "fastboot devices" returns the serial number we'll clear your misc partition (just in case) and fastboot erase your data partition. I think after that you should be able to boot the rom.
Actually, remind me, what was the last thing you flashed? Did you update TWRP already or are you still on 2.5.5?
Click to expand...
Click to collapse
Correct, i don't need any data on this tablet; i can wipe it clean. I think the last thing i flashed was Cromi-X (not sure the number; was back in August probably. My TWRP is 2.5.0.0; i haven't updated that one. I will try to do the fast stuff tomorrow morning; too late tonight. Thanks for all your help.

Cool. I need to sleep too
Yeah we're going to have to update your TWRP version. 2.5.0 is too old to flash anything recent. And while we're at it we'll update your bootloader too. All in good time. See ya tomorrow

berndblb said:
Cool. I need to sleep too
Yeah we're going to have to update your TWRP version. 2.5.0 is too old to flash anything recent. And while we're at it we'll update your bootloader too. All in good time. See ya tomorrow
Click to expand...
Click to collapse
I have installed the fastboot on my PC, ran it figured out my serial number as well. I will wait for your next instruction so that I don't mess anything up (again).

Hoggs17 said:
I have installed the fastboot on my PC. I will wait for your next instruction so that I don't mess anything up (again).
Click to expand...
Click to collapse
Till Bernd wakes up you could read his excellent guide; most question are answered here:
http://forum.xda-developers.com/showthread.php?t=2688891

das chaos said:
Till Bernd wakes up you could read his excellent guide; most question are answered here:
http://forum.xda-developers.com/showthread.php?t=2688891
Click to expand...
Click to collapse
yes, i have been reading that as well but as I don't want to make a mistake and completely brick this thing; i will research this document and educate myself

Hoggs17 said:
yes, i have been reading that as well but as I don't want to make a mistake and completely brick this thing; i will research this document and educate myself
Click to expand...
Click to collapse
Ok, here's my thinking:
I don't know why the tablet reboots to recovery if you try to boot Android - never seen that before.
That it refuses to boot the rom - seen that plenty
That it only boots to recovery and not even to the bootloader - seen that quite a few times if the user used Wipe Data or factory reset from settings.
You seem to a have a mix of both which makes it unique.
So my advice is:
to clear the misc partition (where a "format data" request may still be lurking) in fastboot
wipe the data partition in fastboot - just general housekeeping
flash a new bootloader and recovery using your current recovery
Use the new recovery to flash the rom of your choice - which one do you have in mind?
So let's start. First make sure you have a fastboot connection:
Code:
fastboot devices
Then erase misc and user data
Code:
fastboot erase misc
fastboot erase userdata
You are still in the bootloader menu, push the Vol Up button on the flashing RCK to enter recovery
Flash the 10.6.1.14.10 bootloader, packaged with TWRP 2.8.4.0 from this post (2nd zip from the bottom)
http://forum.xda-developers.com/showpost.php?p=55238386&postcount=3
You have to reboot after this step for the bootloader and recovery to install.
You'll see a brief blue progress bar, then the tablet will reboot again. At this point hold Vol Down to enter the bootloader and then enter recovery which should be 2.8.4.0 at this point.
Flash the rom
Good luck!

"Flash the 10.6.1.14.10 bootloader, packaged with TWRP 2.8.4.0 from this post (2nd zip from the bottom)
http://forum.xda-developers.com/showpost.php?p=55238386&postcount=3
You have to reboot after this step for the bootloader and recovery to install.
You'll see a brief blue progress bar, then the tablet will reboot again. At this point hold Vol Down to enter the bootloader and then enter recovery which should be 2.8.4.0 at this point.
Flash the rom"
I have successfully completed the steps preceeding the above suggestions; I am not sure how to flash the bootloader. I am trying to follow the guide posted here (http://forum.xda-developers.com/showthread.php?t=2688891) by using the command code
fastboot -i 0x0B05 flash recovery twrp.blob
however, i cannot rename my blob file (contained in the 10.6.1.14.10 bootloader "second zip from the bottom" that you linked me to) to twrp.blob. it is simply called blob. am I doing this wrong? i tried using the above command with just blob and it didn't do anything.
on another thread (http://forum.xda-developers.com/showthread.php?t=2688891) you recommend visiting (http://techerrata.com/browse/twrp2/tf700t) and downloading the latest version of twrp. Should I download this file (openrecovery-twrp-2.8.5.0-tf700t.blob) and rename this to twrp.blob?
Also I am not sure on a new custom rom; i've been out of the game for a while; any suggestions?

No the zip is a flashable package. You install just like a rom zip:
Choose Install in TWRP, navigate to the zip, check the box for signature verification and swipe the button.
This will write the bootloader and recovery to the staging partition. When you reboot the bootloader writes them to their proper partitions, then it reboots the tablet again. That's when you can "catch" the boot process to go straight back into recovery and flash the rom.
Maybe you want to try CROMI-X first. Still a very good rom and very stable. Or check the dev section, many to choose from...

berndblb said:
No the zip is a flashable package. You install just like a rom zip:
Choose Install in TWRP, navigate to the zip, check the box for signature verification and swipe the button.
This will write the bootloader and recovery to the staging partition. When you reboot the bootloader writes them to their proper partitions, then it reboots the tablet again. That's when you can "catch" the boot process to go straight back into recovery and flash the rom.
Maybe you want to try CROMI-X first. Still a very good rom and very stable. Or check the dev section, many to choose from...
Click to expand...
Click to collapse
gotcha. the only problem is; after i use the command on the bootloader and i go to Install on twrp; i don't see the zip to install...i retried it again (repeated the commands) but i'm not seeing the zip in my directory anywhere. hmmm...

Hoggs17 said:
gotcha. the only problem is; after i use the command on the bootloader and i go to Install on twrp; i don't see the zip to install...i retried it again (repeated the commands) but i'm not seeing the zip in my directory anywhere. hmmm...
Click to expand...
Click to collapse
You got the zip on your microSD, right?
Tap on the field where it says Internal Storage and switch to external

berndblb said:
You got the zip on your microSD, right?
Tap on the field where it says Internal Storage and switch to external
Click to expand...
Click to collapse
oops; yeah i was blind; forgot to switch the internal to external storage. ok now I see twrp and I am able to swipe to flash but the flash fails and gives me the following message
Updating partition details...
Installing '/external_sdcard/TF700_10.6.1.14.10_US_Boot_TWRP_2840-signed.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/external_sdcard/TF700_10.6.1.14.10_US_Boot_TWRP_2840-signed.zip'
Updating partition details...
with a big red Failed right above the home key.

Hoggs17 said:
oops; yeah i was blind; forgot to switch the internal to external storage. ok now I see twrp and I am able to swipe to flash but the flash fails and gives me the following message
Updating partition details...
Installing '/external_sdcard/TF700_10.6.1.14.10_US_Boot_TWRP_2840-signed.zip
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Verifying zip signature...
E: Zip signature verification failed: 1
Error flashing zip '/external_sdcard/TF700_10.6.1.14.10_US_Boot_TWRP_2840-signed.zip'
Updating partition details...
with a big red Failed right above the home key.
Click to expand...
Click to collapse
..... which means the file got corrupted during download or copy to the card.
That's what signature verification is for.
Download it again.