Related
SOLVED!
I need to send my DHD to repair, so I want to make it (almost) stock. It is now ENG S-OFF, HBOOT 0.85.2007, radio 26.14.04.28_M, CID HTC_Y13.
I think I will let it stay S-OFF, so I would just install a RUU.exe.
I have tried with two different releases of RUU's, both RUU_Ace_sen30_S_HTC_WWE_3.12.401.1_Radio_12.65.60.29.
The process stops at the moment when it says "ten minutes". It then shortly shows that I am not using the correct upgrade tool, which probably means that I am using a wrong RUU? What am I doing wrong?
it depends which country your in I need to know to help you.
Sent from my HTC Desire HD A9191 using XDA
I am from Denmark, I don't know whether HTC_Y13 is specific danish? It is also the CID of my newly bought Sensation
henrylar said:
I am from Denmark, I don't know whether HTC_Y13 is specific danish? It is also the CID of my newly bought Sensation
Click to expand...
Click to collapse
Have you tried reverting to stock with the Hack Kit? maybe that it is working.
---------- Post added at 08:14 AM ---------- Previous post was at 08:13 AM ----------
henrylar said:
I am from Denmark, I don't know whether HTC_Y13 is specific danish? It is also the CID of my newly bought Sensation
Click to expand...
Click to collapse
Have you tried reverting to stock with the Hack Kit? maybe that it is working.
or If you want to stay S-OFF, then u can restore the original backup and unroot...
unfortunately I did not take a backup of the stock, I have just checked :-(
Actually I have the goldcard I used to unlock and root it. However, my vol up button is not working ( vol down is) - which is why it has to go to service.
Is there anything I can do with that when installing the RUU from Windows?
I might go the hack kit, I have never used it that way around. I just try to understand what the problem is about installing the RUU, CID? - the ext4, that it does not like (I am on ARHD, Gingerbread and Ext4 recovery)?
When I try to use the RUU.exe: The fault comes when it is going to restart to bootloader, then it says: "fault 155, fault when updating the image"
henrylar said:
unfortunately I did not take a backup of the stock, I have just checked :-(
Actually I have the goldcard I used to unlock and root it. However, my vol up button is not working ( vol down is) - which is why it has to go to service.
Is there anything I can do with that when installing the RUU from Windows?
I might go the hack kit, I have never used it that way around. I just try to understand what the problem is about installing the RUU, CID? - the ext4, that it does not like (I am on ARHD, Gingerbread and Ext4 recovery)?
When I try to use the RUU.exe: The fault comes when it is going to restart to bootloader, then it says: "fault 155, fault when updating the image"
Click to expand...
Click to collapse
If your volume rocker is broken, maybe that is the issue, it stays pressed. You should try to flash a RUU from command prompt and fastboot, but first you have to get the PD98IMG.zip file....
Vol up does not act as if it is stuck, more like no reaction. The wifi also turned off a few days later, and I have seen that this is a normal fault, first vol up goes, then wifi - and that it takes a new board.
As said, I have the goldcard with a PD98img.zip on. There is a lot of ".img" files in that. Shall I fastboot flash to the recovery.img, that is within that zip, and then what?
Or do I need to find it from the procedure of looking at a temp-file when I try to install the RUU.exe?
Sorry for asking, but I think that I better double check in this situation
henrylar said:
Vol up does not act as if it is stuck, more like no reaction. The wifi also turned off a few days later, and I have seen that this is a normal fault, first vol up goes, then wifi - and that it takes a new board.
As said, I have the goldcard with a PD98img.zip on. There is a lot of ".img" files in that. Shall I fastboot flash to the recovery.img, that is within that zip, and then what?
Or do I need to find it from the procedure of looking at a temp-file when I try to install the RUU.exe?
Sorry for asking, but I think that I better double check in this situation
Click to expand...
Click to collapse
you can flash the zip file from fastboot...the img file you will be able just if you are ENG S-OFF
Just get the original RUU and then run it. maybe the PD98IMG.zip file that u have in your sdcard is not the correct one. Make sure that it is the one for your phone!!
Thank you - I am eng S_OFF
I am not sure I understand what you propose. Shall I extract the zip file from the RUU? What would the name be I should look for Can I fastboot a zip file, I thought it had to be an .img file?
henrylar said:
Thank you - I am eng S_OFF
I am not sure I understand what you propose. Shall I extract the zip file from the RUU? What would the name be I should look for Can I fastboot a zip file, I thought it had to be an .img file?
Click to expand...
Click to collapse
not actually. I think flashing a PD98IMG.zip file is better and safer. I am just saying that you should try using the correct RUU.
but can I do that without using vol up?
You can flash the RUU with the phone in fastboot. Plug it in (you should see fastboot USB in red), have the file in the PC, open a cmd session as admin and navigate to where the PD98IMG.zip file is and then type:
Fastboot oem rebootRUU (you should get a black screen with silver HTC)
Fastboot flash zip PD98IMG.zip (when you get the okay in the cmd screen, ignore the green bar in the phone)
Fastboot reboot
That will flash the file without using volume rocker. Hope it works...
Sent from my Inspire 4G using XDA
Thank you very much. I am unfortunately not home for the next days, but will try this which seems at the best solution.
henrylar said:
Thank you very much. I am unfortunately not home for the next days, but will try this which seems at the best solution.
Click to expand...
Click to collapse
Yeah, that should work...you can even boot into bootloader from command prompt.
If you need help, just PM me....
Success!I had to delete HTC sync to make get connection at the boot, but then everything went fine.
Thank you very much.
henrylar said:
Success!I had to delete HTC sync to make get connection at the boot, but then everything went fine.
Thank you very much.
Click to expand...
Click to collapse
Glad you made it....take care...
Hi guys,
This is my first thread here in XDA, so, forgive me by a possible mistake.
I recently bought a HOX, the seller said that is the international version.
I'm in 4.0.3, with software version 1.29.707.11 (already checked for updates, but phone says its up to date)
So, sometimes when i turn my wifi on, he doesn't connect in my network (already saved), i go to wifi settings, put to scan, and, aparently, the phone don't scan the networks and doesn't found my network too.
Obviously, im on the range of the network, and don't have that factory problem with bad wifi signal.
And, sometimes too, phone takes a lot of time to get carrier signal, so i turn on plane mode, then turn off, and finally get carrier signal.
My question is: is this normal? What can i try to fix it? (Thinked on a factory reset)
I don't tried anything yet.
If anyone could help, i'll appreciate and if the thread is on the wrong place, please move it
Just try flashing the RUU, which will delete everything and return it to stock.
BenPope said:
Just try flashing the RUU, which will delete everything and return it to stock.
Click to expand...
Click to collapse
Thanks for the help Pope!
I am VERY noob in HTC tools, can you say me what exactly is this "RUU", and where i can get it?
Its basically, a factory reset right? What is the difference from normal FR to this RUU tool?
lock! said:
Thanks for the help Pope!
I am VERY noob in HTC tools, can you say me what exactly is this "RUU", and where i can get it?
Its basically, a factory reset right? What is the difference from normal FR to this RUU tool?
Click to expand...
Click to collapse
The difference is that it will reflash the ROM from scratch, it's the first thing HTC do when you take your phone for repair. It's very safe (when flashed with decent remaining battery) and very thorough.
Check the Shipped ROM sticky in the development section.
I am searching about the Rom Update Utility, but i'm not finding a good tutorial to follow, explaining the whole process.
If anyone could help me in the process :laugh:
Edit:
Thanks again Pope! I'll look in dev section
You just have to charge the phone, put the phone in fastboot mode (hold down the volume down key when switching on the phone, then navigate from there), plug phone into Windows PC and double click RUU.
You may want to do an "adb backup" (you'll have search for this) beforehand, flash RUU, test and then restore.
BenPope said:
You just have to charge the phone, put the phone in fastboot mode (hold down the volume down key when switching on the phone, then navigate from there), plug phone into Windows PC and double click RUU.
You may want to do an "adb backup" (you'll have search for this) beforehand, flash RUU, test and then restore.
Click to expand...
Click to collapse
I'm not finding the correct RUU file for the One X, can you help me? Or just show me a place to search... (Some links here at job are blocked --') Basically finding the correct RUU file i'll do the rest without problem...
This "restore" you mean in the end, its the factory reset in the phone? Or another restore?
Don't need a backup, i got the phone 2 days ago hehehe
My HOX is totally clean.
No unlocked bootloader, no root.
This will not be a problem doing the flash with the stock RUU right?
lock! said:
My HOX is totally clean.
No unlocked bootloader, no root.
This will not be a problem doing the flash with the stock RUU right?
Click to expand...
Click to collapse
No, that's perfect, you don't need anything other than stock, and it will remain stock.
http://www.filefactory.com/file/5c0...Radio_1.1204.105.14_release_260743_signed.exe
BenPope said:
No, that's perfect, you don't need anything other than stock, and it will remain stock.
http://www.filefactory.com/file/5c0...Radio_1.1204.105.14_release_260743_signed.exe
Click to expand...
Click to collapse
Ben sorry for tons of questions hehe
I'm reading a tutorial, and on it said that i need my CID number, in order to download the correct RUU file for the correct region of my HOX. How can i know if this RUU you posted is the correct for my HOX?
I've tried to get my CID number (downloaded the fastboot flasher tool) but when i put the cid command he returns: CID > None lol
I Know that my HOX is from Shangai (has a SH in serial number) and got my MID number.
So, i just need to know which file i need to download, the right one of course hehehe
If i will need the CID to know, i'll ask for the files for fastboot commands (i don't found them)
If not, just confirm the link you posted ealier if its the correct RUU for my case.
PS.: This link posted is only for premium users, and i don't have a premium acc, can you provide in another mirror?
You can't flash the wrong RUU, the phone won't let you.
You don't need your CID as you are not unlocked, knowing that you are 1.29.707.x is enough. It's the right RUU.
I'm sure you don't need me to hold your hand whilst you use google to find that file somewhere else. The sticky dev thread I previously mentioned will likely have a ton of mirrors for the file.
So.. i'll look fot the file in other places.
Today, i've connected in my wifi network, and the phone says there's an update...
It's the same update announced days ago, but in my case with a different update number...
Phone has been upgraded to ICS 4.0.4 and Sense 4.1.
If the problems persist, i will flash the RUU anyway, but, because of this update, nothing changes right? The RUU file you posted still valid for my HOX?
Not any more, you've updated your hboot, so you'll need an updated RUU (you can't install on older hboot, packaged with an older RUU).
You're lucky:
http://www.filefactory.com/file/3rc...Radio_2.1204.135.20_release_278245_signed.exe
and
http://forum.xda-developers.com/showpost.php?p=30273253&postcount=1724
BenPope said:
Not any more, you've updated your hboot, so you'll need an updated RUU (you can't install on older hboot, packaged with an older RUU).
You're lucky:
http://www.filefactory.com/file/3rc...Radio_2.1204.135.20_release_278245_signed.exe
and
http://forum.xda-developers.com/showpost.php?p=30273253&postcount=1724
Click to expand...
Click to collapse
HELL YEAH!
I'll test for 2 ~ 3 days, if i note the same problem i'll flash it!
Thanks for all the help Pope!
With this 707 update I got better WiFi ..smooth, fast...amazing
Sent from my HTC One X using XDA Premium HD app
dragonesdenano said:
With this 707 update I got better WiFi ..smooth, fast...amazing
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Same here man...
In a network that once stood in 40% signal, now i'm getting almost 100%!
Apparently, carrier signal is working fine too.. i'll test for more 3 days...
I just got a new HTC One M8, I got it second hand, but kinda new, all rooted and everything, I was told I can just go on
and install new ROM's and it will all work. That didn't work.
I installed roms before, I know what needs to be done. I flashed my HTC Desire HD, hundreds of times.
So I came here, downloaded the new revolution rom from here
http://forum.xda-developers.com/showthread.php?t=2694917
I also downloaded the new Venom Rom from this site(to check them both)
Anyway I install the rom, I get these screenshots
Except for symlink fails, it seemed to all work.
I press reboot I get this screen
even when I press install SuperSU, it does something reboots and goes back to recovery, and it won't start my phone.
I tried a few times different ROM's, the SuperSU question keeps coming back everytimes i press reboot from TWRP, and every ROM
I tried won't start, I can only use the recovery.
I have TWRP v2.8.6 - the newest.
Any suggestions? Anything will do!
Thanks
If this helps, before I open the recovery i have this, so you can see my phone information
Try again with TWRP 2.6.3.3
dav_sap said:
If this helps, before I open the recovery i have this, so you can see my phone information
Click to expand...
Click to collapse
You have a GPE bootloader, can't install a Sense ROM
You need to convert it back to Sense bootloader if you decide to install a Sense ROM
ckpv5 said:
You have a GPE bootloader, can't install a Sense ROM
You need to convert it back to Sense bootloader if you decide to install a Sense ROM
Click to expand...
Click to collapse
Any guide here of how to do that?
dav_sap said:
Any guide here of how to do that?
Click to expand...
Click to collapse
I just gave instructions to someone else less than 5 minutes ago.
Here: http://forum.xda-developers.com/showpost.php?p=59894924&postcount=2
Ignore the superCID part, you already are superCID.
xunholyx said:
I just gave instructions to someone else less than 5 minutes ago.
Here: http://forum.xda-developers.com/showpost.php?p=59894924&postcount=2
Ignore the superCID part, you already are superCID.
Click to expand...
Click to collapse
I read your guide there, and I have a question.
should I be in some window in the pc/phone to run the RUU? becuase I connected my phone and went to fastboot mode, typed in
cmd "fastboot devices" and got the SN and I understood i was connected to fastboot. Then just tried to run the RUU and got
an error, not really sure if I need to run it from a different window or anything
Thanks!
dav_sap said:
I read your guide there, and I have a question.
should I be in some window in the pc/phone to run the RUU? becuase I connected my phone and went to fastboot mode, typed in
cmd "fastboot devices" and got the SN and I understood i was connected to fastboot. Then just tried to run the RUU and got
an error, not really sure if I need to run it from a different window or anything
Thanks!
Click to expand...
Click to collapse
What error? Did it say something and give you a number perhaps?
It might not be the right RUU for your model.
In fastboot, do fastboot getvar all and post the readout here. Delete the serial # and IMEI from it though. That is sensitive and personal information.
I, or someone else if they see this first, will direct you to the proper RUU.
xunholyx said:
What error? Did it say something and give you a number perhaps?
It might not be the right RUU for your model.
In fastboot, do fastboot getvar all and post the readout here. Delete the serial # and IMEI from it though. That is sensitive and personal information.
I, or someone else if they see this first, will direct you to the proper RUU.
Click to expand...
Click to collapse
Here it is
thanks
dav_sap said:
Here it is
thanks
Click to expand...
Click to collapse
I don't know. It should work. Try flashing the splash zip first that you can get from here first, then run the RUU as administrator.
xunholyx said:
I don't know. It should work. Try flashing the splash zip first that you can get from here first, then run the RUU as administrator.
Click to expand...
Click to collapse
I'll try to download the file again, and runnning it as administrator and I'll let you know.
Thanks for everything!
xunholyx said:
I don't know. It should work. Try flashing the splash zip first that you can get from here first, then run the RUU as administrator.
Click to expand...
Click to collapse
The RUU starts and it kinda start installing, but after verfication I go next, and it fails, saying my RUU is not the right version.
dav_sap said:
The RUU starts and it kinda start installing, but after verfication I go next, and it fails, saying my RUU is not the right version.
Click to expand...
Click to collapse
Go to where I linked to get the splash zip. Follow those instructions if you haven't already.
After you have flashed that, run the RUU. You may have to run it twice. Don't disconnect or reboot. Just run it a second time.
I am currently on KK Revolution 9.1 and trying to upgrade the firmware to the new 4.28.502.1 so I can get LP and when I get into the ADB and try to flash it, it states "Remote: Not allowed" . The phone is s-off and unlocked. Do I need to relock it and unlock it again?? Ideas?? Starting to lose support for some of the items on KK.
suzyq42 said:
I am currently on KK Revolution 9.1 and trying to upgrade the firmware to the new 4.28.502.1 so I can get LP and when I get into the ADB and try to flash it, it states "Remote: Not allowed" . The phone is s-off and unlocked. Do I need to relock it and unlock it again?? Ideas?? Starting to lose support for some of the items on KK.
Click to expand...
Click to collapse
AT&T devices are totally compatible with WWE/International firmware, and S-Off allows you to install that.
You are on AT&T, correct? Because 4.28.502.1 is from that carrier. If not, let me/us know and don't follow these instructions.
This is the easiest way, and you don't need a PC to do it.
Download this firmware.
Rename it to 0P6BIMG.zip (that's a zero, not the letter) using a file explorer and place it onto the root of your extSD (not in a folder).
Boot into bootloader by powering off your phone, then turning it on by holding down both the power button and vol down.
Select hboot if it doesn't automatically (vol buttons to navigate~power button to select) and follow the prompts (vol up to flash~power to reboot).
That should be it. Delete the renamed zip from your extSD, otherwise every time you boot to hboot it'll try to update again.
Then go back to bootloader and confirm that it says 4.16.401.10 next to OS.
Congratulations! You are now on Lollipop firmware and can flash the newest ROMs.
suzyq42 said:
I am currently on KK Revolution 9.1 and trying to upgrade the firmware to the new 4.28.502.1 so I can get LP and when I get into the ADB and try to flash it, it states "Remote: Not allowed" . The phone is s-off and unlocked. Do I need to relock it and unlock it again?? Ideas?? Starting to lose support for some of the items on KK.
Click to expand...
Click to collapse
You don't need to relock with s-off. Something else is going on. Post your getvar data (be sure to delete IMEI and serial number as these are personal info).
xunholyx said:
AT&T devices are totally compatible with WWE/International firmware, and S-Off allows you to install that.
You are on AT&T, correct? Because 4.28.502.1 is from that carrier. If not, let me/us know and don't follow these instructions.
This is the easiest way, and you don't need a PC to do it.
Download this firmware.
Rename it to 0P6BIMG.zip (that's a zero, not the letter) using a file explorer and place it onto the root of your extSD (not in a folder).
Boot into bootloader by powering off your phone, then turning it on by holding down both the power button and vol down.
Select hboot if it doesn't automatically (vol buttons to navigate~power button to select) and follow the prompts (vol up to flash~power to reboot).
That should be it. Delete the renamed zip from your extSD, otherwise every time you boot to hboot it'll try to update again.
Then go back to bootloader and confirm that it says 4.16.401.10 next to OS.
Congratulations! You are now on Lollipop firmware and can flash the newest ROMs.
Click to expand...
Click to collapse
It did it but now there is red lettering one the screen. How do I get that taken off and please point me to the directions for wiping the old ROM and installing the new. I had it on my screen in the form yesterday and now I can't find it again.
suzyq42 said:
It did it but now there is red lettering one the screen. How do I get that taken off and please point me to the directions for wiping the old ROM and installing the new. I had it on my screen in the form yesterday and now I can't find it again.
Click to expand...
Click to collapse
Here is the bigger issue, for some reason, the phone can't get past the opening screen. The only way I have found to get past this is to power drain the phone. Once done, you can boot into recovery. Then, I can start again. Must be some sort of circuity blocking this.
suzyq42 said:
Here is the bigger issue, for some reason, the phone can't get past the opening screen. The only way I have found to get past this is to power drain the phone. Once done, you can boot into recovery. Then, I can start again. Must be some sort of circuity blocking this.
Click to expand...
Click to collapse
As @redpoint73 said earlier, post your getvar. Hook up to your PC, get into ADB/fastboot and enter the command fastboot getvar all.
I was helping someone else with AT&T last night on the VenomROMs website, and mistakenly thought you were superCID when it was him. That won't be a problem though. It will abort with a CID mismatch.
The reason I suggested WWE firmware is that Marshmallow is coming out soon and WWE will get it way before AT&T updates.
If you want to stay on AT&T firmware, you could run the official RUU from HTC's US website.
Post your getvar, and we can go from there.
suzyq42 said:
I am currently on KK Revolution 9.1 and trying to upgrade the firmware to the new 4.28.502.1 so I can get LP and when I get into the ADB and try to flash it, it states "Remote: Not allowed" . The phone is s-off and unlocked. Do I need to relock it and unlock it again?? Ideas?? Starting to lose support for some of the items on KK.
Click to expand...
Click to collapse
OK here should be the final solution, when you are in fastboot/hboot screen you must enter "fastboot oem rebootRUU" then once you see the black screen with HTC logo then you may flash the firmware, you can not flash firmwares on PC while fastboot is actively running, but of course run the firmware flash command TWICE! first flash it will fail because HBOOT gets updated by it self, then on second flash the rest of the firmware files get updated.
If you have S-OFF then you never have to lock your bootloader again.
I had a HTC M8 with HTC developers edition installed 4.12
I tried to flash install SuperSU and it rebooted.. now the phone is completely unresponsive
no HTC logo,can't turn it off, can't turn it on.
I'm really hoping someone can help me recover my phone?
By the way, I am basically a noob with Androids.
update
if i hold the power button down + volume up / down
it will reboot with HTC logo , powered by android.
it then goes to a blank screen.
delete
Have you done a backup previous to rooting it, and with SU version did you use?
If you've got a backup you could try holding Vol+ and power as long until the screen goes dark, then in this exact moment switch to holding Vol- and hold it until the bookcases comes up.
Now you can go to recovery and restore the backup. If you have accomplished that use a cmd and enter the fastboot getvar all command and post it here, without IMEI and Serial No. Maybe one can find a RUU to flash back to Stock.
Send from my coffee machines swarm intelligence.
hi guys, thanks for your replies.
I spent all day googling, trying to figure out how to fix it and haven't been successful yet. I'll tell you what I did.
If I tried to hold down the volume buttons and power buttons, it would restart the phone, the HTC logo would appear and then the screen would go blank, so
I installed ADB and Fastboot on my computer, and I was able to type
ADB reboot-bootloader and that brought up the Fastboot / HBoot menu
I then flashed TWRP to the phone, and tried to install a new version of the Developers Edition from HTC using their RUU (from their website) but it failed.
Last ditch effort, was trying to flash SkyDragon but there was not enough space on my phone so it failed with a 'Not enough Space' error.
I then read some instructions that mentioned deleting the cache, so I did this, but now, when I connect my phone to ADB, it always says OFFLINE and I can't connect to fastboot or ADB.
I am really hoping I haven't made it even worse.
HTCNerdYoda said:
Have you done a backup previous to rooting it, and with SU version did you use?
Now you can go to recovery and restore the backup. If you have accomplished that use a cmd and enter the fastboot getvar all command and post it here, without IMEI and Serial No. Maybe one can find a RUU to flash back to Stock.
Click to expand...
Click to collapse
Hi,
Unfortunately I didn't make any backups, mainly because I use auto-sync to the cloud.
I followed your instructions and got to the recovery menu
It says:
** Software status: Modified **
M8_UL PVT SHIP S-ON
HBOOT-3.19.0.0000
Radio-1.25.214500021.0GG
OpenDSP-V48.2.2.000564-M8974_FO.1211
OS-4.16.401.10
emmc-boot 2048mb
Ok will check if there is a RUU to be found tomorrow morning and report back what to do after it.
Send from my coffee machines swarm intelligence.
ckpv5 said:
Hold both power button + volume up, when the screen turn blank, release both button and hold & press volume down button. This will take you to hboot.
Select recovery then try again to install SuperSU 2.65 or 2.64 (don't use any other version)
When done, reboot but when TWRP offer to install root, don't install.. just reboot
and see how it goes.
If still unsuccessful, relock bootloader and install the Dev Ed RUU - http://www.htc.com/us/support/htc-one-m8/news/
Click to expand...
Click to collapse
Thank you for your reply.
I entered into recovery, TeamWin Recovery project opened
I am not sure, how from here,I can install SuperSU?
IamASHER said:
Thank you for your reply.
I entered into recovery, TeamWin Recovery project opened
I am not sure, how from here,I can install SuperSU?
Click to expand...
Click to collapse
Just forget it ... your post #1 made me believe that you have a Dev Edition but your other post show you have a EU device.
I already deleted my previous post, so ignore it .. won't work for you.
Just wait for the other guy's help
Or ... seeing you're not sure how to use a RUU based on your above post, I suggest that you restore a 4.16.401.10 stock non-rooted backup and its matching recovery (no need to relock bootloader) then do OTA to 4.16.401.13
You can get all the files and How-To in my thread linked in my signature
Then you can install any custom Dev ED Marshmallow ROM that available in Development section if you want to, no need to root as they are pre-rooted.
Or you can root the stock ROM with no problem with the root offer in TWRP.
IamASHER said:
Thank you for your reply.
I entered into recovery, TeamWin Recovery project opened
I am not sure, how from here,I can install SuperSU?
Click to expand...
Click to collapse
So here we go. You can download the RUU here here. It's an executable for Windows PC. Start your M8 into bootloader, connect it to your PC and execute the file I posted in my link. This will help you to get back to a full stock International M8.
Send from my coffee machines swarm intelligence.
HTCNerdYoda said:
So here we go. You can download the RUU here here. It's an executable for Windows PC. Start your M8 into bootloader, connect it to your PC and execute the file I posted in my link. This will help you to get back to a full stock International M8.
Send from my coffee machines swarm intelligence.
Click to expand...
Click to collapse
Thank you.
I booted my M8 into Bootloader and then ran the file, unfortunately, I get an error:
ERROR 155 Unknown Error
When I follow the on screen instructions from the RUU, which tells me to remove the USB, the Bootloader screen appears
on my phone and it says 'Security Fail'
RUU
Is this because I modified by phone after I bought it?
It's an EU phone from Romania, but I later went to the HTC site and unlocked it and installed the Developers edition onto it, at least I thought I did.
Have you relocked your bootloader prior to executing the file? Has to be done for a RUU to work on an M8. When in bootloader start a CMD on your PC and navigate to your adb folder. Then type "fastboot oem lock" and right away "fastboot reboot bootloader" to verify that it says relocked at the top. If so execute the RUU once more.
BTW don't remove it from USB while flashing until flash has been completed otherwise the flash is going to fail.
Send from my coffee machines swarm intelligence.
HTCNerdYoda said:
Have you relocked your bootloader prior to executing the file? Has to be done for a RUU to work on an M8. When in bootloader start a CMD on your PC and navigate to your adb folder. Then type "fastboot oem lock" and right away "fastboot reboot bootloader" to verify that it says relocked at the top. If so execute the RUU once more.
BTW don't remove it from USB while flashing until flash has been completed otherwise the flash is going to fail.
Send from my coffee machines swarm intelligence.
Click to expand...
Click to collapse
Thank you. Its working again... I really appreciate your help
Never mind! Glad to read that all's working fine again. Enjoy your M8 and have a nice day.
help bricked m8
i bricked my m8 while tring to flash marshmallow in it with twrp now its stuck in the swiring screen ...i left it there till it died..the real issue is that my voulme down isnt working..is there anyway i can enter recovery?
Only if the M8 ist recognized by adb and fully booted, as then you could reboot to recovery by "adb reboot recovery".
But as I understood you are now on stock again by RUU aren't you!?
It's a risk to try to flash Custom Recovery and ROM, without been able to boot to bootloader by using hardware buttons, as if you get stuck again there won't be an easy way out of it.
Send from my coffee machines swarm intelligence.
HTCNerdYoda said:
Only if the M8 ist recognized by adb and fully booted, as then you could reboot to recovery by "adb reboot recovery".
But as I understood you are now on stock again by RUU aren't you!?
It's a risk to try to flash Custom Recovery and ROM, without been able to boot to bootloader by using hardware buttons, as if you get stuck again there won't be an easy way out of it.
Send from my coffee machines swarm intelligence.
Click to expand...
Click to collapse
He can't be stock by RUU because a RUU is not flashed via TWRP. And he never mentioned to try to flash a custom recovery, he's already on TWRP. And an issue with the volume rocker is always a problem, on a perfectly stock device or a custom modded one.....issue stays the same
Mr Hofs said:
He can't be stock by RUU because a RUU is not flashed via TWRP. And he never mentioned to try to flash a custom recovery, he's already on TWRP. And an issue with the volume rocker is always a problem, on a perfectly stock device or a custom modded one.....issue stays the same
Click to expand...
Click to collapse
I assumed he followed my advice to download and flash the linked WWE RUU when he stated that all is working fine again. Sorry I've been confused for a moment and forgot there are to participants having the same problem.
Send from my coffee machines swarm intelligence.
emmanex84 said:
i bricked my m8 while tring to flash marshmallow in it with twrp now its stuck in the swiring screen ...i left it there till it died..the real issue is that my voulme down isnt working..is there anyway i can enter recovery?
Click to expand...
Click to collapse
Try the ADB command or get the volume button fixed. That's about it what you can do.
HTCNerdYoda said:
Only if the M8 ist recognized by adb and fully booted, as then you could reboot to recovery by "adb reboot recovery".
But as I understood you are now on stock again by RUU aren't you!?
It's a risk to try to flash Custom Recovery and ROM, without been able to boot to bootloader by using hardware buttons, as if you get stuck again there won't be an easy way out of it.
Send from my coffee machines swarm intelligence.
Click to expand...
Click to collapse
i tried usiing ruu it ddnt work it ddnt see the device,adb also doesnt see the device
---------- Post added at 09:25 AM ---------- Previous post was at 09:01 AM ----------
HTCNerdYoda said:
I assumed he followed my advice to download and flash the linked WWE RUU when he stated that all is working fine again. Sorry I've been confused for a moment and forgot there are to participants having the same problem.
Send from my coffee machines swarm intelligence.
Click to expand...
Click to collapse
my problem now is..is there any way i can flash a rom on it or something just to take it past the boot loop