[Q] Unable to install software update - One (M7) Q&A, Help & Troubleshooting

I have the HTC One Dev edition and have unrooted the device and installed RUU so I can apply OTA updates. The problem is when I try to apply OTA update to 1.29.1540.17 the phone reboots to Fastboot. Bootloader shows Tampered relocked Hboot is at version 1.44.0000. If I reboot the phone it's not updated and is asking me to install update again. I would like to install this update and stay unrooted so I can receive the update to 4.2.2 which should be coming shortly.
Any help would be greatly appreciated.

You've the stock recovery, right?

As far as I know. I ran the ruu utility from the htc dev site which is supposed to return the phone to stock. If that's not the case then maybe not.

The ruu only restores stock ROM only ,but you have to flash stock kernel and recovery manually

tonztime said:
I have the HTC One Dev edition and have unrooted the device and installed RUU so I can apply OTA updates. The problem is when I try to apply OTA update to 1.29.1540.17 the phone reboots to Fastboot. Bootloader shows Tampered relocked Hboot is at version 1.44.0000. If I reboot the phone it's not updated and is asking me to install update again. I would like to install this update and stay unrooted so I can receive the update to 4.2.2 which should be coming shortly.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Hey, RUUs generally flash stock recovery!!
I got the problem,
You have htcDEV edition
So your bootloader UNLOCKED initially right??
So i think you should keep it unlocked
Try and reply what happens
HIT THANKS IF I HELPED YOU

prunzzz said:
Hey, RUUs generally flash stock recovery!!
I got the problem,
You have htcDEV edition
So your bootloader UNLOCKED initially right??
So i think you should keep it unlocked
Try and reply what happens
HIT THANKS IF I HELPED YOU
Click to expand...
Click to collapse
Yes I have Dev edition and the bootloader was unlocked initially. Are you saying to keep bootloader unlocked and run the RUU?

tonztime said:
Yes I have Dev edition and the bootloader was unlocked initially. Are you saying to keep bootloader unlocked and run the RUU?
Click to expand...
Click to collapse
NO NO NO
after RUU, before OTA try keeping BL unlocked and get OTA
I think mostly it will work
You got my point!!

prunzzz said:
NO NO NO
after RUU, before OTA try keeping BL unlocked and get OTA
I think mostly it will work
You got my point!!
Click to expand...
Click to collapse
Ok. I ran RUU and tried running OTA with BL unlocked and got the same problem of booting to bootloader when trying to install OTA.

Do you have stock recovery ?
Sent from my Nexus 7 using xda app-developers app

tonztime said:
Ok. I ran RUU and tried running OTA with BL unlocked and got the same problem of booting to bootloader when trying to install OTA.
Click to expand...
Click to collapse
The TAMPERED is gone from fastboot, ya??
If not may be stock recovery wasnt flashed correctly
This is it
Thats all i can think
May be reflash stock recovery,
Even then if you cant get OTA its strange

If the TAMPERED is still there, the OTA won't install AFAIK.

Omg fkn hell
First grab the appropriate ruu for your phone,then start it up,but dont put in the phone ,while its still open,go to the windows search bar on the menu and type %temp% you will see a folder,search in the first 2 folders you will find ROM.zip inside that is all the **** you need,so extract from it boot.IMG(kernel) and recovery.IMG(recovery),
Now boot your phone to boot loader flash those 2 files,relock bootloader,(fastboot oem lock ) something like this i forgot,make sure to double check it then boot your phone up,unroot it with supersu app ,reboot then flash the update ....,that's assuming you're on stock rom,if on a custom one, after flashing the img files,run the ruu so it can restore the stock software ..

Sorry to hijack, i bought the one yesterday, immediately rooted. Does this mean I won't get ota updates? It's running 4.1.
Will I have to unroot and install stock recovery to update?
Sent from my HTC One using xda app-developers app

X82X said:
Sorry to hijack, i bought the one yesterday, immediately rooted. Does this mean I won't get ota updates? It's running 4.1.
Will I have to unroot and install stock recovery to update?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Exactly

BigJoey010 said:
Exactly
Click to expand...
Click to collapse
I've seen here that there is a list of RUU's. My phone is the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm not sure which RUU to use. Also, the page gives a list of OTA. Can I just install the correct OTA to upgrade?
I'm just worried I'll screw this phone up, barely had it a day. Again, apologies for hijacking.

BigJoey010 said:
Do you have stock recovery ?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have the RUU straight from htcdev for the HTC One Dev edition of the phone. This should be all I need to get back to stock. Is this not the case?

So I ran RUU utility after relocking phone and superuser apk still shows as installed. I then downloaded ES file explorer and gave it superuser permission, mounted the filesystem as rw and deleted the su file in system/bin and system/xbin and then deleted the superuser.apk file from system/app. After that I tested to make sure I no longer had root access. The test showed I no longer had root access and then I rebooted and all the su and superuser files were back again. Does anyone have an explanation for what I'm doing wrong? I just want to get back to stock so I can install OTA updates from HTC again and get 4.2.2 update.

Bro why are you doing it manually ? You must go into the app and press unroot,that's it
Sent from my Nexus 7 using xda premium

BigJoey010 said:
Bro why are you doing it manually ? You must go into the app and press unroot,that's it
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
I don't see that option in the superuser app. I do see that option on my GN that has su installed but not on my HTC one with superuser installed.

BigJoey010 said:
The ruu only restores stock ROM only ,but you have to flash stock kernel and recovery manually
Click to expand...
Click to collapse
Lie. The RUU flash EVERYTHING back to 100% stock - kernel, recovery, ROM, the lot

Related

help please, i need help

I intent flash ics in my att vivid, but my phone bricked, then i want to back stock, i download ruu cingular, and when run the ruu say error 140 eroor bootloader. i need help please you sorry my english i dont speak and write well... i wait for your help.. tks...
I had the same problem. Error 140 means there's a corruption in the a cards data structure.
Did you unlock your bootloader?
Pm me with what you have done so far. I'll help as much as I can, but be forewarned you may need to replace your device regardless.
Sent from my HTC PH39100 using xda premium
discobritanics said:
I intent flash ics in my att vivid, but my phone bricked, then i want to back stock, i download ruu cingular, and when run the ruu say error 140 eroor bootloader. i need help please you sorry my english i dont speak and write well... i wait for your help.. tks...
Click to expand...
Click to collapse
When you run the ruu, you must re-lock your bootloader. Have you locked your bootloader?
Go to this thread, they have the tool you need to fix your phone:
http://forum.xda-developers.com/showthread.php?t=1498003
Hope it helps! Good Luck
you say it's bricked, but yet it goes into bootloader you can flash ruu?
i think you maybe misspoke, what happened exactly? can you show pictures?
error 140 bootloader version error is simple, it means that the main version is newer than the one you are trying to flash. since you flashed ics ruu, you cannot go back to gb ruu. you have to follow the guide here by thecubed
http://forum.xda-developers.com/showthread.php?t=1529669
if u can take pics first and show me what your phone is doing before you do anything else that will be better
Please don't make two separate threads in two different sections asking for the exact same thing.
Sent from my HTC PH39100 using xda premium
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mod plz move to gen
ebaul said:
When you run the ruu, you must re-lock your bootloader. Have you locked your bootloader?
Go to this thread, they have the tool you need to fix your phone:
http://forum.xda-developers.com/showthread.php?t=1498003
Hope it helps! Good Luck
Click to expand...
Click to collapse
IIRC, you have to be able to boot the phone to get this method to work?
I'm having a similar problem and I tried the file from http://forum.xda-developers.com/showthread.php?t=1529669 to no avail, it doesn't say an error code it just reboots and goes black after HTC boot screen.
I think my problem started when I tried to flash the OTA from androidninjas; he put the ICS hboot on top and I was too excited to read so I d/l and flash the file (was named PH39IMG...) but when I went to boot it turned black. So I d/l and flash the new file, after using HBOOT to clear out the phone etc. Still no luck. And I've tried numerous GB ruu's as well as every ICS one I can find. Brick?
Definitely interested to hear the fix to this.
Before flashing ICS, did you relock your Hboot & were you running GB?
If your screen went dark, but can still get into hboot, you are fine. Just need a recovery. There is an error with the older standard CWM. So you need to install a new version of recovery.
GSLEON3 said:
Before flashing ICS, did you relock your Hboot & were you running GB?
If your screen went dark, but can still get into hboot, you are fine. Just need a recovery. There is an error with the older standard CWM. So you need to install a new version of recovery.
Click to expand...
Click to collapse
Yes to both and I thought relocking got rid of root? So I was afraid I wouldn't be able to flash a custom rom.
Moved to General sub section, please pay attention where you open a thread next time
htc vivid
My phone is similar, I unlocked and all, i got stuck booting...i relocked the phone,i loaded the PH39IMG.zip onto a sd card and booted from it, it says checking the image, next thing it does is update fail main version is older. any help would be appreciated
quepasakimosabe said:
My phone is similar, I unlocked and all, i got stuck booting...i relocked the phone,i loaded the PH39IMG.zip onto a sd card and booted from it, it says checking the image, next thing it does is update fail main version is older. any help would be appreciated
Click to expand...
Click to collapse
if it's locked..just boot to fastboot, plug the phone into your computer, and run the latest ruu. Then unlock

Stock ROM Reset | 1.31.651.2 + 1.29.651.10 | Stock Recovery Included

If you are still S-On (or S-off but lazy or tentative) and want a simple way to return to the stock ROM and also be able flash back the stock radio and recovery then this may be for you.
XDA member migascalp gave me the idea of packaging stock ROM's with the aroma installer and include the ability to flash the stock recovery also as sort of a poor mans RUU since so many still are S-on and cannot properly run a RUU.
I have been making these for a few different versions for the GSM model M7 UL:
See here: http://www.htc1guru.com/downloads/stock-rom-downloads/
I got a request to do one for the Sprint Variant, so here it is. To be clear, I personally do not own the Sprint version, so I couldn't test this, however it is a fairly basic script and I only changed the partition info for formatting and copying the data. Thanks to XDA member @(^_^)@ for the partition layout.
If you are looking to run the stock ROM but rooted (You can add root during my installer) or modded then you will probably want one of these:
http://forum.xda-developers.com/showthread.php?t=2368907
Thanks to Indirect for the firmware and stock rom dumps.
Thanks to the.emilio for Radio information.
You simply flash in recovery like installing any other rom.
Here are the screen shots of the Aroma Installer. Sorry for some the bad edits, its really hard to get a good pic taken manually at bootloader or recovery:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
It seems like the Radio flashing was a problem, so I have removed it from the package. It will not show up as an option during the installer.
ROM and Recovery flash fine.
I have updated the download link and md5
Thanks
Here is the download link:
Guru Reset M7 Sprint 1.31.651.2
md5: f3d055dea52b60674833c2cbb87893fb
Guru Reset M7 Sprint 1.29.651.10
md5: 29a4b3cd30a848a8e6c9e1e7bd079740
Guru Reset M7 Sprint 3.04.651.2
md5: 0cc1048c835512e1d988525ea8aa2815
........Credits........​Thanks to Indirect for the 1.31.651.2 Stock ROM
Thanks to O.M.J. for the 3.04.651.2 Stock ROM​
Enjoy!
Stuck on the "Installing Stock Rom" screen. Won't flash anything, just stays at 0.00%. Just stuck on that screen... I'm HTC Dev-unlocked only, on stock 1.31
Edit: Tried it again, this time with just the recovery, no radio, and it worked fine :good: Still waiting for it to reboot but it looks good.
rubyknight said:
Stuck on the "Installing Stock Rom" screen. Won't flash anything, just stays at 0.00%. Just stuck on that screen... I'm HTC Dev-unlocked only, on stock 1.31
Edit: Tried it again, this time with just the recovery, no radio, and it worked fine :good: Still waiting for it to reboot but it looks good.
Click to expand...
Click to collapse
OK, I know in TWRP when finished you have select to reboot, I didn't insert that into the script.
Odd that it is the Radio that has the issue. I will pull the package for now and update it so there is no choice for Radio install only recovery.
Thanks
Uploading new version without the option to flash the radio.
I think most are just concerned with ROM and Recovery anyway.
I will update OP when new link is live.
New version with no option to flash radio is now live.
OP Updated.
Thanks
crushalot said:
New version with no option to flash radio is now live.
OP Updated.
Thanks
Click to expand...
Click to collapse
And as the post says, it will return me to 100% OEM Stock ROM and recovery without needing S-OFF first?
GeekasaurusWrex said:
And as the post says, it will return me to 100% OEM Stock ROM and recovery without needing S-OFF first?
Click to expand...
Click to collapse
That is correct.
Well technically 99% as the stock radio was pulled from the package and can't be installed with the rom and recovery. The radio version shouldn't matter but you can always manually flash the correct radio before running this installer.
This demo is of AT&T Stock ROM and then OTA but the install and procedure is the same. I can't update this video for the roms in the this thread because I don't have a Sprint phone.
crushalot said:
That is correct.
Well technically 99% as the stock radio was pulled from the package and can't be installed with the rom and recovery. The radio version shouldn't matter but you can always manually flash the correct radio before running this installer.
Click to expand...
Click to collapse
Well, I can say that this has worked for me. I flashed the radios, did the reset and back on all stock everything. The only issues are that Qualcomm's Enhanced Location stops working, and my phone randomly rebooted once but that may have been coincidental. I just v wished I had saved the firmware update to dropbox so I wouldn't have to download it again.
My issue was I am s-on and running a 4.3 Rom. There was no way to get the entire firmware package (PRI, firmware, radio's, etc) without being s-off. I noticed revone AND moonshine wouldn't work on the new 1.55hboot so I used this download and flashed it then manually did the OTA update to 4.3. Yes I lost root, yes my Qualcomm would not work, however, I got the FULL firmware update. I then just re-rooted and flashed OMJs deodexed and life is all good. Thank you for making this, it helped me a ton. Now I just gotta wait for an s-off method on hboot 1.55.
Sent from my HTCONE using xda app-developers app
if you have at any point upgrade to 4.3 from 4.1 using a rooted rom, back up your 0 folder or this process will wipe it out completely.
GeekasaurusWrex said:
Well, I can say that this has worked for me. I flashed the radios, did the reset and back on all stock everything. The only issues are that Qualcomm's Enhanced Location stops working, and my phone randomly rebooted once but that may have been coincidental. I just v wished I had saved the firmware update to dropbox so I wouldn't have to download it again.
Click to expand...
Click to collapse
Looks like that is known issue on stock roms:
http://forum.xda-developers.com/showthread.php?t=2467607
I2izzo said:
My issue was I am s-on and running a 4.3 Rom. There was no way to get the entire firmware package (PRI, firmware, radio's, etc) without being s-off. I noticed revone AND moonshine wouldn't work on the new 1.55hboot so I used this download and flashed it then manually did the OTA update to 4.3. Yes I lost root, yes my Qualcomm would not work, however, I got the FULL firmware update. I then just re-rooted and flashed OMJs deodexed and life is all good. Thank you for making this, it helped me a ton. Now I just gotta wait for an s-off method on hboot 1.55.
Sent from my HTCONE using xda app-developers app
Click to expand...
Click to collapse
Nice. That is good to know.
Thanks
itster2 said:
if you have at any point upgrade to 4.3 from 4.1 using a rooted rom, back up your 0 folder or this process will wipe it out completely.
Click to expand...
Click to collapse
Thanks. Good thing to know. I will update the OP.
itster2 said:
if you have at any point upgrade to 4.3 from 4.1 using a rooted rom, back up your 0 folder or this process will wipe it out completely.
Click to expand...
Click to collapse
Doesn't 0 live in the media folder? I checked the wipe script and it should leave everything in /data/media alone and I thought that would include the 0 folder.
New Version Posted
I created a package with the slightly older version. May be useful for those that have older firmware and no touchscreen on 1.31.651.2.
OP has been updated.
Guru Reset M7 Sprint 1.29.651.10
md5: 29a4b3cd30a848a8e6c9e1e7bd079740
Just to be clear, I can flash this to get back to bone-stock. Then I can do the OTA to get the new 4.3 firmware?
I am currently running Team Nocturnal's GPE(4.2.2) and S-On with ClockworkMod Recovery. Thanks guys.
jharre08 said:
Just to be clear, I can flash this to get back to bone-stock. Then I can do the OTA to get the new 4.3 firmware?
I am currently running Team Nocturnal's GPE(4.2.2) and S-On with ClockworkMod Recovery. Thanks guys.
Click to expand...
Click to collapse
Yes, As long as your current firmware version matches the version of the stock rom reset.
Ok great! Forgive my ignorance on this, but how do I confirm this? I see I have a Baseband of 1.00.20.0626...
jharre08 said:
Ok great! Forgive my ignorance on this, but how do I confirm this? I see I have a Baseband of 1.00.20.0626...
Click to expand...
Click to collapse
That is the radio version. To check your firmware, boot to your bootloader screen (Hold power and Vol Down) and the firmware version should show for the line OS.

Can't find my RUU

I have been looking around but i can't find my RUU.
I want to return my phone back to stock, since i can't update my phone while rooted.
Also my experience with this is seriously 0 (buddy of mine rooted this), so i'm sorry if i might sound stupid.
I have downloaded all the Ruu files from the return back to stock forum here and non of them worked.
My software number is: 1.29.111.11
Thanks in advance
Whose the carrier?
caster62003 said:
Whose the carrier?
Click to expand...
Click to collapse
T-mobile
Alright, now that I have a clear mind and actually read your question completely...
When you tried the previous RUUs before, did they fail during flash or did Android not function correctly when you got in?
If the RUU flash failed, you more than likely still have an unlocked bootloader, which was required during the root process and the RUU does not like, so it fails.
Considering your knowledge on Android/HTC One, I'm going to point you here, download the Toolkit, extract it to somewhere... Note: I am not affiliated with the development of the Toolkit, I have used it before and IMO it is a great program, very HTC One noob friendly.
On your phone make sure USB Debugging is enabled, then, launch the Toolkit -> On the left hand side, under Basic ADB, click Bootloader. Your phone will turn off, then get into the Bootloader.
At the top, it should say Unlocked, if it does, you need to relock the bootloader, now on the right hand side of the Toolkit, check the checkbox under Agreement which will then enable the Re-lock button, click that (DO NOT CLICK S-On), Your phone will reboot to Android, Once back, click the Bootloader button again Under Basic ADB. This time instead of Unlocked, it will say Relocked. Now try running the RUU again, this time it should work.
Once the RUU flash is done, you should be all set to get going again.
caster62003 said:
Alright, now that I have a clear mind and actually read your question completely...
When you tried the previous RUUs before, did they fail during flash or did Android not function correctly when you got in?
If the RUU flash failed, you more than likely still have an unlocked bootloader, which was required during the root process and the RUU does not like, so it fails.
Considering your knowledge on Android/HTC One, I'm going to point you here, download the Toolkit, extract it to somewhere... Note: I am not affiliated with the development of the Toolkit, I have used it before and IMO it is a great program, very HTC One noob friendly.
On your phone make sure USB Debugging is enabled, then, launch the Toolkit -> On the left hand side, under Basic ADB, click Bootloader. Your phone will turn off, then get into the Bootloader.
At the top, it should say Unlocked, if it does, you need to relock the bootloader, now on the right hand side of the Toolkit, check the checkbox under Agreement which will then enable the Re-lock button, click that (DO NOT CLICK S-On), Your phone will reboot to Android, Once back, click the Bootloader button again Under Basic ADB. This time instead of Unlocked, it will say Relocked. Now try running the RUU again, this time it should work.
Once the RUU flash is done, you should be all set to get going again.
Click to expand...
Click to collapse
Sorry for answering a bit late, but i had exams. Anyway i found some instructions here and i've followed the instructions but i've been stuck at step 10
for the last hour it's been looking like this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what is it that i'm doing wrong here?
Edit: i kept retrying the steps and i got a bit further, but now after i type fastboot flash zip firmware.zip i get this fail
TM-87 said:
Sorry for answering a bit late, but i had exams. Anyway i found some instructions here and i've followed the instructions but i've been stuck at step 10
for the last hour it's been looking like this...
what is it that i'm doing wrong here?
Edit: i kept retrying the steps and i got a bit further, but now after i type fastboot flash zip firmware.zip i get this fail
Click to expand...
Click to collapse
that's normal you have to issue "fastboot flash zip firmware.zip" twice!
so now IMMEDIATELY do it again, DO NOT REBOOT
the second flash should come back with success
nkk71 said:
that's normal you have to issue "fastboot flash zip firmware.zip" twice!
so now IMMEDIATELY do it again, DO NOT REBOOT
the second flash should come back with success
Click to expand...
Click to collapse
Ok i've tried doing fastboot flash zip firmware.zip again, but now i get this message
I have retried making this file again by redownloading everything, but i keep getting this unkown error...
TM-87 said:
Ok i've tried doing fastboot flash zip firmware.zip again, but now i get this message
I have retried making this file again by redownloading everything, but i keep getting this unkown error...
Click to expand...
Click to collapse
"cannot load" just means the filename (ie "firmware.zip") is wrong. check your folder for the correct name.
nkk71 said:
"cannot load" just means the filename (ie "firmware.zip") is wrong. check your folder for the correct name.
Click to expand...
Click to collapse
Thanks that worked, i've run the fastboot flash zip firmware.zip twice now and it worked both times. atleast that's what it said, when i rebooted the phone i still had superSU isn't that stuff supposed to be gone?
TM-87 said:
Thanks that worked, i've run the fastboot flash zip firmware.zip twice now and it worked both times. atleast that's what it said, when i rebooted the phone i still had superSU isn't that stuff supposed to be gone?
Click to expand...
Click to collapse
Nope, superSU should still be there. You only upgraded firmware, nothing to do with ROM or SU.
Sent from my HTC One using Tapatalk
nkk71 said:
Nope, superSU should still be there. You only upgraded firmware, nothing to do with ROM or SU.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
.... So then ... how do i unroot / return to stock i followed instructions on youtube and they said i needed the RUU file so that's when i stumbled onto this problem and now that i've found the solution ... i still have no idea how to get rid of the twrp and superSU off my phone ....
I just want to return the phone back to how i bought it, since after the rooting thing i couldn't update since it would just return to twrp when trying to instal the update....
TM-87 said:
.... So then ... how do i unroot / return to stock i followed instructions on youtube and they said i needed the RUU file so that's when i stumbled onto this problem and now that i've found the solution ... i still have no idea how to get rid of the twrp and superSU off my phone ....
I just want to return the phone back to how i bought it, since after the rooting thing i couldn't update since it would just return to twrp when trying to instal the update....
Click to expand...
Click to collapse
It's not the root preventing the update from what I can tell. What you need is to flash stock recovery over twrp
Sent from my HTC One
gusto5 said:
It's not the root preventing the update from what I can tell. What you need is to flash stock recovery over twrp
Sent from my HTC One
Click to expand...
Click to collapse
So i need to put this RUU.zip onto my phone and flash it via twrp?
TM-87 said:
So i need to put this RUU.zip onto my phone and flash it via twrp?
Click to expand...
Click to collapse
Sorry mate, kind a lost track of what you want to achieve. Can you please explain.
Also post a "fastboot getvar all" (remove IMEI and s/n before posting)
nkk71 said:
Sorry mate, kind a lost track of what you want to achieve. Can you please explain.
Also post a "fastboot getvar all" (remove IMEI and s/n before posting)
Click to expand...
Click to collapse
Again sorry for the late reply, still busy with my exams. Anyway, what i want to do is return the phone back like before i rooted the phone/ remove twrp, superSu and all that. Right now i can't update my phone and i'm still on JB 4.1. Each time i try to download and instal the update it keeps going to twrp.
Here's my "fastboot getvar all"
Bump
no one knows a solution?
TM-87 said:
no one knows a solution?
Click to expand...
Click to collapse
You probably need to get S-Off, if you want to go back to 100% stock. whats the date of your bootloader?
nkk71 said:
You probably need to get S-Off, if you want to go back to 100% stock. whats the date of your bootloader?
Click to expand...
Click to collapse
Where does it show the date of the bootloader?
TM-87 said:
Where does it show the date of the bootloader?
Click to expand...
Click to collapse
in bootloader , the attached screen, we need to see if you are patched 1.44 hboot or unpatched; unpatched will be dated before June 2013

[Guide] How to Downgrade from KK to JB S-OFF Required

Okay Guys. here is a guide how to downgrade back to JB from using KK. You will need to be S-OFF and also will to have a locked or relocked bootloader. and just follow my steps. You will need adb and fastboot and you will need the 3.05.651.6 decrypted you will find the file here http://forum.xda-developers.com/showthread.php?t=2576995
(1) From fastboot you need to first re-lock your bootloader. using this command
fastboot oem lock
then you reboot your device into bootloader. make sure your device shows relocked or locked on top of the screen. once you see that then go to step #2
(2) now type this command fastboot oem rebootRUU after that you should see black screen with green HTC logo.
if you got this far go to step #3
(3) now the file you downloaded please rename it too rom.zip (make sure you have it named correctly) my advice i would just found the file you downloaded and right click it and look for rename and i would just type the word rom and hit enter to ensure it is correct. If you did that go to step #4
(4) Now, type this command fastboot flash zip rom.zip , let it run it course during the process you will see this message . " pre hboot 90 " if you see that then just press the up arrow on the keyboard and press enter and let the process run again and then let it run it will flush your device at this point and will lose everything on your storage. once you have done that sit back 10-20 mins. and wait for the process to finish. after that go to Step #5
(5) type this command in command prompt fastboot reboot-bootloader and press enter . Once your at bootloader menu select factory reset and press power button and let it do reset and when it done. your device will reboot and your done.
Credits - Go to O.M.J for the files
P.S. Hopefully this will help you for anyone that needs this.
Pretty sure it's just a matter of running the RUU you want if you're s-off...
Indirect said:
Pretty sure it's just a matter of running the RUU you want if you're s-off...
Click to expand...
Click to collapse
According to recent reports, no it is not that simple
It does work been working with O.M.J and I did this with two devices already.
Indirect said:
Pretty sure it's just a matter of running the RUU you want if you're s-off...
Click to expand...
Click to collapse
Yeah I just ran a jb RUU without relocking boot loader and s-off without any issues.
I'm trying this now. I'll report back soon!
---------- Post added at 08:42 PM ---------- Previous post was at 08:41 PM ----------
Kraizk said:
According to recent reports, no it is not that simple
Click to expand...
Click to collapse
I'm here to agree! I can't get an older RUU to flash and I'm S-OFF. I've tried on multiple computers and done everything I can think of... With no luck. I've tried the whole "tricking" the bootloader to thinking you're using an older base and everything.
wwjoshdew said:
I'm trying this now. I'll report back soon!
---------- Post added at 08:42 PM ---------- Previous post was at 08:41 PM ----------
I'm here to agree! I can't get an older RUU to flash and I'm S-OFF. I've tried on multiple computers and done everything I can think of... With no luck. I've tried the whole "tricking" the bootloader to thinking you're using an older base and everything.
Click to expand...
Click to collapse
It works .
DUDE, you are FREAKING AWESOME! After trying and failing so many times by using different RUU's, zip's, and etc...
You're guide got my HTC One back to 4.3!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
wwjoshdew said:
DUDE, you are FREAKING AWESOME! After trying and failing so many times by using different RUU's, zip's, and etc...
You're guide got my HTC One back to 4.3!
Click to expand...
Click to collapse
Your Welcome ! I didn't have time too make the rom.zip , thanks O.M.J . He help me with that file.
wwjoshdew said:
DUDE, you are FREAKING AWESOME! After trying and failing so many times by using different RUU's, zip's, and etc...
You're guide got my HTC One back to 4.3!
Click to expand...
Click to collapse
Where's the video of this process Josh?
BD619 said:
Where's the video of this process Josh?
Click to expand...
Click to collapse
Whats going on boss?
tommyjoesanders said:
Whats going on boss?
Click to expand...
Click to collapse
Just giving Josh a hard time
BD619 said:
Just giving Josh a hard time
Click to expand...
Click to collapse
He good guy. Just been trying to help out on the forum with some people having issues with KK Update. and needing to downgrade. I am just glad O.M.J file was here.
milesb3 said:
Yeah I just ran a jb RUU without relocking boot loader and s-off without any issues.
Click to expand...
Click to collapse
I haven't had such luck running the JB RUU. Currently I have an HTC One brick and back on the HTC EVO LTE until I can get it figured out.
weidnerj said:
I haven't had such luck running the JB RUU. Currently I have an HTC One brick and back on the HTC EVO LTE until I can get it figured out.
Click to expand...
Click to collapse
If you can get into bootloader just try this method I think it will work for you
weidnerj said:
I haven't had such luck running the JB RUU. Currently I have an HTC One brick and back on the HTC EVO LTE until I can get it figured out.
Click to expand...
Click to collapse
It's odd that some are having issues while others are not. I just ruu'd again from stock kk to make sure I wasn't going crazy with a 3.04 encrypted zip I extracted from the official ruu. Did it in mac os x and went off without a hitch.
Does 4.4.2 perform worse?
milesb3 said:
It's odd that some are having issues while others are not. I just ruu'd again from stock kk to make sure I wasn't going crazy with a 3.04 encrypted zip I extracted from the official ruu. Did it in mac os x and went off without a hitch.
Click to expand...
Click to collapse
i thought that was teh whole point of s-off.
tommyjoesanders said:
If you can get into bootloader just try this method I think it will work for you
Click to expand...
Click to collapse
I am willing to try anything about now... But going to take a few hours to download the file so won't be able to try until tomorrow after work.
Thanks for the suggestion!!!
weidnerj said:
I am willing to try anything about now... But going to take a few hours to download the file so won't be able to try until tomorrow after work.
Thanks for the suggestion!!!
Click to expand...
Click to collapse
Keep me posted. I will do what I can to help anyone

Moto x At&t rooted and I Can't update to 4.4.4

Hello xda community I have problem I have At&t unlocked boot loader 4.4.2 rooted and I receive the ota I Can't update to 4.4.4 when press install it reboot to recovery and show message in red color "security failed recovery downgraded"
Pls help me
MoMoGAX said:
Hello xda community I have problem I have At&t unlocked boot loader 4.4.2 rooted and I receive the ota I Can't update to 4.4.4 when press install it reboot to recovery and show message in red color "security failed recovery downgraded"
Pls help me
Click to expand...
Click to collapse
You will not be able to take an ota with a rooted rom. The rom must be unmodified in any way for the ota to succeed in the upgrade. So your only chance is to either unroot the rom or factory restore the rom. If you factory restore, remember to backup your data.
iam on stock rom and I can't factory reset it show me the same message
MoMoGAX said:
iam on stock rom and I can't factory reset it show me the same message
Click to expand...
Click to collapse
You just said you were rooted, and you can not be rooted to take an ota. I am pretty sure of it.
Thanks for replay but Iam rooted
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Root=no upgrade. FleetPhone is saying because you are rooted your phone will not update. You can't have root.
Guys....it's not about being rooted. It's about NOT having STOCK RECOVERY, *or* about changes that were made to /system.
Usually just being rooted won't stop you from taking updates. But you can NOT take an update without Stock Recovery. You probably have TWRP recovery still installed - this will prevent the OTA from installing.
Aside from that, any significant modifications to /system, for example Xposed will need to be uninstalled first.
If you can't figure out the problem, use RSD Lite to flash the entire 4.4.2 ROM, then you can take the OTA.
NEVER DOWNGRADE. You can only do this because you are still on 4.4.2 and haven't updated to 4.4.4. Once on 4.4.4, any attempt to downgrade will likely result in a brick.
Good Luck :good:
You must hide root with SuperSU & use STK recovery
I just got ota last night for att. Is there any root method?
cell2011 said:
I just got ota last night for att. Is there any root method?
Click to expand...
Click to collapse
Nope, not unless you unlock through the China middleman. Just search 'China middleman' and you will find the thread.
Good luck
MoMoGAX said:
Hello xda community I have problem I have At&t unlocked boot loader 4.4.2 rooted and I receive the ota I Can't update to 4.4.4 when press install it reboot to recovery and show message in red color "security failed recovery downgraded"
Pls help me
Click to expand...
Click to collapse
Hey I have the same att moto x. Could you please tell me how you unlocked your bootloader? And rooted? Thanks a lot man.
alimzia said:
Hey I have the same att moto x. Could you please tell me how you unlocked your bootloader? And rooted? Thanks a lot man.
Click to expand...
Click to collapse
I didn't unlocked the boot loader I used jcase root method slap my moto from 4.2.2
I have the OTA 4.4.4 and cant root any suggestions?
MoMoGAX said:
Hello xda community I have problem I have At&t unlocked boot loader 4.4.2 rooted
Click to expand...
Click to collapse
MoMoGAX said:
I didn't unlocked the boot loader I used jcase root method slap my moto from 4.2.2
Click to expand...
Click to collapse
?
Sent from my XT1060
rocketsaucev2 said:
?
Sent from my XT1060
Click to expand...
Click to collapse
Sorry it's locked boot loader I root on 4.2.2 then I enable survival mode in super su then take ota to 4.4.2 but I don't l don't know if I install the stock firmware using rsd I will lose the root I will give it try
MoMoGAX said:
Sorry it's locked boot loader I root on 4.2.2 then I enable survival mode in super su then take ota to 4.4.2 but I don't l don't know if I install the stock firmware using rsd I will lose the root I will give it try
Click to expand...
Click to collapse
Yes, you'll lose root by using rsd
Sent from my XT1060
I have AT&T Moto X with unlocked bootloader and root. All I did to take update was restore stock recovery and apply 4.4.2 system.img to ensure there were not system changes and my phone accepted update fine (didn't lose anything either). Then I got root back I installed TWRP and SuperSU again. Done.
You can do all of this with the MotoX tookit. http://forum.xda-developers.com/moto-x/development/tool-moto-x-toolkit-v1-4-0-t2477132
Lots of great info and walkthroughs http://mark.cdmaforums.com/MotoX.htm
MoMoGAX said:
I didn't unlocked the boot loader I used jcase root method slap my moto from 4.2.2
Click to expand...
Click to collapse
MoMoGAX said:
Sorry it's locked boot loader I root on 4.2.2 then I enable survival mode in super su then take ota to 4.4.2 but I don't l don't know if I install the stock firmware using rsd I will lose the root I will give it try
Click to expand...
Click to collapse
Ok, your problem of not being able to take the OTA... that is because of how SlapMyMoto works, and tricks it plays to give you root and write protection disabled.
If you want to take the OTA, you will have no choice but to flash completely back to stock (using RSDLite) and WILL lose root. For how, see -> http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Keep in mind that with a LOCKED bootloader, you will NOT be able to DISABLE Write Protection when on 4.4.2 and above. If on 4.4.2, PIE or TOWELPIEROOT can be used to root, but write protection will still be enabled, so root and changes made by root apps would be lost at power off/on or "hard boot" and root apps done have the ability to create files in /system and such. There is no root for 4.4.4 with locked bootloader. For more see -> http://forum.xda-developers.com/moto-x/general/one-stop-shop-how-root-moto-x-confusion-t2826159 its not a very long thread, so please read ALL of it... including Post #70 of that thread
And before you ask... No, if you are on 4.4.4 you can NOT fully downgrade to 4.4.2 or lower. If you are on 4.4.2 you can NOT fully downgrade to 4.4 (aka 4.4.0) or lower! If you try, you will likely brick your phone or set it up to brick with future OTA's. (this is true for locked and Unlocked bootloaders)
IF you have an ATT, Verizon or Republic wireless, you can try the China Middleman thread in the general section to see if you can get a bootloader unlock code if you want to root and disable write protection no matter what ROM is on your phone.
KidJoe said:
Ok, your problem of not being able to take the OTA... that is because of how SlapMyMoto works, and tricks it plays to give you root and write protection disabled.
If you want to take the OTA, you will have no choice but to flash completely back to stock (using RSDLite) and WILL lose root. For how, see -> http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Keep in mind that with a LOCKED bootloader, you will NOT be able to DISABLE Write Protection when on 4.4.2 and above. If on 4.4.2, PIE or TOWELPIEROOT can be used to root, but write protection will still be enabled, so root and changes made by root apps would be lost at power off/on or "hard boot" and root apps done have the ability to create files in /system and such. There is no root for 4.4.4 with locked bootloader. For more see -> http://forum.xda-developers.com/moto-x/general/one-stop-shop-how-root-moto-x-confusion-t2826159 its not a very long thread, so please read ALL of it... including Post #70 of that thread
And before you ask... No, if you are on 4.4.4 you can NOT fully downgrade to 4.4.2 or lower. If you are on 4.4.2 you can NOT fully downgrade to 4.4 (aka 4.4.0) or lower! If you try, you will likely brick your phone or set it up to brick with future OTA's. (this is true for locked and Unlocked bootloaders)
IF you have an ATT, Verizon or Republic wireless, you can try the China Middleman thread in the general section to see if you can get a bootloader unlock code if you want to root and disable write protection no matter what ROM is on your phone.
Click to expand...
Click to collapse
Thank you for help and quick reply you made my day
At&t rom is fkn awesome in batery life

Categories

Resources