This is my first android phone. It's S-ON and hboot version is 0.98.002. After reading all the threads I can find, it became clear to me that at the moment the way to s-off is to downgrade hboot to 0.98.0000 using an official signed RUU.
The problem is being unrooted, it doesn't seem to be able to "downgrade". I tried several official roms and the RUU installers all stops at ERROR[140]: Wrong Bootloader Version. My phone is shipped with rom version 1.46.1400.9 Neither the GingerBreak 1.2 apk and the GingerBreak command line tool can get the phone rooted.
So I'm kinda stuck... should I resort to XTC Clip? or is there any other way to help root the phone? or should I wait for AlphaRevx update with support for the new hboot or newer GingerBreak release? Any help is much appreciated.
u need to s-off ur phone first then root..check this
http://forum.xda-developers.com/showthread.php?t=1162102
Hi Adidas108, I have read the post but it only applies to hboot 0.98.0000 whereas my phone is 0.98.0002, my question is still not answered
laitonsn said:
Hi Adidas108, I have read the post but it only applies to hboot 0.98.0000 whereas my phone is 0.98.0002, my question is still not answered
Click to expand...
Click to collapse
You need to downgrade your hboot first and then s-off once you have the 0.98.0000 hboot
see this thread : http://forum.xda-developers.com/showthread.php?t=1078497
This is the method i used and am now s-off
jh787 said:
You need to downgrade your hboot first and then s-off once you have the 0.98.0000 hboot
see this thread : http://forum.xda-developers.com/showthread.php?t=1078497
This is the method i used and am now s-off
Click to expand...
Click to collapse
GingerBreak 1.2 doesn't seem to be able to root my phone. In the running apk, the application can run forever with the spinning circle on the floating notification window... as I said, the lastest android seems to have patched the hole used by GingerBreak
laitonsn said:
GingerBreak 1.2 doesn't seem to be able to root my phone. In the running apk, the application can run forever with the spinning circle on the floating notification window... as I said, the lastest android seems to have patched the hole used by GingerBreak
Click to expand...
Click to collapse
I know. read the full post carefully.
All you need is temp root to be able to pull the file needed for editing.
Have all the commands that are needed copied into notepad so you can quickly copy and paste. It doesnt give you much time.
Also, i had to do a factory rest between the two temp roots.(although there is another way if you dont want to factory reset.)
See this post
http://forum.xda-developers.com/showthread.php?p=13918319#post13918319
Ensure
1. you have a gold card
2. USB Debugging is on
3. Have HTC Sync (for drivers) Uninstall after
Step 3 says it will complain about something going wrong but you already have root.
Just use adb and see if yu can get superuser permissions.
If you have already tried it then you will have factory reset device or delete temp files from /data/user/temp.
see this post
http://forum.xda-developers.com/showpost.php?p=13924643&postcount=47
laitonsn said:
This is my first android phone. It's S-ON and hboot version is 0.98.002. After reading all the threads I can find, it became clear to me that at the moment the way to s-off is to downgrade hboot to 0.98.0000 using an official signed RUU.
The problem is being unrooted, it doesn't seem to be able to "downgrade". I tried several official roms and the RUU installers all stops at ERROR[140]: Wrong Bootloader Version. My phone is shipped with rom version 1.46.1400.9 Neither the GingerBreak 1.2 apk and the GingerBreak command line tool can get the phone rooted.
So I'm kinda stuck... should I resort to XTC Clip? or is there any other way to help root the phone? or should I wait for AlphaRevx update with support for the new hboot or newer GingerBreak release? Any help is much appreciated.
Click to expand...
Click to collapse
I'm in a similar boat. I upgraded to the 1.47 europe RUU out of curiosity, not realising there was no way back. Unfortunately Gingerbreak does not work on this rom.
Gingerbreak is needed to "trick" HTC Sync into thinking you have a lower versioned ROM installed, since you can only upgrade with HTC sync. So the method runs a script to trick it into thinking the version is 1.27.something, then you can upgrade from there to any RUU you want.
Unfortunately, until gingerbreak works on 1.46+, we are boned.
tigris666 said:
I'm in a similar boat. I upgraded to the 1.47 europe RUU out of curiosity, not realising there was no way back. Unfortunately Gingerbreak does not work on this rom.
Gingerbreak is needed to "trick" HTC Sync into thinking you have a lower versioned ROM installed, since you can only upgrade with HTC sync. So the method runs a script to trick it into thinking the version is 1.27.something, then you can upgrade from there to any RUU you want.
Unfortunately, until gingerbreak works on 1.46+, we are boned.
Click to expand...
Click to collapse
I had hboot 0.98.0002 on my device with the latest rom.
I used the procedure in the above post and downgraded hboot. and then s-off.
You dont need htc sync except for drivers.
You are using adb via a command window.
You are confusing the info you have read.
It is hboot we need to trick not the rom version
jh787 said:
I had hboot 0.98.0002 on my device with the latest rom.
I used the procedure in the above post and downgraded hboot. and then s-off.
You dont need htc sync except for drivers.
You are using adb via a command window.
Click to expand...
Click to collapse
When you say you had the latest rom, which rom was it? I bet it was less than 1.46
I tried what you said of factory reset in order to get second root, since it worked first time but not since. It made no difference. As someone replied to you in the other thread, factory reset is overkill, you can just rm /data/local/tmp/* and then re-push the Gingerbreak files.
The simple fact is, as pointed out in the Gingerbreak thread by the developer himself, it just does not work on the latest ROMs since they plugged the exploit.
tigris666 said:
When you say you had the latest rom, which rom was it? I bet it was less than 1.46
I tried what you said of factory reset in order to get second root, since it worked first time but not since. It made no difference. As someone replied to you in the other thread, factory reset is overkill, you can just rm /data/local/tmp/* and then re-push the Gingerbreak files.
The simple fact is, as pointed out in the Gingerbreak thread by the developer himself, it just does not work on the latest ROMs since they plugged the exploit.
Click to expand...
Click to collapse
If you got it first time for pulling the files what is stopping you from getting it the second time?
Yes, factory reset is overkill (I know now) but that is how i did it and i did point out that there was an alternative way.
The developer is referring to ginger break in general which used to be enough to root the gingerbread roms but that exploit has now been plugged.
@laitonsn check this thread
http://forum.xda-developers.com/showthread.php?t=1002506
- download RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release and flash
- u will get 0.98.0000
- s-off ur phone then with Alpharevx
http://forum.xda-developers.com/showthread.php?t=1162102
- then do whatever u want
jh787 said:
If you got it first time for pulling the files what is stopping you from getting it the second time?
Click to expand...
Click to collapse
The fact that my rom is now 1.47 is stopping me. Previous I was on a 1.36 telstra ROM. Gingerbreak worked fine on that, but as I keep saying, now I'm on 1.47, gingerbreak will no longer work, and therefore there is no way back (yet).
Feel free to upgrade to 1.46+ yourself if you wish to prove me wrong
tigris666 said:
The fact that my rom is now 1.47 is stopping me. Previous I was on a 1.36 telstra ROM. Gingerbreak worked fine on that, but as I keep saying, now I'm on 1.47, gingerbreak will no longer work, and therefore there is no way back (yet).
Feel free to upgrade to 1.46+ yourself if you wish to prove me wrong
Click to expand...
Click to collapse
I am already s-off so double to you LOL
se my signature...so ur wrong
Adidas108 said:
se my signature...so ur wrong
Click to expand...
Click to collapse
I was talking to tigris666, not you mate
Adidas108 said:
se my signature...so ur wrong
Click to expand...
Click to collapse
Perhaps you S-OFF'd from a lower ROM and then upgraded. Everything I've found suggests that once you are S-ON 1.47, you are screwed.
If you are S-ON 1.36 then you will be ok, cos you can gingerbreak, flash 1.28, S-OFF, flash 1.47... bam that is how you get S-OFF 1.47
tigris666 said:
Perhaps you S-OFF'd from a lower ROM and then upgraded. Everything I've found suggests that once you are S-ON 1.47, you are screwed.
If you are S-ON 1.36 then you will be ok, cos you can gingerbreak, flash 1.28, S-OFF, flash 1.47... bam that is how you get S-OFF 1.47
Click to expand...
Click to collapse
nope.
phone was rooted and s-off with 1.28 and i cooked 1.47,root,int.d and so on and flashed via recovery
if u flash with .exe file, i think u'll get s-on and hboot 0.98.0002 again
Adidas108 said:
nope.
phone was rooted and s-off with 1.28 and i cooked 1.47,root,int.d and so on and flashed via recovery
Click to expand...
Click to collapse
Exactly. OP was asking how you S-OFF when he is already 1.46. It's simply not possible, yet people coming on here telling him it is. Poor bloke probably getting his hopes up.
Hi! I have a problem with downgrade: after this command nothing happens
d:\Downloads\Downgrade_v2\Downgrade>adb shell
$ ./data/local/tmp/GingerBreak
./data/local/tmp/GingerBreak
[**] Gingerbreak/Honeybomb -- android 2.[2,3], 3.0 softbreak
[**] (C) 2010-2011 The Android Exploid Crew. All rights reserved.
[**] Kudos to jenzi, the #brownpants-party, the Open Source folks,
[**] Zynamics for ARM skills and Onkel Budi
[**] donate to [email protected] if you like
[**] Exploit may take a while!
[+] Plain Gingerbread mode!
[+] Found PT_DYNAMIC of size 232 (29 entries)
[+] Found GOT: 0x00014360
[+] Using device /devices/platform/goldfish_mmc.0
[*] vold: 0000 GOT start: 0x00014360 GOT end: 0x000143a0
my hboot 0.98.0002 my version 1.47.401.4
what i am doing wrong?
Related
UPDATE: With all of the newer rooting and S-Off methods, and new hardware and firmware revisions, this thread may or may not help with your specific case if trying to unroot and go back to unrooted stock. I originally wrote this based of of the very first root methods known for the Launch EVO. There is a good chance that this method will still work, but there could definitely be something unaccounted for in your own specific case, so tread with caution. It is very doubtful that anything in this tutorial will result in your EVO becoming a fancy-schmancy paperweight, but if something goes afoul, you could have a nice headache to deal with...
Ok guys. There is a lot of partial and mis-information floating around out there about how to UN ROOT if you have to send your phone back for replacement, or you want the official unrooted OTA 2.2.
OLD NEWS!!!---> NEWER METHODS AVAILABLE TO ACTUALLY FIX PRI DOWNGRADE> SEARCH!!!! EDIT your PRI to show 1.40, thanks to sturmen for the pointer, and Calkulin for the method: http://forum.xda-developers.com/showpost.php?p=7267559&postcount=66
This assumes you are full root, S-Off. Note, this is not tested with simple root but should work (EDIT, Simple Root is basically Toastcfh's method, so you simple root users should be set), only with Toastchf's root method and nand unlock.
After reading every thread on the forum here, I think I finally found a fool proof way to do it. All the info was out there, but in several places and each one was missing something.
1) Before you start clicking and flashing and running RUUs, Check your HBoot build. You need to have the 0.76.2000 from Toastcfh's method #2. If you have 0.79.0000 (whatever) go to step 2 below. If you're getting Bootloader errors when running an RUU, I can almost guarantee that you don't have the correct HBOOT. If you somehow still have 0.76.2000 from previous modding, proceed to step 3.
2) Toast's Nand Unlock method. Found here: http://forum.xda-developers.com/showthread.php?t=701835
EDIT: The more I think about it, I think you can just run Simple Root to re-attain the .76 HBOOT and engineering build. It would eliminate the need for any adb, and SHOULD produce the same results. Just run the RUU after you run and complete simple root. See notes in BLUE below too!
THIS STEP IS 100% NECESSARY IF YOU HAVE THE .79 HBOOT version!!!...Do step #2 in Toast's thread, just like you did when you originally unlocked NAND (OR YOU SHOULD BE ABLE TO JUST RUN SIMPLE ROOT AGAIN...UNconfirmed, but should work methinks...). Not 100% sure which steps are necessary, but I do know you need to do steps #1 (Well, #1 is Nandroid Backup, so proceed at own risk if you skip) and #2 again. Make sure after you flash the Flash_Image, and the mtd-eng through adb, that you then load the PC36IMG.zip (Engineering Build), onto the root of your SD card, and boot into HBOOT, and let it install (just like you did when rooting). I didn't bother to flash the Recovery image at the end of step 3, but I don't think it would hurt if you're nervous about losing a custom recovery image in case this method for some reason does not work. It has come to my attention that flashing the engineering build (the PC36IMG from Toast's thread)through fastboot, might be as crucial as simply having the .76 HBOOT version. It at least is a surefire way to make sure you can run an RUU on top of it. There are probably other builds/roms that will work and allow you to run the RUU, but this one is confirmed, so don't skip that step!
3) If you have the 0.76.2000 HBOOT (can be checked by powering down, and booting by holding VOL down and Power), then you can go ahead and boot into the rom, and proceed with downloading the RUUs found here: http://shipped-roms.com/shipped/Supersonic/
Go ahead and download the first one (at least). I think the others are optional to "upgrade" but why should we care. We just want to go back to unrooted stock.
4) Make sure you have the latest version of HTC Sync installed, found here: http://www.htc.com/uk/SupportViewNews.aspx?dl_id=933&news_id=627
Install, and let it do it's thing. Will probably have to restart your PC when complete. Not even 100% sure this is necessary, but it won't hurt. It's basically for the HTC drivers from what I understand.
5) Run the RUU from your pc while your evo is in the phone loaded state of the Rom, (not the bootloader) with the phone connected through USB and have HTC sync selected. Even if it doesn't connect to HTC sync on your PC, you should be ok.
If you get a USB error after the screen goes black with the HTC LOGO, don't touch the phone. Exit the RUU via the EXIT button when given the option.
6) Run the RUU again and see what happens. The Error could happen 1 more time, but just exit again, and run RUU one last time.
7) Thank everyone here at XDA that our EVOs are so badass...I'm certinly not a dev, but these devs work hard for us to have the baddest ass phone there is right now.
Any problems, let me know. I assume your errors are the same ones I was getting, and it's all because of the wrong HBOOT.
I really take no credit for this, as I'm just compiling information in a tut....
Thanks op.
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
arozer said:
Or you can flash the new FroYo update release. =D
But thanks OP. Your hard work is much appreciated.
Click to expand...
Click to collapse
You might be correct, but I couldn't get the FROYO OTA to show up in any of the roms I was using.
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
sturmen said:
Question: what's the deal with the PRI? Has anyone been able to properly fix that yet?
Click to expand...
Click to collapse
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
EDIT: Yess! See below and in OP!
Bang3r said:
From my research, NO...Unfortunately, but this should get you as good as possible with what's out there now..
Click to expand...
Click to collapse
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
sturmen said:
Hm. I think I remember someone made a hex-edited PRI that people can flash in case they have to return it. I'll find it...
Click to expand...
Click to collapse
That would be cool, but I'm not too worried about that part. Phone is going back tomorrow!
Well, worry even less! Special thanks to Calkulin!
thankssssss
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
I'm getting error 155 running Ava Froyo and trying to go back.
blix1337 said:
I followed your guide and ran into a few issues. From my experiences, you can only run the RUU from your software version or higher (Can't use a 1.32 RUU on a Evo with software version 1.47). Therefore, I think everyone should always flash the engineering build so they can use the earliest RUU. Just my 2 cents though...
Click to expand...
Click to collapse
Yes, you are correct, but so am I. This is exactly what step 2 in the OP does (which is a link to Toastcfh's thread about the engineering build).
tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
Ok. RE-read the OP. Everything is there. Check your HBOOT version by booting to the bootloader. If you have .79, you need to re-flash the engineering build before the RUU will work (Step 2 in the OP to get HBOOT to .76). You cannot run the RUU on top of AVA froyo or any froyo, or any rooted custom 2.1 for that matter if you don't have the proper HBOOT (Which I believe you cannot have if you are running any custom rom). Flash to the engineering build, then the RUU.
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
joypunk said:
How far "unrooted" does this get you? Can you still re-root using toast's method or SimpleRoot?
Click to expand...
Click to collapse
Yes you can still REroot VIA those methods. As long as you don't do a FROYO OTA or manually flash the UNROOTED Froyo...there is no ROOT method for FROYO yet.
It returns completely to UNROOTED stock, except for the PRI, which there is a fix for on the 1st page.
And incidentally (and I just figured this out last night) Simple Root is Toast's method, just automated...
EDIT: I think that you could even UNROOT and RUU to 1.3x (whatever it is), then use the ROOTING methods that were in place before the official 1.47 OTA rooting methods. But, I just did simpleroot last night on top of 1.47, and it is freaking SIMPLE....1 click for root...1 click to flash recovery.
tpdtopcop said:
Thanks a lot for this. I have searched for a un root that worked and you were right the bootloader was the problem. Followed directions here and I am back to stock Froyo un rooted.
Thanks
topcop
Click to expand...
Click to collapse
This is what were trying to show you on Androidcentral as well. Glad you are set!
tonyk__78 said:
I'm getting error 155 running Ava Froyo and trying to go back.
Click to expand...
Click to collapse
As long as you have .76 HBOOT flash back to an earlier rom...one that has a 1.32 base. Then use the 1.32 RUU or 1.47 RUU. You should be set. Make sure you have completed step 2 in OP.
Yes. I have .79, thanks!
Sent from my PC36100 using XDA App
Here full RUU froyo update for Sapphire
http://www.filefactory.com/file/b4d...obile_US_3.12.531.1_FRG83D_release_signed.exe
Enjoy!
Cool
Sent from my HTC Magic using XDA App
RUU says:
Code:
ModelID: SAPP30000
CIDNUM: T-MOB010
This means this RUU is ONLY FOR the MyTouch3g (Sapphire 32B)
Not sure what this is ? (i mean,what is a full RUU froyo update for Sapphire)???
The rule of thumb is if you don't know what something is, chances are YOU DON'T NEED IT.
This is the official update to Android 2.2.1 (no Sense) for the MyTouch3G, which is the american version of the Sapphire 32B. As your country is Serbia, where the 32A was distributed, you should stay away from this.
Yeah but i got my phone in Switzerland ,so i got a 32b sadly.
I'd like to try this...are there any spl/radio req.?
You're better off using one of the custom, rooted ROMs based on this.
Lol k
Sent from my HTC Magic using XDA App
Keep getting download unsuccessful
Sent from my T-Mobile myTouch 3G using XDA App
Mirrored here: http://www.multiupload.com/MNJWXL0CX9
unable to root
so i installed this on my mt3g and it has unrooted my phone.
sapphire pvt 32b ship s-on g
hboot-1.33.0013 (sapp30000)
cpld-10
radio-2.22.28.25
oct 21 2009, 22:33:27
i've tried every method i could find (and understand) to try to reroot my phone to no avail.
ive done the unlockr method of downgrading using sappimg.nbh - including using a goldcard but i get an error that it failed and that its an older version (i just cant remember wat the exact message was)
ive done the universal unlocker thats supposed to work on the 2.2.1 but it freezes (super one click or somethign)
flashrec wont work obviously cuz i cant downgrade to 1.5
anything else i can try? im no expert obviously..but does this mean that i have to wait till a new, updated method is out to root my phone? since this is the latest tmobile release?
pakilord1211 said:
so i installed this on my mt3g and it has unrooted my phone.
sapphire pvt 32b ship s-on g
hboot-1.33.0013 (sapp30000)
cpld-10
radio-2.22.28.25
oct 21 2009, 22:33:27
i've tried every method i could find (and understand) to try to reroot my phone to no avail.
ive done the unlockr method of downgrading using sappimg.nbh - including using a goldcard but i get an error that it failed and that its an older version (i just cant remember wat the exact message was)
ive done the universal unlocker thats supposed to work on the 2.2.1 but it freezes (super one click or somethign)
flashrec wont work obviously cuz i cant downgrade to 1.5
anything else i can try? im no expert obviously..but does this mean that i have to wait till a new, updated method is out to root my phone? since this is the latest tmobile release?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=547133
i mean this pretty much says it all bro just read through it a couple times.
btw are you on 2.2?
thisishoot said:
http://forum.xda-developers.com/showthread.php?t=547133
i mean this pretty much says it all bro just read through it a couple times.
btw are you on 2.2?
Click to expand...
Click to collapse
What if I'm already on 2.2.1? What rom out there would be higher than that? I get the same Main Version Older message that they are? Is it referring to my hboot which is 1.33.0013?
did it...but ill try this
thisishoot said:
http://forum.xda-developers.com/showthread.php?t=547133
i mean this pretty much says it all bro just read through it a couple times.
btw are you on 2.2?
Click to expand...
Click to collapse
through settings i go to about phone and it says i have android version 2.2.1
i went through this process already but ill try it again because in the steps i took, i dont remember doing the reverse string thing. redownloading sappimg.zip now
appreciate the help
went through flashing sappimg...after a while it just says main version is older! update fail! do you want to reboot device?
ive rooted before and none of the processes ive used before are working. im thinking that i just need to be patient until a new method/adjustment comes out. but then again, im a newb.
So still new to rooting and custom roms and what not....bottom line is that this is for my T-Mobile mytouch 3g correct? I'm running the beatsmod from the forum runs pretty well I want to try this but I have a question do I need the new radio and spl? Or just flash in recovery mode?
can anyone give me an answer please?
Sent from my T-Mobile myTouch 3G using XDA App
pakilord1211 said:
so i installed this on my mt3g and it has unrooted my phone.
sapphire pvt 32b ship s-on g
hboot-1.33.0013 (sapp30000)
cpld-10
radio-2.22.28.25
oct 21 2009, 22:33:27
i've tried every method i could find (and understand) to try to reroot my phone to no avail.
ive done the unlockr method of downgrading using sappimg.nbh - including using a goldcard but i get an error that it failed and that its an older version (i just cant remember wat the exact message was)
ive done the universal unlocker thats supposed to work on the 2.2.1 but it freezes (super one click or somethign)
flashrec wont work obviously cuz i cant downgrade to 1.5
anything else i can try? im no expert obviously..but does this mean that i have to wait till a new, updated method is out to root my phone? since this is the latest tmobile release?
Click to expand...
Click to collapse
Lol . Search on the Android software development .. I think there are some apk`s that could help you with rooting ( or google one click root ) . After that you can instal a custom recovery by installing RomManager and install your desired recovery from there.
Hope I`ve made some sense ...Pm me if you don`t manage to do it.
bubert said:
Lol . Search on the Android software development .. I think there are some apk`s that could help you with rooting ( or google one click root ) . After that you can instal a custom recovery by installing RomManager and install your desired recovery from there.
Hope I`ve made some sense ...Pm me if you don`t manage to do it.
Click to expand...
Click to collapse
ive done the superclick method and it went nowhere but i see some further instructions that ill try with it. if i can get it rooted, ill be bale to manage from there hopefully with the recovery and the roms. even the universal one click root apk is useless now since 2.2.1 has patched the loophole it used to use.
ill give it a shot..l
great...superoneclick worked for me...thats what i get for trying to do things too quick...i actually tried using this before but it didnt work and now i see the reason y (too stupid to read instructions)
http://forum.xda-developers.com/showthread.php?t=803682
my phone is now rooted (i can grant superuser permissions)...now ill go on to installing a custom recovery and rom
sorry to those that had to put time into helping me due to me not doing my part and thanks for your help
and the beat goes on..
everything's getting weird now. my phone got rooted but i've been unable to install a custom recovery (amon_ra's). when i put in the appropriate command into terminal, i get an error that it failed or its not found and apparently its an issue with the root method that worked for me. yes i did use rom manager and flashed a recovery using rom manager but have been unable to boot into recovery. the tmobile screen comes up and the phone goes nowhere frmo there until i pull the battery and restart it.
now im trying another method to root and the whole sdk method is messing up. if i type fastboot devices into command prompt im told that theres a dsl missing. if i type adb shell or adb devices, adb is not a recognized command.
im considering accepting that all i can get is root and not a custom rom/recovery
Hi Guys,
Apologies if this has been discussed before. I have looked for answers everywhere and i could not find any.
Ok, I have a Desire S which is branded to Telstra (Australia), I was sick of all the useless app that Telstra had put in and wanted to get rid of all those.
I used revolutionary method to get it s-off and install Generic Firmware. After that i was happy not having any of Telstra's bloatware on the phone. Then came the update of 2.3.5 and as usual downloaded the firmware and used RRU to Update. Big mistake on my part, i didn't read anything and just tried to push RRU on the phone, the result was White screen with HTC logo and nothing past that. Tried everything no luck, then looking for answers, i found a solution to remove revolutionary, I could see revolutionary gone in HBOOT but the phone would not start.
to solve this i went to telstra to send it to repair, warranty was there and when telstra asked what happened, i said i was updating an app and it went to this screen, Tech guys said this is the similar 3rd problem in a day. so after 5 days the phone got repaired, New IMEI number and logic board had to be replaced.
Now all over again i have bunch of telstra bloatware on the phone. I want to get Generic 2.3.5 with sense 3.0. what is the process to follow so that i don't make the same mistake again?
All i want to do is get it s-off and install generic Firmware, the easiest way possible something like revolutionary. I tried going with ADB but found a bit risky.
Any advice in getting Generic HTC Desire S (2.3.5 with Sense 3.0) the easiest way would be helpful. Thanks in advance.
HBOOT info:
SAGA PVT SHIP s-ON RL
HBOOT-0.98.0002
RADIO-3805.04.02.01_M
eMMC-boot
Mar 30 2011,17:29:31
Thanks
To get a generic firmware from some other area, you need to get Super CID. I don't know much about it, just that CID's like a region code, Super CID enables you to get generic ROMs from any region. Only XTC Clip can do that on a Desire S as far as i know. Flashing a custom ROM after Revolutionary S-OFF is a better option....
Listen, I really recommend you to use a Custom ROM based on the update if you are ready to S-OFF. Hyperion is much faster and has a lot more features. Hell, if you do S-OFF, why settle for Sense 3? Get Sense 3.5. I recommend endymion.
@shrome99: Thanks dude, correct me if i am wrong, to get a generic firmware onto the desire s there is no option but to go for s-off and customs roms are better than stock ones, the reason i am asking is i have not used custom roms and willing to stick to stock.
What is the easiest way to get the rom sorted, I know how to get the custom rom installed there are too many posts everywhere that you can read through and make a decision and find roms of your choice, but there seems to be nothing about stock roms, i am sure there are people who are willing to get stock rom and their carrier is not rolling out the update coz they want more junk to be added.
Steps on how to get generic stock rom would be really helpful.
Thanks again
zryvffn said:
@shrome99: Thanks dude, correct me if i am wrong, to get a generic firmware onto the desire s there is no option but to go for s-off and customs roms are better than stock ones, the reason i am asking is i have not used custom roms and willing to stick to stock.
What is the easiest way to get the rom sorted, I know how to get the custom rom installed there are too many posts everywhere that you can read through and make a decision and find roms of your choice, but there seems to be nothing about stock roms, i am sure there are people who are willing to get stock rom and their carrier is not rolling out the update coz they want more junk to be added.
Steps on how to get generic stock rom would be really helpful.
Thanks again
Click to expand...
Click to collapse
+1 to above
IMO, if you're considering making a change then put on a decent custom (see my sig) you won't regret it
ben_pyett said:
+1 to above
IMO, if you're considering making a change then put on a decent custom (see my sig) you won't regret it
Click to expand...
Click to collapse
Hey Ben, Thanks for this, I went ahead and got the ROM as you suggested. Installed the base verison, then the add-on and the update. I have been palying around with it and so far loving it.
Only problem tough, I cannot use Market. I can open market look for apps and download, but when it starts to install, the phone re-boots. any known issues with this and is there a workaround to sort this out.
Ok, so here is what i did, Flashed Base version again and market started working again with no issues. Another issue which is not so much of an issue but only at night, why does the soft keys don't lit up on Desire S?. any way to fix these. Thanks guys.
Sometimes firing up and signing into Google talk makes the market start working again
Sent from my HTC Desire S using xda premium
sadsac said:
Sometimes firing up and signing into Google talk makes the market start working again
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Thanks for that, I did a search for the issue and did the same thing as you had advised, but didn't work. Then I flashed the base version again and then the update, which worked. Don't know what had happened there.
But yeah loving the new rom and i would say was a better move to be on a custom ROM and getting rid of Carrier's junk installed.
Cheers!
Ok, so instead of creating a new post i have decided to post it here since it is already been discussed.
I was happy with rooted phone and endymion Rom and was happy until my phone started heating up and restarted on its own as if it had a mind of its own, I called HTC and they advised to send it for repair, i had to unroot the phone and sent for repair. Got the phone back with updated version and i need help rooting the phone.
when i boot the phone in fast boot this is what i get:
****LOCKED****
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-BOOT
Aug 22 2011, 15:22:13
Android Version 2.3.5
HTC Sense Verison 3.0
Software Number: 2.14.841.4
Baseband Version: 2.14.841.4 CL 184593 Release-Keys
Now i need to Root the phone again so i can be another happy user of endymion.
I am looking at this guide and needed help.
http://forum.xda-developers.com/showthread.php?t=1443636&page=1
The oldest RUU i can find for my provider is RUU_Saga_Telstra_WWE_1.36.841.3_Radio_20.28d.30.0805U_3805.04.02.01_M_release_184558_signed.exe
I was reading the guide and this is where i am confused.
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 .
./misc_version -s 1.27.405.6 do i change this to 1.36.841.3 or leave it as it is?
Any help will be greatly appreciated.
Thanks.
IMO you can leave it as it is. 1.27.xxx is older than your RUU version so I think it will work fine.
chninkel said:
IMO you can leave it as it is. 1.27.xxx is older than your RUU version so I think it will work fine.
Click to expand...
Click to collapse
Thanks for that, yes i did follow the guide, and then got stuck again. The problem i am facing is after pushing all the files as of the guide, i run tacoroot the phone restarts and all i get is a red triangle with exclamation mark in it and nothing else happens.
then to get rid of it, i pull out the battery and do a complete factory reset. I have done this about 5 times now but still the same.
Also tried using super one click but that dint work either and freezes on waiting for device.
anything i have missed or is there any other solutions, any GUI programs or video to help if i am missing something.
any help is appreciated.
Thanks
I believe that you have to boot the original recovery before using tacoroot to get it working ( I mean boot it once, then boot normally).
After using tacoroot --root, your phone will probably go in bootloop, don't worry about that and change your misc_version as described in the tutorial.
And please, stop pulling out the battery, you will brick your phone this way.
chninkel said:
And please, stop pulling out the battery, you will brick your phone this way.
Click to expand...
Click to collapse
+1
You can pull it out as often as you want..but at least you should know the risk.
Sent by my fingers to your head
chninkel said:
I believe that you have to boot the original recovery before using tacoroot to get it working ( I mean boot it once, then boot normally).
After using tacoroot --root, your phone will probably go in bootloop, don't worry about that and change your misc_version as described in the tutorial.
And please, stop pulling out the battery, you will brick your phone this way.
Click to expand...
Click to collapse
I don't understand,"boot into original recovery". To try i booted the phone in HBOOT and pressed recovery and same thing the triangle shows. am i missing something here.
EDIT: I went till the last step and this is what i get "Patching and backing up partition 17...
Error Opening backup file.
#"
any idea
zryvffn said:
To try i booted the phone in HBOOT and pressed recovery
Click to expand...
Click to collapse
That's what I meant.
You can try misc_version_universal to avoid error patching partition 17 (see attachment below).
chninkel said:
That's what I meant.
You can try misc_version_universal to avoid error patching partition 17 (see attachment below).
Click to expand...
Click to collapse
Thanks dude, this worked and going thru revolutionary. i did some changes in the steps and will update what i did in a while after i get a rom installed.
Thank you everyone for help and support. i was able to downgrade my HBOOT and install a custom ROM. It would not have been possible if you guys had not supported.
one thing i have learnt is the more you read the more you find things useful and you actually learn how ti weigh your risk and benefits and avoid ending up with an expensive paper weight.
so this is what i did.
after using universal misc version file i was getting 140 error in RUU, boot loader version error, tried 3 time but would not let me get past that, then out of frustration i thought about giving it a last try for good or for worse, in the misc version section i changed a bit.
adb shell
cd /data/local/tmp
./misc_version -s 1.36.841.3 (Same number as my RUU)
then RUU went fine and then revolutionary.
well, if any kind of newbie person in trying to root the phone i would suggest to read and if you think you have read enough, its probably you haven't.
special thanks to @chninkel, @eyahl. Thanks Guys for all the support.
Cheers!
I want to downgrade my desire S to be able to use revolutionary.
Can I use this method? (http://forum.xda-developers.com/showthread.php?t=1399331)
My Desire has the following specifications:
- 2.3.5
- Hboot 2.000.002
- 2.10.401.8
What version do I download the RUU? 2.10.401.8?
If this method does not work what happens? The phone continues to work the same way?
Thanks
Fredericosilva said:
I want to downgrade my desire S to be able to use revolutionary.
Can I use this method? (http://forum.xda-developers.com/showthread.php?t=1399331)
My Desire has the following specifications:
- 2.3.5
- Hboot 2.000.002
- 2.10.401.8
What version do I download the RUU? 2.10.401.8?
If this method does not work what happens? The phone continues to work the same way?
Thanks
Click to expand...
Click to collapse
I really wish you wouldn't do that. Switching indiscriminately between HBOOT versions is one possible way (if something goes wrong) to convert your Desire S to one very expensive paperweight. Most new ROMs require the newer HBOOT. Guaranteed you won't be staying long on the old HBOOT. But if you insist, a brief glimpse at the Dev section should satiate your curiosity.
Saipro said:
I really wish you wouldn't do that. Switching indiscriminately between HBOOT versions is one possible way (if something goes wrong) to convert your Desire S to one very expensive paperweight. Most new ROMs require the newer HBOOT. Guaranteed you won't be staying long on the old HBOOT. But if you insist, a brief glimpse at the Dev section should satiate your curiosity.
Click to expand...
Click to collapse
So what you recommend to do root and install a new rom? The only way I have to s-off is downgrade hboot, for now...
Fredericosilva said:
So what you recommend to do root and install a new rom? The only way I have to s-off is downgrade hboot, for now...
Click to expand...
Click to collapse
Ok. Downgrade. But it's as easy as pushing the appropriate HBOOT to your device via ADB. If you've downloaded the appropriate HBOOT, you're almost there. It's as easy as using this tested & trusted method
Saipro said:
Ok. Downgrade. But it's as easy as pushing the appropriate HBOOT to your device via ADB. If you've downloaded the appropriate HBOOT, you're almost there. It's as easy as using this tested & trusted method
Click to expand...
Click to collapse
I believe it's not that easy. Engineering HBOOT (or any HBOOT for that matter) can't be flashed without S-OFF, since HTCDev-unlocked bootloader won't accept that flash, from ADB or any other source - the writes just won't go through, they'll be cached by eMMC and lost upon reboot.
So, as the OP says, he has no choice but to downgrade.
OP, there's a sticky in Development section, ROMS/RECOVERY/ROOT/HBOOT/etc. Please read it instead of posting, and you'll discover 3 guides (at least).
Jack_R1 said:
I believe it's not that easy. Engineering HBOOT (or any HBOOT for that matter) can't be flashed without S-OFF, since HTCDev-unlocked bootloader won't accept that flash, from ADB or any other source - the writes just won't go through, they'll be cached by eMMC and lost upon reboot.
So, as the OP says, he has no choice but to downgrade.
OP, there's a sticky in Development section, ROMS/RECOVERY/ROOT/HBOOT/etc. Please read it instead of posting, and you'll discover 3 guides (at least).
Click to expand...
Click to collapse
Well, that could be. But a few people seem to have done it via ADB. What really puzzles me is the number of people who unlock their phones using HTCDEV. It's unbelievable!
It seems much easier and less intimidating than S-OFF guides.
And then they're getting stuck, because they usually don't understand a thing in what they did. And then they come and open endless threads "Ok, I unlocked with HTCDev, now what do I do". Oh well, such is life...
mr
how to root evo 4g
Jack_R1 said:
I believe it's not that easy. Engineering HBOOT (or any HBOOT for that matter) can't be flashed without S-OFF, since HTCDev-unlocked bootloader won't accept that flash, from ADB or any other source - the writes just won't go through, they'll be cached by eMMC and lost upon reboot.
So, as the OP says, he has no choice but to downgrade.
OP, there's a sticky in Development section, ROMS/RECOVERY/ROOT/HBOOT/etc. Please read it instead of posting, and you'll discover 3 guides (at least).
Click to expand...
Click to collapse
Hmm confusing this root is....
Hmm been reading for a week now, I have the same Hboot and RUU and I'm a bit puzzeled.
I don't want to go the HTCDev way, because of the limitations afterward.
I have an unbranded Desire S, S-on and locked, with Hboot 2.00.0002.
- When I understand it right there is no other way then a downgrade right?
- This downgrade has to be done with Zergrush (although I thought it didn't work for 2.3.3 and above?) to gain temp root, then the misc_version to fool the phone so we can use the older RUU (not sure which one to take though, the oldest WWE?)
Now I could s-off through AlpaRev, but I have a question or two there as well
- I want to work with the Engineering Hboot (seems to be better?), can I do this directy via AlphaRev Iso, or do I need to flash/push it later? What would be the advantage over using the Alpharev one?
- Similar question, but now about the recovery that comes with Alpharev (CWM). I prefer 4EXT, can I bake that in in one go, or do I rather use the 4EXT installer from the market afterward?
Feel free to comment on my noobness, but on my desire it was a lot easier.
Don't want to end up with a paper weight.
Cheers
May the force be with you...
Edit: quoted the wrong post...
You sound very well informed and have done your research well, something to be commended.
Downgrade hboot, soff with revolutionary then afterwards fast boot flash eng hboot
Eng hboot is better IMO, as provides you more options
Swyped firm ym Desire S unsig XAD Permuim
ben_pyett said:
You sound very well informed and have done your research well, something to be commended.
Downgrade hboot, soff with revolutionary then afterwards fast boot flash eng hboot
Eng hboot is better IMO, as provides you more options
Swyped firm ym Desire S unsig XAD Permuim
Click to expand...
Click to collapse
Thanks for the boost of confidence, I'm no cmd line hero, hence the hesitation.
I used mainly terminal emulator to push recovery, hboot were easy as well with the right zip.
Could you comment in further detail about my RUU question and tell me if it is possible to add EXT4 install with Alparev?
Is this btw also a downgrade of the os and radio? I.o.w. does this process leave me with an old radio and os (2.3.3 without 3.0 sense)?
I understood as well that the hboot 0.98.0000 and 0002, work only with RUU containing 2.3.3?
Does this engineering boot work with 2.3.5 and above?
What confuses the hell out of me is the need to relock the phone, wasn't the whole idea not the direct opposite?
Why this need to relock?
Again, cheers for the help, on the old desire this was all quite easy obtained by just reading and a lot less command line code..
germsandbugs said:
Thanks for the boost of confidence, I'm no cmd line hero, hence the hesitation.
I used mainly terminal emulator to push recovery, hboot were easy as well with the right zip.
Could you comment in further detail about my RUU question and tell me if it is possible to add EXT4 install with Alparev?
Is this btw also a downgrade of the os and radio? I.o.w. does this process leave me with an old radio and os (2.3.3 without 3.0 sense)?
I understood as well that the hboot 0.98.0000 and 0002, work only with RUU containing 2.3.3?
Does this engineering boot work with 2.3.5 and above?
What confuses the hell out of me is the need to relock the phone, wasn't the whole idea not the direct opposite?
Why this need to relock?
Again, cheers for the help, on the old desire this was all quite easy obtained by just reading and a lot less command line code..
Click to expand...
Click to collapse
Yes once downgraded you will be on 2.3.3 and sense 2.1.
Did it myself a week back. Don't want sense 3.or 3.5. Perfectly happy with sense 4 and go back to 2.1 for camera.
Coming to the hboot.
you should definitely flash an eng-hboot, which is good on case you need warranty.
I would recommend you to go for the old eng hboot 0.98 as it had a larger cache memory. So should stay on 0.98 unless facing issues.
I don't think you need to relock again. That would be needed only if you need to go for warranty
If you follow the steps listed, out should be straight forward. Let me know if you need any help.
Swyped from a primed Desire S
hi everyone
i havebeen struggling with this for 2 years now. i have HTC sensation with hboot 1.18.xxxx that i bought in 2011. after the first year i have been keen to move to a newer rom. i have tried to look up inf in xda and elsewhere and got no where with this.
i have been worried about bricking so much that i didnt try to many weird procedures. i had even tried to go through with the android revolution installation procedure but failed right on. because revolutionary does not with with my device even though thr hboot is supported.
i badly need to move to a newer jelly bean based rom or later else my device is like a stone-age crap. i sincerely request some straight forward process / guidance of getting through this without weird, wire trick etc.
i really want to keep this device instead of buying a new device for no reason. but i dont know how to start and how to end. kindly help me out.
rajdeeprath said:
hi everyone
i havebeen struggling with this for 2 years now. i have HTC sensation with hboot 1.18.xxxx that i bought in 2011. after the first year i have been keen to move to a newer rom. i have tried to look up inf in xda and elsewhere and got no where with this.
i have been worried about bricking so much that i didnt try to many weird procedures. i had even tried to go through with the android revolution installation procedure but failed right on. because revolutionary does not with with my device even though thr hboot is supported.
i badly need to move to a newer jelly bean based rom or later else my device is like a stone-age crap. i sincerely request some straight forward process / guidance of getting through this without weird, wire trick etc.
i really want to keep this device instead of buying a new device for no reason. but i dont know how to start and how to end. kindly help me out.
Click to expand...
Click to collapse
1st
This is definately not the place to ask for "all inclusive help".
You should at least do some own basic researches or leave your phone as it is,
especially when you're worried about bricking your device.
There are so many excellent descriptions here, that could guide you to flash a custom rom.
2nd
If you are on hboot 1.18 you don't need to do the wire trick for s-off, just have a look at this.
If you searched a little bit, you'd find out yourself.
But even the wire trick is nothing "bad", I did it on 6 devices till now.
I'd like to encourage you to simply read/search a little bit more here in the forums before coming back and asking for help.
tom0769 said:
1st
This is definately not the place to ask for "all inclusive help".
You should at least do some own basic researches or leave your phone as it is,
especially when you're worried about bricking your device.
There are so many excellent descriptions here, that could guide you to flash a custom rom.
2nd
If you are on hboot 1.18 you don't need to do the wire trick for s-off, just have a look at this.
If you searched a little bit, you'd find out yourself.
But even the wire trick is nothing "bad", I did it on 6 devices till now.
I'd like to encourage you to simply read/search a little bit more here in the forums before coming back and asking for help.
Click to expand...
Click to collapse
thanks for the reply. as i mentioned revolutionary does NOT work for me. it says failed to get root. i have already tried those things about 8 times now and it didnt work for me. thats why i have posted here for help.
using htcdev i know i can try to unlock but it wont soff. so i dont know if that will help me or not.
rajdeeprath said:
thanks for the reply. as i mentioned revolutionary does NOT work for me. it says failed to get root. i have already tried those things about 8 times now and it didnt work for me. thats why i have posted here for help.
using htcdev i know i can try to unlock but it wont soff. so i dont know if that will help me or not.
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=2751187 to gain S-OFF. Don't worry about the htcdev part.
I did it on a complete stock sensation xe with hboot 1.27 or 1.29 (can't remember exactly).
Just use the temp root and rumrunner.
For any information read the thread first, before asking.
Also this thread should be moved, because it doesn't belong into the development section.
Sajito said:
Try this http://forum.xda-developers.com/showthread.php?t=2751187 to gain S-OFF. Don't worry about the htcdev part.
I did it on a complete stock sensation xe with hboot 1.27 or 1.29 (can't remember exactly).
Just use the temp root and rumrunner.
For any information read the thread first, before asking.
Also this thread should be moved, because it doesn't belong into the development section.
Click to expand...
Click to collapse
thanks i will try to read up and post back if needed. Admin please move the thread to appropriate category.
Sajito said:
Try this http://forum.xda-developers.com/showthread.php?t=2751187 to gain S-OFF. Don't worry about the htcdev part.
I did it on a complete stock sensation xe with hboot 1.27 or 1.29 (can't remember exactly).
Just use the temp root and rumrunner.
For any information read the thread first, before asking.
Also this thread should be moved, because it doesn't belong into the development section.
Click to expand...
Click to collapse
i went through the thread again and again but still find it somewhat confusing. I cant seem to separate the temproot process start and end in there. can someone outline just the temproot procedure and the pre-requisite for it ?
Does temproot require controlbear files ? rumrunner site says it requires a htc dev unlocked device. is that a must ?
rajdeeprath said:
i went through the thread again and again but still find it somewhat confusing. I cant seem to separate the temproot process start and end in there. can someone outline just the temproot procedure and the pre-requisite for it ?
Does temproot require controlbear files ? rumrunner site says it requires a htc dev unlocked device. is that a must ?
Click to expand...
Click to collapse
I'm not 100% sure about the exact steps anymore, but you don't need Controlbear, you just need the temp root.
When you have temp root, run rumrunner and follow the instructions.
I said read the thread, cause it might be possible that you get the message that it didn't work, while it actually did work.
You'll get everything needed in the thread. Otherwise just ask.
Sajito said:
I'm not 100% sure about the exact steps anymore, but you don't need Controlbear, you just need the temp root.
When you have temp root, run rumrunner and follow the instructions.
I said read the thread, cause it might be possible that you get the message that it didn't work, while it actually did work.
You'll get everything needed in the thread. Otherwise just ask.
Click to expand...
Click to collapse
Seriously dont know if i am plain unlucky or topic are not very useful for a newbie.
1. Revolutionary failed
2. i did temp root + rumrunner - failed (image attached)
I wonder if my device was not made on this earth or something. Just simply soff. Also dont know if i cant install a JB rom on this without soff safely.
rajdeeprath said:
Seriously dont know if i am plain unlucky or topic are not very useful for a newbie.
1. Revolutionary failed
2. i did temp root + rumrunner - failed (image attached)
I wonder if my device was not made on this earth or something. Just simply soff. Also dont know if i cant install a JB rom on this without soff safely.
Click to expand...
Click to collapse
What firmware and hboot do you have?
My rom is gingerbread stock version 1.52.xxxx and hboot is 1.18.0000
rajdeeprath said:
My rom is gingerbread stock version 1.52.xxxx and hboot is 1.18.0000
Click to expand...
Click to collapse
do you have sdk tools installed?(adb/fastboot)
also check if usb debugging mode is ticked
oh! hello again hope you are great.
yes i have adb setup properly. i do android dev so all development tools are setup properly. htc drivers are installed htc sync has been uninstalled.
i have tried on windows 8 and windows 7 pcs.
rajdeeprath said:
oh! hello again hope you are great.
yes i have adb setup properly. i do android dev so all development tools are setup properly. htc drivers are installed htc sync has been uninstalled.
i have tried on windows 8 and windows 7 pcs.
Click to expand...
Click to collapse
if revolutionary.io method doesn't work then try to update officially
see this thread
http://forum.xda-developers.com/showthread.php?t=1672425
then try with juopunutbear or rumrunner method again
rajdeeprath said:
My rom is gingerbread stock version 1.52.xxxx and hboot is 1.18.0000
Click to expand...
Click to collapse
One thing you could do is:
- get your phone updated to ICS (OTA over device settings) to get the latest firmware/hboot on it
- HTC Dev unlock your device (nothing complicated, you need to have fastboot running)
- Install/flash latest 4ext recovery (once more via fastboot) and enable smart flash option
Now in recovery with updated firmware/hboot make a nandroid backup and flash almost every rom you like.
In first place I'd not flash a CM12 rom.
tom0769 said:
One thing you could do is:
- get your phone updated to ICS (OTA over device settings) to get the latest firmware/hboot on it
- HTC Dev unlock your device (nothing complicated, you need to have fastboot running)
- Install/flash latest 4ext recovery (once more via fastboot) and enable smart flash option
Now in recovery with updated firmware/hboot make a nandroid backup and flash almost every rom you like.
In first place I'd not flash a CM12 rom.
Click to expand...
Click to collapse
firstly thank you very much for continuing to show hope. appreciate that. tell me thiss. i have a ota pending which i haven't gone for yet.
4.0 update sense 3.6 system upgrade 3.33.720.6
see attached image.
i never did that cause not everyone on htc blog had a good experience. Should i do that now ? will that help me move forward? will i be able to install android revolution or vipers or cyanogenmod after this? will i be able to soff?
i understand 3.33 is ics firmware ? right? what if i wish to go for jellybean ?
thanks
rajdeeprath said:
firstly thank you very much for continuing to show hope. appreciate that. tell me thiss. i have a ota pending which i haven't gone for yet.
4.0 update sense 3.6 system upgrade 3.33.720.6
see attached image.
i never did that cause not everyone on htc blog had a good experience. Should i do that now ? will that help me move forward? will i be able to install android revolution or vipers or cyanogenmod after this? will i be able to soff?
i understand 3.33 is ics firmware ? right? what if i wish to go for jellybean ?
thanks
Click to expand...
Click to collapse
since you update to ics you will be able to flash every ics/jb/kk/lp custom rom you like
so should i go ahead with the official ics update?
It's up to you.
Might be you're just satisfied with your new ICS firmware.
If you want to go further, unlock and custom recovery is an quite easy step.
For custom rom s-off is not necessarily needed.
Sent from my Sensation using XDA Free mobile app
rajdeeprath said:
so should i go ahead with the official ics update?
Click to expand...
Click to collapse
If you do the update, try again with rumrunner after it has finished.
Thanks. I updated to ICS and did a full factory reset. The device seems to be quiet smooth compared to GB though. The next update i do will be using what you suggested. Without SOFF flashing a custom rom.
When i get there i will message back on this thread. Going to test drive this ICS now for a while.time.