Related
Hi all,
This may sound like an old problem but believe me, it's not. Let me explain.
I've rooted my Transformer TF101G (B90) last year sometime on 3.2.1. This works fine with no issues. I've flashed ClockworkMod after installing ROM Manager. This worked fine, I can boot normally, I can boot to recovery, no problem.
With the latest update available from ASUS via the web, I decided to to allow the annoying icon complaining about upgrading to download and run the upgrade. After downloading the update the Pad rebooted so if to install the new update. This landed me on the CWM with an error message that stated the verification (or something failed). After this, the Transformer wouldn't boot directly to Android, but ended up booting to the recovery partition every time. I had to use the fastboot option to "cold boot" into Android.
This was annoying, so I googled and found the solution on this forum to fix the issue with 5.5.0.4 that kept rebooting to recovery. This solved that problem and I was still able to boot to recovery whenever required.
I decided to update CWM to version 5.8.2.1 via ROM Manager. This seemed to work via ROM Manager, but restarting the transformer and going to recovery showed version 5.5.0.4 still. So I went back to ROM Manager and it showed that it was upgraded to 5.8.2.1. I decided to update this to ClockworkMod Touch by purchasing it via Google market to support the guys that do development on it. This claimed to install also. "Reboot into Recovery" from ROM Manager still showed version 5.5.0.4.
I was now very confused.
So I decided to downgrade CWM from the 5.8.2.1 version it stated was installed to version 5.8.1.9. This worked according to ROM Manager, but rebooting into recovery still showed 5.5.0.4. I mean, WTF!
In the meanwhile the freeken update icon on the task tray still complained about updating Android. I allowed it again to try and update. At the point it rebooted it left me stuck on the "EEE Pad" screen.
Booting up with Vol - and Power takes me to the screen that gives you an option to press Vol + to boot to RCK. Doing so the Pad freezes at "Booting Recovery Kernel Image". My PC then detects USB ADB interface but any adb commands respond with "error: device offline" or "error: device not found".
Booting up with Vol + and Power leaves the screen blank. My PC then detects an USB APX interface. Using "fastboot -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img" only responds with "waiting for device".
The only way to boot my tablet at the moment is to use the "cold boot" option.
I would like to think I've tried everything out there and would appreciated anybody that could point me to maybe something else I could try.
PS: In ROM Manager I get "An error occurred while attempting to run privileged commands" when I use the "Fix Permissions" option.
PeekNPoke said:
PS: In ROM Manager I get "An error occurred while attempting to run privileged commands" when I use the "Fix Permissions" option.
Click to expand...
Click to collapse
Fixed the privileged error by installing Busybox, but still unable to boot to recovery even when reinstalling CWM with the "Erase Recovery" option ticked.
PeekNPoke said:
Fixed the privileged error by installing Busybox, but still unable to boot to recovery even when reinstalling CWM with the "Erase Recovery" option ticked.
Click to expand...
Click to collapse
I had the same problem. It seems the 5.5.0.4 or whatever recovery has borked the transformer. First, I was just in a recovery loop and when I followed how to get out of it, I have no recovery at all now it seems. I need to find a recovery.img and fastboot to manually install it but I can't find a recovery.img that is current.
dragon_76 said:
I had the same problem. It seems the 5.5.0.4 or whatever recovery has borked the transformer. First, I was just in a recovery loop and when I followed how to get out of it, I have no recovery at all now it seems. I need to find a recovery.img and fastboot to manually install it but I can't find a recovery.img that is current.
Click to expand...
Click to collapse
I can't get fastboot to work either. I though I might reinstall ClockworkMod via
fastboot.exe -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img
but it never connects.
Is there no tool that could be used from the adb shell that could re-flash ClockworkMod or even the original recovery (if that is available somewhere)?
PeekNPoke said:
I can't get fastboot to work either. I though I might reinstall ClockworkMod via
fastboot.exe -i 0x0b05 flash recovery recovery-clockwork-touch-5.8.2.1-tf101.img
but it never connects.
Is there no tool that could be used from the adb shell that could re-flash ClockworkMod or even the original recovery (if that is available somewhere)?
Click to expand...
Click to collapse
Same problem here(tf101g): tried to update to ics.... stuck on cwm 5.5.0.4
Resolved problem using: echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Now i can't access to cwm, even if i update to the last cwm touch....paying...any idea?
recovery
Sorry for my bad english,
I think I have the solution
First invites you down the driver and the nvflsh see appendix are the drivers are too large as a single file
2 go into the apx and the modern transformer connected to the PC
Third drivers instalation
4 instalation nvflasch
then you have a new recovery
This worked for me
ps I have a B60
mmarco80 said:
Same problem here(tf101g): tried to update to ics.... stuck on cwm 5.5.0.4
Resolved problem using: echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Now i can't access to cwm, even if i update to the last cwm touch....paying...any idea?
Click to expand...
Click to collapse
I've solved The problem whit the gnufabio toolsto install recovery. Then Used "reboot to recovery"
Now i've manually installed official ics ....work fine!
Thomas Cardif said:
Sorry for my bad english,
I think I have the solution
First invites you down the driver and the nvflsh see appendix are the drivers are too large as a single file
2 go into the apx and the modern transformer connected to the PC
Third drivers instalation
4 instalation nvflasch
then you have a new recovery
This worked for me
ps I have a B60
Click to expand...
Click to collapse
I tried this combined with the instructions on android.modaco.com/topic/335416-nvflash-setup-instructions-drivers-links-active because I'd never used nvflash before.
I managed to boot my TF101 in APX-mode, but as soon as I do any nvflash-command (e.g. nvflash --sync) the connection to the TF is lost:
C:\Program Files (x86)\nvflash>nvflash --sync
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
Click to expand...
Click to collapse
After that I have to reboot the TF and shut it down again to be able to go into APX-mode again.
What do I miss? Mine is a B80.
hans_zelf said:
What do I miss? Mine is a B80.
Click to expand...
Click to collapse
You can't use nvflash with a B80
baseballfanz said:
You can't use nvflash with a B80
Click to expand...
Click to collapse
Oops. Fastbook doesn't seem to work either. Any ideas?
Yeah, I can't get fastboot to work either. I still have root access on the device. Is it not possible to flash the recovery from to root prompt on the device?
I tried using ADB. That way I actually can access the device and copy the recovery.img to the device using:
adb push recovery.img /data/local/recovery.img
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock2 /system
# cd /system
# cat /data/local/recovery.img > recovery.img
# flash_image recovery recovery.img
Click to expand...
Click to collapse
Works out until the last step. Then I get a message sh: flash_image: not found. Am I missing some files I have to flash first or have I forgotten something else?
Success!
Finally I succeeded!
Flashed recovery using Gnufabio's RecoveryInstaller. (After that the TF101 rebooted itself but still got stuck at the splashscreen. Did a cold Linux-boot).
Opened an ADB-session:
C:\Program Files\...\platform-tools>adb shell
/ # su
/ # echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes transferred in 0.039 secs (128 bytes/sec)/ # exit
Click to expand...
Click to collapse
Finally, using ROM-manager I downgraded to CWM 5.5.0.4.
After that I was able to boot into recovery, but not from ROM-manager. I had to hold Vol- but at least I have a working recovery and was able to upgrade to ICS.
I'm not sure if the first step was really necessary but this is how I did it.
Hey hans_zelf,
Wow, I'm glad you got it going. I'll give it a go aswell and give feedback here. By the way, where did you get the recovery.img file you originally tried to flash?
Not really sure. I did a search within the forum and found several img's and zips.
But in the end I didn't need it because both RecoveryInstaller and ROM-manager download their own.
Ok,
I did the following:
adb shell
su
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
exit
Used ROM Manager v5.0.0.6, selected "Erase Recovery" in the settings menu, then flashed ClockworkMod 5.5.0.4, and powered down.
I then tried to start with Vol + and Power, just a blank screen but the 0955:7820 usb driver loaded. Then I used Vol - and Power, it booted to the Eee screen with the blue progress bar, after this is booted normally to the OS.
I powered it down again, and this time booted with Vol - and Power. Got to the screen that says use Vol + to load Recovery. I did that, and Bobs-Your-Uncle !!!!! IT WORKS !!!
Thanks hans_zelf, I'd still be stuck if it wasn't for you !
PS: I think the trick might have been to flash the 5.5.0.4 back, I'm not sure, and I'm not trying this again
You're welcome, but all I really did was combine some very helpfull tips from this forum
In the meantime I flashed my recovery to repacked Touch CWM v5.8.1.8 by Roach2010. Works like a charm. Not only touch support but also keyboard!
Thanks hans_zelf & PeekNPoke. Got my tf101 back into recovery mode from following what you guys said. I had this problem because I upgraded CWM in Rom Manager. Is that what happened to you guys? If so I think this should be stickied because if was a easy mistake and this is the only thread I could find that helped get my recovery back. Thanks again
Yep. Mine was also barked after I upgraded CWM from ROM-Manager.
mike0122 said:
Thanks hans_zelf & PeekNPoke. Got my tf101 back into recovery mode from following what you guys said. I had this problem because I upgraded CWM in Rom Manager. Is that what happened to you guys? If so I think this should be stickied because if was a easy mistake and this is the only thread I could find that helped get my recovery back. Thanks again
Click to expand...
Click to collapse
me too, i've solved whit gnufabio recovery
Today I felt ambitious and tried to install a new JB rom (AOSPA 4.2.2). The instructions said that if I had 3 icons I would be on JB bootloader and that I would need to upgrade to the latest TWRP 2.5.0.0 (I was on 2.4.4.0). Well, what I missed is the fact that there were two different versions of 2.5.0.0 (one specifically for JB 4.2) and of course I flashed to wrong one.
Now when the tablet boots it goes straight to recovery and asks for a PW (I don't know the password and never set one). I can select cancel which lets me into the main menu but none of the functions actually have write access. Nothing mounts or lets me gain access to the internal memory. When I try to reboot it immediately goes back to recovery, never letting me get back into fastboot to install the correct version.
Reading some forums and doing some other google search I don't find anyone with exactly the same problem, but it seems that I cannot get out of this mess. I know that nvflash is out of question since that is not working on JB yet.
If anyone has encountered a similar issue or knows how I could potentially get fastboot to trigger again so I can flash the correct version of recovery, that would be a great start.
Thanks !!
Have a look here
http://forum.xda-developers.com/showpost.php?p=42254642&postcount=10
pjc21 said:
Have a look here
http://forum.xda-developers.com/showpost.php?p=42254642&postcount=10
Click to expand...
Click to collapse
Great, That is exactly what happened. Looks like I'll be looking for a new tablet.
I am wondering if the Google Nexus 10 would have a similar risk of bricking. Guess it's time to do some research.
Thanks.
anosis said:
Great, That is exactly what happened. Looks like I'll be looking for a new tablet.
I am wondering if the Google Nexus 10 would have a similar risk of bricking. Guess it's time to do some research.
Thanks.
Click to expand...
Click to collapse
You may want to check & confirm that fastboot will not flash (you don't get the blue bar on tab when flashing) before looking for a new tab, although this "fastboot flash brick" issue results about 90% of the time you may be lucky and be in that 10% that does not.
You should be able to access fastboot using the "adb reboot-bootloader" command while in recovery, if pc does not pick-up device for adb in recovery have a look here and follow on from the device manager part.
When you get to the bootloader menu have a look at the text in the top left and confirm which 4.2 bootloader version your on, either 10.6.1.8 or 10.6.1.15.3 - then download the correct twrp version for that bootloader and see if you can flash it via fastboot.
If that does not work, which will most likely not would you like to try something for me? which may or may not work, just an idea.
Download this file, unzip it & copy the bootloader.bin file in your android-sdk/platform-tools folder.
Boot back to fastboot using the adb reboot-bootloader command and try
Code:
fastboot -i 0x0b05 flash bootloader bootloader.bin
If this works and does not freeze the tab then
Code:
fastboot reboot-bootloader
If the tab does reboot to this command then check the bootloader version here in the bootloader menu and if it has worked it should say 10.4.2.20 in the text in the top left of the screen.
If by chance this has worked then you should also now have 4 icons in the bootloader as you will now be back on a 4.1 bootloader.
If this does work at all let me know for next steps.
pjc21 said:
You may want to check & confirm that fastboot will not flash (you don't get the blue bar on tab when flashing) before looking for a new tab, although this "fastboot flash brick" issue results about 90% of the time you may be lucky and be in that 10% that does not.
You should be able to access fastboot using the "adb reboot-bootloader" command while in recovery, if pc does not pick-up device for adb in recovery have a look here and follow on from the device manager part.
When you get to the bootloader menu have a look at the text in the top left and confirm which 4.2 bootloader version your on, either 10.6.1.8 or 10.6.1.15.3 - then download the correct twrp version for that bootloader and see if you can flash it via fastboot.
If that does not work, which will most likely not would you like to try something for me? which may or may not work, just an idea.
Download this file, unzip it & copy the bootloader.bin file in your android-sdk/platform-tools folder.
Boot back to fastboot using the adb reboot-bootloader command and try
Code:
fastboot -i 0x0b05 flash bootloader bootloader.bin
If this works and does not freeze the tab then
Code:
fastboot reboot-bootloader
If the tab does reboot to this command then check the bootloader version here in the bootloader menu and if it has worked it should say 10.4.2.20 in the text in the top left of the screen.
If by chance this has worked then you should also now have 4 icons in the bootloader as you will now be back on a 4.1 bootloader.
If this does work at all let me know for next steps.
Click to expand...
Click to collapse
Followed your google usb instructions to make ADB work. Executed the bootloader command and was greeted with the three icons (4.2 bootloader I believe). Then flashed the correct TWRP 2.5 4.2 (no blue progress bar) and waited for the command prompt to show successful write. Rebooted and when recovery started up, showed nothing was different. Still requires me to enter a PW and none of the mounts work.
Then followed your bootloader update instructions and while it said it was successful I only get three icons when in fastboot.
Should I try the older TWRP that I had on there before (2.4.4.0) to see if that at least lets me back in?
anosis said:
Followed your google usb instructions to make ADB work. Executed the bootloader command and was greeted with the three icons (4.2 bootloader I believe). Then flashed the correct TWRP 2.5 4.2 (no blue progress bar) and waited for the command prompt to show successful write. Rebooted and when recovery started up, showed nothing was different. Still requires me to enter a PW and none of the mounts work.
Then followed your bootloader update instructions and while it said it was successful I only get three icons when in fastboot.
Should I try the older TWRP that I had on there before (2.4.4.0) to see if that at least lets me back in?
Click to expand...
Click to collapse
Miraculously the tablet will allow me now to cold boot into the previous rom. That at least makes it usable again, but it probably means that I am stuck on this. Also strange is that the tablet now no longer is recognized as a USB device. I cannot access the internal ram??
Under 'About Tablet' my build # shows 10.6.1.14.4/US DEODEX. Not sure if this might help in fixing the recovery issue?
Anyway I am glad I don't have to spend money to get a replacement, but sure hope I can fix the existing recovery image issue.
So tried to flash back the previous version of TWRP and it will not. Even though the fastboot command prompt shows a successful flash nothing appears to be changed, which refers to the original issue that states that I am stuck on whatever rom is on this tablet.
Is the reason I cannot flash back an older or correct version because there is a permission issue? Is there something I can do directly from within the rom after it boots up, like the shell emulator?
Sorry, I'd thought I'd posted under Q&A/Help. Not sure if a moderator can move it where it belongs?
My tf300t (ICS v9.3.4.17) is unlocked, rooted, and has TWRP 2.6.3.0 installed. I also have created the nvflash backups so it's currently running on the AndroidRoot v9.4.3.30r01 bootloader. I've stayed with
ICS and not updated anything except TWRP, but was just about to update to either ICS v9.4.3.30 or jump and install the latest JB.
Earlier today I went into Terminal Emulator, typed su and reboot as I've always done. I thought my tablet had shutdown because the screen stayed blank. I tried the power button and nothing so thought
maybe my power button had given out. I then tried plugging in the charging/usb cable which normally would get it to boot and again blank screen. Last I tried connecting to my pc and found it was in
APX mode. I'm able to boot up from nvflash and function normally but I'm stuck once I shut off the tablet from ICS (have to rerun nvflash to boot up again).
When I power off from APX mode, it automatically restarts back into APX mode. I was able to get into TWRP and tried restoring my latest nandroid (System, Data, Recovery, & Boot partitions) but no
change. Also tried a factory reset but same results - booting into APX yet again...
Ack, at this point I'm about ready to punt. I have my backups (TB & Helium) and am thinking of trying to update to v9.4.3.30 to see if this clears up booting into APX mode. To do this, can I just install the single
zip using TWRP & then re-flash TWRP using adb (or fastboot assuming I get it back)? Or do it via nvflash? If by nvflash, are these the correct commands after unpacking the v9.4.3.30 blob:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
Thoughts or ideas are really appreciated!
APX Mode
wha2do said:
My tf300t (ICS v9.3.4.17) is unlocked, rooted, and has TWRP 2.6.3.0 installed. I also have created the nvflash backups so it's currently running on the AndroidRoot v9.4.3.30r01 bootloader. I've stayed with
ICS and not updated anything except TWRP, but was just about to update to either ICS v9.4.3.30 or jump and install the latest JB.
Earlier today I went into Terminal Emulator, typed su and reboot as I've always done. I thought my tablet had shutdown because the screen stayed blank. I tried the power button and nothing so thought
maybe my power button had given out. I then tried plugging in the charging/usb cable which normally would get it to boot and again blank screen. Last I tried connecting to my pc and found it was in
APX mode. I'm able to boot up from nvflash and function normally but I'm stuck once I shut off the tablet from ICS (have to rerun nvflash to boot up again).
When I power off from APX mode, it automatically restarts back into APX mode. I was able to get into TWRP and tried restoring my latest nandroid (System, Data, Recovery, & Boot partitions) but no
change. Also tried a factory reset but same results - booting into APX yet again...
Ack, at this point I'm about ready to punt. I have my backups (TB & Helium) and am thinking of trying to update to v9.4.3.30 to see if this clears up booting into APX mode. To do this, can I just install the single
zip using TWRP & then re-flash TWRP using adb (or fastboot assuming I get it back)? Or do it via nvflash? If by nvflash, are these the correct commands after unpacking the v9.4.3.30 blob:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
Thoughts or ideas are really appreciated!
Click to expand...
Click to collapse
WoW that is an old bootloder..... v9.3.4.17 What is the SKU of that bootloader??
Enter APX mode and bootstrap in, If thats the ways its done.. I don't know because, I did my nvflash after jb came out...Run this command
Code:
nvflash -r --go
It will not reboot your tablet but it is supposed to let the bootloader resume on go which should be the next boot....
Just long hold your power button and let your tablet boot normally... Let me know if this helps at all... Thx lj
O yeah just be aware that the newest version of TWRP is having some issues... Just a FYI
lj50036 said:
WoW that is an old bootloder..... v9.3.4.17 What is the SKU of that bootloader??
Enter APX mode and bootstrap in, If thats the ways its done.. I don't know because, I did my nvflash after jb came out...Run this command
Code:
nvflash -r --go
It will not reboot your tablet but it is supposed to let the bootloader resume on go which should be the next boot....
Just long hold your power button and let your tablet boot normally... Let me know if this helps at all... Thx lj
O yeah just be aware that the newest version of TWRP is having some issues... Just a FYI
Click to expand...
Click to collapse
Thanks for the reply. The bootloader is the original one loaded when I created the nvflash backups. When rebooting from nvflash and holding the vol down button, I see:
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.3.30-20120206"
This had to have been universal for all that ran it way back when, though the SKU on my tablet is US (US_epad-9.4.3.2012...) and no real issues in over the year I've had it.
The nvflash -r --go command is the same as nvflash --resume --go...both reboot the device (nvflash help verifies they're the same).
------> Back to the issue at hand *sigh* <-----
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Sooo...what's my next step? Have noticed TWRP 2.6.3.0 seems to be a bit flaky in the past. Should I try installing US_epad-user-9.4.3.30.zip using TWRP? I have
OTA Rootkeeper installed with SuperSU so root should either remain or be restorable (fingers crossed). Or do I need to use nvflash to flash each partition? Or finally go
back to my original nvflash blobs? I really don't want to move forward and screw up something worse than it is!
Side note: I've tried to install tried & true TWRP v2.3.1.0. Using adb, it appears to flash successfully, I reboot into ICS, and then nvflash boot into TWRP - but I'm still
on v2.6.3.0. Possibly not rebooting smoothly into ICS isn't allowing the img file to take? For now will deal continue using my installed version v2.6.3.0 I guess...
Thanks for direction on where to go next! And if can, spell out my steps to take in detail (sometimes I may be a tad dense and don't mind any eyestrain, lol).
wha2do said:
Thanks for the reply. The bootloader is the original one loaded when I created the nvflash backups. When rebooting from nvflash and holding the vol down button, I see:
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.3.30-20120206"
This had to have been universal for all that ran it way back when, though the SKU on my tablet is US (US_epad-9.4.3.2012...) and no real issues in over the year I've had it.
The nvflash -r --go command is the same as nvflash --resume --go...both reboot the device (nvflash help verifies they're the same).
------> Back to the issue at hand *sigh* <-----
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Sooo...what's my next step? Have noticed TWRP 2.6.3.0 seems to be a bit flaky in the past. Should I try installing US_epad-user-9.4.3.30.zip using TWRP? I have
OTA Rootkeeper installed with SuperSU so root should either remain or be restorable (fingers crossed). Or do I need to use nvflash to flash each partition? Or finally go
back to my original nvflash blobs? I really don't want to move forward and screw up something worse than it is!
Side note: I've tried to install tried & true TWRP v2.3.1.0. Using adb, it appears to flash successfully, I reboot into ICS, and then nvflash boot into TWRP - but I'm still
on v2.6.3.0. Possibly not rebooting smoothly into ICS isn't allowing the img file to take? For now will deal continue using my installed version v2.6.3.0 I guess...
Thanks for direction on where to go next! And if can, spell out my steps to take in detail (sometimes I may be a tad dense and don't mind any eyestrain, lol).
Click to expand...
Click to collapse
Ok so you are 100% sure that you have had a US SKU version bootloader from when you got it new????
Where are you getting the firmware zip file from??
And you think this all started because of a wrong recovery flash???
lj50036 said:
Ok so you are 100% sure that you have had a US SKU version bootloader from when you got it new????
Where are you getting the firmware zip file from??
And you think this all started because of a wrong recovery flash???
Click to expand...
Click to collapse
Thanks for the quick reply... I'm positive on the US SKU - I have a screenshot I took of the SW info when it was brand new - here it is:
http://i1331.photobucket.com/albums...delampSWinfo-2012-11-25-07-29_zps27ba6fc6.jpg
As for the earlier firmware zips I've got, they were provided in one of the XDA posts - possibly this one: http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Nope, it just suddenly started while using the tablet normally. No flashing, restoring nandroids, etc in at least a week or two. I was playing one of my games on the tablet and sometimes the graphics will act
funny or it'll fc on me. So I either do a cold restart or reboot using Terminal Emulator to get the behaving normally again. In this case I rebooted using Android Terminal and suddenly only had a black
screen. Finally realized it wasn't powered down but was going into APX mode... Sorry, just tried flashing the older version of TWRP I'd always used since v2.6.3.0 has been flaky off and on. V2.6.3.0 was
originally flashed about 2-3 weeks ago and I'll just stick with it while working on fixing this!
The only thing I can think which may be unrelated. My daughter loaded a non-market game that was tagged as having Android:Fujacks by Avast! Being non-market, maybe foolishly? I let Avast
uninstall it. But I'm almost positive I rebooted a few times after without any issues. Also restoring an earlier nandroid didn't help, so don't think it's the system or data partitions messed up. Could it
be the boot partition that's gone funky?
That's why I'm wondering if an "upgrade" to v9.4.3.30 would clear this up - and if so, best/safest way to do it? Hope that helps fill in a little more!
wha2do said:
Thanks for the quick reply... I'm positive on the US SKU - I have a screenshot I took of the the SW info when it was brand new - here it is:
http://i1331.photobucket.com/albums...delampSWinfo-2012-11-25-07-29_zps27ba6fc6.jpg
As for the earlier firmware zips I've got, they were provided in one of the XDA posts - possibly this one: http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Nope, it just suddenly started without having done any flashing or restoring nandroids. I was playing one of my games on the tablet and sometimes the graphics will act
funny or it'll fc on me. So I either do a cold restart or reboot using Terminal Emulator to get it back to normal. In this case I rebooted using Android Terminal and suddenly
a black screen. Finally realized it wasn't powered down but was going into APX mode.
The only thing I can think which may be unrelated. My daughter loaded a non-market game that was tagged as having Android:Fujacks by Avast! Being non-market, maybe
foolishly? I let Avast uninstall it. But I'm almost positive I rebooted a few times after without any issues. Also restoring an earlier nandroid didn't help, so don't think it's the system
or data partitions messed up. Could it be the boot partition that's gone funky?
That's why I'm wondering if an "upgrade" to v9.4.3.30 would clear this up - and if so, best/safest way to do it? Hope that helps fill in a little more!
Click to expand...
Click to collapse
Ok the .30 zip from them what is inside the zip??
lj50036 said:
Ok the .30 zip from them what is inside the zip??
Click to expand...
Click to collapse
It's the normal Stock v9.4.3.30 update from ASUS. It's the "US_epad-user-9.4.3.30.zip" which in turn contains the META-INF folder and the blob file. The blob file contains:
blob.APP ; system img
blob.EBT ; bootloader.bin
blob.LNX ; boot img
blob.PT ; partition table I presume
blob.SOS ; stock recovery img
The blob names are exact and I think I have each identified as to their purpose going from old notes. EBT, APP, and LNX are the three that I believe could/would be flashed using nvflash
if necessary (if can't just install the full update zip & reinstall TWRP over the stock recovery)...
Is that what you're looking for?
wha2do said:
It's the normal Stock v9.4.3.30 update from ASUS. It's the "US_epad-user-9.4.3.30.zip" which in turn contains the META-INF folder and the blob file. The blob file contains:
blob.APP ; system img
blob.EBT ; bootloader.bin
blob.LNX ; boot img
blob.PT ; partition table I presume
blob.SOS ; stock recovery img
The blob names are exact and I think I have each identified as to their purpose going from old notes. EBT, APP, and LNX are the three that I believe could/would be flashed using nvflash
if necessary (if can't just install the full update zip & reinstall TWRP over the stock recovery)...
Is that what you're looking for?
Click to expand...
Click to collapse
Ok so it just a blob binary and a META-INF folder in the zip??
lj50036 said:
Ok so it just a blob binary and a META-INF folder in the zip??
Click to expand...
Click to collapse
Yep...standard update zip inside a zip that comes from ASUS.
wha2do said:
Yep...standard update zip inside a zip that comes from ASUS.
Click to expand...
Click to collapse
We need to get to fastboot and verify that we can see your devices boot into the bootloader screen.. As I recall you should have a
usb icon you must select to enable fastboot... Can you get to this point??
lj50036 said:
We need to get to fastboot and verify that we can see your devices boot into the bootloader screen.. As I recall you should have a
usb icon you must select to enable fastboot... Can you get to this point??
Click to expand...
Click to collapse
No, the icons one normally sees are missing/not available to be selected. When I reboot from nvflash & hold the vol down button, I only have two options. Volume up to enter TWRP as expected, or it begins cold booting. Guess that got lost in my lengthy message above:
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Click to expand...
Click to collapse
So unfortunately, no fastboot - only ADB, APX, and Recovery (TWRP) modes available.
wha2do said:
No, the icons one normally sees are missing/not available to be selected. When I reboot from nvflash & hold the vol down button, I only have two options. Volume up to enter TWRP as expected, or it begins cold booting. Guess that got lost in my lengthy message above:
So unfortunately, no fastboot - only ADB, APX, and Recovery (TWRP) modes available.
Click to expand...
Click to collapse
Ok well we need a different version of twrp than what your on now I would highly recommend a version older that what your on now.. as the newer twrps are buggy 2.5.5.0 is a solid one... Make sure you get the one for your tablet...as there are a few different versions... Than rename it
Code:
twrp.blob
Make sure you don't rename it twrp.blob.blob as windows is good at doing still stuff like that.....
Move your twrp.blob to the root of your c drive than open a command window as admin and type
Code:
cd /
This will move you to the root of your c drive in your command window than type
Code:
dir
This will list all the files and folder in the root of your c drive make sure you see the twrp.blob if so your ready
Boot your tablet into APX mode bootstrap into nvflash mode and type
Code:
nvflash -r --download 5 twrp.blob
The output of this will look something like this
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Than
Code:
nvflash -r --go
Then try to enter recovery...
Let me know
lj50036 said:
Ok well we need a different version of twrp than what your on now I would highly recommend a version older that what your on now.. as the newer twrps are buggy 2.5.5.0 is a solid one... Make sure you get the one for your tablet...as there are a few different versions... Than rename it
Code:
twrp.blob
Make sure you don't rename it twrp.blob.blob as windows is good at doing still stuff like that.....
Move your twrp.blob to the root of your c drive than open a command window as admin and type
Code:
cd /
This will move you to the root of your c drive in your command window than type
Code:
dir
This will list all the files and folder in the root of your c drive make sure you see the twrp.blob if so your ready
Boot your tablet into APX mode bootstrap into nvflash mode and type
Code:
nvflash -r --download 5 twrp.blob
The output of this will look something like this
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Than
Code:
nvflash -r --go
Then try to enter recovery...
Let me know
Click to expand...
Click to collapse
Ok - picked up v2.5.0.0 (don't see a v2.5.5.0 on the TWRP website) and successfully installed the .blob file but... As soon as I hit the volume up button it went to cold boot instead. I remembered with the Prime that for some reason, the TWRP img file format needed to be used when on the AndroidRoot bootloader. So long story short, got the img file installed and I have TWRP 2.5.0.0 running at the moment.
So where to next? And thanks so far
wha2do said:
Ok - picked up v2.5.0.0 (don't see a v2.5.5.0 on the TWRP website) and successfully installed the .blob file but... As soon as I hit the volume up button it went to cold boot instead. I remembered with the Prime that for some reason, the TWRP img file format needed to be used when on the AndroidRoot bootloader. So long story short, got the img file installed and I have TWRP 2.5.0.0 running at the moment.
So where to next? And thanks so far
Click to expand...
Click to collapse
So you can get into recovery now??? if so, take the double zipped firmware......unzip it one time and the zip that is made move to.....O
Do you have a way to put that zip on an sdcard so we can get it on your tablet?? If not no big deal.... Just let me know if you can make that happen.....
lj50036 said:
So you can get into recovery now??? if so, take the double zipped firmware......unzip it one time and the zip that is made move to.....O
Do you have a way to put that zip on an sdcard so we can get it on your tablet?? If not no big deal.... Just let me know if you can make that happen.....
Click to expand...
Click to collapse
Sorry, I get over wordy (lol)... Yes, I have TWRP 2.5.0.0 installed and was able to get in. I'd already prepared for this - have the unzipped (once) file sitting in my tablet's root folder (/sdcard). Checked and checksum matched so it transferred without errors (used Airdroid, in case wondering).
Took a few extra minutes - wanted double check all was there as I thought. So yes, have the v9.4.3.30 zipfile (containing META files & blob) on tablet's "root" directory. Currently in TWRP v2.5.0.0 and ready to install it (figuring that's the next step)...
Just give me the greenlight, lol
One thing doing quickly is making a nandroid - never can be too safe, heh! Should be about another 5 minutes...
wha2do said:
One thing doing quickly is making a nandroid - never can be too safe, heh! Should be about another 5 minutes...
Click to expand...
Click to collapse
No worries at all you take your time.... Let me know....
lj50036 said:
No worries at all you take your time.... Let me know....
Click to expand...
Click to collapse
Good to go!
wha2do said:
Good to go!
Click to expand...
Click to collapse
??????
Still here - at this point have the zipfile unzipped once, on the tablet's root directory, and TWRP v2.5.0.0 installed. I assume going to install the zip file via TWRP Install? Tablet's got plenty of battery charge so good to go - just let me know!
I am unable to boot into recovery on my tf300t. I can get to the menu with 3 icons I select RCK and it shows installing system then Error!
I still was able to unlock and root the device but I still can't get past error or figure out how to install a new recovery.
Any help?
Thanks
Grem135 said:
I am unable to boot into recovery on my tf300t. I can get to the menu with 3 icons I select RCK and it shows installing system then Error!
I still was able to unlock and root the device but I still can't get past error or figure out how to install a new recovery.
Any help?
Thanks
Click to expand...
Click to collapse
The error triangle means you have to install a recovery (before you use it).
Make sure the recovery you will install is compatible before flashing it.
cmendonc2 said:
The error triangle means you have to install a recovery (before you use it).
Make sure the recovery you will install is compatible before flashing it.
Click to expand...
Click to collapse
All instructions I find for flashing a recovery have you booting into RCK to flash it. Is there another way?
Grem135 said:
All instructions I find for flashing a recovery have you booting into RCK to flash it. Is there another way?
Click to expand...
Click to collapse
You can use Terminal Emulator to flash it if you are rooted correctly.
Code:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Make sure you install the -42 version.
cmendonc2 said:
You can use Terminal Emulator to flash it if you are rooted correctly.
Code:
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Make sure you install the -42 version.
Click to expand...
Click to collapse
Thanks for the help. I finally can boot into recovery. It took a bit to realize sdcard meant internal memory not the microsd like on my phone.
Thanks button hit. :good:
Hi XDA,
I am a complete noob, and this is my first time posting, so bear with me.
Some time ago I rooted and unlocked my TF300 with SuperSu. Recently I wanted to upgrade to 4.4 kitkat. However, my Tablet was stuck at Andriod 4.1 because of the the unlock.
I went to manually update my TF via the Asus website. I installed the 10.6.1.8 using my TWRP 2.5, and Oem 4.1 OS. Installation worked just fine. After install, I booted up and I had 4.2 with everything working correctly.
Next step was to install TWRP 2.7.0.1. I reset my TF and went into RCK to see something went wrong when updating.
My TWRP will not load, and I get the Android on his back with the red triangle when I try to enter RCK.
Thanks in advance!!
I managed to install 10.6.1.27, but it did not change anything with my boot loader.
I downloaded motochopper, but that didn't seem to work, just told me my abt was out of date. SuperSu isn't working now either, "No Binary, There is a problem."
How do I install TWRP 2.7 with no boot loader? Please help.
TallMilk said:
I managed to install 10.6.1.27, but it did not change anything with my boot loader.
I downloaded motochopper, but that didn't seem to work, just told me my abt was out of date. SuperSu isn't working now either, "No Binary, There is a problem."
How do I install TWRP 2.7 with no boot loader? Please help.
Click to expand...
Click to collapse
Most people just install TWRP via fastboot like
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
You could try using other root methods, like Framaroot or Kingo. I think Kingo was reported to work on the latest stock version.
cmendonc2 said:
Most people just install TWRP via fastboot like
Code:
fastboot -i 0x0B05 flash recovery twrp.blob
You could try using other root methods, like Framaroot or Kingo. I think Kingo was reported to work on the latest stock version.
Click to expand...
Click to collapse
I will look into that, but I am pretty sure I was already rooted, unless losing my boot loader means I am no longer rooted.
Another thing, I can't find a twrp.blob for 2.7, just a zip. I have one for 2.5, but that is useless because I already have 4.2. I also have not been able to find a working link to fastboot.
If anyone could give me a link to the fastboot or a link to a tutorial, that would be amazing. I have done my research, but all the lingo and different methods can be mind bending.
Thanks
TallMilk said:
I will look into that, but I am pretty sure I was already rooted, unless losing my boot loader means I am no longer rooted.
Another thing, I can't find a twrp.blob for 2.7, just a zip. I have one for 2.5, but that is useless because I already have 4.2. I also have not been able to find a working link to fastboot.
If anyone could give me a link to the fastboot or a link to a tutorial, that would be amazing. I have done my research, but all the lingo and different methods can be mind bending.
Thanks
Click to expand...
Click to collapse
You can get the img (which substitutes as a blob) from extracting it from the TWRP 2.7 zip file.
1) You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery twrp.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6.) Go back into TWRP and install what you want.
You are amazing. I will give it a try tonight and report back!
cmendonc2 said:
You can get the img (which substitutes as a blob) from extracting it from the TWRP 2.7 zip file.
1) You will need ADB and fastboot for this: http://forum.xda-developers.com/showthread.php?p=42407269. I would suggest keeping the tablet at least at 50% battery.
2) Install Naked Drivers. This may be optional for you. If you can proceed to the next step without, you won't need it.
3) Enter fastboot by rebooting and holding down the power button. TF300 enters fastboot automatically since this is 4.2 BL.
4) Next we need to enter a command. In side the ADB folder, hold shift and right click. Then select Open command window here.
first check to make sure the device is connected:
Code:
fastboot devices
The device serial number should be listed.
enter command:
Code:
fastboot flash recovery twrp.img -i 0x0b05
Blue bar on device will fill. Be patient.
5) Reboot the Device back into Android. This is an important step.
6.) Go back into TWRP and install what you want.
Click to expand...
Click to collapse
Installed adb fastboot. However, my device does not automatically go into fastboot, I still have to hold down the volume key.
Once I am in fastboot usb (with the 3 icons), I fastboot successfully and get the serial number, then when I type the 'fastboot flash recovery twrp.img -i 0x0b05' command I get this error: cannot load 'twrp.img' : No error
I am attemping to use the 2.7.0.1 twrp from the 4.4.2 page. I have extracted the recovery.img (tried renaming to twrp and left it the same) and placed it in the root of both my external and internal sd.
I have now tried it with .zips .img .blob and I receive the same error everytime. Not sure what I am doing wrong now.
TallMilk said:
Installed adb fastboot. However, my device does not automatically go into fastboot, I still have to hold down the volume key.
Once I am in fastboot usb (with the 3 icons), I fastboot successfully and get the serial number, then when I type the 'fastboot flash recovery twrp.img -i 0x0b05' command I get this error: cannot load 'twrp.img' : No error
I am attemping to use the 2.7.0.1 twrp from the 4.4.2 page. I have extracted the recovery.img (tried renaming to twrp and left it the same) and placed it in the root of both my external and internal sd.
I have now tried it with .zips .img .blob and I receive the same error everytime. Not sure what I am doing wrong now.
Click to expand...
Click to collapse
Put the twrp.img into your ADB folder, where you installed it. Then run the next command.
cmendonc2 said:
Put the twrp.img into your ADB folder, where you installed it. Then run the next command.
Click to expand...
Click to collapse
Awesome! Worked like a charm. twrp 2.7.0.1 installed perfectly.
Then I tried to flash the cyanogenmod. Said it installed fine, but it just gets stuck on the loading screen...
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
SilentSpartan said:
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
Click to expand...
Click to collapse
Finally got it to work. I had to do a wipe first, read about old roms interfering with new installations.
SilentSpartan, I used SuperSU last year to root and unlock my tablet when it was still a 4.0 android to flash to 4.1. This recent update was from 2.5 TWRP on a rooted device running 4.2. When I installed 4.2, it blew away my TWRP, and I had to flash the new TWRP 2.7.0.1.
That flash from OEM fastboot to TWRP 2.7.0.1 is what I needed help with.
TallMilk said:
Finally got it to work. I had to do a wipe first, read about old roms interfering with new installations.
SilentSpartan, I used SuperSU last year to root and unlock my tablet when it was still a 4.0 android to flash to 4.1. This recent update was from 2.5 TWRP on a rooted device running 4.2. When I installed 4.2, it blew away my TWRP, and I had to flash the new TWRP 2.7.0.1.
That flash from OEM fastboot to TWRP 2.7.0.1 is what I needed help with.
Click to expand...
Click to collapse
Damn, so I'm screwed. Why does Asus have to such so much...? You can no longer unlock afaik.
SilentSpartan said:
I am trying to do exactly what TallMilk is doing...put Cyanogenmod on my tablet. It is my understanding that I have to unlock my bootloader though? Which I have tried doing a million different ways with the Asus Unlock tool which always gives me an error.
If I follow the instructions posted above I will be able to flash Cyanogenmod without unlocking my bootloader?
Click to expand...
Click to collapse
You're going to have to unlock no matter what. Did you try both v7 and v8 of the unlocker and calling Asus Support to tell them to put your serial number back into the database (get a manager)?
cmendonc2 said:
You're going to have to unlock no matter what. Did you try both v7 and v8 of the unlocker and calling Asus Support to tell them to put your serial number back into the database (get a manager)?
Click to expand...
Click to collapse
I've tried every firmware and unlock tool combination. Nothing works. I sent them an email a day ago. Depending on there response, maybe I'll try calling. I'm so fed up with this tablet, I'm about to throw it out my window. $400 POS. :good:
SilentSpartan said:
I've tried every firmware and unlock tool combination. Nothing works. I sent them an email a day ago. Depending on there response, maybe I'll try calling. I'm so fed up with this tablet, I'm about to throw it out my window. $400 POS. :good:
Click to expand...
Click to collapse
Did you ever get your tablet fixed? I am having some problems myself after a miserable m9 update.