[Q] Cannot install recovery on TF101G - Eee Pad Transformer Q&A, Help & Troubleshooting

Hi,
I have TF101G (WW 9.2.2.6) with ICS 4.0.3 and wanted to upgrade to JB.
For that it has to be rooted.
I downloaded 1-Click Transformer Root (http://forum.xda-developers.com/showthread.php?t=1689193) and rooted it.
Then tried to install recovery: Rogue XM Recovery 1.5.0 (CWM-based Recovery v5.0.2.8).
It installed OK. Tried backup and restore and it worked OK.
Then I wanted to install NO-NAME 4.2 or KatKiss 4.2 and both recommend installing TWRP.
But when I install TWRP (tried with 2.6.3.0 and 2.3.2.3) - tried from XM "Install ZIP", tried dd if=??? of=???
and even went to modify 1-Click and put TWRP blob instead of XM blob.
(I have noticed that all tutorials say of=/dev/block/mmcblk0p4 but 1-Click uses of=/dev/block/mmcblk0p3!!!)
Only through 1-Click I can get to TWRP for the first time only. Any other attempt to go to TWRP finished with
TWRP load screen and some script loads saying something like: "Wiping cache" ... "Clearing data" and
it makes a full factory reset. Every time I try to go to TWRP.
I even restored to stock and tried again - same result.
This is not my first device on which I am installing CM - installed on
Samsung I900 and Tab 10.1, HTC Desire and SE Xperia X8.
What is the highest CM I can istnall from XM 1.5.0?
Can I install 4.2 with XM 1.5.0?
I am doing something wrong here, but what?
Has anyone installed TWRP 2.6.x.x from XM 1.5.0?
Thanks all,
--
Q

You CAN install 4.2 or 4.3 ROMs with XM.
The issue comes in when you go to flash and update, you will get your data that was in the /sdcard/ will appear in the /sdcard/0/ directory. This has to do with the new file structure for the multi users.
If you are already rooted, you can try the terminal method using twrp.blob.
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Reboot normally (not to recovery) to complete the install. Then reboot to recovery.
Also, does your tablet boot to recovery by default? If so, this can cause issues trying to flash a recovery update.

frederuco said:
You CAN install 4.2 or 4.3 ROMs with XM.
Click to expand...
Click to collapse
OK, I'll give it a try!
The issue comes in when you go to flash and update, you will get your data that was
in the /sdcard/ will appear in the /sdcard/0/ directory. This has to do with the new file structure for the multi users.
Click to expand...
Click to collapse
Data is not an issue. I can wipe every upgrade.
If you are already rooted, you can try the terminal method using twrp.blob.
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Reboot normally (not to recovery) to complete the install. Then reboot to recovery.
Click to expand...
Click to collapse
I have tried that. Rebooted several times to system, and even performed a cold boot.
Every time I try to boot to recovery - TWRP performs a factory restore.
One odd thing I have noticed: when I flashed stock or XM recovery after
reboot the blue line lasted a bit. But with TWRP it just flashed quickly,
like it just set some flag and it will do its doing some time later.
Also, does your tablet boot to recovery by default? If so, this can cause issues trying to flash a recovery update.
Click to expand...
Click to collapse
No, it behaves normally. Only XM recovery functions well, so I will stick with it while I can.
Thanks for tips. I will report back with 4.2 progress

LOL, don't upgrade recoveries and roms late at night.
All was OK all along. I was pressing wrong buttons:
VOL.DOWN+POWER - PAUSE - VOL.DOWN - VOL.UP - VOL.UP
instead of
VOL.DOWN+POWER - VOL.UP
I accused of TWRP performing factory resets and that is what it supposed to do.
XM recovery did not know how to do factory reset automatically - and that confused me.
Installed TWRP 2.6.3.0 again and KatKiss 4.2.2. I did not check 3G yet but
I have noticed some screen flickering.
Should I flash fsync_on.zip?

quazy99 said:
LOL, don't upgrade recoveries and roms late at night.
All was OK all along. I was pressing wrong buttons:
VOL.DOWN+POWER - PAUSE - VOL.DOWN - VOL.UP - VOL.UP
instead of
VOL.DOWN+POWER - VOL.UP
I accused of TWRP performing factory resets and that is what it supposed to do.
XM recovery did not know how to do factory reset automatically - and that confused me.
Installed TWRP 2.6.3.0 again and KatKiss 4.2.2. I did not check 3G yet but
I have noticed some screen flickering.
Should I flash fsync_on.zip?
Click to expand...
Click to collapse
Yes, flash fsync_on.zip if you want extra data security. No, if you want better performance with the risk of data corruption if you get random reboots or something.

Related

Infinity bootlooping, seems unfixable

First off, let me start out by saying that the Infinity is running on what is possibly the worst software ever designed. Props, Asus. You've made my life hell until the last second.
So, here's my problem. The tablet was working fine 24 hours ago. I turned it off last night, turned it on this morning, working great on CROMi-Xeno (which is awesome, it actually makes the tablet bearable.) and played on it for a while before turning off again. While playing it, I noticed it lag a little more than usual, so I decided to cold boot it. Booted bootloader, hit cold boot, and.... bootlooping. Awesome. No biggie, I'll just restore a backup. I waited for it to restore, and when it was finished, wiped cache and Dalvik, and.... bootlooping again. I tried wiping system and data. Still bootlooping. I downloaded Asus 's official firmware from their website, and flashed. Bootlooping. Someone help me fix this and get it back to stock firmware, so I can sell it and be done with it once and for all. I will never buy another Asus product again.
greydelta38 said:
First off, let me start out by saying that the Infinity is running on what is possibly the worst software ever designed. Props, Asus. You've made my life hell until the last second.
So, here's my problem. The tablet was working fine 24 hours ago. I turned it off last night, turned it on this morning, working great on CROMi-Xeno (which is awesome, it actually makes the tablet bearable.) and played on it for a while before turning off again. While playing it, I noticed it lag a little more than usual, so I decided to cold boot it. Booted bootloader, hit cold boot, and.... bootlooping. Awesome. No biggie, I'll just restore a backup. I waited for it to restore, and when it was finished, wiped cache and Dalvik, and.... bootlooping again. I tried wiping system and data. Still bootlooping. I downloaded Asus 's official firmware from their website, and flashed. Bootlooping. Someone help me fix this and get it back to stock firmware, so I can sell it and be done with it once and for all. I will never buy another Asus product again.
Click to expand...
Click to collapse
I'm wondering if my version of TWRP is too old or something. Can anyone explain in detail how to update to a newer version of TWRP or install CWM in order for flashing to fully work?
greydelta38 said:
I'm wondering if my version of TWRP is too old or something. Can anyone explain in detail how to update to a newer version of TWRP or install CWM in order for flashing to fully work?
Click to expand...
Click to collapse
what version do you currently have, just download the .blob from twrp's site boot into fastboot and run "fastboot flash recovery *name of blob*.blob"
JoinTheRealms said:
what version do you currently have, just download the .blob from twrp's site boot into fastboot and run "fastboot flash recovery *name of blob*.blob"
Click to expand...
Click to collapse
Yeah - I'm also wondering what bootloader you are running with it.
If you are not current on either flash the bootloader/TWRP package from CROMi-X OP, boot back into system, let it bootloop if it does, boot back into TWRP and reflash the rom.
That seems like it would be the only explanation, but now it won't even boot into recovery. I can get it into fastboot, but as soon as I select recovery image it shows the firmware upgrade symbol and then immediately shows the Android Error symbol, and sticks there until I hard power down. When I'm in fastboot, here's what I'm gonna do:
1. connect fastbooted Infinity to pc with all necessary drivers installed
2. download filename.blob from TWRP's website for the Infinity
3. on command console enter -fastboot flash recovery filename.blob- and it will push the recovery through fastboot hopefully
Is that correct? I'm under the impression that as long as I can get to the fastboot menu, ANYTHING is repairable.
greydelta38 said:
That seems like it would be the only explanation, but now it won't even boot into recovery. I can get it into fastboot, but as soon as I select recovery image it shows the firmware upgrade symbol and then immediately shows the Android Error symbol, and sticks there until I hard power down. When I'm in fastboot, here's what I'm gonna do:
1. connect fastbooted Infinity to pc with all necessary drivers installed
2. download filename.blob from TWRP's website for the Infinity
3. on command console enter -fastboot flash recovery filename.blob- and it will push the recovery through fastboot hopefully
Is that correct? I'm under the impression that as long as I can get to the fastboot menu, ANYTHING is repairable.
Click to expand...
Click to collapse
The command is
fastboot -i 0x0B05 flash recovery filename.blob
Since you can boot into the bootloader, check the version# and make sure you flash a compatible recovery.
Most of the time, as long as you can get into the BL, it's fixable. But to make it unbrickable you need nvFlash. And that's just become possible for or tablet on JB. May be a project for once you got this problem fixed: http://forum.xda-developers.com/showthread.php?t=2455925
I suspect you need to format data to fix the issues (you'll lose everything on the internal sd card) but before you do follow bernd's recommendation and get TWRP on there (you wiped it out when you flashed ASUS stock) and then use the file explorer in TWRP to copy anything important to an external SD and make sure the cromi-x rom is on sd too. Then format data from the wipe menu and reinstall. You'll be back to normal in no time. :good:
BTW You may have got some corruption from turning f-sync off.
berndblb said:
The command is
fastboot -i 0x0B05 flash recovery filename.blob
Since you can boot into the bootloader, check the version# and make sure you flash a compatible recovery.
Most of the time, as long as you can get into the BL, it's fixable. But to make it unbrickable you need nvFlash. And that's just become possible for or tablet on JB. May be a project for once you got this problem fixed: http://forum.xda-developers.com/showthread.php?t=2455925
Click to expand...
Click to collapse
sbdags said:
I suspect you need to format data to fix the issues (you'll lose everything on the internal sd card) but before you do follow bernd's recommendation and get TWRP on there (you wiped it out when you flashed ASUS stock) and then use the file explorer in TWRP to copy anything important to an external SD and make sure the cromi-x rom is on sd too. Then format data from the wipe menu and reinstall. You'll be back to normal in no time. :good:
BTW You may have got some corruption from turning f-sync off.
Click to expand...
Click to collapse
I tried wiping internal before recovery was lost and it didn't work. I suspected that some problems arose from turning fsync off too. I'm pushing TWRP 2.6 to the Infinity now, will try flashing your excellent rom again and see if it takes without bootlooping.
greydelta38 said:
I tried wiping internal before recovery was lost and it didn't work. I suspected that some problems arose from turning fsync off too. I'm pushing TWRP 2.6 to the Infinity now, will try flashing your excellent rom again and see if it takes without bootlooping.
Click to expand...
Click to collapse
You need to specifically format data in twrp not just wipe data. Only formatting will restore the device now once data corruption has occurred.

[Q] Can't Flash or Restore Backup

I originally had Katkiss 4.3 v19 and it was working fine. I then wanted to update to the recent 4.3.1 v27 but when I tried to flash the new ROM, it says that it can't open the zip file and failed. I backed up beforehand, so I wiped the cache and dalvik. I then tried to flash the ROM again, but it still says failed. I went to restore the backup to go back and for some reason, it is also failing.
I have TWRP 2.6.0.0 and I am stuck in recovery where I can't flash anything. Not even when I wanted to flash to stock.
I have the Asus EEE transformer tf101 tablet.
How do I fix this?
Please Help.
Are you trying to flash from Micro SDCard ?
Maybe the card has corrupted - try formatting the card in a PC, then copy #27 back to it, and try flashing again
Or try another MicroSD Card
*Detection* said:
Are you trying to flash from Micro SDCard ?
Maybe the card has corrupted - try formatting the card in a PC, then copy #27 back to it, and try flashing again
Or try another MicroSD Card
Click to expand...
Click to collapse
I did this and it says successful but I don't think it's completely flashed because the last line says E:Unable to mount '/staging'. Plus when I reboot, it just goes back to recovery. I flashed SuperSU but it didn't change anything.
EDIT: Ok. So I tried flashing any rom and it says 'successful', yet it seemed like it flashed the rom too quickly. Afterwards, I'd reboot but it just goes from the Eee transformer logo to twrp recovery. This happens to all of the 'successful' flashes. When I tried to flash the stock rom, it would just say failed.
I really don't know what to do at this point. I tried formatting the SD card, changing the SD card, reinstalling twrp using the EasyRecovery app and I wiped my internal and external data (which I think is the problem and IDK how to recover them). I even tried flashing a new recovery (CWM) and, like the other 'successful' flashes, still goes back to TWRP.
gigases said:
I did this and it says successful but I don't think it's completely flashed because the last line says E:Unable to mount '/staging'. Plus when I reboot, it just goes back to recovery. I flashed SuperSU but it didn't change anything.
EDIT: Ok. So I tried flashing any rom and it says 'successful', yet it seemed like it flashed the rom too quickly. Afterwards, I'd reboot but it just goes from the Eee transformer logo to twrp recovery. This happens to all of the 'successful' flashes. When I tried to flash the stock rom, it would just say failed.
I really don't know what to do at this point. I tried formatting the SD card, changing the SD card, reinstalling twrp using the EasyRecovery app and I wiped my internal and external data (which I think is the problem and IDK how to recover them). I even tried flashing a new recovery (CWM) and, like the other 'successful' flashes, still goes back to TWRP.
Click to expand...
Click to collapse
The /staging/ error is normal, nothing to worry about.
Question, if you shut down the tablet from recovery. Then turn it on with a 3 second power button press, does it go directly to recovery?
If so, this is causing your tablet NOT to finish the flash when it reboots. It needs to reboot normally and you should see the Eee Pad logo with a progress indicator.
If you do have a recovery boot loop, try this. Boot to recovery and go to the Advanced section and open a terminal window.
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Then reboot normally (not to recovery). Then after it tries to boot not into recovery, boot back to recovery and try restoring your 019 backup.
frederuco said:
The /staging/ error is normal, nothing to worry about.
Question, if you shut down the tablet from recovery. Then turn it on with a 3 second power button press, does it go directly to recovery?
If so, this is causing your tablet NOT to finish the flash when it reboots. It needs to reboot normally and you should see the Eee Pad logo with a progress indicator.
If you do have a recovery boot loop, try this. Boot to recovery and go to the Advanced section and open a terminal window.
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
Then reboot normally (not to recovery). Then after it tries to boot not into recovery, boot back to recovery and try restoring your 019 backup.
Click to expand...
Click to collapse
Yes. When I reboot/shutdown from recovery, it shows the eee pad and nvidia logo on the bottom and then goes to recovery. I did what you said with the terminal window. I also typed in the code. and it says:
5+0 records in
5+0 records out
5 bytes (5B) copied,
0.006015 seconds, 831B/s
Afterwards, I rebooted normally and it still goes back to recovery. It doesn't even go to the 'ASUS' logo where there is a wheel on the bottom.
gigases said:
Yes. When I reboot/shutdown from recovery, it shows the eee pad and nvidia logo on the bottom and then goes to recovery. I did what you said with the terminal window. I also typed in the code. and it says:
5+0 records in
5+0 records out
5 bytes (5B) copied,
0.006015 seconds, 831B/s
Afterwards, I rebooted normally and it still goes back to recovery. It doesn't even go to the 'ASUS' logo where there is a wheel on the bottom.
Click to expand...
Click to collapse
May need to do it from an ADB shell, but adb shell is blocked on TWRP 2.6.X.X for security reasons.
I would suggest flashing TWRP again using EasyFlasher. See my guide here: www.transformerforums.com/forum/asu...nt/31927-frederucos-guide-root-rom-tf101.html . Grab one of the repacked versions with TWRP 2.6 and you should be back in business in no time.
I did everything and it all seemed fine. Now I'm in a bootloop. I used the TWRP 2.6.3.0 EasyFlasher
Okay. I just tried other recoveries (CWM and Rogue) and they seemed to go well. I tried flashing, yet it still does the same thing as before where it goes to the logo and then to the recovery.
gigases said:
I did everything and it all seemed fine. Now I'm in a bootloop. I used the TWRP 2.6.3.0 EasyFlasher
Okay. I just tried other recoveries (CWM and Rogue) and they seemed to go well. I tried flashing, yet it still does the same thing as before where it goes to the logo and then to the recovery.
Click to expand...
Click to collapse
At this point, I would try restoring stock using EasyFlasher. Just download the asus firmware file and leave it as is (do not unzip) and put it in the asusupdate folder in EasyFlasher.
Once you flash back to stock and can boot, then flash TWRP with EasyFlasher and you should be good to go.
frederuco said:
At this point, I would try restoring stock using EasyFlasher. Just download the asus firmware file and leave it as is (do not unzip) and put it in the asusupdate folder in EasyFlasher.
Once you flash back to stock and can boot, then flash TWRP with EasyFlasher and you should be good to go.
Click to expand...
Click to collapse
That did it. I flashed back to stock and it can boot again. I'll flash TWRP again.:fingers-crossed: Thank You
Any time! I have a few EasyFlashers with newer versions of TWRP in the EasyFlasher thread. Start and the end and read backwards to find them.

[Q] Can't flash TF101 (Rooted, TWRP2.7.0.1)

I have a rooted (Superuser 3.1.3) TF101 with TWRP 2.7.0.1. I HAD Katkiss 4.3 installed. One day the tablet locked up and then starting bootlooping. I went into recovery, wiped everything, did factory reset, format /system.
Then I tried to reflash Katkiss 4.3_020, it failed with "set_perm: some changes failed". I then tried katkiss 4.4.2_023c - it failed with a similar error message. Tried flashing stock (US_epad-user-9.2.1.27) - same thing. The first part of the error message for all three ROMs is the same set_perm failure. The next couple of lines gives different error messages depending on the ROM. Generally something like: "E: error executing updater binary in zip".
Now I have a tablet with no ROM on it (when I tried to boot it hangs at the ASUS screen). I can get into the TWRP recovery menu just fine - I can flash other things like superuser or gapps without error. But any ROM I try to flash gives the set_perm error.
Any thoughts?
Chris
Try using Easyflasher to flash a different version of TWRP in case recovery is the problem, TWRP builds newer than 2.3.2.3 are not official builds, they have been continued by another member here once the project was abandoned by the original team
http://forum.xda-developers.com/showthread.php?t=1688012
Use Easyflasher to flash TWRP again - then try flashing KatKiss #23
Thanks but...
Easyflasher doesn't seem to work for me anymore (odd because it is what I first used to root/update my TF101). It runs and declares success - but nothing gets pushed to my device. Tried both SBK1 and SBK2. Using universal naked 0.72 and 0.73 on win7 64 bit.
I tried to find an older version of TWRP like you suggested - but I couldn't. Seems they want you to use "goo manager" from the play store... which doesn't work for me since I can't boot... And the goo website doesn't list an older TWRP for my device.
In any case, the latest TWRP seems to work in every other respect. I read somewhere that superuser can set an "immutable" bit that can survive a wipe? If true - could that be my permissions problem?
Chris
stuck on load screen
*Detection* said:
Try using Easyflasher to flash a different version of TWRP in case recovery is the problem, TWRP builds newer than 2.3.2.3 are not official builds, they have been continued by another member here once the project was abandoned by the original team
http://forum.xda-developers.com/showthread.php?t=1688012
Use Easyflasher to flash TWRP again - then try flashing KatKiss #23
Click to expand...
Click to collapse
I'm new as one can get at this and likely deserve any hammering I may get....TF1010 B70, CWM 5.8.3.4, I know I missed a step somewhere. I can't recover to 4.3 as the back up was bad, not recognized by any computer, loops to recovery and holding power and vol dn the booting to the linuz get me a long (14 hrs) flashing KatKiss boot screen.
I've tried Easyflasher aswell with no results, Please, any hope for this thing, Thanks in advance!
Sounds like your problem is a bit different - can you get into your bootloader? After voldown+power you should see some small text in the upper left of the screen then immediately hit vol up.... From there you should be able to reflash any ROM...
ldwhyte said:
I'm new as one can get at this and likely deserve any hammering I may get....TF1010 B70, CWM 5.8.3.4, I know I missed a step somewhere. I can't recover to 4.3 as the back up was bad, not recognized by any computer, loops to recovery and holding power and vol dn the booting to the linuz get me a long (14 hrs) flashing KatKiss boot screen.
I've tried Easyflasher aswell with no results, Please, any hope for this thing, Thanks in advance!
Click to expand...
Click to collapse
ChrisG12 said:
Sounds like your problem is a bit different - can you get into your bootloader? After voldown+power you should see some small text in the upper left of the screen then immediately hit vol up.... From there you should be able to reflash any ROM...
Click to expand...
Click to collapse
Thanks for your reply, when I do use that button combo, it goes into the ClockworkMod Recovery v5.8.3.4, the native one seems to be gone.
Is that a bad thing? Once in ClockworkMod - you can install a new ROM (such as KatKiss or even go back to stock). Just find the right zip file on the web, copy to your sdcard and then in clockwork select that zip file to install.... Or am I missing something?
ldwhyte said:
Thanks for your reply, when I do use that button combo, it goes into the ClockworkMod Recovery v5.8.3.4, the native one seems to be gone.
Click to expand...
Click to collapse
Ok - back to my problem - I installed a new recovery and get the same error. The two recoveries I have tried are TWRP (2.3 and 2.7.0.1) and cwm-6.0.2.1-notouch-hybrid. Both seem to work fine (and I had no trouble previously with my device running TWRP and Katkiss 4.3).
After a crash I needed to reinstall a ROM. I've copied four ROMs to my sdcard (Katkiss 4.3, Katkiss 4.4.2, Omni 4.4.2, and stock asus). I've tried all 4 ROMs with both recoveries. I get the same error when I try to install the zips. Usually it is "set_perm: some changes failed". Though stock asus zip fails with a different message "Assert failed: package_extract_file(“blob”, “/tmp/blob”)".
Any ideas on what is keeping a recovery from installing the zip? Note they can install other zips fine (i.e. other recoveries, superuser, gapps, etc.). But not the ROM.
ChrisG12 said:
Is that a bad thing? Once in ClockworkMod - you can install a new ROM (such as KatKiss or even go back to stock). Just find the right zip file on the web, copy to your sdcard and then in clockwork select that zip file to install.... Or am I missing something?
Click to expand...
Click to collapse
No it's not, but I can't get anything onto the SD card, only the ext card and I CWM will not mount it to flash from. if I'm missing something and I sure I am, Im greatful for any help, and thanks again..

[Q] Only fastboot accessible to flash / restore my TF700

Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Asphodele said:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Click to expand...
Click to collapse
Hey Your in the right place
Shoot me an email, we can review your issues and if we find a solution we can post back here to help
XDA users with there issues....
My email is everywhere talke a look around
Thx Josh
Asphodele said:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Click to expand...
Click to collapse
Sounds like you are on an old bootloader. Flash the stock rom from asus by unzipping the zip you download from their website and placing in the root folder of your micro sd and then go into rck from the bootloader menu (power + volume down whilst booting)
Or you could just flash it from recovery....
lj50036 helped me to flash a new bootloader, recovery, rom and nvflash to make it unbrickable
Not just helped he spent many times to explain me how it works and what he did.
He is very nice and this was a pleasure to talk with him, i'm happy that there's still person like that on this planet
see you !
Asphodele said:
lj50036 helped me to flash a new bootloader, recovery, rom and nvflash to make it unbrickable
Not just helped he spent many times to explain me how it works and what he did.
He is very nice and this was a pleasure to talk with him, i'm happy that there's still person like that on this planet
see you !
Click to expand...
Click to collapse
I buy a tf700 with cm 11 a few days ago i am really interessted on how this steps works. I really want to make it unbrickeable, But i dont really understand how it works. I can not enter in fastboot. at least i got cwm interface when rebooting with adb into recovery.
Can u explain how you did it?
It invovles flashing a modified bootloader and the flatline recovery and then using Wheelie to generate your nvflash blobs.
Step-by-step instructions (which you need to follow to the letter) are here:
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Stuck in boot loop, fastboot and recovery accessible
Hello,
I'm having a similar issue and I need help! Initially my tablet was rooted with Cromi-X 5.4. Then I decided to try Crombi-KK.
Here is what happened:
- Updated TWRP recovery
- Did a full wipe as recommended
- Flashing got stuck at the Crombi-KK loading sign
- Tried to reflash but TWRP wasn't detecting data partition anymore
- Instead installed the other recommended recovery CWMR.
- Flashed Crombi-KK, it worked. Played around with it for a few days, it was wonderful, fast and responsive.
- Battery died out and when I turned it back on I got a UIDs system inconsistent error.
- I found online many recommendations to reflash so I tried to do that
- Since then I'm stuck in a boot loop. I see the initial "bios" Asus logo then it restarts over and over.
- I am able to access bootloader and recovery
I've tried reflashing the asus stock blob. I've tried wiping the data through CWMR but it starts working and then it restarts. I don't know what to do anymore, so if anyone can help me, I would really appreciate it!
Thanks
Which recovery and bootloader version do you have now?
A (for KK) outdated bootloader seems the most likely culprit.
You can try save the recovery log when you flash or grab a logcat of the bootloop, but probably it'll only tell you that the recovery cannot mount /data.
Determine that you are on the correct bootloader, if not update it. If you're lucky the tablet will start right up. If it doesn't, formatting /data is the only way I know to get it back. Not just wiping - formatting it. You will loose everything on internal SD, so I hope you have a nandroid you can restore from later.
If you use TWRP 2.7+ be aware that formatting can take more than an hour. Let it finish!
For good measure, download CROMBi-KK again, check the md5 and then flash that file.
I'm on 10.6.1.14.10 bootloader which I think is the latest one
I have 6.0.4.7 CWMR
I'm trying to format data completely but when i do it in CWMR it starts and then the tablet reboots on it's own after a couple of minutes.
How can I retrieve the logs, I never had to do it before.
Thanks for your help
Mhh, getting a little more complicated.
Your BL is ok...
What do you see in CWM when you go into Mounts and Storage? What is mounted?
The recovery logs are under Advanced > show logs.
I'm at work now but from what I remember the only thing mounted was the cache. I'll double check tonight. Do you think there's any hope or I have a brand new paper weight?
yasyas said:
I'm at work now but from what I remember the only thing mounted was the cache. I'll double check tonight. Do you think there's any hope or I have a brand new paper weight?
Click to expand...
Click to collapse
Can you fastboot flash twrp?
It's much much better than CWM, has its own terminal and will be easier to offer the correct format command.
sbdags said:
Can you fastboot flash twrp?
It's much much better than CWM, has its own terminal and will be easier to offer the correct format command.
Click to expand...
Click to collapse
So I flashed TWRP and when I go in mount/storage everything is selected except for system. Should I do a format data from the wipe menu before flashing crombi-kk again?
yasyas said:
So I flashed TWRP and when I go in mount/storage everything is selected except for system. Should I do a format data from the wipe menu before flashing crombi-kk again?
Click to expand...
Click to collapse
To be in the safe side, yes, that is what I would do. TWTRP 2.7.+ takes a long time to format and it may seem the process got stuck. Give it at least 90 minutes to finish.
Then reflash CROMBi
I'm back up and running !!!
This time installing TWRP, everything was mounted (maybe my previous flash before CWMR wasn't good), did a format data, waited until it was done, flashed latest Crombi-KK and going through setup now. Hopefully won't have the same UID issue on next shutdown. I didn't enable fsync or journaling so hopefully it won't happen again.
Thanks both of you for your help!
Good deal! Happy for you!
Rooting google pixel zl

[Q&A] [RECOVERY][TF300T] TWRP 2.8.7.0 touch recovery [2015-06-23]

Q&A for [RECOVERY][TF300T] TWRP 2.8.7.0 touch recovery [2015-06-23]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][TF300T] TWRP 2.8.7.0 touch recovery [2015-06-23]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Does TWRP 2.8 (latest version 2.8.7.0) okay to start out with? Meaning, if we are at the latest version of stock (ASUS build JOP40D.US_epad-10.6.1.27-5-20130902; Android 4.2.1) and we are going to flash a custom rom for the first time, the latest versions of TWRP won't brick our devices?
It could be that I'm just confused because there were lots of older versions that reference individual Android builds (JB vs ICS). And people would say "if you have X version of Android, use Y version of TWRP or you're gonna brick it".
Can't enter twrp but everything ok
Today i flashed 2.8.7.0 img with twrp 2.8.5.0 and than reboot tablet. Than i tried enter the recovery but tablet booting normally.
In bootloader screen click RCK but say "unrecoverable bootloader error 0x00000000
Tried
Flash twrp with adb
Flash twrp with terminal
But not working. Tablet starting normally when i tried enter the recovery.
Tablet working normally. Please help me.
I am using katkiss 5.1.1
Edit: i solved problem with this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
I got sent here, so I'll try again.
I'm a little confused now, because I can't understand what is happening to my tablet. Let me explain step by step what I did, maybe one of you can figure out what is wrong.
I was running CM11 M12 with TWRP 2.8.1.0 and wanted to try the new Android 5.1. I decided to go with the latest Omnirom and found out I needed at least TWRP 2.8.5.0.
So first step would be to update TWRP. When I got at the TWRP website I read that there was something new in TWRP 2.8.4.0, so I decided to first go from .1 to .4 and then go to the latest .7. An upgrade to .4 went fine through Fastboot. Then I thought I could try the new in GUI recovery flasher, but I didn't understand it properly so I chose to go safe and flash the .7 through Fastboot.
I guess that's where I went wrong. The tablet went to recovery just fine, but in TWRP it couldn't access anything anymore. "Unable to mount" on everything. Internal storage was 0. It didn't boot to the ROM anymore.
So after some tinkering, not really sure what I did anymore, I got my access to the FS again. I had the CM11 M12 ROM still in the MicroSD, so I ran the "install ROM procedure" for that one and it booted again.
Only now I don't seem to have a recovery anymore. I can get into Fastboot, but when I send the "fastboot -i 0x0b05 flash staging twrp.blob" the tablet hangs itself. Holding power revives it and it boots to CM11M12 again. I tried to flash different TWRP versions (.4 .5 .6 and .7) but no sigar.
Does anyone have an idea how to get my recovery back?
Edit0: I tried to install the TWRP manager from the store and get a recovery from there, but the app doesn't work. It hangs when I try to tap on the "Recovery version to install" option.
Edit1: I followed the link in the post above and solved it. Next thing I did was flashing the .6 TWRP recovery and it stuck. Time to wrestle with some new roms! Thanks!
Edit2: Back to square one. The TWRP can't see anything in my internal storage. Is my storage memory going dry? "Unable to mount ###" shows up for every partition.
Edit3: And now it can see in my internal memory again... Hardware failure?
2.8.7.0 on tf300t reboot/shutdown does not work
hi, thanks for all your effort!
i just used fastboot to load 2.8.7.0 on a stock tf300t. it seems to work fine with one exception, when I choose reboot system or shutdown, but result in me booting back to twrp immediately. the only way i can shutdow/reboot is to hold the power key for 10s, then press it again to boot
everything else seems to work ok (flashing etc)....
any ideas whats going on?
thanks again
tguadagno said:
hi, thanks for all your effort!
i just used fastboot to load 2.8.7.0 on a stock tf300t. it seems to work fine with one exception, when I choose reboot system or shutdown, but result in me booting back to twrp immediately. the only way i can shutdow/reboot is to hold the power key for 10s, then press it again to boot
everything else seems to work ok (flashing etc)....
any ideas whats going on?
thanks again
Click to expand...
Click to collapse
for me it's the same..
thanks in advance
edy
aoesp3 said:
Today i flashed 2.8.7.0 img with twrp 2.8.5.0 and than reboot tablet. Than i tried enter the recovery but tablet booting normally.
In bootloader screen click RCK but say "unrecoverable bootloader error 0x00000000
Tried
Flash twrp with adb
Flash twrp with terminal
But not working. Tablet starting normally when i tried enter the recovery.
Tablet working normally. Please help me.
I am using katkiss 5.1.1
Edit: i solved problem with this http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Click to expand...
Click to collapse
Same problem! hope this works. I bought mine in US so I downloaded V10.6.1.27.5 Only for US SKU (Android 4.2).
After this is it ok to flash the latest TWRP again?
anjeu67 said:
Same problem! hope this works. I bought mine in US so I downloaded V10.6.1.27.5 Only for US SKU (Android 4.2).
After this is it ok to flash the latest TWRP again?
Click to expand...
Click to collapse
Nope. I am using lastest TWRP(2.8.7.0) now.
Hello
Can someone help me please?
For the moment i have TWRP 2.8.0.1 and i want to update it to 2.8.7.0.
First of all, i tried to update it with twrp manager.
So i open twrp manger
The install recovery screen opens and i choose for "Install Recovery".
Then i'm redirected to jmz software and then i got next screen:
Forbidden - you don't have permission to access /tf300t/ on this server.
What i'm i doing wrong?
tguadagno said:
hi, thanks for all your effort!
i just used fastboot to load 2.8.7.0 on a stock tf300t. it seems to work fine with one exception, when I choose reboot system or shutdown, but result in me booting back to twrp immediately. the only way i can shutdow/reboot is to hold the power key for 10s, then press it again to boot
everything else seems to work ok (flashing etc)....
any ideas whats going on?
thanks again
Click to expand...
Click to collapse
Same here... what gives?
Same here also.
ecb116 said:
Same here... what gives?
Click to expand...
Click to collapse
Same problem here,, no answers?

Categories

Resources