Related
I have searching for a solution here for last 2 days but couldn't find one
Problem :
My one x is displaying black screen with silver "htc" logo. It does not boot in bootloader or recovery. Although fastboot commands are still running on this blackscreen.
What I did
I successfully unlocked my one x and installed paranoiandroid but when I started using it my phone began to hang and the touch was disable.
Then I read the post for getting bavk to stock using RUU. I followed these step.
- checked my phone version using "fastboot getvar version-main"
- downloaded "RUU_ENDEAVOR_U_ICS_40_S_hTC_Asia_WWE_2.17.707.3_Radio_2.1204.135.20_release_278245_signed"
- unlocked the bootloader "fastboot oem lock"
- Ran the RUU exe file.
Now the RUU is giving an error the RUU is not correct but it is the same version which I get from "fastboot getvar version-main" and now my phone is only displaying the black screen with sliver "htc" logo.
I shall be grateful if someone can provide a solution to my problem. Thank you.
try 'fastboot reboot-bootloader' or 'fastboot oem reboot-bootloader' (forgot which one).
Then try find a correct RUU to flash or just flash a custom ROM.
tomascus said:
try 'fastboot reboot-bootloader' or 'fastboot oem reboot-bootloader' (forgot which one).
Then try find a correct RUU to flash or just flash a custom ROM.
Click to expand...
Click to collapse
Thank you for the reply.
I have tried it. The command executes but the phone again boots in blackscreen with silver "htc" logo. It is not going in bootloader.
If you re-run the command fastboot getvar version-main, will it give you the same no. 2.17.707.3 ?
ckpv5 said:
If you re-run the command fastboot getvar version-main, will it give you the same no. 2.17.707.3 ?
Click to expand...
Click to collapse
Yes it is giving the same version and I have downloaded the exact RUU version still RUU fails to complete its setup stating "not correct RUU, download the correct file"
I was searching for a solution and found that RUU setup also works if the RUU version is an updated version with same region e.g x.xx.707.x.
I have downloaded RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_WWE_3.14.707.24_Radio_5.1204.162.29_release_296434_signed. Should I try this?
sherwaniusman said:
I was searching for a solution and found that RUU setup also works if the RUU version is an updated version with same region e.g x.xx.707.x.
I have downloaded RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_WWE_3.14.707.24_Radio_5.1204.162.29_release_296434_signed. Should I try this?
Click to expand...
Click to collapse
Good luck! :laugh:
tomascus said:
Good luck! :laugh:
Click to expand...
Click to collapse
No luck same error occurred.
Mind if i asking? Do u just run the RUU or u flash boot_signed.img etc etc first?
Sent from my HTC One X using xda premium
serwan said:
Mind if i asking? Do u just run the RUU or u flash boot_signed.img etc etc first?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I unlocked the bootloader and ran RUU.exe file from my computer. The setup begins and error occurs while flashing the rom image
I think you should reinstall the HBoot manually...
What CID do you have?
Is your Bootloader "relocked" ??
andyoso said:
I think you should reinstall the HBoot manually...
What CID do you have?
Click to expand...
Click to collapse
How to reinstall the Hboot?
sherwaniusman said:
I unlocked the bootloader and ran RUU.exe file from my computer. The setup begins and error occurs while flashing the rom image
Click to expand...
Click to collapse
U need to RELOCKED your bootloader.
Please google how to extract boot_signed.img , recovery_signed.img and rom.zip from RUU. After u've extract those, flash boot_signed and recovery_signed first. Then boot to recovery, flash your rom.zip and only after that u run the RUU. Give it a try.
Sent from my HTC One X using xda premium
sherwaniusman said:
How to reinstall the Hboot?
Click to expand...
Click to collapse
You should download it before...if you give me your CID pass you the correct link to download the correct "firmware.zip" that contains the HBoot.
After the downloading you should type this command twice:
fastboot flash zip firmware.zip
Click to expand...
Click to collapse
andyoso said:
You should download it before...if you give me your CID pass you the correct link to download the correct "firmware.zip" that contains the HBoot.
After the downloading you should type this command:
Click to expand...
Click to collapse
Thank you. My cidread returns HTC_044. Also I have logged into bootloader screen again. I just ran the Unlock_bin file I received during rooting my device and now my phone isn't displaying the black screen and finally entered bootloader.
The problem I figured out was my bootloader was relocked and my RUU setup failed, so I had a custom rom installed with locked bootloader. That's why the phone was bricked I wan't entering bootloader.
Now I can access my recovery as well.
serwan said:
U need to RELOCKED your bootloader.
Please google how to extract boot_signed.img , recovery_signed.img and rom.zip from RUU. After u've extract those, flash boot_signed and recovery_signed first. Then boot to recovery, flash your rom.zip and only after that u run the RUU. Give it a try.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
You don't need to extract anything from the ruu, if you have the right ruu just lock the bootloader and leave the phone there ... Start the ruu from pc with admin rights.....
Im speakung from my experiance. I have face this problem before. RUU program cant install the rom. So i have to flash everything extracted from RUU first. Only after that the RUU can install the rom. But maybe im just got lucky though.
Sent from my HTC One X using xda premium
Hi All
I tried the ace hack kit again to get s-off and really messed up
It went through the process until it said radio flashed please wait....
Phone rebooted and stuck on the white htc screen
Managed to recover with a pd98.img but this has wiped my root and 4ext and the phone boots into 2.33 sense 2.1
hboot has changed from 2.0xxxxxxx to 0.85.0024
Problem is when i do the htcdev procedure to unlock the bootloader i get an error when running fastboot oem get_identifier_token
It just says bootloader command error
Help!!
Stu
You'll need to update the firmware to the latest
hacktrix2006 said:
You'll need to update the firmware to the latest
Click to expand...
Click to collapse
How do i do that if i cant unlock the bootloader to install a custom recovery?
You download the lastest RUU you can find for your phone from
http://forum.xda-developers.com/showthread.php?t=2094087
hacktrix2006 said:
You download the lastest RUU you can find for your phone from
http://forum.xda-developers.com/showthread.php?t=2094087
Click to expand...
Click to collapse
Ok thanks
My DHD was originally branded Virgin from the UK the cid is VIRGI001
I can see some UK Orange on the site but cant see a virgin
Which one can I use?
Stu
Then you will need to make a Goldcard then download the WWE Version then run the .exe and get the rom.zip file copied some where then with goldcard inplace run fastboot with the following commands
fastboot oem rebootRUU
fastboot flash zip rom.zip
That will then flash it. make sure before running fastboot your in the same place as fastboot and the rom.zip file though
hacktrix2006 said:
Then you will need to make a Goldcard then download the WWE Version then run the .exe and get the rom.zip file copied some where then with goldcard inplace run fastboot with the following commands
fastboot oem rebootRUU
fastboot flash zip rom.zip
That will then flash it. make sure before running fastboot your in the same place as fastboot and the rom.zip file though
Click to expand...
Click to collapse
Ok made the goldcard (hopefully)
My image build is 2.50.405.2
There isnt a build higher than this on the list but there is a wwe build with the same number
RUU_Ace_Gingerbread_S_HTC_WWE_2.50.405.2_Radio_12.54.60.25_26.09.04.11_M2_release_199042_signed
All the other builds are lower
Will this work?
Stu
ps
On Windows 7 any idea where the rom zip is extracted to when the exe is run?
Rom.zip will be any one of the folders in temp just type %temp% in run box. As for the Rom if that's the latest then it's the latest.
Also 3.x.405 is latest
Sent from my HTC Desire HD using xda app-developers app
All looks like it worked
The fastboot sent a load of files to the phone
And it completed ok
But phone is still on the black htc screen with the green progress bar appx 95% across
What do i do now?
If fastboot says completed just type.fastboot reboot
Sent from my HTC Desire HD using xda app-developers app
Ok waited about 10 mins then did fastboot reboot
Nothing changed and i still cant get_identifier_token
See attached
Stu
Have you installed the HTC dev boot yet if not then do the same with that
As you did with the ruu via fast boot
Sent from my HTC Desire HD using xda app-developers app
Hi Hacktrix
You're being really helpful and I appreciate it.
Sorry for being a bit thick but what do you mean by installing the HTC dev boot?
Have i missed something?
I cant get the token still as it still says bootloader error
Flashing the rom.zip seems to go without error but nothing changes on the phone
Cheers
Stu
Not a problem. Right have you gone to the HTC dev site and registered
Sent from my HTC Desire HD using xda app-developers app
If so i can do everything for you including S-Off'ing your device if you want that done too.
Yes im reg on htcdev
I already htcdev unlocked this phone prior to me messing it up with the ace hack kit
yes id like it s-off as well
Just easier flashing roms as before had to flash rom and fast boot the boot.img
stu
Send me a PM and i will help you ok mate
pm sent with my email addy
Cheers
Hey guys,
So I have a Developer Edition M8 (HBOOT- 3.19), and I went through multiple steps trying to get GPE onto it. Since I'm posting here, I screwed up along the way, and Google hasn't been to helpful. To put it simply, I do not have an OS on the phone right now, and need to flash stock back onto it, and am having trouble because TWRP recovery no longer wishes to run.
Here's what happened:
I was following an outdated guide to getting GPE (I didn't know it was outdated at the time) and it said to flash insertcoin in order to be able to use firewater to get S-Off. I flashed insertcoin, realized firewater was no longer supporeted, and felt like I had wasted a few hours. I then found sunshine and tried to use it, but insertcoin was not close enough to stock to be compatible, so I tried to flash a stock ROM I found on this thread here onto the phone. I am fairly certain I downloaded the correct file, as the HBOOT 3.19 leads to the 3.xx file, and my CIS is BS_US002, so I downloaded the 3.28 file available. I took the zip, placed it onto the phone, and wiped insertcoin, and tried to install the stock ROM. Well, it failed.
I went back to the drawing board, actually read the instructions, and did this: I placed the unpacked zip into the TWRP/Backups folder on the phone. I then used fastboot flash recovery FILE.IMG to flash boot.emmc.win from my computer to the phone. Now, when I try to go into recovery to wipe and recover, it no longer enters TWRP. It is stuck on the HTC screen.
What do I do from here? My main goal is just to get stock back onto the phone, and I hope I did not mess up the phone.
To put all phone info in one place:
HTC One M8 Developer Edition
HBOOT- 3.19
CID- BS_US002
Thank you!
rbalutiu said:
Hey guys,
So I have a Developer Edition M8 (HBOOT- 3.19), and I went through multiple steps trying to get GPE onto it. Since I'm posting here, I screwed up along the way, and Google hasn't been to helpful. To put it simply, I do not have an OS on the phone right now, and need to flash stock back onto it, and am having trouble because TWRP recovery no longer wishes to run.
Here's what happened:
I was following an outdated guide to getting GPE (I didn't know it was outdated at the time) and it said to flash insertcoin in order to be able to use firewater to get S-Off. I flashed insertcoin, realized firewater was no longer supporeted, and felt like I had wasted a few hours. I then found sunshine and tried to use it, but insertcoin was not close enough to stock to be compatible, so I tried to flash a stock ROM I found on this thread here onto the phone. I am fairly certain I downloaded the correct file, as the HBOOT 3.19 leads to the 3.xx file, and my CIS is BS_US002, so I downloaded the 3.28 file available. I took the zip, placed it onto the phone, and wiped insertcoin, and tried to install the stock ROM. Well, it failed.
I went back to the drawing board, actually read the instructions, and did this: I placed the unpacked zip into the TWRP/Backups folder on the phone. I then used fastboot flash recovery FILE.IMG to flash boot.emmc.win from my computer to the phone. Now, when I try to go into recovery to wipe and recover, it no longer enters TWRP. It is stuck on the HTC screen.
What do I do from here? My main goal is just to get stock back onto the phone, and I hope I did not mess up the phone.
To put all phone info in one place:
HTC One M8 Developer Edition
HBOOT- 3.19
CID- BS_US002
Thank you!
Click to expand...
Click to collapse
use this
http://dl3.htc.com/application/RUU_..._2G_20.63.4196.01_release_394319_signed_2.exe
clsA said:
use this
Click to expand...
Click to collapse
Just flash the exe onto the phone using the fastboot command? or is there something more to it?
rbalutiu said:
Just flash the exe onto the phone using the fastboot command? or is there something more to it?
Click to expand...
Click to collapse
it's a RUU just click it in windows
no flashing just put the phone in bootloader fastboot usb
clsA said:
it's a RUU just click it in windows
no flashing just put the phone in bootloader fastboot usb
Click to expand...
Click to collapse
I downloaded the RUU and tried running it: it gave me error code 155 and said that it cannot update the phone. Right below it also states to get the correct RUU and try again, although I think this is the right one.
Is there any way to troubleshoot this/fix this?
rbalutiu said:
I downloaded the RUU and tried running it: it gave me error code 155 and said that it cannot update the phone. Right below it also states to get the correct RUU and try again, although I think this is the right one.
Is there any way to troubleshoot this/fix this?
Click to expand...
Click to collapse
Flash this first
https://www.androidfilehost.com/?fid=95784891001612796
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then flash the RUU ...
clsA said:
Flash this first
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then flash the RUU ...
Click to expand...
Click to collapse
I put in both flash zip commands and both resulted in failures, stating "remote: 99 unknown fail". Was this intended or something went wrong?
rbalutiu said:
I put in both flash zip commands and both resulted in failures, stating "remote: 99 unknown fail". Was this intended or something went wrong?
Click to expand...
Click to collapse
I figured out the problem but still no solution: both of these require s-off. The bootloader is unlocked, but I currently have S-On. What can we do to either make it S-Off or put the stock ROM on the phone?
The ruu and Firmware works fine with s-on
post the command window output ..your doing something wrong
rbalutiu said:
I figured out the problem but still no solution: both of these require s-off. The bootloader is unlocked, but I currently have S-On. What can we do to either make it S-Off or put the stock ROM on the phone?
Click to expand...
Click to collapse
bootloader needs to be relocked when you are s-on, for ruu mode flashing (firmware.zip or full ruu)
nkk71 said:
bootloader needs to be relocked when you are s-on, for ruu mode flashing (firmware.zip or full ruu)
Click to expand...
Click to collapse
Thanks nkk71, but the Developer edition he has comes with the bootloader unlocked .. i never locked mine to flash the RUU ( I did s-off the phone so I'm not sure if it's needed or not)
OP: use fastboot oem lock to relock your bootloader and try the RUU again
clsA said:
Thanks nkk71, but the Developer edition he has comes with the bootloader unlocked .. i never locked mine to flash the RUU ( I did s-off the phone so I'm not sure if it's needed or not)
OP: use fastboot oem lock to relock your bootloader and try the RUU again
Click to expand...
Click to collapse
Yep, I know it's silly that the US Dev edition (bootloader unlocked by default), has to be relocked for RUU mode flash with S-ON... same thing on the M7
nkk71 said:
Yep, I know it's silly that the US Dev edition (bootloader unlocked by default), has to be relocked for RUU mode flash with S-ON... same thing on the M7
Click to expand...
Click to collapse
Progress made.
I locked bootloader, ran the RUU, got stock back onto there. Then unlocked again, rerooted, and got s-off. Now I'm trying to install the GE RUU as said by this site and its giving me something that says "FAILED <remote: 42 custom id check fail>" .
Just this one last step, what can I do to go around this and fix this?
Thank you both for your help so far!
rbalutiu said:
Progress made.
I locked bootloader, ran the RUU, got stock back onto there. Then unlocked again, rerooted, and got s-off. Now I'm trying to install the GE RUU as said by this site and its giving me something that says "FAILED <remote: 42 custom id check fail>" .
Just this one last step, what can I do to go around this and fix this?
Thank you both for your help so far!
Click to expand...
Click to collapse
you'll need to edit the android_info.txt to include your MID and CID
Should look like this
modelid: 0P6B12000
modelid: 0P6B17000
modelid: 0P6B1****
cidnum: 11111111
cidnum: T-MOB010
cidnum: CWS__001
cidnum: BS_US001
cidnum: BS_US002
cidnum: GOOGL001
mainver: 3.11.1700.5
btype:0
aareport:1
hbootpreupdate:3
Click to expand...
Click to collapse
And you'll want these new files, not the old one's on that site
Lollipop > http://forum.xda-developers.com/showthread.php?t=2708589
and the older Build: 4.4.4 - 2.12.1700.1 about half way down the page here >> http://www.graffixnyc.com/m8.php
clsA said:
you'll need to edit the android_info.txt to include your MID and CID
Should look like this
And you'll want these new files, not the old one's on that site
Lollipop > http://forum.xda-developers.com/showthread.php?t=2708589
and the older Build: 4.4.4 - 2.12.1700.1 about half way down the page here >> http://www.graffixnyc.com/m8.php
Click to expand...
Click to collapse
Thanks so much! Got 5.0.1 running on the phone, thanks for all the help!
Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.
RalphORama said:
Phone specs:
Code:
RELOCKED
M8_UL PVT SHIP S-OFF
CID-11111111
HBOOT-3.16.0.0000
RADIO-1.23.213311491.05G
OpenDSP-v48.2.2-00564-M8974_FO.1211
OS-4.20.531.4 (1.54.401.5)
eMMC-boot 2048MB
So I'm trying to update my One M8, and I think I messed up pretty bad. I tried running the RUU updater for my T-Mobile variant (found on HTC's ROM Download page), but got the infamous "error 155." However, my bootloader is re-locked. Therefore, according to all the forum posts I could find, I shouldn't be getting that error. I've run a few commands since then, including fastboot oem writecid 11111111 and fastboot erase cache. Somehow, I've managed to get to the point where my phone won't even boot into recovery, it just gets stuck at the "Entering recovery..." screen. However, while stuck on this screen, the phone does respond to ADB commands. I can get root shell access, but I'm not sure what to do with it.
I've tried flashing TWRP 3.0.0.0 to no avail. I've tried running fastboot boot <twrp filename here>, also to no avail. I'm pretty much stuck with a phone that only boots into fastboot, and a weird purgatory-recovery where I can achieve shell access. The RUU file fails to update no matter what I do.
Is there a way I can fix this, or have I completely bricked my phone?
Thank you for your time.
Click to expand...
Click to collapse
Have you flashed both stock recovery for the RUU in particular youre flashing and re-locked BL, and are you installing a version number that is equal to or higher than the one you already have installed.
Completely stock phone should flash RUU, as long as its not a version down from whats installed, ie, trying to flash LP when MM is already flashed on phone, UNLESS of course youre s-off and supercid, because with supercid you should be able to flash any RUU .
But i had similar issues, im s-on, so i had to revert to stock LP completely, then flashed HTC__001 Stock MM for my phone, failing all that there is always the option of copying a nandroid on here to ur sd card, boot into twrp and restore the Nandroid just to get it up and running again.
I would run the RUU, let it sit at first screen, goto start button and type in %temp%, find the folder inside temp that ruu just created, (sort by date), pull the rom.zip from that to ur desktop, Unzip it and get the files recovery and boot.img, flash them both to ur phone via fastboot, if it still works, then restart ur phone and it should load up, you could then try to install the RUU from windows again, failing that after flashing recovery and boot, goto ur stock recovery and wipe and reset then reboot phone.
It doesnt sound like hard brick, just soft brick, it should be ok.
If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers
Mr Hofs said:
Or flash the standalone firmware first and then the full ruu.
Click to expand...
Click to collapse
This is most likely the solution. In particular, if OP is trying to install MM RUU, there is a new peculiarity (requirement?) with all MM RUUs, where you need to have MM firmware in order to run the RUU, or else you will have Error 155.
Find the firmware.zip that matches the version number of the RUU, flash it; then try the RUU again.
---------- Post added at 09:42 AM ---------- Previous post was at 09:35 AM ----------
gazza35 said:
Have you flashed both stock recovery for the RUU
Click to expand...
Click to collapse
You don't need stock recovery to RUU. Folks keep saying this, and its not true.
You need stock recovery to OTA, but you do not need it for RUU. OTA and RUU are two very different things.
gazza35 said:
because with supercid you should be able to flash any RUU .
Click to expand...
Click to collapse
This is also not true. You need to match MID and CID (or SuperCID) in order to flash an RUU. SuperCID bypasses the CID check, but you still need to pass the MID check.
---------- Post added at 09:44 AM ---------- Previous post was at 09:42 AM ----------
gazza35 said:
But i had similar issues, im s-on, so i had to revert to stock LP
Click to expand...
Click to collapse
Same peculiarity with the MM RUU I mentioned above (need to flash the MM firmware if coming from LP) also applies if you try to downgrade back to LP. Meaning, you need to flash the LP firmware, then LP RUU.
Mr Hofs said:
If you try to flash a Android MM ruu i suggest to flash a lower ruu first. Usually the big jump from the 3.16 boot loader to a 3.19 boot loader is too much.
Or flash the standalone firmware first and then the full ruu.
The high version of TWRP doesn't work because your bootloader is too low (3.16) if you want a working TWRP then use a 2.7 version.
If you can get to the bootloader then it's just a softbrick. A hardbrick is only when the bootloader is not accessible anymore or when the phone doesn't boot up in any way anymore.
Cheers
Click to expand...
Click to collapse
Thank you (and everyone else) for your replies! Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
EDIT: I flashed TWRP 2.7 and I was able to boot into recovery! I love progress.
RalphORama said:
Out of curiosity, where can I find a lower RUU? I can only find the most recent one from HTC's website.
Click to expand...
Click to collapse
You can find the links for older T-Mob RUUs here: http://forum.xda-developers.com/showthread.php?t=2714456
Phone Specifications:
Baseband Version: 1.29.213311491.05G_20.58.4198.03_F
Android Version: 6.0.1
S-On/S-Off Status: S-On
Root Status: Rooted
Phone Model: HTC One M8 (T-Mobile)
Custom Recovery: TWRP
~Problem~
My Device Is Rooted And I Would Like To Un-Root It And Get Back To Stock.
I Followed DroidModderX ROOT Master (YouTuber) And His Video On Using HTC's Official RUU To Restore And Update My Phone.
Video Title: HTC One How To Unbrick, Unroot, Stock Factory Reset RUU Developer Edition ~ By: DroidModderX ROOT Master
I Was Following The Steps And Confirmed Everything, But While Running The RUU, It Said CID Not Compatible, Download Correct One From HTC Website. Well That Was The T-Mobile 6.20 Marshmallow Update RUU Which Was Made For My HTC.
I Don't Have Money To Turn My S-OFF Either Cause You Have To Pay $25 For Sunshine To Work. (Are There Any Other Ways Of Turning S-OFF?)
So How Can I Proceed From Here To Get My Phone Unrooted And Back To Stock.
~Notes~
Slim6 Launcher Has The Root Control In Developers Options. (Doesn't Use SuperSu App)
TheKookieGuy said:
Phone Specifications:
Baseband Version: 1.29.213311491.05G_20.58.4198.03_F
Android Version: 6.0.1
S-On/S-Off Status: S-On
Root Status: Rooted
Phone Model: HTC One M8 (T-Mobile)
Custom Recovery: TWRP
~Problem~
My Device Is Rooted And I Would Like To Un-Root It And Get Back To Stock.
I Followed DroidModderX ROOT Master (YouTuber) And His Video On Using HTC's Official RUU To Restore And Update My Phone.
Video Title: HTC One How To Unbrick, Unroot, Stock Factory Reset RUU Developer Edition ~ By: DroidModderX ROOT Master
I Was Following The Steps And Confirmed Everything, But While Running The RUU, It Said CID Not Compatible, Download Correct One From HTC Website. Well That Was The T-Mobile 6.20 Marshmallow Update RUU Which Was Made For My HTC.
I Don't Have Money To Turn My S-OFF Either Cause You Have To Pay $25 For Sunshine To Work. (Are There Any Other Ways Of Turning S-OFF?)
So How Can I Proceed From Here To Get My Phone Unrooted And Back To Stock.
~Notes~
Slim6 Launcher Has The Root Control In Developers Options. (Doesn't Use SuperSu App)
Click to expand...
Click to collapse
relock bootlaoder. flash your device specific RUU
Sent from my MotoE2(4G-LTE) using Tapatalk
Question?
sonnu0100 said:
relock bootlaoder. flash your device specific RUU
Sent from my MotoE2(4G-LTE) using Tapatalk
Click to expand...
Click to collapse
So I Relock The Bootloader And Run The RUU File On My Computer Again?
Thank You For Your Patience And Help.
Could You Possibly Send Me A Link On How To Relock Bootloader. Thank You
sonnu0100 said:
relock bootlaoder. flash your device specific RUU
Sent from my MotoE2(4G-LTE) using Tapatalk
Click to expand...
Click to collapse
I Can't Get S-Off To Relock My Bootloader
I Don't Have Money For Sunshine
Are There Any Alternatives
You don't need S-Off to relock it. Just enter the bootloader and open a command window in your adb (fastboot) directory and type: "fastboot oem lock" without the quotes. After that you can type "fastboot getvar cid" to see what is the exact CID of your phone so you can flash the proper RUU.
todorkaravalchev said:
You don't need S-Off to relock it. Just enter the bootloader and open a command window in your adb (fastboot) directory and type: "fastboot oem lock" without the quotes. After that you can type "fastboot getvar cid" to see what is the exact CID of your phone so you can flash the proper RUU.
Click to expand...
Click to collapse
Oh Alright Thank You.
Will Update If It Works Soon.
I made a batch file which you can use for easyer locking. It's attached below. Just put it into your adb/fastboot directory, extract it and run it!
todorkaravalchev said:
I made a batch file which you can use for easyer locking. It's attached below. Just put it into your adb/fastboot directory, extract it and run it!
Click to expand...
Click to collapse
I'll check out ur file In a second
Could u provide step by step instructions on what to do.
Just so I don't screw up along the way
Thank u
COMPLETE
todorkaravalchev said:
I made a batch file which you can use for easyer locking. It's attached below. Just put it into your adb/fastboot directory, extract it and run it!
Click to expand...
Click to collapse
I Used Your File And It Locked Bootloader But Couldn't Find CID.
So I Ran The Command Myself And It Showed Me It.
Everything Is Sorted Out And Works Now.
Thank You
TheKookieGuy said:
I Don't Have Money To Turn My S-OFF Either Cause You Have To Pay $25 For Sunshine To Work. (Are There Any Other Ways Of Turning S-OFF?)
Click to expand...
Click to collapse
Sunshine is the only way to s-off. But you don't need s-off to relock to bootloader (as you now know), to return to stock, or to run the proper RUU for your version.
Moderator Information,
Thread has been closed at OP's request.