Cannot update bootloader - Asus Transformer TF700

I am currently using bootloader 10.4.4.25 and cannot install the latest cm 11
And I am using CWR 6.0.4
Can anyone advise how can I update the bootloader so I can install cm11?
Thanks

Download the latest Asus firmware, unzip the file once resulting in another zip.
Copy that zip to your tabet and flash it in CWM (that you have everything you care about backed up off the tablet goes without saying, right?). That will get you onto the latest bootloader but also wipe your custom recovery.
Boot into fastboot, flash a CM11 compatible recovery.
Reboot
Boot into recovery, do a factory wipe and then flash the rom.

Thanks for the advise. I am downoading the latest firmware from ASUS website and will install it.
I am not sure how to flash a CM11 compatible recovery from fastboot. Can you give more details please? Shoudl I follow the root instruction from the ROM post and re-root the machine again?
Thanks in advance
berndblb said:
Download the latest Asus firmware, unzip the file once resulting in another zip.
Copy that zip to your tabet and flash it in CWM (that you have everything you care about backed up off the tablet goes without saying, right?). That will get you onto the latest bootloader but also wipe your custom recovery.
Boot into fastboot, flash a CM11 compatible recovery.
Reboot
Boot into recovery, do a factory wipe and then flash the rom.
Click to expand...
Click to collapse

Related

Question on updating to CM-10.2 from stock 4.1.2

I flashed CWM in odin,but when i boot up into CWM it boots the stock recovery.Also,do i need to flash the bootloader and radio if coming from 4.1.2? I must be getting old..I did it on my last relay,but i don't remember how.Do i have to flash the bootloader first?
Thanks
The 4.1.2 stock image apparently has code within its start up routine to overwrite a custom recovery if one is detected at boottime. After flashing with ODIN, did you reboot into the system, or did you directly boot into CWM? If you're on 4.1.2 stock, there will be no need to update the bootloader or modem, you're on the latest. Try flashing CWM, and then immediately booting into recovery. You can also delete the files Stock calls to reflash the recovery from the image once you're able to get in via CWM, and utilize adb.
Magamo said:
The 4.1.2 stock image apparently has code within its start up routine to overwrite a custom recovery if one is detected at boottime. After flashing with ODIN, did you reboot into the system, or did you directly boot into CWM? If you're on 4.1.2 stock, there will be no need to update the bootloader or modem, you're on the latest. Try flashing CWM, and then immediately booting into recovery. You can also delete the files Stock calls to reflash the recovery from the image once you're able to get in via CWM, and utilize adb.
Click to expand...
Click to collapse
Yes,i booted into the system,then restarted into CWM...I'll try reflashing,and booting right into recovery and let you know,Thanks for the reply!
Yep,that did it...Got it up and running..Thanks again Magamo..

[SOLVED] TWRP 3.0.2 bootloop

Hello everyone.
I had a problem flashing TWRP on my Google Nexus 5, or better the problem comes when I try to enter the recovery.
I followed this pattern from stock android 6.0.1 with august security patch:
1) unlock bootloader
2) downloaded lastest TWRP (3.0.2 hammerhead) recovery from the official website
3) flash it with "fastboot flash recovery recovery.img"
Until this point everything's alright but then when I unplug my phone from the laptop and click on enter recovery something strange happens.
I can see the TWRP boot image but as soon as I go in I see tons of errors related to "cannot mount ..." and some partitions name like /data, /cache, and then starts the bootloop without let me any chance to do something. Sorry but I can't see every error beacuse this happen too fast.
Any idea on what is going on?
I've tried the TWRP 3.0.1 but is the same shuold I go down or maybe I have to change it beacuse of compatibily issues with the monthly patches?
Thank you for your help, I hope I explained my problem clearly.
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
audit13 said:
After unlocking the bootloader, phone wipe all data? Did you reboot after unlocking bootloader?
Click to expand...
Click to collapse
No I've just unlocked and then tryied to flash the recovery without wipe.
But data is already wiped by unlocking the bootloader isn't it?
Anyway thanks for your reply as soon as I can I'll try what you have written.
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
audit13 said:
Yes, the data should be automatically wiped. Try TWRP 2.87. If the phone still doesn't boot into TWRP, reflash stock recovery, flash userdata.img, immediately boot into stock recovery using the button combo without rebooting, perform a factory wipe, reboot into fastboot, and flash TWRP again.
Click to expand...
Click to collapse
Thank you so much for telling me to flash the 2.8.7, i've choosen the 2.8.7.1 without success (it did't flash i don't know why) but then after another wipe all I've flashed the 2.8.7.0 and it seems to work.
The only thing I would like to ask now is: I'm going to flash superSU and elementalX over stock AOSP (I don't want custom ROM for now) and can this recovery cause problem because of it is not the last update?
Thank you again for the answer!
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
TWRP Restore problem
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
I have rebooted...deleted all my music... (I think that the issue may come from insufficient disk space) and relaunched...
Will see...
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
hunter-dz said:
download Nexus Root Toolkit-type in google Nexus Root Toolkit - and watch from yuotoube how it work's
good luck
Click to expand...
Click to collapse
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
kevtuning said:
My N5 was already rooted... and it's the second time that I update the OTA using directly TWRP... and for the August patch it has worked fine.
I don't know what's happen now...
Click to expand...
Click to collapse
Download thé nrt and i Will teach how to root ur n5
And type in Google nrt n5 xda
audit13 said:
I have not tried 2.87 with Elemental X. The only way to determine whether it will work would be to try it. I recommend creating a nandroid backup before flashing Elemental so you can restore if something goes wrong.
Click to expand...
Click to collapse
Now I can confirm that I was able to flash the lastest SuperSU and ElementalX with TWRP 2.8.7.0 without any problem, so thank you again for your help.
kevtuning said:
Hi, I have an issue with the resotre of TWRP...
Here's what I did:
-Downloaded the latest OTA image https://developers.google.com/android/nexus/ota
-Downloaded latest SuperSU http://download.chainfire.eu/supersu-stable
-Downloaded latest ElementalX http://elementalx.org/devices/nexus-5/
-reboot to TWRP
Choose OTA, then SuperSU, then ElementalX
Luunch the restore..
And my screen is "blocked" from 5 hours on Install Zip 1 of 3.
"blocked" means doesn't move to the Zip2 but the clock is moving... the screen is locking itself after few seconds and I am able to unlock it...
Any idea how to exit properly ?
Click to expand...
Click to collapse
Hi, I've have successfully installed the last OTA update but not with zip file, instead I downloaded the factory image and flashed with fastboot boot.img and system.img (also vendor.img if you have one) then rebooted into TWRP and installed the lastest ElementalX and SuperSU.
I'm not sure but I think that factory image zip file are not installable via recovery but only with the flash-all that comes with them. This script use fastboot to flash everything you need of the factory image
You can find this procedure on the ElementalX website, here is the link hope it can help out: http://elementalx.org/how-to-install-android-monthly-security-updates/
Finally... I installed CM13 and ElementalX... in some minutes ...
I suppose the the problem was in my zip file...

Oneplus one stuck in boot logo while updating latest TWRP 3.0.2

Hi,
was trying to install new ROM & completly wipe out OPO (Including OS). to do so got some error in zip file execution.
So tried to update TWRP (2.8.6 to 3.0.2) and now stuck into OPO boot screen.
Please help!
Thanks in advance!
BR//
Ashok
ashokyadav668 said:
Hi,
was trying to install new ROM & completly wipe out OPO (Including OS). to do so got some error in zip file execution.
So tried to update TWRP (2.8.6 to 3.0.2) and now stuck into OPO boot screen.
Please help!
Thanks in advance!
BR//
Ashok
Click to expand...
Click to collapse
Can you boot into the recovery? Or fastboot? Also before trying to install a new ROM did you backup your previous?
Durso81 said:
Can you boot into the recovery? Or fastboot? Also before trying to install a new ROM did you backup your previous?
Click to expand...
Click to collapse
Can't boot into recovery mode, maybe something went wrong while updating TWRP to 3.0.2 but can boot into fastboot.
also had backup of previous rom but since i can't boot into TWRP now so can't restore it. Earlier on TWRP 2.8.6 i was getting zip file execution error while restoring/installing new ROM.
So for now i have only access to fastboot mode, how to proceed futher?
ashokyadav668 said:
Can't boot into recovery mode, maybe something went wrong while updating TWRP to 3.0.2 but can boot into fastboot.
also had backup of previous rom but since i can't boot into TWRP now so can't restore it. Earlier on TWRP 2.8.6 i was getting zip file execution error while restoring/installing new ROM.
So for now i have only access to fastboot mode, how to proceed futher?
Click to expand...
Click to collapse
You have 2 options you can flash the stock rom and recovery via fastboot here is a guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 (Just skip step 4 don't relock the bootloader specially if you want to install TWRP) Make sure you download the correct file there is a 64gb and a 16gb listed in this guide or you can download the stock file straight from cynogen OS here https://cyngn.com/support
Or you can reinstall TWRP via fastboot by downloading TWRP here https://dl.twrp.me/bacon/ and install your backup if its still there. If its not there you can either download and install any custom rom you want or if you want the stock rom go with option 1 above and then re-install twrp. (Always remeber after installing TWRP don't fully boot into the system or you will loose TWRP, boot straight to recovery once its done flashing TWRP by holding the power button and volume down. )
Durso81 said:
You have 2 options you can flash the stock rom and recovery via fastboot here is a guide http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541 (Just skip step 4 don't relock the bootloader specially if you want to install TWRP) Make sure you download the correct file there is a 64gb and a 16gb listed in this guide or you can download the stock file straight from cynogen OS here https://cyngn.com/support
Or you can reinstall TWRP via fastboot by downloading TWRP here https://dl.twrp.me/bacon/ and install your backup if its still there. If its not there you can either download and install any custom rom you want or if you want the stock rom go with option 1 above and then re-install twrp. (Always remeber after installing TWRP don't fully boot into the system or you will loose TWRP, boot straight to recovery once its done flashing TWRP by holding the power button and volume down. )
Click to expand...
Click to collapse
Thanks!
Do you recommend any video guide for option 2 (TWRP via Fastboot).
ashokyadav668 said:
Thanks!
Do you recommend any video guide for option 2 (TWRP via Fastboot).
Click to expand...
Click to collapse
Never watched a video so can't recommend one particular. But here is a link to all guides and how to http://forum.xda-developers.com/oneplus-one/general/index-oneplus-one-resources-compilation-t2843675
Also there is a one click tool here to make it easy
http://forum.xda-developers.com/oneplus-one/development/toolbox-oneplus-one-toolbox-t2808987
ashokyadav668 said:
Thanks!
Do you recommend any video guide for option 2 (TWRP via Fastboot).
Click to expand...
Click to collapse
Thank you Durso81,
i have successfully installed TWRP & ROM.
Thanks for your time & effort for a beginner.

Updating TWRP on my TF700T

I have a TF700T laying around for quite some time and I forgot how I installed TWRP. My TWRP version is 2.4.1.0. I want to update it to the latest TWRP to upgrade my ROM. I download the .img file but I cant see it under recovery. It seems it cant detect the image file. Can somebody please help me with this as to how to update TWRP.
Read the first three posts of this: https://forum.xda-developers.com/showthread.php?t=2688891
Then yo need to make sure that you are on the correct bootloader (post 3)
You cannot flash an img file in your recovery version. That came later. So you have to do it in fastboot as described in my guide (always the best way) or you can download this and flash it in your current recovery. Then reboot
https://androidfilehost.com/?fid=889964283620755946
That's TWRP 3.1..1. in a flashable zip. Just make sure the bootloader ends in .10 before flashing it.

recovery broken after format system and reboot - how to unbrick?

It's an old device. I got it for free since it was just laying around in friend's home. Worked OK after factory reset with stock ROM. Wanted to upgrade Android.
Previously successfully flashed TWRP from andi34.github.io/recoveries_tab2.html for Samsung Galaxy Tab 2 GT-P3100 using heimdall on Linux. Could start the TWRP recovery. Then I followed FAQ andi34.github.io/faq.html
backup all important files (e.g. contacts) and store them on your MicroSD-Card or on your PC/Laptop
copy the rom and gapps you like to install to your MicroSD-Card (make sure Gapps match the Android version of the Rom!)
boot into your custom recovery
make a backup of your current running rom and store it on your MicroSD-Card or on your PC/Laptop (some of the following are named slight different depending on the recovery you use)
wipe cache
wipe dalvic cache
wipe/format system
wipe/format data
reboot your recovery once!
Click to expand...
Click to collapse
After reboot, I could no longer start recovery.
Perhaps I should not have formatted system?
Perhaps I should not have rebooted before flashing the ROM zip?
I can still enter download (ODIN) mode. Re-flashed the TWRP recovery. Rebooted. Still cannot enter TWRP. But can still enter download mode.
What do you recommend now?
Can I flash LinageOS ROM zip from andi34.github.io/roms_tab2_lineage.html using heimdall? But heimdall does not really support zip files? It's harder than that? Any guide for that?
Or do I have to re-flash the stock ROM? Can I flash the stock ROM using heimdall?
Get the stock rom for the device then use ODIN to flash the stock rom back, the stock rom should fix it as it also flashes the stock recovery back.
Did you reboot System instead of Recovery? What TWRP version was this? I also thought of scenarios like this.
Can you still boot to recovery (twrp)

Categories

Resources