I tried to restore my phone back to 1.36.531.6 and redo the entire process to check something, but nothing seems to work. If I try any of the RUUs (either 531.5 or 531.6) I get "Main version is older". The longer method with the separate stock recovery also doesn't work anymore. Any ideas how to downgrade the stock rom?
I'm assuming you're not rooted?
nope, im rooted, just wanted to see whether i can use any of the downgrade methods and do it again. as i mentioned at the OP, they dont work on my phone, so im waiting for someone to confirm and hopefuly a solution will soon be found.
lgtsanev said:
nope, im rooted, just wanted to see whether i can use any of the downgrade methods and do it again. as i mentioned at the OP, they dont work on my phone, so im waiting for someone to confirm and hopefuly a solution will soon be found.
Click to expand...
Click to collapse
do u have the new stock rom install on your phone?
if so, i think u can install new RUU only after using a custom rom...
Before the update, I was able to flash the 531.6 RUU without problem, now I can't. Also, I got a confirmation from another guy who gets the same "main version" message (he also flashed the OTA)... I was thinking that perhaps I should flash another ROM+kernel, and then try to do the downgrade... Im doing this right now with QuickSense, and will share what happened...
P.s. Of course, as a noob just now I realized this wont do any good, since theyve upgraded hboot...
You guys need to edit the text in the android-info.txt file.
It's because the hboot needs to verify the current file. For example in this new file that you just downloaded it has:
modelid: PH8511000
cidnum: T-MOB010
mainver: 1.43.531.3
hbootpreupdate:0
DelCache:1
The previous version that you tried earlier:
modelid: PH8511000
cidnum: T-MOB010
mainver: 1.36.531.5
hbootpreupdate:0
DelCache:1
See the difference? So all I did was modified the 1.36.531.5 with 1.43.531.3 and replaced the android-info.txt file in the zip file and it worked.
I'm not sure why HTC does this or even if there is a way around it but so far we have three versions for the US PH85IMG.zip files.
1.43.531.3 (newest)
1.36.531.6 (kinda new)
1.36.531.5 (shipped)
Other carriers such as Wind may have a different version so it's kinda difficult to make a universal PH85IMG.zip file. I'm curious if we could just use something as simple as:
modelid: PH8511000
cidnum: T-MOB010
hbootpreupdate:0
DelCache:1
or
modelid: PH8511000
cidnum: T-MOB010
mainver: *
hbootpreupdate:0
DelCache:1
Anyone is welcome to try if you like.
So 1.36.531.5 and 6 work with the new hboot? That would be an ingenious solution!
lgtsanev said:
So 1.36.531.5 and 6 work with the new hboot? That would be an ingenious solution!
Click to expand...
Click to collapse
wont work man sorry
I am having the same problem.
How to downgrade the device to be!
Related
ROOT and S-OFF IS REQUIRED
i think, s-on too,through what ive read in user feed back
but if your phone explodes, or goes bad guy transfeormer on your ass
you dont know where i live
<exactly>
PLEASE READ POST 1 AND 2 BEFORE TRYING
After over 13 months with this phone and thousands of flashes behind me, I've realised that having this hboot (for some reason) causes the least rom/boot/kernel issues
After having to revert to stock ICS, I lost the said hboot and got updated to 1.49.0053 and found that bootmanager app could no longer edit boot.img correctly, so I found this patch (sorry can't give credits, don't know who too) and flashed it, now I'm back and having no issues at all
guide
#1, Download zip (IN POST 2)
#1, Simply place the pg86img.zip on root of sd,
#3, Boot into bootloader and run the update
#4, Follow onscreen instructions
it will flash the bootloader, reboot, then flash splash img , then reboot
and your now in hboot 1.49.0007
Simple as that
...............................................................................................................................................................................................................................................
FIXES
(NO LONGER NEEDED)
\/ \/ \/ \/
\/ \/ \/
\/ \/
\/
...............................................................................................................................................................................................................................................
IF YOU FIND THAT BOOTLOADER THROWS AN INCOMPATIBLE CID ERROR
OVER ADB TYPE "fastboot oem writecid 11111111" FOR SUPER CID
thanks to flashmaniac for making this common knowledge
OR
OVER ADB PUT THE FOLLOWING
Fastboot oem writecid "HTC__001"
(or whatever your cid is)
thanks to metamasterplay for making this common knowledge
Also the cid problem can be fixed when you add HTC__* to the android-info.txt and the rest VODAP* and so on....
thanks to flashmaniac for making this common knowledge
If you want your cid id added, give us a holler
I'm quite sure you will find many different issues you were having before are now, no longer an issue
PG86IMG.zip
Working for EVERYONE
these cid's are added into the compatibility check file (android-info.txt file)
cidnum:htc_*
cidnum:VODAP_*
cidnum:VODAP_405
cidnum:YOIGO***
cidnum:VODAP***
cidnum:VIRGI***
cidnum:T-MOB***
cidnum:TELUS***
cidnum:TELST***
cidnum:SBM__***
cidnum:SKT__***
cidnum:BSTAR***
cidnum:H3G__***
cidnum:FASTW***
cidnum:HTCCN***
cidnum:HTC__***
cidnum: HTC__001
cidnum: HTC__032
cidnum: HTC__A07
cidnum: HTC__102
cidnum: HTC__304
cidnum: HTC__203
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__016
cidnum: HTC__J15
cidnum:YOIGO***
cidnum:VODAP***
cidnum:VIRGI***
cidnum:T-MOB***
cidnum:TELUS***
cidnum:TELST***
cidnum:SBM__***
cidnum:SKT__***
cidnum:BSTAR***
cidnum:H3G__***
cidnum:FASTW***
cidnum:HTCCN***
cidnum:HTC__***
cidnum:HTC__*
cidnum:VODAP__*
cidnum:HTC__662
cidnum:HTC__044
thanks to flashmaniac for all his information and awesomness
Hi I M Going to Try This
I am S-off
hboot 1.49.0007
Mwakious 12.4
some days ago flashing the pg86img hboot is (i think) not working good...when connected to pc it says device not recognized...
even adb dont work..
whenever i connect to pc it only charges...
i tryed several roms and trics like check\uncheck usb debug, other usb and usb cords etc ...but even my phone dont connect to pc
Now I m going to flash this pg86img hopping that it will solve my problem....let's see
it can do everything except pc connection
@gav-collins1983
please tel me if you know abut my problem..plz
maurydes said:
hi gave-collins i have my evo s.off(juopuntnear)h.boot 1.53.777 i tried the pg86img response is "cid incorrect-failed" any idea?: Confuso:
Click to expand...
Click to collapse
Oh, hmmmmm do you know your current cid, maybe a change in the txt file may be a fix , but as I aunt an android developer I ain't 100 sure, go check your cid, il check the txt file in the pg IMG
modelid: PG8630000
cidnum: HTC__001
cidnum: HTC__032
cidnum: HTC__A07
cidnum: HTC__102
cidnum: HTC__304
cidnum: HTC__203
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__016
cidnum: HTC__J15
mainver: 1.20.401.2
hbootpreupdate:12
DelCache:1
Here's the txt file hboot uses to determine compatiblity , which firmware are you currently running ?
maurydes said:
hi gave-collins i have my evo s.off(juopuntnear)h.boot 1.53.777 i tried the pg86img response is "cid incorrect-failed" any idea?: Confuso:
Click to expand...
Click to collapse
Fastboot oem writecid HTC__001
Sent from my HTC EVO 3D X515m using xda app-developers app
metamasterplay said:
Fastboot oem writecid HTC__001
Sent from my HTC EVO 3D X515m using xda app-developers app
Click to expand...
Click to collapse
Thanks budd, updated op with that info, giving you credits
Just upgraded my hboot and reverted back like eating donuts. So I confirm this works . You should require a sticky from mods.
metamasterplay said:
Just upgraded my hboot and reverted back like eating donuts. So I confirm this works . You should require a sticky from mods.
Click to expand...
Click to collapse
Thanks for the effort you just put in, I know a lot only do it if needed , so to upgrade and downgrade for trial purposes is much appreciated, thanks again
gav-collins1983 said:
Oh, hmmmmm do you know your current cid, maybe a change in the txt file may be a fix , but as I aunt an android developer I ain't 100 sure, go check your cid, il check the txt file in the pg IMG
Click to expand...
Click to collapse
my cid is vodap 405,what should i do?
maurydes said:
my cid is vodap 405,what should i do?
Click to expand...
Click to collapse
Just try the fastboot method of writing an added cid as explained in the op
Hi GaveCollins
What About My Problem Below??
I am S-off
hboot 1.49.0007
Mwakious 12.4
some days ago flashing the pg86img hboot is (i think) not working good...when connected to pc it says device not recognized...
even adb dont work..
whenever i connect to pc it only charges...
i tryed several roms and trics like check\uncheck usb debug, other usb and usb cords etc ...but even my phone dont connect to pc
Now I m going to flash this pg86img hopping that it will solve my problem....let's see
it can do everything except pc connection
@gav-collins1983
please tel me if you know abut my problem..plz
ipsuvedi said:
Hi GaveCollins
What About My Problem Below??
I am S-off
hboot 1.49.0007
Mwakious 12.4
some days ago flashing the pg86img hboot is (i think) not working good...when connected to pc it says device not recognized...
even adb dont work..
whenever i connect to pc it only charges...
i tryed several roms and trics like check\uncheck usb debug, other usb and usb cords etc ...but even my phone dont connect to pc
Now I m going to flash this pg86img hopping that it will solve my problem....let's see
it can do everything except pc connection
@gav-collins1983
please tel me if you know abut my problem..plz
Click to expand...
Click to collapse
I already answered this budd, earlier on , check a few posts back
I was already reverted from 1.53..... to 1.49..... with using a jouponutbear wire trick, but this good news are :cyclops:
I can tell you that this is only working when you are s-off already. No chance for any other than that.
Still always good as long as you have s-off. Also the cid problem can be fixed when you add HTC__* to the android-info.txt
and the rest VODAP* and so on....
* = wildcard
so no problem for CID anymore =)
Thanks , Flashmaniac, il update op , but can't thank you. I've used my 8 already
gav-collins1983 said:
Thanks , Flashmaniac, il update op , but can't thank you. I've used my 8 already
Click to expand...
Click to collapse
Welcome.
Flashmaniac said:
I can tell you that this is only working when you are s-off already. No chance for any other than that.
Still always good as long as you have s-off. Also the cid problem can be fixed when you add HTC__* to the android-info.txt
and the rest VODAP* and so on....
* = wildcard
so no problem for CID anymore =)
Click to expand...
Click to collapse
So , let me get this right
If I add "VODAP_*" to the txt file in the pg86img it will be working without hassle for anyone on that cid ? Do you have a list of cids by any chance, so I can manually add them all and save people some time
gav-collins1983 said:
Just try the fastboot method of writing an added cid as explained in the op
Click to expand...
Click to collapse
"fastboot oem writecid htc_001" fail : (writecid) invalid cid.....any idea?
maurydes said:
"fastboot oem writecid htc_001" fail : (writecid) invalid cid.....any idea?
Click to expand...
Click to collapse
Try some of these
cidnum: HTC__001
cidnum: HTC__032
cidnum: HTC__A07
cidnum: HTC__102
cidnum: HTC__304
cidnum: HTC__203
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__405
cidnum: HTC__Y13
cidnum:HTC__016
cidnum: HTC__J15
OR GIVE ME YOUR CID, AND IL SEE IF I CAN FIX IT MY END
I bricked my Desire X, I think I tried to unroot by, pushing "recovery_signed.img" & "Relocking" the Bootloader and then I opened RUU & it says 'ERRROR{155}. Now when I "Turn ON" the device it directly goes into bootloader & no response at all. What should i do now to get device loaded with Stock ROM??
Since you're from Dubai you won't be able to use available ruus cause they are made for Eastern Europe.
Just unlock bootloader, flash custom recovery and flash Hasoon's on Infernal's stock rom.
s:
sorry to hear that i got bricked and i cant even go in recovery
devilcummer said:
sorry to hear that i got bricked and i cant even go in recovery
Click to expand...
Click to collapse
You're not bricked, use fastboot...
Sent from my HTC Desire X using Tapatalk 2
I had done it once earlier succesfully!
nlooooo said:
Since you're from Dubai you won't be able to use available ruus cause they are made for Eastern Europe.
Just unlock bootloader, flash custom recovery and flash Hasoon's on Infernal's stock rom.
Click to expand...
Click to collapse
I had once unbricked succesfully through an RUU which got deleted accidently. Then I downloaded a new RUU which have this error. Can u help me?
What is written on top of your phone's bootloader, unlocked or relocked?
reply to nlooooo
nlooooo said:
What is written on top of your phone's bootloader, unlocked or relocked?
Click to expand...
Click to collapse
RELOCKED
*Security Warning*
May I extract the 'rom.zip' fom the current RUU and flash or whatever it is...
Just go to fastboot and run RUU, if that doesn't work try do download RUU again. And which RUU did you use earlier?
Go to fastboot, connect phone to PC, and run command
fastboot getvar cid
from command prompt, I assume you have adb installed.
reply to nlooooo
nlooooo said:
Just go to fastboot and run RUU, if that doesn't work try do download RUU again. And which RUU did you use earlier?
Go to fastboot, connect phone to PC, and run command
fastboot getvar cid
from command prompt, I assume you have adb installed.
Click to expand...
Click to collapse
Should I run the command from adb installed directory? May i know the use of that command?
Never mind, just run RUU from fastboot
Forget about using a RUU when you're from Dubai or another place that doesn't correspond to one of the CID's listed in the RUU thread.
Only option you have is to do what nloooo said in the first place (unlock bootloader, flash CWM and, once in CWM, adb push a 1.14 or 1.18 stock rom to sdcard so you can flash that in CWM) or by restoring a nandroid backup you made earlier.
First check the boot you have (says somewhere on the same screen where it says it's relocked) then either adb push the 1.14 or the 1.18 from the deodexed stock rom thread.
He said that he used ruu previously so he might have a compatible device. Or he had some other ruu but I don't know where he got it.
So, we need him to adb getvar cid so we can know what to tell him... Can he get USB mounted to push PM66IMG.zip?
Sent from my HTC Desire X using Tapatalk 2
I got CID!
Stereo8 said:
So, we need him to adb getvar cid so we can know what to tell him... Can he get USB mounted to push PM66IMG.zip?
Click to expand...
Click to collapse
it showed HTC__J15 .. What to do now?? Stereo8 can u check whether the zip file name 'PM66IMG.zip' correct? I got a vertical progress bar on the right of screen when I renamed it to 'PM66DIAG.zip'? Is it OK??
Did you try to download RUU again and to run it?
You said you got error 155 that's not CID mismatch, this is from RUU readme file:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
Click to expand...
Click to collapse
Are you sure you downloaded Desire X RUU?
EDIT:
The RUU that we have should be compatible with your phone, this is from android-info.txt frextracted from RUU:
modelid: PM6610000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__M27
cidnum: HTC__J15
cidnum: HTC__032
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__016
mainver: 1.18.401.1
btype:1
aareport:1
hbootpreupdate:13
DelFat:1
DelCache:1
reply to nlooooo
nlooooo said:
Did you try to download RUU again and to run it?
Click to expand...
Click to collapse
I ran it again & still same stage! What about post no:14 nlooooo??
I told you that you have compatible device and forget about PM***.img.
Post me the version of RUU that you have.
@Sarun said:
I ran it again & still same stage! What about post no:14 nlooooo??
Click to expand...
Click to collapse
Clear cache, using fastboot flasher,
Reflash recovery usibg same app.
Then flash rom. It will work
Sent from my HTC Desire X using xda app-developers app
current condition
vipinlahoti said:
Clear cache, using fastboot flasher,
Reflash recovery usibg same app.
Then flash rom. It will work
Click to expand...
Click to collapse
The phone is boooting to android with 'UNLOCKED" status. But in the first bootscreen it shows something like this in red color "This build is for....." also I cant turn on the WiFi it's struck in 'Turning On.."
Guys what should i do further?
help me
nlooooo said:
I told you that you have compatible device and forget about PM***.img.
Click to expand...
Click to collapse
The phone is boooting to android with 'UNLOCKED" status. But in the first bootscreen it shows something like this in red color "This build is for....." also I cant turn on the WiFi it's struck in 'Turning On.."
Guys what should i do further?
First, off, awesome NOOB video, and after watching it I can safely say I've done my due diligence. I have scoured our internet and several parallel earth internets with no luck in finding a solution. If any of you can give me a hand, I'd really appreciate it.
Phone Specs:
HTC Rezound
VIGOR PVT SHIP S-ON RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-V14.6.0.7708.00.0507
eMCC-BOOT
Sep 20 2012,17:40:22
SDK tools: "Pulled from the SDK of February 13, 2013"
PROBLEM: Cannot revert to stock rom by
1) using an RUU exe to revert, but it crashes on both my home and office PCs (Win7). The file is the only one I've been able to find: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed
2) or flashing from Amon Ra or TWRP (can't mount eMCC/data)
3) or uploading PH98IMG.zip to SD card and letting Hboot handle the heavy lifting (sticks at HTC boot up screen on reboot)
4) or using "fastboot oem rebootRUU" followed by "fastboot flash zip PH98IMG.zip" gets
sending 'zip' (624366 KB)...
OKAY [ 55.743s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 142.046s
BACKGROUND: I'm obviously a noob, but the only way to learn is by digging in. Here's the progression that's led me to this point:
1) Learned to unlock bootloader
2) Installed cm-10.1-20130629-NIGHTLY-vigor (officially unsupported by available for Rezound from CyanogenMOD's website)
3) Noticed instability so I wiped everything (x3) and tried to revert to stock. Couldn't make any progress, especially since the RUU exe crashes on both Win7 systems I have.
4) To get functionality for work, switched to cm-10.1.0.1-vigor.
5) Still have stability issues, so I'm trying yet again to revert. Current results of attempts are listed above under "PROBLEMS"
Note1: Per Scott's suggestion over either at Phandroid or ScottsRoms (can't remember I've been so many different places), I've modified the android-info.txt in PH98IMG.zip as follows, making sure the version number is higher than the current from CID Getter:
"modelid: PH9810000
cidnum: VZW__001
mainver: 4.09.605.2
hbootpreupdate:12
DelCache:1
DelFat:1
"
Note 2: MD5s check out.
Note 3: Before my first installation of CyanogenMOD's latest nightly, adb worked fine and would list my phone. After CyanogenMOD's latest nightly, adb does succeed in starting daemon and lists what it think is my phone, but instead of listing a phone it lists a blank space and returns to the command prompt. if I try adb reboot, it returns error: device not found. BUT fastboot still works fine.
Appendix 1: fastboot getvar all returns:
C:\Users\Josh\Desktop\Root Project\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.28.0000
(bootloader) version-baseband: 2.23.10.0123r/2.23.10.0124r
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: (seem odd to anyone else that there's no number there?)
(bootloader) serialno: ******
(bootloader) imei:
(bootloader) product: vigor
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PH9810000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: cecc19f7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.499s
Appendix 2: The sequence I've been following trying to get the thing to accept the stock rom is below...and I've tried small variations variations when what's below fails miserably.
1. Load TWRP or Amon Ra recovery
2. Wipe, wipe, wipe!
3. Reboot bootloader
4. fastboot flash recovery recovery_signed.img (have treated as interchangeable in sequence with step 5)
5. fastboot flash boot boot_signed.img (have treated as interchangeable in sequence with step 4)
6. (used this, also from Scott, before I started manually editing the android-info.txt in the image zip) fastboot flash zip SetMainVersionLOW.zip (to make sure the main version is lower than the stock ROM version--otherwise it'll think you're upgrading to a lower version and won't run)
7. fastboot oem lock
8. This step varies. I've tried
a. fastboot oem rebootRUU then fastboot flash zip PH98IMG.zip
b. fastboot boot TWRP or Amon Ra recovery, then flashing PH98IMG.zip from there
c. dropping PH98IMG.zip on the SD card and letting Hboot handle the heavy lifting
I take it you didn't take a back up of your previous rom before installing CM10.1?
mjones73 said:
I take it you didn't take a back up of your previous rom before installing CM10.1?
Click to expand...
Click to collapse
That's correct. And I deserve what I'm going through for that alone if nothing else.
One additional note I'm about to edit into the post above. I've also tried using an RUU exe to revert, but it crashes on both my home and office PCs (Win7). The file is the only one I've been able to find: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed
JoshManning said:
That's correct. And I deserve what I'm going through for that alone if nothing else.
One additional note I'm about to edit into the post above. I've also tried using an RUU exe to revert, but it crashes on both my home and office PCs (Win7). The file is the only one I've been able to find: RUU_VIGOR_ICS_35_S_VERIZON_WWE_3.14.605.12_Radio_RS_1.22.10.0424r_3622A_MR3_9K_release_270509_signed
Click to expand...
Click to collapse
I believe won't be able to use the RUU anyway because your hboot version is too high, you can't back down if you're s-on (and I could be wrong but I haven't seen a RUU with the latest OTA included). I'd suggest just installing a stock rooted rom - http://forum.xda-developers.com/showthread.php?t=2260154
mjones73 said:
I believe won't be able to use the RUU anyway because your hboot version is too high, you can't back down if you're s-on (and I could be wrong but I haven't seen a RUU with the latest OTA included). I'd suggest just installing a stock rooted rom - http://forum.xda-developers.com/showthread.php?t=2260154
Click to expand...
Click to collapse
Thank you! The opening post notes that the ROM comes without the radio or firmware. Will I be ok? I build my own PCs and know that must be an idiot question, but I just don't yet understand enough about the way the phones work. Thank you very much for your help.
JoshManning said:
Thank you! The opening post notes that the ROM comes without the radio or firmware. Will I be ok? I build my own PCs and know that must be an idiot question, but I just don't yet understand enough about the way the phones work. Thank you very much for your help.
Click to expand...
Click to collapse
You already have the latest firmware on your phone, that doesn't get touched when you do a rom install.
Thank you, Matt! I'm downloading the ROM right now. Will post results once it's down.
SOLVED
JoshManning said:
Thank you! The opening post notes that the ROM comes without the radio or firmware. Will I be ok? I build my own PCs and know that must be an idiot question, but I just don't yet understand enough about the way the phones work. Thank you very much for your help.
Click to expand...
Click to collapse
Oh my gosh! I can't believe that did the trick. Matt, you rock! May I send you a Starbucks card or something?
Couple of clarifications if you have time:
1) TWRP wouldn't install the ROM, but Amon Ra would. Any idea why?
2) What in my original post led you to this solution? Just trying to learn. =)
Thank you again!
JoshManning said:
Oh my gosh! I can't believe that did the trick. Matt, you rock! May I send you a Starbucks card or something?
Couple of clarifications if you have time:
1) TWRP wouldn't install the ROM, but Amon Ra would. Any idea why?
2) What in my original post led you to this solution? Just trying to learn. =)
Thank you again!
Click to expand...
Click to collapse
The update-binary and the updater-script in the META-INF are not updated to work properly with TWRP in the rom you installed.
I learned that the hard way when I built my OTA Blue rom.
good to see you got it working
kc6wke said:
The update-binary and the updater-script in the META-INF are not updated to work properly with TWRP in the rom you installed.
I learned that the hard way when I built my OTA Blue rom.
good to see you got it working
Click to expand...
Click to collapse
Makes perfect sense. Rocking along now nicely thanks to you. Seriously, can I send you an Amazon card or something?
JoshManning said:
Oh my gosh! I can't believe that did the trick. Matt, you rock! May I send you a Starbucks card or something?
Couple of clarifications if you have time:
1) TWRP wouldn't install the ROM, but Amon Ra would. Any idea why?
2) What in my original post led you to this solution? Just trying to learn. =)
Thank you again!
Click to expand...
Click to collapse
You're welcome, kc6wke covered question 1, for number 2, I knew you couldn't RUU cause you are on the latest firmware and s-on, it's not possible to downgrade firmware unless you're s-off. Your only option really was to install a different rom so I gave you a stock rooted one.
Matt, I've got an additional question if you have time. Any idea why my attempts to root the new ROM aren't taking hold? The phone is running just fine off the ROM you directed me to. After installation, I booted into Amon RA 3.16, installed superuser and su, and rebooted. Nothing. SUChecker returns "su declined / not found"
Actually nevermind. SUChecker is returning a false negative. Apologies, and thanks again!
The one I gave you was already rooted, no need to do that.
mjones73 said:
The one I gave you was already rooted, no need to do that.
Click to expand...
Click to collapse
I now remember your saying that. Thank you so much for your help. I really appreciate it.
Josh,
I may be wrong but I think that the iemi is sensitive info so you might want to delete that from your original post. Maybe delete your serial number as well just in case.
btw... my phone doesn't show a mainver either, never got an answer as to why not, but it works fine.
Thanks! Done and done.
well he was a noob, but then he just became just like the rest of them
how did he uploaded the rom in Amon Ra.
band001 said:
how did he uploaded the rom in Amon Ra.
Click to expand...
Click to collapse
Depends, are you s-on or s-off?
mjones73 said:
Depends, are you s-on or s-off?
Click to expand...
Click to collapse
s-off
---------- Post added at 06:46 PM ---------- Previous post was at 06:31 PM ----------
band001 said:
s-off
Click to expand...
Click to collapse
Sorry but i am s-on not s-off yet. trying to get info on how to also if this does not work.
I am trying to get my HTC One back to stock to install the 4.2.2 update. I prefer the HTC Sense rom compared to a custom rom.
It was purchased unbranded in Australia. I have flashed TWRP recovery and rooted. I can't find the correct RUU to restore.
Does anyone know which RUU to run, or if I can flash a stock recovery to do this update?
Fastboot Details:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-main: 1.29.980.17
version-misc: PVT SHIP S-ON
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__039
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
It depends...
nmarlor said:
I am trying to get my HTC One back to stock to install the 4.2.2 update. I prefer the HTC Sense rom compared to a custom rom.
It was purchased unbranded in Australia. I have flashed TWRP recovery and rooted. I can't find the correct RUU to restore.
Does anyone know which RUU to run, or if I can flash a stock recovery to do this update?
Fastboot Details:
version: 0.5
version-bootloader: 1.44.0000
version-baseband: 4A.14.3250.13
version-main: 1.29.980.17
version-misc: PVT SHIP S-ON
product: m7_ul
platform: HBOOT-8064
modelid: PN0714000
cidnum: HTC__039
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Click to expand...
Click to collapse
My understanding is that it depends... I'm pretty sure you can S-OFF and change the modelid and cidnum, so you can essentially use any RUU, or more specifically, use the RUU that is supplied by your service provider.
The other thing you can do is simply flash a stock ROM in recovery and that won't matter whether you have the settings correct or not.
The RUUs can be found here: http://forum.xda-developers.com/showthread.php?t=2377902
and stock ROM images can be found here: http://forum.xda-developers.com/showthread.php?t=2384631
It doesn't appear there is an RUU out for your phone yet as-is, so you'd probably have to change the MID and CID to use an RUU.
Progress.... Finally
Thanks for the reply.... I wish I had seen your stock recovery file earlier!
I am with Vodaphone and this is the first time in years that I have had good quality data connections with them. Due to this I am hesitant change the CIDNUM and flashing another RUU an possible another radio. The stock radio is working well and keeping the LTE working well is my main priortiy.
I have played with the GE 4.3 rom and also with Cyanogenmod 10.2. The GE was rather plain and I felt it was missing a lot of the standard android functions. I also missed having the white setup menu from the HTC rom. CM10.2 is only a new release. I have used CM10.1 on my old SG2 and enjoyed the rom and the daily updates. I missed having Beats audio (paying with the EQ's just doesn't sound the same over the HTCs spectacular speakers) and LTE never worked. This might be due to the fact that the model on the CM site is HTC One (GSM) which from what I have read is not an LTE model. I will try this again after 10.2 has settled down and they have fixed a lot of the bugs.
I figured out how to get the OTA update yesterday.
1. Restore the nandroid from here. This worked but I think the nandroid was from an Optus phone which had the CIDNUM change to HTC__039 before sale. There was one optus app (called "Sim Setup") installed after the restore.
2. CMW was still installed so I flashed the recovery.img from the same nandroid through fastboot. This took the recovery back to stock.
3. Relocked the bootlader.
4. OTA update then worked Downloaded >400mb over LTE in Coburg, Melbourne in less then 5 minutes.
4.2.2 is working well except there is now a vodaphone app (called "Updates"). This is a odd and I want a fully HTC stock rom. This weekend I will try restoring from a TWRP nandroid I made before I flashed any custom roms and then try OTA again. This should work ok but I will take another nandroid just in case.
I am happy to hare more details with other people who might be having probems restoring their HTC__039 back to stock to receive OTA.
When I originally unlocked the bootloader I used the HTC method as I wasn't aware of revone. Is it possible to use this now as I had no lock trying to S-OFF the device after the HTC method?
So I've been trying my damnedest for the past week to un-root my HTC One, but I can't seem to make any progress. Unfortunately, I believe I may have flashed the wrong ROM at one point, making my situation much worse. I think the kernel is totally wrong, the CID, and god only knows what else. I never S-OFFed, so I can't imagine i screwed things up too bad, but nevertheless, I have had no luck running a valid RUU in Windows nor gotten fastboot to successfully flash the stock rom zip. I have an AT&T HTC One M7, currently showing the following info:
INFOversion: 0.5
INFOversion-bootloader: 1.54.0000
INFOversion-baseband: 4A.18.3263.15
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.06.1700.10
INFOversion-misc: PVT SHIP S-ON
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: CWS__001
INFObattery-status: good
INFObattery-voltage: 4184mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-94cf81a8fd
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
All I want to do is un-root and restore the device entirely back to stock and somehow I've really messed my phone up. Total noob here, appreciating any direction and advice to get my phone back to it's original state. Can anyone help? Thanks in advance!
Move Thread
Would anyone know how I could move this thread to the more general HTC One board (http://forum.xda-developers.com/forumdisplay.php?f=2117)? Since this is not a carrier specific problem and nobody in the AT&T forum seem to know what to do either, it would make sense for more HTC One users to see this as they may have more advice. thanks
When you tried to Flash the stock RUU did you make sure to relock the bootloader first?
RespectTheTech said:
When you tried to Flash the stock RUU did you make sure to relock the bootloader first?
Click to expand...
Click to collapse
yep and I got Error 155 every time, after more than a handful of attempts. I tried troubleshooting the error by reading more than a dozen threads here on xda, but still could not get anything to work.
jinkus said:
yep and I got Error 155 every time, after more than a handful of attempts. I tried troubleshooting the error by reading more than a dozen threads here on xda, but still could not get anything to work.
Click to expand...
Click to collapse
Earlier today I had completely bricked my phone and inadvertently deleted the entire OS so that it wouldn't boot any further than the HTC Logo.
The Forum won't let me post links yet because my lack of posts so I will PM you the links I used to get back to stock.
RespectTheTech said:
Earlier today I had completely bricked my phone and inadvertently deleted the entire OS so that it wouldn't boot any further than the HTC Logo.
The Forum won't let me post links yet because my lack of posts so I will PM you the links I used to get back to stock.
Click to expand...
Click to collapse
That RUU file by DesignGears is one of the few RUU's I've attempted to use, and have gotten Error 155 with. In the video, the guy mentions that while running the RUU, the Image Version for both From and TO should be the same. Mine are not. The From version is 3.06.1700.10 and the To version is 1.26.502.12. So the ROM/kernel on my phone is for the Google Play Edition, yet I do not have a Google Play Edition phone.
If I try using fastboot to flash a 1.26.502.12 AT&T rom.zip file I downloaded, I get this error: usb_write failed with status e00002be
jinkus said:
That RUU file by DesignGears is one of the few RUU's I've attempted to use, and have gotten Error 155 with. In the video, the guy mentions that while running the RUU, the Image Version for both From and TO should be the same. Mine are not. The From version is 3.06.1700.10 and the To version is 1.26.502.12. So the ROM/kernel on my phone is for the Google Play Edition, yet I do not have a Google Play Edition phone.
If I try using fastboot to flash a 1.26.502.12 AT&T rom.zip file I downloaded, I get this error: usb_write failed with status e00002be
Click to expand...
Click to collapse
The Image versions I had didn't match either, but weren't off as far as yours. Mine was From 1.26.502.15 and To 1.26.502.12. So even though he says they have to match, They don't. Wondering if they problem lies with the Goog Edition ROM. Have you tried to clean install any of the AT&T ROM's? Curious if you are able to do that then it should let you Relock the bootloader and then Install the RUU. Hypothetically anyways.