/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.
Related
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?
Hi!
I have for a long time tried to get access tto my phone from my PC to be able to flash a new rom. I have installed newest drivers, but in device-manager it says i don't. I have tried to do this on win7 and win8 but doesnt work:/
Anyone has an idea?
Thanks in advance
Hboot - 1.28.0000
{
"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"
}
ScopeZz DK said:
Hi!
I have for a long time tried to get access tto my phone from my PC to be able to flash a new rom. I have installed newest drivers, but in device-manager it says i don't. I have tried to do this on win7 and win8 but doesnt work:/
Anyone has an idea?
Thanks in advance
Click to expand...
Click to collapse
you don't need a pc to flash a rom, you just need it to transfer the rom itself on the sdcard... go into recovery, mount usb and that's it...it should work
matt95 said:
you don't need a pc to flash a rom, you just need it to transfer the rom itself on the sdcard... go into recovery, mount usb and that's it...it should work
Click to expand...
Click to collapse
Well now the problem by not being able to access sd is fixed, but i thought you need to do the commands Fastboot flash boot.img and Fastboot erase cache to install a new rom?
ScopeZz DK said:
Well now the problem by not being able to access sd is fixed, but i thought you need to do the commands Fastboot flash boot.img and Fastboot erase cache to install a new rom?
Click to expand...
Click to collapse
Yes, you have to flash new rom after a full wipe in recovery, boot into fastboot usb and use this command for flash the boot.img
Guich said:
Yes, you have to flash new rom after a full wipe in recovery, boot into fastboot usb and use this command for flash the boot.img
Click to expand...
Click to collapse
I know and that is impossible for me since I get the Device not found everytime I try to do commands.Which is weird when I seem to have done everything right
Did you install HTC syncmanager ? If so uninstall it but leave the drivers on the pc !
Then put the phone in the bootloader and check if you see there
Fastboot usb (in red text)
Mr Hofs said:
Did you install HTC syncmanager ? If so uninstall it but leave the drivers on the pc !
Then put the phone in the bootloader and check if you see there
Fastboot usb (in red text)
Click to expand...
Click to collapse
It does say fastboot usb, but commands doesnt work. HTC sync not installed and have tried to install drivers manually, through sync and through exe file. Still says device not found and device manager says drivers are outdated
ScopeZz DK said:
It does say fastboot usb, but commands doesnt work. HTC sync not installed and have tried to install drivers manually, through sync and through exe file. Still says device not found and device manager says drivers are outdated
Click to expand...
Click to collapse
Go into the device manager, update driver but pick the supported device from the list (don't pin me on the exact way as im not on the pc to check now) select the android phone from the list and install it (or at least update it)....
Mr Hofs said:
Go into the device manager, update driver but pick the supported device from the list (don't pin me on the exact way as im not on the pc to check now) select the android phone from the list and install it (or at least update it)....
Click to expand...
Click to collapse
It worked! Still not able to see SD card when I plug it into the PC, but I can just do it through recovery And at least rebbot phone command worked! Thanks a lot!
Good, you might want to consider updating your hboot. That might solve some issues. The 1.28 contains some bugs.
It may have also something to do with jellybean because they removed usb mass storage in there. Only mtp is available.
The latest custom JB roms (at least some) are supporting usb mass storage again
Mr Hofs said:
Good, you might want to consider updating your hboot. That might solve some issues. The 1.28 contains some bugs.
It may have also something to do with jellybean because they removed usb mass storage in there. Only mtp is available.
The latest custom JB roms (at least some) are supporting usb mass storage again
Click to expand...
Click to collapse
Well thanks man! Am looking into updating my hboot now, got any threads with tuts? Because its been a very long time since I've flashed anything, and the threads i can find isnt saying the same: http://forum.xda-developers.com/showthread.php?t=1660807 and http://forum.xda-developers.com/showthread.php?t=1924003
Do
Fastboot getvar version-main
and
Fastboot oem readcid
Report those back and i can help
Mr Hofs said:
Do
Fastboot getvar version-main
and
Fastboot oem readcid
Report those back and i can help
Click to expand...
Click to collapse
version-main: 3.14.401.600
(bootloader) DEBUG: cid: HTC__Y13
You can obtain your 1.39 hboot firmware update here
http://forum.xda-developers.com/showthread.php?t=1957376
Its the first one in the OP.
Put the file in the fastboot folder and rename it to firmware.zip
Then put the phone in the bootloader and relock it
Fastboot oem lock
Then flash the firmware with these commands
Fastboot oem rebootRUU (watch the capitals, this command will reboot into a black screen with a silver HTC logo)
At that point you flash the firmware
Fastboot flash zip firmware zip (if it fails the first time, don't worry....just repeat the command until it says oke)
Then unlock the bootloader, reflash the custom recovery and install a brand new JB rom of your choice !
Mr Hofs said:
You can obtain your 1.39 hboot firmware update here
http://forum.xda-developers.com/showthread.php?t=1957376
Its the first one in the OP.
Put the file in the fastboot folder and rename it to firmware.zip
Then put the phone in the bootloader and relock it
Fastboot oem lock
Then flash the firmware with these commands
Fastboot oem rebootRUU (watch the capitals, this command will reboot into a black screen with a silver HTC logo)
At that point you flash the firmware
Fastboot flash zip firmware zip (if it fails the first time, don't worry....just repeat the command until it says oke)
Then unlock the bootloader, reflash the custom recovery and install a brand new JB rom of your choice !
Click to expand...
Click to collapse
Well, thanks for all the help! Now its time for me to **** around with all the different roms out there
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
Hi.
I've got an HTC One M8 and would like to get everything back to stock, but have been experiencing a bunch of issues.
The phone was stolen a couple weeks ago and I got it back yesterday. The person installed Android 6.0.1, ClockworkMod 6.0.4.8, Turbo, Viper and I've found a com.cyanogenmod.eleven folder on the SD card (not sure what it is though). I've tried doing everything by following "How to Unroot the HTC One M8 Complete Guide" by the Unlockr on Youtube (can't post a link since I'm new) , but I've been running into problems.
I can't connect the phone to a PC. I've checked Device Manager - it recognizes the phone as an Android Phone and it seems to think that it's a CD ROM.
My version-main is blank, and my cidnum is 02___102.
I've managed to get to Recovery but I get "md5 missmatch" every time i try to run it. There isn't a nandroid.md5 file in any of the backup folders.
Could someone please help me get my phone back to an out of the box state? I'm not a pro, but I'll be able to follow instructions.
Thanks.
Easiest way would be a RUU. Just find one that matches your Cid and you're good to go
Skickat från min HTC One M9 via Tapatalk
Roobwz said:
Easiest way would be a RUU. Just find one that matches your Cid and you're good to go
Skickat från min HTC One M9 via Tapatalk
Click to expand...
Click to collapse
Thanks dude, but could you elaborate a bit?
I found a collection of M7 RUUs but can't seem to find them for M8. What does the process look like, as in what should I do after I find the correct RUU?
milun said:
Thanks dude, but could you elaborate a bit?
I found a collection of M7 RUUs but can't seem to find them for M8. What does the process look like, as in what should I do after I find the correct RUU?
Click to expand...
Click to collapse
I don't have the time right now, but I'm sure that there's many guides in the general forums about how you can return 100%to stock
Skickat från min HTC One M9 via Tapatalk
Roobwz said:
I don't have the time right now, but I'm sure that there's many guides in the general forums about how you can return 100%to stock
Skickat från min HTC One M9 via Tapatalk
Click to expand...
Click to collapse
Like I said, it's not the guide I'm worried about, it's the issues I've been running into. Writing 10 sentences doesn't really require that much time if you know what you're writing about.
Thanks man, you've really helped me out.
milun said:
Could someone please help me get my phone back to an out of the box state? I'm not a pro, but I'll be able to follow instructions.
Thanks.
Click to expand...
Click to collapse
Can you get to the bootloader ?
If possible, post here fastboot getvar all result without serial & imei no.
Need to confirm your current firmware version base on these getvar details because your version-main is blank before we can advise whether to use RUU or non-rooted stock nandroid backup to restore
ckpv5 said:
Can you get to the bootloader ?
If possible, post here fastboot getvar all result without serial & imei no.
Need to confirm your current firmware version base on these getvar details because your version-main is blank before we can advise whether to use RUU or non-rooted stock nandroid backup to restore
Click to expand...
Click to collapse
Here's the getvar image I got when I tried to unroot the phone a couple days ago. If it's missing anything important I'll do it again. And yes, I can get into bootloader and recovery.
{
"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"
}
milun said:
Here's the getvar image I got when I tried to unroot the phone a couple days ago. If it's missing anything important I'll do it again. And yes, I can get into bootloader and recovery.
View attachment 3766822
Click to expand...
Click to collapse
Yes, please do it again as the important info i.e. hboot & baseband are missing
ckpv5 said:
Yes, please do it again as the important info i.e. hboot & baseband are missing
Click to expand...
Click to collapse
Here it is.
milun said:
Here it is.
View attachment 3766842
Click to expand...
Click to collapse
Great.. your firmware is 4.20.206.1
I'll give you link to RUU in half an hour when I'm home.
Meantime you may want a different method, restore non-rooted nandroid backup and its stock recovery then do OTA. You can read my thread linked in my signature.
ckpv5 said:
Great.. your firmware is 4.20.206.1
I'll give you link to RUU in half an hour when I'm home.
Meantime you may want a different method, restore non-rooted nandroid backup and its stock recovery then do OTA. You can read my thread linked in my signature.
Click to expand...
Click to collapse
Thank you!
I read your post earlier, but since I'm a noob I couldn't figure it out. So I'll wait for the RUU if that's ok with you.
milun said:
Thank you!
I read your post earlier, but since I'm a noob I couldn't figure it out. So I'll wait for the RUU if that's ok with you.
Click to expand...
Click to collapse
Here is the 4.20.206.1 RUU.exe : https://www.androidfilehost.com/?fid=95916177934555499
and you need PC with USB2.0 (don't use USB3.0 or any USB hub) and the latest HTC USB drivers -
http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
As your device is S-On, you need to relock the bootloader.
Put your device on bootloader/fastboot mode and connect to PC.
Open a command prompt from your fastboot/adb folder, run these commands to relock bootloader
fastboot oem lock
fastboot reboot-bootloader
right click the RUU.exe and select run as administrator, follow the instructions accept, next, next, update & blalblabla until it finish.
Lates you can check for OTA and update the device to the latest Marshmallow. I believe there will be two OTAs.
Note : this procedure will wipes everything on your device and give you out of the box state phone.
ckpv5 said:
Here is the 4.20.206.1 RUU.exe : https://www.androidfilehost.com/?fid=95916177934555499
and you need PC with USB2.0 (don't use USB3.0 or any USB hub) and the latest HTC USB drivers -
http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
As your device is S-On, you need to relock the bootloader.
Put your device on bootloader/fastboot mode and connect to PC.
Open a command prompt from your fastboot/adb folder, run these commands to relock bootloader
fastboot oem lock
fastboot reboot-bootloader
right click the RUU.exe and select run as administrator, follow the instructions accept, next, next, update & blalblabla until it finish.
Lates you can check for OTA and update the device to the latest Marshmallow. I believe there will be two OTAs.
Note : this procedure will wipes everything on your device and give you out of the box state phone.
Click to expand...
Click to collapse
Ok, so here's a bunch of questions. Bear with me, please
1. The RUU link takes me to a blank page, I guess it's down or something.
2. When I run the adb installer and choose to install the drivers it asks me if I want to install Samsung drivers. Is that how it's supposed to be?
3. Is it necessary to uninstall HTC Sync Manager? If so, how do I leave the drivers?
4. Do I need to put the RUU in a specific folder or can I run it from wherever I downloaded it?
milun said:
Ok, so here's a bunch of questions. Bear with me, please
1. The RUU link takes me to a blank page, I guess it's down or something.
2. When I run the adb installer and choose to install the drivers it asks me if I want to install Samsung drivers. Is that how it's supposed to be?
3. Is it necessary to uninstall HTC Sync Manager? If so, how do I leave the drivers?
4. Do I need to put the RUU in a specific folder or can I run it from wherever I downloaded it?
Click to expand...
Click to collapse
1. Link is ok for me ...
View attachment 3766907
2. Choose Y to install it system-wide but N for the drivers. You can open command prompt anywhere that you like even from desktop, the adb/fastboot work.
3. Yes, uninstall HTC Sync Manager, the installer will install Htc Sync Manager, USB Drivers and some microsoft needed runtime (separately). When you uninstall HTC Sync Manager, it will uninstall HTC Sync Manager only.
4. Anywhere that you like ... put on desktop for easy access.
ckpv5 said:
1. Link is ok for me ...
View attachment 3766907
2. Choose Y to install it system-wide but N for the drivers. You can open command prompt anywhere that you like even from desktop, the adb/fastboot work.
3. Yes, uninstall HTC Sync Manager, the installer will install Htc Sync Manager, USB Drivers and some microsoft needed runtime (separately). When you install HTC Sync Manager, it will uninstall HTC Sync Manager only.
4. Anywhere that you like ... put on desktop for easy access.
Click to expand...
Click to collapse
Awesome.
I'll try to get the link to open and I'll let you know how everything went when it's done.
Thanks dude.
ckpv5 said:
Here is the 4.20.206.1 RUU.exe : https://www.androidfilehost.com/?fid=95916177934555499
and you need PC with USB2.0 (don't use USB3.0 or any USB hub) and the latest HTC USB drivers -
http://forum.xda-developers.com/showpost.php?p=64926362&postcount=4
As your device is S-On, you need to relock the bootloader.
Put your device on bootloader/fastboot mode and connect to PC.
Open a command prompt from your fastboot/adb folder, run these commands to relock bootloader
fastboot oem lock
fastboot reboot-bootloader
right click the RUU.exe and select run as administrator, follow the instructions accept, next, next, update & blalblabla until it finish.
Lates you can check for OTA and update the device to the latest Marshmallow. I believe there will be two OTAs.
Note : this procedure will wipes everything on your device and give you out of the box state phone.
Click to expand...
Click to collapse
So, I finally got the link to work and got everything set up, but I noticed that there's an O2 in the name of the RUU. I believe O2 is a carrier and my phone had no carrier when I bought it, I just wanted to check if that could be an issue before I do anything.
milun said:
So, I finally got the link to work and got everything set up, but I noticed that there's an O2 in the name of the RUU. I believe O2 is a carrier and my phone had no carrier when I bought it, I just wanted to check if that could be an issue before I do anything.
Click to expand...
Click to collapse
You wrote on your post #1 "My version-main is blank, and my cidnum is 02___102" and your getvar all show cidnum O2__102 ... that means your device is an O2 variant.
I believe it is SIM unlocked, so you can use any SIM on it. Being an O2 device, you can only run O2 RUU and installing RUU won't relock the SIM unlock.
ckpv5 said:
You wrote on your post #1 "My version-main is blank, and my cidnum is 02___102" and your getvar all show cidnum O2__102 ... that means your device is an O2 variant.
I believe it is SIM unlocked, so you can use any SIM on it. Being an O2 device, you can only run O2 RUU and installing RUU won't relock the SIM unlock.
Click to expand...
Click to collapse
Aaaah, ****... The more you know, I guess
Thanks
ckpv5 said:
You wrote on your post #1 "My version-main is blank, and my cidnum is 02___102" and your getvar all show cidnum O2__102 ... that means your device is an O2 variant.
I believe it is SIM unlocked, so you can use any SIM on it. Being an O2 device, you can only run O2 RUU and installing RUU won't relock the SIM unlock.
Click to expand...
Click to collapse
I followed the steps you provided and the phone is back to its original state. Words can't express how grateful I am.
I'll make sure to donate when I get some extra cash, and if there's anything else I can do for you do tell. Thank you for bearing with a noob like me!
Milan
milun said:
I followed the steps you provided and the phone is back to its original state. Words can't express how grateful I am.
I'll make sure to donate when I get some extra cash, and if there's anything else I can do for you do tell. Thank you for bearing with a noob like me!
Milan
Click to expand...
Click to collapse
Great to know that you solved your problem :good:
No worry about donation, it is not needed .. to see a happy note from someone when he solved his problem, that's my satisfaction
Hi,
I got a little bit of a problem on my head.... I planned to flash CM12.1 on my HOX but i flashed a different boot.img by mistake! Now i cant get the phone into debugging mode and while using hasoonss toolkit it wont see my device cause i cant get it into debugging mode . Any ideas on how to solve the problem? There are a lot of threads inhere about bricked hox but i cant find one talking about the same problem....
Hope i can get some help on this.
Ow and a bit more info, i can get into bootloader and recovery.
go_insane1981 said:
Ow and a bit more info, i can get into bootloader and recovery.
Click to expand...
Click to collapse
if you can get into bootloader then just get the good boot.img and flash it using fastboot flash boot boot.img
Tried that but it won't see my device.
It doesn't apear in my devices.
go_insane1981 said:
It doesn't apear in my devices.
Click to expand...
Click to collapse
When on bootloader/fastboot mode, type
fastboot devices
to check connection
if it returns your device serial no, then it is good for you to
fastboot flash boot boot.img
adb devices is working when in recovery or on running OS, not on bootloader/fastboot
ckpv5 said:
When on bootloader/fastboot mode, type
fastboot devices
to check connection
if it returns your device serial no, then it is good for you to
fastboot flash boot boot.img
adb devices is working when in recovery or on running OS, not on bootloader/fastboot
Click to expand...
Click to collapse
Tried both ways again but no reaction wth a list of devices. It's blank...
install htc drivers http://www.mediafire.com/?eqrqb44r3ot18g1
SÜPERUSER said:
install htc drivers http://www.mediafire.com/?eqrqb44r3ot18g1
Click to expand...
Click to collapse
Any options on how to install the drivers different from normally? Apparently the drivers won't install as it should install...
Have HTC sync on my system, can i use some of those exe's in there?
This is wat happens with HTC installer.
go_insane1981 said:
This is wat happens with HTC installer.
Click to expand...
Click to collapse
You have a newer sets of drivers installed and the installer exits instead of downgrade the version.
Are you sure you are in fastboot mode?
To enter this.
Power off your phone.
Hold Power and volume down button until phone enters a white screen with Hboot written on it.
{
"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"
}
Now press power button again. The screen should now change to this
Showing fastboot marked in red.
Go to device manager and look for the driver. It should look like this ( Android USB Devices, My HTC)
In cmd type fastboot devices.
My cmd returns this.
Cant seem to get the drivers in my device manager, they are installed but not showing in my device manager...
SÜPERUSER said:
You have a newer sets of drivers installed and the installer exits instead of downgrade the version.
Are you sure you are in fastboot mode?
To enter this.
Power off your phone.
Hold Power and volume down button until phone enters a white screen with Hboot written on it.
Now press power button again. The screen should now change to this
Showing fastboot marked in red.
Go to device manager and look for the driver. It should look like this ( Android USB Devices, My HTC)
In cmd type fastboot devices.
My cmd returns this.
Click to expand...
Click to collapse
Ok i used a old htc and now it sees my device again.
Device manager sees the HOX now too.
go_insane1981 said:
Device manager sees the HOX now too.
Click to expand...
Click to collapse
It was my thought at first. So now we know that htc apparently dropped the support for one x and older devices in their driver pack. Good to know
Now i need to take a look at how i can push a diff rom in there since the other rom apparently wont work..
go_insane1981 said:
Now i need to take a look at how i can push a diff rom in there since the other rom apparently wont work..
Click to expand...
Click to collapse
What rom are you trying to install?
SÜPERUSER said:
What rom are you trying to install?
Click to expand...
Click to collapse
http://forum.xda-developers.com/htc-one-x/development/rom-cyanogenmod-12-1-t3396521
go_insane1981 said:
http://forum.xda-developers.com/htc-one-x/development/rom-cyanogenmod-12-1-t3396521
Click to expand...
Click to collapse
Have you flashed this "new storage layout"?
http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
SÜPERUSER said:
Have you flashed this "new storage layout"?
http://forum.xda-developers.com/htc-one-x/orig-development/storage-layout-hox-endeavoru-t3022358
Click to expand...
Click to collapse
Making a new layout is something i missed, Mone said ;
Flashing instruction like usual: perform a full wipe with TWRP for new layout, flash the ROM, flash the suggested GApps, reboot into fastboot mode, flash the boot.img exctracted from the ROM.zip, reboot into system, enjoy cm-12.1.
So i wiped the damn thing( ) after making a backup offcourse(which btw doesn't help cuz its screwed...). But i completely missed that i had to make a new layout... But stil i am convinced it can be "unbricked" one way or another.
I basicly follwed all the steps mentioned in this thread; http://forum.xda-developers.com/showthread.php?t=2069904 and it al worked up to the point i flashed the wrong kernel. After that i searched the forum for hours and found some things which could be connected but with a total different view of what my problem is/was(partially solved with your help) and ended up with putting a SOS sign up for help.