This are all steps that I have tried and nothing works:
1. Install twrp 2.7.0.2 succesfully, then viper. (no wifi)
2. flash ruu for att, install twrp 2.7.0.2 succesfully, the viper. (no wifi)
3. flash ruu for att, install twrp 2.8.6.0, twrp recovery won't load, stuck on screen
I've read in some threads that wifi issues are because of old firmware, but I installed latest rue and didn't solve anything, and for some reason twrp 2.6.8.0 which says is for all carriers won't work in my phone. Also tried installing ARHD rom and it doesn't work either. Is there any file I need to flash for wifi to work or what are the specific steps I need to follow for it to work correctly. I did this in another HTC M8 for Sprint and had no issues at all. I appreciate your help.
*** I managed to flash 4.4.2 custom kitkat rom. Wifi works in this one. How do I go from this one to Viper M8 without messing the wifi up? In the page it says to upgrade to 5.0.1 before but how do I even do that? Not sure what I'm supposed to flash before installing Viper or where to find it. Do I also need to update TWRP before? Thanks.
Did you try the Viper thread?
Haven't found detailed instructions yet. I managed to flash a stock rom for 4.4.2 for at&t. But when I searched on the phone for an ota update to 5.0.1 it didn't find any. Then I flashed viper again but wifi didn't work. I guess I have to install stock 4.4.2 again, the install a stock update to 5.0.1 and then flash viper. I'll try this option later to see if it finally works. Have been working on this for the past 3 days.
What RUU did you run?
Did you relock the bootloader to run the RUU (required since you are s-on)?
Your hboot indicates you are still on 4.4.2 firmware, which is why WiFi is broken on 5.0 (Lollipop) ROMs. You either ran the wrong RUU, or the RUU failed to install due to unlocked bootloader.
Easiest way to update the firmware is to relock the bootloader and run the AT&T Lollipop RUU.
I downloaded ann RUU zip file for version 4.4.2 and just placed it in sdcard and asked for uptade automaticaly. I don't have the AT&T sim card, which I guess is the reason why I press software update and it says that the phone is up to date. The two ruu I found for lollipop, one says european version and the other is .exe which won't work on a mac. I really don't know if a lollipop ruu zip file of the US version even exists or if installing the European version is the same thing or if my only option is OTA update with a sim card
Finally got it to work. Long process but I'll explain what I did for anyone with the same problem. Thanks for the help everyone.
* I downloaded RUU.exe from one of the threads
* Used parallels on mac ( download free trial of software and windows 7)
* First enabled show hidden files on windows
* went to C> users> (USERNAME)> APP DATA> LOCAL > temp> (open folder just created, one with a really long list of letters)> copy rom.zip from there to mac 1.6gb file
*rename to OP6bimg.zip
* copy to sd card root
* open bootloader > hboot
* it should automatically ask to complete update, just press volume up button and it should work just fine
* now you should be in stock lollipop.
(I havrn't rooted yet, but I guess now I won't have any wifi issues when flashing custom rom)
dannygarced said:
I downloaded ann RUU zip file for version 4.4.2 and just placed it in sdcard and asked for uptade automaticaly.
Click to expand...
Click to collapse
That means you are on 4.4.2 firmware. So you if you try to run any more recent version based ROMs (4.4.3, 4.4.4, 5.0, etc.) you will have broken WiFi. You need to run the 5.0 RUU to fix this.
dannygarced said:
I don't have the AT&T sim card, which I guess is the reason why I press software update and it says that the phone is up to date. d
Click to expand...
Click to collapse
That is correct. AT&T is unique compared to most other versions of the M8 in that you need to be connected to AT&T's network to get the OTA updates.
dannygarced said:
I really don't know if a lollipop ruu zip file of the US version even exists or if installing the European version is the same thing
Click to expand...
Click to collapse
Running the Euro RUU zip is definitely not the same thing as the AT&T RUU. The RUU checks the CID and MID of the phone. Since the CID and MID on the phone will not match what the RUU is looking for, the RUU will fail.
I haven't seen a Lollipop zip version of the RUU for AT&T.
Related
Here is the first Official ATT RUU for the Jetstream. I think many users waiting for this.
Now you can restore your device to stock always.
This update is only for AT&T Jetstream!!
(by the way, you can flash this ruu to any Jetstream which has s-off)
You can create a CWM flashable zip format from this RUU easily. Just extract the rom.zip file and flash the required .img files. This preserves your data partition but clean install is recommended.
This RUU deletes all your personal data and apps so backup to SD card.
http://www.htc.com/us/support/jetstream-att/downloads/
MIRROR:
https://rapidshare.com/files/1394623110/htc_jetstream_emr_update_1.30.502.1_us.exe
This system update includes:
Security patch
Removal of HTC Logger
Bug fixes
i can't see any thing fitting the description you wrote. just the htc sync and some PDF's...
am i wrong?
Make sure you relocked your bootloader!!! otherwise update will fail!!!
guru_shastri said:
i can't see any thing fitting the description you wrote. just the htc sync and some PDF's...
am i wrong?
Click to expand...
Click to collapse
Try to refresh the page or empty your cache and try again. I downloaded right now. If no luck I can upload to multiupload.
i still can't see it.
tried using other browsers even. no stock rom link.
could u make it CWM flashable and then upload to multiupload?
also,
can u specify what it contains?
I cannot make CWM zip but I can upload the RUU
please upload it. thanks.
here is the download link:
https://rapidshare.com/files/1394623110/htc_jetstream_emr_update_1.30.502.1_us.exe
sweet...thanks!
I hope everyone like this release and now everyone can back to stock who bricked his device. I'm waiting for this too from last november.
well, i tried running the file on my unlocked device. it failed (as expected..)
since creating the CWM flashable is over my skills, how can i run it?
does it worth the trouble in relocking the bootloader?
i d/lded the Ruu, but the installation failed (bootloader unlocked)
i got the rom.zip file but i have no idea how to convert it to cwm zip file. couldnt find a proper guide to it
now what do we do?
Can any upload it to another mirror
other than rapidshare?
Are the updates in this RUU worthwhile?
Relock your device bootloader first!!!!! Than run the RUU. I updated my relocked device successfully yesterday.
You can unlock it again after update. I successfully rooted it as well.
Now my device is much stable.
If you have AT&T working sim and data plan, you can update from the settings via OTA.
Update will fail if your device has unlocked bootloader!!!!!!!!!
Well, i updated my device.
i locked my device (fastboot oem lock) which put me in a "security issues" state.
that means the device is in bootloader state only. the only way to keep going from that point is running the RUU to overwrite the issues.
after the update - an unlock is required. that is done with the bin file sent from HTC when first unlocking the device. (fastboot flash unlocktoken Unlock_code.bin)
Now, ReRoot and your good to go.
OK. just finished the cycle. have no idea what the update contains actually - but still - doesnt worth the trouble. hopefully task or doomlord will make the RUU into a CWM flasable..
feherhollo, if you can, in the future be more specific about the process you do. lines like "relock the device" arn't so clear to everybody. thanks.
If you can all wait another day, I'll have a CWM-flashable zip out this weekend. It looks like bmw-boy might be doing this as well.
I'm trying to return my HTC One back to being unrooted because I wanna update it and almost everywhere I read, you need to unroot to get over the air updates. So I got S-Off and I relocked my bootloader, but whenever I try running the RUU, it always fails. I tried flashing it and I tried running the exe file. Why does it keep failing? Also, is it true you can't get OTA updates while being rooted? The RUU I use is for Cingular (which from my understanding is the one AT&T uses) and I have Super CID. Lastly, if anyone knows an easier way to return my phone to being completely stock and unrooted that would be great. Thanks in advance!
Which RUU did you use? Apparently the last official one was JB 4.3 w/ Sense 5.0, ver. 3.17.502.3. The one for KK4.4.2 w/ Sense 5.0, ver. 4.18.502.7 was apparently not actually released by ATT and many people were having problems with it.
clsA said:
Well near as I can tell the RUU did not originate from HTC, someone was able to create it and sign it same as HTC would. But the files behave differently than the "Real" HTC RUU. The only solution I found was to use the True HTC RUU from 3.xx.502.x and OTA to 4.xx.502.x to 5.xx.502.x. It requires s-off to flash the OTA's so it's not the perfect solution for everyone.
Click to expand...
Click to collapse
So if you tried with the KK4.4.2 RUU, download the JB4.3 RUU from http://www.htc1guru.com/. Since you're S-OFF, you can use either the .exe or the decrypted .zip. I used the decrypted .zip before and it worked fine. Once you get that flashed you can then take the OTAs to update to KK4.4.2 w/ Sense 6. You'll need to be on the AT&T network to get those OTA. Otherwise you'll need to manually flash the updates, as clsA states in his post that I quoted above.
As for not getting OTAs while being rooted....
It's not so much that being rooted prevents getting OTAs. It's the process of getting to root that modifies or deletes system files that need to be intact for the OTA to work. OTA need to be installed through stock recovery. If you're rooted, it's most likely that you have a custom recovery. Also, unlocking the bootloader deletes some files the OTA checks for. If those files not there, the OTA will not install.
Flashing an RUU is the easiest way to get completely stock. It resets the phone to an out-of-the-box state. Whereas a factory reset done from bootloader or recovery basically just wipes the data partition, which will remove any apps you installed and user data. But any modifications to the system partition that are done remain. You don't get back the files that are deleted when you unlocked the bootloader.
Also, since you are S-OFF, there's no need to relock your bootloader to run an RUU. That's only required if you're S-ON. And once you get S-OFF, there is no reason to go back to S-ON.
Since I just want to get the new OTA update, do you recommend I just flash the update as opposed to going back to stock recovery because I don't mind having a rooted phone? Also, my phones camera suddenly became blurry, is it possible that the rooting had something to do with it? If it did, would flashing the OTA update fix it or would I need to go back to stock recovery or would neither fix it? Sorry for so many questions.
First off, what version is currently on your phone? Depending on where you're currently at you may need to flash more than one update in order to get it to the latest version. And no matter what, you'll need to flash stock recovery in order for the updates to flash. OTA updates, whether taken OTA or flashed manually, require stock recovery, as I mentioned before. Also, again as I mentioned before, the process of rooting your phone (more specifically, the process of unlocking your bootloader) most likely deleted files from your system partition that need to be in place in order for the OTA updates to install. If they are not there, the update will fail. So to answer your question...No, I don't recommend "just flash the update as opposed to going back to stock recovery". It won't work.
Since you didn't answer my question and state which RUU you tried, I don't know if you tried a bad 4.4.2 RUU or if there are other issues with your device and/or computer that's preventing any RUU from installing. If you just don't want to flash the RUU, then you can try flashing the update in the phone's current state and when it fails, you can analyze the error report, try to track down stock versions of the files you're missing and restore them if you find them, then try the update again, hoping you found everything. That's a lot more of a hassle than just flashing the RUU, flashing the updates, rooting, and setting up your phone.
Another option is to just flash a custom ROM. Most of them will bring the phone up to the latest version. Some will even take it higher than what is officially available from AT&T.
As for your camera problem, can't see how just rooting would cause that, but maybe it did. Without knowing the cause of the issue, I can't say if just flashing the OTA would fix it. If it's a software issue, then possibly it would. If it's a hardware issue, then probably not. Focus on updating the phone and worry about the camera issue if it still persists once updated.
Sorry, I forgot about your question. First of all, I got it working using RUU Zip M7 UL JB43 SENSE50 MR Cingular US 3.17.502.3-decrypted. The one that didn't work for me is RUU Zip M7 UL JB 50 Cingular - 1.26.502.12. Second, I am running 4.4.2. Thats for anyone who comes across this and was wondering. Thanks for your help sharksfan7. Also, in case you were wondering, my camera is still blurry, but I'll start a different thread for that.
I was trying to flash my AT&T HTC One M8 to either T-Mobile or Google Play Edition. I rooted, unlocked my bootloader, got S-Off, but my firmware/hboot was outdated (3.16). I tried to flash CM12 instead, and here's where I messed up. I tried to flash the AT&T stock RUU ZIP without relocking the bootloader and now my HBOOT says "Software status: Modified". I'm running CM12, and all RUU exe don't detect my phone. I just want to convert my M8 to the T-Mobile or GPE. Any help is GREATLY appreciated,
ad4mydev said:
I was trying to flash my AT&T HTC One M8 to either T-Mobile or Google Play Edition. I rooted, unlocked my bootloader, got S-Off, but my firmware/hboot was outdated (3.16). I tried to flash CM12 instead, and here's where I messed up. I tried to flash the AT&T stock RUU ZIP without relocking the bootloader and now my HBOOT says "Software status: Modified". I'm running CM12, and all RUU exe don't detect my phone. I just want to convert my M8 to the T-Mobile or GPE. Any help is GREATLY appreciated,
Click to expand...
Click to collapse
The RUU isn't recognizing your phone because you have a non HTC rom on your phone. Just flash one of the various stock roms from this forum and then you can use the RUU. Secondly, you don't have to re-lock your bootloader if you are s-off to run the RUU.
Fixing the Device
ad4mydev said:
I was trying to flash my AT&T HTC One M8 to either T-Mobile or Google Play Edition. I rooted, unlocked my bootloader, got S-Off, but my firmware/hboot was outdated (3.16). I tried to flash CM12 instead, and here's where I messed up. I tried to flash the AT&T stock RUU ZIP without relocking the bootloader and now my HBOOT says "Software status: Modified". I'm running CM12, and all RUU exe don't detect my phone. I just want to convert my M8 to the T-Mobile or GPE. Any help is GREATLY appreciated,
Click to expand...
Click to collapse
<br />
Hi, Since you do have a working device with a rom on it, all you need to do is find a T-Mobile Rom that is compatible with the At&t version. Make sure this is a stock rom because an accidental flash can hard brick your device. Thanks.
johnnyutah22 said:
The RUU isn't recognizing your phone because you have a non HTC rom on your phone. Just flash one of the various stock roms from this forum and then you can use the RUU. Secondly, you don't have to re-lock your bootloader if you are s-off to run the RUU.
Click to expand...
Click to collapse
AFAIK, the ROM doesn't need to be stock to RUU, only to OTA. There doesn't even need to be a ROM on the device to RUU.
Also, if there was something wrong with the phone's configuration, an error message would have been the result; not failing to connect to the phone.
If the RUU isn't recognizing the device at all, there is probably a fundamental USB connectivity issues. OP should try to :
- Make sure phone is booted into OS, or into bootloader-fastboot mode to RUU. "Regular" bootloader mode or recovery won't work.
- Try another USB cable or port, even another computer if possible (in particular USB 3.0 doesn't play well with RUUs).
- Uninstall and re-install HTC Sync and Drivers.
Also, keep in mind that in order to run an RUU that is different from your version (which is the case for T-Mob RUU or GPE RUU on an AT&T device) you need to change the CID and MID to correspond to the RUU. This won't cause failure to connect, but will cause the RUU to fail with an error message.
---------- Post added at 09:36 AM ---------- Previous post was at 09:31 AM ----------
kps2501 said:
Hi, Since you do have a working device with a rom on it, all you need to do is find a T-Mobile Rom that is compatible with the At&t version.
Click to expand...
Click to collapse
The AT&T variant won't support all 3G (HSPA) and 4G (LTE) bands used by T-Mobile if you just flash a T-Mob ROM. You need to install the T-Mob firmware to enable full T-Mob band support; which the RUU does.
Also, the RUU will "fully convert" to the T-Mob or GPE versions; and allow official OTA updates for that version, if that is what the OP is looking for. But the band support is the more important factor.
kps2501 said:
Make sure this is a stock rom because an accidental flash can hard brick your device.
Click to expand...
Click to collapse
Not sure what is trying to be conveyed here. No ROMs (stock or custom) meant for the "GSM" versions of the M8 (meaning stay away from Sprint and Verizon specific ROMs) will brick your phone.
Flashing a ROM meant for another device can brick your phone (and may be possible with s-off), but again, that isn't what you stated (although may be what you meant)
Thanks to all.
I ended up figuring it out using the steps below.
•ADB sideload CM12 via TWRP
•Once booted started USB debugging
•Changed the MID to the GPe (using ADB shell)
•Changed CID from CWS__001 to GOOGL001
•Rebooted into bootloader (fastboot oem rebootRUU)
•Found the RUU zip (can't post the link- too new)
•Pushed it to the phone (fastboot flash zip)
•Failed
•Flashed again
•Success
Sent from my HTC One_M8 using XDA Free mobile app
Hello everybody,
After receiving a new HTC One M9, I wanted to root it to remove the annoying bloatware apps that come pre-loaded. I unlocked the bootloader, installed TWRC and tried to install SU. After many tries, it wouldn't install so I tried to flash a ROM instead. It worked, but lo and behold, the ROM doesn't work on my phone at all. (Android Revolution 40) Now my SIM card isn't registering either and I just want to put the phone back into the stock mode. I found some tutorials and found a RUU file on the HTC website for 3.41.651 which is the latest one for Marshmallow I think. I think the process now is to relock bootloader then use the RUU file .exe via my computer, but I figured I'd ask before I let my stupid ideas run wild. Thanks in advance to anyone who offers help.
Software up to date issue
HI all, just got this M8 and it is an ATT Version. but I believe it is unlocked because I am using it with cricket.
When trying to update Android Tells me software is up to date ?
Android version 5.0.2
HTC Sense Version 6.0
Software Number 4.28.502.1
HTC SDK API Level
I am pretty sure that ATT has updated to Marshmallow by now / So why can't I update? I am on wifi and 4G/LTE Could it be because I am using a Cricket Sim Card in the Phone ?
I have downloaded the RUU for Marshmallow software version 6.20.502.5. Should I continue with the Manual update ?
I believe this phone was originally purchased from ATT on May of 2016 if it makes any difference , figured I post it. since it could be a newer version of HTC M8.
Also is there a way to back up my current stock rom, without Rooting phone ? Thanks for all your help.
As I cannot root my phone, because when I go into developer option and search for S-off That option is not there and I can't Continue.
My responses below in red font:
ELEVO said:
HI all, just got this M8 and it is an ATT Version. but I believe it is unlocked because I am using it with cricket.
When trying to update Android Tells me software is up to date ?
I am pretty sure that ATT has updated to Marshmallow by now / So why can't I update? I am on wifi and 4G/LTE Could it be because I am using a Cricket Sim Card in the Phone ?
That is correct, the AT&t version (and most US versions) can only OTA update if connected to the proper branded carrier (AT&T in this case). Therefore, the RUU is your best option to update.
I have downloaded the RUU for Marshmallow software version 6.20.502.5. Should I continue with the Manual update ?
You can. But you need to flash the 6.20.502.5 firmware first, before you can flash the RUU. See instructions to flash the firmware here: https://forum.xda-developers.com/showpost.php?p=67123738&postcount=7
Then run the RUU. Keep in mind, that RUU will wipe the phone. So backup your data to an off-phone location (cloud, computer, etc.) before RUU.
Also is there a way to back up my current stock rom, without Rooting phone ? The current Lollipop ROM? No, there will be no way to revert to LP by official means, once you RUU to Marshmallow. I doubt you will find the need or desire to "downgrade" to obsolete LP version. If for some reason you did want to, there are options, but would require unlocking the bootloader (to install custom recovery and flash a Lollipop ROM), or s-off (which would allow you to "downgrade" by RUU - which is not allowed with s-on).
As I cannot root my phone, because when I go into developer option and search for S-off That option is not there and I can't Continue.
You are misunderstanding a couple things:
1) s-off is not a setting in Developer Options. s-off can only be obtained with sunshine app ($25)
2) You don't need s-off to root this device. Simply unlock the bootloader, install TWRP, and flash SuperSU to root
Click to expand...
Click to collapse
Detailed
redpoint73 said:
My responses below in red font:
Click to expand...
Click to collapse
Thanks for the detailed reply, really helpful and greatly appreciated :good:
Two more Questions, Can I upgrade to an official DEV Edition RUU on this ATT Device? or would I have to use a Custom Dev ROM ? as I am trying to Tether with my phone, just like my official Developer HTC M8 I purchased in 2014 , Seems AT&T phone wont allow me to Tether ?
Also once I flash firmware and upgrade to official RUU will need to Unlock and Root Loader? Will doing upgrading to official Marshmallow Relock bootloader and Un Root Phone ? Back to Stock ? Thanks again, I will be attempting this pretty soon. Thanks again
For the Record, I have made a back up of my Lollipop via TWRK. I also backed it up using Titanium back up, just in case.
Again, my responses in red font:
ELEVO said:
Thanks for the detailed reply, really helpful and greatly appreciated :good:
You're welcome. Always happy to help!
Two more Questions, Can I upgrade to an official DEV Edition RUU on this ATT Device?
You can't flash the Dev Edition RUU with s-on. Even though the versions are very similar (same model ID - MID) the two versions have different carrier ID (CID). Wrong carrier ID will make the Dev Ed RUU fail, by definition. And the only way to change CID is with s-off. Further, its not really necessary to flash the Dev Ed RUU (and not worth spending money of s-off) to accomplish what you want (see more below)
or would I have to use a Custom Dev ROM ? as I am trying to Tether with my phone, just like my official Developer HTC M8 I purchased in 2014 , Seems AT&T phone wont allow me to Tether ?
Its correct that the AT&T stock ROM disables tethering. Flashing most custom ROMs (or the Dev Ed ROM) will enable tethering - as well as remove annoying AT&T branding and bloat apps. Flashing the Dev Ed RUU is not necessary to accomplish this.
Also once I flash firmware and upgrade to official RUU will need to Unlock and Root Loader? Will doing upgrading to official Marshmallow Relock bootloader and Un Root Phone ? Back to Stock ? Thanks again, I will be attempting this pretty soon. Thanks again
You need to relock the bootloader in order to flash firmware and RUU (command: fastboot oem lock). Once the RUU is complete, the phone will be on a fully stock "factory" image. So you will be unrooted. You will also be back to stock recovery (no longer have TWRP installed). From there, what you want to do:
1) Unlock the bootloader again. Either use the same unlock bin code you used to unlock BL before. Or get a new code from HTCDev.com
2) Flash TWRP back to the phone with fastboot. TWRP 3.0.2 is recommended for compatibility with MM firmware.
3) Flash the desired custom ROM. The custom ROM will be rooted (if you flash the Dev Ed ROM, you can select root in the AROMA installer).
For the Record, I have made a back up of my Lollipop via TWRK. I also backed it up using Titanium back up, just in case.
Always good to make backups. Although be aware, that RUU will wipe the phone, including internal storage. So if you picked internal storage as your backup location, you'll want to move/copy to another location (removable SD is okay, otherwise to computer or cloud).
Also note that restoring app data (as well as call logs, SMS) using Titanium, after RUU or ROM flash should be okay. But don't restore any system data, as this can cause problems.
Click to expand...
Click to collapse
redpoint73 said:
Again, my responses in red font:
Click to expand...
Click to collapse
Ok i came back to this old post. I forgot all about it, it really is helping me alot.
My questioin is after i Relock the bootloader can i do a factory wipe? will this remove everything from my phone and bring it back to stock?
I relocked my phone, but all my apps and contacts are their.
Bricked ?
ELEVO said:
Ok i came back to this old post. I forgot all about it, it really is helping me alot.
My questioin is after i Relock the bootloader can i do a factory wipe? will this remove everything from my phone and bring it back to stock?
I relocked my phone, but all my apps and contacts are their.
Click to expand...
Click to collapse
I think i may have bricked my phone? I went and installed an RUU firmware file for Marshmallow as most instruct to do via Fastboot. All went well, installation completed and i was able to send command to phone to reboot. when it tried to reboot. white screen with HTC Comes on and then goes almost black with a very light dark grey background.
Phone would not reboot into anything but dark screen. even when i restarted it with power button. the only thing that worked for me, was Holding Down Power/Volume and quickly hit the volume down button before device would vibrate to reboot, that took me into recovery. Below is what i see in Recovery.
Phone now has new software
***RELOCKED***
m8_UL_CA PVT SHIP S-ON
HBOOT-3.1.0.0000
RADIO-4.0 [email protected]
OpenDSP-V56.2.2-00593-M8974_FO.0126
0S-6.20.502.5
eMMC-boot 2048MB
APR 14 2016,19:39:46.0
HBOOT
<Vol UP> to previous item
<Vol Down> to next item
<Power> to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
CHECK SMARTSD
IMAGE CRC
SHOW BARCODE
I was able to run and "IMAGE CRC" via boot loader. it gave me alot of numbers after calculating. not sure if that is a good sign ?
Things I've tried in Recovery.
1. Recovery goes back to black screen.
2. SHOW BARCODE Works- 3 bar codes showed up.
3. Fastboot works. but when i try command "adb devices" it says list of devices attached. but nothing shows up
4. Tried to do a factory reset and tries to do it, then a black phone pops up on screen with green arrow sgoing in circles for like 10 seconds. then reboots to dark screen.
Please Help :crying: Thanks
Can anyone help me with this? I bought the phone with me on vacation and now using an HTC Developer Edition that the button down doesn't work and Volume down button us sunk in But at least i have my phone with all my contacts and apps , For now ?
I would like to know if i can unbrick my other HTC . Thanks.
Late in responding, as I was on work travel myself, and not on XDA for over a week.
ELEVO said:
I think i may have bricked my phone?
Click to expand...
Click to collapse
It's basically impossible for you to do anything with an s-on M8 that will actually brick it. That is the good thing about s-on.
ELEVO said:
I went and installed an RUU firmware file for Marshmallow as most instruct to do via Fastboot. All went well, installation completed and i was able to send command to phone to reboot. when it tried to reboot. white screen with HTC Comes on and then goes almost black with a very light dark grey background.
Click to expand...
Click to collapse
I think you only flashed the firmware.zip and not the RUU. Based on the condition here, and your other thread you created here: https://forum.xda-developers.com/htc-one-m8/help/htc-one-e-m8-fastboot-issues-t3757628
I clearly described above to flash the firmware.zip then the RUU. They are 2 completely different things. Firmware is about 80 MB and only contains hboot, radio, and a few other things. RUU is a full image that is 1.5 GB.
No boot after flashing signed firmware is normal, as it expects the RUU to be run afterwards.
ELEVO said:
Fastboot works. but when i try command "adb devices" it says list of devices attached. but nothing shows up
Click to expand...
Click to collapse
adb doesn't work in fastboot mode. Only fastboot commands will work in fastboot mode. You can only use adb when booted to OS (not an option for you, obviously) or alternately in custom recovery TWRP. So what you describe (adb not working) is normal and expected.
However, fastboot is enough to get the phone working from the described condition.