Hello everyone,
I've rooted by HTC one and also flashed a custom recovery en kernel.
Now I want to sell my phone but I cant get the RUU to run. When I run it it never goes past the first step: "checking headers".
I've had this problem before, someone on this forum advised me to erase the cache, flash firmware en then run the RUU again. This worked but it is nog working now as flashing the firmware gives me an error.
My getvar all looks like this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH35CW911477
(bootloader) imei: 354436056664251
(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: 3918mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm running the correect RUU (as in it corresponds with my cid)
I'm trying to flash the 3.62.401.1 firmware.
And this is what happends:
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
I really hope some can help me. Thanks!
marcusabu said:
Hello everyone,
I've rooted by HTC one and also flashed a custom recovery en kernel.
Now I want to sell my phone but I cant get the RUU to run. When I run it it never goes past the first step: "checking headers".
I've had this problem before, someone on this forum advised me to erase the cache, flash firmware en then run the RUU again. This worked but it is nog working now as flashing the firmware gives me an error.
My getvar all looks like this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH35CW911477
(bootloader) imei: 354436056664251
(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: 3918mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm running the correect RUU (as in it corresponds with my cid)
I'm trying to flash the 3.62.401.1 firmware.
And this is what happends:
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
I really hope some can help me. Thanks!
Click to expand...
Click to collapse
Your device is s-on so you can't use that ruu. You can't downgrade firmware while s-on. It probably worked last time because you were updating.
Why is it you need to flash an ruu is there a problem with your device?
Danny201281 said:
Your device is s-on so you can't use that ruu. You can't downgrade firmware while s-on. It probably worked last time because you were updating.
Why is it you need to flash an ruu is there a problem with your device?
Click to expand...
Click to collapse
OOH crap.
I'm going to sell it so it should be able to recieve OTA's. Is there any other way for this?
marcusabu said:
OOH crap.
I'm going to sell it so it should be able to recieve OTA's. Is there any other way for this?
Click to expand...
Click to collapse
You can flash a Stock Rom and recovery and the phone will get OTA updates. But without s-off you won't be able to fully lock the bootloader (best you'll get is ***RELOCKED***) and you won't be able to remove the Tampered flag.
Danny201281 said:
You can flash a Stock Rom and recovery and the phone will get OTA updates. But without s-off you won't be able to fully lock the bootloader (best you'll get is ***RELOCKED***) and you won't be able to remove the Tampered flag.
Click to expand...
Click to collapse
That'll be fine. I'm on stock rom so I just need to find the stock recovery. It doens't matter that the phone is still rooted?
marcusabu said:
That'll be fine. I'm on stock rom so I just need to find the stock recovery. It doens't matter that the phone is still rooted?
Click to expand...
Click to collapse
if you have flashed back the stock rom then your "phone" isn't rooted anymore. You root a rom, not the phone itself. so if you reflash a rom, you'll loose root (unless you re-root or if you have flashed a pre-rooted rom, which isn't the case with a stock rom)
If you havent flashed the stock rom and you are planning just to flash the stock recovery back, I would suggest to flash the stock rom to ensure that everything will be fine for the next owner.
stock recovery and rom for 6.09.401.5 can be found on arhd website (download section) and probably here in the general section, there is a recovery collection thread.
alray said:
if you have flashed back the stock rom then your "phone" isn't rooted anymore. You root a rom, not the phone itself. so if you reflash a rom, you'll loose root (unless you re-root or if you have flashed a pre-rooted rom, which isn't the case with a stock rom)
If you havent flashed the stock rom and you are planning just to flash the stock recovery back, I would suggest to flash the stock rom to ensure that everything will be fine for the next owner.
stock recovery and rom for 6.09.401.5 can be found on arhd website (download section) and probably here in the general section, there is a recovery collection thread.
Click to expand...
Click to collapse
Wow I didn't even know that. Anyway, I flashed de stock rom en recovery and it looks like I'm al set. Thank you!
marcusabu said:
Wow I didn't even know that. Anyway, I flashed de stock rom en recovery and it looks like I'm al set. Thank you!
Click to expand...
Click to collapse
no prob, you can leave the bootloader unlocked (If its not to late ) so if the new owner want it unlocked, he will not loose all HTC preloaded apps when unlocking it from htcdev.com...
Danny201281 said:
You can flash a Stock Rom and recovery and the phone will get OTA updates. But without s-off you won't be able to fully lock the bootloader (best you'll get is ***RELOCKED***) and you won't be able to remove the Tampered flag.
Click to expand...
Click to collapse
It's done. Thanks for the help I really appreciate it.
Related
I've seen similair threads but nothing posted seems to work for me, and i've been trying to get to stock 4.4 for what seems like ages.
I'll attach a getvar below, but essentially i'm on stock 4.3, although rooted and with TWRP recovery. Despite that, I received the OTA that would update my phone to 4.4.2. I know my phone has the right CID, MID, and firmware for the update, i double checked, and the fact i received it anyways. I've tried installing the OTA on various "Stock" recoveries, i've found around the forum for the htc one, but all have failed and its ended with a red triangle over the phone, and then it gets stuck booting; forcing me to flash a custom recovery, push a nandroid, restore, and start all over again.
Simply, i have an OTA, the right firmware, CID, MID etc, but can someone tell me or point me towards a recovery it will work with, or a work around (I've seen things about extracting the firmware.zip from the main one etc etc). Any reply will be helpful, all i want is for it to install.
(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.206.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: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4285mV
(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.093s
Gaff3rs said:
I've seen similair threads but nothing posted seems to work for me, and i've been trying to get to stock 4.4 for what seems like ages.
I'll attach a getvar below, but essentially i'm on stock 4.3, although rooted and with TWRP recovery. Despite that, I received the OTA that would update my phone to 4.4.2. I know my phone has the right CID, MID, and firmware for the update, i double checked, and the fact i received it anyways. I've tried installing the OTA on various "Stock" recoveries, i've found around the forum for the htc one, but all have failed and its ended with a red triangle over the phone, and then it gets stuck booting; forcing me to flash a custom recovery, push a nandroid, restore, and start all over again.
Simply, i have an OTA, the right firmware, CID, MID etc, but can someone tell me or point me towards a recovery it will work with, or a work around (I've seen things about extracting the firmware.zip from the main one etc etc). Any reply will be helpful, all i want is for it to install.
(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.206.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: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4285mV
(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.093s
Click to expand...
Click to collapse
Is the stock recovery you've been using from a 3.62.206.x ruu?
It needs to be the same version as your current OS.
Had same issue. Apply it manually from sdcard.
Sent from my Nexus 5 using Tapatalk
mb_guy said:
Is the stock recovery you've been using from a 3.62.206.x ruu?
It needs to be the same version as your current OS.
Click to expand...
Click to collapse
I don't think it was actually, so do I need to find an o2 RUU, and pull the recovery img from that?
Gaff3rs said:
I don't think it was actually, so do I need to find an o2 RUU, and pull the recovery img from that?
Click to expand...
Click to collapse
just use the full RUU
http://www.androidruu.com/getdownlo...8_10.38r.1157.04L_release_353143_signed_2.exe
samflorin said:
Had same issue. Apply it manually from sdcard.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Do you mean just apply the full zip as I would any Rom through TWRP?
clsA said:
just use the full RUU
http://www.androidruu.com/getdownlo...8_10.38r.1157.04L_release_353143_signed_2.exe
Click to expand...
Click to collapse
thanks very much, by running this, will it just update to 4.4.2? as the OTA would have done, just a lot more simple...
Gaff3rs said:
thanks very much, by running this, will it just update to 4.4.2? as the OTA would have done, just a lot more simple...
Click to expand...
Click to collapse
it will wipe your phone clean
backup to your PC and HTC backup
clsA said:
it will wipe your phone clean
backup to your PC and HTC backup
Click to expand...
Click to collapse
Alright thanks for the heads up, do i need to do anything else first? unroot, lock bootloader? or is it fine to run as i am, custom recovery, unlocked bootloader?
Gaff3rs said:
Alright thanks for the heads up, do i need to do anything else first? unroot, lock bootloader? or is it fine to run as i am, custom recovery, unlocked bootloader?
Click to expand...
Click to collapse
you s-off you don't have to lock the bootloader
just backup and run the RUU
clsA said:
you s-off you don't have to lock the bootloader
just backup and run the RUU
Click to expand...
Click to collapse
alright thanks a lot, you've quite possibly saved me after a month of confusion
Gaff3rs said:
Do you mean just apply the full zip as I would any Rom through TWRP?
Click to expand...
Click to collapse
No. Apply it through stock recovery.
Use the recovery.img from your downloaded OTA zip file and try again, that way work for me but i have to redownload the OTA file thou...
I was updated from 2.24.*.* to 3.63.*.* and 4.20.*.* .I use the stock recoveries around the internet I've fond and fail. Than I extract the recovery.img from my 4.3 OTA zip, flash it on 4.2 OS and than just tap Setting>About>SoftwareUpdate. it went well. I countinuously updated that I can't even copy the 4.4 OTA zip file
samflorin said:
No. Apply it through stock recovery.
Click to expand...
Click to collapse
I mmanaged to get to 4.4.2 using the RUU.exe someone else posted, but i'll keep that in mind for future if i cant find a RUU
I wanted to GPE my HTC One m7. Having HBoot 1.57 made things a bit hard. I tried Moonshine, Revone, Firewater and Rumrunner, with no luck.
I decided I would pay for SunShine, but I needed a working system first. The various versions of the aforementioned tools were tested on a variety of roms and versions, which probably made this a real mess.
I ended up using this guide to get back to stock rom with stock recovery. (Apparently I am too noob to post links :-/ Here was a link to HTC1Guru "Reset to Stock for S-On")
It works. However, after applying the hotfix for a new system update, and rebooting, dowloading and installing the new update (4.4.3), I get stuck in a boot loop. My bootloader is unlocked, and I can flash a recovery. Booting up recovery while in this boot loop state gives me the phone with a red triangle warning sign on it.
My phone is S-On, HBoot 1.57, bought in Europe, using the *.*.401.* ROMs.
I've tried installing the stock 4.2.2 ROM twice and then applying update, no success. Any ideas on what I can do to get back to a stock phone, not in a boot loop?
Thanks in advance.
Sklirg said:
I wanted to GPE my HTC One m7. Having HBoot 1.57 made things a bit hard. I tried Moonshine, Revone, Firewater and Rumrunner, with no luck.
I decided I would pay for SunShine, but I needed a working system first. The various versions of the aforementioned tools were tested on a variety of roms and versions, which probably made this a real mess.
I ended up using this guide to get back to stock rom with stock recovery. (Apparently I am too noob to post links :-/ Here was a link to HTC1Guru "Reset to Stock for S-On")
It works. However, after applying the hotfix for a new system update, and rebooting, dowloading and installing the new update (4.4.3), I get stuck in a boot loop. My bootloader is unlocked, and I can flash a recovery. Booting up recovery while in this boot loop state gives me the phone with a red triangle warning sign on it.
My phone is S-On, HBoot 1.57, bought in Europe, using the *.*.401.* ROMs.
I've tried installing the stock 4.2.2 ROM twice and then applying update, no success. Any ideas on what I can do to get back to a stock phone, not in a boot loop?
Thanks in advance.
Click to expand...
Click to collapse
The reason it's bootlooping is because the updates that you are downloading are trying to update your hboot, but because you are already on the latest hboot they are failing.
Could you post your fastboot getvar all please without the imei and serial numbers please.
Seanie280672 said:
The reason it's bootlooping is because the updates that you are downloading are trying to update your hboot, but because you are already on the latest hboot they are failing.
Click to expand...
Click to collapse
That makes sense.
Seanie280672 said:
Could you post your fastboot getvar all please without the imei and serial numbers please.
Click to expand...
Click to collapse
Of course!
Code:
λ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
*snip*
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3956mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
Thanks
Sklirg said:
That makes sense.
Of course!
Code:
λ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
*snip*
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3956mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.077s
Thanks
Click to expand...
Click to collapse
Ok, first thing is first, you will need twrp 2.6.3.3 recovery on your phone, once that's done, push or sideload the Rom linked below, it's full stock Rom 6.09.401.12 so just one above yours, then flash it like any other Rom.
http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.12_odexed.zip
Seanie280672 said:
Ok, first thing is first, you will need twrp 2.6.3.3 recovery on your phone, once that's done, push or sideload the Rom linked below, it's full stock Rom 6.09.401.12 so just one above yours, then flash it like any other Rom.
Click to expand...
Click to collapse
Thank you! This worked wonders.
Sklirg said:
Thank you! This worked wonders.
Click to expand...
Click to collapse
Your welcome, that's what we're here for :good:
good day can you please help me with my problem. i was trying to a flash a custom ROM then then my M7 was stucked in the boot logo.
my hboot version 1.57.000 and flagged as ***TAMPERED*** and ***RELOCKED***. i have S-ON. and here's my getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35AW907688
(bootloader) imei: *********180157
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
your help will be very much appreciated.
thanks and more power
akoskiko99 said:
good day can you please help me with my problem. i was trying to a flash a custom ROM then then my M7 was stucked in the boot logo.
my hboot version 1.57.000 and flagged as ***TAMPERED*** and ***RELOCKED***. i have S-ON. and here's my getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35AW907688
(bootloader) imei: *********180157
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
your help will be very much appreciated.
thanks and more power
Click to expand...
Click to collapse
why is your bootloader relocked ? Unlock it if you want to flash and use Roms
clsA said:
why is your bootloader relocked ? Unlock it if you want to flash and use Roms
Click to expand...
Click to collapse
i've already unlocked my M7 using HTCDev but still i've encounted and error
c:\fastboot>fastboot flash zip c:\fastboot\firmware.zip
sending 'zip' (433840 KB)...
OKAY [ 18.603s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 18.840s
akoskiko99 said:
i've already unlocked my M7 using HTCDev but still i've encounted and error
c:\fastboot>fastboot flash zip c:\fastboot\firmware.zip
sending 'zip' (433840 KB)...
OKAY [ 18.603s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 18.840s
Click to expand...
Click to collapse
Now why are you flashing firmware ? the bootloader has to be relocked to flash firmware with s-on
You said you were flashing a rom / needs bootloader unlocked / custom recovery installed
flashing firmware / RUU needs bootloader relocked
clsA said:
Now why are you flashing firmware ? the bootloader has to be relocked to flash firmware with s-on
You said you were flashing a rom / needs bootloader unlocked / custom recovery installed
flashing firmware / RUU needs bootloader relocked
Click to expand...
Click to collapse
Looks to me mate like hes renamed the rom to firmware.zip and trying to flash it like firmware, hence the failed to parse Android info.
You can't flash it like that, you need to put the rom you downloaded on your internal storage and flash / install it from within twrp recovery.
clsA said:
why is your bootloader relocked ? Unlock it if you want to flash and use Roms
Click to expand...
Click to collapse
Seanie280672 said:
Looks to me mate like hes renamed the rom to firmware.zip and trying to flash it like firmware, hence the failed to parse Android info.
You can't flash it like that, you need to put the rom you downloaded on your internal storage and flash / install it from within twrp recovery.
Click to expand...
Click to collapse
how can i can put the stock rom in the internal storage if my phone stucked in the boot logo?
clsA said:
Now why are you flashing firmware ? the bootloader has to be relocked to flash firmware with s-on
You said you were flashing a rom / needs bootloader unlocked / custom recovery installed
flashing firmware / RUU needs bootloader relocked
Click to expand...
Click to collapse
hi clsA,
sorry if i confused, um so confused myself. again my apologies.
by this time, i've already unlocked the HBOOT using HTCdev
i've already installed TWRP to flash ROM
but the problem now is how can i transfer a stock rom to my M7 if it is stucked in the boot logo?
i hope i made myself clear to you.
thanks
akoskiko99 said:
hi clsA,
sorry if i confused, um so confused myself. again my apologies.
by this time, i've already unlocked the HBOOT using HTCdev
i've already installed TWRP to flash ROM
but the problem now is how can i transfer a stock rom to my M7 if it is stucked in the boot logo?
i hope i made myself clear to you.
thanks
Click to expand...
Click to collapse
TWRP 2.8.5.0 gives many options you can mount storage as mtp
usb otg
Sideload rom
Adb push
yatindroid said:
TWRP 2.8.5.0 gives many options you can mount storage as mtp
usb otg
Sideload rom
Adb push
Click to expand...
Click to collapse
i did it! man!! i was so close in giving up!!!...
thanks to all you who spent their time replying on my post.
clsA
Seanie
yatindroid
i forget the others. sorry.
Thank you very much!
I have an M7 which currently has cm10 installed and unlocked using HTC Dev. I can't S-OFF becuase the HBOOT is 1.61 (I've tried all methods apart from sunshine but they've failed)
The phone is currently locked to o2 uk, and i got an unlock code but aparrently these only work if the phone is stock.
I currently have cm10 installed, and i need to install a stock rom and relock.
I've tried flashing a RUU but no luck.
Currently have TWRP RECOVERY.
any help greatly appreciated!
charmander21 said:
I have an M7 which currently has cm10 installed and unlocked using HTC Dev. I can't S-OFF becuase the HBOOT is 1.61 (I've tried all methods apart from sunshine but they've failed)
The phone is currently locked to o2 uk, and i got an unlock code but aparrently these only work if the phone is stock.
I currently have cm10 installed, and i need to install a stock rom and relock.
I've tried flashing a RUU but no luck.
Currently have TWRP RECOVERY.
any help greatly appreciated!
Click to expand...
Click to collapse
O2 UK RUU is the 2nd one down in the list, instructions on how to flash it are a bit further up http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
By the way, HBOOT 1.61 (which is the Lollipop HBOOT) Sunshine is the only way to s-off this HBOOT, dont waste your time trying other methods, they will fail, and Sunshine also requires a stock rooted rom, so after flashing the rom linked above, just flash a custom recovery, root it by flashing SuperSU 2.46.zip and then download and run sunshine.......and the alternative, live with s-on.
Thanks, I tried this method but flashing the rom failed. THe process went on for several minutes then ended in this:
sending 'zip'... (368766 KB) OKAY
sending time = 15.457 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAIL12 signature verify fail
FAILED (remote: 12 signature verify fail)
Execution time is 421(s)
Now i can only boot into bootloader and not android.
after a couple of reboots i'm back into android. Thanks.
charmander21 said:
after a couple of reboots i'm back into android. Thanks.
Click to expand...
Click to collapse
theres 2 reasons why you got those error's
1. either you are s-on and didnt relock your bootloader first
or
2. you didnt use the recommended HTC_fastboot.exe from the instructions, the normal fastboot wont work, you need to use HTC's
just to be sure, could you post your fastboot getvar all without imei and serial number please.
I did make sure to follow the instructions, i've double checked them and I did follow allt he steps including using htc's fast boot. Here are the results from getvar all
c:\fastboot>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.18.206.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3839mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4deaef41
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.168s
Note i am currently on insertcoin, not the o2 RUU.
charmander21 said:
I did make sure to follow the instructions, i've double checked them and I did follow allt he steps including using htc's fast boot. Here are the results from getvar all
c:\fastboot>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.18.206.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3839mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4deaef41
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.168s
Note i am currently on insertcoin, not the o2 RUU.
Click to expand...
Click to collapse
doesnt matter which rom your already on, it doesnt change the firmware, and you are already on the latest firmware 7.18.206.2, that RUU.zip should work fine, maybe there is a problem with the RUU.
there is a stock nandroid here: https://www.androidfilehost.com/?fid=95916177934549269 which you can restore through twrp recovery if you want to get back to full stock.
Hi guys i had problem, few days ago phone notify me about update, i thought ok it nice, I restored stock recovery and I relocked bootloader in fastboot.
I clicked the install , process ran without errors. in stock recovery and BANG 3-4 first times phone stopped on boot, i tried factory reset after boot phone giving me black screen, next I tried to flash RUU's.
Before update a I had 7.19.401.22, i flashed this version - not working, flashed 7.19.401.2 - not working, flashed 7.19.401.30 - not working although it ,the same version is after update.
I don't know what to do :crying:
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.19.401.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37RW902282
(bootloader) imei: xxxxxxxxxxxxxxx
(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: 3730mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Flashed RUU's
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.30_Radio_4T.35.3218.16_10.33Q.1718.01L_release_449611_combined_signed.zip
Jakqa said:
Hi guys i had problem, few days ago phone notify me about update, i thought ok it nice, I restored stock recovery and I relocked bootloader in fastboot.
I clicked the install , process ran without errors. in stock recovery and BANG 3-4 first times phone stopped on boot, i tried factory reset after boot phone giving me black screen, next I tried to flash RUU's.
Before update a I had 7.19.401.22, i flashed this version - not working, flashed 7.19.401.2 - not working, flashed 7.19.401.30 - not working although it ,the same version is after update.
I don't know what to do :crying:
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.19.401.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37RW902282
(bootloader) imei: xxxxxxxxxxxxxxx
(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: 3730mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Flashed RUU's
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.22_Radio_4T.35.3218.16_10.33Q.1718.01L_release_430964_signed.zip
PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.30_Radio_4T.35.3218.16_10.33Q.1718.01L_release_449611_combined_signed.zip
Click to expand...
Click to collapse
The ota caused a bootloop because you have installed it on a rooted phone. Unlike older updates (6.xx.xxx.x and before), you can't simply reflash the stock recovery to update. Lollipop updates can only be installed on 100% stock and non-rooted rom. That wasn't a problem in the past but its now a well know problem with all newer updates.
Your version-main is now 7.19.401.30 because, unlike the software, the firmware updated fine. You can't flash the 7.19.401.22 RUU because its now a downgrade in version (because your firmware got updated). Downgrading using a RUU requires S-OFF, your phone is S-ON. Same reason why the 7.19.401.2 won't work.
7.19.401.30 ruu is a "combined" RUU so it can't be flashed on a s-on phone.
Your option are:
unlock the bootloader, flash twrp recovery and flash a rom
or achieve s-off using sunshine and flash the .22 or the .30 ruu (you'll need to do option 1 first because you need a working rom to be able to s-off the phone)
Or maybe someone already uploaded a nandroid backup of 7.19.401.30. If you find one you can restore the backup using a custom recovery and then reflash the stock recovery.
alray said:
The ota caused a bootloop because you have installed it on a rooted phone. Unlike older updates (6.xx.xxx.x and before), you can't simply reflash the stock recovery to update. Lollipop updates can only be installed on 100% stock and non-rooted rom. That wasn't a problem in the past but its now a well know problem with all newer updates.
Your version-main is now 7.19.401.30 because, unlike the software, the firmware updated fine. You can't flash the 7.19.401.22 RUU because its now a downgrade in version (because your firmware got updated). Downgrading using a RUU requires S-OFF, your phone is S-ON. Same reason why the 7.19.401.2 won't work.
7.19.401.30 ruu is a "combined" RUU so it can't be flashed on a s-on phone.
Your option are:
unlock the bootloader, flash twrp recovery and flash a rom
or achieve s-off using sunshine and flash the .22 or the .30 ruu (you'll need to do option 1 first because you need a working rom to be able to s-off the phone)
Or maybe someone already uploaded a nandroid backup of 7.19.401.30. If you find one you can restore the backup using a custom recovery and then reflash the stock recovery.
Click to expand...
Click to collapse
1.What Kind of rom? Stock or custom - without s-off?
3.Do You know anyone who could upload a backup of 7.19.401.30?
Jakqa said:
1.What Kind of rom? Stock or custom - without s-off?
3.Do You know anyone who could upload a backup of 7.19.401.30?
Click to expand...
Click to collapse
1.a stock or stockish rom is best if you want to achieve s-off, You don't need s-off to flash a custom rom, only an unlocked bootloader + a custom recovery.
3. No, might want to ask in the update thread in the general section (see sticky threads)