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
<Collaboration><Dev><Ideas> HTC Evo 2.3.3 Gingerbread Root Collaboration.
* I love the color orange.HTC Evo 2.3.3 Gingerbread Root Collaboration
The Lowdown on Everything
FASTBOOT
HTC's RUU releases basically run the adb reboot bootloader code, reconnect to the phone, verify the version and run a series of fastboot commands to install the contents of the PC36IMG (detailed below). In the same way it may be possible to run fastboot commands from command prompt with the SDK installed if you can time it just right in the flashing process, or not. The bootloader can be quite picky when it comes to letting anyone or anything flash anything lower than the version on the phone, or unsigned.
Click to expand...
Click to collapse
PC36IMG
The PC36IMG is what is flashed in the bootloader. The contents of the zip include the radio, system, and more. As long as S-ON is present the bootloader won't flash any PC36IMG that isn't signed by HTC themeselves, however with S-OFF you can flash custom PC36IMGs as well as downgrade, because the bootloader doesn't check the firmware version to see if it's newer or not. If someone was however to be a sneaky awesome ninja and steal HTC's secret sauce then we could simply sign any PC36IMG we wanted to and fake a newer version in the android info txt.
Click to expand...
Click to collapse
RECOVERY
From my understanding the stock recovery references alot with the bootloader to check for most of the same checks it looks for in the PC36IMG, but in the update.zip HTC includes for updates. The stock recovery won't flash anything but signed HTC update.zips either, which again you need the special sauce to sign. Custom recoveries like Amon RA or Clockwork remove the security and don't reference with the bootloader (since your phone has to be S-OFF anyways to flash a custom recovery.) A custom recovery is the key in flashing customs roms and kernels, if you can achieve it with the security on (S-ON) the you won't even have to worry about achieving S-OFF. However, that's near impossible due to the security in the bootloader HTC implements with updates. Which is why the bootloader has to be cracked to install anything.
Click to expand...
Click to collapse
RUU
The RUU is an official tool HTC puts out so people can reflash there phone with a stock firmware just like if it is brand new and your turning it on for the first time. The files included inside of the RUU frontend include the PC36IMG which is essentially what is flashed in the process, but in a fancy way I guess you could put it. The same security applies to the RUU, you can't downgrade versions without S-OFF because the bootloader still checks the version on the phone currently to see if it can flash the PC36IMG or not (when security is on [S-ON] )
Click to expand...
Click to collapse
APKS
I'm sure alot of you know of applications such as Visionary or Z4Root, they both use common exploits to root your phone in a simple application, first temp root then permanent root. They push the approiate resources, Superuser, su, busybox, set the permissions for everything to run, and clean up everything in the blink of an eye thanks to simple scripts. The same thing is still quite possible with any exploit, the exploit just has to be found in the software. You find the exploit you gain root. You have root you can do almost anything to your phone, but S-OFF still plays a role in everything with what you can and cannot flash. Sigh. I know right..
Click to expand...
Click to collapse
Our Mission
The whole purpose of this thread is to collaborate on possible ways to obtain S-OFF and/or root on 2.3.3, either update. We are community, thus we must act like one, and not bash each other for trying. If you have a truthful idea or any questions feel free to post them. You never know, you could very well help with rooting the latest update. This has gone on far to long it's been almost 2 months and no root. This is our time to free each other from the chains of security because we all like to be dangerous sometimes.
Click to expand...
Click to collapse
Possible Rooting Ideas
What Works What Doesn't
I encourage everyone to try previous rooting methods, and methods to obtain S-OFF and experiment as much as they feel comfortable with, you never know what you might find. We could be overlooking something.
Click to expand...
Click to collapse
There is no right or wrong answer only better ones than others. Please do not bash users, or slander them for there ideas, everyone has a right to post, but please stay on topic. /end
Am I missing something?
Sent from my PC36100 using XDA Premium App
lil_bono said:
Am I missing something?
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
Just give me a few, I'm still typing.
<done></done>
<words>I'll be back on tomorrow, I'm going to go lay down and talk to my friend. Feel free to comment with any ideas. I, myself, am looking into and working very hard to achieve S-OFF and root for the 2.3.3 update, it will come in time. That's just the key; time.</words>
What other phones have you developed, alone or with a group, a rooting and/or s-off type process for? And I don't mean an app that uses an already known exploit such as rageagainstthecage.
I guess at least we have a fancy thread now. Best of luck to everyone.
ill jsut post a small snippet of thanks for thaking this initiative, i dont know about android os myself one bit, so i can hardly contribute, but would there be a way to "fool" the hboot or Ruu version number ?
either fooling the hboot into thinking the ruu one is trying to flash ( to downgrade of course) is a higher version one, or to somehow change the RUU itself to report a different version number? i realize this may sound incredibly stupid as my programming knowledge is very limited, but jst throwing it out there...
once again, thanks for taking this initiative for the evo 4g community
I was wondering if you could force the RUU update. We know it verifies the version on the phone, but surely to could still flash if it was forced. Sort of like doing an nvflash on the tablets. You'd just need to hack the RUU updater to skip the version check and flash anyway. Unfortunately, I'm not a cracker, so...
This should take off
There's a whole thread in Evo General full of ideas due to some kind of "bounty" to whomever achieves root on 2.3.3. At least we could get a start on what does/doesn't work. (This is not meant to deter traffic from this brainstorming thread)
http://forum.xda-developers.com/showthread.php?t=1162671
skatrwannabe3 said:
There's a whole thread in Evo General full of ideas due to some kind of "bounty" to whomever achieves root on 2.3.3. At least we could get a start on what does/doesn't work. (This is not meant to deter traffic from this brainstorming thread)
http://forum.xda-developers.com/showthread.php?t=1162671
Click to expand...
Click to collapse
Hey, great idea. Just so you know, there is no "bounty" on rooting the ota. I dont even know where that term came from. I just started a thread to say that I am desperate for root, I will pay for someone to figure it out. I never asked anyone or expected anyone else to throw money in on it too. It has since grown into a 600+ dollar pot, and I think that its a good thing. The people that take the time to root it should get a pat on the back.
On topic: I see a bunch of people saying to downgrade, isnt temp root gonna come before that? Shouldnt temp root be the thing to focus on first?
I'm not much of a programmer but ill brick my phone as many times as needed lol
Sent from my PC36100 using XDA App
github said:
What other phones have you developed, alone or with a group, a rooting and/or s-off type process for? And I don't mean an app that uses an already known exploit such as rageagainstthecage.
I guess at least we have a fancy thread now. Best of luck to everyone.
Click to expand...
Click to collapse
I've personally never been the leader of a rooting or S-OFF project before, but my knowledge of Android on a whole is pretty vast. I do develop roms and kernels as well as themes and apps for Android in general, so I guess I'm pretty qualified?
fldash said:
I was wondering if you could force the RUU update. We know it verifies the version on the phone, but surely to could still flash if it was forced. Sort of like doing an nvflash on the tablets. You'd just need to hack the RUU updater to skip the version check and flash anyway. Unfortunately, I'm not a cracker, so...
Click to expand...
Click to collapse
I'm not sure that the RUU is anything but a front end user interface for the process, the actual flashing and everything involves the bootloader, which is why it still pushes the PC36IMG temp. to the sdcard. It might however be in the RUU itself and using fastboot flashes? I'll look into it. Good idea, thanks.
Who rated the thread bad?
bubby323 said:
I'm not sure that the RUU is anything but a front end user interface for the process, the actual flashing and everything involves the bootloader, which is why it still pushes the PC36IMG temp. to the sdcard. It might however be in the RUU itself and using fastboot flashes? I'll look into it. Good idea, thanks.
Click to expand...
Click to collapse
but does the RUU update the hboot itself?
the point is , older hboots and android software are already rooted, if we can get back to those , the end result is the same, we get root, then upgrade using a stock rooted rom, problem solved
bubby323 said:
What Works What Doesn't
Click to expand...
Click to collapse
My recent failures attempts while on 4.24 S-On:
Amon_Ra Recovery PC36IMG.zip flashed from Hboot
Signed 3.70 PC36IMG.zip flashed from Hboot
Signed 4.24 PC36IMG.zip flashed from Hboot (it loads/updates, but is basically a factory reset)
3.70 RUU exe
UnrEVOked3
some chucklehead
bubby323 said:
Who rated the thread bad?
Click to expand...
Click to collapse
Eh, I put in a 5 star vote to make it up, also to show the uselessness of voting.
Has anyone looked at the contents of a PC36IMG.zip? I am still decompliling one, but its a fun task to decipher all of the code. Another thing I need is for someone to tell me which files I should be looking for as far as HTC signing. What I would like to do is maybe strip it from the stock one, and insert it into a custom image.
Sent from the land of motorcycles!
Hi everyone,
I just received a used AT&T One X in the mail and was hoping to root and install CM10. The phone came with 1.85 and I was able to get root using the manual method, but hasoon2000's all-in-one tool fails repeatedly to execute the xfactor exploit. I accepted both of the backups on my phone, and as the phone reboots into the bootloader the command line prints "[-] Failed" and returns that my CID is still CWS_001.
I've tried just about everything I can think of and I'm about to give up. I've read that updating to 2.20 with the RUU and then retrying the all-in-one tool has worked, but the RUU will not complete either (I repeatedly get a low battery or USB connection error despite a fully charged battery and correct USB drivers).
Is there anything else I'm missing, or should I just give up and return this thing?
Put the phone down and read read read. The last thing you want to do is upgrade from 1.85 to 2.2 by ota or by ruu.
Sent from my HTC One XL
954wrecker said:
Put the phone down and read read read. The last thing you want to do is upgrade from 1.85 to 2.2 by ota or by ruu.
Sent from my HTC One XL
Click to expand...
Click to collapse
I've spent hours upon hours reading and have seen nothing about that, so how about a link rather than a condescending reply?
Thank redpoint73.
http://forum.xda-developers.com/showthread.php?t=1671237
Sent from my HTC One XL
I used the adb method for 1.85. I didn't get any errors at the command line, until I try to get superuser access in adb and I get "/system/bin/sh: su not found."
MOD EDIT: unhelpful.
Anyway, it's getting late so I'll check in on this tomorrow. If someone has some insight, I would appreciate it.
Thread Cleaned
Thread cleaned. Keep it more helpful or move on to the next thread please.
mf2112
XDA Moderator
SuperSU says that I don't have the SU binary installed. I thought maybe the binary linked in the 1.85 rooting method post might be the problem, so I tried pushing the binary from androidsu.com and I still have the same problem - no su access at the command line, SuperSU says no binary is installed, busybox won't install. My bootloader does say TAMPERED.
Solved! For anyone who finds this later with the same problem, I tried the 2.20 RUU in fastboot for the 4th or 5th time, and it finally worked! Once I was on 2.20 I was able to easily use the all in one tool to unlock my bootloader.
oceanminded said:
Solved! For anyone who finds this later with the same problem, I tried the 2.20 RUU in fastboot for the 4th or 5th time, and it finally worked! Once I was on 2.20 I was able to easily use the all in one tool to unlock my bootloader.
Click to expand...
Click to collapse
Lol... that's why all in one tools are bad for the community. If you actually read the compilation thread, you'll find a 1 click Super CID and root script for 1.85.
Hope you don't brick your device soon.
Enjoy hboot 1.14 you definitely deserve it
Sent from my HTC One XL
954wrecker said:
Enjoy hboot 1.14 you definitely deserve it
Sent from my HTC One XL
Click to expand...
Click to collapse
He will eventually want to downgrade just like all 1.14 hboot users. He would have to search and read for the script though, oh no.
Sent from my One X using xda premium
thedauntlessone said:
Lol... that's why all in one tools are bad for the community. If you actually read the compilation thread, you'll find a 1 click Super CID and root script for 1.85.
Hope you don't brick your device soon.
Click to expand...
Click to collapse
Yeah, I tried both of those and neither worked. But again, thanks for assuming that you're the only person who reads the stickies. Jesus, this is a hostile forum. Every other device I've owned the communities have been welcoming and helpful, but here it's always LOL CAN'T ROOT? GO READ NEWB. When I posted here I was hoping to get some feedback from someone who might understand what was going on, but I guess that's not the majority of people on this forum. If someone finds this thread with the same problem in the future, I hope they can figure it out as I did.
I had hboot 1.14 when I got the phone, and I see no reason to downgrade now that I've got CM10 up and running, which is all I wanted in the first place.
No you didn't. You were on hboot 1.09. Don't claim we don't know jack when you clearly don't know what you're talking about.
It would be safe to say it's user error if you can't use the super CID script or 1.85 root others else seems to be able to use them without fail.
And this forum seems to be filled with noobs posting asking for root when there are people who take time out of their life to compile resource for noobs to read. If you followed the instructions to the tee, everything would work.
Thank you all for your help, I have learned a great deal in just a short time of reading thanks to your contributions. I have been away for a few months and last I checked, this exploit was not available. I was very pleased to find the wealth of new information and have been reading about the current exploit, and then Hasoon's GUI soon after. But then I too had the same error when attempting both methods, the command line prints "[-] Failed" and returns that my CID is still CWS_001. I am fairly certain my version is 2.20. But I see you mention HBOOT 1.14 Could someone tell me do I need to downgrade to Hboot 1.09 first? Also, point me to the information thread on this or do I just need the Jewel/Evita toolkit? Thanks again for such great support.
Nevermind I figured it out, thank you for all the good reading.
Hi,
First of all, I'm new to this Forum, but i've been following it for quite a while now since almost everything Android related you can find here. And People around here seem really knowledgeable.
I've trying to update my One SV K2_UL, and i seem to got it messed up.
I was able to flash the update, and everything went smoothely, until i got to the firmware files, a cannot get them to flash.
I guess the problem is my phone is S-ON, and i cannot change it's CID, although a tried several ways of doing it.
And i cannot guet my phone to be S-OFF, i tried Moonshine but it gets stuck on second test. - "Waiting for ADB".
My phone is exactly the same as leegreenaway refers in this post:
http://forum.xda-developers.com/showthread.php?t=2512742&page=9
so i guess, it's not an equipment problem, it was really my order of doing things that screwed this.
Can someone please help me? What can I do?
I tried to revert to old version but with no luck.
Thank you in advance.
Rui
Yes, as long you are S-On, you can't flash the firmware files.
If moonshine don't work for you, you can try the new rumrunner S-Off (which is made from the same people).
Take care on the instructions on the page there, as it is new, i can not really tell you how it will work.
I have tried rumrunner also, it behaved a little different from moonshine since it passed the second test, and found the device, but than nothing, it didn't go further it just said - "Press Enter to Exit.".
Thanks for the fast reply btw.
Then maybe this post, can give you a helping hand.
If you have Norton Antivirus, disable it. Make sure, you have a sdcard in the phone.
I did had Norton in the beginning of my day, but i already uninstalled it, just to make sure,.
I do have a sdcard on my phone.
So i tried running rumrunners once again, and took a ps of what is happening.
View attachment 2398349
When i see it right, you are on windows 8?
Windows 8 is known as not "driver-friendly" related to android/adb.
Maybe you have a chance to use a Windows 7 PC or even Linux.
Maybe @beaups knows whats the problem is...
Yes you're right,
i'm on windows 8.
unfortunately i do not own any PC with win7, althought ADB looks to be working right since i was able to use the shell and other adb stuff, i might as well give it a try tomorrow at work. I just hope i can turn this around, the phone is working great appart from that fantastic noise the speaker makes.
Thank you.
Well, today I tried to use both moonshine and rumrunner at work, but with no luck. The pc at work is running win7, althought the problem persisted exactly the same in rumrunner, in moonshine it was a bit different because it only stopped the second time it was waiting for adb. I was wondering if someone with the orange phone from UK could provide the firmware from that update, and if this souls male a difference.
Thanks again,
Sent from my HTC One SV using xda app-developers app
Last idea on my side:
You wrote in first post, you flashed everything except firmware. That means, you have the Sense 5 software already installed?
I think you should try then with the stock software, moonshine is made for.
Maybe its checking the version (HTC One SV (k2_ul) 2.14.401.6) and fails, because it is wrong.
Well, actually I got that same conclusion in my mind yesterday, just when I arrived at home from work. So I used the 2.14 odexed stock you provided in a thread, and from there I was able to run moonshine, it completed successfully, and after I just had to re-flash the 3.22 odexed, change the cid and flash the firmware. Voila, problems solved everything is in order now.
So the problem was only, the boot img moonshine was trying to flash would never work on my sys version.
Thank you very much for your help, this was a great learning experience.
Cheers,
Rui
Sent from my HTC One SV using xda app-developers app
Glad you got it sorted out.
old.splatterhand said:
Yes, as long you are S-On, you can't flash the firmware files.
If moonshine don't work for you, you can try the new rumrunner S-Off (which is made from the same people).
Take care on the instructions on the page there, as it is new, i can not really tell you how it will work.
Click to expand...
Click to collapse
Thankyou thiese s-off utility helped me to take s-off
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.