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.
Related
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
Can someone just confirm that this is the correct process for updating the HBOOT on my HTC One X from 0.95 to 1.3x (I'm unsure about step 5 & 6)
1. Determine the CID of my phone using
Code:
fastboot oem readcid
The phone reports
Code:
cid: HTC__001
which according to this means it is a HTC-WWE.
2. Download the latest HTC One X ROM from HTCdev which is endeavoru-jb-crc-3.1.10-e8d900a.zip
3. Copy the ROM to the phone
4. Relock the bootloader using
Code:
fastboot oem lock
5. Go into fastboot mode and type
Code:
fastboot oem rebootRUU
6. Flash the new firmware using
Code:
fastboot flash zip endeavoru-jb-crc-3.1.10-e8d900a.zip
On first time running the command will report FAILED, don't panic and just run the command again.
7. Reunlock the bootloader via HTCDev.
8. Flash a custom recovery using
Code:
fastboot flash recovery recovery.img
9. Download the CM10.1 ROM & extract the boot.img from the zip
10. Boot into recovery & install the ROM
11. Install the Google Addon
12. Boot into boot loader using
Code:
adb reboot bootloader
and use fastboot to flash the boot.img
Code:
fastboot flash boot boot.img
.
13. Use
Code:
fastboot erase cache
14. Reboot and enjoy
Warning
At 2 step, you have to donwload the zip from here and not the source of kernel!!!
And in 6 step you have to use: "fastboot flash zip "name_of_zip.zip"
Don't forget that you will have to unlock your bootloader at the end of all this (assuming you want to do that) and this will probably erase all your data again so back it up, including the SD card.
There is a firmware flashing tool in the development section that makes it easy!
I've found a post here which describes the procedure step by step.
UPDATE HBOOT FOR JB
1. You need your Unlock_bin from htcdev.com to re-unlock ur bootloader so please before u
proceed make sure u have this. Then reboot bootloader, and fire up CMD on your PC (start ->
execute -> cmd) and cd to ur fastboot directory
2. fastboot getvar cid or if it fails fastboot oem readcid will give u the cid of your phone
3. fastboot getvar version-main will give u ur actually RUU version
4. Now we have software version and CID. Time to get our RUU ->
http://androidfiles.org/ruu/?dir=Endeavor
5. Download the RUU for ur Phone (u need a higher or equal version then getvar version-main
reported
6. Place the .exe on ur PC and now we will extract the .zip (the rom.zip what is known as the
RUU) out of the .exe
7. Follow this tutorial: http://www.freeyourandroid.com/guide/extract-rom-from-ruu to get
the .zip out of the .exe
8. rename the .zip to whatever u like and place it in the fastboot folder of ur pc
9. boot phone in bootloader
10. lock bootloader with fastboot oem lock
11. reboot bootloader, and fire up CMD on your PC (start -> execute -> cmd) and cd to ur
fastboot directory.
12. bring phone into RUU mode: fastboot oem rebootRUU
13. fastboot flash zip rom.zip (u extracted and placed it before in ur fastboot folder)
14. In most cases this fails the first time. So redo fastboot flash zip rom.zip (this step costed me
2 hours because i didn´t know that)
15. boot into system when finished and if the version of the RUU isn´t allready on Jellybean
make all necessary OTA updates until u reach latest hboot (1.36, 1.39)
16. place the Unlock.bin which u got long time ago from htcdev.com (and hopefully u haven´t
lost it) in fastboot folder
17. reboot into bootloader
18. fastboot flash unlocktoken Unlock_code.bin
19. Ur bootloader is unlocked again
20. Congratz... u sucessfully updated ur hboot
Click to expand...
Click to collapse
You can do as you described using the file I linked...
without use a ruu
Guich said:
You can do as you described using the file I linked...
without use a ruu
Click to expand...
Click to collapse
Does that mean if you flash the exact matching cid file from your link you don't have to follow the steps above? re relocking the phone and unlocking etc?
Why the heck are you trying to flash the kernel source in fastboot? There are instructions everywhere and in none of them say that you must go near kernel source
If you just want to update Hboot:
1. relock bootloader 'fastboot oem lock'
2. check cid: fastboot getvar cidnum
3. download firmware.zip from here: http://forum.xda-developers.com/showthread.php?t=1957376
4. in fastboot mode, type: fastboot oem rebootRUU
5. flash the firmware.zip using: fastboot flash zip firmware.zip
6. Reunlock your bootloader: fastboot flash unlocktoken unlock_code.bin
7. reflash custom recovery: fastboot flash recovery <name of recovery.img>
If you want to install ROM after:
8. flash boot.img of ROM
9. go to recovery and flash ROM
10. done
det66 said:
Does that mean if you flash the exact matching cid file from your link you don't have to follow the steps above? re relocking the phone and unlocking etc?
Click to expand...
Click to collapse
No.
You have to use this procedure, but whit the firmware.zip that you can found at the link i linked, and not whit kernel source.
If you see the OP, you can see that he want upgrade his hboot with kernel source, and he's wrong.
You have to use the firmware.zip that you can found at the link that i have linked.
All the rest of procedure is right
Managed it gents . Now on HBoot 1.39.0000 thank you very much for all your help. Really appreciated:good::good:
This method is to take your device back to full stock for whatever reason you may need.
This will make your phone s-on and locked again without tamper notification.
Must have ADB drivers installed. If you s-off then you should have these.
These procedures will EASILY BRICK you device if not done exactly. Copy and paste each command exactly. Double and triple check your entries to ensure you typed or copied them exactly.
1. Change CID back to stock.
Code:
reboot into fastboot
fastboot oem writecid CWS__001
^^This command is important. Make sure you type 8 characters in CWS__001
2. Remove tampered flag and relock.
Code:
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
3. Flash RUU from here.
4. Turn back to s-on. Reboot to fastboot
Code:
fastboot oem writesecureflag 3
5. Check in fastboot you are s-on and locked
jmztaylor said:
This method is to take your device back to full stock for whatever reason you may need.
This will make your phone s-on and locked again without tamper notification.
Must have ADB drivers installed. If you s-off then you should have these.
These procedures will EASILY BRICK you device if not done exactly. Copy and paste each command exactly. Double and triple check your entries to ensure you typed or copied them exactly.
1. Change CID back to stock.
Code:
adb shell
su
echo -ne "CWS__001" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
2. Remove tampered flag and relock.
Code:
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
3. Flash RUU from here.
4. Turn back to s-on. Reboot to fastboot
Code:
fastboot oem writesecureflag 3
5. Check in fastboot you are s-on and locked
Click to expand...
Click to collapse
another way to change cid while s off is to
Code:
fastboot oem writecid CWS__001
there is also a zip to relock:
http://androidforums.com/droid-dna-all-things-root/691712-how-reset-your-lock-status-flag.html
be aware it has not been tested on the one vx,since i dont have this device. id dump mmcblk0p3 and check the lock flag location if your interested in pursuing this option. if it works,it makes things pretty noob proof:
-fastboot oem writecid xxxxxxxx
-flash lock zip
-run ruu
-fastboot oem writesecureflag 3
no copy/pasting commands that can brick your device if typed or copied wrong
Stock RUU no longer available at link
scotty1223 said:
there is also a zip to relock:
http://androidforums.com/droid-dna-all-things-root/691712-how-reset-your-lock-status-flag.html
be aware it has not been tested on the one vx,since i dont have this device. id dump mmcblk0p3 and check the lock flag location if your interested in pursuing this option. if it works,it makes things pretty noob proof:
-fastboot oem writecid xxxxxxxx
-flash lock zip
-run ruu
-fastboot oem writesecureflag 3
no copy/pasting commands that can brick your device if typed or copied wrong
Click to expand...
Click to collapse
noobsaibot34 said:
Stock RUU no longer available at link
Click to expand...
Click to collapse
With a bit of searching im sure you can find stock ruus for your device. I have faith
The important part of my post and the link I posted was the zip file to lock your bootloader.
Sent from my HTC PG09410 using Tapatalk 2
Tried to install latest RUU file and failed. Now phone is stuck on htc logo with black screen only when plugged in pc. Also when unplugged, goes to bootload with no options and only shows RUU.
Phone is unlocked and s-off. Had Bootloader installed and now wont show
Need help ASAP
Thanks
gmdiesel05 said:
Tried to install latest RUU file and failed. Now phone is stuck on htc logo with black screen only when plugged in pc. Also when unplugged, goes to bootload with no options and only shows RUU.
Phone is unlocked and s-off. Had Bootloader installed and now wont show
Need help ASAP
Thanks
Click to expand...
Click to collapse
did you flash the ruu.zip 2 times .. the first flash only updates the hboot
clsA said:
did you flash the ruu.zip 2 times .. the first flash only updates the hboot
Click to expand...
Click to collapse
yes the second time it said device not found! In cmd window, i type adb devices and none there
This is what happens, and hangs there
C:\Users\Desktop\platform-tools>fastboot oem rebootRUU
< waiting for device >
...
(bootloader) Start Verify: 0
OKAY [ 0.072s]
finished. total time: 0.073s
C:\Users\Cedrik\Desktop\platform-tools>fastboot flash zip RUU-HTC_One_M8_GPE_5.0
.1-3.11.1700.5.zip
gmdiesel05 said:
yes the second time it said device not found! In cmd window, i type adb devices and none there
Click to expand...
Click to collapse
it has nothing to do with adb you phone is in fastboot RUU mode
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
what file are you trying to flash ?
clsA said:
it has nothing to do with adb you phone is in fastboot RUU mode
fastboot oem rebootRUU
fastboot flash zip ruu.zip
fastboot flash zip ruu.zip
fastboot reboot
what file are you trying to flash ?
Click to expand...
Click to collapse
Im trying to flash RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
latest non rooted GPE
Seems to hang. wont let me type in cmd
gmdiesel05 said:
Im trying to flash RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
latest non rooted GPE
Seems to hang. now i cant flash a 2nd time
Click to expand...
Click to collapse
are you s-off ? is your phone a GSM M8 ?
Did you try the other method, just renaming the RUU to 0p6bimg.zip (<a 0 (Zero) not a capital o (O), naturally...)
What error do you get when the flashing of the RUU fails?
Like mentioned by clsA said, adb devices won't work in fastboot mode, it should be "fastboot devices" to check if it's connected
---------- Post added at 06:20 AM ---------- Previous post was at 06:18 AM ----------
gmdiesel05 said:
Im trying to flash RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
latest non rooted GPE
Seems to hang. wont let me type in cmd
Click to expand...
Click to collapse
You changed CID and MID I take it?
CID - GOOGL001
MID - 0P6B17000
Would have helped a bit if we had an idea what the error was.
clsA said:
are you s-off ? is your phone a GSM M8 ?
Click to expand...
Click to collapse
sure is in s-off. and it is a GSM. Also its in GOOGL001 CID
I made sure I followed instruction properly so I dont screw up.
clsA said:
are you s-off ? is your phone a GSM M8 ?
Click to expand...
Click to collapse
Yeah he said his phone is S-OFF in OP
Phone is unlocked and s-off. Had Bootloader installed and now wont show
Click to expand...
Click to collapse
gmdiesel05 said:
sure is in s-off. and it is a GSM. Also its in GOOGL001 CID
I made sure I followed instruction properly so I dont screw up.
Click to expand...
Click to collapse
just use the fastboot flash zip ruu.zip command again
clsA said:
just use the fastboot flash zip ruu.zip command again
Click to expand...
Click to collapse
I just closed cmd window and restared. redid fastboot flash zip ruu.zip and seems to hang still
hope i didnt screw this up....
gmdiesel05 said:
I just closed cmd window and restared. redid fastboot flash zip ruu.zip and seems to hang still
hope i didnt screw this up....
Click to expand...
Click to collapse
try and unplug the phone from the pc and hold volume up + power for 10 seconds
when the phone reboots try the ruu again .. if the bootloader says RUU in red don't do the fastboot oem rebootRUU command just go straight to flashing
The RUU flashes very slow are you waiting long enough ?
clsA said:
try and unplug the phone from the pc and hold volume up + power for 10 seconds
when the phone reboots try the ruu again .. if the bootloader says RUU in red don't do the fastboot oem rebootRUU command just go straight to flashing
The RUU flashes very slow are you waiting long enough ?
Click to expand...
Click to collapse
OK so i started from scratch. closed cmd window, unplugged phone, replugged and opened cmd window.
fastboot devices. shows device
fastboot oem rebootRUU. it reboots and goes to htc screen
fastboot flash zip 0p6bimg.zip. sorry renamed file. after i pressed enter, it opened another window and sent zip file. then it closed and now seems to not do anything.
maybe im not waiting long enough?
ok heres the latest
FAILED <command write failed <No such device or address>>
gmdiesel05 said:
OK so i started from scratch. closed cmd window, unplugged phone, replugged and opened cmd window.
fastboot devices. shows device
fastboot oem rebootRUU. it reboots and goes to htc screen
fastboot flash zip 0p6bimg.zip. sorry renamed file. after i pressed enter, it opened another window and sent zip file. then it closed and now seems to not do anything. Sorry you lost me here
maybe im not waiting long enough?
Click to expand...
Click to collapse
you have the file renamed just copy it to your Ext - sdcard and let the bootloader flash it
don't forget to delete or rename it on the sdcard before you reboot again or it will flash it again
ok heres the latest
FAILED <command write failed <No such device or address>>
gmdiesel05 said:
OK so i started from scratch. closed cmd window, unplugged phone, replugged and opened cmd window.
fastboot devices. shows device
fastboot oem rebootRUU. it reboots and goes to htc screen
fastboot flash zip 0p6bimg.zip. sorry renamed file. after i pressed enter, it opened another window and sent zip file. then it closed and now seems to not do anything.
maybe im not waiting long enough?
Click to expand...
Click to collapse
Yeah this pretty much tells me you didn't properly read the guide to converting your device to GPE. When I mentioned "the 0p6bimg.zip" method I kind of figured you'd know to place it on SD Card and reboot into bootloader so that the bootloader can pick up the .zip file and flash it from there. Flashing in from RUU sort of gave it away there
Method 1
No computer required. Everything else still required. s-off, super CID/gpe CID etc..
1. Rename the RUU zip file 0p6bimg.zip (if your hboot is looking for a different name then rename it to whatever it's looking for)
2. Place the zip on your external SD card
3. Power off your phone
4. Boot into Hboot (hold down vol down as you power on the device)
5. it will load the zip and ask you if you want to proceed
6. Say yes
7. Wait
8. Profit
Click to expand...
Click to collapse
Didn't say anything about flashing it in RUU mode.
BerndM14 said:
Yeah this pretty much tells me you didn't properly read the guide to converting your device to GPE. When I mentioned "the 0p6bimg.zip" method I kind of figured you'd know to place it on SD Card and reboot into bootloader so that the bootloader can pick up the .zip file and flash it from there. Flashing in from RUU sort of gave it away there
Didn't say anything about flashing it in RUU mode.
Click to expand...
Click to collapse
i used
Method 2
ADB/FastBoot Method
Code:
adb reboot bootloader
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
you will the following message:
Code:
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
Just run the same command again:
Code:
fastboot flash zip RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5.zip
Code:
fastboot reboot
I bought an M8 last year, locked to vodafone UK (CID VODAP001). I have since unlocked through HTC-DEV, S-OFFed using sunshine, converted to GPE for a while, and am now using it on a developer CID (BS_US002) entirely stock in order to get the OTA lollipop update straight from HTC. I obviously have the tampered message and unlocked bootloader, I am looking to return it to stock as much as possible (apart from S-ON). I have been looking at this thread but am not sure if it will work. I was looking to keep stock lollisense. My question is do I need to change my CID/MID back to the original ones or can I leave them as is and remove the tampered message etc.
My guide will work but there are bits that aren't needed now we have the RUU. I'll post in the morning with proper steps as I'm my phone at the mo and links are a PITA on here!
EddyOS said:
My guide will work but there are bits that aren't needed now we have the RUU. I'll post in the morning with proper steps as I'm my phone at the mo and links are a PITA on here!
Click to expand...
Click to collapse
Much appreciated! I'll check back tomorrow.
Right, lets try and get this sorted. As you're S-OFF it'll make things a LOT easier!
First, download the following and put them in 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 (you can leave the name as it is)
1. Personally, I'd get the tamper flag and the locking done first SO root the phone if you haven't already and then use the guides by @scotty1223 - Tamper Flag & Locking the bootloader. You can also, apparently, do the commands in TWRP as the recovery already has root access so if you'd prefer flash the latest TWRP found HERE (fastboot flash recovery recovery.img) and then connect the phone when in TWRP and do the commands as highlighted by the guides by Scotty. Also, if you changed the MID at all, change that back using Scotty's guide HERE
2. Once you've reset the tamper flag and locked the phone (but still S-OFF), change the CID to Super CID - fastboot oem writecid 11111111
3. Reboot the bootloader to confirm it's done - fastboot reboot-bootloader
4. Now we should be in a position to flash the EU RUU file SO reboot the phone into RUU mode - fastboot oem rebootRUU
5. Once in RUU mode, we now have to use the HTC fastboot to flash the ZIP - htc_fastboot flash zip ruu.zip
6. The ZIP will take a few passes to complete and it'll reboot the phone accordingly
7. Once complete, reboot to the bootloader again - fastboot reboot-bootloader
8. Chance the CID to the unbranded EU one - fastboot oem writecid HTC__001
9. Again, reboot the bootloader to make sure it's taken - fastboot reboot-bootloader
10. Once confirmed, boot into the stock recovery and do a factory reset (optional but, personally, I'd do it)
11. Reboot
EddyOS said:
Right, lets try and get this sorted. As you're S-OFF it'll make things a LOT easier!
First, download the following and put them in 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 (you can leave the name as it is)
1. Personally, I'd get the tamper flag and the locking done first SO root the phone if you haven't already and then use the guides by @scotty1223 - Tamper Flag & Locking the bootloader. You can also, apparently, do the commands in TWRP as the recovery already has root access so if you'd prefer flash the latest TWRP found HERE (fastboot flash recovery recovery.img) and then connect the phone when in TWRP and do the commands as highlighted by the guides by Scotty. Also, if you changed the MID at all, change that back using Scotty's guide HERE
2. Once you've reset the tamper flag and locked the phone (but still S-OFF), change the CID to Super CID - fastboot oem writecid 11111111
3. Reboot the bootloader to confirm it's done - fastboot reboot-bootloader
4. Now we should be in a position to flash the EU RUU file SO reboot the phone into RUU mode - fastboot oem rebootRUU
5. Once in RUU mode, we now have to use the HTC fastboot to flash the ZIP - htc_fastboot flash zip ruu.zip
6. The ZIP will take a few passes to complete and it'll reboot the phone accordingly
7. Once complete, reboot to the bootloader again - fastboot reboot-bootloader
8. Chance the CID to the unbranded EU one - fastboot oem writecid HTC__001
9. Again, reboot the bootloader to make sure it's taken - fastboot reboot-bootloader
10. Once confirmed, boot into the stock recovery and do a factory reset (optional but, personally, I'd do it)
11. Reboot
Click to expand...
Click to collapse
Is there any way I can use regular fastboot instead of htc_fastboot? I'm on a mac..
Nope, the Google one doesn't work for some reason. HOWEVER, apparently there is an HTC version on the HTC Dev site, which might very well work...
https://www.htcdev.com/process/legal_fastboot_mac
Failing that you'll need to use a Windows PC
EddyOS said:
Nope, the Google one doesn't work for some reason. HOWEVER, apparently there is an HTC version on the HTC Dev site, which might very well work...
link
Failing that you'll need to use a Windows PC
Click to expand...
Click to collapse
I was getting failures with remote:32 header error when usng that fastboot, managed to get on a windows PC and all sorted now. Thanks for your help!
No worries, glad I could help. I take it all the locking/tamper removing went OK as well?
EddyOS said:
No worries, glad I could help. I take it all the locking/tamper removing went OK as well?
Click to expand...
Click to collapse
Everything went to plan, all back to stock apart from S-OFF now
EddyOS said:
Right, lets try and get this sorted. As you're S-OFF it'll make things a LOT easier!
First, download the following and put them in 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 (you can leave the name as it is)
1. Personally, I'd get the tamper flag and the locking done first SO root the phone if you haven't already and then use the guides by @scotty1223 - Tamper Flag & Locking the bootloader. You can also, apparently, do the commands in TWRP as the recovery already has root access so if you'd prefer flash the latest TWRP found HERE (fastboot flash recovery recovery.img) and then connect the phone when in TWRP and do the commands as highlighted by the guides by Scotty. Also, if you changed the MID at all, change that back using Scotty's guide HERE
2. Once you've reset the tamper flag and locked the phone (but still S-OFF), change the CID to Super CID - fastboot oem writecid 11111111
3. Reboot the bootloader to confirm it's done - fastboot reboot-bootloader
4. Now we should be in a position to flash the EU RUU file SO reboot the phone into RUU mode - fastboot oem rebootRUU
5. Once in RUU mode, we now have to use the HTC fastboot to flash the ZIP - htc_fastboot flash zip ruu.zip
6. The ZIP will take a few passes to complete and it'll reboot the phone accordingly
7. Once complete, reboot to the bootloader again - fastboot reboot-bootloader
8. Chance the CID to the unbranded EU one - fastboot oem writecid HTC__001
9. Again, reboot the bootloader to make sure it's taken - fastboot reboot-bootloader
10. Once confirmed, boot into the stock recovery and do a factory reset (optional but, personally, I'd do it)
11. Reboot
Click to expand...
Click to collapse
Hey, just did all points but how to go back to s-on and get ride of "test device" info?
EDIT: nvm, problem solved by myself. Thanks for the tutorial