hope some one can clarify this for me.
If I flashed twrp over stock firmware, and now I want to update the firmware, I assume by flashing the full firmware it will bring back the stock recovery? What if I just flash the OTA zip?
thanks,
Both ways will bring back stock recovery, they will also make you lose root.
Just do OTA, flash the root zip from within stock recovery, install TWRP from the GOOmanager app, done.
Very easy. Just make sure you always keep the root zip on your phone. This makes rooting after an update easier.
Sent from my X909 using Tapatalk 2
GlennE_ said:
Both ways will bring back stock recovery, they will also make you lose root.
Just do OTA, flash the root zip from within stock recovery, install TWRP from the GOOmanager app, done.
Very easy. Just make sure you always keep the root zip on your phone. This makes rooting after an update easier.
Sent from my X909 using Tapatalk 2
Click to expand...
Click to collapse
simple enough! thanks for clearing up. BTW, for re-installing the TWRP from goomanager, is there a way to do it off-line? For the recover, the goo will download the img file and auto install for you. If I updated the firmware and can I some some how flash the already downloaded recover img without re-download it each time?
thanks again,
You're welcome, happy to help.
Should be possible, but I haven't figured that out yet. I just let it redownload...
Sent from my X909 using Tapatalk 2
GlennE_ said:
You're welcome, happy to help.
Should be possible, but I haven't figured that out yet. I just let it redownload...
Sent from my X909 using Tapatalk 2
Click to expand...
Click to collapse
Just to do a follow up since I just got my phone delivered yesterday which is much sooner than anticipated. Here is what I did:
1. use CASUAL to root and installed TWRP (v 2.4xx)
2. installed Goo and updated to the latest TWRP (v 2.5)
3. reboot into TWRP and flashed the full zip for the latest 0629 firmware.
4. before reboot to system, i flashed the root.zip file.
5. reboot to system, all apps and settings are retained, system is rooted. Just out of curiosity, I reboot into recovery again and it boots right into TWRP!!?
So after full firmware flash, the TWRP recovery didn't get overwritten by the stock rom.
doesn't bother me but just confused again. May be TWRP 2.5 is able to stick even after stock firmware update?
Related
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.
As the subject mentioned, It gets auto-unrooted. So, every nightly update, I always do CF-Auto-Root to root it again.
The problem is my TWRP recovery gets wiped, and I still have to install new TWRP recovery again.
Is there any other easier rooting method which doesnt erase my TWRP recovery other than CFroot method?
khunkami said:
As the subject mentioned, It gets auto-unrooted. So, every nightly update, I always do CF-Auto-Root to root it again.
The problem is my TWRP recovery gets wiped, and I still have to install new TWRP recovery again.
Is there any other easier rooting method which doesnt erase my TWRP recovery other than CFroot method?
Click to expand...
Click to collapse
OK, that's REALLY strange... TWRP shouldn't be getting clobbered unless the way you're installing it is causing weird issues.
Have you tried flashing TWRP using heimdall/odin/JOdin? It sounds like you're using some sort of root app to flash it on-device???
As to losing root - SuperSU->Settings->Install backup script is the workaround until we integrate SuperSU into omni.
Entropy512 said:
OK, that's REALLY strange... TWRP shouldn't be getting clobbered unless the way you're installing it is causing weird issues.
Have you tried flashing TWRP using heimdall/odin/JOdin? It sounds like you're using some sort of root app to flash it on-device???
As to losing root - SuperSU->Settings->Install backup script is the workaround until we integrate SuperSU into omni.
Click to expand...
Click to collapse
I installed TWRP recovery through Goomanager, install script on the phone.
Is that why my TWRP recovery keeps getting removed everytime I do system update?
khunkami said:
I installed TWRP recovery through Goomanager, install script on the phone.
Is that why my TWRP recovery keeps getting removed everytime I do system update?
Click to expand...
Click to collapse
Possibly, goomanager might be doing something weird like doing a fakeflash. I'm not sure.
If you install a TWRP image using heimdall or odin it should persist - the dd method listed in http://teamw.in/project/twrp2/124 should work too. (i337 is the AT&T/Rogers Note2, right?)
Omni shouldn't be flashing recovery on this device (Omni only changes recovery on devices that can't change kernel without changing recovery - like the I9100/I777/N7000 and many Sonys), but even if it is, it should be flashing a TWRP build...
Entropy512 said:
Possibly, goomanager might be doing something weird like doing a fakeflash. I'm not sure.
Click to expand...
Click to collapse
I've seen / had the issue to with GooManager. Indeed it is doing a "fakeflash", if you go into recovery from GooManager you will get into the recovery but after that. If you do it on boot you won't get there. No matter what, unless you do a manual install for the recovery..
Hope this helped,
Gertlily said:
I've seen / had the issue to with GooManager. Indeed it is doing a "fakeflash", if you go into recovery from GooManager you will get into the recovery but after that. If you do it on boot you won't get there. No matter what, unless you do a manual install for the recovery..
Hope this helped,
Click to expand...
Click to collapse
I am just curious. Why does Omni Rom unroot the device after system-update?
khunkami said:
I am just curious. Why does Omni Rom unroot the device after system-update?
Click to expand...
Click to collapse
It is not only the issue on OmniROM but on (almost) every ROM, I've had the same on cyanogen and Samsung Stock.. So flashing it yourself is better.. Hope this bug will get fixed somewhere in the future.
Bye,
Sent from my Nexus 7 using Tapatalk
khunkami said:
I am just curious. Why does Omni Rom unroot the device after system-update?
Click to expand...
Click to collapse
It's because Omni doesn't have root yet. It's on the to do list. The easiest way is to install SuperSU to system, then install the back up script. That way you'll keep root through updates.
khunkami said:
As the subject mentioned, It gets auto-unrooted. So, every nightly update, I always do CF-Auto-Root to root it again.
The problem is my TWRP recovery gets wiped, and I still have to install new TWRP recovery again.
Is there any other easier rooting method which doesnt erase my TWRP recovery other than CFroot method?
Click to expand...
Click to collapse
I know very little about anything, and I was experiencing this same thing. CF-Auto-Root reinstalls stock recovery which overwrites TWRP during the rooting process. Each time I update a nightly and then run CF-Auto-Root to re-root it. After that I use mobile ODIN to reinstall TWRP recovery and all is good.
AKdballs said:
I know very little about anything, and I was experiencing this same thing. CF-Auto-Root reinstalls stock recovery which overwrites TWRP during the rooting process. Each time I update a nightly and then run CF-Auto-Root to re-root it. After that I use mobile ODIN to reinstall TWRP recovery and all is good.
Click to expand...
Click to collapse
You shouldn't be using CF-Auto-Root if you have a custom recovery (which you need in order to install Omni). Just flash SuperSU in recovery.
I knew something wasn't quite right but I did it that way because it works. I have downloaded su onto the SD card, as well as the latest nightly build of Omni. Can I install the new nightly with TWRP, and add su as a second zip to install at the same time? Or should I flash them separately?
Sent from my SGH-I337M using xda app-developers app
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?
Hi Everyone,
a little while ago, I got notification of an OTA update. My Shield Tablet is rooted, but I tried and downloaded the OTA 2.2 anyway. It failed to install the about 130MB update and after reboot I still was on 2.1 and the 2.2 notification came up again.
If your Shield Tablet is rooted, get the FULL OTA 2.2 from this thread :
https://forums.geforce.com/default/...official-feedback-thread-released-2-17-15-/4/
( get LTE or WiFi version )
then copy this about 770MB file, as well as the SuperSU.zip file to your main storage
boot into your current custom recovery and select INSTALL ZIP.....
After you flashed the OTA, flash the SuperSU.zip and reboot.
Once rebooted, re-install BusyBox and run the NextApSDFIX and reboot again !
Voi la, all set !
( you don't loose your custom recovery or anything else if you do it this way ! )
I will give this a try, thanks mate ??
The links in that post are dead for me
Sent from my SHIELD Tablet using XDA Free mobile app
tcardozo said:
The links in that post are dead for me
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
When you click on the link, you are getting some extra text. Remove everything after ".zip" and they work fine.
I can't keep root on 2.2 I am using CWM 6.0.5.0 and I tried the new TWRP and no luck. Unlocked bootloader if it helps.
On CWM: I flashed the full 2.2, wiped cache and dalvik, then re-installed SuperSU from chainfire's zip. I can't get root to stick. If I flash TWRP, recovery gets lost and I have to flash CWM. I repeat the process and nothing. Any ideas?
sixstringedmatt said:
On CWM: I flashed the full 2.2, wiped cache and dalvik, then re-installed SuperSU from chainfire's zip. I can't get root to stick. If I flash TWRP, recovery gets lost and I have to flash CWM. I repeat the process and nothing. Any ideas?
Click to expand...
Click to collapse
Did you flash the SuperSU .zip in recovery? Did you use the latest SuperSU v.2.46?
Sent from my SHIELD Tablet using XDA Free mobile app
Sure did. Downloaded straight from Chainfire's website. Unfortunately, I think I will have to revert to stock and flash 2.2. I've tried every method I know and I can't get CWM to stick or root to enable.
EDIT: I just wiped everything and went fresh. Probably needed to happen anyway. Thanks for the support!
I think I've updated to the latest version (2.2.1 is it?) and I just unlocked the bootloader. Won't I be able to flash a custom recovery and root? :/ Sorry, I'm trying to figure out why the custom recovery won't flash so when I read this I kinda panicked!
This morning I my phone pesented itself in TWRP.
Maybe this is because over the past days I repeatedly got notifications that a system upgrade wanted to install itself (I have a modified 26s X720 from Tora33).
I rejected those notifications.
Now I am stuck in TWRP and I cannot get around it. What I tried:
Reinstalling previous firmware (Tora33 26s) still on the phone
Restoring a TWRP backup from 6 months ago (TWRP didn't see it, maybe it's from a previous TWRP version, I now have v. 3.1)
Flash via fastbood factory image using Mauro's Tool All In One (error message "can't find file mke2fs.conf")
Wipe data, cache, dalvik cache, system; then install Mauro_V2.2 cleansed 23s firmware which I transferred to the phone
Every time it boots up in TWRP.
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Sent from my LEX720 using xda premium
mchlbenner said:
Your bricked you never flash ota with twrp you should read before doing anything.
The only thing that can help is ofil.
I suggest you study well before trying it.
Click to expand...
Click to collapse
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Wortelstok said:
Oh boy. Thanks anyway. OTA flashed itself, couldn't stop it. Maybe I made it worse by trying to fix.
The bootloader is not locked according to the AIO tool. I can flash succesfully any firmware, only after flashing the phone will still boot in TWRP. It is strange it still boots in TWRP. Is there no simpler trick like flashing the standard recovery and then flashing OFW?
You mention Ofil; do you think the guide described here work?
Click to expand...
Click to collapse
Yes, that QFIL guide is for the x720.
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
marik1 said:
In my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
I'll mention myself;
https://forum.xda-developers.com/le-pro3/how-to/guide-simple-to-return-to-stock-x720-t3618658
Click to expand...
Click to collapse
If he was just going back stock that would work he flash 28s ota with twrp so this will not work.
Sent from my LEX720 using xda premium
No brick after OFW push 28s
The pushed (unvoluntary) update didn't brick my phone after all. This may be important for those that have modified stock ROMs with TWRP.
Not being able to restore OFW was a bug in Mauro's All-in-One tool which he fixed last night. After I could easily flash 20S or 26S stock from his repository. I would also recommend this as safest/easiest procedure. Afterwards you can just flash TWRP from the same tool and move from there.
By the way, immediately after flashing 20s the FW notified it wanted to update itself, again!
n my opinion, the best way to return stock is to push update.zip into phones main folder, then install stock recovery, then in this one install update zip then check that OS is working. If it is, then go into twrp and wipe. Can't do it?
Click to expand...
Click to collapse
Might have tried that