Hello
I wanted to speed up the TF201 with the help of the Kernel Adjutor. Something went wrong and after a series of frustrated attempts the only thing I get after starting the TF 201 are
- the ASUS /nvidia screen with the message "the device is unlocked"
- 4 penguins with a text "3.xxxxx message length: 9" (xxxxx being random numbers)
- the blue "teamwin" screen.
I cannot get into any other screen by pressing the volume up or down.
In June 2017 I have installed KatKiss 7.1 v023 following your tutorial. I have also made the backup recommended there.
How do I have to proceed to get the TF201 back to normal ?
Thank you very much for your help.
SwissJames
You might have to bring it back using a PC/Laptop along with Minimal ADB and Fastboot, you would have to wipe it and in the process loss everything.
Is your back-up on an external media like the micro SD or SD card?
NP
Hello Nektopoli
Thanks for your support.
backup files "bricksafe.img", "factory-config.img" and "unlock-token.img" are on the PC.
I still have the original files on micro SD from the upgrade to Android 7.1 Nougat as described in the tutorial.
After much research and many unsuccessful tries, it seems that I get lucky with lj50036's post: https://forum.xda-developers.com/showthread.php?t=2538028. After following his instructions it I was able to boot into fastboot.
At the step "fastboot -w" I got stuck: erasing cache "Command write failed <unknown error>"
So I closed the terminal and opened a new one (as described).
"fastboot erase boot" failed again "Command write failed <unknown error>"
Restarting the PC fixed the issue.
I managed to get the other steps done as well.
Now the tablet is working again with Android 4.1.1.
Next I'll upgrade it back to 7.1
Regards
SwissJames
swissjames said:
Hello Nektopoli
Thanks for your support.
backup files "bricksafe.img", "factory-config.img" and "unlock-token.img" are on the PC.
I still have the original files on micro SD from the upgrade to Android 7.1 Nougat as described in the tutorial.
After much research and many unsuccessful tries, it seems that I get lucky with lj50036's post: https://forum.xda-developers.com/showthread.php?t=2538028. After following his instructions it I was able to boot into fastboot.
At the step "fastboot -w" I got stuck: erasing cache "Command write failed <unknown error>"
So I closed the terminal and opened a new one (as described).
"fastboot erase boot" failed again "Command write failed <unknown error>"
Restarting the PC fixed the issue.
I managed to get the other steps done as well.
Now the tablet is working again with Android 4.1.1.
Next I'll upgrade it back to 7.1
Regards
SwissJames
Click to expand...
Click to collapse
Have you updated the bootloader to 10.6.1.27.1 and installed the TWRP recovery console?
NP
No, not yet. As I flashed the tab with the official ASUS firmware, everything has gone. Bootloader is 10.4.2.18 and the TWRP recovery console is gone. (RCK ends up with a "dead" android...). I'll follow the latest version of the tutorial https://forum.xda-developers.com/tr...uide-tutorial-asus-transformer-prime-t3486237 to upgrade the tab.
Can you access the tablet via a computer/laptop using and ADB fastboot program like "Minimal ADB and Fastboot" https://forum.xda-developers.com/showthread.php?t=2317790
If you can, you could manually wipe the tablet, and flash JB Bootloader 10.6.1.27.1 and TWRP 2.5, then update the TWRP and install 7.1
NP
I almost got through the guide till chapter 8. Trying to install the open_gaaps-arm 7.1 pico I got the error msg "insufficient storage space available in System partition". The error log is attached.
Maybe you have an idea what I could delete on the System partition (and how). I have tried e.g. to get rid of the gmail account, but without success.
You should wipe the system partition before flashing the ROM, SuperSU and GAPPs using TWRP when you flash a new ROM
Alternatively, if you're using a PC and Fastboot to install the ROM
the: [fastboot erase system] command will wipe the system, but I don't think it will change the System partition to F2FS
NP
I have wiped all partitions before proceeding.
The size of my "system" partition after wiping is 503 MB (8 MB used) with ext4 (510 / 116 MB used with f2f). So I opted for the ext4-variant as described in the guide.
After installing KatKiss-7.1_TF201_026.zip, 433 MB are used in "system"
After installing SuperSU-v2.82.zip, 440 MB are used in "system".
So there is not enough space left for open_gaaps-arm-7.1_pico.zip with about 125 MB unzipped.
Is there a way to increase the size of the "system" partition ? (there is enough space left in the "data" partition where I could take some...)
Or do you see other options ?
Can you get back into the recovery console?
NP
yes I think so.
By pressing power and volume - I got to the selection screen and chose RCK. Now I am in TWRP again.
When you boot into the fastboot screen, the one with the RCK icon you should see the bootloader version at the top of the screen, what version is your tablet on?
this is what mine looks like
NP
it says
<1.00 e> released by "ww_epad-10.4.2.15-20120917" A03
sj
I checked the configuration of the bootloader before I began with the upgrade from 4.1. It said 10.4.2.18-20112122...
sj
What version TWRP do you have working now?
Ok, with the working TWRP you can flash the new Bootloader v10.6.1.21.1 found here;
https://androidfilehost.com/?fid=23060877490002899
This will also install TWRP 2.5 at this point we don't want to install any thing else. Once you are on the correct bootloader and TWRP 2.5 you will need to update TWRP in two steps. First to TWRP 2.8.5.1 and then to TWRP 3.1.0-1 once you have a working TWRP you can wipe the TF and flash the 7.1.2 ROM.
NP
As you suggested I downloaded the zipped file and put it on the pc and on the sd-card.
Swiped it with the twrp 3.1.0-1 from the sd-card
looked ok. Requested reboot.
The blue line appeared. It took no time at all to complete.
Now the I am on the asus-screen
reboot to get to see the version. still 10.4.2.15 with twrp 3.1.0-1
next try: installing the bootloader with cmd.exe
typed on pc: "adb devices"
response:
"list of devices attached"
"015d0787774bf603 recovery"
typed: "adb push nHairyBean_Bootloader_TWRP2.5.zip /sdcard" (the one I got from the site you indicated)
response: "1325 KB/s" etc -> looks as transferred to sdcard
on tab: "installing files.."
"done..."
"now please restart..."
"updating partition details..."
"...done"
reboot to get to see the version.
screen says
"OS will cold boot in 10 seconds if no input is detected"
"booting recovery kernel image"
Version is still 10.4.2.15 with twrp 3.1.0-1
That is so bizarre that it wont update the bootloader or downgrade the TWRP.
One way to fix this is to do a FULL "adb wipe"
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
This will wipe the complete table back to nothing.
Then:> adb push nHairyBean_Bootloader_TWRP2.5.zip /sdcard
This should get you on the correct bootloader and TWRP, after this boot into fastboot to confirm you're on the correct bootloader then flash 3.1.0-1
NP
I did what you suggested and erased all the files ->worked well.
Then "adb push nHairyBean_Bootloader_TWRP2.5.zip /sdcard" -> got an error: "device not found"
I restarted the tab and then clicked on the USB-symbol.
"adb devices" showed an empty list of devices attached.
"fastboot -i 0x0b05 flash recovery flatline_TF201.img" gave "OKAY" and "writing recovery"
Bootloader is still 10.4.2.15
On the tab I am now on Flatline CWM Recovery v1.0RC1
TWRP is gone.
"adb devices" shows "0123456789ABCDEF recovery"
again "adb push nHairyBean_Bootloader_TWRP2.5.zip /sdcard" success ! Data were copied.
reboot. Bootloader is still on 10.4.2.15
nBootloader should now be in the /sdcard
next intent:
"fastboot -i 0x0b05 flash recovery flatline_TF201.img" gave "OKAY" and "writing recovery"
restart, then to RCK - flatline CWM recovery
install zip from sdcard -> no files found
got in advanced - wheelie - I accept the above statement - flash androidRoot BL power off
-> blue progress line is almost empty. then progress line disappears, ASUS screen shows up.
In Flatline recovery tried "install zip from sdcard" - "choose zip from sdcard".
only "- AndroidRoot/" is shown. (no nHairyBean_Bootloader_TWRP2.5.zip). So no way of installing the nHairyBean_Bootloader-
On one hand, it seems that I am able to establish a connection between the PC and the tab when in RCK, but when in USB, the connection seems not possible.
Hmmm...
Maybe I am missing something basic in this whole thing that keeps me from progressing.
What if I use the backup-files and try to go back to the initial configuration of the TF201 ? Or are there other options with the CWM-Recovery ?
Regards sj
That sounds like the best idea, going back to the stock ROM, they can be found here; https://www.asus.com/Tablets/Eee_Pad_Transformer_Prime_TF201/HelpDesk_Download/
Download the version for you region install and see if you can get back to stock.
NP
I downloaded the file you indicated. Now how do I get it into use ?
I cannot get into APX-mode
the only program working in the tab seems to be the flatline CWM Recovery v1.0RC1.
I tried to send the zip-file with "adb sideload <filename>" Error: failed to write data 'protocol fault <no status>'
I copied the zip-file to the external sd-card, but do not see how I can access it. The sd-card mentioned on screen ("Apply update from .zip file on SD card")seems to be an internal storage.
Related
Did you get the message: Magic Value Mismatch:-.-.-.-.-.-?!
After flashing a new recovery it happens sometimes.
GREEN ZONE
Are you able to go to the recocery menu(power + vol up)? If not, go to BLUE ZONE. If yes, follow these steps
1. check whether you have copied your rom as "update.zip" to your SD card's root directory
2. Go to recovery menu and install update.zip
BLUE ZONE
You may did something wrong while flashing a new recovery. Here is the right method:
1. go back to fastboot mode(power+power+power+vol up) and type these commands on your PC
2. fastboot erase userdata
3. fastboot erase system
4. fastboot erase cache
5. fastboot erase linux
6. fastboot erase recovery
7. fastboot flash recovery recovery.img (change path, if recovery.img is not in the same directory as fastboot.exe)
8. fastboot reboot
Are you able now to go to the recovery menu? If yes, go to GREEN ZONE and follow steps. If not, go to ORANGE ZONE.
ORANGE ZONE
Are able to unpack the update.zip and find the system.img and boot.img files? If not, then go to RED ZONE. If yes, copy these 2 files to the directory where the fastboot.exe is, run these commands:
1. fastboot erase recovery
2. fastboot flash recovery recovery.img
3. fastboot -w
4. fastboot erase linux
5. fastboot erase system
6. fastboot flash system system.img
7. fastboot flash linux boot.img
8. fastboot reboot
ROM is installed. Enjoy it!
RED ZONE
Make sure, that you copied the same recovery.img to fastboot folder, that you had flashed before to your tablet.
Type this command in recovery mode:
1. fastboot boot recovery.img
This command will run the recovery from your PC. After the recovery menu is booted, go to GREEN ZONE and enjoy your ROM!
If this was helpful to you, please do not hesitate to click on Thanks!
Lol, nice to see my post copy/pasted without any links indicated. Anyway, I hope It's helpful for ppl.
Tried following these steps, however, I'm still getting this error... followed this thread
http://forum.xda-developers.com/showthread.php?t=1470823
installed recovery successfully (via fastboot), and update seems to install fine, until I reboot and get the "Magic Value Mismatch" again..
Any ideas?
yellowumbrella said:
Tried following these steps, however, I'm still getting this error... followed this thread
http://forum.xda-developers.com/showthread.php?t=1470823
installed recovery successfully (via fastboot), and update seems to install fine, until I reboot and get the "Magic Value Mismatch" again..
Any ideas?
Click to expand...
Click to collapse
So you installed the recovery via fastboot. Did you manage to boot into recovery mode?
I had that issue, that I couldn't boot into recovery mod from my Folio, by pressing power+Up button. Thats why I added the RED ZONE method. Its like booting recovery from your PC. (fastboot boot recovery.img). All the times I wanna upgrade my current ROM, I have to do this step, because the power+up does not work, and the Folio skips booting in recovery and wanna do normal booting. However there is no Rom installed on machine, so I get the magic value mismatch message.
So try to boot recovery from your PC, but be sure you have copied to your fastboot folder the same recovery, that you flashed onto the tablet.
I hope it was helpful. If something is not clear, feel free to ask.
Hi there, thanks for the answer.
I am able to install recovery images via fastboot.
Device is showing up as a question mark with >fastboot devices
but recovery installs fine. CWM gives a series of e: can't opne/mount /cache errors.
Foliomod 1.4 installs no problem, thanks to the method here
http://forum.xda-developers.com/showthread.php?t=1458876
yellowumbrella said:
Hi there, thanks for the answer.
I am able to install recovery images via fastboot.
Device is showing up as a question mark with >fastboot devices
but recovery installs fine. CWM gives a series of e: can't opne/mount /cache errors.
Foliomod 1.4 installs no problem, thanks to the method here
http://forum.xda-developers.com/showthread.php?t=1458876
Click to expand...
Click to collapse
Are you able to wipe cache from recovery? And what else errors are listed?
One more thing, try to flash your boot.img and system.img via fastboot as written above.
If I follow this
http://forum.xda-developers.com/showthread.php?t=1458876
and let it install cwm v 3, I get the cache error and cannot wipe or mount via recovery.
If I follow the ICS thread, and flash the new cwm v5 via fastboot, I don't get the cache error, but the rom simply won't start. If I open the package, there is a boot.img, but not a system.img, just a system folder...
I could try flashing boot.img, but I don't see how that could help
yellowumbrella said:
If I follow this
http://forum.xda-developers.com/showthread.php?t=1458876
and let it install cwm v 3, I get the cache error and cannot wipe or mount via recovery.
If I follow the ICS thread, and flash the new cwm v5 via fastboot, I don't get the cache error, but the rom simply won't start. If I open the package, there is a boot.img, but not a system.img, just a system folder...
I could try flashing boot.img, but I don't see how that could help
Click to expand...
Click to collapse
Well just to see it clear. So you are able to install Foliomod 1.4, so your Internal storage is not broken.
When I get home, I will check the system folder of ICS rom. There are some method to create system.img from an unpacked folder...
So, in CWM 5.5.0.4 you manage to install Zip from SD card, ROM and GAPPS as well, but the Rom does not boot?!
yup, that's exactly it.
Haven't tried installing Gapps since I can't even get the rom to boot.
I have a perfectly working tablet with foliomod 1.4, and I did get honeycomb to run but some apps crashed so I reverted back to foliomod.
with CWM CWM 5.5.0.4 everything seems to work great, except at reboot, nothing happens (somehow, I no longer even get the magic value mismatch)
------------------
PS. not sure if this is at all relevant, but I cannot fastboot from win7, I'm fastbooting in either ubuntu or xp via VirtualBox, and the device, when calling >fastboot devices shows up as ?????????? (ubuntu) and ? (xp)... :\
yellowumbrella said:
yup, that's exactly it.
Haven't tried installing Gapps since I can't even get the rom to boot.
I have a perfectly working tablet with foliomod 1.4, and I did get honeycomb to run but some apps crashed so I reverted back to foliomod.
with CWM CWM 5.5.0.4 everything seems to work great, except at reboot, nothing happens (somehow, I no longer even get the magic value mismatch)
------------------
PS. not sure if this is at all relevant, but I cannot fastboot from win7, I'm fastbooting in either ubuntu or xp via VirtualBox, and the device, when calling >fastboot devices shows up as ?????????? (ubuntu) and ? (xp)... :\
Click to expand...
Click to collapse
Try to install gapps as well. Maybe it helps...
nope, no luck even with gapps installed..
just a blank screen..
sigh
yellowumbrella said:
nope, no luck even with gapps installed..
just a blank screen..
sigh
Click to expand...
Click to collapse
Have you tried all the roms? ICS Alpha 1,2,3 and 4?
Tried 3 and 4, didn't bother trying earlier ones, as it seems the latest ones work for most users
yellowumbrella said:
nope, no luck even with gapps installed..
just a blank screen..
sigh
Click to expand...
Click to collapse
Hmmm strange. I ask it for you on developers forum. What you can still do, is to check the steps, that you did them correctly. In most of the cases users forget something, or do some steps incorrectly.
Try to erase userdata, cache, system, linux and recovery in fastboot. You mentioned you had problem with fastboot under Win7. Problem may occur, in case of not proper erasing.
Thanks, I'll give it another try tonight.
Fastboot in win7 is simply not seeing the device. It shows up in XP and Ubuntu, but as "??????" - not sure if that could be a symptom.
I'll post a reply as soon as I've tried, and let you know how it went.
yellowumbrella said:
Thanks, I'll give it another try tonight.
Fastboot in win7 is simply not seeing the device. It shows up in XP and Ubuntu, but as "??????" - not sure if that could be a symptom.
I'll post a reply as soon as I've tried, and let you know how it went.
Click to expand...
Click to collapse
For me it works perfectly on Win7. After Installing SDK and JDK the in the devicemanager it is shown as an Unknown device. Simply add the driver manually to it.
Download driver from attachment.
Copy it to SDK\USB_driver folder
That works for me. After its done, the Folio is shown as "Fastboot" in device manager. But connect the tablet in fastboot mode to your PC before you add driver manually to it.
Thanks for that.
Tried it, still not working in win7. It shows up correctly in device manager, but fastboot itself just doesn't want to see it...
I've attached a screenshot for you
EDIT: screenshot gets resized, but it shows device manager listing
NVIDIA Android Fastboot Device
and a terminal with fastboot not seeing the device
yellowumbrella said:
Thanks for that.
Tried it, still not working in win7. It shows up correctly in device manager, but fastboot itself just doesn't want to see it...
I've attached a screenshot for you
EDIT: screenshot gets resized, but it shows device manager listing
NVIDIA Android Fastboot Device
and a terminal with fastboot not seeing the device
Click to expand...
Click to collapse
When You have win7, You have run the console as admin!
Or copy the complete Fastboot folder to another Destination like c:\temp...
Thanks stefannsv, tried it, still not showing...
But I can access fastboot on another platform, so I assume it's not an issue, I can just switch over to another OS to flash
no go, followed both this original post (tried all steps except orange, cause the rom I'm trying to install has a system folder, not a system.img)
Last method I tried was:
1) boot into fastboot
2) boot cwm-recovery-5.5.0.4.img directly from PC
3) wipe data/factory reset
4) wipe cache partition
5) install zip from SD card and chose the alpha 4 release
installing update...
then back to recovery, reboot and voilĂ ... magic value mismatch again (it had disappeared for a while... )
Also, when booting into CWM 3.0.0.5, I get a series of "E: Can't mount/cache/recovery" type errors.. could this be related?
booting directly into recovery from PC doesn't alllow me to install any ROMS, not even foliomod 1.4 which works if using puppet13th's method
I've a rooted ZTE V972M. I tried to increase internal storage following instructions in
"Re-Partition any MTK6589 Phone, Without A PC! (More /Data Storage!)"
When I reboot my phone, it stucks at logo screen.
What I've done trying to fix it:
1. Enter the recovery mode; it's a stock recovery (Android system recovery <3e>); wipe data/factory reset, wipe cache partition.
Result: still stuck at logo when rebooting.
2. Flash a stock ROM in recovery mode.
Result: Update aborted. In the log file, it says "failed to mount /cache (No such file or directory)" detailed in attached file. The stock rom I used is for ZTE LEO S1, while my phone is DTAC LION HD which is a house brand of my phone carrier. So, there may be a problem of ROM signing.
3. I installed "Minimal ADB and Fastboot" and "ZTE_Android_Driver", and run "adb devices" command.
Result: There is nothing under " List of devices attached", so I assume adb cannot see my phone. In Windows' Device Manager, it shows "Portable Devices" and lists drive I:\ and K:\ under it.
In summary, My phone is rooted. I might have damaged partition /data and /cache which causes the bootloop. I can still enter stock recovery mode. I have a stock ROM, but may not be properly signed.
Please suggest me on what I can do next.
Thanks.
sasawatd said:
I've a rooted ZTE V972M. I tried to increase internal storage following instructions in
"Re-Partition any MTK6589 Phone, Without A PC! (More /Data Storage!)"
When I reboot my phone, it stucks at logo screen.
What I've done trying to fix it:
1. Enter the recovery mode; it's a stock recovery (Android system recovery <3e>); wipe data/factory reset, wipe cache partition.
Result: still stuck at logo when rebooting.
2. Flash a stock ROM in recovery mode.
Result: Update aborted. In the log file, it says "failed to mount /cache (No such file or directory)" detailed in attached file. The stock rom I used is for ZTE LEO S1, while my phone is DTAC LION HD which is a house brand of my phone carrier. So, there may be a problem of ROM signing.
3. I installed "Minimal ADB and Fastboot" and "ZTE_Android_Driver", and run "adb devices" command.
Result: There is nothing under " List of devices attached", so I assume adb cannot see my phone. In Windows' Device Manager, it shows "Portable Devices" and lists drive I:\ and K:\ under it.
In summary, My phone is rooted. I might have damaged partition /data and /cache which causes the bootloop. I can still enter stock recovery mode. I have a stock ROM, but may not be properly signed.
Please suggest me on what I can do next.
Thanks.
Click to expand...
Click to collapse
can you return to stock using the mediatek flash tool and your stock firmware?(I'm not knowledgeable with MTK)
Lgrootnoob said:
can you return to stock using the mediatek flash tool and your stock firmware?(I'm not knowledgeable with MTK)
Click to expand...
Click to collapse
mediatek flash tool cannot see the phone either.
May be, if I can install CWM or TWRP, I might be able to update the stock rom with it. I've read elsewhere that If a phone can enter recovery mode, we can use fastboot in download mode. But I don't know how to install CWM or TWRP with fastboot.
sasawatd said:
mediatek flash tool cannot see the phone either.
May be, if I can install CWM or TWRP, I might be able to update the stock rom with it. I've read elsewhere that If a phone can enter recovery mode, we can use fastboot in download mode. But I don't know how to install CWM or TWRP with fastboot.
Click to expand...
Click to collapse
Driver issue?
Syntax for fastboot stuffz
try flashing:
Code:
fastboot flash recovery recovery.img
If flashing isn't working then try booting it directly
Code:
fastboot boot recovery.img
Thought I'd dust off my old TF201 (rooted) and put the KatKiss Nougat ROM on to see how it performs; was previously running CromiX.
I booted into TWRP recovery and did a full wipe and format of /data, then upgraded TWRP to 2.8.7.0 using the kang flashable zip. So far so good. Rebooted into the new TWRP and tried to upgrade TWRP further by loading a TWRP 2.8.7.2 image file via the TWRP settings. Rebooting recovery now fails - I get an error message in bootloader that there was an "unrecoverable bootloader error (0x00000000)" and it locks up.
I've tried reloading TWRP 2.8.7.0 via fastboot using
Code:
fastboot -i 0x0B05 flash recovery <image_file>
; this appeared to work, but rebooting into recovery now either gives the bootloader error message above, or else it briefly flashes the screen, restarts the bootloader and the cursor flashes over the Android icon and can't be moved with the volume down switch. If I select this option with volume up, I get four penguins followed by a "preinit starting" message and then a bunch of "=" symbols before it locks up again.
Rebooting into fastboot allows me to send fastboot commands from my PC, but adb commands fail with "no devices/emulators found".
I've reached the end of my experience and have no idea what to try next. Could someone please offer some advice on how to proceed?
Thanks!
Solution found
If anyone's interested in such an ancient tablet... post #12 in the TF300 support thread held the answer. They are generic fastboot commands, so the model of the tablet really doesn't matter.
I'm now back to stock 4.1 and ready to start over.
My TF201 was fine with stock 4.1.1 installed. I didn't have to enter a password to open it. Pressing power button was enough to reach the home screen.
I decided to install Nougat so I followed the thread "from stock to nougat" step by step (which is a great threat btw) but, of course, something went wrong.
I need help with getting the device out of the current status, which is :
- Only TWRP 2.6.3.0 is installed. I press Down + Power but no '3 icons' appear anymore.
- When I enter TWRP I get asked for a password. I highly doubt that I've (ever) set a password but somehow the device is now encrypted (?) / password protected. I can bypass the password screen by simply clicking 'cancel' but still can't mount anything inside TWRP, not system or external sd card, nor can I unzip / flash a Rom.
Before TWRP (this morning) HairyBean recovery was installed, but I couldn't flash anything there either, it ended always in an "can't unzip" error.
The good news is when connected to Win10 I have a working fastboot and adb connection !
What should be the next step to solve this (and to reach Nougat) ? How can I get the 3 icons back ?
You have the wrong TWRP installed for Nougat v7.1, you have to be on TWRP 2.8.0.0 or higher. You should flash the highest version available to date. LATEST TWRP: https://androidfilehost.com/?fid=457095661767150802
The BIG question is, what BOOTLOADER are you on? I think you have to be on bootloader version 10.6.1.27.1 to get the TWRP to work.
NP
Nektopoli said:
You have the wrong TWRP installed for Nougat v7.1, you have to be on TWRP 2.8.0.0 or higher. You should flash the highest version available to date. LATEST TWRP: https://androidfilehost.com/?fid=457095661767150802
The BIG question is, what BOOTLOADER are you on? I think you have to be on bootloader version 10.6.1.27.1 to get the TWRP to work.
Click to expand...
Click to collapse
Last bootloader is from the HairyBean-Upgrade zip :
Upgrade+Hairybean+2.31+(4.2.1)+Bootloader+&+TWRP+( 2.5).zip
But again, I couldn't flash anything either. It all ended with "can't unzip" error.
Right now, I can't boot into fastboot. The device always boots into TWRP 2.6.3.0.
I did the steps on this page : [HOW-TO] Unbrick your Transformer Prime (or not) by Diamondback
- Type: "adb shell"
- You should see a "#" now
- Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter]
- Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
- Exit the shell and reboot your Prime via CWM
- It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
Click to expand...
Click to collapse
but the result is the same, the device ONLY boots into TWRP (and asks for a password).
Without being able to boot into fastboot, how can I install the latest TWRP ?
So holding the VOL bottom down when turning on the tablet doesn't bring to the screen with: [RCK] [ANDRIOD] [WIPE DATE] choices in the middle?
NP
Nektopoli said:
So holding the VOL bottom down when turning on the tablet doesn't bring to the screen with: [RCK] [ANDRIOD] [WIPE DATE] choices in the middle?
NP
Click to expand...
Click to collapse
No. But I can send "adb reboot bootloader", and then it comes up after reboot.
So I've tried 2-3 times to flash recovery with :
fastboot flash recovery twrp-3.1.0-1-tf201t.img
but it always hangs at "writing 'recovery' ".
The device freezes.
Any suggestions what I should do now ?
msegmx said:
No. But I can send "adb reboot bootloader", and then it comes up after reboot.
So I've tried 2-3 times to flash recovery with :
fastboot flash recovery twrp-3.1.0-1-tf201t.img
but it always hangs at "writing 'recovery' ".
The device freezes.
Any suggestions what I should do now ?
Click to expand...
Click to collapse
Btw, bootloader is "WW_epad-10.6.1.27.1-20130711".
Have to tried renaming the TWRP.img file "TWRP.blob" then;
fastboot -i 0x0B05 flash recovery c:\adb\TF201t\TWRP.blob (you will need the to input the location of the file on you computer, that is where I flashed mine from) also did you wipe the recovery partition?
NP
https://forum.xda-developers.com/showthread.php?t=2038464
Nektopoli said:
Have to tried renaming the TWRP.img file "TWRP.blob" then;
fastboot -i 0x0B05 flash recovery c:\adb\TF201t\TWRP.blob (you will need the to input the location of the file on you computer, that is where I flashed mine from) also did you wipe the recovery partition?
NP
https://forum.xda-developers.com/showthread.php?t=2038464
Click to expand...
Click to collapse
Two questions before I totally brick my TF201 :
1) how to I wipe recovery partition ? (note: In fastboot mode, is it the third 'wipe data' icon ? does that wipe recovery, too ?)
2) the page says "THIS LINK IS FOR TF201 RUNNING JB BOOTLOADER ONLY! DO NOT USE IT IF YOU ARE NOT SURE WHAT YOU ARE RUNNING STOP NOW!".
How can I be sure what bootloader I'm on ?
(the text at the top of the page where the 3 icons are says :
HTML:
Key driver not found.. Booting OS
Android cardhU-user bootloader <1.00 e> released by "WW_epad-10.6.1.27.1-20130711" A03
Starting Fastboot USB download protocol
WW_epad-10.6.1.27.1 - 20130771 A03 is the JB bootloader, same one I'm on. You just have to wipe the recovery partition using adb command;
fastboot erase recovery
Then
fastboot -i 0x0B05 flash recovery c:\TWRP.blob
Once you get the TWRP from the link working you can flash the new ROM using the TWRP recovery console.
NP
msegmx said:
Two questions before I totally brick my TF201 :
1) how to I wipe recovery partition ? (note: In fastboot mode, is it the third 'wipe data' icon ? does that wipe recovery, too ?)
2) the page says "THIS LINK IS FOR TF201 RUNNING JB BOOTLOADER ONLY! DO NOT USE IT IF YOU ARE NOT SURE WHAT YOU ARE RUNNING STOP NOW!".
How can I be sure what bootloader I'm on ?
(the text at the top of the page where the 3 icons are says :
HTML:
Key driver not found.. Booting OS
Android cardhU-user bootloader <1.00 e> released by "WW_epad-10.6.1.27.1-20130711" A03
Starting Fastboot USB download protocol
Click to expand...
Click to collapse
Nektopoli said:
WW_epad-10.6.1.27.1 - 20130771 A03 is the JB bootloader, same one I'm on. You just have to wipe the recovery partition using adb command;
fastboot erase recovery
Then
fastboot -i 0x0B05 flash recovery c:\TWRP.blob
Once you get the TWRP from the link working you can flash the new ROM using the TWRP recovery console.
NP
Click to expand...
Click to collapse
I've tried many things, but right now when I try to enter recovery it says in red "unrecoverable bootloader error (0x0000000)"
fastboot erase system <- this end with an OK
fastboot erase recovery <- this doesn't end at all, command never ends
fastboot erase misc <- same as "erase recovery", doesn't end
flashing any blob, or any file doesn't end. Flashing blob says "sending.." and then doesn't continue, it is stuck there.
I also put the zip from inside the Asus blob zip onto an SD card, but since I don't have a recovery I can't start the process. -> unrecoverable bootloader error
So whatever I tried, it doesn't succeed. Either the tablet is stuck (the green RCK icon stops blinking) or it does nothing at all, for example after issuing a "fastboot flash recovery.." command, it just blinks the whole time and nothing happens.
The only successful commands are (so far) "fastboot reboot-bootloader" and "fastboot erase system".
Any suggestions are welcome..
Ok, good news, I have TWRP 3.1.0-1 installed.
I had the SD Card inside the tablet. the "unrecoverable bootloader error" was on screen.
The filename inside SD card is "EP201_SDUPDATE.zip".
So I did a Volume Down Button + Power button long press (as I did so many times before) and rebooted the tablet.. and somehow it recognized the zip file and started updating the system.
So, an Android robot appeared with a scroll-bar beneath it, and the the Android robot changed to a dead one with a red X on it.
After rebooting the tablet again I saw 4 icons, so that is the ICS bootloader, right ? at the top it says now "WW_epad-10.4.2.18-20121122" A03
Nevertheless I just flashed the latest TWRP through fastboot command.
Next I'll try to install a custom Rom.
But before that, do I need HairyBean recovery or bootloader first ?
Edit : I followed the steps here and everythning went fine so far. The tab is rebooting right now.
Thanks for your help !!
I'm using KatKiss 7.1.2 on my TF201 found here
https://forum.xda-developers.com/transformer-prime/development/rom-katkiss-nougat-t3459313
NP
---------- Post added at 04:04 PM ---------- Previous post was at 03:52 PM ----------
msegmx said:
Ok, good news, I have TWRP 3.1.0-1 installed.
I had the SD Card inside the tablet. the "unrecoverable bootloader error" was on screen.
The filename inside SD card is "EP201_SDUPDATE.zip".
So I did a Volume Down Button + Power button long press (as I did so many times before) and rebooted the tablet.. and somehow it recognized the zip file and started updating the system.
So, an Android robot appeared with a scroll-bar beneath it, and the the Android robot changed to a dead one with a red X on it.
After rebooting the tablet again I saw 4 icons, so that is the ICS bootloader, right ? at the top it says now "WW_epad-10.4.2.18-20121122" A03
Nevertheless I just flashed the latest TWRP through fastboot command.
Next I'll try to install a custom Rom.
But before that, do I need HairyBean recovery or bootloader first ?
Edit : I followed the steps here and everythning went fine so far. The tab is rebooting right now.
Thanks for your help !!
Click to expand...
Click to collapse
You know need to install the JB bootloader but you're fine with TWRP,
The correct bootloader for the ROM is: WW_epad-10.6.1.27.1 - 20130771 A03
NP
H932 with Havok Pie, I don't use Gapps but wanted to get Gcam working so I flashed Open Gapps Pico. Decided I didn't want Gapps on the phone so I went to TWRP to restore a backup I made the previous day. I had backed up all partitions except the largest personal files partition. After running the restore it gave an error about /system (did not realize it may have just needed noverity or the other file flashed?). Did some searching and found that I could change the file system and that cleared it up for one person. Changed /system to FAT but then realized that would not support all the internal memory, so then went to EXT3 (couldn't find what it should be formatted to) it threw an error, so then I tried exFAT, that seemed to work BUT it then got stuck on "updating partitions" and would never finish, waited 10-15min. Only way to get out of TWRP was to hold all 3 buttons and it would power down the device.
So here I am now, I have TWRP in recovery and laf, except it's stuck on the teamwin boot logo. ADB does see the phone. Just read I can grab the twrp log file, attached.
hlp
"adb fastboot recovery" has not effect.
You could try fastboot boot TWRP.img
stays at "waiting for devices".
Doesn't H932 have little or no fastboot.
How is it that both twrp installs don't work (laf + recovery).
So it looks like there is some fastboot. When shutting down from the failed start of twrp, I'm given the options to Power Off or Restart at Fastboot Mode. "fastboot boot twrp.img" says downloading, then failed, says (remote: unknown command). "fastboot getvar unlocked" gives "unlocked: yes".
LGUP says "there is no handset".
Another guy had a similar (or exactly the same) problem, he used "fastboot oem lock", then "fastboot oem unlock". But didn't work for me.
Tried "fastboot erase system",
returns:
"Did you mean to fastboot format this ext4 partition?
erasing 'system'...
FAILED (remote: unknown command)
finished. total time: -0.000s"
tried: "fastboot format:ext4 system"
returns:
"CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for system"
Is that because there are limited or no fastboot commands on the H932?
Would a battery disconnect do anything? Would going through the lafploit FUWL section help?
Don't have the phone anymore. Can anyone confirm, was noverity needed to get flashed after using twrp restore?