I'm going round in circles, trying to work out what I'm doing wrong.
I have hboot 0.43, and a fastboot getvar-main gives me 1.26.707.4
I presently am rooted etc and want to upgrade to JB. I have a nandroid backup of my stock rom. Hboot 0.43 means I cannot upgrade to JB hboot directly.
I restored the backup, flash the boot image from the backup, erase the cache and then flashed the stock recovery (1.29). Reboot. so far so good.
When the phone reboots it tells me there is a system update to 1.28.707.10 (31.82MB). I tell it to download and it says it will.
The problem is the speed. It's been going about 20 minutes so far and it has downloaded 0.15MB!! That's it.
I would try another method, but I can't find an RUU for my phone.
Any help appreciated.
Do fastboot oem readcid
Let us know what cid you have
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
Do fastboot oem readcid
Let us know what cid you have
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Sorry, forgot to add that.
I have HTC_044
liquidguru said:
Sorry, forgot to add that.
I have HTC_044
Click to expand...
Click to collapse
give me a couple of minutes, il just double check which is the correct one and drop it into my FTP server.
il PM you with connection details
OK i have sorted the file you need, details have been sent in a PM.
that is the Jellybean RUU for your CID.
make sure you have a well charged battery
relock your bootloader then run that on your PC and it will bump you all the way up to stock Jellybean
bagofcrap24 said:
give me a couple of minutes, il just double check which is the correct one and drop it into my FTP server.
il PM you with connection details
OK i have sorted the file you need, details have been sent in a PM.
that is the Jellybean RUU for your CID.
make sure you have a well charged battery
relock your bootloader then run that on your PC and it will bump you all the way up to stock Jellybean
Click to expand...
Click to collapse
Fantastic, thanks...it will take me a little while to download, but I'll let you know the results
sent from somewhere
liquidguru said:
Fantastic, thanks...it will take me a little while to download, but I'll let you know the results
sent from somewhere
Click to expand...
Click to collapse
No problem
wow thats some seriously slow internet, are you only on a 1MB line
bagofcrap24 said:
No problem
wow thats some seriously slow internet, are you only on a 1MB line
Click to expand...
Click to collapse
I live in the middle of nowhere in the middle of Indonesia. An exceptionally beautiful place and I'm pretty lucky to have any internet , so can't complain about the speed to much...at least it works.
sent from somewhere
Ok, no luck.
Relocked bootloader, no probs.
When I run the RUU it start ok, but when it gets to updating the signature I get:
ERROR [132]: SIGNATURE ERROR
The ROM Update Utility cannot update your Android phone
Please get the correct ROM Update Utility and try again
So, what to do next?
Did u update your bootloader? U have same cid as me... Your bootloader should show 1.36...then you can flash JB ruu...
Sent from my HTC One X using xda app-developers app
liquidguru said:
Ok, no luck.
Relocked bootloader, no probs.
When I run the RUU it start ok, but when it gets to updating the signature I get:
ERROR [132]: SIGNATURE ERROR
The ROM Update Utility cannot update your Android phone
Please get the correct ROM Update Utility and try again
So, what to do next?
Click to expand...
Click to collapse
could be a bad download, did notice a few disconnects as you was downloading it from me.
found another link here
http://androidfiles.org/ruu/securek...Radio_5.1204.162.29_release_296434_signed.exe
100% that its the correct RUU for your device
Code:
modelid: PJ4610000
cidnum: HTC__044
mainver: 3.14.707.24
btype:1
aareport:1
hbootpreupdate:12
RadioVer: 5.1204.162.29
erasebcid: 1
delcache: 1
---------- Post added at 02:46 PM ---------- Previous post was at 02:39 PM ----------
audahadi said:
Did u update your bootloader? U have same cid as me... Your bootloader should show 1.36...then you can flash JB ruu...
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
running the RUU on HBOOT 0.43 should automatically update the HBOOT to 1.36, but by the sounds of it. He isnt getting that far
usually the signature fail is either because
1. Wrong RUU
2. Bootloader Still Unlocked
3. Corrupt Download
I don't think there is anything wrong with the download. I use a download manager, so it can handle disconnects.
Hboot still says 0.43
I think the problem may be that I need to update to an intermediate hboot first. So I need an RUU for Hboot 1.26 or something. Then from there I can update my hboot
I'm going to try the 1.28.707.10 RUU
liquidguru said:
I don't think there is anything wrong with the download. I use a download manager, so it can handle disconnects.
Hboot still says 0.43
I think the problem may be that I need to update to an intermediate hboot first. So I need an RUU for Hboot 1.26 or something. Then from there I can update my hboot
I'm going to try the 1.28.707.10 RUU
Click to expand...
Click to collapse
im not too sure on that one.
the RUU updates your HBOOT for you
but if you want to try it there is a thread here
http://forum.xda-developers.com/showthread.php?t=1957376
which contains 1.36 HBOOT's which you can flash
lock bootloader
download the one for your phone from thread above (see your CID HTC__044 - x.xx.707.x - Asia WWE (World Wide English))
rename to firmware.zip
fastboot oem rebootRUU
fastboot flash zip firmware.zip
then you can try the RUU again
bagofcrap24 said:
could be a bad download, did notice a few disconnects as you was downloading it from me.
found another link here
http://androidfiles.org/ruu/securek...Radio_5.1204.162.29_release_296434_signed.exe
100% that its the correct RUU for your device
Code:
modelid: PJ4610000
cidnum: HTC__044
mainver: 3.14.707.24
btype:1
aareport:1
hbootpreupdate:12
RadioVer: 5.1204.162.29
erasebcid: 1
delcache: 1
---------- Post added at 02:46 PM ---------- Previous post was at 02:39 PM ----------
running the RUU on HBOOT 0.43 should automatically update the HBOOT to 1.36, but by the sounds of it. He isnt getting that far
usually the signature fail is either because
1. Wrong RUU
2. Bootloader Still Unlocked
3. Corrupt Download
Click to expand...
Click to collapse
Thanks..didn't notice that as before I only update bootloader then straight to custom rom..but worth a try
Sent from my HTC One X using xda app-developers app
bagofcrap24 said:
im not too sure on that one.
the RUU updates your HBOOT for you
but if you want to try it there is a thread here
http://forum.xda-developers.com/showthread.php?t=1957376
which contains 1.36 HBOOT's which you can flash
Click to expand...
Click to collapse
That did it i think! Success!! MIUI now booting.
Many thanks for all your help.
going from Hboot 0.43 to 1.36 directly
Hi people, im not too familiar with the hboot part therefore wanted to ask a few questions before trying:
1. is it possible to upgrade directly from 0.43 to 1.36 with the RUU for tmob-005 from the mentioned website or do i need to do it stagewise?
2. will it this process erase the data on my SDCARD?
a quick and accurate response shall be greatly appreciated!! :good:
usmanyo said:
Hi people, im not too familiar with the hboot part therefore wanted to ask a few questions before trying:
1. is it possible to upgrade directly from 0.43 to 1.36 with the RUU for tmob-005 from the mentioned website or do i need to do it stagewise?
2. will it this process erase the data on my SDCARD?
a quick and accurate response shall be greatly appreciated!! :good:
Click to expand...
Click to collapse
1. no
2. not sure but go with the worst case scenario and back it up before !
Mr Hofs said:
1. no
2. not sure but go with the worst case scenario and back it up before !
Click to expand...
Click to collapse
at 1. you said "no", as in it cant be done directly?
No it cant be done directly .... You got that right, the step to a JB hboot s to high !
In your case (from such a low hboot) it need to be done in steps
And about the direct firmware flash im not certain if it works directly but i would not risk it. There is for sure a RUU that fits your hboot. So I would go for safe and install a ruu to get back to stock and then officially ota all the way up to JB !
usmanyo said:
Hi people, im not too familiar with the hboot part therefore wanted to ask a few questions before trying:
1. is it possible to upgrade directly from 0.43 to 1.36 with the RUU for tmob-005 from the mentioned website or do i need to do it stagewise?
2. will it this process erase the data on my SDCARD?
a quick and accurate response shall be greatly appreciated!! :good:
Click to expand...
Click to collapse
Just flash the correct hboot from the post that bagofcrap24 linked to : http://forum.xda-developers.com/show....php?t=1957376
It doesn't erase your data and is a lot easier than trying to find the correct RUU and flashing that.
liquidguru said:
Just flash the correct hboot from the post that bagofcrap24 linked to : http://forum.xda-developers.com/show....php?t=1957376
It doesn't erase your data and is a lot easier than trying to find the correct RUU and flashing that.
Click to expand...
Click to collapse
Your opinion depends completely how familiar the person is with fastboot and commands :thumbup:
And btw, for such a low hboot there is definitely a RUU available
Related
Hi Everyone,
I have become slightly frustrated as I seem to be unable to flash the stock rom back onto my HTC One X. I have a CID of HTC__001 which seems to be perfect and I am with Orange Uk. I have downloaded the correct RUU for the specific radio I have (2.1204.135.20) and when I run the exe in windows. It starts to work and then says my USB is not connected.
Previously I have been rooted and have flashed the recovery image, which does mean I am connected via use and in fastboot mode. Not sure what is causing this issue. If anyone could provide any assistance that would be fantastic.
Thanks
Andy
Andy,
Ruus need stock recovery. Are you back on stock recovery? Also, phone must be booted up into rom and respond to adb commands such as
Adb devices
This should list your devices serial number as connected. If you see that, then try running the ruu.
Sent from my HTC One X using xda premium
1. If you have HTC__001 then download the 2.17.401.2 RUU from here - http://d-h.st/HoB
2. Relock your bootloader!!
3. Boot the phone into fastboot and connect to the PC
4. Run the RUU
That's it, no stock recovery required
Thanks
Thanks for both of your replies. I have since managed to install the sense jelly bean roms from Insert Coin and also Maximum, realised that I did not need to install the RUU, just need to flash the boot.img. All is now great. The RUU that you posted was the one i tried but failed :s Its ok now though as now I am unable to return to ICS roms
EddyOS said:
1. If you have HTC__001 then download the 2.17.401.2 RUU from here - http://d-h.st/HoB
2. Relock your bootloader!!
3. Boot the phone into fastboot and connect to the PC
4. Run the RUU
That's it, no stock recovery required
Click to expand...
Click to collapse
Hello
Im on the same situation, but i cant get the RUU to install. I flashed the stock recovery, i relock the bootloader, but im always getting Error 155 Im with full batery, i run as administrator but i cant get thr RUU to flash. Any idea? Thanks in advance:fingers-crossed:
DropePT said:
Hello
Im on the same situation, but i cant get the RUU to install. I flashed the stock recovery, i relock the bootloader, but im always getting Error 155 Im with full batery, i run as administrator but i cant get thr RUU to flash. Any idea? Thanks in advance:fingers-crossed:
Click to expand...
Click to collapse
How far does the RUU installer get? I had problems on the weekend where it got to the install shield then stopped. This was resolved by turning off norton and running as administrator.
shadwell_lad said:
How far does the RUU installer get? I had problems on the weekend where it got to the install shield then stopped. This was resolved by turning off norton and running as administrator.
Click to expand...
Click to collapse
I only get into the black screen with HTC logo:silly: I have Microsoft Security Essentials, already flashed RUU without problems, this was the 1st time. Meanwhile, flashed now with football rom, Revolution without any problems. Just wonder if when OTA will be available, if i can install it
thanks so much guys, this helped me a lot!
Help needed!
Hi guys. I'm very new to this so forgive me if I seem a bit stupid at times. I've been reading a lot and trying to learn things about the phone but I've got myself a bit stuck.
I have a HOX with the following;
*** relocked ***
CID HTC__001
Hboot 1.12.0000
radio-2.1204.135.20
Everything was stock, I unlocked and rooted. All went well, everything worked fine. Didn't install any ROM's. Installed CWM. Then JB was released so I unrooted and relocked and flashed stock recovery.
The phone now has;
Android 4.0.4
HTC Sense 4.1
Software 2.17.401.2
API 4.23
HTC Extension 403_1_GA_20
Everything works. I can boot the phone and everything works as it should. The only issue I can see is that it won't boot into recovery. I get the green arrows, press power and up volume, some errors are reported on the screen - Cannot find /cache/recovery/command and Failed to open loopdevice, no such file or directory. The phone then restarts and boots the OS.
My question is, what should I do next to be able to receive the OTA JB update? I assume I'll need to do some combination of flashing the boot.img and recovery.img but I'm unsure what the process is, or even if my assumptions are correct? Help??
EDIT 1 : I found this. http://forum.xda-developers.com/showthread.php?t=1193540
I think it's what I need. I just need to read some more and find out what ROM I need to download. Can anyone advise if this is in fact what I need to do and what ROM I should be looking for?
EDIT 2 : I also found this RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
Can anyone confirm for me this is the process and the ROM I need to return to stock before I go ahead and run this?
In advance, thank you for any help/advice that's offered.
The RUU should work.
That guide is for a different phone. Check the stickies in the dev section of this forum.
BenPope said:
The RUU should work.
That guide is for a different phone. Check the stickies in the dev section of this forum.
Click to expand...
Click to collapse
Thanks for the reply BenPope. Yea, I saw the guide was for a different device, but the steps are virtually identical. I went ahead and ran the RUU. Everything flashed OK, no errors, no issues. Re-locked the bootloader. Still can't run recovery tho. Still getting the same errors. As I understand it I won't be able to get OTA updates installed if Recovery isn't working correctly. Have I got this right? Any ideas?
You're saying everything in the wrong order. Please be more clear.
To run the RUU, your hboot needs to be locked. If after the RUU you can't access recovery something went wrong and the RUU failed. What errors are you getting?
g12__ said:
EDIT 2 : I also found this RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
Can anyone confirm for me this is the process and the ROM I need to return to stock before I go ahead and run this?
In advance, thank you for any help/advice that's offered.
Click to expand...
Click to collapse
Take boot_signed.img and recovery_signed and Rom.zip from the RUU. Boot to fastboot, flash boot_signed.img and recovery.img . Boot to recovery and flash the rom.zip.
Sent from my HTC One X using xda premium
Your problem was due to flashing stock recovery AFTER relock.
Try this:
1. Unlock again.
2. Fastboot flash stock recovery.
3. Then, relock.
4. Boot your phone.
Try to update then.
Sent from my HTC One X using XDA Premium HD app
EddyOS said:
1. If you have HTC__001 then download the 2.17.401.2 RUU from here - http://d-h.st/HoB
2. Relock your bootloader!!
3. Boot the phone into fastboot and connect to the PC
4. Run the RUU
That's it, no stock recovery required
Click to expand...
Click to collapse
is this RUU same for cid_032????????????????
yode said:
is this RUU same for cid_032????????????????
Click to expand...
Click to collapse
2.17.401.2 RUU is for :
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__M27
cidnum: HTC__032
cidnum: HTC__016
cidnum: HTC__J15
I have a stupid question.
I've flashed my device with the official European JB RUU 3.14.401.27 (if i'm correct).
I've relocked my bootloader etc, and RUU update is done.
But the bootloader said it's **RELOCKED**.
Is there a way to remove that text without SuperCID?
And will it be a problem to send my device back to HTC repair center? (for the G-sensor.. )
Thanks in advance!
****head said:
I have a stupid question.
I've flashed my device with the official European JB RUU 3.14.401.27 (if i'm correct).
I've relocked my bootloader etc, and RUU update is done.
But the bootloader said it's **RELOCKED**.
Is there a way to remove that text without SuperCID?
And will it be a problem to send my device back to HTC repair center? (for the G-sensor.. )
Thanks in advance!
Click to expand...
Click to collapse
It's impossible to change or remove that text .
You will have to pay for repair unless you are extremely lucky.
Sent from my HTC One X
TToivanen said:
It's impossible to change or remove that text .
You will have to pay for repair unless you are extremely lucky.
Sent from my HTC One X
Click to expand...
Click to collapse
sigh ....
thanks for the info.
do you know how much they will ask for the repair?
****head said:
do you know how much they will ask for the repair?
Click to expand...
Click to collapse
No but there is a slight chance it could be covered by warranty since it is a hardware fault. Sorry for your loss man.
Sent from my HTC One X
Hi there,
now I really need your help,
I read the thread
http://forum.xda-developers.com/showthread.php?t=1859714
But fastboot returns
version-main: 1.28.207.9
I can`t find a RUU for that?
So is it right that if I don`t have a nandroid-backup, I can`t return to stock at the moment?
What's your cid ? Is it a branded or a unbranded device ?
Do fastboot command
Fastboot oem readcid
Mr Hofs said:
What's your cid ? Is it a branded or a unbranded device ?
Do fastboot command
Fastboot oem readcid
Click to expand...
Click to collapse
Thank you for your quick reply.
Its an unbrandend device.
Here is the result:
(bootloader) DEBUG: cid: O2___102
OKAY [ 0.140s]
finished. total time: 0.140s
Thank you
Its a branded device ! Your cid starts with O2
---------- Post added at 02:14 PM ---------- Previous post was at 02:03 PM ----------
What you can try to do is to flash a nandroid backup matching your cid number, the nandroid will have a higher software number so it will start with 2.17.207.**. Do a full wipe and restore that nandroid with the boot.img and after that you flash back the 2.17 stock recovery and you are back on stock to obtain the JB update !
Check here http://forum.xda-developers.com/showthread.php?t=1975140
Mr Hofs said:
Its a branded device ! Your cid starts with O2
---------- Post added at 02:14 PM ---------- Previous post was at 02:03 PM ----------
What you can try to do is to flash a nandroid backup matching your cid number, the nandroid will have a higher software number so it will start with 2.17.207.**. Do a full wipe and restore that nandroid with the boot.img and after that you flash back the 2.17 stock recovery and you are back on stock to obtain the JB update !
Check here http://forum.xda-developers.com/showthread.php?t=1975140
Click to expand...
Click to collapse
I will try this now.
Reporting back later on.
Thank you so much!
phindr0id said:
I will try this now.
Reporting back later on.
Thank you so much!
Click to expand...
Click to collapse
Ok, there is one existing.
Flashing now.
What I am wondering about, I bought the device without a contract, so it should be unbranded.
This device is my girlfriends, I bought the same device in another store and my cid is HTC__102...
Strange ? HTC__102 is unbranded yes, O2__102 is from a carrier if i'm not mistaken ! Otherwise it also should be HTC__102
You bought it from a store ? Or second hand ? And you are running it with the O2 carrier ?
Mr Hofs said:
Strange ? HTC__102 is unbranded yes, O2__102 is from a carrier if i'm not mistaken ! Otherwise it also should be HTC__102
You bought it from a store ? Or second hand ? And you are running it with the O2 carrier ?
Click to expand...
Click to collapse
I bought it from a small store, yes. New, not second hand.
And its running with the O2 carrier... strange
phindr0id said:
I bought it from a small store, yes. New, not second hand.
And its running with the O2 carrier... strange
Click to expand...
Click to collapse
Ok,
I am back on stock now
Thanks for that!!
But I am sure it was an unbranded device...
Could it be that the CID is modified by flashing a ROM?
phindr0id said:
Ok,
I am back on stock now
Thanks for that!!
But I am sure it was an unbranded device...
Could it be that the CID is modified by flashing a ROM?
Click to expand...
Click to collapse
Well actually not that i know of ! The fastboot command gives the real cid from the phone and not a software generated cid number !
Now you are on stock 2.17 software .... if you flash back the 2.17 stock recovery you are also ready to update to JB when the provider rolls it out !
This is the stock 2.17 recovery
http://db.tt/U5CK4noo
:thumbup:
Mr Hofs said:
Well actually not that i know of ! The fastboot command gives the real cid from the phone and not a software generated cid number !
Now you are on stock 2.17 software .... if you flash back the 2.17 stock recovery you are also ready to update to JB when the provider rolls it out !
This is the stock 2.17 recovery
http://db.tt/U5CK4noo
:thumbup:
Click to expand...
Click to collapse
So,
everything seems to be fine now.
I flashed the stock-recovery, however, o2 did not release an update until now.
Though I still can`t beliebe that its a branded o2 device.
Thank you again for your help Mr Hofs :good:
I hope some other people find this thread useful, too.
Hello friends, I really don't know if this is the correct thread but I will give it a try ...I bought an HTC ONE X and my problem is that I took the phone from a friend of mine and it had ARHD installed already (with hboot 1.28.0000 and 3.14.401.600 and HTC__01).
I managed to flash hboot 1.39.0000 and I download RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radi o_5.1204.162.29_release_298897_signed.exe !! I am trying to flash the stock rom as you understand but whatever I did I get error in the update process of the RUU (error 55, then 155 I think). My bootloader is relocked right now and I really don't know what to do. I have search a lot of topics, I am reading from yesterday but I can't make the phone work. Should I flash something else (like boot.img) ??
Many thanks for your help.
brandon7gr said:
Hello friends, I really don't know if this is the correct thread but I will give it a try ...I bought an HTC ONE X and my problem is that I took the phone from a friend of mine and it had ARHD installed already (with hboot 1.28.0000 and 3.14.401.600 and HTC__01).
I managed to flash hboot 1.39.0000 and I download RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radi o_5.1204.162.29_release_298897_signed.exe !! I am trying to flash the stock rom as you understand but whatever I did I get error in the update process of the RUU (error 55, then 155 I think). My bootloader is relocked right now and I really don't know what to do. I have search a lot of topics, I am reading from yesterday but I can't make the phone work. Should I flash something else (like boot.img) ??
Many thanks for your help.
Click to expand...
Click to collapse
You updated the hboot to 1.39 and i think the ruu comes with hboot 1.36 so that's a downgrade to the hboot and that is not possible ! I think that's why you get an error !
You should unlock the bootloader again and flash the custom recovery and then flash a custom rom......or a stock like custom rom....
where can i obtain a nandroid backup of o2_002 2.1.207.x to flash? I am currently having problems with my nandroid backup
davitox87 said:
where can i obtain a nandroid backup of o2_002 2.1.207.x to flash? I am currently having problems with my nandroid backup
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1975140
Sent from my HTC One X using xda app-developers app
treebill said:
http://forum.xda-developers.com/showthread.php?t=1975140
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
will the o2_001 nandroid work? I am searching for the o2_002 and did not see it in the thread.
EDIT: Found one here
http://www.putlocker.com/public/XEv...4ZOXtZ2v6XEekZuP2ZtUZJH5vnx9aKNMNJHYcoIMkTue9
Hi, first of all apologies for posting a thread similar to a few that have already been asked, however I am unable to find an answer and could desperately do with some help here and would be extremely grateful for anyone's time.
I need to go back to stock RUU however keep getting Error 132 - Signature error.
Yes, I have been running the RUU as administrator and keeping the phone in fastboot when running the RUU, and I have been relocking the bootloader first with fastboot oem lock. Details are below and again, thank you for your time. Appreciate it.
HBoot: 1.36
RADIO-5.1204.164D.30
CID: VODAP001
version-main: 3.14.161.27
Attempted RUU: RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed
RUU Error [132]: Signature error.
If there are no reasonable explanations to this the alternative is to flash a rom with the exact properties of the stock RUU's and hope the buyer won't notice! Shouldn't have left this so last minute as things always haven't seemed as simple as they should be with this whole rooting stuff!
Edit: I also have no backups so am unable to use that method as an alternative.
You're flashing the wrong RUU.
Find the RUU for 3.1.4.161.27 and then run it.
Sent from my HTC ViperX
Give this a go !
Download this nandroid backup and place it in the right folder on the sdcard
http://bugsylawson.com/index.php/files/file/211-cwm-nandroid-backup-cid-vodap001-2171614/
Sdcard\clockworkmod\backup\time and date folder\backup files
Flash the boot.img from that nandroid backup, perform a full wipe in the recovery and restore the nandroid backup. After that you flash back the stock recovery (2.17).
http://db.tt/U5CK4noo
Boot up the phone, check if it all works and go into the software update menu and update to JB again with official OTA.
athulele said:
You're flashing the wrong RUU.
Find the RUU for 3.1.4.161.27 and then run it.
Sent from my HTC ViperX[/QUOTE
To me the same problem occurs to me when wanting to update my HTC One M9 with the RUU 4.23.617.1 to pass to Nougat
Do you know what I can do?
My device is locked and S-On :llorando:
---------- Post added at 07:20 PM ---------- Previous post was at 07:19 PM ----------
athulele said:
You're flashing the wrong RUU.
Find the RUU for 3.1.4.161.27 and then run it.
Sent from my HTC ViperX
Click to expand...
Click to collapse
To me the same problem occurs to me when wanting to update my HTC One M9 with the RUU 4.23.617.1 to pass to Nougat
Do you know what I can do?
My device is locked and S-On
Click to expand...
Click to collapse
zilzavala said:
To me the same problem occurs to me when wanting to update my HTC One M9 with the RUU 4.23.617.1 to pass to Nougat
Do you know what I can do?
My device is locked and S-On
Click to expand...
Click to collapse
If your device is locked, then you probably do not have the "unlocked developer edition" the 617 part means it's for the unlocked developer edition. try downloading the ROM for your phone version / carrier.
If you ARE dev edition:
I'm having the same problem. I actually have the unlocked developer edition, I'm S-off and Super Cid.. yet.. 4.23.617.1 RUU throws signature error. Tried from multiple machines, and multiple downloads direct form HTC. I think the current image at HTC is corrupt. This is not the first time this has happened, and I bet they never fix it.
I can flash previous 617 RUUs just fine.
im having the same problem(132: signature error) triying to flash 4.27.502.7(nougat) from 3.38.502.41(marshmallow) on my at&t m9...:crying:
I have this problem too
XsaucerX said:
im having the same problem(132: signature error) triying to flash 4.27.502.7(nougat) from 3.38.502.41(marshmallow) on my at&t m9...:crying:
Click to expand...
Click to collapse
athulele said:
You're flashing the wrong RUU.
Find the RUU for 3.1.4.161.27 and then run it.
Sent from my HTC ViperX
Click to expand...
Click to collapse
bro i have the same problem pls help me.
my phone details
htc one m9
htc_himauhl pvt s-off
cid-11111111
LK-1.0.0.0000
RADIO-01.01_U11440792_97.00.51203G_F
openDsp-15.6.1.00522.8994._1026
os-3.35.401.32
oct 12 2016,17:37:19(671758)
bro pls help
My hox is still on ics. Cid__102 (germany) and i did not recieve any ota updates.
How can i update it to JB using the ruu?
Sent from my HTC One X
give the main version-number to be sure : Fastboot getvar version-main
My device cid is htc__102 (germany) while the version of the software is x.xx.415.x (middle east) weird.....!
I tried flashing
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed
and gave me error 132
Give the output of
fastboot getvar version-main
Sent from my HTC One X using xda app-developers app
1.29.415.11
Relock the bootloader and keep the phone in the relocked bootloader and then run this ruu with admin rights
http://bugsylawson.com/files/file/1...52-radio-2120413520-release-275980-signedexe/
After the ruu you update with the official ota's from within the phone (update menu)
Mr Hofs said:
Relock the bootloader and keep the phone in the relocked bootloader and then run this ruu with admin rights
http://bugsylawson.com/files/file/1...52-radio-2120413520-release-275980-signedexe/
After the ruu you update with the official ota's from within the phone (update menu)
Click to expand...
Click to collapse
Thank you I will try it now
But how do i re-lock the bootloader when it says it is locked?
Full locked ? As in never unlocked,rooted, flashed ???
Then just run the ruu
Mr Hofs said:
Full locked ? As in never unlocked,rooted, flashed ???
Then just run the ruu
Click to expand...
Click to collapse
yes, never unlocked or flashed any custom rom
When i tried flashing the ruu u provided i get error 131
You selected the ruu by clicking on it via the right mouse button and selecting :
Run as administrator ?
And what does this return ?
Fastboot oem readcid
Post the whole outcome please
Right click run as administrator
The program just started
Fastboot oem readcid
HTC__102
Sent from my HTC One X+
HTC__102 should be software like
*.**.401.* not 415
Check your bootloader, what does it say ?
A : LOCKED
B : RELOCKED
C : UNLOCKED
D : non of the above
Mr Hofs said:
HTC__102 should be software like
*.**.401.* not 415
Click to expand...
Click to collapse
I know is very strange. I think it should be HTC__J15. Is there any way to change the cid?
Sent from my HTC One X+
qaliza said:
I know is very strange. I think it should be HTC__J15. Is there any way to change the cid?
Sent from my HTC One X+
Click to expand...
Click to collapse
Certainly not without s-off ! Can you give a screenshot of the bootloader ?
Mr Hofs said:
Certainly not without s-off ! Can you give a screenshot of the bootloader ?
Click to expand...
Click to collapse
Sent from my HTC One X+
Something fishy going on ! The 415 ruu didn't work i assume. You could try the 2.17.401 ruu !
You tried the 3.14 ruu and that failed because of the low hboot you have now. It can't jump from that low to that high one.
Mr Hofs said:
Something fishy going on ! The 415 ruu didn't work i assume. You could try the 2.17.401 ruu !
You tried the 3.14 ruu and that failed because of the low hboot you have now. It can't jump from that low to that high one.
Click to expand...
Click to collapse
I will try the 2.17.401 ruu next weekend when my brother returns coz its his phone. Thank you so much for ur help.
Sent from my HTC One X+
Back again
Unfortunately the 2.17.401 ruu did not work as well.
Here is what I'm going to do and would like your guidance..
1- flash firmware package for JB htc__102 from here
2- unlock bootoader from htc dev
3- flash custom recovery
4- flash stock jelly bean rom (odexed) and boot.img provided by mike1986.from here
5- flash stock recovery back again and relock bootloader to be able to receive ota updates
Will this work?
You can try. If the firmware is wrong it won't be flashed anyway. But yeah it is an option to try. But i think it will fail because the 2.17 ruu should have updated the hboot too. A ruu or ota file contains the firmware package that you will try to flash seperatly with command.
Give it a shot. But the info your phone is giving by the cid and main commands are not in line with what they should be !
Mr Hofs said:
You can try. If the firmware is wrong it won't be flashed anyway. But yeah it is an option to try. But i think it will fail because the 2.17 ruu should have updated the hboot too. A ruu or ota file contains the firmware package that you will try to flash seperatly with command.
Give it a shot. But the info your phone is giving by the cid and main commands are not in line with what they should be !
Click to expand...
Click to collapse
Thank you for your help. I'll give it a try and see how it goes..
my htc one m8 stuck at the bootloader after im trying to flash the stock ruu. right now i cant even go to the recovery. how can i fix this and get it running? before this its run on cyanogenmod 12.1 . i cannot found the right ruu for my htc one m8. please someone help me.
My bootloader is relock cause I'm trying to flash it back to stock. And my software status said modified. My HTC one m8 is also S-ON. How can I start from that?
fitsuhaimi said:
my htc one m8 stuck at the bootloader after im trying to flash the stock ruu. right now i cant even go to the recovery. how can i fix this and get it running? before this its run on cyanogenmod 12.1 . i cannot found the right ruu for my htc one m8. please someone help me.
Click to expand...
Click to collapse
Do you have unlocked bootloader? If you have, just install adb and fastboot drivers, then plug m8 into pc and enter fastboot mode. Watch from 2:00 https://www.youtube.com/watch?v=9HWj_1KHbuY and do the same
after you do all that, just put some rom into sdcard or usb, and flash it.
fitsuhaimi said:
my htc one m8 stuck at the bootloader after im trying to flash the stock ruu. right now i cant even go to the recovery. how can i fix this and get it running? before this its run on cyanogenmod 12.1 . i cannot found the right ruu for my htc one m8. please someone help me.
My bootloader is relock cause I'm trying to flash it back to stock. And my software status said modified. My HTC one m8 is also S-ON. How can I start from that?
Click to expand...
Click to collapse
You can't find the proper RUU? Did you try to run an RUU not meant for your device? You should just get errors and the process should halt.
What does it say next to "OS" in your bootloader menu? That will tell you your current firmware version. Does it have two different versions with the newer one in red? If so you need to run the RUU again. The first run just updated the hboot.
There's nothing on the os.
Crying
fitsuhaimi said:
There's nothing on the os.
Click to expand...
Click to collapse
Post the results of fastboot getvar all. Edit out your IMEI and serial# from it first. That is private information you should never post on a public forum.
I already PM you the pictures of my phone.
Why can't you write your
hboot no.
version-main no.
CID
MID
here .. so people can help you ?
If you have those data .. check the thread linked in my signature to see whether there is one backup for you or not.
Can't wait for your answer .. need to sleep now .. good luck & good night
ckpv5 said:
Why can't you write your
hboot no.
version-main no.
CID
MID
here .. so people can help you ?
If you have those data .. check the thread linked in my signature to see whether there is one backup for you or not.
Can't wait for your answer .. need to sleep now .. good luck & good night
Click to expand...
Click to collapse
Hboot 3.19
Version-main blank (of course same as OS in bootloader) You need to update your recovery @fitsuhaimi
CID HTC__621
MID 0P6B11000
He has the M8x. 709 firmware. No RUU for that version AFAIK.
---------- Post added at 02:49 PM ---------- Previous post was at 02:36 PM ----------
fitsuhaimi said:
I already PM you the pictures of my phone.
Click to expand...
Click to collapse
Go to @ckpv5's thread. Link here.
You'll need the backup that is 4.24.709.2 (judging from your baseband you are on Lollipop). The 709 part is crucial! That is for your version of M8 and you can't flash a backup (or RUU, or firmware) made for other versions.
Can you tech me step by step what i should do.
im not that good at this kinda thing but im really interested in learning. And also it can save my phone.
xunholyx said:
Hboot 3.19
Version-main blank (of course same as OS in bootloader) You need to update your recovery @fitsuhaimi
CID HTC__621
MID 0P6B11000
He has the M8x. 709 firmware. No RUU for that version AFAIK.
---------- Post added at 02:49 PM ---------- Previous post was at 02:36 PM ----------
Go to @ckpv5's thread. Link here.
You'll need the backup that is 4.24.709.2 (judging from your baseband you are on Lollipop). The 709 part is crucial! That is for your version of M8 and you can't flash a backup (or RUU, or firmware) made for other versions.
Click to expand...
Click to collapse
What's the baseband no. ?
He may need 4.16.709.9 if the baseband is lower than 1.26
ckpv5 said:
what's the baseband no. ?
He may need 4.16.709.9 if the baseband is lower than 1.26
Click to expand...
Click to collapse
1.26.21331147a1.16g
So what should i do now? Please help me :crying::crying::crying:
fitsuhaimi said:
So what should i do now? Please help me :crying::crying::crying:
Click to expand...
Click to collapse
First thing you need to do is update your recovery to TWRP 2.8.7.0.
Then go to the thread I linked you to, and follow the instructions in post #1 (skip the first step~update recovery). You'll need the 4.24.709.2 backup that is in post #3.
You can stop at step 9. You just need the ROM backup and not the stock recovery. After step 9 just reboot.