Related
HELP!!
I am new to rooting, and tried to root my phone using a guide on this forum. I got my head around bits of it but im confused now and seriously need help. I successfully unlocked the bootloader screen and when I hit recover I can access clockworkmod fine. But when I try to flash the firmware by placing the PG58img.zip on the SD card, it tries to run it but says "wrong image", "no image", then stays on parsing for a while. If I restart the device it just stays on the white HTC screen. What have I done.
I am unsure what version kernel I should be trying, (tried a few, they all stay on parsing), and I could use a good ROM too.
its a pyramid pvt ship s-on rl
hboot-1.27
I really need some help and Id much appreciate it
iwkya said:
HELP!!
I am new to rooting, and tried to root my phone using a guide on this forum. I got my head around bits of it but im confused now and seriously need help. I successfully unlocked the bootloader screen and when I hit recover I can access clockworkmod fine. But when I try to flash the firmware by placing the PG58img.zip on the SD card, it tries to run it but says "wrong image", "no image", then stays on parsing for a while. If I restart the device it just stays on the white HTC screen. What have I done.
I am unsure what version kernel I should be trying, (tried a few, they all stay on parsing), and I could use a good ROM too.
its a pyramid pvt ship s-on rl
hboot-1.27
I really need some help and Id much appreciate it
Click to expand...
Click to collapse
Follow the below guide to letter to get a working rom
http://forum.xda-developers.com/showthread.php?p=25587345
Sent from my pyramid.. Through blazing fast sonic waves
ganeshp said:
Follow the below guide to letter to get a working rom
http://forum.xda-developers.com/showthread.php?p=25587345
Sent from my pyramid.. Through blazing fast sonic waves
Click to expand...
Click to collapse
Thanks man, I shall follow it exactly and let you know how it goes. Lost without my phone.
problems
Ok so I have tried it to the letter, few issues though..
Since I have no working rom running, I cannot "enable usb debugging" in order to install the 4ext recovery. I got around this but doing this in the bootloader instead - is this ok ?
4ext seemed to work, and i have followed it to the letter, super wipe installed great, then I installed revolution rom which went well, choosing to install a stock kernal. However after reboot - still a white HTC screen
The only thing I can think of is that my firmware is wrong. Since I cannot get into settings (as i have no rom) and can only access bootloader and now 4ext, I cannot see its version - if there is a way can you help please
I need 3.32 but don't know if i have it or not as I have played around with it that much (my own fault i know )
Is there any way to see the version i have and install 3.32 firmware in 4ext or bootloader. Everytime I have tried in the past by copying it to the sd card, it gives me the parsing message and no image wrong image..grrr
Thanks greatly man
iwkya said:
Ok so I have tried it to the letter, few issues though..
Since I have no working rom running, I cannot "enable usb debugging" in order to install the 4ext recovery. I got around this but doing this in the bootloader instead - is this ok ?
4ext seemed to work, and i have followed it to the letter, super wipe installed great, then I installed revolution rom which went well, choosing to install a stock kernal. However after reboot - still a white HTC screen
The only thing I can think of is that my firmware is wrong. Since I cannot get into settings (as i have no rom) and can only access bootloader and now 4ext, I cannot see its version - if there is a way can you help please
I need 3.32 but don't know if i have it or not as I have played around with it that much (my own fault i know )
Is there any way to see the version i have and install 3.32 firmware in 4ext or bootloader. Everytime I have tried in the past by copying it to the sd card, it gives me the parsing message and no image wrong image..grrr
Thanks greatly man
Click to expand...
Click to collapse
4EXT flashed fine ..thats no probs there ..and you did the right thing (adb reboot-bootloader is to get to fastboot ..which you can do it manually too)
did you enabled the smartflash ?? ---> THIS is the main step
did you check the md5 of the ROM ? (you can do it via 4EXT itself - its in install form sdcard-> check md5 i think) and verify it aganist the md5sum given in ARHD thread (in general just below the download link)
also flash the rom again ..no wipe this time ..just flash it
can you post the complete HBOOT details ? seeing that i can give you the proper suggestion (afaik if you are on ICS earlier ..you have correct firmware)
I have performed the md5 check and it was ok. Im thinking that after 4ext rebooted after the superwipe, I didn't re-enable smart flash (forgot it needs to be done again), so I just enabled it and am reinstalling the ROM with no superwipe this time..
My hboot is 1.27 so i must have 3.32..
I really do appreciate this, sorry im a n00b
Finished flashing rom, reboot and same again. White HTC screen. I really am lost now
This is what my screen says in bootloader
unlocked
pyramid pvt ship s-on rl
hboot-1.27.0000
radio-11.22.3504.07_m
openADSP-v02.6.0.2226.00.0131
eMMC-boot
iwkya said:
I have performed the md5 check and it was ok. Im thinking that after 4ext rebooted after the superwipe, I didn't re-enable smart flash (forgot it needs to be done again), so I just enabled it and am reinstalling the ROM with no superwipe this time..
My hboot is 1.27 so i must have 3.32..
I really do appreciate this, sorry im a n00b
Finished flashing rom, reboot and same again. White HTC screen. I really am lost now
Click to expand...
Click to collapse
EDIT: you got correct firmware no need to flash it again
dude the smart flash is said temporary for a reason ..you need to enable it every time ..when ever you enter the recovery ..until you make the smartflash permanent by following step 5 (which can be done only when you have a bootlable, rooted rom )
Yea im guessing the firmware is ok, the 4ext is great, superwipe works fine, the rom installs complete. When reboot, it just stays ont he white screen
Really annoying now since i have no phone and cannot seem to find anything else on it.
iwkya said:
Yea im guessing the firmware is ok, the 4ext is great, superwipe works fine, the rom installs complete. When reboot, it just stays ont he white screen
Really annoying now since i have no phone and cannot seem to find anything else on it.
Click to expand...
Click to collapse
you enabled smartflash just before flashing the rom ?
and still stuck there ?
ok do the extra1 step mentioned in the guide (skip the adb steps again ..and do only fastboot steps)
I feel you
iwkya said:
Yea im guessing the firmware is ok, the 4ext is great, superwipe works fine, the rom installs complete. When reboot, it just stays ont he white screen
Really annoying now since i have no phone and cannot seem to find anything else on it.
Click to expand...
Click to collapse
I can really understand your annoyance I have experienced the exact same problem to the letter. After several attempts to reach out No One seemed to help or understand my problem. I then went back to my HD2 and now have the HOX as my main unit.
I get stuck on the white logo screen or beats screen everytime I flash a ROM. I tried everything at least I think so.
mitchelleersel said:
I can really understand your annoyance I have experienced the exact same problem to the letter. After several attempts to reach out No One seemed to help or understand my problem. I then went back to my HD2 and now have the HOX as my main unit.
I get stuck on the white logo screen or beats screen everytime I flash a ROM. I tried everything at least I think so.
Click to expand...
Click to collapse
all your threads are before i joined XDA
Yea, im well pissed off. I have done everything, yes I enabled smartflash and installed the rom again, done that a few times now. Ran superwipe a few times, nothing.....
going to re image the recovery and try it all again.
if that doesnt work, its in the bin..
iwkya said:
Yea, im well pissed off. I have done everything, yes I enabled smartflash and installed the rom again, done that a few times now. Ran superwipe a few times, nothing.....
going to re image the recovery and try it all again.
if that doesnt work, its in the bin..
Click to expand...
Click to collapse
you keep on doing superwipe ..it wipes everything
just do it once ..only once
then enable smartflash
then flash the rom
if it still stuck
then do the extar 1 step in the guide (you need to get the boot.img of the kernel you have chosen while installing the AHD rom earlier)
thats all follow that once and reply me back if it didnt worked
(no extra steps)
ok done it again, same thing happens.
Now.. you are referring to an extra step regarding the boot image. It isnt clear in the guide. Where do I get the boot image from, and how and when do I apply it.
?
iwkya said:
ok done it again, same thing happens.
Now.. you are referring to an extra step regarding the boot image. It isnt clear in the guide. Where do I get the boot image from, and how and when do I apply it.
?
Click to expand...
Click to collapse
Usually the fitting boot.img can be found inside the .zip of your desired Rom.
Finding your "boot.img"
Open your rom's zip file
Open the "kernels" folder
Open the folder of the kernel you chose during install of your rom (if there are any choices)
Extract the "boot.img" to C:\Android (or wherever your adb and fastboot are located)
Click to expand...
Click to collapse
he does say how to find it right?
the zip in your case is ARHD 6.6.7 rom zip file
and you are asking again for how and when ..when he clearly explained the steps on how to do it
and i already told you when to apply it
ohh btw skip the adb steps ..you can go to bootloader manually and do the fastboot commands
ok, so i got somewhere
I found a boot.img in the rom/kernals
then i used fastboot flash boot boot.img
this flashed the img
now when i reboot i get off the htc screen and im stuck on the beats audio screen -- oo while I been typing its come off the beast screen and booted into android yey.. Thank you every so much man. I kinda understand this a little more too thanks to you and the guide.
I shall post when I have problems with this rom (notice i said when)
Thank you..
iwkya said:
ok, so i got somewhere
I found a boot.img in the rom/kernals
then i used fastboot flash boot boot.img
this flashed the img
now when i reboot i get off the htc screen and im stuck on the beats audio screen -- oo while I been typing its come off the beast screen and booted into android yey.. Thank you every so much man. I kinda understand this a little more too thanks to you and the guide.
I shall post when I have problems with this rom (notice i said when)
Thank you..
Click to expand...
Click to collapse
thanks you do it but hitting the thanks button to useful posts (that's how xda kept it )
I am still stuck at boot screen
Hey I tried to do everything my guy here did and still no luck.
the last thing I tried was flashing latest firmware package without the HBOOT, then flashed the newest recovery, then performed a superwipe because latest rom differed from ARHD, then flashed the ROM and then the Boot.img just to be sure (even though this should not be necessary according to the firmware)
How can I figure out whats wrong?
Firstly thanks to everyone who give their time to help
My tech skills are useless, all these terms s-off, s-on, roms etc
is above my pay grade, my brain is fried i am jumping from thread to thread
trying to fix my wifi issue and it's driving me dilly.
I am on Android 4.0.3 - Sense 3.6, phone is rooted HTC-Dev and Flashed 4EXT.
I have been trying to fix the WiFi issue but im getting nowhere, i give up.
Can i revert back to Gingerbread?
Is there a step by step guide?
Help Appreciated
Thanks
1st: are you s-on or s.off?
If you are s-off you can extract the rom.zip from the appropriate GB RUU (but you dont tell what is) then rename it PG58IMG. Put in the root of your sd card (not in a folder) and reboot the device while holding down volume+ power button.
PG58IMG willbe automatically recognized and start to do its things. Then you will be prompted if you want to upgrade. Say yes by pushing volume up.
Wait untill the entire process is done and prompted to reboot (it may reboot itself a couple of times during the process, just do nothing and wait).
At the end of process you will be back to GB and need to set the phone like new. You will lose all data and settings.
Hope it helps.
How do i know if i'm S-off or S-on?
Used HTCDev to unlock bootloader then flashed 4EXT and something called
CWM-SuperSU-v0.96?
Thanks
This is the method i used:
http://forum.xda-developers.com/showthread.php?t=1632553
Good day my dear friends,
Boring Intro------
Yesterday I was trying to root my wife's HTC Sensation which I upgraded to Official Middle East ICS 4.0.3 hboot 1.27.000 and I found this way by pure luck-----
I installed CMW and did the rooting while the device is S-ON
I'm not sure if this is a new method or was done before but I thought I'd share it to return some of your favors in this great forum.
I need to thank Mr.hasoon2000 because we will use his tol from the HTC One X forum.
Requirements:
1. Download the HTC One X All-In-One Toolkit V1.0 from this link, Thanks Mr.hasoon2000 I hope you don't mind me using your tool here.
2. Download the latest CMW recovery , choose the latest for Pyramid (The Sensation) in *.img. Here is the CMW 5.8.0.9 link.
3. Download SuperSU 0.88.zip, thanks Mr.Chainfire or from this link [23.04.2012] SuperSU v0.88.
Step By Step Method:
1. Copy the SupperSU.zip file to your SD root.
2. Extract the HTC One X All-In-One Toolkit V1.0 to the Disktop.
3. Connect your Mobile and make sure you're in the charging mood and your check USB development or debugging option.
4. Run the One X.exe application.
5. Install the HTC drivers.
****If you unlocked your Sensation's bootloader from HTCdev.com then skip step 6 ****
6. Register in HTCdev.com website, choose Unlock Bootloader, choose your device and follow the instructions. ~This May Void your Warranty~
7. Rename the CWM recovery to CWM5827, then copy it to HTC One X All-In-One Toolkit folder/Data folder/recoveries and replace the one inside.
8. Flush the CWM recovery using the toolkit, horray you installed CWM.
9. From Commands choose Boot into recovery and from CWM flush the SuperSU.zip.
10. Congratulations, You're Now ROOTED .
Unthick fastboot from your phone (should be under settings-Battery) Then reboot phone while holding volume down + power buttons and read what the bootloader says.
Or pull out and reinsert battery, then power up the phone while holding down volume
remove battery from phone
Remove any memory card installed in phone
put battery back into phone
press volume down..
While pressing volume down
Press power button...
Continue pressing both Until you enter bootloader
You will see white screen, print lots of writing in different colored text, but the top line will say 's-on' or 's-off'
Report back here
Sent from my ADR6425LVW using Tapatalk 2
By the way I dont understand why you want to go back to GB. Once you are back you will be prompted to update to ICS again!.
Why dont you run directly a stock ICS RUU and see it it solves your issue?. In case you are S-On that would be the easiest way (the RUU).
If you want to go back to the way the phone was when you first got it, no root or anything, use an RUU
http://forum.xda-developers.com/showthread.php?t=1672425
That's everything you need to know. Basically run a program in Windows with the phone plugged in and it'll do all the work for you.
OK guys looks like i'm S-ON
PYRAMID PUT SHIP S-ON RL
kualmente said:
By the way I dont understand why you want to go back to GB. Once you are back you will be prompted to update to ICS again!.
Click to expand...
Click to collapse
I've tried everything to get my WiFi to work with ICS, read here someone saying reverting to Gingerbread may work.
kualmente said:
Why dont you run directly a stock ICS RUU and see it it solves your issue?. In case you are S-On that would be the easiest way (the RUU).
Click to expand...
Click to collapse
Some help please.
How do i do that, is there a step by step you can point me to?
Thank you very much...
Read the guide posted by Skipjacks. There is all you need.
kualmente said:
Read the guide posted by Skipjacks. There is all you need.
Click to expand...
Click to collapse
Thanks
Will that put me back to Gingerbread?
Cheers
No, if you are s-on the easiest way is to run the appropriate RUU.exe (still ICS not GB). But first you need to make some search and detect what is the right RUU for you according to your country, cid and mid.
When you will find it, just download the exe and, plug your phone to the pc and execute the RUU.exe
You cannot go back to GB as you are S-On.
RUU works for either the same software version or up not down.
Hello people. Just one question. I searched on google and here on xda how to do it but still Im not sure how to do it. I have HTC Desire S, S-OFF with 2.00.002 hboot version and 4.0.4. android version. How do I permanetly root? The official 4.0.4 is kinda laggy, at least for me. I tried few methods but still nothing.. And, I found few methods like for 0.98 hboot or 2.3.5. android but my phone isnt that so Im not sure will it work. Thanks im advance
chorba69 said:
Hello people. Just one question. I searched on google and here on xda how to do it but still Im not sure how to do it. I have HTC Desire S, S-OFF with 2.00.002 hboot version and 4.0.4. android version. How do I permanetly root? The official 4.0.4 is kinda laggy, at least for me. I tried few methods but still nothing.. And, I found few methods like for 0.98 hboot or 2.3.5. android but my phone isnt that so Im not sure will it work. Thanks im advance
Click to expand...
Click to collapse
Is your bootloader unlocked? If so then flash a custom recovery and flash a custom ROM, they all tend to be pre-rooted.
Sent from my Desire S using xda app-developers app
You're already S-OFF so you don't need to worry about most steps in guides.
I assume you have a custom recovery? You can just flash one of the superuser/superSU zip packages. (Desire S uses ARM).
You may also need to flash busybox.
My good gentlemen,
he says the phone is s off already
If you want to ROOT your phone (my case: Desire S , Mfc date: 2011-July ). This is the procedures i learned from China Android forums, at least it works on Me.!!
Make Sure your Hboot is 2.00.0002
Prepare 2 files first: Superuser-3.0.7-efghi-signed.zip and su-bin-3.0.3.2-efghi-signed.zip
(you should find those on the internet)
First:
Recovery --> install Superuser-3.0.7-efghi-signed.zip from SDcard, and Reboot;
Second:
Recovery --> Install su-bin-3.0.3.2-efghi-signed.zip from SDcard Again and Reboot.
Usually, your phone should be Rooted.!!
Have Fun
Thanks for answers Well, the only thing I wanna do is flash a custom rom, and I dont know do I need rooted device for that? If I dont, what do I need? And, how can I check is my bootloader unlocked? And, where can I find a custom recovery? Can anyone link me please? Thanks ^^
I learned few things on my old Desire but this seems little complicated If isnt a probem, can anyone give me a step by step guide what I have to do to start flashing custom roms or something? I'd appreciate it. Thanks in advance
chorba69 said:
Thanks for answers Well, the only thing I wanna do is flash a custom rom, and I dont know do I need rooted device for that? If I dont, what do I need? And, how can I check is my bootloader unlocked? And, where can I find a custom recovery? Can anyone link me please? Thanks ^^
I learned few things on my old Desire but this seems little complicated If isnt a probem, can anyone give me a step by step guide what I have to do to start flashing custom roms or something? I'd appreciate it. Thanks in advance
Click to expand...
Click to collapse
Reboot to bootloader and check the first and second lines of text there...
first states < unlocked > if it was unlocked
second at the end: s-off.... or s- on
If your device realy was: s- off,
then your bootloader does not perform check of a signature,
so, in human language means: you may flash anything you want
custom recovery: clockworkmod or 4ext,
you may find in index thread for desire s...
here is the link
http://forum.xda-developers.com/showthread.php?t=1146601
there you can find tutorials about flashing, rooting etc, etc...all you`ll need
here is another link to the help thread, where you may ask questions if you
stumbled somewhere, along the way
http://forum.xda-developers.com/showthread.php?t=2143855
one more thing: when choosing roms, you should only flash roms for your device
htc desire s ( that`ll save you headaches )
Erm.. Just checked and it says bootloader is locked :/ It is S-OFF but locked. How can I unlock it? On HTCdev or? Thanks
chorba69 said:
Erm.. Just checked and it says bootloader is locked :/ It is S-OFF but locked. How can I unlock it? On HTCdev or? Thanks
Click to expand...
Click to collapse
I`ve never had stock s-off device ( always had to do it myself )
but if you phone was never rooted before and its security flag is set to s- off,
then i think its bootloader will never check manufacturer`s signature
Try this:
download from the market or from 4ext thread (index thread )
< 4ext recovery updater > and from within that application,
try to install recovery ( you`ll need it anyway )
if that`ll turn out to be succesful, then your phone is ready for the ride...
Go to the thread from the second link ( help thread )
and ask there whether device that is s- off, needs its bootloader to be unlocked
in order to be ready to flash custom roms...
To unlock bootloader you may try comand ( not sure if that would work for you )
fastboot oem unlock
issued to you phone through comand prompt ...
Prior to this action you should set up ADB on your pc,
and of course install the drivers for your device...
Says this what I attached. What now?
chorba69 said:
Says this what I attached. What now?
Click to expand...
Click to collapse
Ok then...
you have to flash recovery via fastboot
1. download and set up adb and drivers for you phone ( and install them )
2. download recovery ( clockworkmod or 4ext )
3.extract < recovery_xxxyyy.img > from the zip file- if you downloaded it zipped...
4.rename file to < recovery.img > and place it in the folder
where you`ve placed ADB
5.open command prompt and issue command:
cd c:\name of the folder with ADB [ enter ]
6. reboot your phone to bootloader and wire it to you pc
7. issue command:
fastboot devices
if your device has been recognised( list of devices attached xxxyyy05321...)
you`ll see your phone`s ID
8. issue command:
fastboot flash recovery recovery.img
9. reboot bootloader, and from its option choose recovery
10. from recovery you may flash < superuser.zip >
if you just want your current rom rooted
or via recovery you may flash custom rom...
Alright mate thanks a lot. Im gonna try that as soon as I come home. Just one thing more, any chance of bricking my device? While doing that.
chorba69 said:
Alright mate thanks a lot. Im gonna try that as soon as I come home. Just one thing more, any chance of bricking my device? While doing that.
Click to expand...
Click to collapse
To be honest, when fiddling with phone`s system, bootloader etc..
however small- there is always a chance that you may manage to brick it,
but i`ve been followiing the above mentioned procedures- and many others before me,
many times, and it was always working without a problem,
it was tested and shared, first by the great ones among us,
so one may call them safe to perform,
but you should always remember to be careful,
and better read or ask twice, before doing something you do not fully understand
Ok just to make sure Im doing everything alright.
First, nothing to do with bootloader? Unlock or something?
Next, I create new folder on my pc on C partiton (because of cmd prompt you've said?), download adb and phone drivers and place them in the folder. Then install the drivers. Afterwards, download recovery and place it in the folder with adb and phone drivers and rename to recovery.img. Next, I reboot phone in bootloader and flash recovery. Then I have to reboot in bootloader again, how to? Phone will turn off so I can reboot in bootloader or what? Then I go in recovery, flash superuser.zip for rooted phone and afterwards flash custom rom. Thats it?
chorba69 said:
Ok just to make sure Im doing everything alright.
First, nothing to do with bootloader? Unlock or something?
Next, I create new folder on my pc on C partiton (because of cmd prompt you've said?), download adb and phone drivers and place them in the folder. Then install the drivers. Afterwards, download recovery and place it in the folder with adb and phone drivers and rename to recovery.img. Next, I reboot phone in bootloader and flash recovery. Then I have to reboot in bootloader again, how to? Phone will turn off so I can reboot in bootloader or what? Then I go in recovery, flash superuser.zip for rooted phone and afterwards flash custom rom. Thats it?
Click to expand...
Click to collapse
In bootloader, there is an option to reboot it,
While in fastboot usb mode, bootloader is the first option,
go into it (power button )....
There you can also find < recovery > option....
@chorba69
Go here and find the zip download link (here), extract to same folder as fastboot/adb (and optionally md5 check).
Reboot your phone into Fastboot (reboot to bootloader and if there is an option "fastboot", choose it, else you're already there)
Connect by USB (see the "+files" in my signature if you need windows drivers so your computer understands it's an android phone)
Open a command prompt window (hold shift, right click in the folder, open command prompt..)
Code:
fastboot flash recovery recovery.img
Wait for flash, if you see a message like "waiting for device", your phone isn't connected, you're on the wrong screen on your phone or your computer doesn't have the drivers installed.
Reboot back into bootloader
vol up/down, power button to choose Recovery
You now have a custom recovery (and you're viewing it), now you just have to select your zip from sdcard to flash it (this time the zip is the superuser/whatever).
Backups save phone's lives!
I'm curious about the first line of your hboot (after locked/unlocked/relocked)? e.g. mine is "SAGA PVT ENG S-OFF", if yours says "SAGA PVT SHIP S-OFF" then you're "radio s-off" and can do things like change your phones CID (let it use any network). If it's ENG S-OFF and not pre owned, then you're very lucky indeed (and some people might want more info about/a copy of your hboot)!
Paulie, I attached the image as you can see. Says it's PVT SHIP S-OFF. Do I need to do something before flashing recovery and superuser/rom etc? Or it's not important? Whats the difference anyways between PVT and ENG? And thanks ^^
Mhm. Just tried to flash recovery but recieved this message (attached). Im on FASTBOOT USB screen on phone and in the right directory on pc. Do I need to set up adb or something? Or what do I have to do now?
PVT is expected there, SHIP seems to mean "this version is for general release" whereas "ENG" signifies that it is an ENGineering version.
chorba69 said:
Mhm. Just tried to flash recovery but recieved this message (attached). Im on FASTBOOT USB screen on phone and in the right directory on pc. Do I need to set up adb or something? Or what do I have to do now?
Click to expand...
Click to collapse
I'm surprised you got this error. S-OFF should've meant you had no problem. Instead, you can try using the PG88IMG.zip method. Place the file in the root directory of your phone's SD card, reboot to bootloader and it should detect it and ask you if you want to apply the update.
Remember to delete/rename/move this zip file after it's done, as you'll not be able to use your bootloader normally whilst it is detected.
If you still get another error message, let us know!
Please be careful with the file below.
P88IMG.zip MD5: 729f7b435eadf6321ffc36d1da6a0f83
recovery.img MD5: b81b154d1381c9a7f23be39b645be38b
paulie-uk said:
PVT is expected there, SHIP seems to mean "this version is for general release" whereas "ENG" signifies that it is an ENGineering version.
I'm surprised you got this error. S-OFF should've meant you had no problem. Instead, you can try using the PG88IMG.zip method. Place the file in the root directory of your phone's SD card, reboot to bootloader and it should detect it and ask you if you want to apply the update.
Remember to delete/rename/move this zip file after it's done, as you'll not be able to use your bootloader normally whilst it is detected.
If you still get another error message, let us know!
Please be careful with the file below.
P88IMG.zip MD5: 729f7b435eadf6321ffc36d1da6a0f83
recovery.img MD5: b81b154d1381c9a7f23be39b645be38b
Click to expand...
Click to collapse
Hmm. So after I put that file on SD card, I have to flash it or flash the recovery.img? Or just when I put it and enter bootloader it will automatically start flashing the recovery?
I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!
Flashing boot.img did not work. I'm in bootloop hell.
mollysue said:
I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!
Click to expand...
Click to collapse
Since you are S-On with SuperCID, I would say to revert back to your original CID and then flash the appropriate RUU. Make sure you definitely change back to your original CID, as trying to run the RUU with S-ON and SuperCID will brick your phone. You can then re-SuperCID your phone, unlock the bootloader, and try a new custom ROM. I would also recommend getting back to S-OFF after doing all of the above.
Sent from my HTC One XL using XDA Premium 4 mobile app
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
mollysue said:
I've searched far and wide, and I found a lot of threads regarding the specifics of my problem, but none that solve it. A point in the right direction is much appreciated.
I have an AT&T HTC One X (used to be S-OFF now S-ON), unlocked, HBOOT 1.12.0002 CID 1111111
I've been running CM 10.1.3 for a while now and it's very glitchy and causes random reboots and freezes. I've been trying to upgrade to 10.2 or try a variety of different roms. When flashing I kept getting the following error: E:Error executing updater binary in zip..
I lived with the rom for a while because of the error, but today got fed up. I googled it and found out TWRP was probably the problem so I downgraded to 2.3.3.0. Then I got a (Status 7) error which means either that the ROM is not for the Evita (not true) or TWRP is out of date (true but necessary). I tried getting the .zip to stop checking what phone it was, didn't work.
SO I wonder if I have to upgrade HBOOT? I google it and try this guide.
It all worked up until the adb part, where at first it said the device was not there, then that it was offline, then it said permission denied. So I tried again thinking I did something wrong, but after flashing zip it said "FAILED(remote:99 unknown fail).
Now my phone is S-ON and stuck in bootloop. I'll flash boot.img and hopefully it will be fine, but I just want to know what the hell is wrong with my phone, any ideas? I cannot possibly continue with this stupid ROM as it's driving me nuts, but PHONE NOT COOPERATING.
Thanks!!!!!
Click to expand...
Click to collapse
Code:
adb version
How u get S-ON again anyway after S-OFF......FAILED 99 : check your adb version by entering this on your adb folder......most likely u got 1.0.29 version which is always show device offline....u need to update it to 1.0.31 version ....check other Q&A thread.....it been talking over and over again......if u do first XDA rules.....READ. As per timmaaa requested ......in case u dont know ...... power off your phone.....then hold both power button+vol down for few second and only let go power button while u still holding vol down.....this will bring u to bootloader
timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
I thought so.....hboot 1.12......
timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
Good catch Timmaaa!
Sent from my HTC One XL using XDA Premium 4 mobile app
//JavaJ said:
Since you are S-On with SuperCID, I would say to revert back to your original CID and then flash the appropriate RUU. Make sure you definitely change back to your original CID, as trying to run the RUU with S-ON and SuperCID will brick your phone. You can then re-SuperCID your phone, unlock the bootloader, and try a new custom ROM. I would also recommend getting back to S-OFF after doing all of the above.
Sent from my HTC One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
****, what's my original CID, I didn't write it down?
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
I must have read it wrong then, SORRY.
It says:
EVITA PVT SHIP S-ON RL
HBOOT-1.140002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 111 2012
timmaaa said:
Hang on, there's something very fishy here. The hboot 1.12 is not an Evita hboot, that's an Endeavoru hboot. Please post your hboot details (the first five lines in bootloader), and please post the full filename of the ROM you're flashing.
I believe you're confused as to which device you actually have, and you're potentially trying to flash a ROM that isn't meant for your device.
Sent from my Evita
Click to expand...
Click to collapse
ted77usa said:
Code:
adb version
How u get S-ON again anyway after S-OFF......FAILED 99 : check your adb version by entering this on your adb folder......most likely u got 1.0.29 version which is always show device offline....u need to update it to 1.0.31 version ....check other Q&A thread.....it been talking over and over again......if u do first XDA rules.....READ. As per timmaaa requested ......in case u dont know ...... power off your phone.....then hold both power button+vol down for few second and only let go power button while u still holding vol down.....this will bring u to bootloader
I thought so.....hboot 1.12......
Click to expand...
Click to collapse
No I have "Android Debug Bridge version 1.0.31".
Ah ok, that makes more sense! Are you absolutely sure the ROM you're flashing is an Evita ROM? Where did you download it and what is the full filename?
You said the phone was s-on but not anymore? Why did you return it to s-on? You're gonna need to get s-off again so you can RUU up to 3.18 so you can flash the recent aosp ROMs. When you get the error 99 after flashing the zip, just force a reboot back to bootloader by holding volume down and power together. Once you're back in bootloader you can start again (without the adb reboot bootloader command because you're already in bootloader) and you should get error 92 now. Now, before you give the adb soffbin commands you need to make sure the screen is unlocked and stays unlocked, also make sure usb debugging is enabled in developer options. If it's an aosp ROM you'll also need to grant root access to adb in developer options.
For now my suggestion would be to download a Sense ROM, preferably Android 4.0 or 4.1, this should at least boot and enable you to get s-off on your phone again. Don't forget top flash the boot.img via fastboot.
Sent from my Evita
---------- Post added at 07:27 PM ---------- Previous post was at 07:25 PM ----------
mollysue said:
No I have "Android Debug Bridge version 1.0.31".
Click to expand...
Click to collapse
Your adb version is fine, you can leave that the way it is.
Sent from my Evita
mollysue said:
****, what's my original CID, I didn't write it down?
I must have read it wrong then, SORRY.
It says:
EVITA PVT SHIP S-ON RL
HBOOT-1.140002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 111 2012
Click to expand...
Click to collapse
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE
ted77usa said:
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
ted77usa said:
Well if u said is right on OP......U bought AT&T HTC ONE X it should have AT&T LOGO in the front......if u do that mean your original CID I believe if I'm not mistaken are CWS__001 . If I were u ......I just keep continue try S-OFF first by going back to Android 4.0 ICS Rom and flash original rom boot.img manually from fastboot and check my other Q&A THREAD coz I had same error with u.......but I'm S-OFF now
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
I decided to boot into recovery and flash CM 10.0.0, and so I got out of bootloop. It's very glitchy, the keyboard keeps crashing, but it "works".
Now I'm trying to get S-OFF using this tool. At first it didn't work, so I changed the CID back to original. Now I get the following error:
Before we continue:
Ensure your phone is rooted.
Disable "Fast boot" on the phone under Settings -> Power.
Enable "USB Debugging" under Settings -> Developer Options.
Make sure your HTC One XL is connected to your mac via a USB cable.
When you're ready, press return to continue...
Copying your misc partition to your sdcard partition...
Unknown id: if=/dev/block/mmcblk0p4
Copying the file to your computer so we can work with it...
remote object '/sdcard/mmcblk0p4' does not exist
Making a backup copy here too...
cp: tmp/mmcblk0p4: No such file or directory
Changing CID to Super CID in local copy...
unable to read input file tmp/mmcblk0p4 at /Users/user/Downloads/OneXL_SuperCID_Mac_v1_1/bin/HOX_bin_partition_edit.pl line 22.
ERROR
There was a problem converting the CID in the local copy of your binary partition
and we can not continue.
Press return to exit
It might be that I did not disable fastboot, but that is because the option is just not available on the phone, there is no "Power" category. I did enable debugging, but there was no notification in the menu bar making me maybe think that the OS is just too glitchy for this to work.
I didn't know what else to do, tried unlocking the bootloader through HTCDev but when I got to step 13 the notification did not come on screen like it was supposed to and so that was unsuccessful. I guess this was a silly idea.
I'm trying to be as descriptive as possible in case this happens to anyone else!
Cannot find stock Android 4.1 as suggested, for some reason. I found this, but I have a mac and .exe files mean nothing to me. I figure 10.0.0 has to be as stable as it gets with what I have, so I reflashed and boot.img. Now I'm stuck in bootloop again! Am I not meant to have nice things?
Could you suggest a rom to download and flash? After that I'll try S-OFF via Facepalm again.
mollysue said:
I decided to boot into recovery and flash CM 10.0.0, and so I got out of bootloop. It's very glitchy, the keyboard keeps crashing, but it "works".
Now I'm trying to get S-OFF using this tool. At first it didn't work, so I changed the CID back to original. Now I get the following error:
Before we continue:
Ensure your phone is rooted.
Disable "Fast boot" on the phone under Settings -> Power.
Enable "USB Debugging" under Settings -> Developer Options.
Make sure your HTC One XL is connected to your mac via a USB cable.
When you're ready, press return to continue...
Copying your misc partition to your sdcard partition...
Unknown id: if=/dev/block/mmcblk0p4
Copying the file to your computer so we can work with it...
remote object '/sdcard/mmcblk0p4' does not exist
Making a backup copy here too...
cp: tmp/mmcblk0p4: No such file or directory
Changing CID to Super CID in local copy...
unable to read input file tmp/mmcblk0p4 at /Users/user/Downloads/OneXL_SuperCID_Mac_v1_1/bin/HOX_bin_partition_edit.pl line 22.
ERROR
There was a problem converting the CID in the local copy of your binary partition
and we can not continue.
Press return to exit
It might be that I did not disable fastboot, but that is because the option is just not available on the phone, there is no "Power" category. I did enable debugging, but there was no notification in the menu bar making me maybe think that the OS is just too glitchy for this to work.
I didn't know what else to do, tried unlocking the bootloader through HTCDev but when I got to step 13 the notification did not come on screen like it was supposed to and so that was unsuccessful. I guess this was a silly idea.
I'm trying to be as descriptive as possible in case this happens to anyone else!
Cannot find stock Android 4.1 as suggested, for some reason. I found this, but I have a mac and .exe files mean nothing to me. I figure 10.0.0 has to be as stable as it gets with what I have, so I reflashed and boot.img. Now I'm stuck in bootloop again! Am I not meant to have nice things?
Could you suggest a rom to download and flash? After that I'll try S-OFF via Facepalm again.
Click to expand...
Click to collapse
Well try any ICSbase rom......i did tried cleanrom 4.2 ICS base Rom sense 4.......but since u on 1.14 hboot u need to extract boot.img from original Rom to your working adb/fastboot folder and push it manually from fastboot.....
1.put ICS of your choice inside ur SD card
2.copy or extract boot.img from Rom you about to flash and place it inside your working adb/fastboot folder.
3.connect your phone to PC and make sure USB debugging check....and HTC driver install properly
4. Flash Rom from recovery and choose go back> reboot> bootloader and this would bring u to fastboot USB mode if u have correct driver install and USB debugging check .
5. Go to your adb/fastboot folder hold shift+right click > open command Window .....and enter code to push boot. img tru fastboot......I forgot the code...but I'm sure timmaaa knew out of his head......
6.if successfull......reboot system and u should have working ics sense 4 Rom
7.play with it a day or too before u attempt facepalm S-OFF and in the mean time do more reading.......
Swyped From BlueICESense_JBE
ted77usa said:
Well try any ICSbase rom......i did tried cleanrom 4.2 ICS base Rom sense 4.......but since u on 1.14 hboot u need to extract boot.img from original Rom to your working adb/fastboot folder and push it manually from fastboot.....
1.put ICS of your choice inside ur SD card
2.copy or extract boot.img from Rom you about to flash and place it inside your working adb/fastboot folder.
3.connect your phone to PC and make sure USB debugging check....and HTC driver install properly
4. Flash Rom from recovery and choose go back> reboot> bootloader and this would bring u to fastboot USB mode if u have correct driver install and USB debugging check .
5. Go to your adb/fastboot folder hold shift+right click > open command Window .....and enter code to push boot. img tru fastboot......I forgot the code...but I'm sure timmaaa knew out of his head......
6.if successfull......reboot system and u should have working ics sense 4 Rom
7.play with it a day or too before u attempt facepalm S-OFF and in the mean time do more reading.......
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
Thanks!!!! The rom worked. I'm going to let it sit for a while before doing any more tampering. At least I have a working phone *happy dance*
Q&A for [s-off] moonshine s-off for ville_c2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [s-off] moonshine s-off for ville_c2. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hello everyone.
I tried using Moonshine to S-OFF my HTC One S (villec2), which didn’t quite go as intended and now I’m stuck in a boot loop.
I downloaded Moonshine from the Moonshine website, under HTC One S – S3 model (ville_c2), first download for ROM version 3.19.401.101 (I got that version number from Software information somewhere in Settings). I then made sure that the phone had Fast boot disabled under power options, turned off the screen lock, connected the phone to the desktop (running Ubuntu 14.10) via the USB cable, and did sudo ./distiller. Moonshine did its magic for a few minutes and, in the end, the phone was powered off. However, when I powered it on, it got stuck in a boot loop.
Now, to solve this, I rebooted into recovery mode (I’ve got something that says CWM-based Recovery v5.5.0.4, not quite sure where I got that) and tried restoring the backup I had previously made and/or wiping caches, none of which seemed to help.
So here’s where I am now: I can boot into bootloader just fine. The bootloader says moonshine S-OFF on top. Normal boot is stuck in a boot loop; it shows the regular splash screen for a few seconds, then a window entitled Android is upgrading… and a spinning progress thingy along with Optimizing app 1 of 24. for a second, then Starting apps. for a few more seconds, then the screen just turns off and the loop begins anew. Occasionally I can see, for a brief moment, an error message right at the end; I can’t quite discern what it says, but it is about a crash of something with gapps in its name.
During the boot loop, I can connect to the phone using ADB (and by that I mean that I can access the shell with adb shell or reboot into bootloader or recovery with adb reboot bootloader or adb reboot recovery). Oddly enough, when I try to power down, the phone doesn’t power down but reboots into recovery instead. I tried powering it down by: holding the power button for a really long time (this, however, just restarts the boot loop); FASTBOOT → POWER DOWN from the bootloader; adb reboot -p; adb shell → reboot -p.
So, what do I do now? (I apologize if I made some obvious mistake with the procedure described above, or with making this post…)
EDIT: I also forgot to mention that the Moonshine directory seems to contain a file called boot_backup.img; can it help me with anything?
i have a problem with s-on. this app solved.
thanks for s-off
Hi, i want to thank all the people involved into moonshine's s-off solution for villec2. I've run it on 64-bit Debian Wheezy. It worked perfect. Finally my One S is free .
I can't thank you on solution thread because i have not enough posts to post anywhere.
The CID for my One S was ORANGB10. It was bought in ORANGE PL.
Thanks again.
moonshine on stock ICS
Moonshine on stock ICS?
---------- Post added at 03:01 PM ---------- Previous post was at 02:30 PM ----------
Moonshine on stock ICS 4.0.4?
moonshine on stock ICS
Moonshine on stock ICS 4.0.4?
Aleksic82 said:
Moonshine on stock ICS 4.0.4?
Click to expand...
Click to collapse
moonshine request a jb bases rom but in runrummer dont say anything. They say runrummer run in a stock or another roM. So, checkout, try and coment!
JavierG123 said:
moonshine request a jb bases rom but in runrummer dont say anything. They say runrummer run in a stock or another roM. So, checkout, try and coment!
Click to expand...
Click to collapse
I would recommend to have a close to stock ROM for rumrunner too. I remember I've used Viper at that time for this purpose
Sent from nowhere over the air...
Rapier said:
I would recommend to have a close to stock ROM for rumrunner too. I remember I've used Viper at that time for this purpose
Sent from nowhere over the air...
Click to expand...
Click to collapse
i have 4.1.1. 3.20.518.102 CL175688 release-keys. can i use rumrunner?
moonshine on stock ICS
Hi every one, greetings from Serbia!! I have couple problems on my Htc one s ville2. 1. Can't unlock relocked bootloader, i many time try, its finish every segment ok htcdev, cmd, token, bin code, mobile phone accept, i click yes on ulock htc screen on mobile and enter power buton, restart phone, and up system, every ok, but not unlocked in bootloader, stay relocked. Phone its s-on, my phone (ICS 4.0.4)find OTA update and download, but cant install update, Verification Failed. S-on its problematic? Why i can't unlocked bootloader, i want to install twpr and flash officiall (and root) OTA update on my Htc.
Aleksic82 said:
Hi every one, greetings from Serbia!! I have couple problems on my Htc one s ville2. 1. Can't unlock relocked bootloader, i many time try, its finish every segment ok htcdev, cmd, token, bin code, mobile phone accept, i click yes on ulock htc screen on mobile and enter power buton, restart phone, and up system, every ok, but not unlocked in bootloader, stay relocked. Phone its s-on, my phone (ICS 4.0.4)find OTA update and download, but cant install update, Verification Failed. S-on its problematic? Why i can't unlocked bootloader, i want to install twpr and flash officiall (and root) OTA update on my Htc.
Click to expand...
Click to collapse
Search a RUU for your phone. maybe that work
moonshine on stock ICS
Yes i m, flash RUU and after that, i try to unlock bootloader, but i can't , many time i try... After that, in software update find last update, and downloading, every ok, but can't install, variant system version-raport. Any solution?
Aleksic82 said:
Hi every one, greetings from Serbia!! I have couple problems on my Htc one s ville2. 1. Can't unlock relocked bootloader, i many time try, its finish every segment ok htcdev, cmd, token, bin code, mobile phone accept, i click yes on ulock htc screen on mobile and enter power buton, restart phone, and up system, every ok, but not unlocked in bootloader, stay relocked. Phone its s-on, my phone (ICS 4.0.4)find OTA update and download, but cant install update, Verification Failed. S-on its problematic? Why i can't unlocked bootloader, i want to install twpr and flash officiall (and root) OTA update on my Htc.
Click to expand...
Click to collapse
Here is the thread for Ville S4 dunno anything about C2 and I won't recommend you to flash or use any procedure from here unless it's stated that works for C2. You might risk bricking your device otherwise
Sent from nowhere over the air...
Ok, i understand that. I have one question for every one, can i install ota update on s-on, s-off its need or not? I have on my htc one s ville 2 s-on, i cant unlock bootloader, always relocked, many, many times i try, one_kit_v, or easy Unlock tools or direct on htcdev, always phone acept comand end always acept on screen yes unlock press power key, but stay relocked. In app get cid from gp, says htc__044-asia wwe, but in cmd fastboot getvar cid stay 11111, im confused, many question, but no answer, i hope so its riff jtag box not only solution on my phone. Thanks anyway!
I guess having S-On for Ville C2 means same thing...that is, you must flash kernel in fastboot mode after every ROM flash.
So you could use OTA but after installing OTA you have to go to fastboot and flash the kernel from that OTA. It also means you should open the OTA zip on your PC and extract it from there to have it at hand when needed
Sent from nowhere over the air...
Rapier said:
I guess having S-On for Ville C2 means same thing...that is, you must flash kernel in fastboot mode after every ROM flash.
So you could use OTA but after installing OTA you have to go to fastboot and flash the kernel from that OTA. It also means you should open the OTA zip on your PC and extract it from there to have it at hand when needed
Sent from nowhere over the air...
Click to expand...
Click to collapse
Thanks man.
Flash kernel after RUU exe ICS update? I can't OTA install, phone its find, download but cat't, verifact- variant system version, can't install. From recovery, recovery error flash zip, cant find update, i think this problem caused s-on.
Aleksic82 said:
Ok, i understand that. I have one question for every one, can i install ota update on s-on, s-off its need or not? I have on my htc one s ville 2 s-on, i cant unlock bootloader, always relocked, many, many times i try, one_kit_v, or easy Unlock tools or direct on htcdev, always phone acept comand end always acept on screen yes unlock press power key, but stay relocked. In app get cid from gp, says htc__044-asia wwe, but in cmd fastboot getvar cid stay 11111, im confused, many question, but no answer, i hope so its riff jtag box not only solution on my phone. Thanks anyway!
Click to expand...
Click to collapse
Aleksic82 said:
Ok, i understand that. I have one question for every one, can i install ota update on s-on, s-off its need or not? I have on my htc one s ville 2 s-on, i cant unlock bootloader, always relocked, many, many times i try, one_kit_v, or easy Unlock tools or direct on htcdev, always phone acept comand end always acept on screen yes unlock press power key, but stay relocked. In app get cid from gp, says htc__044-asia wwe, but in cmd fastboot getvar cid stay 11111, im confused, many question, but no answer, i hope so its riff jtag box not only solution on my phone. Thanks anyway!
Click to expand...
Click to collapse
1-. if you want to install another RUU different at you CID you need be a S-OFF and SuperCID.
2-. if you want to install .zip rom flashed from recovery you DONT need be a S-OFF, but, after flash a rom you need flash boot.mg from fastboot.
3-.The problem with unlock boot loader its very strange, i relock and unlock boot loader a lot of time and no problems.
Hey guys
I sincerely apologize in advance if this is wrong thread to post such question in. Please be so kind to redirect me to the right thread, I just got registered
Here's my problem. Couple of days ago my phone (HTC One S, villec2, S-ON, here's the picture from bootloader http://tinypic.com/r/qo87k6/8) started behaving somewhat out of the order. Every process that was there, everything started throwing out errors with the likes of Google play has stopped working, Music has stopped working, Messages has stopped working, nothing was the same as it was before that. And nothing else like cleaning the phone with some apps from Google Play didn't help. Therefore, I decided to install myself a custom ROM
Phone was already rooted two days after I got it. It was pretty straightforward process really. That was two years ago. I needed root acess to install some app that required root acess, don't ask me which app was this because I don't remember, honestly. It also installed TWRP 2.6.0.0 and SuperSU
I downloaded ROM (this one in particular http://www.android.gs/update-htc-one-s-to-android-5-1-1-lollipop-with-resurrection-remix-5-4-4-custom-rom/), followed instructions, got into TWRP and this is when the turd hit the fan. Instructions said that I need to wipe my phone. I did just that, with one exepction - I wiped everything from my phone. Spare me saying that I'm an idiot, I've got over that fact already
Basically, TWRP said that no OS is installed. Everything was wiped out from internal SD card aswell, including my ROM file that I put on the phone. I tried with mounting USB storage, which got me into the SD card on my PC and I've put ROM file on it again. So I tried flashing the ROM with TWRP but it kept telling me that my device is not supported to install this ROM
So I was stuck in bootloader with option to flash TWRP.img file from fastboot enviroment on PC, nothing more than that
I've tried at least 4 different ROM-s. One got installed on my phone but when I rebooted my device it got stuck on HTC logo screen and kept rebooting (boot loop I think it's called) until I manually got into bootloader with combination of power down+volume down button
So I started looking for solutions. I found out, that there's two different "flavours" of HTC One S. One is ville, the other one is villec2, which I have. I've read all about RUU files that can help me recover my phone but after searching through http://androidruu.com/?developer=VilleC2 I found nothing that can help me. I've downloaded two different RUU's, locked and unlocked bootloader twice, rebooted RUU but none of them was compatible with my phone
I've seen something about OTA manual updates, which I also tried but it didn't do anything. I've tried flashing firmware.zip that I got from OTA update file, flashed boot.img but then the phone got to the point where it should update but it kept showing me red triangle. The only option was, again, to boot it into bootloader and I was back at square one
Then I read something about turning your phone S-OFF with that moonshine software and about installing any RUU I want without complications. So I got one and realized that I can't do anything with it because my phone only boots in bootloader and as far as I understand, you need to run distiller.exe while the device is turned on and it has to be in Android OS. Which is not an option with me, because as I said, I can only boot my phone into bootloader and then boot something else via fastboot commands on my PC
Am I screwed here? I've tried literally every single thing, I've looked over dozens of recovery guides for this phone but none of them worked for me. I heard that I need exactly the same ROM (matching CID and everything) that was previously installed on the device. Thing is that I didn't do any backup of stock ROM before all that fiasco. I've tried this site too http://forum.xda-developers.com/showthread.php?t=2200930 but all links seem dead, because it only shows me some advertisement things and nothing else
I know I got myself in a situation where anyone with a bit more brain than me would use this bricked phone as a paperweight but I'm stubborn enough to try just about everything to revive my device. At this moment it's stuck in bootloop. I can't boot into recovery because it only keeps rebooting over and over and over again. Fastboot recognizes my device if I type fastboot devices into command prompt but that's just about it
So please, if somebody has the slightest idea what am I to do, tell me all about it because I've ran out of ideas and there's nothing more to my knowledge to try at this point. Thanks in advance!