currently I'm on 2.6.0.0 and I was thinking of the benefits to upgrading to the latest version, plus also the risks involved. Whats the best way to upgrade TWRP ?
Use goomanager. It's by far the easiest since it's mostly automated.
mjb152 said:
currently I'm on 2.6.0.0 and I was thinking of the benefits to upgrading to the latest version, plus also the risks involved. Whats the best way to upgrade TWRP ?
Click to expand...
Click to collapse
I just downloaded the latest version of TWRP, booted into the bootloader and loaded the image by
Code:
fastboot flash recovery {insert name of image file here}
. Easy peasy,,,
oops, it's a bit late. I found the goomanager and installed it, trouble is I installed the OTA update which has set my device unrooted. There is no TWRP any more, not sure how to get into recovery mode as a dead android with a red triangle appears. I'm unlocked, but just cant get into recovery.
I took a full TWRP backup before I started, any tips ?
mjb152 said:
oops, it's a bit late. I found the goomanager and installed it, trouble is I installed the OTA update which has set my device unrooted. There is no TWRP any more, not sure how to get into recovery mode as a dead android with a red triangle appears. I'm unlocked, but just cant get into recovery.
I took a full TWRP backup before I started, any tips ?
Click to expand...
Click to collapse
Just use ADB to Fastboot flash recovery. Either Fastboot flash your root file or copy it to your device. If you copy it to your device, then boot to recovery and flash your Superuser or SuperSU .zip. You don't want to restore your backup though if your on the latest OTA now and your backup is the previous OTA.
SwiftKey'ed from my White Note 2 via XDA Premium HD
Wug works well.. Simple too.
Sent from my Nexus 7 using xda app-developers app
theres TWRP flashable zips in the TWRP thread, this is the easiest if you alrady got TWRP
you can use wug to install it for the first time then use goomanager to update it later or TWRP manager to dl manually.
Related
I apologize for the noob question but I've never found myself in this particular situation...
I've decided to stick with the 4.3 JWR66V factory image while I wait for a working rooted version to be released or even an updated SuperSU or Superuser zip (that doesn't drain the battery or lose root with certain apps).
I used the factory image found HERE and followed the detailed instructions found HERE. I followed the instructions under section "D" vigorously which meant that I installed the stock recovery image as well. Everything is running as it should. However, I was curious if it was safe to flash TWRP 2.6.0.0 recovery through fastboot with my current setup. I'd like to use that recovery to wipe cache/dalvik and possibly fix permissions. However, I'm not sure if this will break something so I am hesitant to try it.
I have made sure the bootloader is unlocked. But I am curious if it's safe to flash and use TWRP while I am not rooted.
You can install recovery with no problem, root has nothing to do with it. however i think upon a reboot your recovery will be replaced with factory.
Interesting. I wonder why/how the system would flash back to stock recovery if I've pushed the TWRP recovery image over the factory image?
I flashed twrp from fastboot and it's still there. Just waiting on root
Sent from my Nexus 4 using xda app-developers app
otariq said:
I flashed twrp from fastboot and it's still there. Just waiting on root
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Without root would there be any functionality within TWRP that I shouldn't touch? Or does recovery functionality have no dependency on root?
What is there you wanna do? I just replaced stock with twrp so I can just flash the su zip when its out because I don't always have access to a PC. Also, Franco released his initial 4.3 kernel which I'm thinking about flashing.
When rebooting from twrp it'll ask if you wanna flash the su.apk because you don't have root I chose no because it wouldn't do anything for us right now without the binaries
Sent from my Nexus 4 using xda app-developers app
Good point. As of right now I guess I don't have a huge need for it. I'll just leave everything as is until a proper SuperSU is released. At which point I'll install the latest TWRP and root.
Just a question, wasn't nexus root toolkit supposed to be able to revert to stock?
I did it in previous android versions.
now I am running slim rom with CWM and "reverting to stock 4.3" using NRT doesn't work, the process finishes but nothing is done.
skinniezinho said:
Just a question, wasn't nexus root toolkit supposed to be able to revert to stock?
I did it in previous android versions.
now I am running slim rom with CWM and "reverting to stock 4.3" using NRT doesn't work, the process finishes but nothing is done.
Click to expand...
Click to collapse
No idea. I use a Mac and flash back to stock via Fastboot. You should just learn to do that anyway so you have a better sense of exactly what is going on and if something fails you'll know exactly which step is failing in order to correct it. Relying on a toolkit is like never taking the training wheels off your bike.
Hello guys, first time posting here, I'm pretty sure it's a silly question, sorry if it is but I couldn't find the answer anywhere. I have an unlocked and rooted device, I installed the last 4.3 update this morning, and usually TWRP let me automatically fix the root just after install the update. But this time it just installed it and booted the tablet, and when I try to enter the recovery mode to fix the root in TWRP, I only see the droid with the exclamation mark.
So the problem is that I don't have root, and I cannot enter TWRP to fix it. TWRP went away with the latest update?. For entering the TWRP I pressed vol+ vol- and power and the pick recovery... is it correct?
Thank you in advance for the great community we have in android and sorry for my english
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
3DSammy said:
The same thing happened to me, I resolved it by:
- download a recovery image such as TWRP to a desktop/laptop and then flash it via abd
- now boot into recovery and flash SuperSU 1.51 or higher (1.55)
From what I read you probably did this once before. The 4.3 update overwrote your recovery image and root.
Click to expand...
Click to collapse
Same for me, Starting have some problems as I tried a "reboot to recovery" apk and got it stuck in the bootloader screen and it wasnt going anywhere.. still had TWRP but reflashing things wasnt working..
Used Wug's Nexus Root Toolkit to bring it back to life..
All good
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
prezeus said:
I reflashed the recovery image and rooted again with Wug's Root Toolkit. All good!! Thank you for your answers guys!! Cannot find the way to put SOLVED in the thread title...
Click to expand...
Click to collapse
Nice that it is solved but please do nog use toolkits anymore. I respect the effort and time people take to make them but learning fastboot is just way better. Maybe harder but hard work pays off. Almost everyone will tell the same.
For people who want to use fastboot:
1. Flash custom recovery via fastboot.
2. Boot into recovery.
3. Flash latest supersu.
You can put solved in the title by edeting it.
Sent from my Galaxy Nexus using XDA Premium HD app
same
Good time . I have a similar problem : after a recent update missing root. I tried to flash a custom recovery by fastboot, but the process hangs at downloading recovery.img to nexus. I tried using other drivers and a different version of fastboot, but to no avail.
Ps: by same drivers and fastboot I got the root before.
Greetings,
First I'm sorry if this isn't the right thread for this, I'll gladly delete and change threads if need be.
Second, I just got an LG G2 (Verizon) today. It's great but I want more so I rooted it, confirmed that it's rooted. But that's all I can do. I can't install a recovery app on here to save my life. I tried downloading the VZW recovery img and pushing that with the loki_flash but I got two errors mainly.
Input file is not a valid loki image and Loki aboot does not match device. I'm trying to run either TWRP or CWM, anything really so I can flash a custom ROM on this bad boy.
If the image is not a valid loki image I'm assuming I don't have the right pair of files? (loki/recovery) and if the aboot image doesn't match the device I'm assuming that I don't have the right loki? Are these correct assumptions or am I making an ass out of just me???
My phone is rooted, ROM Manager says I have both TWRP AND CWM on my phone but if I try to boot into recovery via ROM Manager or adb I get a black screen and nothing more.
Does anyone have ANY insight at all into how I can go about the next step?
paryguy said:
Greetings,
First I'm sorry if this isn't the right thread for this, I'll gladly delete and change threads if need be.
Second, I just got an LG G2 (Verizon) today. It's great but I want more so I rooted it, confirmed that it's rooted. But that's all I can do. I can't install a recovery app on here to save my life. I tried downloading the VZW recovery img and pushing that with the loki_flash but I got two errors mainly.
Input file is not a valid loki image and Loki aboot does not match device. I'm trying to run either TWRP or CWM, anything really so I can flash a custom ROM on this bad boy.
If the image is not a valid loki image I'm assuming I don't have the right pair of files? (loki/recovery) and if the aboot image doesn't match the device I'm assuming that I don't have the right loki? Are these correct assumptions or am I making an ass out of just me???
My phone is rooted, ROM Manager says I have both TWRP AND CWM on my phone but if I try to boot into recovery via ROM Manager or adb I get a black screen and nothing more.
Does anyone have ANY insight at all into how I can go about the next step?
Click to expand...
Click to collapse
Sorry didn't mean to hit the thanks button.
What build are you on (11A,12B? What recovery image are you using (ie, from what thread)?
Sent from chdhsheh fhhdud
TWRP
Follow the install instructions for TWRP 2.6.3.2. Then after you've confirmed you can boot the OS from the recovery, place the 2.6.3.3 on the root of your SD. Reboot into recovery and flash 2.6.3.3. Reboot into recovery again and you'll be good to go.
Version 2.6.3.2 won't flash 4.4 ROMs but 2.6.3.3 will flash 4.2 (I'm assuming), 4.3, and 4.4.
Download FreeGee app from the play store and install TWRP recovery from it. It was the only way I could install it on my LG G2.
So many
simon_lefisch said:
Sorry didn't mean to hit the thanks button.
What build are you on (11A,12B? What recovery image are you using (ie, from what thread)?
Sent from chdhsheh fhhdud
Click to expand...
Click to collapse
I followed many tutorials last night including this one.
(I am too new to post links in a message.) The link I was going to post was from howtorootmobiledotcom
I downloaded any version of TWRP I could, there were only 2, one img of each version and one zip. I used the loki from the zip that came with it as well but still no go.
paryguy said:
I followed many tutorials last night including this one.
(I am too new to post links in a message.) The link I was going to post was from howtorootmobiledotcom
I downloaded any version of TWRP I could, there were only 2, one img of each version and one zip. I used the loki from the zip that came with it as well but still no go.
Click to expand...
Click to collapse
What build number are you on?
Sent from chdhsheh fhhdud
vnrse Theologisch
simon_lefisch said:
What build number are you on?
Sent from chdhsheh fhhdud
Click to expand...
Click to collapse
I used RussGJohnson solution and it worked in a matter of seconds. Now I'm stuck though. I wiped everything and can boot into TWRP but I have no ability to sideload anything. I have all the latest LG drivers, even the lastest android sdk drivers, nothing is working. If I boot up normally the LG logo comes up and just sits there.
I can boot into recovery using the whole volume down + power button combo but then when I go to sideload my computer isn't seeing the device. I'm on a Win 8 machine using the stock cable. I've tried both USB 2 and 3 ports
It's done
Using RussGJohnson's suggestion worked great.
The issue I had with being unable to sideload a ROM wasn't resolved but I just used my Mac to do it instead. That worked just fine. Win8 couldn't recognize the device while in recovery. Go figure.
free gee very fast
Use Flashify u n00b.
http://shield.nvidia.com/tablet-release-notes/2.2/
now to figure out how to get this to update on my rooted LTE Tablet.....
I'm rooted and just got the update. But haven't completed the update yet as I'm too lazy to reroot.
I tried using the nvidia updater, which failed since it rebooted and CWM had no idea what to do. I made a CWM backup so I am going to see how well it flashes in CWM manually.
I managed to find the OTA download location and have superSU at the ready in my downloads folder in case I have to reflash. the OTA saved as:
/data/data/com.nvidia.ota/files/ROM/shield_tablet_software_upgrade_2.2_-_lte__5.0.1.zip
Someone please report the steps on how to do this for Rooted 2.1.
CWM install zip failed. build fingerprint mismatched, its probably CWM. Will try sideloading stock recovery then installing the zip afterward, I think I remember seeing somewhere here that's how people upgraded rooted devices from 2.0 to 2.1
Omg things seem to be more snappy! The dreaded lag may be gone! I'm not rooted so I did the ota install
I'm really interested in your findings, i need to find a tutorial on how to flash back stock recovery then i can do the update and hopefully reroot.
Iorkca said:
I'm really interested in your findings, i need to find a tutorial on how to flash back stock recovery then i can do the update and hopefully reroot.
Click to expand...
Click to collapse
currently working on it right now, need about a few to upload all files and then get everything setup....
From a post on Geforce forum
fjrichman
*
*
*
*
For rooted users you'll want to use theses.
US LTE Full:*http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_do-full_ota-29979_512.4856.zip
US Wifi Full:*http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29979_512.4856.zip
I successfully updated rooted wifi using link
Awsome sounds good. Quick question to get stock recovery back all id have to do is extract the recovery.img file from the ota 2.1 file i downloaded off nvidia's site and load it like i did the CWM recovery from the root thread right?
Or (if you've got root) wait until the full 2.2 .zip is available, then download it and flash it through your custom recovery, followed by the latest SuperSU. (just like the last Lollipop update).
Interestingly, the OTA update tool has an option for "Check full update" (under the top right menu), but it doesn't seem to return anything...yet...
Sent from my SHIELD Tablet using XDA Free mobile app
Pretty much you are going
Flash Stock recovery by any preferred method
Flash Update
adb Reflash CWM recovery
Thru recovery flash SuperSU
**Profit**
Working on getting all the files in one package as of right now. Damn internet hogs in my house.
Cant we use Flashify to flash stock recovery and then updating the OTA and then reflash our recoverys and supersu.zip?
NaminatoR1254jaime.sier said:
Cant we use Flashify to flash stock recovery and then updating the OTA and then reflash our recoverys and supersu.zip?
Click to expand...
Click to collapse
Yeah, if you have the stock recovery file....
mcord11758 said:
From a post on Geforce forum
fjrichman
*
*
*
*
For rooted users you'll want to use theses.
US LTE Full:*http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_do-full_ota-29979_512.4856.zip
US Wifi Full:*http://ota.nvidia.com/ota/rom/productionBL-droid-signed-wx_na_wf-full_ota-29979_512.4856.zip
I successfully updated rooted wifi using link
Click to expand...
Click to collapse
Did you clean install, or did you dirty flash?
Just curious if this can be applied as an update our not.
Sent from my SHIELD Tablet using XDA Free mobile app
masterchiefb117 said:
Yeah, if you have the stock recovery file....
Click to expand...
Click to collapse
I dont
But Im downloading the 2.1 update stock images. Funny how I deleted the 2 gb zip yesterday and now I need it.
masterchiefb117 said:
Pretty much you are going
Flash Stock recovery by any preferred method
Flash Update
adb Reflash CWM recovery
Thru recovery flash SuperSU
**Profit**
Working on getting all the files in one package as of right now. Damn internet hogs in my house.
Click to expand...
Click to collapse
You won't be able to successfully flash the UPDATE .zip file (~94MB) on a rooted (read: modified) Lollipop version.
Recovery version is irrelevant.
You need the FULL 2.2 rom (already found above , ~731MB), flash it in your current custom recovery and re-root by flashing SuperSU again.
Sent from my SHIELD Tablet using XDA Free mobile app
ok, here's what I dug up. If you are rooted and want it NOW, get to it, otherwise wait for someone to clean up the process:
get the OTA from here: https://forums.geforce.com/default/...hread-released-2-17-15-/post/4464815/#4464815
get your latest SuperSU flashable zip: http://download.chainfire.eu/396/SuperSU/
get your recovery ready for reflashing, the OTA will install the stock recovery again. I went with: http://forum.xda-developers.com/showpost.php?p=58864006&postcount=90
boot into recovery and install zip from sideload. then choose either: adb sideload productionBL-droid-signed-wx_na_do-full_ota-29979_512.4856.zip or adb sideload productionBL-droid-signed-wx_na_wf-full_ota-29979_512.4856.zip
reboot and let the upgrade happen, you've lost root and recovery, but you still are unlocked so you just have to reflash them. get into fastboot with power and volume down, then flash recovery: fastboot flash recovery openrecovery-twrp-2.8.5.0-shieldtablet.img
load up recovery and flash the superSU zip and you're back in business.
ShrekOpher said:
Did you clean install, or did you dirty flash?
Just curious if this can be applied as an update our not.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Wiped cache and davlik then just in case flashed supersu after rom
An Droid said:
You won't be able to successfully flash the UPDATE .zip file (~94MB) on a rooted (read: modified) Lollipop version.
Recovery version is irrelevant.
You need the FULL 2.2 rom (already found above , ~731MB), flash it in your current custom recovery and re-root by flashing SuperSU again.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
That means a rooted lollipop user with custom recovery, can download the full ota, and dirty flash it, right?
Hello,
Is it possible to update from 5.0 to 5.1 if i have unlocked the bootloader? I also have TWRP. I downloaded the 5.1 update, but when i want to install it the phone reboots and i get into TWRP menu. Is there any way to flash the OTA update without losing my current data on the phone?
Thank you!
Dealing with the same problem here.
IIRC TWRP automatically handled OTA updates in the past but it doesn't seem to be working anymore.
What was the procedure you were using before? You just installed as a normal zip from TWRP ?
For the ota to work you have to be 100% stock system, recovery, and kernel. I'd just flash the system and boot images from 5.1 in fastboot to update.
Sent from my Nexus 5 using XDA Free mobile app
So sad. I will lose all the stuff I have on the device.
tzeus said:
So sad. I will lose all the stuff I have on the device.
Click to expand...
Click to collapse
Not if you just flash the System and Boot images and remove -w from the Flashall.bat command to prevent the wipe instead of using the OTA. If you use the OTA, you will have to be stock as the previous posted stated, which since you are rooted with a custom recovery, would require you to flash the stock image, wiping your device, before you could run the OTA. This is the result of a change in the way Android 5.+ authenticates, which is why it worked previously. It now checks the whole partition, and one byte out of place will abort it.
That said, you can always backup your phone (which is a good thing to do anyway before flashing/upgrading) to prevent data loss.
Edit: Actually, thinking about it, I think Wugs added a No Wipe option to his toolkit, just flash System and Boot images from there is likely easiest for you.
Can i flash 5.1 directly ? And then root and unlock bootloader/flash TWRP again ?
tzeus said:
Can i flash 5.1 directly ? And then root and unlock bootloader/flash TWRP again ?
Click to expand...
Click to collapse
To be clear, you do not need to relock your bootloader. You can just flash 5.1 and then root and install a custom recovery like TWRP again, yes. If you are not familiar, Wug's NRT make this a breeze. Once you get 5.1 installed, just hit root. It will install the latest TWRP version and root/install SuperSU and Busybox for you.
I need to download the whole 5.1 image from Google. And flash just like any other ROM from TWRP ?
tzeus said:
I need to download the whole 5.1 image from Google. And flash just like any other ROM from TWRP ?
Click to expand...
Click to collapse
No, download the image and extract it. See this, http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app