Hi everyone, sorry for this long topic, I just try to understand everything correctly.
So recently I got my hands on my new device HTC One X+ of course before buying it I did check XDA HOX+ forum to see what I will be able to do with it, so I understand no S-OFF at this time, so no hardcore ROM flashing etc. but I was fine with that as I do enjoy Sense 4.x and up so I thought I will not do anything with my HOX+ at least for the first couple of months.
So with these kind of thought I went to confirm purchase of the phone, I did bought it as a second hand, but I wasn't ready for what I seen when I had it in my hands, first of all I noticed it is rooted, then I noticed it has TWRP installed, and last thing was InsertCoin ROM and of course my prayers to see in bootloader S-OFF didn't fulfill.
Now what I got out from my phone was that I have:
bootloader: 1.40.0000
version-main: 1.17.161.7
cidnum: VODAP001
I flashed CM11 nightlys and so far I am on CM11, everything is smooth and I enjoy it, but I still would like to revert back to complete stock or I would love to get ARHD rom running on my phone.
I did look up on internet for Vodafone RUU, but all I found was older one - 1.14.161.13 where I would obviously get bootloader version error ([140])
So far no luck to get some newer one.
Also I was unable to try on ARHD as there was no firmware.zip file for my CID and I wasn't able to get anything what I could send to mike1986 so he can create firmware package for VODAP001 CID.
Another thing I noticed while trying to find some decent solution to get things right, people say that you can use TWRP backups, I mean someone who has for example same CID makes a backup and then you can use that persons made backup to restore your own phone, is that right ? Like if someone got for example stock RUU with CID VODAP001 and he gives me his backup I could be able to restore it back to the state it was as bought from Vodafone ?
Any information will be appreciated, and thanks in advance.
Related
Hi. I'm in one of those boat situations.
Rooted my international UK hox+ which is on O2.
ENRC2B_U_JB_45
CID O2___001
Build 1.17.401.1
HBOOT 1.35.0000
Radio 3.1204.168.32
Just wondering if its possible to restore using someone else's nandroid backup from a different but same cid phone?
Tried to extract the rom from the O2 RUU but rar/7zip won't have any of it.
Also wondering if there are RUU updates in the future that will sort me back to stock? If so it it just a matter of time?
Sorry for bringing up the same thing you keep hearing about but just wanna settle my head. Thanks
kingtonberry said:
Hi. I'm in one of those boat situations.
Rooted my international UK hox+ which is on O2.
ENRC2B_U_JB_45
CID O2___001
Build 1.17.401.1
HBOOT 1.35.0000
Radio 3.1204.168.32
Just wondering if its possible to restore using someone else's nandroid backup from a different but same cid phone?
Tried to extract the rom from the O2 RUU but rar/7zip won't have any of it.
Also wondering if there are RUU updates in the future that will sort me back to stock? If so it it just a matter of time?
Sorry for bringing up the same thing you keep hearing about but just wanna settle my head. Thanks
Click to expand...
Click to collapse
I have the same problem and I have been posting all over this forum trying to get help.
It would appear that either there is no solution or nobody knows what the solution is.
screenoff said:
I have the same problem and I have been posting all over this forum trying to get help.
It would appear that either there is no solution or nobody knows what the solution is.
Click to expand...
Click to collapse
Yea. Have a very good friend giving me advise.
should be able to push the firmware.zip 0.35 through adb sideload.
Will let you know if I get it sorted. Just after stock for a nandroid back up.
its what we get for not making backups :x
kingtonberry said:
Yea. Have a very good friend giving me advise.
should be able to push the firmware.zip 0.35 through adb sideload.
Will let you know if I get it sorted. Just after stock for a nandroid back up.
its what we get for not making backups :x
Click to expand...
Click to collapse
Perhaps, I am a bit confused.
I do have a nandroid back up, but the version is showing hboot 1.35 and this is apparently why I am not able to run the Stock RUU even after I have relocked the bootloader.
I was under the impression that when I originally did the rooting etc, this changed my hboot version from 1.30 to1.35.
I have already bricked my phone once and it cost me heavily so I am now very cautious not to do the same thing again.
All I want to do is return to Original Stock.
At the moment there are only old releases of ruu which won't work, cause of newer hboot. If someone provides a backup you will have success, but most Users don't share their backups. I opened a thread for backups, with less success
Gesendet von meinem HTC One X+ mit Tapatalk 2
Was thinking to try push firmware on it. Or will O2 throw a RUU in the future? If they ever.
I have a nandroid backup that I did before flashing the updated ROM onto my phone.
This backup was done just after I had unlocked and rooted my phone.
What action actually caused the updating of hboot ?
Was it the unlocking of the bootloader or the rooting ?
Because if it was neither of these actions, then I have a nandroid backup that has the original hboot version.
But, unless I am failing to carry out some other action when trying to return to stock, my present hboot version is 1.35.
Do any of the Developers read this thread or Experienced people because I would like to know what action actually updates the HBOOT version ?
Is it the Unlocking ?
Is it the Rooting ?
Is it the Flashing of an Updated ROM, like AOKP Jelly Bean 4.2.2 ?
For a new person like me, this is a learning curve and it is interesting to understand what actually takes place.
did anything happen with this? Id like to go back to stock, purely just to wipe the phone clean, but the o2 uk ruu fails saying wrong version. my hboot is 1.35.0000 radio 3.1204.168.32.
Is it possible for me to get back to stock?
is there another way of wiping the phone clean?
You have to use a backup.
Install a clean one , install stock recovery and lock your phone.
Thats all
I opened a thread a couple of month ago, but nobody provides backups ...
Mikey F said:
did anything happen with this? Id like to go back to stock, purely just to wipe the phone clean, but the o2 uk ruu fails saying wrong version. my hboot is 1.35.0000 radio 3.1204.168.32.
Is it possible for me to get back to stock?
is there another way of wiping the phone clean?
Click to expand...
Click to collapse
already told you, there's no RUU for our devices....just find a plain stock rom...
Hello all!
First of all, I think this website is awesome, lots of usefull stuff and information, you guys doing a great job. By guides on this site I was able to unlock my phone, root it and install all kinds of different ROMS. With those guides it was very easy! However now I seem to stupid to restore my HTC ONE (TMO-101) back to stock. What I exactly want? Just completly restore it to default. After hours of doing and reading stuff, I just gave up. I think I made it even worse as before. I used and restored an backup (old one) from original state. But! I cannot update with the OTA pushed. Seems I first have to put back the original recovery and unroot the device. I thought that an RUU would be the solution, however I cannot find any for my version or in other words one that actually works for me! Then I thought ok lets try the backups made by someone else and restore those, recovery tool is not working anymore... If you could provide me with the correct steps and tools to perform this, I would be very thankfull! Because I'm totally lost....
My HTC ONE current state:
***TAMPERED***
***RELOCKED***
***SECURITY WARNING***
M7_UL PVT SHIP S-ON RH
HBOOT 1.44
Android version 4.1.2
* Used Clockmod recovery before but it does not seem to work anymore, so basically no recovery atm.
Thanks in advance for looking in to my issue!
Hanzz2013 said:
Hello all!
First of all, I think this website is awesome, lots of usefull stuff and information, you guys doing a great job. By guides on this site I was able to unlock my phone, root it and install all kinds of different ROMS. With those guides it was very easy! However now I seem to stupid to restore my HTC ONE (TMO-101) back to stock. What I exactly want? Just completly restore it to default. After hours of doing and reading stuff, I just gave up. I think I made it even worse as before. I used and restored an backup (old one) from original state. But! I cannot update with the OTA pushed. Seems I first have to put back the original recovery and unroot the device. I thought that an RUU would be the solution, however I cannot find any for my version or in other words one that actually works for me! Then I thought ok lets try the backups made by someone else and restore those, recovery tool is not working anymore... If you could provide me with the correct steps and tools to perform this, I would be very thankfull! Because I'm totally lost....
My HTC ONE current state:
***TAMPERED***
***RELOCKED***
***SECURITY WARNING***
M7_UL PVT SHIP S-ON RH
HBOOT 1.44
Android version 4.1.2
* Used Clockmod recovery before but it does not seem to work anymore, so basically no recovery atm.
Thanks in advance for looking in to my issue!
Click to expand...
Click to collapse
I was in the same boat as you last night, I thought I bricked my phone, but thanks to this post, I was able to do it. http://forum.xda-developers.com/showthread.php?t=2496074
First you have to relock your bootloader, it's quite easy. Go to your fastboot folder on your computer (the same one you used to unlock your phone) open command prompt there (Shift + right click) then type fastboot oem lock then run that RUU that I posted and it will restore you to 100% stock, like you just took it out of the box.
Thanks!!
Gonna try this right away:good:
It's not working. Model-ID error (130). Had this one before, it's the US version. But, I got the TMO101 (DE). This is the model also sold in the Netherlands.......
Any RUU available for this as well? Couldn't find it or
Other options?
Thanks!
Hi all,
So recently I caved and decided I should attempt to install a custom rom and bring my android experience to the next level. Being completely new to this but being fairly tech savvy I decided I would be able to do this no problem. I Went to the cyanogen mod blog and followed the guide to unlocking the bootloader and then to install the rom. Everything seemed to be going perfectly until I got to the final step and rebooted, but it would not boot past the "HTC ONE" screen. I kept retrying the previous steps until I noticed I forgot to flash the boot.img . I then did that and reinstalled the rom, but alas; still no luck. The only difference now is that it doesn't boot past the "Queitly Different" screen. I haven't been able to get past this bump in my android enlightning road. I was able to boot into a sketchy looking 4.3 but it lacked many features and wasn't able to detect my sim card. If anyone has some suggestions or tips on how I could correct these errors, would be greatly apprectiated.
I was told this is vital information in the helping process ( I'm still new to this)
Evitare_UL PVT SHIP S-ON RL
HBOOT-1.40.0000
CPLD-None
MICROP-None
Thank you in advance !
Jakezors said:
Hi all,
So recently I caved and decided I should attempt to install a custom rom and bring my android experience to the next level. Being completely new to this but being fairly tech savvy I decided I would be able to do this no problem. I Went to the cyanogen mod blog and followed the guide to unlocking the bootloader and then to install the rom. Everything seemed to be going perfectly until I got to the final step and rebooted, but it would not boot past the "HTC ONE" screen. I kept retrying the previous steps until I noticed I forgot to flash the boot.img . I then did that and reinstalled the rom, but alas; still no luck. The only difference now is that it doesn't boot past the "Queitly Different" screen. I haven't been able to get past this bump in my android enlightning road. I was able to boot into a sketchy looking 4.3 but it lacked many features and wasn't able to detect my sim card. If anyone has some suggestions or tips on how I could correct these errors, would be greatly apprectiated.
I was told this is vital information in the helping process ( I'm still new to this)
Evitare_UL PVT SHIP S-ON RL
HBOOT-1.40.0000
CPLD-None
MICROP-None
Thank you in advance !
Click to expand...
Click to collapse
Evitare_UL is the AT&T version of this phone, not the international one x+ (enrc2b) and since these phones have some differences in hardware the roms are not compatible. afaik there's no CM for Evitare_UL, only a very early version with lots of bugs.
so atm it's not possible for you to get anything above android 4.1, best would be you get yourself a stock based rom for AT&T one x+ from the One X+ Android Development forum and install this. Otherwise you have will have to restore a backup if you made one...
Okay , so you've cleared a whole lot up for me. Would you be able to direct me to any of these roms by any chance?
Jakezors said:
Okay , so you've cleared a whole lot up for me. Would you be able to direct me to any of these roms by any chance?
Click to expand...
Click to collapse
oh come on, it's not that hard to find the One X+ Android Developement forum
just make sure the rom is made for your phone (read the first posts(s) by the dev) and then try one yourself, i can't recommend anything since i have the international One X+.
A few months ago I, posted a thread with a similar idea in mind however, the only answer I got was (I'm paraphrasing) "Why go back to stock,the custom ROMS are much better anyways". Well the time has come where I figure out the "why?". Yesterday I brought the phone into Wind for a check of why it's not sending MMS messages when the data is on (strangely enough it turns data on while sending the mms but, that's a story for another time). The people at Wind refused to look at my phone and told me to come back when it has stock firmware. (because, obviously I haven't returned to stock yet). Now from what I understand, from doing some research today on the forums, that the HTC Amaze (Wind Variant) has some weird software issues upon flashing a T-Mobile based ROM which I can link back to Speed Rom. So, I do the standard "Relock the bootloader and run the RUU.exe" and it just comes up with an error saying my hboot is the wrong version. The forums are pretty blank on ways to get around this (well besides going S-OFF which is a problem considering I need to bring my phone in to get the MMS issue checked. Also, I don't have that level of confidence in myself to insure I don't destroy my phone when going s-off). So, I was wondering if anyone has a fix for the issue. I'm confident that someone could possibly help me with my issue. (PS my current ROM is the latest Cyanogenmod 10 nightly, and I'm using 4ext recovery on the Amaze/Ruby).
Hope, I can get this issue resolved and thank you for helping me out with what ever problems I've had on my journey with this phone.
P.S: I didn't mean to double post the same question it's just I really needed this problem solved. I hope you can forgive me. (I fully understand if I can't return to stock under these circumstances.)
It's funny, I'm kind of in the same boat, except for 2 "minor" differences:
1) The "Smart Flash" on 4EXT never worked for me (and has consistently corrupted my internal SD card, but been able to fix it each time), so I have S-ON yet
2) I've rooted the phone itself and unlocked the bootloader, but the HBOOT is 1.93.0002, and from what I've seen, the latest firmware patch is .2222 although that really shouldn't matter
This is my 2nd HTC Amaze, and the first time I've gone through the rooting and that, took me at most an hour to complete, including time spent choosing a CMOD (I ended up with 7). This time around...I'm practically pulling my hair out because I cannot perform the S-OFF via Linux (LiveCD of course) nor starting from "square 1". I seem to be in limbo with 4EXT.
I installed Viper Amaze 1.7.2, but continually got stuck on the boot screen. Further investigation revealed that I needed to superCID the phone, which in turn would be to S-OFF first.
Additionally, I've downloaded and flashed the "stock ICS" ROM (since that was my stock ROM to begin with, naturally upgraded ICS), renamed to PH85IMG.zip yadda yadda. It recognizes and loads, but never "updates", more or less does anything after the loading bar on the bootloader.
So, just to try how much I've dug myself in with this, I've downloaded and tried 2 other ROMS, both saying "bad" (no status 7 error like the RUU flash).
I want to try out the Viper Amaze ROM since so much work and effort went into it, and it seriously looks awesome, but because my original tool that I used (HTC Super Tool) didn't require me all of these extra steps (and I didn't remember the program until now), I want to return back to stock so I can start over in a sense and complete those couple of steps that I inadvertently missed. I really feel like I'm missing something stupid.
Out of 7 Android phones that I've completed the custom ROM setup, it has to be this phone...
Anyways, tl;dr here's what I got:
Bootloader:
**Unlocked**
Ruby PVT SHIP S-ON RL
HBOOT 1.93.0002
eMMC-boot
Starting ROM: Wind Mobile ICS 4.0.3 Stock ROM
End ROM: Viper Amaze 1.7.2
Where I'm At: 4EXT, Status 7 error upon stock ROM flash. No other custom ROM works. PH85IMG.zip doesn't seem to do much upon loading via bootloader.
darkandshadow said:
Bootloader:
**Unlocked**
Ruby PVT SHIP S-ON RL
HBOOT 1.93.0002
eMMC-boot
Starting ROM: Wind Mobile ICS 4.0.3 Stock ROM
End ROM: Viper Amaze 1.7.2
Where I'm At: 4EXT, Status 7 error upon stock ROM flash. No other custom ROM works. PH85IMG.zip doesn't seem to do much upon loading via bootloader.
Click to expand...
Click to collapse
I actually have the same HBOOT version as you! I have never met a device which had more difficulties going back to stock than the Wind variant of the Amaze. Anyway best of luck on your issue, and just try to remember me if you find a way back to stock. I guess we are on the same boat and the Wind isn't helping us out *Budum Tssss* . (BTW if you manage to make it back to stock I suggest you use hasoon2000's toolkit for the Amaze. It's a good toolkit for the Amaze.)
Megapead said:
I actually have the same HBOOT version as you! I have never met a device which had more difficulties going back to stock than the Wind variant of the Amaze. Anyway best of luck on your issue, and just try to remember me if you find a way back to stock. I guess we are on the same boat and the Wind isn't helping us out *Budum Tssss* . (BTW if you manage to make it back to stock I suggest you use hasoon2000's toolkit for the Amaze. It's a good toolkit for the Amaze.)
Click to expand...
Click to collapse
I managed to install the Viper Amaze. I went back, relocked the bootloader, got a new
ID token unlock key, and reflashed (the hell out of) everything. It actually worked.
As for the Wind Rom push back, try the EXE found here on XDA:
http://forum.xda-developers.com/wiki/HTC_Amaze_4G/ROMs
darkandshadow said:
I managed to install the Viper Amaze. I went back, relocked the bootloader, got a new
ID token unlock key, and reflashed (the hell out of) everything. It actually worked.
As for the Wind Rom push back, try the EXE found here on XDA:
http://forum.xda-developers.com/wiki/HTC_Amaze_4G/ROMs
Click to expand...
Click to collapse
I tried, that EXE seems to only be for update from Gingerbread purposes or, was broke after I flashed a T-Mobile ROM on the device.
Hi all,
I was hoping for a little help. I got my phone last summer on At&t and immediately converted the Developer's Edition. The phone is currently rooted,
has s-off and is on a KitKat Rom.
The above said, would I be able to get back to stock? I've Googled it and can only find instructions on Stock to Developer's, not the other way around.
TIA
infg3570
infg3570 said:
Hi all,
I was hoping for a little help. I got my phone last summer on At&t and immediately converted the Developer's Edition. The phone is currently rooted,
has s-off and is on a KitKat Rom.
The above said, would I be able to get back to stock? I've Googled it and can only find instructions on Stock to Developer's, not the other way around.
TIA
infg3570
Click to expand...
Click to collapse
did you s-off ? did you change your CID ?
just change your CID back to AT&T
fastboot oem writecid CWS__001
and flash the AT&T RUU
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
clsA said:
did you s-off ? did you change your CID ?
just change your CID back to AT&T
fastboot oem writecid CWS__001
and flash the AT&T RUU
http://www.androidruu.com/getdownlo...09_10.26.1718.01L_release_356565_signed_2.exe
Click to expand...
Click to collapse
Thank you! All though I have email notification set up for replies, I never received one. Interesting is that my CID remains the At&t and i currently have s-off. When I RUU.exe (I downloaded the same the other night), I get an error and it restarts my phone. I'm wondering if it's because I have a KitKat Rom already installed and the software number is slightly higher than the RUU? The software number is 4.18.502.7 (my phone). I think the RUU is 502.1.
Thanks again,
infg3570
infg3570 said:
Thank you! All though I have email notification set up for replies, I never received one. Interesting is that my CID remains the At&t and i currently have s-off. When I RUU.exe (I downloaded the same the other night), I get an error and it restarts my phone. I'm wondering if it's because I have a KitKat Rom already installed and the software number is slightly higher than the RUU? The software number is 4.18.502.7 (my phone). I think the RUU is 502.1.
Thanks again,
infg3570
Click to expand...
Click to collapse
If your s-off use my decrypted RUU here
http://www.androidfilehost.com/?fid=23329332407580500
instructions are here
http://forum.xda-developers.com/showthread.php?t=2695749
clsA said:
If your s-off use my decrypted RUU here
http://www.androidfilehost.com/?fid=23329332407580500
instructions are here
http://forum.xda-developers.com/showthread.php?t=2695749
Click to expand...
Click to collapse
I tried as you have suggested your decrypted file. Unfortunately, I get an error when trying to run it via ADB in fastboot.
I've rooted when I first got the phone last summer using Revone method/tool. All worked fine and i had continued updating the OS a few times with stock rooted phones.
The last that i updated to was a stock rooted odex kitkat ROM found here http://forum.xda-developers.com/showthread.php?t=2676986
Only thing that seemed wrong was that I couldn't reinstall any of my apps requiring root. The error that would pop up is "Could not install to SD card".
Now, I have to say that I noticed that with some updates, it seems that new ROMS don't clean up the old files/framework even after fully wipes. It seems to back it up in some folders (sdcard0, sdcard00, sdcard000 etc). All though the sdcard folder seems clean and refreshed, the others mentioned had all my old files in there. Since I've updated to kitkat, I can no longer view these folders (I used to use Root Explorer, but now since the kitkat install - I can't). What caused me to notice was the fact that my storage, in the 'Other:' section, shows 20GB out of 32. So, I used ES File Mgr to see if I can create some space by deleting the so-called backup folders. I think that was a bad mistake because now, even after a full data wipe, I still can't:
* Install root-required apps
* flash the zip file you provided
* use the exe version of the zip you provided (still get an error with that as well)
* Clear the 20gb of data I don't need
* get back to the At&t carrier brand from the Developer's Edition that i switched it to back last summer.
Fortunately the phone works fine, but is this hopeless? Anything I can do to get this going again (really thing I messed things up)
Is there anything else I can try?
thank you,
infg3570