Related
I am sorry to announce, but I am pulling this tutorial. Tutorial is not meant for branded phones and recently I am getting few of those asking for help!
Sorry unbranded device owners, but my intention is to have brick free world!
Have a nice day! And safe flashing.
P.s. FYI, new boot loader can be unlocked using htcdev.com and locked again using the same.
/Edzz
good to know if somthing goes wrong and must be done in warranty time
can I use your guide for my thread ? I will give you credit.. thanks.
Why not do it the easy way since you're already S-OFF?
Take the ENG HBOOT found here and put the PG88IMG.zip in the root of your SD card
Boot into the bootloader (Volume Down + POWER)
Go into FASTBOOT mode
The bootloader will automagically detect your new HBOOT and install it
After rebooting your phone you can install any RUU you want. That will bring HBOOT back to the installed original
Make sure you make a good backup up front and be carefull what RUU to flash. The newer ones will overwrite HBOOT with version 0.98.0002, which, up to this date, can't be put to S-OFF yet by Alpharevx. I recommand you install the oldest RUU version you can find. A list of original ROMS can be found here
Good luck!
@nodeffect
Feel free.
@jorgen2009
such approach won't work with Alpharev hboot. They appear to have kinda locked it by making it appear ar 6.x Hboot version. That means, that bootloader will bypass upgrade. Been there, tried that, didn't work
chiekurz said:
@nodeffect
Feel free.
@jorgen2009
such approach won't work with Alpharev hboot. They appear to have kinda locked it by making it appear ar 6.x Hboot version. That means, that bootloader will bypass upgrade. Been there, tried that, didn't work
Click to expand...
Click to collapse
The original ENG HBOOT didn't work if i recall correctly. Redownload the ENG-HBOOT and you'll notice the version has changed to a number higher than Alpharev's. It DOES work now, in fact, my phone is S-ON again as we speak
Will have to try that again.
jorgen2009 said:
Why not do it the easy way since you're already S-OFF?
Take the ENG HBOOT found here and put the PG88IMG.zip in the root of your SD card
Boot into the bootloader (Volume Down + POWER)
Go into FASTBOOT mode
The bootloader will automagically detect your new HBOOT and install it
After rebooting your phone you can install any RUU you want. That will bring HBOOT back to the installed original
Make sure you make a good backup up front and be carefull what RUU to flash. The newer ones will overwrite HBOOT with version 0.98.0002, which, up to this date, can't be put to S-OFF yet by Alpharevx. I recommand you install the oldest RUU version you can find. A list of original ROMS can be found here
Good luck!
Click to expand...
Click to collapse
So i downloaded 2 files:
The PG88IMG.zip and eng_hboot
what do i put on my sd card, only PG88IMG.zip or both of them?
.sh4d0w. said:
So i downloaded 2 files:
The PG88IMG.zip and eng_hboot
what do i put on my sd card, only PG88IMG.zip or both of them?
Click to expand...
Click to collapse
Only the PG88IMG.zip, don't rename or extract it or it won't work, just put the file in the root of your SD card
So what is the use of Eng S-Off.rar?
And another question the RUU is an .exe?
And is this old enough RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed ?
Thanks.
LE: i flashed the pg88img.zip and i am still Alpharevx hboot 6.xxxxx etc (but the update was successful)
Maybe... if i flash a RUU? I just wanted to get eng s-off.. don't want to get s-on now
.sh4d0w. said:
So what is the use of Eng S-Off.rar? [/QUOTE
Look at this thread
And another question the RUU is an .exe?
Click to expand...
Click to collapse
yes, it's direct from HTC and unfortunately can only be run from within Windows
And is this old enough RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed ?
Click to expand...
Click to collapse
yes, that comes with the HBOOT 0.98.0000
Thanks.
Click to expand...
Click to collapse
your welcome
LE: i flashed the pg88img.zip and i am still Alpharevx hboot 6.xxxxx etc (but the update was successful)
Maybe... if i flash a RUU? I just wanted to get eng s-off.. don't want to get s-on now
Click to expand...
Click to collapse
just check again in fastboot, ENG HBOOT version has changed to 6.98.2000 iirc. After running the RUU it should be 0.98.0000 again as ENG HBOOT can be overwritten in contrast to the AlphaRevX HBOOT. If you only want ENG HBOOT don't flash the RUU obviously
Click to expand...
Click to collapse
Ok i just checked.
I have like this
--- AlphaRev ---
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
So nothing changed.... and i did the update like... 5 times
It asks vol + to install update
And after it's finished
Power down to reboot.
Maybe i got the wrong file? The PG88IMG.zip attached here http://forum.xda-developers.com/showthread.php?t=1113820
.sh4d0w. said:
Ok i just checked.
I have like this
--- AlphaRev ---
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
So nothing changed.... and i did the update like... 5 times
It asks vol + to install update
And after it's finished
Power down to reboot.
Maybe i got the wrong file? The PG88IMG.zip attached here http://forum.xda-developers.com/showthread.php?t=1113820
Click to expand...
Click to collapse
You can try with this modified ENG Hboot for devices with AlpharevX
Please, report if works
heavyhms said:
You can try with this modified ENG Hboot for devices with AlpharevX
Please, report if works
Click to expand...
Click to collapse
Nope.... doesn't work at all. Not even loading.
.sh4d0w. said:
Nope.... doesn't work at all. Not even loading.
Click to expand...
Click to collapse
Try to re-download Eng Hboot (normal and modified) after deleting browser cache. Disable antivirus software during download and transfer to microsd.
Do not download file directly with desire S browser: use a pc
You can try also with a different microsd card
.sh4d0w. said:
Nope.... doesn't work at all. Not even loading.
Click to expand...
Click to collapse
Should be the right version...
BTW I changed the link in my first post here to this one. I accidently posted the wrong version
BTW...... the original eng hboot is 1 mb and this modified one is only 260 kb ???
Maybe that's why it doesn't work.
In winrar i have like this
Name__________________Size________Packed
engHBOOToverARX.img___1.048.576____262.273
Added your guide to my thread. Thanks for this one, it's very useful.
p.s. you got a typo for the title of this thread. "Tutorial", not totutial... please correct it, thanks
I did it.. using the adb comands in first page..
LE: Great! Alpharev beta site doesn't work.....stuck with stock lol ))
LE2: New alphareve+unrevoked site http://revolutionary.io/ Back to S-OFF
chiekurz said:
(Windows only? Not sure if RUU works on other platforms)
With thanks to user Murchelago for providing adb method to restore stock boot and HTC for providing RUU's here is step by step, how to return to stock after Alpharevx S-Off.
Prerequisites:
Debugging mode on
Root access
Hboot.img (attached)
RUU for stock restore. Can be downloaded here: http://forum.xda-developers.com/showthread.php?t=1002506
How to:
1. Put the hboot.img you want to flash in the root of the sdcard.
2. In cmd run the following commands (after each command press enter):
adb devices
adb shell
su
dd if=/dev/block/mmcblk0p18 of=/sdcard/backup.img
dd if=/sdcard/hboot.img of=/dev/block/mmcblk0p18
reboot bootloader
3. RUN Downloaded RUU
4. You are on stock again!
After running ADB commands and rebooting into bootloader, you will get security warning. This is normal, just continue with flashing RUU.
Worked for me perfectly 3 times without any issues. However issues might occur and I can not take any responsibility for them. Use this tutorial on your own responsibility
Click to expand...
Click to collapse
I can confirm that you CANNOT just RUU a device. As the name implies, ROM Update Utility.
I followed everything on the first page and can confirm that I've successfully reverted back to HBOOT 0.98.0000.
AFAIK my phone was flashed with the hTC_Asia_WWE_1.31.707.2 on stock.
I tried to RUU using the oldest firmware that I can find, HTC_Europe_1.28.401.1. But it gave me the error 131 (AFAIK) customer ID error. About language and stuffs. Model ID, etc.
So I tried to RUU with the oldest hTC_Asia_WWE_1.31.707.2 (the oldest that I can find that is an ASIA one.). Then it gave me the error 140 (bootloader error). The readme doesn't have any information on this one, even on the net for HTC Saga.
So I tried to RUU with the "LATEST" hTC_Asia_WWE_1.48.707.1 that I found and everything works well. I really am not quite sure why I was not able to "downgrade", just "upgrade".
AFAIK i just updated my radio to the latest 20.28I.30.085AU_3805.06.02.03_M found on the hTC_Asia_WWE_1.48.707.1 when I was S-OFFed. It may have something to do with it.
Just an additional info. I'm now S-ON and on-stock hTC_Asia_WWE_1.48.707.1_20.28I.30.085AU_3805.06.02.03_M
Hi,
After running with revolutionary and my rooted stock rom 1.47.401.4, I got yesterday a new OTA with 2.10.401.4 (2.3.5 and sense 3).
When trying to install it, it failed (blue android with big "!" on my screen)
First I downgraded my hboot back to 0.98.0000, but than I did something stupid .
I flash my hboot to the one provided with the OTA 2.00.0002, incl radio and all other stuff from the firmware.zip.
Now I ended up with a *** LOCKED *** HBOOT 2.00.0002, but also a 1.47.401.4 rom with android.
I tried to use the RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed.exe from windows, but that fails as the hboot has the incorrect version.
THe other thing I could do is go back to a 0.98 HBOOT, but that doesn't work either. the rom is ***LOCKED***, I have no root and it's S-ON.
I also searched for an RUU_Sage_HTC_Europe_*2.10.401.4*.exe as that might work because the HBOOT has the right version, but I could not find anything like that
Does anyone have an idea how I can go forward or how to go back ??
My phone is alive again as used the recovery.img procedure below and installed Saga3D 3.0. After that, I tried also the RUU installation to fully go back to stock, but that doesn't work. It complains about a security failure in hboot screen. I locked it back with 'fastboot oem lock', but that doesn't make the RUU work either.
lessimp said:
THe other thing I could do is go back to a 0.98 HBOOT, but that doesn't work either. the rom is ***LOCKED***, I have no root and it's S-ON.
Click to expand...
Click to collapse
did u try that or u think that wont work?
Before I updated to 2.00.0002, I created a dd-backup on the sdcard for the 0.98.000
when I however use adb to connect, I don't see how I can restore that back without root. I also didn't see the sdcard mounted
I was also thinking ....
Would it maybe also be possible to create a PG88IMG.zip with all the right software for 1.47.401.4 ? and restore that via recovery ? would the current hboot allow a downgrade ?
Today I was able to get the **LOCKED*** off to UNLOCKED via htcdev.com
In the thread http://forum.xda-developers.com/showthread.php?t=1299438
I found this (identical to my problem)
If anyone has the same problem and has hboot-2.00.0002 & S-ON you have to unlock the bootloader via htcdev.com site following all the steps and flash the EXT4 Recovery via FASTBOOT and NOT ADB.!!
Then go to recovery and flash any custom rom.
I don't unserstand what I have to do next. ADB does not work anymore, and only fastboot is available. I downloaded an EXT4 recovery (4EXTRecovery_v2.1.0_saga.zip) which have me an recovery.img and a META-INF folder.
When I name the zip image update.zip, and run
C:\android>fastboot.exe update update.zip
it fails with ...
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
How to I proceed to get it working ?
BTW, HBOOT is UNLOCKED but still S-ON
Please help
you already update hboot right. try this
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed
from here.
budingyun said:
you already update hboot right. try this
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed
from here.
Click to expand...
Click to collapse
You can RUU with that correct version or follow my instructions to achieve custom recovery/rom since you are already "unlocked":
Skanob said:
You should be able to change your recovery without any problem if your s-off or unlocked 2.xx.xx hboot s-on.
1. Get 4ext recovery.img
2. connect phone on fastboot
3. In cmd use these command to push the recovery image:
fastboot flash recovery D:\recovery.img (<- should be directory of 4ext recovery image)
fastboot reboot-bootloader
Now you should have 4ext recovery.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
From here on you can now flash custom ROMs that you would like that is compatible to Desire S.
How to flash HBOOT v1.17.2008?
I've got the engineering HBOOT from here, but have not been able to find the information on how to flash it.
Any idea?
Look in the dev section there is a way to flash that hboot think needs to be in a IMG.zip there is one around just search in dev section
Any link?
The search there seems to be really hard!
I'm on my phone give me a min ill look
http://forum.xda-developers.com/showpost.php?p=20681060&postcount=22
There is the IMG.zip chesk md5sum ans place in sdcard boot into bootloader ans should flash hboot back
You flash in fastboot, there is a guide here:
http://android-dls.com/wiki/index.php?title=Fastboot
If you currently have hboot 1.20 the fastboot flash commands are disabled though.
There is a thread on firmware versions in the development section that might help. Also:
http://forum.xda-developers.com/archive/index.php/t-1203784.html
Sensation XE tbc
Even then I think you need to be s-off to downgrade hboot
I was already at S-OFF w/ 1.17.1111.
I've put that ZIP and "flashed" from the HBOOT.
Now my unit can only go to the HBOOT (it says ENS S-OFF).
But doesn't boot any more.
I've tried to re-flash my previous v1.17.1111 but I still get 1.17.2008.
NOW WHAT?
Your take out the IMG.zip out of sdcard and your phone should boot right back up
Try to flash the eng hboot img from fastboot?
Sensation XE tbc
DONE
Now I'm back up and running.
Thanks to everyone.
Does anybody know where to get an hboot image v1.09 or below?
Can it be extracted from an RUU file (not shure about this)? Any instructions on this anywhere? (I'll go and search myself after this post - but any hints are welcome).
rootrider said:
Does anybody know where to get an hboot image v1.09 or below?
Can it be extracted from an RUU file (not shure about this)? Any instructions on this anywhere? (I'll go and search myself after this post - but any hints are welcome).
Click to expand...
Click to collapse
Its in the T-Mobile 1.84 ruu. Search how to extract ROM packages from ruus. Its a fairly easy process and you will end up with a ROM.zip that contains everything, including that hboot version.
Sent from my HTC One S using Tapatalk 2
You can extract hboot images from RUUs and OTAs. In RUUs it is directly in rom.zip, in OTAs it is in firmware.zip. I posted some here: http://forum.xda-developers.com/showthread.php?p=31108359#post31108359 It includes 1.06.
Your hboot sits in mmcblk0p12. I doubt we can write to it, and if we can I fear brickage. Be careful.
-Jobo
is there any known issues with flashing recovery onto a device with 1.09?? I have 1.09 and i cant get any recoveries to stick.
Here is the hboot you requested. The link will last until I clean up my dropbox folder.
https://dl.dropbox.com/s/qjtzpt4eu7ts4xp/hboot_8960_1.09.0000_20120402_signedbyaa.img?dl=1
Enzopreme said:
is there any known issues with flashing recovery onto a device with 1.09?? I have 1.09 and i cant get any recoveries to stick.
Click to expand...
Click to collapse
I had this issue when I first tried to flash a new recovery. I had to flash the interim CWM recovery by Paul Brian first then updated to twrp at a later time. Below is a link to the recovery that worked for me when I had the problem.
http://forum.xda-developers.com/showthread.php?t=1579584
Hi everyone..
I am sitting on a One S which has an unlocked bootloader, is not S-off, Hboot 2.15.
Previously was rooted and had Viper Rom installed 3.1, experienced lot of random reboots, tried to go S-OFF with rumrunner and moonshine, without it working.
Tried to return to a nandroid backup (TrickDroid 9.0) but now system is not responding and results in a reboot after 1-2 minutes after rom is booted.
I would like to return to Stock Rom with a RUU, but I can't seem to find the right one and I really need some help..
Even if I found the right one I don't know how to install it because phone keeps rebooting and fastboot doesn't seem to work on Win 8.
HELP!!
Okay. I got fastboot to work on my girlfriends computer and windows 7..
I got the following from running "fastboot getvar all":
Code:
<bootloader> version: 0.5
<bootloader> version-bootloader: 2.15.0000
<bootloader> version-baseband: 1.15.50.05.29
<bootloader> version-spld: None
<bootloader> version-microp: None
<bootloader> version-main:
<bootloader> version-misc: PVT SHIP S-ON
<bootloader> serialno: H*************
<bootloader> imei: 35***********
<bootloader> product: vle
<bootloader> platform: HBOOT-8960
<bootloader> modelid: PJ4010000
<bootloader> cidnum: T-MOB101
<bootloader> battery-statis: good
<bootloader> battery-voltage: 3867mV
<bootloader> partition-layout: Generic
<bootloader> security: on
<bootloader> buildmode: SHIP
<bootloader> boot-mode: FASTBOOT
<bootloader> cimmitno-bootloader: dirty-64bedd38
<bootloader> hbootpreupdate: 11
<bootloader> gencheckpt: 0
Which RUU should I get my hands on?
And do I need to run any fastboot commands before I try installing the RUU?
same
i've ****d mine to lmao
I tried all the RUU's on the RUU page from one of the sticky posts that had anything to do with T-mobile (since the device came with that as a splash screen) or Europe editions without any positive outcome.
I received Error 130 or 131 at all RUU installation that had either "Europe" or "TMO" in them..
I will keep on trying to find the right RUU, but I would really appreciate if someone had the answer and spoke up..
Thanks!
Hammerbak said:
I tried all the RUU's on the RUU page from one of the sticky posts that had anything to do with T-mobile (since the device came with that as a splash screen) or Europe editions without any positive outcome.
I received Error 130 or 131 at all RUU installation that had either "Europe" or "TMO" in them..
I will keep on trying to find the right RUU, but I would really appreciate if someone had the answer and spoke up..
Thanks!
Click to expand...
Click to collapse
I have not seen a RUU that had a radio version that high. The highest version I have seen is 1.13. I think that's the problem.
Is there no way to downgrade the radio?
I mean I have access to fastboot and TWRP recovery..?
Maybe by using a nand backup or so?
Sent from my C6603 using xda app-developers app
Hammerbak said:
Is there no way to downgrade the radio?
I mean I have access to fastboot and TWRP recovery..?
Maybe by using a nand backup or so?
Sent from my C6603 using xda app-developers app
Click to expand...
Click to collapse
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
---------- Post added at 09:47 AM ---------- Previous post was at 09:38 AM ----------
808phone said:
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
Click to expand...
Click to collapse
Do a search on your radio version: google 1.15.50.05.29
Are you in the US? US T-Mobile??
Anyway, this was the closest info I found:
http://forum.xda-developers.com/showthread.php?t=2520005
808phone said:
AFAIK there is no way unless you are S-OFF. I'm not sure how you got a radio version that high. Someone with more knowledge needs to chime in.
---------- Post added at 09:47 AM ---------- Previous post was at 09:38 AM ----------
Do a search on your radio version: google 1.15.50.05.29
Are you in the US? US T-Mobile??
Anyway, this was the closest info I found:
http://forum.xda-developers.com/showthread.php?t=2520005
Click to expand...
Click to collapse
Well, no I'm not in the US. I live in Denmark.
The phone however was bought in Germany 2 years ago, and was delivered from T-mobile I think.
I will give this a try.
However the reason I want to get back to STOCK is due to getting S-OFF.
If I can get the phone working as it is now with TrickDroid 9.0 ROM that would also suffice. At least for quite some time.
The problem I have with the ROM is that "system" stops responding on boot.
I am thinking that this problem could be due to kernel incompatibility because the phone had the Viper One ROM before, which I think flashed another kernel together with the ROM.
Could this be the problem and could it be solved with flashing a new kernel?
However is it possible to flash a kernel without the use of the recovery?
I can't mount the internal memory and the phone has no slot for a SD card
Again.. Thanks!
I would post here:
http://forum.xda-developers.com/showthread.php?t=2110195&page=183
This seems to be the place to get help.
Did you do an md5 on the files before flashing? Do you remember flashing boot.img from TrickDroid?
808phone said:
I would post here:
http://forum.xda-developers.com/showthread.php?t=2110195&page=183
This seems to be the place to get help.
Did you do an md5 on the files before flashing? Do you remember flashing boot.img from TrickDroid?
Click to expand...
Click to collapse
Already did post in there, with no responses so far..
Well I had TrickDroid 9.0 running fine before I updated to Viper One ROM, and this was when problems started happening.
Then I went back with a NAND restore from recovery..
I don't remember flashing the boot.img, as I thought that followed along when I flashed the TrickDroid ROM, but since I think that doing a NAND recovery, doesn't bring a long the kernel I guess that if I installed the kernel from TrickDroid I could get the phone working with this.. What do you think?
Which file contains the kernel..? Is that the boot.img?
Once again, thanks for putting an interest in this post and helping me out! You're a lifesaver so far!
If you are not s-off then you need to flash the boot.IMG.
If you didn't do this, then could be the problem. AFAIK the boot.IMG contains the kernel.
http://forum.cyanogenmod.com/topic/79408-fastboot-flash-boot-bootimg/
Here's another link that might help.
http://www.guidingtech.com/12705/solve-boot-loop-htc-one-x-custom-rom/
Latest radio for WWE devices was 1.15 and it's not a problem you have that. For me it proved to be better than 1.20 which is coming from the leaked firmware 2.16 so it's unofficial. You can't flash a different radio unless you're S-Off or have a lower hboot (1.09 or below) which you don't have. Stay with 1.15 it is OK
If you're S-On you MUST flash the ROM kernel EVERY time after you flash a ROM. This is done by extracting the boot.img from the ROM ZIP and flash it via fastboot command (fastboot flash boot boot.img). Also no nandroid restore will flash back the kernel from the backup since it is not possible to write to that partition if you're S-On
Now, what options do you have... First you must decide WHICH ROM do you want on your phone. If it's latest Viper you would like, fine, it's a very good ROM, stable and with lot of customization and support. What you should do is like this:
1. Download the ROM, save it on your pc and check MD5 sum
2. Extract the boot.img from it. This is a little bit tricky since Viper use an Aroma installer and it's made for both 2.15 and 2.16 hboots. So the boot.img is not in the ususal place in the zip file (that is the root of it) and also it is not called plain boot.img. It is located somewhere in the ZIP folders (sorry but I don't use Viper and don't have the zip at hand to tell you exactly where to look) and it should be named something like boot_2.15.img (or something like this). Look into the ZIP and try to locate this file, you should find 2 files named similar one with 2.15 and one with 2.16 in their names. The one you need is the one containing 2.15 in the name. Extract that one on your pc
3. I assume that you have ADB/fastboot working and you can launch the fastboot command from any directory on your pc (it's in the PATH). If not it could be that command will not work. In this case copy the extracted boot_2.15.img in the folder where you have fastboot (usually Android-SDK/platform-tools) and open a command prompt there
4. Restart the phone in recovery and mount the USB storage from it. You should see it after a while on your PC. Don't worry if it doesn't appear instantly, but it shouldn't take more than 1-2 min. Eventually unplug the phone and plug it again into USB. If you cannot mount the USB and have it accessible from PC we have to try the ADB Sideload but first we'll see if you get there and we need this. For now I presume you can mount USB and you can access it from PC. OK, now copy the ROM ZIP on your sdcard in a folder you'll remember
5. Now flash the ROM in recovery as you normal do and wipe cache/dalvik when prompted to
6. Restart your phone in bootloader and plug it in the USB. Go to fastboot and on screen you should see "FASTBOOT USB". Issue on the pc in the opened command prompt the command "fastboot devices". It should return the device id and that's the proof the device is recognised by the fastboot command. If you have returned an blank response or something like an error, check if drivers and everything on your PC is installed properly for fastboot to work
7. If "fastboot devices" returns something (should look like "FA2BGW... fastboot") then you're good to go. Issue from the same command prompt the command "fastboot flash boot boot_2.15.img" (replace boot_2.15.img with the actual name of the file you have extracted from the ROM zip)
8. Restart to system
At this point you should have Viper 3.1.0 flashed and working. Check and setup the ROM then you may want to download the 2 OTA updates and install them to get to the latest 2.1.3
let us know how it went and where are you stuck. Note every error message you might get and better ask first than be sorry later...
Good luck
Rapier said:
Latest radio for WWE devices was 1.15 and it's not a problem you have that. For me it proved to be better than 1.20 which is coming from the leaked firmware 2.16 so it's unofficial. You can't flash a different radio unless you're S-Off or have a lower hboot (1.09 or below) which you don't have. Stay with 1.15 it is OK
Click to expand...
Click to collapse
Could you maybe provide a link to the WWE RUU that has the 1.15 Radio? I have been searching almost everywhere unable to find it and I would really like to go back to stock so that I can use rumrunner or moonshine to get S-off and avoid all the hassle that I have right now.. xD
Rapier said:
If you're S-On you MUST flash the ROM kernel EVERY time after you flash a ROM. This is done by extracting the boot.img from the ROM ZIP and flash it via fastboot command (fastboot flash boot boot.img). Also no nandroid restore will flash back the kernel from the backup since it is not possible to write to that partition if you're S-On
Now, what options do you have... First you must decide WHICH ROM do you want on your phone. If it's latest Viper you would like, fine, it's a very good ROM, stable and with lot of customization and support. What you should do is like this:
1. Download the ROM, save it on your pc and check MD5 sum
2. Extract the boot.img from it. This is a little bit tricky since Viper use an Aroma installer and it's made for both 2.15 and 2.16 hboots. So the boot.img is not in the ususal place in the zip file (that is the root of it) and also it is not called plain boot.img. It is located somewhere in the ZIP folders (sorry but I don't use Viper and don't have the zip at hand to tell you exactly where to look) and it should be named something like boot_2.15.img (or something like this). Look into the ZIP and try to locate this file, you should find 2 files named similar one with 2.15 and one with 2.16 in their names. The one you need is the one containing 2.15 in the name. Extract that one on your pc
3. I assume that you have ADB/fastboot working and you can launch the fastboot command from any directory on your pc (it's in the PATH). If not it could be that command will not work. In this case copy the extracted boot_2.15.img in the folder where you have fastboot (usually Android-SDK/platform-tools) and open a command prompt there
4. Restart the phone in recovery and mount the USB storage from it. You should see it after a while on your PC. Don't worry if it doesn't appear instantly, but it shouldn't take more than 1-2 min. Eventually unplug the phone and plug it again into USB. If you cannot mount the USB and have it accessible from PC we have to try the ADB Sideload but first we'll see if you get there and we need this. For now I presume you can mount USB and you can access it from PC. OK, now copy the ROM ZIP on your sdcard in a folder you'll remember
5. Now flash the ROM in recovery as you normal do and wipe cache/dalvik when prompted to
6. Restart your phone in bootloader and plug it in the USB. Go to fastboot and on screen you should see "FASTBOOT USB". Issue on the pc in the opened command prompt the command "fastboot devices". It should return the device id and that's the proof the device is recognised by the fastboot command. If you have returned an blank response or something like an error, check if drivers and everything on your PC is installed properly for fastboot to work
7. If "fastboot devices" returns something (should look like "FA2BGW... fastboot") then you're good to go. Issue from the same command prompt the command "fastboot flash boot boot_2.15.img" (replace boot_2.15.img with the actual name of the file you have extracted from the ROM zip)
8. Restart to system
At this point you should have Viper 3.1.0 flashed and working. Check and setup the ROM then you may want to download the 2 OTA updates and install them to get to the latest 2.1.3
let us know how it went and where are you stuck. Note every error message you might get and better ask first than be sorry later...
Good luck
Click to expand...
Click to collapse
Thanks.
There's definitively a lot I will have to work with.
As far as I know I can't mount the Internal memory over the USB while in recovery (I have no SD-card slot in my One S), however I will check it out later and get back to you.
I would very much like to get back to TrickDroid first of all, since it's the ROM already installed on the device I think I only have to flash the kernel and then it should be working.
If it is so I can then put Viper One ROM on the phone and flash that using the procedure that you described above.
However I am unable to find the TrickDroid 9.0 ROM since the ROM seems to have gone out of development.. Or at least that is my guess. If I'm lucky I have it somewhere on my old laptop and can get the boot.img from there. And as well I know how fastboot and ADB works, I just need the commands that I will be using.
I will try to find the TrickDroid boot.img and flash that using fastboot and then I will get back to you.
If I don't find it, is it then possible that another kernel might support TrickDroid (like ElementalX or whatever it is called)?
Hammerbak said:
Could you maybe provide a link to the WWE RUU that has the 1.15 Radio? I have been searching almost everywhere unable to find it and I would really like to go back to stock so that I can use rumrunner or moonshine to get S-off and avoid all the hassle that I have right now.. xD...
Click to expand...
Click to collapse
HERE is a list with all RUUs, taken from dev section. Find what you may need
Hammerbak said:
...As far as I know I can't mount the Internal memory over the USB while in recovery (I have no SD-card slot in my One S), however I will check it out later and get back to you...
Click to expand...
Click to collapse
No, you don't have a card slot but you should be able to mount the internal memory as an sdcard
Hammerbak said:
If I don't find it, is it then possible that another kernel might support TrickDroid (like ElementalX or whatever it is called)?
Click to expand...
Click to collapse
Yes, you could flash ElementalX but that was gone further to support the newer ROMs like Viper 3.x. I think it's a better idea to flash Buletproof kernel (also by flar2) that was compatible with older Sense ROMs. It similar with Elemental but more stable and close to stock with some added goodies
Sounds good. I would try and flash that boot.img. I had a similar problem but was able to find an RUU that worked.
Maybe you just missed this part (or not)
Reboot into bootloader
Go into fastboot mode
fastboot flash boot boot.img
fastboot erase cache
Reboot
---------- Post added at 10:11 PM ---------- Previous post was at 10:08 PM ----------
I should point out that I did NOT have success with ViperOneS. It looks awesome and did lots of things well except hold onto calls! Every time I would make a call, it would hang up for no reason. This problem apparently doesn't happen to everyone, but it did to me.
BTW: I have CM11 running so smoothly on my HTC One S. Pretty much all of my major issues are fixed. Only the limitations of google remain.
Rapier said:
HERE is a list with all RUUs, taken from dev section. Find what you may need
Click to expand...
Click to collapse
I tried all the "Europe" and "TMO" version already.
Will try the WWE versions in the coming days if I get time. However it doesn't look like there is no 1.15 Radio ones..
Rapier said:
You could flash ElementalX but that was gone further to support the newer ROMs like Viper 3.x. I think it's a better idea to flash Buletproof kernel (also by flar2) that was compatible with older Sense ROMs. It similar with Elemental but more stable and close to stock with some added goodies
Click to expand...
Click to collapse
As far as I could read on the bulletproof kernel page, it requires S-OFF if you're going to use v. 2.x+. I guess I would have to use the version just before 2.0 which is 1.4?
I downloaded the 1.4 version and it contains 4 folders:
boot
kernel
META-INF
system
Is the boot image that is found in the boot folder the only file I will need to flash to install the bulletproof kernel 1.4? Installation on the page said I would need to flash it from recovery, but I am unable to go into recovery. Aka I found a huge problem. Since I tried to install some RUU's I am no longer able to get into recovery because I locked the bootloader..
What do I need to do?
I would suppose that I needed to flash the boot.img from the bulletproof kernel, while being in fastboot, but I don't know how that works with the bootloader being "relocked" so I will stand by for an answer..
Another thing I could do would be to go to the HTCDev page and try to unlock the bootloader again..
Which would you recommend?
Hammerbak said:
I tried all the "Europe" and "TMO" version already.
Will try the WWE versions in the coming days if I get time. However it doesn't look like there is no 1.15 Radio ones..
As far as I could read on the bulletproof kernel page, it requires S-OFF if you're going to use v. 2.x+. I guess I would have to use the version just before 2.0 which is 1.4?
I downloaded the 1.4 version and it contains 4 folders:
boot
kernel
META-INF
system
Is the boot image that is found in the boot folder the only file I will need to flash to install the bulletproof kernel 1.4? Installation on the page said I would need to flash it from recovery, but I am unable to go into recovery. Aka I found a huge problem. Since I tried to install some RUU's I am no longer able to get into recovery because I locked the bootloader..
What do I need to do?
I would suppose that I needed to flash the boot.img from the bulletproof kernel, while being in fastboot, but I don't know how that works with the bootloader being "relocked" so I will stand by for an answer
Click to expand...
Click to collapse
OK, so it's like this. You're right, I forgot that some kernel zips don't contain the boot.img itself, instead they extract the boot.img from your current ROM and repack it, that's why it is required to have S-Off because this operation can be made only in recovery (or by repacking the kernel on your pc but that's more complex and don't want to go through it since it requires Linux and other things). You should find an older kernel ZIP like the 1.4 you mentioned and use the boot.img from it.
Also you should unlock the device again at HTC dev to be able to flash the kernel in fastboot. After unlocking you can re-flash TWRP recovery and If I was you I would rather flash Viper 3.x ROM from recovery then flash the boot.img from it in fastboot, instead of trying to get a boot.img that works with TrickDroid
Now to the radio...latest US radio was 1.11 and latest Europe radio was 1.13. That's why you could not find 1.15 radio in those RUU. Version. 1.15 should be in a WWE RUU but I don't know exactly in which one. Initially I had 1.09es radio and only after changing to another hboot I was able to flash a different one. And I've upgraded my radio via tecardo's zip flashable in recovery since my hboot allows it even if I am not S-Off. There were some older hboots like 1.09 and 1.06 that allows almost everything a S-Off will allow (flashing radios and kernels from recovery that is)
If you're at this point (almost stock) I would try to flash a stock RUU (any stock RUU) and try to get S-Off first. If you previously tried to get S-Off while you were on Viper...that could be the problem. I heard many people having issues or not able to properly S-Off due to the fact they were not on stock ROM. Maybe now it's a good point to start over since you don't have anything to loose anyway. Then the things will be much easier, you could upgrade your radio from the ZIP directly, without the need to flash a RUU for that. If you don't want to try that again, just follow my advice above: unlock the bootloader again on HTC dev site, flash TWRP recovery then flash Viper 3.x and it's kernel in fastboot. You'll end up with an S-On device running on 2.15 firmware and latest Viper. Only downside to this is that you will be stuck with your current radio (the one from the RUU you flashed). You could even flash an AOSP KK ROM if you like, the same way
Rapier said:
OK, so it's like this. You're right, I forgot that some kernel zips don't contain the boot.img itself, instead they extract the boot.img from your current ROM and repack it, that's why it is required to have S-Off because this operation can be made only in recovery (or by repacking the kernel on your pc but that's more complex and don't want to go through it since it requires Linux and other things). You should find an older kernel ZIP like the 1.4 you mentioned and use the boot.img from it.
Also you should unlock the device again at HTC dev to be able to flash the kernel in fastboot. After unlocking you can re-flash TWRP recovery and If I was you I would rather flash Viper 3.x ROM from recovery then flash the boot.img from it in fastboot, instead of trying to get a boot.img that works with TrickDroid
Now to the radio...latest US radio was 1.11 and latest Europe radio was 1.13. That's why you could not find 1.15 radio in those RUU. Version. 1.15 should be in a WWE RUU but I don't know exactly in which one. Initially I had 1.09es radio and only after changing to another hboot I was able to flash a different one. And I've upgraded my radio via tecardo's zip flashable in recovery since my hboot allows it even if I am not S-Off. There were some older hboots like 1.09 and 1.06 that allows almost everything a S-Off will allow (flashing radios and kernels from recovery that is)
If you're at this point (almost stock) I would try to flash a stock RUU (any stock RUU) and try to get S-Off first. If you previously tried to get S-Off while you were on Viper...that could be the problem. I heard many people having issues or not able to properly S-Off due to the fact they were not on stock ROM. Maybe now it's a good point to start over since you don't have anything to loose anyway. Then the things will be much easier, you could upgrade your radio from the ZIP directly, without the need to flash a RUU for that. If you don't want to try that again, just follow my advice above: unlock the bootloader again on HTC dev site, flash TWRP recovery then flash Viper 3.x and it's kernel in fastboot. You'll end up with an S-On device running on 2.15 firmware and latest Viper. Only downside to this is that you will be stuck with your current radio (the one from the RUU you flashed)
Click to expand...
Click to collapse
Okay. Just to put in aspect I have the following choices:
Try to gain S-OFF as phone is now with rumrunner or moonshine
Try to get TrickDroid to work by flashing a kernel that is supported
Try to flash Viper and it's kernel from fastboot
If I try to gain S-OFF using rumrunner, do I still need to unlock the bootloader through HTCDevs?
I will try the first mentioned choice first, since gaining S-OFF would ease stuff up quite a bit.
If I can't gain S-OFF using rumrunner I will try to use moonshine.
If that doesn't work either I will be happy with just getting TrickDroid 9.0 to work as a starter.. Step by step procedure to actually gaining a working device firstly.
Then I can start thinking of how to get Viper One working after that or going back to stock to try the S-OFF methods once again.
My list of intentions is to:
Get S-OFF - whether it works or not
Getting the device to be booted and actually perform phone calls and etc.
Research the method and possibilites of getting back to stock to try S-OFF again.
Plan further upgrades to either new ROMs and/or Kernels
I'm pretty sure rumrunner and moonshine.io are similar. hmmmm after re-reading... you might have to be boot loader unlocked.
"WHAT RUMRUNNER CAN DO FOR YOU:
S-OFF Your HTC device
Unlock your bootloader (devices that are blocked by htcdev only, e.g. Verizon HTC One)"
Hard to tell. I know that someone got their ONE S - S-OFF using moonshine and they did NOT unlock the boot loader.
Good luck.
808phone said:
I'm pretty sure rumrunner and moonshine.io are similar. hmmmm after re-reading... you might have to be boot loader unlocked.
"WHAT RUMRUNNER CAN DO FOR YOU:
S-OFF Your HTC device
Unlock your bootloader (devices that are blocked by htcdev only, e.g. Verizon HTC One)"
Hard to tell. I know that someone got their ONE S - S-OFF using moonshine and they did NOT unlock the boot loader.
Good luck.
Click to expand...
Click to collapse
Okay.
Is was just about to write what you put in your edit. Haha lazy me.. xD
Well I guess as a starter I can go and unlock the bootloader, flash a recovery and try rumrunner.
When I get the recovery working I can start to plan what to do next
EDIT:
Bootloader is unlocked now and for some reason recovery wasn't removed
so I have unlocked bootloader and have a working recovery now.
Will try rumrunner S-OFF now..