Related
Hi there. I was fooling around with my TF300T (I was foolish at some point, probably) and managed to install Jellybean using this method. It started working fine. So it did that I restored my files using Titanium Backup Pro, installed from the App store right after the first boot. The apps/data I restored with Titanium Backup, as far as I can remember, were mostly games and Dolphin stuff, nothing directly related to system, as far as I know.
After this backup restoration, I used the tablet a little more, played the games to check if my progress was not lost and all that. It worked, Angry Birds at least had all the levels I completed before yet marked as completed after restore the procedure.
So far so goo... no! For some reason I can't remember I restarted the tablet, at least I tried! It got stuck on the loading screen (the white Asus, not the shiny one). So, after that I tried to restore it again, and then I probably did something completely stupid and I can't even remember what.
I even tried superwipe on it, but that didn't work neither.
At this point my tablet let me flash recovery image, CWM and TWRP. I can use adb shell with CWM but not with TWRP.
For some reason, I don't know, when I use CWM it doesn't mount /sdcard, TWRP seem to be mounting it, but go figure, I can only access the /sdcard that TWRP mounts using TWRP, if I change the recovery to CWM for some bizarre (or obvious to you guys) reason, I can't mount it.
And no matter what recovery I use, I can't flash any ROM. Both recovery tells me it was flashed, no error message (at least not at the screen) but every time it reboots to finish the installation, I see the Asus logo with a progress bar that goes from 0% to 100% in less then one second, and once it's filled, the tablet reboots itself and show me the regular boot screen with the Asus logo (again, the white one, not the silver-shiny).
So, resuming my problem, I can fastboot and adb shell it (adb only with ClockWorkMod Touch), but flashing doesn't seem to work. And I believe the internal memory/storage structure have been compromised.
How do I fix this?
Here is what I did to fix it
brbjr said:
...
Download a cm9 rom, open the zip file and extract boot.blob . Flash with 'fastboot -i 0x0B05 flash boot boot.blob' then reboot...
Click to expand...
Click to collapse
manegonzalez said:
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
Click to expand...
Click to collapse
Doing it now. I'll update as soon as I finish it. Thank you very much for your reply.
UPDATE 1: I can see the shiny-silver ASUS and the progress circles, waiting to see what happen!
UPDATE 2: Setting up Jellybean now (Welcome setup)!
UPDATE 3: Looks like it's working!
Dude, thank you so much! I'll fool around with it. Is there a root method working already? I was wondering if there's a way to restore my backups, at least the ones I made for my gaming progress.
Man you saved my life. Thank you very much!
When i try it i get error: "Failed to process command flash: system error(0xa)"
any help?
Thank you for posting this thread, I wasn't paying attention one day and flashed the wrong version of something and ended up stuck on the white Asus logo. Flashed a ROM's blob via fastboot and was up and running in no time, though it did take 2 attempts, the first time it received the blob but failed to write it.
Itege said:
Thank you for posting this thread, I wasn't paying attention one day and flashed the wrong version of something and ended up stuck on the white Asus logo. Flashed a ROM's blob via fastboot and was up and running in no time, though it did take 2 attempts, the first time it received the blob but failed to write it.
Click to expand...
Click to collapse
You're welcome!
Now click thank you so you can help me
I recommend you to use the CleanROM 2.5, it's stable and fast! Really fast! Faster then the ASUS Stock ROMs. I'm really enjoying it.
Still can't flash ROMs
Thanks so much for this. It really helped to get me back to where I was. However, I still can't flash any roms besides the stock asus jb. What can i do? I've tried several different ROMs. I still get stuck at the ASUS "The Device is Unlocked" page
poisondminds said:
Thanks so much for this. It really helped to get me back to where I was. However, I still can't flash any roms besides the stock asus jb. What can i do? I've tried several different ROMs. I still get stuck at the ASUS "The Device is Unlocked" page
Click to expand...
Click to collapse
Fastboot TWRP or CWM recovery, format everything in there and flash ex. cleanrom 2.5
Let me know if it won't work
allram said:
Fastboot TWRP or CWM recovery, format everything in there and flash ex. cleanrom 2.5
Let me know if it won't work
Click to expand...
Click to collapse
For CleanROM he'll need a specific TWRP version. It's better give CleanROM thread a read before install it.
allram said:
When i try it i get error: "Failed to process command flash: system error(0xa)"
any help?
Click to expand...
Click to collapse
Any luck with this? I'm having the same issue...
This tablet is such a fiesty little *****... Nowhere near as simple as my GNex to flash things.
I'm having the exact same issue as you did. It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
Please tell me you know what to do... I'm getting desperate. I can't end up with a $500 paperweight...
Guticb said:
Any luck with this? I'm having the same issue...
This tablet is such a fiesty little *****... Nowhere near as simple as my GNex to flash things.
I'm having the exact same issue as you did. It just will NOT let me flash the stock JB rom. The tablet tells me Failed to process command flash:systemerror (oxa) and command prompt says
C:\Fastboot>fastboot -i 0x0B05 flash system blob
sending 'system' (799748 KB)... OKAY [144.648s]
writing 'system'... FAILED (remote: (InvalidSize))
Please tell me you know what to do... I'm getting desperate. I can't end up with a $500 paperweight...
Click to expand...
Click to collapse
1. Please, make sure the Tablet is the only one Android device connected to your computer
2. The bootloader is unlocked, right?
3. It's not the matter (almost impossible to be the case), but what are you using as recovery, TWRP or CWM?
4. Are you trying to flash the Official ROM?
- Sent from the Future, using my Delorean
- Enviado do Futuro, usando meu Delorean
mizifih said:
Originally Posted by brbjr View Post
...
Download a cm9 rom, open the zip file and extract boot.blob . Flash with 'fastboot -i 0x0B05 flash boot boot.blob' then reboot...
Quote:
Originally Posted by manegonzalez View Post
hey I was super frustrated by this but I took some time out and then I found this post I tried it and it worked perfectly give it a shot
Looks like partition sizes chaged with the Asus update. I couldn't flash CM10 or any other rom as well (signature mismatch). If you installed the official 4.1.1 update, you need to manually install it again. Older versions and rollbacks wont work unless you push to some trickery mmcblk0p4, but that's another thread in itself
Download the JB update from Asus's website (if you still have it, that's fine) and extract the blob file. Put the blob file in teh same directory as your fastboot. Boot your TF300 into bootloader and enter:
fastboot -i 0x0B05 flash system blob
It will take a while to install, so be patient. Hope this helps
Click to expand...
Click to collapse
This is an awesome fix, thought I was buggered with a tablet that couldnt mount anything, couldn't get into download mode, recovery was fubared.. and then I stumbled on this
THANK YOU
Hi all,
I have flashed numerous roms onto my TF300 over the months, and decided to have a go at the new Jelly Bean Hydro by seanzscreams. After flashing the US 400mb standard rom from ASUS, I followed the steps and went into fastboot. From there I used Imraans method of copying my fastboot.exe and the others onto a folder called Recovery1 in my Program Files (x86). However, my device does not seem to respond to any files that I am sending through to it..as in on my cmd it is just stuck at the 'sending 'recovery' <7304KB>. After being unable to send anything to my device and it not being able to boot (btw I did not receive any sort of signature flash confirmation) I decided to wipe my data from the bootloader. I was then able to boot into the ASUS JB rom (the US version, my tf300 is WW) , which I am currently using. Now, as twrp goo imanager is not up yet the only way I can flash any recovery is via my cmd..so what can I do? My bootloader is obviously unlocked, as I tap onto the USB icon and hit volume up my computer recognizes the fastboot device..but I am unable to send anything (or flash) into the device from fastboot..(to clarify this is the "fastboot -i 0x0B05 flash recovery twrp.blob" command.) This is most likely something very simple that I have not realized but if anyone can help, please respond!
Thanks in advance.
because Idsera
Von Clausewitz said:
Hi all,
I have flashed numerous roms onto my TF300 over the months, and decided to have a go at the new Jelly Bean Hydro by seanzscreams. After flashing the US 400mb standard rom from ASUS, I followed the steps and went into fastboot. From there I used Imraans method of copying my fastboot.exe and the others onto a folder called Recovery1 in my Program Files (x86). However, my device does not seem to respond to any files that I am sending through to it..as in on my cmd it is just stuck at the 'sending 'recovery' <7304KB>. After being unable to send anything to my device and it not being able to boot (btw I did not receive any sort of signature flash confirmation) I decided to wipe my data from the bootloader. I was then able to boot into the ASUS JB rom (the US version, my tf300 is WW) , which I am currently using. Now, as twrp goo imanager is not up yet the only way I can flash any recovery is via my cmd..so what can I do? My bootloader is obviously unlocked, as I tap onto the USB icon and hit volume up my computer recognizes the fastboot device..but I am unable to send anything (or flash) into the device from fastboot..(to clarify this is the "fastboot -i 0x0B05 flash recovery twrp.blob" command.) This is most likely something very simple that I have not realized but if anyone can help, please respond!
Thanks in advance.
Click to expand...
Click to collapse
EDIT: Seemed to fix it by changing to USB 2.0 port instead of 3.0..not sure why it would do that. In case anyone else had the same issue, try switching to an USB 3.0 Port.
Attempting to root, to backup then to install cm 10.1 or other rom
I've installed cwm from this thread http://forum.xda-developers.com/showthread.php?t=1668173
I can boot into recovery ok, however I get the following errors:
can't mount /cache/recovery/command
can't mount /cache/recovery/log
can't mount /cache/recovery/last_log
can't mount /cache/recovery/.
when trying to access internal or external sd card get:
can't mount /sdcare/
can't mount /emmc
Any help appreciated
Update: tried twrp 2.4.3.0 does the same thing
The new update has encryption by default. That's why you can't mount anything. I am not sure if team win will release an update for their recovery or if Asus needs to do it. Seems like this update really screwed over some people.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
The new update has encryption by default. That's why you can't mount anything. I am not sure if team win will release an update for their recovery or if Asus needs to do it. Seems like this update really screwed over some people.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
wow not good news. Guess I'l just have to monitor sites and see what happens over time.
Disappointing for sure as this last update screwed up the hdmi out, I have functional tablet it might as well be a bricked pos, arg !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
It's worthless to me in it's present state
Hmm where is the phone num so i can call gripe at asus
tonyjsan said:
wow not good news. Guess I'l just have to monitor sites and see what happens over time.
Disappointing for sure as this last update screwed up the hdmi out, I have functional tablet it might as well be a bricked pos, arg !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
It's worthless to me in it's present state
Hmm where is the phone num so i can call gripe at asus
Click to expand...
Click to collapse
Think you can only email them :/
I dont think its asus who encrypted it. I think it was google. I am not sure though so dont quote me xD
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
Think you can only email them :/
I dont think its asus who encrypted it. I think it was google. I am not sure though so dont quote me xD
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
twrp I think might support that sort of thing already, i went back into twrp2 and it does ask for a password at first, a check of the logs by twrp said can't decrypt
Who ever set the encryption, needs to show how to unset it.
I'm having the same issue that tonyjsan described.
This was I did:
1 - I updated to 4.2.1 via OTA.
2 - Download Asus unlock apk & unlocked the boot loader.
3 - Then installed the CWM 6.0.2.3 via fast boot.
4 - Tried to installed CM10.1 nightly couldn't acess SD started to get the following:
can't mount /cache/recovery/command
can't mount /cache/recovery/log
can't mount /cache/recovery/last_log
can't mount /cache/recovery/.
when trying to access internal or external sd card get:
can't mount /sdcare/
can't mount /emmc/
Now it's the point where I got stupid, and decided to go into the bootloader and do a full wipe, which I THINK wiped everything and installed the recovery Kernel (which now is CWM) into the main image.
Now my TF300T only boot to CWM and I can acess it via ADB do thing like push files, but i've lost the boot loader and cannot go into fastboot.
Really need the expertise of a guru right now
Help is appreciated
Getting Same Issues
Both the latest TWRP2 and latest CWM are a bust for me too.
If the recovery kernel image can't get at the disk partitions - then no custom ROMS
can be installed.
I guess being the first non-nexus with 4.2.1 isn't such great news after all.
xbill9 said:
If the recovery kernel image can't get at the disk partitions - then no custom ROMS
can be installed.
Click to expand...
Click to collapse
Starting to get the felling I have a 300$ dollar brick on my desk
Same Here
I've run into the same thing. I did the OTA update to 4.2.1, and then I decided to root, so I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2041627.
Unlocked worked.
Recovery Flash worked.
Mounting any part of the sdcard (internal or external) does not work in recovery.
I can still boot into the OS, so I'm not bricked, but I can't install root because I can't see the internal storage to flash it.
Is it possible to flash back to 4.1.1?
Yes, but your recovery must be working.
vconceicao said:
I'm having the same issue that tonyjsan described.
This was I did:
1 - I updated to 4.2.1 via OTA.
2 - Download Asus unlock apk & unlocked the boot loader.
3 - Then installed the CWM 6.0.2.3 via fast boot.
4 - Tried to installed CM10.1 nightly couldn't acess SD started to get the following:
can't mount /cache/recovery/command
can't mount /cache/recovery/log
can't mount /cache/recovery/last_log
can't mount /cache/recovery/.
when trying to access internal or external sd card get:
can't mount /sdcare/
can't mount /emmc/
Now it's the point where I got stupid, and decided to go into the bootloader and do a full wipe, which I THINK wiped everything and installed the recovery Kernel (which now is CWM) into the main image.
Now my TF300T only boot to CWM and I can acess it via ADB do thing like push files, but i've lost the boot loader and cannot go into fastboot.
Really need the expertise of a guru right now
Help is appreciated
Click to expand...
Click to collapse
vconceicao said:
Starting to get the felling I have a 300$ dollar brick on my desk
Click to expand...
Click to collapse
as sad as it seems :'( you are more than likely bricked. Every thread I read, even on 4.1 stock, once you do the "wipe all" option in bootloader menu, without a stock recovery. You become bricked.
wirikidor said:
I've run into the same thing. I did the OTA update to 4.2.1, and then I decided to root, so I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2041627.
Unlocked worked.
Recovery Flash worked.
Mounting any part of the sdcard (internal or external) does not work in recovery.
I can still boot into the OS, so I'm not bricked, but I can't install root because I can't see the internal storage to flash it.
Is it possible to flash back to 4.1.1?
Click to expand...
Click to collapse
You should be able to fastboot the stock Asus 4.1.1 .blob file.
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
vconceicao said:
Now it's the point where I got stupid, and decided to go into the bootloader and do a full wipe, which I THINK wiped everything and installed the recovery Kernel (which now is CWM) into the main image.
Now my TF300T only boot to CWM and I can acess it via ADB do thing like push files, but i've lost the boot loader and cannot go into fastboot.
Really need the expertise of a guru right now
Help is appreciated
Click to expand...
Click to collapse
When you said wipe, you used the wipe data option, when sitting at the first menu (boot loader menu) after pressing power and vol down ?
One other thing I'd share here to is that the factory wipe, from within settings, for me does not work, it boots to twrp / recovery, when I exit all data still there. So was wondering which one you used ?
Is the encryption on the partitions from sbk nvflash crap (i'm thinking not ??) or just an encrypted ext4 partition ??
elesbb said:
You should be able to fastboot the stock Asus 4.1.1
Click to expand...
Click to collapse
If I drop back to 4.1.1 will I have the same problem with not being able to access cache, data etc. in twrp or cwm, will it be encrypted ?
I'm also wondering dropping back to 4.1.1 will the 4.2.1 multi-user stuff mess with the downgrade, appears to be using sym links to create separate directory for each user.
tonyjsan said:
If I drop back to 4.1.1 will I have the same problem with not being able to access cache, data etc. in twrp or cwm, will it be encrypted ?
I'm also wondering dropping back to 4.1.1 will the 4.2.1 multi-user stuff mess with the downgrade, appears to be using sym links to create separate directory for each user.
Click to expand...
Click to collapse
Hello I have 4.1.1 It is unlocked. I have flashed the CWM and when I boot into recovery I only see the sd card and will not let me rrot via the zip either. I get an error in CWM saying that root persmissions need to be fixed. I have tried to fix then not to fix. Still nothing.
Not sure if this is inline with what everyone else is seeing.
ASUS did push from .17 to .20 the other day.
This is a fishing trip. 4.2 is multi-user, for multi-user to work the tablet has to be encrypted or users could access each others space. I don't have 4.2 so I can't test. If multi-user is deactivated encryption is not necessary. If multi-user is turned off can you find a setting to unencrypt?
It seems I remember someone unencrypting with twrp or fastboot but it took three tries, multi-user would still need to be off. This is not a suggestion just my thoughts.
My version of fastboot does not list unencrypt as an option.
Holy cow I now have cm 10.1, root, and hdmi out problem fixed. After lots digging to be sure I did not screw the tablet up here is what I did.
1) Downgrade to US_10.4.2.20, using fastboot and blob from asus web site.
2) after rebooting I had the previous boot-loader screen (in which usb icon shows), I re-installed recovery twrp2.
3) I did not even bother to boot into 10.4.2.20, went straight to recovery and I had access to cache, data, sdcard etc...
4) adb pushed the cm 10.1 zip to the sdcard and the gapps zip as well.
5) flash cm 10.1 then gapps
6) reboot and all is well.
There is one word of caution, not sure what happen but do not use the usb port on the keyboard dock with cm 10.1, it zapped a usb jump drive and a 500 gb portable drive , still looking into if I can recovery the drive and what caused it.
I's so glad I'm on CM 10.1 tablet running faster just seems to perform better.
I have also had this issue and managed to come back from it.
In doing some testing of the new ota update 4.2.1 (10.6.1.8) I have found that this issue is a direct result of the new 4.2.1 bootloader, it will not work with any custom recovery. twrp will give password prompt and be unable to mount anything but possible system, same goes for cwm minus the password prompt.
After doing a full wipe from twrp and then flashing just the new 4.2.1 bootloader, I rebooted back into twrp and it's encrypted, can't mount anything.
This method will not work if you cannot flash from fastboot successfully. In fact if you have attempted any other way to fix it may not work.
After I rebooted twrp to find it was encrypted the first thing I did was to reboot into fastboot mode and did the following:
flashed the 4.2.1 stock recovery, I have uploaded to here
Copy the "stock.blob" file to your android-sdk\platform-tools folder.
Also download the "US_epaduser_10_4_2_20_UpdateLauncher.zip" from the Asus website and unzip,
In the unzipped folder you will then have another zip file "US_epad-user-10.4.2.20.zip" unzip this also and now in that unzipped folder you will have a "blob" file, copy this to your android-sdk\platform-tools folder.
Boot into fastboot and check your pc can see your device:
open a command prompt and cd to your platform-tools directory.
Code:
fastboot devices
This should return your device serial, if not then fastboot is not setup correctly.
Next:
Code:
fastboot -i 0x0b05 flash recovery stock.blob
fastboot -i 0x0b05 reboot
Boot back into fastboot:
Code:
fastboot -i 0x0b05 flash system blob
fastboot -i 0x0b05 reboot
The system blob will take some time 10min or so to flash, so just give it some time then issue the reboot command.
Also first reboot after system blob flash will take some time, you will see a progress bar under the Asus logo.
Once your tablet has fully loaded you can now boot back into fastboot and flash a custom recovery & flash custom rom again.
I do suggest skipping the 4.2.1 update for now until this issue has been fixed.
As I have said this may not work for everyone depending on if you have attempted any other commands via fastboot or adb.
This has worked for me twice now but try at own risk.
pjc21 said:
I have also had this issue and managed to come back from it.
In doing some testing of the new ota update 4.2.1 (10.6.1.8) I have found that this issue is a direct result of the new 4.2.1 bootloader, it will not work with any custom recovery. twrp will give password prompt and be unable to mount anything but possible system, same goes for cwm minus the password prompt.
After doing a full wipe from twrp and then flashing just the new 4.2.1 bootloader, I rebooted back into twrp and it's encrypted, can't mount anything.
This method will not work if you cannot flash from fastboot successfully. In fact if you have attempted any other way to fix it may not work.
After I rebooted twrp to find it was encrypted the first thing I did was to reboot into fastboot mode and did the following:
flashed the 4.2.1 stock recovery, I have uploaded to here
Copy the "stock.blob" file to your android-sdk\platform-tools folder.
Also download the "US_epaduser_10_4_2_20_UpdateLauncher.zip" from the Asus website and unzip,
In the unzipped folder you will then have another zip file "US_epad-user-10.4.2.20.zip" unzip this also and now in that unzipped folder you will have a "blob" file, copy this to your android-sdk\platform-tools folder.
Boot into fastboot and check your pc can see your device:
open a command prompt and cd to your platform-tools directory.
Code:
fastboot devices
This should return your device serial, if not then fastboot is not setup correctly.
Next:
Code:
fastboot -i 0x0b05 flash recovery stock.blob
fastboot -i 0x0b05 reboot
Boot back into fastboot:
Code:
fastboot -i 0x0b05 flash system blob
fastboot -i 0x0b05 reboot
The system blob will take some time 10min or so to flash, so just give it some time then issue the reboot command.
Also first reboot after system blob flash will take some time, you will see a progress bar under the Asus logo.
Once your tablet has fully loaded you can now boot back into fastboot and flash a custom recovery & flash custom rom again.
I do suggest skipping the 4.2.1 update for now until this issue has been fixed.
As I have said this may not work for everyone depending on if you have attempted any other commands via fastboot or adb.
This has worked for me twice now but try at own risk.
Click to expand...
Click to collapse
Question: You said you reflashed the stock bootloader. I had gotten my tf300 couple days ago but went through the ota update not thinking of issues if wanted to root so I'm not rooted totally stock on 4.2.1but if possible would like to flash back to stock locked bootloader if possible. After reading all the issues with trying to flash custom recovery and root after ota figured I'd just wait till some of the issues are figured out. I'm new to this device but have rooted many other android phones in the passed so not a total noob just learning about this one been reading alot. Just wondering if there were a way to do so for future updates as i read you lose ota capability if unlocked. Thanks
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
aerdely said:
Question: You said you reflashed the stock bootloader. I had gotten my tf300 couple days ago but went through the ota update not thinking of issues if wanted to root so I'm not rooted totally stock on 4.2.1but if possible would like to flash back to stock locked bootloader if possible. After reading all the issues with trying to flash custom recovery and root after ota figured I'd just wait till some of the issues are figured out. I'm new to this device but have rooted many other android phones in the passed so not a total noob just learning about this one been reading alot. Just wondering if there were a way to do so for future updates as i read you lose ota capability if unlocked. Thanks
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
This approach recovered the tablet.
As long as the bootloader is working - it is probably fixable.
Here is how I got it to work:
-preloaded my ROM and Gapps on the SD card
-flashed stock system blob (for the right region) from the ASUS website
-let the stock ROM reboot
-it hangs - but will be visible from ADB
-reboot to fastboot
-install TWRP or CWM from fastboot
-reboot recovery
-then flash ROM + Gapps
There has to be something in the new OTA bootloader or OTA system that
locks down the partitions.
xbill9 said:
This approach recovered the tablet.
As long as the bootloader is working - it is probably fixable.
Here is how I got it to work:
-preloaded my ROM and Gapps on the SD card
-flashed stock system blob (for the right region) from the ASUS website
-let the stock ROM reboot
-it hangs - but will be visible from ADB
-reboot to fastboot
-install TWRP or CWM from fastboot
-reboot recovery
-then flash ROM + Gapps
There has to be something in the new OTA bootloader or OTA system that
locks down the partitions.
Click to expand...
Click to collapse
Yea should of mentioned im not rooted haven't done that yet as if you are on the 4.2.1 ota you can't without issues. Device works fine I'm on stock recovery and firmware but just an unlocked bootloader and just little worried because some have mention can lose any future ota's if thats not the case than i guess no issue at all but not sure on that and was just looking for a way to either relock the bootloader or reflash it. Probably isn't at the moment but some have been asking about this because of issues with the ota.
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
I have had my TF700 for a while, and merrily went from ICS through the various OTA upgrades to 4.2.1
I have attempted to follow along the "All in One Guide" in order to get Rooted so I can install Cyanogenmod or alternative to get rid of the crapware delivered by Asus. But I seem to get stuck when trying to "Flash" anything. Or at least I think so.
I unlocked the bootloader using the apk provided by Asus. Bootloader shows as unlocked when booting.
adb devices shows my device attached. When booted into fastboot mode fastboot devices shows my device attached.
I have also done a complete data wipe, not that that should matter.
1st, I have tried to install twrp using GooManager, and the fastboot method. Using GooManager, the file downloads and then nothing seems to happen. GooManager will also not reboot to recovery. Using the Fastboot method I get "error: cannot load 'twrp.blob': No error". I have downloaded the file multiple times and it does not appear to be corrupted.
I have tried to roll back to ICS by downloading the correct firmware, renaming it and copying to my SDCard, then booting into recovery. US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip I only get the Android guy with the red triangle until it reboots.
I have also tried http://forum.xda-developers.com/showthread.php?t=1929712 but this does nothing as twrp is not installed and the regular recovery doesn't do anything.
What should I try next? It would seem like I'm missing something obvious.
When you download firmware from Asus, the file you need to put on your SDCard is not the file you downloaded, but the zip file contained within. Its a zip in a zip. Extract the file you downloaded and you will find another zip file inside and that's the one you rename and copy to your SDCard. Also make sure your SDCard is formatted FAT32. exFAT will not work and is the default Sandisk format.
Got rolled back to ICS but..
I successfully rolled back to ICS .30
Now adb fails to recognize the device. Previously it did recognize. I reinstalled the drivers in fastboot mode and "normal" mode. I have tried the universal naked drivers and the Asus drivers. fastboot reboot will successfully reboot the device, but nothing shows up when I do a adb devices or fastboot devices.
fastboot -i 0x0B05 flash recovery twrp.blob Gets the same error, error: cannot load 'twrp.blob': No error.
When I run through *** Rooting Your TF700 with Debugfs automated root *** I get the error "You must install device specific drivers...."
Fixed
Adhar said:
I successfully rolled back to ICS .30
Now adb fails to recognize the device. Previously it did recognize. I reinstalled the drivers in fastboot mode and "normal" mode. I have tried the universal naked drivers and the Asus drivers. fastboot reboot will successfully reboot the device, but nothing shows up when I do a adb devices or fastboot devices.
fastboot -i 0x0B05 flash recovery twrp.blob Gets the same error, error: cannot load 'twrp.blob': No error.
When I run through *** Rooting Your TF700 with Debugfs automated root *** I get the error "You must install device specific drivers...."
Click to expand...
Click to collapse
I discovered that I couldn't install twrp as I was in the wrong folder when executing the command. I needed to cd to the folder that contained the .blob file. Then it was trivial to use twrp to flash the root.zip file and gain root, and then flash cyanogenmod 10.0, wipe, and then reboot.
Everything is fine, now downloading Google apps.
Adhar said:
I discovered that I couldn't install twrp as I was in the wrong folder when executing the command. I needed to cd to the folder that contained the .blob file. Then it was trivial to use twrp to flash the root.zip file and gain root, and then flash cyanogenmod 10.0, wipe, and then reboot.
Everything is fine, now downloading Google apps.
Click to expand...
Click to collapse
When I read "seems like I'm missing something obvious" from your original post I went back and re-read it looking for the obvious. It wasn't immediately apparent what was wrong. If you hadn't posted the name of the firmware file it wouldn't have been obvious to me either but I thought I recognized it as the downloaded not the internal zip file name and verified it with my downloaded firmware. Glad to help and that you got it all worked out.