Database Info

[Q] Recovery

Just about to finish with the 2.20 exploit when I ran into a hiccup and now my bootloader screen shows TAMPERED with UNCLOCKED right below it. I just backed up my current system, am I to reboot or can I stay in TWRP and flash the perm root without having to reboot?

thinkhope said:
Just about to finish with the 2.20 exploit when I ran into a hiccup and now my bootloader screen shows TAMPERED with UNCLOCKED right below it. I just backed up my current system, am I to reboot or can I stay in TWRP and flash the perm root without having to reboot?
Click to expand...
Click to collapse
What are you trying to do? Flash the SU.zip onto your stock ROM? if so, just flash it in TWRP and reboot.

absolutelygrim said:
What are you trying to do? Flash the SU.zip onto your stock ROM? if so, just flash it in TWRP and reboot.
Click to expand...
Click to collapse
Yes. Is the tampered message anything to worry about? I pushed the SU .zip and rebooted and phone seems to work fine, though it seems like I don't have LTE all of a sudden.

thinkhope said:
Yes. Is the tampered message anything to worry about? I pushed the SU .zip and rebooted and phone seems to work fine, though it seems like I don't have LTE all of a sudden.
Click to expand...
Click to collapse
No, tampered just means /system partition was modified, most likely due to su being present in /system/xbin
Now that su is there, do you have a superuser app, such as SuperSU? If not, download it from the market and run the program to update your su binary and get configured. As for the LTE, I don't know

absolutelygrim said:
No, tampered just means /system partition was modified, most likely due to su being present in /system/xbin
Now that su is there, do you have a superuser app, such as SuperSU? If not, download it from the market and run the program to update your su binary and get configured. As for the LTE, I don't know
Click to expand...
Click to collapse
Thanks! Yes I do, I installed root checker just to double check and I indeed have root access. Now onto flashing a custom ROM. If someone can just give me a nod and let me know I'm heading in the right direction, I'd really appreciate it.
I'm going to use AOKP JellyBean. I download it, extract the boot.img to my fastboot folder, open up a cmd and "fastboot flash boot boot.img" Can I delete the boot.img from the ROM zip file after I flashed it throught fastboot? This is where Im getting a little confused.

thinkhope said:
Thanks! Yes I do, I installed root checker just to double check and I indeed have root access. Now onto flashing a custom ROM. If someone can just give me a nod and let me know I'm heading in the right direction, I'd really appreciate it.
I'm going to use AOKP JellyBean. I download it, extract the boot.img to my fastboot folder, open up a cmd and "fastboot flash boot boot.img" Can I delete the boot.img from the ROM zip file after I flashed it throught fastboot? This is where Im getting a little confused.
Click to expand...
Click to collapse
Yes, but you don't have to. It should work as long as you already flashed boot.img from fastboot

absolutelygrim said:
Yes, but you don't have to. It should work as long as you already flashed boot.img from fastboot
Click to expand...
Click to collapse
Thank you very much!!
Sent from my One X using xda app-developers app

how to update to 4.4.x after this... New to android

First of all, I have been reading this forum for about two weeks and just registered in order to get some help as I do not want to break my one week old nexus 5.
From my reading, the updates can be done in quite different ways and because of that I want to be sure what I should do.
I started by:
- root the mobile with cf-auto root. It did everything for me, got the superuser icon automatically
- installed clockwork mod and I have the custom recovery. By the way, I made a backup with it but where was it written? I want to copy it to my pc.
- other than that, I have installed some root only apps like rom manager, greenify, root Explorer, etc. I supported those developers with purchase. Those guys deserve it.
Anyway, i am looking for the safe way to update to 4.4.1. I read some members saying they lost root after the update, others lost something else (I am referring to the thread on nexus 5 general forum).
Can you help me? What path shall I go? Thanks a lot.

To update you'll basically have to go back to stock in a way. By that I mean you can either flash the System.img file from the Factory Image and then update using the update files for 4.4.1 by flashing it in recovery (via Sideload) and then just root again. OR you can install an updated "Stock" 4.4.1 image from the development section and root that.

cesar.maranhao said:
- installed clockwork mod and I have the custom recovery. By the way, I made a backup with it but where was it written? I want to copy it to my pc.
Click to expand...
Click to collapse
Hi, your backups are in /mnt/shell/emulated/clockworkmod/backup/
Copy to your PC with 'adb pull /mnt/shell/emulated/clockworkmod/backup'
Cheers

shotta35 said:
To update you'll basically have to go back to stock in a way. By that I mean you can either flash the System.img file from the Factory Image and then update using the update files for 4.4.1 by flashing it in recovery (via Sideload) and then just root again. OR you can install an updated "Stock" 4.4.1 image from the development section and root that.
Click to expand...
Click to collapse
i sense i am getting somewhere but how do i do that? i am new to this and been reading a lot but the first time all seems very vague. i need a little more help from you!
lets assume i want to just apply the 4.4.1 update (maybe this is the easiest way for now). how do i do it?
also, after the update succeds, i need to root again correct? what happens to all the apps i have right now with root permissions? do they stop working until i root again and give them root privileges again? can i use the cf auto root again?
also, i am on ART, i thought of letting you know since that can cause some problems updating(??)

finistere said:
Hi, your backups are in /mnt/shell/emulated/clockworkmod/backup/
Copy to your PC with 'adb pull /mnt/shell/emulated/clockworkmod/backup'
Cheers
Click to expand...
Click to collapse
thanks!
one more thing...
can't i copy that folder like a regular folder? just copy paste?
or move that folder (with root explorer) to my dropbox folder?

cesar.maranhao said:
i sense i am getting somewhere but how do i do that? i am new to this and been reading a lot but the first time all seems very vague. i need a little more help from you!
lets assume i want to just apply the 4.4.1 update (maybe this is the easiest way for now). how do i do it?
also, after the update succeds, i need to root again correct? what happens to all the apps i have right now with root permissions? do they stop working until i root again and give them root privileges again? can i use the cf auto root again?
also, i am on ART, i thought of letting you know since that can cause some problems updating(??)
Click to expand...
Click to collapse
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
cesar.maranhao said:
thanks!
one more thing...
can't i copy that folder like a regular folder? just copy paste?
or move that folder (with root explorer) to my dropbox folder?
Click to expand...
Click to collapse
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.

shotta35 said:
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
Click to expand...
Click to collapse
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!

cesar.maranhao said:
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
Click to expand...
Click to collapse
You do it from Recovery. So just copy the file to the phone in some folder. You can't update the phone with it running. So reboot to CWM and then choose Install from ZIP then find the file on your storage and then choose update. That may or may not work as I said depending.
-----------------
Plenty of these questions around... check them out first.
http://forum.xda-developers.com/showthread.php?t=2561198
http://forum.xda-developers.com/showthread.php?p=47369234
http://forum.xda-developers.com/showthread.php?t=2561076

shotta35 said:
If you want to apply the new update it all depends on your current setup. I gave you vague options because I don't know what you've done to your phone. If you've only rooted and not changed any of the files in system then it's easy to just flash the update with the recovery. You can download the update and then start recovery (look it up). Once in recovery start ADB sideload and connect to your PC (this assumes you already have working ADB, if not.... look it up ). To sideload you just need to adb sideload filename.zip. You can probably use WugFresh's Toolkit to also sideload but I generally don't use those so dunno what they do these days. Much easier to learn and understand what it does then do it yourself.
If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery.
You can just copy it, no need to use ADB but this is why it's good to know how to use ADB.
Click to expand...
Click to collapse
cesar.maranhao said:
thanks for the reply. i am reading on the adb sideload right now... i already have the update zip inside the platform tools. however, in the command prompt, it says my device is unauthorized (i have both the usb debugging and unknown sources ticked). the nexus 5 is connected as MTP.
any clues?
about what i have done to my nexus, i applied the cf autoroot, installed clockwork mod... nothing much besides some play store apps..
as for this paragraph:
"If you have a custom recovery you might just be able to flash the update with the recovery like you normally flash any zip in recovery. "
i have never done it, hence all these questions!
Click to expand...
Click to collapse
shotta35 said:
You do it from Recovery. So just copy the file to the phone in some folder. You can't update the phone with it running. So reboot to CWM and then choose Install from ZIP then find the file on your storage and then choose update. That may or may not work as I said depending.
-----------------
Plenty of these questions around... check them out first.
http://forum.xda-developers.com/showthread.php?t=2561198
http://forum.xda-developers.com/showthread.php?p=47369234
http://forum.xda-developers.com/showthread.php?t=2561076
Click to expand...
Click to collapse
yes, i have been reading those topics and many others.. i managed to solve the adb device unauthorized anyway. just flashed the 4.4.1 zip file under clockwork mod recover.. android is upgrading at the moment. lets see if everything is work as it should.

No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM (install file from internal storage).. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.

RusherDude said:
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM.. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
Click to expand...
Click to collapse
yes, everything is fine. 4.4.1 loaded fine without any errors. i have root checker and when i tested, it says i do not have proper root access. i also lost my clockwork mod recovery.
i am now checking into it to see what needs to be done to gain root access again and get the custom recovery as it was before the update.

cesar.maranhao said:
yes, everything is fine. 4.4.1 loaded fine without any errors. i have root checker and when i tested, it says i do not have proper root access. i also lost my clockwork mod recovery.
i am now checking into it to see what needs to be done to gain root access again and get the custom recovery as it was before the update.
Click to expand...
Click to collapse
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..

RusherDude said:
No need to sideload adb bla bla..
copy the OTA zip into the phone, and just flash it in CWM (install file from internal storage).. 1 minute and done.
You'll get error status 7 at checking if you changed something in system (apart from rooting), else you shouldn't have any problem.
Click to expand...
Click to collapse
RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
i see. things are starting to make sense for me.
before reading you post, i tried to get the clockwork mod recovery through the Rom Manager App. it failed. i am now looking for those files you mentioned.
EDIT: i am at the clockworkmod recovery website... is the file i want an IMG?

cesar.maranhao said:
i see. things are starting to make sense for me.
before reading you post, i tried to get the clockwork mod recovery through the Rom Manager App. it failed. i am now looking for those files you mentioned.
EDIT: i am at the clockworkmod recovery website... is the file i want an IMG?
Click to expand...
Click to collapse
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.

RusherDude said:
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
Click to expand...
Click to collapse
but how do i install it? when i go into recovery it only gives me 4 options:
reboot system now
apply update from adb
wipe cache/factory reset
wipe cache partition
i am lost

cesar.maranhao said:
but how do i install it? when i go into recovery it only gives me 4 options:
reboot system now
apply update from adb
wipe cache/factory reset
wipe cache partition
i am lost
Click to expand...
Click to collapse
That's the stock recovery, you can't do nothing from there.
You need to flash the recovery via fastboot (didn't you do that the first time to get your custom recovery..?)
Check this tutorial mate: http://forum.xda-developers.com/showthread.php?t=2507905

RusherDude said:
You'd only be looking for the supersu binaries, since you already have the recovery IMG from te previous time, right? (the one that you need for fastboot).
EDIT: Yes, IMG files are for fastboot, ZIP files for recovery.
Click to expand...
Click to collapse
RusherDude said:
That's the stock recovery, you can't do nothing from there.
You need to flash the recovery via fastboot (didn't you do that the first time to get your custom recovery..?)
Check this tutorial mate: http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
no, i got the custom recovery when i installed clockworkmod recovery from the play store. i am now reading the thread you linked me! thanks!

cesar.maranhao said:
no, i got the custom recovery when i installed clockworkmod recovery from the play store. i am now reading the thread you linked me! thanks!
Click to expand...
Click to collapse
done it! i now have root again and the clockworkmod custom recovery! nice!
:good:

RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
from where can i get the flashable clokwork mod recovery zip file?
i am going to apply the 4.4.2 update now and will be doing it this way:
from the recovery apply the 4.4.2 zip. after this apply the supersu zip. i want to install the custom recovery zip too so when the phone restarts everything will be configured. is this possible?

RusherDude said:
You need to flash the recovery again via fastboot (youll lose it every time, unless you flash the flashable recovery ZIP just after flashing the OTA and before rebooting the phone).You'll have this problem every OTA unless you flash the zipped version everytime.
I'd recommend the easy way to root, get the SuperSU binaries and flash them through the custom recovery and you're done..
Click to expand...
Click to collapse
well, it seems i haven't lost my custom recovery. was it because i installed the supersu before rebooting?

Block OTA Updates

I am S-off and rooted on Verizon. What file or files do I have to freeze via TBU to not get the soon to be released update ?
Thanks in advance

jjmstang said:
I am S-off and rooted on Verizon. What file or files do I have to freeze via TBU to not get the soon to be released update ?
Thanks in advance
Click to expand...
Click to collapse
delete or rename from .apk to .bak
system/app
HtcOMADM_SettingsPlugin_VZW.apk
HtcOMADM_VZW.apk

jjmstang said:
I am S-off and rooted on Verizon. What file or files do I have to freeze via TBU to not get the soon to be released update ?
Thanks in advance
Click to expand...
Click to collapse
A custom recovery like CWM or TWRP should also cause the update to fail.

Okay thanks for the quick responses

Figured I'd add on to these answers.
Modifying anything will pretty much mess up the OTA's. As far as I know if everything is not 100% stock (besides S-OFF & bootloader unlock) then the update will fail.
Root your phone = failed update
Custom recovery = failed update
Edit a file in /system (add a line or remove a line or change 0 to 1 in something) = failed update
Etc

Can't you just freeze the Updater 6. whatever with titanium?

Mudvayne622 said:
Can't you just freeze the Updater 6. whatever with titanium?
Click to expand...
Click to collapse
Yes, that will prevent a nag, but it would still allow you to manually update it in settings.
I'd follow what Andy said, then it's for sure unable to update
Sent from my HTC6525LVW using Tapatalk
---------- Post added at 04:13 PM ---------- Previous post was at 04:07 PM ----------
S1L3nTShaDoWz said:
Figured I'd add on to these answers.
Modifying anything will pretty much mess up the OTA's. As far as I know if everything is not 100% stock (besides S-OFF & bootloader unlock) then the update will fail.
Root your phone = failed update
Custom recovery = failed update
Edit a file in /system (add a line or remove a line or change 0 to 1 in something) = failed update
Etc
Click to expand...
Click to collapse
This is mostly true, but sometimes the overall update will fail but bits and pieces of it will actually pass. This is exactly what you don't want.
For example, a new bootloader would pass, but the system and the recovery push would fail. This could potentially lock your bootloader. It's still better to stop the update without giving it a chance to install, despite having root and a custom recovery.
Sent from my HTC6525LVW using Tapatalk

Dougau said:
A custom recovery like CWM or TWRP should also cause the update to fail.
Click to expand...
Click to collapse
It will cause it not to install, but won't stop the nag to install the OTA.

Can't you stop it by going into About/software update and unchecking auto download?

Thanks I wasn't sure. This is my first HTC (former Motorola fan). Even once the developers get ahold of the update and create a flashable zip for us do we still need to put the stock recovery back or flash the update.zip in custom recovery? I'm S-Off, BL unlocked and rooted with TWRP.
---------- Post added at 08:06 PM ---------- Previous post was at 08:01 PM ----------
OdinValknir said:
Can't you stop it by going into About/software update and unchecking auto download?
Click to expand...
Click to collapse
Once I saw this I was curious about that option. But every time I go into About/Software Update, settings crashes. Maybe due to Sense 6 Toolbox in my settings menu?

I'm not 100% sure... I am actually curious about all this too... This phone is the first and only phone I've ever unlocked/rooted/ S-off etc.... I'm currently running Venom Viper ONE ROM on Here and have neglected to flash the most current version bc it's based on 4.3
I'm still waiting to see how it all pans out... And clueless as to how to update kitkat once it does come through... Whether I can do it manually... Or if I have to go back to stock sense 6 so on and so forth... Guess we shall see

OdinValknir said:
I'm not 100% sure... I am actually curious about all this too... This phone is the first and only phone I've ever unlocked/rooted/ S-off etc.... I'm currently running Venom Viper ONE ROM on Here and have neglected to flash the most current version bc it's based on 4.3
I'm still waiting to see how it all pans out... And clueless as to how to update kitkat once it does come through... Whether I can do it manually... Or if I have to go back to stock sense 6 so on and so forth... Guess we shall see
Click to expand...
Click to collapse
You can do it manually through fastboot, all you're going to want to update is the firmware.
Sent from my HTC6525LVW using Tapatalk

BadUsername said:
You can do it manually through fastboot, all you're going to want to update is the firmware.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Through fastboot? I have never seen an option for firmware or update in fastboot... Again.. forgive me I am still relatively new to all this

OdinValknir said:
Through fastboot? I have never seen an option for firmware or update in fastboot... Again.. forgive me I am still relatively new to all this
Click to expand...
Click to collapse
It's not going to update the rom, but it'll update your baseband and other firmware, you can package it in a flashable zip and flash it in a custom recovery or with the fastboot flash command.
Sent from my HTC6525LVW using Tapatalk

andybones said:
delete or rename from .apk to .bak
system/app
HtcOMADM_SettingsPlugin_VZW.apk
HtcOMADM_VZW.apk
Click to expand...
Click to collapse
Will renaming the files with ES File Explorer work instead of TBU. I had to schedule the update for later this evening, hoping that I can rename with ES and be done with it.

GarnerArms said:
Will renaming the files with ES File Explorer work instead of TBU. I had to schedule the update for later this evening, hoping that I can rename with ES and be done with it.
Click to expand...
Click to collapse
Yessir, just rename to .bak rather than .apk

Awesome. Do I need to rename both or just the setting plug-in?
Sent from my HTC6525LVW using XDA Free mobile app

BadUsername said:
Yes, that will prevent a nag, but it would still allow you to manually update it in settings.
I'd follow what Andy said, then it's for sure unable to update
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
FYI: I froze the updater w/ TBU and the nag continued to....nag. I renamed the APK files and so far so good.

andybones said:
Yessir, just rename to .bak rather than .apk
Click to expand...
Click to collapse
Andy, good to see you on here with the M8
I had the G3 for a couple weeks...it was ok I guess, but I already have a tablet. Ha, needed to be able to hold my phone with one hand. G3 is overrated!
I'm about to root and I'll be sure to try out any ROMs you have made for the M8!!

S1L3nTShaDoWz said:
Figured I'd add on to these answers.
Modifying anything will pretty much mess up the OTA's. As far as I know if everything is not 100% stock (besides S-OFF & bootloader unlock) then the update will fail.
Root your phone = failed update
Custom recovery = failed update
Edit a file in /system (add a line or remove a line or change 0 to 1 in something) = failed update
Etc
Click to expand...
Click to collapse
I was rooted with weaksauce and it pestered me with the update relentlessly. Every time I turned on the phone I had to click a bunch of junk to get rid of it. Unfortunately I did not realize this was a full OS update, it just mentioned updating to the fancy charging thing and clicked "yes" to be rid of the annoyance. As soon as I clicked it my phone rebooted and I knew I was in trouble. Lost root and can't get it back without paying for sunshine. I'm poor!

[Q] Not sure what to do. Stuck at HTC boot screen

Have a rooted Verizon HTC One M8. Didn't have a custom rom on it. I was just happy with not having ads, and being able to have access to files on the phone. The one problem that I kept having was it constantly telling me that I needed to do an update. I tried freezing Update files in Titanium Backup, but I would still see the notifications. Followed advice elsewhere on the internet, and tried to Force Close Download Manager. I then went into TWRP and wiped Cache and Dalvic Cache. Now, it's completely stuck on the white HTC screen on bootup. I can boot into Recovery, but I'm not sure what to do to get the phone back to working condition.
Please help! This is not the Sunday afternoon that I was envisioning today. I just wanted the update notifications to stop.

SmoovySmoov said:
Have a rooted Verizon HTC One M8. Didn't have a custom rom on it. I was just happy with not having ads, and being able to have access to files on the phone. The one problem that I kept having was it constantly telling me that I needed to do an update. I tried freezing Update files in Titanium Backup, but I would still see the notifications. Followed advice elsewhere on the internet, and tried to Force Close Download Manager. I then went into TWRP and wiped Cache and Dalvic Cache. Now, it's completely stuck on the white HTC screen on bootup. I can boot into Recovery, but I'm not sure what to do to get the phone back to working condition.
Please help! This is not the Sunday afternoon that I was envisioning today. I just wanted the update notifications to stop.
Click to expand...
Click to collapse
Were You temp rooted or did you s off?

dottat said:
Were You temp rooted or did you s off?
Click to expand...
Click to collapse
I am S-Off'd.

SmoovySmoov said:
I am S-Off'd.
Click to expand...
Click to collapse
I have two solutions. One that wipes and one that doesn't. The one that doesn't you will need to reflash twrp and a su.zip when done but it's easy. Sound ok?
Run the exe on the first post here. Make sure your phone is in fastboot mode.
http://forum.xda-developers.com/showthread.php?t=2883845
Official RUU 3.28.605.4 EXE/ZIP

dottat said:
I have two solutions. One that wipes and one that doesn't. The one that doesn't you will need to reflash twrp and a su.zip when done but it's easy. Sound ok?
Run the exe on the first post here. Make sure your phone is in fastboot mode.
http://forum.xda-developers.com/showthread.php?t=2883845
Official RUU 3.28.605.4 EXE/ZIP
Click to expand...
Click to collapse
So this would take me back to not rooted, or am I reading that incorrectly? If so, is there no way to stay rooted, just to reflash stock rom?

Yes. But you will still get nagged to update too. If you want to simply flash stock then flash this one via recovery. http://forum.xda-developers.com/showthread.php?t=2914922
[ROM][10/22/14] - Stock Rooted 4.4.4 - OTA 3.28.605.4 - W/P - BusyBox and Root - UP!
Rerooting the phone after updating using the exe is easy to do though
SmoovySmoov said:
So this would take me back to not rooted, or am I reading that incorrectly? If so, is there no way to stay rooted, just to reflash stock rom?
Click to expand...
Click to collapse

dottat said:
Yes. But you will still get nagged to update too. If you want to simply flash stock then flash this one via recovery. http://forum.xda-developers.com/showthread.php?t=2914922
[ROM][10/22/14] - Stock Rooted 4.4.4 - OTA 3.28.605.4 - W/P - BusyBox and Root - UP!
Rerooting the phone after updating using the exe is easy to do though
Click to expand...
Click to collapse
So, I have your original method downloading. Are you saying that after I flash that, and then reroot it (which I will need help with as well, since I used Sunshine before), I won't get nagged to do an update all the time?

SmoovySmoov said:
So, I have your original method downloading. Are you saying that after I flash that, and then reroot it (which I will need help with as well, since I used Sunshine before), I won't get nagged to do an update all the time?
Click to expand...
Click to collapse
You will be up to date. When you flash twrp You can grab the latest su.zip from here http://download.chainfire.eu/supersu
Wipe cache when flashing su.
Sunshine was an exploit to gain s off. Not root. S off means you can flash whatever you want. In this case, root is just an app you flash.

dottat said:
You will be up to date. When you flash twrp You can grab the latest su.zip from here http://download.chainfire.eu/supersu
Wipe cache when flashing su.
Sunshine was an exploit to gain s off. Not root. S off means you can flash whatever you want. In this case, root is just an app you flash.
Click to expand...
Click to collapse
Still have about 15 minutes on the download. Sorry for all the questions, but I want to make sure I get what all you are saying.
1) Once the download finishes, I run the program and follow the prompts. This will return me to stock, not rooted.
2) I then need to flash SuperSU using TWRP. This will get me rooted again? Where do I place the .zip on my external SD card? I've had problems with TWRP in that I never see anything that I can install when I go to the Install screen there. It just says TWRP. No files. I try to navigate to the external SD, but there's never anything there that I can install.

SmoovySmoov said:
Still have about 15 minutes on the download. Sorry for all the questions, but I want to make sure I get what all you are saying.
1) Once the download finishes, I run the program and follow the prompts. This will return me to stock, not rooted.
2) I then need to flash SuperSU using TWRP. This will get me rooted again? Where do I place the .zip on my external SD card? I've had problems with TWRP in that I never see anything that I can install when I go to the Install screen there. It just says TWRP. No files. I try to navigate to the external SD, but there's never anything there that I can install.
Click to expand...
Click to collapse
You have a working fastboot/adbsetup? You only need fastboot for this exercise to work.
---------- Post added at 03:19 PM ---------- Previous post was at 03:09 PM ----------
Here's a quick how to..for after you run that exe.
Take the su.zip to your internal storage.
Download twrp 2.8.1.0 here
http://techerrata.com/browse/twrp2/m8_wlv
Download fastboot/adb here
https://www.androidfilehost.com/?fid=23501681358559711
Extract the fastboot/adb zip. Copy the new twrp image into this new folder. Open the newly extracted folder and while holding the shift button right click on your mouse. Select open command prompt here.
Put phone in fastboot mode and connect to your pc. Run the following command to flash twrp.
Fastboot flash recovery openrecovery-twrp-2.8.1.0-m8_wlv.img
After this completes select boot loader on the phone screen. Then select recovery. Choose wipe and select advanced. Only select cache and wipe. When done hit the home button icon at the bottom. Then click install. Scroll down and find your su.zip and flash it. Reboot when done

dottat said:
You have a working fastboot/adbsetup? You only need fastboot for this exercise to work.
Click to expand...
Click to collapse
Not 100% on that one. Are you meaning having adb set up on my computer? If so, no. I tried once before, and couldn't figure out what I was doing. I achieved root by using Sunshine to S-Off, and then Klingo One Click Root Method.

SmoovySmoov said:
Not 100% on that one. Are you meaning having adb set up on my computer? If so, no. I tried once before, and couldn't figure out what I was doing. I achieved root by using Sunshine to S-Off, and then Klingo One Click Root Method.
Click to expand...
Click to collapse
Edited my last post

dottat said:
Edited my last post
Click to expand...
Click to collapse
It keeps saying that the Update Utility cannot see my phone.

SmoovySmoov said:
It keeps saying that the Update Utility cannot see my phone.
Click to expand...
Click to collapse
Can you install team viewer and pm me the details to screen share.

dottat said:
Can you install team viewer and pm me the details to screen share.
Click to expand...
Click to collapse
I wasn't in fastboot. It's updating now.

SmoovySmoov said:
I wasn't in fastboot. It's updating now.
Click to expand...
Click to collapse
? good

dottat said:
You have a working fastboot/adbsetup? You only need fastboot for this exercise to work.
---------- Post added at 03:19 PM ---------- Previous post was at 03:09 PM ----------
Here's a quick how to..for after you run that exe.
Take the su.zip to your internal storage.
Download twrp 2.8.1.0 here
http://techerrata.com/browse/twrp2/m8_wlv
Download fastboot/adb here
https://www.androidfilehost.com/?fid=23501681358559711
Extract the fastboot/adb zip. Copy the new twrp image into this new folder. Open the newly extracted folder and while holding the shift button right click on your mouse. Select open command prompt here.
Put phone in fastboot mode and connect to your pc. Run the following command to flash twrp.
Fastboot flash recovery openrecovery-twrp-2.8.1.0-m8_wlv.img
After this completes select boot loader on the phone screen. Then select recovery. Choose wipe and select advanced. Only select cache and wipe. When done hit the home button icon at the bottom. Then click install. Scroll down and find your su.zip and flash it. Reboot when done
Click to expand...
Click to collapse
Okay, so I completed the first part, and am back to not rooted. Not completely following your instructions above, though. I extracted the fastboot/adb file to my Desktop. It's just those files. There's no folder. Are you saying I just need to create a folder with them in it, and then add the twrp file to it?

SmoovySmoov said:
Okay, so I completed the first part, and am back to not rooted. Not completely following your instructions above, though. I extracted the fastboot/adb file to my Desktop. It's just those files. There's no folder. Are you saying I just need to create a folder with them in it, and then add the twrp file to it?
Click to expand...
Click to collapse
Unzip the rar file and then continue
Edit...You should have extracted to a folder not current directory. You want those files within a folder and then yes place the twrp in there too
Once you run through this all it will make better sense going forward.

dottat said:
Unzip the rar file and then continue
Edit...You should have extracted to a folder not current directory. You want those files within a folder and then yes place the twrp in there too
Once you run through this all it will make better sense going forward.
Click to expand...
Click to collapse
Feel like I'm close, but it's not 100% yet.
Got the phone back to operational. Went looking in apps, and SuperSU was not listed. Everything says that I'm rooted, but it was not there. Googled SuperSU apk, and followed a link to download it via Google Play. Redownloaded it, and when opened, it says "There is no SU binary installed, and SuperSU cannot install it." Also, the damn update that started this whole mess just popped up on the screen again.

SmoovySmoov said:
Feel like I'm close, but it's not 100% yet.
Got the phone back to operational. Went looking in apps, and SuperSU was not listed. Everything says that I'm rooted, but it was not there. Googled SuperSU apk, and followed a link to download it via Google Play. Redownloaded it, and when opened, it says "There is no SU binary installed, and SuperSU cannot install it." Also, the damn update that started this whole mess just popped up on the screen again.
Click to expand...
Click to collapse
Did you flash the su.zip in recovery?
Also, since you wiped cache the ota should be gone. Go to settings and chose app manager. Slide over to the right until you see all at the top. Hit the magnifying glass and search for htcdm. When it finds it click on it. Force stop and clear data for it.
Also, since you are running stock with just a few tweaks of your own, you may want to flash santods ota killer zip. It would prevent what started this off in the first place and remove the leftover prompt in the same shot.
https://www.androidfilehost.com/?fid=23329332407587434

Can someone provide the nde63x boot.img

So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx

mpetruzz said:
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
Click to expand...
Click to collapse
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Or, just flash the whole image with flash-all command. 7.1.1 (NMF26O, Dec 2016) is the one you want and its found here https://developers.google.com/android/images. You can edit the script and remove the -w and it'll keep the user data in tact. For me, it was better to start from scratch.

Droid1019 said:
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Click to expand...
Click to collapse
Ok thanks! I had a few people give me the wrong command line that's prolly why it wasn't working. I'll give this a shot later!!

Droid1019 said:
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Or, just flash the whole image with flash-all command. 7.1.1 (NMF26O, Dec 2016) is the one you want and its found here https://developers.google.com/android/images. You can edit the script and remove the -w and it'll keep the user data in tact. For me, it was better to start from scratch.
Click to expand...
Click to collapse
OK, so now I'm using those commands and still am getting the error message cannot load path/to/boot.img.
I can give the flash all a try, how to I edit the script to remove the -w??

mpetruzz said:
OK, so now I'm using those commands and still am getting the error message cannot load path/to/boot.img.
I can give the flash all a try, how to I edit the script to remove the -w??
Click to expand...
Click to collapse
If you get that error message it sounds like you don't have the right path for it to find that file. With the phone in bootloader mode I type in the command then drag the bit image into the terminal window and execute. I use a Mac so I don't know if you can drag the file in on a Windows machine. You'll have the same issue with the flash all if you don't have the right path.

mpetruzz said:
So I'm on a VP and am BL unlocked, twrp'd and rooted on 7.1 and want to update to 7.1.1. I want to flash the stock boot.img so I can take the OTA and update. Problem is I keep trying to extra the boot.img but can't get it to flash.
Not sure if I'm doing it wrong or have the wrong img but it's driving me nuts.
I've read through the forums and I know I'll get flamed for asking but I just need a bit of help with this.
Thx
Click to expand...
Click to collapse
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.

bobby janow said:
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.[/QUOTE
Yeah that does sound better!!. Honestly I might just leave it on 7.1 til some Roms come out.
Click to expand...
Click to collapse

mpetruzz said:
bobby janow said:
Can't you just flash stock recovery and sideload the OTA? Seems a lot easier and safer.[/QUOTE
Yeah that does sound better!!. Honestly I might just leave it on 7.1 til some Roms come out.
Click to expand...
Click to collapse
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse

bobby janow said:
mpetruzz said:
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
Right now I'm only BL unlocked, twrp'd and rooted. No kernel modifications.
Where do I get the recovery.img from?
I was told by others here I need to flash the stock boot image in order to take the OTA. Jeez I'm getting so confused cause I keep getting different info
Click to expand...
Click to collapse

mpetruzz said:
bobby janow said:
Right now I'm only BL unlocked, twrp'd and rooted. No kernel modifications.
Where do I get the recovery.img from?
I was told by others here I need to flash the stock boot image in order to take the OTA. Jeez I'm getting so confused cause I keep getting different info
Click to expand...
Click to collapse
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse

bobby janow said:
mpetruzz said:
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
OK so i'm in the system image file for 7.1 and am not seeing the recovery.img. Must be doing something wrong, but it's def not there. Anywhere else I can grab it from?
Also once I get it what would the adb command line be to flash it?
Click to expand...
Click to collapse

bobby janow said:
mpetruzz said:
Stock recovery is in the image file from Google. Download it and extract it and flash it in bl. You might need things to "take" the OTA but I don't believe you need anything to flash the OTA (adb sideload) That will overwrite any kernel (boot.img) changes you made. But you said you made no kernel changes so why would you need to flash a boot.img?
Click to expand...
Click to collapse
I got it and am all set!! Used the skipsoft tool to flash the stock recovery, then sideloaded the OTA!!
Thanks brother for all the help!!!!
Click to expand...
Click to collapse

Hey I'm pretty new to this but is there a way I can update without a computer, I dont mind losing root as long as I'm still unlocked... I'm using a Verizon phone on at&t if that matters... If not I can always to it tomorrow when I can get to a computer..

bobby janow said:
mpetruzz said:
7.1.1 is worth it. Not sure when roms are coming out but with the OTA it's about a 10 minute install and reboot. You'll need to just fastboot flash recovery recovery.img for the stock, go directly into recovery with the vol keys / power key and then adb sideload the ota file after entering the recovery menu.
Did you flash another kernel? Is that why you want to replace the boot.img? If so you can probably just flash the OTA without changing anything other than recovery since it will overwrite the boot.img anyway.
Click to expand...
Click to collapse
OK maybe i spoke too soon. I sideloaded the OTA and was able to install TWRP, but now when I flash the su zip I don't have the SuperSu app and can't get root. I've tried it twice and it looks like it's flashed but then when I reboot it's not there.
What am I not doing to get this too work??
Click to expand...
Click to collapse

mpetruzz said:
bobby janow said:
OK maybe i spoke too soon. I sideloaded the OTA and was able to install TWRP, but now when I flash the su zip I don't have the SuperSu app and can't get root. I've tried it twice and it looks like it's flashed but then when I reboot it's not there.
What am I not doing to get this too work??
Click to expand...
Click to collapse
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
This is where you'll need to go at this point. Lots to read but you have to do it in order to get it working correctly. Good luck, you'll get it.
Click to expand...
Click to collapse

bobby janow said:
mpetruzz said:
http://forum.xda-developers.com/pixel-xl/development/root-supersu-t3490156
This is where you'll need to go at this point. Lots to read but you have to do it in order to get it working correctly. Good luck, you'll get it.
Click to expand...
Click to collapse
Got it, man this pixel is crazy different than what I'm used too. Thanks all for the help!
Click to expand...
Click to collapse