Related
Hi
i have HTC ONE GPE and i tried to downgrade the HBOOT
from 1.54 to 1.44 to change the CID but all my tries fail
can any one help me with this problem
irooon said:
Hi
i have HTC ONE GPE and i tried to downgrade the HBOOT
from 1.54 to 1.44 to change the CID but all my tries fail
can any one help me with this problem
Click to expand...
Click to collapse
If all you need to do is change your cid, you don't need to downgrade HBOOT. Just use the rumrunner technique to S-off (if you're not already) found here, and you should be fine.
kibmikey1 said:
If all you need to do is change your cid, you don't need to downgrade HBOOT. Just use the rumrunner technique to S-off (if you're not already) found here, and you should be fine.
Click to expand...
Click to collapse
i think GPE (Google play edition) no need S-off
if u know how just tell me
Sent from my HTC One using XDA Premium HD app
still waiting any answer
Sent from my GT-I9505 using XDA Premium HD app
irooon said:
still waiting any answer
Sent from my GT-I9505 using XDA Premium HD app
Click to expand...
Click to collapse
No, you need s-off to make those sorts of changes
rider5512 said:
No, you need s-off to make those sorts of changes
Click to expand...
Click to collapse
i know no need for s-off but I'm still searching for the right HBOOT 1.44 i try three HBOOT and all give me error 'remote 99'
Sent from my HTC One using XDA Premium HD app
S-OFF IS REQUIRED TO DOWNGRADE.
Sent with pigeons.
how can i make s-off for googl play edition ?
Sent from my HTC One using XDA Premium HD app
i try too many HBOOT and the result is remote error and i modified the zip file to my phone id and all result is same plz anyone help
C:\Program Files\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip hboot_hexed_m7_wls.
zip
target reported max download size of 1526722560 bytes
sending 'zip' (485 KB)...
OKAY [ 0.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 0.484s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip hboot_hexed_m7_wls.
zip
target reported max download size of 1526722560 bytes
sending 'zip' (485 KB)...
OKAY [ 0.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 0.484s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip hboot_hexed_m7roger
s.zip
target reported max download size of 1526722560 bytes
sending 'zip' (485 KB)...
OKAY [ 0.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 0.484s
Click to expand...
Click to collapse
I can't post links since I'm a new member, but....
Google Search: "How to Convert Your Google Play Edition HTC One into an HTC One with Sense & No Bloat"
search results should be from htc-one.wonderhowto
Step 2 tells you how to get hboot 1.44
It's probably your android.txt that is incorrect. Your MID (Model ID) has to match the one in the txt file.
irooon said:
i try too many HBOOT and the result is remote error and i modified the zip file to my phone id and all result is same plz anyone help
Click to expand...
Click to collapse
1- you NEED to be S-Off
2- why would you want to flash a Sprint hboot "hboot_hexed_m7_wls.zip" on your device
jambamochi said:
I can't post links since I'm a new member, but....
Google Search: "How to Convert Your Google Play Edition HTC One into an HTC One with Sense & No Bloat"
search results should be from htc-one.wonderhowto
Step 2 tells you how to get hboot 1.44
It's probably your android.txt that is incorrect. Your MID (Model ID) has to match the one in the txt file.
Click to expand...
Click to collapse
I'm doing all the steps and i change the MID on the HBOOT and all give me the same result
nkk71 said:
1- you NEED to be S-Off
2- why would you want to flash a Sprint hboot "hboot_hexed_m7_wls.zip" on your device
Click to expand...
Click to collapse
i try too many HBOOT to downgrade and i think for the HTC ONE GOOGLE PLAY EDITION no need for s-off
irooon said:
i try too many HBOOT to downgrade and i think for the HTC ONE GOOGLE PLAY EDITION no need for s-off
Click to expand...
Click to collapse
OK, maybe I should say it again, YOU CANNOT FLASH OR DOWNGRADE AN HBOOT (ESPECIALLY A HEX-EDITED UNSIGNED HBOOT) with S-ON.
Whether you have a HTC One M7_U, M7_UL, M7_WLS, M7 etc. etc. etc. running GPe, Sense, iOS, Ubuntu, Windows, or anything else you can think of.
Just go get S-Off and then you can flash whatever you want. And when/if you do, do some reading before you have a total brick on your hands.
Sorry if that sounds rude, but this is the fact.
nkk71 said:
OK, maybe I should say it again, YOU CANNOT FLASH OR DOWNGRADE AN HBOOT (ESPECIALLY A HEX-EDITED UNSIGNED HBOOT) with S-ON.
Whether you have a HTC One M7_U, M7_UL, M7_WLS, M7 etc. etc. etc. running GPe, Sense, iOS, Ubuntu, Windows, or anything else you can think of.
Just go get S-Off and then you can flash whatever you want. And when/if you do, do some reading before you have a total brick on your hands.
Sorry if that sounds rude, but this is the fact.
Click to expand...
Click to collapse
i already open the bootloader and root my device but i didn't see any one say that i should make s-off for the Google play edition any way if u know hot to do it just give me hint or link
and many thanks to ur replay
jambamochi said:
I can't post links since I'm a new member, but....
Google Search: "How to Convert Your Google Play Edition HTC One into an HTC One with Sense & No Bloat"
search results should be from htc-one.wonderhowto
Step 2 tells you how to get hboot 1.44
It's probably your android.txt that is incorrect. Your MID (Model ID) has to match the one in the txt file.
Click to expand...
Click to collapse
C:\Program Files\Minimal ADB and Fastboot>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar modelid
modelid: PN0712000
finished. total time: 0.000s
C:\Program Files\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash zip orig_hboot_1.44.000
0_M7_RUUmode.zip
target reported max download size of 1526722560 bytes
sending 'zip' (486 KB)...
OKAY [ 0.234s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 0.484s
Click to expand...
Click to collapse
i try it again to show u the result and i change the mid in the HBOOT info and zip it again and i flash it same result
irooon said:
i try it again to show u the result and i change the mid in the HBOOT info and zip it again and i flash it same result
Click to expand...
Click to collapse
Won't work with S-On. Don't waste you're time.
irooon said:
i already open the bootloader and root my device but i didn't see any one say that i should make s-off for the Google play edition any way if u know hot to do it just give me hint or link
and many thanks to ur replay
Click to expand...
Click to collapse
Check http://rumrunner.us it has packages for GPe 3.06.1700.10 and GPe 3.07.1700.10
EDIT: read and follow instructions to the letter!
Hit the thanks button if I helped
nkk71 said:
Won't work with S-On. Don't waste you're time.
Check http://rumrunner.us it has packages for GPe 3.06.1700.10 and GPe 3.07.1700.10
EDIT: read and follow instructions to the letter!
Hit the thanks button if I helped
Click to expand...
Click to collapse
==================== rumrunner S-OFF 0.1.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ---
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (5/120)
Waiting
[PN0712000-1.54.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (9/120)
Device detected.....................
[------------------------------------------------------------]
Test 3: Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: **** it
Click to expand...
Click to collapse
see what happen
irooon said:
see what happen
Click to expand...
Click to collapse
just a hunch, but do you have fastboot drivers installed?
yes and i unlock the bootloader and root the device
Sent from my GT-I9505 using XDA Premium HD app
Can this be done? I got a Google Play Edition phone and decided I do not like stock Android on this phone. I would like it to be basically a stock developer's edition with Sense and all with working OTAs. Not really familiar with HTC stuff coming from Samsung. My HBOOT is 1.54 and it is S-ON. Can I do what I want?
hjjfffaa said:
Can this be done? I got a Google Play Edition phone and decided I do not like stock Android on this phone. I would like it to be basically a stock developer's edition with Sense and all with working OTAs. Not really familiar with HTC stuff coming from Samsung. My HBOOT is 1.54 and it is S-ON. Can I do what I want?
Click to expand...
Click to collapse
I think you can do that if you get S-Off (use a tool called Rumrunner) and change your CID so you can flash the appropriate RUU. But why stock? The customized ROMs are so much more interesting.
fenstre said:
I think you can do that if you get S-Off (use a tool called Rumrunner) and change your CID so you can flash the appropriate RUU. But why stock? The customized ROMs are so much more interesting.
Click to expand...
Click to collapse
So if I S-Off can I S-On? I think I read somewhere that was required for OTAs to work. I want stock just for the reliability and hassle free nature of it.
hjjfffaa said:
So if I S-Off can I S-On? I think I read somewhere that was required for OTAs to work. I want stock just for the reliability and hassle free nature of it.
Click to expand...
Click to collapse
Oh, I don't know about that. The rumrunner forum post said they don't really know what happens if you S-On after S-Offing, and that you might not be able to S-Off again. I wouldn't chance it.
fenstre said:
Oh, I don't know about that. The rumrunner forum post said they don't really know what happens if you S-On after S-Offing, and that you might not be able to S-Off again. I wouldn't chance it.
Click to expand...
Click to collapse
But I can downgrade to 1.44 and that would allow me to S-On and get OTA updates right? Or am I totally wrong?
Okay so I've unlocked the bootloader, S-OFF'd, changed to superCID, relocked and tried to run the RUU.exe. I keep getting Error 155: UNKNOWN ERROR. Not sure what to do here. I've also tried using the CID BS_US001 and also some combinations involving an unlocked bootloader. All the same error.
hjjfffaa said:
Okay so I've unlocked the bootloader, S-OFF'd, changed to superCID, relocked and tried to run the RUU.exe. I keep getting Error 155: UNKNOWN ERROR. Not sure what to do here. I've also tried using the CID BS_US001 and also some combinations involving an unlocked bootloader. All the same error.
Click to expand...
Click to collapse
You have S-off which is good. I'm going to ask you to use the BS_US001 CID. Try downloading the 1.29.1540.17 zip from HTC Dev. Do a fastboot oem rebootRUU and flash the zip from there. It should prompt you to do this twice.
Sent from my HTC One using XDA Premium 4 mobile app
Okay I have changed back to the BS_US001 CID, bootloader is still re-locked. I am downloading the 1.29.1540.17.zip right now, it'll be done in 50 minutes.
hjjfffaa said:
Okay I have changed back to the BS_US001 CID, bootloader is still re-locked. I am downloading the 1.29.1540.17.zip right now, it'll be done in 50 minutes.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2497712
You can follow that thread if you want to set the phone to locked.
I'm sorry I forgot about the 4.3 zip, use that one if you want to go straight to 4.3. Again, my apologies
Sent from my HTC One
I don't care if it says re-locked (so long as it functions how it should), I just want my Sense ROM. I already have the 4.3 Dev Edition zip, should I try flashing it with fastboot?
I tried flashing the 3.22.1540.1 zip and got this problem, which doesn't seem consistent with the one guide I've seen for this process.
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1133421 KB)...
OKAY [ 53.663s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
finished. total time: 60.625s
Click to expand...
Click to collapse
Try 'fastboot erase cache' and 'fastboot reboot-bootloader' before you 'fastboot oem rebootruu' and then run the fastboot flash zip filename.zip'
Sent from my HTC One
The results:
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot erase
cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.065s]
finished. total time: 0.065s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot reboo
t-bootloader
rebooting into bootloader...
OKAY [ 0.037s]
finished. total time: 0.038s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot oem r
ebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.050s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1133421 KB)...
OKAY [ 53.359s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
finished. total time: 60.318s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Click to expand...
Click to collapse
Could this be a result of the 1.54 bootloader?
hjjfffaa said:
The results:
Could this be a result of the 1.54 bootloader?
Click to expand...
Click to collapse
Can you take an image of your bootloader for me real quick
gusto5 said:
Can you take an image of your bootloader for me real quick
Click to expand...
Click to collapse
Here you go.
hjjfffaa said:
Here you go.
Click to expand...
Click to collapse
As far as I can tell you have met all the criteria for running the RUU, I'm not sure why you're running into this. My last suggestion is to try a different USB port. Hopefully someone else will chime in on this if that (which i don't imagine will) does anything at all.
gusto5 said:
As far as I can tell you have met all the criteria for running the RUU, I'm not sure why you're running into this. My last suggestion is to try a different USB port. Hopefully someone else will chime in on this if that (which i don't imagine will) does anything at all.
Click to expand...
Click to collapse
Thanks for all your help. Trying a different USB port.
You were right, it did nothing.
hjjfffaa said:
The results:
Could this be a result of the 1.54 bootloader?
Click to expand...
Click to collapse
You may be right. Let's have you downgrade the Bootloader to 1.44 and then try running the RUU again.
Just remember that you already have the right MID and CID. CID you changed yourself, MID already matches as the Google Play Edition shares the same MID as the Developer edition (and a few other North American HTC Ones).
Here are the (real) results:
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot oem r
ebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.049s]
finished. total time: 0.049s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>fastboot flash
zip hbootRUU.zip
target reported max download size of 1526722560 bytes
sending 'zip' (508 KB)...
OKAY [ 0.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 0.516s
D:\Android SDK\adt-bundle-windows-x86-20131030\sdk\platform-tools>
Click to expand...
Click to collapse
In 'android-info' I modified to the MID to match mine. Do I need to add the CID to this in order to have it work? I noticed there was not BS_US001 CID listed inside.
hjjfffaa said:
Here are the results:
In 'android-info' I modified to the MID to match mine. Do I need to add the CID to this in order to have it work? I noticed there was not BS_US001 CID listed inside.
Click to expand...
Click to collapse
For this part, and the ruu cid 11111111 might be more effective.
Sent from my Nexus 7 using XDA Premium 4 mobile app
gusto5 said:
For this part, and the ruu cid 11111111 might be more effective.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
All right, should I add it to the android-text file though?
Hello,
can i install every RUU on a HTC One with SuperCID 11111111?
Thanks
Mr.Nieto said:
Hello,
can i install every RUU on a HTC One with SuperCID 11111111?
Thanks
Click to expand...
Click to collapse
If you have a gsm htc one then yes, you would need to change android-info.txt to match cid number.
Mr.Nieto said:
Hello,
can i install every RUU on a HTC One with SuperCID 11111111?
Thanks
Click to expand...
Click to collapse
wrong forum... ask in Q & A :good:
passion8059 said:
If you have a gsm htc one then yes, you would need to change android-info.txt to match cid number.
Click to expand...
Click to collapse
Hi. Where is that android-info.txt? When i download RUU files they're .exe Files...
Is it required to have bootloader unlocked to install a RUU?
Thread Moved to Q&A, Help & Troubleshooting forum.
As a future reference, all questions get posted in Q&A, NOT development. Even if you have a development related question in future, it still belongs in Q&A.
Regards,
- KidCarter93
Forum Moderator
Mr.Nieto said:
Hi. Where is that android-info.txt? When i download RUU files they're .exe Files...
Is it required to have bootloader unlocked to install a RUU?
Click to expand...
Click to collapse
SuperCID will not allow you to install "Any" RUU
The MID must also match your phone and you must lock the bootloader before running the RUU
your brightstar RUU failed because the MID mismatch
also post a fastboot getvar all without imei/sn
clsA said:
SuperCID will not allow you to install "Any" RUU
The MID must also match your phone and you must lock the bootloader before running the RUU
Click to expand...
Click to collapse
Here is the getvar all result:
version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.63.161.6
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: 11111111
battery-status: good
battery-voltage: 4288mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-ea0bccbd
hbootpreupdate: 11
gencheckpt: 0
I got the follwing info in my bootloader:
****TAMPERED***
***RELOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT 1.55.0000
RADIO 4A-21.3263.04
What can i do now? I want a stock Google Play ROM or HTC Stock ROM on my phone...
Mr.Nieto said:
Hi. I got the follwing info in my bootloader:
****TAMPERED***
***RELOCKED***
M7_UL PVT SHIP S-ON RH
HBOOT 1.55.0000
RADIO 4A-21.3263.04
What can i do now? I want a stock Google Play ROM on my phone...
Click to expand...
Click to collapse
First you have to get s-off
use rumrunner or firewater to get S-Off: http://firewater-soff.com/ or http://rumrunner.us/
Fast and easy way to GPE is here
http://forum.xda-developers.com/showthread.php?t=2356654
clsA said:
First you have to get s-off
use rumrunner or firewater to get S-Off: http://firewater-soff.com/ or http://rumrunner.us/
Fast and easy way to GPE is here
http://forum.xda-developers.com/showthread.php?t=2356654
Click to expand...
Click to collapse
Yes, i already done that before i did S-ON again...
After that i got to change the CID?
For the GPE you have posted i dont need a S-OFF, right?
Mr.Nieto said:
Yes, i already done that before i did S-ON again...
After that i got to change the CID?
For the GPE you have posted i dont need a S-OFF, right?
Click to expand...
Click to collapse
why did you go s-on ?
it's much easier if your s-off with any GPE
what recovery do you use ?
clsA said:
why did you go s-on ?
it's much easier if your s-off with any GPE
what recovery do you use ?
Click to expand...
Click to collapse
I currently got no recovery but i install TWRP...
Why S-OFF? I have heard that is very insecure...
Mr.Nieto said:
I currently got no recovery but i install TWRP...
Why S-OFF? I have heard that is very insecure...
Click to expand...
Click to collapse
good .. install TWRP 2.6.3.3 and use the ARHD GPE you'll love it it's very refined
clsA said:
good .. install TWRP 2.6.3.3 and use the ARHD GPE you'll love it it's very refined
Click to expand...
Click to collapse
So now i try to unlock my device again and it says:
target reported max download size of 1512640512 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.146s
even when i try to install TWRP it says:
target reported max download size of 1512640512 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.161s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.889s
What happened?
Mr.Nieto said:
So now i try to unlock my device again and it says:
target reported max download size of 1512640512 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.146s
even when i try to install TWRP it says:
target reported max download size of 1512640512 bytes
sending 'recovery' (9184 KB)...
OKAY [ 1.161s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.889s
What happened?
Click to expand...
Click to collapse
probably because your s-on relocked and SuperCID
@SaHiLzZ @nkk71
is their anything he can do ?
clsA said:
probably because your s-on relocked and SuperCID
Click to expand...
Click to collapse
What can i do now?
Can you generate a NEW unlock token from htcdev website. ?
sent from my mobile device
SaHiLzZ said:
Can you generate a NEW unlock token from htcdev website. ?
sent from my mobile device
Click to expand...
Click to collapse
That worked, thanks! Now i try to install TWRP...
Hold on. WHAT is your final goal?
sent from my mobile device
Installing TWRP worked too! Very nice! Thanks!
Got a question... i am currently able to S-OFF and change CID...
What is required to install the RUU
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
Do i need to set the CID to a special One? And what is required too for that step? Is that possible?
SaHiLzZ said:
Hold on. WHAT is your final goal?
sent from my mobile device
Click to expand...
Click to collapse
My first goal is to install RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
I want a stock rom from HTC on my device... when that isnt possible i install the GPE Custom ROM
Hi all,
Several months ago I have converted my HTC One M7 to GPE.
Now I need to return back to stock. I have followed the (quite simple) guide that I found in this forum but I don't seem able to reach my goal.
I need an helping hand so bad.
This is what I have tried so far:
- Changed my CID from GOOGL001 to HTC__001 (OK)
- Re-Locked my bootloader.
- Recovery is GPE stock. ROM is GPE stock (4.4.4)
- Executed "fastboot oem rebootRUU" and then
- fastboot flash zip ruu.zip (where ruu.zip is the full stock, Wipe ZIP 6.06.401.1 rom taken from here: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
- Issued the above command twice, as usual.
After rebooting my device, the HTC logo (powered by Android) appears followed by the old Google Edition animation (ie: 4 colored spinning circles).
The phone seams to remain stuck at this point.
I have restored the GPE Rom and everything seems to be perfectly working.
Tried the above steps twice then finally gave up.
Has anybody here managed to revert his device from GPE to WWE Sense (.401.) ?
Any clues please?
Thanks a lot.
slvrbllt said:
Hi all,
Several months ago I have converted my HTC One M7 to GPE.
Now I need to return back to stock. I have followed the (quite simple) guide that I found in this forum but I don't seem able to reach my goal.
I need an helping hand so bad.
This is what I have tried so far:
- Changed my CID from GOOGL001 to HTC__001 (OK)
- Re-Locked my bootloader.
- Recovery is GPE stock. ROM is GPE stock (4.4.4)
- Executed "fastboot oem rebootRUU" and then
- fastboot flash zip ruu.zip (where ruu.zip is the full stock, Wipe ZIP 6.06.401.1 rom taken from here: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
- Issued the above command twice, as usual.
After rebooting my device, the HTC logo (powered by Android) appears followed by the old Google Edition animation (ie: 4 colored spinning circles).
The phone seams to remain stuck at this point.
I have restored the GPE Rom and everything seems to be perfectly working.
Tried the above steps twice then finally gave up.
Has anybody here managed to revert his device from GPE to WWE Sense (.401.) ?
Any clues please?
Thanks a lot.
Click to expand...
Click to collapse
wel if I read your post right, all you have flashed is the 401 firmware, you've not actually flashed the 401 rom or RUU, so all you changed was the firmware, the link you supplied is firmwares and HBOOT only, its not rom's
slvrbllt said:
Hi all,
Several months ago I have converted my HTC One M7 to GPE.
Now I need to return back to stock. I have followed the (quite simple) guide that I found in this forum but I don't seem able to reach my goal.
I need an helping hand so bad.
This is what I have tried so far:
- Changed my CID from GOOGL001 to HTC__001 (OK)
- Re-Locked my bootloader.
- Recovery is GPE stock. ROM is GPE stock (4.4.4)
- Executed "fastboot oem rebootRUU" and then
- fastboot flash zip ruu.zip (where ruu.zip is the full stock, Wipe ZIP 6.06.401.1 rom taken from here: https://docs.google.com/spreadsheets/d/1LQDLpVZYyUpXPgC2sh1BvAS9Oo8B-fTiZU_JhpIH-fU/pubhtml#
- Issued the above command twice, as usual.
After rebooting my device, the HTC logo (powered by Android) appears followed by the old Google Edition animation (ie: 4 colored spinning circles).
The phone seams to remain stuck at this point.
I have restored the GPE Rom and everything seems to be perfectly working.
Tried the above steps twice then finally gave up.
Has anybody here managed to revert his device from GPE to WWE Sense (.401.) ?
Any clues please?
Thanks a lot.
Click to expand...
Click to collapse
change cid to htc__001 and if required, your MID to PN0710000
no need to relock bootloader when s-off
flash the appropriate ruu.zip or .exe, there is no 6.06.401 ruu.
reboot phone and enjoy
if you return back to stock for warranty purpose you will need to set back the bootloader to "locked" not "relocked"and remove the tampered flag before running the ruu.
for more information check nkk71 guide linked in my signature.
list of ruu for your phone:
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
dont use the 1.20.401.1 ruu, its a pre-release version with no ota updates.
Seanie280672 said:
wel if I read your post right, all you have flashed is the 401 firmware, you've not actually flashed the 401 rom or RUU, so all you changed was the firmware, the link you supplied is firmwares and HBOOT only, its not rom's
Click to expand...
Click to collapse
I didn't realise that it was just the firmware.
alray said:
[...] omissis [...]
Click to expand...
Click to collapse
I will try to flash the exe you have linked as soon as I get back from my holidays.
Thank you guys! I've really appreciated your help.
I'm gonna make things easy. Ive used this method twice for returning to stock, as ive had to return my phone for issues twice. I guarentee that it works. youtube.c om/watch?v=uEBAKSDxbkI. This is 100% stock. :highfive:
Mickey Meyers said:
I'm gonna make things easy. Ive used this method twice for returning to stock, as ive had to return my phone for issues twice. I guarentee that it works. youtube.c om/watch?v=uEBAKSDxbkI. This is 100% stock. :highfive:
Click to expand...
Click to collapse
and that's the easy way ?........lol, took him 10 mins to lock his bootloader, the easy way is to reboot to your bootloader and type fastboot oem lock, 2 seconds its done, that applies to firmware flashes, ruu flash commands and then to s-on too.
alray said:
change cid to htc__001 and if required, your MID to PN0710000
no need to relock bootloader when s-off
flash the appropriate ruu.zip or .exe, there is no 6.06.401 ruu.
reboot phone and enjoy
if you return back to stock for warranty purpose you will need to set back the bootloader to "locked" not "relocked"and remove the tampered flag before running the ruu.
for more information check nkk71 guide linked in my signature.
Click to expand...
Click to collapse
I'm back and so are my issues.
Following your suggestions I have downloaded the following RUU:
RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
Despite I'm S-OFF, I usually keep my bootloader (re)locked for safety reasons.
My bootloader screen shows:
Code:
M7_UL PVT SHIP S-OFF RH
CID-HTC__001
HBOOT-1.54.0000
RADIO-4T.27.3218.09
OpenDSP-v32.120.274.0909
OS-4.09.1700.1
eMMC-boot 2048MB
Jun 16 2014,20:13:15.8
As you can see I have already changed my CID.
When I launch the exe it start trying to flash but I immediately get an Error 158 and it quits.
I extracted the rom.zip from the file and tried the fastboot method.
This is what I get upon executing the command:
Code:
fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
[b]Invalid sparse file format at header magi[/b]
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
sending sparse 'zip' (1490936 KB)...
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
OKAY [ 61.513s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 61.715s
Did anybody run into similar issues before?
Any help would be pretty much appreciated.
Thanks, guys.
slvrbllt said:
I'm back and so are my issues.
Following your suggestions I have downloaded the following RUU:
RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe
Despite I'm S-OFF, I usually keep my bootloader (re)locked for safety reasons.
My bootloader screen shows:
Code:
M7_UL PVT SHIP S-OFF RH
CID-HTC__001
HBOOT-1.54.0000
RADIO-4T.27.3218.09
OpenDSP-v32.120.274.0909
OS-4.09.1700.1
eMMC-boot 2048MB
Jun 16 2014,20:13:15.8
As you can see I have already changed my CID.
When I launch the exe it start trying to flash but I immediately get an Error 158 and it quits.
I extracted the rom.zip from the file and tried the fastboot method.
This is what I get upon executing the command:
Code:
fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
[b]Invalid sparse file format at header magi[/b]
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
sending sparse 'zip' (1490936 KB)...
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 80250270 is not a multiple of the block size 4096
OKAY [ 61.513s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) shift signature_size for header checking...
FAILED (remote: 32 header error)
finished. total time: 61.715s
Did anybody run into similar issues before?
Any help would be pretty much appreciated.
Thanks, guys.
Click to expand...
Click to collapse
use the 1.28.401.7 ruu.zip, there are some issues with 4.x ruus. Do not flash it using a windows 8.1 computer
alray said:
use the 1.28.401.7 ruu.zip, there are some issues with 4.x ruus. Do not flash it using a windows 8.1 computer
Click to expand...
Click to collapse
Well, guess what ?
Code:
target reported max download size of 1526722560 bytes
sending 'zip' (1009784 KB)...
OKAY [ 37.420s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail
Please check if you flash part)
finished. total time: 42.758s
I've also tried with super CID but got the same results.
Any other hints ?
slvrbllt said:
Well, guess what ?
Code:
target reported max download size of 1526722560 bytes
sending 'zip' (1009784 KB)...
OKAY [ 37.420s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 22 loading zip info fail
Please check if you flash part)
finished. total time: 42.758s
I've also tried with super CID but got the same results.
Any other hints ?
Click to expand...
Click to collapse
How about trying a Guru Reset 5.11.401.10 you will have to unlock your bootloader and put TWRP back on your phone to flash it. It should take you back to stock and at the end it will ask you if you want to root. If you want to go complete stock just select the no option.
majmoz said:
How about trying a Guru Reset 5.11.401.10
Click to expand...
Click to collapse
I will.
But wasn't I supposed to flash any RUU I like given I'm S-OFF ?!?!
I would like to figure out why my device isn't flashing the stock ruu at all...
slvrbllt said:
Well, guess what ?
Code:
target reported max download size of 1526722560 bytes
[B][COLOR="Red"]sending 'zip' (1009784 KB)...[/COLOR][/B]
Any other hints ?[/QUOTE]
you should have checked MD5, the actual filesize is 1009792KB
here's an AFH mirror: [URL="https://www.androidfilehost.com/?fid=23329332407584993"]RUU Zip M7_UL_JB_50_HTC_Europe_1.28.401.7[/URL]
Click to expand...
Click to collapse
nkk71 said:
you should have checked MD5, the actual filesize is 1009792KB]
Click to expand...
Click to collapse
You're right! I extracted the rom.zip from the ruu but did not decrypted it.
The one you have suggested worked fine.
I'm back stock now.
Thank you everybody for your help.
PS: On a side note, GURU reset saved me from the hassle of going through all the updates from 1.28.401.7 up to 6.09.401.5.
Cheers
slvrbllt said:
PS: On a side note, GURU reset saved me from the hassle of going through all the updates from 1.28.401.7 up to 6.09.401.5.
Cheers
Click to expand...
Click to collapse
you mean after you downgraded using ruu 1.28.401.7, you flashed a newer Guru Reset ROM, and took OTAs after that?
I'm glad it worked for you, but I would highly recommend against that, because the firmware upgrades (within the OTAs) are incremental, so skipping versions could potentially miss important upgrades within the firmwares, or even worse send you into QHSUSB_DLOAD mode
eg, assuming you installed a 4.xx Guru Reset ROM, and took OTA update to 5.xx, then there's a high chance you would have ended in QHSUSB_DLOAD mode, because the 5.xx firmware (inside the OTA) is missing SBL3
nkk71 said:
you mean after you downgraded using ruu 1.28.401.7, you flashed a newer Guru Reset ROM, and took OTAs after that?
Click to expand...
Click to collapse
Well, after having flashed 1.28.401.7 (I was on latest GPE before), it started downloading a few OTAs (if I recall well, I applied all otas up to version 2.x).
It took me 1.5hrs to get to this point, so I gave up and installed the Guru Reset 5.11.401.10 instead.
Upon reboot it downloaded the latest OTA and jumped straight to 6.09.401.5.
The smartphone seems to be working fine. How can I be sure that all the required pieces are in place?
I was using the latest Viper Rom and my Camera busted on my phone. So naturally I needed to get the M7 back to stock. I have never done it before so I did some searching and found the method right in this same forum.
So Walking through the instructions everything went well
I locked the bootloader
went through the process of flashing the stock rom with fastboot and it keeps erroring out. I am consistently getting "FAILED (status read failed (Too many links))" I tried the RUU and I keep getting unknown errors from those too. I have tried multiple PC and different usb cables and ports. I am completely stumped.
I was under the impression that it didn't matter which stock ROM you tried but I did try many different ones.
Would anyone have any suggestions?
I'm not sure what RUU guide you used, but I and a few others have had success with the guide I wrote. Try it and follow up here or in that thread if you have issues (or if it worked for you).
http://forum.xda-developers.com/spr...de-reset-phone-using-ruu-htcfastboot-t2876110
Thanks for the links and the response. I followed your step to a tee and got to step 6 and tried to flash the firmware. I am s-off and when I pushed the firmware o am now getting;
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830
Any suggestions?
Thanks again for your help.
Just another thing I noticed with your guide
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
s-off means the bootloader is unlocked and s-on means that it is locked. so your instructions are a little unclear. I am assuming that you meant that you need the bootloader locked.
On a whim I unlocked my bootloader again using fastboot and my BIN file and my phone did finally boot back to the Viper rom instead of being stuck on the Bootloader screen. I am curious why going s-on is making the phone fail and soft bricking the phone. Maybe my HBOOT is wrong? Could my Twerk recovery corrupted HBOOT?
Thanks again for your help!
raremind said:
Thanks for the links and the response. I followed your step to a tee and got to step 6 and tried to flash the firmware. I am s-off and when I pushed the firmware o am now getting;
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830
Any suggestions?
Thanks again for your help.
Click to expand...
Click to collapse
raremind said:
Just another thing I noticed with your guide
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
s-off means the bootloader is unlocked and s-on means that it is locked. so your instructions are a little unclear. I am assuming that you meant that you need the bootloader locked.
On a whim I unlocked my bootloader again using fastboot and my BIN file and my phone did finally boot back to the Viper rom instead of being stuck on the Bootloader screen. I am curious why going s-on is making the phone fail and soft bricking the phone. Maybe my HBOOT is wrong? Could my Twerk recovery corrupted HBOOT?
Thanks again for your help!
Click to expand...
Click to collapse
I think this is the issue: since you are s-off, you should have ignored step 4 and not have locked your bootloader. A locked bootloader will not allow you to flash the firmware (it fails the security check since it wasn't created by HTC). Unlock your bootloader and try to flash the firmware file again. The reason I'm not sure is because it was my impression that an s-off phone ignores the locked/unlocked flag. But, I never lock my bootloader so I'm not sure.
By the way, s-off =/= unlocked and s-on =/= locked. Phones start as locked and s-on. Unlocking the bootloader through HTC Dev allows you to install custom recoveries and ROMs. However, it is limited because you are still s-on (security on). For example, you can only upgrade hboots, but can never downgrade to an older one. Same with RUUs. Being s-off is very flexible but more dangerous as you can access normally protected partitions. Hope that clears things up some.
Thank you again for your help. I seem to be a little more confused now. Line 4 of your guide states;
4. If you are s-off, you do not need to lock the bootloader. If you are s-on, then you need to lock the bootloader by typing "fastboot oem lock" (again, no quotes)
Click to expand...
Click to collapse
Why would I lock the the bootloader using "fastboot oem lock" if I already have s-on. You said you can not flash firmware with s-on but line 4 says I should before I flash firmware. What I just got from you, am I understanding right that I should not "fastboot oem lock" before you flash the firmware? If you are s-on the bootloader is already locked and you would not be able to do step 5.
I am s-off right now. Would I flash the firmware now, then s-on when run the RUU?
Unlocked bootloader does not = s-off.
My guess is you are unlocked not s-off.
S-OFF explained - by a Developer
So if I need to update the firmware do I need to be s-on or s-off? I need to get the phone back to stock and am having a really hard time.
raremind said:
So if I need to update the firmware do I need to be s-on or s-off? I need to get the phone back to stock and am having a really hard time.
Click to expand...
Click to collapse
Easiest way to go back to stock is to RUU. If you are s-on you need to re-lock (it will tell you in bootloader if you are s-on or s-off)
Updating firmware can be done s-on (need to re-lock bootloader) or s-off (no locking required).
BD619 said:
Easiest way to go back to stock is to RUU. If you are s-on you need to re-lock (it will tell you in bootloader if you are s-on or s-off)
Updating firmware can be done s-on (need to re-lock bootloader) or s-off (no locking required).
Click to expand...
Click to collapse
That's just the thing. I am s-on and relocked and every RUU I have tried failed. I have tried it with fastboot the exe and everything else under the sun. Everything I have tried has failed. here is what I am seeing:
Code:
*** TAMPERED ***
*** RELOCKED ***
*** Security warning ***
M7_WLS PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO- 1.01.20.0984_2
OpenDSP- v32.120.274.0909
OS-5.05.651.2
eMMC-boot 2048MB
Sep 24 2014, 16:58:42:0
I rooted and flashed TEAMWIN recovery and Viper 7.1 - My Camera started acting up and I couldn't talk on calls so I wanted to get it back to stock. The only thing I was able to do successfully trying to get it back to stock was lock the bootloader. Everything beyond that has failed.
This is what I get updating the firmware:
Code:
target reported max download size of 1514139648 bytes
sending 'zip' (39656 KB)...
OKAY [ 2.917s]
writing 'zip'...
(bootloader) signature checking..
FAILED (remote: 12 signature verify fail)
finished. total time: 7.830s
This is what I got when I locked the bootloader:
Code:
D:\Downloads\HTC\Try this\Minimal ADB and Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such file or directory))
finished. total time: 1.199s
Trying to flash RUU I get:
Code:
D:\Downloads\HTC\Try this\Minimal ADB and Fastboot>fastboot flash zip Sprint_HTC
_One_m7wls_1.29.651.7_encrypted_ROM.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1029700 KB)...
OKAY [ 37.166s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (status read failed (Too many links))
finished. total time: 133.077s
Running the RUU.exe I recieve an unknown error. Am I screwed?
Ok first off you are using the wrong RUU.
You need to use the 5.05.651.2 RUU
So, you are s-on and relocked (you said s-off before so that threw me off). Because you are s-on, you may not be successful flashing the firmware, hence the security warning in the first box (see the link explaining s-off that @BD619 left). I probably need to fix my guide to reflect that issue. In the second box, you get an error trying to relock which makes sense since you are already locked. In the third box, it looks like you get an error since you are trying to flash an older RUU (not allowed since you are s-on).
At this point, as BD said, you should be able to just go here and download the ruu exe (it's the first link). I run it as an administrator just to be safe. Follow the prompts and wait around ten minutes for it to do its thing.
Don't get too frustrated. The (forced) learning process from this is very valuable. BD and I are just members who have been on here long enough to have a good understanding of what's going on. Not speaking for BD, but I started on here knowing next to nothing about Android except it's based on Linux.
Not speaking for BD, but I started on here knowing next to nothing about Android except it's based on Linux.
Click to expand...
Click to collapse
You knew more then me lol.
My first couple posts were me begging for help because I bricked my sons Epic 4G Touch lol (posted in Development...reasoning I thought it would get more exposure and I would get helped faster lol)
BD619 said:
(posted in Development...reasoning I thought it would get more exposure and I would get helped faster lol)
Click to expand...
Click to collapse
Haha, noob! I would have replied with "Cool ROM, bro".
Well thank you both! I was able to successfully flash the 5.05.651.2 RUU. Such a simple thing that was causing me such problems. I was under the impression that the RUU version didn't make a difference. I wish they would add that to the guides! Well thanks to both of you!