Hi
by the time i have heard so much about bricked phones and thought that could not have happend to me. finally it happend to me.
i am a proud owner of bricked HTC desire HD - white screen after RUU file instalation.
S-ON, locked.
i can unlock it becuse htcdev doesent support any more my version of hboot.it is 2.00.027. it needs to be updated to version 2.00.029.
i found a dosen programs and guids to solve my issue BUT nowhere could i find how my computer supose to see my DHD.
USB debbuging is off and i cant reach it due to white screen.
when i plug data cabel in, computer recognizes it as android 1.0., no G particion and HTC sync doesent work. Hboot mode doesent seems to make any hepl
everybody who have faced this kind of problem please post
Thanks in advance
You've tried re-installing the official RUU through fastboot?
that something i havent done so far. how that suppose to be done?
make a small guide.
i accept all suggestions
Actually this might help:
http://forum.xda-developers.com/showthread.php?t=1049414
If you ment by re-installing RUU file - put RUU file the same or higher version of whats on the phone on the sd card rename it PD98IMG.zip enter the hboot (not the fastboot) - hboot will ask me if i want to update - the answer is yes but with fastboot i have no clue.
orangekid said:
Actually this might help:
http://forum.xda-developers.com/showthread.php?t=1049414
Click to expand...
Click to collapse
thats something that i have done first.
last ten days ive been doing nothing but trying to unbrick my DHD
thanks for effort.
t
You're s-off? Flash a recovery then a ROM
Sent from my Desire HD using Tapatalk 4 Beta
humzaahmed155 said:
You're s-off? Flash a recovery then a ROM
Sent from my Desire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
iam
s-on
HBOOT 2.00.0027
MICROP - 0438
RADIO 26.14.04.28_M
eMMc - boot
pure stock
locked, unrooted
hboot needs to be updated on version 2.00.0029 because htcdev doesent support any more this version of HBOOT. ican do that with the HBOOT updaters but my computer dont see my phone. the usb debugging is off.
what to do that my computer sees my phone? i tried hboot, fastboot, regular mode etc...
s-on
this post would solve my problem completely but as i mentioned computer cant see my phone. it sees it as android 1.0., no G particion and htc sync doesent work
http://forum.xda-developers.com/showthread.php?t=2286438
i hope this link would help you full to understand whats bugging me for a while.
charles66 said:
iam
HBOOT 2.00.0027
MICROP - 0438
RADIO 26.14.04.28_M
eMMc - boot
pure stock
locked, unrooted
hboot needs to be updated on version 2.00.0029 because htcdev doesent support any more this version of HBOOT. ican do that with the HBOOT updaters but my computer dont see my phone. the usb debugging is off.
what to do that my computer sees my phone? i tried hboot, fastboot, regular mode etc...
Click to expand...
Click to collapse
Ok so the SD update thru hboot doesn't work,
Have you run the RUU from your computer during fastboot?
orangekid said:
Ok so the SD update thru hboot doesn't work,
Have you run the RUU from your computer during fastboot?
Click to expand...
Click to collapse
you mean run the ruu file on computer and connect phone via cabel in fastboot usb - yes
application on comp. stuck on bootloader rebooting with the .......................... keep on going and going with no end
charles66 said:
you mean run the ruu file on computer and connect phone via cabel in fastboot usb - yes
application on comp. stuck on bootloader rebooting with the .......................... keep on going and going with no end
Click to expand...
Click to collapse
you're 100% sure you have the correct drivers?
Try it again with another USB cable too maybe.
am 100% sure my driver are ok.
i tried two more others cabels.
i thought of all that but useless.
i ran out of ideas
Running "fastboot devices" on your computer while your phone is plugged in and in fastboot mode, what does it show?
Hmm, launch the RUU exe file, then go to its app data in windows, and pull the ROM.zip file, rename it to PD98IMG.zip, stick it on your sdcard and go into hboot
Sent from my Desire HD using Tapatalk 4 Beta
bananagranola said:
Running "fastboot devices" on your computer while your phone is plugged in and in fastboot mode, what does it show?
Click to expand...
Click to collapse
nothing. device manager shows android 1.0.
htc sync says no conected devices
G particion doesent pop up - cant reach the datas on sd card
cant reach device from computer
all drivers updated and installed for sure
white screen - obviously usb debugging off
if i could see the device i solved all my problems. the rest wouldnt bug me at all - i mean on unlooking, flashing recovery and rom
humzaahmed155 said:
Hmm, launch the RUU exe file, then go to its app data in windows, and pull the ROM.zip file, rename it to PD98IMG.zip, stick it on your sdcard and go into hboot
Sent from my Desire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
already tried, doesent work.
hboot needs to be updated
charles66 said:
already tried, doesent work.
hboot needs to be updated
Click to expand...
Click to collapse
What that PD98IMG does IS update your hboot (and everything else) to what's in the RUU. And are you sure your phone is in fastboot (not hboot) when you run "fastboot devices?"
charles66 said:
s-on
this post would solve my problem completely but as i mentioned computer cant see my phone. it sees it as android 1.0., no G particion and htc sync doesent work
http://forum.xda-developers.com/showthread.php?t=2286438
i hope this link would help you full to understand whats bugging me for a while.
Click to expand...
Click to collapse
You need to flash a RUU from fastboot as you were told. The ruu needs to be for your device (match CID and Main Version) other wise it will fail. Depending on what Main Version you are you might be able to update the hboot and then unlock the bootloader. Boot the device in hboot, press power and plug it to the PC (you should see fastboot usb in red) then open a cmd in the PC and run this command:
Code:
fastboot getvar all
Paste the outcome in here deleting the IMEI
glevitan said:
You need to flash a RUU from fastboot as you were told. The ruu needs to be for your device (match CID and Main Version) other wise it will fail. Depending on what Main Version you are you might be able to update the hboot and then unlock the bootloader. Boot the device in hboot, press power and plug it to the PC (you should see fastboot usb in red) then open a cmd in the PC and run this command:
Code:
fastboot getvar all
Paste the outcome in here deleting the IMEI
Click to expand...
Click to collapse
C:\android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0027
(bootloader) version-baseband: 26.14.04.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: 0438
(bootloader) version-main: 3.12.405.1
(bootloader) serialno: SH198RX00810
(bootloader) imei: 3xxxxxxxxxx
(bootloader) product: ace
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PD9810000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4135mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 743ca94a
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) region-id: 0
all: Done!
finished. total time: 0.000s
C:\android>
here is what i got. now i have to find the RUU file that match cid and main version.
thanks mate. i ll try.
i keep you informing
Related
Having a problem with my DHD after unlocking the bootloader through HTCDEV and then running the Advanced ACE Hack Kit.
It appears to be flashing roms but when rebooting it's just freezing at the HTC screen.
Now, I know it must be something I've done/I'm doing but I have no idea what so can someone please talk me through flashing the easiest rom in the easiest way?
Can you access to the bootloader(Turn off the device then press and hold vol down and power together until booted)?
ymcc said:
Can you access to the bootloader(Turn off the device then press and hold vol down and power together until booted)?
Click to expand...
Click to collapse
Yep. I can get into the bootloader so i've been going into recovery (which is now ClockworkMod 5.0.2.7) and trying to flash different roms from there but none are working so it must be something I'm doing
What it sais when you try and fail.Are there any errors ?
ymcc said:
What it sais when you try and fail.Are there any errors ?
Click to expand...
Click to collapse
Nope. I've tried 4 different roms and they all seem to work but when it reboots I just get the HTC at startup but it hangs there
You are not bricked if you can access bootloader.
You have to flash the Roms boot.img separate when you flash roms with unlocked bootloader, I would recommend to run the ruu from your computer when in fastboot mode, then relock the bootloader using HTCdev and rerun the advanced ace hack kit.
Sent from my HTC Desire HD using xda premium
Muikkuman said:
You are not bricked if you can access bootloader.
You have to flash the Roms boot.img separate when you flash roms with unlocked bootloader, I would recommend to run the ruu from your computer when in fastboot mode, then relock the bootloader using HTCdev and rerun the advanced ace hack kit.
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
I know I'm gonna look like a complete spaz here but can you tell me how to do it? I flashed my Magic and it was so easy compared to this :-S
Where do I put the rom? Do I need to unzip it first? Amd what commands do I use in fastboot?
Which of it? flash Rom or get real S-OFF?
Sent from my HTC Desire HD using xda premium
Dont unzip it copy to sdcard root.check android development stickies you got your answers and tools there you need to wipe everything then flash over and flash 4ext recovery wipe boot.imp then flash a rom
Sent from my Desire HD using xda app-developers app
Gixermouse said:
Having a problem with my DHD after unlocking the bootloader through HTCDEV and then running the Advanced ACE Hack Kit.
It appears to be flashing roms but when rebooting it's just freezing at the HTC screen.
Now, I know it must be something I've done/I'm doing but I have no idea what so can someone please talk me through flashing the easiest rom in the easiest way?
Click to expand...
Click to collapse
Gixermouse, you commited a mistake covered in the effen manual...you tried running the kit with an unlocked bootloader. You need to relock it first and then re run the Kit.
Do the following:
1) Boot in hboot and then choose fastboot.
2) Plug the phone (until you see fastboot usb)
3) Open a cmd as Admin in the PC or Terminal as root (in linux or mac)
4) Type: fastboot oem lock
then you should see OKAY. finished...then reboot the phone and from the htc screen run the Hack Kit again...
It will work unless you did a factory reset....if you need help just let me know...:good:
glevitan said:
Gixermouse, you commited a mistake covered in the effen manual...you tried running the kit with an unlocked bootloader. You need to relock it first and then re run the Kit.
Do the following:
1) Boot in hboot and then choose fastboot.
2) Plug the phone (until you see fastboot usb)
3) Open a cmd as Admin in the PC or Terminal as root (in linux or mac)
4) Type: fastboot oem lock
then you should see OKAY. finished...then reboot the phone and from the htc screen run the Hack Kit again...
It will work unless you did a factory reset....if you need help just let me know...:good:
Click to expand...
Click to collapse
OK! I've followed what you said to do and on the HBOOT scree it now says *** RELOCKED *** at the top but when I try to run the hack kit it's saying "Error: device not found". I've tried at the HTC screen, HBOOT screen ad FASTBOOT screen. Any ideas?
Gixermouse said:
OK! I've followed what you said to do and on the HBOOT scree it now says *** RELOCKED *** at the top but when I try to run the hack kit it's saying "Error: device not found". I've tried at the HTC screen, HBOOT screen ad FASTBOOT screen. Any ideas?
Click to expand...
Click to collapse
umm...it seems that u have done a factory reset. I guess the best u can do is to flash a ruu, go back to stock and then when working re run the Hack Kit to gain S-OFF and root.
Do you know, what your cid is? boot in fastboot, plug the phone until you see fastboot usb and then from a cmd session as admin type
fastboot getvar all....paste here the INFOcidnum
Gixermouse said:
OK! I've followed what you said to do and on the HBOOT scree it now says *** RELOCKED *** at the top but when I try to run the hack kit it's saying "Error: device not found". I've tried at the HTC screen, HBOOT screen ad FASTBOOT screen. Any ideas?
Click to expand...
Click to collapse
since ur are saying that it says no device found then u have no other option but to flash the p98img.zip through fastboot but make sure not to flash a dhd shipped with gingerbread with a froyo ruu.Peace
What country and carrier is your phone from? The AAHK has am option to download RUUs. Try to use that. If that doesn't workout, I'll try to find an RUU for you (depending on your country and carrier).
Sent from my Desire HD using xda premium
Right. Here's all the info from the Getvar command minus the IMEI number:
version: 0.5
version-bootloader: 0.85.0024
version-baseband: 26.09.04.11_M2
version-cpld: None
version-microp: 0438
version-main: 1.80.502.3
serialno: HT0BHRX15082
product: ace
platform: HBOOT-7230
modelid: PD9810000
cidnum: HTC__001
battery-status: good
battery-voltage: 4165mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: a3d4fa0f
hbootpreupdate: 11
gencheckpt: 0
region-id: 0
The phone is a replacement board fitted by HTC under waranty after mine died (through no fault of my own that time!)
It wasn't network locked and was running 2.3.5 when I recieved it.
By booting in recovery and mounting the system data and cache I was able to make it appear to flash a rom and when I did a backup the files were on there but it still wouldn't boot.
If there's anything else you need let me know because the LG-A100 I've borrowed is now driving me crazy and I'm getting a bit desperate
Gixermouse said:
Right. Here's all the info from the Getvar command minus the IMEI number:
version: 0.5
version-bootloader: 0.85.0024
version-baseband: 26.09.04.11_M2
version-cpld: None
version-microp: 0438
version-main: 1.80.502.3
serialno: HT0BHRX15082
product: ace
platform: HBOOT-7230
modelid: PD9810000
cidnum: HTC__001
battery-status: good
battery-voltage: 4165mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: a3d4fa0f
hbootpreupdate: 11
gencheckpt: 0
region-id: 0
The phone is a replacement board fitted by HTC under waranty after mine died (through no fault of my own that time!)
It wasn't network locked and was running 2.3.5 when I recieved it.
By booting in recovery and mounting the system data and cache I was able to make it appear to flash a rom and when I did a backup the files were on there but it still wouldn't boot.
If there's anything else you need let me know because the LG-A100 I've borrowed is now driving me crazy and I'm getting a bit desperate
Click to expand...
Click to collapse
OK...STOP TRYING THINGS!! you might mess the device. I will send u a RUU in a PM that you will have to flash over fastboot....if you need help just let me know that way and we will work the way out.
Hi guys, this is very simple tut on how to lock your bootloader,downgrade,s-off and root
Full wipe before Doing this. (Recommended)
Relocking BOOTLOADER Steps(skip this if your bootloader is locked)
--------------------------
1.First download the fastboot folder (Click here!)
2.Then EXTRACT it to where you can locate it (e.g C/Desktop)
3.Now put your cursor to your EXTRACTED Fastboot Folder And Press SHIFT+Right click on the Fastboot folder and click 'Run as Command Prompt'
4.Minimize the Command prompt
5.Now on your HTC DESIRE Turn it off and load into bootloader (press Power+ volume down and hold untill a white screen pops up)
6.Then use your volume up and down to controle it (Volume up goes up, Volume down goes down (duh) and pressing power button enters directory)
7.press Volume down to fastboot on your htc and click the power button
8.Go back to your computer and open your minimized command prompt
9.Type in this code
fastboot oem lock
10.If you did this sucesfully a fail word will come up and your phone will shut down. Reload your htc bootloader and you will see relocked on your pink header.(Note: this product cant be 'locked':crying
11. Voila! Enjoy your downgrade and rooting!
Downgrade steps [1.03](Skip this if your hboot is 1.02)
-----------------
1. Download tools package (click here!)
NOTE: THIS FILE DOES NOT CONTAIN VIRUS NOR TROJAN BUT YOUR ANTIVIRUS DETECTS IT AS VIRUS SO TURN YOUR ANTIVIRUS OFF
2. Download the HTC Desire ROM (RUU)
3. For branded phones you need to create GoldCard (How to)
4. Extract theses tools where you can actually remember.
5. Run RUU and wait till the ROM update utility screen appears.
6. Go to Temp directory where your ruu is downloaded (C:\Users\Your User Name\AppData\Local\Temp for Win7 and vista,C:\Documents and Settings\Your User Name\Local Settings\Temp for WINXP Users) and search for rom.zip
7. Copy the rom.zip and paste it to sdcard and rename it to PB99IMG.zip
8. Connect your phone to computer via USB as charge only and enable USB debugging and Unknown Sources.
9. Run DOWNGRADER on tools folder that you downloaded and extracted it.
10. Follow the onscreen instructions (This may take upto 1 to 2 min)
11. Your phone will be reset, wait for detect and check the Update Package.
12. After checking update package, press vol-up to begin update process, IN FIRST TIME AFTER PRESSING VOL-UP YOUR PHONE WILL RESET AND DO NOTHING, YOU SHOULD DO AGAIN FOR STEPS 11,12
s-off Steps:
1.Click this
2.fill up your information
3.save your beta key somewhere
4.Download revolutionary
5.follow step and on some occasions they will ask for beta key
6.your phone will s-off
Rooting
-----------------------
1. download unrevoked (click here)
and let the programme do the rest
How to flash your own costume recovery!!
--------_------------
Press shift+right click on the extracted fast boot and click open as command prompt something like that and minimize that and download your costume recovery. Then put it inside fast boot and rename it as recovery. Then plug in your HTC and go to boot loader and go to fast boot. Now¶π° go back to your command prompt and typein this code
fastboot flash recovery.img
If u did this successfully then it will say successfully flash costume recovery
Notes
The process will flash a clockwork mod recovery partition:good:
This process will wipe all the data from your phone:good:
The downgrade installs an official stock HTC ROM with Hboot1.02 (You can s-off with revolutionary and after it You can flash any version of Hboot):fingers-crossed:
Your sdcard should be fat32 formatted:good:
This Pure entertainment will relock the bootloader:laugh:
When life gives you lemonade
HiT THANKS IF THIS HELPED YOU. AND POST A REPLY FOR IMPROVEMENTS
Improvement credit
Nloooo
Respect for the effort but there are a few misunderstandings:
1. Locking of bootloader??? Why for God's sake??? A ton of people lost their hair trying to unlock it!!!!
2. Downgrading? What kind? You have to explain the reason (1.03 bootloader or what)
3. Quoting "2. Download the HTC Desire ROM (RUU)". Don't mix rom with RUU (Rom Update Utility), they are not the same.
Plus: which RUU to download, you have to explain, what version (Android related), which region based (for branded devices)...
Ok you mentioned goldcard-explain why (for branded devices)...
My recommendation: suggest 2.3 RUU, it's usable with all phone types (amoled or slcd) and all regions (no goldcard needed applicable for all brends).
Also you have to mention that all RUUs can be used from PC while phone is connected via USB.
4. S-off process: revolutionary-yes but for 0.93. and 1.02 hboots, for older versions of hboots alpharev reflash utility needed
5. Rooting: Unrevoked-yes but when you don't use Revolutionary (gaining s-off using Alpharev reflash utility).
Revolutionary itself gives option to flash recovery (Clockwork Mod) which you use to flash Superuser app to gain root access (explained on documentation page for
Revolutionary, all you need is to read http://unrevoked.com/rootwiki/doku.php/public/revolutionary)
6. Quoting "The process will flash your recovery partition back to stock" - no, Revolutionary will flash ClockworkMod recovery.
7. Quoting "The downgrade installs an official stock HTC ROM with Hboot1.02 (You can s-off with revolutionary and after it You can flash any version of Hboot)" - not necessarily the hboot will be 1.02, it depends on which RUU you choose to flash.
Plus:
Downgrade package contains virus, warn potential user - what is it, a virus that will ruin their PC or just an exploit used to gain access to restricted phone partitions.
I hope I helped...
wow... i agree with nlooooo, good effort but u just confused the s*** outa me lol.
Sent from my HTC Desire
ok thank you nloo
Thank you for your reply and I appreciate for your time writing this! I will,perhaps, change my thread
just go by what nlooooo says, i mean just add a bit more detail to what ur saying. this is a TUT and people might use this and the last thing u want is people blaming u if anything goes wrong because u forgot to mention something
Sent from my HTC Desire
thanks!
good work!
Stop spamming and start hitting the thanks button!
Sent from my HTC Desire using xda premium
Umg
my problem is that I can't boot in the OS, it is always stuck at HTC logo I did relock and I can't flash RUU, get "signarure error"
ferencz1 said:
my problem is that I can't boot in the OS, it is always stuck at HTC logo I did relock and I can't flash RUU, get "signarure error"
Click to expand...
Click to collapse
Try the 2.3 RUU. Check my sig.
my phone was sent for repair, got new motherboard and after one hour of using it he just froze. I removed my battery and put it back, after that it stuck on HTC logo screen. So I went to flash RUU but I couldn't install it I got singarure error, so I made bootloader unlock and after that I don't know what to do next.
Nothing in bootloader it says: "checking PB99IMG.zip - no images found"
so I really don't know how to make downgrade because I can't get into the OS I can't flash RUU's and PB99IMG's, some PB99IMG's are read but after that it just stops, I don't get the screen with recovery...OK, boot....OK, etc (I don't get parsing message). He just get's in the bootloader again :/
hi sorry for a stupid quistion but i had to ask
can i use this to relock bootloader on my htc desire hd?
slimboy01 said:
can i use this to relock bootloader on my htc desire hd?
Click to expand...
Click to collapse
The command is the same, so just make sure u got fastboot set up then use the command
fastboot oem lock
done
i relocked my bootloader using this tool
RUU needed
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 13.10.401.8
(bootloader) serialno: HT13KTJ32915
(bootloader) imei: 35506*******
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.163s
i didn't find any correct ruu
please help :/
mkumar55533 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 13.10.401.8
(bootloader) serialno: HT13KTJ32915
(bootloader) imei: 35506*******
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.163s
i didn't find any correct ruu
please help :/
Click to expand...
Click to collapse
This is the htc desire (bravo) section, click the link below and use the correct guide for ur device (desire "s") and u can find the correct ruu at shipped roms.
http://forum.xda-developers.com/showthread.php?t=1318919
I did relock and how to back to unlock ?
nlooooo said:
Respect for the effort but there are a few misunderstandings:
1. Locking of bootloader??? Why for God's sake??? A ton of people lost their hair trying to unlock it!!!!
2. Downgrading? What kind? You have to explain the reason (1.03 bootloader or what)
3. Quoting "2. Download the HTC Desire ROM (RUU)". Don't mix rom with RUU (Rom Update Utility), they are not the same.
Plus: which RUU to download, you have to explain, what version (Android related), which region based (for branded devices)...
Ok you mentioned goldcard-explain why (for branded devices)...
My recommendation: suggest 2.3 RUU, it's usable with all phone types (amoled or slcd) and all regions (no goldcard needed applicable for all brends).
Also you have to mention that all RUUs can be used from PC while phone is connected via USB.
4. S-off process: revolutionary-yes but for 0.93. and 1.02 hboots, for older versions of hboots alpharev reflash utility needed
5. Rooting: Unrevoked-yes but when you don't use Revolutionary (gaining s-off using Alpharev reflash utility).
Revolutionary itself gives option to flash recovery (Clockwork Mod) which you use to flash Superuser app to gain root access (explained on documentation page for
Revolutionary, all you need is to read http://unrevoked.com/rootwiki/doku.php/public/revolutionary)
6. Quoting "The process will flash your recovery partition back to stock" - no, Revolutionary will flash ClockworkMod recovery.
7. Quoting "The downgrade installs an official stock HTC ROM with Hboot1.02 (You can s-off with revolutionary and after it You can flash any version of Hboot)" - not necessarily the hboot will be 1.02, it depends on which RUU you choose to flash.
Plus:
Downgrade package contains virus, warn potential user - what is it, a virus that will ruin their PC or just an exploit used to gain access to restricted phone partitions.
I hope I helped...
Click to expand...
Click to collapse
I done relock but after bootloader I cant downgrad ! I need help unlock bootloader back . I type fastboot oem unlock but dont work !!!
Ah, the old times.
miniandroidp : can you give us some photos?
I have a US HTC One M8 that I bought direct unlocked from htc's site direct in January 2015.
I rooted my device, and was running Paranoid Android 5.1 with TWRP recovery and decided to switch back to stock so I could sell the device.
I downloaded the RUU for my device from htc's site (ruu 6.12.1540.4 for unlocked/developer htc one m8).
I plugged in my device, typed in "fastboot oem lock" until the top of the bootloader said "Software status: modified" and "RELOCKED."
Then I ran the RUU but got Error 155 saying it was the wrong RUU. My device now had a silver HTC logo stuck in the middle. I pressed the power + volume down and got to the bootloader.
But now there is no option for "Recovery" in the bootloader, and the "Reboot" option just takes me straight back to the bootloader.
Here is what it says at the bootloader now:
***Software status: Modified***
*** RELOCKED***
***Security Warning ***
It says OS-4.16.1540.8
In addition, I can't charge without the screen being on. I plug in my phone and it shows the battery icon for a few seconds and then goes back into the booloader with "fastboot ac"
Please help me get my device working & back to stock. Any information or tips will help. I can take photos and provide with any additional information if needed.
Thanks.
AeroPeg said:
I have a US HTC One M8 that I bought direct unlocked from htc's site direct in January 2015.
I rooted my device, and was running Paranoid Android 5.1 with TWRP recovery and decided to switch back to stock so I could sell the device.
I downloaded the RUU for my device from htc's site (ruu 6.12.1540.4 for unlocked/developer htc one m8).
I plugged in my device, typed in "fastboot oem lock" until the top of the bootloader said "Software status: modified" and "RELOCKED."
Then I ran the RUU but got Error 155 saying it was the wrong RUU. My device now had a silver HTC logo stuck in the middle. I pressed the power + volume down and got to the bootloader.
But now there is no option for "Recovery" in the bootloader, and the "Reboot" option just takes me straight back to the bootloader.
Here is what it says at the bootloader now:
***Software status: Modified***
*** RELOCKED***
***Security Warning ***
It says OS-4.16.1540.8
In addition, I can't charge without the screen being on. I plug in my phone and it shows the battery icon for a few seconds and then goes back into the booloader with "fastboot ac"
Please help me get my device working & back to stock. Any information or tips will help. I can take photos and provide with any additional information if needed.
Thanks.
Click to expand...
Click to collapse
Are you S-Off? Is your device Developer Edition?
Sent from my HTC One_M8 using Tapatalk
AeroPeg said:
I have a US HTC One M8 that I bought direct unlocked from htc's site direct in January 2015.
I rooted my device, and was running Paranoid Android 5.1 with TWRP recovery and decided to switch back to stock so I could sell the device.
I downloaded the RUU for my device from htc's site (ruu 6.12.1540.4 for unlocked/developer htc one m8).
I plugged in my device, typed in "fastboot oem lock" until the top of the bootloader said "Software status: modified" and "RELOCKED."
Then I ran the RUU but got Error 155 saying it was the wrong RUU. My device now had a silver HTC logo stuck in the middle. I pressed the power + volume down and got to the bootloader.
But now there is no option for "Recovery" in the bootloader, and the "Reboot" option just takes me straight back to the bootloader.
Here is what it says at the bootloader now:
***Software status: Modified***
*** RELOCKED***
***Security Warning ***
It says OS-4.16.1540.8
In addition, I can't charge without the screen being on. I plug in my phone and it shows the battery icon for a few seconds and then goes back into the booloader with "fastboot ac"
Please help me get my device working & back to stock. Any information or tips will help. I can take photos and provide with any additional information if needed.
Thanks.
Click to expand...
Click to collapse
about error 155, try the following
1. Lock your bootloader through by booting into hboot and then going into fastboot and issuing the command "fasboot oem lock".
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Should work. Best of luck
How do I flash a new recovery?
SergioRmz, My device is S-ON, not developer edition, just factory unlocked from htc
Rawfire, I can't flash a RUU. The RUU just gives me an error after a few seconds from starting it - it says try again with a different RUU / wrong RUU (error 155).
Also, could you help me flash a new recovery? Could I flash a new recovery, then flash someone's stock nandroid backup & recovery to get my device to stock? Can I do all of this with a RELOCKED & S-ON device?
I have no idea how to flash a new recovery so instructions would be very very helpful
One final question - Can you tell me the best way in my current sitatution to get my device to stock without S-OFF? I'm willing to try anything (except S-off) to get my device to stock so I can sell it / trade it in.
AeroPeg said:
SergioRmz, My device is S-ON, not developer edition, just factory unlocked from htc
Rawfire, I can't flash a RUU. The RUU just gives me an error after a few seconds from starting it - it says try again with a different RUU / wrong RUU (error 155).
Also, could you help me flash a new recovery? Could I flash a new recovery, then flash someone's stock nandroid backup & recovery to get my device to stock? Can I do all of this with a RELOCKED & S-ON device?
I have no idea how to flash a new recovery so instructions would be very very helpful
One final question - Can you tell me the best way in my current sitatution to get my device to stock without S-OFF? I'm willing to try anything (except S-off) to get my device to stock so I can sell it / trade it in.
Click to expand...
Click to collapse
I can suggest couple of things, unlock the bootloader to install custom recovery and then you can flash any compatible rom,
Or to suggest some exact RUU, what's your device's exact model?
rawfire said:
about error 155, try the following
1. Lock your bootloader through by booting into hboot and then going into fastboot and issuing the command "fasboot oem lock".
2. Once locked, reboot your system.
3. Open RUU and follow onscreen instructions.
Should work. Best of luck
Click to expand...
Click to collapse
Just tried this, said "Device was already locked!"
Then tried RUU again, still said Error 155 "please get the correct RUU and try again"
When I unplug the phone it says error zip file with RUU written under it, and I had to press power + volume down to get it to the bootloader again.
Thanks for your continued help rawfire.
AeroPeg said:
Just tried this, said "Device was already locked!"
Then tried RUU again, still said Error 155 "please get the correct RUU and try again"
When I unplug the phone it says error zip file with RUU written under it, and I had to press power + volume down to get it to the bootloader again.
Thanks for your continued help rawfire.
Click to expand...
Click to collapse
Considering your firmware, I would suggest you to try THIS RUU & flash...
Device info
Thanks rawfire, downloading it now...
My phone says os-4.16.1540.8
Is there any other device info you need?
AeroPeg said:
Thanks rawfire, downloading it now...
My phone says os-4.16.1540.8
Is there any other device info you need?
Click to expand...
Click to collapse
try this one out, I'm sure it'll work.
Can't open
rawfire said:
try this one out, I'm sure it'll work.
Click to expand...
Click to collapse
Windows says invalid file, can't open.
7 zip can't extract either. I've tried both mirrors
Any other RUU suggestions?
AeroPeg said:
Thanks rawfire, downloading it now...
My phone says os-4.16.1540.8
Is there any other device info you need?
Click to expand...
Click to collapse
Is that os-4.16.1540.8 written on the bootloader ? If yes, you have a Dev Ed device, the other RUU meant for EU won't work for you.
Post fastboot getvar all (without serial & imei no.) then we know the actual device version
If it is indeed a Dev Ed device, what you need to do :
1. flash the 6.12.1540.4 firmware
See this : http://forum.xda-developers.com/showpost.php?p=64407841&postcount=2862
How-to, see this : http://forum.xda-developers.com/showpost.php?p=64416322&postcount=2864
2. Run RUU 6.12.1540.4 after the firmware is installed
Or the easy way is :
find 4.16.1540.8 RUU and install this then after, do OTA to 4.17.1540.9 then 6.12.1540.4
Edit : here is the direct HTC link for 4.16.1540.8 RUU - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
Fastboot getvar all
ckpv5 said:
Is that os-4.16.1540.8 written on the bootloader ? If yes, you have a Dev Ed device, the other RUU meant for EU won't work for you.
Post fastboot getvar all (without serial & imei no.) then we know the actual device version
If it is indeed a Dev Ed device, what you need to do :
1. flash the 6.12.1540.4 firmware
See this : http://forum.xda-developers.com/showpost.php?p=64407841&postcount=2862
How-to, see this : http://forum.xda-developers.com/showpost.php?p=64416322&postcount=2864
2. Run RUU 6.12.1540.4 after the firmware is installed
Or the easy way is :
find 4.16.1540.8 RUU and install this then after, do OTA to 4.17.1540.9 then 6.12.1540.4
Edit : here is the direct HTC link for 4.16.1540.8 RUU - http://dl3.htc.com/application/RUU_...G_20.68.4196.01_F_release_411207_signed_2.exe
Click to expand...
Click to collapse
Here's what I got when I typed fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.035s
Update: just googled 0P6B12000 is Dev edition, my bad. Going to try easy method of installing the 4.16.1540.8 RUU. Thanks ckpv5. Will post with results.
AeroPeg said:
Here's what I got when I typed fastboot getvar all:
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul_ca
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
Click to expand...
Click to collapse
Then it is confirmed that you have a Dev Ed device.
Go with the easy way that I posted above. Install RUU 4.16.1540.8 then do OTA to the latest, done.
Additional - as you mentioned you're going to sell this device, I suggest after the last OTA 6.12.1540.4 is done, run RUU 6.12.1540.4 to remove all the OTA leftovers in device. You'll have a clean device after the last RUU.
4.16.1540.8 RUU stuck
ckpv5 said:
Then it is confirmed that you have a Dev Ed device.
Go with the easy way that I posted above. Install RUU 4.16.1540.8 then do OTA to the latest, done.
Additional - as you mentioned you're going to sell this device, I suggest after the last OTA 6.12.1540.4 is done, run RUU 6.12.1540.4 to remove all the OTA leftovers in device. You'll have a clean device after the last RUU.
Click to expand...
Click to collapse
4.16.1540.8 RUU has been stuck at "Updating.. (0/7) Sending....." for 20+ minutes now. Phone is showing just the silver htc logo, no progress bar or anything else.
Should I try flashing the 6.12.1540.4 firmware now? Thanks for the help so far ckpv5
Also, is the phone charging while connected to the computer & updating? Just asking since I can't see the battery percent (no OS) and don't want the phone to die while flashing.
AeroPeg said:
4.16.1540.8 RUU has been stuck at "Updating.. (0/7) Sending....." for 20+ minutes now.
Click to expand...
Click to collapse
This show you have USB/PC connection problem. To run RUU you need Windows PC with USB2.0 and the latest HTC USB drivers installed.
See the How-To linked above for the HTC Sync Manager download page, install it as it will install the USB Driver, then uninstall the Sync Manager but leave the driver
While flashing .. charging is minimal, won''t be enough if you don't have at least 70% battery
ckpv5 said:
This show you have USB/PC connection problem. To run RUU you need Windows PC with USB2.0 and the latest HTC USB drivers installed.
See the How-To link above.
While flashing .. charging is minimal, won''t be enough if you don't have at least 70% battery
Click to expand...
Click to collapse
Thanks for the info, going to reinstall HTC Sync Manager and try again. Does it need to be USB 2.0, or can it be USB 3.0?
Also, how long can I charge without having the screen burn because when I plug in the phone to the wall or the the computer, it shows the bootloader screen. It stays in that screen while charging so I don't want to charge for extended periods otherwise screen will burn. Can you tell me if I am right on this?
AeroPeg said:
Thanks for the info, going to reinstall HTC Sync Manager and try again. Does it need to be USB 2.0, or can it be USB 3.0?
Also, how long can I charge without having the screen burn because when I plug in the phone to the wall or the the computer, it shows the bootloader screen. It stays in that screen while charging so I don't want to charge for extended periods otherwise screen will burn. Can you tell me if I am right on this?
Click to expand...
Click to collapse
You must use USB2.0
When in bootloader, choose power down then charge it, you'll see the progress and there will be no screen burn.
If you don't have a USB2.0 - other options :
Option 1:
Clean your PC temp folder - just select "run" then type %temp% and clear all that your can.
Run the RUU again (not necessary to connect to phone), when the RUU dialog open, check in %temp% you should see two new folders are created. Find ROM.zip in one of the folder, copy out the ROM.zip to your desktop. You can close the RUU dialog box.
Rename the RUU.zip to 0P6BIMG.zip (that's a zero not "O") then put it on your microSD.
boot to bootloader then select hboot or boot to hboot - it's your choice
hboot will scan the file and ask to volume up to update
volume up
finish, press power to reboot and do all the setup stuff
remove 0P6BIMG.zip from your microSD
now you have ROM installed then can proceed with OTA and the rest.
Option 2:
Re unlock your bootloader again with your unlock_code.bin that you got from HTC.
Install TWRP 2.8.7.0
Restore a clean non-rooted 4.16.1540.8 nandroid backup and its stock recovery
Reboot.. setup.. OTA..OTA.. done.
You can get all the needed files in the link shown in my signature
So now .. you have 3 options to choose.
1. RUU method
2. 0P6BIMG.zip method
3. Nandroid method
I got to go now ... good luck
SOLUTION - see ckpv5's 3 solutions
ckpv5 said:
You must use USB2.0
When in bootloader, choose power down then charge it, you'll see the progress and there will be no screen burn.
If you don't have a USB2.0 - other options :
Option 1:
Clean your PC temp folder - just select "run" then type %temp% and clear all that your can.
Run the RUU again (not necessary to connect to phone), when the RUU dialog open, check in %temp% you should see two new folders are created. Find ROM.zip in one of the folder, copy out the ROM.zip to your desktop. You can close the RUU dialog box.
Rename the RUU.zip to 0P6BIMG.zip (that's a zero not "O") then put it on your microSD.
boot to bootloader then select hboot or boot to hboot - it's your choice
hboot will scan the file and ask to volume up to update
volume up
finish, press power to reboot and do all the setup stuff
remove 0P6BIMG.zip from your microSD
now you have ROM installed then can proceed with OTA and the rest.
Option 2:
Re unlock your bootloader again with your unlock_code.bin that you got from HTC.
Install TWRP 2.8.7.0
Restore a clean non-rooted 4.16.1540.8 nandroid backup and its stock recovery
Reboot.. setup.. OTA..OTA.. done.
You can get all the needed files in the link shown in my signature
So now .. you have 3 options to choose.
1. RUU method
2. 0P6BIMG.zip method
3. Nandroid method
I got to go now ... good luck
Click to expand...
Click to collapse
Thanks a TON ckpv5. I followed your instructions & reinstalled HTC Sync Manager, then connected the cable to a USB 2.0 port instead of 3.0. The RUU method you originally suggested worked like a charm. I now have stock HTC software, stock recovery just like I wanted. I then did an OTA to the latest software. When I sell my device in a few days, I'll be sure to follow your tip and run the latest 6.12.1540.4 RUU to clear off all the old OTA files.
Many thanks again for your help - hopefully others will see the 3 solutions you posted.
Hi. my mid and bootlader Can i flash 4.16.1540.8 my device gets updated
Thanks..
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.25.214500021.06G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.401.10
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT44LWM05174
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
ceylin45 said:
Hi. my mid and bootlader Can i flash 4.16.1540.8 my device gets updated
Click to expand...
Click to collapse
Yes ... just follow what is written on top post above.
Hello XDA,
I have an HTC one m8 in my possession which i am trying to unbrick but i'm having some issues.
The phone has custom recovery Philz
I have no SD card available to me at the moment
I have relocked the bootloader to try and run the RUU 'RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4'
installer as part of my efforts to unbrick, but this doesn't work, the RUU installer gets stuck at 0% while 'Sending'.
Any help would be much appreciated
Not enough info. Do a fastboot getvar all, and post the results (be sure to delete IMEI and serial numbers, as these are private info).
In particular, need (at a minimum):
CID
MID
s-off or s-on
firmware (main) version
hboot number
radio number
Bootloader status (locked, relocked, unlocked)
Original version (CID, MID) if those numbers have been modified
Also, did you try the RUU just once, or multiple times? A number of folks have reported it hanging on sending, but then it will run properly on a subsequent attempt.
Thanks for the reply, here is all the information i could acquire.
***TAMPERED***
***RELOCKED***
***Security Warning***
M8_UL PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO-1.19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__002
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 5e4b24e4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I have tried running the RUU multiple times
Redragonrc said:
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__002
I have tried running the RUU multiple times
Click to expand...
Click to collapse
The RUU you stated in the top post won't work (its the RUU for the Developer's Edition). The RUU needs to match your CID and MID, meaning you need the RUU for the Euro version, which doesn't have Marshmallow yet.
Best bet is to run the Lollipop RUU for the Euro version (4.16.401.10) which can be found here: http://forum.xda-developers.com/showthread.php?t=2701376
I have run the 4.16.401.10 RUU.exe but it just gets stuck at Updating...(0/7) Sending...
I have done done the prerequisites for running the RUU:
disabled antivirus, updated HTC drivers, run the RUU as admin
I checked that i have USB data communications with adb:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
HT43JWM06196 fastboot
Redragonrc said:
I have run the 4.16.401.10 RUU.exe but it just gets stuck at Updating...(0/7) Sending...
I have done done the prerequisites for running the RUU:
disabled antivirus, updated HTC drivers, run the RUU as admin
I checked that i have USB data communications with adb:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
HT43JWM06196 fastboot
Click to expand...
Click to collapse
Hi ,can you try on another pc/ laptop
Redragonrc said:
I have run the 4.16.401.10 RUU.exe but it just gets stuck at Updating...(0/7) Sending...
Click to expand...
Click to collapse
Try running it again. RUU is known to hang from time to time, then work on subsequent attempts.
If it still doesn't work, try another PC, as suggested above. Win7 and USB 2.0 have the best chance of success.
Or you can download the zip version, rename to 0P6BIMG.zip and put it on the phone. Reboot to bootloader, and it should install.
bombo_b said:
Hi ,can you try on another pc/ laptop
Click to expand...
Click to collapse
Hi,
I just tried it on another computer and the same result.
redpoint73 said:
Try running it again. RUU is known to hang from time to time, then work on subsequent attempts.
If it still doesn't work, try another PC, as suggested above. Win7 and USB 2.0 have the best chance of success.
Or you can download the zip version, rename to 0P6BIMG.zip and put it on the phone. Reboot to bootloader, and it should install.
Click to expand...
Click to collapse
I managed to reach 1/7 through the RUU.exe and gave me a 155 error.
I don't have a Windows 7 computer avaliable to me only Windows 10.
I could try buying an SD card, putting the rom onto the SD card, unlock the bootloader and run the custom recovery again and try to install the from from the SD card?
It also appears there is TWRP and Philz recovery on this device, could this be the cause of any problems?
Redragonrc said:
I could try buying an SD card, putting the rom onto the SD card, unlock the bootloader and run the custom recovery again and try to install the from from the SD card?
Click to expand...
Click to collapse
You can do that, but you'd have to use a Kitkat ROM, as your firmware is (old) Kitkat. And you would be stuck on the KitKat ROM until you updated the firmware.
I think its better to get the RUU to work, such as adb push the RUU zip to the phone's internal storage, and run in bootloader.
Redragonrc said:
It also appears there is TWRP and Philz recovery on this device, could this be the cause of any problems?
Click to expand...
Click to collapse
Its one or the other, you can't have both (TWRP and Philz) on the phone at the same time.
Do you mean, is it the cause of RUU not running? NO.
Hello,
The RUU.exe has made some progress and now hangs at 1/8 consistantly.
redpoint73 said:
I think its better to get the RUU to work, such as adb push the RUU zip to the phone's internal storage, and run in bootloader..
Click to expand...
Click to collapse
I have tried to adb sideload the rom but i just get 'cannot read'
Redragonrc said:
could you explain how i can do this? thanks
Click to expand...
Click to collapse
Actually, I'm realizing (reading in another thread) that the RUU zip needs to be on a removable SD, not on internal storage (haven't actually done it this way, I always use the RUU.exe).
From what I understand, put the 0p6bimg.zip on the SD card (as you mentioned, you will need to buy one) then boot into bootloader, and it will install.
Another alternative, you can apparently also fastboot flash the RUU:
http://forum.xda-developers.com/htc-one-m8/general/htc-one-m8-european-signed-ruu-0p6bimg-t2911563
---------- Post added at 04:35 PM ---------- Previous post was at 03:54 PM ----------
Redragonrc said:
I have tried to adb sideload the rom but i just get 'cannot read'
Click to expand...
Click to collapse
A ROM or an RUU? What file exactly?
Post a screenshot of the adb commands and responses, if you can.
Hi again,
Went and got myself and SD card and put cm13 on it from which i've loaded the rom and got myself a working phone now.
I went ahead an ran the RUU after installing cm13 and the RUU ran perfectly.
It seems using the SD card was the best option for me.
Thanks Redpoint73 for all the help so far.
P.S it seems my m8 is a retail version as the stock rom i installed has a demo application that wipes the phone everyday, but this is an easy solution as i will just install another custom os or something. i just can't use stock. :<
Redragonrc said:
P.S it seems my m8 is a retail version as the stock rom i installed has a demo application that wipes the phone everyday, but this is an easy solution as i will just install another custom os or something. i just can't use stock. :<
Click to expand...
Click to collapse
What "stock ROM" are you referring to?
The ROM installed by the RUU you stated in Post #1 shouldn't be doing this.
Hello, i am having a big trouble here
I was trying to format my phone but the bootloader's screen does not appear, it's been a while, when I enter the bootloader screen is just black, but the options work , I entered on recovery screen and went wipe, ticked all the options and I wipe , now my phone does not show anything, only black screen.
When i press power+up for 15 seconds, the cell shakes, i can flash recovery using fastboot by cmd, i can use anything with fastboot, but if i try something with adb, it says that i dont have adb devices. Can i solve my problem using fastboot option? i already flash a recovery by fastboot, but i cant enter on recovery, i can enter on fastboot reboot-bootloader for example.
Someone can help me plz?
Thx for attention. And sorry for bad english hehehe
Tirania_br said:
but if i try something with adb, it says that i dont have adb devices.
Click to expand...
Click to collapse
This is normal, and as it should be. adb command only work within OS and recovery, adb command do NOT work in bootloader.
I've seen a few reports of this issue (black screen in bootloader, although the options work if you select them "blindly"). If an RUU exists for your version, I would try to run that RUU, and see if that helps.
redpoint73 said:
This is normal, and as it should be. adb command only work within OS and recovery, adb command do NOT work in bootloader.
I've seen a few reports of this issue (black screen in bootloader, although the options work if you select them "blindly"). If an RUU exists for your version, I would try to run that RUU, and see if that helps.
Click to expand...
Click to collapse
thx, i found a RUU for my phone but very old, and found another current version here, but not for my version.
i have s-off on phone, these the information
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) cidnum: HTC__621
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I dont have any acess on cellphone screen, all i can do is fastboot code on my pc.
I have 2 questions.
How can i flash this RUU in my situation?
Is better use the old RUU of my version or the new of another version? i can use because i am s-off, or am i wrong?
thx for help
Tirania_br said:
I dont have any acess on cellphone screen, all i can do is fastboot code on my pc.
I have 2 questions.
How can i flash this RUU in my situation?
Click to expand...
Click to collapse
RUU is ideal to flash in fastboot mode. So being in fastboot mode (even if you can't see the screen) is a good thing.
Tirania_br said:
Is better use the old RUU of my version or the new of another version? i can use because i am s-off, or am i wrong?
Click to expand...
Click to collapse
Either should work under the proper conditions below:
1) Older RUU for your version may fail with Error 155. Going back to pre-MM by RUU usually requires flashing the older fimrware.zip, then RUU in order to bypass Error 155.
2) S-off alone is not enough to flash another version's RUU. You need to change the CID, and possibly the MID (if its different from what the RUU requires). But those aren't difficult with s-off.
Now, whether either one of those will help your issue (blank screen on bootloader) is the big question. But I'd say RUU is your best bet at a fix.
redpoint73 said:
RUU is ideal to flash in fastboot mode. So being in fastboot mode (even if you can't see the screen) is a good thing.
Either should work under the proper conditions below:
1) Older RUU for your version may fail with Error 155. Going back to pre-MM by RUU usually requires flashing the older fimrware.zip, then RUU in order to bypass Error 155.
2) S-off alone is not enough to flash another version's RUU. You need to change the CID, and possibly the MID (if its different from what the RUU requires). But those aren't difficult with s-off.
Now, whether either one of those will help your issue (blank screen on bootloader) is the big question. But I'd say RUU is your best bet at a fix.
Click to expand...
Click to collapse
Hi, before i do all steps i want to know if i will do everyting ok
my cell's information again
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.24_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.20.709.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: HTC__621
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 205bdca3
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
i didnt get RUU of my version. I got 4.17.1540.9 - HTC One U.S. Developer Edition.
The steps
fastboot oem writecid BS_US002
fastboot reboot-bootloader
fastboot oem lock - i really need to do this?
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip OR Double-click the file and run it as any other executable program.
Its alright?
Tirania_br said:
i didnt get RUU of my version. I got 4.17.1540.9 - HTC One U.S. Developer Edition.
The steps
fastboot oem writecid BS_US002
fastboot reboot-bootloader
fastboot oem lock - i really need to do this?
fastboot oem rebootRUU
htc_fastboot flash zip ruu.zip OR Double-click the file and run it as any other executable program.
Its alright?
Click to expand...
Click to collapse
Just changing the CID is not enough to run that RUU, you need to match the Dev Edition MID as well. Instructions here: http://forum.xda-developers.com/showthread.php?t=2708581
The 4.17.1540.9 RUU is Lollipop. So it will probably fail with Error 155 as I already point out (Item 1 in my last post) forcing you to flash the firmware seperately, then RUU again. You're adding more complexity than needed (for no good reason). Therefore, I'd suggest the Dev Edition MM RUU 6.12.1540.4, if you are going to convert to Dev Edition (CID, MID, etc.). RUU 6.12.1540.4 linked at the bottom of the following: http://www.htc.com/us/support/htc-one-m8/news/
No need to relock the bootloader. This isn't required to RUU since you are s-off (only required to RUU when s-on). And I also do not recommend to lock the bootloader. There is no benefit to doing so in your case (since its not required to RUU) and an unlocked bootloader gives you more options if you run into more issues (you can flash custom recovery, etc.). So locking the bootloader is a waste of steps and time, and limits your options.
redpoint73 said:
Just changing the CID is not enough to run that RUU, you need to match the Dev Edition MID as well. Instructions here: http://forum.xda-developers.com/showthread.php?t=2708581
The 4.17.1540.9 RUU is Lollipop. So it will probably fail with Error 155 as I already point out (Item 1 in my last post) forcing you to flash the firmware seperately, then RUU again. You're adding more complexity than needed (for no good reason). Therefore, I'd suggest the Dev Edition MM RUU 6.12.1540.4, if you are going to convert to Dev Edition (CID, MID, etc.). RUU 6.12.1540.4 linked at the bottom of the following: http://www.htc.com/us/support/htc-one-m8/news/
No need to relock the bootloader. This isn't required to RUU since you are s-off (only required to RUU when s-on). And I also do not recommend to lock the bootloader. There is no benefit to doing so in your case (since its not required to RUU) and an unlocked bootloader gives you more options if you run into more issues (you can flash custom recovery, etc.). So locking the bootloader is a waste of steps and time, and limits your options.
Click to expand...
Click to collapse
thank you! i am almost there!
now the steps i have to do:
adb shell
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x32\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
adb reboot bootloader
fastboot getvar all //see if change mid
fastboot fastboot reboot-bootloader
fastboot oem writecid BS_US002
fastboot reboot-bootloader
fastboot getvar all //see if change cid
fastboot oem rebootRUU //need do this? if my Ruu is .exe
Double-click the file and run it as any other executable program. Follow the instructions by the program.
I have only one big problem now, the first command, i cant use adb, i can only use with fastboot, don't know why. adb device cant find, i have the drivers, the pc does a sound when i connect the phone, if i press power button on black screen bootloader i enter in fastboot mode and this commands i can do.
there is a command to do this with fastboot?
Tirania_br said:
I have only one big problem now, the first command, i cant use adb, i can only use with fastboot, don't know why. adb device cant find, i have the drivers, the pc does a sound when i connect the phone, if i press power button on black screen bootloader i enter in fastboot mode and this commands i can do.
Click to expand...
Click to collapse
adb command don't work in bootloader, as I already stated.
Do you still have TWRP custom recovery (its not clear, based on your descriptions so far). If so, boot into recovery, and try adb commands.
redpoint73 said:
adb command don't work in bootloader, as I already stated.
Do you still have TWRP custom recovery (its not clear, based on your descriptions so far). If so, boot into recovery, and try adb commands.
Click to expand...
Click to collapse
I did not have more , when I tried to enter on recovery mode the cell came into loop , I downloaded a new version of the recovery , for my surprise it worked! got access to recovery , now everything was much easier! thank you for help and understanding. Now I have my phone back ! haha
Tirania_br said:
I did not have more , when I tried to enter on recovery mode the cell came into loop , I downloaded a new version of the recovery , for my surprise it worked! got access to recovery , now everything was much easier! thank you for help and understanding. Now I have my phone back ! haha
Click to expand...
Click to collapse
i thinked my problem was gone, but when i try to run the Ruu i get always error 155.
i think is because my cellphone is cdma, from taiwan...
I took back my old cid and mid, restored a nandroid and now is ok.
The bootloader still with black screen, but i can live with it.
Thank u for attention, u help me a lot
Tirania_br said:
i thinked my problem was gone, but when i try to run the Ruu i get always error 155.
i think is because my cellphone is cdma, from taiwan...
I took back my old cid and mid, restored a nandroid and now is ok.
The bootloader still with black screen, but i can live with it.
Thank u for attention, u help me a lot
Click to expand...
Click to collapse
First .. your device is not a CDMA device, it is a GSM.
What you can try to fix that bootloader with black screen ... flash full signed 6.20.709.2 firmware.zip.
You can get the full signed firmware in my thread (post #5) : http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860