Database Info

New to Nexus, stuck in Fastboot! Please Help!

Hey guys,
I'm brand new to the Nexus S but I'm not new to flashing/rooting etc. However I am having an issue here.
I successfully unlocked my bootloader today, and flashed CWM Recovery, rooted, and finally flashed CM7. I wanted to try Netarchy's kernel, so I installed Kernel Manager from the market and tried that way (been wanting to try out that app anyways). Well, I got an error, something about insufficient memory. The error message said I should reboot and try again.
So I rebooted.
Well now I am stuck in fastboot menu with "NO BOOT OR RECOVERY IMG" at the top of the screen.
So, I copied CWM recovery back into my AndroidSDK\Tools folder, and did
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
but I just keep getting
Code:
error: cannot load "recovery-clockwork-3.0.2.4-crespo.img"
I reinstalled drivers and tried again. Same error.
I double checked file name, tried renaming the recovery image file name, made sure it was in the same directory as fastboot.exe. If I do
Code:
fastboot devices
it DOES see my phone. I just can't get the recovery image to flash!
Can someone please help me???

Does your computer show the extensions of the files?
E.G. does fastboot appear as "fastboot" or "fastboot.exe" ?
And I'd recommend using 3.0.2.5 rather than 3.0.2.4. 3.0.2.4 is known to have bugs with it working. Your phone needs to be in bootloader mode in order for this command to work. http://forum.xda-developers.com/showthread.php?t=988686

Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.

matt2053 said:
Originally, just fastboot. But I changed the folder view to not hide known extensions so I could double check an make sure I hadn't named it recovery.img.img or something. Unfortunately that doesn't seem to be the issue.
Click to expand...
Click to collapse
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?

zephiK said:
Hm. thats where I was going towards. Try fastboot flashing the 3.0.2.5 recovery, its also weird that it says no boot img.
What kind of Nexus S do you have? 9020A, 9020T, 9023?
Click to expand...
Click to collapse
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Trying your link now.

matt2053 said:
9020T
I think maybe Kernel Manager formatted those partitions, tried to flash the kernel, error, but no rollback or backup.....
Click to expand...
Click to collapse
I personally flash kernels manually. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)

zephiK said:
I personally flash kernels by myself. I'm going to upload this bootloader, I couldn't find it on XDA anymore but its a bootloader img that was from 2.3.3. it's the I9020XXKA3 bootloader
http://www.mediafire.com/download.php?sn9fu022r88w2n7
MD5: BBA9E3926224CA5C9B4DF891F50F1A90
(verify its MD5 hash.. if you don't know how, google HashTab)
place the file in /sdk/tools/
assure your phone is in bootloader mode (with android in the back)
fastboot flash bootloader bootloader.img
what happens? BE SURE that your phone is indeed 9020T before flashing this (incase anybody else with another model attempts this)
Click to expand...
Click to collapse
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.

matt2053 said:
I usually flash them myself too. I was just interested in trying out the app because I've used some very cool stuff from the dev (shinzul) in my HTC Evo days.
I got the same error on the CWM 3.0.2.5.
I will try flashing the bootloader now. Thanks for taking the time.
Click to expand...
Click to collapse
I just found it awkward that your phone said:
"NO BOOT OR RECOVERY IMG"
Click to expand...
Click to collapse
Let me know the results.
my bootloader appears as:
FASTBOOT MODE
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - I9020XXKA3
BASEBAND VERSION - I9020XXKB3
CARRIER INFO - TMB
SERIAL NUMBER - <removed>
LOCK STATE - UNLOCKED
and the navigational stuff
Click to expand...
Click to collapse

Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.

matt2053 said:
Hmmmmm well I got "error: cannot load 'bootloader.img'."
I'm beginning to wonder if the problem is on my PC side, with fastboot or something.
Click to expand...
Click to collapse
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.

zephiK said:
you're placing it in /sdk/tools right? The Android SDK has to be matched up with 2.3.X.
Try starting all over. Uninstall drivers for your phone. Redownload the Android SDK.
As a last resort, you can try Odin but I haven't had any experience with it on the Nexus S so I can't help you with that but if you want to try Odin thats your choice.
Part 1 will get you started: http://forum.xda-developers.com/showthread.php?t=895545
It's very possible you have a bad version of the SDK. So try this, if it doesn't work try Odin imo.
Click to expand...
Click to collapse
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!

matt2053 said:
yes that was where I placed it.
I'm reinstalling SDK and drivers. I don't think we'll need Odin. I think my fastboot was just wonky. I had installed/moved/reinstalled/uninstalled the SDK several times today trying to get the stoopid drivers installed. PDANet was the only thing that ever worked!
Click to expand...
Click to collapse
if anything... if you have another system, you could try it on that system. you could also try it in another USB socket.
i mean, i dont think its your drivers but it doesnt hurt to see if it thats the problem.. your device was detected.
so your phone is unable to start up (get past google) and not able to get into recovery?

Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!

matt2053 said:
Holy **** I finally got it.
I had to enter the filepath and file. Derp.
Code:
fastboot flash recovery recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Not Work ^^^^^
Code:
fastboot flash recovery c:\android\tools\recovery-clockwork-3.0.2.4-crespo.img
^^^^^ Did Work ^^^^^
Whew, I was scared there for a bit!
THANKS for your help dude!!!
Click to expand...
Click to collapse
... WOW! i thought you knew that.
if you want the first command to work you have to do:
cd C:\android\tools\
fastboot flash recovery recovery.. blah blah blah
Click to expand...
Click to collapse
but congrats it was all you!

Yeah I must have had a brain fart. I obviously did it correctly earlier in the day when I flashed Clockwork originally. I was thinking the environment variable editing I did handled the need for the directory but I guess that's only for the command not the file.
Well, all is good now anyway!
Sent from my Nexus S using XDA App

Another Recovery

If anybody need recovery, full worked with new 4.1.1 JB get it here.
Moderator Edit:
Link removed as it is proven this recovery can damage your device.

Gigabyte0 said:
If anybody need recovery, full worked with new 4.1.1 JB get it here
Click to expand...
Click to collapse
What exactly is that, where is it from?
Recovery shouldn't have anything to do with installed Android version.
Sent from my GT-I9000 using xda app-developers app

pawitp said:
What exactly is that, where is it from?
Recovery shouldn't have anything to do with installed Android version.
Sent from my GT-I9000 using xda app-developers app
Click to expand...
Click to collapse
If I were to guess, it's a different CWM recovery using JB Kernel?. It probably came from 4pda.ru which is a russian site. HAs a lot of android tablet stuff.
Just a guess. Might research it a little and see what I come up with.
It's not exactly the easiest site to navigate through.
MD

Moscow Desire said:
If I were to guess, it's a different CWM recovery using JB Kernel?. It probably came from 4pda.ru which is a russian site. HAs a lot of android tablet stuff.
Just a guess. Might research it a little and see what I come up with.
It's not exactly the easiest site to navigate through.
MD
Click to expand...
Click to collapse
I don't exactly see the need of a new recovery, since it works independent of the Android version. An "unknown" recovery would be possibly unsafe as well.

Gigabyte0 said:
If anybody need recovery, full worked with new 4.1.1 JB get it here
Click to expand...
Click to collapse
this one save´d my TAB!!!
i was able to reanimate it after i messed up ..
THX a lot

pawitp said:
I don't exactly see the need of a new recovery, since it works independent of the Android version. An "unknown" recovery would be possibly unsafe as well.
Click to expand...
Click to collapse
This is not "unknown" recovery. This 6.0.1.1 with kernel from bootloader JB (boot.img)
And this recovery normal mount all partition, make backup-restore and other function.
For ICS bootloader need original recovery 6.0.1.1
For JB bootloader my recovery, rebuilding from original JB bootloader and CMW recovery

Gigabyte0 said:
This is not "unknown" recovery. This 6.0.1.1 with kernel from bootloader JB (boot.img)
And this recovery normal mount all partition, make backup-restore and other function.
For ICS bootloader need original recovery 6.0.1.1
For JB bootloader my recovery, rebuilding from original JB bootloader and CMW recovery
Click to expand...
Click to collapse
You should give some info when posting, otherwise it is "unknown".
The boot.img contains the kernel not the bootloader. The kernel source is yet to be released by Acer and we don't know if Acer has blocked the dangerous emmc wipe command (which will randomly brick tablets, the more you wipe, the riskier you are) like I did on my kernel or not.

This is not "unknown" recovery. This 6.0.1.1 with kernel from bootloader JB (boot.img)
And this recovery normal mount all partition, make backup-restore and other function.
For ICS bootloader need original recovery 6.0.1.1
For JB bootloader my recovery, rebuilding from original JB bootloader and CMW recovery
Click to expand...
Click to collapse
But what it does not, it does not flashes. Freezes and hangs. Have my tab after 30 minutes. removed and restarted, now it hangs in APX mode. Do you have a solution for this?

Hi There
after i recovered my Tab to work, i´ve done a flash with this Recovery and it freezes.
After this i only was able to turn off the Decvice.
Now it seem´s that i can´t turn on, Black Screen, no LED, only thing the Computer tells an USB Device want´s to install.
Try to install APX drivers an failed.
some ideas?

meier2009 said:
Hi There
after i recovered my Tab to work, i´ve done a flash with this Recovery and it freezes.
After this i only was able to turn off the Decvice.
Now it seem´s that i can´t turn on, Black Screen, no LED, only thing the Computer tells an USB Device want´s to install.
Try to install APX drivers an failed.
some ideas?
Click to expand...
Click to collapse
"This recovery" meaning mine or Gigabyte0's?
If you're in APX mode, you're out of luck and the service center will probably need to replace your mainboard.

"This recovery" meaning mine or Gigabyte0's?
If you're in APX mode, you're out of luck and the service center will probably need to replace your mainboard.
Click to expand...
Click to collapse
Yes, it meant the version of Gigabyte0. Does not sound good.

Spread the word please:
ONLY USE PAWITP'S RECOVERY UNLESS YOU WANT A BRICKED TABLET
If pawitp's recovery is not working for you, then wait. The Recovery released by Gigabyte0 and found on 4PDA is built with Acer's kernel and Acer still has not fixed the brick bug!
Again, do NOT use Gigabyte0's recovery!

NoThrills said:
Spread the word please:
ONLY USE PAWITP'S RECOVERY UNLESS YOU WANT A BRICKED TABLET
If pawitp's recovery is not working for you, then wait. The Recovery released by Gigabyte0 and found on 4PDA is built with Acer's kernel and Acer still has not fixed the brick bug!
Again, do NOT use Gigabyte0's recovery!
Click to expand...
Click to collapse
And I will concurr. So far, Pawitp's has caused 0 issues.
Why somebody would want to install an unheard of recovery, with absolutely 0 information about it, is just asking for trouble.
I'll toss in a note to the FSM, and have him deal with Gigabyte0 on what to do with this link.
MD

Moscow Desire said:
And I will concurr. So far, Pawitp's has caused 0 issues.
Why somebody would want to install an unheard of recovery, with absolutely 0 information about it, is just asking for trouble.
I'll toss in a note to the FSM, and have him deal with Gigabyte0 on what to do with this link.
MD
Click to expand...
Click to collapse
Maybe you can also let this know on 4PDA.ru, as I am not Russian (and you are) you can probably explain it better:
In the Acer 3.0 Android kernel the command MMC_CAP_ERASE, which has caused all the old bricks, is still present. At least it is in the A110 3.0 kernelsource and I have no reason to believe they would remove it in the A700 3.0 kernelsource but not in the A110 one.
When this command exists in the kernel, and the Recovery also allows it (Recovery can also disable it, but the current A700 recovery doesn't do that), you are almost guarantueed a brick.
If you could translate that to 'the Russians' I guess we can save a few more people from bricking.

Thread Closed

[Q] Bricked Device? Please Help me!!!!!!!!! im LOST

hi, iam new user of TF300t, i installed the Energy.TF201.or.TF300..JB.03.18.2013.( i dont remebmer is the STOCKED or THEMED) ! after that i wanted to install BAKED_TF300T_BB-8, but the device stay on the boot menu! so what i did , installed the 6.0.2.3 CWM ( [CWM][6.0.2.3 / 5.5.0.4] Official CWM Recovery for JB/ICS + ROOT) ! after that i rebooted the device. Stock in the Asus LOGO! After i rebboted by holding the power menu and volume down, i choosed the wipe option ( i dont know why) and from tht time, it rebbots only in the 6.0.2.3 CWM what ever i do!
For 5 days, i have tried to flash via fastboot twrp.blob, i have pushed the firmware from asus to /sdcard and flashed via fastboot always, i have tried and read similaire problems! didt succed! i have always the message tht Can not mount sdcard! cant mound E/data! cant mount anythingg!! What ever i do, always reboot to this CWM !!!!!
please any one help me!!!!!!! thanks a lot!!!

You have installed an incompatible older custom recovery on the 4.2.1 bootloader. What you should have one is downgraded the bootloader from the energy thread to 4.1.1. You didn't need to downgrade your recovery.
Anyway I think you have bricked now.

sbdags said:
You have installed an incompatible older custom recovery on the 4.2.1 bootloader. What you should have one is downgraded the bootloader from the energy thread to 4.1.1. You didn't need to downgrade your recovery.
Anyway I think you have bricked now.
Click to expand...
Click to collapse
but i can use adb commands, and fastboot commande ( except tht i have waiting for device each time) so its bricked for EVER?!

You appear to have the same brick as everyone else. Caused by an older recovery on the latest bootloader.
If you can get fastboot to accept a lower bootloader or get it to accept TWRP 2.4.4.0 you should be able to recover but as you said it won't accept anything........

sbdags said:
You appear to have the same brick as everyone else. Caused by an older recovery on the latest bootloader.
If you can get fastboot to accept a lower bootloader or get it to accept TWRP 2.4.4.0 you should be able to recover but as you said it won't accept anything........
Click to expand...
Click to collapse
yes, it accept nothing! even if i downgrade to ics to apply the nvflash its worse! so should i say bye forever to my tf300t?!! if yes, which tablets tht cn be less bricked than others? thks a lottt! wht would u do if u were at my place? thksssssssssss

buy a new mainboard (motherboard)
Sent from my TF300T using xda app-developers app

How are you trying to downgrade? Can you get to the booloader? If yes, try this:
In bootloader, wipe data
Reboot into bootloader
Then, using fastboot, flash system blob from Asus stock ROM using fastboot (fastboot -i 0x0b05 flash staging blob)
If that succeeds, flash appropriate TWRP from bootloader using fastboot, then flash bootloader compatible ROM
If it only (re)boots to recovery, then you'll have to hang in there until a solution is invented. Until that time, you're bricked
---------- Post added at 10:08 PM ---------- Previous post was at 10:06 PM ----------
On a side note - can I flash 4.1 compatible ROMs on a 4.1 bootloader using the newest patched 2.4.4.0 TWRP without getting into trouble?

Ti2 said:
How are you trying to downgrade? Can you get to the booloader? If yes, try this:
In bootloader, wipe data
Reboot into bootloader
Then, using fastboot, flash system blob from Asus stock ROM using fastboot (fastboot -i 0x0b05 flash staging blob)
If that succeeds, flash appropriate TWRP from bootloader using fastboot, then flash bootloader compatible ROM
If it only (re)boots to recovery, then you'll have to hang in there until a solution is invented. Until that time, you're bricked
---------- Post added at 10:08 PM ---------- Previous post was at 10:06 PM ----------
On a side note - can I flash 4.1 compatible ROMs on a 4.1 bootloader using the newest patched 2.4.4.0 TWRP without getting into trouble?
Click to expand...
Click to collapse
thanks for yr reply ill try even im bricked! ill by another tabelt but not asus, maybe samsung, i have a GS2 , i install every thing without problem, i think there tables dont brick easly! true?

You wouldn't be bricked if you had read the instructions and followed them to the letter (and ask questions when unsure).
With that in mind - you can just as easily brick any device.

Ti2 said:
You wouldn't be bricked if you had read the instructions and followed them to the letter (and ask questions when unsure).
With that in mind - you can just as easily brick any device.
Click to expand...
Click to collapse
No that's just wrong for a bunch of people. At the time I did it. There was no warning, no indication of any problems. Just decided to do it at the wrong time. If it was 1 day later, I would have seen the bricked threads or had the patched TWRP.

sevenalive said:
No that's just wrong for a bunch of people. At the time I did it. There was no warning, no indication of any problems. Just decided to do it at the wrong time. If it was 1 day later, I would have seen the bricked threads or had the patched TWRP.
Click to expand...
Click to collapse
Wrong? No.
Harsh? Yes.
Read read read. Learn learn learn. Then read some more. When unsure, ask questions. Don't just try, then read the manual tot learn how you screwed up...
I am unsure tot flash 4.1 bootloader based roms through the 4.2 patched TWRP. I am NOT just going to try, I am awaiting an answer for 3 days now.
Is a Tab(2) as easily to brick as a Transformer? Yes it is.

sevenalive said:
No that's just wrong for a bunch of people. At the time I did it. There was no warning, no indication of any problems. Just decided to do it at the wrong time. If it was 1 day later, I would have seen the bricked threads or had the patched TWRP.
Click to expand...
Click to collapse
true wht u said !

Not trying to be harsh but that's why they call it "bleeding edge". You take the risks if you cannot be patient.
Sent from my SCH-I510 using xda app-developers app

hi,
did you try to use TWRP 2.4.4.0 - 4.2 this is the only one can read and write the sdcard on my TF300t after update to 4.2.1 good luck

lk2l said:
hi,
did you try to use TWRP 2.4.4.0 - 4.2 this is the only one can read and write the sdcard on my TF300t after update to 4.2.1 good luck
Click to expand...
Click to collapse
no succes to flash anything! always back to cwm 6.0.2.3...

when you type fastboot devices or adb devices can you see the device?

lk2l said:
when you type fastboot devices or adb devices can you see the device?
Click to expand...
Click to collapse
i can see this 0123456789ABCDEF, thts not the device name sure! isn't ? i can flash via fastboot ( sending ok, flashing ok) i flashed the blob file tht comes with the Asus frimwork 10.6.1.8 but nothing, always i go back to the 6.0.2.3 CWM! i flashed the twrp.blob file! same thing! im turning in an empty circle! good for trash??

depend if the code you write is only an example probably it is, is the device code.
don't worry until you can see the device you should be able to fix it... only thing is to found how

lk2l said:
depend if the code you write is only an example probably it is, is the device code.
don't worry until you can see the device you should be able to fix it... only thing is to found how
Click to expand...
Click to collapse
hope so! thkssssssssssssssssssssss

can you tell me which procedure you do to flash the recovery?
here you can found all I have used to flash my tf300t with the bootloader 4.2.1
fastboot+twrp recovery 2.4.4.0-4.2
is possible your fastboot dosen't work correctly?

[Q] Can someone please explain the bootloader upgrade process to me?

I have an Asus TF300T that I have unlocked, and flashed TWRP 10.6.3.1 onto it. I have then flashed the latest 4.4 Cyanogen nightly, and it bootloops. I think this is because of my bootloader.
Normally once I am at the custom recovery point on a device, I have no further issues and flash rom's like crazy. This specific bootloader requirement is new to me. I've farted around on a few devices before (Moto Milestone, HTC Desire Z, HP Touchpad, Sam GS3), but I'm not very technical.
I think my current bootloader is 10.4.2.18. (It reads Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.2.18-20121122" A03).
How do I upgrade my bootloader to allow for 4.4 rom's, and must I downgrade my bootloader if I want to install something like Ubuntu?
The instructions mentioned here http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7 took me to http://forum.xda-developers.com/showthread.php?p=49258989 but neither of these post's seem to be talking about the bootloader. Is there a way to simply upgrade just the bootloader? Or must I flash a special stock Asus rom that upgrades it for me, then reflash TWRP and proceed from there?

I think I may understand. I've downloaded the latest firmware update from the Asus website. Is this zip flashable within TWRP? Or can I simply fastboot the blob within the firmware zip? If so, what would the command be?

jiddahidda said:
I think I may understand. I've downloaded the latest firmware update from the Asus website. Is this zip flashable within TWRP? Or can I simply fastboot the blob within the firmware zip? If so, what would the command be?
Click to expand...
Click to collapse
Use fastboot to install the latest stock blob. Remember to extract the blob file:
Code:
fastboot -i 0x0B05 flash system blob.blob
Then you can flash TWRP 2.6.3.2 and then a KitKat ROM.

I seem to have lost the ability to get it into fastboot mode to apply your instructions. Is it bricked if it bootloops, and I cannot get into that bootloader screen by holding down the volume down button? Your instructions are straight forward but I haven't had a chance to try them yet because of this new issue. So does this sound like it's bricked?

cmendonc2 said:
Code:
fastboot -i 0x0B05 flash system blob.blob
Click to expand...
Click to collapse
Is there another way to get it into fastboot mode? See my post above this one.

I can get into APX mode. Can I fix this using APX mode? I'm googling around but I'll wait for word from you before doing anything, I don't want to make this worse.

jiddahidda said:
I can get into APX mode. Can I fix this using APX mode? I'm googling around but I'll wait for word from you before doing anything, I don't want to make this worse.
Click to expand...
Click to collapse
You cannot use APX mode unless you have already made NvFlash Backups. IF you made then, you can recover using that method.
I seem to have lost the ability to get it into fastboot mode to apply your instructions. Is it bricked if it bootloops, and I cannot get into that bootloader screen by holding down the volume down button? Your instructions are straight forward but I haven't had a chance to try them yet because of this new issue. So does this sound like it's bricked?
Click to expand...
Click to collapse
Yes, that does sound bricked. What you can do is look up Buster's recovery script and try using that to recover. It should be in the General Section.

cmendonc2 said:
You cannot use APX mode unless you have already made NvFlash Backups. IF you made then, you can recover using that method.
Click to expand...
Click to collapse
I think I know the answer, but I'll ask anyway. Is it possible to use someone elses NvFlash backups? I looked into making these backups but never did it .
cmendonc2 said:
Yes, that does sound bricked. What you can do is look up Buster's recovery script and try using that to recover. It should be in the General Section.
Click to expand...
Click to collapse
I've seen you suggest this script several times in several threads, but could never find it. I've been searching for threads with the word Buster or Recovery or Script and I can't find anything that seem's to be what you're talking about? Sorry to be a pain, what's his XDA username?

I think I've found it, but it relies on getting into fastboot, which I can't do. I stumbled on this post earlier while panicing when it first bricked. I think I'm screwed .
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12

jiddahidda said:
I think I've found it, but it relies on getting into fastboot, which I can't do. I stumbled on this post earlier while panicing when it first bricked. I think I'm screwed .
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Click to expand...
Click to collapse
Yes, but did you try using the paper clip to reset it? try a few combinations of using it.

(Solved) Soft-bricked, but unable to flash anything but CWM.

Hello, I seem to have soft bricked my tf700.
​I flashed a newish pacman nightly in CWM (after wiping data/cache/dalvik cache), which completed with no errors, then I flashed the corresponding GAPPS. But my device became stuck in the pacman boot intro.
​So I tried flashing slimkat which led to my device not getting past the first bootup screen (where you can enter recovery if pressing the corresponding buttons).
​After this screw-up I stupidly hit the wipe data button on the bootloader. I then tried doing the method of using fastboot to erase system, cache, and all that so I could flash system blob of the newest asus US SKU (that is correct for a US bought tf700 right?). Either this or wiping the data caused me to have a different bootloader as pictured below as I no longer have the android button and it does not ask me to press volume up to access recovery (the only way to access recovery is by hitting the wipe data button in bootloader).
​I can still fastboot flash CWM, but trying to flash TWRP does not work as it finishes but going into recovery causes the tablet to just restart. Trying to flash asus stock as above would always give me an error like the one pictured below. Similar errors occur if trying to flash any rom inside CWM via an external sd card.
​I do not have access to adb as i believe i dont have usb debugging enabled since the pacman rom or any other rom did not ever start. It just gives me the device not found error even after manually installing the drivers on two different computers.
Cant seem to get these pics to load, but copying the url and pasting it works.
http://imgur.com/AaU0GMt
http://imgur.com/vDTVa4B

You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.

tylerleo said:
You probably flashed the wrong Rom. Try flashing the >right< stock Rom and go from there. Double check everything you flash.
Click to expand...
Click to collapse
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.

gio3505 said:
Whats the "right" rom here? Talking about the original asus stock rom? I have now tried the the pacman nightly, pacman release, slim kat release, clean rom release, an ICS asus stock rom, and two different versions of the jellybean asus stock rom. These were either done in CWM via internal sd card, external sd card, or done through fastboost flash system blob and flash zip.
Click to expand...
Click to collapse
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.

tylerleo said:
Whatever Rom came on the device,(Good thing to have, da) I'm not familiar with this device.
Click to expand...
Click to collapse
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.

gio3505 said:
As far as i know, i have installed the stock rom, or atleast multiple versions of it with no success as it gives me an error stating something like staging or system when trying to write it.
Click to expand...
Click to collapse
Hmm, I'd Download a stock Rom for the device offline, take on the sd card and put it on there real quick and try to flash that, if not, you probably bricked your device. I wouldn't know how to fix it beyond that. Ask the dev that made the Rom were everything that went south and an email to cwm wouldn't hurt either

I am also not sure if I need to have my external sd card formatted a certain way or download a specific CWM to allow flashing the stock rom. Ive spent over 10 hours trying to figure this out, very frustrating.

I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/

gio3505 said:
I have run CWM 6.0.4.6, CWM 6.0.4.7, and older versions to see if I could flash the stock rom with no luck. I have also tried different versions of TWRP but they always hang and reboot my tf700. I get errors ranging from status 6, status 7, cannot mount data, cannot mount staging, and cannot mount system. I am completely lost on what I can do. I have even tried a seperate sdcard to see if maybe the one I was originally using was bad with no luck. GG :/
Click to expand...
Click to collapse
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?

berndblb said:
You gotta stop flashing stuff and slow down!
During all of this you never posted your bootloader version, so you may have been on the wrong bootloader to begin with - who knows.
When you hit the Wipe Data in the bootloader menu you caused the BL do write a wipe data command to the misc partition, causing the tablet to boot to recovery each time you booted (I'm guessing here) and then interrupting it. Usually, with CWM installed, it eventually sorts it out and executes the wipe data command, but that takes hours! You just have to leave it alone.
Hard to tell where you are now since you flashed all kinds of stuff since then.
Can you still boot into the bootloader and have a fastboot connection?
What's the BL version number?
If you boot, what does it boot into?
The picture links are broken - at least in Tapatalk. Post them again?
Click to expand...
Click to collapse
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?

gio3505 said:
Yes, the pictures are broken. You can still copy paste the url though. Couldnt figure out why it wouldnt work.
The tablet boots into the first screen that states it is unlocked, but does not go any further.
There is no bootloader version on the top left when holding down power + volume down.
I can still get to the place where it allows me to wipe data or fastboot, but the android icon to boot into android is now gone.
adb does not recognize my device even after manually installing the drivers, but fastboot works fine.
Is there any other way to find my bootloader version?
Click to expand...
Click to collapse
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!

berndblb said:
Maybe you want to edit your post with the urls then.... Makes it easier for people trying to help...
You're seriously messed up, I think. I see a USB icon in there which would indicate that your bootloader is ancient. But then it says: "starting USB fastboot protocol".
Is that after you selected the USB icon?
Anyway, I think you're only chance is buster99's method to get it back. Did you try that already?
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Naturally you have to extract the system blob from the 10.6.1.14.10 US Asus firmware, but then you can try to fastboot flash it with buster's method.
Good luck!
Click to expand...
Click to collapse
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.

gio3505 said:
Its starts the usb fastboot automatically if no input is selected. I had a different bootloader up until i tried that thing that buster did. It always gives me an error like cant write to system or something if i try it.
Click to expand...
Click to collapse
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?

berndblb said:
Which blob did you flash with buster's method?
I'm afraid you flashed something totally incompatible with your tablet...
You did not generate your nvflash blobs sometime prior to this, did you?
Click to expand...
Click to collapse
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.

gio3505 said:
I flashed the asus stock rom downloaded from their website. The US version as it was bought in the US (right? 0.o). I hadnt heard of nvflash before trying to install a rom so i did not make a backup.
Click to expand...
Click to collapse
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.

berndblb said:
Are you sure you downloaded the correct firmware? For the TF700?
Do you still have the original zip you extracted the blob from?
Post the exact file name please.
Click to expand...
Click to collapse
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.

gio3505 said:
US_epaduser10_6_1_14_10_UpdateLauncher (2)
or
US_epaduser_VER104425UpdateLauncher
or
US_epad_user_9_4_5_30_20120907_UpdateLauncher
Ive downloaded a lot of different versions from the asus website. The last one came from a forum post listing older firmware, which I have tried a lot of different ones.
Click to expand...
Click to collapse
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...

berndblb said:
You flashed all of those blobs???
In which order?
With what result?
Jeez - I think you're done for...
Sorry mate, but gotta catch some sleep now. Maybe somebody else has a bright idea...
Click to expand...
Click to collapse
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.

gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Right stop flashing random stuff - you have combinations of JB4.2.1, JB4.1.1 and ICS 4.0.3 just listed there.
Let me put a call out to @lj50036 who may be able to save you but if you have messed the bootloader up with no nvflash backups you are not going to be happy with the result. If you can still get to the bootloader screen then he can perform miraculous superhero acts and *maybe* save your device.

gio3505 said:
I flashed the newest one first, and it gave me one of those errors that wouldnt allow me to flash it, and i tried the others with the same result. So technically i didnt flash any of them. I have been able to flash some roms, but they wouldnt boot so i would be stuck where i was when i started.
Click to expand...
Click to collapse
Shoot me an email at [email protected]
We can use hangouts see if there is a solution to your issue ...
Thx Josh