Database Info

Somewhat worried...

Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?

redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
go to the root of your external sd card and delete all the zip file(s), you probably left it there when you downgrade. Also delete file from internal sdcard in /cache/recover if any. Once you unlocked you shouldn't receive anymore OTA.

redheadplantguy said:
I finally got the nerve to unlock. I had to downgrade doing it.
Click to expand...
Click to collapse
Strange, many people said the unlock tool works fine on JB.
redheadplantguy said:
Now, I heard after unlocking, an ota will brick tablet.
Click to expand...
Click to collapse
Where?
I don't say it cannot brick your tablet, but I am not aware of any reports that it does.

redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!

MartyHulskemper said:
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!
Click to expand...
Click to collapse
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.

redheadplantguy said:
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.
Click to expand...
Click to collapse
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.

buhohitr said:
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.
Click to expand...
Click to collapse
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.

redheadplantguy said:
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.
Click to expand...
Click to collapse
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.

buhohitr said:
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.
Click to expand...
Click to collapse
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.

redheadplantguy said:
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.
Click to expand...
Click to collapse
That does sound like it actually flashed something (at least partly). I would run that unlock tool another time just to be sure I wouldn't get into trouble down the road (Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on. Flashing over stock, well... minor nuisance, but it would be majorly inconvenient to have to flash root and stuff all the time.)

MartyHulskemper said:
Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on.
Click to expand...
Click to collapse
No, it just doesn't work. The updater-script inside the OTA package compares the checksums of the system apps to be patched, and aborts as soon as one doesn't match the previous stock ROM.
The only potential danger I see is the communication with the bootloader which kernel to boot - the OTA downloader (DMClient) somehow has to instruct the bootloader to load the recovery kernel to install the dlpkgfile from /cache, and if that process is still not understood by custom recovery creators (there were some problems apparently, I don't know if they are solved), you might end up with a device that only boots into the recovery and not into Android.

Thanks. I will.
Sent from my SGH-T679 using Xparent ICS Blue Tapatalk 2

F2 to HE update?

I bought my S3 used and it was already unlocked but from what I can tell still had the stock ROM (base version says it is I535VRLF2 but DEVICE STATUS says it is modified). When it powers up, I do not get a CWM or TWMP screen -- it goes directly to the normal startup so I am not sure what the previous owner loaded/did. I do not see any folders in the root folder (using ES FIle Explorer) for CWM and nothing in DATA/BACKUP (EDIT: just saw build number is VRALG7)...
Today I got a notice about an OTA upgrade (to HE) and got help on how to freeze it (as I did not want to lose root and all the customization I did to some files) but now I am wondering what changes were made from F2 to HE. I did find a post that talks about the HE upgrade.
Was F2 the previous OTA for the S3, or did my phone miss other OTAs? And if so, I am missing out on some important changes where I should let the OTA happen and then go and unlock the phone again? I read a number of threads about 'the new radio' which I assume is software to improve the phone or WIFI. Am I missing out?
Thanks
Frank
Michigan

I don't think you are missing out on anything to be honest. I did update mine and reroot without any issues, but can't really tell a difference. I would still do it so I can have the latest update on my phone since this one doesn't lock anything that we can't get back into.
Sent from my SCH-I535 using xda premium

There has been only three official releases, F2,G7,and HE. Since you are at G7 I would go ahead and OTA HE. Latest ROMS are based off of it plus you will have all the latest firmware and modem.

sfobrien said:
There has been only three official releases, F2,G7,and HE. Since you are at G7 I would go ahead and OTA HE. Latest ROMS are based off of it plus you will have all the latest firmware and modem.
Click to expand...
Click to collapse
Thanks for the reply. Will that break either my root or unlock (actually, I am not sure what state this phone is at since I did not do it -- I do find SuperSU in APPS, and have granted SuperUser to programs like Titanium Pro but there is nothing for CWM or other ROM managers...)?
Frank

If you did an OTA to get to G7 your root is probably gone. You said you have Titanium installed, try to use it. If not rooted it won't work and will advise you so. If this is the case do the OTA to HE and then you will be up to date stock ROM wise.

sfobrien said:
If you did an OTA to get to G7 your root is probably gone. You said you have Titanium installed, try to use it. If not rooted it won't work and will advise you so. If this is the case do the OTA to HE and then you will be up to date stock ROM wise.
Click to expand...
Click to collapse
No, sorry, I must not have explained it correctly. Titanium Pro, ES File Explorer, etc works fine, and I can edit/delete/freeze, etc no problem. So it is still rooted (or unlocked, I can figure out which is which). I would update to HE but only if it did not mess up what I have....
Thanks
Frank

FMinMI said:
No, sorry, I must not have explained it correctly. Titanium Pro, ES File Explorer, etc works fine, and I can edit/delete/freeze, etc no problem. So it is still rooted (or unlocked, I can figure out which is which). I would update to HE but only if it did not mess up what I have....
Thanks
Frank
Click to expand...
Click to collapse
Ok I understand now. Root and unlocked are two different things. You can flash an HE ROM and not lose your root. Unlock in your case I think you are referring to the bootloader. It will have to be unlocked prior to flashing custom ROMS. Get an app called EZ Unlock from the Playstore and it will unlock bootloader for you if it's not unlocked already.
I recommend CleanROM 3.1 if you decide to flash. Hope this has helped you some.

I'm trying to revert back to custom because i lost my IMEI but the process I was following required me to flash "VRALF bootchain" 2x and then flash "HE package" but i dont know where to get the HE package and i tried flashing root66 and VRALHD but they both failed can someone help me?

andimanium said:
I'm trying to revert back to custom because i lost my IMEI but the process I was following required me to flash "VRALF bootchain" 2x and then flash "HE package" but i dont know where to get the HE package and i tried flashing root66 and VRALHD but they both failed can someone help me?
Click to expand...
Click to collapse
The only way to get stock HE currently is OTA.

sfobrien said:
Ok I understand now. Root and unlocked are two different things. You can flash an HE ROM and not lose your root. Unlock in your case I think you are referring to the bootloader. It will have to be unlocked prior to flashing custom ROMS. Get an app called EZ Unlock from the Playstore and it will unlock bootloader for you if it's not unlocked already.
I recommend CleanROM 3.1 if you decide to flash. Hope this has helped you some.
Click to expand...
Click to collapse
I am not interested in loading any custom ROMs (although I am hoping we get the official JB soon). The only thing that is of interest to me is to be able to run certain programs that require superuser access (e.g. Titanium Pro) and to be able to edit and delete files in the root directory. So I assume all I need is root, and I don't want any OTA updates to take that away (or overwrite files that I have modified or edited that deal with the OS). Maybe that is why I cannot find any reference to CWM -- the previous owner only rooted it but did not unlock it....
Frank

FMinMI said:
I am not interested in loading any custom ROMs (although I am hoping we get the official JB soon). The only thing that is of interest to me is to be able to run certain programs that require superuser access (e.g. Titanium Pro) and to be able to edit and delete files in the root directory. So I assume all I need is root, and I don't want any OTA updates to take that away (or overwrite files that I have modified or edited that deal with the OS). Maybe that is why I cannot find any reference to CWM -- the previous owner only rooted it but did not unlock it....
Frank
Click to expand...
Click to collapse
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
http://www.scottsroms.com/downloads.php?do=file&id=247

Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.

prdog1 said:
Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.
Click to expand...
Click to collapse
Thanks forgot about GooManager.

sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
http://www.scottsroms.com/downloads.php?do=file&id=247
Click to expand...
Click to collapse
OK. I have 6.0.0.8 right now. I am surprised it was there, as with my Nexus and my TP on a cold boot it would show CWM at startup. And there would be folders in the root directory (/CWM). But yes, I have CMW.
And OK on now being able to download and install a rooted HE. But most are saying it either does nothing or makes the phone run a little hotter, so unless I see a pressing need, I will just stay with what I have.
Thanks again.
Frank

prdog1 said:
Or you can download GooManager and flash TWRP for a more user friendly touch recovery. :laugh:
And flash the same rom from Scott.
Click to expand...
Click to collapse
I had tried TWRP with my HP TP and although it has a nice interface, one time, on loading a new nightly, it TOTALLY messed up my TP. I thought it was bricked. I ended up having to do a complete restore back to WebOS using WebDoctor and a lot of what I thought was code-level input via the PC trying to bring it back to life. Since then, I have only used CWM.
Thanks for the input though!
Frank

FMinMI said:
I had tried TWRP with my HP TP and although it has a nice interface, one time, on loading a new nightly, it TOTALLY messed up my TP. I thought it was bricked. I ended up having to do a complete restore back to WebOS using WebDoctor and a lot of what I thought was code-level input via the PC trying to bring it back to life. Since then, I have only used CWM.
Thanks for the input though!
Frank
Click to expand...
Click to collapse
It is personal choice. I have not had any problems with it and have been running since device was released for pre-order. I run whatever recovery seems to be most stable for the device. CWM for Tbolt. Amon Ra for Rezound. And now TWRP for S3. Have seen more bricks and failed flashes contributed to CWM so I stick with TWRP.

help
sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
Can anyone tell me why every time I try to flash a ROM after I have taken all the OTA updates I am on VRLGHE; when my phone re-boots I get the verizon screen saying I have unapproved software and take to a verizon store.
Click to expand...
Click to collapse

FMinMI said:
OK. I have 6.0.0.8 right now. I am surprised it was there, as with my Nexus and my TP on a cold boot it would show CWM at startup. And there would be folders in the root directory (/CWM). But yes, I have CMW.
And OK on now being able to download and install a rooted HE. But most are saying it either does nothing or makes the phone run a little hotter, so unless I see a pressing need, I will just stay with what I have.
Thanks again.
Frank
Click to expand...
Click to collapse
The OTA installed with a custom recovery installed? Interesting. Usually OTA's fail if anything but stock recovery is installed. I only lost root but restored root with OTA Rootkeeper with stock recovery. Good to know that custom recovery can be installed and still get OTAs!

masonjb said:
sfobrien said:
Got just the thing for you. First test to make sure you have newest CWM. Power down, Hold volume up,home button,and lock button at same time until phone flashes twice then release. This will put you in recovery and you can see what version you have. The latest is 6.0.1.2. If not you can find newest version or a touch version right here at XDA. Then if you want just a rooted HE version here you go.
Can anyone tell me why every time I try to flash a ROM after I have taken all the OTA updates I am on VRLGHE; when my phone re-boots I get the verizon screen saying I have unapproved software and take to a verizon store.
Click to expand...
Click to collapse
Boot loader is locked.
Click to expand...
Click to collapse

prdog1 said:
masonjb said:
Boot loader is locked.
Click to expand...
Click to collapse
OK, I used EZ Unlock 1.2 and it said "unlocked" is there a way to know for sure before flashing if it is unlocked?
Thanks!
Click to expand...
Click to collapse

Bricked MAXX, Need Help

Hello,
I have been crack flashing for a long time, but when I got the Droid Maxx from verizon I was disappointed at the lack of an unlocked bootloader. I had been running safestrap and was getting the phone ready to return for a refund so I can get the developer edition.
So, it looks like using safestrap I completely wiped the system partition. I can get the phone to boot to flashboot mode or to the safestrap flash screen but that is all.
Using RSDlite I attempted to flash 12.9.0, but get the return message "Failed flashing process. 2/17 flash partition "gpt.bin" -> Phone returned FAIL. On the phone it said:
"downgraded security version
update gpt_main version failed
preflash validation failed for GPT."
So it looks like the issue might be because I am flashing the FXZ file for 12.15.15, but I cannot find the FXZ file for it.
I also tried using House of Moto. Attached is a screen shot of what I get.
So basically it looks like I have no ROM whatsoever. Is there a way out of this so I can return the phone for a refund?
Thanks in advance!

I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?

kclantz said:
I realized that I had not set things up correctly for House of Moto, I ran it, and boot.img, system.img, and motoboot.img are not loading because they are from the previous image and it will not allow a downgrade.
So, I guess I need to get the factory image of the latest update, or perhaps get those *.img files from someone with a working phone and drop them in to folder before flashing.
Anyone have the factory image after the OTA? Or perhaps the missing files I need (if dropping them will actually work, of course)?
Click to expand...
Click to collapse
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.

ahjee said:
,
I am having the same problem only I am on the Droid Ultra and not the Maxx, I too need the files for the latest OTA because the two older files are supposedly out dated for me, i get a bunch of failures. What sucks is some files were clearly restored because it erased Safestrap and now i have stock recovery but it didn't restore the OS or anything so i cannot boot up into anything but fastboot....hopefully someone uploads the latest ota to the site or even the forums....good luck to you. i need it as well.
Click to expand...
Click to collapse
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.

rds217 said:
I'm in the same boat, but not quite as bad. I've got the mini, and it boots into the normal mode, but not all things work - touchless controls crash every time I try to open it, and my calendars won't sync. My recovery is gone, when I try to boot into it, I get an android logo with it's chest open with a red triangle.
I tried using RSD Lite and fastboot with the original stock image files, but the result are the same. I'm going to hold out for someone to post an image with the OTA included or another workaround. Amazing how we got the same problems at roughly the same time after the OTA.
Click to expand...
Click to collapse
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing

So I just got back from the Verizon store, I went in to see if they could flash the files I need. They told me they couldn't but gave me a number at motorola to see if they would e-mail the files to me.
Unfortunately that didn't work. Motorola said I could send the phone in for a repair, and that was my only option.
I think I'll take the second option and wait until someone posts the files and flash them with RSD Lite.
I just hope that happens soon, as I am wanting to return the phone and get the developer edition. I have until Saturday to return it and I doubt they will give me a refund with it in this state.

ahjee said:
if yours boots into the OS maybe you can still root it, after you root it you can then modify system apps, getting rid of touchless control and then reinstall it, may fix the force close. also if you manage to gain root you could install safestrap. the android with the triangle is the stock recovery, i forget what buttons or button combination you have to hit to make the menu appear but that is the stock recovery by what you're describing
Click to expand...
Click to collapse
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
jcase said:
If you used 1.1 and have a problem with recovery coming back, run the following command:
adb shell su -c "dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/dev/block/platform/msm_sdcc.1/by-name/recovery"
Click to expand...
Click to collapse

rds217 said:
Here's the issue, I can't boot into write-protected off mode. When I tried running HouseOfMoto, I flashed stock recovery for pre-OTA; since I received the OTA, I can't install PwnMyMoto, which is what gave me the write-protection off mode in the first place. Now when I go from the bootloader into recovery, I get the dead android + red triangle, what you call stock recovery.
I have root level access, but it's all but useless since the system is write protected. In other words, no Safestrap. I'll have to live with what I've got until someone finds time and reason to upload the post-OTA image or something newer.
Edit: Fixed it, maybe it will work for you guys. Check the PwnMyMoto thread for the source, I can't post it due to being new.
Click to expand...
Click to collapse
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.

kclantz said:
With my issue I cannot even get to the point where I can use ADB. I am pretty much stuck with fastboot commands. I can get the bootloader and stock recovery, but nothing more.
Is there something that I can edit in the update file that would allow the version downgrade test to pass? I've played around with the XML file, but I am not having much luck.
Click to expand...
Click to collapse
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk

erishasnobattery said:
Your only current options are to wait for a newer FXZ or have Motorola perform a repair on it.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Thanks, that was what I was afraid of. I guess now I will check obsessively for the new FXZ files. Got have some way to spend my day (you know, as opposed to doing my job ).

[Q] Unable to get back to stock

I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.

Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.

Mcsecne said:
I am using ViperOneM8 1.7.0. I am trying to get back to stock so that I can get the 4.4.3 OTA.
I seem to be stuck. I am back to locked, but still s-off. I have tried flash 0P6BIMG.zip in RUU mode but unable. I have tried to unlock with firewater s-off but it does run. Please help.
Click to expand...
Click to collapse
If s off you can use the newest one. You don't need to the one below. Use the newest ruu and use the SD card method/option.
jsaxon2 said:
Use this: http://forum.xda-developers.com/verizon-htc-one-m8/help/official-ruu1-55-605-2-t2883845
It will take you back to stock. You will still be s-off.
Click to expand...
Click to collapse

TWRP & Flashify work with this?
Sorry for my noobie question, but I rooted back in April with WeakSauce & TWRP and also installed Flashify. I am fuzzy on what I did and now, I am afraid of bricking my phone through ignorance.
Can I use these files to upgrade to 4.4.3 on my Verizon HTC One M8? If so, what is the most straightforward way to do this? Can I use Flashify or TWRP to load the OP6ZBIMG.ZIP file?
Thanks

I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-return-htc-one-m8-verizon-to-stock-s-on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.

nraines said:
I was able to get back to stock by following this guide I found here: http://www.bane-tech.com/how-to-ret...on-relock-bootloader-unrootuninstall-supersu/
Everything worked great until the final step of removing SuperSU. I was unable to remove SuperSU using all methods I could find. It remains as a system app, but I am no longer rooted.
My intentions were to return it to stock for the warranty screen replacement by HTC, so I took the risk and hid SuperSU in the app drawer and sent it in for the warranty work. It came back fixed and factory reset, but SuperSU was still there. I still wanted to return my phone to a complete stock experience in case I need to return it to Verizon, so I took a risk of taking the OTA released in September, thinking it would wipe SuperSU out of the system apps. Somehow, the OTA left SuperSU in tact. I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.

dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.

nraines said:
Any advice regarding taking the next OTA? I tried using Sunshine to unlock and root again, but had no luck. I know if I take the OTA, I definitely won't be able to use Sunshine as it currently stands, but I'm just looking to get back to stock right now.
Click to expand...
Click to collapse
Do not take ota. What was the sunshine prob?

dottat said:
Do not take ota. What was the sunshine prob?
Click to expand...
Click to collapse
It force closes during the initial check.

nraines said:
It force closes during the initial check.
Click to expand...
Click to collapse
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?

dottat said:
had you previously temp rooted? I have something we can try if your internal SD is backed up....
edit... yes i can fix yours. Do you have google hangouts?
Click to expand...
Click to collapse
Incoming PM

back to stock
dottat said:
That's because that is a crap guide. You turned s on before removing su which turned on /system write protection and basically write protected your su app.
You must remove su after locking bootloader and making sure all is well with lock and tamper status. You should only turn s on AFTER this is all verified.
Click to expand...
Click to collapse
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks

empty_cups said:
dotdat,
Is there a non-crap guide to un-rooting?
I want to get my HTC One M8 which is rooted and on 4.4.2 updated to 4.4.3. I don't really care if I loose root.
Thanks
Click to expand...
Click to collapse
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.

unroot
dottat said:
You don't need to unroot. If you have not modified system apps and you have stock recovery the ota will flash.
Click to expand...
Click to collapse
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?

empty_cups said:
I have uninstalled TWRP, Busy Box & SU. When I run the Check Root program it says I have ROOT.
I have twice accepted to OTA, it reboots, goes about 1/3rd through and goes to the red triangle thing which I then go into the recovery console.
On the bottom it says:
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Verifying current system...
"/system/customize/ACC/default.xml" has unexpected contents.
Write host_mode:0 done
At this point I reboot and I am back to where I was. Any pointers?
Click to expand...
Click to collapse
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845

not working
dottat said:
Su doesn't matter. You are going to need it to fix your problem. Did you make changes (like hotspot hack) to the default.xml file?
Actually. An easy way to fix it is to either flash a totally stock Rom or flash the official ruu i I have posted in the non dev section. It doesn't wipe and would put you back to 100% stock and let you take the ota
http://forum.xda-developers.com/showthread.php?t=2883845
Click to expand...
Click to collapse
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?

Done
empty_cups said:
I tried and it failed. I did do the "hotspot" hack, is there an easy way to unhack it?
Click to expand...
Click to collapse
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.

empty_cups said:
Just wanted to thank you. I ended up doing the hboot image, then the other one took just fine. I am now on 4.4.3 without root which is fine by me as the only reason I wanted root was for Wi-Fi which now works with foxfi.
Click to expand...
Click to collapse
Since you are s off you can take the ota and then flash twrp and flash su. Easiest way...

nraines said:
I also noticed that the stock camera app was limited to only camera or selfie mode. Video, Zoe and the others weren't able to be accessed. Has anyone else experienced these issues, or have any recommendations for fixing them? I am considering taking the HTC Eye OTA due soon from Verizon, hoping that will fix my problems, but I'm not too confident since the last OTA didn't work as expected.
Click to expand...
Click to collapse
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.

jkeirnan87 said:
I'm on complete stock (not even rooted) and I've been having this problem for a while. I found out that sometimes when it happens, I can fix it by restarting my phone, but it goes back to being broken soon after. I noticed that it started to happen after I installed the Google now launcher, leading me to believe that it's a ram problem (and hence restarting will help) so I uninstalled a bunch of useless apps and now I use about 1g ram at idle, and the problem still persists.
This morning, I updated with the new OTA (4.4.4 and HTC Eye) and the problem is still here. If anyone could help, it would be greatly appreciated.
Click to expand...
Click to collapse
You are s on too right? If so I don't have an option for you yet. Your system files are write protected which means the most you can do is clear data for the app or factory reset. Are you using an SD card and if so does it make a difference which storage location you use?

How to upgrade to LP 5.01 (Stage Fright Patch) w/o wiping data or reflashing recovery

This is an upgrade pathway that worked well for me in upgrading to 5.0.1 originally from KK as I described in THIS post. All the same thanks go out for the original ideas and guidance to: dottat, Dees Troy, and Darth.
The same method works. Even if you're S-OFF, the trick is following the S-ON instructions...that's it.
Find the latest S-ON RUU and instructions HERE.
The latest TWRP (for the HTC One M8) HERE.
The latest SuperSU per the instructions HERE.
Install the S-on 5.0.1 RUU by whatever method you chose from the link above. I used the fastboot method and it did a great job upgrading the stystem. Most importantly, it did NOT wipe my data. You can also use the htc_fastboot.exe in it's extraction directory for all subsequent fastboot operations [highly recommended]. It will reboot and take at least 5 minutes to update all of your applications. At first, it looks like it hangs on the Verizon splash for a minute or three, then it shows you the upgrade of your applications with a count up. How long it takes depends on how many applications you have and how large they are.
Follow the guides to install TWRP and reinstall SuperSU for root. (step 5) I went to the new TWRP page (step 2) and loaded mine by fastboot, then used the new TWRP to flash SuperSU as described.
If you haven't taken the OTA, that should take care of the upgrade nag screens and keep your data intact. If you have, keep reading.
REMINDER: to reflash any tweaks. My favorite package is HERE at the bottom of the links list. It has just about everything I like.
ADDITIONAL INFO FROM dotatt
You also would be wise to note if the user was already getting nagged for the ota they will still be nagged about it even after upgrading this way. Couple more steps needed
Click to expand...
Click to collapse
AND HIS DESCRIPTION VIA PM
If the user doesn't download the OTA and defer it they might be able to get away with it. Once the file is downloaded (and it goes in /cache) the user will need to wipe cache to delete the actual file as well as go into app manager and clear data on the htcdm app. When they enter the software update screen again it should check and show no updates available instead of asking when to install the deferred update.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
If you need to get rid of the nag screen, the update files, and clear htcdm data, you may be able to use THIS (M8vzw OTA Killer updated for Lollipop) tool.

I have a problem and need help, maybe you can help. I was stock but was s-off and took the stage fright update and phone did all the update and when the phone booted it did not go past the Verizon bootup screen, can anybody help me with this? Thanks you.
Sent from my Nexus 6 using Tapatalk

luvtorev01 said:
I have a problem and need help, maybe you can help. I was stock but was s-off and took the stage fright update and phone did all the update and when the phone booted it did not go past the Verizon bootup screen, can anybody help me with this? Thanks you.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I answered your other post. Please only post for help in one thread. Thanks.
Sent from my Nexus 6 using Tapatalk

Thanks for keeping your eyes open, dottat. Good reminder that he'll have to reflash TWRP and SuperSU though. And, he'll have to reflash any tweaks.

homers1 said:
Thanks for keeping your eyes open, dottat. Good reminder that he'll have to reflash TWRP and SuperSU though. And, he'll have to reflash any tweaks.
Click to expand...
Click to collapse
You also would be wise to note if the user was already getting nagged for the ota they will still be nagged about it even after upgrading this way. Couple more steps needed ?
Sent from my Nexus 6 using Tapatalk