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
Related
hello,
i currently have installed slimbean 3.1.0 (4.1.2) on my hox
now i want to upgrade to 4.2.2 (http://forum.xda-developers.com/show....php?t=2172020) but when i flash the rom i alway get an error.
assert failed : getprop("ro.bootloader") Status 7 and something with hboot.
my hboot version is 1.12 and my cid is HTC__102
how can i fix this error?
thanks in advance,
Update the hboot first
What comes out :
Fastboot getvar version-main
Mr Hofs said:
Update the hboot first
What comes out :
Fastboot getvar version-main
Click to expand...
Click to collapse
when i run the command i get the following: version-main: 2.17.401.2
can i use method 3 from this tutorial? http://forum.xda-developers.com/showthread.php?t=1660807
where can i download the right files? i'm from europe/austria.
the last thing: "Run the RUU exe file (of your CID) in fastboot mode"
does this mean i need to open the exe when my phone is connected in fastboot usb?
thanks in advance,
BigAndroidFan said:
when i run the command i get the following: version-main: 2.17.401.2
can i use method 3 from this tutorial? http://forum.xda-developers.com/showthread.php?t=1660807
where can i download the right files? i'm from europe/austria.
the last thing: "Run the RUU exe file (of your CID) in fastboot mode"
does this mean i need to open the exe when my phone is connected in fastboot usb?
thanks in advance,
Click to expand...
Click to collapse
Download this RUU :http://bugsylawson.com/files/file/1...12-radio-2120413520-release-274900-signedexe/
Lock your bootloader using following command:
Code:
fastboot oem lock
Then run the ruu with admin privileges. It will take your phone to full stock! Then you can update OTA via Software Updates to the latest firmware and then you can flash any 4.2.2 roms out here!
vin4yak said:
Download this RUU
Lock your bootloader using following command:
Code:
fastboot oem lock
Then run the ruu with admin privileges. It will take your phone to full stock! Then you can update OTA via Software Updates to the latest firmware and then you can flash any 4.2.2 roms out here!
Click to expand...
Click to collapse
and i dont need to extract and flash the boot.img and signed_recovery.img from the exe before i lock the bootloader?
Nope
thanks guys, it worked!
Great!! Enjoy JB!
Case closed ! :d
Hi, I'm trying to install cm10.1-RC5 from Arch Linux. I've wiped and factory reset and flashed the boot.img. I don't have s-off.
When I try to install the .zip in ClockworkMod 5.8.4.0 I get errors indicating that my bootloader isn't a compatible version. For example:
assert failed: getprop("ro.bootloader") == "1.31.0000"
E:Error in /sdcard/cm-10.1.0-RC5-endeavoru.zip
(Status 7)
Installation aborted.
I gather that this means my hboot or firmware needs an update. I've found this thread which seems relevant:
http://forum.xda-developers.com/showthread.php?t=2241419
I ran "fastboot oem readcid" and got this:
...
(bootloader) DEBUG: cid: VODAP021
OKAY [ 4.075s]
finished. total time: 4.075s
So I guess this means I need Vodaphone specific firmware? Where can I access this?
Or am I on the wrong track?
Post the result of fastboot getvar version-main..
This is a cmd fastboot command (windows)... No idea what's the command for Linux.. Might be something similar..
This way we can make sure which firmware you have...
-Sent from my IceCold One X!
vin4yak said:
Post the result of fastboot getvar version-main..
This is a cmd fastboot command (windows)... No idea what's the command for Linux.. Might be something similar..
This way we can make sure which firmware you have...
-Sent from my IceCold One X!
Click to expand...
Click to collapse
Thanks for the quick reply, here's the output:
version-main: 1.29.862.11
finished. total time: 4.069s
I've located this thread:
http://forum.xda-developers.com/showthread.php?t=1957376&highlight=upgrade+firmware+linux
This pointed me to .zip containing hboot 1.36.
I tried following these instructions:
http://sadevil.org/blog/2012/12/23/manually-flashing-an-ota-update/
Unfortunately the directories the tutorial references are different to the one in my .zip.
Now there are 2 ways you can upgrade your device's hboot
1: Returning to stock with a ruu and then updating to jellybean hboot with ota update.
2. Flashing the firmware zip and then installing a custom rom.
For running a ruu you will need access to a windows pc since it's an exe file : http://bugsylawson.com/files/file/1...11-radio-1120410514-release-260561-signedexe/
If you want to upgrade your firmware by flashing... Here's the firmware upgrade for your cid : http://goo.gl/yAa0G
Download the firmware and rename it to firmware.zip and then put it in the fastboot folder..
Steps:
1. Relock bootloader : fastboot oem lock
2. Reboot to ruu : fastboot oem rebootRUU
It will take you to a black htc screen... Wait for a few seconds for the screen to settle down and then flash the firmware :
Fastboot flash zip firmware.zip
You might need to flash the firmware twice if you get an error the first time! Its quite normal! After successfully flashing the firmware, you need to unlock the Bootloader, flash a custom recovery and then flash the custom rom!
PS: Again, the commands are for fastboot cmd (windows).. Linux might be a little different..
-Sent from my IceCold One X!
vin4yak said:
Now there are 2 ways you can upgrade your device's hboot
1: Returning to stock with a ruu and then updating to jellybean hboot with ota update.
2. Flashing the firmware zip and then installing a custom rom.
For running a ruu you will need access to a windows pc since it's an exe file : http://bugsylawson.com/files/file/1...11-radio-1120410514-release-260561-signedexe/
If you want to upgrade your firmware by flashing... Here's the firmware upgrade for your cid : http://goo.gl/yAa0G
Download the firmware and rename it to firmware.zip and then put it in the fastboot folder..
Steps:
1. Relock bootloader : fastboot oem lock
2. Reboot to ruu : fastboot oem rebootRUU
It will take you to a black htc screen... Wait for a few seconds for the screen to settle down and then flash the firmware :
Fastboot flash zip firmware.zip
You might need to flash the firmware twice if you get an error the first time! Its quite normal! After successfully flashing the firmware, you need to unlock the Bootloader, flash a custom recovery and then flash the custom rom!
PS: Again, the commands are for fastboot cmd (windows).. Linux might be a little different..
-Sent from my IceCold One X!
Click to expand...
Click to collapse
Golden gold you are sir/madam! Got CM10.1 running like a beast!
Thankyou kindly.
That's Great! Enjoy cm10! :good:
-Sent from my IceCold One X!
firmware for htc_38 for hboot update
I have HTC One X, currently i m at hboot 1.72 and CWR 6.0.4.7. I want to update my hboot for that i need firmware for my device whose CID is htc_38. I have already gone through xda page of "collection of firmware" to search for my device's firmware but i didnt get it there. plzzzzzzz help me out here.
abhinav625 said:
I have HTC One X, currently i m at hboot 1.72 and CWR 6.0.4.7. I want to update my hboot for that i need firmware for my device whose CID is htc_38. I have already gone through xda page of "collection of firmware" to search for my device's firmware but i didnt get it there. plzzzzzzz help me out here.
Click to expand...
Click to collapse
You are with the latest firmware!!!!
Hi,
So after fighting for hours, I managed to successfully use fastboot flash zip command to RUU the google play edition rom to my phone. However, the tutorial I followed didn't say I needed to match my CID and MID, so now I am stuck at the GPE fastboot bootloader. I can flash a custom recovery (I put TWRP on after the RUU was finished). However, since my phone is stuck at fastboot, I can't transfer any files to it using adb.
What I have: Fastboot, and TWRP recovery. Booting normally brings up Fastboot. Booting to recovery brings up TWRP.
My goal: Change my CID and MID so I can properly RUU the GPE rom to my phone. I think I can change the CID from fastboot but I don't think I can change MID from there.
What do you think? Am I going in the right direction? Did I make a wrong assumption?
In fastboot, you should be able to change you CID running this command:
Code:
fastboot oem writecid GOOGL001
If your MID doesn't start with 0P6B, you need to open the RUU file with a zip explorer program and modify the android-info.txt file inside and add your MID to the list. Follow this guide: http://forum.xda-developers.com/showthread.php?t=2708589
hellhawk741 said:
In fastboot, you should be able to change you CID running this command:
Code:
fastboot oem writecid GOOGL001
If your MID doesn't start with 0P6B, you need to open the RUU file with a zip explorer program and modify the android-info.txt file inside and add your MID to the list. Follow this guide: http://forum.xda-developers.com/showthread.php?t=2708589
Click to expand...
Click to collapse
Well I changed my CID and MID according to the thread (I edited the android-info.txt). However when I ran fastboot flash zip it failed with
FAILED (remote: not allowed)
Any ideas? It worked before, which confuses me as to why it's not working now.
EDIT: Nevermind I am an idiot. FAILED (remote: not allowed) means you need to reboot into RUU mode by using fastboot oem rebootRUU. However now I am back to where I started.
I successfully RUUed the Google Play rom, but now my phone only boots to the bootloader and fastboot.
I'm confused by flashing the RUU, if you have an ext SD card you can copy the image there rename it, boot and it will install itself. There is a rooted image available in the Android Development forum by GrafxNYC. I followed his instructions there and it worked perfectly.
Assuming the RUU file is not an exe file, move it to your SD card and rename it to match your MID exactly and reboot into bootloader. It should flash without a problem.
Ive been wrestling with this since last Saturday but I've finally got the GPE rom working. I couldn't tell you what I did, because I've gotten sidetracked and backtracked a bazillion times. I need to make a new thread though, the GPE rom is *extremely* unstable and crashes very frequently
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
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.