Hello,i have a htc one m7(t-mob101)...s-on,unlocked and a custom rom,how can i turn it back to stock to have software warranty?
I have tryed all methods,and no succes.
dnautzu01 said:
Hello,i have a htc one m7(t-mob101)...s-on,unlocked and a custom rom,how can i turn it back to stock to have software warranty?
I have tryed all methods,and no succes.
Click to expand...
Click to collapse
Try this site http://www.handy-faq.de/forum/htc_one_custom_roms/282822-htc_one_firmwaresammlung_ruus_otas_backups.html and look for the nandroid backup and install it. It should put you back at stock.
Since you are S-ON, you will not be able to remove "Tampered" or return to "Locked" status. You need S-OFF to accomplish that, you could follow nkk71's SuperGuide to Stock link in my signature.
and if i want to go to t-mob 010 for the us?to have more updates?i can do that?i`m new in this and i`m a little afraid,i dont want to brake the phone...and i see the site htc1guru is off
dnautzu01 said:
and if i want to go to t-mob 010 for the us?to have more updates?i can do that?i`m new in this and i`m a little afraid,i dont want to brake the phone...and i see the site htc1guru is off
Click to expand...
Click to collapse
To receive the TMOUS updates you must be on TMOUS network. If you are, then you could change your CID & MID to TMOUS. If I were in the European area, I would change the CID to an Int'l one then use the .401 software version. It get updated directly from HTC and it is not dependent on the carrier. The CID for Germany is HTC__002. Here is how you could do it:
Here are the steps to re-branding your phone to Int'l:​
Unlock bootloader if not unlocked already!
Install Custom recovery
Download TWRP 2.6.3.3 from here: http://techerrata.com/browse/twrp2/m7
Achieve S-OFF, if not already!
With your hboot 1.5x use rumrunner or firewater to get S-Off: http://firewater-soff.com/ or http://rumrunner.us/
Try all options!
Change CID to the new code:
Code:
[B][I]adb reboot bootloader
fastboot oem writecid HTC__002[/I][/B] <- (CID is exactly 8 characters)
[B][I]fastboot reboot-bootloader[/I][/B]
Change MID to the new code: PN0710000 using: [TOOL] MID change without ENG HBOOT | Aroma GUI
Remove "Tampered" with the Guru Bootloader Reset Tool
Download and flash 4.19.401.9 firmware; place firmware in your fastboot/adb folder and rename to firmware.zip. Ensure you have moved all of your personal items off of your phone this firmware will wipe your phone. Open a command window in your fastboot/adb folder and type:
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip firmware.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Execute http://www.htc1guru.com/dld/ruu_m7_ul_k44_sense55_mr_htc_europe_4-19-401-9_r_radio_4a-23-3263-28_10-38r-1157-04l_release_353069_signed_2-1-exe/ or RUU 4.19.401.9 which now matches your CID & MID
There is no need to lock/relock bootloader with S-OFF, and do not even THINK about going back to S-ON!!!
Now you can receive the OTAs or flash them manually.
OTA_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.11-4.19.401.9_R_release_355954met8o678uio0omu3.zip
OTA_M7_UL_K44_SENSE60_MR_HTC_Europe_5.11.401.10-4.19.401.11_release_372404wj19h95c0x6oa19n.zip
OTA_M7_UL_K443_SENSE60_MR_HTC_Europe_6.09.401.5-5.11.401.10_release_386803.zip
OTA_M7_UL_K443_SENSE60_MR_HTC_Europe_6.09.401.10-6.09.401.5_release_397712mm1f6dd6rksg0p3s.zip
Click to expand...
Click to collapse
Related
i would like to know what everything means in htc's bootloader, whats fastboot? and whats does hboot mean, and what does everything thing in the bootloader mean and do? and why do we rename roms to PG05IMG... is that htc's way, like we like to use update.zip in custom recoverys.. thanks
anyone?????????
marcogiudice said:
anyone?????????
Click to expand...
Click to collapse
You're probably not getting a reply because these types of questions have been answered numerous times over the years - and people would probably rather ignore it than be a jerk by saying "ever heard of the search button??". Anyway... jsut Google "ADB for noobs", or "beginners guide to ADB" and you will probably find what you are looking for.
Lipmonger said:
You're probably not getting a reply because these types of questions have been answered numerous times over the years - and people would probably rather ignore it than be a jerk by saying "ever heard of the search button??". Anyway... jsut Google "ADB for noobs", or "beginners guide to ADB" and you will probably find what you are looking for.
Click to expand...
Click to collapse
i see what your saying i did google it before i posted and didnt find what i was looking for, i got adb setup correctly and have been using for it for 16 months but coming across htc bootloader it way different then motos or samsung's with some things in there that would help all the new tb users and should be posted and stickied or in the wiki thread
ok i found half my answer... this for other acquiring minds like me
Here's some (hopefully useful) information about the bootloader:
What's HBOOT?
It's immediately loaded when the phone is switched on. It's mostly responsible for checking and initialising the hardware and starting the phone's software, for flashing official software releases (RUUs via Fastboot), as well as a few other things. In some ways it's comparable to the BIOS on a PC.
How do I root HBOOT?
You can't, it makes no sense. It's a bootloader, not Android. It's like trying to play a DVD on your kettle.
What does upgrading HBOOT do?
It may add extra hardware support for new phones (e.g. SLCD displays) and may fix a few bugs. HTC doesn't release information about it.
What does downgrading HBOOT do?
The opposite. So, if you flash an SLCD phone with an old version of HBOOT that doesn't have the support, the screen won't work.
But rooting depends on HBOOT version?
It doesn't.
Why does upgrading HBOOT remove root?
It doesn't. When you flash an official update your ROM is replaced with an official one, which is why root is lost.
How do I change HBOOT version?
By installing an official RUU/update. There's no other way - the bootloader is protected by the phone's hardware security because a corrupt bootloader means a bricked phone with no way to recover. RUUs contain a version of the bootloader, which is automatically flashed.
Why do I need to downgrade HBOOT to root 0.92?
You don't. You had to downgrade Android because unrevoked3 couldn't root froyo. The new release can, so it works.
Why all the talk about HBOOT then?
Because it is confused with software release, which is the important part. An RUU won't work if the installed software is a higher version (e.g. 1.20.x won't work if you have 1.21.x), and people have mistaken that check for HBOOT version.
What about the xda 0.92 to 0.80 downgrade? It runs on froyo.
It's an engineering/test release from HTC that was leaked. It fakes its software version to 2.09.405.8 so it will run on froyo and downgrade the ROM, so long as you're not on a higher release than that. The process has nothing to do with HBOOT, but it does downgrade the bootloader to 0.80 as a side effect - and results in a dead screen on SLCD phones. It's generally a bad idea to use this hack.
Why would any of this matter?
Because instructions based only on HBOOT version are not reliable. They may not work, or may cause your phone to stop working.
OK NOW FOR FASTBOOT........
Fastboot
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images. It is disabled in the production G1 devices since USB support is disabled in the bootloader[1]. This can be changed if you get root on the device. See also [2]
Fastboot prerequisites
To be able to use fastboot, you need to be running either an ADP1 or the Engineering Bootloader on your G1.
If you are developing on a linux host, you may need to tweak UDEV to recognize the phone in fastboot mode. You may already have done this to get the phone recognized in Eclipse, but you need to do it again for fastboot, since fastboot uses a different device ID: 0bb4:0c01. The warning sign is that fastboot says "< waiting for device >" forever, even when you have the "FASTBOOT" message on the phone; if this happens, try adding the device ID 0bb4:0c01 to your UDEV configuration for Android.
For Opensuse 11.1, the following config file, in /etc/udev/rules.d/11-android.rules, seems to work:
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c01", MODE="0666", OWNER="mylogname"
SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", ATTRS{idProduct}=="0c02", MODE="0666", OWNER="mylogname"
NOTE: change "mylogname" to your Linux login ID. Also note that the product ID bit is optional (probably easier to leave it out), and you need to change "0bb4" to the vendor ID for your phone if it isn't made by HTC (whose vendor ID is 0bb4). You can find the vendor id using 'lsusb'. An alternative to this is just to run fastboot as root, using sudo.
Starting Fastboot
On the G1: To start fastboot, first get to the bootloader: turn off your phone and hold down the "camera" button while powering it back on. You will see a white screen with skateboarding bugdroids. If you just see the normal multicolored bootloader screen, you need to get the device side of fastboot working as noted above. Plug your phone into the usb and if you see "serial0" hit the "back" key. You should now see "fastboot" on the screen.
On the Samsung Galaxy: power down the phone, then long-press the two Call buttons. Beware that fastboot mode will continue to reboot the phone after ~30 seconds of inactivity.
Fastboot Binary
To make use of fastboot, you also need the fastboot program compiled for your host computer. If you have already built Android, you will have this file already. Its location should be:
<android source location>/out/host/{os}_{arch}/bin/fastboot
If you do not have fastboot built, you can either compile the Android source or try DarkriftX's precompiled fastboot (compiled on kubuntu x86)
Fastboot Commands
Here are the commands you can run on your host after fastboot has been started on a device connected via USB. This is a paste directly from the fastboot binary's "--help" command:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall 'flash boot' + 'flash system'
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
Forcing fastboot to load on every boot
Developers who are creating new images to try out very often can remove their boot and recovery images which will force the phone to enter bootloader mode every time you boot. To fix this, you would reflash the boot and recovery images back allowing the phone to boot normally.
$ fastboot erase boot
$ fastboot erase recovery
NOW,
SO WHY DO WE CHANGE RUU.'S TO PG05IMG??????????
AND THE COUPLE OF OTHER OPTIONS DO IN BOOTLOADER?
THANK U!
I'm guessing it's because that's what it looks for. Kind of like the apply update.zip on stock android recovery. If you notice when you flash, it goes through PG05IMG.X with various file extensions trying to find it and gives a not found error before it finally gets to .zip
PJnc284 said:
I'm guessing it's because that's what it looks for. Kind of like the apply update.zip on stock android recovery. If you notice when you flash, it goes through PG05IMG.X with various file extensions trying to find it and gives a not found error before it finally gets to .zip
Click to expand...
Click to collapse
right, so ok then i was guessing right its like update.zip for stock recovery
thanks
Somewhat of an explanation of our signature checking bootloader can be found here
http://forum.xda-developers.com/showthread.php?t=1008210
I've looked around and I can't seem to find a way to unlock the bootloader on my 2.3.6 Atrix. Most tuts are for 2.3.4. What's the best way to do it?
http://dl.dropbox.com/u/34025287/4547-fix-try2.sbf
Flash this with RSD lite - run the fastboot oem unlock commands if needed. Its as simple as that
G-Man. said:
http://dl.dropbox.com/u/34025287/4547-fix-try2.sbf
Flash this with RSD lite - run the fastboot oem unlock commands if needed. Its as simple as that
Click to expand...
Click to collapse
You just run those in ADB, right?
mugabuga said:
You just run those in ADB, right?
Click to expand...
Click to collapse
Yes that's correct. You shouldn't need to if you unlocked your bootloader before the .141 update. To re-root use this method, it will give a couple errors at a certain point, just disregard the errors and continue with the commands and reboot your Atrix when you've finished - http://www.atrixforums.com/forum/mo...ing-stock-locked-2-3-4-2-3-6-a.html#post47155
G-Man. said:
Yes that's correct. You shouldn't need to if you unlocked your bootloader before the .141 update. To re-root use this method, it will give a couple errors at a certain point, just disregard the errors and continue with the commands - http://www.atrixforums.com/forum/mo...ing-stock-locked-2-3-4-2-3-6-a.html#post47155
Click to expand...
Click to collapse
But even if I've never unlocked it, it should still work?
mugabuga said:
But even if I've never unlocked it, it should still work?
Click to expand...
Click to collapse
If you've never unlocked it, it will act like a soft brick and hang on the first reboot - this is normal. You should have a screen pop up with a list of a dozen or more options, you'll need to select 'fastboot' and then run the command in ADB - fastboot oem unlock - this will give you a unique ID # - repeat the fastboot oem unlock command with the # at the end like this - fastboot oem unlock <unique ID # here> and press enter, it will give a warning about voiding your warranty, select yes and continue. From there, it should proceed with the unlock. After wards you'll need to let it fully reboot. Then boot your Atrix BACK into fastboot again, and flash RomRacers latest recovery with ADB. You can find the thread in the Development section. Then you load your ROM of choice onto your internal SD card and boot into CWM Recovery (RomRacers) and flash the ROM - give your Atrix 10-15 mins to fully boot after you install your ROM.
G-Man. said:
If you've never unlocked it, it will act like a soft brick and hang on the first reboot - this is normal. You should have a screen pop up with a list of a dozen or more options, you'll need to select 'fastboot' and then run the command in ADB - fastboot oem unlock - this will give you a unique ID # - repeat the fastboot oem unlock command with the # at the end like this - fastboot oem unlock <unique ID # here> and press enter, it will give a warning about voiding your warranty, select yes and continue. From there, it should proceed with the unlock. After wards you'll need to let it fully reboot. Then boot your Atrix BACK into fastboot again, and flash RomRacers latest recovery with ADB. You can find the thread in the Development section. Then you load your ROM of choice onto your internal SD card and boot into CWM Recovery (RomRacers) and flash the ROM - give your Atrix 10-15 mins to fully boot after you install your ROM.
Click to expand...
Click to collapse
EDIT: Fixed the problem by pulling the batt and unpluging from the computer.
mugabuga said:
Alright. It says it worked on the phone, but my RSD Lite claims it failed with an error switching phone to BP Pass through mode (0x70BE). Its just hanging at the success screen on my phone.
Click to expand...
Click to collapse
Can you upload a pic of the screen you are seeing?
[edit] I gotta get to bed, I'll check back here tomorrow if someone else is unable to assist you tonight. Its after midnight here and I'm getting over a bad cold still. I will check back here tomorrow.
mugabuga said:
EDIT: Fixed the problem by pulling the batt and unpluging from the computer.
Click to expand...
Click to collapse
Glad to hear that Ya had me a bit concerned for a minute there...
I have been trying to lock everything back up to return my phone I am s on but was wanting to relock the bootloader and unroot. I i could not get the ruu to work I am on the new bootloader someone told me to adb oem lock so I did now my phone says tampered locked and security warning but it wont come out of the bootloader every time I try to reboot it goes back to the bootloader even if i power down it still goes back to the bootloader. please help
as of right now all i have is fastboot
shawnten said:
I have been trying to lock everything back up to return my phone I am s on but was wanting to relock the bootloader and unroot. I i could not get the ruu to work I am on the new bootloader someone told me to adb oem lock so I did now my phone says tampered locked and security warning but it wont come out of the bootloader every time I try to reboot it goes back to the bootloader even if i power down it still goes back to the bootloader. please help
as of right now all i have is fastboot
Click to expand...
Click to collapse
If the RUU doesn't work, the other two alternatives are to attempt to flash the stock system.img and stock boot.img through fastboot .. although I'm not sure this will work with S-ON, depends on whether or not the device is locked/unlocked via HTC's official method.
Also, the second alternative, could use the PG*zip file which is stored inside the RUU. the zip file can be extracted from the RUU and placed on the root of the sdcard. Then the bootloader will grab this file and flash, essentially performing the same thing as the RUU would.
I just got a at&t M8 from a friend its unlocked ( tampered & s-on running 4.4.2 how can i update it to lolilpop / Get all updates from At&t ...Help Me
nadir5191 said:
I just got a at&t M8 from a friend its unlocked
Click to expand...
Click to collapse
You mean SIM unlocked or bootloader unlocked. Or both?
If bootloader unlocked, you need to relock it with fastboot command: fastboot oem lock
Then you will want to run the Lollipop RUU on a PC (preferably not Win10).
Backup any personal data you want to keep before relocking bootloader and/or running RUU, as those steps will wipe all data on the phone (including internal storage).
Also, are you using AT&T as your carrier?
redpoint73 said:
You mean SIM unlocked or bootloader unlocked. Or both?
If bootloader unlocked, you need to relock it with fastboot command: fastboot oem lock
Then you will want to run the Lollipop RUU on a PC (preferably not Win10).
Backup any personal data you want to keep before relocking bootloader and/or running RUU, as those steps will wipe all data on the phone (including internal storage).
Also, are you using AT&T as your carrier?
Click to expand...
Click to collapse
My carrier is AT&T also its SIM unlock & running teamwin
where can i find the fastboot command: fastboot oem lock & Lollipop RUU on a PC (preferably not Win10).
nadir5191 said:
My carrier is AT&T also its SIM unlock & running teamwin
where can i find the fastboot command: fastboot oem lock & Lollipop RUU on a PC (preferably not Win10).
Click to expand...
Click to collapse
Code:
fastboot oem lock
is the command used with fastboot.exe
See [how to] lock/unlock your bootloader without htcdev(s-off required) by scotty1223
ROM Update Utility (RUU) is a Windows compatible executable (.exe) which will flash a complete software image to your device, including ROM, hboot, radio, stock recovery, and firmware. This is a handy method to return to (nearly) stock condition;
see [INDEX] AT&T One (M8) Resources Compilation Roll-Up (Updated 9/4/15) by redpoint73
sd_shadow said:
Code:
fastboot oem lock
is the command used with fastboot.exe
See [how to] lock/unlock your bootloader without htcdev(s-off required) by scotty1223
Click to expand...
Click to collapse
Section 1 on the above link is useful (setting up adb). But to avoid any confusion it should be noted that Section 2 (which also requires s-off) is not necessary. Section 2 method is only needed if you want to "hack" the bootloader screen to say LOCKED.
Simply setting up adb/fastboot, then opening Windows command prompt and typing command (after changing directory to the proper fastboot.exe location) fastboot oem lock will make the bootloader say RELOCKED which is sufficient to run the RUU. Also, this is possible with s-on.
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.