Related
Ok so I just recently got my hands on a Nexus 5 which I rooted with CF Auto Root and relocked the bootloader with Bootunlocker for security (I'm guessing I should unlock before the update). I see reports surfacing of a possible 4.4.3 update in the near future. So before that happens I want to figure out the best practice for updating a N5 with CF Auto Root. It stands to reason I'll do a full backup so that's a given.
I'm not new to rooting. Done it a few times. Just haven't had a device that gets regular OTAs in my country so it hasn't come up.
Is there a way to update so that root is preserved? Obviously I'd like to keep the process as simple as possible but if I have to work from scratch it's not the end of the world.
As I understand it, you can do normal OTA as long as it's stock but you lose root. In that case, does the OTA relock the bootloader or will it stay unlocked? Which then basically means a new root which wipes the device.
Or perhaps it's better to ask what the best procedure for updating a stock Nexus 5 with CF Auto Root.
Everything that you have ever wanted to know about OTA can be found here http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
Ah thanks. Appreciate it.
generally no, after ota you lose root. but there are apps that will save your root so that you keep root after an update.
I've been looking at Survival Mode in Super SU and RootKeeper but there seems to be some question as to their success.
Reaper1242 said:
I've been looking at Survival Mode in Super SU and RootKeeper but there seems to be some question as to their success.
Click to expand...
Click to collapse
ive never used any since i dont ota, i update my custom rom as soon as its updated, but ive heard of success with rootkeeper. but it doesnt matter, it literally takes 3 minutes to root a nexus the right way(via fastboot).
Yea, I should use fastboot in future.
Reaper1242 said:
As I understand it, you can do normal OTA as long as it's stock but you lose root. In that case, does the OTA relock the bootloader or will it stay unlocked? Which then basically means a new root which wipes the device.
Click to expand...
Click to collapse
The stock Android OS update will not relock the bootloader. So, once you apply the OTA.zip file in recovery, all you will need to do is reflash the SuperSU, and you are done.
(Note that depending on your system status, you may not be able to apply the OTA.zip directly - for instance, if you have updated/deleted system files etc, in which case, you will first need to go back to stock - refer to the link that @mistahseller provided for details about how to go back to stock)
jj14 said:
The stock Android OS update will not relock the bootloader. So, once you apply the OTA.zip file in recovery, all you will need to do is reflash the SuperSU, and you are done.
(Note that depending on your system status, you may not be able to apply the OTA.zip directly - for instance, if you have updated/deleted system files etc, in which case, you will first need to go back to stock - refer to the link that @mistahseller provided for details about how to go back to stock)
Click to expand...
Click to collapse
you would need to flash a custom recovery first, then supersu in your custom recovery.
Thanks everyone for the responses.You've made everything much clearer.
simms22 said:
you would need to flash a custom recovery first, then supersu in your custom recovery.
Click to expand...
Click to collapse
Good point. I assumed that op had installed a custom recovery when he rooted, but that is not always the case.
Ok so I'm going to sideload myself. Been a while so I just want to confirm the process so I don't screw up.
I'm using TWRP
Obviously I'll do a NANdroid and probably Titanium as well.
1) Unlock bootloader with Bootunlocker
2) Connect device to PC
3) Boot into TWRP recovery and go to Advanced > ADB Sideload
4) type adb sideload update.zip (or whatever I call the file)
5) reboot device and check if it's working
6) reboot to recovery and reflash superuser.zip
I think that's it. Is there anything else I need to be aware of? If I'm right it should then be updated, rooted and in the same state before I updated.
I am in the same situation. I am currently rooted with a unlocked boot loader. When 4.4.3 comes along I plan to upgrade it. I have only rooted and have CWM no custom ROM. I know o cannot perform a OTA update. So do I copy the update zip (4.4.3) and just flash in CWM? Is this correct, and if so do I lose root/ boot loader. Thanks. I have read the thread above but do not understand
Sent from my Nexus 5 using XDA Premium 4 mobile app
dec1153 said:
I am in the same situation. I am currently rooted with a unlocked boot loader. When 4.4.3 comes along I plan to upgrade it. I have only rooted and have CWM no custom ROM. I know o cannot perform a OTA update. So do I copy the update zip (4.4.3) and just flash in CWM? Is this correct, and if so do I lose root/ boot loader. Thanks. I have read the thread above but do not understand
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Flash stock system.img and flash recovery.img and then do the update.zip from the stock recovery..
If you don't want to flash, then make sure you have removed all the modifications you have done to system apps. If you don't remember then I would certainly recommend flashing stock images...
Sent from my Nexus 5 using Tapatalk
Q&A for [ROOT] Root for SHIELD Tablet 2.0 (Lollipop)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT] Root for SHIELD Tablet 2.0 (Lollipop). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
UK Root?
Wondering if i should try root since im in UK.
Heres the boot.img from the UK update, is it any different from the NA version before i try root?
EDIT: Wont let me post outside links
Should i try it or no?
DazEB said:
Wondering if i should try root since im in UK.
Heres the boot.img from the UK update, is it any different from the NA version before i try root?
EDIT: Wont let me post outside links
Should i try it or no?
Click to expand...
Click to collapse
If it is the WiFi Only model it should work, but no promises. If it is LTE please PM the link to the boot.img
Cwm and future ota
Does CWM prevents future OTA? What if I want root but stock recovery? Thanks.
Sweet, I followed the "Locked bootloader" method step by step and it working perfectly, no problem whatsoever. Thank you very much!!
layanto said:
Does CWM prevents future OTA? What if I want root but stock recovery? Thanks.
Click to expand...
Click to collapse
Cwm had not prevented any OTAs on the shield tablet for me yet.
Sent from my SHIELD Tablet using XDA Free mobile app
Hi,
Thanks for the instructions. I followed the unlocked bootloader one, but now I cant boot. I flashed the modified LTE boot img and now everytime I boot it keeps going into fastboot mode.
Unlocked bootloader
flashed CWM
Booted into CWM and flashed SuperSU Beta
Selected Yes to fix Root
Reboot system
Boot back into fastboot and flash the modified boot.img
Reboot system...............now keeps booting into fastboot.
Please help.
EDIT: I'm an idiot. Unzip the boot.img before you flash it. Problem solved.
layanto said:
Does CWM prevents future OTA? What if I want root but stock recovery? Thanks.
Click to expand...
Click to collapse
You can also restore stock recovery afterward by flashing this
SuperPichu said:
You can also restore stock recovery afterward by flashing this
Click to expand...
Click to collapse
Possibly dumb question, but is the stock recovery on 4.4.2 KK the same as stock recovery on L? If I backup the stock recovery on KK with flashify, can I then restore once I am rooted and on L?
layanto said:
Possibly dumb question, but is the stock recovery on 4.4.2 KK the same as stock recovery on L? If I backup the stock recovery on KK with flashify, can I then restore once I am rooted and on L?
Click to expand...
Click to collapse
You can definitely restore it if you make a backup. I'm actually not sure if they are the same.
Can this be done without a computer?
Jaybenosa said:
Can this be done without a computer?
Click to expand...
Click to collapse
No
Sent from my SHIELD Tablet using XDA Free mobile app
Yah I figured. So I'm pretty much a noob and I'm trying to unlock my bootloader right now but I'm so lost lol
So I failed miserably, accidentally hit reboot system after step 4 so now I'm on lollipop not rooted and no unlocked boot loader nor have a recovery ??
Jaybenosa said:
Yah I figured. So I'm pretty much a noob and I'm trying to unlock my bootloader right now but I'm so lost lol
Click to expand...
Click to collapse
This is how to unlock the bootloader. It will erase all your userdata.
https://developer.nvidia.com/sites/...eld/SHIELD_tab/HowTo-Flash-Recovery-Image.txt
In reading through the other thread, I can't seem to definitively find what I'm looking for.
My Shield has a locked bootloader, but I've installed the OTA. Is my only option to unlock the bootloader and then follow the unlocked bootloader root method? Or is there a way to root only (I'd like to keep stock recovery) with the OTA already installed?
KentuckyHouse said:
In reading through the other thread, I can't seem to definitively find what I'm looking for.
My Shield has a locked bootloader, but I've installed the OTA. Is my only option to unlock the bootloader and then follow the unlocked bootloader root method? Or is there a way to root only (I'd like to keep stock recovery) with the OTA already installed?
Click to expand...
Click to collapse
You will have to unlock. You can restore the stock recovery afterward if you wish
Sent from my SHIELD Tablet using XDA Free mobile app
Does towelroot still work for the LTE devices when moving to lolli?
OK, so I had to unlock my bootloader since I'd already taken the OTA.
Now I'm at this point. I can't seem to get recovery to stick. I've flashed it multiple times in fastboot and it just won't stick. Now, over in the other thread, someone has asked if I've done the "fastboot flash boot boot-root.img" step yet. This confuses me, as that step comes AFTER you flash recovery, then flash SuperSU with CWM. But seeing as how I can't get recovery to stick, I can't flash SuperSU, and that means I can't move on to that step.
So I guess what I'm asking is, can I run "fastboot flash boot boot-root.img" before "fastboot flash recovery recovery.img"? Will that make a difference? Will it brick my tablet?
I'm all out of ideas here.
Locked bootloader and updated to ver 2.0 lollipop.
Hi there.
I have downloaded and installed version 2 lollipop and I would like root to store my games on SD. When checking the root guide it informed me to download update but not install. I have already installed the update and was wandering if they is a way to root my device still.
Kind regards
Hello guys!!!, Today I get the new OTA with the firmware 05Q and I install it. I see in the forum a version of 05Q rooted LINK HERE
I only want to ask if anyone know another way of get root actually or if I should wait until our amazing toolkits for 1+1 get updated.
Thanks i nadvance!!! :cyclops:
You can gain root following, This thread. If you already have a custom recovery install, might be easier to install the pre-rooted 05QA. I went the second route.
P.S. That toolkit will root 05QA, just does not have the new firmware to go back to stock.
I have a custom recovery installed ofc, if I install the pre-rooted 05Q I lost all my data and apps? Should I do a factory reset? Thanks for your fast answer mate!!
Istvan_86 said:
I have a custom recovery installed ofc, if I install the pre-rooted 05Q I lost all my data and apps? Should I do a factory reset? Thanks for your fast answer mate!!
Click to expand...
Click to collapse
If you have custom recovery installed. Do a back up first. You should not have to wipe or lose anything.
rraquib said:
If you have custom recovery installed. Do a back up first. You should not have to wipe or lose anything.
Click to expand...
Click to collapse
Really thanks again mate!! I do it, like you, as soon as possible.
Wait guys, all you need to do is flash SuperSU from your custom recovery. That's it, nothing more.
@rraquib, why on earth would you tell him to flash the entire ROM again??
timmaaa said:
Wait guys, all you need to do is flash SuperSU from your custom recovery. That's it, nothing more.
@rraquib, why on earth would you tell him to flash the entire ROM again??
Click to expand...
Click to collapse
@timmaaa Read carefully I mentioned both option and he was wondering about the pre-rooted version.
rraquib said:
@timmaaa Read carefully I mentioned both option and he was wondering about the pre-rooted version.
Click to expand...
Click to collapse
You said that flashing entire ROM would be easier, it isn't. All that's need to get root is to flash the SuperSU zip. He's already on 05Q so flashing the ROM zip is completely and utterly pointless. It's like telling someone who's run out of petrol to install a entirely new petrol tank that's full of petrol (when all that's actually needed is the fuel).
It doesn't matter what someone thinks might be the solution, if you're going to answer in the q&a section you need to give the best and easiest solution.
The thing is flashing update-supersu is not working... for me at least. I updated OTA.. After installation finished, rebooted to TWRP and tried to install update-supersuv2.37.zip...
It doesn't show any error, but when I reboot my phone there is no supersu installed ( actually there is one but it's greyed out with android icon and not showing up on application list )
timmaaa said:
Wait guys, all you need to do is flash SuperSU from your custom recovery. That's it, nothing more.
@rraquib, why on earth would you tell him to flash the entire ROM again??
Click to expand...
Click to collapse
+1
only SU from TWRP
plato79 said:
The thing is flashing update-supersu is not working... for me at least. I updated OTA.. After installation finished, rebooted to TWRP and tried to install update-supersuv2.37.zip...
It doesn't show any error, but when I reboot my phone there is no supersu installed ( actually there is one but it's greyed out with android icon and not showing up on application list )
Click to expand...
Click to collapse
Install a newer version
#stayparanoid
Sorry guys for don´t answer your comments, I have been working out of my country for a couple of weeks.
I get root on 05Q with just flashing SuperSU 2.46 from recovery. Easy and fast, just that.
Anyway you have my thanks in your respective buttons.
EDIT: If moe people with doubts read this. I use the info on this post. http://forum.xda-developers.com/showthread.php?t=2788632
Q&A for EXE/ZIP RUU M8_VZW 5.0.1 (s-off only)(newest)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for EXE/ZIP RUU M8_VZW 5.0.1 (s-off only)(newest). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
billblack said:
Long time lurker. I read and can use Google . Regardless, it failed and scared the crap out of me as it wouldn't boot. Got back into boot loader, fired up EXE again and it seems to have finished the 2nd time. A few more grey hairs, but all is good my friend. Thanks.
Click to expand...
Click to collapse
Same thing happened to me! Failed the first time around, worked the second. Booting now and it appears to be working (Android is upgrading...)
So when I use the ruu for sdcard and I reboot after I get send to recovery and can't boot system. Why is that?
EXE/ZIP RUU M8_VZW 5.0.1 Help
I installed the RUU zip via SD last night. I was running Dottat's EXE/ZIP RUU M8_VZW 4.4.4 (s-off only) with stock recovery. When I flashed the 5.0.1 RUU zip, I have a couple Partition Fails (unfortunately, I don't remember exactly which ones). However, in the time since I installed it, I saw all the new messages in the thread about others having the same Partition Fail errors. Even with the errors, my phone booted fine. I am having some weirdness though (major lag after sending a message in Facebook Messenger app....a reboot resolves the lag for a little while, then it returns; Verizon Caller ID app won't load; logging in to Swiftkey keyboard's cloud with my Google account fails with an error). So I see the new zip to flash the L Hboot BEFORE flashing the RUU. Obviously too late for that. Also, I installed TWRP recovery in place of the stock recovery.
So my question is: How should I proceed with trying to get the 5.0.1 to flash with no errors? Should I install Dottat's 4.4.4 (s-off), which will get me back to stock recovery...then let it boot up. Then flash the L hboot, and then finally flash the 5.0.1 RUU? Or are there other alternatives?
Thanks!
mbarcus said:
I installed the RUU zip via SD last night. I was running Dottat's EXE/ZIP RUU M8_VZW 4.4.4 (s-off only) with stock recovery. When I flashed the 5.0.1 RUU zip, I have a couple Partition Fails (unfortunately, I don't remember exactly which ones). However, in the time since I installed it, I saw all the new messages in the thread about others having the same Partition Fail errors. Even with the errors, my phone booted fine. I am having some weirdness though (major lag after sending a message in Facebook Messenger app....a reboot resolves the lag for a little while, then it returns; Verizon Caller ID app won't load; logging in to Swiftkey keyboard's cloud with my Google account fails with an error). So I see the new zip to flash the L Hboot BEFORE flashing the RUU. Obviously too late for that. Also, I installed TWRP recovery in place of the stock recovery.
So my question is: How should I proceed with trying to get the 5.0.1 to flash with no errors? Should I install Dottat's 4.4.4 (s-off), which will get me back to stock recovery...then let it boot up. Then flash the L hboot, and then finally flash the 5.0.1 RUU? Or are there other alternatives?
Thanks!
Click to expand...
Click to collapse
Run it once more. The failed PU was for the data partition. If you run it once more it will be successful. I think the root cause here is the changes to partitions that occurred with this OTA and that the likely solution is to flash the L hboot first before doing the RUU to L. Once on L firmware/OS you can use the RUU again with no issues.
One big dang speed bump in all the fun.
dottat said:
Run it once more. The failed PU was for the data partition. If you run it once more it will be successful. I think the root cause here is the changes to partitions that occurred with this OTA and that the likely solution is to flash the L hboot first before doing the RUU to L. Once on L firmware/OS you can use the RUU again with no issues.
One big dang speed bump in all the fun.
Click to expand...
Click to collapse
Can I run the RUU again using TWRP? Or do I need to be on Stock Recovery? And thank you for your help!!
mbarcus said:
Can I run the RUU again using TWRP? Or do I need to be on Stock Recovery? And thank you for your help!!
Click to expand...
Click to collapse
recovery doesnt' weigh in here. You can install it from bootloader using the SD card method.
How do I flash L Hboot? with twrp? do I have to flash it or can I just use the ruu to get to the new 5.0.1 firmware? thanks
So you asked to report our experience ...
First, let me say thanks. I am now on 5.0.1 and back to root thanks to your work and willingness to share.
Background:
I was stock 4.4.4, unlocked, s-off with TWRP recovery when the VZW 5.0.1 OTA hit. I had a number of bloatware apps frozen through Titanium Backup and probably due to a combination of all that I couldn't load the update. Reflashing boot, system and recovery still wouldn't let me take the OTA, so I ended up using HTC SyncManager repair to make Verizon happy. I got the update, kept unlocked and s-off, but lost root.
Recovering Root:
After finding your stuff, I first tried loading through the bootloader with your zips in the root of my SD card (128 GB, single partition, exFAT). No go for either the hboot or the RUU. both gave me a "Wrong image" message and only allowed reboot to system.
So the next step was to try flashing with TWRP. I flashed TWRP 2.8.5.0 via fastboot and then let it do all it's stuff (Busybox, SuperSU, SD Card Fix, etc.) , rebooted to system just to have everything catch up to itself, and then rebooted to TWRP recovery. I then flashed the hboot and the RUU through TWRP, rebooted, and I'm back to full root.
So again, thanks! A happy camper backing everything up with Titanium again and hoping that you really wanted to hear a real-world experience.
A_Levis said:
First, let me say thanks. I am now on 5.0.1 and back to root thanks to your work and willingness to share.
Background:
I was stock 4.4.4, unlocked, s-off with TWRP recovery when the VZW 5.0.1 OTA hit. I had a number of bloatware apps frozen through Titanium Backup and probably due to a combination of all that I couldn't load the update. Reflashing boot, system and recovery still wouldn't let me take the OTA, so I ended up using HTC SyncManager repair to make Verizon happy. I got the update, kept unlocked and s-off, but lost root.
Recovering Root:
After finding your stuff, I first tried loading through the bootloader with your zips in the root of my SD card (128 GB, single partition, exFAT). No go for either the hboot or the RUU. both gave me a "Wrong image" message and only allowed reboot to system.
So the next step was to try flashing with TWRP. I flashed TWRP 2.8.5.0 via fastboot and then let it do all it's stuff (Busybox, SuperSU, SD Card Fix, etc.) , rebooted to system just to have everything catch up to itself, and then rebooted to TWRP recovery. I then flashed the hboot and the RUU through TWRP, rebooted, and I'm back to full root.
So again, thanks! A happy camper backing everything up with Titanium again and hoping that you really wanted to hear a real-world experience.
Click to expand...
Click to collapse
There's just one problem with this all.... lol...
you can't flash the RUU or hboot zips through TWRP.
..
dottat said:
There's just one problem with this all.... lol...
you can't flash the RUU or hboot zips through TWRP.
Click to expand...
Click to collapse
Well, XDA does call me a "Junior Member". Probably a good reason for that.
Looking back at the TWRP log, it seems you are right and my attempts to flash hboot and RUU from TWRP failed (but any indication of that flashed by so fast that I couldn't tell). So does that mean that my fastboot flash of TWRP recovery opened up everything that I needed to get root directly from TWRP (installation of BusyBox and SuperSU)?
A_Levis said:
Well, XDA does call me a "Junior Member". Probably a good reason for that.
Looking back at the TWRP log, it seems you are right and my attempts to flash hboot and RUU from TWRP failed (but any indication of that flashed by so fast that I couldn't tell). So does that mean that my fastboot flash of TWRP recovery opened up everything that I needed to get root directly from TWRP (installation of BusyBox and SuperSU)?
Click to expand...
Click to collapse
Most recoveries will offer to flash su on an unrooted rom. You can either do that or manually flash the newest supersu.zip After you boot up you can install busybox from an app like this... https://play.google.com/store/apps/details?id=stericson.busybox
So what rom/firmware are you currently on?
After using the RUU, it finished with a successful update. I booted into recovery to create a backup, but now when I try to boot back into the OS, it goes back into TWRP like it would if I were booting into recovery. Anyone have any ideas?
---------- Post added at 10:30 PM ---------- Previous post was at 10:25 PM ----------
Nickchapstick said:
So when I use the ruu for sdcard and I reboot after I get send to recovery and can't boot system. Why is that?
Click to expand...
Click to collapse
After looking for a little bit, it appears I'm having a similar issue.
klw7890 said:
After using the RUU, it finished with a successful update. I booted into recovery to create a backup, but now when I try to boot back into the OS, it goes back into TWRP like it would if I were booting into recovery. Anyone have any ideas?
---------- Post added at 10:30 PM ---------- Previous post was at 10:25 PM ----------
After looking for a little bit, it appears I'm having a similar issue.
Click to expand...
Click to collapse
You were able to boot up the OS successfully the first time right?
dottat said:
You were able to boot up the OS successfully the first time right?
Click to expand...
Click to collapse
Yes. It booted to OS the first time, after the RUU completed, but now it just boots back into recovery.
klw7890 said:
Yes. It booted to OS the first time, after the RUU completed, but now it just boots back into recovery.
Click to expand...
Click to collapse
Stock recovery?
dottat said:
Stock recovery?
Click to expand...
Click to collapse
Initially, yes. I flashed the latest TWRP. I think I might have flashed the wrong version. I'm rerunning the RUU. I really appreciate the help.
If it was the right version by chance, do you have any idea what could've caused that?
klw7890 said:
Initially, yes. I flashed the latest TWRP. I think I might have flashed the wrong version. I'm rerunning the RUU. I really appreciate the help.
If it was the right version by chance, do you have any idea what could've caused that?
Click to expand...
Click to collapse
Did you use flashify? Reason I ask is that app still thinks it's a Sprint phone. Use the twrp I have posted in the op.
dottat said:
Did you use flashify? Reason I ask is that app still thinks it's a Sprint phone. Use the twrp I have posted in the op.
Click to expand...
Click to collapse
"That app" being TWRP Manager?
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Dito13 said:
Hey there fellow U11 Users,
I just received the update concerning 60fps HD-Video etc. I use TWRP so the update can't be installed by itself. So I have two questions:
A
Where do I find the update file. I looked around a lot but couldn't locate it.
B
Once found, can I just flash it with TWRP?
Thanks in advance!
Click to expand...
Click to collapse
See here: https://forum.xda-developers.com/u11/how-to/collection-htcu-u11-ruu-firmware-t3612048/page63
Alright, thanks! :good: That only leaves the first question unanswered.
Dito13 said:
Alright, thanks! :good: That only leaves the first question unanswered.
Click to expand...
Click to collapse
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Thank you kindly!
OMJ said:
/data/data/com.htc.updater/files
btw...twrp can install the update but you need to flash the firmware.zip inside the ota manually
Click to expand...
Click to collapse
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Dito13 said:
Just to be clear: I only flash the firmware.zip manually via TWRP or do I need to flash the whole ota?
Sorry for the question. I mostly handled Nexus devices...
Click to expand...
Click to collapse
twrp will install the ota zip but it wont install the firmware.zip inside, you have to extract & manually install from download mode
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Dito13 said:
grrr.... I tried following your suggestions, but recieved error 7 in TWRP. Can you help me in the right direction?
Click to expand...
Click to collapse
list your steps your using to install the ota via twrp....personally, I let the system initiate the install (booted into OS) as if I was 100% stock, once twrp loads, it automatically installs except for the firmware.zip
more details here...
OK, I am a Noob to the HTC world. I am used to easy flashing/rooting/etc. on Nexus devices.
TWRP doesn't do anything after accepting the ota. When I try to install the OTA via TWRP I receive Error 7. I worked my way through a lot of guides here on XDA concerning manual OTA installing. One thing I tried was flashing back to stock recovery which I found in the firmware.zip of the OTA in bootloader mode. That failed also ("FAILED (remote: not allowed on PRODUCTION device).
Edit: The device has obviously an unlocked bootloader, s-on, rooted via magisk and is a DGLU device, software number 1.16.400.5
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
schmeggy929 said:
Are you on an Untouched System Image? Completely stock ROM? While it is great we can flash the OTA in TWRP, the system stills needs to be stock, and of course will still have to fastboot firmware.
Click to expand...
Click to collapse
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Dito13 said:
Yes, everything is stock.
I managed to flash the stock recovery now. I didn't remember to use the download mode /sorry. Then Then I checked for the ota again, downloaded it and tried to apply but I landed in the stock recovery with the red exclamation mark and then nothing happened.
Click to expand...
Click to collapse
re-flash twrp and try it again.
schmeggy929 said:
re-flash twrp and try it again.
Click to expand...
Click to collapse
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Dito13 said:
Same result unfortunately. TWRP hands out Error 7 and "system partition has unexpected contents" or something like that although I didn't do any tinkering with the stock rom. I flashed Magisk and did a backup before and that was all.
Click to expand...
Click to collapse
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
schmeggy929 said:
Only thing I would say is start fresh. Backup all the data for your apps first. Flash the RUU, Take the OTA and reinstall all your apps.
Click to expand...
Click to collapse
Thanks again - seems to have worked. It will be interesting to see which problems occur with the Android Oreo update which was announced till the end of the year by HTC