Database Develop

Need help flashing stock ROM on HTC One

Hi. I'v got friend's HTC One on stock 4.3 (3.63.161.6). I need to flash stock 4.3 Europe that has Polish language included.
I've downloaded this stock RUU:
RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4.exe
How do I flash it? Is it safe to flash it on my friend's HTC One that has stock 4.3 (3.63.161.6), S-ON and locked bootloader (the phone was never rooted, modded etc.)? Should I first S-OFF and unlock bootloader? What tool do I use to flash this RUU? What are these CID and MID about? Should I care about them?
It's the first time I'm working with a HTC, so I'm a total HTC noob. I only had few Samsungs and currently a Nexus 4 and know how to work with these but not HTC.

daerragh said:
Hi. I'v got friend's HTC One on stock 4.3 (3.63.161.6). I need to flash stock 4.3 Europe that has Polish language included.
I've downloaded this stock RUU:
RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4.exe
How do I flash it? Is it safe to flash it on my friend's HTC One that has stock 4.3 (3.63.161.6), S-ON and locked bootloader (the phone was never rooted, modded etc.)? Should I first S-OFF and unlock bootloader? What tool do I use to flash this RUU? What are these CID and MID about? Should I care about them?
It's the first time I'm working with a HTC, so I'm a total HTC noob. I only had few Samsungs and currently a Nexus 4 and know how to work with these but not HTC.
Click to expand...
Click to collapse
1- you'll need s-off to be able to downgrade
2- how about sharing a "fastboot getvar all" (removing IMEI and s/n before posting)

Thanks for quick reply. Is there a RUU stock Europe ROM in such a version, so I wouldn't need to S-OFF; so I woudn't need to downgrade the firmware?
I tried to run the RUU when my phone is in Fastboot USB mode, it started updating but it stopped in the middle of the process. Phone works normally, it didn't brick. How do I install this RUU: RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14 .3250.13_10.33.1150.01_release_311663_signed_2_4.e xe
This is the fastboot getvar all output:
Code:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Wszelkie prawa zastrzeżone.
D:\h>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT35EW901589 device
D:\h>adb reboot-bootloader
D:\h>fastboot getvar all
(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.63.161.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *REMOVED*
(bootloader) imei: *REMOVED*
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4016mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ea0bccbd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s

daerragh said:
Thanks for quick reply. Is there a RUU stock Europe ROM in such a version, so I wouldn't need to S-OFF; so I woudn't need to downgrade the firmware?
I tried to run the RUU when my phone is in Fastboot USB mode, it started updating but it stopped in the middle of the process. Phone works normally, it didn't brick. How do I install this RUU: RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14 .3250.13_10.33.1150.01_release_311663_signed_2_4.e xe
This is the fastboot getvar all output:
Code:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. Wszelkie prawa zastrzeżone.
D:\h>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
HT35XXXXXXXX device
D:\h>adb reboot-bootloader
D:\h>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-main: 3.63.161.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
all: Done!
finished. total time: 0.040s
Click to expand...
Click to collapse
1- you're going to have to change CID to HTC__032 for Eastern Europe country/language
2- your MID is PN0710000, so this RUU: http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
(the other one is for PN0711000, ie M7_U not UL)
(steps 1 and/or 2 NEED S-OFF)
3- if you dont want to go through all that hassle, why not try https://play.google.com/store/apps/details?id=jp.co.c_lis.ccl.morelocale or similar and see if that does the job.

Thanks. I'm now S-OFF, changed CID and waiting for the RUU you've provided to download. I'malso on custom rom - slimbean 4.3. Do I need to somehow flash stock before installing the ruu?
OK. Im on SlimBean. I'm running the RUU fomr bootloader mode, it starts OK, asks if I wont to update from: 3.63.161.5 to: 1.28.401.7. I click next. The update starts and after a minute an error appears (error 155: error updating image) and the update stops. I can still boot the device to fastboot, so it isn't bricked. What do I do now to flash the RUU?
After installing the RUU, what do I have to do for the OTA updates to work? Do I have to S-ON or lock the bootloader?

daerragh said:
Thanks. I'm now S-OFF, changed CID and waiting for the RUU you've provided to download. I'malso on custom rom - slimbean 4.3. Do I need to somehow flash stock before installing the ruu?
OK. Im on SlimBean. I'm running the RUU fomr bootloader mode, it starts OK, asks if I wont to update from: 3.63.161.5 to: 1.28.401.7. I click next. The update starts and after a minute an error appears (error 155: error updating image) and the update stops. I can still boot the device to fastboot, so it isn't bricked. What do I do now to flash the RUU?
After installing the RUU, what do I have to do for the OTA updates to work? Do I have to S-ON or lock the bootloader?
Click to expand...
Click to collapse
NO NO, no s-on no locking!! U need to downgrade hboot to 1.44 first (& separately), then ruu will work just fine.
Check guru, or my guide in my signature (only the hboot downgrade).
I'm off for tonight...
Sent from my HTC One using Tapatalk

To expand on nkk71's post..
If you’re on hboot which is above 1.44, then first thing is to downgrade that:
so download this: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
in bootloader/FASTBOOT USB, flash it:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <---- just in case the above said “failed flush again”
fastboot reboot-bootloader
--> and confirm hboot is now 1.44
Click to expand...
Click to collapse
Then run the RUU..

Thanks a lot! So now I've got hboot 1.29.401.12_hboot_1.44 but I want to flash RUU which is 1.28, namely this one: RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe.
Is it OK? Also, I'm currently on SlimBean, can I flash the RUU straight over SlimBean 4.3, SlimBean custom kernel and custom CWM recovery?

Yes, as long as you are S-OFF... flash away the RUU. It will overwrite all partitions.

OK. I flashed the RUU. Do I now have to do sth for the OTA updates to work with the phone? Or can I start updating the phone straight away?

Not really, connect to wifi, and start smashing Check Update button.. you should get about 2-4 updates as you installed one of the oldest RUU

Thank you all for your replies. The phone now officially has polish language and I'm in the process of udpating it via OTA. Everything works fine! Thanks again

Perfect, please mark the thread as [SOLVED] and give thanks to nkk71!

[Q] Unable to unlock, flash recovery or s-off or RUU

I have one hell of a problem.
Status of device:
-Google play edition kit kat htc one (converted from att version)
-No recovery, recovery is INACCESSABLE
-No root, and temp root does not work as well.
-Stock att RUU's not working (as of yet)
-I have tried firewatter, revone and rum runner to try and root so i can get s-off but unable.
-For whatever reason fastboot oem unlock does not as well as the unlock token.
Things i haven't tried because i cant find them:
-Google play edition RUU.exe file
-A standalone RUU for downgrading hboot 1.54 (which is my device currently)
-A modified RUU.exe that will allow me to restore to stock ANYTHING
-A RUU.zip that i can flash manually without s-off
Any suggestions?

j.sax.riley said:
I have one hell of a problem.
Status of device:
-Google play edition kit kat htc one (converted from att version)
-No recovery, recovery is INACCESSABLE
-No root, and temp root does not work as well.
-Stock att RUU's not working (as of yet)
-I have tried firewatter, revone and rum runner to try and root so i can get s-off but unable.
-For whatever reason fastboot oem unlock does not as well as the unlock token.
Things i haven't tried because i cant find them:
-Google play edition RUU.exe file
-A standalone RUU for downgrading hboot 1.54 (which is my device currently)
-A modified RUU.exe that will allow me to restore to stock ANYTHING
-A RUU.zip that i can flash manually without s-off
Any suggestions?
Click to expand...
Click to collapse
you probably have to redo the process at http://www.htcdev.com/bootloader/
redo the process and try to unlock your bootloader with the new unlock.bin
just follow the steps

OK.. Explain this. If you converted. You went SOFF. Then how do you end up with LOCKED Bootloader and SJON?
sent from my mobile device

I have had the same problem few weeks ago
First unlock your bootloader again with a new unlock.bin ...redo the hole process
http://www.htcdev.com/bootloader/
Second regain S-Off with rumrunner
Finaly you should be able to restore with a RUU

Dosent go
Boachti said:
I have had the same problem few weeks ago
First unlock your bootloader again with a new unlock.bin ...redo the hole process
Second regain S-Off with rumrunner
Finaly you should be able to restore with a RUU
Click to expand...
Click to collapse
It says on the prompt that it completed successfully with the unlock, however i do not receive a prompt on the device stating the developer options to accept or deny.
I will proceed as if i did and try my att ruu to try and update the device.
I tried with a google ruu and get signature verify fail, i think that i get the same issue with the att ruu.
IF you can suggest a RUU that will help me out of the situation i would really appreciate it.
Also if there is any reason why rum runner will not complete, i can swear adb is up everything should work but it just will not complete.

j.sax.riley said:
It says on the prompt that it completed successfully with the unlock, however i do not receive a prompt on the device stating the developer options to accept or deny.
I will proceed as if i did and try my att ruu to try and update the device.
I tried with a google ruu and get signature verify fail, i think that i get the same issue with the att ruu.
IF you can suggest a RUU that will help me out of the situation i would really appreciate it.
Also if there is any reason why rum runner will not complete, i can swear adb is up everything should work but it just will not complete.
Click to expand...
Click to collapse
Turning security back to ''on'' and relocking your bootloader on GPE was a bad decision, you probably bricked your device forever.
This is discussed in this thread: http://forum.xda-developers.com/showthread.php?t=2547894
With S-ON and Locked (Re-Locked) bootloader, your only hope is to flash a RUU of same or higher version than the version currently installed on your phone. You can't downgrade anything with s-on using a ruu.exe neither a ruu.zip. You are stuck until htc release a newer gpe ruu.
Post the output of ''fastboot getvar all'' minus your IMEI and SERIALNO

alray said:
Turning security back to ''on'' and relocking your bootloader on GPE was a bad decision, you probably bricked your device forever.
This is discussed in this thread:
With S-ON and Locked (Re-Locked) bootloader, your only hope is to flash a RUU of same or higher version than the version currently installed on your phone. You can't downgrade anything with s-on using a ruu.exe neither a ruu.zip. You are stuck until htc release a newer gpe ruu.
Post the output of ''fastboot getvar all'' minus your IMEI and SERIALNO
Click to expand...
Click to collapse
Is there any chance of spoofing the ruu.zip to make it look like a higher verison?
If not that can i just flash a recovery image even if its stock so i can have a recovery as i currently don't even have that which i think is the source of my problems.

j.sax.riley said:
Is there any chance of spoofing the ruu.zip to make it look like a higher verison?
If not that can i just flash a recovery image even if its stock so i can have a recovery as i currently don't even have that which i think is the source of my problems.
Click to expand...
Click to collapse
Unfortunately no. ''spoofing'' the ruu will require to decrypt it. With s-on you can't flash a decrypted ruu, you can only flash a ruu that is signed with HTC private key (decrypted ruu can't be signed back with HTC private key). S-OFF would have saved your phone in this case.
The only way to flash the stock recovery in your case is to flash a signed firmware.zip of the same of higher version.
Still waiting your ''fastboot getvar all'' output

alray said:
Unfortunately no. ''spoofing'' the ruu will require to decrypt it. With s-on you can't flash a decrypted ruu, you can only flash a ruu that is signed with HTC private key (decrypted ruu can't be signed back with HTC private key). S-OFF would have saved your phone in this case.
The only way to flash the stock recovery in your case is to flash a signed firmware.zip of the same of higher version.
Still waiting your ''fastboot getvar all'' output
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(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-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

j.sax.riley said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(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-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Afaik, there is no ruu you can flash. Your version is 3.62.1700.1 and the latest ruu I can find is 3.58.1700.5 which is a downgrade (require S-OFF) You'll need to find or wait for a ruu higher or equal to 3.62.1700.1

alray said:
Afaik, there is no ruu you can flash. Your version is 3.62.1700.1 and the latest ruu I can find is 3.58.1700.5 which is a downgrade (require S-OFF) You'll need to find or wait for a ruu higher or equal to 3.62.1700.1
Click to expand...
Click to collapse
That sux.
Are you sure there is no other way?
The htc regular version stock is version 4 something and so i was hopping that would override any bull**** i have going on.
i tired temp roots to see if i can s-off in os with firewater but i was unsuccesffully at gaining temp root.
Its funny to me because i swear reading somewhere that "andoid 4.4 is great" dont even have to root because of app ops or something but its obvious now thats a load of b.s and i should have just always run rooted as that has never done me wrong.
Do you know where i would find a ruu when one comes out? as one probably will with 4.4.3 coming out soon.

j.sax.riley said:
That sux.
Are you sure there is no other way?
Click to expand...
Click to collapse
If you can't s-off using rumrunner or firewater then no, idt there is other options.
j.sax.riley said:
The htc regular version stock is version 4 something and so i was hopping that would override any bull**** i have going on.
Click to expand...
Click to collapse
The international version ruu is a .401 base (not .1700) and require to change CID and probably MID. Changing those values require S-OFF!
j.sax.riley said:
Do you know where i would find a ruu when one comes out? as one probably will with 4.4.3 coming out soon.
Click to expand...
Click to collapse
htcdev.com under the ''kernel source code'' section, http://htc1guru.com and http://androidruu.com/?developer=M7

[*] Attempting to acquire root. This will take 5-10 minutes, be patient
error in setsockopt().
Failed to get prepare_kernel_cred address.
Failed to get commit_creds address.
Failed to get ptmx_fops address.
Failed to setup variables.
This is my output from trying temp root with firewater method.
I am not sure what the issue is that is happening but i assume with the first failure the whole system collapses.
Thank you for the help btw, and i will keep my eyes open for a new ruu.
What do i need to be looking for in the ruu to make sure it will work with my phone?
Specific cid and mid?

j.sax.riley said:
What do i need to be looking for in the ruu to make sure it will work with my phone?
Specific cid and mid?
Click to expand...
Click to collapse
must be signed and same or higher version than 3.62.1700.1.
any .1700 version will match your CID and MID (GOOGL01 and PN0712000)

Last question,
Flashing a newer hboot or the "modified gpe bootloader"
Is it possible since im s-off, and will it change anything?
And why wont this zip work?
RUU Zip M7 Google Edition 4.4 3.58.1700.5
Because its version 3.58 and i am 3.62?

I like Htc phones and especially their commitment to bring timely updates.
But.....i do miss being able to use odin and never have to worry if your device gets f-ed up you can always reformat it to stock without trying to get a warranty replacement (which i cant because i'm rocking my google play edition) which is great and totally beats cyanogen mod for stability.
Although....i miss blink feed lol

j.sax.riley said:
Last question,
Flashing a newer hboot or the "modified gpe bootloader"
Is it possible since im s-off, and will it change anything?
Click to expand...
Click to collapse
Fomr the output of your fastboot getvar all, you are S-ON not S-OFF so you won't be able to flash a modifed hboot. Btw, if you flash a modified hboot in the future with s-off, you will brick your device if you s-on again (with a modified hboot)
j.sax.riley said:
And why wont this zip work?
RUU Zip M7 Google Edition 4.4 3.58.1700.5
Because its version 3.58 and i am 3.62?
Click to expand...
Click to collapse
Yes, 3.58 is a downgrade of version from what you have currently on your phone. Downgrading require S-OFF

[Q] HTC ONE (m7) 64GB Developer Edition

Hello everybody, I´m a little newbie here so need some URGEN HELP.
1.- I bought an HTC ONE (m7) 64GB Developer Edition from SWAPPA with ClockworkMod Recovery and CyanogenMod 11 on it.
2.- While looking into XDA-Developer was following a thread to get it back to stock recovery using nandroid so I can flash an RUU from HTCDEV
While doing that seems that I erase everything from the phone and now it´s giving me an error mounting e:/ drive and It doesn´t recognize the phone in ADB mode.
I´m stuck with the CWM without the ability to get files into /sdcard/0/clockworkmode/backups
Can someone help me or point me in the right direction to get back to the stock android that the HTC Developer Edition (m7) comes in factory default.

ulises.boom said:
2.- While looking into XDA-Developer was following a thread to get it back to stock recovery using nandroid so I can flash an RUU from HTCDEV
Click to expand...
Click to collapse
you don't need stock recovery to use a ruu. Recovery is overwritten by the ruu.
ulises.boom said:
While doing that seems that I erase everything from the phone and now it´s giving me an error mounting e:/ drive and It doesn´t recognize the phone in ADB mode.
I´m stuck with the CWM without the ability to get files into /sdcard/0/clockworkmode/backups
Can someone help me or point me in the right direction to get back to the stock android that the HTC Developer Edition (m7) comes in factory default.
Click to expand...
Click to collapse
Just flash the latest dev edition ruu http://www.htc1guru.com/2014/03/android-dev-ruu/

@alray Thanks for the prompt response.
I will download and try that later today after work.
But some questions so I don´t do something stupid:
I have to restart the phone on Fastboot mode or Recovery Mode for the RUU to work, as the phone is starting with the Gray and red triangle and an admiration mark.?
Thanks

ulises.boom said:
@alray Thanks for the prompt response.
I will download and try that later today after work.
But some questions so I don´t do something stupid:
I have to restart the phone on Fastboot mode or Recovery Mode for the RUU to work, as the phone is starting with the Gray and red triangle and an admiration mark.?
Thanks
Click to expand...
Click to collapse
you can run the ruu.exe in bootloader mode if you want, it will then switch to ruu mode by itself. If the phone were booted in the OS the ruu.exe will make it reboot in ruu mode.

@arlay Sorry to tell you that it didn´t work.
Let me explain a little of what I have here:
It seems that I erase everythin in the Phone except by the Fastboot and Recovery.
I´m having the following errors:
E:Can´t mount /cache/recovery/
E: unknown volume "/sdcard/.android_secure
Running the RUU I got Error 155.
And another thing, it can find /system/xbin/su
Do I hava a recobrable one or a brick?
I have it on s-on and could not made it s-off with revone
alray said:
you can run the ruu.exe in bootloader mode if you want, it will then switch to ruu mode by itself. If the phone were booted in the OS the ruu.exe will make it reboot in ruu mode.
Click to expand...
Click to collapse

ulises.boom said:
@arlay Sorry to tell you that it didn´t work.
Let me explain a little of what I have here:
It seems that I erase everythin in the Phone except by the Fastboot and Recovery.
I´m having the following errors:
E:Can´t mount /cache/recovery/
E: unknown volume "/sdcard/.android_secure
Running the RUU I got Error 155.
And another thing, it can find /system/xbin/su
Do I hava a recobrable one or a brick?
I have it on s-on and could not made it s-off with revone
Click to expand...
Click to collapse
1- can you post a "fastboot getvar all" (excluding IMEI and s/n)
2- with S-On you need to relock bootloader for RUU (same or higher version) to work
3- for S-Off, you should also try rumrunner and firewater

@nkk71 Here is the results of the getvar
List of devices attached
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1540.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(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: 4281mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (
status read failed (Too many links))
finished. total time: 0.062s
nkk71 said:
1- can you post a "fastboot getvar all" (excluding IMEI and s/n)
2- with S-On you need to relock bootloader for RUU (same or higher version) to work
3- for S-Off, you should also try rumrunner and firewater
Click to expand...
Click to collapse

ulises.boom said:
@nkk71 Here is the results of the getvar
List of devices attached
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-main: 1.29.1540.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
finished. total time: 0.062s
Click to expand...
Click to collapse
Personally, I would use this ruu.exe : http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
it's the same version as your current one, which would give you a chance to S-Off, if you wish.... a higher version, could make that more difficult.
the RUU will work but you need to lock your bootloader using fastboot oem lock
I know it's ironic that the Dev Edition is bootloader unlocked be default, but RUU's wont work with that.

@arlay & @nkk71 Thanks a million for helping me solve my problem.
I have a functional HTC ONE m7ul Developer Edition back in business.
Now to wait for a KitKat Update to put it on the Mobile.
nkk71 said:
Personally, I would use this ruu.exe : http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-16-exe/
it's the same version as your current one, which would give you a chance to S-Off, if you wish.... a higher version, could make that more difficult.
the RUU will work but you need to lock your bootloader using fastboot oem lock
I know it's ironic that the Dev Edition is bootloader unlocked be default, but RUU's wont work with that.
Click to expand...
Click to collapse

I´m a very happy man again.
Have been receving and updating the phone with already three OTA Updates without any issues so far.
Many thanks to the guys/girls on XDA-Developers for this very helpful site.
ulises.boom said:
@arlay & @nkk71 Thanks a million for helping me solve my problem.
I have a functional HTC ONE m7ul Developer Edition back in business.
Now to wait for a KitKat Update to put it on the Mobile.
Click to expand...
Click to collapse

ulises.boom said:
Hello everybody, I´m a little newbie here so need some URGEN HELP.
1.- I bought an HTC ONE (m7) 64GB Developer Edition from SWAPPA with ClockworkMod Recovery and CyanogenMod 11 on it.
2.- While looking into XDA-Developer was following a thread to get it back to stock recovery using nandroid so I can flash an RUU from HTCDEV
While doing that seems that I erase everything from the phone and now it´s giving me an error mounting e:/ drive and It doesn´t recognize the phone in ADB mode.
I´m stuck with the CWM without the ability to get files into /sdcard/0/clockworkmode/backups
Can someone help me or point me in the right direction to get back to the stock android that the HTC Developer Edition (m7) comes in factory default.
Click to expand...
Click to collapse
Is this the link you talking about?
http://www.youtube.com/watch?v=rpA71FXddyU

[SOLVED]Hard bricked HTC one m7 any help?

Ok guys, I think this is going to be a hard one, i'll try to explain as good as I can:
Core problem:
After replacing my broken display assembly (before, I was on PA beta 5, rooted, unlocked, supercid and s-off) the phone went into bootloop. I reopened the case and found i had accidentally switched the grey and blue antenna connectors on the motherboard. I don't know if that was what was causing the bootloops but it's the only thing i found wrong inside the case.
So far so good. But after fixing the cable error the bootloops persisted and i wasn't able to go to recovery (TWRP 2.8.xx).
Then followed a whole lot of tampering and trying to fix things (I know this was a very bad idea)
What I tried already after reading a whole lot of threads:
1. Return to s-on (what a complete brain fart, as with no working rom i cannot reverse this)
2. Factory reset via hboot
3. bootloader relocked then unlocked then relocked again to flash ruus
4. tried flashing ruu's via fastboot (zip) and via exe. No luck, the zip file flashing hangs at "(bootloader) checking signature" and after a while fails with an unknown error and the ruu exe flashing stops with "htc-fastboot has stopped working"
5. tried flashing recovery img via fastboot; result: all twrp recoveries from 2.7.xx on upwards won't boot (bootloop); 2.6.xx works but cannot flash cm11 or PA; it says "successful for cm10 but rebooting results in bootloop again)
6. tried flashing recovery zip via twrp 2.6.xx => same result as 5.
7. on twrp 2.6.xx i tried reformating cache, data and system partitions via mkfs.ext4. then retried 4. and 5. => same results
EDIT1: 8. rewritten version-main from 4.19.xxxxxx to 1.00.000.0 (via HTC One All-In-One Toolkit by Hasoon2000) in an desperate attempt to fix ruu flashing, no luck as well (i think that even broke more things )
EDIT2: now that i think of it, somewhere along the line flashing a ruu zip sort of worked, because it updated my hboot from 1.44 to 1.57. Which is making things even worse i think.
current state:
i can start in bootloader mode, and from there start recovery (still twrp 2.6.xx)
fastboot getvar all gives:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT357W*******
(bootloader) imei: 3544************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
If you need any additional info, i'd gladly supply.
anyone has an idea of what to try next? my last resort would be to send it in to a JTAG flashing service, but i'd rather not do that as it is expensive.
thx in advance,
uuzi

uuzi said:
Ok guys, I think this is going to be a hard one, i'll try to explain as good as I can:
Core problem:
After replacing my broken display assembly my phone (before brick, I was on PA beta 5, rooted, unlocked, supercid and s-off) the phone was in a bootloop. I reopened the case and found i had accidentally switched the grey and blue antenna connectors on the motherboard. I don't know if that was what was causing the bootloops but it's the only thing i found wrong inside the case.
So far so good. But after fixing the cable error the bootloops persisted and i wasn't able to go to recovery (TWRP 2.8.xx).
Then followed a whole lot of tampering and trying to fix things (I know this was a very bad idea)
What I tried already after reading a whole lot of threads:
1. Return to s-on (what a complete brain fart, as with no working rom i cannot reverse this)
2. Factory reset via hboot
3. bootloader relocked then unlocked then relocked again to flash ruus
4. tried flashing ruu's via fastboot (zip) and via exe. No luck, the zip file flashing hangs at "(bootloader) checking signature" and after a while fails with an unknown error and the ruu exe flashing stops with "htc-fastboot has stopped working"
5. tried flashing recovery img via fastboot; result: all twrp recoveries from 2.7.xx on upwards won't boot (bootloop); 2.6.xx works but cannot flash cm11 or PA; it says "successful for cm10 but rebooting results in bootloop again)
6. tried flashing recovery zip via twrp 2.6.xx => same result as 5.
7. on twrp 2.6.xx i tried reformating cache, data and system partitions via mkfs.ext4. then retried 4. and 5. => same results
current state:
i can start in bootloader mode, and from there start recovery (still twrp 2.6.xx)
fastboot getvar all gives:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT357W*******
(bootloader) imei: 354436054678733
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
If you need any additional info, i'd gladly supply.
anyone has an idea of what to try next? my last resort would be to send it in to a JTAG flashing service, but i'd rather not do that as it is expensive.
thx in advance,
uuzi
Click to expand...
Click to collapse
First of all and as I'm sure you've discovered going back to S-on is never a good fix for anything except warranty
(bootloader) version-main: 1.00.000.0 < ----- I noticed this in your getvar, that is not normal especially with hboot 1.57 I've never seen anything like that before. Don't know if this is a hardware issue. Flashing firmware may solve it but with s-on and super cid I'm not even sure thats possible or which firmware you can use with your version main that way. Going back to s-on may well have been the nail in the coffin here I'm afraid.
If your able to boot recovery you can push a rom to flash but you need to fix the firmware first as I fear that's the cause of your bootloop. Hopefully @nkk71 @clsA or @majmoz have somthing to add here :good:

oh yeah that's somethong i've forgot to add, i've manually written version-main: 1.00.000.0 in a desperate attempt to get the ruu to flash correctly. will edit my original post to include that.

uuzi said:
oh yeah that's somethong i've forgot to add, i've manually written version-main: 1.00.000.0 in a desperate attempt to get the ruu to flash correctly. will edit my original post to include that.
Click to expand...
Click to collapse
What was the original version main?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
What was the original version main?
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
4.19.xxxxxx which was when it updated hboot to 1.57 i guess
sorry i edited some things in my OP

uuzi said:
EDIT2: now that i think of it, somewhere along the line flashing a ruu zip sort of worked, because it updated my hboot from 1.44 to 1.57. Which is making things even worse i think.
Click to expand...
Click to collapse
When you flashed the ruu did your run
Code:
fastboot flash zip "nameofruu".zip
Twice?
You have to flash the zip twice the first flash just updates hboot. Second flash installs the ruu.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
When you flashed the ruu did your run
Code:
fastboot flash zip "nameofruu".zip
Twice?
You have to flash the zip twice the first flash just updates hboot. Second flash installs the ruu.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
i'm not really sure right now, i'm trying again now

Danny201281 said:
(bootloader) version-main: 1.00.000.0 < ----- I noticed this in your getvar, that is not normal especially with hboot 1.57 I've never seen anything like that before.
Click to expand...
Click to collapse
that's done using the misctool which just writes anything you want into the misc partition (that partition is not secured, so you can even use that with S-On devices.
uuzi said:
4.19.xxxxxx which was when it updated hboot to 1.57 i guess
sorry i edited some things in my OP
Click to expand...
Click to collapse
4.19 is hboot 1.56 (with the exception of some .70x. editions, but those have a different MID, unless I'm mistaken)
hboot 1.57 would imply a 5.xx or higher firmware
so the problems:
1- there is no ruu for 1.57 hboot (ie 5.xx or 6.xx)
2- you have SuperCID, so don't know if you can unlock using HTCdev anymore... try!!
3- you don't have a ROM on it to get S-OFF, which you desperately need
if you manage to get unlocked, flash TWRP, install a stock ROM, and Sunshine S-OFF
but anyway, with all you did, this could very well be a hardware problem now, no?

Result:
Code:
C:\unbrick>fastboot oem rebootRUU
(bootloader) Start Verify: 3
OKAY [ 0.030s]
finished. total time: 0.031s
C:\unbrick>fastboot flash zip ruu.zip
sending 'zip' (1010240 KB)...
OKAY [ 32.802s]
writing 'zip'...
(bootloader) signature checking...
FAILED (status read failed (Unknown error))
finished. total time: 801.973s

nkk71 said:
that's done using the misctool which just writes anything you want into the misc partition (that partition is not secured, so you can even use that with S-On devices.
4.19 is hboot 1.56 (with the exception of some .70x. editions, but those have a different MID, unless I'm mistaken)
hboot 1.57 would imply a 5.xx or higher firmware
so the problems:
1- there is no ruu for 1.57 hboot (ie 5.xx or 6.xx)
2- you have SuperCID, so don't know if you can unlock using HTCdev anymore... try!!
3- you don't have a ROM on it to get S-OFF, which you desperately need
if you manage to get unlocked, flash TWRP, install a stock ROM, and Sunshine S-OFF
but anyway, with all you did, this could very well be a hardware problem now, no?
Click to expand...
Click to collapse
it being a hardware problem is my biggest fear
i can unlock using htcdev, so that's one good thing, the remaining problem is now that i can't flash any twrp recovery later that anything 2.6.xxx. 2.7.xxx and 2.8.xxx result in bootlooping when trying to start recovery

nkk71 said:
that's done using the misctool which just writes anything you want into the misc partition (that partition is not secured, so you can even use that with S-On devices.
Click to expand...
Click to collapse
Yeah I got that after he had said he'd changed it manually. Just caught me off guard thought it was something bigger. :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
---------- Post added at 05:01 PM ---------- Previous post was at 04:57 PM ----------
uuzi said:
it being a hardware problem is my biggest fear
i can unlock using htcdev, so that's one good thing, the remaining problem is now that i can't flash any twrp recovery later that anything 2.6.xxx. 2.7.xxx and 2.8.xxx result in bootlooping when trying to start recovery
Click to expand...
Click to collapse
What about TWRP 2.6.3.3 If it's still working maybe you can flash ARHD to get it booting maybe.
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

OH MY F**** GOD!
TWRP 2.6.3.3 and ARHD 82.0 did the trick!
IT WORKED! i'm in ARHD right now! VERY VERY VERY much apprieciated!
YOU my man are my personal hero!

uuzi said:
OH MY F**** GOD!
TWRP 2.6.3.3 and ARHD 82.0 did the trick!
IT WORKED! i'm in ARHD right now! VERY VERY VERY much apprieciated!
YOU my man are my personal hero!
Click to expand...
Click to collapse
Glad to here your back up good job :good:
Sent from my HTC One M7 - ARHD 82.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Display mesed up.

Hey guys,
I was trying to change my MID using this thread http://forum.xda-developers.com/showthread.php?t=2322820
Here is the log
C:\sdk tools\sdk-tools>fastboot getvar all
(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: HT354W913005
(bootloader) imei: 356378050014257
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3925mV
(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.078s
C:\sdk tools\sdk-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.051s
C:\sdk tools\sdk-tools>fastboot flash zip aman.zip
target reported max download size of 1526722560 bytes
sending 'zip' (479 KB)...
OKAY [ 0.250s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,43
(bootloader) [RUU]UZ,hboot,99
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
OKAY [ 2.125s]
finished. total time: 2.375s
C:\sdk tools\sdk-tools>fastboot oem writemid PN0712000
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
C:\sdk tools\sdk-tools>fastboot oem writecid BS_US001
...
(bootloader) Start Verify: 0
(bootloader) Input CID is not super CID
(bootloader) Start Verify: 0
OKAY [ 0.063s]
finished. total time: 0.063s
C:\sdk tools\sdk-tools>fastboot oem writemid PN0712000
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.016s]
finished. total time: 0.016s
Click to expand...
Click to collapse
After that i tried to reboot my device,the following screen comes up https://drive.google.com/file/d/0BzZKsM1BVUJvaEViZ2loRy0yQlk/view?usp=sharing.The bootloader is working even with the screen stuck like this but when i try to write fastboot oem rebootRUU the device switches off.Any help will be appreciated.
P.S.- Is this device soft bricked or hard bricked?

General Al Capo said:
Hey guys,
I was trying to change my MID using this thread http://forum.xda-developers.com/showthread.php?t=2322820
Here is the log
After that i tried to reboot my device,the following screen comes up https://drive.google.com/file/d/0BzZKsM1BVUJvaEViZ2loRy0yQlk/view?usp=sharing.The bootloader is working even with the screen stuck like this but when i try to write fastboot oem rebootRUU the device switches off.Any help will be appreciated.
P.S.- Is this device soft bricked or hard bricked?
Click to expand...
Click to collapse
Why did you use a 2 year old method to change MID ? and why change the MID at All ?
Step 6:
When you start your command prompt follow the steps in the picture below. PLEASE BE PATIENT!! After flashing the ENG HBOOT your HTC One will not boot up but you'll just get a gray spotted screen. Your device is not bricked. You can still use adb commands to write the model ID and CID even with a gray screen. WHEN REBOOTING HOLD DOWN POWER BUTTON FOR A FEW SECONDS. You might have to press and hold power button and volume down button when rebooting your phone.
Click to expand...
Click to collapse
You need to reflash a good hboot .. that thing you flashed is really really old
this RUU may save you
http://forum.xda-developers.com/showthread.php?t=2358781
This is how you change the MID
MID_Change_1.01.zip
https://www.androidfilehost.com/?fid=23501681358538634
It works in custom recovery

clsA said:
Why did you use a 2 year old method to change MID ? and why change the MID at All ?
You need to reflash a good hboot .. that thing you flashed is really really old
this RUU may save you
http://forum.xda-developers.com/showthread.php?t=2358781
This is how you change the MID
MID_Change_1.01.zip
https://www.androidfilehost.com/?fid=23501681358538634
It works in custom recovery
Click to expand...
Click to collapse
Thanks for replying.I was using the RUU to get back to stock but it was stuck at checking headers 4% installation.I googled it and found the method was to match the MID and CID to that of Custom ROM extracted from RUU.Guess i made a mistake for not checking if the method is old or new. Everytime i write fastboot oem rebootRUU the system reboots.I had Hboot 1.54

General Al Capo said:
Thanks for replying.I was using the RUU to get back to stock but it was stuck at checking headers 4% installation.I googled it and found the method was to match the MID and CID to that of Custom ROM extracted from RUU.Guess i made a mistake for not checking if the method is old or new. Everytime i write fastboot oem rebootRUU the system reboots.I had Hboot 1.54
Click to expand...
Click to collapse
your phone was Google play edition ... I hope you did not relock the bootloader, their is no way to unlock a bootloader on the GPe
the fastboot flash zip aman.zip may have been the fatal mistake. If you can not flash another hboot over it your screwed as far as I can tell.
Maybe @alray or @Danny201281 or @nkk71 can help you

General Al Capo said:
Thanks for replying.I was using the RUU to get back to stock but it was stuck at checking headers 4% installation.I googled it and found the method was to match the MID and CID to that of Custom ROM extracted from RUU.Guess i made a mistake for not checking if the method is old or new. Everytime i write fastboot oem rebootRUU the system reboots.I had Hboot 1.54
Click to expand...
Click to collapse
Even if you had your own reason to change the MID I don't understand why you took the risk to use this method even if its clearly mentioned in the OP you shouldn't:
MOD EDIT
Seems this guide, if not properly followed will cause a (soft)brick. Also there are more up to date guides.
[how to]change your MID without the eng bootloader
[TOOL] MID change without ENG HBOOT | Aroma GUI
In the interests of all users the guide is hidden, below.
If you wish to follow it go ahead. If you brick your handset, you were warned.
Click to expand...
Click to collapse
After that i tried to reboot my device,the following screen comes up https://drive.google.com/file/d/0BzZ...ew?usp=sharing.
Click to expand...
Click to collapse
The device should already be rebooted to that screen before attempting to change the MID.
Did you rebooted between "fastboot flash zip arman.zip" and "fastboot oem writecid PN0720000". It looks like you tried to change your MID when the phone was still in RUU mode but it must be done when in bootloader mode (when the screen is messed up).
And you will obviously need to use a RUU.exe like said in the guide (not so clearly I agree) : "Run the ruu" ( as opposed to flash the ruu) is insinuating that you must use a ruu.exe.

alray said:
Even if you had your own reason to change the MID I don't understand why you took the risk to use this method even if its clearly mentioned in the OP you shouldn't:
The device should already be rebooted to that screen before attempting to change the MID.
Did you rebooted between "fastboot flash zip arman.zip" and "fastboot oem writecid PN0720000". It looks like you tried to change your MID when the phone was still in RUU mode but it must be done when in bootloader mode (when the screen is messed up).
And you will obviously need to use a RUU.exe like said in the guide (not so clearly I agree) : "Run the ruu" ( as opposed to flash the ruu) is insinuating that you must use a ruu.exe.
Click to expand...
Click to collapse
I am trying to run the RUU .exe but it is not recognizing my device as i am using windows 8.1. I also have the latest HTC Sync manger and drivers.It seems that ill have to give it a go in Windows 7.

General Al Capo said:
I am trying to run the RUU .exe but it is not recognizing my device as i am using windows 8.1. I also have the latest HTC Sync manger and drivers.It seems that ill have to give it a go in Windows 7.
Click to expand...
Click to collapse
Uninstall HTC Sync leave the driver
What happened to the Google play RUU.zip I linked you too?
Your not ready to flash the Developer RUU yet.
Get the phone back working with the RUU I linked first.
I use Windows 8.1 every day it only affects HTC One with hboot 1.44
You have hboot 1.54 it should work fine

clsA said:
You have hboot 1.54 it should work fine
Click to expand...
Click to collapse
Not after he flashed the modded hboot. He is now on Hboot 1.43 so he will need win 7

The problem is everytime i write fastboot oem rebootRUU the device restarts.

General Al Capo said:
The problem is everytime i write fastboot oem rebootRUU the device restarts.
Click to expand...
Click to collapse
I see potential problem.
1- asked you a question in post #5, you did not answered.
2- Told you have to use a ruu.exe so why are you still trying to "fastboot oem rebootRUU" ? You must change your MID while booted in bootloader (when you can see that messed gray screen). Once you have correct CID and MID combination, launch the RUU.exe (with the phone still bootloader mode, not in "fastboot oem rebootRUU" mode).

alray said:
I see potential problem.
1- asked you a question in post #5, you did not answered.
2- Told you have to use a ruu.exe so why are you still trying to "fastboot oem rebootRUU" ? You must change your MID while booted in bootloader (when you can see that messed gray screen). Once you have correct CID and MID combination, launch the RUU.exe (with the phone still bootloader mode, not in "fastboot oem rebootRUU" mode).
Click to expand...
Click to collapse
I did that.At the end it says error-please get the correct rom utility.

General Al Capo said:
I did that.At the end it says error-please get the correct rom utility.
Click to expand...
Click to collapse
still not answered my crucial question from post #5 :
Did you rebooted between "fastboot flash zip arman.zip" and "fastboot oem writecid PN0720000". It looks like you tried to change your MID when the phone was still in RUU mode but it must be done when in bootloader mode (when the screen is messed up).
Click to expand...
Click to collapse
+ I must know what ruu exactly you are trying to flash (complete file name + link to the file)
Also post your "fastboot getvar all" again so we can double check you current situation.

Andriod info of RUU
modelid: PN0712000
cidnum: BS_US001
cidnum: BS_US002
mainver: 7.17.1540.7
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Click to expand...
Click to collapse
getvar all
C:\abc\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.39.2000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.1540.7
(bootloader) version-misc: PVT ENG S-OFF
(bootloader) serialno: HT354W913005
(bootloader) imei: 356378050014257
(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: 4234mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 080b6f61
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.130s
C:\abc\sdk-tools>
Click to expand...
Click to collapse
alray said:
still not answered my crucial question from post #5 :
+ I must know what ruu exactly you are trying to flash (complete file name + link to the file)
Also post your "fastboot getvar all" again so we can double check you current situation.
Click to expand...
Click to collapse
Yes you are right.I was following that guides DOS image so i did changed the MID while in RUU and it gave error.Later i did it in bootloader and it was fine.

General Al Capo said:
Andriod info of RUU
getvar all
Yes you are right.I was following that guides DOS image so i did changed the MID while in RUU and it gave error.Later i did it in bootloader and it was fine.
Click to expand...
Click to collapse
Why is your version-main now 7.17.1540.7 when it was 5.11.1700.3? The 7.17.1540.7 ruu flashed partially?
So if I understand right, you are trying to flash the 7.17.1540.7 ruu.exe when booted in bootloader mode and gives you the error to re-try with the correct rom update utility?

alray said:
Why is your version-main now 7.17.1540.7 when it was 5.11.1700.3? The 7.17.1540.7 ruu flashed partially?
So if I understand right, you are trying to flash the 7.17.1540.7 ruu.exe when booted in bootloader mode and gives you the error to re-try with the correct rom update utility?
Click to expand...
Click to collapse
My version main on my first try with ruu was 5.11.1700.3 and it said ENG boot .Then after running the ruu install ,it didnt recognize my device and so after that i installed Windows 7 and now it fails at updating data (1/5) and says ,please use the correct ROM utility.

General Al Capo said:
My version main on my first try with ruu was 5.11.1700.3 and it said ENG boot .Then after running the ruu install ,it didnt recognize my device and so after that i installed Windows 7 and now it fails at updating data (1/5) and says ,please use the correct ROM utility.
Click to expand...
Click to collapse
try with this RUU:http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-3-exe/. Then if it doesn't work there might be another option but im not 100% confident it will work. I think the 7.17.1540.7 ruu.exe won't flash because the hboot version is to old (1.43). We used 1.xx.xxx.xx RUU when converting phones using this procedure back in 2013, no one ever attempted to flash a 7.xx.xxx.x ruu while on the (1.43) eng hboot yet, you're the first one.
And btw, you'll definitively need to use win 7 as long as your hboot is not a least version 1.54.

alray said:
try with this RUU:http://www.htc1guru.com/dld/ruu_m7_ul_jb_50_brightstarus_wwe_1-29-1540-3-exe/. Then if it doesn't work there might be another option but im not 100% confident it will work. I think the 7.17.1540.7 ruu.exe won't flash because the hboot version is to old (1.43). We used 1.xx.xxx.xx RUU when converting phones using this procedure back in 2013, no one ever attempted to flash a 7.xx.xxx.x ruu while on the (1.43) eng hboot yet, you're the first one.
And btw, you'll definitively need to use win 7 as long as your hboot is not a least version 1.54.
Click to expand...
Click to collapse
Thanks for your help:good:.Will try this RUU after downloading it.

The RUU you gave me worked like a charm.Thank you for your assistance.

General Al Capo said:
The RUU you gave me worked like a charm.Thank you for your assistance.
Click to expand...
Click to collapse
glad to know everything is fine now. Don't forget if you want to convert your device again to another version, use the method clsA posted at first page. Very much easier and safer. The whole procedure is now done using a GUI (aroma installer) from a custom recovery.