adb "protocol failure" and ROM woes - Transformer TF300T Q&A, Help & Troubleshooting

So, much of the stuff in this and other threads has been a tremendous help. I did pretty much exactly what OP did in this thread http://forum.xda-developers.com/showthread.php?t=1779080.
I was having trouble getting my computer to recognize the usb drivers. I was able to finally get ADB to see the tablet by following this thread., Now, when I go to push the stock rom, I get an error message of "Protocol Failure" in cmd.
Any ideas?

I am trying the Universal Naked Drivers, as I have other android devices. I'm shooting in the dark with that though.

I noticed it says adb out of date. Have you tried updating the sdk?
Any chance you have a HTC phone with htc sync installed on the PC? Read that adb version isn't compatible

same thing happened to me using windows. i tried it using ubuntu and i was able to successfully adb push the rom to the tf300 without any problems.
Sent from my ASUS Transformer Pad TF300T

atomicblue said:
same thing happened to me using windows. i tried it using ubuntu and i was able to successfully adb push the rom to the tf300 without any problems.
Sent from my ASUS Transformer Pad TF300T
Click to expand...
Click to collapse
I tried ubuntu and ADB worked perfectly. I was able to go back to .30 stock.
Now though, whenever I try to flash ASUS-HYDRO 3.7 all I get is a bootloop. I am following each step verbatim.

when you flashed the base did you get any bootloops? the bootloop is probably caused because maybe you flashed both the base and the update at the same time. you were supossed to to flash the base and boot into it then flash the update after the base booted atleast once.
Sent from my ASUS Transformer Pad TF300T

atomicblue said:
when you flashed the base did you get any bootloops? the bootloop is probably caused because maybe you flashed both the base and the update at the same time. you were supossed to to flash the base and boot into it then flash the update after the base booted atleast once.
Sent from my ASUS Transformer Pad TF300T
Click to expand...
Click to collapse
That was the base, not the update. I also get hardlocked at boot if I try with CleanROM.
The only ROM that works is Stock .30. I have also verified that I am running stock after booting in stock, checking kernel version.
Ive tried wiping system multiple times before installing, Ive tried cache, and Dalvik. I also factory reset. Same results every go. Ive redownloaded the zips just incase as well.

which version of CWM are you using?
I had many problems with the touch or TWRP.
If you are not already on it, try 5.5.0.4

mikaole said:
which version of CWM are you using?
I had many problems with the touch or TWRP.
If you are not already on it, try 5.5.0.4
Click to expand...
Click to collapse
I'm using 5.5.0.4.
I go from this stage, install CWM 5.5.0.4 via fastboot, and let it reboot. I restart again in CWM and follow the instructions listed on the ASUS-Hydra page.
-1.you must be unlocked (bootloader) and must have CWM.
Click to expand...
Click to collapse
Check.
-2 reboot to recovery
Click to expand...
Click to collapse
Check
-3.format system under mounts and storage
Click to expand...
Click to collapse
Check
-4.wipe data factory reset
Click to expand...
Click to collapse
Check
-5. choose install zip
Click to expand...
Click to collapse
Check
-6. install and reboot
Click to expand...
Click to collapse
After doing this, the tablet boots to the screen that says This Device is unlocked, and has ASUS in the middle. It sits there for a couple minutes, and then reboots, repeating over and over.
I eventually force shutdown, reenter CWM, and flash .30 back on it, and then fastboot CWM back on. I go through the setup process with .30, and everything works with stock, including wifi and camera.

Related

Neither Win7 nor Mint recognise TF101 by USB since updating to ICS

I know it's probably a PEBCAK issue, but since upgrading to ICS neither my Win boot nor my Mint one recognise the Transformer on USB... Neither does adb or fastboot for what is worth...
Anyone else experiencing the issue?
+1
But since i transfer my data via Dock/USB it's not a big issue atm.
jordivf said:
I know it's probably a PEBCAK issue, but since upgrading to ICS neither my Win boot nor my Mint one recognise the Transformer on USB... Neither does adb or fastboot for what is worth...
Anyone else experiencing the issue?
Click to expand...
Click to collapse
My B50 was recognized by Win7 after successfully installing the device driver. A TF101 Drive was created with SD and External Storage available. I have a stock ICS, no root and no custom roms.
Mine did to. Although I had to go into device manager and uninstall the replug mine in and they reinstalled themselves. All but one that I can remember off hand but I just double-clicked it and it installed the 2nd time.
I had same issue... if you used CWM flashable package, you need to reflash bootloader. I've found link in dev section. From then everything is just fine.
Sent from my ICS TF101 by XDA HD app
You flash in CWM bootloader > http://forum.xda-developers.com/attachment.php?attachmentid=919716&d=1330205295 and your problem is solved
md5: 830CC58626C9772087203820BF22B96D
source: http://forum.xda-developers.com/showpost.php?p=22964131&postcount=47
reupload: http://www.mediafire.com/?h4pgduf8zsgmh96
E: gnufabio (Revolver ROM) use this boot image in his ROM, I think you can use this package for your US version TF
jozka.1 said:
You flash in CWM bootloader > http://forum.xda-developers.com/attachment.php?attachmentid=919716&d=1330205295 and your problem is solved
md5: 830CC58626C9772087203820BF22B96D
source: http://forum.xda-developers.com/showpost.php?p=22964131&postcount=47
Click to expand...
Click to collapse
I tried this method but got an error "status 7 installation aborted". Any solutions would be appreciated.
michael_duvalle said:
I tried this method but got an error "status 7 installation aborted". Any solutions would be appreciated.
Click to expand...
Click to collapse
Make sure you flash the update appropriate for your region.
The version linked might be for US, and you might have WW firmware. Etc. The version of the update and your firmware must match.
josteink said:
Make sure you flash the update appropriate for your region.
The version linked might be for US, and you might have WW firmware. Etc. The version of the update and your firmware must match.
Click to expand...
Click to collapse
It was the WW version I tried but still no joy.
michael_duvalle said:
It was the WW version I tried but still no joy.
Click to expand...
Click to collapse
You are rooted and flashing this in CWM, right?
(Just cheking to be sure about the basics here)
josteink said:
You are rooted and flashing this in CWM, right?
(Just cheking to be sure about the basics here)
Click to expand...
Click to collapse
Yes. I was originally on Prime 2.1.0, flashed ww-9.2.1.11-CWM-full-rooted.zip, then flashed ww-8.6.5.21-9.2.1.11-CWM-full-rooted.zip on top. No wipes were performed and everything else except the battery usage is working properly.
jozka.1 said:
You flash in CWM bootloader > http://forum.xda-developers.com/attachment.php?attachmentid=919716&d=1330205295 and your problem is solved
md5: 830CC58626C9772087203820BF22B96D
source: http://forum.xda-developers.com/showpost.php?p=22964131&postcount=47
Click to expand...
Click to collapse
You, Sir, are a genius.
Yup! That sorted the issue.
michael_duvalle said:
Yes. I was originally on Prime 2.1.0,
Click to expand...
Click to collapse
No wipes were performed
Click to expand...
Click to collapse
Well, this might be the culprit.
I ALLWAYS wipe when flashing Major changes (Honeycomb -> ICS / different custom-ROMs) and usually don't have any Problems.
schauol1 said:
Well, this might be the culprit.
I ALLWAYS wipe when flashing Major changes (Honeycomb -> ICS / different custom-ROMs) and usually don't have any Problems.
Click to expand...
Click to collapse
What would be the best way to fix this then. Should I revert to Honeycomb stock and update the official way or shall I just wipe and reflash ww-8.6.5.21-9.2.1.11-CWM-full-rooted.zip. Also, If I did the second method, what exactly should I wipe?
Cheers
michael_duvalle said:
I tried this method but got an error "status 7 installation aborted". Any solutions would be appreciated.
Click to expand...
Click to collapse
Which version CWM do you use? I use Rogue XM Recovery v1.3.0 and no problem.
You can flash the boot image from Android (terminal or ADB) :
extract bloob file from .zip to sdcard and
Code:
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
wait several minutes for better safety and reboot your TF.
jozka.1 said:
Which version CWM do you use? I use Rogue XM Recovery v1.3.0 and no problem.
You can flash the boot image from Android (terminal or ADB) :
extract bloob file from .zip to sdcard and
Code:
su
dd if=/sdcard/blob of=/dev/block/mmcblk0p4
wait several minutes for better safety and reboot your TF.
Click to expand...
Click to collapse
When you mean extract blob from the zip and place to the root of SD, do you mean the internal SD or the Removable SD?
It doesn´t matter, I prefer internal memory.
Code:
dd if=[B]/sdcard/blob[/B] of=/dev/block/mmcblk0p4
this is path to blob (internal SD)
jozka.1 said:
It doesn´t matter, I prefer internal memory.
Code:
dd if=[B]/sdcard/blob[/B] of=/dev/block/mmcblk0p4
this is path to blob (internal SD)
Click to expand...
Click to collapse
I tried it in terminal and it said that the file was written in several seconds. Several minutes later I went back to it, rebooted and still no joy.
And before boot system did you saw flash new blob file?
jozka.1 said:
And before boot system did you saw flash new blob file?
Click to expand...
Click to collapse
Yes. I left terminal open for about 10 minutes, then rebooted.

Stuck in Boot Loop!

I got the tablet "unlocked:, Rooted, And running clockworkmod recovery. I had over the air update to 4.1 before all this but had no issues. I downloaded a ROM for 4.1, and when I rebooted into CWM I went to wipe my data and thats when it happened. The data wipe froze. I ended up having to forcfully turn it off. Then I got bootloop. I can get into cwm but I cant find my ROM to flash it. So im literally stuck. Is there a One Click revert to stock I can use? Or anything? Many thanks to anyone who can help. Note: this is my 1st tablet - Asus Transformer tf300t
jburke90 said:
I got the tablet "unlocked:, Rooted, And running clockworkmod recovery. I had over the air update to 4.1 before all this but had no issues. I downloaded a ROM for 4.1, and when I rebooted into CWM I went to wipe my data and thats when it happened. The data wipe froze. I ended up having to forcfully turn it off. Then I got bootloop. I can get into cwm but I cant find my ROM to flash it. So im literally stuck. Is there a One Click revert to stock I can use? Or anything? Many thanks to anyone who can help. Note: this is my 1st tablet - Asus Transformer tf300t
Click to expand...
Click to collapse
I also made a backup before everything but I cant restore it. It says MD5 Mismatch. Im really stuck here...
so try to load your rom to sd card. then install from that?
naelme said:
so try to load your rom to sd card. then install from that?
Click to expand...
Click to collapse
I have no access to my sd card. The ROM I downloaded previously does not show up in CWM.
You can't flash it again from cwm by redowloding, then putting on your SD card then munt in it?
U could reflash your unit with stock ROM using fastboot. I just unbricked my unit doing that after 5 days of fighting.
This is what I did, I downloaded job update from Asus then moved the blob to c/fast boot, loaded unit to fast boot then typed
fastboot -i 0x0B05 flash system blob
But make sure our boot loader is 10.4 or it will signature mismatch, so down load the appropriate boot loader .
That's what I did at least and my unit is working again.
naelme said:
You can't flash it again from cwm by redowloding, then putting on your SD card then munt in it?
U could reflash your unit with stock ROM using fastboot. I just unbricked my unit doing that after 5 days of fighting.
Click to expand...
Click to collapse
What would my commands be to do this? Thanks
jburke90 said:
What would my commands be to do this? Thanks
Click to expand...
Click to collapse
I used
fastboot -i 0x0B05 flash system blob
read above edit.
i found the info here but had to tweak because once you upgrade bootload to 10.4 there is no going back it seems.
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/
you will lose your cwm, but you can re implement it when your done.
naelme said:
You can't flash it again from cwm by redowloding, then putting on your SD card then munt in it?
U could reflash your unit with stock ROM using fastboot. I just unbricked my unit doing that after 5 days of fighting.
This is what I did, I downloaded job update from Asus then moved the blob to c/fast boot, loaded unit to fast boot then typed
fastboot -i 0x0B05 flash system blob
But make sure our boot loader is 10.4 or it will signature mismatch, so down load the appropriate boot loader .
That's what I did at least and my unit is working again.
Click to expand...
Click to collapse
Can I use a custom ROM zip and get it from that? My internet is really slow tonight and 300mb is just crawling so downloading a stock ROM will take me another hour or so.... I am rooted if that helps.
jburke90 said:
Can I use a custom ROM zip and get it from that? My internet is really slow tonight and 300mb is just crawling so downloading a stock ROM will take me another hour or so.... I am rooted if that helps.
Click to expand...
Click to collapse
it has to match your current bootloader. if you updated jellybean your bootloader version is 10.4 and that is irreversible. so find out if that rom works on your current boot loader. once you go jb you can't go back.
in short. idk. if you want your unit install a rom that is made for your bootloader. idk custom roms. i use stock os rooted.
naelme said:
it has to match your current bootloader. if you updated jellybean your bootloader version is 10.4 and that is irreversible. so find out if that rom works on your current boot loader. once you go jb you can't go back.
in short. idk. if you want your unit install a rom that is made for your bootloader. idk custom roms. i use stock os rooted.
Click to expand...
Click to collapse
It is a JB ROM so it seems like it would work (fingers crossed).
jburke90 said:
It is a JB ROM so it seems like it would work (fingers crossed).
Click to expand...
Click to collapse
let me know. if the bootloader is 10.4 it should.
jburke90 said:
It is a JB ROM so it seems like it would work (fingers crossed).
Click to expand...
Click to collapse
Well this didn't work. I found the boot.blob and did what everything said to do but still boot loops. Not sure if it was because its not stock or not. I did notice that when I put in the command to reboot, it said it reboot but the tablet did nothing..... so is there a chance that it didn't even flash? It did seem very fast.
Verify boot loader version and use stock ROM.......
Find working custom ROM. Don't brick it
naelme said:
Verify boot loader version and use stock ROM.......
Click to expand...
Click to collapse
I will do that tomorrow. How do I verify my boot loader though?

Not booting after AOPK 4.2.2 installation

Hi
Today I've tried to free my TF300T from the stock rom. It was running on the last official version from ASUS (JB 4.2).
Firstly I did unlock the boot loader with the official tool from ASUS.
The I have installed TWRP (fastboot -i 0x0b05 flash recovery twrp.blob) as described here: http://forum.xda-developers.com/showthread.php?t=2187982
And at last, I installed AOPK 4.2.2 as described here: http://forum.xda-developers.com/showthread.php?t=2112369
Now my device always stopps booting at the ASUS screen. I still can enter the recovery mode and I have tried to reinstall AOPK 4.2.2 several times. Unfortunately with no success. The system still doesn't boot.
Does someone have an idea? Many thanks!
And i have twrp v.2.4.4.0 installed.
If just tried to reinstall the stock ASUS Transformer Pad TF300T Firmware: V10.6.1.8 Only for WW SKU (Android 4.2) - 2013.03.11 update.
Twrp always reports: Failed.
Nobody? I would really appreciate a hint.
Thanks
ducmac said:
And i have twrp v.2.4.4.0 installed.
If just tried to reinstall the stock ASUS Transformer Pad TF300T Firmware: V10.6.1.8 Only for WW SKU (Android 4.2) - 2013.03.11 update.
Twrp always reports: Failed.
Click to expand...
Click to collapse
ducmac said:
Nobody? I would really appreciate a hint.
Thanks
Click to expand...
Click to collapse
Are you trying to re-install stock firmware via the blog file? You have to unzip the ZIP file you download from Asus website at least twice to get it. And make sure it's the firmware version you need WW vs US. I had to restore with stock firmware and used US...
ducmac said:
Hi
Today I've tried to free my TF300T from the stock rom. It was running on the last official version from ASUS (JB 4.2).
Firstly I did unlock the boot loader with the official tool from ASUS.
The I have installed TWRP (fastboot -i 0x0b05 flash recovery twrp.blob) as described here: http://forum.xda-developers.com/showthread.php?t=2187982
And at last, I installed AOPK 4.2.2 as described here: http://forum.xda-developers.com/showthread.php?t=2112369
Now my device always stopps booting at the ASUS screen. I still can enter the recovery mode and I have tried to reinstall AOPK 4.2.2 several times. Unfortunately with no success. The system still doesn't boot.
Does someone have an idea? Many thanks!
Click to expand...
Click to collapse
That AOKP version that you are trying to install is not compatible with your tf300, you were running the latest Asus official 4.2 and the bootloader is not the same.
You need to install either Energy ROM or Cleanrom 4.3
Erik.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Thanks Eric. I tried to install this rom, but the TF300 is still not booting: http://forum.xda-developers.com/showthread.php?t=2204166
Any ideas?
ricco333 said:
That AOKP version that you are trying to install is not compatible with your tf300, you were running the latest Asus official 4.2 and the bootloader is not the same.
You need to install either Energy ROM or Cleanrom 4.3
Erik.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
ducmac said:
Thanks Eric. I tried to install this rom, but the TF300 is still not booting: http://forum.xda-developers.com/showthread.php?t=2204166
Any ideas?
Click to expand...
Click to collapse
Did you download the rom onto your sdcard?i ask this because anytime i do that, twrp says 'failed'.
Yes I've downloaded it to the internal SD card. The installation acutally works fine, it just doesn't boot.
crazynitro said:
Did you download the rom onto your sdcard?i ask this because anytime i do that, twrp says 'failed'.
Click to expand...
Click to collapse
MaMMiTs said:
Are you trying to re-install stock firmware via the blog file? You have to unzip the ZIP file you download from Asus website at least twice to get it. And make sure it's the firmware version you need WW vs US. I had to restore with stock firmware and used US...
Click to expand...
Click to collapse
Any working firmware would do it When i try to install the stock firmware, I always get the error "failed" when i try to flash it.
ducmac said:
Any working firmware would do it When i try to install the stock firmware, I always get the error "failed" when i try to flash it.
Click to expand...
Click to collapse
Since you followed that guide for upgrade i am guessing you got his link for the right recovery for this bootloader? It should look like:
openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
The one for this bootloader have a -4.2. at the end.
If so I would put the CROMI 4.3 rom (its great) on a known working SD card and do a full wipe. Cache, dalvik, factory reset, and wipe internal. Possibly even format data on the internal since there may still be data from a rom meant for the 4.1.1 bootloader. Then i would try to reinstall CROMI.
Also if you just want stock, there is a stock rooted rom available: http://forum.xda-developers.com/showthread.php?t=2243025

(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

Thought I was doing so well; tablet won't boot to OS

Hey folks; I'm hoping I can get some advice or pointers, or maybe just a slap upside the head with something I've missed.
I have one of the original Shield tablets, and played around with it quite a lot, installing various custom ROMs from the marvelous directions I've found here. When the battery thing happened, I submitted the required info and happily received my new tablet. The original was rooted and customised still, kill-switch averted, and I had two working tablets. I gave the new stock one to my wife.
But then, about three months ago, I was playing with mine again installing a newer ROM than the one I was using (I *think* I was going from an older Bliss rom to one of the Cyanogen), and ... Something Happened (tm). The tablet rebooted in the middle of everything, and now won't boot to an image.
I'm on Windows 10 now, and had some fun getting the drivers working, but they seem to. I can communicate with the tablet through Fastboot, but ADB doesn't see it. I've flashed several versions of TWRP to the tablet, and can boot into that recovery - both through Fastboot and the tablet's power+vol-dn buttons. I've used TWRP to flash several different ROMs, and it *appears* to work (there are no errors), but when I reboot the tablet .... nada. Nothing but the Nvidia boot screen for days.
So now... what have I missed? I'm a little reluctant to flash a stock ROM, but I'm at a loss. I used to have more time to fiddle and figure, and I'm afraid that my impatience is going to kill the thing.
Format system and data see if that works
You need to have the latest bootloader to run the latest roms.
Sent from my ZTE A2017U using Tapatalk
skooter32 said:
Format system and data see if that works
Click to expand...
Click to collapse
Have done, but I'll try it again. Thanks
lafester said:
You need to have the latest bootloader to run the latest roms.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I've tried the latest and the not-so-latest, all with similar results.
Hnefatafl said:
I've tried the latest and the not-so-latest, all with similar results.
Click to expand...
Click to collapse
so you wan t your "burning" tablet set again stock?
Did you read about "recovery images" for shield tablet?
If fastboot is working you can flash the recovery image and all will update to the latest(blob,system,boot, etc)
flash latest twrp for shieldtablet.
after that use the nomoreota.zip to prevent the software brick from nvidida
Hnefatafl said:
Have done, but I'll try it again. Thanks
Click to expand...
Click to collapse
Also format data system to something other than ext4 then re format it back
skooter32 said:
Also format data system to something other than ext4 then re format it back
Click to expand...
Click to collapse
can I ask what that should bring?
wiQbold said:
so you wan t your "burning" tablet set again stock?
Did you read about "recovery images" for shield tablet?
If fastboot is working you can flash the recovery image and all will update to the latest(blob,system,boot, etc)
flash latest twrp for shieldtablet.
after that use the nomoreota.zip to prevent the software brick from nvidida
Click to expand...
Click to collapse
No, I don't want it stock at all, I was just worried that was my only option to get this thing to respond again. I was running BlissPop v.somethingorother, but wanted to update. That's when things went awry.
Right, well it looks like I've got this thing going. I could flash TWRP 3.1.0-0, but not any 3.1.1. Cyanogenmod 12 worked. Reading up a little more (it got slow at work for a couple of days...) I flashed the firmware to 5.0, and could now install TWRP 3.1.1-1! Then I could install (in this case) Lineage 14.1, which *almost* worked. It booted, but there's no wifi.
Then I found a suggestion - I think it was on these forums somewhere - and restarted. Wiped all data again, flashed Cyanogenmod 12, no gapps. Restarted, checked everything including wifi, and is good. Rebooted back into recovery, performed a factory reset, then installed Lineage 14.1 and gapps. When it rebooted, everything is working!
So. Firmware. Huh.
Thanks all.
Hnefatafl said:
No, I don't want it stock at all, I was just worried that was my only option to get this thing to respond again. I was running BlissPop v.somethingorother, but wanted to update. That's when things went awry.
Click to expand...
Click to collapse
do not know if you need the bootloader(blob) from nougat to boot up, that lafester told you. but that sounds plausible. skooter says something from re-formating. so if you tried that all and nothing changes? cache and data partition you wiped also, so it has to be work for my understanding.
went always stock, so can t help you..
but you can use recovery images > twrp > bliss/linage. no need to boot up stock?
wiQbold said:
can I ask what that should bring?
Click to expand...
Click to collapse
I have had similar issues and I tried everything even this plus what harm is it going to be and as the fellow below said if ur in fastboot and recovery with no issues then surely u should be flashing stick to fix Ur problem ?

Categories

Resources