i have followed a lot of threads and tryed to root my phone again but nothing work, here is what i have;
i was in 1.85 and rooted, s-off, unlocked, then install RUU and again relocked, unlocked, still s-off (no changes here) hboot upgraded 2.14 and now i have 3.18 now need root again following this steps 1 of this steps present problems:
---------------------------------------
1. Go to the HTC Website and download HTC Sync Manager from here. Once installed ensure that it is not running. You can do this by going to Task Manager (Right Click Taskbar > Start Task Manager) > Processes > Then end the HSMServiceEntry.exe and htcUPCTLoader.exe processes.
2. Download the attached onxr.zip file that contains the files required to Root your phone.
3. Create a new folder on C:\ Drive called Android and then extract the Zip file into that location.
4. Connect up your phone to your computer using the USB cable that came with the phone.
5. Enabled USB Debugging. Settings > Developer Options > USB Debugging
6. Make sure the phone is in Charge Only mode by pulling down the Notification bar from the top of your screen, pressing on USB Connection Type and selecting Charge Only. HERE IS THE PROBLEM I CANT PUT THE PHONE IN MODE CHARGE ONLY, NOT GIVE ME THIS OPTION, WHEN I CONNECT THE CELL TO COMPUTER INMEDIATLY ACTIVE DEBUGG MODE AND SHOW ME IN MY PC UNIT E:/HTC ONE X (SD CARD) I CANT REMOVE THIS UNIT, I CANT STOP FROM COMPUTER
7. Browse to C:\Android and find the correspodning file to your operating system:
--------------------------------------------------
then i try run root.bat:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permission denied
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
REBOOT
/system/bin/sh: can't create /data/local.prop: Permission denied
AGAIN REBOOT
the phone restart 2 or 3 times but root not completed, i read some threads about this permission denied but no one have solution, i hope if some 1 happend the same thing please what to do i cant install twrp from fastboot (flashing complete, but twrp not installed (when try to join in recovery screen frezzed in red letters)
Jairoskov said:
i have followed a lot of threads and tryed to root my phone again but nothing work, here is what i have;
i was in 1.85 and rooted, s-off, unlocked, then install RUU and again relocked, unlocked, still s-off (no changes here) hboot upgraded 2.14 and now i have 3.18 now need root again following this steps 1 of this steps present problems:
---------------------------------------
1. Go to the HTC Website and download HTC Sync Manager from here. Once installed ensure that it is not running. You can do this by going to Task Manager (Right Click Taskbar > Start Task Manager) > Processes > Then end the HSMServiceEntry.exe and htcUPCTLoader.exe processes.
2. Download the attached onxr.zip file that contains the files required to Root your phone.
3. Create a new folder on C:\ Drive called Android and then extract the Zip file into that location.
4. Connect up your phone to your computer using the USB cable that came with the phone.
5. Enabled USB Debugging. Settings > Developer Options > USB Debugging
6. Make sure the phone is in Charge Only mode by pulling down the Notification bar from the top of your screen, pressing on USB Connection Type and selecting Charge Only. HERE IS THE PROBLEM I CANT PUT THE PHONE IN MODE CHARGE ONLY, NOT GIVE ME THIS OPTION, WHEN I CONNECT THE CELL TO COMPUTER INMEDIATLY ACTIVE DEBUGG MODE AND SHOW ME IN MY PC UNIT E:/HTC ONE X (SD CARD) I CANT REMOVE THIS UNIT, I CANT STOP FROM COMPUTER
7. Browse to C:\Android and find the correspodning file to your operating system:
--------------------------------------------------
then i try run root.bat:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permission denied
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
REBOOT
/system/bin/sh: can't create /data/local.prop: Permission denied
AGAIN REBOOT
the phone restart 2 or 3 times but root not completed, i read some threads about this permission denied but no one have solution, i hope if some 1 happend the same thing please what to do i cant install twrp from fastboot (flashing complete, but twrp not installed (when try to join in recovery screen frezzed in red letters)
Click to expand...
Click to collapse
...If your bootloader is unlocked, just flash recovery and flash su. You don't need to go through all that again. That was all to get an unlocked bootloader, which you already have.
Does your bootloader say locked, relocked, or unlocked?
exad said:
...If your bootloader is unlocked, just flash recovery and flash su. You don't need to go through all that again. That was all to get an unlocked bootloader, which you already have.
Does your bootloader say locked, relocked, or unlocked?
Click to expand...
Click to collapse
when i installed RUU was RELOCKED but i follow the proces for UNLOCKED again and its ok now is UNLOCKED.
AFTER RUU.
1.85
UNLOCKED
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24P.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
NOV 26 2012,18:37:14-1
BEFORE RUU
3.18
UNLOCKED
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
i enter in fastboot mode and flash twrp 2.5.0.0 and not work, flashing complete but when tryed to go recovery the cell dont to nothing, i should try flash su file? and i have root checker app and say "you are not root acces" installed superuserAP too, and say "binary missing, this is a problem".
i dont know what more to do i want install new rom this stock 4.1.1 3.18 suck, wifi theatering not work and charge mode onl not work.
Jairoskov said:
when i installed RUU was RELOCKED but i follow the proces for UNLOCKED again and its ok now is UNLOCKED.
AFTER RUU.
1.85
UNLOCKED
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24P.32.09.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
NOV 26 2012,18:37:14-1
BEFORE RUU
3.18
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-1.09.0000
RADIO-0.17.32.09.12
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
i enter in fastboot mode and flash twrp 2.5.0.0 and not work, flashing complete but when tryed to go recovery the cell dont to nothing, i should try flash su file? and i have root checker app and say "you are not root acces" installed superuserAP too, and say "binary missing, this is a problem".
i dont know what more to do i want install new rom this stock 4.1.1 3.18 suck, wifi theatering not work and charge mode onl not work.
Click to expand...
Click to collapse
Use twrp 2.3.3.1 nothing higher
Sent from my HTC One XL using xda premium
You need to install the super user zip file or flash a rom in recovery. (31Ken31 is right about the version)
Download recovery and be sure to check the MD5 before flashing. You could have a bad download causing you issues.
If it STILL freezes while loading recovery after flashing recovery that you've verified the MD5 for,
RUU again and then try again. (I've seen that problem before) If you are S-OFF, you don't need to lock your bootloader to RUU.
31ken31 said:
Use twrp 2.3.3.1 nothing higher
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
i have downloader 2.3.3.0 and flash and now when join in recovery show red letter "this method is for developed options etc etcetc" and then black screen and i have to force restart, when i flash recovery i write "fastboot flash recovery twrp.img" for flash super user how is?
Jairoskov said:
i have downloader 2.3.3.0 and flash and now when join in recovery show red letter "this method is for developed options etc etcetc" and then black screen and i have to force restart, when i flash recovery i write "fastboot flash recovery twrp.img" for flash super user how is?
Click to expand...
Click to collapse
Flashing superuser is done in recovery like a rom. You need to flash recovery properly before you can do anything. Make sure your download of TWRP is not corrupt. As I said if your download of TWRP is not corrupt(md5 matches) and it's still not booting into recovery, RUU again and then try flashing recovery again. use 2.3.3.1 so you don't need to downgrade your touchscreen firmware to use it.
31ken31 said:
Use twrp 2.3.3.1 nothing higher
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
excuse me the question, how to prove MD5 matches? i download the program FlashSFV 2.6 but im not sure if this work.
this when try to test root acces
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL] Uploaded with ImageShack.us[/IMG]
my info
[/URL] Uploaded with ImageShack.us[/IMG]
when tryed to go recovery after install twrp flashed by fastboot
pictures are X
Nevermind, pulled links from properties and checked them. Do what I suggested in my last post.
Remember, if the MD5 of the TWRP you downloaded matches and still doesn't flash, Run the RUU again and then try flashing twrp again. And don't forget to do fastboot erase cache after flashing twrp.
You do not need to relock your bootloader to RUU since you are S-OFF.
exad said:
pictures are X
Nevermind, pulled links from properties and checked them. Do what I suggested in my last post.
Remember, if the MD5 of the TWRP you downloaded matches and still doesn't flash, Run the RUU again and then try flashing twrp again. And don't forget to do fastboot erase cache after flashing twrp.
You do not need to relock your bootloader to RUU since you are S-OFF.
Click to expand...
Click to collapse
fastboot erase cache "after install twrp" and not work
i tryed other methods with adb shell
C:\X_Factor>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found (su not found )
127|[email protected]:/ $
any other idea?
twrp cant install!!!!
i want take the risk installing new ROM with fastboot, this is possible?
Jairoskov said:
fastboot erase cache "after install twrp" and not work
i tryed other methods with adb shell
C:\X_Factor>adb shell
[email protected]:/ $ su
su
/system/bin/sh: su: not found (su not found )
127|[email protected]:/ $
any other idea?
twrp cant install!!!!
i want take the risk installing new ROM with fastboot, this is possible?
Click to expand...
Click to collapse
If you cannot manage to get TWRP to install you should not even be rooting. That's the most basic part of the entire rooting/flashing process. I already told you RUU and then flash twrp and then fastboot erase cache. Did you RUU?
You really seem to have very little idea what you're doing and if you can't get TWRP to install, you should not even be attempting to root. I am not trying to be mean. I am simply warning you.
No, you cannot flash a rom with fastboot.
exad said:
If you cannot manage to get TWRP to install you should not even be rooting. That's the most basic part of the entire rooting/flashing process. I already told you RUU and then flash twrp and then fastboot erase cache. Did you RUU?
You really seem to have very little idea what you're doing and if you can't get TWRP to install, you should not even be attempting to root. I am not trying to be mean. I am simply warning you.
No, you cannot flash a rom with fastboot.
Click to expand...
Click to collapse
Hahaha bull****. You are a big troll. A noob that has been usong android for one month and thinks he already knows android. Yes you can flash a rom with fastboot. Go learn. And who are you to tell people they should or shouldn't root? Loser
Sent from my HTC One X using xda premium
-_- fine flash your ROM with fast boot then. And who I am is the guy who's been helping people on this forum every day for quite some time and also the guy who's trying to keep you from brciking your phone. Your insults don't bother me
Sent from my One X using xda app-developers app
maldinimi said:
Hahaha bull****. You are a big troll. A noob that has been usong android for one month and thinks he already knows android. Yes you can flash a rom with fastboot. Go learn. And who are you to tell people they should or shouldn't root? Loser
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
When you brick it let me know I'll buy it for parts
Sent from my HTC One XL using xda premium
maldinimi said:
Hahaha bull****. You are a big troll. A noob that has been usong android for one month and thinks he already knows android. Yes you can flash a rom with fastboot. Go learn. And who are you to tell people they should or shouldn't root? Loser
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Good luck getting to get anybody to help you now.
By the way, do yourself a favor and take a look at some of Exad's posts. You might wanna retract that bull**** statement.
Sent from my Evita
maldinimi said:
Hahaha bull****. You are a big troll. A noob that has been usong android for one month and thinks he already knows android. Yes you can flash a rom with fastboot. Go learn. And who are you to tell people they should or shouldn't root? Loser
Click to expand...
Click to collapse
Speaking of losers, cya around the next time you create a new XDA account
exad said:
If you cannot manage to get TWRP to install you should not even be rooting. That's the most basic part of the entire rooting/flashing process. I already told you RUU and then flash twrp and then fastboot erase cache. Did you RUU?
You really seem to have very little idea what you're doing and if you can't get TWRP to install, you should not even be attempting to root. I am not trying to be mean. I am simply warning you.
No, you cannot flash a rom with fastboot.
Click to expand...
Click to collapse
wow im back and its not good see this ppl insulting when you really are helping a lot of ppl here, anyways this comments must be ignored and let him go away, in other side i will RUU today and i will let you know about what happend when finish , because im very frustrated my screen every day is worst, one time i not remember what i do but the complete screen was working and then worst again
well when finish RUU i will write again...
Jairoskov said:
wow im back and its not good see this ppl insulting when you really are helping a lot of ppl here, anyways this comments must be ignored and let him go away, in other side i will RUU today and i will let you know about what happend when finish , because im very frustrated my screen every day is worst, one time i not remember what i do but the complete screen was working and then worst again
well when finish RUU i will write again...
Click to expand...
Click to collapse
Don't worry, we'll be here awaiting your update! :good:
exad said:
Don't worry, we'll be here awaiting your update! :good:
Click to expand...
Click to collapse
ok, i made clear install RUU again, the next step is:
restart phone in fastboot mode
-fastboot flash recovery twrp.img
-fastboot erase cache
-fastboot reboot-fasboot
then i using volume buttons i will join in to recovery.
its this right?
will wait until u answerme before do anything.
Yes that sounds right to me
Sent from my Evita
Related
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 have also created an automated Tool for S-Off . Those who find this guide difficult to understand and download and use the tool from the thread
HERE
After the advanced ace hack kit (AAHK) was taken down, it was a bit tough to get an S-Off on our devices. The existing guides never explained anything much.
So , I will be explaining and trying to simplify the S-Off method for HTC Desire HD.
Please note: I take absolutely no CREDIT for this. All I have done is simplified it.
The following goes unsaid.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about directions in this method
* before following it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Please donot ask me what fastboot mode is or how to boot into it or the advantages of an "S-OFF". I have only made this guide a bit simplified , but not noob friendly. This is still for advanced users and in addition for intermediate users.
Requirements
Your device must be rooted and the bootloader must be unlocked
Android sdk tools must be installed
Please make sure you have the Unlock_code.bin that you used to unlock the bootloaders since you will need it.
Most Important : Please follow the instructions exactly, Don't exit from shell unless I ask you to. I will not entertain any PMs or posts if you don't follow them.
Directions
I would prefer using a linux machine for this, but the choice is upto you.
1 . Download and extract this and cd into the directory in your terminal / CMD window and push the following files
Code:
#~adb push misc_version /data/local/tmp
#~adb push goldcard /data/local/tmp
#~adb push gfree /tmp/
2 . Make sure you have the original "boot.img" of your ROM on you PC HDD.
3 . Make a Goldcard in the following way
Code:
#~adb shell
$~su
#~chmod 775 /data/local/tmp/goldcard
#~cat /sys/class/mmc_host/mmc2/mmc2:*/cid
This will generate the CID. Copy the generated CID
Code:
#~/data/local/tmp/goldcard -c <YOUR_CID_HERE> -o /data/local/tmp/goldcard.img
#~dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1
This should create the Goldcard.
4. Next to lower the main version
Code:
#~chmod 775 /data/local/tmp/misc_version
#~/data/local/tmp/misc_version -s 1.11.111.1
#~reboot bootloader
5. Next relock the bootloader
Code:
#~fastboot oem lock
6. Flash the firmware.zip in RUU
Code:
#~fastboot oem rebootRUU
#~fastboot flash zip firmware.zip
#~fastboot reboot-bootloader
7. Unlock bootloader with the Unlock_code.bin got from HTC's Developer site
Code:
#~fastboot flash unlocktoken Unlock_code.bin
8. Next flash your ROM's boot.img
Code:
#~fastboot flash boot boot.img
9. Next flash the recovery.img
Code:
#~fastboot flash recovery recovery.img
#~fastboot boot recovery.img
Don't worry : The screen will stay blank. ADB will work.
10. Now to S-OFF...
Code:
#~adb shell
#~chmod 775 /tmp/gfree
#~/tmp/gfree -f
#~reboot bootloader
Now the device will reboot to bootloader. And you will see that your device as been S-Offed.
11. Next step is to enter fastboot mode on the device. (Please keep the device connected to the PC)
Choose the appropriate Hboot_xxxx.zip file for your phone
Code:
#~fastboot oem rebootRUU
#~fastbbot flash zip hboot_xxxxx.zip
#~fastboot reboot
12. Now flash CWM recovery
Download file from here
Pull battery out and reinsert. Boot phone to fastboot mode.
Connect to PC.
Code:
#~fastboot flash recovery recovery-clockwork-touch-5.8.1.5-ace.img
That's it!! Now flash your favourite ROM and reboot.
CREDITS
The Guy who posted the original method here
Cheers!!
Module returned an unknown code (No such file or directory).
Hmm, i tried this, but at the last few steps (tmp/gfree -f) i get this error,
Code:
Attempting to power cycle eMMC... Failed. Module returned an unknown code (No such file or directory).
i rebooted into the bootloader and the status was still:
"***** AAHK *****
ACE PVT ENG S-ON RL
HBOOT-0.85.2425
etc, etc
my device was fully s-off before this, I'm not a noob either lol
humzaahmed155 said:
Hmm, i tried this, but at the last few steps (tmp/gfree -f) i get this error,
Code:
Attempting to power cycle eMMC... Failed. Module returned an unknown code (No such file or directory).
i rebooted into the bootloader and the status was still:
"***** AAHK *****
ACE PVT ENG S-ON RL
HBOOT-0.85.2425
etc, etc
my device was fully s-off before this, I'm not a noob either lol
Click to expand...
Click to collapse
Did you run this as root in adb ?
deathscream said:
Did you run this as root in adb ?
Click to expand...
Click to collapse
I ran the process in recovery, I didn't think I'd have to use su to complete the process, I'll try it again with root access
Sent from my Desire HD using Tapatalk 4
Edit: followed it step by step on linux as well, while doing "adb push gfree /tmp/" i got the error "failed to copy 'gfree' to '/tmp/': Is a directory"
atleast when you explain the guide you need to explain that you need a STOCK rom, not anything else.you must have 2.3.5 with the stock kernel and gfree will work then.Any other ROM/Kernel combo and it will give the same error.
Steam. said:
atleast when you explain the guide you need to explain that you need a STOCK rom, not anything else.you must have 2.3.5 with the stock kernel and gfree will work then.Any other ROM/Kernel combo and it will give the same error.
Click to expand...
Click to collapse
Oh right okay, I was running cm10.1 the whole time /: I'll try with a stock rooted ROM
Sent from my Desire HD using Tapatalk 4
Steam. said:
atleast when you explain the guide you need to explain that you need a STOCK rom, not anything else.you must have 2.3.5 with the stock kernel and gfree will work then.Any other ROM/Kernel combo and it will give the same error.
Click to expand...
Click to collapse
Well it's not true. I ran this running cm10.1 pipeliner's rom .
deathscream said:
Well it's not true. I ran this running cm10.1 pipeliner's rom .
Click to expand...
Click to collapse
Hmm, any ideas on why it isn't working?
Sent from my Desire HD using Tapatalk 4
humzaahmed155 said:
Hmm, any ideas on why it isn't working?
Sent from my Desire HD using Tapatalk 4
Click to expand...
Click to collapse
go ahead try it on stock, you'll see it will work right off the bat.
backup your current rom, it's easy to restore afterwards.why go through all the trouble when the solution is nitr00's rooted stock rom.
Steam. said:
go ahead try it on stock, you'll see it will work right off the bat.
backup your current rom, it's easy to restore afterwards.why go through all the trouble when the solution is nitr00's rooted stock rom.
Click to expand...
Click to collapse
Yeah I'm just going to do a nandroid, flash the ROM, and get it over with, at the start I had the official eng boot loader, the 0.85.***7 one, I saw the aahk one and wanted that because it was newer (generally I go for the latest version on everything ) I flashed it over fastboot and ended up having s-on, it was pretty annoying to find that the tool I used to get the other eng boot loader quit working too (Easy one click s-off)
Sent from my Desire HD using Tapatalk 4
Annoyingly enough, every gingerbread sense rom that i flash gets stuck at a black screen just after the splash screen, adb will not pick it up either.
Hold the phone! I forgot to flash the boot.img seperately
Yet another edit: i'm still getting the error "Failed to copy 'gfree' to '/tmp/': Is a directory" I'm running the stock rooted rom too.
I found the problem, it was indeed a typo on your part, '/tmp/' isn't a directory when it has the slash at the end too, its supposed to be "/tmp"
Completed the whole process using the guide on the aahk website instead
Hey guys,
I have a serious problem with my at&t htc one x, first time when i wanted to install a custom rom, i didn't backup ( i know my fault)
i had some problems with installation that drives me to change my cid to HTC_621 ( i don't know why i changed the 1st time, im noob)
now i can only install custom roms like viperXL and also,but it drains my battery,so i want to go back to stock room, or CM10.2 but i can't, when i try RUU it always give me an error, and when i downloaded the CM10.2.zip and tried to flash it via twrp it says Installation Failed. im totally confused and need real help.
my HBOOT infos:
Tampered
Unlocked
EVITA PVT SHIP S ON RL
HBOOT 1.14.0002
RADIO 0.19as.32.09.11_2
OpenDSP-v29.1.0.45.622
eMMC-boot
Jun 11 201. 14:36
What's your Cid? It should be 1111 etc.. Make sure ur super cid, then s- off.. After following those steps then try running the RUU
Sent from my Nexus 4 using XDA Premium 4 mobile app
zinter95 said:
Hey guys,
I have a serious problem with my at&t htc one x, first time when i wanted to install a custom rom, i didn't backup ( i know my fault)
i had some problems with installation that drives me to change my cid to HTC_621 ( i don't know why i changed the 1st time, im noob)
now i can only install custom roms like viperXL and also,but it drains my battery,so i want to go back to stock room, or CM10.2 but i can't, when i try RUU it always give me an error, and when i downloaded the CM10.2.zip and tried to flash it via twrp it says Installation Failed. im totally confused and need real help.
my HBOOT infos:
Tampered
Unlocked
EVITA PVT SHIP S ON RL
HBOOT 1.14.0002
RADIO 0.19as.32.09.11_2
OpenDSP-v29.1.0.45.622
eMMC-boot
Jun 11 201. 14:36
Click to expand...
Click to collapse
Why did you change the CID to HTC__621? That doesn't even look like it's for our device. That's the reason the RUU is failing.
The reason cm10.2 won't boot is because you need to RUU to 3.18 with the 2.14 hboot to flash that ROM, it does state that clearly in the install instructions for that ROM.
You're gonna need to get SuperCID first, then you can get s-off, then you can RUU to 3.18, then you can flash the cm10.2 ROM.
Sent from my Evita
I tried to SuperCID but i couldnt, i tried the hex editor way, but it gives me always errors, i guess thats why i can s-off.
Any solutions?
Ok, but why did you change it HTC__621? I don't think that's a CID for our device, were you trying to install software or something? The only problem is that without s-off you can only manually change the CID once, and you've used that one chance up by changing it to HTC__621. As far as a solution goes I'm not sure, there are a few different methods to change your CID, I'd suggest you try them all.
Sent from my Evita
zinter95 said:
I tried to SuperCID but i couldnt, i tried the hex editor way, but it gives me always errors, i guess thats why i can s-off.
Click to expand...
Click to collapse
SuperCID is mandatory for the s-off method. So yes, that is why you can't s-off.
i changed my cid to 11111111 now, but i still cannot change it to s-off i followed the instructions but i always failed.
You need to give more info. Where in the process did it fail?
Sent from my Evita
At the first time i failed when i type that code;
Code:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
and when i wanted to try another time it keeps failing in the step before that one.
You're not being very specific, just saying it fails doesn't help diagnosing the problem.
Have you extracted the soffbin zip into the fastboot folder as per the instructions? Do you have usb debugging enabled in developer options? If applicable (on aosp ROM) have you granted adb root access in developer options?
When you say the step before that one, you mean the fastboot flash zip command right? And my guess is that you're getting error 99 instead of error 92? If you get error 99, force a reboot into the bootloader (by holding volume down and power) and start again from the beginning.
Sent from my Evita
timmaaa said:
You're not being very specific, just saying it fails doesn't help diagnosing the problem.
Have you extracted the soffbin zip into the fastboot folder as per the instructions? Do you have usb debugging enabled in developer options? If applicable (on aosp ROM) have you granted adb root access in developer options?
When you say the step before that one, you mean the fastboot flash zip command right? And my guess is that you're getting error 99 instead of error 92? If you get error 99, force a reboot into the bootloader (by holding volume down and power) and start again from the beginning.
Sent from my Evita
Click to expand...
Click to collapse
heey, im in this step right now
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
any time i run that command it says Device offline or device not found, but i have the latest updates of htc synmanager ..
im running RageXl 1.03 ROM.
How can i solve it please?
Uninstall HTC Sync Manager but leave the drivers installed. Make sure you have usb debugging enabled in developer options. When you try again you might get error 99 instead of error 92 after flashing the zip st the beginning. If this happens, force a reboot back to bootloader by holding volume down and power and start again from the beginning of the process.
Sent from my Evita
timmaaa said:
Uninstall HTC Sync Manager but leave the drivers installed. Make sure you have usb debugging enabled in developer options. When you try again you might get error 99 instead of error 92 after flashing the zip st the beginning. If this happens, force a reboot back to bootloader by holding volume down and power and start again from the beginning of the process.
Sent from my Evita
Click to expand...
Click to collapse
i uninstalled htc syn manager but it still telling me device offline!!!!!!!!!!!!!!!!!
Wow, that's a lot of exclamation marks. Maybe you need to try on a different ROM. Check your drivers, check adb, make sure usb debugging is enabled. It's almost impossible for me to diagnose what's going on without being there, you need to troubleshoot it.
Sent from my Evita
timmaaa said:
You're not being very specific, just saying it fails doesn't help diagnosing the problem.
Have you extracted the soffbin zip into the fastboot folder as per the instructions? Do you have usb debugging enabled in developer options? If applicable (on aosp ROM) have you granted adb root access in developer options?
When you say the step before that one, you mean the fastboot flash zip command right? And my guess is that you're getting error 99 instead of error 92? If you get error 99, force a reboot into the bootloader (by holding volume down and power) and start again from the beginning.
Sent from my Evita
Click to expand...
Click to collapse
Heey,
I installed an aosp rom, and everything was going alrgiht until the last step , the last command;
C:\Android>adb shell su -c "/data/local/tmp/soffbin3.zip"
/data/local/tmp/soffbin3.zip[2]: ┴¹Í♣î¶: not found
/data/local/tmp/soffbin3.zip[4]: syntax error: '³' unexpected
/data/local/tmp/soffbin3.zip[2]: ©╚ÇÎ⌂idþº╬R░4↔´NØU÷Å┘)È¿jØ&j+ò╩U¿PñF╩‗ÇTAäBÑJÇJ
ôç
►╝D<B}░wYQéäèÈ─ï¨╬▄;╗wªnEÃ>{¯╣þþ×{¯╣?þ╣╣┼yMË╚*ö: not found
/data/local/tmp/soffbin3.zip[2]: ┘ªnc↕♂mè◄←ßîÃÚ: not found
/data/local/tmp/soffbin3.zip[2]: can't create │╗▒Î÷: Read-only file system
/data/local/tmp/soffbin3.zip[2]: ô♦ý☻─Q└: not found
/data/local/tmp/soffbin3.zip[2]: ª↕Wê2└Ù}▄G╗2öó^*▲ñ¹®ç♦/│.×: not found
C:\Android>
i dont know whats the problem, may you help me?
What language and locale is your Windows and phone set to?
To me it looks like an application that does not correctly handle non-English locales.
Or something is corrupt.
twistedddx said:
What language and locale is your Windows and phone set to?
To me it looks like an application that does not correctly handle non-English locales.
Or something is corrupt.
Click to expand...
Click to collapse
my phone is set to english and my computer to french!but i dont think thats the problem.
anyone can help me guys??
You've entered the command incorrectly. There should be no ".zip" at the end of the command. Because of this I'm also assuming you haven't extracted (unzipped) the soffbin zip file into your adb/fastboot folder? Read the instructions on the s-off thread again, you must follow them absolutely precisely with no deviations.
Sent from my Evita
timmaaa said:
You've entered the command incorrectly. There should be no ".zip" at the end of the command. Because of this I'm also assuming you haven't extracted (unzipped) the soffbin zip file into your adb/fastboot folder? Read the instructions on the s-off thread again, you must follow them absolutely precisely with no deviations.
Click to expand...
Click to collapse
Yeah, when modding your phone, don't improvise or add things, unless you are positive of what you are doing. Folks have bricked their phones by not following instructions exactly.
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*
I want to install "[ROM][AROMA] KickDroidXL v5.2.0" but my htc one x (at&t) is completely stock.
So: step 1: unlocked with htcdev.com
step 2: Custom recovery
step 3: Firmware
Based on the "you need" info
Step 4: flash rom.
(I think i will s-off as well my mobile)
My questions are:
1) Is there any problem if i keep stock recovery?
2) On firmware instructions that is given here: "http://forum.xda-developers.com/showthread.php?t=2485865" 4th post
how should i do this throught commands (i use windows) or through my phone's screen when it is powered up by volume down and power buttons??
thanks a lot!
ps.christos said:
I want to install "[ROM][AROMA] KickDroidXL v5.2.0" but my htc one x (at&t) is completely stock.
So: step 1: unlocked with htcdev.com
step 2: Custom recovery
step 3: Firmware
Based on the "you need" info
Step 4: flash rom.
(I think i will s-off as well my mobile)
My questions are:
1) Is there any problem if i keep stock recovery?
2) On firmware instructions that is given here: "http://forum.xda-developers.com/showthread.php?t=2485865" 4th post
how should i do this throught commands (i use windows) or through my phone's screen when it is powered up by volume down and power buttons??
thanks a lot!
Click to expand...
Click to collapse
Here are your steps:
Before I can give any advice on the steps you need to take I need to see your bootloader details, the first five lines will do. I can answer your questions though.
1. You can't keep the stock recovery, a custom recovery is required on a modified phone.
2. The commands are issued through a command prompt on a Windows PC (you need to have adb/fastboot installed on the PC).
Sent from my Evita
timmaaa said:
Here are your steps:
Before I can give any advice on the steps you need to take I need to see your bootloader details, the first five lines will do. I can answer your questions though.
1. You can't keep the stock recovery, a custom recovery is required on a modified phone.
2. The commands are issued through a command prompt on a Windows PC (you need to have adb/fastboot installed on the PC).
Sent from my Evita
Click to expand...
Click to collapse
There are some changes of the planes and because of lack "playing" with my mobile i haven't reply you. So i desided to go for CyanogenMod 11.0 so instractions are:
" 1.S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
2.Update to 3.18 RUU or later.
3.Flash a custom recovery (TWRP/CWM with SELinux capabilities).
4.Download latest nightly from http://download.cyanogenmod.org/?device=evita.
5.Locate 4.4 Gapps via a quick Google search.
6.Wipe factory/data reset in recovery before installing CM11.0 (unless you are already on a CM11.0 build).
7.Reboot into recovery and install nightly and gapps."
Before the instraction i think i should root and unlock the bootloader, so i used "[TOOL] HTC One X (Evita) All-In-One Toolkit V3.0.1 [7-7-2013] [PERM ROOT][Noob-Proof]" to unlock bootloader and root the phone. I have done this. I will (haven't do it yet) s-off and then flash custom recovery. Then it is the easy part i thing, (same as in every device, i have done it to htc desire).
So my question is am i rooted? Some apps like titanium backup and adfree gives me error, that is why i am thinging or i am not rooted or i have to "gain" su access through terminal. For flashing custome recovery i will use "[TOOL] HTC One X (Evita) All-In-One Toolkit V3.0.1 [7-7-2013] [PERM ROOT][Noob-Proof]" and for s-off i will try to use this guide "[S-Off] Facepalm S-Off for HTC One XL" any easier suggestions about s-off??
So to make our life easier here is what i get form power button + volume down:
*** UNLOCKED ***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Forget about using the toolkit, all it does is act as a crutch and it clearly hasn't succeeded in rooting your device. Plus, it removes some vital learning experience which you definitely need.
You don't need root yet if you're going to flash a custom ROM. All that's required to install a custom recovery is an unlocked bootloader which you already have. The custom ROMs you want to install are pre-rooted.
To install a recovery is very simple, all it takes is a few fastboot commands. Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Once you've done this all you need to do is find a ROM and gapps and install them. Take a look at the Evita FAQ thread and the How-To Guide For Beginners thread in my signature, they contain some very valuable information that you'll need.
Sent from my Evita
timmaaa said:
Forget about using the toolkit, all it does is act as a crutch and it clearly hasn't succeeded in rooting your device. Plus, it removes some vital learning experience which you definitely need.
You don't need root yet if you're going to flash a custom ROM. All that's required to install a custom recovery is an unlocked bootloader which you already have. The custom ROMs you want to install are pre-rooted.
To install a recovery is very simple, all it takes is a few fastboot commands. Download the modified version of TWRP 2.6.3.0 from here. Put the file in your fastboot folder. Connect phone in fastboot mode, open command prompt from within fastboot folder, issue the following commands:
Code:
fastboot flash recovery "filename.img"
(the exact filename, minus the talking marks)
Code:
fastboot erase cache
Code:
fastboot reboot-bootloader
Once you've done this all you need to do is find a ROM and gapps and install them. Take a look at the Evita FAQ thread and the How-To Guide For Beginners thread in my signature, they contain some very valuable information that you'll need.
Sent from my Evita
Click to expand...
Click to collapse
I found what i did wrong so now i have root my mobile! The guide that you posted is very helpfull, thanks for that! One last question though (hopefully last) i still have to go s-off for flashing CyanogenMod 11.0 since it is in the installation procedure right?? Thanks again.
You do need s-off, because you need to run the 3.18 RUU in order to flash any current aosp ROM. You must have s-off before you run the RUU or you'll brick.
Sent from my Evita
timmaaa said:
You do need s-off, because you need to run the 3.18 RUU in order to flash any current aosp ROM. You must have s-off before you run the RUU or you'll brick.
Sent from my Evita
Click to expand...
Click to collapse
I have done everything exept s-off. So now what i get in the "info" screen is what i had before, but at the begging it says *** TAMPERED *** , root works as well. The thing is i tried s-off using this method "http://forum.xda-developers.com/showthread.php?t=2155071" and i had exactly what it says i mean both in screens and the 92 error, but i always was s-on when system boot to bootloader at the end. I tried more times and after a point i tried the toolkit, from that point error 92 turned to error 99 (unkown error). Now this holds for both ways that i try. Any ideas what i do wrong? By the way i made a backup before starting the whole procedure. Thanks again and sorry for asking, but everything else was solven by reading and i can not reach as many info about s-off as it was for root.
The tampered flag in your bootloader is normal, that means you have root, nothing to worry about. The error 99 problem can be solved by forcing a reboot to the bootloader (directly after getting error 99) by using the volume down + power button combo, then starting the s-off procedure again from the beginning. Or you could try the Rumrunner s-off method instead. That does require an unsecured kernel though so if you're still on a stock ROM it probably won't work. It should work if you flash the Kickdroid ROM first though.
Sent from my One XL using XDA Premium 4 mobile app
timmaaa said:
The tampered flag in your bootloader is normal, that means you have root, nothing to worry about. The error 99 problem can be solved by forcing a reboot to the bootloader (directly after getting error 99) by using the volume down + power button combo, then starting the s-off procedure again from the beginning. Or you could try the Rumrunner s-off method instead. That does require an unsecured kernel though so if you're still on a stock ROM it probably won't work. It should work if you flash the Kickdroid ROM first though.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just show the so wanted s-off. I read somewhere that error 99 will turn to "normal error 92" after rebooting. So yesterday i did 3 reboots and felt to sleep and today i tried the same procedure and now i am s-off! Sorry for the nagging!!
timmaaa said:
The tampered flag in your bootloader is normal, that means you have root, nothing to worry about. The error 99 problem can be solved by forcing a reboot to the bootloader (directly after getting error 99) by using the volume down + power button combo, then starting the s-off procedure again from the beginning. Or you could try the Rumrunner s-off method instead. That does require an unsecured kernel though so if you're still on a stock ROM it probably won't work. It should work if you flash the Kickdroid ROM first though.
Sent from my One XL using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok i need your help again, if it is possible. I try to flash cm11 rom and i got the:
"E:error executing updater binary in zip ..........
E: error installing the zip file ......."
So i did my research and i thing the problem is due to recovery, right??
In this threat "[Q&A][CM 10.1][4.2.2] CyanogenMod 10.1 Questions and Help thread"
you have said: " Originally Posted by timmaaa View Post
No you can't use TWRP 2.6, you need to use the unofficial modified version of TWRP 2.6.3.0 from our Original Android Development section."
The thing is i am using TWRP 2.6.3.0 downloaded from here: "http://forum.xda-developers.com/showthread.php?t=1677447" should i go for "http://forum.xda-developers.com/showthread.php?t=2558503"??????
some more details (bootloader details):
*** UNLOCKED ***
EVITA PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v34.1.0.45.1219
e-MMC-boot
Thank you very much.
Well, only one of those links contains the unofficial modified TWRP 2.6.3.0 which is 4.4 compatible, so the answer should be simple.
Sent from my Evita
timmaaa said:
Well, only one of those links contains the unofficial modified TWRP 2.6.3.0 which is 4.4 compatible, so the answer should be simple.
Sent from my Evita
Click to expand...
Click to collapse
Do you know if there might be a problem with compatibility?? I mean if i try to restore back up made with TWRP 2.5 when i have the unofficial modified TWRP 2.6.3.0??i bet there is a backwords compatibility, right?
thanks again!
From all reports I've seen, they're not compatible. But even if you didn't want to flash KitKat ROMs you should never use TWRP 2.5 because it's super buggy and will cause issues. I'd say just flash the unofficial TWRP 2.6.3.0 and install the KitKat ROM of your choice. If you need to go back to stock there are other ways apart from a backup you can do it.
Sent from my Evita