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
Related
When I hold the power button plus Volume down key I am only getting two options. One is to wipe data and the other is to enter USB Fastboot mode. I just upgraded to the latest TWRP recovery and when I click the Wipe icon the TWRP splash screen shows up for a second. What I am hoping is that someone has some insight as to why the recovery icon has disappeared and how to get it back. Usually I am not the person asking the questions generally I am the one answering. If anyone has a clue it would definitively help. I did search and found a couple threads where something similar happened but there was no direct answer as how to fix it. Please help.
stedrocklp said:
When I hold the power button plus Volume down key I am only getting two options. One is to wipe data and the other is to enter USB Fastboot mode. I just upgraded to the latest TWRP recovery and when I click the Wipe icon the TWRP splash screen shows up for a second. What I am hoping is that someone has some insight as to why the recovery icon has disappeared and how to get it back. Usually I am not the person asking the questions generally I am the one answering. If anyone has a clue it would definitively help. I did search and found a couple threads where something similar happened but there was no direct answer as how to fix it. Please help.
Click to expand...
Click to collapse
I had a similar issue when I restored a TWRP backup I made with pre version 2.2.1. I was able to get help from the Dees_Troy on IRC.
Notes from IRC conversation
Whatever you restored from your pre TWRP 2.2.1 old backup is not a kernel. The dev that made the original device configuration files for the 300 couldn't find boot . So he just threw boot onto the wrong partition you need to install a working kernel via fastboot.
Steps that got me backup and running.
1. Flashed latest TWRP via fastboot. 'fastboot -i 0x0B05 flash recovery twrp.blob' rebooted
2. Downloaded a cm9 rom and opened the zip file and extract boot.blob . Flashed with 'fastboot -i 0x0B05 flash boot boot.blob' then rebooted.
Now TWRP recovery worked and I was able to install a new custom rom.
Backups made with version 2.2.1 or grater work correctly for me now.
Thank you Thank you Thank you!
brbjr said:
I had a similar issue when I restored a TWRP backup I made with pre version 2.2.1. I was able to get help from the Dees_Troy on IRC.
Notes from IRC conversation
Whatever you restored from your pre TWRP 2.2.1 old backup is not a kernel. The dev that made the original device configuration files for the 300 couldn't find boot . So he just threw boot onto the wrong partition you need to install a working kernel via fastboot.
Steps that got me backup and running.
1. Flashed latest TWRP via fastboot. 'fastboot -i 0x0B05 flash recovery twrp.blob' rebooted
2. Downloaded a cm9 rom and opened the zip file and extract boot.blob . Flashed with 'fastboot -i 0x0B05 flash boot boot.blob' then rebooted.
Now TWRP recovery worked and I was able to install a new custom rom.
Backups made with version 2.2.1 or grater work correctly for me now.
Click to expand...
Click to collapse
That was definitely the problem and I had been trying everything for the past two days. I appreciate you taking the time to reply.
asus tf300 help
brbjr said:
I had a similar issue when I restored a TWRP backup I made with pre version 2.2.1. I was able to get help from the Dees_Troy on IRC.
Notes from IRC conversation
Whatever you restored from your pre TWRP 2.2.1 old backup is not a kernel. The dev that made the original device configuration files for the 300 couldn't find boot . So he just threw boot onto the wrong partition you need to install a working kernel via fastboot.
Steps that got me backup and running.
1. Flashed latest TWRP via fastboot. 'fastboot -i 0x0B05 flash recovery twrp.blob' rebooted
2. Downloaded a cm9 rom and opened the zip file and extract boot.blob . Flashed with 'fastboot -i 0x0B05 flash boot boot.blob' then rebooted.
Now TWRP recovery worked and I was able to install a new custom rom.
Backups made with version 2.2.1 or grater work correctly for me now.
Click to expand...
Click to collapse
hey Im sry I never posted here b4 but I think this thread is the closest to the problem I have. My tf300 jad 4.1.1 ota update, i decided to change the rom since it seemed to have so many advantages. I installed TWRP correctly and according to the process I made later with debugfs tool I got root. It was all good but then I messed up, I installed Hydroponyc rom without backing up my rom and from then on, all hell broke loose. I can acces Clockworck (I changed TWRP for clock thought it might help......) and fastboot but any rom I install it doesnt go past the first asus logo that says device is unlocked on the upper left of the screen. Is there anyway u could help me please? Forgive my noobness I never posted here b4 I dont know if Im breaking any rule but i dont wanna wind up with a very expensive paper weight.
Did I brick it?
manegonzalez said:
hey Im sry I never posted here b4 but I think this thread is the closest to the problem I have. My tf300 jad 4.1.1 ota update, i decided to change the rom since it seemed to have so many advantages. I installed TWRP correctly and according to the process I made later with debugfs tool I got root. It was all good but then I messed up, I installed Hydroponyc rom without backing up my rom and from then on, all hell broke loose. I can acces Clockworck (I changed TWRP for clock thought it might help......) and fastboot but any rom I install it doesnt go past the first asus logo that says device is unlocked on the upper left of the screen. Is there anyway u could help me please? Forgive my noobness I never posted here b4 I dont know if Im breaking any rule but i dont wanna wind up with a very expensive paper weight.
Click to expand...
Click to collapse
I kinda have the same problem! Tried the boot.blob thing but, sadly, that didn't work for me ;(
solution
mizifih said:
I kinda have the same problem! Tried the boot.blob thing but, sadly, that didn't work for me ;(
Click to expand...
Click to collapse
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
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.
manegonzalez said:
hey Im sry I never posted here b4 but I think this thread is the closest to the problem I have. My tf300 jad 4.1.1 ota update, i decided to change the rom since it seemed to have so many advantages. I installed TWRP correctly and according to the process I made later with debugfs tool I got root. It was all good but then I messed up, I installed Hydroponyc rom without backing up my rom and from then on, all hell broke loose. I can acces Clockworck (I changed TWRP for clock thought it might help......) and fastboot but any rom I install it doesnt go past the first asus logo that says device is unlocked on the upper left of the screen. Is there anyway u could help me please? Forgive my noobness I never posted here b4 I dont know if Im breaking any rule but i dont wanna wind up with a very expensive paper weight.
Click to expand...
Click to collapse
you can flash the file named "blob" extracted from stock JB zip file(download from ASUS website,now there is only US SKU,10.4.2.29),it's about 7XX MB,then use the command "fastboot -i 0x0B05 flash system blob" (put the blob in the same directory with fashboot),It will restore your JB OS.till now,other rom can not work by this way.
jijitax4 said:
you can flash the file named "blob" extracted from stock JB zip file(download from ASUS website,now there is only US SKU,10.4.2.29),it's about 7XX MB,then use the command "fastboot -i 0x0B05 flash system blob" (put the blob in the same directory with fashboot),It will restore your JB OS.till now,other rom can not work by this way.
Click to expand...
Click to collapse
What if you can only boot to APX mode? I only have the option of using that because my unlocked bootloader got erased in the process of updating to JB. Is there a way to install a bootloader using fastboot? Or will it only work with an existing bootloader?
In other words, when I issue the fastboot command
fastboot -i 0x0B05 flash system blob
I get "waiting on device" and nothing happens after that.
Thank you, this worked !!!!!!
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
sorry for my poor english:crying:
i hope you can understand what i need help
my TF300T OTA updated 4.2.1
tonight i unlocked my TF300T and flashed CWMV6.0.2.3
but the recovery can't mount all choice in "mounts and storage"
then i see this"http://forum.xda-developers.com/showthread.php?t=2206996"
he said"FIXED!!! Did a wipe....in the fastboot screen (not in recovery since it didn't work)And now the internal sd is visible and mounted, so next step flashed supersu......aaaaaaand i'm done "
then i do the same
a wipe in fastboot screen
and now i can't enter fastboot screen (no matter have/not press volumedown+power）
it can only enter recovery but do nothing becasue recovery can‘t mount everything
i have no confidence you will understand my english...
are there other ways enter fastboot？how can i revive it only can use recovery？
many thanks
May i ask another question for help
i did the wipe data in bootloader once
now in recovery mode /adb devices can get it
but in bootloader /fastboot devices can't connect my device now
so i can't flash The official firmware use /fastboot -i 0x0b05 flash system blob
are there anyway to fix it？
thanks verymuch
i have the same problem. only i flasher the latest twrp recovery. TWRP 2.4.4.0 Touch Recovery
First, CWM 6.0.2.3 is not compatible with Asus 4.2.1, you should have done a little bit of reading and you would have found this very useful thread http://forum.xda-developers.com/showthread.php?t=2187982 where it explains everything you can possibly know and need about upgrading and flashing recovery and gain root. on 4.2.1
Both of you guys have flashed incompatible recovery versions for your bootloaders and now are stuck, try to access Fastboot, keep trying update your drivers and also check several USB ports because fastboot is your only choice now.
Erik
ricco333 said:
First, CWM 6.0.2.3 is not compatible with Asus 4.2.1, you should have done a little bit of reading and you would have found this very useful thread http://forum.xda-developers.com/showthread.php?t=2187982 where it explains everything you can possibly know and need about upgrading and flashing recovery and gain root. on 4.2.1
Both of you guys have flashed incompatible recovery versions for your bootloaders and now are stuck, try to access Fastboot, keep trying update your drivers and also check several USB ports because fastboot is your only choice now.
Erik
Click to expand...
Click to collapse
thanks Erik,thanks for your reply
May i ask another question for help
i did the wipe data in bootloader once
now in recovery mode /adb devices can get it and replied ”0123456789ABCDEF recovery“（but this is not my S/N number）
but in bootloader /fastboot devices can't connect my device now
so i can't flash the official firmware use /fastboot -i 0x0b05 flash system blob
are there anyway to fix it？
thanks verymuch
Hi all,
I'm a total noob here. Somehow I managed to unlock and root my ASUS TF300T successfully, even though the instructions I was referring to were sketchy. Unfortunately I started the process before finding the detailed instructions here on how to flash the ROM. So it looks like I misinterpreted the sketchy instructions and hosed up the process. I managed to get the Katkiss zip file on the internal SD of the tablet, but when I tried to install it, it failed.
I now know where I went wrong so I'm not sure if it's fixable now: Rather than wipe while in TWRP, I wiped from the main bootloader screen (RCK, Android, WIPE DATA). Idiotic noob mistake which I realize now, but too late.
Currently when I attempt to boot up using the power + down volume, my screen shows:
Code:
Key driver not found.. booting OS
Android cardhu-user bootloader <1.00 e> released by "US-epad-10.6.1.27.5-20130902" A03
If I select RCK, I can get to TWRP, but it can't find a way to push the stock ROM file from ASUS from my PC back to the tablet. I tried using ADB push, but I get an error that it's not a valid command.
I can see the tablet in Device manager if I connect using the USB, but when I use the ADB devices command, nothing is returned - no error message, no device information.
Any thoughts on how whether it's possible to get back to the stock ROM? It shows
Code:
The Device is Unlocked.
on the ASUS splash screen but always boots to TWRP if I do not hold the down-volume button when starting up. I'm not sure if it's still rooted.
Thanks in advance for any suggestions!
I would like to advise you to get back on stock rom without any further experiments.
First of all the USB driver must be installed on your PC.
-Download “Minimal ADB and Fastboot”.
-Make a folder C:/Fastboot and extract it there and install it. Download the latest firmware V10.6.1.27.5 fitting to your device from the ASUS official website and unzip it twice.
-Copy the .blob file into the folder C:/Fastboot.
-Start “Minimal ADB and Fastboot” and put in "fastboot devices". The device should appear as "xxx device".
Now type in step by step (wait after every step!):
fastboot erase system
fastboot erase recovery
Fastboot erase user data
fastboot erase boot
fastboot erase misc
fastboot erase cache.
After that put in "fastboot -i 0x0B05 flash system blob" without " " .
Now it takes a while "sending..." appears then "write..." and the load status will be shown.
If loading is finished put in "fastboot -i 0x0B05 reboot". It takes a while to start into a clean JB 4.2.2!
After that you are ready to flash Kang TWRP 2.8.7.2 again and make a clean install of a custom rom of your choice by taking care exactly of the instruction given by Timduru in each post #1 of each CR.
Thank you for your reply, ebonit. It looks like I have an older version of TWRP currently installed: v2.5.0.0. Is that a problem? If I'm going to flash TWRP again, should I definitely overwrite the current install with Kang TWRP 2.8.7.2?
Thanks again. I may have additional questions because I'm totally new to this and there's so much information out there. I appreciate your patience!
RedSkies said:
Thank you for your reply, ebonit. It looks like I have an older version of TWRP currently installed: v2.5.0.0. Is that a problem? If I'm going to flash TWRP again, should I definitely overwrite the current install with Kang TWRP 2.8.7.2?
Thanks again. I may have additional questions because I'm totally new to this and there's so much information out there. I appreciate your patience!
Click to expand...
Click to collapse
For all MM 6.0.1 and N 7.1.0 versions you need Kang TWRP 2.8.7.2. That's mandatory as seen in each post #1.
If you get back on stock rom, you don't have any custom recovery remaining. There is nothing to overwrite. You must flash Kang TWRP anyway. After that you may flash any custom rom of your choice as clean install.
Thank you so much for your help. It looks like I'm back to the stock ROM. I will try flashing Katkiss later when I can give it my full attention and am less likely to make stupid errors!
RedSkies said:
Thank you so much for your help. It looks like I'm back to the stock ROM. I will try flashing Katkiss later when I can give it my full attention and am less likely to make stupid errors!
Click to expand...
Click to collapse
I cannot stress this enough. MAKE AN NVFLASH BACKUP ASAP!!!! I bricked my device 2-3 years ago and had I made an NVFlash backup I could have recovered it. Unfortunately I did not have a backup and so I just had the tablet sit on my shelf until a few days ago when I finally got a replacement motherboard and swapped the bricked one out. Again MAKE AN NVFLASH BACKUP. You can use the flatline utility described in one of the threads in this device's forum here on XDA.
Sent from my Nexus 6 using XDA-Developers mobile app
Can someone give me more detailed help MM 6.01?
ebonit said:
For all MM 6.0.1 and N 7.1.0 versions you need Kang TWRP 2.8.7.2. That's mandatory as seen in each post #1.
If you get back on stock rom, you don't have any custom recovery remaining. There is nothing to overwrite. You must flash Kang TWRP anyway. After that you may flash any custom rom of your choice as clean install.
Click to expand...
Click to collapse
Ebonit, this is what I need to know, all underlined.
Can anyone give me complete step by step instructions on how to install MM 6.01 on my TF300t. It's so slow it's annoying and unusable. I am a newbie and don't understand how to flash this and flash that and do several other steps... more detailed instructions for each step below would be so helpful. I would be more than happy to make a payment donation for more detailed help.. thanks! Cindy
Install KANG TWRP Recovery
Backup everything !
Boot into the recovery
Click to expand...
Click to collapse
The first time or everytime you have an issue when dirty flashing (Especially when changing android versions):
do a full wipe , if you have issues make sure that you format /data (format is different than wipe)
Warning: formatting will remove what is stored in your internal storage, so store the rom /gapps/supersu zips onto an external storage (microSD, SD card..) or make sure you know how to push them back through adb.
Change /data filesystem to f2fs
Then everytime (even when "dirty flashing") do the following steps:
Flash the rom
Flash the SuperSU zip
Flash gapps
Wipe cache/dalvik
Reboot
What do you want? Every information you need is written in your post. Any further questions you may have will be find an answer somewhere in the forum.
Kang TWRP is the most important tool. It will do the job. Do you have it?
If not, look here http://forum.xda-developers.com/transformer-tf300t/development/recovery-twrp-t3046479. There is the install instruction as well.
If yes, then start into recovery and and realize step by step what you found in post #1 and is written down by yourself in your post itself.
Hello everyone,
I have accidentally messed up a TF700 device that my grandma received from a friend. Now I am stuck in a loop, when the device boots up directly into recovery. In recovery, I can connect with adb and reboot to bootloader with fastboot mode, where I see the three icons and I can connect with fastboot, I can even boot the stock ROM, which works fine now, because /data has been wiped.
I have been looking for recovery blob on Asus website, but it looks like Asus has totally cut off the device support, I can not find anything.
Because I have been doing lots of nasty things to the tablet, by following a guide for flashing the TF201 (long story including wrong model name on the device sticker ) the easiest solution is probably to flash the original recovery, bootloader and ROM. Does anyone has by accident the recovery blob for Bootloader 1.00e ww_epad-10.6.1.14.10-20130801 a03 ?
Or is there any other solution for the loop? The problem is that in the recovery, I can not do almost anything, no partition can be mounted, I have probably flashed recovery for TF201.
Thank you.
Yes, best would be if you reflash the Asus firmware, then start from scratch.
Geab the zip here https://www.androidfilehost.com/?fid=817550096634791660
Extract it until you see the system blob (called simply "blob"), move it to your fastboot directory and flash it in fastboot:
fastboot flash system blob
Reboot
That returns you to a stock system.
Then flash the latest TWRP, format /data, then flash your Katkiss rom of choice
Good luck
Sent from my Pixel 2 using Tapatalk
This is awesome, thank you for such quick reply. Just one more question, is it OK to flash US recovery if there is WW version bootloader? Just to be sure not to scew it even more
Yes, flash away. The bootloader is the same for WW and US, just some wifi modules are different, I think.
That firmware is US anyway and it includes the bootloader, so you'll have a US BL afterwards
Sent from my Pixel 2 using Tapatalk
OK, sounds good then
I have tried downloading the archive now several times and no matter what program I use for unpacking, I always get error. May I ask you please to verify that the file is alright?
hornmich19 said:
OK, sounds good then
I have tried downloading the archive now several times and no matter what program I use for unpacking, I always get error. May I ask you please to verify that the file is alright?
Click to expand...
Click to collapse
Works fine for me. Downloaded it and it opened without problem. Try this link, uploaded the same file here: https://www.dropbox.com/s/tz1lcspqayhs7ug/US_epad-user-10.6.1.14.10.zip?dl=0
No I just can not extract it
7-zip, winrar, gzip tried and I always get CRC error. I can however open it to see what files are inside, but not extract the blob to flash it. So maybe there was a little misunderstanding.
So Good news (partially), I have managed to find on the Internet similar package with WW. Extracted the blob and flashed to system partition. But nothing has changed, it is still booting right to recovery (FlatLine CWM)
Strange thing is, in recovery, I can not mount any partition.
Another strange thing is that in the fastboot mode, there is no blue progress bar as it used to be before I damaged it. Also it does not respond to any reboot commands. I have to do hard reset.
Any idea to try out, please?
Mhhh, maybe you have to go the super clean route.
Run these commands one after the other, letting every single one finish. Some are very fast, some take a bit longer
fastboot erase misc
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot flash system blob
fastboot reboot
If it hangs at any of the commands (30 min or more does not return to prompt) just reboot with the buttons and continue with the next command.
Good luck
Awesome, I have some progress here, thanks to you. After formating the other partitions, the fastboot screen finally started to react and the blue progressbar appeared and the blob has been flashed.
After that, I have rebooted the tablet and it was stuck on the ASUS splash screen. When I rebooted to fastboot again, and tried recovery, I got Dead Android image instead. So there was no recovery image on the partition. When I tried to select cold boot to Android, I gets stuck again. So I have at least flashed TWRP recovery back again and I can boot to that recovery.
Also it looks like, despite of what was the archive name, I have now US bootloader and not WW anymore
So how to ged rid of the ASUS splash screen now? I suspect there is no kernel and RAMdisk on the boot partition now, since I have formated it, right?
I have tried flashing the JB kernel linked in the thread here https://forum.xda-developers.com/showthread.php?t=1919961 but without any result. However I am not 100% sure about the android version.
Or maybe this is a good time to flash completely different ROM?
Ok, step-by-step...
Strange though that it did not boot after flashing the blob... hope you do not have something else going on.
The Asus blob contains everything: Every partition is reflashed with stock software so everything should be in place. The dead Android is the stock recovery showing that it cannot find anything to flash. That is perfectly normal and healthy.
Yes, do not try to piece the system together, flash a full rom now (after formatting /data in TWRP).
https://forum.xda-developers.com/tr.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
I would recommend one of the KatKiss roms, the latest is here:
https://forum.xda-developers.com/transformer-tf700/development/rom-t3457417
Hello and sorry for not replying long. The baby at home was sick so I didn't have time to play with the tablet.
I have flashed the ROM you linked and the tablet finally is booting and working :victory: Or so far it looks like that
Thank you so much for your asistance here, I learned a lot on this journey.
For whatever it is worth, I just had a sudden occurrence of a similar problem. Im still using this tablet on an almost daily basis and one day it started a boot loop. When I tried the RCK it would show TWRP and then bootloop again. Followed the 'simple clean' steps and reflashed twrp and clean version of KatKiss and now good to go! Thanks @berndblb for the refresher course in fastboot commands.....