Related
Hi, here is a complete list of all the fastboot commands supported by the hero. The protocol is as described here, but there are extras..
reboot-bootloader -- reboot into bootloader. Standard
reboot -- reboot. Standard
getvar -- get various specific variables. Standard, but there are new variables.
download -- download something into phone memory. Standard
erase -- erase a partition. Standard (but wont erase mfg*, misc*). Standard
flash -- flash previously downloaded data. HTC's version has various security mode dependant restrictions (e.g. checks signatures if security is enabled). Standard
boot -- boot the previously downloaded data as a kernel image. Standard
signature -- set the signature for previously downloaded data. Standard
setflag -- set a flag, implemented but does nothing on hero.
clearflag -- clear a flag, implemented but does nothing on hero.
oem -- OEM specific command.
You can download a ZIP or NBH image and tell it to flash using the partition name "zip" or "nbh" instead of a real partition name.
Here's a list of the getvar variables:
version
version-bootloader
version-baseband
version-cpld
version-microp
version-main (or "mainver")
serialno
product
platform
mid (or "modelid")
cid (or "cidnum")
battery-status
battery-voltage
partition-layout
security
build-mode
boot-mode
commitno-bootloader
version-tp
hbootpreupdate
Here are the OEM commands. Execute with "fastboot oem <command>"
keytest
heap
boot -- boots the image from flash, not the one downloaded into memory.
reset
powerdown
rebootRUU
task -- parameter "28"= format userdata, "29" = format system+userdata (only does system if security is off though)
rtask
h (or ?) -- list the OEM commands.
rtask supports the following hex codes: 0,7,8,9. I'm guessing they'll be the same as documented here, but I've not dared try any yet The command 9 isn't listed on that page though..
Hope this helps. I've just got my serial debug cable working
Thanks its a nice list. Ill be getting my Hero tomorrow morning, so i cant wait!
thanks for the info, really useful!
I am trying to find the command or switch to RM a files from system/media as its read only (of course) I presume its not a fastboot issues but any help appreciated
R3PUBL1K said:
I am trying to find the command or switch to RM a files from system/media as its read only (of course) I presume its not a fastboot issues but any help appreciated
Click to expand...
Click to collapse
adb remount
or
mount -o remount,rw /dev/block/mtdblock3 /system
First one issued from your pc, the second one from a shell on the phone.
You need root access.
Hello guys,
in this thread i will explain, how a RUU (Rom Update Utility) works.
What does a RUU contain?
Yeah, really important for some guys. A normal RUU contains following files:
- AdbWinApi.dll (for use of adb.exe)
- adb.exe (for adb commands)
- ARUGlobal.dll (for the executable file)
- ARUWizard.exe (the RUU executable)
- ARUWizard.ini (basic configuration for the RUU)
- some language files for the RUU
- some bmp-files for the recovery fail (solutions)
- one PHONE.bmp shown in the RUU
- fastboot.exe (for fastboot commands)
- rom.zip (a signed HTC Rom)
- ReadMe-files in different languages
- some other unimportant files
Normaly the RUU is provided in a executable. This exe-file is a compressed, self-extracting InstallShield archive. If you start the file, the InstallShieldWizard extract the contents in the temp-folder of your current User and starts the ARUWizard.exe which is the "real" RUU.
Click to expand...
Click to collapse
What does the RUU while updateing the phone?
Well, its much easier as you think. First the RUU check which version is installed in phone. This is basicly done with following adb-command:
Code:
adb -s {phones adb name} shell getprop ro.build.description
The return is the version number of the phone.
If the phone is started in fastboot mode the RUU run following command and become the same return like with the adb-command:
Code:
fastboot -s {phones fastboot name} getvar version-main
If the version of the RUU rom.zip is higher as the version of the Rom installed on the phone, the RUU give you the option to update your phone.
Click to expand...
Click to collapse
The Update process
Some of you maybe think now, the RUU begins to do magic things. But the next thing is very easy. The RUU restarts the phone into fastboot RUU mode:
Code:
adb reboot-bootloader
fastboot oem rebootRUU
The next command is easily to send the rom.zip to the phones fastboot:
Code:
fastboot update {full path to the update package (rom.zip)}
The rest will do by phones fastboot, not by the RUU self. The RUU return and give out the actual state of the installation only, and gives you the error message if anything go false, or the message, that the phone is updated successfully. After this the RUU will restart the phone.
Click to expand...
Click to collapse
That is basicly what the RUU did, not more
Thx especially for the adb/fastboot commands.
Now everyone can see why modifying the ruu will not give us full access
Yeah, thats the BIG reason why i created this thread
ONeill123 said:
Code:
adb -s {phones adb name} shell getprop ro.build.description
Click to expand...
Click to collapse
does that mean i can change my version in build.prop ro.build.description and we can reinstall a rom from other country ????
ONeill123 said:
CODE]adb reboot-bootloader
fastboot oem rebootRUU[/CODE]
The next command is easily to send the rom.zip to the phones fastboot:
Code:
Code:
fastboot update {full path to the update package (rom.zip)}
The rest will do by phones fastboot, not by the RUU self. The RUU return and give out the actual state of the installation only, and gives you the error message if anything go false, or the message, that the phone is updated successfully. After this the RUU will restart the phone.
Click to expand...
Click to collapse
in ths way giving the comands manually can we falsh ny rom.zip ?? is it possible.? my wfs is with my bro he is gone out of town.. so cant try it.. will surely do it when he gets back.. but still very exited to know. is it possible?
You misunderstood all i think
To the ro.build.description:
The RUU check this only to get the current version and prevent a unuseful restart of phone and to give you the information. Not more.
And you can change the build.prop only with unlocked BL or s-off, and then you can install the system.img of another country self without a RUU.
To the rom.zip:
The RUU sent the rom.zip to fastboot only. The signature check do the fastboot/bootloader of the phone. So you can change the rom.zip, but the bootloader will say "signature error" or something else.
ONeill123 said:
You misunderstood all i think
To the ro.build.description:
The RUU check this only to get the current version and prevent a unuseful restart of phone and to give you the information. Not more.
And you can change the build.prop only with unlocked BL or s-off, and then you can install the system.img of another country self without a RUU.
To the rom.zip:
The RUU sent the rom.zip to fastboot only. The signature check do the fastboot/bootloader of the phone. So you can change the rom.zip, but the bootloader will say "signature error" or something else.
Click to expand...
Click to collapse
hehehe actually i have radio probs.. with my wifi n data pack.. so thought that i might be able to update the radio like this hehehe nvm ty oneil
Hi folks
I have recently bought a HTC One M8 on ebay which was converted to play edition by the seller using GPE RUU. I know very little about this but would like to attempt to return to stock whilst ensuring no flagged messages are left on.
I have searched and only come across guides that are specific to specific circumstances. Does anyone have or know of a general and safe guide that would work in my case?
Any help greatly appreciated.
Thanks in Advance
Sid
Do you have any idea what version the phone was running before GPe? Can you see the model number at the bottom of the back of the phone?
EddyOS said:
Do you have any idea what version the phone was running before GPe? Can you see the model number at the bottom of the back of the phone?
Click to expand...
Click to collapse
model: OP6B100
No idea what it was running before.
OK, going by that ID we can assume it's an EU unbranded handset. Or we can at least we can treat it as such. So, assuming you want to go back to 100% stock Sense (but keep S-OFF) do the following:
First, download the following to your fastboot folder:
4.16.401.10 RUU ZIP - https://drive.google.com/file/d/0B17smFr95pleU2NqcVB3NWxoNnM/view (rename it ruu.zip - not ruu.zip.zip)
htc_fastboot.exe - https://www.androidfilehost.com/?fid=95897840722646249
1.54.401.5 FW ZIP - http://www.androidfilehost.com/?fid=23329332407589439 (rename it firmware.zip)
TWRP - http://techerrata.com/file/twrp2/m8/openrecovery-twrp-2.8.4.0-m8.img (rename it to recovery.img)
HTC Sync Manager (for the drivers) - http://www.htc.com/uk/support/software/htc-sync-manager.aspx (install it and then uninstall Sync Manager but leave the drivers)
1. First things first, change the CID to Super CID - fastboot oem writecid 11111111
2. Once done, reboot the bootloader to confirm it's showing the Super CID - fastboot reboot-bootloader
3. Once confirmed it's set, we now need to set the right MID in case this was changed by the seller. To do this, we can use TWRP. Flash TWRP (downloaded earlier) - fastboot flash recovery recovery.img
4. Once flashed, boot into TWRP and connect the phone to your PC
5. Once the drivers are installed, make sure the PC sees the phone by typing adb devices
6. So long as it's been shown as a connected device, type adb shell
7. We can now change the MID to the EU unbranded one by using the following command (copy/paste this as it has to be exact)
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x31\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
8. Once done, we can now 'lock' the bootloader using the following command (whilst still in adb shell)
Code:
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
9. And we can also reset the tamper flag at the same time
Code:
echo -ne '\x00' | dd of=/dev/block/mmcblk0p6 bs=1 seek=5314564
10. Once all that is done, type exit to leave adb shell and then reboot the phone into the bootloader through the reboot menu in TWRP
11. Once back at the bootloader, you should find the phone is now 'LOCKED' and it shouldn't say 'TAMPERED' at the top either but should still have the black bootloader interface that the GPe has. We can now set it all back to Sense
12. Reboot the phone into RUU mode - fastboot oem rebootRUU
13. Once in RUU mode, flash the firmware ZIP - fastboot flash zip firmware.zip
14. The process will fail the first time and reboot. Run the same command again once it's rebooted - fastboot flash zip firmware.zip
15. Once finished, reboot the phone to the bootloader to confirm you now have the white 'Sense' bootloader - fastboot reboot-bootloader
16. Assuming it's correctly flashed, reboot back into RUU mode - fastboot oem rebootRUU
17. We can now flash the RUU using the htc_fastboot package - htc_fastboot flash zip ruu.zip
18. Once finished, reboot back to the bootloader one last time - fastboot reboot-bootloader
19. Once back in the bootloader, change the CID to HTC__001 - fastboot oem writecid HTC__001
20. Reboot the bootloader to confirm the change has been successful - fastboot reboot-bootloader
21. Once back at the boot loader, disconnect the phone and boot into recovery and do a factory reset
22. Once the reset finishes, reboot the phone
That should get it all working but any issues obviously let us know
Fastboot folder? I did say i was a newbie! thanks
OK, perhaps it might be worth reading up on fastboot/adb before doing anything as the above isn't for the faint-hearted!
EDIT: I've attached my 'fastboot' folder. Extract it to the root of your C: drive so it's easy to get to. All the commands in my guide are done through a command prompt in Windows starting in that folder, e.g. C:\platform-tools\fastboot oem rebootRUU
https://drive.google.com/file/d/0B8L4pkbzdlR3Z3dsNGZfSWhCeTA/view
ok, I have installed fastboot adb andi have a folder called adb in my c:. I am now downloading all the items listed above and renaming as appropriate and moving to the folder named adb. am I on the right track?
Getting there. You could've just downloaded/extracted the folder I linked to on your C: drive but as long as the contents is somewhere you can easily find you should be OK
i have the same problem but mine is in a loop.... my htc m8 is an 0P6B700, ive tried to convert it to a lollipop GOOGL001 but it didnt work... and i am stuck in bootloader.... i have already installed the twrp 2.8... and i have the working the fastboot in my pc... but i dont know what to do....
i want to install a lollipop rom.. but its ok if i need back to stock.
Any help will be appreciated
thanks.
tonytdc1000 said:
i have the same problem but mine is in a loop.... my htc m8 is an 0P6B700, ive tried to convert it to a lollipop GOOGL001 but it didnt work... and i am stuck in bootloader.... i have already installed the twrp 2.8... and i have the working the fastboot in my pc... but i dont know what to do....
i want to install a lollipop rom.. but its ok if i need back to stock.
Any help will be appreciated
thanks.
Click to expand...
Click to collapse
Please start your own thread rather than hijacking someone else's, and also post your output from fastboot getvar all so we can work out what's best to get you back up and running
I know your getting help here, but...Can I ask..
When you bought the One M8 on eBay, did the ad or photos say you were buying an M8 unlocked and Converted from Sense to GPE.
If Not, you do know youve been sold an incorrect product and you have a case against the seller for false advertising, so save yoursewlf the issues, exersize your rights and send it back.
Plus, you say you are new to flashing / unlocking, so if you brick this M8, you dont have any returns room.
Just wanted to say that and hope it helps. Good Luck
EddyOS said:
Please start your own thread rather than hijacking someone else's, and also post your output from fastboot getvar all so we can work out what's best to get you back up and running
Click to expand...
Click to collapse
Ok i will... thanks
EddyOS said:
Getting there. You could've just downloaded/extracted the folder I linked to on your C: drive but as long as the contents is somewhere you can easily find you should be OK
Click to expand...
Click to collapse
Hi Eddy
Thanks for all your support, i have successfuly completed step 1, 2 and 3. Now I need some assistance in flashing TWRP. How do i do this and what do i use?
regards
3 was flashing TWRP so if you've done that you now enter recovery via the bootloader.
I tried to update my phone to 6.0 from 4.4.2 with ADB. Came with an error "System partition size error". It doesn't see the SD card when I tried to install from it.
My phone stuck at hboot screen. I can only access recovery and hboot menu. And when I tried to update to Lolipop with exe from a computer it says "Error 155: Unknown error". Xp 32 bit USB 2.0.
After I said reboot system through TWRP and it said No OS installed! .
But I have already installed ViperOne 3.2.1 Kitkat and Stock 4.4.4 before without any error still can't escape from boot menu. Any help would appreciate.
Here is some information:
S-OFF
Unlocked
version: 0.5
version-bootloader: 3.16.0.0000
version-baseband: 1.14.2133156.UA24G
version-cpld: None
version-microp: None
version-main: 1.12.401.17
version-misc: PVT SHIP S-OFF
serialno: FA43CSF00379
imei: ***********
imei2: Not Support
meid: 99000499006617
product: m8_whl
platform: hTCBmsm8974
modelid: 0P6B10000
cidnum: 11111111
battery-status: good
battery-voltage: 0mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 0a41237a
hbootpreupdate: 11
gencheckpt: 0
And I think the device was T-Mobile 13000 at first but I'm not sure about it.
Did you update the firmware? I ran into a similar issue because my device shipped out with 4.4.2.
To update the firmware, you have to do the following:
Set your OEM's CID. Do not use SUPERCID.
My device was GPE, so [fastboot oem writecid GOOGL001]
Re-lock your Bootloader using Fastboot.
[fastboot oem lock ] then [fastboot reboot ruu]
You'll see the device logo centered onscreen.
Flash a firmware update file (does NOT have to be a whole ROM) and you'll be able to update to the threshold of that firmware.
I have Marshmallow firmware. So I can use MM or LP as well as KK ROMs now without bootloop.
Be sure to hit thanks if I helped! Be even more sure to PM me if you need help (like firmware files if you have the same variant).
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?
My current firmware is: 3.28.401.9. Which one do you suggest to install? And I would really appreciate if you send me firmware files. I'm not sure which variant's firmware I should use.
Edit: By the way I can install roms but ruu.exe gives me error.
DreamGod said:
My current firmware is: 3.28.401.9.
Click to expand...
Click to collapse
wrong ...
your firmware is 1.12.401.17 as shown on your getvar details on post #1.
and your device is a sprint device (m8_whl) and you should not flash any GSM firmware.
Sprint & GSM has different System partition size (your error)
change your model-ID currently shown as 0P6B10000 back to to sprint 0P6B70000
and install Sprint RUU or firmware. You can find them on Sprint forum.
furboom1240 said:
Did you update the firmware? I ran into a similar issue because my device shipped out with 4.4.2.
To update the firmware, you have to do the following:
Set your OEM's CID. Do not use SUPERCID.
My device was GPE, so [fastboot oem writecid GOOGL001]
Re-lock your Bootloader using Fastboot.
[fastboot oem lock ] then [fastboot reboot ruu]
You'll see the device logo centered onscreen.
Flash a firmware update file (does NOT have to be a whole ROM) and you'll be able to update to the threshold of that firmware.
I have Marshmallow firmware. So I can use MM or LP as well as KK ROMs now without bootloop.
Be sure to hit thanks if I helped! Be even more sure to PM me if you need help (like firmware files if you have the same variant).
Sent from my HTC M8 GPE
Mass Transit Honchkrow
Click to expand...
Click to collapse
He is S-Off. No need to relock the bootloader ever.
And for S-On users, the only time you will need to relock the bootloader is for running an RUU
Also, superCID will work with any firmware. No need to set the CID to his carrier's (not OEM's) CID
xunholyx said:
He is S-Off. No need to relock the bootloader ever.
And for S-On users, the only time you will need to relock the bootloader is for running an RUU
Click to expand...
Click to collapse
I thought so too. I'm also s-off but my firmware update stalled code 20 until I relocked the bootloader. But when I was finished I reversed that course [fastboot OEM unlock] and then dismissed the warning.
That's exactly what I did. Note that I mention RUU in my Fastboot instructions. :\
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?
furboom1240 said:
I thought so too. I'm also s-off but my firmware update stalled code 20 until I relocked the bootloader. But when I was finished I reversed that course [fastboot OEM unlock] and then dismissed the warning.
That's exactly what I did. Note that I mention RUU in my Fastboot instructions. :\
Sent from my HTC M8 GPE
Mass Transit Honchkrow
Click to expand...
Click to collapse
Error 20? Never heard of that one, no idea what it is.
ckpv5 said:
wrong ...
your firmware is 1.12.401.17 as shown on your getvar details on post #1.
and your device is a sprint device (m8_whl) and you should not flash any GSM firmware.
Sprint & GSM has different System partition size (your error)
change your model-ID currently shown as 0P6B10000 back to to sprint 0P6B70000
and install Sprint RUU or firmware. You can find them on Sprint forum.
Click to expand...
Click to collapse
Thank you I will try and tell the results. I though that my device was GSM didn't even know that it was Sprint. I was totally wrong at first then.
xunholyx said:
Error 20? Never heard of that one, no idea what it is.
Click to expand...
Click to collapse
Something I got in the Fastboot.
You open a command window and reference the file.
You either get a OKAY (milliseconds taken) or FAILED (error##). Some errors are obvious, like the cable disconnected, your recovery is out of date, update your SDK.
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?
furboom1240 said:
Something I got in the Fastboot.
You open a command window and reference the file.
You either get a OKAY (milliseconds taken) or FAILED (error##). Some errors are obvious, like the cable disconnected, your recovery is out of date, update your SDK.
Sent from my HTC M8 GPE
Mass Transit Honchkrow
Click to expand...
Click to collapse
Yeah, I know what the error codes are. LOL! I'm far from new at this.
I just haven't heard of error 20
xunholyx said:
Yeah, I know what the error codes are. LOL! I'm far from new at this.
I just haven't heard of error 20
Click to expand...
Click to collapse
Sometimes remembering this stuff makes my head hurt. I often went to webchat to diagnose issues or find similarities.
Sometimes it's how I word a problem, the other time its the problem itself that throws off a bit... ?
Sent from my HTC M8 GPE
? Mass Transit Honchkrow ?
ckpv5 said:
wrong ...
your firmware is 1.12.401.17 as shown on your getvar details on post #1.
and your device is a sprint device (m8_whl) and you should not flash any GSM firmware.
Sprint & GSM has different System partition size (your error)
change your model-ID currently shown as 0P6B10000 back to to sprint 0P6B70000
and install Sprint RUU or firmware. You can find them on Sprint forum.
Click to expand...
Click to collapse
Hello, it's me again. I'm trying to change my model-id but it shows like that:
P6B7\ (enter)
0000
My device won't open (only hboot and fastboot, no recovery) so I'm not sure how I can use adb since it doesn't show my device and its serial number. I appreciate your help...
DreamGod said:
Hello, it's me again. I'm trying to change my model-id but it shows like that:
P6B7\ (enter)
0000
My device won't open (only hboot and fastboot, no recovery) so I'm not sure how I can use adb since it doesn't show my device and its serial number. I appreciate your help...
Click to expand...
Click to collapse
How did you do that ? You wrote the code on your own instead of copy paste the whole code ? I don't know whether can fix that ... let's try again.
1. You need to install the old version TWRP recovery as your current hboot is 3.16.0.0000
install TWRP 2.8.1.0 - https://dl.twrp.me/m8/
2. After TWRP 2.8.1.0 installed, boot to recovery
mount - system
3. connect to PC and open a command prompt from your fastboot/adb folder then run command
adb shell
then this code (copy and paste .. don't write them on command prompt on your own)
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
exit
on recovery select reboot - bootloader
then run command fastboot getvar mid - you should have 0P6B70000 now (hopefully)
ckpv5 said:
How did you do that ? You wrote the code on your own instead of copy paste the whole code ? I don't know whether can fix that ... let's try again.
1. You need to install the old version TWRP recovery as your current hboot is 3.16.0.0000
install TWRP 2.8.1.0 - https://dl.twrp.me/m8/
2. After TWRP 2.8.1.0 installed, boot to recovery
mount - system
3. connect to PC and open a command prompt from your fastboot/adb folder then run command
adb shell
then this code (copy and paste .. don't write them on command prompt on your own)
Code:
echo -ne '\x30\x00\x50\x00\x36\x00\x42\x00\x37\x00\x30\x00\x30\x00\x30\x00\x30' | dd of=/dev/block/mmcblk0p5 bs=1 seek=16384
exit
on recovery select reboot - bootloader
then run command fastboot getvar mid - you should have 0P6B70000 now (hopefully)
Click to expand...
Click to collapse
Firstly I want to thank you with your help I've changed model-id.
Then I installed this firmware: https://www.androidfilehost.com/?fid=24391638059059188
and the screen was like that: http://hizliresim.com/4lZjAL
I've succeeded to open boot menu. Then I tried to install this version: https://www.androidfilehost.com/?fid=24052804347796593
but sd card gave me "wrong zippe image!". When I tried to install with .exe it gave me "Error: 155 Unknown error". Couldn't install with command either. I think something is wrong with firmware or rom. By the way there's a text "OP6B100x" behind my phone. Are we sure about the variant of my phone? I'm not even sure which firmware and rom I should install. I appreciate all your help.
DreamGod said:
Firstly I want to thank you with your help I've changed model-id.
Then I installed this firmware: https://www.androidfilehost.com/?fid=24391638059059188
and the screen was like that: http://hizliresim.com/4lZjAL
I've succeeded to open boot menu. Then I tried to install this version: https://www.androidfilehost.com/?fid=24052804347796593
but sd card gave me "wrong zippe image!". When I tried to install with .exe it gave me "Error: 155 Unknown error". Couldn't install with command either. I think something is wrong with firmware or rom. By the way there's a text "OP6B100x" behind my phone. Are we sure about the variant of my phone? I'm not even sure which firmware and rom I should install. I appreciate all your help.
Click to expand...
Click to collapse
Text "OP6B100x" behind your phone most probably due to change of back cover.
Your getvar on post #1 clearly shown it is Sprint
meid: 99000499006617
product: m8_whl
where the "OP6B100x" should read
meid: 00000000000000
product: m8_ul
After you installed 6.20.651.3_full_firmware.zip, you should run the 6.20.651.3 RUU.exe (you should not get error 155)
but instead, you tried a lower version RUU.zip which require a htc_fastboot to flash it. I don't know what you meant by "sd card gave me "wrong zippe image!"". Was it you tried with external_sd method ?
about the screen that you get .. I don't know for sure .. maybe it's because your ROM version is wrong for the firmware that newly installed ... and maybe (the one that I'm always scare of) .. you previously installed GSM firmware 1.12.401.17 on a CDMA device which may altered some of your system partition tables.
That's why there's a big warning here : http://forum.xda-developers.com/showpost.php?p=51700638&postcount=2
warning! provided only for folks who have changed their mid and realized they shouldnt have,or achieved s off via a java card. DO NOT change a gsm or vzw device to this in attempts to use it on sprint and convert to a sprint device(or vice versa).
Can you post current fastboot getvar all result after you made all these changes ? You may need to reflash the 6.20.651.3 and run 6.20.651.3 RUU.exe after the firmware installed.
ckpv5 said:
Text "OP6B100x" behind your phone most probably due to change of back cover.
Your getvar on post #1 clearly shown it is Sprint
meid: 99000499006617
product: m8_whl
where the "OP6B100x" should read
meid: 00000000000000
product: m8_ul
After you installed 6.20.651.3_full_firmware.zip, you should run the 6.20.651.3 RUU.exe (you should not get error 155)
but instead, you tried a lower version RUU.zip which require a htc_fastboot to flash it. I don't know what you meant by "sd card gave me "wrong zippe image!"". Was it you tried with external_sd method ?
about the screen that you get .. I don't know for sure .. maybe it's because your ROM version is wrong for the firmware that newly installed ... and maybe (the one that I'm always scare of) .. you previously installed GSM firmware 1.12.401.17 on a CDMA device which may altered some of your system partition tables.
That's why there's a big warning here : http://forum.xda-developers.com/showpost.php?p=51700638&postcount=2
warning! provided only for folks who have changed their mid and realized they shouldnt have,or achieved s off via a java card. DO NOT change a gsm or vzw device to this in attempts to use it on sprint and convert to a sprint device(or vice versa).
Can you post current fastboot getvar all result after you made all these changes ? You may need to reflash the 6.20.651.3 and run 6.20.651.3 RUU.exe after the firmware installed.
Click to expand...
Click to collapse
After I installed Marshmallow, I can open phone now. Thank you for your all help.
Oh, thanks
I tried rooting my device and at last I was succesfull but now I want to install the latest ROM but to install that I need to upgrade my hboot and I am not getting how to do that please somebody help me my phone is in S-ON mode and it's an At&t international version phone
sheikharfaz said:
I tried rooting my device and at last I was succesfull but now I want to install the latest ROM but to install that I need to upgrade my hboot and I am not getting how to do that please somebody help me my phone is in S-ON mode and it's an At&t international version phone
Click to expand...
Click to collapse
post the result of fastboot getvar all ( after removing serialno and mei )
sheikharfaz said:
I tried rooting my device and at last I was succesfull but now I want to install the latest ROM but to install that I need to upgrade my hboot and I am not getting how to do that please somebody help me my phone is in S-ON mode and it's an At&t international version phone
Click to expand...
Click to collapse
Your sequence is a bit mixed up. You should have updated firmware (hboot, radio, etc.) before unlocking bootloader. As you'll now have to relock the bootloader in order to update firmware. Then unlock it again, and TWRP again, to install custom ROM.
You also do not need root to flash custom ROMs (just need unlocked bootloader, custom recovery, and right firmware); unless you had another specific reason to root first?
Also, you will want all the updated firmware, not just hboot. As firmware contains a bunch of modules besides hboot, which will not play well with current ROMs (especially WiFi, Bluetooth, as well as radio and others). All the firmware installs in one zip, so it's not hard to do.
However, I agree with the previous post that we need more info on the phone. Fastboot getvar all, and post the results (delete IMEI and serial number before posting).
"At&t international version" is a contradiction. It's either one or the other, it can't be both.
redpoint73 said:
You should have updated firmware (hboot, radio, etc.) before unlocking bootloader. As you'll now have to relock the bootloader in order to update firmware.
Click to expand...
Click to collapse
Here's something I just learned recently (2 or 3 mos ago), although I haven't been able to test it myself since my M8 is S-Off.
When flashing an RUU.zip or signed firmware.zip from extSD instead of from your PC, relocking your bootloader isn't necessary.
Like I said, I haven't confirmed it myself, but the person who told me that I consider a reliable source. He was positive about it with M9, and quite sure it was the same with the M8.
redpoint73 said:
Your sequence is a bit mixed up. You should have updated firmware (hboot, radio, etc.) before unlocking bootloader. As you'll now have to relock the bootloader in order to update firmware. Then unlock it again, and TWRP again, to install custom ROM.
You also do not need root to flash custom ROMs (just need unlocked bootloader, custom recovery, and right firmware); unless you had another specific reason to root first?
Also, you will want all the updated firmware, not just hboot. As firmware contains a bunch of modules besides hboot, which will not play well with current ROMs (especially WiFi, Bluetooth, as well as radio and others). All the firmware installs in one zip, so it's not hard to do.
However, I agree with the previous post that we need more info on the phone. Fastboot getvar all, and post the results (delete IMEI and serial number before posting).
"At&t international version" is a contradiction. It's either one or the other, it can't be both.
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.58.502.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.037s
redpoint73 said:
Your sequence is a bit mixed up. You should have updated firmware (hboot, radio, etc.) before unlocking bootloader. As you'll now have to relock the bootloader in order to update firmware. Then unlock it again, and TWRP again, to install custom ROM.
You also do not need root to flash custom ROMs (just need unlocked bootloader, custom recovery, and right firmware); unless you had another specific reason to root first?
Also, you will want all the updated firmware, not just hboot. As firmware contains a bunch of modules besides hboot, which will not play well with current ROMs (especially WiFi, Bluetooth, as well as radio and others). All the firmware installs in one zip, so it's not hard to do.
However, I agree with the previous post that we need more info on the phone. Fastboot getvar all, and post the results (delete IMEI and serial number before posting).
"At&t international version" is a contradiction. It's either one or the other, it can't be both.
Click to expand...
Click to collapse
Can i get what next i can do?
because i am not able to find the right firmware.Can you help me with that?
sheikharfaz said:
Can i get what next i can do?
because i am not able to find the right firmware.Can you help me with that?
Click to expand...
Click to collapse
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
sheikharfaz said:
(bootloader) version-main: 1.58.502.1
Click to expand...
Click to collapse
As suspected, you need to update all the firmware, not just hboot. Your firmware is still on the original 2014 release of Kitkat. This will cause many issues, even if you updated hboot. For instance, you would find WiFi would be broken on just about every current custom ROM around; due to the WiFi firmware partition on the phone being outdated, and not compatible with the current ROMs.
ahmed has the process outlined well. I would recommend to follow his instructions above.
ahmed.ismael said:
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
Click to expand...
Click to collapse
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
what does this mean ? which image should i flash?
sheikharfaz said:
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
what does this mean ? which image should i flash?
Click to expand...
Click to collapse
just do "fastboot flash zip *whatever you renamed it to*.zip" a second time without rebooting
ahmed.ismael said:
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
Click to expand...
Click to collapse
i am not able to unlock my device back
E:\new\android-sdk-windows\platform-tools>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1826418688 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.133s]
writing 'unlocktoken'...
FAILED (remote: unlock token check failed)
finished. total time: 0.144s
ahmed.ismael said:
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
Click to expand...
Click to collapse
stuck in bootloop after locking the device
i accidently mistyped fastboot reboot instead of fastboot reboot-bootloader
what shall i do now
xunholyx said:
just do "fastboot flash zip *whatever you renamed it to*.zip" a second time without rebooting
Click to expand...
Click to collapse
stuck in bootloop
what can i do?please help
ahmed.ismael said:
remove serialno from the getvar result in your post above
i don't know what you want
you need the latest firmware to flash a custom rom or you need to flash the latest stock rom ( by using RUU ) ???
in all cases you need to flash the latest firmware first 6.20.502.5 ( it's the latest firmware for your AT&T device variant )
6.20.502.5 is marshmallow and it's the latest official OS for this device
note :- flashing the signed firmware will wipe your internal storage so make sure to backup your files
flash firmware
1-download this signed firmware https://mega.nz/#!XV5EjYhS!gNN_rAYovaMQpaeP2OSdkfYAIEAmv6VnB-QlZ1VadMU ( rename it to something short and easy if you like )
2- open a cmd window in the folder where the firmware located
3- relock the bootloader ( if it's unlocked ) by this commands
fastboot oem lock
fastboot reboot-bootloader
3- now start flashing the firmware using this commands and replace firmwarename with the actual firmware name
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
if you see FAILED (remote: 90 hboot pre-update! please flush image again immediately)
then repeat the flashing command again
fastboot flash zip firmwarename.zip
after it complete type
fastboot reboot-bootloader
flash custom rom
now you have the latest firmware if you want to flash a custom rom unlock the bootloader and flash twrp then flash the desired rom
flash stock rom using RUU.exe
if you want the latest stock rom RUU.exe it's available on htc website here http://www.htc.com/us/support/htc-one-m8-att/news/
direst link for the RUU http://dl3.htc.com.s3.amazonaws.com...70_ATT_MR_Cingular_US_6.20.502.5_combined.exe
after flash the firmware and do all the above commands run the RUU as a normal application and follow the setup wizard
Click to expand...
Click to collapse
please send me next steps too.
sheikharfaz said:
stuck in bootloop
what can i do?please help
Click to expand...
Click to collapse
You flashed firmware first?
xunholyx said:
You flashed firmware first?
Click to expand...
Click to collapse
yes,now how do i come out of this bootloop ,there is nothing on screen except that htc logo
Okay. How long did you wait for it to boot up? I can take up to 20 mins sometimes. crazy I know
xunholyx said:
Okay. How long did you wait for it to boot up? I can take up to 20 mins sometimes. crazy I know
Click to expand...
Click to collapse
the battery got drained .so now i am able to get into bootloader .can i please get how to unloack bootloader .i have tried fastboot oem unlock and even
fastboot flash unlocktoken Unlock_code.bin
please help
sheikharfaz said:
the battery got drained .so now i am able to get into bootloader .can i please get how to unloack bootloader .i have tried fastboot oem unlock and even
fastboot flash unlocktoken Unlock_code.bin
please help
Click to expand...
Click to collapse
request another unlock_code
follow the steps to unlock the bootloader again on the hcdev website http://www.htcdev.com/bootloader/
sheikharfaz said:
can i please get how to unloack bootloader .i have tried fastboot oem unlock please help
Click to expand...
Click to collapse
This command doesn't work on the M8, it's not even worth trying. The whole point of the HTCDev.com bootloader unlock process, is due to the fact that HTC forbids unlocking the bootloader with that command. It only applies to certain devices.
You need to use the bin code command. If it doesn't work, just request a new bin code, like ahmed suggested.