Database Develop

[Q] Downgrading 4.3 to 4.1.2

Because i'm having bluetooth audio problems with numerous carkits/headsets i found out that going back to stock 4.1.2 resolves this problem.
The way i do this now is:
1. flash hboot 1.44
2. restore downloaded nandroid backup via CWM stock rom 1.29.401.12 for HTC__E11 (M7 CWM Nandroid Backup / CID HTC__102 / 1.29.401.12 (DE Unbranded - Thanks to FordSierra88))
after restoring touch doesn't work but use a USB Mouse
3. flash stock 1.29.401.12 recovery
4. fastboot oem lock
5. install RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
I have a feeling that i'm taking a sightseeing tour with this approach. Can i do this quicker???
Maybe via Guru reset? or RUU.zip? I understand that my CID must be stock and no Custom recovery installed and bootloader locked?
Again.. my goal is stock rom including OTA's. I stop installing OTA's after the one in the picture.
Can someone clear things up for me please?

Tranzy said:
Because i'm having bluetooth audio problems with numerous carkits/headsets i found out that going back to stock 4.1.2 resolves this problem.
The way i do this now is:
1. flash hboot 1.44
2. restore downloaded nandroid backup via CWM stock rom 1.29.401.12 for HTC__E11 (M7 CWM Nandroid Backup / CID HTC__102 / 1.29.401.12 (DE Unbranded - Thanks to FordSierra88))
after restoring touch doesn't work but use a USB Mouse
3. flash stock 1.29.401.12 recovery
4. fastboot oem lock
5. install RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
I have a feeling that i'm taking a sightseeing tour with this approach. Can i do this quicker???
Maybe via Guru reset? or RUU.zip? I understand that my CID must be stock and no Custom recovery installed and bootloader locked?
Again.. my goal is stock rom including OTA's. I stop installing OTA's after the one in the picture.
Can someone clear things up for me please?
Click to expand...
Click to collapse
"I have a feeling that i'm taking a sightseeing tour with this approach. Can i do this quicker???" :silly:
can you post a "fastboot getvar all" excluding IMEI and s/n

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4315mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
wow... just noticed my signature.. i guess it needs updating

Tranzy said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
wow... just noticed my signature.. i guess it needs updating
Click to expand...
Click to collapse
go to my guide, http://forum.xda-developers.com/showthread.php?t=2541082
in RUU.ZIP method, use this ruu.zip : http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
no need to mess with UNLOCKED or TAMPERED (unless you want), and definitely do not change S-Off.
let me know if you have any questions.

nkk71 said:
go to my guide, http://forum.xda-developers.com/showthread.php?t=2541082
in RUU.ZIP method, use this ruu.zip : http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
3.62
no need to mess with UNLOCKED or TAMPERED (unless you want), and definitely do not change S-Off.
let me know if you have any questions.
Click to expand...
Click to collapse
I tried flashing Guru_Reset_M7_1.29.401.13 and ticked everything stock. Ended up with touchscreen not working and noticed that i was still on version 3.62.
I will download the zip you suggested. I takes a while to download so i will report back.

Tranzy said:
I tried flashing Guru_Reset_M7_1.29.401.13 and ticked everything stock. Ended up with touchscreen not working and noticed that i was still on version 3.62.
I will download the zip you suggested. I takes a while to download so i will report back.
Click to expand...
Click to collapse
yeah that's normal, because the touchscreen drivers were updated in 2.xx (and not backwards compatible)
you just need to use Step 2:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE
fastboot reboot-bootloader
all done, no need to mess with anything else (tampered, unlocked, S-Off), everything back to stock 1.28 and you can take OTAs to whichever version you want, or stop at 1.28
recommend you stay s-off

nkk71 said:
yeah that's normal, because the touchscreen drivers were updated in 2.xx (and not backwards compatible)
you just need to use Step 2:
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip <- yes TWICE
fastboot reboot-bootloader
all done, no need to mess with anything else (tampered, unlocked, S-Off), everything back to stock 1.28 and you can take OTAs to whichever version you want, or stop at 1.28
recommend you stay s-off
Click to expand...
Click to collapse
Do i need to flash the hboot 1.44 and do i need to lock the bootloader for this to work?

Tranzy said:
Do i need to flash the hboot 1.44 and do i need to lock the bootloader for this to work?
Click to expand...
Click to collapse
I'm at work. So i will have to download this at home later on. But i need a working phone now. So i decided to give the RUU.exe file a go again. (It worked before) but it failed this time. The only thing i did was flash the 1.44 hboot again and now the rom installed nicely.
I guess the RUU.exe needs the 1.44 hboot after all? Is this correct?
Sorry but i'm fairly new to this all and i'm just trying this out following your guides and that of other. Trial and error method

Tranzy said:
I'm at work. So i will have to download this at home later on. But i need a working phone now. So i decided to give the RUU.exe file a go again. (It worked before) but it failed this time. The only thing i did was flash the 1.44 hboot again and now the rom installed nicely.
I guess the RUU.exe needs the 1.44 hboot after all? Is this correct?
Sorry but i'm fairly new to this all and i'm just trying this out following your guides and that of other. Trial and error method
Click to expand...
Click to collapse
yes correct, the RUU.exe needs a separate hboot downgrade first (if hboot is 1.55+), to allow the RUU to work.
on the other hand, the ruu.zip method does not.
End result is the same.

[Q] HELP with updating HTC One to 4.4...

Hello, I have a rooted international HTC One currently running 4.3 Android with Sense 5.0. I am trying to perform an OTA system update that I have received... I downloaded the new 4.4 Android (1.1 GB) and I have selected "Install Update". But when the phone restarts, it just enters recovery and opens TWRP by itself!
So then I try to flash the downloaded OTA file via TWRP, but that also fails... Does anyone know how I can get 4.4 on my HTC One? Thank you

arbank94 said:
Hello, I have a rooted international HTC One currently running 4.3 Android with Sense 5.0. I am trying to perform an OTA system update that I have received... I downloaded the new 4.4 Android (1.1 GB) and I have selected "Install Update". But when the phone restarts, it just enters recovery and opens TWRP by itself!
So then I try to flash the downloaded OTA file via TWRP, but that also fails... Does anyone know how I can get 4.4 on my HTC One? Thank you
Click to expand...
Click to collapse
You can't apply ota with a custom recovery, you need your stock recovery.

arbank94 said:
Hello, I have a rooted international HTC One currently running 4.3 Android with Sense 5.0. I am trying to perform an OTA system update that I have received... I downloaded the new 4.4 Android (1.1 GB) and I have selected "Install Update". But when the phone restarts, it just enters recovery and opens TWRP by itself!
So then I try to flash the downloaded OTA file via TWRP, but that also fails... Does anyone know how I can get 4.4 on my HTC One? Thank you
Click to expand...
Click to collapse
Depending on whats been done to the phone you can eather flash stock recovery and try the update from their or you have to ruu back to stock and take the update that way.
fastboot getvar all will tell you what stock recovery you need or what ruu to use

alray said:
You can't apply ota with a custom recovery, you need your stock recovery.
Click to expand...
Click to collapse
So would you recommend getting stock recovery following nkk71's guide in your signature, or should I just flash a 4.4 rom?

arbank94 said:
So would you recommend getting stock recovery following nkk71's guide in your signature, or should I just flash a 4.4 rom?
Click to expand...
Click to collapse
Do what cIsA said. Check the output of "fastboot getvar all". Look at your main-ver # and find the corresponding stock recovery. There is a thread in general section with a collection of stock recovery.
You can post the output of getvar here minus imei/sn and we will link you the correct recovery.

Okay so I ran a fastboot getvar all, and apparently there is no RUU for my device, because it is Latin American with a CID of HTC_332. (I searched almost everywhere)
Now, after flashing a 4.4 rom I downloaded, my HTC device wasn't turning on anymore (it was getting stuck at the HTC boot logo). So I restored from a backup I made in TWRP, and that didn't work either. So now my problem just got 1000x worse because of a mistake I just made now of completely wiping my device and the OS.
So for the moment I'll try to flash a new boot.img, get S-OFF again, and change the CID to 11111111 (as I have read) where I will then download a RUU I can use. I'll let you know what happens.

Whoa there.. No need to flash boot.IMG.
What's you're steps? I think you are about to make it worse
sent from my mobile device

Okay well I'm in a tight situation atm.
My phone is completely wiped, with no OS or anything. The only thing I have access to is fastboot, and the TWRP bootloader. Also considering my phone is wiped, I believe I have S-ON as well.
So what is the first step to just get a boot going? (unless I'm not completely screwed that is..)
EDIT- I have successfully flashed Android Revolution to my phone from TWRP by pushing the zip via adb fastboot. Got my phone running again. Step 1 complete.
Step 2 now is to get S-OFF again...
Step 3- Change my CID to 11111111 using the SuperCID method (there is no RUU for my Latin American CID; HTC_332)
Step 4- Use an appropriate RUU to get 4.4 stock after I have changed my CID.
Before I continue with these steps, can anyone confirm with me if I am on the right path?

Step 2 - Confirmed.
Step 3 & Step 4 ... What is an appropriate RUU? You have not yet posted a fastboot getvar all output yet. (remove imei)

SaHiLzZ said:
Step 2 - Confirmed.
Step 3 & Step 4 ... What is an appropriate RUU? You have not yet posted a fastboot getvar all output yet. (remove imei)
Click to expand...
Click to collapse
I had the same cid when I bought mine. Irc, MID was PN0711000 with s.w. X.XX.599.X.
so he could use the 1.29.401.2 ruu on htc1guru but he have to change cid.
---------- Post added at 08:04 PM ---------- Previous post was at 08:02 PM ----------
arbank94 said:
EDIT- I have successfully flashed Android Revolution to my phone from TWRP by pushing the zip via adb fastboot. Got my phone running again.
Before I continue with these steps, can anyone confirm with me if I am on the right path?
Click to expand...
Click to collapse
You could just stay with arhd, its a very good rom...

alray said:
You could just stay with arhd, its a very good rom...
Click to expand...
Click to collapse
Agreed!:laugh:

alray said:
I had the same cid when I bought mine. Irc, MID was PN0711000 with s.w. X.XX.599.X.
so he could use the 1.29.401.2 ruu on htc1guru but he have to change cid.
---------- Post added at 08:04 PM ---------- Previous post was at 08:02 PM ----------
You could just stay with arhd, its a very good rom...
Click to expand...
Click to collapse
C:\Users\Arban\Downloads\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x
86_64-20131030\sdk\platform-tools>adb push htcrom2.zip /sdcard/
3455 KB/s (1180577030 bytes in 333.659s)
C:\Users\Arban\Downloads\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x
86_64-20131030\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH392W901414
(bootloader) imei: **************
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e0349bfc
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
So yeah... there's no RUU as I said.
alray, in order to use that 1.29.401.2 RUU, what do I have to change my CID to?
EDIT: I'll just stick with your suggestion alray and stay with ARHD lol. (but in case I change my mind, what CID should I change to for that RUU?... so that I won't have to bump this thread or make a new one later)

arbank94 said:
C:\Users\Arban\Downloads\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x
86_64-20131030\sdk\platform-tools>adb push htcrom2.zip /sdcard/
3455 KB/s (1180577030 bytes in 333.659s)
C:\Users\Arban\Downloads\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x
86_64-20131030\sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH392W901414
(bootloader) imei: **************
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e0349bfc
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
So yeah... there's no RUU as I said.
alray, in order to use that 1.29.401.2 RUU, what do I have to change my CID to?
EDIT: I'll just stick with your suggestion alray and stay with ARHD lol. (but in case I change my mind, what CID should I change to for that RUU?... so that I won't have to bump this thread or make a new one later)
Click to expand...
Click to collapse
These CID:
HTC__001
HTC__J15
HTC__A48
HTC__M27
are compatible with the 1.29.401.2 ruu.zip so i'll suggest you to use HTC__001 if you change your mind. Personally, I would stay on ARHD. No benefit to flash that RUU vs ARHD. ARHD is always up to date...

[Q] SuperCID and RUU WWE

Hi
I have Unlocked Bootloader, S-Off and SuperCID, installed GPE ROM via RUU.zip
Now I need to install ROM via RUU. exe but I don't see superCID on supported CID list.
Will stock GPE ROM boot with CID HTC__032?
Or... Can I flash this RUU on superCID?
This RUU is here:
http://bit.ly/1EPvdwI

Super CID will help you or better have same CID as gpe have
Because ruu checks CID & MID and can give errors

ok. I changed it to HTC__032 and RUU force closes during gathering device information on Windows 7.
On Windows 8 fastboot crashes :/
all systems are 64-bit
But... If I have GPE ROM and firmware 5.0.1 can I flash KitKat based ROM's eg ViperOne?

Gpe have CID like GOOGLE01 I'm not sure better search before changing
Your 032 certainly not help you use win 7
ViperOne need sense firmware GPE firmware not good

Bruce666 said:
ok. I changed it to HTC__032 and RUU force closes during gathering device information on Windows 7.
On Windows 8 fastboot crashes :/
all systems are 64-bit
But... If I have GPE ROM and firmware 5.0.1 can I flash KitKat based ROM's eg ViperOne?
Click to expand...
Click to collapse
read and do this, I was having the same problem: http://forums.androidcentral.com/ht...tall-4-3-ruu-windows-7-8-1-a.html#post3466555
you must install all of them one at a time with reboots inbetween each, and if you have a full RUU make sure your MID also matches, you may also have to flash the corresponding sense firmware first.

yatindroid said:
Gpe have CID like GOOGLE01 I'm not sure better search before changing
Your 032 certainly not help you use win 7
ViperOne need sense firmware GPE firmware not good
Click to expand...
Click to collapse
so... what can I do? now I have CID HTC__032 and this ROM.
RUU exe crashes, fastboot crashes. What can I do? Guru reset won't work in this case when I have GPE firmware?

Bruce666 said:
so... what can I do? now I have CID HTC__032 and this ROM.
RUU exe crashes, fastboot crashes. What can I do? Guru reset won't work in this case when I have GPE firmware?
Click to expand...
Click to collapse
Are you able to post your fastboot getvar all ?

Seanie280672 said:
Are you able to post your fastboot getvar all ?
Click to expand...
Click to collapse
yes no problem
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:XXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4193mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.115s

Bruce666 said:
yes no problem
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:XXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4193mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.115s
Click to expand...
Click to collapse
Thanks, do NOT at any point go s-on, you need to flash the stock sense firmware first then run the RUU
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
you need 4.19.401.9
Because you are s-off you will not need to re-lock the bootloader nor lock it, just run the RUU whilst your phone is still in fastbootUSB mode straight after the firmware flash.

Seanie280672 said:
Thanks, do NOT at any point go s-on, you need to flash the stock sense firmware first then run the RUU
http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
you need 4.19.401.9
Click to expand...
Click to collapse
and fastboot will not crash? I'm very afraid about it

Bruce666 said:
and fastboot will not crash? I'm very afraid about it
Click to expand...
Click to collapse
When is fastboot crashing ?

Seanie280672 said:
When is fastboot crashing ?
Click to expand...
Click to collapse
in the last step. after copying in stage 1/5 fastboot crashes. Memory is untouched

Bruce666 said:
in the last step. after copying in stage 1/5 fastboot crashes. Memory is untouched
Click to expand...
Click to collapse
no it shouldnt crash, its a different type of fastboot kind of................basically when you install an RUU, the software is installed first and the last thing the RUU does is flash the firmware, however, because you have GPE firmware on your phone, the software install is failing, only way around it is to flash the firmware first, see here: http://forum.xda-developers.com/showthread.php?t=2733523 don't follow this guide, its just to give you an idea of what we are doing.
To flash a firmware you must be in bootloader/fastbootUSB mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip (there will be some nerving pauses, just let it run, make sure it says successful before the next command) then:
Fastboot reboot-bootloader
Run RUU now..........

Seanie280672 said:
no it shouldnt crash, its a different type of fastboot kind of................basically when you install an RUU, the software is installed first and the last thing the RUU does is flash the firmware, however, because you have GPE firmware on your phone, the software install is failing, only way around it is to flash the firmware first, see here: http://forum.xda-developers.com/showthread.php?t=2733523
To flash a firmware you must be in bootloader/fastbootUSB mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip (there will be some nerving pauses, just let it run, make sure it says successful before the next command) then:
Fastboot reboot-bootloader
Run RUU now..........
Click to expand...
Click to collapse
ok but this is RUU.exe not zip. is flashing firmware wiping all data?

Bruce666 said:
ok but this is RUU.exe not zip. is flashing firmware wiping all data?
Click to expand...
Click to collapse
you need to download the firmware file from the link I gave you earlier: 4.19.401.9 firmware, put it in the same folder as fastboot files, then boot your phone to fastbootUSB mode and follow the commands above.
heres the link again: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC/HTC_One/401/
the RUU will wipe your phone when you install it.

Seanie280672 said:
you need to download the firmware file from the link I gave you earlier: 4.19.401.9 firmware, put it in the same folder as fastboot files, then boot your phone to fastbootUSB mode and follow the commands above.
the RUU will wipe your phone when you install it.
Click to expand...
Click to collapse
ok. but will ROM I have flashed boot on this Firmware? coz I have RUU.exe

Bruce666 said:
ok. but will ROM I have flashed boot on this Firmware? coz I have RUU.exe
Click to expand...
Click to collapse
Run the RUU.exe after you have flashed the firmware, after the firmware and the RUU, you will be back on stock Sense, remember to flash the firmware twice, follow the commands above

Seanie280672 said:
Run the RUU.exe after you have flashed the firmware, after the firmware and the RUU, you will be back on stock Sense, remember to flash the firmware twice, follow the commands above
Click to expand...
Click to collapse
ok. but will ROM i have boot on this firmware?

Bruce666 said:
ok. but will ROM i have boot on this firmware?
Click to expand...
Click to collapse
what rom do you have ?

Seanie280672 said:
what rom do you have ?
Click to expand...
Click to collapse
I have this ROM
http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927

Bootloop on Insertcoin rom and unable to install Stock RUU after HTC m7 dev edition

I flashed Insercoin 7.0.9 where bootloop apeared. ( my phone is S-ON, unlocked bootloader, hboot 1.61, rooted ) I managed to go to recovery and go into bootloader mode where i installed RUU according to my CID , but when it starts installing the RUU it shows error [155]. I think must be because of the unlocked bootloader, if I relock it, will I be able to unlock it again later ? after installing InsertCoin it stays on HTC white screen. Does the fact that I am S-ON matters ?
What could be the reason that after installing Insercoin it stays on this white htc screen :?
If i have to install stock ruu should i relock bootloader, because of the error 155 ?

beerfly said:
I flashed Insercoin 7.0.9 where bootloop apeared. ( my phone is S-ON, unlocked bootloader, hboot 1.61, rooted ) I managed to go to recovery and go into bootloader mode where i installed RUU according to my CID , but when it starts installing the RUU it shows error [155].
Click to expand...
Click to collapse
Yes you must be locked or relocked to flash ruu with s-on.
I think must be because of the unlocked bootloader, if I relock it, will I be able to unlock it again later ?
Click to expand...
Click to collapse
Yes you'll be able to unlock again.
after installing InsertCoin it stays on HTC white screen. Does the fact that I am S-ON matters ?
Click to expand...
Click to collapse
No, Insert Coin doesn't require s-off.
What could be the reason that after installing Insercoin it stays on this white htc screen :?
Click to expand...
Click to collapse
From my own experience, latest developer edition firmware (7.17.1540.7) doesn't play nice with newer custom roms kernel. I experienced similar issues when flashing custom roms and using the kernels that comes with these while using the 7.17.1540.7 firmware. Using the stock kernel or converting your phone from dev edition to wwe version 7.19.401.2 (s-off required to convert) should fix the problem.
If i have to install stock ruu should i relock bootloader, because of the error 155 ?
Click to expand...
Click to collapse
Yes, you must be locked or relocked if s-on. Also make sure to choose the right ruu that match your CID, MID and firmware version. If you have any doubt, post the output of "fastboot getvar all" and we'll help you determine what ruu you need.

Yes, you must be locked or relocked if s-on. Also make sure to choose the right ruu that match your CID, MID and firmware version. If you have any doubt, post the output of "fastboot getvar all" and we'll help you determine what ruu you need.[/QUOTE]
Thank you for your time, here is getvar :
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.1540.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35K************
(bootloader) imei: *********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4188mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

beerfly said:
Thank you for your time, here is getvar :
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.1540.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35K************
(bootloader) imei: *********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4188mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-eff4f609
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Looks like you are having the same issue I had when trying this rom with a 7.17.1540.7 firmware. So you can either:
relock your bootloader
flash the 7.17.1540.7 ruu
re-unlock (if needed)
or
Flash latest insert coin rom and then flash the stock 7.17.1540.7 kernel and see if it boot. (already tried with isertcoin 7.0.7 and it worked)
or
Achieve s-off
Flash the 7.19.401.2 WWE firmware
flash latest insert coin.
Option #3 is what I have currently and everything is working fine.

Flash latest insert coin rom and then flash the stock 7.17.1540.7 kernel and see if it boot. (already tried with isertcoin 7.0.7 and it wor
Okay i flashed latest version of IC, how to put the 7.17.1540.7boot.img in the phone is what bothers me .. :/

beerfly said:
Flash latest insert coin rom and then flash the stock 7.17.1540.7 kernel and see if it boot. (already tried with isertcoin 7.0.7 and it wor
Okay i flashed latest version of IC, how to put the 7.17.1540.7boot.img in the phone is what bothers me .. :/
Click to expand...
Click to collapse
if you have latest twrp, select "install". In the bottom right corner, there is a button "Images.../Zips...", select it so it says "select image to install" instead of "select zip to install". then select the kernel file. When asked to "select partition to flash image", select "boot" and swipe to flash. then reboot the phone.
Remember that first boot can take up to 15-20 minutes with phone staying at htc white screen for a while.

alray said:
if you have latest twrp, select "install". In the bottom right corner, there is a button "Images.../Zips...", select it so it says "select image to install" instead of "select zip to install". then select the kernel file. When asked to "select partition to flash image", select "boot" and swipe to flash. then reboot the phone.
Remember that first boot can take up to 15-20 minutes with phone staying at htc white screen for a while.
Click to expand...
Click to collapse
Thanks, i know this option but I cant push or sideload the file as its format is *.img, even if select *all files it does not appear. I use HTC One toolkit for this.
Okay , I relocked the bootloader and installed original stock RUU, maybe will cancel my plans for S-off and installing custom rom. Will just root and thats it. Thanks for your help @alray . You deserve a big cold beer now.

beerfly said:
Thanks, i know this option but I cant push or sideload the file as its format is *.img, even if select *all files it does not appear. I use HTC One toolkit for this.
Click to expand...
Click to collapse
Using toolkits is not ideal. Learning adb and fastboot would be better. With adb you can push files of all types easily using "adb push" command. e.g:
Code:
adb push my_kernel_file.img /sdcard
Even simpler, if you have a recent version of TWRP (e.g: 2.8.6.0) and latest HTC drivers installed on your computer, you can see your phone like a removable storage drive on your computer when booted in twrp. Just drag and drop the kernel to your phone.
Okay , I relocked the bootloader and installed original stock RUU, maybe will cancel my plans for S-off and installing custom rom. Will just root and thats it. Thanks for your help @alray . You deserve a big cold beer now.
Click to expand...
Click to collapse
No problem, if you change your mind and still need help just quote me here. Have a good day

No problem, if you change your mind and still need help just quote me here. Have a good day
Well , my phone did change its mind - now decided that latest xposed is not compitable with my phone, in case that I use very same apk before and ran properly , its wierd now.
Fixed, all good now.

possible brickage

i attempted to unlock bootloader on my wife's old HTC M7 (Australian/Vodafone), i was able to unlock the bootloader, but had to do some serious trial and error to get a custom recovery installed, eventually got an older twrp loaded, but the phone just refused to boot into recovery.
i then relocked the bootloader (no S-OFF), and when i try and unlock he bootloader now, the phone attempts to boot into the recovery, and is failing...
i've been trying to find an RUU from somewhere, just to blat the phone back to an old state, and try again.
are there RUUs available anywhere? i dont' care if its not for the local carrier, i just want to get a basic android rom on the thing.
However, im curious if i need to s-off to do this (wasnt the case with my previous HTC)
help!
<<<I NOW KNOW WHAT THE ISSUE WAS, I WAS FLASHING RECOVERY FROM THE HTC M8, NOT M7>>>
any ideas?

gjw00 said:
i then relocked the bootloader (no S-OFF), and when i try and unlock he bootloader now, the phone attempts to boot into the recovery, and is failing...
Click to expand...
Click to collapse
Really bad idea to relock the bootloader with a custom recovery, well you shouldn't relock at all if there is anything "custom" installed on your phone.The process of unlocking bootloader requires the stock recovery. The only way to flash the recovery partition is when the bootloader is unlocked or by flashing a signed firmware.zip or ruu.zip. The firmware.zip or ruu.zip must match your version-main, CID and MID.
i've been trying to find an RUU from somewhere, just to blat the phone back to an old state, and try again.
are there RUUs available anywhere? i dont' care if its not for the local carrier, i just want to get a basic android rom on the thing.
Click to expand...
Click to collapse
Its not working like that. If your phone is S-ON the ruu must be made for your carrier (must match CID and MID, must be same or newer version-main)
post the output of "fastboot getvar all" (remove your imei and serialno)

alray said:
Really bad idea to relock the bootloader with a custom recovery, well you shouldn't relock at all if there is anything "custom" installed on your phone.The process of unlocking bootloader requires the stock recovery. The only way to flash the recovery partition is when the bootloader is unlocked or by flashing a signed firmware.zip or ruu.zip. The firmware.zip or ruu.zip must match your version-main, CID and MID.
Its not working like that. If your phone is S-ON the ruu must be made for your carrier (must match CID and MID, must be same or newer version-main)
post the output of "fastboot getvar all" (remove your imei and serialno)
Click to expand...
Click to collapse
ok, i've been trying with a bunch of RUUs i found on the web, and trying to flash inside RUU (wasnt 100% sure what rebooting to RUU was for actually)
the CID is VODAP021, i will need to check when i get back home to see what the MID is, its not the GPE of the m7, if that helps, you reckon if i find an OTA update, and extract out the ruu.zip, it might blat a stock recovery on? will i need to use htc_fastboot, or just the standard fastboot?
my nexus 5 has finally shat it (small child cracked screen, now screen has crapped itself), just want to get a basic android build onto the m7 in the final few weeks before the new pixel phones are out...

gjw00 said:
ok, i've been trying with a bunch of RUUs i found on the web, and trying to flash inside RUU (wasnt 100% sure what rebooting to RUU was for actually)
the CID is VODAP021, i will need to check when i get back home to see what the MID is, its not the GPE of the m7, if that helps, you reckon if i find an OTA update, and extract out the ruu.zip, it might blat a stock recovery on? will i need to use htc_fastboot, or just the standard fastboot?
my nexus 5 has finally shat it (small child cracked screen, now screen has crapped itself), just want to get a basic android build onto the m7 in the final few weeks before the new pixel phones are out...
Click to expand...
Click to collapse
You can extract a firmware.zip (not an ruu) from an ota update and flash it to restore the stock recovery. You must use the right version. Waiting for your fastboot getvar all.
Sent from my HTC One using XDA Labs

fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.980.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

gjw00 said:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.21.980.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
7.21.980.51 is the latest version for vodap021 and can't find a 7.21.980.51 firmware.zip or ota.zip.
At least there is a 7.21.980.51 ruu on ir-file.com, bad news is that you must register to this website to be able to download (20$ for 30 days)
http://ir-file.com/show.php?token=32375

i can load the phone into the OS btw, i've a feeling that OTA might on the device, you think its' accessible using a non-root browser? i could maybe get the ota zip off the device and try flashing that in RUU?

gjw00 said:
i can load the phone into the OS btw, i've a feeling that OTA might on the device, you think its' accessible using a non-root browser? i could maybe get the ota zip off the device and try flashing that in RUU?
Click to expand...
Click to collapse
Yes, if you can capture the ota this is the best option (because its free). Look in your /download folder, you're looking for a long file name starting with "OTA_M7_UL_L50_SENSE60" and ending with ".zip". Save it on your computer and extract the "firmware.zip" file from it. Then reboot in RUU mode and flash the firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you should be able to unlock again.

it worked! thank you..