[Q] Can't root my HTC Wildfire - Wildfire Q&A, Help & Troubleshooting

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

Related

[GUIDE] Unlocking (& Re-locking) the Motorola Xoom for flashing

The following will VOID your warranty but will easily unlock the Xoom for fast software flashes using a custom recovery and will allow flashing root files or manipulated system files on to your current software installation.
This will ERASE your Xoom.
1) Get the Motorola USB drivers MOTODEV > Documentation & Tools > USB Drivers (you need to sign up on their but maybe you can google this and find it as well)
2) Get the Android SDK Android SDK | Android Developers (you only really need the fastboot executable file for your host OS)
2.5) - I will soon put together a windows pack for usb drivers & fastboot so you don't have to download all this stuff just to do one task.
3) Power off your Xoom
4) Press and hold the volume down button while pressing the power button
Even after the Xoom turns back on keep it pressed down and you'll see some starting fastboot protocol text on the top left of the screen.
5) Open a command window in your sdk\tools folder (not platform tools and depending on when you get the SDK you may need to copy over some DLL files)
6) type:
fastboot oem unlock
Click to expand...
Click to collapse
7) read the warning on your Xoom's screen, hit volume up if you wish.
You're now free to put whatever data you want on your tablet. Cheers.
-- To RE-LOCK your Xoom, boot in to fastboot, and on your computer (from the tools folder):
fastboot oem lock
Click to expand...
Click to collapse
Read this warning:
{
"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"
}
You actually have to read the warning and understand it - If you have modified your Xoom's software outside of the user space you won't be able to successfully re-lock your device. You'll have to restore it back to 100% factory, which you can do here: http://developer.motorola.com/produ...utm_source=supportforums&utm_term=unlockboard (The Verizon Wireless stock software).
This wouldn't negate the free LTE upgrade would it?
I'm not sure. I'd say you should re-lock the boot loader and restore any custom stuff to factory before you send it back in though.
I'm curious, what are the hardware ids in the usb driver when the xoom is in fastboot? Is the usb driver that is active while it's in fastboot called something like single adb device?
Thanks!
Sent from my MB860 using XDA App
How do you relock it?
Sent from my HTC Vision using Tapatalk
Wow, that has to be the easiest unlock I have ever seen. Does this mean we will not have to install something like Amon's RA Recovery to flash ROMs whenever people get a chance to make them?
Also, if we issue a fastbook oem lock (or whatever the proper command is), can we then send it in for repairs? in other words, is there some history on the device that says I unlocked it?
youareme7 said:
I'm curious, what are the hardware ids in the usb driver when the xoom is in fastboot? Is the usb driver that is active while it's in fastboot called something like single adb device?
Thanks!
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Windows first found it as fastboot, then I got the moto driver from their dev site and I didn't look what it was called after that. I think a Moto composite device or something, I'm pretty sure it installed 3 drivers. I will double check when I'm back home.
djunio said:
How do you relock it?
Sent from my HTC Vision using Tapatalk
Click to expand...
Click to collapse
I'm not sure but I would say "fastboot oem lock" should probably work. - What I am really curious about is if fastboot oem unlcok writes something to the tablet somewhere that lets Moto/VZW know it was unlocked.
padanfain said:
Wow, that has to be the easiest unlock I have ever seen. Does this mean we will not have to install something like Amon's RA Recovery to flash ROMs whenever people get a chance to make them?
Also, if we issue a fastbook oem lock (or whatever the proper command is), can we then send it in for repairs? in other words, is there some history on the device that says I unlocked it?
Click to expand...
Click to collapse
We'll still need a custom recovery to make life easier, but after you unlock it you can push any files/images to wherever you want.
The unlock screen makes you agree to the fact you're voiding your warranty. I'm not sure if re-locking it will be enough and I'd venture to speculate that there should be a difference between a hardware fail and software fail for warranty work. I guess we'll see.
thefredelement said:
This will ERASE your Xoom.
Click to expand...
Click to collapse
What does this mean? Does unlocking the device wipe everything, or just wipe data/cache? Is system effected just by executing this, or are you referring to the flash process?
mikejs78 said:
What does this mean? Does unlocking the device wipe everything, or just wipe data/cache? Is system effected just by executing this, or are you referring to the flash process?
Click to expand...
Click to collapse
It's a factory reset.
i know this was the same unlock for Nexus One, but will this give us root? has anyone attempted to install SuperUser.apk and su?
koush has just tried this and did not unlock bootloader. was this done on a consumer device or developer's device?
socomdark said:
koush has just tried this and did not unlock bootloader. was this done on a consumer device or developer's device?
Click to expand...
Click to collapse
A consumer device.
Is he using the right moto dev drivers and fastboot from the 3.0 sdk?
socomdark said:
koush has just tried this and did not unlock bootloader. was this done on a consumer device or developer's device?
Click to expand...
Click to collapse
I just saw his tweet, he was trying to boot a kernel from fastboot it looks like.
thefredelement said:
I just saw his tweet, he was trying to boot a kernel from fastboot it looks like.
Click to expand...
Click to collapse
yea but it looks like he has got clockwork mod on there.
If we void the warranty what happens to the return policy? store.motorola.com 's return policy to be specific
confused
Am i supposed to hold down the volume key the whole time while I'm clicking the fastboot command. I'm a little confused if anyone help understand
You just hold down the volume down key and power button until the white fastboot protocol text appears.
cant get it
thefredelement said:
You just hold down the volume down key and power button until the white fastboot protocol text appears.
Click to expand...
Click to collapse
ok done that but when it will not open in command prompt http://media.xda-developers.com/images/smilies/mad.gif. i think i will jus give up cause something not right.. The command prompt jus pops up and immediately goes away...but thanks for the help i jus wait for the thunderbolt and root it....lol big ups to all whom do and to KOUSH!!!! that brotha is awesome
No big deal here, you have to open the command prompt properly.
If you're on windows7, then browse to the folder in windows explorer, right click on the folder and select open command window here
In windowsXP go to start, run, type in cmd and then cd to the directory where the file is located.
I just purchased a Xoom, has anyone tried to issue the fastboot OEM lock command to see if it will indeed relock the device?

[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.

[Stuck] in CWM Recovery while rooting

Hi everyone, yes i have a DHD, and i tried to root it with AAHK tool. I know that many have success, but i failed.
Now i got stuck in CWM Recovery and can't get out. Although i tried all the options in the list, but it always returns the CWM screen.
I also tried to install a Rom cook, it said that Success, but then i return again in the CWM screen.
Here it's some pic
{
"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"
}
Here it's Hboot menu
This is when i try to run AAHK tool once more.
P/S: i've read the instruction of AAHK tool before action, my phone was pure, S-On, and run Android ver 2.3.5.
P/S 2: i think in the process, my usb cable wasn't properly connected (not my fault, DHD is a old device), cos i heard the sound of something plug in and out my pc many many times
You got obtained S-OFF so you're not stuck.
Muikkuman said:
You got obtained S-OFF so you're not stuck.
Click to expand...
Click to collapse
What does that mean?
Muikkuman said:
You got obtained S-OFF so you're not stuck.
Click to expand...
Click to collapse
What do you mean? I'm stucking there.
I can't get to home screen although i tried many way. Reboot it, flash it, wipe its data, ... It always return in this CWM screen, and i call it Stuck.
Please help
july3rd said:
What do you mean? I'm stucking there.
I can't get to home screen although i tried many way. Reboot it, flash it, wipe its data, ... It always return in this CWM screen, and i call it Stuck.
Please help
Click to expand...
Click to collapse
Is your volume rocker flaw? That seems to be a hardware issue and not software. Maybe it got stuck and that is why it boots to recovery..
glevitan said:
Is your volume rocker flaw? That seems to be a hardware issue and not software. Maybe it got stuck and that is why it boots to recovery..
Click to expand...
Click to collapse
Unfortunately my volume rocker works very well
july3rd said:
Unfortunately my volume rocker works very well
Click to expand...
Click to collapse
That is not unfortunate...have you tried flashing a ruu from fastboot to see what.happens?
Sent from my GT-N7000 using xda app-developers app
glevitan said:
That is not unfortunate...have you tried flashing a ruu from fastboot to see what.happens?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I don't rly know much of rooting a phone, but when i use AAHK tool, it asked me if i want to load some "RUU" file and install it, i said Yes.
If that is not what u're talking, please give some construction.
july3rd said:
I don't rly know much of rooting a phone, but when i use AAHK tool, it asked me if i want to load some "RUU" file and install it, i said Yes.
If that is not what u're talking, please give some construction.
Click to expand...
Click to collapse
Are you able to boot in hboot? You don't need recovery to flash a RUU..paste the information displayed in your hboot here...
Ok, first download the zip I've attached to this post. Extract the contents, run 'Start here.bat'. Now, on your phone, go back to the hboot screen, connect your phone to your computer, and press 'power'. Verify that the phone shows 'FASTBOOT USB' in red. Now go to the cmd window that opened with 'Start here.bat', and type (or copy-paste) from here -
Code:
fastboot flash recovery openrecovery-twrp-2.4.1.0-ace.img
When it finishes and displays a 'success' message, exit cmd, disconnect your phone, use 'volume down' to highlight 'recovery' and press power to select it. Your phone will boot into this new recovery which is called TWRP. TWRP and 4ext are the best recoveries for this device. CWM is outdated, especially the version you're using. Now using this recovery, wipe your device properly by running wiping 'system' and 'factory reset/data' in the wipe menu, and then flash whatever ROM you want. It should work fine.
Note: If it fails, then you've done something and you don't have an S-OFF bootloader anymore. As long as your bootloader has the same top line as in the picture you posted, you're good. If you have run an RUU either on your own or using AAHK, and you have an S-ON bootloader now, connect your phone back in hboot mode, enable 'FASTBOOT USB' and run AAHK again. You'll end up with an S-OFF bootloader, and you can follow the above step.
Also, the sound of your phone disconnecting and connecting repeatedly to your computer was not a problem with the USB cable. It happens everytime AAHK reboots the phone, because the phone disconnects while turning off and connects back when turning on. AAHK failed the second time you ran it because it you already got a fully unlocked S-OFF bootloader in the first try. It only works if the bootloader is locked.
sashank said:
Ok, first download the zip I've attached to this post. Extract the contents, run 'Start here.bat'. Now, on your phone, go back to the hboot screen, connect your phone to your computer, and press 'power'. Verify that the phone shows 'FASTBOOT USB' in red. Now go to the cmd window that opened with 'Start here.bat', and type (or copy-paste) from here -
Code:
fastboot flash recovery openrecovery-twrp-2.4.1.0-ace.img
When it finishes and displays a 'success' message
Click to expand...
Click to collapse
Thank you for your attention, Here it's the result
Btw, each time i load into Hboot, the screen flash into this
and then he goes to the normal Hboot.
Idk if it helps anything, i just give all i got to you.
july3rd said:
Thank you for your attention, Here it's the result
Btw, each time i load into Hboot, the screen flash into this
and then he goes to the normal Hboot.
Idk if it helps anything, i just give all i got to you.
Click to expand...
Click to collapse
you can not use flash commands in fasboot as you don't have ENG S-OFF (do not flash the tradicional but the modified one in the Hack Kit)
Or flash the zip file in fastboot this way:
Boot in fastboot usb (check that in the phone is display that)
Put this zip file somewhere you can find it: https://docs.google.com/file/d/0B2d8xxQzn5owMkpCQlBibkU2amM/edit?usp=sharing.
Open a cmd as admin in the PC
Go to where the recovery zip folder is located (in cmd)
And then type:
Code:
fastboot oem rebootRUU
fastboot flash zip cwm-5.0.2.7-ace.zip (when you get the OKAY in the cmd session you are done)
fastboot reboot-bootloader
When finished, you should have CWM recovery installed
glevitan said:
you can not use flash commands in fasboot as you don't have ENG S-OFF (do not flash the tradicional but the modified one in the Hack Kit)
Click to expand...
Click to collapse
Thank you, all steps has worked, but it seems that nothing has changed. The phone reboot and still stuck at the famous CWM screen.
Btw, i now can't use AAHK tool anymore, it always say that Phone not plugged in, or Driver not installed, or USB debugging not enabled.
glevitan said:
you can not use flash commands in fasboot as you don't have ENG S-OFF (do not flash the tradicional but the modified one in the Hack Kit)
Click to expand...
Click to collapse
Ah, my bad. I completely forgot about that. I've always had ENG S-OFF I'll remember your method. :good:
sashank said:
Ah, my bad. I completely forgot about that. I've always had ENG S-OFF I'll remember your method. :good:
Click to expand...
Click to collapse
Then maybe you have another solution ?
I'm still waiting for you guys :hopefully:
Yeah. If you still have S-OFF, connect your phone in fast boot and run AAHK. Choose the option to flash ENG hboot and flash the 0.85.2425 version. Once it's done, you'll see 'ACE PVT ENG S-OFF' at the top. Now you can do again what I said in the previous post.
Sent from my Desire HD using xda premium
sashank said:
Yeah. If you still have S-OFF, connect your phone in fast boot and run AAHK. Choose the option to flash ENG hboot and flash the 0.85.2425 version. Once it's done, you'll see 'ACE PVT ENG S-OFF' at the top. Now you can do again what I said in the previous post.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
I can't, as i said, the AAHK tool don't recognize my device anymore. I did install the driver. I'll take a screen shot for you later
july3rd said:
I can't, as i said, the AAHK tool don't recognize my device anymore. I did install the driver. I'll take a screen shot for you later
Click to expand...
Click to collapse
Because you are trying to open he Hack Kit normally, but your phone does not boot so adb can't be used. Boot in fastboot usb and then open a cmd as admin and navigate to where the hack kit is located, then type:
Code:
hack-ace.cmd fastboot
That should bring the menu to flash ENG S-OFF...
glevitan said:
Because you are trying to open he Hack Kit normally, but your phone does not boot so adb can't be used. Boot in fastboot usb and then open a cmd as admin and navigate to where the hack kit is located, then type:
Code:
hack-ace.cmd fastboot
That should bring the menu to flash ENG S-OFF...
Click to expand...
Click to collapse
Still can't
I think my phone is missing something...
july3rd said:
Still can't
I think my phone is missing something...
Click to expand...
Click to collapse
ok, do you mind if I have a look to it over teamviewer?

HTC Desire 530 Root/S-OFF

Yes, this is very similar jcase's post. His helped me out a lot, but I went more in depth. Here is his post.
http://forum.xda-developers.com/desire-530/help/root-s-off-desire-530-guide-to-root-t3410015
0) Download these files
SuperSu 2.74 - https://download.chainfire.eu/964/Su...0519174328.zip
Universal ADB Driver
Android SDK - https://developer.android.com/studio/index.html
TWRP - https://www.androidfilehost.com/?fid=24588212152304477 (Experimental build)
SunShine - http://theroot.ninja/apks/SunShine-latest.apk (Optional)
1) Visit htcdev.com and unlock your bootloader
-sign up as a dev, activate your email, and follow the steps
2) Download twrp from the app store. You won’t be able to run it yet but you still need it
3) Put the supersu zip file from your computer into your download folder of your phone
4) Get fastboot & adb running on your computer.
- open cmd prompt
-navigate to the fastboot/adb folder in your cmd prompt
-with your phone plugged into your computer type “adb devices”
-if it returns your device good
-now in cmd type “adb reboot downloader” (you can also do this by powering off your phone then turning your phone on by holding the down volume button and the power button at the same time.
-once you are in the downloader type “fastboot devices” in cmd
-if this returns your device good
-DO NOT GO ANY FURTHER TILL THIS IS WORKING!!!
4)Once your phone is in the rebooted downloader screen type “fastboot flash recovery <twrpDownloadFromAbove>”
-make sure you are on the downloader page and not the bootloader page
-this should end in .img
-this is a second boot screen for your phone. The first time I did this recovery wasn’t working because I was trying to fastboot on the bootloader page.
5) Now boot into recovery mode by navigating to it on your phone or using the cmd “adb reboot recovery”
-Once you are here you will see the twrp screen
6a) The way I did it is going into the twrp recovery boot and going to install and choosing the supersu.zip file I moved to my phone in step 3. After it is done reboot your phone and now you are rooted.
6b) The other way is to go to advanced in twrp and enable sideload
-now in cmd type “adb sideload <SuperSuDownloadFromAbove>”
7) If you need to turn S-OFF install sunshine on your phone and it will do it.
-You need to have your phone rooted first to turn your S-OFF with sunshine
Hi, I've been trying to root my phone since a couple of days but I've not been able to do it. I followed your guide as well as jcase one, but the results are the same, I can't boot to recovery mode after flashing the twrp image saying "failed to boot to recovery mood. Press volume up or down to back to menu" when I choose the option from bootloader screen (which is the only place where I can find a "boot recovery" option, and using the cmd command doesn't work.
vistor_sanh said:
Hi, I've been trying to root my phone since a couple of days but I've not been able to do it. I followed your guide as well as jcase one, but the results are the same, I can't boot to recovery mode after flashing the twrp image saying "failed to boot to recovery mood. Press volume up or down to back to menu" when I choose the option from bootloader screen (which is the only place where I can find a "boot recovery" option, and using the cmd command doesn't work.
Click to expand...
Click to collapse
I get this same thing, do yo fix it?
Faviopiano2 said:
I get this same thing, do yo fix it?
Click to expand...
Click to collapse
When you are in the bootloader screen does it say unlocked at the top? Also make sure you've flashed the twrp img to recovery. If it flashes correctly you should see that it starts downloading ok your phone
whittlestick said:
When you are in the bootloader screen does it say unlocked at the top? Also make sure you've flashed the twrp img to recovery. If it flashes correctly you should see that it starts downloading ok your phone
Click to expand...
Click to collapse
Yes its unlocked already, and when finish flashing its ok too
Successful Root!
Thanks I followed all of the instructions and I was able to successfully get Root on my metro pcs HTC Desire 530.
IF YOU ARE HAVING ISSUE with the TWRP.img
- Make sure you have "OEM Unlocking" enabled under developer options in settings since the phone wiped when you unlocked the bootloader it probably unclicked that option and you just have to enable it again.
- Check md5sum of the TWRP image file maybe you have a corrupt file and therefore a bad flash (I use OP link it worked fine).
- When pushing the TWRP image make sure you have a good USB connection.
{
"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 have a problem flashing the recovery. What is the OP link?
---------- Post added at 12:38 AM ---------- Previous post was at 12:32 AM ----------
matora said:
I have a problem flashing the recovery. What is the OP link?
Click to expand...
Click to collapse
TWRP Official page?
---------- Post added at 01:15 AM ---------- Previous post was at 12:38 AM ----------
izou1838 said:
Thanks I followed all of the instructions and I was able to successfully get Root on my metro pcs HTC Desire 530.
IF YOU ARE HAVING ISSUE with the TWRP.img
- Make sure you have "OEM Unlocking" enabled under developer options in settings since the phone wiped when you unlocked the bootloader it probably unclicked that option and you just have to enable it again.
- Check md5sum of the TWRP image file maybe you have a corrupt file and therefore a bad flash (I use OP link it worked fine).
- When pushing the TWRP image make sure you have a good USB connection.
Click to expand...
Click to collapse
Please, give me the OP link. Thanks
@matora
OP is original post otherwise the link provided.
One thing I did do different is I downloaded and installed "Minimal ADB and Fastboot" and I also installed HTC sync manager prior to flashing the recovery
Hope it helps
izou1838 said:
@matora
OP is original post otherwise the link provided.
One thing I did do different is I downloaded and installed "Minimal ADB and Fastboot" and I also installed HTC sync manager prior to flashing the recovery
Hope it helps
Click to expand...
Click to collapse
From where you install the HTC sync manager and the minimal adb?
Just got this phone an hour ago since my LG-D855 is stuck in download mode so great to see a root tread/method here will try this later
Sent from my HTC Desire 530 using XDA-Developers mobile app
whittlestick said:
Yes, this is very similar jcase's post. His helped me out a lot, but I went more in depth. Here is his post.
http://forum.xda-developers.com/desire-530/help/root-s-off-desire-530-guide-to-root-t3410015
0) Download these files
SuperSu 2.74 - https://download.chainfire.eu/964/Su...0519174328.zip
Universal ADB Driver
Android SDK - https://developer.android.com/studio/index.html
TWRP - https://www.androidfilehost.com/?fid=24588212152304477 (Experimental build)
SunShine - http://theroot.ninja/apks/SunShine-latest.apk (Optional)
1) Visit htcdev.com and unlock your bootloader
-sign up as a dev, activate your email, and follow the steps
2) Download twrp from the app store. You won’t be able to run it yet but you still need it
3) Put the supersu zip file from your computer into your download folder of your phone
4) Get fastboot & adb running on your computer.
- open cmd prompt
-navigate to the fastboot/adb folder in your cmd prompt
-with your phone plugged into your computer type “adb devices”
-if it returns your device good
-now in cmd type “adb reboot downloader” (you can also do this by powering off your phone then turning your phone on by holding the down volume button and the power button at the same time.
-once you are in the downloader type “fastboot devices” in cmd
-if this returns your device good
-DO NOT GO ANY FURTHER TILL THIS IS WORKING!!!
4)Once your phone is in the rebooted downloader screen type “fastboot flash recovery <twrpDownloadFromAbove>”
-make sure you are on the downloader page and not the bootloader page
-this should end in .img
-this is a second boot screen for your phone. The first time I did this recovery wasn’t working because I was trying to fastboot on the bootloader page.
5) Now boot into recovery mode by navigating to it on your phone or using the cmd “adb reboot recovery”
-Once you are here you will see the twrp screen
6a) The way I did it is going into the twrp recovery boot and going to install and choosing the supersu.zip file I moved to my phone in step 3. After it is done reboot your phone and now you are rooted.
6b) The other way is to go to advanced in twrp and enable sideload
-now in cmd type “adb sideload <SuperSuDownloadFromAbove>”
7) If you need to turn S-OFF install sunshine on your phone and it will do it.
-You need to have your phone rooted first to turn your S-OFF with sunshine
Click to expand...
Click to collapse
uum it hangs here and nothing happens and I know and is working because I adb devices and this phone shows up
Sent from my HTC Desire 530 using XDA-Developers mobile app
dornz said:
View attachment 3915766 uum it hangs here and nothing happens and I know and is working because I adb devices and this phone shows up
Sent from my HTC Desire 530 using XDA-Developers mobile app
Click to expand...
Click to collapse
Does 'fastboot devices' return your phone or just 'dab devices'?
whittlestick said:
Does 'fastboot devices' return your phone or just 'dab devices'?
Click to expand...
Click to collapse
Ya I think I need to create a sub folder named fastboot in adb before I issue fastboot devices command thanks for reply
Sent from my HTC Desire 530 using XDA-Developers mobile app
dornz said:
Ya I think I need to create a sub folder named fastboot in adb before I issue fastboot devices command thanks for reply
Sent from my HTC Desire 530 using XDA-Developers mobile app
Click to expand...
Click to collapse
Wait so it does or doesn't? If it doesn't I think you might have a bad stock img you might have bad stock img on your phone. Is the stock img the same on that was on the phone when you bought it?
whittlestick said:
Wait so it does or doesn't? If it doesn't I think you might have a bad stock img you might have bad stock img on your phone. Is the stock img the same on that was on the phone when you bought it?
Click to expand...
Click to collapse
so I get this going and now I try to highlight token text but boot loader text keeps getting highlighted to so when I paste in in to token box in HTC dev I get error saying token string not long anuf or error. Basicly when I highlight it it needs to be token start to token end but when I mark on cmd it highlights boot loader text to
Sent from my HTC Desire 530 using XDA-Developers mobile app
dornz said:
View attachment 3916973 so I get this going and now I try to highlight token text but boot loader text keeps getting highlighted to so when I paste in in to token box in HTC dev I get error saying token string not long anuf or error. Basicly when I highlight it it needs to be token start to token end but when I mark on cmd it highlights boot loader text to
Sent from my HTC Desire 530 using XDA-Developers mobile app
Click to expand...
Click to collapse
You have to copy and paste it on a notepad, edit and remove the bootloader parts, recopy and place in the Htcdev box. At least that's what I came up with to get the job done.
DWil's Magic Carpet
wilbigdaddy2000 said:
You have to copy and paste it on a notepad, edit and remove the bootloader parts, recopy and place in the Htcdev box. At least that's what I came up with to get the job done.
DWil's Magic Carpet
Click to expand...
Click to collapse
Thanks will try again later
Sent from my LG-D855 using XDA-Developers mobile app
Did anyone get viper4android to work on our device? If so what did u do?
DWil's Magic Carpet
I cannot register in HTCDev (literally, it doesn't allow me to create an account), is there any other way to unlock my bootloader?
i get it thanks alot

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.

Categories

Resources