Related
Hey guys,
I seriously need some help, reverting my international HOX+ back to stock, as I am going to sell it.
My main problem is, that i have an o2 germany one, for that it seems to be impossible to get any suitable RUU
I am able to unlock / relock the bootloader, flash custom or stock recovery, flash any custom rom... not a problem.
But I'm stuck with the order of the steps! When I flash a stock rom (1.17.401.xx), my next step should be flashing stock recovery and then relock bootloader, right? I did so and got a security warning at bootloader and it seems, that there is no rom left on the phone.
How do I trick this, to relock, use stock rec. and stock rom?
Thanks for any help!!!
AW: Need help, going back to stock
you need the correct RUU for O2 brandings
yep. any news, where to get it?
thought, there might be a workaround...
I think there is no ruu atm.
I'll have a look for it.
AW: Need help, going back to stock
That would be very nice!
Sent via Xperia Z
The only o2 ruu is this one:
http://www.androidfiles.org/ruu/sec...Radio_3.1204.167.31_release_289474_signed.exe
Based on your informations, you need a ruu for a german phone.
It doesn't matter that there is "UK" in the name.
The United Kingdoms are in europe, like germany.
Give it a try and tell me if it has worked or not.
If it doesn't work, open your Bootloader and flash an custom recovery/kernel/rom and wait until there's a dumped o2 ruu.
the_brad said:
But I'm stuck with the order of the steps!
Click to expand...
Click to collapse
1.Go into the bootloader and make sure your phone is connected to your computer.
2.Relock your bootloader, using the cmd (Windows) or the terminal (Linux).
3.You make it with "fastboot oem lock".
4.Run the "ruu.exe" as administrator and let it work.
5.Drink a coffee and wait until it's done.
AW: Need help, going back to stock
Ok, many thanks for that!
I already tried that ruu, but maybe my fault was, I did not lock the bootloader, before.
Will try that, later this evening and give feedback
Sent via Xperia Z
You're welcome!
If you got any problems, send me a private message and we try to solve the problem.
AW: Need help, going back to stock
Doesn't work gives me bootloader error. Stops after updating signature...
Sent via Xperia Z
what about running ruu, extracting rom.zip and flashing this one? ruu could be 1.17.401 for example!?
will this work or result in a brick? is this method still possible on one x series? my evo 3d provided this while using a zip named to pc86img.zip (or very similar :cyclops
edit: if possible, will the phone check cid in the zip?
pretty much same here, except I am on O2 UK, and a higher version than the RUU available so it doesn't work, so frustrating, just want to go back to stock
alternate method would be: flashing a nandroid backup of a stock rom.
problem: don't own one
Is anybody out there, who can provide me a full backup of rom 1.17.207.xx with cid 02___102 o2 germany?
that would save my weekend, guys!
Hi.
I have the same problem but am on o2_UK i cant get back to stock.Doesn't mater whatever RUU i try is the same.
I have 1.17.401.1 cid02__001 and really badly need to go on stock ROM
Any help would be great.
Thanks a lot in advance.
So here's a little bit of context first:
1-This is a friend's phone
2-The data partion corrupted on its own
3-I unlocked the bootloader
4-Flashed twrp
5-Formatted data partition through adb
6-Flashed cm11 normally
Now the phone network doesnt want to work and both the imei and baseband show up as unknown even though they show up normally with the command "fastboot getvar all" .
I've tried restoring to this backup http://forum.xda-developers.com/showthread.php?t=2775650 but it kept crashing and rebooting and it had the same imei and baseband problem so i went back to cm11.
Any ideas?
tinclan said:
So here's a little bit of context first:
1-This is a friend's phone
2-The data partion corrupted on its own
3-I unlocked the bootloader
4-Flashed twrp
5-Formatted data partition through adb
6-Flashed cm11 normally
Now the phone network doesnt want to work and both the imei and baseband show up as unknown even though they show up normally with the command "fastboot getvar all" .
I've tried restoring to this backup http://forum.xda-developers.com/showthread.php?t=2775650 but it kept crashing and rebooting and it had the same imei and baseband problem so i went back to cm11.
Any ideas?
Click to expand...
Click to collapse
If imei and baseband are missing in Settings it is a sign that it is a hardware issue and will cause a host of problems. If under warranty you can return to carrier or HTC for repair. However, since you unlocked the bootloader and I would guess it is S-ON you will not be able to return it to 100% stock for a warranty repair. You can still return it but will have to pay for the repair.
majmoz said:
If imei and baseband are missing in Settings it is a sign that it is a hardware issue and will cause a host of problems. If under warranty you can return to carrier or HTC for repair. However, since you unlocked the bootloader and I would guess it is S-ON you will not be able to return it to 100% stock for a warranty repair. You can still return it but will have to pay for the repair.
Click to expand...
Click to collapse
Omg man that's totally not the response I wanted to hear. What about the fact that the iemi and baseband show up fine using the "fastboot getvar all" command? And BTW I only unlocked the bootloader when the data partition corrupted, before I tried to unlock the bootloader HTC had already told my friend that they're gonna charge him $200 bucks to fix that issue and that wasn't really an option for him. Also, do you think the issue maybe because of corrupted firmware. I though that maybe if we werent able to fix the issue then I works just get s-off and run an ruu then try to remove the tampered banner and get back the bootloader states to "locked", what do you think?
tinclan said:
Omg man that's totally not the response I wanted to hear. What about the fact that the iemi and baseband show up fine using the "fastboot getvar all" command? And BTW I only unlocked the bootloader when the data partition corrupted, before I tried to unlock the bootloader HTC had already told my friend that they're gonna charge him $200 bucks to fix that issue and that wasn't really an option for him. Also, do you think the issue maybe because of corrupted firmware. I though that maybe if we werent able to fix the issue then I works just get s-off and run an ruu then try to remove the tampered banner and get back the bootloader states to "locked", what do you think?
Click to expand...
Click to collapse
It is worth a try to see if the firmware or RUU will fix the issue, however, if it is hardware then it will not.
majmoz said:
It is worth a try to see if the firmware or RUU will fix the issue, however, if it is hardware then it will not.
Click to expand...
Click to collapse
Thanks for replying! I will definitely try flashing the firmware and RUU before concluding that it's a hardware problem, but btw do you know if i need s-off to flash firmware for the same os version and same cid/mid or will it just check that it's compatible and overwrite the one already there?
tinclan said:
Thanks for replying! I will definitely try flashing the firmware and RUU before concluding that it's a hardware problem, but btw do you know if i need s-off to flash firmware for the same os version and same cid/mid or will it just check that it's compatible and overwrite the one already there?
Click to expand...
Click to collapse
If you are S-ON then RUU & firmware must be the same version or higher and signed. When you flash the firmware or RUU it will overwrite the partitions and it may wipe all of your data as well. So, if you can you will want to copy all of your data/files off of the phone prior to flashing the firmware or RUU.
majmoz said:
If you are S-ON then RUU & firmware must be the same version or higher and signed. When you flash the firmware or RUU it will overwrite the partitions and it may wipe all of your data as well. So, if you can you will want to copy all of your data/files off of the phone prior to flashing the firmware or RUU.
Click to expand...
Click to collapse
I really appreciate your help, I have one final question. If i extract the firmware from the official ota update then it's signed, right? Also, do i have to lock the bootloader, flash the stock recovery and have the stock sense ROM or if having the relocked bootloader and/or stock recovery enough?
tinclan said:
I really appreciate your help, I have one final question. If i extract the firmware from the official ota update then it's signed, right? Also, do i have to lock the bootloader, flash the stock recovery and have the stock sense ROM or if having the relocked bootloader and/or stock recovery enough?
Click to expand...
Click to collapse
Yes, the firmware in the OTA is signed.
Yes, you must lock your bootloader prior to flashing firmware or RUU if S-ON
If you flash the stock firmware it will include the stock recovery
majmoz said:
Yes, the firmware in the OTA is signed.
Yes, you must lock your bootloader prior to flashing firmware or RUU if S-ON
If you flash the stock firmware it will include the stock recovery
Click to expand...
Click to collapse
Thanks a lot for your help
Hi im Nissanka from srilankan
my phone is HTC One m7
my problem is IME Unknown
this problem is solution tell me please
Phone name
HTC One
IMEI
Unknown
IMEI SV
Unknown
Device serial number
FA42KWM01166
Phone number
Unknown
IMSI
Unavailable
IP address
Unavailable
Wi-Fi MAC address
e8.99.c4.86.72.45
My AT&T HTC One ( M8 ) is rooted, has S-off, and has the Google Play Edition Android Lollipop ROM ported over the top of Sense. This would be all fine and dandy, but my charging port is loose, causing me to lose connection to the charger at random times, as well as almost never being able to hold a consistent data connection to any PC. I want to return this to AT&T under my warranty, but I'm not a big fan of the idea of returning a device that has been tampered with. How could I revert to my unrooted, s-on, stock Sense device without using a data connection to my PC?
You can try the "bootable" RUU here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
Step-by-step instruction under the link "Old guide" on the thread above.
Only bootable RUUs were made for 1.58, and 2.23 updates, AFAIK.
Also, based on reports on XDA, if you are returning to AT&T, they apparently don't care if the phone is modded. And even reports of successful warranty service with phones with custom ROMs installed. But I agree, its probably best to return the phone to as close to stock as possible before sending in for warranty service.
redpoint73 said:
You can try the "bootable" RUU here: http://forum.xda-developers.com/att...-2-23-502-3-bootable-ruu-pc-required-t2860486
Step-by-step instruction under the link "Old guide" on the thread above.
Only bootable RUUs were made for 1.58, and 2.23 updates, AFAIK.
Also, based on reports on XDA, if you are returning to AT&T, they apparently don't care if the phone is modded. And even reports of successful warranty service with phones with custom ROMs installed. But I agree, its probably best to return the phone to as close to stock as possible before sending in for warranty service.
Click to expand...
Click to collapse
Thank you! I just need to know how I'd change my CID to the appropriate value without connecting via adb. I'm currently using the GOOGL001 CID for OTA Lollipop GPE updates.
nerdyotter said:
Thank you! I just need to know how I'd change my CID to the appropriate value without connecting via adb. I'm currently using the GOOGL001 CID for OTA Lollipop GPE updates.
Click to expand...
Click to collapse
I don't personally know such a method. I'd think it would be "possible" via terminal emulator or some other means. How "easy" or "feasible" it is (and whether there is such an existing method) is another question.
redpoint73 said:
I don't personally know such a method. I'd think it would be "possible" via terminal emulator or some other means. How "easy" or "feasible" it is (and whether there is such an existing method) is another question.
Click to expand...
Click to collapse
Thank you. I'll continue to look. Appreciate the help!
Please bear with me since I'm not too experienced on this and did research on XDA to the best I could before asking. I'm planning on returning my device to stock, but I'm worried I might brick it. I'm currently running the Skydragon 9.0 rom (http://forum.xda-developers.com/att-htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062367) and toggled on quite a lot of things. Mainly, I remember allowing it to overwrite my current kernel.
My device has S-ON from what I saw on HBOOT, is using the Skydragon custom kernel, and I'm using TWRP custom recovery. I still have the RUU I downloaded from AT&T to return my device to stock 5.0.2 firmware. My question is, shall I just run the RUU and it will all be back to stock? Should I flash the stock recovery first? Should I relock the bootloader first? and if any of those are true, in what order?
The guide which seemed the most similar to me was this one http://forum.xda-developers.com/showthread.php?t=2751011 but that required S-OFF which I don't have and don't think it's a good thing to have. Could anyone point me in the right direciton? thanks!
First of all, what is your intent in returning to stock: to sell or give away the phone? Or return for warranty service?
sarxion said:
Please bear with me since I'm not too experienced on this and did research on XDA to the best I could before asking. I'm planning on returning my device to stock, but I'm worried I might brick it.
Click to expand...
Click to collapse
You won't brick the phone with s-on. You just won't.
You might screw something up, and temporarily render the phone unable to boot. But that can easily be fixed with the right knowledge; and that is not a brick.
sarxion said:
I'm currently running the Skydragon 9.0 rom (http://forum.xda-developers.com/att-htc-one-m8/development/rom-sd-4-0-sense7-port-sdkernel-t3062367) and toggled on quite a lot of things. Mainly, I remember allowing it to overwrite my current kernel.
Click to expand...
Click to collapse
On this device, flashing a custom ROM always overwrites the kernel. What you selected when you flashed the ROM, is to flash the custom SD kernel instead of flashing the "stock" HTC kernel that came with the ROM base (that Skydragon 9 is based on).
None of that matters, once you return to stock, the custom ROM (including kernel) and any other settings, tweaks, etc. will be returned to their "stock" condition.
sarxion said:
My question is, shall I just run the RUU and it will all be back to stock?
Click to expand...
Click to collapse
Will "all" be back to stock? No. The bootloader will still say RELOCKED instead of the original LOCKED condition. You need s-off to make it say LOCKED.
Also bear in mind that HTC has a record of you unlocking the bootloader, if you did it via HTCDev.com (which is most likely the case). Nothing will change that fact, and it should be disclosed to potential buyers if selling/trading the phone (that it was bootloader unlocked and modded, then returned to near-stock condition).
But everything else will be back to stock after RUU: Stock ROM, stock kernel, stock recovery, and the user data will be wiped.
sarxion said:
Should I flash the stock recovery first? Should I relock the bootloader first? and if any of those are true, in what order?
Click to expand...
Click to collapse
No need to flash stock recovery.
You will need to relock the bootloader to RUU.
Backup (move) anything you want to keep (personal photos, etc.) to your computer, etc. before RUU, as RUU will wipe the phone.
sarxion said:
The guide which seemed the most similar to me was this one http://forum.xda-developers.com/showthread.php?t=2751011 but that required S-OFF which I don't have and don't think it's a good thing to have.
Click to expand...
Click to collapse
As I've mentioned, s-off is only needed if you want to return the phone to LOCKED (instead of RELOCKED). I will agree its probably not necessary to spend $25 for s-off just to do that.
Further, the guide is very old (May 2014 - right after the phone was released) and probably before any RUU was available. It follows a much more complicated path to "return to stock" and needlessly so.
Just relock the bootloader and run the RUU, is my recommendation.
redpoint73 said:
First of all, what is your intent in returning to stock: to sell or give away the phone? Or return for warranty service?
You won't brick the phone with s-on. You just won't.
You might screw something up, and temporarily render the phone unable to boot. But that can easily be fixed with the right knowledge; and that is not a brick.
On this device, flashing a custom ROM always overwrites the kernel. What you selected when you flashed the ROM, is to flash the custom SD kernel instead of flashing the "stock" HTC kernel that came with the ROM base (that Skydragon 9 is based on).
None of that matters, once you return to stock, the custom ROM (including kernel) and any other settings, tweaks, etc. will be returned to their "stock" condition.
Will "all" be back to stock? No. The bootloader will still say RELOCKED instead of the original LOCKED condition. You need s-off to make it say LOCKED.
Also bear in mind that HTC has a record of you unlocking the bootloader, if you did it via HTCDev.com (which is most likely the case). Nothing will change that fact, and it should be disclosed to potential buyers if selling/trading the phone (that it was bootloader unlocked and modded, then returned to near-stock condition).
But everything else will be back to stock after RUU: Stock ROM, stock kernel, stock recovery, and the user data will be wiped.
No need to flash stock recovery.
You will need to relock the bootloader to RUU.
Backup (move) anything you want to keep (personal photos, etc.) to your computer, etc. before RUU, as RUU will wipe the phone.
As I've mentioned, s-off is only needed if you want to return the phone to LOCKED (instead of RELOCKED). I will agree its probably not necessary to spend $25 for s-off just to do that.
Further, the guide is very old (May 2014 - right after the phone was released) and probably before any RUU was available. It follows a much more complicated path to "return to stock" and needlessly so.
Just relock the bootloader and run the RUU, is my recommendation.
Click to expand...
Click to collapse
Thank you very much for your quick answer. I'm returning it to stock firmware to sell the device. Is it safe to lock the bootloader while Skydragon is on my device? and after that, just run the AT&T RUU and I'm done, right?
Also, do you by any chance have any resource on how to relock the bootloader? I've searched for guides on this but I the guides I find don't look very trustworthy, or don't apply, such as this one that requires S-OFF http://forum.xda-developers.com/showthread.php?t=2708571
sarxion said:
Thank you very much for your quick answer. I'm returning it to stock firmware to sell the device. Is it safe to lock the bootloader while Skydragon is on my device? and after that, just run the AT&T RUU and I'm done, right?
Click to expand...
Click to collapse
Correct. It doesn't matter what ROM is on the device when you relock the bootloader. The phone will be rendered unable to boot (may even wipe OS) when you relock.
sarxion said:
Also, do you by any chance have any resource on how to relock the bootloader? I've searched for guides on this but I the guides I find don't look very trustworthy
Click to expand...
Click to collapse
I don't know what you mean by "trustworthy". But you won't fine a "guide" because its a single fastboot command: fastboot oem lock
redpoint73 said:
Correct. It doesn't matter what ROM is on the device when you relock the bootloader. The phone will be rendered unable to boot (may even wipe OS) when you relock.
I don't know what you mean by "trustworthy". But you won't fine a "guide" because its a single fastboot command: fastboot oem lock
Click to expand...
Click to collapse
Thank you very much. So I can run the RUU with my M8 on bootloader mode? Because after relocking the bootloader, I'm asuming it probably won't even boot since it's running a custom ROM and kernel. (I'll be running the exact same RUU version I ran before installing the custom rom)
sarxion said:
So I can run the RUU with my M8 on bootloader mode?
Click to expand...
Click to collapse
The RUU will run with the phone in bootloader-fastboot mode, yes.
sarxion said:
Because after relocking the bootloader, I'm asuming it probably won't even boot since it's running a custom ROM and kernel.
Click to expand...
Click to collapse
That is correct. And in fact, as far as I know, the phone is rendered unable to boot into OS after relocking the bootloader, even if you were on the stock ROM.
OP,
Were you able to go back to stock?
"Unfortunately, AT&T Ready2Go has stopped." Is stuck looping on my phone.
About a year ago I rooted my phone, following these directions. (I can't yet post a link, but the first option on google when searching "how to root m8" is the site, htconeroot.com, that I used.)
This morning I noticed that my phone was not vibrating anymore no matter if I restarted the phone or what settings were applied. So I checked online to see if there was a fix, and a factory reset was recommended.
So when I got back from work today, I thought I had successfully uninstalled the root using SuperSU. Then I performed a factory reset. My phone then went into TWRP recovery which was alarming. So I rebooted the system from TWRP , then the message in the title kept popping up over and over again, so I am in a bit of a pickle. I can message and call at the moment but that is about it.
I'm thinking the problem is similar to this one someone had on a note 3, except I was trying to factory reset rather than update. http://forum.xda-developers.com/showthread.php?t=2663120
Has this happened to anyone else, and do you have any suggested fixes for resetting this phone???
Thanks in advance.
I've seen a number of cases on the M8 forums of various processes stopping with message "XXX has stopped" after a factory reset. Not sure what is causing this. But there are a variety of ways to recover.
Since you have TWRP, you can try to restore a TWRP backup of your own (if you made one) or install a stockish ROM. Those methods may be helpful if you want to retain or retrieve any personal data.
Otherwise, relock the bootloader and RUU back to full stock (RUU will wipe the phone).
redpoint73 said:
Otherwise, relock the bootloader and RUU back to full stock (RUU will wipe the phone).
Click to expand...
Click to collapse
Honestly I'd be fine returning to full stock, at least for the time being, to see if the vibration problem would fix itself. But do I need to be S-OFF for RUU?
eaflook said:
But do I need to be S-OFF for RUU?
Click to expand...
Click to collapse
No, and I wish folks would stop saying you need s-off to RUU (not you, but I assume you got this notion from another post/thread).
You can run the an RUU made for the AT&T M8, as long as you aren't "downgrading" to a previous version (such as Lollipop to Kitkat). For that, you need s-off; or to change the CID and run another carrier version RUU.
You do need to relock the bootloader to run RUU while s-on, with command: fastboot oem lock
Are you currently on LP or MM (what does it say for OS number on the bootloader screen)?
redpoint73 said:
No, and I wish folks would stop saying you need s-off to RUU (not you, but I assume you got this notion from another post/thread).
You can run the an RUU made for the AT&T M8, as long as you aren't "downgrading" to a previous version (such as Lollipop to Kitkat). For that, you need s-off; or to change the CID and run another carrier version RUU.
You do need to relock the bootloader to run RUU while s-on, with command: fastboot oem lock
Are you currently on LP or MM (what does it say for OS number on the bootloader screen)?
Click to expand...
Click to collapse
Um... the OS line on the bootloader screen looks blank, unless I'm looking in the wrong place.
Should I do this? http://forum.xda-developers.com/htc-one-m8/help/guide-how-to-solve-soft-brick-phone-t2824193
eaflook said:
Um... the OS line on the bootloader screen looks blank, unless I'm looking in the wrong place.
Click to expand...
Click to collapse
No, you're looking in the right place. Its somewhat common for OS number to be blank, its a known bug in older TWRP versions that it deletes the OS number.
What does it say for hboot number and radio number?
If the phone still on the stock ROM you originally rooted on? If so, is it Lollipop, Kitkat, etc.?
eaflook said:
U
Should I do this? http://forum.xda-developers.com/htc-one-m8/help/guide-how-to-solve-soft-brick-phone-t2824193
Click to expand...
Click to collapse
You can do that. All that "guide" describes is one way to get a ROM on an SD and flash it, which is one of the options I already suggested in Post #2 above.
But what ROM will work, somewhat depends on the info I requested above.
redpoint73 said:
What does it say for hboot number and radio number?
Click to expand...
Click to collapse
hboot number-3.19.0.0000
radio [email protected]
redpoint73 said:
If the phone still on the stock ROM you originally rooted on? If so, is it Lollipop, Kitkat, etc.?
Click to expand...
Click to collapse
Yes it is still on the stock root ROM. I am running Lollipop 5.0.2.
eaflook said:
hboot number-3.19.0.0000
radio [email protected]
Yes it is still on the stock root ROM. I am running Lollipop 5.0.2.
Click to expand...
Click to collapse
You should be fine flashing most any ROM on the AT&T or "international" M8 development forums. Just avoid other dev sections for variants, such as the Sprint or Verizon dev sections.
Before flashing a ROM, you may want to update your TWRP version to 3.0.whatever.
Although I have to admit, I'm still on TWRP 2.8.4, and its worked fine flashing LP and MM custom ROMs. Any older than 2.8.something may cause issues.
Alternately, relock bootloader and run RUU 4.28.502.2 (Lollipop). If you want to run the Marshmallow RUU (6.20.502.5), you'll need to flash the MM firmware first, then RUU. Link that describes that process, as well as all ATT RUUs is on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
redpoint73 said:
You should be fine flashing most any ROM on the AT&T or "international" M8 development forums. Just avoid other dev sections for variants, such as the Sprint or Verizon dev sections.
Before flashing a ROM, you may want to update your TWRP version to 3.0.whatever.
Although I have to admit, I'm still on TWRP 2.8.4, and its worked fine flashing LP and MM custom ROMs. Any older than 2.8.something may cause issues.
Alternately, relock bootloader and run RUU 4.28.502.2 (Lollipop). If you want to run the Marshmallow RUU (6.20.502.5), you'll need to flash the MM firmware first, then RUU. Link that describes that process, as well as all ATT RUUs is on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Click to expand...
Click to collapse
Do you know how I might update TWRP from 2.7.0.2?-----Nevermind, I got it.
eaflook said:
Do you know how I might update TWRP from 2.7.0.2?-----Nevermind, I got it.
Click to expand...
Click to collapse
Good practice is to post what you did (or going to do) for the benefit of others that may have the same question; or so we can verify you are on the right track.
In case others may have the same question (or you get stuck again), all TWRP versions, and instructions (recommend install with fastboot method) are here: https://twrp.me/devices/htconem8gsm.html