Develop Bugs

[Q] Desire HD freezes on startup and can't install RUU [PICs]

Hello,
i hope some one can help me
Phone is unlocked so it doesn't matter which rom i use, i just want it to work again, but warranty is gone cause this happened when i tried to install a rooted rom
it freezes on startup (HTC logo and white screen)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i downloaded 3 RUU .exe roms, after opening them on TEMP folder of windows copied rom.zip
renamed it to PD98IMG.zip and update.zip but neither of them fixed the problem i read somewhere that it should find the file and start the update but it just loads the file like picture below and then nothing happens
after loading it shows this page and nothing...
i dont know what should i do to install them from SD Card so i tried Recovery section and then this happened for all 3 roms
it keeps saying E: Can't Open /sdcard/PD98IMG.zip (bad)
for all 3 RUU roms, what should i do?

letgrab said:
Hello,
i hope some one can help me
Phone is unlocked so it doesn't matter which rom i use, i just want it to work again, but warranty is gone cause this happened when i tried to install a rooted rom
it freezes on startup (HTC logo and white screen)
i downloaded 3 RUU .exe roms, after opening them on TEMP folder of windows copied rom.zip
renamed it to PD98IMG.zip and update.zip but neither of them fixed the problem
i dont know what should i do to install them from SD Card so i tried Recovery section and then this happened for all 3 roms
it keeps saying E: Can't Open /sdcard/PD98IMG.zip (bad)
for all 3 RUU roms, what should i do?
Click to expand...
Click to collapse
You have to relock the bootloader and then reflash the Ruu in the PD98IMG.zip way.
To relock, just boot to hboot and choose fastboot.
Plug the phone and You should see fastboot USB in red.
Open a CMD as admin or terminal as root in the PC
Type: fastboot oem lock
Then, just re try booting in hboot with the Ruu in the root of the sdcard....

glevitan said:
You have to relock the bootloader and then reflash the Ruu in the PD98IMG.zip way.
To relock, just boot to hboot and choose fastboot.
Plug the phone and You should see fastboot USB in red.
Open a CMD as admin or terminal as root in the PC
Type: fastboot oem lock
Then, just re try booting in hboot with the Ruu in the root of the sdcard....
Click to expand...
Click to collapse
thank you so much
i did as you said, Red FASTBOOT USB appeared in phone and windows recognized MY HTC
then i opened CMD as administrator and typed fastboot oem lock
but this happened
'fastboot' is not recognized as an internal or external command.

letgrab said:
thank you so much
i did as you said, Red FASTBOOT USB appeared in phone and windows recognized MY HTC
then i opened CMD as administrator and typed fastboot oem lock
but this happened
Click to expand...
Click to collapse
ok...you don't have the adb drivers. Unplug the phone and download the Hack Kit, unzip it and just run the hack-ace.cmd as admin. That will install the adb drivers and so other commands, then close it. Plug the phone back and again from fastboot usb in red try the command
http://forum.xda-developers.com/showthread.php?t=1259821

glevitan said:
ok...you don't have the adb drivers. Unplug the phone and download the Hack Kit, unzip it and just run the hack-ace.cmd as admin. That will install the adb drivers and so other commands, then close it. Plug the phone back and again from fastboot usb in red try the command
http://forum.xda-developers.com/showthread.php?t=1259821
Click to expand...
Click to collapse
ok im on it ,i will reply with result
i don't know how to thank you
i was really upset about this

letgrab said:
ok im on it ,i will reply with result
i don't know how to thank you
i was really upset about this
Click to expand...
Click to collapse
if it fails, just let me know...we will sort it out...

glevitan said:
if it fails, just let me know...we will sort it out...
Click to expand...
Click to collapse
[edit] sorry i'm reading the manual now, i think i know why this happened, i'm uninstalling HTC Sync and drivers and then install drivers inside this hack
my connection is slow so it took a while to download
i tried running hack-ace.cmd as admin
but the following errors appeared
then i connected the phone and tried again, the same error appeared

letgrab said:
[edit] sorry i'm reading the manual now, i think i know why this happened, i'm uninstalling HTC Sync and drivers and then install drivers inside this hack
my connection is slow so it took a while to download
i tried running hack-ace.cmd as admin
but the following errors appeared
then i connected the phone and tried again, the same error appeared
Click to expand...
Click to collapse
I have just sent u a PM...

finally i RELOCKED the phone
now i got a new error i think its because i've chosen the wrong rom am i right? so im downloading a new one
i got your message my friend, but now i've relocked i don't think its necessary any more is it?
btw do you have a LibertyReserve account for Donations?
i dont have paypal or visa but i really wanna donate something, your help is really appreciated

letgrab said:
finally i RELOCKED the phone
now i got a new error i think its because i've chosen the wrong rom am i right? so im downloading a new one
i got your message my friend, but now i've relocked i don't think its necessary any more is it?
btw do you have a LibertyReserve account for Donations?
i dont have paypal or visa but i really wanna donate something, your help is really appreciated
Click to expand...
Click to collapse
There's no need to donate. Thanks I appreciate it.
Now that u are relocked, I need the CID number to find a working RUU.
To get that, boot in fastboot, plug the phone (fastboot usb in red)
Open a cmd as admin and type: fastboot getvar all. Find the INFOcidnum...and paste it here.

glevitan said:
There's no need to donate. Thanks I appreciate it.
Now that u are relocked, I need the CID number to find a working RUU.
To get that, boot in fastboot, plug the phone (fastboot usb in red)
Open a cmd as admin and type: fastboot getvar all. Find the INFOcidnum...and paste it here.
Click to expand...
Click to collapse
INFOcidnum is: HTC__621

letgrab said:
INFOcidnum is: HTC__621
here are more info if needed
Click to expand...
Click to collapse
Do not publish your IMEI..I just got what I wanted....
---------- Post added at 07:58 PM ---------- Previous post was at 07:42 PM ----------
glevitan said:
Do not publish your IMEI..I just got what I wanted....
Click to expand...
Click to collapse
Okay, the issue is that there's no direct ruu for your CID number. But u can try the following.
Plug the phone in fastboot, then run the Hack Kit as admin and choose the fastboot method...see what happens. If not you will have to create a goldcard with the sdcard CID.

glevitan said:
Do not publish your IMEI..I just got what I wanted....
---------- Post added at 07:58 PM ---------- Previous post was at 07:42 PM ----------
Okay, the issue is that there's no direct ruu for your CID number. But u can try the following.
Plug the phone in fastboot, then run the Hack Kit as admin and choose the fastboot method...see what happens. If not you will have to create a goldcard with the sdcard CID.
Click to expand...
Click to collapse
no it didn't work , it works with error when im on ClockworkMod but nothing on fastboot menu
i find a little number maybe 12 digits on sdcard (starts with 0935 i think cant read it), but its so small and engraved in black

letgrab said:
no it didn't work , it works with error when im on ClockworkMod but nothing on fastboot menu
i find a little number maybe 12 digits on sdcard, but its so small and engraved in black
Click to expand...
Click to collapse
then you will have to create a goldcard and downgrade to an unbranded GB RUU. DO NOT ATEMPT TO DOWNGRADE TO A FROYO RUU...

glevitan said:
then you will have to create a goldcard and downgrade to an unbranded GB RUU. DO NOT ATEMPT TO DOWNGRADE TO A FROYO RUU...
Click to expand...
Click to collapse
thanks but where can i find a GingerBread RUU for my CID

glevitan said:
then you will have to create a goldcard and downgrade to an unbranded GB RUU. DO NOT ATEMPT TO DOWNGRADE TO A FROYO RUU...
Click to expand...
Click to collapse
This is how to create a goldcard: http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
Then just place the file I will send u (rename it PD98IMG.zip) in the root of the sdcard and boot in hboot.
OR
you can unlock the bootloader again and then try flashing a custom rom...there's a way...gotta find the thread.
Found it!!...read this:
http://forum.xda-developers.com/showthread.php?t=1781802&highlight=unlock+bootloader+

glevitan said:
This is how to create a goldcard: http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
Then just place the file I will send u (rename it PD98IMG.zip) in the root of the sdcard and boot in hboot.
OR
you can unlock the bootloader again and then try flashing a custom rom...there's a way...gotta find the thread.
Found it!!...read this:
http://forum.xda-developers.com/showthread.php?t=1781802&highlight=unlock+bootloader+
Click to expand...
Click to collapse
thanks
im on it now, will reply result
btw whats the command to Unlock Hboot again

letgrab said:
thanks
im on it now, will reply result
btw whats the command to Unlock Hboot again
Click to expand...
Click to collapse
If I am not wrong Is: fastboot oem unlock
Hope it works

i tried everything
my last hope is trying to install a Custom Rom ( Android Revolution HD 7.0.4 ) from Recovery section i just want it to work again doesn't matter RUU or any rom (can't open RUU roms in Recovery it says Cant Open Bad File i hope this doesn't happen to custom roms)
its downloading now and i hope it works
thank you my friend for your help today, you tried to help me step by step and im really grateful

letgrab said:
i tried everything
my last hope is trying to install a Custom Rom ( Android Revolution HD 7.0.4 ) from Recovery section i just want it to work again doesn't matter RUU or any rom (can't open RUU roms in Recovery it says Cant Open Bad File i hope this doesn't happen to custom roms)
its downloading now and i hope it works
thank you my friend for your help today, you tried to help me step by step and im really grateful
Click to expand...
Click to collapse
Well, hope it works...just let me know...we will work something out.

[Q] Start anew

Hello,
To start off, I want to say that I DID search on this forum, for similar threads, and while I did find some, I couldn't find out how to do it.
My Phone:
HTC One X
S-ON
Rooted
Locked bootloader
ROM: Android Revolution HD
CID: HTC__E11
I flashed my current ROM a while ago, but I really cannot remember doing it and I deleted the backup I made before flashing (I always back up before flashing) because I thought I was running the stock ROM (without trouble) and I needed space.
What I want to do now, is get rid of EVERYTHING and just reset it to what it was when I first booted it, when that's all done, I want to root it again and unlock the bootloader.
The problem is that I can't find the appropriate RUU. I've been looking for it for a good while now, but I can't seem to find it.
I've downloaded OTA_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27-2.17.401.2_release_298985n1wwcwzs385c0bvz.zip from
htcruu.com/ index.php?dir=Endeavor (not allowed to put links here, sorry) and I put that in my SDCard directory.
When I tried to flash it (I don't know whether I am supposed to or not, but I only got a .zip and no .exe...) it did not work.
If you need the error, tell me and I'll do it again.
Regards,
Pim

If you can't find a ruu, you can use a stock nandroid backup. You can find a collection of them at general if I remember correctly.
Sent from my HTC One X

The ruu doesn't work because it's an OTA ....its just an update file ! Not the whole RUU
http://www.htcruu.com/securekey.php...Radio_5.1204.162.29_release_298897_signed.exe
this is the full RUU

Yes. Previous poster is correct. Download that file.
Do not put it on your sdcard.
Plug your phone into PC
Reboot into hboot by holding power & volume down for about 20seconds.
Press power button to go to fastboot
Open a cmd window and run fastboot oem lock to relock your bootloader
Run your ruu as administrator on your PC by right clicking and pressing open as administrator
Follow the instructions on your PC to flash the ruu
Sent from my HTC One X using xda app-developers app

Thanks a lot, but I'm still having trouble :s
I connect my phone to my pc via USB when I am looking at these options on my screen:
- HBOOT
- REBOOT
- REBOOT BOOTLOADER
- POWER DOWN
When I type "fastboot oem lock" in cmd, I get the following response:
" 'fastboot' is not recognized as internal or external command, operable program or batch file ".
And when I run the RUU (as administrator) I get "Error [170]: USB CONNECTION ERROR".
Regards,
Pim

Do you have HTC drivers installed and java SDK platform files ?
Have you ever used fastboot commands ?
Do you have a fastboot folder on the pc with fastboot/adb files in it ? When you connect the phone to the pc and put in bootloader menu you should see something like fastboot USB
Download this
http://db.tt/ldx3qOOU
And put the folder in c:\
So you have
C:\fastboot\ files in the folder
Open a dosprompt in that folder and type
Fastboot devices while the phone is still in bootloader menu If it comes up with your serial its good

Mr Hofs said:
Do you have HTC drivers installed and java SDK platform files ?
Have you ever used fastboot commands ?
Do you have a fastboot folder on the pc with fastboot/adb files in it ? When you connect the phone to the pc and put in bootloader menu you should see something like fastboot USB
Download this
db.tt/ldx3qOOU
And put the folder in c:\
So you have
C:\fastboot\ files in the folder
Open a dosprompt in that folder and type
Fastboot devices while the phone is still in bootloader menu If it comes up with your serial its good
Click to expand...
Click to collapse
Thanks.
I installed Windows to do this (Nothing worked on Mac, and things like this are usually easier on Windows than on Mac), and I forgot to install these things again.
I'll try this in a sec and I'll report here when I'm done.
Regards,
Pim

Mr Hofs said:
The ruu doesn't work because it's an OTA ....its just an update file ! Not the whole RUU
htcruu. com/securekey.phpfile=Endeavor/RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe
this is the full RUU
Click to expand...
Click to collapse
bagofcrap24 said:
Yes. Previous poster is correct. Download that file.
Do not put it on your sdcard.
Plug your phone into PC
Reboot into hboot by holding power & volume down for about 20seconds.
Press power button to go to fastboot
Open a cmd window and run fastboot oem lock to relock your bootloader
Run your ruu as administrator on your PC by right clicking and pressing open as administrator
Follow the instructions on your PC to flash the ruu
Click to expand...
Click to collapse
Hello,
First of all, I'd like to apologize for leaving so suddenly, but I had some other, more important, things on my mind.
Thanks for the link, but when I try to do that (and follow all the instructions I get on the screen), it all goes well, until just after "erasing user data", when I get the error as seen in the attachments.
When I started my phone, I had to fill in the basic questions, but I later found out that all my files were still there, while the apps themselves had been uninstalled...
I figured some general stuff out, and adb and fastboot are now *finally* working as they should.
Regards,
Pim
EDIT: Since I'm not quite sure whether or not the attachments are working, I uploaded them to imgur:
imgur. com/a/yMxph <= just remove the space before the between the "imgur." and "com/a/yMxph"

Well, I've just downloaded the correct RUU, but I'm currently getting error 155: unknown error...
I'm kinda clueless about what to do now...
Regards,
Pim

Download from the 2.17.401 ruu and try again.....otherwise flash back the stock recovery from the main version that you currently have
http://androidfiles.org/ruu/securek...Radio_2.1204.135.20_release_274900_signed.exe
So the stock recovery should be 1.29 based

Mr Hofs said:
Download from the 2.17.401 ruu and try again.....otherwise flash back the stock recovery from the main version that you currently have
http://androidfiles.org/ruu/securek...Radio_2.1204.135.20_release_274900_signed.exe
So the stock recovery should be 1.29 based
Click to expand...
Click to collapse
I used the same RUU I used before, but this time with relocked bootloader (forgot to relock that again), this time it worked!
I'm currently updating to Jelly Bean, and then I'll root it again etc. If I'm right, S-OFF is possible for the One X these days, right?
If so, would anyone know an easy and clear tutorial?
Regards,
Pim

Noone figured out the way to S-off for HOX yet, no.

BlueSingA said:
Noone figured out the way to S-off for HOX yet, no.
Click to expand...
Click to collapse
Sigh... well, thanks anyway.
Regards,
Pim

[Q] Can't root my HTC Wildfire

For days now I have been trying to root this HTC Wildfire (NOT Wildfire S) that my dad gave to me (so I take it that this phone is very old), because I need to install Android 2.3 on it to be able to download Skype (the phone is stuck on Android 2.2). However after trying many guides, on this website AND others, I am simply unable to do it, so that is why I am writing this forum post.
This is the HBOOT screen:
(As a new user I can not post any images or links for some reason so I just typed this
*** LOCKED (OOW) ***
BUZZ PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0622
TOUCH PANEL-ATMEL224_20aa
RADIO-3.35.20.10
Dec 13 2011, 12:08:54
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
I have tried so many different things, especially posts on this website, and have so far been unsuccessful, but that may be mainly because I am new to this type of thing.
Any help is appreciated, it seems to me that there is almost no solution, half the links to files I need for this process has turned out to be so old that it is no longer even there.

NurusS said:
I have tried so many different things, especially posts on this website, and have so far been unsuccessful, but that may be mainly because I am new to this type of thing.
Any help is appreciated, it seems to me that there is almost no solution, half the links to files I need for this process has turned out to be so old that it is no longer even there.
Click to expand...
Click to collapse
Hi there, welcome to the forum
Have you tried using my guide to root hboot 1.02.0000? What have you tried already? (Links please ) also what are you getting stuck on/at?
lastly what version of windows are you on?
Sent from my Desire S using Tapatalk

heavy_metal_man said:
Hi there, welcome to the forum
Have you tried using my guide to root hboot 1.02.0000? What have you tried already? (Links please ) also what are you getting stuck on/at?
lastly what version of windows are you on?
Sent from my Desire S using Tapatalk
Click to expand...
Click to collapse
Yes, I have. I spent a lot of time trying to use your method but it simply didn't work
http://forum.xda-developers.com/showthread.php?t=2262345 I take it you mean this post?
I have problems at step 3. When I use the htcdev instructions, when I'm on the RUU it says ERROR[191]: ROM IS NOT SUPPORTED
And after that there is nothing that I can do to continue with your instructions. I am on Windows 8.

NurusS said:
Yes, I have. I spent a lot of time trying to use your method but it simply didn't work
http://forum.xda-developers.com/showthread.php?t=2262345 I take it you mean this post?
I have problems at step 3. When I use the htcdev instructions, when I'm on the RUU it says ERROR[191]: ROM IS NOT SUPPORTED
And after that there is nothing that I can do to continue with your instructions. I am on Windows 8.
Click to expand...
Click to collapse
Okay, windows 8 can have some issues with android development but we "should" ( ) be able to get around them.
to your main issue you do not need to flash the ruu, as you already have the upgraded hboot, so skip that part and move onto getting your unlock token via fastboot.( should it say that you need to download the ruu just to move the web page along then do so, but you dont need that file.) View here for a how to on getting fastboot set up with windows 8 and view here for commonly ran into issues with windows 8. Should you get stuck or need more advice just ask pal

heavy_metal_man said:
Okay, windows 8 can have some issues with android development but we "should" ( ) be able to get around them.
to your main issue you do not need to flash the ruu, as you already have the upgraded hboot, so skip that part and move onto getting your unlock token via fastboot.( should it say that you need to download the ruu just to move the web page along then do so, but you dont need that file.) View here for a how to on getting fastboot set up with windows 8 and view here for commonly ran into issues with windows 8. Should you get stuck or need more advice just ask pal
Click to expand...
Click to collapse
Are you sure? it says S-ON, LOCKED and I'm not sure what you mean by the adb folder (where we put the BUZZ-recovery file), but it seems to work where I put it and is stuck forever at < waiting for device >
What is the problem here?

NurusS said:
Are you sure? it says S-ON, LOCKED and I'm not sure what you mean by the adb folder (where we put the BUZZ-recovery file), but it seems to work where I put it and is stuck forever at < waiting for device >
What is the problem here?
Click to expand...
Click to collapse
Yeah im positive pal. the old hboot never used to say locked. if its sits at waiting for device it means that the device is not connected okay. can you run the command
Code:
adb devices
for me and see if it detects the phone.
Do you have usb debugging enabled?
Did you download the zip file from the forum page?

heavy_metal_man said:
Yeah im positive pal. the old hboot never used to say locked. if its sits at waiting for device it means that the device is not connected okay. can you run the command
Code:
adb devices
for me and see if it detects the phone.
Do you have usb debugging enabled?
Did you download the zip file from the forum page?
Click to expand...
Click to collapse
I ran the command an got this back:
C:\Users\Nurus>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH14RPY08821 device
I have USB debugging enabled on my phone.
What zip files are you referring to?

NurusS said:
I ran the command an got this back:
C:\Users\Nurus>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
SH14RPY08821 device
I have USB debugging enabled on my phone.
What zip files are you referring to?
Click to expand...
Click to collapse
Sorry for my delay pal, you seem to have download the correct zip file from the op. Try these commands
Adb reboot bootloader
(The device should reboot into fastboot, highlighted in red at the top, Followed by.)
fastboot oem get_identifier_token
Then highlight the code using right click/mark/ then select it all and right click it again. Post that into the htcdev website.
Sent from my nexus 7 using Tapatalk

heavy_metal_man said:
Sorry for my delay pal, you seem to have download the correct zip file from the op. Try these commands
Adb reboot bootloader
(The device should reboot into fastboot, highlighted in red at the top, Followed by.)
fastboot oem get_identifier_token
Then highlight the code using right click/mark/ then select it all and right click it again. Post that into the htcdev website.
Sent from my nexus 7 using Tapatalk
Click to expand...
Click to collapse
I did what you said, I got <waiting for device> again.

NurusS said:
I did what you said, I got again.
Click to expand...
Click to collapse
When the command prompt states waiting for the device,and you have booted into hboot using the command fastboot reboot boot loader, does the phone say fastboot in red at the top, with options like fastboot reboot and other options in red? Or is it the standard black/blue writing? If its not all red then with the fastboot option highlighted press power once. I will upload pictures of what o mean as soon as I get to my laptop.

heavy_metal_man said:
When the command prompt states waiting for the device,and you have booted into hboot using the command fastboot reboot boot loader, does the phone say fastboot in red at the top, with options like fastboot reboot and other options in red? Or is it the standard black/blue writing? If its not all red then with the fastboot option highlighted press power once. I will upload pictures of what o mean as soon as I get to my laptop.
Click to expand...
Click to collapse
Fastboot is highlighted in red.

NurusS said:
Fastboot is highlighted in red.
Click to expand...
Click to collapse
Sorry for my very delayed response pal, life got in the way.
ok so your hboot looks like this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
yeah like this except yours will say locked and not unlocked at this stage.
So from here open your command prompt from within the adb folder
Then enter this command, copy and pastif prefered.
Code:
fastboot oem get_identifier_token
this should return a large code in the command prompt.
You will then need to Rght click, mark, and then highlight all the code like the htcdev website states.
post that info into the website and they will email you your unlock token.bin
post back on how you get on.

heavy_metal_man said:
Sorry for my very delayed response pal, life got in the way.
ok so your hboot looks like this?
yeah like this except yours will say locked and not unlocked at this stage.
So from here open your command prompt from within the adb folder
Then enter this command, copy and pastif prefered.
Code:
fastboot oem get_identifier_token
this should return a large code in the command prompt.
You will then need to Rght click, mark, and then highlight all the code like the htcdev website states.
post that info into the website and they will email you your unlock token.bin
post back on how you get on.
Click to expand...
Click to collapse
Once again, I just get <waiting for device>

NurusS said:
Once again, I just get <waiting for device>
Click to expand...
Click to collapse
Okay, then your issue is with your fastboot driver. Do you have another computer you can use?

Just install android SDK and jdk and then try to install your drivers as heavy metal man said. I hope this could work..or try to use this
http://forum.xda-developers.com/showthread.php?t=2317790
Sent from my Moto G using XDA Free mobile app

M8 stuck in bootloader?

Hi,
my son's m8 just stopped working, came up with a screen saying something like "illegal use of software....."
It only boots to bootloader. Won't go into recovery, Factory recovery, I've tried a few things but things but fastboot commands won't recognize the phone. The phone does show "fast boot USB" but my PC doesn't seem to recognize the connection.
Phone is original software, locked, S-on, no mods. It does say on the screen "software modified"
Any way around this? I'll upload some screen pics.
Thanks for any advice
Marky_

Marky_ said:
Hi,
my son's m8 just stopped working, came up with a screen saying something like "illegal use of software....."
It only boots to bootloader. Won't go into recovery, Factory recovery, I've tried a few things but things but fastboot commands won't recognize the phone. The phone does show "fast boot USB" but my PC doesn't seem to recognize the connection.
Phone is original software, locked, S-on, no mods. It does say on the screen "software modified"
Any way around this? I'll upload some screen pics.
Thanks for any advice
Marky_
Click to expand...
Click to collapse
Run your device specific RUU via sd card method .
Hit THANKS if somebody help you

hi,
I have "Run your device specific RUU via sd card method . "
I have tried multiple RUU files for my device from a couple of different sources. none worked
see attached pics. fastboot, adb and htc_fastboot won't communicate with my phone either.
any other sources that anyone could recommend that may get this M8 booting again?
regards
Marky_

It's not easy to fix this kind of problem when the correct RUU version is not available and the bootloader is LOCKED
I suggest :
a) Not sure whether this will work as 6.24.841.1 firmware is partial update from 6.12.841.4 but worth a try.
Get the fw_6.24.841.1.zip from my thread : http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Since you said your PC is not communicating with your device (which I believe due to lack of HTC USB drivers - you can check in PC Device Manager to make sure), you can install it with microsd method
Rename the fw_6.24.841.1.zip to 0P6BIMG.zip (make sure your PC doesn't have windows extension hidden, it not it may read as 0P6BIMG.zip.zip and won't install)
Put in microsd and go to hboot to update, reboot and see whether it can boot now.
b) if the above fails, you need to try to unlock bootloader thru http://www.htcdev.com/
if it can be unlocked, install TWRP then restore the 6.24.841.1 backup that you can get from my thread linked in my signature.

ckpv5 said:
It's not easy to fix this kind of problem when the correct RUU version is not available and the bootloader is LOCKED
I suggest :
a) Not sure whether this will work as 6.24.841.1 firmware is partial update from 6.12.841.4 but worth a try.
Get the fw_6.24.841.1.zip from my thread : http://forum.xda-developers.com/showpost.php?p=60218734&postcount=5
Since you said your PC is not communicating with your device (which I believe due to lack of HTC USB drivers - you can check in PC Device Manager to make sure), you can install it with microsd method
Rename the fw_6.24.841.1.zip to 0P6BIMG.zip (make sure your PC doesn't have windows extension hidden, it not it may read as 0P6BIMG.zip.zip and won't install)
Put in microsd and go to hboot to update, reboot and see whether it can boot now.
b) if the above fails, you need to try to unlock bootloader thru http://www.htcdev.com/
if it can be unlocked, install TWRP then restore the 6.24.841.1 backup that you can get from my thread linked in my signature.
Click to expand...
Click to collapse
Hi I am back.... doh.
After numerous attempts the above did finally work BUT the phone could not connect to internet or google playstore.
So, I tried the above FW method again, now it just keeps rebooting => HTC screen, optimizing apps then reboots
any other suggestions / links for me to try.
question..... what are the ****diag.zip & ****diag.nbh that HBOOT also looks for when booting to SDcard? Would one of these files be worth a try?
Thanks
Marky_

Marky_ said:
Hi I am back.... doh.
After numerous attempts the above did finally work BUT the phone could not connect to internet or google playstore.
So, I tried the above FW method again, now it just keeps rebooting => HTC screen, optimizing apps then reboots
any other suggestions / links for me to try.
question..... what are the ****diag.zip & ****diag.nbh that HBOOT also looks for when booting to SDcard? Would one of these files be worth a try?
Thanks
Marky_
Click to expand...
Click to collapse
I believe you do have hardware issue. Maybe corrupted data/emmc.
When it was working but no internet .. why didn't you try to unlock bootloader ? It's already out of warranty .. with bootloader unlock, you can try other thing like formatting data partition and restore a non-rooted stock nandroid.
Until now .. I never see a RUU been released for device version.

ckpv5 said:
I believe you do have hardware issue. Maybe corrupted data/emmc.
When it was working but no internet .. why didn't you try to unlock bootloader ? It's already out of warranty .. with bootloader unlock, you can try other thing like formatting data partition and restore a non-rooted stock nandroid.
Until now .. I never see a RUU been released for device version.
Click to expand...
Click to collapse
Hi, I did try to unlock bootloader, when I got the m8 working. yes it is out of warranty
I re-downloaded all files to my PC as HTC Dev asked but the fastbboot service could not recognize the phone. HTC sync was connecting and the phone was showing in my PC but the USB fastboot still would not let me :crying:
so..... without unlocking the bootloader, how do I "try formatting data partition and restore a non-rooted stock nandroid"
thank you

Marky_ said:
Hi, I did try to unlock bootloader, when I got the m8 working.......
I re-downloaded all files to my PC as HTC Dev asked but the fastbboot service could not recognize the phone. HTC sync was connecting and the phone was showing in my PC but the USB fastboot still would not let me :crying: .......
Click to expand...
Click to collapse
fastboot (( service )) only works in fastboot mode ( bootloader ) not while the device booting into android
Marky_ said:
........ without unlocking the bootloader, how do I "try formatting data partition and restore a non-rooted stock nandroid" .....
Click to expand...
Click to collapse
you can't
the only way is the RUU

Help! HTC One M8 (Rogers Canada) Bricked?

/Users/sekhon/Desktop/Brick Phone.jpg
Hi,
My HTC M8 (which i have not used for a year) seems to have been cricked to what ever extent !
I put it on charge and the following shows up
________________________________________
*** Software status: Modified ***
*** Locked ***
M8_UL PVT Ship S-ON
(few other lines)
FastBOOT AC
<vol up. to previous item>
<vol down> to next item>
<power> to select item
HBOOT
RAMDUMP
REBOOT
REBOOT FASTBOOT
POWER DOWN
no matter what i do it just ends up here and doesn't really startup,
I had aSD Card in the phone and removed it and tried to restart but no luck!
Any help would be highly appreciated !

saint4mbuddapest said:
no matter what i do it just ends up here and doesn't really startup,
Click to expand...
Click to collapse
So what did you try to do? The above doesn't tell us anything you tried or didn't try (aside from removing the SD card).
Don't want to waste the time and effort, to advise you to do things you may have already tried.

Hello,
Thanks for the reply!
I tried to connect it to my mac via usb to flash a rom or twrp etc but my computer doesn't show the phone.
I tried selecting the recovery mode from the menus and nothing happens.
It just restarts and goes back to the same mode.
So honestly i havnt tried much as i do not know where to begin.. Apart from going into all of the menus on the screen and that's it.
I think i the phone is missing the recovery and the rom? Not sure.... Help!

saint4mbuddapest said:
I tried to connect it to my mac via usb to flash a rom or twrp etc but my computer doesn't show the phone.
Click to expand...
Click to collapse
The mac will only be able to connect via fastboot, in the current condition. Do you have fastboot/adb setup on your mac? I'm not a mac user, so I won't be able to advise much on that.
saint4mbuddapest said:
I think i the phone is missing the recovery and the rom? Not sure.... Help!
Click to expand...
Click to collapse
Since the phone will only boot to bootloader, you are correct in that it appears the ROM is damaged or corrupt. Since I don't think the Rogers version has RUU to recover, you are right in the approach of flashing TWRP and ROM to the phone.
However, you will also need to unlock the bootloader, in order to flash TWRP. And you will need working fastboot connection to mac/PC in order to unlock bootloader and flash TWRP. So you really need to troubleshoot the connection issue, first.
You might also read through the following thread for more recovery options or info: https://forum.xda-developers.com/showthread.php?t=2694297

redpoint73 said:
Since I don't think the Rogers version has RUU to recover
Click to expand...
Click to collapse
On post #1 OP wrote (few other lines) which is important to be highlighted. Without OS info no way to help.
Or as usual need fastboot getvar all result. If it is Lollipop RUU 4.20.631.3 is available for free.
Also I remember Marshmallow RUU is available too on AFH but can't confirm it now as I maybe wrong ..need to search for it
Edit : here is Marshmallow RUU - http://gsm-firmware.com/index.php?a=browse&b=file-info&id=14070
Leave it to you to guide OP.
Maybe need to flash 6.13.631.7 firmware first before RUU

Thanks!
I just tried the add fast boot connection went through all the steps ok, HOWEVER when i type in ./adb devices it does not show the phone. So far all posts and videos i have found explain about trouble shooting when the phone OS is still running but none for my situation.
There is a red highlights text which says "FASTBOOT"
and it turns to "FASTBOOT USB" when i plug in with my MAC
Also i have tried 2 different USB cables same result, tried clicking on the "REBOOT FASTBOOT" as well same result.
Anything else i can do to have a working connection ?
redpoint73 said:
The mac will only be able to connect via fastboot, in the current condition. Do you have fastboot/adb setup on your mac? I'm not a mac user, so I won't be able to advise much on that.
Since the phone will only boot to bootloader, you are correct in that it appears the ROM is damaged or corrupt. Since I don't think the Rogers version has RUU to recover, you are right in the approach of flashing TWRP and ROM to the phone.
However, you will also need to unlock the bootloader, in order to flash TWRP. And you will need working fastboot connection to mac/PC in order to unlock bootloader and flash TWRP. So you really need to troubleshoot the connection issue, first.
You might also read through the following thread for more recovery options or info: https://forum.xda-developers.com/showthread.php?t=2694297
Click to expand...
Click to collapse

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
http://i65.tinypic.com/254x8g0.jpg
<img src="http://i65.tinypic.com/254x8g0.jpg" border="0" alt="Image and video hosting by TinyPic">

saint4mbuddapest said:
Thanks!
I just tried the add fast boot connection went through all the steps ok, HOWEVER when i type in ./adb devices it does not show the phone. So far all posts and videos i have found explain about trouble shooting when the phone OS is still running but none for my situation.
There is a red highlights text which says "FASTBOOT"
and it turns to "FASTBOOT USB" when i plug in with my MAC
Also i have tried 2 different USB cables same result, tried clicking on the "REBOOT FASTBOOT" as well same result.
Anything else i can do to have a working connection ?
Click to expand...
Click to collapse
Have you installed the HTC drivers to your computer?
If not, install HTC Sync Manager (you can get the MAC version here). During the installation of Sync Manager the drivers will be installed. After they are, Uninstall Sync Manager (it doesn't play nice with ADB/fastboot) and the drivers will remain

xunholyx said:
Have you installed the HTC drivers to your computer?
If not, install HTC Sync Manager (you can get the MAC version here). During the installation of Sync Manager the drivers will be installed. After they are, Uninstall Sync Manager (it doesn't play nice with ADB/fastboot) and the drivers will remain
Click to expand...
Click to collapse
Just tried that as well, no improvement

saint4mbuddapest said:
I just tried the add fast boot connection went through all the steps ok, HOWEVER when i type in ./adb devices it does not show the phone.
Anything else i can do to have a working connection ?
Click to expand...
Click to collapse
When on fastboot, correct command is fastboot devices or ./fastboot devices
Based on your bootloader screenshot, you can try the above linked RUU to fix your phone

saint4mbuddapest said:
I just tried the add fast boot connection went through all the steps ok, HOWEVER when i type in ./adb devices it does not show the phone. So far all posts and videos i have found explain about trouble shooting when the phone OS is still running but none for my situation.
There is a red highlights text which says "FASTBOOT"
and it turns to "FASTBOOT USB" when i plug in with my MAC
Click to expand...
Click to collapse
This is working normally, and as intended.
adb and fastboot are related, but different conditions, usage and requirements.
adb: Only works in OS, or alternately TWRP. Needs debugging enabled in phone settings. Will not work in fastboot mode.
fastboot: Only works in fastboot mode. Does not require debugging enabled in phone settings.
Stuck in fastboot mode, you should get a response (phone's ID) to: fastboot devices
Otherwise, there may be a driver or USB connectivity issue.
However, since ckpv5 linked an RUU for you to use, the mac won't help you. RUU is probably the easiest way to get the phone back up and running. But you'll need access to a PC for the RUU to work. RUU won't work properly with mac, even emulating a PC.

redpoint73 said:
However, since ckpv5 linked an RUU for you to use, the mac won't help you. RUU is probably the easiest way to get the phone back up and running. But you'll need access to a PC for the RUU to work. RUU won't work properly with mac, even emulating a PC.
Click to expand...
Click to collapse
It's zip format, can use microsd method

ckpv5 said:
It's zip format, can use microsd method
Click to expand...
Click to collapse
Nice. :good: Obviously, I missed that detail. Should have figures, since most M8 versions without "official" released RUUs seem to get them leaked as zip format.