Related
Attempting to root, to backup then to install cm 10.1 or other rom
I've installed cwm from this thread http://forum.xda-developers.com/showthread.php?t=1668173
I can boot into recovery ok, however I get the following errors:
can't mount /cache/recovery/command
can't mount /cache/recovery/log
can't mount /cache/recovery/last_log
can't mount /cache/recovery/.
when trying to access internal or external sd card get:
can't mount /sdcare/
can't mount /emmc
Any help appreciated
Update: tried twrp 2.4.3.0 does the same thing
The new update has encryption by default. That's why you can't mount anything. I am not sure if team win will release an update for their recovery or if Asus needs to do it. Seems like this update really screwed over some people.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
The new update has encryption by default. That's why you can't mount anything. I am not sure if team win will release an update for their recovery or if Asus needs to do it. Seems like this update really screwed over some people.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
wow not good news. Guess I'l just have to monitor sites and see what happens over time.
Disappointing for sure as this last update screwed up the hdmi out, I have functional tablet it might as well be a bricked pos, arg !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
It's worthless to me in it's present state
Hmm where is the phone num so i can call gripe at asus
tonyjsan said:
wow not good news. Guess I'l just have to monitor sites and see what happens over time.
Disappointing for sure as this last update screwed up the hdmi out, I have functional tablet it might as well be a bricked pos, arg !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
It's worthless to me in it's present state
Hmm where is the phone num so i can call gripe at asus
Click to expand...
Click to collapse
Think you can only email them :/
I dont think its asus who encrypted it. I think it was google. I am not sure though so dont quote me xD
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
elesbb said:
Think you can only email them :/
I dont think its asus who encrypted it. I think it was google. I am not sure though so dont quote me xD
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
twrp I think might support that sort of thing already, i went back into twrp2 and it does ask for a password at first, a check of the logs by twrp said can't decrypt
Who ever set the encryption, needs to show how to unset it.
I'm having the same issue that tonyjsan described.
This was I did:
1 - I updated to 4.2.1 via OTA.
2 - Download Asus unlock apk & unlocked the boot loader.
3 - Then installed the CWM 6.0.2.3 via fast boot.
4 - Tried to installed CM10.1 nightly couldn't acess SD started to get the following:
can't mount /cache/recovery/command
can't mount /cache/recovery/log
can't mount /cache/recovery/last_log
can't mount /cache/recovery/.
when trying to access internal or external sd card get:
can't mount /sdcare/
can't mount /emmc/
Now it's the point where I got stupid, and decided to go into the bootloader and do a full wipe, which I THINK wiped everything and installed the recovery Kernel (which now is CWM) into the main image.
Now my TF300T only boot to CWM and I can acess it via ADB do thing like push files, but i've lost the boot loader and cannot go into fastboot.
Really need the expertise of a guru right now
Help is appreciated
Getting Same Issues
Both the latest TWRP2 and latest CWM are a bust for me too.
If the recovery kernel image can't get at the disk partitions - then no custom ROMS
can be installed.
I guess being the first non-nexus with 4.2.1 isn't such great news after all.
xbill9 said:
If the recovery kernel image can't get at the disk partitions - then no custom ROMS
can be installed.
Click to expand...
Click to collapse
Starting to get the felling I have a 300$ dollar brick on my desk
Same Here
I've run into the same thing. I did the OTA update to 4.2.1, and then I decided to root, so I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2041627.
Unlocked worked.
Recovery Flash worked.
Mounting any part of the sdcard (internal or external) does not work in recovery.
I can still boot into the OS, so I'm not bricked, but I can't install root because I can't see the internal storage to flash it.
Is it possible to flash back to 4.1.1?
Yes, but your recovery must be working.
vconceicao said:
I'm having the same issue that tonyjsan described.
This was I did:
1 - I updated to 4.2.1 via OTA.
2 - Download Asus unlock apk & unlocked the boot loader.
3 - Then installed the CWM 6.0.2.3 via fast boot.
4 - Tried to installed CM10.1 nightly couldn't acess SD started to get the following:
can't mount /cache/recovery/command
can't mount /cache/recovery/log
can't mount /cache/recovery/last_log
can't mount /cache/recovery/.
when trying to access internal or external sd card get:
can't mount /sdcare/
can't mount /emmc/
Now it's the point where I got stupid, and decided to go into the bootloader and do a full wipe, which I THINK wiped everything and installed the recovery Kernel (which now is CWM) into the main image.
Now my TF300T only boot to CWM and I can acess it via ADB do thing like push files, but i've lost the boot loader and cannot go into fastboot.
Really need the expertise of a guru right now
Help is appreciated
Click to expand...
Click to collapse
vconceicao said:
Starting to get the felling I have a 300$ dollar brick on my desk
Click to expand...
Click to collapse
as sad as it seems :'( you are more than likely bricked. Every thread I read, even on 4.1 stock, once you do the "wipe all" option in bootloader menu, without a stock recovery. You become bricked.
wirikidor said:
I've run into the same thing. I did the OTA update to 4.2.1, and then I decided to root, so I followed these instructions: http://forum.xda-developers.com/showthread.php?t=2041627.
Unlocked worked.
Recovery Flash worked.
Mounting any part of the sdcard (internal or external) does not work in recovery.
I can still boot into the OS, so I'm not bricked, but I can't install root because I can't see the internal storage to flash it.
Is it possible to flash back to 4.1.1?
Click to expand...
Click to collapse
You should be able to fastboot the stock Asus 4.1.1 .blob file.
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
vconceicao said:
Now it's the point where I got stupid, and decided to go into the bootloader and do a full wipe, which I THINK wiped everything and installed the recovery Kernel (which now is CWM) into the main image.
Now my TF300T only boot to CWM and I can acess it via ADB do thing like push files, but i've lost the boot loader and cannot go into fastboot.
Really need the expertise of a guru right now
Help is appreciated
Click to expand...
Click to collapse
When you said wipe, you used the wipe data option, when sitting at the first menu (boot loader menu) after pressing power and vol down ?
One other thing I'd share here to is that the factory wipe, from within settings, for me does not work, it boots to twrp / recovery, when I exit all data still there. So was wondering which one you used ?
Is the encryption on the partitions from sbk nvflash crap (i'm thinking not ??) or just an encrypted ext4 partition ??
elesbb said:
You should be able to fastboot the stock Asus 4.1.1
Click to expand...
Click to collapse
If I drop back to 4.1.1 will I have the same problem with not being able to access cache, data etc. in twrp or cwm, will it be encrypted ?
I'm also wondering dropping back to 4.1.1 will the 4.2.1 multi-user stuff mess with the downgrade, appears to be using sym links to create separate directory for each user.
tonyjsan said:
If I drop back to 4.1.1 will I have the same problem with not being able to access cache, data etc. in twrp or cwm, will it be encrypted ?
I'm also wondering dropping back to 4.1.1 will the 4.2.1 multi-user stuff mess with the downgrade, appears to be using sym links to create separate directory for each user.
Click to expand...
Click to collapse
Hello I have 4.1.1 It is unlocked. I have flashed the CWM and when I boot into recovery I only see the sd card and will not let me rrot via the zip either. I get an error in CWM saying that root persmissions need to be fixed. I have tried to fix then not to fix. Still nothing.
Not sure if this is inline with what everyone else is seeing.
ASUS did push from .17 to .20 the other day.
This is a fishing trip. 4.2 is multi-user, for multi-user to work the tablet has to be encrypted or users could access each others space. I don't have 4.2 so I can't test. If multi-user is deactivated encryption is not necessary. If multi-user is turned off can you find a setting to unencrypt?
It seems I remember someone unencrypting with twrp or fastboot but it took three tries, multi-user would still need to be off. This is not a suggestion just my thoughts.
My version of fastboot does not list unencrypt as an option.
Holy cow I now have cm 10.1, root, and hdmi out problem fixed. After lots digging to be sure I did not screw the tablet up here is what I did.
1) Downgrade to US_10.4.2.20, using fastboot and blob from asus web site.
2) after rebooting I had the previous boot-loader screen (in which usb icon shows), I re-installed recovery twrp2.
3) I did not even bother to boot into 10.4.2.20, went straight to recovery and I had access to cache, data, sdcard etc...
4) adb pushed the cm 10.1 zip to the sdcard and the gapps zip as well.
5) flash cm 10.1 then gapps
6) reboot and all is well.
There is one word of caution, not sure what happen but do not use the usb port on the keyboard dock with cm 10.1, it zapped a usb jump drive and a 500 gb portable drive , still looking into if I can recovery the drive and what caused it.
I's so glad I'm on CM 10.1 tablet running faster just seems to perform better.
I have also had this issue and managed to come back from it.
In doing some testing of the new ota update 4.2.1 (10.6.1.8) I have found that this issue is a direct result of the new 4.2.1 bootloader, it will not work with any custom recovery. twrp will give password prompt and be unable to mount anything but possible system, same goes for cwm minus the password prompt.
After doing a full wipe from twrp and then flashing just the new 4.2.1 bootloader, I rebooted back into twrp and it's encrypted, can't mount anything.
This method will not work if you cannot flash from fastboot successfully. In fact if you have attempted any other way to fix it may not work.
After I rebooted twrp to find it was encrypted the first thing I did was to reboot into fastboot mode and did the following:
flashed the 4.2.1 stock recovery, I have uploaded to here
Copy the "stock.blob" file to your android-sdk\platform-tools folder.
Also download the "US_epaduser_10_4_2_20_UpdateLauncher.zip" from the Asus website and unzip,
In the unzipped folder you will then have another zip file "US_epad-user-10.4.2.20.zip" unzip this also and now in that unzipped folder you will have a "blob" file, copy this to your android-sdk\platform-tools folder.
Boot into fastboot and check your pc can see your device:
open a command prompt and cd to your platform-tools directory.
Code:
fastboot devices
This should return your device serial, if not then fastboot is not setup correctly.
Next:
Code:
fastboot -i 0x0b05 flash recovery stock.blob
fastboot -i 0x0b05 reboot
Boot back into fastboot:
Code:
fastboot -i 0x0b05 flash system blob
fastboot -i 0x0b05 reboot
The system blob will take some time 10min or so to flash, so just give it some time then issue the reboot command.
Also first reboot after system blob flash will take some time, you will see a progress bar under the Asus logo.
Once your tablet has fully loaded you can now boot back into fastboot and flash a custom recovery & flash custom rom again.
I do suggest skipping the 4.2.1 update for now until this issue has been fixed.
As I have said this may not work for everyone depending on if you have attempted any other commands via fastboot or adb.
This has worked for me twice now but try at own risk.
pjc21 said:
I have also had this issue and managed to come back from it.
In doing some testing of the new ota update 4.2.1 (10.6.1.8) I have found that this issue is a direct result of the new 4.2.1 bootloader, it will not work with any custom recovery. twrp will give password prompt and be unable to mount anything but possible system, same goes for cwm minus the password prompt.
After doing a full wipe from twrp and then flashing just the new 4.2.1 bootloader, I rebooted back into twrp and it's encrypted, can't mount anything.
This method will not work if you cannot flash from fastboot successfully. In fact if you have attempted any other way to fix it may not work.
After I rebooted twrp to find it was encrypted the first thing I did was to reboot into fastboot mode and did the following:
flashed the 4.2.1 stock recovery, I have uploaded to here
Copy the "stock.blob" file to your android-sdk\platform-tools folder.
Also download the "US_epaduser_10_4_2_20_UpdateLauncher.zip" from the Asus website and unzip,
In the unzipped folder you will then have another zip file "US_epad-user-10.4.2.20.zip" unzip this also and now in that unzipped folder you will have a "blob" file, copy this to your android-sdk\platform-tools folder.
Boot into fastboot and check your pc can see your device:
open a command prompt and cd to your platform-tools directory.
Code:
fastboot devices
This should return your device serial, if not then fastboot is not setup correctly.
Next:
Code:
fastboot -i 0x0b05 flash recovery stock.blob
fastboot -i 0x0b05 reboot
Boot back into fastboot:
Code:
fastboot -i 0x0b05 flash system blob
fastboot -i 0x0b05 reboot
The system blob will take some time 10min or so to flash, so just give it some time then issue the reboot command.
Also first reboot after system blob flash will take some time, you will see a progress bar under the Asus logo.
Once your tablet has fully loaded you can now boot back into fastboot and flash a custom recovery & flash custom rom again.
I do suggest skipping the 4.2.1 update for now until this issue has been fixed.
As I have said this may not work for everyone depending on if you have attempted any other commands via fastboot or adb.
This has worked for me twice now but try at own risk.
Click to expand...
Click to collapse
Question: You said you reflashed the stock bootloader. I had gotten my tf300 couple days ago but went through the ota update not thinking of issues if wanted to root so I'm not rooted totally stock on 4.2.1but if possible would like to flash back to stock locked bootloader if possible. After reading all the issues with trying to flash custom recovery and root after ota figured I'd just wait till some of the issues are figured out. I'm new to this device but have rooted many other android phones in the passed so not a total noob just learning about this one been reading alot. Just wondering if there were a way to do so for future updates as i read you lose ota capability if unlocked. Thanks
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
aerdely said:
Question: You said you reflashed the stock bootloader. I had gotten my tf300 couple days ago but went through the ota update not thinking of issues if wanted to root so I'm not rooted totally stock on 4.2.1but if possible would like to flash back to stock locked bootloader if possible. After reading all the issues with trying to flash custom recovery and root after ota figured I'd just wait till some of the issues are figured out. I'm new to this device but have rooted many other android phones in the passed so not a total noob just learning about this one been reading alot. Just wondering if there were a way to do so for future updates as i read you lose ota capability if unlocked. Thanks
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Click to expand...
Click to collapse
This approach recovered the tablet.
As long as the bootloader is working - it is probably fixable.
Here is how I got it to work:
-preloaded my ROM and Gapps on the SD card
-flashed stock system blob (for the right region) from the ASUS website
-let the stock ROM reboot
-it hangs - but will be visible from ADB
-reboot to fastboot
-install TWRP or CWM from fastboot
-reboot recovery
-then flash ROM + Gapps
There has to be something in the new OTA bootloader or OTA system that
locks down the partitions.
xbill9 said:
This approach recovered the tablet.
As long as the bootloader is working - it is probably fixable.
Here is how I got it to work:
-preloaded my ROM and Gapps on the SD card
-flashed stock system blob (for the right region) from the ASUS website
-let the stock ROM reboot
-it hangs - but will be visible from ADB
-reboot to fastboot
-install TWRP or CWM from fastboot
-reboot recovery
-then flash ROM + Gapps
There has to be something in the new OTA bootloader or OTA system that
locks down the partitions.
Click to expand...
Click to collapse
Yea should of mentioned im not rooted haven't done that yet as if you are on the 4.2.1 ota you can't without issues. Device works fine I'm on stock recovery and firmware but just an unlocked bootloader and just little worried because some have mention can lose any future ota's if thats not the case than i guess no issue at all but not sure on that and was just looking for a way to either relock the bootloader or reflash it. Probably isn't at the moment but some have been asking about this because of issues with the ota.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
I configured nvflash on a new unrooted, unlocked TF300T, running the 9.4.3.30 firmware by following the directions at. androidroot mobi t3_nvflash. The AndroidRoot9.4.0.30r01 bootloader and nvflash were installed and the tablet was successfully booted into APX mode, nvflash was bootstrapped using wheelie, and the bricksafe.img, factory-config.img and unlock-token.img files were generated and saved.
Unfortunately, I was not able to use fastboot to install clockworkmod recovery or enable root. Flashing was attempted initially using Windows XP and again later using Ubuntu 12.04, with the following result:
# fastboot -i 0x0B05 flash recovery recovery.img
sending 'recovery' (5306 KB)...
OKAY [ 2.443s]
writing 'recovery'...
OKAY [ 2.058s]
finished. total time: 4.500s
# fastboot -i 0x0B05 reboot
rebooting...
All seems well, but recovery does not install, the tablet does not reboot, and will not accept further flashboot commands. It has to be restarted by holding down the start button. On restart a blue line quickly flashes across the screen, but on boot to fastboot/recovery mode there is no icon to access recovery.
Device: TF300T Transformer Pad
Android Version 4.0.3;
Build Number: IML74.US_epad-9.4.3.30-201220604
Questions:
To what partition/folder is the recovery image flashed on the TF300T?
Has anyone ever actually used nvflash to unbrick a TF300T? If so will someone point me to instruction how to repair/restore the original/unlocked bootloader using nvflash, or something close?
Is there a procedure to install CWM recovery using nvflash?
Thank you for your help, any assistance is appreciated.
Some Hard Learned Advice
I'm still unable to flash a custom recovery, but the good news is that my tablet works although it's not rooted, and I have a functioning nvflash
If you want to avoid my problem, I recommend that you root your tablet before you install nvflash. Remember that at present, you can only install nvflash on a TF300T running ICS but, definitely do install nvflash. Follow the instructions from the folks at androidroot.mobi, but don't forget to root first.
listerism said:
I'm still unable to flash a custom recovery, but the good news is that my tablet works although it's not rooted, and I have a functioning nvflash
If you want to avoid my problem, I recommend that you root your tablet before you install nvflash. Remember that at present, you can only install nvflash on a TF300T running ICS but, definitely do install nvflash. Follow the instructions from the folks at androidroot.mobi, but don't forget to root first.
Click to expand...
Click to collapse
I believe you would want to follow the guide in the General section for the TF300 to upgrade from ICS to JB 4.1.1. Its called
[GUIDE]Upgrade your TF300t to Jellybean 4.1, root & remove bloatware[Noobproof]
Then update to the newest version of 4.1.1. Then finally put a version of TWRP that is compatible with the 4.1.1 bootloader on the device. Also when I Installed the recovery I used the "recovery.blob" file, not the .img
listerism said:
I configured nvflash on a new unrooted, unlocked TF300T, running the 9.4.3.30 firmware by following the directions at. androidroot mobi t3_nvflash. The AndroidRoot9.4.0.30r01 bootloader and nvflash were installed and the tablet was successfully booted into APX mode, nvflash was bootstrapped using wheelie, and the bricksafe.img, factory-config.img and unlock-token.img files were generated and saved.
Unfortunately, I was not able to use fastboot to install clockworkmod recovery or enable root. Flashing was attempted initially using Windows XP and again later using Ubuntu 12.04, with the following result:
# fastboot -i 0x0B05 flash recovery recovery.img
sending 'recovery' (5306 KB)...
OKAY [ 2.443s]
writing 'recovery'...
OKAY [ 2.058s]
finished. total time: 4.500s
# fastboot -i 0x0B05 reboot
rebooting...
All seems well, but recovery does not install, the tablet does not reboot, and will not accept further flashboot commands. It has to be restarted by holding down the start button. On restart a blue line quickly flashes across the screen, but on boot to fastboot/recovery mode there is no icon to access recovery.
Device: TF300T Transformer Pad
Android Version 4.0.3;
Build Number: IML74.US_epad-9.4.3.30-201220604
Questions:
To what partition/folder is the recovery image flashed on the TF300T?
Has anyone ever actually used nvflash to unbrick a TF300T? If so will someone point me to instruction how to repair/restore the original/unlocked bootloader using nvflash, or something close?
Is there a procedure to install CWM recovery using nvflash?
Thank you for your help, any assistance is appreciated.
Click to expand...
Click to collapse
Since you already have installed nvflash and have your files I'll try to answer with that in mind.
First I suggest using twrp of the latest version for ICS not cwm.
The partition for recovery is recovery. The commands you provided are correct (I do suggest using a blob file with fastboot - and twrp not cwm).
For unbrick with nvflash yes others have here is a link with the commands needed.
Remember you only have to flash what is needed to recover your tablet.
Did you perhaps download the wrong version of recovery? There is specific versions for ICS and JB 4.1.1 and JB 4.2.1. However I think of you use a blob instead it may work. But as above posters said, I would update to the version of stock android that you want. Cuz when you update your going to loose root and recovery anyways so why bother putting it on there? So I wouldn't flash anything till you are on the version you want to root. Also it will be safer to upgrade with stock recovery. TONS of people have bricked by updating to 4.2.1 with an incompatible recovery. You've been warned.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Nevermind. I need to read entire posts...
No USB icon
Hi Guys,
I have 4.2.1 installed and want to move up to 4.2.2 however i now notice that when I try to boot back into recovery I have no USB icon to reinstall TWRP. I used TWRP 2.5 to install 4.2.1. Can someone explain how I can get TWRP back onto the system and get my USB icon back so I can keep up to date.
Your assistance will be gratefully appreciated.
Cheers
Asus TF300T
The 4.2 bootloader doesn't have a separate fastboot mode. As soon as you're in the bootloader, fastboot starts. There's no icon to select because it's already in fastboot mode.
speye007 said:
Hi Guys,
I have 4.2.1 installed and want to move up to 4.2.2 however i now notice that when I try to boot back into recovery I have no USB icon to reinstall TWRP. I used TWRP 2.5 to install 4.2.1. Can someone explain how I can get TWRP back onto the system and get my USB icon back so I can keep up to date.
Your assistance will be gratefully appreciated.
Cheers
Asus TF300T
Click to expand...
Click to collapse
The new 4.2 bootloader has no usb icon. When you enter the bootloader do not press any keys you will automatically enter usb mode. Watch the upper left for a message showing fastboot started..
---------- Post added at 10:34 AM ---------- Previous post was at 10:33 AM ----------
EndlessDissent said:
The 4.2 bootloader doesn't have a separate fastboot mode. As soon as you're in the bootloader, fastboot starts. There's no icon to select because it's already in fastboot mode.
Click to expand...
Click to collapse
You were to quick for me that time.
tobdaryl said:
The new 4.2 bootloader has no usb icon. When you enter the bootloader do not press any keys you will automatically enter usb mode. Watch the upper left for a message showing fastboot started..
---------- Post added at 10:34 AM ---------- Previous post was at 10:33 AM ----------
You were to quick for me that time.
Click to expand...
Click to collapse
Thanks I'll let you know it goes
speye007 said:
Thanks I'll let you know it goes
Click to expand...
Click to collapse
Well thanks that did work however I now have and issue with TWRP wanting a password and I've tried the
http://forum.xda-developers.com/showthread.php?t=2187982
Click to expand...
Click to collapse
fix but I get a dual screen of TWRP and can't do a thing with it is there a way that I can wipe the unit and start again this is getting frustrating and from what I can see no one from TWRP is offereing any suggestions to fix this issue either.....very frustrating as this is my daily
Your assistance would be gratefully appreciated
Cheers
speye007 said:
Well thanks that did work however I now have and issue with TWRP wanting a password and I've tried the fix but I get a dual screen of TWRP and can't do a thing with it is there a way that I can wipe the unit and start again this is getting frustrating and from what I can see no one from TWRP is offereing any suggestions to fix this issue either.....very frustrating as this is my daily
Your assistance would be gratefully appreciated
Cheers
Click to expand...
Click to collapse
The reason no one from TWRP is fixing it is because there's nothing to fix. It wasn't a TWRP bug. It was ASUS's bug, and they fixed it in the most recent OTA update. I would suggest using fastboot to flash back to stock to get your stock recovery back, then update to the most recent OTA, then you can flash TWRP back.
Edit: What I just said was actually kind of in the OP of the thread to which you linked, in bright red letters. It said that you need to be on the very latest OTA for that version of TWRP to work. In fact, those were, more-or-less the very first words in the post.
EndlessDissent said:
The reason no one from TWRP is fixing it is because there's nothing to fix. It wasn't a TWRP bug. It was ASUS's bug, and they fixed it in the most recent OTA update. I would suggest using fastboot to flash back to stock to get your stock recovery back, then update to the most recent OTA, then you can flash TWRP back.
Edit: What I just said was actually kind of in the OP of the thread to which you linked, in bright red letters. It said that you need to be on the very latest OTA for that version of TWRP to work. In fact, those were, more-or-less the very first words in the post.
Click to expand...
Click to collapse
Hi sorry its taken me time to get back. I've had some issues with this I now get a double TWRP screen that I can't do anything with and when I can get back to a normal screen it asks for a password all the time and I've tried to factory reset from inside (not from twrp) and it does nothing at all
So I'd like to try and reset back to factory and start again if thats possible? And is there a good tutorial on this?
Cheers & thank you for your assistance
speye007 said:
Hi sorry its taken me time to get back. I've had some issues with this I now get a double TWRP screen that I can't do anything with and when I can get back to a normal screen it asks for a password all the time and I've tried to factory reset from inside (not from twrp) and it does nothing at all
So I'd like to try and reset back to factory and start again if thats possible? And is there a good tutorial on this?
Cheers & thank you for your assistance
Click to expand...
Click to collapse
If you want to go back to stock, just flash the stock firmware in fastboot. There are lots of guides for flashing stock ROMs throughout the forum.
EndlessDissent said:
If you want to go back to stock, just flash the stock firmware in fastboot. There are lots of guides for flashing stock ROMs throughout the forum.
Click to expand...
Click to collapse
I found the issue you need to go to this version of TWRP (which I may add is not on the download list fromTWRP) http://goo.im/devs/OpenRecovery/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
I now have TWRP working and I'm running 10.6.1.8 however I find that I can not factory reset or use TWRP to upgrade firmware to 10.6.1.15 or any other ROM. The device says "Device is unlocked" & I'm also having an issue trying to locate a good tutorial on how to flash new firmware or kernel with fastboot. If anyone knows of a great tutorial that is easy to follow and also how I can obtain any of the required .img files that would be great.
This is getting frustrating now not being able to flash anything at all (angry)
I'm also getting an error message when I try to use the Asus unlock apk (An unknown error occurs,which maybe a network connection issue. Please wait and try again later) yes done toooo many times.
I've now even tried to flash CWM instead of TWRP and nothing ....the device boots fine and works fine I just can not factory reset, or install a new or updated rom from TWRP.
Message from TWRP :
Updating partition details...
Simulating actions...
Updating partition details...
and TWRP says Successful but nothing happens
can someone help me out here before I rip what little hair I still have out ggggrrrrrrrr
Hi,
Can someone help? My TF300T is bricked and I can't access fastboot or recovery. I can go into APX and I have the nvflash files backup.
I followed this guide http://forum.xda-developers.com/showthread.php?p=40432730
It goes all ok, then when I try to get into recovery (turning the tablet on with vol. down pressioned) it displays:
Platform Pre OS Boot configuration...
Cold booting Linux.
And then it try to boot the stock ICS rom I restaured with nvflash, but freezes on ASUS logo http://puu.sh/3Z522.jpg
I already left it for 1+ hours.
Thanks
foxrlx said:
Hi,
Can someone help? My TF300T is bricked and I can't access fastboot or recovery. I can go into APX and I have the nvflash files backup.
I followed this guide http://forum.xda-developers.com/showthread.php?p=40432730
It goes all ok, then when I try to get into recovery (turning the tablet on with vol. down pressioned) it displays:
Platform Pre OS Boot configuration...
Cold booting Linux.
And then it try to boot the stock ICS rom I restaured with nvflash, but freezes on ASUS logo http://puu.sh/3Z522.jpg
I already left it for 1+ hours.
Thanks
Click to expand...
Click to collapse
Did you use the first set of recovery instructions or the second?
Which firmware version did you unblob to get your files?
Which recovery did you flash?
tobdaryl said:
Did you use the first set of recovery instructions or the second?
Which firmware version did you unblob to get your files?
Which recovery did you flash?
Click to expand...
Click to collapse
I already tried the first method some times:
using blob from official ICS from Asus (versions 9.4.3.30 and 9.4.3.29)
about the recovery I tried ICS CWM recovery, 2.6 ICS TWRP recovery and 2.4 ICS TWRP recovery
without success accessing that menu where I can select recovery, fastboot, android or wipe.
when I try turning the tablet on holding Vol. Down I get that message on my first post.
Then I tried once the second method (the one using bricksafe.img). Still the same.
foxrlx said:
I already tried the first method some times:
using blob from official ICS from Asus (versions 9.4.3.30 and 9.4.3.29)
about the recovery I tried ICS CWM recovery, 2.6 ICS TWRP recovery and 2.4 ICS TWRP recovery
without success accessing that menu where I can select recovery, fastboot, android or wipe.
when I try turning the tablet on holding Vol. Down I get that message on my first post.
Then I tried once the second method (the one using bricksafe.img). Still the same.
Click to expand...
Click to collapse
I can't duplicate your findings. The guide works properly for me, every time.
I'm lost.
If there are no other replies that help I would suggest posting in the nvflash thread.
tobdaryl said:
I can't duplicate your findings. The guide works properly for me, every time.
I'm lost.
If there are no other replies that help I would suggest posting in the nvflash thread.
Click to expand...
Click to collapse
I also tried to use the latest update from asus using a JB TWRP or JB CWM recovery.
The problem still the same.
I can't post on dev's forum.
If there's no problem could you please post link to this thread there?
Thanks
foxrlx said:
I also tried to use the latest update from asus using a JB TWRP or JB CWM recovery.
The problem still the same.
I can't post on dev's forum.
If there's no problem could you please post link to this thread there?
Thanks
Click to expand...
Click to collapse
In my nvflash restore guide I have removed my second restore method till further study can be done.
tobdaryl said:
In my nvflash restore guide I have removed my second restore method till further study can be done.
Click to expand...
Click to collapse
Should I post about this on your thread about the nvflash?
foxrlx said:
Should I post about this on your thread about the nvflash?
Click to expand...
Click to collapse
I don't think it will make a difference.
I have not forgotten you. I glanced through the nvflash thread and found little attempt to help in most cases. I have been through the 100 and the 201 threads and have started through the 700.
I have started reading through the complete 300 thread and taking notes. I did make one addition to my first method of recovery. You might want to try it again.
I have spent several hours and feel I am near completion. I have a new method on paper but I still need to test on my tablet and refine it before suggesting for anyone else to use.
Could you tell me how you came to this point with your tablet? It might give me some insight into what needs to be done.
tobdaryl said:
I don't think it will make a difference.
I have not forgotten you. I glanced through the nvflash thread and found little attempt to help in most cases. I have been through the 100 and the 201 threads and have started through the 700.
I have started reading through the complete 300 thread and taking notes. I did make one addition to my first method of recovery. You might want to try it again.
I have spent several hours and feel I am near completion. I have a new method on paper but I still need to test on my tablet and refine it before suggesting for anyone else to use.
Could you tell me how you came to this point with your tablet? It might give me some insight into what needs to be done.
Click to expand...
Click to collapse
Thank you very much.
Well, I was on some CM10.1 nightly with TWRP, I was going to update to the latest nightly and wipe. I misclicked and wiped the /system.
I installed the CM10.1 and gapps ok. But it wasn't working, the boot was looping.
Then the recovery wasn't working either and there was no option to fastboot.
The first time I tried restoring the nvflash it worked all ok. Then I updated to JB and the recovery was broken again, so I tried the nvflash restore again and that's where everything started.
I tried that new method, only difference the wheelie didn't allow me to use --resume so I used the -r.
But the problem still the same
Maybe that menu where I select recovery, fastboot, wipe, android is broken? because that message shows only when I try to boot holding vol. down.
I already flashed lots of gadgets and never had this kind of problem, I think I wasn't paying much attention when I wiped the /system hahah
foxrlx said:
Thank you very much.
Well, I was on some CM10.1 nightly with TWRP, I was going to update to the latest nightly and wipe. I misclicked and wiped the /system.
I installed the CM10.1 and gapps ok. But it wasn't working, the boot was looping.
Then the recovery wasn't working either and there was no option to fastboot.
The first time I tried restoring the nvflash it worked all ok. Then I updated to JB and the recovery was broken again, so I tried the nvflash restore again and that's where everything started.
I tried that new method, only difference the wheelie didn't allow me to use --resume so I used the -r.
But the problem still the same
Maybe that menu where I select recovery, fastboot, wipe, android is broken? because that message shows only when I try to boot holding vol. down.
I already flashed lots of gadgets and never had this kind of problem, I think I wasn't paying much attention when I wiped the /system hahah
Click to expand...
Click to collapse
Your bootloader (ebt) the menu you mention with fastboot etc. was replaced in the first method.
Your files from blobunpack are from ICS 9.4.3.30?
The asus tablets are an odd breed. Asus created a mess with the bootloader and have continued to make it worse and worse.
Here is some info you may find useful that I posted in another thread.
Bootloaders have been an issue on this tablet since 4.1 (JB) arrived.
I swap at will between the JB bootloaders using stock recovery - next bootloader up or down.
Yes, be careful! Match bootloader, rom and twrp.
Here are the bootloaders, stock roms, and twrp- now you have to match your custom rom.
4.0 bootloader - 9.4.3.17, 9.4.3.29, 9.4.3.30 - twrp openrecovery-twrp-2.5.0.0-tf300t-ICS.blob
4.1 bootloader - 10.4.2.9, 10.4.2.13, 10.4.2.17, 10.4.2.18, 10.4.2.20 - twrp openrecovery-twrp-2.5.0.0-tf300t-JB.blob
4.2 bootloader - 10.6.1.8 - twrp openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
4.2.1 bootloader - 10.6.1.15.3, 10.6.1.27.1 - twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
tobdaryl said:
Your bootloader (ebt) the menu you mention with fastboot etc. was replaced in the first method.
Your files from blobunpack are from ICS 9.4.3.30?
The asus tablets are an odd breed. Asus created a mess with the bootloader and have continued to make it worse and worse.
Here is some info you may find useful that I posted in another thread.
Bootloaders have been an issue on this tablet since 4.1 (JB) arrived.
I swap at will between the JB bootloaders using stock recovery - next bootloader up or down.
Yes, be careful! Match bootloader, rom and twrp.
Here are the bootloaders, stock roms, and twrp- now you have to match your custom rom.
4.0 bootloader - 9.4.3.17, 9.4.3.29, 9.4.3.30 - twrp openrecovery-twrp-2.5.0.0-tf300t-ICS.blob
4.1 bootloader - 10.4.2.9, 10.4.2.13, 10.4.2.17, 10.4.2.18, 10.4.2.20 - twrp openrecovery-twrp-2.5.0.0-tf300t-JB.blob
4.2 bootloader - 10.6.1.8 - twrp openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
4.2.1 bootloader - 10.6.1.15.3, 10.6.1.27.1 - twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
Click to expand...
Click to collapse
I unpacked the 9.4.3.30 again
Downloaded the TWRP 2.5 ICS blob file
and tried the nvflash again with those files, the problem still the same.
It's weird, because the first time it worked perfectly. with the same files.
I'll try using the 10.6.1.27.1 and TWRP 2.5 JB
foxrlx said:
I unpacked the 9.4.3.30 again
Downloaded the TWRP 2.5 ICS blob file
and tried the nvflash again with those files, the problem still the same.
It's weird, because the first time it worked perfectly. with the same files.
I'll try using the 10.6.1.27.1 and TWRP 2.5 JB
Click to expand...
Click to collapse
I'm still refining my next offer. I'll give you a shout when I'm finished - testing is in progress but slow.
The only way I found to emulate your tablet was to flash cm 10.1 while running stock ICS 9.4.3.30. The next hour was spent just getting the computer and tablet to communicate. I had to boot linux and use it to gain access. Once I used linux to nvflash 9.4.3.30 bootloader, boot, system, and twrp recovery windows recognized the tablet again but I still had no bootloader menu or useable tablet.
About an hour and a half later I had a fully functional tablet. I can't post or suggest the method I used used to recover as it borders on insanity.
Later tonight I'll try for a much safer and simpler method.
Thanks
I tried with the JB files. But no success
I will wait for your new method
Sent from my Nexus 4
foxrlx said:
Thanks
I tried with the JB files. But no success
I will wait for your new method
Sent from my Nexus 4
Click to expand...
Click to collapse
You're going to need some other help. I have not been able to find anything that is repeatable even with the same brick each time.
Go ahead and post in my nvflash thread and I'll let your post pass. Maybe someone else will respond (it is not a popular thread to post, although many have used the info).
How many posts do you need to be able to post in the developers section?
tobdaryl said:
You're going to need some other help. I have not been able to find anything that is repeatable even with the same brick each time.
Go ahead and post in my nvflash thread and I'll let your post pass. Maybe someone else will respond (it is not a popular thread to post, although many have used the info).
How many posts do you need to be able to post in the developers section?
Click to expand...
Click to collapse
Ok, thanks for all the helping.
I think at least 10 posts.
Is there any way to erase everything before flashing the files? I don't know, maybe there are some data getting in the way.
Sent from my Nexus 4
foxrlx said:
Ok, thanks for all the helping.
I think at least 10 posts.
Is there any way to erase everything before flashing the files? I don't know, maybe there are some data getting in the way.
Sent from my Nexus 4
Click to expand...
Click to collapse
Erasing can be done with fastboot.
Here are the ones I know.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 reboot
I just finished reading the tf700 nvflash thread. They are using the following commands as a standard and I have seen these used on our tablet. I can't prove this at the moment as I have a screen issue.
wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 14 factory-config.img
nvflash --resume --download 7 unlock-token.img
nvflash --resume –go
I'll look through my notes and give you the info I have for the Nvflash IRC.
tobdaryl said:
Erasing can be done with fastboot.
Here are the ones I know.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 reboot
I just finished reading the tf700 nvflash thread. They are using the following commands as a standard and I have seen these used on our tablet. I can't prove this at the moment as I have a screen issue.
wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 14 factory-config.img
nvflash --resume --download 7 unlock-token.img
nvflash --resume –go
I'll look through my notes and give you the info I have for the Nvflash IRC.
Click to expand...
Click to collapse
Hi,
But I can't access fastboot mode
I tried those commands alone and tried combining with the ones on your guide but no success.
I guess I'm out of luck.
When you restore your blob files, does your tablet boot ok? Because mine keep on that ASUS logo with that rotating loading image.
foxrlx said:
Hi,
But I can't access fastboot mode
I tried those commands alone and tried combining with the ones on your guide but no success.
I guess I'm out of luck.
When you restore your blob files, does your tablet boot ok? Because mine keep on that ASUS logo with that rotating loading image.
Click to expand...
Click to collapse
Sometimes I have the booting problem you describe as well as boot looping. I can usually get a normal boot by pressing volume down and pressing the reset. Then let the tablet cold boot. If that fails I'll use wheelie and then nvflash to reboot.
wheelie -r --blob blob.bin
nvflash --resume --go
tobdaryl said:
Sometimes I have the booting problem you describe as well as boot looping. I can usually get a normal boot by pressing volume down and pressing the reset. Then let the tablet cold boot. If that fails I'll use wheelie and then nvflash to reboot.
wheelie -r --blob blob.bin
nvflash --resume --go
Click to expand...
Click to collapse
I tried several times but nothing different happened, I don't know what's happening that my bootloader menu doesn't show up.
What could interfere with this? Besides the blob.ebt file.
When you restore your device what rom and recovery you use?
Thanks.
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've been trying to get nvflash access though this guide [androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/] but after doing "Step 1: Flash AndroidRoot BL" and rebooting the device it gets stuck at the ASUS logo screen (without the spinning wheel).
It's an unlocked TF700T successfully downgraded from JB to Firmware .30.
Did anyone else encounter this problem and has a solution?
I'm a little afraid to do the whole flashing proceedure through fastboot again without knowing if that's a good idea.
Why did you downgrade to an ICS firmware???
Which guide did you follow? Step 1 should have been to flash the recovery flatline_device image. And then you use it to flash the modded bootloader (which is JB 10.6.14.4 BL btw).
Can you still boot into fastboot and the recovery?
Here are the official instructions for nvflash: https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Sent from my K00C using Tapatalk
Thanks for the quick reply.
I downgraded because a guide told me (here on XDA) that to root my device i'd have to downgrade to ICS because of some exploit, which has been apperantly closed in JB, for 'motochopper'. Well that's what I remember.
My Firefox and PC crashed and I lost my tabs so I couldn't find that guide right now...
For nvflash I read exacly that guide you refered to.
I am still able to get to the flashed flatline recovery and since the usb icon (fastboot) isn't there where the 3 icons are showing I assume it's running by default (?).
miduku said:
Thanks for the quick reply.
I downgraded because a guide told me (here on XDA) that to root my device i'd have to downgrade to ICS because of some exploit, which has been apperantly closed in JB, for 'motochopper'. Well that's what I remember.
My Firefox and PC crashed and I lost my tabs so I couldn't find that guide right now...
For nvflash I read exacly that guide you refered to.
I am still able to get to the flashed flatline recovery and since the usb icon (fastboot) isn't there where the 3 icons are showing I assume it's running by default (?).
Click to expand...
Click to collapse
Yes you are on fastboot by default now.
So, what could you suggest?
Should I (be able to) upgrade back to JB, to 10.6.14.4?
There's no need for root in any of this. Downgrading was what messed you up I believe.
I think you are ok. That you have only 3 icons indicates that the bootloader flash went fine (ICS BLs have 4). Confirm this by reading the tiny script in the upper left on the bootloader menu screen.
My guess is that this bootloader doesn't do well with ICS firmware. But the BL flash happens before Android gets booted. Did you see a blue progress bar during reboot? That would have been the bootloader installing. So it flashed ok, but then got stuck on booting the rom.
So you should be ok to proceed.
The rest of the process is done in recovery and APX mode. Shouldn't matter what ROM you have installed.
Once you generated your backups, you have to flash a bootloader and recovery for whatever rom you want to run.
I would recommend you flash the bootloader/TWRP package from the CROMi-X thread. That BL may boot the ICS rom you have currently installed, but even if it get's stuck on booting the rom - don't worry.
Same process: bootloader and recovery get installed before Android boots.
Just boot back into TWRP and flash CROMi-X. Even if you eventually want to run something else - this would give you a stable base.
http://forum.xda-developers.com/showthread.php?t=2425383
miduku said:
So, what could you suggest?
Should I (be able to) upgrade back to JB, to 10.6.14.4?
Click to expand...
Click to collapse
jhh
yeah after flashing the AndroidRoot recovery image (flatline_tf700.img) thorugh fastboot I saw the blue bar telling me it flashed successfully. I could even reboot .
But then after flashing the AndroidRoot custom bootloader I wasn't able to reboot anymore. There was no blue bar during reboot.
The upper left corner says:
Code:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB download protocol
Hm... I was planning on having CROMBi-kk but the guide says it needs 'ASUS STOCK JB 4.2.1 BOOTLOADER VERSION 10.6.1.14.x'... so that looks like that won't happen for me unless I manage to flash it back to the stock bootloader somehow. :/
So do I understand this correctly:
With the current Firmware .30 still installed I should take the latest CROMi-X package. Flash the recovery and the bootloader over the current one and then flash the CROMi-X rom?
What about nvflash then? Will I be able to generate the blob files with TWRP? I'm asking because AndroidBoot recovery looks like a modded CW-recovery I think and it has the options 'advances > wheelie > ...' , where you do the whole "nvflash stuff".
miduku said:
The upper left corner says:
Code:
Key driver not found.. Booting OS
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.6.1.14.4-20130329" A03
Starting Fastboot USB download protocol
Click to expand...
Click to collapse
Can you get to the recovery now? Maybe you can just continue with generating the blobs.
_that said:
Can you get to the recovery now? Maybe you can just continue with generating the blobs.
Click to expand...
Click to collapse
Yes, I was able to create the wheelie blobs if that's what you mean, but I wasn't able to adb pull those. Don't know what I'm doing wrong there.
I'm not sure how to continue from here on after creating the blobs.
miduku said:
Yes, I was able to create the wheelie blobs if that's what you mean, but I wasn't able to adb pull those. Don't know what I'm doing wrong there.
I'm not sure how to continue from here on after creating the blobs.
Click to expand...
Click to collapse
I wasn't able to adb pull them either, but they are there. Serach your entire SD card for blob.bin and/or bricksafe.img and you'll find them. Can't remember where wheelie hid them.....
You have a very specialized recovery and bootloader right now which you have to change to run a rom.
To get to the latest bootloader you can either flash the bootloader/TWRP package from the CROMi-X thread or flash the latest Asus firmware file.
Then reboot.
If you want to go for CROMBi-KK you have to install TWRP 2.7
Reboot
Do a factory wipe in TWRP
Then flash CROMBi-KK
Ok got it all sorted out with alot of help.
There was alot of fastboot erasing and so on involved
and flashing of the latest Asus firmware.
Then we got the whole nvflash procedure up and running, generated and saved the blob files,
flashed TWRP and CROMBi-kk and voila.
My TF700T is up and running.
thnx for all the help
miduku said:
Ok got it all sorted out with alot of help.
There was alot of fastboot erasing and so on involved
and flashing of the latest Asus firmware.
Then we got the whole nvflash procedure up and running, generated and saved the blob files,
flashed TWRP and CROMBi-kk and voila.
My TF700T is up and running.
thnx for all the help
Click to expand...
Click to collapse
Glad to see you all sorted. How is the rom?
sbdags said:
Glad to see you all sorted. How is the rom?
Click to expand...
Click to collapse
It's faster than stock asus rom that's for sure.
I know it's not quite finished but I've noticed some bugs like:
- when using chromecast the right quicksettings panel glitches quite alot (I'm using trebuchet)
- I've noticed that occassionally the power button (on device and keyboard) doesn't work to turn off the tablet or set it to sleep. only by closing the 'netbook/tablet-keyboard-hybrid-thing' it goes to sleep. after soft-resetting it the problem was gone. I think it only happened when I accessed the glitchy quicksettings panel while using chromecast.
Other than some of the still missing features it's running quite good
I don't regret flashing this custom rom over the slow and old stock one.