Database Info

[Q] Can't access root and Google apps

I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.

SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!

I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?

Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.

Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?

Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.

Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.

Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.

1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.

3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.

Where do I go to get the recovery image?

The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.

Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.

Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.

There isn't a link...

Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.

It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.

I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.

I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.

Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back

My Asus TF300T Is Completely Dead!

I had upgraded to 4.2 firmware (WW_epad-user-10.6.1.8) using the second method described on http://forum.xda-developers.com/showthread.php?t=2187982. This worked well and everything was working until I messed up today D: I was trying to flash SuperSU using TWRP but it couldn't recognize my Internal SD Card so I thought there might be something wrong with my installation. When I entered the bootloader I noticed the message: Key driver not found.. Booting OS. I don't know what this means. I did not read the first thread in the General section and tried to do a restore using the 4.2 firmware package. I used the "fastboot flash system blob" command and this time everything was messed up. The blue bar that appears on installation is no longer appearing and I have an "unrecoverable bootloader" error. Nothing I did worked! What should I do?? Please provide me some simple steps. I used these commands before flashing system blob...
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
This was a very stupid move on my part but I thought this would allow a clean install D: D: Please help!

gee man you completely wiped the sucker, you may be bricked =(. i would start by trying to fastboot flash the patched version of twrp. unless you can boot into twrp already then try to flash the asus package again thru twrp. also, could twrp see your internal sd before you bricked?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

markymark567 said:
gee man you completely wiped the sucker, you may be bricked =(. i would start by trying to fastboot flash the patched version of twrp. unless you can boot into twrp already then try to flash the asus package again thru twrp. also, could twrp see your internal sd before you bricked?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
No, that is the reason why I wiped everything (stupid move I know)...TWRP was screwed up to begin with. I flashed 2.5 JB version and it couldn't detect my internal SD card. I made sure it was the right model and everything so TWRP messed me up. I don't know how to flash a working version of TWRP since I don't know what version works with 4.2 tf300 firmware.

sonar2854 said:
No, that is the reason why I wiped everything (stupid move I know)...TWRP was screwed up to begin with. I flashed 2.5 JB version and it couldn't detect my internal SD card. I made sure it was the right model and everything so TWRP messed me up. I don't know how to flash a working version of TWRP since I don't know what version works with 4.2 tf300 firmware.
Click to expand...
Click to collapse
there is a modded 2.4.4 version i believe that sees all correctly. the post on how to root and update describe and link it. but being now you flashed the wrong one. you cant mount anything to flash correct one. i think you are s.o.l. i hope iam am wrong. good luck.

kaos420 said:
there is a modded 2.4.4 version i believe that sees all correctly. the post on how to root and update describe and link it. but being now you flashed the wrong one. you cant mount anything to flash correct one. i think you are s.o.l. i hope iam am wrong. good luck.
Click to expand...
Click to collapse
I'm not sure how to flash it...I tried fastboot flash recovery twrp.blob (2.4.4.0 v4.2). It just freezes although the cmd says it was successful

I keep getting a bootloader error (0x0000000) everytime I try and enter RCK, Android, Wipe Data... Is there a way to reinstall the bootloader? WW_epad 10.6.1.8

No mate
As of now there's no solution to that.
Do ppl ever read before they flash? I've never seen as much bricks as I've seen on this device since the new 10.6x.x Asus bootloader... it's a shame
Read read read, understand understand understand, then read more. I almost feel sorry for you guys who are "just flashing away"

FML :crying::crying:

sonar2854 said:
I keep getting a bootloader error (0x0000000) everytime I try and enter RCK, Android, Wipe Data... Is there a way to reinstall the bootloader? WW_epad 10.6.1.8
Click to expand...
Click to collapse
Bump!
I have a couple of questions.
I would like to know about your bootloader (how many icons and which ones) and whether you can still get into twrp.

tobdaryl said:
Bump!
I have a couple of questions.
I would like to know about your bootloader (how many icons and which ones) and whether you can still get into twrp.
Click to expand...
Click to collapse
Okay, so when I press Volume Down + Power, I enter the bootloader. The bootloader has three icons: RCK, Android Logo, Wipe Data. I have no access to TWRP since there is a unrecoverable bootloader error 0x0000000 when I try to enter RCK.

sonar2854 said:
Okay, so when I press Volume Down + Power, I enter the bootloader. The bootloader has three icons: RCK, Android Logo, Wipe Data. I have no access to TWRP since there is a unrecoverable bootloader error 0x0000000 when I try to enter RCK.
Click to expand...
Click to collapse
The odds are slim but let's try a couple of things.
From power off, hold power and volume down, release when you see the icons. You should see the entering fastboot message in the upper left.
fastboot -i 0x0B05 reboot bootloader
if that fails
Power off and use the same procedure.
fastboot reboot bootloader
Tell me the result.

tobdaryl said:
The odds are slim but let's try a couple of things.
From power off, hold power and volume down, release when you see the icons. You should see the entering fastboot message in the upper left.
fastboot -i 0x0B05 reboot bootloader
if that fails
Power off and use the same procedure.
fastboot reboot bootloader
Tell me the result.
Click to expand...
Click to collapse
Okay, I tried both and it doesn't work without adding a hyphen in between reboot and bootloader so reboot-bootloader. Otherwise, with the hyphen added, both work.

sonar2854 said:
Okay, I tried both and it doesn't work without adding a hyphen in between reboot and bootloader so reboot-bootloader. Otherwise, with the hyphen added, both work.
Click to expand...
Click to collapse
Sorry for that mistake. Now try rck and let's see if the bootloader is now accepted. If we are lucky the result has changed.

tobdaryl said:
Sorry for that mistake. Now try rck and let's see if the bootloader is now accepted. If we are lucky the result has changed.
Click to expand...
Click to collapse
Eh...I don't really know how to explain this but this is what happened. Once the bootloader rebooted after entering the CMD command, I pressed volume up to access RCK and there was a "blink" and there is now a green glowing square around the Android Icon. I cannot move the volume up or down (it is frozen on the Android Icon with the green square glowing), so I don't know what that "blink" was. If i try to press volume up now there is the bootloader error again.

sonar2854 said:
Eh...I don't really know how to explain this but this is what happened. Once the bootloader rebooted after entering the CMD command, I pressed volume up to access RCK and there was a "blink" and there is now a green glowing square around the Android Icon. I cannot move the volume up or down (it is frozen on the Android Icon with the green square glowing), so I don't know what that "blink" was. If i try to press volume up now there is the bootloader error again.
Click to expand...
Click to collapse
Download the 10.4.2.20 stock firmware. Unzip once and rename the resulting zip EP201_768_SDUPDATE.zip. Place this on your external sdcard and boot into your bootloader. Volume up on RCK.

tobdaryl said:
Download the 10.4.2.20 stock firmware. Unzip once and rename the resulting zip EP201_768_SDUPDATE.zip. Place this on your external sdcard and boot into your bootloader. Volume up on RCK.
Click to expand...
Click to collapse
Um, I don't have an external SD Card? The only SD Card I have is the Internal Storage

sonar2854 said:
Um, I don't have an external SD Card? The only SD Card I have is the Internal Storage
Click to expand...
Click to collapse
Uh!
Tell me what 2.5 JB version is.
Unzip 10.6.1.8 stock firmware twice and place the blob file into the directory with adb and fastboot. Boot into the bootloader and don't press anything.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
if the command fails try again without -i 0x0B05

tobdaryl said:
Uh!
Tell me what 2.5 JB version is.
Unzip 10.6.1.8 stock firmware twice and place the blob file into the directory with adb and fastboot. Boot into the bootloader and don't press anything.
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 reboot
if the command fails try again without -i 0x0B05
Click to expand...
Click to collapse
When you say 2.5 JB version...are you talking about TWRP? I don't think TWRP is on the tablet because I can't access it. All I saw was a blink when I pressed volume up on RCK, not TWRP? I have tried flash system blob before I posted here and it did nothing. There is no progress bar when fastboot flashing =/ I think it froze. Yup it froze, just tried to do fastboot reboot-bootloader and it said failed. Also, after the system was done writing, after 2 seconds it said complete so it didn't work.

sonar2854 said:
When you say 2.5 JB version...are you talking about TWRP? I don't think TWRP is on the tablet because I can't access it. All I saw was a blink when I pressed volume up on RCK, not TWRP? I have tried flash system blob before I posted here and it did nothing.
Click to expand...
Click to collapse
I understood about twrp and flashing system blob but I thought we had been able to get stock recovery working instead of twrp.
I 'm sorry that is all I have with no sdcard and no adb.

tobdaryl said:
I understood about twrp and flashing system blob but I thought we had been able to get stock recovery working instead of twrp.
I 'm sorry that is all I have with no sdcard and no adb.
Click to expand...
Click to collapse
I have never used the stock recovery so what is it supposed to look like? Is it that dead Android with the battery because that didn't show up? I will try and get an external sd card tomorrow and try it if you think it might work. I have the 4.2 bootloader so are you sure that I should put Version V10.4.2.20 and recover using that version? Anyways, if it ends up not working, I would just like to say thank you very much for trying.

[Q] Nexus 5, internal storage 0Mb

Hi everyone,
I am French and I use a translator to talk to you, sorry for language mistakes.
I just ask for your help because at last my nexus one days is blocked.
When I go into TWRP he asks me a passeword and my internal memory shows 0MB
Unable to flash a rom stock, steps go well but it does not change anything in the nexus.
Unable to update bootloader, the old version back
I focused in fastboot and recovery (TWRP)
Do you have a solution?
Thanking you in advance
Loïc

Sounds like uv messed up the partitions. unsure if theres a fix on this

Try
fastboot flash cache cache.img
Where cache.img is from the factory image

jd1639 said:
Try
fastboot flash cache cache.img
Where cache.img is from the factory image
Click to expand...
Click to collapse
This is happening without any problems but it does not change the problem.
I'm lost ...

in TWRP i have
E:Unable to mount ' /cache'
E:Unable to mount ' /persist'
E:Unable to mount storage

Problems:
Internal-memory found in TWRP (internal storage: 0MB)
-In flash, everything seems to work well but the file does not replace those on the laptop (eg when I erase bootloader and flash I HHZ11K to replace HHZ11D there was the nexus, the ben 11D never deletes
-Unable to wipe dalvik Cache
TWRP-request a password, so I'm Cancel to use the recovery
Impossible to replace the recovery with a stock version everything seems ok but always returns TWRP
Thank you for your help

worfeur said:
Problems:
Internal-memory found in TWRP (internal storage: 0MB)
-In flash, everything seems to work well but the file does not replace those on the laptop (eg when I erase bootloader and flash I HHZ11K to replace HHZ11D there was the nexus, the ben 11D never deletes
-Unable to wipe dalvik Cache
TWRP-request a password, so I'm Cancel to use the recovery
Impossible to replace the recovery with a stock version everything seems ok but always returns TWRP
Thank you for your help
Click to expand...
Click to collapse
What version of twrp are you using?

jd1639 said:
What version of twrp are you using?
Click to expand...
Click to collapse
I use twrp 2.6.3.2

worfeur said:
I use twrp 2.6.3.2
Click to expand...
Click to collapse
Try to flash this in fastboot, fastboot flash recovery recovery.img. Where recovery.img is the file below. If it installs, wipe cache within it
http://d-h.st/nbu. It's 2.6.3.4

This very same thing happened to me this morning, and a friends Nexus 5 the other day. Not sure why but the fact that you are the third I have seen in the last few days is making me believe it's a common issue. It happened to me, I watched a movie, fell asleep, and woke up to "Type password to decrypt storage" message, and the same message you have in Recovery as well. To my knowledge, I never set a password, let alone while I slept.
What happened is somehow the "userdata" partition on the phone got corrupt. When this happens, for some reason it thinks the partition was encrypted. You can attempt to fix it with a repair utility, or
Go to the bootloader (Hold Volume Down and Power when turning the phone on) then install and use adb and type this
Code:
adb e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Or from recovery, run a command and and run
Code:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
See if that works. If it does, your data will be fine. I did not find this fix until after I tried a full reset but it worked for my friend.
If that does not work, you will have to factory reset your phone. You will lose all data on the phone. Hopefully you have a backup. This worked for me.
Use tools from here:
https://developers.google.com/android/nexus/images#hammerhead
and follow instructions here http://forum.xda-developers.com/showthread.php?t=2513701
I see you mentioned you tried this, however you may want to try it again, and follow those steps, make sure to go to the Nexus 5's factory recovery after and "Reset to Factory". Likewise it needs to be run from bootloader, not recovery. And you must have unlocked bootloader.
**EDIT** What firmware were you running? CyanogenMod?

N5
1. you unlock it
2. recovery with software.
Thanks

Wergin said:
1. you unlock it
2. recovery with software.
Thanks
Click to expand...
Click to collapse
What firmware were you using prior to this happening? I would like to know as me and a friend were on CyanogenMod11 (CM11) and this happened to us as well. If CyanogenMod or TWRP is causing it, it should be reported as a bug.

worfeur said:
Hi everyone,
I am French and I use a translator to talk to you, sorry for language mistakes.
I just ask for your help because at last my nexus one days is blocked.
When I go into TWRP he asks me a passeword and my internal memory shows 0MB
Unable to flash a rom stock, steps go well but it does not change anything in the nexus.
Unable to update bootloader, the old version back
I focused in fastboot and recovery (TWRP)
Do you have a solution?
Thanking you in advance
Loïc
Click to expand...
Click to collapse
Why don't you try Clock work mod recovery. Sounds like twrp isn't meshing well with you device. I had issues with all the way to lastest version.Maybe CWM might help.

WoodburyMan said:
What firmware were you using prior to this happening? I would like to know as me and a friend were on CyanogenMod11 (CM11) and this happened to us as well. If CyanogenMod or TWRP is causing it, it should be reported as a bug.
Click to expand...
Click to collapse
Sorry, I do not know the firmware that was installed
It is a device used
habitformer said:
Why don't you try Clock work mod recovery. Sounds like twrp isn't meshing well with you device. I had issues with all the way to lastest version.Maybe CWM might help.
Click to expand...
Click to collapse
when I flash a custom-recovery (stock or cwn) TWRP 2.6.3.2 always returns

I had this same issue.
I went into fastboot and erased recovery and userdata, then ran the flashall.bat in the factory image.
TWRP had a Password. It happened after I tried to flash Cataclysm and it bootlooped (Forgot to check MD5's, not sure why a corrupt download flashed).

WoodburyMan said:
This very same thing happened to me this morning, and a friends Nexus 5 the other day. Not sure why but the fact that you are the third I have seen in the last few days is making me believe it's a common issue. It happened to me, I watched a movie, fell asleep, and woke up to "Type password to decrypt storage" message, and the same message you have in Recovery as well. To my knowledge, I never set a password, let alone while I slept.
What happened is somehow the "userdata" partition on the phone got corrupt. When this happens, for some reason it thinks the partition was encrypted. You can attempt to fix it with a repair utility, or
Go to the bootloader (Hold Volume Down and Power when turning the phone on) then install and use adb and type this
Code:
adb e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Or from recovery, run a command and and run
Code:
e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
See if that works. If it does, your data will be fine. I did not find this fix until after I tried a full reset but it worked for my friend.
If that does not work, you will have to factory reset your phone. You will lose all data on the phone. Hopefully you have a backup. This worked for me.
Use tools from here:
https://developers.google.com/android/nexus/images#hammerhead
and follow instructions here http://forum.xda-developers.com/showthread.php?t=2513701
I see you mentioned you tried this, however you may want to try it again, and follow those steps, make sure to go to the Nexus 5's factory recovery after and "Reset to Factory". Likewise it needs to be run from bootloader, not recovery. And you must have unlocked bootloader.
**EDIT** What firmware were you running? CyanogenMod?
Click to expand...
Click to collapse
thank you for your help
I have access to adb fastboot mode by boot recovery.img (recovery stock google)
and using the control slidload ADB
but impossible to get the command line
but when I type ADB Devices, my phone is found
otherwise I can not do a stock restoration because the bootloader does not update (KKX11D then I flashed back KKX11K) when I do well:
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader

Beauenheim said:
I had this same issue.
I went into fastboot and erased recovery and userdata, then ran the flashall.bat in the factory image.
TWRP had a Password. It happened after I tried to flash Cataclysm and it bootlooped (Forgot to check MD5's, not sure why a corrupt download flashed).
Click to expand...
Click to collapse
thank you I'll try it tonight but I think I already tried

worfeur said:
thank you I'll try it tonight but I think I already tried
Click to expand...
Click to collapse
In twrp 2.6.3.4 go into wipe and format data. You will lose all your data but should fix your problem

jd1639 said:
In twrp 2.6.3.4 go into wipe and format data. You will lose all your data but should fix your problem
Click to expand...
Click to collapse
the problem when another flash recovery is that the 2.6.3.2 version still returns
let me explain:
fastboot erase recovery
fastboot flash recovery recovery TWRP 2.6.3.4.img
* I go into the recovery but still 2.6.3.2
I feel that TWRP to secure or encrypted my internal memory

worfeur said:
the problem when another flash recovery is that the 2.6.3.2 version still returns
let me explain:
fastboot erase recovery
fastboot flash recovery recovery TWRP 2.6.3.4.img
* I go into the recovery but still 2.6.3.2
I feel that TWRP to secure or encrypted my internal memory
Click to expand...
Click to collapse
Can you format data in 2.6.3.2? I'm thinking you have a bigger problem as you've already tried to flash the factory image and it did not work.

[Q] CROMBi-kk flash

Hi!
I hope you can help me.
I obviously did something wrong.
Well I did unlock my tablet and got twrp running, also installed the rom but next after the reboot it just doesn't work and i will get this message (see the picture)
After that i am sent back to the interface of twrp.
I just recogniced I have twrp v.2.6.1.0 running - is that the problem?
Hopefully somebody can help me!
greets agepi

agepi91 said:
Hi!
I hope you can help me.
I obviously did something wrong.
Well I did unlock my tablet and got twrp running, also installed the rom but next after the reboot it just doesn't work and i will get this message (see the picture)
After that i am sent back to the interface of twrp.
I just recogniced I have twrp v.2.6.1.0 running - is that the problem?
Hopefully somebody can help me!
greets agepi
Click to expand...
Click to collapse
YOU MUST BE ON THE ASUS STOCK JB 4.2.1 BOOTLOADER VERSION 10.6.1.14.x AND TWRP 2.6.3.2+ OR CWM 6.0.4.6+ BEFORE FLASHING THIS ROM.
This is copied directly from the Developers ROM.
Cheers

agepi91 said:
Hi!
I hope you can help me.
I obviously did something wrong.
Well I did unlock my tablet and got twrp running, also installed the rom but next after the reboot it just doesn't work and i will get this message (see the picture)
After that i am sent back to the interface of twrp.
I just recogniced I have twrp v.2.6.1.0 running - is that the problem?
Hopefully somebody can help me!
greets agepi
Click to expand...
Click to collapse
You didn't use 'Wipe Data' from the bootloader, did you?
Read the OP for CROMBI-KK, compare it to what you did.
Describe in detail what that was.
"Does not work" is not very helpful...
Check if you can get into fastboot.
Sent from my DROID4 using Tapatalk

Well,
I can go to Twrp recovery and fastboot
I did install the rom with everything present I think.. had to select some things and finish the installing
after that I had to reboot and now i just get the image with the penguins.
Can I somehow go back to the original rom? to restart these things?

agepi91 said:
Well,
I can go to Twrp recovery and fastboot
I did install the rom with everything present I think.. had to select some things and finish the installing
after that I had to reboot and now i just get the image with the penguins.
Can I somehow go back to the original rom? to restart these things?
Click to expand...
Click to collapse
If you made a nandroid before flashing this, then yes, you should be able to restore it.
But let's take it from the beginning. Post your bootloader, recovery and rom versions.
As long as you have access to fastboot you can fix this, so don't do anything hasty.
And please be as specific as you can about what you did. We can only help you if we find out where you went wrong.

berndblb said:
If you made a nandroid before flashing this, then yes, you should be able to restore it.
But let's take it from the beginning. Post your bootloader, recovery and rom versions.
As long as you have access to fastboot you can fix this, so don't do anything hasty.
And please be as specific as you can about what you did. We can only help you if we find out where you went wrong.
Click to expand...
Click to collapse
hm ok I will try
well, I didn't make a nandroid backup - my fault :<
are there specific bootloader? I was on JB 4.2.1
I am now on twrp v2.6.3.2 but I was while I did the flashing on twrp v2.6.1
hm I did flash crombi-kk rom from the OP
maybe I did some wipe before in twrp .. i think it was recommended?
so now I can't do any reflash or anything in twrp - everytime I want to do something there is this error:
E: Unable to open '/cache/recovery/.version'
I also can't get access to my external SD

Check if you can get into fastbot.
Long press Power and Volume Down until you see tiny script.
Read it and post the bootloader version: 10.6.1.14.?

berndblb said:
Read it and post the bootloader version: 10.6.1.14.?
Click to expand...
Click to collapse
Well it reads: ww_epad-10.6.1.14.10-20130801

agepi91 said:
Well it reads: ww_epad-10.6.1.14.10-20130801
Click to expand...
Click to collapse
All right, your bootloader is current.
I would recommend that you flash TWRP 2.7 in fastboot, then boot into it, do a Factory Wipe in TWRP (that can take upwards of 60 minutes) and flash the rom again.

Ok.. I tried but I got the answer
failed (data transfer failure (too many links))
hm I think I've got no connection, right?
well and now I get the message:
FAILED ( command write failed( invalid argument))

What do you get with 'fastboot devices'?
Sent from my K00C using Tapatalk

I get 015d2a5068541017 fastboot

agepi91 said:
I get 015d2a5068541017 fastboot
Click to expand...
Click to collapse
Alright, everything good so far.
Now download the TWRP 2.7 blob for the tf700 and put it into the same folder as your fastboot.exe.
Then issue this command:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
if that is successful
Code:
fastboot reboot
Then boot into TWRP via the fastboot menu.
Then you can factory wipe and flash the rom

berndblb said:
Alright, everything good so far.
Now download the TWRP 2.7 blob for the tf700 and put it into the same folder as your fastboot.exe.
Then issue this command:
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
if that is successful
Code:
fastboot reboot
Then boot into TWRP via the fastboot menu.
Then you can factory wipe and flash the rom
Click to expand...
Click to collapse
Well I did that but nothing works
I've got now twrp 2.7 and i did that factory wipe but nothing ever happens.. just the usual message
'unable to open 'cache/recovery/.version'
Don't know what I did wrong :<
http://imageshack.com/a/img842/662/kwy9.png
that's the message I everytime get - doesn't matter if it's a wipe or install or something else

in bootlooder at the top there is this message:
>key driver not found... booting 05<

is it possible to formate my complete data, because I think therein lies the problem, exept fastboot on my device and flash a recovery from fastboot?

agepi91 said:
is it possible to formate my complete data, because I think therein lies the problem, exept fastboot on my device and flash a recovery from fastboot?
Click to expand...
Click to collapse
If you want to try that, go to the Wipe menu in TWRP, then to Advanced and choose "format data".
In TWRP this can take 90 minutes! D not interrupt it and make sure the tablet is charged or connected to power.
But this will erase your entire data.
The recovery has it's own partition which you can erase in fastboot:
Code:
fastboot erase recovery
.
Then flash the new recovery. You could also try TWRP 2.6.3.2 if 2.7 doesn't work.

agepi91 said:
is it possible to formate my complete data, because I think therein lies the problem, exept fastboot on my device and flash a recovery from fastboot?
Click to expand...
Click to collapse
Your posted image indicates that simulation mode is active in TWRP - turn if off in TWRP settings.
To format data, it's approximately this: Wipe -> Advanced -> Format -> Data -> confirm
Note that it takes up to 2 hours to format and trim the eMMC.
---------- Post added at 09:15 PM ---------- Previous post was at 09:14 PM ----------
berndblb said:
The recovery has it's own partition which you can erase in fastboot:
Code:
fastboot erase recovery
.
Click to expand...
Click to collapse
...which is usually a stupid idea if you don't know exactly what you are doing.

Well I don't know how but it suddenly worked.. i could reinstall the rom but now it seems i am stuck in a bootloop between the picture of the four penguins and a bootscreen of crombi-kk with loading tiles under it
between these two the tablet is rebooting itself constantly

Go back to recovery and do a wipe only Calvin cache and Cache.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

I think I may have softbricked my TF300T trying to flash to KatKiss 6.0

Hi all,
I'm a total noob here. Somehow I managed to unlock and root my ASUS TF300T successfully, even though the instructions I was referring to were sketchy. Unfortunately I started the process before finding the detailed instructions here on how to flash the ROM. So it looks like I misinterpreted the sketchy instructions and hosed up the process. I managed to get the Katkiss zip file on the internal SD of the tablet, but when I tried to install it, it failed.
I now know where I went wrong so I'm not sure if it's fixable now: Rather than wipe while in TWRP, I wiped from the main bootloader screen (RCK, Android, WIPE DATA). Idiotic noob mistake which I realize now, but too late.
Currently when I attempt to boot up using the power + down volume, my screen shows:
Code:
Key driver not found.. booting OS
Android cardhu-user bootloader <1.00 e> released by "US-epad-10.6.1.27.5-20130902" A03
If I select RCK, I can get to TWRP, but it can't find a way to push the stock ROM file from ASUS from my PC back to the tablet. I tried using ADB push, but I get an error that it's not a valid command.
I can see the tablet in Device manager if I connect using the USB, but when I use the ADB devices command, nothing is returned - no error message, no device information.
Any thoughts on how whether it's possible to get back to the stock ROM? It shows
Code:
The Device is Unlocked.
on the ASUS splash screen but always boots to TWRP if I do not hold the down-volume button when starting up. I'm not sure if it's still rooted.
Thanks in advance for any suggestions!

I would like to advise you to get back on stock rom without any further experiments.
First of all the USB driver must be installed on your PC.
-Download “Minimal ADB and Fastboot”.
-Make a folder C:/Fastboot and extract it there and install it. Download the latest firmware V10.6.1.27.5 fitting to your device from the ASUS official website and unzip it twice.
-Copy the .blob file into the folder C:/Fastboot.
-Start “Minimal ADB and Fastboot” and put in "fastboot devices". The device should appear as "xxx device".
Now type in step by step (wait after every step!):
fastboot erase system
fastboot erase recovery
Fastboot erase user data
fastboot erase boot
fastboot erase misc
fastboot erase cache.
After that put in "fastboot -i 0x0B05 flash system blob" without " " .
Now it takes a while "sending..." appears then "write..." and the load status will be shown.
If loading is finished put in "fastboot -i 0x0B05 reboot". It takes a while to start into a clean JB 4.2.2!
After that you are ready to flash Kang TWRP 2.8.7.2 again and make a clean install of a custom rom of your choice by taking care exactly of the instruction given by Timduru in each post #1 of each CR.

Thank you for your reply, ebonit. It looks like I have an older version of TWRP currently installed: v2.5.0.0. Is that a problem? If I'm going to flash TWRP again, should I definitely overwrite the current install with Kang TWRP 2.8.7.2?
Thanks again. I may have additional questions because I'm totally new to this and there's so much information out there. I appreciate your patience!

RedSkies said:
Thank you for your reply, ebonit. It looks like I have an older version of TWRP currently installed: v2.5.0.0. Is that a problem? If I'm going to flash TWRP again, should I definitely overwrite the current install with Kang TWRP 2.8.7.2?
Thanks again. I may have additional questions because I'm totally new to this and there's so much information out there. I appreciate your patience!
Click to expand...
Click to collapse
For all MM 6.0.1 and N 7.1.0 versions you need Kang TWRP 2.8.7.2. That's mandatory as seen in each post #1.
If you get back on stock rom, you don't have any custom recovery remaining. There is nothing to overwrite. You must flash Kang TWRP anyway. After that you may flash any custom rom of your choice as clean install.

Thank you so much for your help. It looks like I'm back to the stock ROM. I will try flashing Katkiss later when I can give it my full attention and am less likely to make stupid errors!

RedSkies said:
Thank you so much for your help. It looks like I'm back to the stock ROM. I will try flashing Katkiss later when I can give it my full attention and am less likely to make stupid errors!
Click to expand...
Click to collapse
I cannot stress this enough. MAKE AN NVFLASH BACKUP ASAP!!!! I bricked my device 2-3 years ago and had I made an NVFlash backup I could have recovered it. Unfortunately I did not have a backup and so I just had the tablet sit on my shelf until a few days ago when I finally got a replacement motherboard and swapped the bricked one out. Again MAKE AN NVFLASH BACKUP. You can use the flatline utility described in one of the threads in this device's forum here on XDA.
Sent from my Nexus 6 using XDA-Developers mobile app

Can someone give me more detailed help MM 6.01?
ebonit said:
For all MM 6.0.1 and N 7.1.0 versions you need Kang TWRP 2.8.7.2. That's mandatory as seen in each post #1.
If you get back on stock rom, you don't have any custom recovery remaining. There is nothing to overwrite. You must flash Kang TWRP anyway. After that you may flash any custom rom of your choice as clean install.
Click to expand...
Click to collapse
Ebonit, this is what I need to know, all underlined.
Can anyone give me complete step by step instructions on how to install MM 6.01 on my TF300t. It's so slow it's annoying and unusable. I am a newbie and don't understand how to flash this and flash that and do several other steps... more detailed instructions for each step below would be so helpful. I would be more than happy to make a payment donation for more detailed help.. thanks! Cindy
Install KANG TWRP Recovery
Backup everything !
Boot into the recovery
Click to expand...
Click to collapse
The first time or everytime you have an issue when dirty flashing (Especially when changing android versions):
do a full wipe , if you have issues make sure that you format /data (format is different than wipe)
Warning: formatting will remove what is stored in your internal storage, so store the rom /gapps/supersu zips onto an external storage (microSD, SD card..) or make sure you know how to push them back through adb.
Change /data filesystem to f2fs
Then everytime (even when "dirty flashing") do the following steps:
Flash the rom
Flash the SuperSU zip
Flash gapps
Wipe cache/dalvik
Reboot

What do you want? Every information you need is written in your post. Any further questions you may have will be find an answer somewhere in the forum.
Kang TWRP is the most important tool. It will do the job. Do you have it?
If not, look here http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. There is the install instruction as well.
If yes, then start into recovery and and realize step by step what you found in post #1 and is written down by yourself in your post itself.