I rooted a while back using revolutionary, and currently have hboot 6.98.1002.
I could really do with getting back to s-on and stock etc etc, but every guide I follow just doesn't seem to work.
I have searched, and searched and searched, but I'm a week down the line and still unable to change my hboot.
I'm at pains to start a new thread, but this thing is drving me bonkers.
I've read the instrcutions here for Alphareved:
http://forum.xda-developers.com/showthread.php?t=1236890
but typing the 'adb devices' in cmd but it just doesn't work. Is there some kind of zip file i should be extraxcting to get the sdk (i think it's called that?).
did u try this exe?
http://dl.google.com/android/installer_r16-windows.exe
edit: what is the output of "adb devices"?
-Download this file, it has the adb and fastboot files needed to proceed
-Extract the file to "c:\" so that the path looks like this C:\android-tools
-Install HTCDriver (Fastboot drivers) (should already be installed from revolutionary) but here's the link again
-Open cmd and type "cd/"
-then type "cd android-tools"
*To test whether you have set up all the files correctly and your phone is connected correctly you can do the following;
*Plug your phone in (when plugging in select CHARGE ONLY (i.e. leave on the home screen)
*In cmd type "adb" and press enter, it should show a list of commands, then type "fastboot"and press enter, it should also show a list of commands)
*If both these commands work you have extracted the files to the right place and have setup cmd right.
*then type "adb devices"
*Should show connected phone serial if not then try get the latest HTCdrivers
Flash the ENG HBoot
To flash the ENG HBoot you can use one of these methods;
1) Fastboot
-Place the .img file (extracted from PG88IMG.zip) in C:\android-tools
-Boot phone into fastboot
-Run command "fastboot flash hboot engHBOOToverARX.img" in CMD
2) Android Flasher
-Download from here
-Select phone, select Hboot .img (bootloader)
-Boot phone into fastboot and select FLASH
3) Updater file (PG88IMG.zip)
-Download the PG88IMG.zip (make sure is called that EXACTLY, not pg88img.zip or PG88IMG.zip.zip)
-Place file on your SD card root, and boot into HBoot, and follow onscreen instructions
4) adb shell (LAST LAST resort, one typo and you can brick your phone, do some reserch before doing it
-Place the hboot on your SD card and remane it to "hboot.img"
-Boot into recovery
-adb devices - Must show your serial
-adb shell
-su (it should show #, that means you have the right permission, if it shows $ afterwards you dont have permission)
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img (backup your current hboot)
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18 (flashes new hboot)
If you have any problems first check out this thread for answers
Install the RUU
How to check if downloaded RUU is compatible with your phone:
To avoid errors etc, you need to confirm your phone is unbranded, i.e. check if your CID matches the CID check list in the RUU you downloaded.
To do this Run the installer, then go to your Windows Temp Folder, sort the folder by date and pick the folder with the latest date, and locate the rom.zip file inside, open it up and open the android-info.txt file. Your CID should be in the list, if not then you need to create a GoldCardto install that RUU.
Here is a list of RUU's you can download for your phone [ROM]Shipped Desire S ROM Collection - xda-developers
Here and here are two great threads for HTC Desire S Guides
Thanks so much for the replies fellas. I'm away from my comp until this evening, but I'll relpy once I've tried these out.
This will work
hycaet said:
I rooted a while back using revolutionary, and currently have hboot 6.98.1002.
I could really do with getting back to s-on and stock etc etc, but every guide I follow just doesn't seem to work.
I have searched, and searched and searched, but I'm a week down the line and still unable to change my hboot.
I'm at pains to start a new thread, but this thing is drving me bonkers.
I've read the instrcutions here for Alphareved:
http://forum.xda-developers.com/showthread.php?t=1236890
but typing the 'adb devices' in cmd but it just doesn't work. Is there some kind of zip file i should be extraxcting to get the sdk (i think it's called that?).
Click to expand...
Click to collapse
I just did for my HTC Desire S (India).
This should help . Read
foX2delta said:
Flash the ENG HBoot
To flash the ENG HBoot you can use one of these methods;
1) Fastboot
-Place the .img file (extracted from PG88IMG.zip) in C:\android-tools
-Boot phone into fastboot
-Run command "fastboot flash hboot engHBOOToverARX.img" in CMD
Click to expand...
Click to collapse
This did it. Perfect. You're a star. This has bugged me for so long. You've made my bloody day. God bless and seasonal greetings.
foX2delta said:
Install the RUU
How to check if downloaded RUU is compatible with your phone:
To avoid errors etc, you need to confirm your phone is unbranded, i.e. check if your CID matches the CID check list in the RUU you downloaded.
To do this Run the installer, then go to your Windows Temp Folder, sort the folder by date and pick the folder with the latest date, and locate the rom.zip file inside, open it up and open the android-info.txt file. Your CID should be in the list, if not then you need to create a GoldCardto install that RUU.
Click to expand...
Click to collapse
How can i check my CID number to match with the RUU version?
terragady said:
How can i check my CID number to match with the RUU version?
Click to expand...
Click to collapse
Not sure of the command right now, Google it, like how to check you cId, then when you run the RUU go to your temp folder, I think there is a file called android.txt in the folder with the rom.zip is and it has the list.
Related
How to s-on desire ?
1) change your revolutionary hboot 6.98.xxxx with an engineering one 0.98.2000
2) pick a RUU for your brand/region from the sticky thread and flash it
that's all
P.S.: more detailed guide here - point 4.1
The problem is that i dont know how but thanks any way
lovelorn.! said:
How to s-on desire ?
Click to expand...
Click to collapse
You need to be a little more involved.
How did you s-off?
-Turn off fastboot menu/settings/power/fastboot (on the phone)
-Turn on USB debugging menu/Settings/Applications/Development/USB debugging (on the phone)
Download this file here, it has the adb and fastboot files needed
-Extract the file to "c:\" so that the path looks like this C:\android-tools
-Install HTCDriver (Fastboot drivers) (should already be installed from revolutionary if you s-offed by them) but here's the link again
-Open cmd and type "cd/"
-then type "cd android-tools"
*To test whether you have set up all the files correctly and your phone is connected correctly you can do the following;
*Plug your phone in (when plugging in select CHARGE ONLY (i.e. leave on the home screen)
*In cmd type "adb" and press enter, it should show a list of commands, then type "fastboot"and press enter, it should also show a list of commands)
*If both these commands work you have extracted the files to the right place and have setup cmd right.
*then type "adb devices"
*Should show connected phone serial if not then try get the latest HTCdrivers
To flash the ENG HBoot you can use one of these methods;
1) Fastboot
-Place the .img file (extracted from PG88IMG.zip) into C:\android-tools
-Boot phone into fastboot
-Run command "fastboot flash hboot engHBOOToverARX.img" in CMD
2) Android Flasher
-Download from here
-Select phone, select Hboot .img (bootloader)
-Boot phone into fastboot and select FLASH
3) Updater file (PG88IMG.zip)
-Place PG88IMG.zip File on your SD card root, and boot into HBoot, and follow onscreen instructions
4) adb shell (LAST LAST resort, one typo and you can brick your phone, do some reserch before doing it
-Place the hboot on your SD card and remane it to "hboot.img"
-Boot into recovery
-adb devices - Must show your serial
-adb shell
-su (it should show #, that means you have the right permission, if it shows $ afterwards you dont have permission)
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img (backup your current hboot)
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18 (flashes new hboot)
To get into Hboot; switch phone off and the press power+vol down
To get start fastboot (boot Hboot, plug phone in "HBoot USB plug" shows once phone is plugged in and press the power button (fastboot is highlighted by default) then it says "Fastboot USB")
*(As a test to ensure you have put your phone into fastboot type "fastboot devices" in cmd, it will show your phones serial, if it shows nothing you have not put your phone into fastboot yet)
All From this thread here under section 2
lovelorn.! said:
The problem is that i dont know how but thanks any way
Click to expand...
Click to collapse
all you need to do is read more to know how to do it like me i read a lot i know its hard but you'll find what you are looking for
This Guide is intended for the users who rooted their devices using the cwm-4.0.1.4-saga.img and su-3.0-efgh-signed.zip files.
note: it may work for the other rooting and downgrade methods
Files needed
*Original Nandroid Backup (rooted)
*Bootloader Unlocked via HTCDev or S-Off
*Oldest RUU that is compatible to your region
*misc_version
*adb and fastboot
*Goldcard Tool and Goldcard IMG
Note: I use this method for the version GB 2.3.5 Sense 3.0 SW 2.15.707.2
Steps:
I. Unlock Bootloader
a. go to www.htcdev.com and choose "Unlock Bootloader" click the "Get Started" green button.
b. you will be redirected to http://htcdev.com/bootloader/ at the "supported Devices" choose "All Other Supported Models"
c. follow the on screen instructions.
II-A. Coming from a custom rom
a. download my Stock Nandroid Backup that I posted here.
b. restore it via 4ext or cwm recovery be sure to wipe all the cache, partition and dalvik before doing so.
c. after restoring my Nandroid Backup boot your device to fastboot and flash the boot.img and recovery.img that I posted here as well.
d. your phone should boot up with no problems.
II-B. Coming from a stock fw
a. be sure that you have your Nandroid Backup and proper boot.img and recovery.img
b. follow the same procedure at II-A the only difference is that you're the one who needs to find your proper boot.img and recover.img
III. Creating a Gold Card
a. download the gold card helper from market.
b. get the cid of your mmc2
c. go to http://psas.revskills.de/?q=goldcard and fill out the form using the reversed cid that gc helper provided.
d. download the goldcard.img
e. download the goldcard tool I posted here.
f. connect your phone as a "Disk Drive" and format your mmc.
e. using gold card tool click "Refresh" to select the HTC MMC that you will use and click "Load GoldCard.img" select the goldcard.img you've downloaded and click "Patch MMC"
IV. Changing your device Version
a. download the AWT Tools and Patch that I posted here
b. extract the files to C:
c. execute this commands using "cmd"
Code:
adb push C:\downsaga\misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version -s 1.27.405.6
exit
exit
IV. Relock your Bootloader
a. go into fastboot mode and execute this command
Code:
fastboot oem lock
V. Flashing the oldest RUU for your Device
a. download the oldest RUU that you can find for your device but make sure it will be newer than 1.27.405.6.
b. if there's no RUU for your device that is newer than 1.27.405.6 change it to 1.20.000.0.
c. go into fastboot mode once again and connect your device to pc.
d. flash your device using the RUU you've downloaded and viola! you have a downgraded Desire S device.
note: you can still cross your fingers so that you can be so sure that you don't have to do this all over again.
Nandroid Backup and Tools - still uploading
I still would rather get temp root rather than using HTC dev.
Don't do the same mistake as I did, htcdev will surely void your warranty. Use ZergRush and misc_version instead: http://forum.xda-developers.com/showthread.php?t=1399331
where is the tool and nandbackup ? can't find it anywhere
ok, this is what i've done so far by reading the forum.. and it's been a great help. but need a bit more help~
HTC Sensation 4G (T-Mo)
CPU: 1.2
Android Version: 4.0.3 (OTA updated)
HTC Sense 3.6
SW Ver: 3.32.531.14.710RD
Kernal Ver: 3.0.16-gc764bfb
Baseband: 11.69A
HTC Dev - Unlocked
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
eMMC-BOOT
i've already installed the CWN-SuperSU-v0.94 from the command.
today, i downloaded the CM9 (latest release on 8/9/12 for STABLE) and installed it from command line. everything went well.. EXCEPT.. upon booting up.. i only see the cyanogenmod 9 (cartoon figure) with the background flashing. it kept on going for close to 15 mins and still wouldn't go further than that.
i then took the battery out and tried it again and still the same thing. so now i recovered back to the original ICS.
i wanted to go Jellybean, but the thought of camera not working won't do it for me. plus waiting for TMo to release the JB.. who knows how long that will take.
anyway.. decided to stick with ICS.
what am i doing wrong here? or should i be using a different ROM; one which can also overclock the cpu?
please help~~
when SON and HTC-DEV unlock ..you need to flash stuff differently
after flashing the ROM you need to flash boot.img separately
now if you are having CWM custom recovery then
flash the cm rom again from it
and copy the boot.img from the rom zip file to the adb/fastboot folder
then flash this separately
connect the phone from bootloader to pc (phone reads fastboot usb after this)
then this command
fastboot flash boot boot.img
then reboot using
fastboot reboot
thats all
but if you are having 4EXT custom recovery ..then things will be much easier for you
just enable smartflash from 4EXT->tools then flash the rom thats all (the recovery will take care of the rest )
also once done do the step #5 from this guide flashing ROMS with SON ..then you can even forget about smartflash (read the guide too it will give you much insight as to why you are facing problems ..especially step #3)
the recovery method i used was the HTC ONE X thingy.
i found the boot.img in the recovery folder. so after i flash the CM9 from the zip file, i'd have to reboot. so instead of reboot, are you saying i need to hold down volume and power to get into recovery mode and flash the boot.img separately?
and where can i find the abd folder? do i use the SDK to copy and paste the files into that folder/ directory?
cthsuks said:
the recovery method i used was the HTC ONE X thingy.
i found the boot.img in the recovery folder. so after i flash the CM9 from the zip file, i'd have to reboot. so instead of reboot, are you saying i need to hold down volume and power to get into recovery mode and flash the boot.img separately?
and where can i find the abd folder? do i use the SDK to copy and paste the files into that folder/ directory?
Click to expand...
Click to collapse
not that boot.img ..you need to extract the boot.img from the cm9 zip file that you have downlaoded ..dont use the boot.img from the one-x tool kit
also yes ..you need to go to bootloader after flashing cm9 (but first copy the boot.img in pc)
then the adb folder is where the adb.exe and fastboot.exe is present (as you did HTC-DEV unlock ..you might have it in either C:\Android-SDK\tools or C:\Android-SDK\platform-tools)
go to there and open command prompt there
(if windows hold shift + right click ->open command window here)
ganeshp said:
not that boot.img ..you need to extract the boot.img from the cm9 zip file that you have downlaoded ..dont use the boot.img from the one-x tool kit
also yes ..you need to go to bootloader after flashing cm9 (but first copy the boot.img in pc)
then the adb folder is where the adb.exe and fastboot.exe is present (as you did HTC-DEV unlock ..you might have it in either C:\Android-SDK\tools or C:\Android-SDK\platform-tools)
go to there and open command prompt there
(if windows hold shift + right click ->open command window here)
Click to expand...
Click to collapse
crap.. when i did the HTC Dev unlock, i did it at work, so the folder: C:\Android-SDK\tools is not present on my laptop. any other way to work around?
cthsuks said:
crap.. when i did the HTC Dev unlock, i did it at work, so the folder: C:\Android-SDK\tools is not present on my laptop. any other way to work around?
Click to expand...
Click to collapse
ahh thats fine ..now we can deal it easy way ..however did you installed installed htc drivers ?
do this go to my soff guide (guide link in my signature )
1.downlaod HTC drivers from it ..in prerequisites point 2
2.first open control panel and uninstall any crap thats starts with HTC
3.install the above drivers
4.download temproot sensation windows zip file from the same soff guide (steps to run this tool -->.point 1)
5.extract it and rename the folder to adb and keep it somewhere like C:\adb
6.go to that adb folder and delete temp_root and temp_root_remove bat files
7.thats it you are done ..now you have working adb (c:\adb ) go there and repeat the steps ive told you earlier
ganeshp said:
ahh thats fine ..now we can deal it easy way ..however did you installed installed htc drivers ?
do this go to my soff guide (guide link in my signature )
1.downlaod HTC drivers from it ..in prerequisites point 2
2.first open control panel and uninstall any crap thats starts with HTC
3.install the above drivers
4.download temproot sensation windows zip file from the same soff guide (steps to run this tool -->.point 1)
5.extract it and rename the folder to adb and keep it somewhere like C:\adb
6.go to that adb folder and delete temp_root and temp_root_remove bat files
7.thats it you are done ..now you have working adb (c:\adb ) go there and repeat the steps ive told you earlier
Click to expand...
Click to collapse
yes i installed the HTC driver already.
following your link to install the SDK manager and keep getting:
"Failed to fetch URL, reason: Connection timed out: connect"
cthsuks said:
yes i installed the HTC driver already.
following your link to install the SDK manager and keep getting:
"Failed to fetch URL, reason: Connection timed out: connect"
Click to expand...
Click to collapse
sdk manager ??
where did i said you to install that ?
ganeshp said:
sdk manager ??
where did i said you to install that ?
Click to expand...
Click to collapse
sorry i must've ended up clicking on the wrong link. so i went back to the previous post you put up.
now if you are having CWM custom recovery then
flash the cm rom again from it yup, i did that. i have the CM9 from cyanogenmod
and copy the boot.img from the rom zip file to the adb/fastboot folder
then flash this separately
yup, i created the adb folder by renaming the root-sensation-wind.zip file from your post. it didn't have the fastboot.exe in there, so i copied it from the SDK manager tool that i had installed previously when i downloaded the wrong file. i also copied the boot.img from the CM9 zip file as you suggested
connect the phone from bootloader to pc (phone reads fastboot usb after this) yup did that..
then this command
fastboot flash boot boot.img
yup did that, and it was completed
then reboot using
fastboot reboot
yup did that as well and it rebooted
thats all
but wait.. the sensation is still stuck at the cyanogenmod 9 with the blue man blinking.. and it's past 10 mins and counting. still won't boot.
here's a copy of what my adb folder looks like. please let me know if i'm doing something wrong.
cthsuks said:
sorry i must've ended up clicking on the wrong link. so i went back to the previous post you put up.
now if you are having CWM custom recovery then
flash the cm rom again from it yup, i did that. i have the CM9 from cyanogenmod
and copy the boot.img from the rom zip file to the adb/fastboot folder
then flash this separately
yup, i created the adb folder by renaming the root-sensation-wind.zip file from your post. it didn't have the fastboot.exe in there, so i copied it from the SDK manager tool that i had installed previously when i downloaded the wrong file. i also copied the boot.img from the CM9 zip file as you suggested
connect the phone from bootloader to pc (phone reads fastboot usb after this) yup did that..
then this command
fastboot flash boot boot.img
yup did that, and it was completed
then reboot using
fastboot reboot
yup did that as well and it rebooted
thats all
but wait.. the sensation is still stuck at the cyanogenmod 9 with the blue man blinking.. and it's past 10 mins and counting. still won't boot.
here's a copy of what my adb folder looks like. please let me know if i'm doing something wrong.
Click to expand...
Click to collapse
Hey it's working?
If not reflash the rom again.. Without any wipe
Sent from my HTC Sensation 4G using xda premium
Below is a cheat sheet I've made to help others keep the commands they'll need and general information organized and consolidated in one place... When I first started using Android years ago I kept one of these so I could refer to it if I forgot a command or a small piece of info and I thought I'd share one for the m8.
Make sure to check out the note at the end of this post regarding Dottat's updated ADB files. They prevent the need to flash ruu's twice as you'll see outlined in this post.
Edit Note:I highly recommend running ruu's via adb. It may look more intimidating than the exe or hboot methods,
but if they were to fail you'd see exactly where it failed in the running log. You can avoid having to wait
for an initial boot of the stock rom if your intentions are to wipe to stock and then install a custom
recovery and whatever your rom/rom(s) of choice are. I personally wipe my phone from recovery, then
wipe via the adb commands below, run the ruu, and then factory reset from stock recovery. I'll then
install a custom recovery and my rom of choice. It's up to you, but I've found this to be the quickest
method of insuring a full-wipe to stock and then into my rom of choice. The wiping above is redundant
and not necessary, but I'll do it if I've got a problem I simply cannot figure out. To be honest the ruu should
wipe everything for you and then running a factory reset w/stock recovery installed should fix any
4g/LTE issues. ***Verizon ADB Information***
--MOST but NOT ALL of this is Universal (Not Carrier Dependent)--
All commands beginning with "fastboot" must be performed at Bootloader
All commands beginning with ADB are performed from a phone that is in Rom
-You may skip the "adb reboot bootloader" step if you're already
at the bootloader
Firmware/RUU/Recovery instructions are available in their specific threads
*This is just a cheat sheet*
Basic ADB Commands:
Recovery Flashing: (TWRP Current Standard)
adb reboot bootloader
fastboot flash recovery recoveryimgname.img
Firmware Flashing:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
*you should be prompted to flash a second time here*
fastboot flash zip firmwarename.zip
fastboot reboot-bootloader
HBoot Flashing:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip hbootfilename.zip
RUU Commands
Wipe By ADB:*optional*(though a wipe is recommended either by recovery or adb)
adb reboot bootloader
fastboot oem task 28
fastboot oem task 29
Install RUU via ADB:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.zip
Install RUU via HBoot:
Rename ruu .zip to 0P6BIMG.zip and copy to root of external sdcard
Boot to your bootloader and enter hboot if you're in fastboot mode
Hboot should automatically read the RUU file and begin unpacking (progress bar at top right)
Follow onscreen prompts after it unpacks...
*sdcard must be formatted to fat32 to read RUU* formatting the sdcard through the android os
will accomplish this. It will mount vfat when you read it by computer or in twrp this is okay.
SELinux Terminal Commands:
1) Grant su level permissions via terminal by typing "su"
2) Enable SELinux status by typing "setenforce x" where x is the variable below
setenforce 0 =Permissive
setenforce 1 =Enforcing
GPE Install Instructions:
Begin with SuperCID:***May no longer be necessary***
1) Get current cid information via;
fastboot oem readcid
Write down your current cid reading
2) Change your cid to 11111111 via;
fastboot oem writecid 11111111
(check cid again with fastboot oem readcid to varify)
3) Reboot to the bootloader
4) Following the reboot back to the bootloader
verify your cid is 11111111
And Then Install Rom Via:
5)Wipe /data; /cache; /system; Dalvik
6)Format /system; /data; /cache to f2fs -optional *Must use Elite Kernel for GPE 5.1*
7)Install Rom
8)Reboot
Remove GPE:***these are just my recommendations***
1) Revert CID via fastboot oem writecid (your stock cid ex: fastboot oem writecid VZW__001
2) Wipe everything /data, /cache, /system, /dalvik
Click Here for dottat's firmware and ruu master collection
Below, on this first page, dottat has linked a file containing updated adb files to be used when installing his ruu's. They correct the issues many have had requiring two flashes of his ruu's. Full information available through his posts in this thread. You can either replace the files in his .zip with your current adb folders files, or use it (after unzipping) as an updated lightweight adb interface folder.
jcole20 said:
Below is a cheat sheet I've made to help others keep the commands they'll need and general information organized and consolidated in one place... When I first started using Android years ago I kept one of these so I could refer to it if I forgot a command or a small piece of info and I thought I'd share one for the m8.
***Verizon ADB Information***
--MOST but NOT ALL of this is Universal (Not Carrier Dependent)--
All commands beginning with "fastboot" must be performed at Bootloader
All commands beginning with ADB are performed from a phone that is in Rom
-You may skip the "adb reboot bootloader" step if you're already
at the bootloader
Firmware/RUU/Recovery instructions are available in their specific threads
*This is just a cheat sheet*
Basic ADB Commands:
Recovery Flashing: (TWRP Current Standard)
adb reboot bootloader
fastboot flash recovery recoveryimgname.img
Firmware Flashing:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip firmwarename.zip
*you should be prompted to flash a second time here*
fastboot flash zip firmwarename.zip
fastboot reboot-bootloader
HBoot Flashing:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip hbootfilename.zip
RUU Commands
Wipe By ADB:*optional*
adb reboot bootloader
fastboot oem task 28
fastboot oem task 29
Install RUU via ADB:
adb reboot bootloader
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.zip
Install RUU via HBoot:
Rename ruu .zip to 0P6BIMG.zip and copy to root of external sdcard
Boot to your bootloader and enter hboot if you're in fastboot mode
Hboot should automatically read the RUU file and begin unpacking (progress bar at top right)
Follow onscreen prompts after it unpacks...
*sdcard must be formatted to fat32 to read RUU* formatting the sdcard through the android os
will accomplish this. It will mount vfat when you read it by computer or in twrp this is okay.
SELinux Terminal Commands:
1) Grant su level permissions via terminal by typing "su"
2) Enable SELinux status by typing "setenforce x" where x is the variable below
setenforce 0 =Permissive
setenforce 1 =Enforcing
GPE Install Instructions:
Begin with SuperCID:***May no longer be necessary***
1) Get current cid information via;
fastboot oem readcid
Write down your current cid reading
2) Change your cid to 11111111 via;
fastboot oem writecid 11111111
(check cid again with fastboot oem readcid to varify)
3) Reboot to the bootloader
4) Following the reboot back to the bootloader
verify your cid is 11111111
And Then Install Rom Via:
5)Wipe /data; /cache; /system; Dalvik
6)Format /system; /data; /cache to f2fs -optional *Must use Elite Kernel for GPE 5.1*
7)Install Rom
8)Reboot
Remove GPE:***these are just my recommendations***
1) Revert CID via fastboot oem writecid (your stock cid ex: fastboot oem writecid VZW__001
2) Wipe everything /data, /cache, /system, /dalvik <-- Optional
*(suggested to use oem task commands)*
3) Format back to ext4 for everything if you changed to f2fs for any reason
4) Run ruu
If ruu doesn't work properly...
5) Run ruu a second time
Some General Tips
-When typing a command like "fastboot flash recovery recoveryname.img" you can use the TAB key to
autocomplete a name or file directory... (This is true in just about every operating systems
command line or terminal interface) ex: if trying to go to C:\Windows and you're already in the
C:\ directory you simply need type "cd C:\w" and hit TAB and it should automatically complete the
field. If you happen to have a directory that comes before Windows alphabetically like "C:\Warez"
(not likely) hit Tab again and it will cycle through directories alphabetically.
Another example is I have twrp-2.8.5 and twrp-2.8.6 in my adb directory. So if it autocompletes
to "twrp-2.8.5.img", I hit tab again it will change to "twrp-2.8.6.img". In some instances you can
use this autocomplete feature to issue commands ie when using an apk decompiler/recompiler tool.
Instead of typing mkdir you can simply autotab to the correct command after typing "m" or "mk" etc.
-If you use the up arrow on your keyboard in Terminal/Command Prompt it will cycle through previous commands.
Example: When flashing firmware after "fastboot flash zip firmware.zip" when prompted to flash a second time you
can just hit UP Arrow on your keyboard and it will automatically go to your previous entry.
-I keep the latest RUU for my device in my adb/android studio (*/platform-tools) directory already
named "0P6BIMG.zip". This is a good practice simply because it streamlines the whole process so you
don't have to wait as a rather large file copies to said directory. I also keep a copy of said RUU
in a folder on my external sd-card. I do this so that if my computer, for whatever reason, was not
able to read the phones storage I can use the file manager in recovery to move it to root and RUU.
-If you have TiTanium Backup Pro you can set it to automatically update your apps. I like to keep an
updated copy of my apps on my external sd-card, my computer, and in cloud via GoogleDrive. This
makes restoring apps from a backup a painless process as I always have them available to me.
-I also keep a running backup of everything important to me on my computer. I have a folder
I've set up specifically for my running backups. Inside said folder I have a copy of my favorite
roms, my music, all the firmware for our device, the HBoot.zip(s), my pictures, all available RUUs,
an MD5 checking program, GApps packages, TWRP backups, TWRP .img(s), TWRP themes, and any other
tweaks/flashable.zips I find important. I highly suggest everyone who doesn't do this make this a
practice. It truly helps a lot.
EDIT: If someone wants me to upload the above as a .txt file I will.
Click to expand...
Click to collapse
That would be great in .txt format.
aaronpw0621 said:
That would be great in .txt format.
Click to expand...
Click to collapse
When I get home (about an hour) I'll upload a .txt of the commands.
HTC One (M8) CM12.1.1
Edit: Okay downloadable .txt file is in OP
jcole20 said:
When I get home (about an hour) I'll upload a .txt of the commands.
HTC One (M8) CM12.1.1
Edit: Okay downloadable .txt file is in OP
Click to expand...
Click to collapse
:good: :good:
@jcole20 a lot of your fastboot reflashing can be removed by the use of the HTC_fastboot I have posted in various places. It does it automatically
dottat said:
@jcole20 a lot of your fastboot reflashing can be removed by the use of the HTC_fastboot I have posted in various places. It does it automatically
Click to expand...
Click to collapse
Thanks @dottat I didn't know. I've only had to reflash once. And that was the first time I ran your ruu (5.0.1). Following that initial hiccup, everytime after it's completed successfully on the first try.
I'll check into that and note it in op. I just wanted to consolidate all the commands we commonly use for people who have trouble remembering them.
HTC One (M8) CM12.1.1
Edit: oh I didn't know you were talking about your ruu.exe(s) ... Yeah, I'm so used to using adb for everything. I've got your exe for lollipop but I've only run it once. (Prior to my pm about something lingering after a ruu) ... I still haven't figured that out BTW. I'll make note in the op that your exes make the ruu adb info obsolete. Thank you again for all your help and work.
jcole20 said:
Thanks @dottat I didn't know. I've only had to reflash once. And that was the first time I ran your ruu (5.0.1). Following that initial hiccup, everytime after it's completed successfully on the first try.
I'll check into that and note it in op. I just wanted to consolidate all the commands we commonly use for people who have trouble remembering them.
HTC One (M8) CM12.1.1
Edit: oh I didn't know you were talking about your ruu.exe(s) ... Yeah, I'm so used to using adb for everything. I've got your exe for lollipop but I've only run it once. (Prior to my pm about something lingering after a ruu) ... I still haven't figured that out BTW. I'll make note in the op that your exes make the ruu adb info obsolete. Thank you again for all your help and work.
Click to expand...
Click to collapse
No that's not what I am talking about. Lol
Download this. Unzip it and you will see what I mean
https://www.androidfilehost.com/?fid=95916177934554784
dottat said:
No that's not what I am talking about. Lol
Download this. Unzip it and you will see what I mean
https://www.androidfilehost.com/?fid=95916177934554784
Click to expand...
Click to collapse
Lol... okay. Why isn't this in your 5.0.1 ruu thread? I wish I had known about this a couple of weeks ago... Thanks though. I did a quick google search for htc_fastboot and what came up was a question you asked someone in one of your ruu threads. I went to the op and all I saw was the exe and ruu.zip so I assumed you were talking about the .exe. Hah
jcole20 said:
Lol... okay. Why isn't this in your 5.0.1 ruu thread? I wish I had known about this a couple of weeks ago... Thanks though. I did a quick google search for htc_fastboot and what came up was a question you asked someone in one of your ruu threads. I went to the op and all I saw was the exe and ruu.zip so I assumed you were talking about the .exe. Hah
Click to expand...
Click to collapse
Have you read the stickied thread in general section?
dottat said:
Have you read the stickied thread in general section?
Click to expand...
Click to collapse
To be honest dottat, I've read so much with regards to this phone in the last month since I got it I don't remember everything that I've read through. I think, with regards to your ruu's, I've mainly used your posted threads in the Verizon Android Development section. I linked your ruu's in the OP now and I used the stickied master list here, but I've only had this phone for a month so I never needed a 4.4.4 ruu (hence not needing to find that master list). Your lollipop ruu has been bumped somewhat regularly so it's the only one I've ever really looked through except when googling something and your 4.4.4 ruu in the same section has come up.
jcole20 said:
To be honest dottat, I've read so much with regards to this phone in the last month since I got it I don't remember everything that I've read through. I think, with regards to your ruu's, I've mainly used your posted threads in the Verizon Android Development section. I linked your ruu's in the OP now and I used the stickied master list here, but I've only had this phone for a month so I never needed a 4.4.4 ruu (hence not needing to find that master list). Your lollipop ruu has been bumped somewhat regularly so it's the only one I've ever really looked through except when googling something and your 4.4.4 ruu in the same section has come up.
Click to expand...
Click to collapse
Here's the post....
http://forum.xda-developers.com/showthread.php?p=56890497
I just gave you the latest and greatest above. Its the awesome sauce man.
dottat said:
Here's the post....
http://forum.xda-developers.com/showthread.php?p=56890497
I just gave you the latest and greatest above. Its the awesome sauce man.
Click to expand...
Click to collapse
Thank you! Heh, I've got the .exes and .zips of your 4.4.4 and 5.0.1 ruus saved. I will probably ruu back to stock again using the above just because... I've still never figured out what broke audiofx for me even after reverting to stock via your ruus. It's been driving me nuts.
HTC One (M8) CM12.1.1
Edit: I'm thinking I flashed V4A via a .zip and didn't realize it, so audiofx wasn't working, it was working as the drivers for audiofx and audiofx was working as the gui for v4a. That's the only explanation I can think of, because your ruu's have been great and I know they are working to revert me completely to stock.
Edit 2: I went ahead and ran a ruu with your updated adb file(s). As usual went off without a hitch and everything seems perfect... booting into my rom of choice now. As usual everything is perfect dottat... thanks!
Hi Everybody!
Im hungarian man and sorry very small speak English. Google Translate helps me.
I have an HTC U11 Black Dual SIM CID34 (4/64) phone. I opened the bootloader and installed TWRP the phone is S-ON status.
Everything is fine so far.
I copy the ROM to SD card and start the phone Recovery mode.
I selected the ROM from this list:
Link: Removed by System
I wanted to install this ROM
2PZCIMG_OCEAN_DUGL_O80_SENSE90GP_MR_HTC_Europe_2.33.401.10_Radio_8998-002772-1711161638_release_signed.zip
Link: Removed by System
TWRP always writes in an invalid ZIP format.
Your phone is not loading Android now. It starts to load but stops at the boot screen. I can boot my phone into Bootloader, Recovery, Download mode.
Thank you for your help!
Please if you write simply to write or step by step how to fix the phone.
Best regards: Szabolcs
kovsza said:
Hi Everybody!
Im hungarian man and sorry very small speak English. Google Translate helps me.
I have an HTC U11 Black Dual SIM CID34 (4/64) phone. I opened the bootloader and installed TWRP the phone is S-ON status.
Everything is fine so far.
I copy the ROM to SD card and start the phone Recovery mode.
I selected the ROM from this list:
Link: Removed by System
I wanted to install this ROM
2PZCIMG_OCEAN_DUGL_O80_SENSE90GP_MR_HTC_Europe_2.33.401.10_Radio_8998-002772-1711161638_release_signed.zip
Link: Removed by System
TWRP always writes in an invalid ZIP format.
Your phone is not loading Android now. It starts to load but stops at the boot screen. I can boot my phone into Bootloader, Recovery, Download mode.
Thank you for your help!
Please if you write simply to write or step by step how to fix the phone.
Best regards: Szabolcs
Click to expand...
Click to collapse
Try renaming the zip file to 2pzcimg.zip,, and place it on the root of your sdcard and boot into downloader mode. Hth, this looks to be an ruu so it will put your phone back to stock and wipe all but the sd card.
hammered58 said:
Try renaming the zip file to 2pzcimg.zip,, and place it on the root of your sdcard and boot into downloader mode. Hth, this looks to be an ruu so it will put your phone back to stock and wipe all but the sd card.
Click to expand...
Click to collapse
I'll try and give you feedback.
I start the phone Downloaded mode. Phone autodetect the SD card ZIP file. I pressed VolUp buttons... and nothing.
Error message: FAIL12 RU_ZIP_ERROR
What's next?
Here you have some details, but are for downgrade from Oreo to nougat (maybe could it works??)
https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481
kovsza said:
I'll try and give you feedback.
Click to expand...
Click to collapse
If you are on pie and trying to downgrade to oreo this cannot be done with out soff , and i do not think
Pie soff is supported,
hammered58 said:
If you are on pie and trying to downgrade to oreo this cannot be done with out soff , and i do not think
Pie soff is supported,
Click to expand...
Click to collapse
If this is the problem then is there an easy way to set it to S-OFF?
Pantumaca said:
Here you have some details, but are for downgrade from Oreo to nougat (maybe could it works??)
https://forum.xda-developers.com/u11/how-to/guide-downgrade-htc-u11-oreo-to-nougat-t3754481
Click to expand...
Click to collapse
This is the description I read. Based on what I described, I got to the version change. The version change failed. But in another place I read that in Download mode you can easily reinstall the previous version.
kovsza said:
This is the description I read. Based on what I described, I got to the version change. The version change failed. But in another place I read that in Download mode you can easily reinstall the previous version.
Click to expand...
Click to collapse
I have used this procedure to downgrade from oreo to nougat, but have not used it to from pie to oreo,
hammered58 said:
I have used this procedure to downgrade from oreo to nougat, but have not used it to from pie to oreo,
Click to expand...
Click to collapse
Then even that solution won't work.
kovsza said:
Then even that solution won't work.
Click to expand...
Click to collapse
Like i said I have not tried it, as far as i know once you are on pie there is no going back unless someone else knows a solution
hammered58 said:
Like i said I have not tried it, as far as i know once you are on pie there is no going back unless someone else knows a solution
Click to expand...
Click to collapse
I see if somebody knows the solution or tried it.
Nobody?
If You want to downgrade from Pie to Oreo. Its pretty easy and simple you has to follow same steps like Oreo to nougat downgrade but with some modifications:- (bootloader unlock is required)
1. I tried it on my own device it worked and it is s-on, So i don't know it works on s-off or not.
2. Download HTC Dev info tool from the below link
https://drive.google.com/file/d/1ubjDGNqCfIply-aRN8C7IQNb-YVkD4M7/view
3. Now connect your device to PC by turning on USB debugging in phone and open the info tool and click on GetDeviceInfo and it will show your device information in the tool.
4. If you want to change CID then follow this step otherwise skip to step 5. Change the CID to your desired CID and click on save.
5. Now change the misc version to the rom misc version which you downloaded for downgrade and click on save and apply changes.
6. Now download and install minimal adb and fastboot.exe in PC and open it and type "adb reboot download" and your phone boot to download mode and type "fastboot getvar all" and it will print your device information in the cmd itself and from their cross check your CID number whether it is changed to your required CID or not and also check the version number is blanked out or not. If it doesn't then something wrong you have done, so again start from step 2.
7. Download the Oreo RUU for your CID from the below link :-
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
8. Now Download BatchTool.exe from the provided link below
https://forum.xda-developers.com/showpost.php?p=67056758&postcount=4
9. Install the tool and and go to the location where you installed the tool generally it will be c:/Android/com now copy the RUU you downloaded for your CID to that folder and rename it to rom.zip for simplicity ie., c:/Android/com/rom.zip
10. Now Download RUU decrypt tool from the below link and extract the zip and drag and drop the rom.zip on to the RUU_decrypt_tool.exe present in the extracted folder.
https://forum.xda-developers.com/devdb/project/?id=15338#downloads
11. And An CMD will pop-up and ask for some yes and no details just accept the default settings with out changing anything and now the RUU decryption will start and after completing a folder will be created in the RUU decrypt tool folder and inside OUT folder look for "hosd_signed.img" and move it to the rom.zip folder ie., c:/Android/com/hosd_signed.img
12. Now open cmd and navigate to the com folder by using by using cd command.
13. Now cross-check whether you are in bootloader mode or not, if yes then proceed to next step otherwise reboot your phone to bootloader mode by typing "htc_fastboot reboot bootloader" (htc_fasboot is a file present in com folder so you need to be in com folder to execute that commands from cmd).
14. Now type "htc_fastboot flash hosd hosd_signed.img" and wait for it to flash and after you see written successful then reboot to RUU mode by typing "htc_fastboot oem rebootRUU" l
15. On booting your phone to RUU mode type "htc_fastboot flash zip rom.zip" (rom.zip is file name of your RUU that you downloaded and renamed to rom.zip).
16. Now the flashing process should start and wait for some time until it finishes.
17. Now you have successful Downgraded from PIE to OREO with your desired CID..,.,.,.,.,:fingers-crossed::fingers-crossed:
Ryü[email protected] said:
If You want to downgrade from Pie to Oreo. Its pretty easy and simple you has to follow same steps like Oreo to nougat downgrade but with some modifications:- (bootloader unlock is required)
1. I tried it on my own device it worked and it is s-on, So i don't know it works on s-off or not.
2. This step is optional and this is only for those who wants to change the CID of their device if not skip to step 4. Just download "HTC dev infotool" turn on USB debugging in phone and connect your device to PC and open HTC dev info tool and click on Getdevice info and it will show you about your device information and from their change the CID of your device to your required CID by changing the CID field and hit save and click apply all changes.
3. Now download and install minimal adb and fastboot.exe in PC and open it and type "adb reboot download" and your phone boot to download mode and type "fastboot getvar all" and it will print your device information in the cmd itself and from their cross check your CID number whether it is changed to your required CID or not. If it doesn't then something wrong you have done, so again start from step 2.
4. Download the Oreo RUU for your CID from the below link :-
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
5. Now Download BatchTool.exe from the provided link below
https://forum.xda-developers.com/showpost.php?p=67056758&postcount=4
5. Install the tool and and go to the location where you installed the tool generally it will be c:/Android/com now copy the RUU you downloaded for your CID to that folder and rename it to rom.zip for simplicity ie., c:/Android/com/rom.zip
6. Now Download RUU decrypt tool from the below link and extract the zip and drag and drop the rom.zip on to the RUU_decrypt_tool.exe present in the extracted folder.
https://forum.xda-developers.com/devdb/project/?id=15338#downloads
7. And An CMD will pop-up and ask for some yes and no details just accept the default settings with out changing anything and now the RUU decryption will start and after completing a folder will be created in the RUU decrypt tool folder and inside OUT folder look for "hosd_signed.img" and move it to the rom.zip folder ie., c:/Android/com/hosd_signed.img
8. Now open cmd and navigate to the com folder by using by using cd command.
9. Now cross-check whether you are in download mode or not, if yes then proceed to next step otherwise reboot your phone to download mode by typing "htc_fastboot reboot-download" (htc_fasboot is a file present in com folder so you need to be in com folder to execute that commands from cmd).
10. Now type "htc_fastboot flash hosd hosd_signed.img" and wait for it to flash and after you see written successful then reboot to RUU mode by typing "htc_fastboot oem rebootRUU" l
11. On booting your phone to RUU mode type "htc_fastboot flash zip rom.zip" (rom.zip is file name of your RUU that you downloaded and renamed to rom.zip).
12. Now the flashing process should start and wait for some time until it finishes.
13. Now you have successful Downgraded from PIE to OREO with your desired CID..,.,.,.,.,:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
is it work on single sim devices to change cid??
filandry said:
is it work on single sim devices to change cid??
Click to expand...
Click to collapse
I think it works but always have a backup before doing anything because i tested it on my HTC dual sim 6/128GB dual sim variant and successfully changed CID from HTC__J15 to HTC__060 and downgraded from PIE to OREO
Ryü[email protected] said:
If You want to downgrade from Pie to Oreo. Its pretty easy and simple you has to follow same steps like Oreo to nougat downgrade but with some modifications:- (bootloader unlock is required)
1. I tried it on my own device it worked and it is s-on, So i don't know it works on s-off or not.
2. This step is optional and this is only for those who wants to change the CID of their device if not skip to step 4. Just download "HTC dev infotool" turn on USB debugging in phone and connect your device to PC and open HTC dev info tool and click on Getdevice info and it will show you about your device information and from their change the CID of your device to your required CID by changing the CID field and hit save and click apply all changes.
3. Now download and install minimal adb and fastboot.exe in PC and open it and type "adb reboot download" and your phone boot to download mode and type "fastboot getvar all" and it will print your device information in the cmd itself and from their cross check your CID number whether it is changed to your required CID or not. If it doesn't then something wrong you have done, so again start from step 2.
4. Download the Oreo RUU for your CID from the below link :-
https://docs.google.com/spreadsheets/d/15JL3tRWDSVOUKo_revEYtQ_tRcOSJ0vWcvk8a7TK8Hk/edit?usp=sharing
5. Now Download BatchTool.exe from the provided link below
https://forum.xda-developers.com/showpost.php?p=67056758&postcount=4
5. Install the tool and and go to the location where you installed the tool generally it will be c:/Android/com now copy the RUU you downloaded for your CID to that folder and rename it to rom.zip for simplicity ie., c:/Android/com/rom.zip
6. Now Download RUU decrypt tool from the below link and extract the zip and drag and drop the rom.zip on to the RUU_decrypt_tool.exe present in the extracted folder.
https://forum.xda-developers.com/devdb/project/?id=15338#downloads
7. And An CMD will pop-up and ask for some yes and no details just accept the default settings with out changing anything and now the RUU decryption will start and after completing a folder will be created in the RUU decrypt tool folder and inside OUT folder look for "hosd_signed.img" and move it to the rom.zip folder ie., c:/Android/com/hosd_signed.img
8. Now open cmd and navigate to the com folder by using by using cd command.
9. Now cross-check whether you are in download mode or not, if yes then proceed to next step otherwise reboot your phone to download mode by typing "htc_fastboot reboot-download" (htc_fasboot is a file present in com folder so you need to be in com folder to execute that commands from cmd).
10. Now type "htc_fastboot flash hosd hosd_signed.img" and wait for it to flash and after you see written successful then reboot to RUU mode by typing "htc_fastboot oem rebootRUU" l
11. On booting your phone to RUU mode type "htc_fastboot flash zip rom.zip" (rom.zip is file name of your RUU that you downloaded and renamed to rom.zip).
12. Now the flashing process should start and wait for some time until it finishes.
13. Now you have successful Downgraded from PIE to OREO with your desired CID..,.,.,.,.,:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
It's not working.error sad you must change version number.
What is the best way for change version number?
Who to change cid and version number?
mehrdad_esmaeeli said:
It's not working.error sad you must change version number.
What is the best way for change version number?
Click to expand...
Click to collapse
Edited the post and forgot to add changing the version number check from step 2 again. If that too not work run this command "adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1 seek=2208 count=16" it will blank out misc version and follow the instructions i posted above.
Ryü[email protected] said:
Edited the post and forgot to add changing the version number check from step 2 again. If that too not work run this command "adb shell dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1 seek=2208 count=16" it will blank out misc version and follow the instructions i posted above.
Click to expand...
Click to collapse
Ok Finally I could
Tnx so much