Related
Well I decided to jump the hoop and go for rooting my mt4g slide. Was doing great and unlocked it using the lovely All-In-One tool kit and couldn't get the phone to show S-off. I figured I needed to get this done before installing a rom's as I tried 2 different ones and neither would work. Tried a few different things and still wouldn't work to get S-off. Long story short, now I'm in a boot loop where the phone automatically goes into the boot loader. It will start up and show the mytouch splash screen before going into the loader. It will scan the sdcard for files and say there isn't a image etc and go back to the main boot loader screen. I can't do anything beyond that. I hit recovery, factory reset, and nothing. Tried putting roms and see if it would out of the blue read one.
It's my fault for taking the risk but adding a bit of insult to my injury is my back up phone, G1, won't even turn on now. So now I'm kind of phone less. Any suggestions on how to restore hboot?
1st of all WRONG FORUM!!!!!! This is for Development, not questions. That's what general is for. Second, there's a couple threads in General about this. Just hit search.
Magical Mods, may we please have this moved. Thanks.
Sent from my MIUI V4
take out your sdcard and use an adapter to put a stock PG59IMG.zip on your sdcard (make sure its named PG59IMG.zip) and go back into the bootloader. It will confirm if you want to install the zip and in 10 mins you'll be back on stock. Oh and ^ plus one please next time post in general as this has nothing to do with developing.
wow ya'll so testy today. I found the roms and info here in development forgive me for asking the question when something goes wrong on the programing side. One would think developers/programers would be helpful when the thread isn't how great the device is or what the bench marks are. Take a chill pill people.
fsured said:
wow ya'll so testy today. I found the roms and info here in development forgive me for asking the question when something goes wrong on the programing side. One would think developers/programers would be helpful when the thread isn't how great the device is or what the bench marks are. Take a chill pill people.
Click to expand...
Click to collapse
Thread reported just for the use of "take a chill pill."
blackknightavalon said:
Thread reported just for the use of "take a chill pill."
Click to expand...
Click to collapse
Yes, the correct terminology is 'Take a chill pill, Bill.
Can't get chill without the Bill.
fsured said:
wow ya'll so testy today. I found the roms and info here in development forgive me for asking the question when something goes wrong on the programing side. One would think developers/programers would be helpful when the thread isn't how great the device is or what the bench marks are. Take a chill pill people.
Click to expand...
Click to collapse
Sorry I wasn't "helpful". I'll do better to assist you next time....or just ignore it
I can't help you and I expect you to get a satisfactory answer.
fsured said:
wow ya'll so testy today. I found the roms and info here in development forgive me for asking the question when something goes wrong on the programing side. One would think developers/programers would be helpful when the thread isn't how great the device is or what the bench marks are. Take a chill pill people.
Click to expand...
Click to collapse
XMC, a Dev. He helped you, we where all noobs once. You should check out the "Welcome to XDA Video". Just follow the Rules. That's all, follow the rules.
Sent from my MIUI V4
To supplement what Agent said the appropriate section for this would be the General section.
Additionally the development area is where devs post new roms, tools and hacks. Users can add observations to these threads to further development.
Hastily spouted for your befuddlement
fsured said:
Well I decided to jump the hoop and go for rooting my mt4g slide. Was doing great and unlocked it using the lovely All-In-One tool kit and couldn't get the phone to show S-off. I figured I needed to get this done before installing a rom's as I tried 2 different ones and neither would work. Tried a few different things and still wouldn't work to get S-off. Long story short, now I'm in a boot loop where the phone automatically goes into the boot loader. It will start up and show the mytouch splash screen before going into the loader. It will scan the sdcard for files and say there isn't a image etc and go back to the main boot loader screen. I can't do anything beyond that. I hit recovery, factory reset, and nothing. Tried putting roms and see if it would out of the blue read one.
It's my fault for taking the risk but adding a bit of insult to my injury is my back up phone, G1, won't even turn on now. So now I'm kind of phone less. Any suggestions on how to restore hboot?
Click to expand...
Click to collapse
"tried a few different things" to get S-Off?
There are two ways of getting S-off. One is done with Revolution if your HBOOT is earlier than 1.45. The other is juopunutbear if your HBOOT is 1.45. Did you check your HBOOT version before "trying a few things"?
Did you read the instructions for the all-in-one toolkit? Or possibly just follow the steps in order in the program? It's specifically designed so you don't need s-off.
I'm assuming you must have flashed CWM recovery since you said you did a factory reset. Did you do Juopunutbear or revolution, or are you planning on leaving S-ON? If S-ON, Did you flash a kernel(boot.img) using the toolkit? If you can get into HBOOT and get into recovery, there's no reason you should need to revert to stock. However, if your plan is to continue doing steps before reading the instructions, you should probably revert to stock anyway before you really do brick your device.
This link will provide you everything you need to get your device running. Just follow the spteps from the beginning. If your bootloader is already unlocked from HTCDev, then start at the step directly after unlocking the bootloader.
http://forum.xda-developers.com/showthread.php?t=1532809
The toolkit worked well for me (even though it was my first attempt at anything), so I guess I'd echo that. It also matched with the step-by-step guides on stuff I found elsewhere in the forum. BUT there is a real difference in the method and order of things for the two hboots, hence KarriOn's questions.
However, having rooted and S-Offed, I then got a bit cocky and managed to end up in a not dissimilar position to you! Total panic, but I managed to get out by thinking through what I'd done, researching, and the cause and hence solution became clear. Took a night sleeping on it, and 2 hours.
what HBOOT?
Did you unlock the boot loader?
Did you get recovery on
Did you do a backup before going any further?
Sent from my myTouch_4G_Slide using xda premium
I followed the all in one tool for everything. I've finally been able to get into cwm recovery. For awhile it wouldn't and I gave up for the night. Came back yesterday morning to tinker with it more and it worked. I've tried flashing the superSu.zip file in cwm and after it reboots it still reads s-on. But either way I can't get the phone to do anything other than boot into the bootloader screen. I'm going to check out the link about 2 posts up and tinker with it after work. Thanks for the replies!
http://forum.xda-developers.com/showthread.php?t=1532809[/QUOTE]
Oh yeah, that is the tread I used and the tool. After getting unlocked from HTC I tried flashing a rom and it wouldn't work. Figured I needed to get s-off for roms also. That is where my error started.
fsured said:
http://forum.xda-developers.com/showthread.php?t=1532809
Oh yeah, that is the tread I used and the tool. After getting unlocked from HTC I tried flashing a rom and it wouldn't work. Figured I needed to get s-off for roms also. That is where my error started.
Click to expand...
Click to collapse
You don't need S-Off for ROMs to work. It sounds like you didn't flash a kernel after installing a ROM. The instructions on doing this are listed in the all-in one tool thread, the "flash ics roms with s-on" thread, and even on the all-in one tool interface itself.
fsured said:
I followed the all in one tool for everything. I've finally been able to get into cwm recovery. For awhile it wouldn't and I gave up for the night. Came back yesterday morning to tinker with it more and it worked. I've tried flashing the superSu.zip file in cwm and after it reboots it still reads s-on. But either way I can't get the phone to do anything other than boot into the bootloader screen. I'm going to check out the link about 2 posts up and tinker with it after work. Thanks for the replies!
Click to expand...
Click to collapse
Flashing SuperUser won't get you to S-Off. Hasoon2000 has two different toolkits. One that will guide you through the rooting process and the other on how to gain S-Off using the Juopunutbear method. Having S-Off isn't necessary to root but it will take a few extra steps to flash a different ROM with S-ON. I was too much of a chicken to try the S-Off method since there is some risk involved but several have reported that it worked successfully for them.
First android phone it's a AT&T One X, i'll be using it on the Bell network. Got a good deal on Kijiji and I didn't ask enough questions apparently, lol.
The phone is clearly not stock, took me several hours to piece that together. I get it, I'm a noob. I can tell it's running Cleanrom 4.5. I want to get it back to something close to stock. I plan to learn all about rooting/roms but I want to do it from a vanilla phone so that I get to actually do it myself.
I googled and found a tutorial (link). I deleted the 'su' file and superuser.apk. I followed the rest of the steps and it didn't seem to do anything, just rebooted back into cleanrom.
I kept googling and now I'm following this guide: http://forum.xda-developers.com/showthread.php?t=1859714
I guess i'm going to flash from an RUU now ? My CID is 11111111, so I've read that means I have superCID and any RUU will work. I want to get to JB eventually, so can I just flash direct to the Europe 3.14 JB from HTCRUU? Or go with one of the ICS versions?
Am I doing this right?
No no no!
Edit: still writing but wanted to say don't flash that ruu
If you want completely stock you need to use fast boot and boot into hboot and run fastboot OEM lock
(You may need to search around to learn how do that)
Then run this ruu. http://beta.androidfilehost.com/?fid=9390077933525139511
Sent from my One X using Tapatalk 2
that is for the wrong phone
only place you should look at is here AT&T, Rogers HTC One X, Telstra One XL
Its good your asking the questions now if you want to go completely stock run an ruu which means relicking the bootloader and running it ill link you to some guides in a sec
---------- Post added at 07:43 AM ---------- Previous post was at 07:43 AM ----------
Oh and like others said don't use that ruu! We have the one XL
cleanrom 4.5 is pretty good and close to stock but adds quick settings, debloated, power menu and some other tweaks. i would keep it how it is and just learn about how custom roms work. you can learn how to use twrp in its current state and maybe learn how to use some root apps.
just so you know your phone is the evita not the endeavoru.
Thanks for the replies.
I haven't tried flashing anything yet so don't worry. I'm taking it slow.
I've already been into fastboot. Figured that out because it was a required step in the guides I said I was trying to use. I have all the drivers installed and I'm able to talk to the phone via fastboot at the comand prompt.
LOL, thanks for letting me know my phone is Evita. I guess I can delete the 600mb RUU I downloaded
I'm a little unclear about HBOOT vs. fastboot. I can get into the bootloader and go to the fastboot USB mode... is this analogous to HBOOT?
So my steps right now are:
1) Download correct RUU, Evita 2.20 ICS - I've also seen people discussing 1.85 vs 2.20, why chose one over another?
2) fastboot oem lock
3) Install RUU while phone is in bootloader mode
That right?
I would strongly suggest to slow down, and learn more about what root is and means, before going back stock. Root is just a change in permissions. You gain absolutely nothing by unrooting, and lose quite a bit. You lose the ability to do all sorts of mods to your phone, flash custom ROMs, use apps that require root like Adaway and Titanium Backup (and many others), remove carrier bloatware, activate tethering, and much more.
People have gone through great pains to find root methods for our device (and other Android devices). Many come on here looking for these root methods, for the awesome benefits that root means. I've seen very few, if any, people before you that have said "crap I accidentally got a rooted device, and don't want root". Think about that one for a while.
Plus, CleanROM 4.5 is already based on a more updated firmware version than any of the official AT&T RUUs. Plus it includes a lot of cool features and optimizations. Again, going from CleanROM to stock is a step backwards, not forwards, and you are gaining nothing, and losing quite a bit. Another thing about CleanROM, is that it is devoid of the AT&T bloatware (and there is a lot). Keep in mind that on the stock AT&T ROM, the bloat is not removable without root, so you are stuck with quite a few crappy apps that you will never use. That alone is a huge reason to have a rooted device. Also bear in mind that stock AT&T does not allow tethering (unless you have a data plan that allows it) and has other stock HTC apps (like FM radio) disabled. These cannot be enabled unless you have root.
Another thing, is that you will not get Jellybean any faster on stock than rooted. While its true that rooted, this phone will not be able to take the OTA when it rolls out (hasn't happened yet). But a stock rooted JB firmware will almost certainly be posted here on XDA, that is safely flashable on a rooted device. This often happens within a couple days of the OTA starting to roll out, if not faster. Sometimes even before the OTA, as sometimes the official RUUs get leaked before the OTA. All it takes is for a dev to get his hands on the files, apply root, and upload it here. Learning how to flash such a file to your device is very simple. Not much more than: download the file to your phone, boot into recovery, and press "install". So yet again, stock gains nothing over being rooted.
While its true that root is not for everyone. But if you've already found this place, and learned what things like RUU, bootloader, and fastboot are, then you probably already know more than most folks do about Android. You may feel in over your head, but it really just takes a few hours of reading to learn the fundamentals. And with that knowledge, you can do so much more with your phone than you can without root.
redpoint73 said:
I would strongly suggest to slow down, and learn more about what root is and means, before going back stock. Root is just a change in permissions. You gain absolutely nothing by unrooting, and lose quite a bit....
Click to expand...
Click to collapse
I appreciate the advice, thanks. To be clear, eventually I will probably bring the device back to where it is now. I've used linux before so I have an understanding of the permissions system and the added benefits of root.
My goal here is to get the phone back to stock so that I can learn the rooting/flashing process from the start, not the end. I understand why that might seem counterintuitive but I'm a very hands on person and I'll learn more of the theory by walking through the process than reading about how somebody else hacked this device to get where it is now.
Sure I'm making extra work for myself but I know what im getting into.
Sent from my HTC One X using xda app-developers app
echoboomer said:
I appreciate the advice, thanks. To be clear, eventually I will probably bring the device back to where it is now. I've used linux before so I have an understanding of the permissions system and the added benefits of root.
My goal here is to get the phone back to stock so that I can learn the rooting/flashing process from the start, not the end. I understand why that might seem counterintuitive but I'm a very hands on person and I'll learn more of the theory by walking through the process than reading about how somebody else hacked this device to get where it is now.
Sure I'm making extra work for myself but I know what im getting into.
Click to expand...
Click to collapse
You should have said so from the start, then. This pretty much negates everything I just typed above.
Its admirable that you want to learn the process from scratch, and its the opposite attitude of most n00bs here.
My advice, as another mentioned above, is stick to XDA, and don't follow instructions from random Googled sites. Most of those sites don't clearly delineate between our phone (Snapdragon S4) and the international (Tegra3) version, and following instructions for the international version is a great way to brick your phone.
Other than that, lock the bootloader, run the RUU, and have fun. Also check your hboot version. If its anything but 1.14, don't run the 2.20 RUU. You will want the 1.73 or 1.85 RUU instead, as the 2.20 RUU will update the hboot to 1.14, which plugs the holes by which boot.img and radios can be flashed from recovery. Unless you want to create ever MORE work for yourself, as the hboot can be downgraded using a Linux computer, lol!
Be sure to check out my index thread, as most anything you will need is here: http://forum.xda-developers.com/showthread.php?t=1671237
Thanks, sounds like I'm on the right track.
Also check back to my OP, I did say that I wanted to learn the whole process but I wanted to do it from stock. sorry you typed all that out but in sure it will help some other noob down the line.
Last thing, 1.85 vs 2.20?
Sent from my HTC One X using xda app-developers app
ChummyDays said:
2.20 has the new hboot, and that means that you have to extract the boot.IMG out of the ROM and flash it through fast boot. With 1.85 you just flash the ROM.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Cool thanks, I found a tutorial last night on how to extract boot.IMG from the ruu exe. I think I'm good to go.
Sent from my HTC One X using xda app-developers app
You might be confused. You shouldn't have to pull a boot.img from an RUU typically, only from a custom ROM zip. And only if you are on boot 1.14.
Sent from my HTC One X using xda app-developers app
Probably confused. Here's what I see in the boot loader.
***
Tampered
Unlocked
Evita PVT Ship S-ON RL
HBOOT-1.09.0000
Radio-0.19as.32.09.09_L
OpenDSP-v28.1.0.32.0504
eMMC-boot
***
Sent from my HTC One X using xda app-developers app
echoboomer said:
HBOOT-1.09.0000
Click to expand...
Click to collapse
This is what you want to see, and why you need to be sure to use the 1.85 RUU.
Background:
My wife migrated from the (US AT&T) One X to the One on day one. Her One X has been sitting in her bedside drawer for almost a year. (She wanted to keep it as a backup.) Her One recently suffered irreparable physical damage; need to get her up and running on the One X.
Before the One X's temporary retirement, we:
Gained SuperCID
Unlocked Bootloader
Flashed custom recovery
Flashed a (Android 4.1 based) AOKP nightly
Did not achieve S-OFF
When the One X came back out of retirement, it had some major stability issues. Coming from the Nexus world, and (admittedly) not doing thorough enough research, I thought I could quickly re-ROM her phone and have her up and running.
Long-story short, I've somehow seemed to corrupt the recovery partition and the boot partition. And I'm not sure where to go next...
I can access the bootloader and fastboot. In fact, the bootloader is immediately loaded on boot.
I cannot achieve S-OFF. Every method I've seen requires some combination of fastboot and adb commands. I can do the fastboot portion, but without a working Android partition, I cannot perform the adb commands.
Every attempt to flash a custom recover via fastboot fails:
FAILED (remote: 12 signature verify fail)
From the research I've done, it seems like I need S-OFF to flash a recovery and ROM, but I need a ROM to achieve S-OFF.
Is that the case? Is there anything else I can try?
Run the 2.20 RUU, it's the only option you have, it should fix your partitions. Do not run the 3.18 RUU while s-on though or you'll brick.
How did the phone end up with borked partitions?
Sent from my Evita<br>
timmaaa said:
Run the 2.20 RUU, it's the only option you have, it should fix your partitions.
Click to expand...
Click to collapse
Found and downloaded 2.20 RUU; was nervous as hell running this with S-ON. The process never errored out, and the application never hung, I never saw a progress bar on the HOX either. (RUU quoted ~10 minutes. I waited 40.) I hard-bounced the phone and tried again... Success!
Thanks for the recommendation!
timmaaa said:
How did the phone end up with borked partitions?
Click to expand...
Click to collapse
I pushed the stock T-Mobile ROM to the phone from the older recovery that was already on the HOX, then rebooted. It hung at boot; was never able to boot back into Android. I was still able to access the bootloader and fastboot, so I tried pushing TWRP to the HOX using the WinDroid Toolkit. After that, I wasn't able to access Android or TWRP, and the phone booted directly to the bootloader.
The biggest mistakes: cockiness and lack of research. (Statement of frustration: this S-ON/S-OFF nonsense is for the birds!)
I'd strongly suggest you get s-off now, and discontinue your use of toolkits in favour of manual fastboot commands.
Sent from my Evita
timmaaa said:
I'd strongly suggest you get s-off now, and discontinue your use of toolkits in favour of manual fastboot commands.
Click to expand...
Click to collapse
Noted. Thanks...
The whole situation was frustrating because it was self-inflicted and I knew better than rush into trying to re-ROMing on hardware I wasn't familiar with.
I usually don't use toolkits; was just on a system that hadn't been prepped with adb yet. I re-learned a valuable lesson: take the time to set that up!
What's most frustrating is that I did try to use adb (after hosing the filesystem). I just kept running into issues with S-ON while trying to push boot.img's and recoverys. Coming from my Nexus world, I'm not accustomed to that.
Cool cool. It might be worth taking a quick look at my Evita FAQ and How-To Guide For Beginners threads in my signature. I'm not insinuating that you're a beginner, but they contain some vital information specific to this device which you might find useful.
Sent from my Evita
timmaaa said:
It might be worth taking a quick look at my Evita FAQ and How-To Guide For Beginners threads in my signature. I'm not insinuating that you're a beginner, but they contain some vital information specific to this device which you might find useful.
Click to expand...
Click to collapse
Yeah... that -- among many, many others threads -- was one of the threads I checked out after killing it.
I was so convinced that S-ON was my problem that I spent most of my time trying to get S-OFF and repair my recovery via fastboot. Had I been able to let go of that notion, I might have gotten somewhere without having to ask for help.
I only-ever mess with the wife's hardware when there's a problem, so I'm not incredibly familiar with it. I'll definitely re-review your guide before I take on any other tasks!
Thanks again!
Okay....so I need to twiddle around with my trusty old HOX in order to solve the constant rebooting issues. (I also want to jump ship off of the memory-heavy Viper Venom that's on it to just straight CM or something similarly light weight)
To do that I've got to update the firmware.
And to do that... first I have to identify what bloody firmware I have so that I use the correct updating method and don't brick my one and only device.
I'm not a total noob... I've been working on a beginner/moderate level with Android for 3 years now... I can get around ADB (typos not withstanding) reasonably well, push commands, get to hboot, know fastboot and such... but I am just not finding the specific answers I need right this moment to get this work done. So if Someone can point me in the proper direction, I would be muchly appreciative.
Right Now my bootloader screen says the following
Tampered
Unlocked
Evita PVT Ship S-ON RLHboot 1.09.0000
Radio 0.20os.32.09.10_2
OpenDSP-v31.1.0.45.0815
eMMC-boot
Click to expand...
Click to collapse
So, who can tell me which firmware version contains Hboot1.09? Once I know that, I can start the process of SuperCID and S-OFF to make these updates. Barring that, anyone who can point me to a one-click unlock tool would be great too... the ones I find on the first few pages of the forum all recommend firmware newer than what I know is installed on here according to the above into, and I am leery to use them for risk of bricking my one and only phone.
Your current firmware is actually irrelevant, you need not worry about that at all. All you need to do is get s-off, which should be a sinch. Because you don't have SuperCID (I'm assuming from your last paragraph) you really only have one option, which is the Rumrunner method. It should work with Viper installed, if not it has a good success rate with the Kickdroid ROM.
Rumrunner S-off
Sent from my Evita
So I did have SuperCID... a readCID command demonstrated that.
and thanks to your assuaging my fears, timmaaaa, I was able to flash to 2.15 without a problem.
the problem now... is even after pushing TWRP every way I know how, I can't get into recovery, even with fastboot erase cache. ugh I feel like yanking my hair out.
but at least the phone hasn't randomly slowed down or rebooted since flashing the new firmware. (and the pesky double-reboot that made flashing it such a core in the first place is fixed too)
::edit:: gonna spend the next hour redownloading the venom ro so I can push the boot.img file, maybe that will fix things.
Did you check the md5 of the recovery download?
Sent from my Evita
timmaaa said:
Did you check the md5 of the recovery download?
Sent from my Evita
Click to expand...
Click to collapse
Yes I did. I also tried to install it via a few onboard solutions like goo.im. no go. it says it's been installed, fastboot insists the phone is unlocked and s-off; but it boots to the flash screen, tries to load recovery, fails, and reboots to the rom.
I am going to assume that the unlock is fubar somehow and start from scratch by installing 2.20 and using the HTC unlock, and go from there.
now if only damned downloads didn't take 5 hours on my slow rural connections... thank you isp conglomeracy.
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.