Develop Bugs

update JB OTA

Any who can make a simple instruction for HowTo install JB OTA 3.14.401.27 on One X?
Tryed bu twhen reboot I stuck in Beats Audio picture. (installed JB boot.img first)
Many ask same thing this days so an instruction would save many questions
Thanks in advance

Here are all guides and tools
http://forum.xda-developers.com/showthread.php?t=1832891
:thumbup:
---------- Post added at 04:06 PM ---------- Previous post was at 03:45 PM ----------
You can't install the JB ota just like that, tell.me what hboot you are on. I think you have to go to stock ics and from there update the hboot with the official ota from HTC ?

Thanks for this info

audiavant said:
Thanks for this info
Click to expand...
Click to collapse
No problem, hoped it helped you !

On point 6 below, shall that recovery.img be from v.3.14 (JB) OTA? (No way back then if somthing went wrong)
1. Relock bootloader: - fasboot oem lock
2. Boot device
3. From command prompt enter: -adb reboot oem-78
4. Flash firmware: - fastboot flash zip nameoffirmwarefile.zip
5. Unlock bootloader again using your original unlock code: - fastboot flash unlocktoken
Unlock_code.bin
6. Flash custom recovery: - fastboot flash recovery nameofrecoveryfile.img
7. Flash boot.img from rom zip: - fastboot flash boot boot.img
8. Flash rom zip through recovery
9. Reboot and enjoy

audiavant said:
On point 6 below, shall that recovery.img be from v.3.14 (JB) OTA? (No way back then if somthing went wrong)
1. Relock bootloader: - fasboot oem lock
2. Boot device
3. From command prompt enter: -adb reboot oem-78
4. Flash firmware: - fastboot flash zip nameoffirmwarefile.zip
5. Unlock bootloader again using your original unlock code: - fastboot flash unlocktoken
Unlock_code.bin
6. Flash custom recovery: - fastboot flash recovery nameofrecoveryfile.img
7. Flash boot.img from rom zip: - fastboot flash boot boot.img
8. Flash rom zip through recovery
9. Reboot and enjoy
Click to expand...
Click to collapse
This is to upgrade the hboot to be able to run a JB rom......this is not for the JB ota
If you want the official JB ota you can go back to stock 100&
Stock rom
Stock kernel
Stock recovery
Or you can run the right RUU
If you want to upgrade the hboot unofficial then use a tool if your CID is in the list of compatible hboots

After step 1 to 7 (to prpare and update hboot) then step 8 on this shuld be to install JB or have I misunderstand?
I am on HTC_Europe_2.17.401.2-1.29.401.12_release_274955b7 and tryed to update but stuck at Beats audio boot image because I not upgraded hboot I think (flashed boot.img only).

audiavant said:
On point 6 below, shall that recovery.img be from v.3.14 (JB) OTA? (No way back then if somthing went wrong)
1. Relock bootloader: - fasboot oem lock
2. Boot device
3. From command prompt enter: -adb reboot oem-78
4. Flash firmware: - fastboot flash zip nameoffirmwarefile.zip
5. Unlock bootloader again using your original unlock code: - fastboot flash unlocktoken
Unlock_code.bin
6. Flash custom recovery: - fastboot flash recovery nameofrecoveryfile.img
7. Flash boot.img from rom zip: - fastboot flash boot boot.img
8. Flash rom zip through recovery
9. Reboot and enjoy
Click to expand...
Click to collapse
Step 1 to 4 is to upgrade the hboot the unofficial way
Step 5 is to open the bootloader so you can flash the custom recovery (cwm 5.4.8.0) back to enable you to flash custom roms
Step 6 is flash the custom recovery like above
Step 7 is to flash the kernel of the new JB custom rom you want to flash
Step 8 is to flash the rom.zip in the custom recovery you flashed in step 6
But what are you trying to do, go back to stock or flash the hboot unofficial ? I think we are misunderstanding something here

I just want to update from original v.2.17 and install v.3.14 JB OTA on a rooted One X

audiavant said:
I just want to iupate from original v.2.17 and install v.3.14 JB OTA on a rooted One X
Click to expand...
Click to collapse
Oke i understand that, but do you want to do it official by your carrier/HTC or do you want to do it the unofficial way
I say run the RUU with the bootloader RELOCKED and wait for the official update

Do it official by carrier/HTC

RUU is not out yet so the unofficial way then (Have downloaded OTA)

audiavant said:
Do it official by carrier/HTC
Click to expand...
Click to collapse
Do you have the ruu ? Otherwise you can download is it here
http://www.htcruu.com/?dir=Endeavor
Put the phone in fastboot USB mode and relock the bootloader restart the bootloader and leave it in bootloader fastboot USB mode then start the ruu.exe from pc with admin rights and it flashes the phone back to stock.
Before doing this backup all you need from the sdcard because everything might be gone after doing this !

Will it work to update OTA directly (without run RUU first) if I lock boot loader, flash boot.img and hboot.img first?

audiavant said:
Will it work to update OTA directly (without run RUU first) if I lock boot loader, flash boot.img and hboot.img first?
Click to expand...
Click to collapse
No
Didn't you make a nandroid backup of the old original rom ?
You have to flash the ota coming from a full 100% stock 2.17 based software phone !

Do you know what more I need to do to get it working that way?

Do this command with the phone in fastboot USB mode
Fastboot getvar version-main
And post result here please

MarcelHofs said:
No
Didn't you make a nandroid backup of the old original rom ? Not the first only v.2.17
You have to flash the ota coming from a full 100% stock 2.17 based software phone !
Click to expand...
Click to collapse
Yes I have downloaded ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27-2.17.401.2_release_298985

MarcelHofs said:
Do this command with the phone in fastboot USB mode
Fastboot getvar version-main
And post result here please
Click to expand...
Click to collapse
2.17.401.2

I understand the safe way to install by run 2.17 RUU but like to find out howto without run 2.17 RUU since it should be possible...

[Q] rerooting after OTA update, cdma htc one v

Hi,
I need help. I did an ota update from htc to improve battery performance on my rooted phone. Now the phone is not rooted anymore. I'm still on stock ics rom, how do I reroot the phone again? Do I just follow the same procedures when I rooted it the first time? Thanks in advance for any help.

Performing the OTA update will cause boot loops with most of the custom roms such as CM10 and AOKP. To successfully run a custom rom you should revert to an older RUU then reroot the phone and choose the custom rom of your choice. Here is a link to the older RUU you need to be able to run most of the custom roms http://forum.xda-developers.com/showthread.php?t=2094373

if you have relocked the bootloader,u have to unlock it again.for this,place the Unlock_code.bin file u received from htc for unlocking ur bootloader the first time in the fastboot folder.(or the platform-tools folder,whichever u have).then boot into bootloader and go to fastboot.then connect phone to pc.then just flash the token using-
fastboot flash unlocktoken Unlock_code.bin
select yes on ur screen,ur bootloader is now unlocked.
now flash a custom recovery by placing the recovery_name.img in the fastboot/platform-tools folder and flash it using-
fastboot flash recovery recovery_name.img
once recovery is flashed,flash this zip in recovery-
http://forum.xda-developers.com/showthread.php?t=1538053
now ur phone is rooted once again

Gryff302 said:
Performing the OTA update will cause boot loops with most of the custom roms such as CM10 and AOKP. To successfully run a custom rom you should revert to an older RUU then reroot the phone and choose the custom rom of your choice. Here is a link to the older RUU you need to be able to run most of the custom roms http://forum.xda-developers.com/showthread.php?t=2094373
Click to expand...
Click to collapse
I'm still on the ROM the phone came with. I did not install any custom ROM after I rooted it first time. Do I reroot by doing the same procedures like I did the first time? i.e. unlock bootloader through HTC dev and use primo superboot to root.

mihirengg19 said:
if you have relocked the bootloader,u have to unlock it again.for this,place the Unlock_code.bin file u received from htc for unlocking ur bootloader the first time in the fastboot folder.(or the platform-tools folder,whichever u have).then boot into bootloader and go to fastboot.then connect phone to pc.then just flash the token using-
fastboot flash unlocktoken Unlock_code.bin
select yes on ur screen,ur bootloader is now unlocked.
now flash a custom recovery by placing the recovery_name.img in the fastboot/platform-tools folder and flash it using-
fastboot flash recovery recovery_name.img
once recovery is flashed,flash this zip in recovery-
http://forum.xda-developers.com/showthread.php?t=1538053
now ur phone is rooted once again
Click to expand...
Click to collapse
I did not flash any custom ROM after it was rooted the first time. The phone is still on the original ROM it came with. Do I just need to unlock and use primo superboot to root again?

yes
edit:just flash the zip i linked you to in recovery after flashing the recovery.u can also do the superboot way but this is more simple...

mihirengg19 said:
yes
edit:just flash the zip i linked you to in recovery after flashing the recovery.u can also do the superboot way but this is more simple...
Click to expand...
Click to collapse
Great! Thanks for the help, I will give it a go.

Flashed recovery as boot.img

Hello everyone,
After having unlocked the boot loader I flashed via fast boot TWRP. The only problem is that I flashed "fastboot flash BOOT recovery.img" instead of RECOVERY... I wasn't paying enough attention...
The phone still boots but it goes straight to recovery. What can I do? Fast boot still recognizes it. I was thinking of extracting the boot.img file from a sense based rom like android revolution HD for the m8 or putting the whole rom android revolution HD on an sd card and flashing via recovery. In other threads users had already flashed a custom rom so they could flash the boot.img extracting it from that but I don't know since I still had the stock unlocked rom.
Would one of these solutions solve the problem?

u can try fastboot flash boot whateverbootloader.img otherwise try fastboot rebootRUU and try flashing hboot from within a ruu zip or wait for HTC to release official RUU

djkinetic said:
u can try fastboot flash boot whateverbootloader.img otherwise try fastboot rebootRUU and try flashing hboot from within a ruu zip or wait for HTC to release official RUU
Click to expand...
Click to collapse
I'll try flashing a boot.img, the other solution is beyond my current skills...

Just extract the boot.img from the ROM you were using. If stock, download one of the stock Roms and then extract the boot.IMG from it and then
fastboot flash boot boot.img
Obviously the boot.img will need to be in your fastboot/adb folder.
Sent from my HTC One_M8 using xda app-developers app

thank you both, I flashed the correct boot.img and everything is fine now

djkinetic said:
u can try fastboot flash boot whateverbootloader.img otherwise try fastboot rebootRUU and try flashing hboot from within a ruu zip or wait for HTC to release official RUU
Click to expand...
Click to collapse
What... He just needs to flash a kernel, why potentially cause someone to brick their device by flashing a hboot which wouldn't even solve the issue?

where did you get the boot.img file ? care to share it I am stuck too. My phones is from Rogers

tawer said:
where did you get the boot.img file ? care to share it I am stuck too. My phones is from Rogers
Click to expand...
Click to collapse
Go to my backup thread and get a nandroid ....the kernel is inside the backup.

Thank you so much.

[Q] Do I need to flash boot.img via fastboot?

I've been using the HTC Desire HD for a long time, and I was wondering if things I've learnt with that phone are still relevant.
With the DHD, if the phone was S-ON (but with an unlocked bootloader and a custom recovery), whenever flashing a new ROM it was necessary to extract the boot.img file from the zip and flash it manually by using: fastboot flash boot boot.img.
That was because a custom recovery couldn't flash a custom kernel while the device was S-ON.
Is that also the case with an M8 device that stays S-ON?
Or is a custom recovery now able to write any custom kernel regardless of being S-ON/S-OFF?
Thanks!

Indeed
s-on = Flash kernel via fastboot
s-off = kernel is flashed via rom/recovery

Thank you for the quick reply!

quick question..if what you say is true..if s on flash kernal in fastboot..if s off just flash normally threw recovery...why in captins thread with his GPE rom..says s off users must flash boot.img in fastboot?...i was about to try his rom ,before i got to that part..i am s off and ive never had to flash a boot.img threw fastboot before flashing the rom....next question..do i need to unpack the rom zip ,extract the boot.img flash it in fastboot..then repack the zip and flash again in recovery?ive never had to do this..i thought i would see a boot.img zip as a seperate download wouldve been lot easier...ive never unpacked a zip to extract a boot.img before...so i had to back out for now..can someone plz give me step by step directions how to flash captins GPE rom..really appreciate it..and i know im in the correct section to ask such a newbie question..thanks in advance

is this still true with modern Marshmallow/Nougat ROMs (and their associated firmware updates)? the device is unlocked and S-ON?
example: I just flashed ViperROM v6.1 on Tmobile M8 with v6.2 firmware and separate flash of boot.img NOT required.
In fact, I validated theory by doing the traditional procedure and result as phone that did not boot.
traditional procedure: flash ROM via TWRP and reboot direct into bootloader and fastboot. then finalize by manual flash of boot.img via fastboot. boot.img pulled from root directory of ROM zip.
any insight would be appreciated. -GA
Mr Hofs said:
Indeed
s-on = Flash kernel via fastboot
s-off = kernel is flashed via rom/recovery
Click to expand...
Click to collapse

gads1 said:
is this still true with modern Marshmallow/Nougat ROMs (and their associated firmware updates)? the device is unlocked and S-ON?
example: I just flashed ViperROM v6.1 on Tmobile M8 with v6.2 firmware and separate flash of boot.img NOT required.
In fact, I validated theory by doing the traditional procedure and result as phone that did not boot.
traditional procedure: flash ROM via TWRP and reboot direct into bootloader and fastboot. then finalize by manual flash of boot.img via fastboot. boot.img pulled from root directory of ROM zip.
Click to expand...
Click to collapse
No need to flash boot.img separately using fastboot (with s-on).
But it shouldn't hurt anything, either. It's just a redundant step, as you are just flashing the same boot.img that TWRP is already installing.
Try it again, without flashing boot.img separately. But I have a feeling something else is causing no boot. Make sure you are using current TWRP (version 3.1) with default TWRP wipe (cache, dalvik and data), or try another ROM.

[Q] HTC One X dead... :(

I tried installing cm rom ...stable version...and by mistake wiped everything...the rom gave me get prop error....after that the mobile is stuck on hboot
i can unlock the bootloader and lock it and its on HBOOT. Plus i installed the TWRP. Tried side loading rom to it but error.
This is my getvar msg....attached....please help
tried everything...even htc all in one tool kit...locked the phone ..flashed the recovery and boot img and stock through all in one...but error
unlocked and through TWRP tried diff roms...pacman ...cm... but nothing... error
please give links to files (recovery, boot, stock rom, ...etc...etc) when you recommend as stuck and have no phone

ishaqz said:
I tried installing cm rom ...stable version...and by mistake wiped everything...the rom gave me get prop error....after that the mobile is stuck on hboot
i can unlock the bootloader and lock it and its on HBOOT. Plus i installed the TWRP. Tried side loading rom to it but error.
This is my getvar msg....attached....please help
tried everything...even htc all in one tool kit...locked the phone ..flashed the recovery and boot img and stock through all in one...but error
unlocked and through TWRP tried diff roms...pacman ...cm... but nothing... error
please give links to files (recovery, boot, stock rom, ...etc...etc) when you recommend as stuck and have no phone
Click to expand...
Click to collapse
Your hboot is too low. Now download this RUU run as administrator then apply all system updates and the flash the CM11

Thant said:
Your hboot is too low. Now download this RUU run as administrator then apply all system updates and the flash the CM11
Click to expand...
Click to collapse
Just connect through Hboot...?.... leave the device as locked? and run this on fastboot usb? Thats it?

ishaqz said:
Just connect through Hboot...?.... leave the device as locked? and run this on fastboot usb? Thats it?
Click to expand...
Click to collapse
Lock the device start the RUU on the PC after this fallow the instruction on the screen

Thant said:
Lock the device start the RUU on the PC after this fallow the instruction on the screen
Click to expand...
Click to collapse
Thanks buddy...that worked.... :good:
should i now unlock in hboot ...flash recovery TWRP or CWM.... and then install CM11?
any other steps?
Can you give link of stable CM11 please....
or best rom recommended?

ishaqz said:
Thanks buddy...that worked.... :good:
should i now unlock in hboot ...flash recovery TWRP or CWM.... and then install CM11?
any other steps?
Can you give link of stable CM11 please....
or best rom recommended?
Click to expand...
Click to collapse
Check for update and update the phone to latest JB 4.2.2 then unlock bootloader copy CM11 to a folder on your cd card flash twrp 2.7.1 then flash CM11 and flash boot.img from CM11.zip archive

Thant said:
Check for update and update the phone to latest JB 4.2.2 then unlock bootloader copy CM11 to a folder on your cd card flash twrp 2.7.1 then flash CM11 and flash boot.img from CM11.zip archive
Click to expand...
Click to collapse
Yup..still updating... thanks and hats off man....
hope not too much but can you post links to the three...stable cm11 or best rom according to you ...TWRP lastest and i guess boot img will be in the file... just few step by step if possible and links...as dont want to get stuck again :silly:
THANKS again...loads:angel:

ishaqz said:
Yup..still updating... thanks and hats off man....
hope not too much but can you post links to the three...stable cm11 or best rom according to you ...TWRP lastest and i guess boot img will be in the file... just few step by step if possible and links...as dont want to get stuck again :silly:
THANKS again...loads:angel:
Click to expand...
Click to collapse
1. I don't use AOSP download CM11 from Original android thread and gapps. Then copy the CM11.zip and gapps to a folder on your sd card
2. take the boot.img from CM11.zip and paste it in your fastboot folder
3. Download TWRP 2.7.1 and paste it in your fastboot foldert and flash it fastboot flash recovery recovery.img and then fastboot flash boot boot.img and last fastboot erase cache
4. Go in recovery flash First CM11.zip then Gapps and reboot and voala