Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?
GRIM1337 said:
Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?
Click to expand...
Click to collapse
I am having the same issue. Just rooted today. Please help!
dpadaddict said:
I am having the same issue. Just rooted today. Please help!
Click to expand...
Click to collapse
Are you able to get into fastboot? If you press and hold power and volume down until you get the option to press volume up to boot to recovery, but don't press voume up, then you will boot into the bootloader screen, with fastboot as an option.
At this site you will find the correct twrp (choose Download - Recovery Image / Fastboot Method) and instructions to flash:
http://teamw.in/project/twrp2/105
Instructions for fastboot and adb you'll find by searching around.
Hope that helps!
fordwolden said:
Are you able to get into fastboot? If you press and hold power and volume down until you get the option to press volume up to boot to recovery, but don't press voume up, then you will boot into the bootloader screen, with fastboot as an option.
At this site you will find the correct twrp (choose Download - Recovery Image / Fastboot Method) and instructions to flash:
Instructions for fastboot and adb you'll find by searching around.
Hope that helps!
Click to expand...
Click to collapse
I wish I could... The message I receive is as follows when I do that:
The Device is UnLocked.
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.5.26-20120720" A03
Booting recovery kernel image
And nothing ever shows up. Just the ASUS logo.
Did you solve your problem? I'm having the same issue and tried to install custom ROMs without solving the problem
reboot the device! (power and vol down for 5 sec)
hold vol down at the ASUS screen, but don't go to recovery, just wait until you see a 3 different logos on your screen.
An Android, a Wipe and a USB Icon
go between theese logos with vol down choose USB Icon with vol up!
Now you are in Fastboot mode and with your PC you can flash another recovery image.
But by the way!
WHY THE HELL DID YOU UNLOCKED YOUR DEVICE IF YOU ARE TOTALLY NEW TO ANDROID?!
You don't need this if you are new to android, even root does a good deal for first serious steps!
kabauterman said:
But by the way!
WHY THE HELL DID YOU UNLOCKED YOUR DEVICE IF YOU ARE TOTALLY NEW TO ANDROID?!
You don't need this if you are new to android, even root does a good deal for first serious steps!
Click to expand...
Click to collapse
Hey, we were all new to Android at some point! That's how you learn though, by doing this sort of stuff. Nothing wrong wth trying! Just need to be careful and read alot. But, you have to start somewhere!
I'm sure that he was reading all of the "Jelly Bean ROM's are so awesome" posts and wanted to see for himself, that's all....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
jtrosky said:
Hey, we were all new to Android at some point! That's how you learn though, by doing this sort of stuff. Nothing wrong wth trying! Just need to be careful and read alot. But, you have to start somewhere!
I'm sure that he was reading all of the "Jelly Bean ROM's are so awesome" posts and wanted to see for himself, that's all....
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I never said I was new to Android. I was new to the ASUS stock tablet recovery orientation (its landscape as I found out). Hence, hit up twice, wiped data. I am by no means new in general. I did not fix the problem. I requested an RMA with Newegg and it was approved I said the issue with it was bad screen bleeding (no lie but it is normal for this tablet but bad was exaggerated) In any case! RMA approved should be getting my new unit Tuesday!
unlocked and RMA because of your own stupidity?
ok do it..
have you tried it with fastboot?
fix
GRIM1337 said:
Hi there so, I received my ASUS Transformer Infinity yesterday and I managed to root and unlock successfully. However, after downloading ROM Manager I stupidly clicked flash CWRM it did it's thing and I thought, well, it was successful so let's try and boot into it to flash a custom ROM I had downloaded. From ROM Manager no dice, tried getting into recovery manually and it worked. However, it was clearly stock recovery. New to Android slates I clicked the volume buttons a couple times to try and see how to move the cursor... this of course wiped my device. At this point, I was pretty sure I was done for, after this completed I rebooted again and low and behold cannot get into the device on normal boot. Tried rebooting, nothing. Tried the keyboard dock, same deal. Stuck on ASUS screen and I never get the spinning wheel. Tried to get back in recovery and I get stuck at loading recovery kernel image. BRICK. The only thing I can do is get into APX recovery but as I understand there is no use for this mode yet on the TF700? Please help! My last option is to RMA to Newegg, if I do this what should I say? I feel being honest is the only way to grantee a repair. How much would this cost out of warranty?
Click to expand...
Click to collapse
Just follow this method and you will be fine
http://forum.xda-developers.com/showthread.php?t=1755576
kabauterman said:
unlocked and RMA because of your own stupidity?
ok do it..
have you tried it with fastboot?
Click to expand...
Click to collapse
If you had my OP in its entirety, you would know that is impossible. :/ Unfortunately, after the data + cache wipe two things happened that I do not understand. 1. The device wouldn't boot (this shouldn't happen unless all partitions were formatted which the device did NOT report it did), 2. This is the really strange part, recovery no longer existed after JUST WORKING - even after my mistake with ROM manager stock recovery remained until the wipe and then I received the message mentioned in my OP (namely: Booting recovery kernel).
GRIM1337 said:
If you had my OP in its entirety, you would know that is impossible. :/ Unfortunately, after the data + cache wipe two things happened that I do not understand. 1. The device wouldn't boot (this shouldn't happen unless all partitions were formatted which the device did NOT report it did), 2. This is the really strange part, recovery no longer existed after JUST WORKING - even after my mistake with ROM manager stock recovery remained until the wipe and then I received the message mentioned in my OP (namely: Booting recovery kernel).
Click to expand...
Click to collapse
Any resolution to this other than the RMA?
HelgesenJ said:
Any resolution to this other than the RMA?
Click to expand...
Click to collapse
Please don't tell me you have used ROM Manager recently. : S Are you having the same issue?
APX available, or not (as with the OP)? NvFlashed? What have you done, or tried to do, yourself?
Moar. Info.
MartyHulskemper said:
Please don't tell me you have used ROM Manager recently. : S Are you having the same issue?
APX available, or not (as with the OP)? NvFlashed? What have you done, or tried to do, yourself?
Moar. Info.
Click to expand...
Click to collapse
One more who used ROM manager recently and now I have a nice tray for serving beers :crying:
I'm having the same issue with APX available by powering on the transformer holding volume+up but with no nvflash backup.
I don't understand why people keep using ROM manager to install recovery, this is a death wish to your device. If they read all the "How to" posts, none of them instructed to use rom manager to install recovery, so I don't know where they got this idea from???? beat me!!!
GRIM1337, you need RMA to send out for repair. Sorry but there's no hope to recovery this.
Didn't use ROM Manager
Updated to JB (from rooted ICS), then tried to unlock and flash recovery: Bootloader is still locked, recovery and system partitions are simply gone!
All I can access is fastboot now, but as bootloader is locked, I cannot flash any custom image/blob or whatsoever.
Can someone generous post their stock recovery or help me flash the JB update ZIP again?
I extracted the blob, but I'm not sure how to flash it? I suppose it contains all the partitions I would need to flash! But how to flash them?
I tried this:
fastboot -i 0x0b05 flash staging blob
Fails after having downloaded the 800Mb blob, the exact same way it fails flashing a custom kernel!?
sending 'staging' (800199 KB)...
OKAY [145.978s]
writing 'staging'...
FAILED (remote: (InvalidState))
finished. total time: 205.000s
3c said:
Updated to JB (from rooted ICS), then tried to unlock and flash recovery: Bootloader is still locked, recovery and system partitions are simply gone!
All I can access is fastboot now, but as bootloader is locked, I cannot flash any custom image/blob or whatsoever.
Can someone generous post their stock recovery or help me flash the JB update ZIP again?
I extracted the blob, but I'm not sure how to flash it? I suppose it contains all the partitions I would need to flash! But how to flash them?
I tried this:
fastboot -i 0x0b05 flash staging blob
Fails after having downloaded the 800Mb blob, the exact same way it fails flashing a custom kernel!?
sending 'staging' (800199 KB)...
OKAY [145.978s]
writing 'staging'...
FAILED (remote: (InvalidState))
finished. total time: 205.000s
Click to expand...
Click to collapse
How did you get into fastboot mode for your device??
buhohitr said:
How did you get into fastboot mode for your device??
Click to expand...
Click to collapse
Well that one's hard: With ICS bootloader, there was like no fastboot mode!!! On the bootloader menu I could only confirm recovery or cancel to boot as usual!!! WTF? But then once with JB bootloader, the menu allowed me to select a different option: a new one had appeared showing a USB logo too! Can't tell if I simply missed the option or proper steps in ICS bootloader though.
3c said:
Well that one's hard: With ICS bootloader, there was like no fastboot mode!!! On the bootloader menu I could only confirm recovery or cancel to boot as usual!!! WTF? But then once with JB bootloader, the menu allowed me to select a different option: a new one had appeared showing a USB logo too! Can't tell if I simply missed the option or proper steps in ICS bootloader though.
Click to expand...
Click to collapse
ICS bootloader had the fastboot option disabled if the device's bootloader was still locked and the USB icon wasn't showing at all.
With the JB bootloader Asus made the USB icon available even if the device was locked so you can access fastboot mode but you can't flash anything (yes,it doesn't make sense, but this is Asus).
Anyway, if you are able to boot in recovery you should be able to restore you device easily,just follow my guide from the general forum.
Re: Help needed i will try
OK WHAT YOU HAVE DONE IS WIPED THE OS FROM THE UNIT...AND LEFT THE BOOTLOADER FILES...SO THERE ISNT
ANYTHING TO BOOT TO AT THE MOMENT... I DID THIS LAST WEEK... IT WAS A BIT SCARY AND FRUSTRATING UNTIL
I FIGURED OUT HOW TO FIX IT.. ITS NOT HARD. ILL PUT DOWN HERE WHAT I DID...
1. DOWNLOAD THE GOOGLE NEXUS 7 TOOL KIT... ( this is a very good rescue tool )
2. RUN IT... INSTALL THE DRIVERS... REBOOT IT ALL AND START THE TOOL KIT AGIAN WITH YOUR TRANSFORMER
CONNECTED TO USB...
3. YOU SHOULD SEE THE SERIAL NUMBER OF YOUR TABLET AT THE TOP OF THE PAGE IN THE TOOLKIT...
IF SO..YOUR ALMOST DONE !
4. THERE ARE MANY CHOICES..SOME WORK SOME DONT ON THE TRANSFORMER...
5. I CHOOSE THE ROOT OPTION...
6. NOW..WHEN IT GETS TO THE PART WHERE IT SAYS ARE U IN FASTBOOT MODE.. SAY NO !!! THAT WILL ACTUALLY
PUT IT IN FASTBOOT AND THEN PROCEED AS DIRECTED ON THE SCREEN TO ROOT...
THATS WHAT I DID...CAUSE I NEEDED ROOT AND I HAD A STUCK BOOT LOOP JUST LIKE YOU.....
BASICALLY YOU NEED TO ROOT IT AGIAN AN THEN REBOOT AND TRY TO GET INTO CWM..OR HAVE IT REINSTALL CWM...TO FLASH A ROM...THAT WORKS..
Related
Hi ppl!
First, my device failed to get the OTA Update because I deleted some system apps (see my original post).
Then I found this post where another user restored original APKs in /system/apps and managed to manually update to JB by downloading the dlpkgfile in this post.
So I proceed, restored my /system/apps (with 755 permissions), rooted with OTA RootKeeper and SuperSU, placed the dlpkgfile and command files, restarted to fastboot (Power+Vol Down) and entered Recovery mode.
The green android with the blue progress bar went for over 10 minutes, then ... the android with the RED TRIANGLE appeared
After a minute or so the device restarted, an ASUS logo with a blue progress bar ran, but then it got stuck in the ASUS logo.
I'm still able to restart to fastboot (Power+Vol Down), where a message appears:
Code:
Android cardhu-user bootloader (1.00 e) released by "US_epad-10.4.2.9-20120809" A03
, and where I have 4 choices:
1. RCK: Recovery mode, when I select this the Red Triangle appears again.
2. Android: Normal android boot, gets freeze right away
3. Fastboot USB download protocol: Tried using ADB, but don't really know what it is. Here's an image of how the device appear in my Windows PC
4. Wipe Data: Already done this, seems to wipe user data, but still gets stuck on ASUS logo
Some pictures I took of my device: http://imgur.com/I13ou http://imgur.com/Jezpn
I also tried downloading .30 firmware from ASUS website and placing the Zip contents in my SD card, then booting recovery but no luck.
It's pretty awful that everything went so bad, I'm hoping there is a solution.
Anything would be really appreciated!!!
Thanks!
benoror said:
Hi ppl!
First, my device failed to get the OTA Update because I deleted some system apps (see my original post).
Then I found this post where another user restored original APKs in /system/apps and managed to manually update to JB by downloading the dlpkgfile in this post.
So I proceed, restored my /system/apps (with 755 permissions), rooted with OTA RootKeeper and SuperSU, placed the dlpkgfile and command files, restarted to fastboot (Power+Vol Down) and entered Recovery mode.
The green android with the blue progress bar went for over 10 minutes, then ... the android with the RED TRIANGLE appeared
After a minute or so the device restarted, an ASUS logo with a blue progress bar ran, but then it got stuck in the ASUS logo.
I'm still able to restart to fastboot (Power+Vol Down), where a message appears:
Code:
Android cardhu-user bootloader (1.00 e) released by "US_epad-10.4.2.9-20120809" A03
, and where I have 4 choices:
1. RCK: Recovery mode, when I select this the Red Triangle appears again.
2. Android: Normal android boot, gets freeze right away
3. Fastboot USB download protocol: Tried using ADB, but don't really know what it is. Here's an image of how the device appear in my Windows PC
4. Wipe Data: Already done this, seems to wipe user data, but still gets stuck on ASUS logo
Some pictures I took of my device: http://imgur.com/I13ou http://imgur.com/Jezpn
I also tried downloading .30 firmware from ASUS website and placing the Zip contents in my SD card, then booting recovery but no luck.
It's pretty awful that everything went so bad, I'm hoping there is a solution.
Anything would be really appreciated!!!
Thanks!
Click to expand...
Click to collapse
You don't have a recovery to boot into
Sent from my SGH-T989 using xda app-developers app
OK, I found this tutorial about flashing ASUS firmware with fastboot: http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/
The problem is that the following commands:
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 flash system US_epad-user-9.4.3.30.zip
both produce the error: "Signature mismatch"
I guess it's becaus my fastboot is newer version, since it was actually installed during the JB update, but I'm trying to flash a older .30 firmware.
I gues I will have to wait ASUS releases the new firmware for manual flashing it.
Just guessing...
benoror said:
OK, I found this tutorial about flashing ASUS firmware with fastboot: http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/
The problem is that the following commands:
fastboot -i 0x0B05 flash system blob
fastboot -i 0x0B05 flash system US_epad-user-9.4.3.30.zip
both produce the error: "Signature mismatch"
I guess it's becaus my fastboot is newer version, since it was actually installed during the JB update, but I'm trying to flash a older .30 firmware.
I gues I will have to wait ASUS releases the new firmware for manual flashing it.
Just guessing...
Click to expand...
Click to collapse
Thank you for posting this. I wanted to try something like this with the new boot loader that came with jb but it appears flashing the older firmware will not work.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
funnel71 said:
Thank you for posting this. I wanted to try something like this with the new boot loader that came with jb but it appears flashing the older firmware will not work.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
You're welcome. So, do you have a clue on how to restore my older bootloader soy I can get back to .30 stock?
benoror said:
You're welcome. So, do you have a clue on how to restore my older bootloader soy I can get back to .30 stock?
Click to expand...
Click to collapse
That is exactly what I'm wanting to know if it's even possible. If I can safely downgrade, I can re-root, but I'm limited on what I can do with a locked bootloader.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
peopole!!! new firmware is out!!!
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF300T/US_epaduser_10_4_2_9_UpdateLauncher.zip
here is a direct download link!!! US version only!!!
PS: im pushing using
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
[blob extracted from the above zip]
okay asus animated boot is up and i seem to successfully unbrick my device!!!!
Screens http://imgur.com/a/D7wqI
kindrudekid said:
peopole!!! new firmware is out!!!
http://dlcdnet.asus.com/pub/ASUS/EeePAD/TF300T/US_epaduser_10_4_2_9_UpdateLauncher.zip
here is a direct download link!!! US version only!!!
PS: im pushing using
[blob extracted from the above zip]
okay asus animated boot is up and i seem to successfully unbrick my device!!!!
Screens http://imgur.com/a/D7wqI
Click to expand...
Click to collapse
I don't know you mate..
But I'm so happy for you!! Glad everything worked out well! Cheers!!
Same Here!!!
Flashing the new ASUS firmware unbricked my device!!!!
Please mark this topic as SOLVED
ASUS should really make this process easier.
Thanks for all the support!
Greetings.
soft bricked?
I dont see how this is solved......I have seen some people comment they have no fastboot or recovery,
I tried to do manual update in cwm and when I rebooted with adb all I have is asus boot logo, it also does not say I have an unlocked bootloader,
I have no fastboot no recovery no adb connect all I have is asus boot logo.......volume+-power does nothing vol down + power also does nothing.
how do you flash new firmware without adb or any type of recovery?
uelabs said:
I dont see how this is solved......I have seen some people comment they have no fastboot or recovery,
I tried to do manual update in cwm and when I rebooted with adb all I have is asus boot logo, it also does not say I have an unlocked bootloader,
I have no fastboot no recovery no adb connect all I have is asus boot logo.......volume+-power does nothing vol down + power also does nothing.
how do you flash new firmware without adb or any type of recovery?
Click to expand...
Click to collapse
I have the same problem!!
please need help on this!!
AFAIK you should still have access to fastboot, I'm newbie and never messed up by unlocking the bootloader
It worked!
Thank you so much! I had this same problem with mine and couldn't find an answer anywhere until I found your post.
hmm, I lost my tablet for nearly a month then updated CM10 when prompted having connected to my new wireless. This of course (since the Oct update) put the ROM out of kilter with the bootloader. I didn't have an old ROM on the SDCARD, and old CWM so I couldn't mount an external to get a rom on. I tried pushing a rom to the SD with adb but the drivers weren't going in right and I just couldn't get any joy. I followed this thread to fastboot the current stock JB on in the hope that it would give me a fresh start but it's hanging now at the second (glossy) ASUS logo. I really don't know where to go from here. Is it possible there was a problem with the write?
erasing the memory from the boot menu worked!
biscuits said:
erasing the memory from the boot menu worked!
Click to expand...
Click to collapse
Can you tell me how you erased memory from boot menu - or maybe i understand this in different way.
I have only bootloop and it boots to CWM where i cannot mount any SD card - not internal not external.
Also Vol down + power doesnt work - there is no option to enter fastboot mode....device just bootloops and then enters CWM...
Tried to push through adb but there is no SD card to copy files. Tried different methods but cannot mount any storage...
Thanks JB update
kindrudekid said:
peopole!!! new firmware is out!!!
here is a direct download link!!! US version only!!!
PS: im pushing using
[blob extracted from the above zip]
okay asus animated boot is up and i seem to successfully unbrick my device!!!!
My fastboot is working but it seems that i cannot write anything on my internal sd card.. When i run fastboot -i 0x0B05 flash system blob
My PC shows no erros - it does all the steps. But my tablet freezes and that it - it never unfreezes, i need to power it off.
But fastboot and abd commands work - like reboot or boot into bootloader.
Click to expand...
Click to collapse
Hello there!
I have a TF700T pad, I installed free rom manager application, from within that application I chose to install clockworkmod recovery, the application loaded the clockworkmod recovery from the internet (there was an indicator on top of the application screen).
After finished, I rebooted into recovery, but it doesn't reboot to recovery, it loads android normally, then I tried to boot to recovery manually by pressing and holding the the power button along with the volume down button it loads nothing and stays there for ever!! I did this several times then it it changed and now it doesn't even load the android normally.
And when I boot into APX mode, the adb can't find it!
In short, I can't access recovery nor system!
When I try to boot to recovery
(power + volume down) It freezs and the following shows on the screen:
"The device is unlocked.
Android cardhu-user bootloader <2.10 e> release by "CN_epad-9.4.5.30-20120907" A03
Checking for android ota recovery
Booting recovery kernel image"
- I downloaded the firmware from ASUS and renamed it to "EP201_768_SDUPDATE" and copied to the root of a formated FAT32 micro SD card and tried to boot, but still freezing on above mentioned screen.
- The PC recognizes it (drivers are correct, i downloaded them and installed them) but the adb can not find the pad and tells me to install tap's specific drivers!
- I tried to flash the recovery image image.img through adb, but same problem, it stays there for ever showing the message "waiting for device".
Please, help me with a solution for that situation!
Thank you.
shreef said:
Hello there!
I have a TF700T pad, I installed free rom manager application, from within that application I chose to install clockworkmod recovery, the application loaded the clockworkmod recovery from the internet (there was an indicator on top of the application screen).
After finished, I rebooted into recovery, but it doesn't reboot to recovery, it loads android normally, then I tried to boot to recovery manually by pressing and holding the the power button along with the volume down button it loads nothing and stays there for ever!! I did this several times then it it changed and now it doesn't even load the android normally.
And when I boot into APX mode, the adb can't find it!
In short, I can't access recovery nor system!
When I try to boot to recovery
(power + volume down) It freezs and the following shows on the screen:
"The device is unlocked.
Android cardhu-user bootloader <2.10 e> release by "CN_epad-9.4.5.30-20120907" A03
Checking for android ota recovery
Booting recovery kernel image"
- I downloaded the firmware from ASUS and renamed it to "EP201_768_SDUPDATE" and copied to the root of a formated FAT32 micro SD card and tried to boot, but still freezing on above mentioned screen.
- The PC recognizes it (drivers are correct, i downloaded them and installed them) but the adb can not find the pad and tells me to install tap's specific drivers!
- I tried to flash the recovery image image.img through adb, but same problem, it stays there for ever showing the message "waiting for device".
Please, help me with a solution for that situation!
Thank you.
Click to expand...
Click to collapse
Do you have nvflash backup? if not, I believe you're done. You need to send out for repair.
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
shreef said:
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
Click to expand...
Click to collapse
I'm assuming you've unlocked the bootloader. Can you get the device into fastboot and push a new recovery through that?
shreef said:
Thank you for your quick response!
Isn't there any other way I could repair it without sending to ASUS repair?? i originally bought it from CHINA and now i am here in EGYPT!!!
Click to expand...
Click to collapse
ArmyAg08 said:
I'm assuming you've unlocked the bootloader. Can you get the device into fastboot and push a new recovery through that?
Click to expand...
Click to collapse
That would be the only remaining option, but ROM Manager is known to do this. If a user cannot even read on a forum before doing stuff, I'm not sure this is going to work out very well.
OK. I'll go back to my hermit cave now.
No, I can only boot in APX mode!
Isn't there any way we can make the adb reconize and access the PAD?
I can bring the recovery image and put in the root of the SD card, but what should I name it so the boot can reconize it and update? (the device says "checking for android ota recovery" !!
shreef said:
No, I can only boot in APX mode!
Isn't there any way we can make the adb reconize and access the PAD?
I can bring the recovery image and put in the root of the SD card, but what should I name it so the boot can reconize it and update? (the device says "checking for android ota recovery" !!
Click to expand...
Click to collapse
APX is NOT adb -- you need to issue commands using fastboot. Did you use the manufacturer's switch? "adb devices" won't return anything, even on a perfectly healthy 700. Take a look here:
http://forum.xda-developers.com/showthread.php?t=1926286
and don't forget to use that switch: -i 0x0B05, as in
fastboot -i 0x0B05 <command>
For example, fastboot -i 0x0B05 devices or fastboot -i 0x0B05 reboot
EDIT: APX = FASTBOOT, for clarity.
MartyHulskemper said:
That would be the only remaining option, but ROM Manager is known to do this. If a user cannot even read on a forum before doing stuff, I'm not sure this is going to work out very well.
OK. I'll go back to my hermit cave now.
Click to expand...
Click to collapse
I only asked because I thought ROM manager was known to brick this tablet if you tried to install a recovery with it. I may be mistaken though.
Sent from my ASUS Transformer Pad TF700T
MartyHulskemper said:
APX is NOT adb -- you need to issue commands using fastboot.
Click to expand...
Click to collapse
APX is also NOT fastboot - in APX mode you can *only* use nvflash, but for that you'd need to have created the blob before bricking.
I am sorry, I didn't really understand what you are trying to say!!
What does "manfacturer's switch" mean?
Also, what does APX = FASTBOOT ?
shreef said:
I am sorry, I didn't really understand what you are trying to say!!
What does "manfacturer's switch" mean?
Also, what does APX = FASTBOOT ?
Click to expand...
Click to collapse
shreef, the short answer is that only ASUS can help you now. I believe that is your only solution.
I'm so sorry.
OK, I have sent it to ASUS!
Thank you guys for your care and help.
Regards
ArmyAg08 said:
I only asked because I thought ROM manager was known to brick this tablet if you tried to install a recovery with it. I may be mistaken though.
Sent from my ASUS Transformer Pad TF700T
Click to expand...
Click to collapse
You're right. I wasn't mad/annoyed at your post. I just wanted to point out it has been known for a while now that ROM Manager does funky things on the 700. I'd just stay away from it -- iIn the sense that if one aspect of a program is broken by a device's particulars, changes are relatively high that some other aspect(s) is/are broken as well and you might get to know which one(s) that is/are by first-hand experience.
_that said:
APX is also NOT fastboot - in APX mode you can *only* use nvflash, but for that you'd need to have created the blob before bricking.
Click to expand...
Click to collapse
You're right. I was cutting the curve. I'm sorry for the confusion.
okantomi said:
shreef, the short answer is that only ASUS can help you now. I believe that is your only solution.
I'm so sorry.
Click to expand...
Click to collapse
That is quite the accurate summary.
@OP: hope ASUS treats your device nicely and you can get back in our midst with a 700 working well for you, soon.
I updated to the newest version from asus site Version WW_V10.6.1.8 and then by mistake flashed the latest version of TWRP recovery. now the tablet is in recovery boot loop. I tried the next command: "adb reboot bootloader" and managed ti get fastboot to work but adb shell does not work.
The weirdest thing is when I press the green android icon in boot loader screen, the system boots normally!!!! but!!! when i do restart it always boots into the twrp screen. the only way to boot the system is with your command. I tried to flash the patched recovery which works with the new firmware (the flash is ok) but i cant pass the recovery screen. How can I get rid of this recovery????
If fastboot is still working ok I would suggest re-flashing the stock 4.2.1 (10.6.1.8) system blob. After doing so you will be completely stock again, so you'll have stock recovery and no root. You can then root again & flash the patched twrp again.
Either of these two threads has the info & commands needed as well as links to the patched twrp for the 4.2.1 bootloader.
[GUIDE] Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked Devices
[HOW-TO] Upgrade or Downgrade to any stock JB Firmware
pjc21 said:
If fastboot is still working ok I would suggest re-flashing the stock 4.2.1 (10.6.1.8) system blob. After doing so you will be completely stock again, so you'll have stock recovery and no root. You can then root again & flash the patched twrp again.
Either of these two threads has the info & commands needed as well as links to the patched twrp for the 4.2.1 bootloader.
[GUIDE] Update/Recovery/Root/Downgrade Android 4.2.1 on Unlocked Devices
[HOW-TO] Upgrade or Downgrade to any stock JB Firmware
Click to expand...
Click to collapse
i did it. it still does the same thing. goes into recovery each time i turn on the tablet. it flashes but does nothing in the same time. is there any way to flash a new recovery or a new rom from inside the system??
tainka said:
i did it. it still does the same thing. goes into recovery each time i turn on the tablet. it flashes but does nothing in the same time. is there any way to flash a new recovery or a new rom from inside the system??
Click to expand...
Click to collapse
If when you flash the system blob via fastboot & you do not get the blue progress bar on the tablet this means that your fastboot is dead with no known fix. This seems to be caused be flashing the incorrect recovery on 4.2.1 (10.6.1.8) bootloader.
To test:
after running the command "fastboot -i 0x0b05 flash system blob" on the command prompt on pc it will say complete but you will get no progress bar on the tablet, after this command run "fastboot reboot" if the tablet does not reboot to this command then you are in the below group sorry.
http://forum.xda-developers.com/showthread.php?t=2179874
pjc21 said:
If when you flash the system blob via fastboot & you do not get the blue progress bar on the tablet this means that your fastboot is dead with no known fix. This seems to be caused be flashing the incorrect recovery on 4.2.1 (10.6.1.8) bootloader.
To test:
after running the command "fastboot -i 0x0b05 flash system blob" on the command prompt on pc it will say complete but you will get no progress bar on the tablet, after this command run "fastboot reboot" if the tablet does not reboot to this command then you are in the below group sorry.
http://forum.xda-developers.com/showthread.php?t=2179874
Click to expand...
Click to collapse
there is no blue progress bar. so there is no solution for that?
tainka said:
there is no blue progress bar. so there is no solution for that?
Click to expand...
Click to collapse
Sorry to say but no.
The only solution is to replace the motherboard, replace the tablet or send to asus for repair which will cost about the same as a new tablet.
Replacing the motherboard looks like the cheapest way to go as you can pick up a second hand tablet with a broken screen but still has a good motherboard for just over $100 on ebay.
pjc21 said:
Sorry to say but no.
The only solution is to replace the motherboard, replace the tablet or send to asus for repair which will cost about the same as a new tablet.
Replacing the motherboard looks like the cheapest way to go as you can pick up a second hand tablet with a broken screen but still has a good motherboard for just over $100 on ebay.
Click to expand...
Click to collapse
the funny thing is that the tablet boots in cold boot and works perfect. I just cant reboot it of turn it off. is it worth the motherboard replacement?
tainka said:
the funny thing is that the tablet boots in cold boot and works perfect. I just cant reboot it of turn it off. is it worth the motherboard replacement?
Click to expand...
Click to collapse
Well that's the thing, you can leave as is but now don't have the option to flash anything else until there is a fix that may or may not come along.
Seeing that you still have a working os it really depends on what you want out of the tab.
It is a very weird issue & I don't believe that the motherboards are actually fried in any way but rather locked up somehow in a conflict between the recovery & bootloader but not sure on that & not sure if there will be a solution for this. So it's really up to you. Sorry I could not be of more help here.
I found multiple development threads that are close to this, but here's the deal...
I took Asus 4.2.1 OTA update and used that for a while.
The device was already unlocked and I decided to try TWRP 2.4.4.0 for recovery before trying any custom ROMs
I followed the big bold red instructions that said:
If you have taken the official Asus Jellybean OTA then be sure to install the '-JB' version of the recovery for your device - and only flash roms that are based on the Asus OTA.
I downloaded the -JB version (at that time, -ICS was the only other choice), and installed it via fastboot.
Upon rebooting, it will only boot into recovery and TWRP can't see any partitions. More importantly, I've spent almost a month now reading the threads that are related to this trying various suggestions in trying to break out of this, and during this time, I've realized that I can't flash anything. ADB works, but the devices says "123456789ABCDEF recovery". I can run "adb reboot bootloader" and I will get my 3-icon 4.2.1 bootloader screen with a blinking green square on RCK. Fastboot devices shows my S/N, and it acts like it is flashing (tried flashing the -4.2 version of TWRP 2.4.4.0 and a new copy of the JB 4.2.1 OTA ROM), but all the tablet does is lock-up. The green square stops blinking and, even though fastboot says it's working, the tablet is no longer responding and requires a reset to reboot, upon which it boots right back into TWRP.
I'm just asking if there is a way out of this yet that doesn't involve replacing the main logic board.
I suppose what bothers me more, is that Teamwin's website for TWRP still has the same instructions in big bold red letters, without acknowledging that there are TWO official Asus Jellybean OTA releases. One will work just fine with the -JB version they specify to download, the other will do what mine did. Anyone current with Asus releases is gonna follow these instructions and brick their pads unless they already know about the -4.2 version of TWRP.
Yo!
Have you tried flashing asus stock 4.2.1 system blob using adb?
Do you know what the command for that would be? I have the same problem. But I don't wanna flash it to the wrong partition.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
klownin5643 said:
Do you know what the command for that would be? I have the same problem. But I don't wanna flash it to the wrong partition.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
This is the link to the instructions i followed. http://forum.xda-developers.com/showthread.php?t=2187982
Here is the main point.
- Method 2: Update using fastboot
Notes:
You will keep all your data
This is the best method to update your tablet if you want to keep all your data, and the safest one
Ensure you have the correct drivers for the tablet installed on your computer, or you will have a "waiting for device" error
To update using fastboot, follow this steps:
If you don't have fastboot yet, download it from here an unpack it somewhere on your computer
Extract the Asus firmware file and put the blob file inside fastboot folder
Open a command line on fastboot folder (write "cmd" on Windows search bar at the Start menu, and then
Code:
cd "FOLDER WHERE YOU EXTRACTED FASTBOOT"
, or you can just use SHIFT + RIGHT CLICK on the folder and select "Open command line window here" or something like that)
Reboot the tablet holding the volume down key until you see some icons. Use the volume down key to select the USB icon and then volume up to select it
Connect the tablet to the computer if you didn't do so
Write
Code:
fastboot -i 0x0B05 flash system blob
, hit enter and wait until it completes
Write this to reboot your tablet:
Code:
fastboot reboot
or hold the power button for 10 seconds if the code doesn't work
You are now updated to Android 4.2
There are 3 things keeping this from working:
1) fastboot -i 0x0B05 flash system blob
This locks the tablet up. Fastboot thinks it's still working, but the blinking RCK has stopped blinking and...
2) fastboot reboot
... doesn't work because the tablet has locked up from the flash attempt. You have to...
3) hold the power button for 10 seconds if the code doesn't work
Which does reboot the tablet, but it goes right back into TWRP, and you have NOT been updated to anything.
Now, in my particular case, I can get it to "adb reboot bootloader" and tell it to cold boot Linux to get into my OS, but that never happens either. It's likely been wiped from one of my multiple attempts at trying others' suggestions for getting out of this.
I'm sorry, you bricked your tablet permantly... Only Asus can fix it now... You flashed a wrong recovery for your tablet... You read the wrong post! That one is for Android 4.1 and not 4.2...
joelalmeidaptg said:
I'm sorry, you bricked your tablet permantly... Only Asus can fix it now... You flashed a wrong recovery for your tablet... You read the wrong post! That one is for Android 4.1 and not 4.2...
Click to expand...
Click to collapse
I did the same thing as the OP. I'm not new at this, I've rooted and run custom ROMs for years on dozens of devices. I always do lots of research before starting the process. What the OP and I are saying is that the Team Win site doesn't state anything about the 421 patch and if you look at the file list, the patch only exists in the 2.4.4.0 version. With those two things in mind, a reasonable person would conclude that 2.5.5.0 is patched for both...as long as you use the -JB version. Obviously wrong as I now know, but certainly not clearly wrong before bricking the device.
I would never assume to blame the Dev's, but I (we) are asking that they be a bit more blatant with the fact JB v4.2 MUST USE TWRP version 2.4.4.0-4.2 and not anything else.
Now, for good or bad, so many people have now bricked their TF300's that there are many threads like this one. Any research at this point will reveal this issue. Still, Team Win should post the warning.
joelalmeidaptg said:
I'm sorry, you bricked your tablet permantly... Only Asus can fix it now... You flashed a wrong recovery for your tablet... You read the wrong post! That one is for Android 4.1 and not 4.2...
Click to expand...
Click to collapse
I wish it was as simple as reading the wrong post... When I downloaded TWRP 2.4.4.0, there were only -ICS and -JB files listed (much like TWRP 2.5.0.0 is now)... Wouldn't you have picked -JB?
Even now, Teamwin's directions tell you that, if you took the Asus JB OTA, that you need the -JB version. They don't differentiate WHICH JB OTA, and they don't mention that a -4.2 version specifically for the 4.2.1 OTA exists. Never mind mentioning that using the -JB version on the latest Asus JB OTA update will BRICK THE TABLET.
There are 192 people that have downloaded the 2.5.0.0-JB blob file as of now. How many of these folks do you suppose have taken the Asus 4.2.1 OTA update and are about to permabrick their tablets?
It sickens me to know of the 192, likely most are on 4.2.1. I only hope they catch it before pushing the ROM.
When you flash recovery its flash ix505blah recovery recovery.blob is it flash ix5o5blah system system.blob? If that makes sense? Or no.?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
The two things here centers around the fact that TWRP is the only thing that will boot, other than the bootloader (but you have to boot TWRP first).
1) If you are in TWRP, there are no partitions mounted. In fact, there are no mmcblk devices at all, which is why there are no partitions mounted. As a result, there is nothing to flash to from here (even if fastboot worked). Adb works from here, but the device serial says "123456789ABCDEF recovery". Fastboot detects no devices at all from here.
2) If you reboot bootloader from adb, you can get access to fastboot. However, any flashing from here locks up the tablet, even though the command looks like it's running and completing the first time. Adb does NOT work from here, sees no devices. Fastboot looks like it sees the right device until you try to flash something with it. Once you try to flash anything, no fastboot command completes, furthering the notion that the tablet is frozen. A reset reboots the tablet back into TWRP, and nothing has changed. Repeat the cycle ad nauseum.
Basically, you can't do squat from TWRP, and fastboot flash from the bootloader locks up the tablet so you can't flash anything. I'm pretty sure it will take a logic board replacement to fix it at this point unless someone comes up with something better.
I'm having the exact same issue as you... I had flashed the TWRP JB blob and it couldn't recognize anything so I tried to flash CWM. Now...My fastboot doesn't do a thing since the blue progress bar doesn't show up and just freezes when trying to flash the stock firmware. I don't think I can send it to Asus for warranty either since my device is unlocked.
Well, I figured there's nothing to lose, so "fastboot erase recovery" got rid of TWRP. So now, it just hangs at the Asus logo unless you hold Vol- while booting, then you get the standard 3-icon bootlader.
I still can't flash anything with fastboot without it locking up though. Not sure I got anywhere... lol.
splashg said:
Well, I figured there's nothing to lose, so "fastboot erase recovery" got rid of TWRP. So now, it just hangs at the Asus logo unless you hold Vol- while booting, then you get the standard 3-icon bootlader.
I still can't flash anything with fastboot without it locking up though. Not sure I got anywhere... lol.
Click to expand...
Click to collapse
You can't flash a recovery? And what about the stock Rom?
Sent from my WT19i using xda app-developers app
splashg said:
Well, I figured there's nothing to lose, so "fastboot erase recovery" got rid of TWRP. So now, it just hangs at the Asus logo unless you hold Vol- while booting, then you get the standard 3-icon bootlader.
I still can't flash anything with fastboot without it locking up though. Not sure I got anywhere... lol.
Click to expand...
Click to collapse
Lol did that too...I don't know if there is anything left to try. Did you try putting stock rom on an external SD card and running RCK?
Ok...so now that I won one, there is a guy on e-bay that has a bunch of TF300T-b1-bl 32gb Transformers with broken screens. He is posting pictures and they all appear (based on the picture) that they have operable firmware. Mine will be here late in the week...I'll pull the main board and put it in mine. I'll let you know how it goes.
splashg said:
Well, I figured there's nothing to lose, so "fastboot erase recovery" got rid of TWRP. So now, it just hangs at the Asus logo unless you hold Vol- while booting, then you get the standard 3-icon bootlader.
I still can't flash anything with fastboot without it locking up though. Not sure I got anywhere... lol.
Click to expand...
Click to collapse
I did the same thing and got the same result. This i very interesting because the
Code:
fastboot -i 0x0b05 flash <partition> <filename>
command which tries to write/edit something on the partition fails (maybe is due to some encryption introduced in 421) but the
Code:
fastboot -i 0x0b05 erase <partition>
which also does the write/edit, succeeds. What I'm trying to say is that either both should fail or succeed because both are trying to do some editing to the storage.
steveb05 said:
Ok...so now that I won one, there is a guy on e-bay that has a bunch of TF300T-b1-bl 32gb Transformers with broken screens. He is posting pictures and they all appear (based on the picture) that they have operable firmware. Mine will be here late in the week...I'll pull the main board and put it in mine. I'll let you know how it goes.
Click to expand...
Click to collapse
Yeah, if it's the ones I've seen the hard part there is that they go for more than a replacement logic board does. Sure, there's likely some other parts still good in there, but if it just has a bad digi, I'm too apt to fix the digi... Basically, I need one where both the digi and the LCD are shot, and goes for less than the logic board does.
Joel, yeah, we can't flash anything. Fastboot flash <any partition> <any file> locks the tablet up. As Vahid alludes to, this is very odd because we have no trouble with fastboot erase. Having a stock image on an SD card and trying to get RCK to reload it doesn't work, presumably because it can't mount the external SD card.
splashg said:
Yeah, if it's the ones I've seen the hard part there is that they go for more than a replacement logic board does. Sure, there's likely some other parts still good in there, but if it just has a bad digi, I'm too apt to fix the digi... Basically, I need one where both the digi and the LCD are shot, and goes for less than the logic board does.
Joel, yeah, we can't flash anything. Fastboot flash <any partition> <any file> locks the tablet up. As Vahid alludes to, this is very odd because we have no trouble with fastboot erase. Having a stock image on an SD card and trying to get RCK to reload it doesn't work, presumably because it can't mount the external SD card.
Click to expand...
Click to collapse
Just got my TF300 back for Asus service center. They said that they had to replace the motherboard @ a cost of $186.00 total, parts and labor. Told them to just send it back. I'll buy a Nexus 7 instead for the same price almost.
Got my broken TF300 ebay win today. Digitizer and LCD were toast. But, the main board went right in to my bricked TF300. I'm unlocked, rooted, and running 4.1.1 and life is good!
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I configured nvflash on a new unrooted, unlocked TF300T, running the 9.4.3.30 firmware by following the directions at. androidroot mobi t3_nvflash. The AndroidRoot9.4.0.30r01 bootloader and nvflash were installed and the tablet was successfully booted into APX mode, nvflash was bootstrapped using wheelie, and the bricksafe.img, factory-config.img and unlock-token.img files were generated and saved.
Unfortunately, I was not able to use fastboot to install clockworkmod recovery or enable root. Flashing was attempted initially using Windows XP and again later using Ubuntu 12.04, with the following result:
# fastboot -i 0x0B05 flash recovery recovery.img
sending 'recovery' (5306 KB)...
OKAY [ 2.443s]
writing 'recovery'...
OKAY [ 2.058s]
finished. total time: 4.500s
# fastboot -i 0x0B05 reboot
rebooting...
All seems well, but recovery does not install, the tablet does not reboot, and will not accept further flashboot commands. It has to be restarted by holding down the start button. On restart a blue line quickly flashes across the screen, but on boot to fastboot/recovery mode there is no icon to access recovery.
Device: TF300T Transformer Pad
Android Version 4.0.3;
Build Number: IML74.US_epad-9.4.3.30-201220604
Questions:
To what partition/folder is the recovery image flashed on the TF300T?
Has anyone ever actually used nvflash to unbrick a TF300T? If so will someone point me to instruction how to repair/restore the original/unlocked bootloader using nvflash, or something close?
Is there a procedure to install CWM recovery using nvflash?
Thank you for your help, any assistance is appreciated.
Some Hard Learned Advice
I'm still unable to flash a custom recovery, but the good news is that my tablet works although it's not rooted, and I have a functioning nvflash
If you want to avoid my problem, I recommend that you root your tablet before you install nvflash. Remember that at present, you can only install nvflash on a TF300T running ICS but, definitely do install nvflash. Follow the instructions from the folks at androidroot.mobi, but don't forget to root first.
listerism said:
I'm still unable to flash a custom recovery, but the good news is that my tablet works although it's not rooted, and I have a functioning nvflash
If you want to avoid my problem, I recommend that you root your tablet before you install nvflash. Remember that at present, you can only install nvflash on a TF300T running ICS but, definitely do install nvflash. Follow the instructions from the folks at androidroot.mobi, but don't forget to root first.
Click to expand...
Click to collapse
I believe you would want to follow the guide in the General section for the TF300 to upgrade from ICS to JB 4.1.1. Its called
[GUIDE]Upgrade your TF300t to Jellybean 4.1, root & remove bloatware[Noobproof]
Then update to the newest version of 4.1.1. Then finally put a version of TWRP that is compatible with the 4.1.1 bootloader on the device. Also when I Installed the recovery I used the "recovery.blob" file, not the .img
listerism said:
I configured nvflash on a new unrooted, unlocked TF300T, running the 9.4.3.30 firmware by following the directions at. androidroot mobi t3_nvflash. The AndroidRoot9.4.0.30r01 bootloader and nvflash were installed and the tablet was successfully booted into APX mode, nvflash was bootstrapped using wheelie, and the bricksafe.img, factory-config.img and unlock-token.img files were generated and saved.
Unfortunately, I was not able to use fastboot to install clockworkmod recovery or enable root. Flashing was attempted initially using Windows XP and again later using Ubuntu 12.04, with the following result:
# fastboot -i 0x0B05 flash recovery recovery.img
sending 'recovery' (5306 KB)...
OKAY [ 2.443s]
writing 'recovery'...
OKAY [ 2.058s]
finished. total time: 4.500s
# fastboot -i 0x0B05 reboot
rebooting...
All seems well, but recovery does not install, the tablet does not reboot, and will not accept further flashboot commands. It has to be restarted by holding down the start button. On restart a blue line quickly flashes across the screen, but on boot to fastboot/recovery mode there is no icon to access recovery.
Device: TF300T Transformer Pad
Android Version 4.0.3;
Build Number: IML74.US_epad-9.4.3.30-201220604
Questions:
To what partition/folder is the recovery image flashed on the TF300T?
Has anyone ever actually used nvflash to unbrick a TF300T? If so will someone point me to instruction how to repair/restore the original/unlocked bootloader using nvflash, or something close?
Is there a procedure to install CWM recovery using nvflash?
Thank you for your help, any assistance is appreciated.
Click to expand...
Click to collapse
Since you already have installed nvflash and have your files I'll try to answer with that in mind.
First I suggest using twrp of the latest version for ICS not cwm.
The partition for recovery is recovery. The commands you provided are correct (I do suggest using a blob file with fastboot - and twrp not cwm).
For unbrick with nvflash yes others have here is a link with the commands needed.
Remember you only have to flash what is needed to recover your tablet.
Did you perhaps download the wrong version of recovery? There is specific versions for ICS and JB 4.1.1 and JB 4.2.1. However I think of you use a blob instead it may work. But as above posters said, I would update to the version of stock android that you want. Cuz when you update your going to loose root and recovery anyways so why bother putting it on there? So I wouldn't flash anything till you are on the version you want to root. Also it will be safer to upgrade with stock recovery. TONS of people have bricked by updating to 4.2.1 with an incompatible recovery. You've been warned.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Nevermind. I need to read entire posts...
No USB icon
Hi Guys,
I have 4.2.1 installed and want to move up to 4.2.2 however i now notice that when I try to boot back into recovery I have no USB icon to reinstall TWRP. I used TWRP 2.5 to install 4.2.1. Can someone explain how I can get TWRP back onto the system and get my USB icon back so I can keep up to date.
Your assistance will be gratefully appreciated.
Cheers
Asus TF300T
The 4.2 bootloader doesn't have a separate fastboot mode. As soon as you're in the bootloader, fastboot starts. There's no icon to select because it's already in fastboot mode.
speye007 said:
Hi Guys,
I have 4.2.1 installed and want to move up to 4.2.2 however i now notice that when I try to boot back into recovery I have no USB icon to reinstall TWRP. I used TWRP 2.5 to install 4.2.1. Can someone explain how I can get TWRP back onto the system and get my USB icon back so I can keep up to date.
Your assistance will be gratefully appreciated.
Cheers
Asus TF300T
Click to expand...
Click to collapse
The new 4.2 bootloader has no usb icon. When you enter the bootloader do not press any keys you will automatically enter usb mode. Watch the upper left for a message showing fastboot started..
---------- Post added at 10:34 AM ---------- Previous post was at 10:33 AM ----------
EndlessDissent said:
The 4.2 bootloader doesn't have a separate fastboot mode. As soon as you're in the bootloader, fastboot starts. There's no icon to select because it's already in fastboot mode.
Click to expand...
Click to collapse
You were to quick for me that time.
tobdaryl said:
The new 4.2 bootloader has no usb icon. When you enter the bootloader do not press any keys you will automatically enter usb mode. Watch the upper left for a message showing fastboot started..
---------- Post added at 10:34 AM ---------- Previous post was at 10:33 AM ----------
You were to quick for me that time.
Click to expand...
Click to collapse
Thanks I'll let you know it goes
speye007 said:
Thanks I'll let you know it goes
Click to expand...
Click to collapse
Well thanks that did work however I now have and issue with TWRP wanting a password and I've tried the
http://forum.xda-developers.com/showthread.php?t=2187982
Click to expand...
Click to collapse
fix but I get a dual screen of TWRP and can't do a thing with it is there a way that I can wipe the unit and start again this is getting frustrating and from what I can see no one from TWRP is offereing any suggestions to fix this issue either.....very frustrating as this is my daily
Your assistance would be gratefully appreciated
Cheers
speye007 said:
Well thanks that did work however I now have and issue with TWRP wanting a password and I've tried the fix but I get a dual screen of TWRP and can't do a thing with it is there a way that I can wipe the unit and start again this is getting frustrating and from what I can see no one from TWRP is offereing any suggestions to fix this issue either.....very frustrating as this is my daily
Your assistance would be gratefully appreciated
Cheers
Click to expand...
Click to collapse
The reason no one from TWRP is fixing it is because there's nothing to fix. It wasn't a TWRP bug. It was ASUS's bug, and they fixed it in the most recent OTA update. I would suggest using fastboot to flash back to stock to get your stock recovery back, then update to the most recent OTA, then you can flash TWRP back.
Edit: What I just said was actually kind of in the OP of the thread to which you linked, in bright red letters. It said that you need to be on the very latest OTA for that version of TWRP to work. In fact, those were, more-or-less the very first words in the post.
EndlessDissent said:
The reason no one from TWRP is fixing it is because there's nothing to fix. It wasn't a TWRP bug. It was ASUS's bug, and they fixed it in the most recent OTA update. I would suggest using fastboot to flash back to stock to get your stock recovery back, then update to the most recent OTA, then you can flash TWRP back.
Edit: What I just said was actually kind of in the OP of the thread to which you linked, in bright red letters. It said that you need to be on the very latest OTA for that version of TWRP to work. In fact, those were, more-or-less the very first words in the post.
Click to expand...
Click to collapse
Hi sorry its taken me time to get back. I've had some issues with this I now get a double TWRP screen that I can't do anything with and when I can get back to a normal screen it asks for a password all the time and I've tried to factory reset from inside (not from twrp) and it does nothing at all
So I'd like to try and reset back to factory and start again if thats possible? And is there a good tutorial on this?
Cheers & thank you for your assistance
speye007 said:
Hi sorry its taken me time to get back. I've had some issues with this I now get a double TWRP screen that I can't do anything with and when I can get back to a normal screen it asks for a password all the time and I've tried to factory reset from inside (not from twrp) and it does nothing at all
So I'd like to try and reset back to factory and start again if thats possible? And is there a good tutorial on this?
Cheers & thank you for your assistance
Click to expand...
Click to collapse
If you want to go back to stock, just flash the stock firmware in fastboot. There are lots of guides for flashing stock ROMs throughout the forum.
EndlessDissent said:
If you want to go back to stock, just flash the stock firmware in fastboot. There are lots of guides for flashing stock ROMs throughout the forum.
Click to expand...
Click to collapse
I found the issue you need to go to this version of TWRP (which I may add is not on the download list fromTWRP) http://goo.im/devs/OpenRecovery/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
I now have TWRP working and I'm running 10.6.1.8 however I find that I can not factory reset or use TWRP to upgrade firmware to 10.6.1.15 or any other ROM. The device says "Device is unlocked" & I'm also having an issue trying to locate a good tutorial on how to flash new firmware or kernel with fastboot. If anyone knows of a great tutorial that is easy to follow and also how I can obtain any of the required .img files that would be great.
This is getting frustrating now not being able to flash anything at all (angry)
I'm also getting an error message when I try to use the Asus unlock apk (An unknown error occurs,which maybe a network connection issue. Please wait and try again later) yes done toooo many times.
I've now even tried to flash CWM instead of TWRP and nothing ....the device boots fine and works fine I just can not factory reset, or install a new or updated rom from TWRP.
Message from TWRP :
Updating partition details...
Simulating actions...
Updating partition details...
and TWRP says Successful but nothing happens
can someone help me out here before I rip what little hair I still have out ggggrrrrrrrr