[SOLVED] Rooting a Factory-S-OFF'ed Desire S (need assistance) - HTC Desire S

Hi all,
so I've been reading around here for a few weeks now. Found a few guides on rooting the Desire S and tried to get basic orientation.
Now I'd like to discuss my particular situation for a bit with you guys, before I attempt to actually do the job on my phone.
There is a slight difference between where I'm finding myself and where all the rooting guides seem to aim:
I bought my Desire S already S-OFF'ed.
You can see my exact specs at the lower end of this post.
As it appears, AlphaRev and Revolutionary are supposed to be used with S-ON devices. I'm not sure what would happen if I run these tools with my S-OFF device.
GingerBreak doesn't work with HBOOT-0.98.0002. So that won't help me either.
The most promising method i found so far is the Temproot + Revolutionary method by Silver Bullet, which has been tested on a device with the exact same Hboot and ROM build as mine, with the only exception, that I am on S-OFF.
Today I've been successful in achieving temporary root access, using the commands from Silvers thread. (I got the # prompt.)
Sof far, so good. Now I've got and S-OFF'ed device with temporary root access possibility.
Silver proposed this in a personal message (hope it's ok I'm posting it here):
You could try to get temporary root access using the commands I have posted in my guide. If you get the "#" prompt then you have root access, so you could use dd from the command prompt to a) backup your current HBOOT, just in case, and b) flash the recovery manager of your choice.
With the recovery manager in place, you'd be able to flash whatever rom you like.
Please note that I have no means to test this procedure on my own!
You should take your risks if you dare!
Now I don't understand how I "use dd from the command prompt to a) backup your current HBOOT, just in case, and b) flash the recovery manager of your choice."
So what do all of you think about this approach? Do you see it as safe? If not, what could possibly be a safer method? Any other suggestions/comments?
Also, could anyone kindly direct me to some info about how exactly do I flash a recovery in this setup?
Thanxalot!

since you are already s-off i think you should be able to install a custom recovery on your device(im not sure about this you may want to wait for someone else to confirm this just to be safe)
once you have a custom recovery you can install a custom ROM or a prerooted stock ROM to gain ROOT access
try this recovery
this is the link to the DS index thread for easy access to more useful threads

If you are s-off, you have fastboot so you can flash a recovery with adb. And flash a new rom
Sent from my HTC Desire S using XDA Premium App

kartkk said:
since you are already s-off i think you should be able to install a custom recovery on your device(im not sure about this you may want to wait for someone else to confirm this just to be safe)
once you have a custom recovery you can install a custom ROM or a prerooted stock ROM to gain ROOT access
try this recovery
this is the link to the DS index thread for easy access to more useful threads
Click to expand...
Click to collapse
Yea, I've been thinking in the same direction.
So there are two possibilities I can think of right now, as to how to install 4EXT recovery.
1) Download "4EXT Recovery UPDATER" to my phone -> then -> Enter temporary root state using adb -> then -> download & flash 4EXT recovery automatically using "4EXT updater"
or
2) Download "4EXTRecovery_v2.1.0_saga.zip" to computer -> then -> enter temporary root state using adb -> then -> flash "4EXTRecovery_v2.1.0_saga.zip" from computer using fastboot.
Agreed? Which one seems more reasonable to you guys?

Could someone experienced please confirm that I'm getting this right?
Flashing 4EXT recovery via fastboot:
1) download <4EXTRecovery_v2.1.0_saga.zip>
2) extract the <recovery.img> file from that zip archive
3) run these commands: fastboot flash recovery recovery.img
Correct? Do I need to wipe something first or can I just flash right away?
Secondly, Silver was talking about first backing up my current Hboot using adb, before I attempt to flash the 4EXT recovery. Does anyone please know how to do this? Can't find it anywhere explained.
Thanks

You'll first need to download and extract the adb & fastboot links from my signature and esnure that you have the HTC Drivers installed on your PC (also in my links in my signature).
Then follow the instructions within the Flash CWM & su via fastboot link that's in my signature.
That will put CWM (clock work mod a custom recovery and make you root by installing the su (super user) )
I'd say follow this and then once you've CWM and are root simply install the 4EXT from the market and update recovery to 4EXT (again link in my sig).
Any question then fire away?

ben_pyett said:
You'll first need to download and extract the adb & fastboot links from my signature and esnure that you have the HTC Drivers installed on your PC (also in my links in my signature).
Then follow the instructions within the Flash CWM & su via fastboot link that's in my signature.
That will put CWM (clock work mod a custom recovery and make you root by installing the su (super user) )
I'd say follow this and then once you've CWM and are root simply install the 4EXT from the market and update recovery to 4EXT (again link in my sig).
Any question then fire away?
Click to expand...
Click to collapse
Ok, got you ben_pyett. Thanks for clear instructions.
So no way (or need) to backup hboot prior to flashing recovery?
And no need to enter temporary root state before flashing WCM?
Gonna give it a try.

mimirom said:
Ok, got you ben_pyett. Thanks for clear instructions.
So no way (or need) to backup hboot prior to flashing recovery?
And no need to enter temporary root state before flashing WCM?
.
Click to expand...
Click to collapse
You can always get the original HBOOT (recovery) back from a stock ROM RUU if and when you need, see link to STOCK ROMS in the thread DEV INDEX
you may be able to do it via temp root fr3vo and adb but I'm not 100% . Temp root - If you're S-OFF I don't think you need to, but be sure to flash correct verison of CWM (saga) or else there is trouble.

I downloaded the newest CWM (recovery-clockwork-5.0.2.0-saga.img) for saga from the Clockworkmod website.
Attempted to flesh it simply using fastboot. This is what I got.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So perhaps the next step could be 1) get into temporary root state 2) flash
Comments?
edit: Ok, I see now the difference - to do it via temproot + adb I need to work with android up and running.

mimirom said:
I downloaded the newest CWM (recovery-clockwork-5.0.2.0-saga.img) for saga from the Clockworkmod website.
Attempted to flesh it simply using fastboot. This is what I got.
So perhaps the next step could be 1) get into temporary root state 2) flash
Comments?
edit: Ok, I see now the difference - to do it via temproot + adb I need to work with android up and running.
Click to expand...
Click to collapse
was your device in HBOOT, FASTBOOT USB ?
How to start Fastboot USB mode:
Unplug USB
Turn the device off
Hold volume down button (HOLD IT) and press power
Hboot will start.
Wait for sdcard scan to complete.
Plug in USB cord connected to the computer
Press power ONCE and Fastboot USB mode starts

ben_pyett said:
was your device in HBOOT, FASTBOOT USB
Click to expand...
Click to collapse
Yes, it was. That's why I get the device listed when I do the <fastboot devices> command
I tried the same procedure also in hboot mode, but there I get a <waiting for device>
When the phone is in fastboot I get <FAILED (remote: not allowed)> now.
Thanks for your assistance ben_pyett. Appreciate it.
edit: So something changed, since I'm not getting the <FAILED (command write failed (Unknown error))> anymore, but now it's <FAILED (remote: not allowed)>

Ensure that you device has device has "Debug USB" enabled
Boot and then Settings->Applications->Development->USB Debugging = YES (tick)
and then try again

Unfortunately that's not the problem. The phone has been in debugging mode from the beginning. It also shows the <usb debugging connected> in status bar when I connect it.
I found an older thread where people seem to have been successful rooting s-off devices with superoneclick. Will read through it.

Thinking back to what I did after I'd Made my s devices s-off although I used xtc
Although first question, have you tried running ginger break? You'll find a link to it from within the root section of the http://forum.xda-developers.com/showthread.php?t=1146601DEV INDEX a sticky in that forum on the root sub section
Anyway what I did myself I've I was s-off was to Install a boot image that then enabled me to simply run one click, which gave me root.
http://forum.xda-developers.com/showthread.php?t=1105763 Link to boot image post
You find link the link to ginger break and super one click used with in the Dev INDEX within the root sub section
So try ginger break first and if that doesn't work, then boot image and super one click which is literally that easy
Once you're root simply download ROM manager from Android market and use that to install Cwm as it's only one click
Good luck
Swyped from my Desire S using XDA Premium

Great help, thanks!
I tried Gingerbrake a few weeks ago without success. A far as I know it doesn't work with HBOOT-0.98.0002. Some folks propose downgrading the hboot but I noticed that it's supposed to be dangerous. However I'll give it another try.
The one click method you propose looks good, thanks. I remember though that I tried to flash something using a "PG88IMG.zip" during my few initial attempts to get root, and my phone refused to read it from the sd card.
Would love to try it right away, have to leave though...
Cheers.

Hi ben_pyett,
it clicked! (pun fully intended)
I first flashed the boot image and then ran SuperOneClick.
I have SuperUser installed. RootChecker confirmed full root access. Right now Im doing a Nandroid backup from CWM recovery.
Loved to see that recovery screen again (I'm coming from Wildfire)
So thank you ben_pyett for your patience and willingness to offer not-just-sporadic support.
_______________________________________​
There were slight complications occurring during the root process. Superoneclick hanged at step 6. After disabling USB debugging it showed a few more lines in the right window section and after enabling USB debugging again it finished the root procedure without further problems.
It seems to me that the phone now takes longer to shut down plus, more importantly, Wifi stopped working. It gives an error message on the Wifi tab in settings.
Actually the phone appears generally unstable now. It just gave me a <Tell HTC> notification with something like "the phone just recovered from an abnormal reboot."
Hope I can sort this out by flashing a new rom...
So far, so good. Go to bed now.

mimirom said:
Hi ben_pyett,
it clicked! (pun fully intended)
I first flashed the boot image and then run SuperOneClick.
I have SuperUser installed. RootChecker confirmed full root access. Right now Im doing a Nandroid backup from CWM recovery.
Loved to see that recovery screen again (I'm coming from Wildfire)
So thank you ben_pyett for your patience and willingness to offer not-just-sporadic support.
_______________________________________​
There were slight complications occurring during the root process. Superoneclick hanged at step 6. After disabling USB debugging it showed a few more lines in the right window section and after enabling USB debugging again it finished the root procedure without further problems.
It seems to me that the phone now takes longer to shut down plus, more importantly, Wifi stopped working. It gives an error message on the Wifi tab in settings.
Actually the phone appears generally unstable now. It just gave me a notification with something like "the phone just recovered from an abnormal reboot."
Hope I can sort this out by flashing a new rom...
So far, so good. Go to bed now.
Click to expand...
Click to collapse
Now you have root you can get custom recovery and from there you can Custom ROMS, there are loads to choose from.
All the problems you report are fixable.....wifi fails as boot image is missing Wifi do modules, but a custom well resolve that, glad you got there in the end.
Ensure that you have Settings->Power->Fastboot set to OFF (un-ticked)
night

Can't root your desire s ? Me too...

smartceleron said:
Can't root your desire s ? Me too...
Click to expand...
Click to collapse
Well, no, I actually rooted it the way described in this thread... The thread is also labeled as "solved" now.
Did u try to follow the steps described? What are your specs?
Sent from my HTC Desire S using XDA App

Related

Bootloader unlocked, what next?

Hi everyone,
I would like to install a custom ROM onto my HTC Desire S but I can't seem to find a guide that I can understand. I do have some experience in flashing a LG Arena if that would help.
Anyway, I have unlocked my bootloader with the official HTC tool yesterday and I have a bit of a problem.
If I want to S-OFF my phone with Revolutionary, I can't select my current HBOOT version (2.00.0002 or so).
My question is; what do I do next?
Thanks in advance
Sent from my HTC Desire S using XDA App
I'm pretty sure there are other ways to s-off now. If you do a search you should find them. But I'm not even sure if you need s-off to install roms if you have unlocked the bootloader
Sent from my DesireS using xda premium
You cannot S-Off with hboot 2.00.0002 (at least there's no way I saw here). You can though downgrade the hboot to 0.98.0000 following the steps in THIS guide, then you can S-Off with Revolutionary.
Even you decide not to downgrade, you should still be able to flash ROMs following the instructions from another topic (all credits should go to Skanob):
Originally Posted by Skanob
You should be able to change your recovery without any problem if your s-off or unlocked 2.xx.xx hboot s-on.
1. Get 4ext recovery.img
2. connect phone on fastboot
3. In cmd use these command to push the recovery image:
fastboot flash recovery D:\recovery.img (<- should be directory of 4ext recovery image)
fastboot reboot-bootloader
Now you should have 4ext recovery.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
Once you have 4EXT Recovery installed, just reboot in recovery and flash the ROM you want
Alright, that helps me a lot! But don't I have to root my phone before I'll be able to install a custom ROM?
EDIT // If I browse to the 4ext website, I cannot download the .img but I can download the app, although it says that it can only be used on S-OFF devices. Where can I get this image file and how do I apply it to my phone? I'm very confused right now.
EDIT // When I was browsing through my Downloads folder, I saw a folder "4EXTRecovery_v2.1.0_bravo" that contained a file "recovery.img". I've used this earlier to unlock my bootloader. Can I use this one in Recovery as well?
Sent from my HTC Desire S using XDA App
You can also just obtain temporary root using for example the zergRush exploit:
http://forum.xda-developers.com/showthread.php?t=1296916
Nilscollection said:
Alright, that helps me a lot! But don't I have to root my phone before I'll be able to install a custom ROM?...
Click to expand...
Click to collapse
No you don't need root at that point. With the method described by Skanob you can flash 4EXT Recovery and after that you can flash a rooted ROM (all ROMs here at XDA are rooted anyways)
Nilscollection said:
...
EDIT // If I browse to the 4ext website, I cannot download the .img but I can download the app, although it says that it can only be used on S-OFF devices. Where can I get this image file and how do I apply it to my phone? I'm very confused right now.
...
Click to expand...
Click to collapse
Sorry cause I was not very clear from the beginning. I don't find it right now, there was a 4EXT flashable zip somewhere from which you could extract the recovery.img file. You can download THIS file (credits goes to caelli) then perform the following:
1. Rename file to PG88IMG.ZIP and place it on the root of your sdcard
2. Boot with vol down + power
3. Wait till the image is recognized (PG88IMG.ZIP is the standard name for radio images and system will recognize and try to flash it)
4. Press vol down for YES (to flash it)
5. Reboot (it'll ask you to press vol down or up for reboot)
After having that flashed, either enter recovery via powerup with vol down pressed and choosing Recovery from boot menu or by issuing on the computer adb reboot recovery command (with phone connected with USB cable). Either ways you'll end up in recovery from where you can flash a rooted ROM of your choice.
As alternative, you can extract the recovery.img from this zip file and follow the instructions that I've give to you in the previous post.
Nilscollection said:
...
EDIT // When I was browsing through my Downloads folder, I saw a folder "4EXTRecovery_v2.1.0_bravo" that contained a file "recovery.img". I've used this earlier to unlock my bootloader. Can I use this one in Recovery as well?
Click to expand...
Click to collapse
That is the file you should find though I don't know if it'll work. The one I've linked above works for Desire S since it was used by one of the members (you can find his post in the same topic where Skanob gives the instructions).
Good luck...
Well, it's been a while and I haven't get a single step closer to installing a custom ROM.
This website says that unlocking the bootloader also makes you perm root, is that true?
Anyway, I've tried rooting my phone using this guide but as soon as I press "root", SuperOneClick freezes and I can't do anything any more.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can someone please help me with this?
Nilscollection said:
Well, it's been a while and I haven't get a single step closer to installing a custom ROM.
This website says that unlocking the bootloader also makes you perm root, is that true?
Anyway, I've tried rooting my phone using this guide but as soon as I press "root", SuperOneClick freezes and I can't do anything any more.
Can someone please help me with this?
Click to expand...
Click to collapse
No need, download the 4ext app, start it, go to online upgrade.
Choose the latest touch version (i would recommend it, but you can choose whatever you like) and hit download only.
Copy the received recovery.img to your pc and flash it at the commandline with
Code:
fastboot flash recovery recovery.img
.
Now you have a recovery.
Download the ROM you like and flash it with recovery.
Reboot to bootloader (no normal reboot in between, it's the last option in 4ext).
Flash the boot.img from the downloaded rom zip with
Code:
fastboot flash boot boot.img
Swyped from my Desire S far away from my PC (maybe)
Tectas said:
No need, download the 4ext app, start it, go to online upgrade.
Choose the latest touch version (i would recommend it, but you can choose whatever you like) and hit download only.
Copy the received recovery.img to your pc and flash it at the commandline with
Code:
fastboot flash recovery recovery.img
.
Now you have a recovery.
Download the ROM you like and flash it with recovery.
Reboot to bootloader (no normal reboot in between, it's the last option in 4ext).
Flash the boot.img from the downloaded rom zip with
Code:
fastboot flash boot boot.img
Swyped from my Desire S far away from my PC (maybe)
Click to expand...
Click to collapse
How do I flash this exactly? Where do I put "fastboot flash boot boot.img", or are these the options when in recovery mode?
EDIT // When I try to upgrade in 4EXT, it says I have to install BusyBox first. BusyBox then says I don't have my phone rooted. What should I do now? I have the free version of 4EXT, if that helps.
Nilscollection said:
How do I flash this exactly? Where do I put "fastboot flash boot boot.img", or are these the options when in recovery mode?
EDIT // When I try to upgrade in 4EXT, it says I have to install BusyBox first. BusyBox then says I don't have my phone rooted. What should I do now? I have the free version of 4EXT, if that helps.
Click to expand...
Click to collapse
Ok, another way, download the Android sdk and instal it.
When your finished open a terminal and type adb devices, if your device is shown as combination of letters and digits your good to go, otherwise download htc sync, instal it and afterwards uninstall it (it's just for the drivers, they won't be removed at uninstall).
Download the attached recovery.img, reboot your device to bootloader and attach it to pc.
Open a terminal and execute the recovery command (make sure you are in the folder where the img file is).
Afterwards boot to recovery flash the ROM and the boot img.
Here is the recovery.img
Pls tell me when you downloaded it, because i will delete the link afterwards.
Swyped from my Desire S far away from my PC (maybe)
Tectas said:
Ok, another way, download the Android sdk and instal it.
When your finished open a terminal and type adb devices, if your device is shown as combination of letters and digits your good to go, otherwise download htc sync, instal it and afterwards uninstall it (it's just for the drivers, they won't be removed at uninstall).
Download the attached recovery.img, reboot your device to bootloader and attach it to pc.
Open a terminal and execute the recovery command (make sure you are in the folder where the img file is).
Afterwards boot to recovery flash the ROM and the boot img.
Here is the recovery.img http://db.tt/9lvfKV7n
Pls tell me when you downloaded it, because i will delete the link afterwards.
Swyped from my Desire S far away from my PC (maybe)
Click to expand...
Click to collapse
I downloaded it! I'll try it now. Thanks a lot!
EDIT // I got into 4EXT Recovery, now what? Should I put my desired ROM onto my SD-card?
Since you unlocked with htcdev, you need to flash the boot.img of your desired ROM separately. You have to do this each time you install a new ROM.
on your PC, extract the boot.img from your ROM file. put both ROM file (probably zip) and the boot.img on your Sd card. (You might create an extra folder for stuff like that on your SD card)
Get into recovery, make backup and wipe and format all. (not SD card
Then choose "flash zip from Sd card"when you're in recovery and flash the ROM first, second the boot.img.
Reboot your phone and you're done.
Edit: try endymion 3.4
Sent by my fingers to your head.
eyahl said:
Since you unlocked with htcdev, you need to flash the boot.img of your desired ROM separately. You have to do this each time you install a new ROM.
on your PC, extract the boot.img from your ROM file. put both ROM file (probably zip) and the boot.img on your Sd card. (You might create an extra folder for stuff like that on your SD card)
Get into recovery, make backup and wipe and format all. (not SD card
Then choose "flash zip from Sd card"when you're in recovery and flash the ROM first, second the boot.img.
Reboot your phone and you're done.
Edit: try endymion 3.4
Sent by my fingers to your head.
Click to expand...
Click to collapse
Alright, gonna try. Let's hope this works!
I'm pretty sure you'll be happy... Post your result here
The phone might take some minutes for the first boot. just be patient
Sent by my fingers to your head.
eyahl said:
I'm pretty sure you'll be happy... Post your result here
The phone might take some minutes for the first boot. just be patient
Sent by my fingers to your head.
Click to expand...
Click to collapse
Could that be like +5 minutes?
Nilscollection said:
Could that be like +5 minutes?
Click to expand...
Click to collapse
Yep. For me it took once about fifteen minutes.
Just.be.patient.
Sent by my fingers to your head.
eyahl said:
Yep. For me it took once about fifteen minutes.
Just.be.patient.
Sent by my fingers to your head.
Click to expand...
Click to collapse
Nope, just had to flash the boot.img as well! ICS works all great now, I love it!
Thank you SO MUCH for your time / effort, all of you
Nilscollection said:
Nope, just had to flash the boot.img as well! ICS works all great now, I love it!
Thank you SO MUCH for your time / effort, all of you
Click to expand...
Click to collapse
well, we told you very often to do so:
Tectas said:
Download the ROM you like and flash it with recovery.
Reboot to bootloader (no normal reboot in between, it's the last option in 4ext).
Flash the boot.img from the downloaded rom
Click to expand...
Click to collapse
Tectas said:
Afterwards boot to recovery flash the ROM and the boot img.
Click to expand...
Click to collapse
eyahl said:
flash the ROM first, second the boot.img.
Click to expand...
Click to collapse
and its written in so many guides...
anyways, always happy to help, have fun with flashing roms, and dont forget to backup everytime...
eyahl said:
well, we told you very often to do so:
and its written in so many guides...
anyways, always happy to help, have fun with flashing roms, and dont forget to backup everytime...
Click to expand...
Click to collapse
Indeed, I guess I skipped it in excitement. But hey, it worked in the end!
I'm really glad you all helped me!

[Q] need help flashing CWM on the latest 1.63.531.2 710RD mt4gs

and i went on this link below
[How To] Flash ICS ROMs with S-ON Unlocked
I'm assuming you have
•Fastboot set up as a PATH, or copied to the folder you are extracting boot.img to
•HTC Drivers installed
•Clockwork Recovery
i have the drivers installed but i dont know the path and its not giving me details and to make it easyier to me i put everything on my desktop so please help me out here cause im about to sell this device and buy myself a g2 or g2x or a samsung android phone i really like bulletproof rom installed bad all i need for help is get CWM on this phone then i can handle it from there thanks.
you can download rom manager from play and install cwm
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You at least have to be unlocked and rooted. You're obviously not rooted, yet.
see
you see i got the bootloader unlocked but still have s-on and the other thread says i can still flash custom rom with s-on still on but you still need to flash cwm on it and its not letting me
crimedave1987 said:
you see i got the bootloader unlocked but still have s-on and the other thread says i can still flash custom rom with s-on still on but you still need to flash cwm on it and its not letting me
Click to expand...
Click to collapse
Have you pushed Superuser from a PC to the phone via USB? After that you can load CWM from ROM Manager.
Hastily spouted for your befuddlement
crimedave1987 said:
you see i got the bootloader unlocked but still have s-on and the other thread says i can still flash custom rom with s-on still on but you still need to flash cwm on it and its not letting me
Click to expand...
Click to collapse
Just being unlocked is not the same as being rooted. You need to be Unlocked AND rooted to install CWM through Root Manager. You're only half of that.
Coug76 said:
Have you pushed Superuser from a PC to the phone via USB? After that you can load CWM from ROM Manager.
Hastily spouted for your befuddlement
Click to expand...
Click to collapse
nope im having trouble doing that i need help on that part
With an unlocked bootloader I simply copy the fastboot and adb files, as well as whatever recovery image I want to flash and push the recovery via fastboot... however if you aren't confident in your skills with the command prompt or fastboot there is always the all-in-one toolkit for the MT4GS that can be downloaded from its own thread in the dev forums (I don't have the link handy but it seemed to work for me on my sister's mt4gs).
I'm having trouble flashing CWM from the market as well. I've rooted (or at least I think I have) via Hasooon2000's tool and the superuser icon shows up in my drawer but when I try to run it I'm never prompted with the usual permission request, just the permission error that OP posted. I am also unable to install anything like Busybox or ROM Toolbox. It seems like the root just wasn't properly set up but none of the methods I've found actually work. I have tried to redo the rooting process, but to no avail.
I flashed CWM from Hasoon200's tool too, and can boot into it, however when I try to take a backup it just goes to a screen with the CWM logo in it and doesn't do anything. I have to pull the battery to get it to reboot.
Never had this much trouble with rooting or flashing a recovery before, but if anyone can help I'd appreciate it.
I'd say do a flash of CWM via adb. Then install Superuser through CWM using a zipped Superuser. Worked flawlessly for me.
yupThisIsMyName said:
I'm having trouble flashing CWM from the market as well. I've rooted (or at least I think I have) via Hasooon2000's tool and the superuser icon shows up in my drawer but when I try to run it I'm never prompted with the usual permission request, just the permission error that OP posted.
I flashed CWM from Hasoon200's tool too, and can boot into it, however when I try to take a backup it just goes to a screen with the CWM logo in it and doesn't do anything. I have to pull the battery to get it to reboot.
Never had this much trouble with rooting or flashing a recovery before, but if anyone can help I'd appreciate it.
Click to expand...
Click to collapse
Are you using the trackpad to select things in recovery? All of my other phones used power while in recovery to select things but the doubleshot uses trackpad to select
Sent from my myTouch_4G_Slide using Tapatalk 2
I'm of two different schools of thought here - my first thought is bad download of CWM... Honestly I'd just read up on fastboot flashing the recovery image and do that to ensure a good root. However as noted above the trackpad select did throw me off at first.
Sent from my myTouch_4G_Slide using XDA
OK, it looks like I don't actually have S-Off and I've got the newer Hboot which, from what I can tell, prevents me from using this method and the only two ways to do this seem to involve either doing some crazy stuff with wires or flashing stuff without taking a backup first. Both of these methods make me very nervous, especially since as far as I can tell there is no way to use anything like Odin or RSD Lite with this phone to restore it in case something gets messed up.
If anyone has a way I can take a backup before flashing a ROM or, better yet, has a way to restore the phone completely in case something goes awry that would be awesome.
Update: Yeah, looks like it was the trackpad thing preventing me from doing this properly. Totally bizarre considering the fact that I was able to select things just fine using the volume buttons but when I hit power (which selects on most devices), it didn't work right.
Thanks for helping me get past this hurdle everyone! Hopefully I can figure out how to get s-off.
Edit: Update - I flashed a ROM that already had root and now that works too. Good enough for now, I'll wait for a less scarey method to get S-off. I'm not about to start messing around with wires.

[GUIDE]Newbie Guide for Root/Recovery/Stock Restore etc. ATT LG G2 (LG D800)

If you have KK or LP there are two ways to get back root and custom recovery:
1) THIS IS THE EASIEST WAY.
Use stumproot app from playstore or their thread to root and then cloudyfa's Autorec app to flash twrp. You can also get autorecd800[/URL from play store (easier)
OR the harder way
2) Go back to JB d80010d (see section 4) and then follow the guide for rooting and recovery (section 2 and 3)
If you are on JB and need to upgrade to ATT kitkat use garyd9's [URL="http://forum.xda-developers.com/showthread.php?p=50882393"]method
or AndroidUser00110001's method.
These methods are almost as easy as flashing ROM and keep root and recovery intact
While the information on rooting, flashing recovery, going to stock exists in LG G2 forum, I found them scattered all over and overwhelming. The different models and different ATT firmware makes it even more confusing for newbies and so I thought we should have a ATT G2 guide. This guide is a combination of various threads in G2 forums and my rooting experience.
I will try to keep this guide up to date. Please let me know if you find something wrong or missing
THANKS: autoprime, hyelton,djrbliss, WACOMalt, PhilZ, TWRP team( DeesTroy et al), Koush, CWM, thecubed,vincom, Judge Joseph Dredd, SuperSport,bigfau. If I missed someone please let me know
Content:
1) Introduction
2) How to root
3) How to flash recovery
4) How to go back to stock (ATT Firmware)
- How to flash Official ATT KitKat
5) FAQs (ADB, Loki, Download Mode, Go to Recovery etc.)
6) Troubleshooting (unbricking)
1) Introduction:
There are many variants of LG G2. The ATT version is called LG D800. This guide is specifically for LG D800.
LG D800 ships with a custom Android Firmware that has been “enhanced” by LG and ATT.
The firmware is unrooted and has its bootloader locked meaning they designed it so that you cannot flash custom ROMS.
Fortunately, XDA’ers are very smart people and ways have been found to circumvent these “security” locks.
Before we begin we need to take care of few things.
Make sure you have drivers for your phone (http://www.lg.com/us/support-mobile/lg-D800)
Enable Developer option (General Settings -> About Phone -> Software Information and tap “Build Number” repeatedly(7-10 times) till you see a toast notification )
Enable USB debugging in developer option
2) ROOTING:
You need root privileges in your phone to run various useful apps like Titanium Backup, AdAway and install custom ROMs. Fortunately, rooting is very easy. Head over to autoprime’s thread) to download the IOroot .I have tested it (on KK). It works perfectly (LP not so sure).
thecubed also has an excellent guide on rooting with a video that you should check out.
Extract the zip into a folder. (I prefer C:\LG\ioroot). Remember this location.
Turn on USB debugging on LG D800 and connect it to your computer
Windows user double click root.bat and you will see a command screen pop up. Linux and Mac user should run the shell script ./root.sh(make sure they have proper permissions- chmod 777 should do it)
Follow the instructions on that screen. They are pretty simple.
It may ask you to disconnect the phone and turn off and then on the usb debug option and then reconnect the phone. Do so if prompted
Also keep an eye on your phone. It may prompt you with a warning. Go ahead and hit continue.
Once your phone is rooted it will give you an option of backing up EFS partition. PLEASE DO SO AND KEEP IT SOMEWHERE SAFE(dropbox etc.)
The screenshots in the "Click to Show Content" below show how ioroot process will progress
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Another advantage of ioroot is that it has adb.exe in it. So if you need to do anything adb you can do that by going to ioroot folder through your command prompt.
***THIS METHOD WILL TRIP THE LG ROOT CHECK AND VOID WARRANTY. YOU HAVE BEEN WARNED*****.
If you encounter any problem head over to FAQs and Troubleshooting section
3) RECOVERY:
To install ROM’s and Kernels you need a custom recovery. Installing custom recovery is discouraged by ATT and hence the bootloader is locked. Fortunately djrbliss has released a tool called lokithat circumvents this lock and lets us flash recoveries, ROMs etc.
WACOMalt’s guide on installing TWRP is a must read for Newbies.
Before we go ahead please make sure that your firmware version is D80010d. If you have D80010o I would recommend going back to D80010d (see “How to go back to Stock” section). While you can flash recovery on D80010o, it does not behave well and you will not be able to flash some ROMs properly.
Things needed before flashing:
Proper drivers (see section 1)
ADB. There are various ways to get it but if you used ioroot you already have it
Go to windows command prompt (cmd) and go to your ioroot folder. which in my case was C:\LG\ioroot. From there you can type adb commands
For more info on ADD and how to get it see FAQs below
To flash recovery:
Get recovery of your choice. TWRP or PhilZ CWM . As of this writing TWRP by Blastagatoris preferable.
Copy the recovery image(.img file) to your adb folder (C:\LG\ioroot in my case). The twrp file is openrecovery-twrp-2.7.6.1-g2att.img. I would rename it to recovery.img just so that it is easier to type later on.NOTE: If you have a terp zip file extract the img file from the archive to use with loki
Download loki from github(https://github.com/djrbliss/loki). Select download zip on the right side on github page.The only file you need from the zip is loki_flash from bin folder.
Copy loki_flash to your adb location (C:\LG\ioroot in my case)
Run the following commands one at a time
Code:
adb push loki_tool /data/local/tmp/loki_tool
adb push recovery.img /data/local/tmp/recovery.img
adb shell
su
cd /data/local/tmp
chmod 777 loki_tool
./loki_tool flash recovery /data/local/tmp/recovery.img
exit
adb reboot recovery
**NOTE: loki_flash HAS BEEN REPLACED WITH loki_tool. JUST A NAME CHANGE. IF YOU HAVE OLDER VERSION OF ZIP REPLACE loki_tool with loki_flash**
The final command will reboot your phone and take you to your recovery
The screenshots in the "Click to Show Content" below show how the process will look like and what would happen if you try to flash non-loki image
4) How to go back to stock (ATT Firmware)
There are many reasons to go back to stock. Restoring warranty, reverting to 80100d firmware, soft bricks or plain old nostalgia. Fortunately, LG has a tool similar to odin called LGFlashTools for D800. Unfortunately, it is not as simple as odin and you have to jump through some hoops.
SuperSport has made restoring to Stock much easier with an installer.
Go to SuperSport thread and get the installer. Install the exe file and you are good to go.
An important thing to keep in mind: There is another better tool called LG Mobile Support Tool but it is for other G2 variants and not for ATT (or Sprint)
hyelton has written an excellent guide on reverting to stock. The tools in this section are from hyelton’s guide. Please read it for more information.
Before we start:
Make sure you have the drivers (section 1)
Download the LG Flash Tool
Download the firmware LGD800AT-01-V10d-310-410-AUG-14-2013.zip and LGD800_20130904_LGFLASHv160.dll files
Extract .tot file from V10d zip
To go back to stock:
Put your phone to download mode (power off. Then press the up volume button and connect it to computer without releasing the vol up button )
Once in download mode it may install stuff. Let it do so
Then change the COM port of your phone to 41 by going to devices and selecting LG G2 (see images below). Then unplug the phone and power it off
Find a key for LG Flash Tool (google search for it) and keep it with you
Now change date of your computer to 2012 January and disconnect internet
Install LG flash tool. It will ask for key. Enter it
You will see a place for loading dll file and tot file. Go ahead load files and click OK.
DO NOT CHANGE ANY OTHER SETTING
Then click on Yellow arrow
Then put you phone on download mode again (vol up and connect to computer)
You will see activity in LG Flash Tool. Let it run. It will automatically boot your phone.
Once your phone is booted and you see your all apps etc. disconnect the phone from comp.
The screenshots in the "Click to Show Content" below show how to change port to 41 and how LG FlashTool will look like when things are going OK.
Congratulations: You are all done
5) FAQs:
Tomsgt has a thread with videos on how to root, flash roms etc. that you should check out.
a) Boot to recovery:
If you have installed recovery you will need to go to it to flash stuff. Most custom ROMs have option in power menu to go to recovery. ATT Stock does not and so there are two ways to do so.
From adb type adb reboot recovery
Power off the phone. Then press volume down+power key. Do not release till you see LG logo. Then release and again press Vol down and power button. You will see a “Factory hard reset” screen that will say press power key to confirm. Do so. It will ask again. Go ahead and press power button again. Then you will boot into recovery.
b) Boot to download Mode:
If you are on custom ROM you should see this option under Power menu.
The other way to do it is Power off phone. Then while pressing volume up button plug the phone into computer. That should bring up the download mode in the phone
c) ADB (Android Debug Bridge):
ADB lets you communicate with your phone through a command line from your computer. You can upload file, flash zips, get logs etc. through adb. For the complete guide go to http://developer.android.com/tools/help/adb.html.
To get ADB you should get the Android SDK (http://developer.android.com/sdk/index.html). It is available for Windows, Linux and Mac. Once you have installed this get the Android SDK Platform Tools (ADB is in this Tools).
Windows users can just use the adb.exe in the ioroot folder (see Introduction Section). Just go to ioroot folder location from your DOS command prompt and type adb commands.
ADB drivers should have installed once you installed the drivers I had suggested in Introduction section.
Koush has a iniversal ADB driver for windows(http://download.clockworkmod.com/test/UniversalAdbDriverSetup6.msi, https://github.com/koush/UniversalAdbDriver). You can try that if you experience driver issues.
d) LOKI:
Loki is a tool/hack made by Dan Rosenberg(djrbliss) to work around the Galaxy S4 bootloader. The tool does not unlock the bootloader but tricks it into running custom kernel. There is an excellent article explaining the hack and I encourage you to read it once. Loki was ported over to G2 and gives us the ability to flash recoveries and ROMs.
As end users you really do not need to worry too much about loki. It is the ROM developers job .
Note than any OTA by ATT may well contain fix for Loki. So DO NOT TAKE OTA.
e) Flash ROM:
PhilZ CWM: Go to “Wipe Data/ Factory Reset” and select “Clean to Install a new Rom”. Once done go back to “Install Zip” and then “choose zip from sd card”
TWRP: Similar but after factory reset you will have to do a “format system” under “mounts and storage”. I have not used twrp in a while so if this is old info please let me know
6) Troubleshooting
a)Unbricking
If you are reading this you have a problem. Your phone has become a brick. But do not despair yet as there are a few ways to unbrick your phone. Let us first determine whether it is a soft brick or a hard one.
Soft Brick: Basically it means your phone is bootlooping or showing a blank screen but you can still go to recovery/download mode. The easiest way to fix this (and determine if you have a soft vs hard brick) is turn off the phone and then press the volume up button and connect to the computer (keeping vol up pressed). If you see your phone enter download mode you are fine. Just restore to stock (see section 4 of this guide). Make sure you flash 80100d firmware.
Hard Brick: If you cannot enter download or recovery mode then you may have a hard-brick. This is not a fun situation to be in but there is a fix that may work. It involves lots of linux commands and is not for newbies but then if you are hard-bricked what have you got to lose. Head over to Partager.info's thread where he explains how @Shelnutt2 helped him unbrick his phone.
reserved
reserved
Good info here for the ATT LG G2 (LG D800), Stickied. Thank you.
Judge Joseph Dredd said:
Good info here for the ATT LG G2 (LG D800), Stickied. Thank you.
Click to expand...
Click to collapse
awesome guide! thank you for taking the time to make this. a couple things suggestions i would make in the guide. first is dont use twrp 2.6.3.2. use 2.6.3.3. it is much better. also dont use the latest philz recovery as of today. it is causing alot of issues so i would change the recommendation for recoveries to twrp 2.6.3.3.
thanks again.
edit: here is a link to 2.6.3.3. no need to loki it because it has already been loki'fied.
http://techerrata.com/browse/twrp2/g2att
freebee269 said:
awesome guide! thank you for taking the time to make this. a couple things suggestions i would make in the guide. first is dont use twrp 2.6.3.2. use 2.6.3.3. it is much better. also dont use the latest philz recovery as of today. it is causing alot of issues so i would change the recommendation for recoveries to twrp 2.6.3.3.
thanks again.
edit: here is a link to 2.6.3.3. no need to loki it because it has already been loki'fied.
http://techerrata.com/browse/twrp2/g2att
Click to expand...
Click to collapse
Thanks
The issue I had was that 2.6.3.3 was a zip and not a loki image. When I tried loki_flash I encountered issue. Hence I recommended using 2.6.3.2 and then flash whatever recovery one wants(2.6.3.3 or PhilZ). But then I was on 80100o when I did that so it could have been firmware's error and not twrp's. If you were able to loki_flash the recovery.img from 2.6.3.3 please let me know.
The PhilZ recovery I recommend above is older one (with no issues )
epapsiou said:
Thanks
The issue I had was that 2.6.3.3 was a zip and not a loki image. When I tried loki_flash I encountered issue. Hence I recommended using 2.6.3.2 and then flash whatever recovery one wants(2.6.3.3 or PhilZ). But then I was on 80100o when I did that so it could have been firmware's error and not twrp's. If you were able to loki_flash the recovery.img from 2.6.3.3 please let me know.
The PhilZ recovery I recommend above is older one (with no issues )
Click to expand...
Click to collapse
yes 10o ota update gives recoveries problems. that's why it is recommended not to do the ota. twrp 2.6.3.2 is the version that takes forever to do wipes. 2.6.3.3 is the version that fixed that and now the wipes are fast.
here is a twrp 2.6.3.3 loki'd recovery. it's for d800 though and i dont think it'd work on other models. that's why the zip files have loki inside of it with a script that loki's specifically for that device. the reason loki_flash wouldnt work for you is because you were trying to use it on a zip file and not an image file. if you would have taken the image file out of the zip file and used that then it would have worked for you. like it just did for me when i just loki'd this attached image.
at&t d800 twrp 2.6.3.3 loki'd recovery = http://d-h.st/Wmg
freebee269 said:
yes 10o ota update gives recoveries problems. that's why it is recommended not to do the ota. twrp 2.6.3.2 is the version that takes forever to do wipes. 2.6.3.3 is the version that fixed that and now the wipes are fast.
here is a twrp 2.6.3.3 loki'd recovery. it's for d800 though and i dont think it'd work on other models. that's why the zip files have loki inside of it with a script that loki's specifically for that device. the reason loki_flash wouldnt work for you is because you were trying to use it on a zip file and not an image file. if you would have taken the image file out of the zip file and used that then it would have worked for you. like it just did for me when i just loki'd this attached image.
at&t d800 twrp 2.6.3.3 loki'd recovery = http://d-h.st/Wmg
Click to expand...
Click to collapse
Thanks. OP updated
I would suggest you add that users who already have the 11o update to "downgrade" to the 11d firmware.
I had lots of problems when I restored my phone back to stock using the 11o update so started fresh from the 11d firmware.
I have 10o with the lateset twrp 2.6.3.3. are you saying that I can not flash rooms with this set up, or if i do it will not work.
irokgalaxy said:
I have 10o with the lateset twrp 2.6.3.3. are you saying that I can not flash rooms with this set up, or if i do it will not work.
Click to expand...
Click to collapse
you can. but you might have complications with the rom after you boot into it.
AndroidUser00110001 said:
I would suggest you add that users who already have the 11o update to "downgrade" to the 11d firmware.
I had lots of problems when I restored my phone back to stock using the 11o update so started fresh from the 11d firmware.
Click to expand...
Click to collapse
I had mentioned that in Introduction section. Have emphasized it now- red and bold
Thanks
epapsiou said:
I had mentioned that in Introduction section. Have emphasized it now- red and bold
Thanks
Click to expand...
Click to collapse
Ha I guess I missed it. Never did learn that lesson about reading and skimming
Nice guide!
experiencing an odd problem when restoring back to factory. of course it still fails but its not that. now when i click on software update it says phone is not registered????? wth is that? now i cant update?
Excellent Work
Thanks for this information.
I was looking for this kind of information at one place, for the new comers like me.
podagee said:
experiencing an odd problem when restoring back to factory. of course it still fails but its not that. now when i click on software update it says phone is not registered????? wth is that? now i cant update?
Click to expand...
Click to collapse
can you provide with detailed steps you followed with screenshots
epapsiou said:
can you provide with detailed steps you followed with screenshots
Click to expand...
Click to collapse
http://forum.xda-developers.com/member.php?u=5182870&tab=quotes
OP updated. Added info on un-bricking (both soft and hard)
I'm trying to return to stock... But when I go into download mode It is stuck at "Firmware Update - 0%". Any tips?
Thanks for this incredible write-up.
I'm sorry, but some of the information about twrp and ota's is out of date and confusing. I just bought a D800 2 weeks ago, and it came with the 10o firmware. I did not have to downgrade, nor do I have any issues flashing or running any roms. I followed autoprime's thread and used ioroot21, and as it is repeated over and over again in that thread, downloaded freegee from the play store and flashed the proper recovery. Simple as that.
Sent from my Dark Chocolate 4.4 G2
aaronDroid80 said:
Thanks for this incredible write-up.
I'm sorry, but some of the information about twrp and ota's is out of date and confusing. I just bought a D800 2 weeks ago, and it came with the 10o firmware. I did not have to downgrade, nor do I have any issues flashing or running any roms. I followed autoprime's thread and used ioroot21, and as it is repeated over and over again in that thread, downloaded freegee from the play store and flashed the proper recovery. Simple as that.
Sent from my Dark Chocolate 4.4 G2
Click to expand...
Click to collapse
I too have 10o firmware. Please let me know if I've to really downgrade it to 10d and then root (just trying to avoid the extra step!). Also please provide that link for rooting as well. Thanks! .

[GUIDE] Unlocking Bootloader, Rooting, and Wiretrick-Free S-OFF for Beginners

Hi all..I'm here with a noob/newbie friendly all-in-one (AIO) guide for HTC Sensation/SensationXE/Sensation 4G. These 3 brothers are identical in looks and in hardware so everything in this guide is a cross-device applicable procedure. When i was a noob i also used this method of rooting and now that i am more experienced in the Senny messing around and am an admin for an FB group for Sensation owners, so i also have made this guide for them and most people have tried and tested this. So you need not worry.
But, as in all guides, the standard disclaimer applies.
WARNING:
Your warranty is now void! I am not responsible for what you do to your device, for your SD cards gone wild, you getting fired by your boss coz the alarm app failed, thermonuclear wars, your device running away from you, scared of being bricked, or your gf/wife breaking up/divorcing with you coz you got obsessed with your seny. You are going to perform these operations at your own risk, as i also did these steps at my own risk as well before making this guide, and nothing bad happened to me following these steps.
PREREQUISITES:
Must register and sign in to htcdev.com.
Download the HTC Sensation 4G all-in-one Toolkit from here: https://drive.google.com/file/d/0B6reUIyJc-MRVUtpQ1l6cFk4eGc/edit?usp=sharing
(Optional, for those who rooted using CWM recovery.) Download 4Ext Recovery Updater.apk from here: http://4ext.net/ and place it on your SD card. For quick access, make a folder named APKs on your SD card and put all required APKs in it.
Backup all files on internal storage of your phone like contacts, messages as unlocking bootloader will factory reset your phone. Titanium Backup and similar programs are not recommended to use as this app requires root access, which we will be trying to obtain with this guide. backup your messages in message settings > backup, and your phonebook you can also backup locally in phonebook settings or you can sync them with your Gmail for auto retrieval after signing in back to your gmail.
Enable USB Debugging on your phone: Settings > Developer Options > tick USB Debugging.
Disable Fast Boot on your phone: Settings > Power/Battery > uncheck Fast Boot if you have it checked.
Take note of your phone’s Software version. If you haven’t updated your Sensation/XE/4G to ICS 4.0.3, then you should have an Hboot version of 1.18 and 1.17. Hboots 1.27 and 1.29 are on ICS 4.0.3 firmware.
Also take note whether you are S-ON or S-OFF. You can do so by booting into bootloader by pressing volume down while turning on your phone.
For S-ON devices with Gingerbread Hboot (1.17 and 1.18), you can skip the Unlocking Bootloader procedure and go over to Revolutionary.io to get your beta key and obtain S-OFF (If Revolutionary will ask you whether you want to flash recovery after obtaining S-OFF, select NO. You can flash 4ext recovery via the toolkit afterwards.
For S-OFF devices which are on Gingerbread, download this Universal Firmware from here: http://d-h.st/SuC. You will need to upgrade your firmware to 3.32/33 before you can flash any rom with a base higher than Gingerbread.
Part 1a: UNLOCKING THE BOOTLOADER (FOR S-ON USERS WHO ARE UPDATED TO ICS STOCK FIRMWARE)
NOTE:
Users who are on Gingerbread and are S-ON can skip UNLOCKING BOOTLOADER and just go over to revolutionary.io to get their beta key to obtain S-OFF then proceed to FLASH A RECOVERY on the toolkit. For those who are on GB and S-OFF by default, you can also skip this step and go on immediately to flash your recovery. (4Ext recommended).
Follow the steps on the toolkit in order, and obviously, install HTC Drivers via the toolkit before beginning any operation. This will ensure your phone will be detected by your computer.
It is not necessary to repeat the steps beginning from installing HTC drivers or anywhere. If you left off on a procedure, you can resume where you left off.
​
WARNING:
This method of rooting has been tried and tested! There are even YouTube video tutorials on how to use this toolkit and i have used this method as well back when i was still a noob looking for an easy and painless way of rooting. But whatever you do wrong I take no responsibility for bricked devices whatsoever. But I assure you that this is a noob proof way. Just follow the procedures and you should be rooted in less than 15 minutes if all goes well.​
LET'S BEGIN!
Extract the Sensation 4G toolkit you downloaded. Place it on your desktop temporarily (but make a copy on your local disk.)
Open the toolkit. You should be greeted by this screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Follow the steps starting from the left box. As you can see, it says install HTC Drivers. You need it so that your PC will recognize your phone. Obviously, you need to Install HTC Drivers first (step 1).
After the installation, if you have already registered and logged on to your HTCDev account, proceed to get your Token ID in step 3. If you did things right, you should see a CMD screen like this:
As shown on the picture, highlight / mark the block of text following this format.
NOTE:
When copying your token ID, start with this line: <<<< Identifier Token Start >>>>
And end with this line: <<<<< Identifier Token End >>>>>
[*]After this, go to “Submit Token ID” on step 4 of the toolkit. You should see the submission screen and paste the token code you copied like this:
then click 'submit'.
[*]Then go to step 5 of the toolkit to finally unlock your bootloader.
[*]After you submit your Token ID, you should receive an email containing your unlock token bin file. Go to your email account associated with your HTCDev account then download the Unlock Token bin file and place it inside the Data folder of your toolkit.
[*]Now go back to your toolkit and finally hit step 5, unlock bootloader. This is very self-explanatory and the toolkit will guide you to the final process. When you click the Unlock bootloader, your device will light up and prompt you to confirm unlock of your bootloader. Select between YES and NO using the volume keys and press power to confirm.
[*]After you confirm unlock of your bootloader, your device will be on the set up screen. Set it up and afterwards, go to your settings again to enable USB Debugging and disable Fast Boot for the rooting process.
​
​
HOORAY! YOU HAVE UNLOCKED YOUR BOOTLOADER! TIME TO ROOT YOUR DEVICE!
​PART 1b:
OBTAINING S-OFF VIA REVOLUTIONARY (FOR DEVICES CURRENTLY ON GINGERBREAD FIRMWARE AND IS S-ON WITH HBOOT 1.17-18):
Head over to revolutionary.io
Once you are at the portal, read through all the interesting stuff and scroll down to Downloads Section.
Now click on Download for Windows, Revolutionary Zip file will start downloading and a menu headed with “Beta Key” will appear, as in the picture:
Now select your operating system, device and HBOOT version. To know your HBOOT version, you must boot into bootloader by holding down volume down key while turning on your phone.
Once the download is complete, extract the zip file contents to a location on your PC of your choice. Make sure that all files are in the same folder.
Install HTC Drivers to your PC. Easiest way to obtain it is through the Sensation 4G all in one Toolkit. There is an option there to “install HTC Drivers.” You can also install HTC Sync and setup your device and then uninstall it without uninstalling the drivers.
After this, connect your phone to the computer, make sure USB debugging is ON (Settings > Developer Options > USB Debugging.)
Now double click to execute Revolutionary on your computer. You should be able to see a terminal window that will be in process of identifying serial key of your device.
Once the serial key is displayed, copy and paste it in the Serial field on the form at Revolutionary.io.
Now click on Generate Key and paste this key at the relevant position in terminal. Better type it out to avoid errors or confusions.
Now sit back and relax while your phone gains S-OFF and an unlocked rewritable NAND.
After the process is complete, Revolutionary will ask you if you want to flash recovery. Answer it with NO as we are going to use 4ext and you can flash it via the Sensation toolkit.
.
HOORAY! NOW YOU ARE S-OFF! TIME TO FLASH A RECOVERY.
​​Part 2: FLASH A CUSTOM RECOVERY AND ROOT YOUR DEVICE:
Make sure your device is connected to PC and USB Debugging enabled. Also, on the Connection type when prompted, select ‘Charge Only’ mode.
On the Toolkit, go to the right box labeled Flash a recovery. Use 4Ext recovery. If this will fail to flash, use ‘Your Own Recovery’. If you did right, it should open up a windows explorer. Go and find your CWM.zip folder and select it. The toolkit will then flash the CWM Touch recovery. After flashing your recovery, your phone should boot up. Do not disconnect it from your pc yet. After it has settled down, on your toolkit, go to the Extras box on the bottom right and select Perm Root. Nothing special here. It will just push/send the superuser app to your phone’s SD card which we will be flashing later.
After the process is done, reboot your phone while holding the volume down button. If done correctly, when the phone turns back on, you should immediately be on a white screen like this:
•Take note of whether your phone is S-ON or OFF by default. It matters. You should see it on the top of your bootloader screen, like in the picture above.​
On the bootloader menu, scroll using volume button up or down, confirm action (OK) using power. Navigate to RECOVERY and hit power. You should then be booted up to your 4Ext / CWM Recovery Touch. You should see a screen like this:
for 4Ext
for CWM recovery.
On that menu, select ‘Install zip (from SD card)’ then navigate your way and locate the superuser.zip we pushed earlier, then select it to flash it. After flashing, go back to your recovery main menu and select Reboot Phone or Reboot Now. Once your phone has booted and settled down, open your app drawer and look for Superuser app. If it’s there, then you are finally rooted!
Follow these steps if you flashed CWM and used it to flash Superuser (this is to change your recovery from CWM to 4Ext:
Now it’s time to change your recovery to 4Ext Recovery Touch. Locate your 4Ext Recovery Updater.apk on your SDcard and install it. Make sure you have an internet connection.
Open your app.
On the 4Ext Recovery Updater/Control screen, select ‘Online Install / Upgrade. It will then take you to the 4Ext.net and the 4Ext Recovery download. In some point, the app will tell you that it is detecting HTC Sensation . If it is correct, tap YES. Then it will take you to a list of versions for the 4Ext Recovery Touch. Of course, select the latest version available ( version 1.0.0.6 RC1). Once selected, download will begin immediately depending on your internet speed. Once it has downloaded the recovery, it will automatically flash it for you. No worries!
After flashing your new custom recovery, the app will ask you a question, “Is your device S-ON? Select Yes if unsure. If you are S-ON and you told the app that you are, it will automatically enable the 4Ext SmartFlash so when you install a custom rom, you won’t have to worry about flashing the kernel/boot image. It will do it for you like you were actually S-OFF.
You are now fully rooted and using the most awesome recovery for Sensation users. Take note, most custom roms require this as a recovery so do not change! And as a reminder, do a Nandroid Backup of your Stock/Current rom before trying out other roms. also, if you want to donate to the devs of this recovery, you may want to consider buying the full version of this app (4Ext Recovery Control) at the playstore. it has additional features, like the ability to flash boot image even when not connected to PC via ADB.
TO MAKE A NANDROID BACKUP:
1.Go to your recovery, select Backup / Restore > Backup (if you want to backup or restore if you want to restore a nandroid backup
REMINDER / RULE OF THUMB:
Before flashing any rom or restoring a backed up ROM, always perform full wipe to ensure a clean install/ restore. On your recovery, go to WIPE / FORMAT and select FORMAT ALL PARTITIONS EXCEPT SD CARD.
​
Part 3: HTC Sensation: S-OFF with Rumrunner Method.​
You Need:​
an HTC Sensation
o Sensation XE and Sensation 4G will work, too
 device ***LOCKED***: download the temproot package from https://www.dropbox.com/s/0xljdqkw9w6jien/temproot-sensation-windows.zip
 device ***UNLOCKED***: no need to download
supported bootloader versions: 1.27.0000 and 1.29.0000.
1.18.0000 and below will not work-For these cases, if you want a wiretrick-free s-off method there’s the Revolutionary S-off at revolutionary.io.
o stock ROM will work. Some custom ROMs are fine, too (tested: ViperS 5.1.0)
o make sure ADB works with your ROM (will always work with stock ROM, problems may occur with CyanogenMod).
o make sure your battery is fully charged.
an original HTC USB cable or a similar cable which you know that ADB/fastboot works with (tested with a Samsung cable).
a Personal Computer with Windows 2000 or higher. Please note that problems may occur when using Windows 8.
the HTC driver package, downloadable from https://www.dropbox.com/s/lq5uv4xqe3rnufz/drivers.exe
the official HTC Universal rumrunner package, downloadable from http://rumrunner.us/downloads-2/
the PG58IMG.zip file containing the 3.33 Universal firmware package (including HBOOT patched by revolutionary) downloadable from http://d-h.st/SuC
Preparation
Make sure HTC Sync is uninstalled on your PC. Install the HTC drivers that you downloaded before.
Disable all security such as antivirus and firewall (re-enable them after the operation), auto-shutdown or auto-hibernate modes on your PC.
Make sure no applications which have access to USB ports are installed on your PC, e.g. MyPhoneExplorer, ODIN, PDAnet, etc.
Unzip the rumrunner and, if needed, the temproot package.
Take the SIM card out of your phone. Backup all content of your SD card to your PC and then format your SD card to FAT32, or if you have a spare SD card, you can use it during the process to save you some time backing up the contents of the SD card you are currently using.
Enable USB debugging in the developer options of your device.
Disable the fast boot option (if you use a stock or Sense-based ROM) in the device options.
Deactivate the SIM PIN prompt.
Deactivate all kinds of password locks, such as FaceLock, unlock pattern etc.
Reboot your phone, connect it to your PC and set “charge only” as the connection type (for stock rom users).
Let’s go for S-OFF
If your phone is on STOCK ICS and ***LOCKED***, execute temp_root.bat from the extracted temproot folder. Your HTC Sensation will restart a few times and the Sense interface will not be shown anymore. Looks like a soft brick, but is not (don’t panic!). After some time, the tool will report temproot success.
If your phone is ***UNLOCKED***, this step must not be performed.
Execute soju.exe from the rumrunner folder. Confirm the security questions and let the tool operate. Your phone must be on standby/booted to your rom, as the tool will try to detect your current ROM. Do not, under any circumstances, move or even touch your phone!
Your phone may reboot a few times while the operation is on going. Don't panic. pay attention to when your phone reboots. If you finally see a black screen with the green HTC Logo during booting up, that means you are S-OFF and the tool is on the final phase of the operation. Wait patiently. After the rumrunner tool has completed the operation, you can now unplug your device.
OPTIONAL;
if you ever encounter problems, you can try flashing the universal firmware i provided in this guide to patch your Hboot version.
After S-OFF has been achieved successfully, move the downloaded PG58IMG.zip to the root directory of your SD card (that means, not into any folder!).
Boot into bootloader. When you’re asked if you want to flash the new firmware, confirm. After that, reboot your phone and delete the ZIP file from your SD card.
Congratulations! You have R/W permissions on all substantial partitions (including /radio, /splash1 etc.). You can now set the SuperCID or flash a new RADIO if you want. It is highly recommended to re-flash 4EXT recovery and to disable SmartFlash.
CREDITS:
• @ganeshp for being a nice person and a database of information for me. He is very helpful on my FB group for Sensation users.
• @hasoon2000 for his awesome HTC AIO toolkit. This toolkit also helped me root my device back when I was still a noob.
• @sixline for offering to help me with my guide. he volunteered to help me review these write ups.
•For the developers of the rumrunner tool. You guys rock! Now people who are not confident of the wire-trick S-OFF like me will have an alternative way.
•All other xda members I may have forgotten.​
Hi nice guide. U should post the link to the Free 4ext recovery updater app not 4ext control as u need to pay for it
oh..sorry.
jmcclue said:
Hi nice guide. U should post the link to the Free 4ext recovery updater app not 4ext control as u need to pay for it
Click to expand...
Click to collapse
oh..sorry bro. i know i have violated xda rules as apps outside playstore are considered warez here. the only reason i posted that is because as i believe, you cannot update to the latest version of the recovery if you use the free version. but ok..i will revise the link.
EDIT: i searched at the playstore. the free version of 4ext is no longer there.
EDIT 2: found it on the 4Ext site.
ichigo_kurosaki said:
oh..sorry bro. i know i have violated xda rules as apps outside playstore are considered warez here. the only reason i posted that is because as i believe, you cannot update to the latest version of the recovery if you use the free version. but ok..i will revise the link.
EDIT: i searched at the playstore. the free version of 4ext is no longer there.
EDIT 2: found it on the 4Ext site.
Click to expand...
Click to collapse
Haha was just gona post the link. Yh u can update to the latest recovery using the free app. Also u could just post the recovery.img here in ur op so people can just flash it via fastboot.
jmcclue said:
Haha was just gona post the link. Yh u can update to the latest recovery using the free app. Also u could just post the recovery.img here in ur op so people can just flash it via fastboot.
Click to expand...
Click to collapse
Good idea. But i think i have the updated recovery image included on the hasoon toolkit. I updated the 4ext recovery there and recompressed the folder for uplnading to my drive.
Sent from my HTCSensation using XDA Premium 4 mobile app
awesome guide:good:
one question
in Part 2: ROOT YOUR DEVICE why did you put a bootloader's screenshot from another device and not from sensation device?
rzr86 said:
awesome guide:good:
one question
in Part 2: ROOT YOUR DEVICE why did you put a bootloader's screenshot from another device and not from sensation device?
Click to expand...
Click to collapse
You are right rzr86 , maybe someone will be confuzed with hboot 1.25 and other things
nah..
rzr86 said:
awesome guide:good:
one question
in Part 2: ROOT YOUR DEVICE why did you put a bootloader's screenshot from another device and not from sensation device?
Click to expand...
Click to collapse
just a sample..coz i had trouble looking for seny bootloader screens on google. will try to change that.: as i said on my note, this guide still needs to be updated as i will include guide for rumrunner S-OFF. we all know there is already an existing guide for it, but i felt the need to make one for Seny users as not so many know this yet and i want to share some side notes. thanks for the feedback.
Very well written guide, thanks al lot!
Nice guide. Thanks for giving me a lot of useful info on just a few printed pages.
Hey ichigo, I tried to use this guide on my friend's Sensation XE with HBOOT 1.29 and Locked. First of all, the all in one toolkit included is not working. I had to download it from another link. Then at the end when using rumrunner, I got an error saying that I have to upgrade my kernel to jb one. Now, I am in progress of downloading viper rom (http://forum.xda-developers.com/showthread.php?t=2531054). Will update if it works.
sixline said:
Hey ichigo, I tried to use this guide on my friend's Sensation XE with HBOOT 1.29 and Locked. First of all, the all in one toolkit included is not working. I had to download it from another link. Then at the end when using rumrunner, I got an error saying that I have to upgrade my kernel to jb one. Now, I am in progress of downloading viper rom (http://forum.xda-developers.com/showthread.php?t=2531054). Will update if it works.
Click to expand...
Click to collapse
you need to use first the temproot bat.file and then use the rumrunner tool
some other user succeeded with ics kernel
http://forum.xda-developers.com/showpost.php?p=53570038&postcount=50
rzr86 said:
you need to use first the temproot bat.file and then use the rumrunner tool
some other user succeeded with ics kernel
http://forum.xda-developers.com/showpost.php?p=53570038&postcount=50
Click to expand...
Click to collapse
Yes it is already.said that for ***LOCKED*** devices tempront is required. Somehow many are having trouble with doing the rumrunner on.stock and locked..i did mine on viperS5.1.0 so i never ran into.problems.
Edit: i didn't write that part in.rumrunner guide. That was written by a (former) fellow admin on my htc seny fb group. i had complete trust coz he was very knowlegeable. So.i never revised his part. If i knew this was gonna happen.i'd.have.suggested to unlock device first..sorry.bro.
sixline said:
Hey ichigo, I tried to use this guide on my friend's Sensation XE with HBOOT 1.29 and Locked. First of all, the all in one toolkit included is not working. I had to download it from another link. Then at the end when using rumrunner, I got an error saying that I have to upgrade my kernel to jb one. Now, I am in progress of downloading viper rom (http://forum.xda-developers.com/showthread.php?t=2531054). Will update if it works.
Click to expand...
Click to collapse
Sent from my HTCSensation using XDA Premium 4 mobile app
If the step 1 of the part 3.guide caused.a mess then.perhaps i should omit that and.instead will strongly advise to.unlock first. What you say rzr86? and did i miss telling to use temproot for locked devices?
Sent from my HTCSensation using XDA Premium 4 mobile app
ichigo_kurosaki said:
If the step 1 of the part 3.guide caused.a mess then.perhaps i should omit that and.instead will strongly advise to.unlock first. What you say rzr86? and did i miss telling to use temproot for locked devices?
Sent from my HTCSensation using XDA Premium 4 mobile app
Click to expand...
Click to collapse
no i am just telling that one user succeded using rumrunner in completely stock situation
that's why i post the link too
the only thing you have to do is run the temproot.bat file first
edit: no you didn't forget to mention temproot for locked devices
Yeah after flashing Viper rom, my device is s-off without hassle. Also, in the last step, why should one use the PG58IMG.zip?? The included zip is not working and I am using my device without flashing it..
sixline said:
Yeah after flashing Viper rom, my device is s-off without hassle. Also, in the last step, why should one use the PG58IMG.zip?? The included zip is not working and I am using my device without flashing it..
Click to expand...
Click to collapse
it is patched firmware with patched hboot version
it is not necessary only optional
rzr86 said:
you need to use first the temproot bat.file and then use the rumrunner tool
some other user succeeded with ics kernel
http://forum.xda-developers.com/showpost.php?p=53570038&postcount=50
Click to expand...
Click to collapse
Well any device should be unlocked after 1st step so temp root not needed???
sixline said:
Well any device should be unlocked after 1st step so temp root not needed???
Click to expand...
Click to collapse
probably if the device is unlocked but not rooted you will still need the temproot but i am not sure for that
rzr86 said:
probably if the device is unlocked but not rooted you will still need the temproot but i am not sure for that
Click to expand...
Click to collapse
Yes probably stock and unlocked still needs the temproot i suppose since executing the rumrunner requires you to be rooted. So temproot does that for us. Well thanks for the tips guys. I will do some minor revisions to.part 3. As i said earlier i didn't write that part based on my own experience.
EDIT: perhaps i should atleast include the step for doing the temproot correctly from the Joupunutbear thread.
EDIT 2: @sixline: you say that the toolkit on my drive didn't work? I will check on it when i get to my laptop at the office today. If it is indead a corrupted upload then i will reupload it.
Sent from my HTCSensation using XDA Premium 4 mobile app

Starting from stock 4.2.2 UK Tab 2 p5110

Hi guys,
Apologies first of all as I'm sure this has been asked over and over again but I'm still struggling to find a concrete route/guide to running custom roms starting from a stock device (Tab 2 10" P5110 JB 4.2.2).
As far as I understood I should do the following:
1. Install CF-Autoroot - However on CF website I read:
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Do I need to worry about the above or can I proceed to install the CF-autoroot via Odin?
2. Install custom recovery as above method leaves with stock recovery - Question here is what is the best way to proceed at this point? Install recovery via rom manager or another method (PC Odin etc) ?
3. Install custom rom and enjoy and improved device
Please if someone could clarify the steps I need to take (exact file versions etc) from a fully stock 10" Tab 2 running 4.2.2 it would be greatly appreciated. Or link me to what I'm after in case I've missed this!
All the best,
GalaxyDude
(Happy Christmas all!)
Galaxydude1 said:
Hi guys,
Apologies first of all as I'm sure this has been asked over and over again but I'm still struggling to find a concrete route/guide to running custom roms starting from a stock device (Tab 2 10" P5110 JB 4.2.2).
As far as I understood I should do the following:
1. Install CF-Autoroot - However on CF website I read:
If you have locked bootloaders, flashing one of these will probably brick your device - with the exception of Nexus devices, which will usually automatically "OEM unlock" and wipe your data !
Do I need to worry about the above or can I proceed to install the CF-autoroot via Odin?
2. Install custom recovery as above method leaves with stock recovery - Question here is what is the best way to proceed at this point? Install recovery via rom manager or another method (PC Odin etc) ?
3. Install custom rom and enjoy and improved device
Click to expand...
Click to collapse
1st, it will only root your mobile, if your purpose is to stay on stock and just delete the bloat wares. and run modded apps. you're good to go
http://forum.xda-developers.com/showthread.php?t=1957165
http://forum.xda-developers.com/showthread.php?t=2203309
just check you're using the file meant for your device only. this thread has a detailed view. and no, its safe as long as you're using the files meant exactly for your device.
2nd installing a custom recovery is the first choice and the best and smartest thing to do, cause if after rooting you did something stupid with the system files, then all your data might be lost, custom recovery helps you keep complete nandroid backup of your device which means almost everything is backed up (except media and external memory card), lets you flash custom rom and in case anything goes wrong, you access the custom recovery and bam, restore your backup, and you're back at the original state. or flash your new custom rom
3. yes install a custom rom after you backup your stock factory rom.
remember taking backup at every step from here on onward is the first rule.
good luck and have fun on xda
Hi Billysam,
Thanks for the speedy reply
I'm aiming to eventually run a nice custom rom but just want to get the rooting and custom firmware down first so as you mention I can do a full nandroid backup before moving on.
I had a look at the link you posted but you're right that leaves you with stock recovery which would be fine if I wasn't going to install a custom rom.
I found http://forum.xda-developers.com/showthread.php?t=1722745
So now I've got:
Odin 3.0.7
philz_touch_5.03.7-p5110.tar.md5
Superuser-3.1.3-arm-signed.zip
Was going to install the above via Odin and then do a full backup, does that sound about right?
Cheers again!
Galaxydude1
Galaxydude1 said:
Hi Billysam,
Thanks for the speedy reply
I'm aiming to eventually run a nice custom rom but just want to get the rooting and custom firmware down first so as you mention I can do a full nandroid backup before moving on.
I had a look at the link you posted but you're right that leaves you with stock recovery which would be fine if I wasn't going to install a custom rom.
I found http://forum.xda-developers.com/showthread.php?t=1722745
So now I've got:
Odin 3.0.7
philz_touch_5.03.7-p5110.tar.md5
Superuser-3.1.3-arm-signed.zip
Was going to install the above via Odin and then do a full backup, does that sound about right?
Cheers again!
Galaxydude1
Click to expand...
Click to collapse
Philz recovery is fine, but some custom roms requires twrp recovery, both are good. check which rom you're going to try and see if it says needs twrp, download that, if not philz is safe too and it's not much hard to switch.
Superuser app, you won't need unless the custom rom you're going to install doesn't have one already. most do. just get custom recovery installed, find a good custom rom, for your device, read instructions and other members who already tried it. don't rush. backup first.
small note- please click reply and then type your msg, it will quote and send me a notification as well. if you don't quote or don't hit thinks, I might not even get notified and see your msg. cheers
billysam said:
Philz recovery is fine, but some custom roms requires twrp recovery, both are good. check which rom you're going to try and see if it says needs twrp, download that, if not philz is safe too and it's not much hard to switch.
Superuser app, you won't need unless the custom rom you're going to install doesn't have one already. most do. just get custom recovery installed, find a good custom rom, for your device, read instructions and other members who already tried it. don't rush. backup first.
small note- please click reply and then type your msg, it will quote and send me a notification as well. if you don't quote or don't hit thinks, I might not even get notified and see your msg. cheers
Click to expand...
Click to collapse
No problem at all, I'd actually deleted the requote to save spam as I assumed you'd be notified auto as you'd contributed
Thanks for the info, on the back of what you've said I think I'll put on PhilsRecovery as I've got it downloaded for my specific model, do a full backup and then can I use Rom manager to install TWRP via the app?
Kind regards,
Galaxydude1
Galaxydude1 said:
Thanks for the info, on the back of what you've said I think I'll put on PhilsRecovery as I've got it downloaded for my specific model, do a full backup and then can I use Rom manager to install TWRP via the app?
Click to expand...
Click to collapse
Yes, go with that. and you can change to twrp with rom manager. but most of the custom rom threads have the recoveries mentioned there and most of the time you will find updated once here on the page. check this page
http://forum.xda-developers.com/galaxy-tab-2/10-inch-development
this is the place you will find all custom roms for your device and updated information. wherever you see P51xx , that rom works for your device as well.
billysam said:
Yes, go with that. and you can change to twrp with rom manager. but most of the custom rom threads have the recoveries mentioned there and most of the time you will find updated once here on the page. check this page
http://forum.xda-developers.com/galaxy-tab-2/10-inch-development
this is the place you will find all custom roms for your device and updated information. wherever you see P51xx , that rom works for your device as well.
Click to expand...
Click to collapse
Thanks for your advice :good:
One thing I just realised though is if you have to be rooted in order to do a full nandroid backup I'll need to flash the recovery with Odin and then install the superuser file zip from recovery before the backup will work.
Am I right in thinking the above?
Cheers again.
Galaxydude1 said:
Thanks for your advice :good:
One thing I just realised though is if you have to be rooted in order to do a full nandroid backup I'll need to flash the recovery with Odin and then install the superuser file zip from recovery before the backup will work.
Am I right in thinking the above?
Cheers again.
Click to expand...
Click to collapse
Get into recovery first and try to backup if it does, you're fine, if it doesn't you can flash superuser zip inside recovery and try then backup.
it's not that risky.
billysam said:
Get into recovery first and try to backup if it does, you're fine, if it doesn't you can flash superuser zip inside recovery and try then backup.
it's not that risky.
Click to expand...
Click to collapse
I just gave it a try but looks like some driver issue going on with PC (Windows 10):
http://imgur.com/5RKLSp6
Just hangs when trying to install drivers (have latest Samsung USB drivers installed) and I've checked and Kies wasn't running, going to try on my Windows 7 PC and see if it's any better. Is there anything else I need installed I'm missing? Should have ADB stuff installed as recently used this laptop to connect to Fire TV.
Will keep thread updated.
Thanks again,
Galaxydude.
Galaxydude1 said:
I just gave it a try but looks like some driver issue going on with PC (Windows 10):
http://imgur.com/5RKLSp6
Just hangs when trying to install drivers (have latest Samsung USB drivers installed) and I've checked and Kies wasn't running, going to try on my Windows 7 PC and see if it's any better. Is there anything else I need installed I'm missing? Should have ADB stuff installed as recently used this laptop to connect to Fire TV.
Will keep thread updated.
Thanks again,
Galaxydude.
Click to expand...
Click to collapse
it shows device connected at com3 in odin. if its blue and shows com3 or any other com, you're connected so the drivers are good, have you enabled usb debugging in settings? if not enable it.
it's getting hanged at installing drivers or is it trying to get update from the internet? might be issue with windows 10. check on windows 7
billysam said:
it shows device connected at com3 in odin. if its blue and shows com3 or any other com, you're connected so the drivers are good, have you enabled usb debugging in settings? if not enable it.
it's getting hanged at installing drivers or is it trying to get update from the internet? might be issue with windows 10. check on windows 7
Click to expand...
Click to collapse
Yeah I managed to get the drivers to install out of download mode but I'm still getting a blue com with it connected and usb debugging enabled.
Going to try on W7 later and post what happens.
All the best.
billysam said:
it shows device connected at com3 in odin. if its blue and shows com3 or any other com, you're connected so the drivers are good, have you enabled usb debugging in settings? if not enable it.
it's getting hanged at installing drivers or is it trying to get update from the internet? might be issue with windows 10. check on windows 7
Click to expand...
Click to collapse
So after reading multiple posts of people saying the blue com status was the same as yellow (different due to software version) I decided to go ahead and try CF-Autoroot with my Tab 2 4.2.2 JB stock and this was SUCCESSFUL:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://imgur.com/VQxjInS
So for those of you wondering if it will work on latest stock firmware it does
Now I'm going to try get a custom recovery installed so I can do a full nandroid backup before I play with any roms.
Thanks all!
Galaxydude1

Categories

Resources