Develop Bugs

[Q] upgraded hboot 1.28 now sdk wont recognise boot files?!

Hi Xda
I upgraded the hboot to 1.28 to try out arhd 12.0, Previous to the upgrade it was something like 0.48 or .98 etc running the latest paranoid android rom
I wanted to go back to the PA rom however when I restored my backup had process errors on start up so thought i needed to reflash the boot img, however for some reason even though adb can see my phone, when i look to flash the boot.img it cannot find it and says cannot load?!
I have tried searching and i have read a few things regards to the 1.28 bootloader.. but nothing specific to my issue, is this the reason why? could some please advise how to enable me to flash boot.img again
Many thanks
Michael

What CID does your phone have?
That hboot only works with very specific CIDS...

Hi peedub, thanks for the reply.
It is HTC_001 or 01. It was in the list of availble CIDs that the hboot works on.
As mentioned it has upgraded successfully and I have ARHD now installed, my issue is that I cannot either restore to previous ROM (Paranoid Android) via CWM due to when it does reboot after restore it comes up with android process failed or something similar.
When trying to reflash the boot.img for Paranoid Android to overcome these issues my ADB/Fastboot/SDK will not recognise the boot.img
however when i type in fastboot devices it recognises my phone.
Has anyone experienced this and can shed some light on a fix?
Many thanks again

I will get there said:
Hi Xda
I upgraded the hboot to 1.28 to try out arhd 12.0, Previous to the upgrade it was something like 0.48 or .98 etc running the latest paranoid android rom
I wanted to go back to the PA rom however when I restored my backup had process errors on start up so thought i needed to reflash the boot img, however for some reason even though adb can see my phone, when i look to flash the boot.img it cannot find it and says cannot load?!
I have tried searching and i have read a few things regards to the 1.28 bootloader.. but nothing specific to my issue, is this the reason why? could some please advise how to enable me to flash boot.img again
Many thanks
Michael
Click to expand...
Click to collapse
Code:
fastboot flash boot path/to/boot.img

Hi Matt
Thanks for your reply, could you explain your post a little more. Is that a diagnostic command to see if Adb is working or would that actually flash the boot.img?
Many thanks

You can't use AOSP/CM/AOKP based ROMs with 1.28 HBOOT and above. Most devs do warn you it's a one way street when upgrading to 1.28 in terms of flashing ROMs.
I'm not sure if running a RUU will work, or not, to downgrade the HBOOT.
Though you could try what matt95 suggested. His suggestion would just flash the boot.img for the ROM you're trying to use.

Thanks Harrysoon
Unfortunately It didnt stipulate this on ARHD as I would have reconsidered. I have seen a link posted somewhere to get around this.
I would have thought however that adb would have at least attempted to flash it and then failed but to not recognise it?
With regards to the path from Matt is that exactly as i type it?

If you can flash a boot.IMG it has to be a special one for 1.28 or 1.31. I'll find it for you
Sent from my HTC One X using xda app-developers app
---------- Post added at 03:43 PM ---------- Previous post was at 03:37 PM ----------
Go to the IceColdJelly page and scroll down till you see the OP specifically say that you can use this boot. IMG for 1.28 or 1.31. Then repack it for your ROM?
Sent from my HTC One X using xda app-developers app

Top man Tom, thank you!

Just checking on repacking a kernal, and I have seen the automated packer tool, however i do not understand how to tie it all in.
http://nibble.cc/repack/
could someone explain steps 2 - 5 with paranoid android being the ROM I want please

I will get there said:
Hi Matt
Thanks for your reply, could you explain your post a little more. Is that a diagnostic command to see if Adb is working or would that actually flash the boot.img?
Many thanks
Click to expand...
Click to collapse
the pc cannot load the file cause you don't tell him where the file is...so follow my command and you should be good

Bricked HTC One X - Can't replace Clockwork, flash Custom ROM

I have rooted my HTC One X by unlocking it from HTCDev, flashing custom recovery and installing custom ROM.
It was working fine for the first day, then it reboots by itself and never go back to life anymore. It is always stuck on the Android Boot Screen.
Device Details:
*** UNLOCKED ****
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.36.0000
CPLD-None
MI CROP-None
RADIO-5.1204.162.29
eMMC-bootmode:disabled
CPU-bootmode:disabled
HW Secure boot:enabled
MODEM PATH : OFF
Nov 16 2012, 18:32:39
Custom Recovery
ClockworkMod Recovery v5.8.4.0 (I downloaded this from download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img)
Custom ROM
tripndroid_endeavoru-ota-eng.noeri_003.zip
I have successfully installed recovery and rom by flashing them and as mentioned above i was able to use it for a day.
Now, Im trying to replace tripNDroid ROM with other ROM ARHD but i cant seem to flash a new ROM.
I copied the new zip file to the device by mounting the USB storage but when I Install from ClockWorkMod, I cant find the file under my sdcard.
I tried deleting all the contents of my sdcard, and copy the new zip file but when i install again from clockwork, the new file is not there and the old files which i deleted returns back.
So i thought clockworkmod is not working anymore, so i tried to flash a new recovery twrp, but after flashing successfully as stated in the terminal after fastboot flash recovery twrprecovery.img and tried to access recovery. clockworkmod still installed and twrp is not.
I cant find any solution from googling that is why i posted it here. hope someone could help me recovery my htc one x. Thanks.

The tripndroid rom has been pulled due to possible bricking of the phone ! My guess it has to do something with that mate !
And did you erase cache
Fastboot erase cache

s4m0k said:
I have rooted my HTC One X by unlocking it from HTCDev, flashing custom recovery and installing custom ROM.
It was working fine for the first day, then it reboots by itself and never go back to life anymore. It is always stuck on the Android Boot Screen.
Device Details:
*** UNLOCKED ****
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.36.0000
CPLD-None
MI CROP-None
RADIO-5.1204.162.29
eMMC-bootmode:disabled
CPU-bootmode:disabled
HW Secure boot:enabled
MODEM PATH : OFF
Nov 16 2012, 18:32:39
Custom Recovery
ClockworkMod Recovery v5.8.4.0 (I downloaded this from download2.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.4.0-endeavoru.img)
Custom ROM
tripndroid_endeavoru-ota-eng.noeri_003.zip
I have successfully installed recovery and rom by flashing them and as mentioned above i was able to use it for a day.
Now, Im trying to replace tripNDroid ROM with other ROM ARHD but i cant seem to flash a new ROM.
I copied the new zip file to the device by mounting the USB storage but when I Install from ClockWorkMod, I cant find the file under my sdcard.
I tried deleting all the contents of my sdcard, and copy the new zip file but when i install again from clockwork, the new file is not there and the old files which i deleted returns back.
So i thought clockworkmod is not working anymore, so i tried to flash a new recovery twrp, but after flashing successfully as stated in the terminal after fastboot flash recovery twrprecovery.img and tried to access recovery. clockworkmod still installed and twrp is not.
I cant find any solution from googling that is why i posted it here. hope someone could help me recovery my htc one x. Thanks.
Click to expand...
Click to collapse
Trip's endeavor unleashed v003 had an issue regarding the kernel or boot.img that can brick your device, that's why the downloadable zip had been removed by the mods. I wonder if how did you manage to get the zip file which has already been removed?
Unfortunately, you need to send your device to your service provider mate, no one has ever recover from that apx mode.
Sent from my HTC One X using xda app-developers app

flammin_ice1986 said:
Trip's endeavor unleashed v003 had an issue regarding the kernel or boot.img that can brick your device, that's why the downloadable zip had been removed by the mods. I wonder if how did you manage to get the zip file which has already been removed?
Unfortunately, you need to send your device to your service provider mate, no one has ever recover from that apx mode.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Oh no! I was able to download it from trip's thread, there was a link there, and that time, i was checking the coments and no negative comments thats why i flashed it.
Thanks for the reply, I think ill have to wait until someone manage to find a solution.

s4m0k said:
Oh no! I was able to download it from trip's thread, there was a link there, and that time, i was checking the coments and no negative comments thats why i flashed it.
Thanks for the reply, I think ill have to wait until someone manage to find a solution.
Click to expand...
Click to collapse
You should send it for repair if its still under warranty. You can't do anything with it right now, even trip broke his device with it.he send it for repair, and his provider replace his motherboard for free!
Make sure you won't be able to go into the bootloader. Just read the last few pages in his thread on how to do it.
Sent from my HTC One X using xda premium

case abooge
Mr Hofs said:
The tripndroid rom has been pulled due to possible bricking of the phone ! My guess it has to do something with that mate !
And did you erase cache
Fastboot erase cache
Click to expand...
Click to collapse
Yeah I did "fastboot erase cache", and additional info, when i try to do "fix permission" in clockworkmod my device reboots.

At the time the download links where up it was already bad, but there where no reports yet..... If you flashed the tripndroid from what stage on it doesn't matter. If you can't flash a custom recovery or get it to boot in anyway, the tripndroid bricked it
The solution is to get it repaired

Mr Hofs said:
At the time the download links where up it was already bad, but there where no reports yet..... If you flashed the tripndroid from what stage on it doesn't matter. If you can't flash a custom recovery or get it to boot in anyway, the tripndroid bricked it
The solution is to get it repaired
Click to expand...
Click to collapse
but why did it work fine for one day before going tits-up? surely it would have bricked straight away if it was a bad rom/kernel

From what i heard is that it did not bork right away.....it was from going from trips rom to another one . That's why it was pulled later on ! And it was a possible brick....so some did have bad luck

Welcome to my world bro.
---------- Post added at 10:17 PM ---------- Previous post was at 10:04 PM ----------
flammin_ice1986 said:
You should send it for repair if its still under warranty. You can't do anything with it right now, even trip broke his device with it.he send it for repair, and his provider replace his motherboard for free!
Make sure you won't be able to go into the bootloader. Just read the last few pages in his thread on how to do it.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
do you now which tread this is ?

Bloodbreed said:
Welcome to my world bro.
---------- Post added at 10:17 PM ---------- Previous post was at 10:04 PM ----------
do you now which tread this is ?
Click to expand...
Click to collapse
This is the thread where i got the download link before it was brought down.
http://forum.xda-developers.com/showthread.php?t=2092946
Searching now the information on how to make the device not to boot on the bootloader so that i could send it to HTC Service Center for a free repair.

s4m0k said:
This is the thread where i got the download link before it was brought down.
http://forum.xda-developers.com/showthread.php?t=2092946
Searching now the information on how to make the device not to boot on the bootloader so that i could send it to HTC Service Center for a free repair.
Click to expand...
Click to collapse
Thanxxx but search and read the whole post but didn t find something which explains how trip block phone in apx mode.

Bloodbreed said:
Thanxxx but search and read the whole post but didn t find something which explains how trip block phone in apx mode.
Click to expand...
Click to collapse
Dude! How's the status of your One X? did you manage to unbrick it?

Signature error 132 when flashing stock RUU

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

lost backup stock rom

I've been trying to install a custom rom on my hox and have had very little luck. I read that to install the CM10.1 rom I had to flash a new boot.img which I did successfully. when I tried to install the rom I got a different error than usual so I decided to just give up. I went ahead and did a factory reset from CWM and cleared the caches and then tried to restore my backup rom image. but when I did, it gave me an error "unable to mount sd". I was able to fix the SD problem but the method I used made me return to stock recovery and then install TWRP. This means I lost my backup of the stock rom.
I think I need to flash a stock boot.img over the one I tried to use for CM10.1 but I'm not sure.
hopefully someone can help. thanks.

erikxj said:
I've been trying to install a custom rom on my hox and have had very little luck. I read that to install the CM10.1 rom I had to flash a new boot.img which I did successfully. when I tried to install the rom I got a different error than usual so I decided to just give up. I went ahead and did a factory reset from CWM and cleared the caches and then tried to restore my backup rom image. but when I did, it gave me an error "unable to mount sd". I was able to fix the SD problem but the method I used made me return to stock recovery and then install TWRP. This means I lost my backup of the stock rom.
I think I need to flash a stock boot.img over the one I tried to use for CM10.1 but I'm not sure.
hopefully someone can help. thanks.
Click to expand...
Click to collapse
Can you tell us the exact steps you used to flash the boot image and ROM? What error did the ROM flashing give?

XyanumX said:
Can you tell us the exact steps you used to flash the boot image and ROM? What error did the ROM flashing give?
Click to expand...
Click to collapse
to flash the boot image, I extracted the rom zip file and removed the boot image. I went into the cmd and typed "flashboot flash boot boot.img".
to flash the rom, I moved the roms zip file onto the storage of the device (drag and drop) and then went into CWM and cleared the caches, did a factory reset, and then selected the zip file to be installed.
here is a picture of the error I got when I tried to install the rom: see attachment
the error is on the second line of code in the updater-script file. other attempts to install the rom gave me an error on the first line until I read that the first line had to be deleted for it to work on the hox.

May be an issue with CWM. Have a read here...... http://forum.xda-developers.com/showthread.php?t=2250785

XyanumX said:
May be an issue with CWM. Have a read here...... http://forum.xda-developers.com/showthread.php?t=2250785
Click to expand...
Click to collapse
CWM might be the reason the rom installation was aborted but I just want to return to stock. the stock rom is installed, I think the only problem is that the boot image is wrong. I searched around and can't find a stock boot image. I saw some tutorials on using RUU to do a restore but it seems a lot more complicated than just flashing the stock boot image. if you think RUU is the best method, please help me pick the correct RUU.

erikxj said:
CWM might be the reason the rom installation was aborted but I just want to return to stock. the stock rom is installed, I think the only problem is that the boot image is wrong. I searched around and can't find a stock boot image. I saw some tutorials on using RUU to do a restore but it seems a lot more complicated than just flashing the stock boot image. if you think RUU is the best method, please help me pick the correct RUU.
Click to expand...
Click to collapse
May be it's a bad download? Download the CM rom zip again and then try to flash it! Use the latest Philz touch recovery...
1. Flash boot.img and then fastboot erase cache
2. Go to recovery and wipe everything
3. flash the rom.zip/gapps.zip and reboot!
If you still want a RUU, then post the result of fastboot getvar version-main

vin4yak said:
May be it's a bad download? Download the CM rom zip again and then try to flash it! Use the latest Philz touch recovery...
1. Flash boot.img and then fastboot erase cache
2. Go to recovery and wipe everything
3. flash the rom.zip/gapps.zip and reboot!
If you still want a RUU, then post the result of fastboot getvar version-main
Click to expand...
Click to collapse
I think I'm just going to RUU. I google searched the hboot and radio numbers from my phone and found a thread where someone had the exact same numbers so I think it makes sense to use the same RUU. here is the info for my phone:
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
I tried using the 'fastboot getvar version-main' command it doesn't give me a number, it only says "version-main: " which is weird.
anyway the ruu I'm considering is called: "RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio_0.19as.32.09.11_2_10.105.32.25L_release_271865_signed"
will that work? I think I will forever brick my phone if I use the wrong one.

try fastboot getvar all

robchongke said:
try fastboot getvar all
Click to expand...
Click to collapse
....the version-main field is still blank

Aah! You have One XL... This is the international one x forum m8!
Don't flash / run anything from here! Go to your phone's forum and ask your question there...
All the best...
-Sent from my IceCold One X!

vin4yak said:
Aah! You have One XL... This is the international one x forum m8!
Don't flash / run anything from here! Go to your phone's forum and ask your question there...
All the best...
-Sent from my IceCold One X!
Click to expand...
Click to collapse
oh, this forum is labeled one x so I thought this was the right place...how can you tell it is the one XL?

erikxj said:
oh, this forum is labeled one x so I thought this was the right place...how can you tell it is the one XL?
Click to expand...
Click to collapse
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Click to expand...
Click to collapse
your phone say's evita. evita is for one xl while endeavor is for one x.

Flashing
Hi
Try connecting your HTC One X to your computer with an USB-cable and then access it, and go and look for a map called CWM, or ClockwordMod. Open it, and then open Backup.
Are you able to find it there? If not, please let me know.

cvv4HOX said:
Hi
Try connecting your HTC One X to your computer with an USB-cable and then access it, and go and look for a map called CWM, or ClockwordMod. Open it, and then open Backup.
Are you able to find it there? If not, please let me know.
Click to expand...
Click to collapse
And then....you are going to accompany him to the HTC one XL forum ?
He has no business here, flashing stuff from here may end in a proper bricked phone.

Oh, well I'm sorry. But it's his fault that he almost bricked his device bij placing this in the wrong Subtab ;p Don't blame on me!
We're losing the subject. Case closed!
Sent from my HTC One X using xda premium

cvv4HOX said:
Oh, well I'm sorry. But it's his fault that he almost bricked his device bij placing this in the wrong Subtab ;p Don't blame on me!
We're losing the subject. Case closed!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Lol you read that he needs to be in the HTC one xl forum and still want to help him here, so in a way ... Yes its your fault then. Redirecting him helps to avoid bricked phones......

[Q] HTC One X cm 10.1 install

Hey there, I am having issues trying to install CM 10.1 on my One X.
To start, I sort of messed up, hit the wrong button on accident and somehow wiped my entire OS from my phone and can't remember how to install one back. If someone has insight on how to bring the original android OS back, that would be helpful. Okay, now to real issue.
This is the issue I have trying to install CM 10.1 on my phone.
Bootloader is unlocked and the phone is rooted.
Once I flash the boot.img and go back into TWRP to install from SD card, it tells me
"assert failled: getprop("ro.product.device") == "endeavoru" 11 getprop("r
E:Error executing updater binary in zip '/sdcard/cm-10.1.0-endeavoru.zip
Error flashing zip '/sdcard/cm-10.1.0-endeavoru.zip'
Any help would be great!

Post the outcome of :
Fastboot getvar version-main
From there we can help better and have some critical info

Mr Hofs said:
Post the outcome of :
Fastboot getvar version-main
From there we can help better and have some critical info
Click to expand...
Click to collapse
It came up with 3.18.502.6

Did you make a nandroid backup of the stock rom ? And what does the top of your bootloader say, can you provide that info ?

Mr Hofs said:
Did you make a nandroid backup of the stock rom ? And what does the top of your bootloader say, can you provide that info ?
Click to expand...
Click to collapse
EVITA PVT SHIP S-ON RL
hboot 2.14.0000
radio 0.24p.32.09.06
openDSP-v34.1.0.45.1219
eMMC-boot
and I did, but for some reason everything was wiped from my sd card so I could not go back and restore my phone

Ah thought so, you are fishing in the wrong forum. You have to be in the HTC one XL (AT&T) forum. We can't help you here as all of this is for a different type hox !
Edit : but your phone can be fixed you can even make it s-off and flash anything you want. But for all that you have to go to your device specific forum

Mr Hofs said:
Ah thought so, you are fishing in the wrong forum. You have to be in the HTC one XL (AT&T) forum. We can't help you here as all of this is for a different type hox !
Click to expand...
Click to collapse
Lol, could you possibly link me the correct forum? I was sent here due to apparently being in the wrong forum?

The link to the correct forum is in the thread i linked here
http://forum.xda-developers.com/showthread.php?t=2356998