[Guide] How to Downgrade Latest Hboot 2.00.0002>> without using HTC Dev V2 - HTC Desire S

This method works for software version 2.11 and above and doesn't work for version 2.10 below.. Please use zegRush if this doesn't work for you.
FOR PHONES THAT ARE NOT ROOTED
Note: For locked bootloaders only. Do not use Htc dev prior to using this guide.
First thanks to:
1. mtothearkus
2.petarpLab..
3.jcase for TacoRoot..
4. amidabuddha
5.zryvffn (misc_version_universal)
I AM NOT RESPONSIBLE FOR ANYTHING THAT MAY HAPPEN TO YOUR DEVICE..
This was tested on latest OTA ASIA 2.15.xx with latest Hboot 2.00.0002.
Latest 2.15 cannot be rooted with zegRush so did some research..
Things Needed:
1.tacoroot
2.misc_version (download attachments below)
3.OLDEST RUU for your "REGION/ BRAND".. i repeat, specific region to avoid customer ID error.
4. adb (you know how it works)
5. phone in USB debugging mode.
STEPS:
1. download tacoroot and misc and put all files in your desired directory.
2. Run terminal and change location to where you files are.
3. now type:
Code:
adb push tacoroot.bin /data/local/tmp/tacoroot
adb push misc_version /data/local/tmp/
4.After pushing all the files, run tacoroot by typing:
Code:
adb shell
chmod 777 /data/local/tmp/*
/data/local/tmp/tacoroot --setup
5. After this commands your phone "REBOOT" the phone to recovery. Now press vol up then power then REBOOT to boot the phone normally. Wait till it boots completely and then type:
Code:
adb shell
/data/local/tmp/tacoroot --root
6.This command will gets you out of adb shell.. so we need to get back to adb shell and you will see "#" sign..meaning you are temp rooted and we can then proceed to changing MISC_VERSION:
Code:
adb shell
cd /data/local/tmp
./misc_version -s 1.27.405.6
7. After its done you can now flash your "REGION/ BRAND specific RUU".
8. After your done with RUU. Proceed to http://revolutionary.io..
Happy Flashing
FOR ROOTED PHONES
*Proceed with:
STEP 3
STEP 6
STEP 7
STEP 8
-Done
*Added misc_version_universal thanks to zryvffn

Thx you are marvelous! I will try it later
Sent from my HTC Desire S using XDA App

scan6 said:
Thx you are marvelous! I will try it later
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Say if you did it by this procedure.

Yes! it works very wellwith my version 2.13 to1.47
It's quite easy to do it
Thx a lot!
Sent from my HTC Desire S using XDA App

Thx for the guide. Worked great. I downgraded from 2.15 to 1.31 asia wwe.
From my Desire S Using XDAP

Hey man, I've added your guide to my thread http://forum.xda-developers.com/showthread.php?t=1186401
Just to let you know. Thanks for the great guide.

nodeffect said:
Hey man, I've added your guide to my thread http://forum.xda-developers.com/showthread.php?t=1186401
Just to let you know. Thanks for the great guide.
Click to expand...
Click to collapse
hey dude thanks.. btw this guide is for those who can't downgrade using mtothearkus method.. those recent 2.15.x versions..its just the same but it uses different root methods.. all credits to mtothearkus..appreciate it dude..thanks..

Thanks, noted.

After rebooting phone from recovery, typing
adb shell
/data/local/tmp/tacoroot --root
Answer:
Rebooting into root.
cannot create /data/local.prop: permission denied
and phone restart...
Desire S, Android 2.3.5, Hboot 2.00.0002

qpkqkma said:
After rebooting phone from recovery, typing
adb shell
/data/local/tmp/tacoroot --root
Answer:
Rebooting into root.
cannot create /data/local.prop: permission denied
and phone restart...
Desire S, Android 2.3.5, Hboot 2.00.0002
Click to expand...
Click to collapse
Dude what your software version number? brand if any?.. if this root doesnt work.. try zegRush method..
or try this
Update to latest available firmware, then try.
If that fails, do a factory reset and try.

Software : 2.10.401.8
Kernel: 2.6.35.10
Non-branded, lastest firmware.
Late I´ll try factory reset.

qpkqkma said:
Software : 2.10.401.8
Kernel: 2.6.35.10
Non-branded, lastest firmware.
Late I´ll try factory reset.
Click to expand...
Click to collapse
Zergrush method from mtothearkus's thread should work for you

qpkqkma said:
Software : 2.10.401.8
Kernel: 2.6.35.10
Non-branded, lastest firmware.
Late I´ll try factory reset.
Click to expand...
Click to collapse
That's it.. hehe. 2.10 is an old firmware.. ASIAN OTA is 2.15.. so try the zegrush method.. this tut was developed for those who can't root using the zegRush..thanks amidabuddha..=)

Signed up here at xda just to say that this worked nicely on my Desire S.
I had difficulty making the ADB code given by shadi22 work at first, but after redoing them and just copy pasting them in terminal, they worked. My Desire S also had an Asia 2.15 ROM and 2.00.0002 Hboot. Used the Asia WWE 1.48.707.1 RUU to downgrade the HBOOT after changing the misc-version and tacorooting, then Revolutionary all the way
At first, I thought that I made a mistake choosing this phone (My Desire's display got borked and SISPH's repair quote was way too expensive for a nearly two year old device ) because of the need to downgrade the hboot before getting S-OFF, but shadi22's method is probably the most elegant of all the S-OFF methods on 2.00.0002 devices

HAHAHA.. thanks dude.. Anyway.. SISPH are full of dumb people.. i had problem with my device too.. a green dot on an LCD screen. my phones on warranty but never had it repaired since they have no replacement part yet. so give up on the idea for that damn SISPH.. They had the worst customer service.. they should never have been contracted with HTC on the first place.. No HTC on my next phone. The reason to go with HTC was mainly for the developers in this beloved site.. But now im seeing great dev from other phone section..=)

Try to do a zergRush method. Everything run fine, i do steps 1-5, do a step 6 (run RUU etc etc.) but RUU say me error updating, phone stuck on HTC logowhen i pull out cable it load in HBOOT and say "RUU Security Fail ! Update Fail!".
Sucks.....im downloading RUU with SW 2.10.401.8 to recover phone.....
Any other method ?

Hey guys,
So I tried this method but encountered the following issue as shown in the image below:
{
"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"
}
Does anyone have any ideas as to where I have went wrong?
Kind regards,
DJM.

dontjudgemekk said:
Hey guys,
So I tried this method but encountered the following issue as shown in the image below:
Does anyone have any ideas as to where I have went wrong?
Kind regards,
DJM.
Click to expand...
Click to collapse
Off hand I would say that /data/local/tmp was not empty before you started and contains more than just the 2 files you copied there, thus the command chmod 777 /data/local/tmp/* is failing.
Why not just do 2 chmod commands for the 2 files you copied?

tpbklake said:
Off hand I would say that /data/local/tmp was not empty before you started and contains more than just the 2 files you copied there, thus the command chmod 777 /data/local/tmp/* is failing.
Why not just do 2 chmod commands for the 2 files you copied?
Click to expand...
Click to collapse
How would I clear the /data/local/tmp directory?
Can you phrase what you mean by performing 2 chmod commands for the 2 files better? I dont understand what you mean unfortunately. Are you referring to the tacoroot.bin and misc_version files?

dontjudgemekk said:
How would I clear the /data/local/tmp directory?
Can you phrase what you mean by performing 2 chmod commands for the 2 files better? I dont understand what you mean unfortunately. Are you referring to the tacoroot.bin and misc_version files?
Click to expand...
Click to collapse
Yes after you create the adb shell and get the $ prompt type:
chmod 777 /data/local/tmp/misc_version
chmod 777 /data/local/tmp/taco root.bin

Related

I'm waiting for Hboot 0.98.0002 S-OFF

My Desier S hboot is 0.98.0002,so I can't s-off my decive
please help me...thx...
PS:my RUU is 1.47......so http://forum.xda-developers.com/showthread.php?t=1173083 can't used...
Evilier said:
My Desier S hboot is 0.98.0002,so I can't s-off my decive
please help me...thx...
PS:my RUU is 1.47......so http://forum.xda-developers.com/showthread.php?t=1173083 can't used...
Click to expand...
Click to collapse
u need to use search button... its a yellow thing up
Evilier said:
My Desier S hboot is 0.98.0002,so I can't s-off my decive
please help me...thx...
PS:my RUU is 1.47......so http://forum.xda-developers.com/showthread.php?t=1173083 can't used...
Click to expand...
Click to collapse
Hi, you might wanna try to flash this ROM to get back to old Hboot
http://www.4shared.com/file/bAebAgjC/RUU_Saga_HTC_Europe_1284011_Ra.html
It may or may not work on your s-on device but worth to try.
ofc he can downgrade with s-on
i did the same, he is just too lazy to use search function
Blezz said:
ofc he can downgrade with s-on
i did the same, he is just too lazy to use search function
Click to expand...
Click to collapse
actually he cant with his radio the temp root using gingerbreak dosent work, so there is no way to downgrade, i have tried every method and have had no luck, but i am sure alpharevx will sort it out eventually
Blezz said:
ofc he can downgrade with s-on
i did the same, he is just too lazy to use search function
Click to expand...
Click to collapse
People like this annoy me. As the OP already stated, he can't downgrade with s-on. Just because YOU did, doesn't mean he can. His stock RUU is too new (1.47) and there is no exploit to get temp root yet for this RUU, so downgrading is not possible.
Agreed, he should use the search function, there are about 3 threads of people trying to s-off their 1.47 device. But in his defence, all 3 of those threads are filled with morons like yourself telling people they can do it. Newsflash, you can't.... yet
I'm waiting to :-(
Hope it will no take very long time ahah
Evilier said:
My Desier S hboot is 0.98.0002,so I can't s-off my decive
please help me...thx...
PS:my RUU is 1.47......so http://forum.xda-developers.com/showthread.php?t=1173083 can't used...
Click to expand...
Click to collapse
Hi Evilier.
I just have few questions regarding to your phone, since its one of the "new" software, do you have the Wi-Fi Death Grip? More info can be found here.
And can you tell me which of the v1.47 do you have? Which country I mean.
Well this is going to be a stretch, since you're on the "new" phones software version, can you update/RUU to the latest (RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.0 85AU_3805.06.02.03_M_release_199476_signed)? Then double check if you still have the so could Wi-Fi Death Grip. Thanks a lot.
+ 1 for a method to unlock/root the "new " firmware. Please devs do your magic
Sent from my HTC Desire S using XDA App
davidreece said:
actually he cant with his radio the temp root using gingerbreak dosent work, so there is no way to downgrade, i have tried every method and have had no luck, but i am sure alpharevx will sort it out eventually
Click to expand...
Click to collapse
Davidreece, I'm on the same wagon here... Tried every thinkable method but simply no joy
Did anyone of you test the ROM suggested by Yungyeh?
jakmor said:
Davidreece, I'm on the same wagon here... Tried every thinkable method but simply no joy
Did anyone of you test the ROM suggested by Yungyeh?
Click to expand...
Click to collapse
i have actually managed it i used fre3vo from this thread
http://forum.xda-developers.com/showthread.php?t=1150006
but i combined the instructions with post 4 from the downgrade thread ( part where you have to chmod the version file then change the version.
first download http://forum.xda-developers.com/attachment.php?attachmentid=591335&d=1304969547
and also this
http://forum.xda-developers.com/attachment.php?attachmentid=661246&d=1311240968
extract them to the same folder then open a command prompt in that folder and follow these instructions
Instructions:
1. adb push fre3vo /data/local/tmp
2. adb push misc_version /data/local/tmp
3. adb shell chmod 777 /data/local/tmp/fre3vo
4. adb shell chmod 777 /data/local/tmp/misc_version
5. Run the binary via 'adb shell /data/local/tmp/fre3vo'
If all goes well, you'll be kicked back to your computer's command prompt.
run 'adb shell' and you should have a '#' prompt instead of $
6. cd /data/local/tmp
./misc_version -s 1.27.405.6
From here you can then install the update/downgrade from the ruu exe for your phone from http://forum.xda-developers.com/showthread.php?t=1002506
then you can just follow the alpharevx instructions as normal because you will be able to run gingerbreak etc, this works on the latest updates as i couldnt use gingerbreak to downgrade due to the vodafone uk update and i am now on a custom rom and s offed
hope this helps everyone.
davidreece said:
i have actually managed it i used fre3vo from this thread
http://forum.xda-developers.com/showthread.php?t=1150006
but i combined the instructions with post 4 from the downgrade thread ( part where you have to chmod the version file then change the version.
first download http://forum.xda-developers.com/attachment.php?attachmentid=591335&d=1304969547
and also this
http://forum.xda-developers.com/attachment.php?attachmentid=661246&d=1311240968
extract them to the same folder then open a command prompt in that folder and follow these instructions
Instructions:
1. adb push fre3vo /data/local/tmp
2. adb push misc_version /data/local/tmp
3. adb shell chmod 777 /data/local/tmp/fre3vo
4. adb shell chmod 777 /data/local/tmp/misc_version
5. Run the binary via 'adb shell /data/local/tmp/fre3vo'
If all goes well, you'll be kicked back to your computer's command prompt.
run 'adb shell' and you should have a '#' prompt instead of $
6. cd /data/local/tmp
./misc_version -s 1.27.405.6
From here you can then install the update/downgrade from the ruu exe for your phone from http://forum.xda-developers.com/showthread.php?t=1002506
then you can just follow the alpharevx instructions as normal because you will be able to run gingerbreak etc, this works on the latest updates as i couldnt use gingerbreak to downgrade due to the vodafone uk update and i am now on a custom rom and s offed
hope this helps everyone.
Click to expand...
Click to collapse
This part got me all excited in the pants a little. I tried it, but the fre3vo script is hanging at "Frame Buffer handle: 4" for about 5 minutes now.
I will try factory reset on my 1.47 RUU and try once more.
@davidreece: can you confirm what RUU version you had when this worked for you?
davidreece said:
i have actually managed it i used fre3vo from this thread
http://forum.xda-developers.com/showthread.php?t=1150006
but i combined the instructions with post 4 from the downgrade thread ( part where you have to chmod the version file then change the version.
first download http://forum.xda-developers.com/attachment.php?attachmentid=591335&d=1304969547
and also this
http://forum.xda-developers.com/attachment.php?attachmentid=661246&d=1311240968
extract them to the same folder then open a command prompt in that folder and follow these instructions
Instructions:
1. adb push fre3vo /data/local/tmp
2. adb push misc_version /data/local/tmp
3. adb shell chmod 777 /data/local/tmp/fre3vo
4. adb shell chmod 777 /data/local/tmp/misc_version
5. Run the binary via 'adb shell /data/local/tmp/fre3vo'
If all goes well, you'll be kicked back to your computer's command prompt.
run 'adb shell' and you should have a '#' prompt instead of $
6. cd /data/local/tmp
./misc_version -s 1.27.405.6
From here you can then install the update/downgrade from the ruu exe for your phone from http://forum.xda-developers.com/showthread.php?t=1002506
then you can just follow the alpharevx instructions as normal because you will be able to run gingerbreak etc, this works on the latest updates as i couldnt use gingerbreak to downgrade due to the vodafone uk update and i am now on a custom rom and s offed
hope this helps everyone.
Click to expand...
Click to collapse
Thanks for the tip. But I'm a little confused at step 5. I'm the ultimate Android noob so please excuse my stupidity, but what exactly did the step mean by "Run the binary via 'adb shell /data/local/tmp/fre3vo"?
How exactly does one "run the binary? I typed in the 'adb shell /data/local/tmp/fre3vo' command for this step and I get
fre3vo by #teamwin
Please wait...
At this point I can't type anything and actually waited...but after about 15 minutes, nothing is happening. Could you point me in the right direction?
vankox said:
Thanks for the tip. But I'm a little confused at step 5. I'm the ultimate Android noob so please excuse my stupidity, but what exactly did the step mean by "Run the binary via 'adb shell /data/local/tmp/fre3vo"?
How exactly does one "run the binary? I typed in the 'adb shell /data/local/tmp/fre3vo' command for this step and I get
fre3vo by #teamwin
Please wait...
At this point I can't type anything and actually waited...but after about 15 minutes, nothing is happening. Could you point me in the right direction?
Click to expand...
Click to collapse
You appear to be doing exactly the correct thing...just be patient...(although I admit it does say a few minutes).
See this refined guide....http://forum.xda-developers.com/showpost.php?p=16104882&postcount=16
I'd be tempted to reboot the phone and start at the beginning again, (although the first two steps may well error as the files will be already there - ignore that and proceed).
first of all many thanks for all the guides, secondly i've followed all the steps and everything works fine but when i run the .exe to actually downgrade it always says that i'm under 30% of phone charge (battery is fully loaded). I made a gold card and everything also... strange..
ratss123 said:
first of all many thanks for all the guides, secondly i've followed all the steps and everything works fine but when i run the .exe to actually downgrade it always says that i'm under 30% of phone charge (battery is fully loaded). I made a gold card and everything also... strange..
Click to expand...
Click to collapse
Just grasping at straws here....Try to fully charge the battery and then power down device and remove the battery, allow both the battery and the device to cool down.
Try again.
Now, again I'm not sure but a full factory reset from HBOOT may remove the existing battery stats....so you could try that?
ben_pyett said:
Just grasping at straws here....Try to fully charge the battery and then power down device and remove the battery, allow both the battery and the device to cool down.
Try again.
Now, again I'm not sure but a full factory reset from HBOOT may remove the existing battery stats....so you could try that?
Click to expand...
Click to collapse
uhm didn't work also with factory reset.... keeps saying it's less then 30%..
lol so near to the s-off and then it doesn't work for something like that!!
Worked like a charm now s- off again running pre rooted 1.47.401 European Rom many thanks
Sent from my HTC Desire S using XDA App
ratss123 said:
uhm didn't work also with factory reset.... keeps saying it's less then 30%..
lol so near to the s-off and then it doesn't work for something like that!!
Click to expand...
Click to collapse
do you know anyone with the same device so that you could try to swap batteries for the update in case your has failed?
ben_pyett said:
do you know anyone with the same device so that you could try to swap batteries for the update in case your has failed?
Click to expand...
Click to collapse
no sadly i don't, tried to run it also on another pc but it's the same.. there is also another thing, few days ago i tried to run the .exe hoping that it would downgrade, later i found out that i've got hboot 92 so i waited for a new method.. When i tried I didn't get any error message, just thath obviusy it couldn't downgrade... today i tried again and I keep gettint low battery....

[Recovery]cwm-5.0.2.3-liberty-agse and stock cwm-5.0.2.3-liberty

Liberty still has something no other device has - ARIA!
{
"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"
}
..........
Downloads:
cwm-5.0.2.3-liberty-agse.zip AGSE (ARIA) Edition - with cap key lights enabled
cwm-5.0.2.3-liberty.zip Stock Clockworkmod 5.0.2.3 - with cap key lights enabled
attn1 said:
Liberty still has something no other device has - ARIA!
Download: cwm-5.0.2.3-liberty-agse.zip
Click to expand...
Click to collapse
and apparently , interesting background images
*****
I am still on v2.5.0.1 - and help on how to install this img?
Thanks so much attn1!
Edit: found this for instructions, would this do?.....
HTML:
http://forum.xda-developers.com/showthread.php?t=1122694
here's 2 ways to do it:
if you have s-off:
boot phone into fastboot mode
hook phone to computer with usb cable
ON COMPUTER:
unzip cwm-5.0.2.3-liberty-agse.zip
command prompt
fastboot flash recovery cwm-5.0.2.3-liberty-agse.img
without s-off: (this is what I did, didn't have a USB cable handy)
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
tommyguns818 said:
Thanks so much attn1!
Edit: found this for instructions, would this do?.....
HTML:
http://forum.xda-developers.com/showthread.php?t=1122694
Click to expand...
Click to collapse
yep, if you are s-off with Revolutionary or AlpharevX.
Nutshell69 said:
and apparently , interesting background images
Click to expand...
Click to collapse
that's Aria herself.
Looking forward to the HTC Jenna
Sent from my Liberty using XDA App
i was wondering.....i've got s-off but no computer around me at the moment. is there a way to install this through the terminal app? I see sObe did it via terminal way but im not sure if he's s-off or not.
EDIT: I went for it and did it through terminal just like sObe and I have s-off. Worked like a charm. Thanks guys!!!
When I chose internal card I get
E:Can't mount /emc/
???
s0be said:
here's 2 ways to do it:
without s-off: (this is what I did, didn't have a USB cable handy)
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
Click to expand...
Click to collapse
tried this twice still failing :S
do i need to be running a certain rom?
I get through su just fine, i cd to the /sdcard/download (where my img is)
type in the flash_image .....
getting sh: flash_image: command not found
so looks like the terminal emulator isnt getting the PATH correctly
echo $PATH returns
/data/local/bin:/sbin:/system/sbin:/system/bin:/system/xbin
ug.
If your doing it through terminal, you need to make sure that your doing it exactly as shown in s0bes post. Also make sure that you have your new cwm 5.0.2.3 download in the download folder on your sd card.
Nutshell69 said:
tried this twice still failing :S
do i need to be running a certain rom?
I get through su just fine, i cd to the /sdcard/download (where my img is)
type in the flash_image .....
getting sh: flash_image: command not found
so looks like the terminal emulator isnt getting the PATH correctly
echo $PATH returns
/data/local/bin:/sbin:/system/sbin:/system/bin:/system/xbin
ug.
Click to expand...
Click to collapse
probably any aosp or cm based rom would work. the stock cleaned up roms, not so much.
Aside from the background thing, what advantages does this recovery have over 2.5.1.7? Is it faster? are the backups compatible?
T
s0be said:
probably any aosp or cm based rom would work. the stock cleaned up roms, not so much.
Click to expand...
Click to collapse
yea - i think thats the problem - not running a cm rom - will install 209 and try
thanks
***EDIT***
Installed CM 211 ROM
did these steps
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
getting errors :
mtd: erase failure at 0x00000000 (I/O error)
.......
thoughts?
Also curious of the benifit vs backward or forward compatibility gotchas. Anyone?
Edit. Tried to instal and get the same errors as above. S-on
Sent from my Liberty using XDA App
Nutshell69 said:
yea - i think thats the problem - not running a cm rom - will install 209 and try
thanks
***EDIT***
Installed CM 211 ROM
did these steps
terminal emulator
su
cd /sdcard/download
unzip cwm-5.0.2.3-liberty-agse.zip
flash_image recovery cwm-5.0.2.3-liberty-agse.img
getting errors :
mtd: erase failure at 0x00000000 (I/O error)
.......
thoughts?
Click to expand...
Click to collapse
Perhaps you can't flash a recovery from the rom without s-off? I'm not an expert to say that's the case... If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago. You might try rebooting into recovery, and using adb shell to do those steps. If you don't have ADB available, this may be beyond an easy upgrade.
I know of no advantages of this recovery over 2.5, btw.
SoCalHTCFuze said:
Also curious of the benifit vs backward or forward compatibility gotchas. Anyone?
Edit. Tried to instal and get the same errors as above. S-on
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
s0be said:
Perhaps you can't flash a recovery from the rom without s-off? I'm not an expert to say that's the case... If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago. You might try rebooting into recovery, and using adb shell to do those steps. If you don't have ADB available, this may be beyond an easy upgrade.
I know of no advantages of this recovery over 2.5, btw.
Click to expand...
Click to collapse
In fact, you cannot flash a recovery without S-OFF, unless you use the original unrevoked tool and select custom recovery (the original unrevoked only managed to install a custom recovery which was good enough at the time).
The whole point of S-OFF is that you can flash the system partition. Like Gene said, if you don't have S-OFF, you'd need to unroot and use unrevoked again.
If you do have S-OFF, it's easy:
(OS X)
md5 /path/to/cwm-5.0.2.3-liberty-agse.img (confirm md5 sum)
./adb devices (confirm you're connected)
./adb reboot bootloader
./fastboot-mac devices
./fastboot-mac flash recovery /path/to/cwm-5.0.2.3-liberty-agse.img
./fastboot-mac reboot
./adb reboot recovery (wait to hit enter until the boot animation starts)
I haven't used it yet but I hear the backups are faster in 5.x
^^^ 5.0.2.3 is a little faster. I saw the new option to fix permissions in the recovery and tried it. Man it took like 30 min to run and chewed about 60 percent of battery. From now on I'll just use ROM manager. It never failed me and is way quicker. On further note....I like it. Go miss aria!
s0be said:
If so, you have to go through the whole unroot and re-flash procedure, which I forgot the steps to LONG ago.
Click to expand...
Click to collapse
Just so people in this situation are aware, you do not have to "unroot" your phone first. Just run Unrevoked a second time on your device and it will overwrite the recovery with the one you select.
drumist said:
Just so people in this situation are aware, you do not have to "unroot" your phone first. Just run Unrevoked a second time on your device and it will overwrite the recovery with the one you select.
Click to expand...
Click to collapse
egads - got this error
Error: failed to get root. Is your firmware too new?

[Root][Guide] Rooting ICS 4.04 leak from the 2.3.6

FILES WERE ATTACHED. I HOPE IT IS VIRUS FREE BUT I CANNOT PROMISE AS THERE MAY BE SOME TROJANS BECAUSE I DOWNLOADED AT SOMEWHERE. You've been warned. That's why I placed the list of files originally.
0. Your system must be in version 2.3.6 or below, which can be rooted by motofail. Do double wipe before you flash.
a) Place the following files in the same folder:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
motofail
su
Superuser.apk (script default) / supersu.apk
b)(optional) Prepare the modified RSDlite which can flash any roms...
c) Prepare the Motorola driver and install it.
d) use notepad to create a script (root.bat)(provided below) and save it in the same folder with the files above.
1. Connect your phone to the computer. You'd better install the drivers for your phone first. Turn on "USB debugging" and connect it as "charging mode".
2. You CANNOT unplug your usb cable and you CANNOT close the rooting program/script in the whole process.
3. Run the root.bat.
4. it will push some files into your phone and reboot your phone.
5. You will see the caution symbol with the Android robot.
6a. Flash your rom by the stock recovery
OR
6b(i). Pull the battery out.
6b(ii). HOLD the volume-down button and put the battery back.(Power ON) It will boot into the AP mode. (If you can see the blank secreen but not showing "USB CONNECTED, FLASH OK" , release the volume button or retry)
6b(iii). run the RSDlite to flash your rom
7. The phone will reboot and update few(1-3) times.
8. The phone will be rooted after the final reboot.
9. Take out your SD card and do factory reset. (The root will be kept) (I found this may solve some problems)
Script is here :
Code:
@echo off
cls
adb kill-server
adb wait-for-device
adb.exe shell mv /data/local/12m /data/local/12m.bak
adb.exe shell ln -s /data /data/local/12m
adb.exe reboot
adb.exe wait-for-device
adb shell rm -r /data/local/tmp
adb shell mkdir /data/local/tmp
adb push motofail /data/local/tmp
adb shell chmod 755 /data/local/tmp/motofail
adb shell /data/local/tmp/motofail exploit
adb reboot
adb wait-for-device
adb remount
adb.exe shell rm /data/local/12m
adb.exe shell mv /data/local/12m.bak /data/local/12m
adb.exe shell mv /data/local.prop /data/local.prop.bak
adb.exe shell "echo 'ro.kernel.qemu=1' >> /data/local.prop"
adb.exe reboot recovery
echo The phone will boot into the recovery mode
echo please follow the tutorial for the rooting process
echo do not close this window
ping -n 8 127.1>nul
adb wait-for-device
adb remount
adb push su /system/bin
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app
adb shell chmod 666 /system/app/Superuser.apk
adb shell rm -r /data/local/tmp
adb shell mkdir /data/local/tmp
echo Your phone is rooted!!!
PAUSE
The script is provided by the crc3334404 at gfan.com .Some text is modified by me.
The guide is mainly based on his guide too. (with several modification and addon etc)
Tested on ME865
attach the required files
Edit:- thanks will try
may be i am noob but when i run the bat file it say
C:\root>adb wait-for-device
* daemon not running. starting it now *
* daemon started successfully *
Click to expand...
Click to collapse
and stays there waited for 15 min but nothing happend
EDIT:- as i said i am noob, forgot to tick usb debugging
shamsud said:
may be i am noob but when i run the bat file it say
and stays there waited for 15 min but nothing happend
Click to expand...
Click to collapse
probably bad drivers or something
shamsud said:
may be i am noob but when i run the bat file it say
and stays there waited for 15 min but nothing happend
EDIT:- as i said i am noob, forgot to tick usb debugging
Click to expand...
Click to collapse
So sorry that I didn't mention originally.
Actually I can't sure whether it works in MB865. May you please tell us after trial. Thanks
Results?
Sent from my Atrix II using xda premium
lilhaiti said:
Results?
Sent from my Atrix II using xda premium
Click to expand...
Click to collapse
Id really like to know as well! Haha
sorry guys am unable to flash with stock recovery it say "assert failed" i downloaded the file from below thread
http://forum.xda-developers.com/showthread.php?t=1684443
Click to expand...
Click to collapse
shamsud said:
sorry guys am unable to flash with stock recovery it say "assert failed" i downloaded the file from below thread
Click to expand...
Click to collapse
do you have a MEARET phone? are you fully stock?
fully stock but Searet rom, now loading mearet rom...
EDIT:= Finally got the rooted ics the above method works
shamsud said:
fully stock but Searet rom, now loading mearet rom...
EDIT:= Finally got the rooted ics the above method works
Click to expand...
Click to collapse
Could you upload a backup.i need it to work on getting cm9 working with data. I cant just use the ics update because its only patch files.i need the already patched files.pm me the link to the upload if u can upload it as soon as possible. I just need the system.ext3.tar
Sent from my MB865 using xda premium
rdavisct said:
Could you upload a backup.i need it to work on getting cm9 working with data. I cant just use the ics update because its only patch files.i need the already patched files.pm me the link to the upload if u can upload it as soon as possible. I just need the system.ext3.tar
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
He sent me a PM I told him to do a cwm backup and give us the system and also to dump boot with dd in case we need it for anything
I rooted failed....
It stock after RDS 4.0.4....
I plug the usb and all drivers are ok, then press anykey, then.....it stock...
My OS windows 7 64bit...
dickluo said:
I rooted failed....
It stock after RDS 4.0.4....
I plug the usb and all drivers are ok, then press anykey, then.....it stock...
My OS windows 7 64bit...
Click to expand...
Click to collapse
Questions may help:
1. did you flash it back to 2.3.6 First?
2. Did you root the 2.3.6 successfully by the batch?
3. Flashed the 4.0 after root with no Window closed?
4. Always connected with usb?
5. Usb debugging enabled?
6. No superuser.apk? May be you don't need to do factory reset after rooting. Please let us kvow.
If all yes, please tell us your 2.3.6 version too. E. G. 55.109.xxx
Sent from my ME865 ICS4.0 using XDA premium.
Double post, deleted
shamsud said:
fully stock but Searet rom, now loading mearet rom...
EDIT:= Finally got the rooted ics the above method works
Click to expand...
Click to collapse
Which cheesecake rom did you start with?
Sent from my ME865 ICS4.0 using XDA premium.
4.0.4 drains battery very fast
Two observations after testing ICS on MB865
1/ battery drains twice as fast for ICS 4.04 compared to GB 3.6.6
2/ Screen slower response
austin_boy said:
Two observations after testing ICS on MB865
1/ battery drains twice as fast for ICS 4.04 compared to GB 3.6.6
2/ Screen slower response
Click to expand...
Click to collapse
Never tried GB 3.6.6 and am afraid it doesn't exist.
My battery is ok:
{
"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"
}
xanadu said:
Never tried GB 3.6.6 and am afraid it doesn't exist.
My battery is ok:
Click to expand...
Click to collapse
Maybe because you are on T-mobile and don't use 3G
socialx said:
0. Your system must be in version 2.3.6 or below, which can be rooted by motofail. Do double wipe before you flash.
Click to expand...
Click to collapse
Can anybody help me to find 2.3.6 firmware for ME865?

[TUT] Downgrade/Unbrick Ville S4

Introduction​
This should work on the S4 version of the HTC One S. I do not recommend trying this on the S3 version..
Nobody is responsible for the outcome of your phone except you. You know the possible risks and you took them
DO NOT ATTEMPT UNLESS YOU ARE COMFORTABLE WITH THIS OR KNOW WHAT YOU ARE DOING
DO NOT ATTEMPT TO DOWNGRADE IF YOU TOOK THE JB OTA. IT HAS BEEN REPORTED TO PERMANENTLY BRICK PHONES ON THE EVITA SIDE
DO NOT ATTEMPT UNLESS YOU HAVE LINUX INSTALLED.. Ubuntu 12.04 or higher preferred - 32/64 bit!
You can use a livecd or wubi. No virtualbox
This guide assumes your Bootloader is unlocked, You have Recovery Installed, and USB Debugging is ENABLED. Please enable USB debugging before continuing​
Creating the brick​
Prerequisites: killp4.. included in the unbrick package
unbrick package: http://dl.dropbox.com/u/40181085/ville.zip
A backed up p4!
*MAKING A NANDROID BACKUP WILL DO NOTHING FOR YOU.. BUT I DO RECOMMEND HAVING ONE AT ALL TIMES*
1. Place killp4 on your /sdcard
2. Download adb and enable USB debugging (adb is in the android SDK, or search Google for a download)
3. Open your command line and type the following
Code:
$ adb shell
$ su
# dd if=/dev/block/mmcblk0p4 of=/sdcard/bakp4
# exit
$ exit
COPY bakp4 to a SAFE location ON YOUR COMPUTER and UNMOUNT your USB storage
4. Kill your phone
Code:
$ adb shell
$ su
# dd if=/sdcard/killp4 of=/dev/block/mmcblk0p4
# exit
$ exit
5. Reboot your phone. The charging light will no longer be on, and you should be stuck on a black screen.
Enumerating your partitions​Q: What does enumerate mean?
A:
Code:
enumerate - to specify one after another.
Synonym: list
Prerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/ville.zip
A null p4 or the bakp4 you acquired earlier.
a null p4 is included in the unbrick package if you didn't save your backup.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID
1. Open up 3 terminal windows
2. On your first window, type
Code:
$ watch -n 1 lsusb
3. Now, hold power down on your phone for about 10 seconds*,OR until you see (QDL mode) disappear and let go, Then go to your second window and repeatedly run the following command
*On the HTC One X you have to hold power for 10 seconds, on the EVO 4G LTE it is ~30 seconds. This number may vary
Code:
$ ls /dev/sd*
You should go from seeing this..
{
"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"
}
to seeing this...
4. Make note of the following.
for me, my devices was listed as /dev/sdb, yours may be listed as /dev/sdc or even /dev/sdd.
make note of /dev/sd*4 and /dev/sd*12
5. Make sure Linux sees the phone
Code:
$ sudo dmesg | grep "qcserial"
You should see "Qualcomm USB modem converter detected" as the last line of the output. If not, you can unplug and replug the USB cable or run...
Code:
$ sudo modprobe qcserial
to reload the driver
6. Reset the driver
Code:
$ sudo modprobe -r qcserial
7. create the block device
Code:
$ sudo mknod /dev/ttyUSB0 c 188 0
8. Open a third Terminal window and navigate to where you stored the ville folder. I saved it to my desktop, so my code is
Code:
$ cd Desktop/ville
$ chmod +x emmc_recover
9. Now we restore the hboot.. replace /sdc12 with your device location that we discovered in step 3 and 4
Code:
$ sudo ./emmc_recover -f ./hboot.nb0 -d /dev/sdc12 -c 24576
You can hit enter at all of the prompts here. If it stalls at "Waiting for /dev/sdc12, hold the power button down on your phone about 10 seconds, or until your see "Qualcomm. Inc. Gobi Wireless Modem (QDL mode) disappear from your terminal window, then release it. 10 seconds or less after you do this, emmc_recovery will see your phone and proceed. Flashing Hboot will take several minutes, as it has to load data in ~23K chunks followed by a reset after each.
or you can open a new terminal window and run the following command IF AND ONLY IF the phone doesn't reset out of QDL mode
Code:
$ sudo ./emmc_recover -r
10. Once that is finished. We have to reset the qcserial driver again.
Code:
$ sudo modprobe -r qcserial
11. And then recreate the block device
Code:
$ sudo mknod /dev/ttyUSB0 c 188 0
12. Now we restore the original mmcblk0p4 that you should have saved as "bakp4"
Code:
$ sudo ./emmc_recover -f ./bakp4 -d /dev/sdc4 -c 24576
13. Again, if it hangs, hold your phone's power button for about 10 seconds, then release. This file will flash very quickly (it's only 1K) and once it completes, you'll immediately notice that your charging light turns back on. You should see "Qualcomm, Inc." or "Qualcomm, Inc. Gobi Wireless modem (QDL mode) disappear from your terminal screen.
14. Press the thanks button for yarrimapirate. As these are his tools/methods
special thanks to
beaups (for helping me understand how to enumerate the partitions)
18th.abn (for getting me the 1.09 hboot and also agreeing to help me)
and yarrimapirate (not only for the scripts which he made for the Evo 4G LTE, but also agreeing to help me in this project and buying a one x with his own money)
This is why it is easier on evita.. http://db.tt/kCeCpDAE
I made a version for you guys.. http://db.tt/ar4sbw6V
Place on your sdcard
open terminal emulator
Code:
$ su
# dd if=/sdcard/mmcblk0p23 of=/dev/block/mmcblk0p23
reboot to fastboot and lock your bootloader. And then run the RUU
You can download the edited version. USE WITH CAUTION
Just finished downgrading from 1.14 to 1.06.
I started with Jet and replaced the bakp4 after it was created with my own and replaced the hboot with the 1.06 version for the One S. Jet got stuck and kept giving me "Failed to flash hboot" so I jumped over to the manual instructions and finished it that way.
Thanks mikeyinid for bringing to my attention that we can do this and being the first guy to try it with the One S. Thanks absolutelygrim for all your hard work and instructions.
dc211 said:
Just finished downgrading from 1.14 to 1.06.
I started with Jet and replaced the bakp4 after it was created with my own and replaced the hboot with the 1.06 version for the One S. Jet got stuck and kept giving me "Failed to flash hboot" so I jumped over to the manual instructions and finished it that way.
Thanks mikeyinid for bringing to my attention that we can do this and being the first guy to try it with the One S. Thanks absolutelygrim for all your hard work and instructions.
Click to expand...
Click to collapse
Jet has a few bugs right now, some users have reported it working, I haven't gotten it to work for me. Failed at flashing hboot, manual method has always saved them
Nice work! This should be on the dev forum. Please request a moderator move it there where those in need have a better chance to find it.
You should mention that Linux is needed earlier on in the OP so people don't brick then realize they can't unbrick cus they don't have Linux. People won't read the whole thing before they jump in.
Sent from my HTC One S using xda premium
Behold_this said:
Nice work! This should be on the dev forum. Please request a moderator move it there where those in need have a better chance to find it.
Click to expand...
Click to collapse
And maybe sticked.
Send from a phone.
which hboot does this downgrade to? i am currently on 1.14.001 can mine be downgraded?
sherry478 said:
which hboot does this downgrade to? i am currently on 1.14.001 can mine be downgraded?
Click to expand...
Click to collapse
It downgrades you to 1.06
sherry478 said:
which hboot does this downgrade to? i am currently on 1.14.001 can mine be downgraded?
Click to expand...
Click to collapse
Yes it can. I downgraded mine from 1.14 to 1.06.
Sent from my HTC One S using xda premium
How easy is this to do if you never used linux? and also can it be done in Virtualbox?
Darknites said:
How easy is this to do if you never used linux? and also can it be done in Virtualbox?
Click to expand...
Click to collapse
Yes and no. LiveCd or install only
absolutelygrim said:
Yes and no. LiveCd or install only
Click to expand...
Click to collapse
Thanks, I see if I got the balls to do it tomorrow lol.
Darknites said:
How easy is this to do if you never used linux? and also can it be done in Virtualbox?
Click to expand...
Click to collapse
Follow grims instructions and it's simple, for anyone
Sent from my HTC One S using xda premium
mikeyinid said:
Follow grims instructions and it's simple, for anyone
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Ya it does seem easy but I never used Linux before and the idea of bricking it to do it just sounds wrong to me lol but the idea of having to use an app or fastboot in till my next phone is no fun lol.
Will I need to download anything other then whats in the OP to go with the linux install?
Darknites said:
Ya it does seem easy but I never used Linux before and the idea of bricking it to do it just sounds wrong to me lol but the idea of having to use an app or fastboot in till my next phone is no fun lol.
Will I need to download anything other then whats in the OP to go with the linux install?
Click to expand...
Click to collapse
Nope.. Should work right off a clean install
absolutelygrim said:
Nope.. Should work right off a clean install
Click to expand...
Click to collapse
Thanks again I get everything sorted tonight to try tomorrow.
Linux running off a usb stick will work right? Think I got puppy linux sitting around my room somewhere.
diabolusmiles said:
Linux running off a usb stick will work right? Think I got puppy linux sitting around my room somewhere.
Click to expand...
Click to collapse
Haven't tried it on puppy.. I prefer using debian based versions
I haven't tried yet, but downgrading hboot like this, does it mean we can run the old ruu?
Sent from my HTC One S using xda premium

[S-Off] Facepalm S-Off for One SV (K2_U, K2PLC_LC, K2_UL)

Welcome to Facepalm S-Off for the HTC One SV (K2_U, K2PLC_CL and K2_UL Only).
This is ONLY for the K2_U, K2PLC_CL, and K2_UL versions of the One SV. If you have a different variant please PM me and we can walk through it for your device. To check which one you have run "adb shell getprop ro.product.device"
Credits and terms:
This is fully beaups and jcase's s-off method. I had NO help in creating or developing it. I only tested the method on the One SV!
Exploit by beaups. Full guide, testing, and concept by jcase and beaups. Thanks to dsb9938 and dr_drache for support and testing. Thanks also to all of the regulars at teamandirc.
Both beaups and jcase will collect the applicable active bounties. Further donations are greatly appreciated and can be sent to:
beaups - [email protected] - http://forum.xda-developers.com/donatetome.php?u=711482
jcase - [email protected] - http://forum.xda-developers.com/dona....php?u=2376614
dsb9938 - [email protected] - http://forum.xda-developers.com/dona....php?u=2963256
dr_drache - [email protected] - https://www.paypal.com/cgi-bin/websc...=6LRSY8MT8P3A6
jmz - [email protected] - http://forum.xda-developers.com/donatetome.php?u=1219335
You can also come by irc for support or just to say thanks: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
While this process shouldn’t be too risky, bricks can happen. None of us will be accountable. If you are worried, don’t do it.
This is a pretty simple method, however, you will need to have a working adb and fastboot environment. This method will work on any operating system that supports adb and fastboot. You should understand how to use a terminal window in your O/S. If you don’t understand adb and fastboot, you probably don’t need S-off.
Lastly, the work herein should not be stolen, repackaged, one clicked, bat’d, etc. soffbin3 is not GPL and may not be reused, integrated into other work, reposted, or redistributed without our permission.
For this to work, you must be rooted and have superCID (unlock/custom recovery is optional), see the threads below for help and information regarding obtaining superCID, unlock, root, etc. Note these threads are provided for convenience only. Please look for support for them in each respective thread if you need it, do NOT clutter this thread with support requests regarding obtaining superCID and/or root! If you try this process without superCID, it will not work, and you may have issues!:
HTC One SV superCID: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
Once you have confirmed you have SuperCID, get started (read it through first so you understand it all):
Follow these instructions EXACTLY. After the error 92 in step 5, whatever you do, do NOT run the fastboot flash command again. Make sure you procede on to step 6.
Let's get started:
1.) Download patcher and unzip it in your working directory:
soffbin3.zip http://androidfiles.org/getdownload.php?file=K2U/soffbin3.zip
2.) Download zip that matches your model and move it in your working directory (do not unzip it!):
K2U http://androidfiles.org/getdownload.php?file=K2U/rom.zip
K2PLC_CL http://androidfiles.org/getdownload.php?file=K2_PLCCL/rom.zip
K2_UL http://androidfiles.org/getdownload.php?file=K2_UL/rom.zip
3.)
Code:
adb reboot bootloader
(wait for bootloader)
4.)
Code:
fastboot oem rebootRUU
(wait for black HTC Screen)
5.)
Code:
fastboot flash zip <appropriate zip filename from above>
After a while, You should see the following error “FAILED (remote: 92 supercid! please flush image again immediately)”
6.) Immediately issue the following command:
Code:
fastboot oem boot
You may see some errors, just wait for the device to boot into Android (only now, you should be booted into Android with no eMMC write protection of any kind active).
7.) Issue the following 3 commands to update the security partition with S-off flags (one command at a time!):
Code:
adb push soffbin3 /data/local/tmp/
adb shell chmod 744 /data/local/tmp/soffbin3
adb shell su -c "/data/local/tmp/soffbin3"
(wait for a few seconds)
8.)
Code:
adb reboot bootloader
9.) You should see what you are looking for!
If you need help or just care to say thanks, join us on IRC: #FacePalm http://chat.andirc.net:8080/?channels=facepalm
Enjoy.
mine too
I made a guide to change the cid to supercid:
[HTC One SV] How to change your CID to SuperCID 11111111
Can confirm that this has worked on my phone:
Before:
{
"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"
}
After:
This is interesting. Hopefully s-off for K2_UL will come soon.
MasterDL said:
This is interesting. Hopefully s-off for K2_UL will come soon.
Click to expand...
Click to collapse
I just need a tester that can follow these directions. but i need to walk them through it because its slightly different
Re: [S-Off] Facepalm S-Off for One SV (K2_U)
Any chance similar method would work ok HTC One S C2?
Sent from my HTC One S using xda app-developers app
Do you have Jelly Bean on your k2_u phones?
Now support cricket One SV's
Did a little donation to jmz, because i not even dreamed about having S-Off 24 hours after the phone was delivered to me! thanks for that.
Transaction ID: 66A624935S776150W
K2_ul rom.zip
I have problems with the rom.zip for K2_UL.
When I do the steps I get after step 5: FAILED (remote: 22 loading zip info fail).
I noticed that the rom.zip I downloaded can not be opened with 7z while the other one for K2_PLCCL can be opened with 7z.
Redownloaded it twice with same result.
Add: Download is correct Md5 matches
Is the file corrupt or am I doing something wrong?
Zamek said:
I have problems with the rom.zip for K2_UL.
When I do the steps I get after step 5: FAILED (remote: 22 loading zip info fail).
I noticed that the rom.zip I downloaded can not be opened with 7z while the other one for K2_PLCCL can be opened with 7z.
Redownloaded it twice with same result.
Add: Download is correct Md5 matches
Is the file corrupt or am I doing something wrong?
Click to expand...
Click to collapse
I just downloaded and i was able to open the zip just fine with winrar. Im not sure what your issue is as you can open one and not the other. The only thing I can suggest is to redownload it again. I have had 2 testers download and use that exact file without issue.
jmztaylor said:
I just downloaded and i was able to open the zip just fine with winrar. Im not sure what your issue is as you can open one and not the other. The only thing I can suggest is to redownload it again. I have had 2 testers download and use that exact file without issue.
Click to expand...
Click to collapse
Thanks for your quick reply.
I can also open the file with winrar but if I do a test archived files I get CRC failed for 4 files.
Zamek said:
Thanks for your quick reply.
I can also open the file with winrar but if I do a test archived files I get CRC failed for 4 files.
Click to expand...
Click to collapse
Yes because its encrypted and signed. HTC has started doing that.
Sent from my HTC One VX using xda premium
jmztaylor said:
Yes because its encrypted and signed. HTC has started doing that.
Sent from my HTC One VX using xda premium
Click to expand...
Click to collapse
So the file is ok. Do you have a hint for FAILED (remote: 22 loading zip info fail). at step 5?
Zamek said:
So the file is ok. Do you have a hint for FAILED (remote: 22 loading zip info fail). at step 5?
Click to expand...
Click to collapse
Other than doing a battery pull or full power down, rebooting into android then going back into bootloader I don't really have a suggestion
Sent from my HTC One VX using xda premium
jmztaylor said:
Other than doing a battery pull or full power down, rebooting into android then going back into bootloader I don't really have a suggestion
Sent from my HTC One VX using xda premium
Click to expand...
Click to collapse
Thanks a lot. Now the SV has JB,is rooted and S-off
I did a battery pull, and additional copied all needed SDK/adb files to a short named directory directly below root.
Don't know what it was but I am happy now.
Thanks again for your effort and support
When I saw the words "S-OFF" on my bootloader screen, I said "F*** me brains!", I was so pleased.
...
...
Hi.
I'm running the JB OTA update with a European HTC unbranded One SV (CID = HTC__203). I installed the JB CWM Recovery and rooted it, but I can't seem to be able to change my CID to SuperCID using the One X method in the link.
I keep pushing the SuperCID modded mmcblk0p4 file, but it doesn't "stick".
"Fastboot oem readcid" still gives my original CID.
Has anyone encountered similar problems changing CID with JB / 2.00 HBOOT ?
Could anyone please help me in this thread since there's no SuperCID thread for the One SV ?
Thanks

Categories

Resources