Database Develop

Galaxy Tab 10.1 Rooted

Samsung Galaxy Tab 10.1 is rooted.
Instructions
1. Download the tool from below attachments:
2. Commands to type:
adb push Rooting-Samsung-Galaxy-Tab-10.1.zip /sdcard/Rooting-Samsung-Galaxy-Tab-10.1.zip
adb reboot recovery
3. Enjoy Samsung Galaxy Tab 10.1 as rooted
Complete Tutorial at http://www.techofweb.com/technology/rooting-galaxy-tablet-10-1.html
Credits
I am posting this thread here as initially I posted it in wrong Thread in Samsung Salaxy Tab Android Development Forum sorry for that

10.1 or 10.1v?
Is this a guide to root the 10.1 or he 10.1v?
I hope iets for 10.1v.

Rodus said:
Is this a guide to root the 10.1 or he 10.1v?
I hope iets for 10.1v.
Click to expand...
Click to collapse
i have the same question

10.1 the 10.1v currently can't boot into recovery.
Sent from my GT-P7100 using XDA Premium App

Already covered here

johnblade said:
i have the same question
Click to expand...
Click to collapse
its for 10.1

I fallowed the instruction and got root, however I could not get titanium backup to work. It just says no root and busy box, help please

Thanks so much! This worked great on the Google i/O version.
Question. I'm on a Mac... any way to make this thing so when I plug it into the Mac that it pops up as a USB drive? My Inspire 4G does it, but this one doesn't, so I can't for the life of me figure out how to transfer files to it without using a windows machine.
Also, is it really incapable of charging off the USB port? It'll only charge if I plug it into the wall socket. Weird.

So I just got my gtab and wanted to know is there a file named "sdcard" already on the system? Or will it make one when you push it,,,otherwise how does it know where to go when you push it to the sdcard?
techofweb said:
Samsung Galaxy Tab 10.1 is rooted.
Instructions
1. Download the tool from below attachments:
2. Commands to type:
adb push Rooting-Samsung-Galaxy-Tab-10.1.zip /sdcard/Rooting-Samsung-Galaxy-Tab-10.1.zip
adb reboot recovery
3. Enjoy Samsung Galaxy Tab 10.1 as rooted
Complete Tutorial at http://www.techofweb.com/technology/rooting-galaxy-tablet-10-1.html
Credits
I am posting this thread here as initially I posted it in wrong Thread in Samsung Salaxy Tab Android Development Forum sorry for that
Click to expand...
Click to collapse

camblue said:
So I just got my gtab and wanted to know is there a file named "sdcard" already on the system? Or will it make one when you push it,,,otherwise how does it know where to go when you push it to the sdcard?
Click to expand...
Click to collapse
sdcard is already "pre-installed" (if you will) on the system. The 32gb hdd space is essentially our SDcard on the 10.1 Tab. So yes. There is already a /sdcard/ file on your system.

Used the techniques and files here to get my tab rooted - everything works well. Now we just need to get more devs to do some roms on the vanilla version...Really looking forward to how HC 3.1 will run on the I/O versions...

my 10.1 doesn't load into recovery. I just get a battery loading once i type in adb reboot recovery...
anyone can help me please
my galaxy tab was just picked up today from the BEST BUY release in NYC.
thanks in advance

wrxphantom said:
my 10.1 doesn't load into recovery. I just get a battery loading once i type in adb reboot recovery...
anyone can help me please
my galaxy tab was just picked up today from the BEST BUY release in NYC.
thanks in advance
Click to expand...
Click to collapse
I'm guessing that the same root method for the I/O tab (running 3.0) will not work on the release tab (running 3.1).

wrxphantom said:
my 10.1 doesn't load into recovery. I just get a battery loading once i type in adb reboot recovery...
anyone can help me please
my galaxy tab was just picked up today from the BEST BUY release in NYC.
thanks in advance
Click to expand...
Click to collapse
See this thread: http://forum.xda-developers.com/showthread.php?p=14551458
If someone could tell you how to post a system dump, would you be willing to do it? I don't know how, but I'd be glad to help you figure it out or to try to recruit someone who knows how to do it.
EDIT: here is a general idea of how it is done for another device.
http://android.modaco.com/content/a...-dump-system-and-boot-from-a-standard-device/
BTW, it sounds like the best time to do this dump is before making any changes to the device.

someone can correct me if I'm wrong but I don't think you can make a system dump without having root access

some observations.
no fastboot, recovery wont mount data (so sdcard is not avail.).
working on dumping.

pershoot said:
some observations.
no fastboot, recovery wont mount data (so sdcard is not avail.).
working on dumping.
Click to expand...
Click to collapse
the retail feels heavier then the IO edition. they may have added something to it.
anywhoo, im trying to take a proper system dump (either by gaining root or other misc avenue with elevated permissions).
just for kicks i took a quickie sys dump as 'shell', with the errors from having reduced perms. no boot (expected).
ill keep you all updated.

pershoot said:
the retail feels heavier then the IO edition. they may have added something to it.
anywhoo, im trying to take a proper system dump (either by gaining root or other misc avenue with elevated permissions).
just for kicks i took a quickie sys dump as 'shell', with the errors from having reduced perms. no boot (expected).
ill keep you all updated.
Click to expand...
Click to collapse
great to know you're working on it. keep it up!

pershoot said:
the retail feels heavier then the IO edition. they may have added something to it.
anywhoo, im trying to take a proper system dump (either by gaining root or other misc avenue with elevated permissions).
just for kicks i took a quickie sys dump as 'shell', with the errors from having reduced perms. no boot (expected).
ill keep you all updated.
Click to expand...
Click to collapse
tried flashing through odin. wouldn't take (all was healthy and passed though prior to flash).
investigating why it didnt flash.
they really locked this thing down didn't they!

We're kind of split between two threads, so I'm arbitrarily choosing this one.
Pershoot: Let's get this thing cracked. Can you grab an "adb shell mount" output for me? I'm curious as to how that compares to the I/O model. If there's a partitioning difference, that's going to be another hurdle.

[Q] ICS Update for Nexus One

Hi,
My Nexus One details are as follows:
Model number : Nexus One
Android version : 2.3.4
Baseband version : 32.50.00.32U_5.12.00.08
Kernel version : 2.6.35.7-ge0fb012
[email protected] #1
Build number : GRJ22
Which is the best way for me to update my phone to ICS (Android 4.0). I have read the official message from Google on categorizing Nexus One as "old" and will no more air the updates.
I am not familiar with the MODs and so; eventhough I scanned through the ROM section; I couldn't figure out myself which way should I opt to upgrade my phone.
Thanks to all for reading my request as it might be a thousandth time such a request is coming through. Thanks for your patience and your advise is eagerly awaited.
Jabir
PS: I have never done a "jailbreak" or "rooting" (whatever name is it) on my phone except those Google aired updates.

You are going to have to root--no way around it
I did it the old fashion way and installed sdk/fastboot oem unlock/flash recovery and a rom with super user in it or flash super user
instructions are in Wiki
there are different ways now I am not familiar with, but prefer the sdk method
you will also need to be on hboot 35.0017 to install blasckrose, although some ICS roms have a miniversion that can run on stock hboot
However, I would root and flash some roms like CM7 stable to get use to things. The hboot and ICS is a bit more complicated at first--read the threads carefully before attempting

Start reading.
http://forum.xda-developers.com/showthread.php?t=1366897

ursJAR said:
Hi,
My Nexus One details are as follows:
Model number : Nexus One
Android version : 2.3.4
Baseband version : 32.50.00.32U_5.12.00.08
Kernel version : 2.6.35.7-ge0fb012
[email protected] #1
Build number : GRJ22
Which is the best way for me to update my phone to ICS (Android 4.0). I have read the official message from Google on categorizing Nexus One as "old" and will no more air the updates.
I am not familiar with the MODs and so; eventhough I scanned through the ROM section; I couldn't figure out myself which way should I opt to upgrade my phone.
Thanks to all for reading my request as it might be a thousandth time such a request is coming through. Thanks for your patience and your advise is eagerly awaited.
Jabir
PS: I have never done a "jailbreak" or "rooting" (whatever name is it) on my phone except those Google aired updates.
Click to expand...
Click to collapse
0. Set up ADB correctly.
1. Root.
2. Optional: Unlock the bootloader
3. Optional: Set SecuFlag off, i.e. S-OFF
4. Fastboot flash a custom recovery
5. Fastboot flash blackrose's hboot. Either stock blackrose or the one specifically for ICS (custom partition layout)
6. Download an ICS ROM of your choosing. My pick would be texasice's.
7. Download an A2SD script as the default one is a li'l buggy.
8. Boot into the recovery of your choosing (4EXT or AmonRa preferred)
9. Make a FULL wipe of settings and partitions and wipe cache and dalvik cache.
10. Flash the ROM zip file
11. Flash the A2SD script file
12. Reboot and boot up your phone. Enter a terminal emulator. Type: su
13. Accept the root request and then type a2sd install,
14. Let your phone reboot on its own and then boot it up again,
15. Return to the terminal emulator, type su and then a2sd cachesd and let it reboot once more.
16. Now you're good to go.
Find out all info on your own, I simply tell you what you need to do.

Theshawty said:
0. Set up ADB correctly.
1. Root.
2. Optional: Unlock the bootloader
3. Optional: Set SecuFlag off, i.e. S-OFF
4. Fastboot flash a custom recovery
Click to expand...
Click to collapse
If you are going to be using fastboot to flash a custom recovery, root is not needed and unlocking the bootloader is not Optional. Root is only needed if you are going to flash the recovery through Android with a program like ROM Manager. Also, S-Off also is something we can't officially get with our phones without using the XTC Clip. But for pretty much all things that we need to do with our phones, S-Off is not required due to it being a dev phone.

As a matter of fact, unlocking the bootloader is actually completely optional, and unless you are doing hardcore modding, completely unnecessary - not to mention that it is the definitive method to losing your warranty. Root, on the other hand, is completely reversible and virtually undetectable if you restore to a stock ROM if you ever need warranty service.
I only started modding recently (a month ago) and in that time, I've already moved to ICS and using a custom Blackrose HBOOT. Its fairly easy - you just have to have the ability to read patiently.
Here is what I would advise, being a bit of a noob myself - yet having never had a single hiccup. This is pretty much the fastest way to do it.
1. Enable USB debugging (in settings>applications>development)
2. Download SuperOneClick (Google it, also has USB drivers if necessary)
3. Connect your phone to the computer, and once all drivers are installed, fire up SuperOneClick, hit 'Root' and watch the magic unfold
4. Download ROM Manager from the Market, follow the instructions (Flash recovery>Download a ROM (CM7 recommended))
Once you are familiar with the basics of installing a ROM from ZIP, head over to the Dev forums, and download ICS for stock HBOOT to get you started!

mrhohoha said:
As a matter of fact, unlocking the bootloader is actually completely optional, and unless you are doing hardcore modding, completely unnecessary - not to mention that it is the definitive method to losing your warranty. Root, on the other hand, is completely reversible and virtually undetectable if you restore to a stock ROM if you ever need warranty service.
Click to expand...
Click to collapse
This is true. I was just going off the instructions that Theshawty wrote. In the instructions he included directions to use fastboot. And without replacing the bootloader to Blackrose (which is probably too in depth to do include here), using fastboot would require the bootloader to be unlocked.

bassmadrigal said:
If you are going to be using fastboot to flash a custom recovery, root is not needed and unlocking the bootloader is not Optional. Root is only needed if you are going to flash the recovery through Android with a program like ROM Manager. Also, S-Off also is something we can't officially get with our phones without using the XTC Clip. But for pretty much all things that we need to do with our phones, S-Off is not required due to it being a dev phone.
Click to expand...
Click to collapse
I have S-OFF'd my device and I didn't use anything called XTC Clip?

Yep. Nothing special required for S-OFF. Heck, you can S-OFF in like 20 seconds by just installing Blackrose! And revert to stock S-ON HBOOT whenever you like!

Using Blackrose does not actually make your device S-Off. The upgraded HBOOT just ignores the flag that is set saying the S-On is still there and displays that you are S-Off. And so, essentially you have S-Off when you use blackrose, but that is only because blackrose ignores the actual setting saying the S-On is still in place. The one thing this will not allow is relocking the bootloader, which full S-Off, when acheived with the XTC Clip, will do.

mrhohoha said:
As a matter of fact, unlocking the bootloader is actually completely optional, and unless you are doing hardcore modding, completely unnecessary - not to mention that it is the definitive method to losing your warranty. Root, on the other hand, is completely reversible and virtually undetectable if you restore to a stock ROM if you ever need warranty service.
I only started modding recently (a month ago) and in that time, I've already moved to ICS and using a custom Blackrose HBOOT. Its fairly easy - you just have to have the ability to read patiently.
Here is what I would advise, being a bit of a noob myself - yet having never had a single hiccup. This is pretty much the fastest way to do it.
1. Enable USB debugging (in settings>applications>development)
2. Download SuperOneClick (Google it, also has USB drivers if necessary)
3. Connect your phone to the computer, and once all drivers are installed, fire up SuperOneClick, hit 'Root' and watch the magic unfold
4. Download ROM Manager from the Market, follow the instructions (Flash recovery>Download a ROM (CM7 recommended))
Once you are familiar with the basics of installing a ROM from ZIP, head over to the Dev forums, and download ICS for stock HBOOT to get you started!
Click to expand...
Click to collapse
The SuperOneClick Application just gets not responding when I click the Root button and after these messages on the right pane are shown
* daemon not running . starting it now on port 5037 *
* daemon started successfully *
Please advise..

Make sure you run it with administrator rights (right click to see the option), and verify that USB Debugging is turned on on the phone. If it is turned on, you need to make sure you have the adb drivers installed (different than the standard USB drivers that windows automatically installs).

Hi all. I have read quite a few pages of the s off blacks install guide. Not really getting it. Can someone please give me simple steps to install blackrose?
Please and thank you.
Sent from my Nexus One using xda premium

Blackrose install guide
Sent from my Nexus One using xda premium

hardrockinandroid said:
Blackrose install guide
Sent from my Nexus One using xda premium
Click to expand...
Click to collapse
Black rose thread http://forum.xda-developers.com/showthread.php?t=1270589

I've read that and everything sounds so complicated. I've watched the vid for resizing partition but they don't say anything. Can someone give a step by step for us noobs for resizing partition please?
Sent from my Nexus One using xda premium

do you have all requirements met from br op page
if so, you need to download the latest br from op and extract it to the download folder you just downloaded br to. then open the extracted folder and clickon br.exe
follow instructions inside the command window that opens
then you need to resize partition to ics sizes thru the breditor

What is op page?Yes bootloader unlocked. Rooted. I have the blackrose zip.the adb and fastboot drivers for windows. Don't know what to do now. I put both files on my desktop. Now what?
Sent from my Nexus One using xda premium

OP page is first page of Dev's thread--mmm
Needs read as well as most of thread to get an understanding of this--lots of folks are running into big trouble if they don't understand it first--
If you are rooted and unlocked do you have sdk installed and can you run adb devices and fastboot devices in command window and see phone's serial number? If so you don't need the usb drivers from OP page--

Yes I have ran commands on a my touch4g, a HTC sensation and a g 2x. Do I just do exactly as the YouTube video shows and then flash the blackrose zip after resizing
the partition? Then flash an Ics Rom?
Sent from my Nexus One using xda premium

TWRP Port to TMO Note

Hi, I would like to port TWRP to the TMO Galaxy Note but since I don't have one I need help from people with the phone. I ported TWRP to the ATT Galaxy Note: http://forum.xda-developers.com/showthread.php?t=1647575.
If someone who has rooted can give me the output of the following commands as root in adb shell or a terminal on the phone:
cat /proc/partitions
cat /proc/emmc
busybox fdisk -l /dev/block/mmcblk0
Thanks!
If anyone is feeling frisky, they can dd this to their recovery partition (/dev/block/mmcblk0p22 at least on the att note)
Don't blame me for borking and make sure that this partition is the right partition. It looks like the cwm touch version in the dev section is a clone of braway's CWM touch so I am guessing they have the same partitions.
Good luck!

I can do this when I get back in for the night. Anything to help move along the development section of this device!!

is there any added benefit in doing this?
i've been using twrp 2.2.1 on my TMO note since day one. I used odin flash CWM then CWM to flash the ATT twrp from teamwins website and have experienced no issues at all.
not trying to discourage development in anyway but if it already exists and works correctly what would be the advantage?

pxldtz said:
is there any added benefit in doing this?
i've been using twrp 2.2.1 on my TMO note since day one. I used odin flash CWM then CWM to flash the ATT twrp from teamwins website and have experienced no issues at all.
not trying to discourage development in anyway but if it already exists and works correctly what would be the advantage?
Click to expand...
Click to collapse
Odds are the devices are identical, but this build will give a device name of "quincytmo" instead of "quincyatt" which may be important for zip files. Most ROMs do a check before installing called an assert where they check the device name to ensure that you're installing the correct ROM for your device.
Still, glad to hear that you've been using TWRP without issue.

Really dont have to port it just use twrp in the at&t dev section i been using for a week works flawlessly and im on a native tmobile note
Didnt read prior post my bad
Sent from my SAMSUNG-SGH-I717 using xda premium

Dees_Troy said:
Odds are the devices are identical, but this build will give a device name of "quincytmo" instead of "quincyatt" which may be important for zip files. Most ROMs do a check before installing called an assert where they check the device name to ensure that you're installing the correct ROM for your device.
Still, glad to hear that you've been using TWRP without issue.
Click to expand...
Click to collapse
that's a valid point. like i said i'm not trying to hinder development, but thanks for answering

bigbiff said:
Hi, I would like to port TWRP to the TMO Galaxy Note but since I don't have one I need help from people with the phone. I ported TWRP to the ATT Galaxy Note: http://forum.xda-developers.com/showthread.php?t=1647575.
If someone who has rooted can give me the output of the following commands as root in adb shell or a terminal on the phone:
cat /proc/partitions
cat /proc/emmc
busybox fdisk -l /dev/block/mmcblk0
Thanks!
If anyone is feeling frisky, they can dd this to their recovery partition (/dev/block/mmcblk0p22 at least on the att note)
Don't blame me for borking and make sure that this partition is the right partition. It looks like the cwm touch version in the dev section is a clone of braway's CWM touch so I am guessing they have the same partitions.
Good luck!
Click to expand...
Click to collapse
Here is the result for /partitions
- For /emmc, result is "no such file or directory"
- For busybox, apparently I didn't have that installed, downloading and installing now, but will take a few minutes because I'm throttled. Will update post with results from that after.
While as others have stated, it's not "necessary" to port over since the ATT version works, I'm more than happy to help to have a version for THIS model, as there are obviously differences between the i717 and the T879. This is apparent because not all ROMS for the i717 work on the T879. Having our own version of TWRP just solidifies the 879 as it's own entity, not just an "also ran"

Android Revolution said:
Here is the result for /partitions
- For /emmc, result is "no such file or directory"
- For busybox, apparently I didn't have that installed, downloading and installing now, but will take a few minutes because I'm throttled. Will update post with results from that after.
While as others have stated, it's not "necessary" to port over since the ATT version works, I'm more than happy to help to have a version for THIS model, as there are obviously differences between the i717 and the T879. This is apparent because not all ROMS for the i717 work on the T879. Having our own version of TWRP just solidifies the 879 as it's own entity, not just an "also ran"
Click to expand...
Click to collapse
I went ahead and posted a t879 friendly image in Development forum. I also added it to goo manager. If you guys could test and report back that would be great.

HTC One Dev edition root question

Hey guys, I have been looking through the forums and have not found an answer to my confusion. I have the dev edition in the US, and I am not sure what steps to follow to root and unlock the bootloader. I don't know the difference between unlocked and s-off, so I am not sure where to start.
I have rooted a number of phones before, but they were always carrier versions so I knew exactly where to start from. Any direction would be great, and I apologize if this has been asked 50 times before.
Sent from my HTC One using Tapatalk 2

Mindstar1 said:
Hey guys, I have been looking through the forums and have not found an answer to my confusion. I have the dev edition in the US, and I am not sure what steps to follow to root and unlock the bootloader. I don't know the difference between unlocked and s-off, so I am not sure where to start.
I have rooted a number of phones before, but they were always carrier versions so I knew exactly where to start from. Any direction would be great, and I apologize if this has been asked 50 times before.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
What version of hboot do you have? If you have 1.44.0000 you can do S-Off and Unlock the bootloader using Revone
If you have 1.54.0000 you can't do S-Off

Dev edition comes with an unlocked bootloader, all you would need to do is flash a custom recovery,twrp will root the device for you,simplest way if JUST looking for root

Dev edition comes with an unlocked bootloader, all you would need to do is flash a custom recovery,twrp will root the device for you,simplest way if JUST looking for root
Click to expand...
Click to collapse
Pardon my ignorance, but what would I gain by looking for more than root?
Sent from my HTC One using Tapatalk 2

What version of hboot do you have? If you have 1.44.0000 you can do S-Off and Unlock the bootloader using Revone
If you have 1.54.0000 you can't do S-Off
Click to expand...
Click to collapse
How do I check which hboot I have?
Sent from my HTC One using Tapatalk 2

At some point you will need a USB cable and a computer (with the android sdk installed on it) to make any of the changes you are contemplating, and there are commands you can run from your computer's terminal app (while the phone is connected to the computer via USB) that tell you what HBOOT you have, but for purely informational purposes, the is a non- technical way to determine your HBOOT:
- power off phone all the way (make sure "fast boot" is turned off in settings..power)
-hold down volume-down and power buttons simultaneously for several seconds until screen turns white
- HBOOT version is clearly visible from this screen. Write down every version number or other info that you see for future reference. Consider taking a photo of this screen.
-to leave this environment, use volume key to change the highlighted selection, and the power button to actually invoke it: select "fastboot" then "reboot" to reboot gracefully
Sent from my HTC One using xda app-developers app

NxNW said:
At some point you will need a USB cable and a computer (with the android sdk installed on it) to make any of the changes you are contemplating, and there are commands you can run from your computer's terminal app (while the phone is connected to the computer via USB) that tell you what HBOOT you have, but for purely informational purposes, the is a non- technical way to determine your HBOOT:
- power off phone all the way (make sure "fast boot" is turned off in settings..power)
-hold down volume-down and power buttons simultaneously for several seconds until screen turns white
- HBOOT version is clearly visible from this screen. Write down every version number or other info that you see for future reference. Consider taking a photo of this screen.
-to leave this environment, use volume key to change the highlighted selection, and the power button to actually invoke it: select "fastboot" then "reboot" to reboot gracefully
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
OK, I just did what you said and the HBOOT is 1.44.0000. So, based on what was said earlier, I am good to do the Revone option? If I do Revone, what am I missing out on compared to any other option? Thanks for the help!

Go for it. I had 1.44 and eventually got revone to work. [ there is an undocumented tip that may help you (power off the device "hard", ie hold down power button for like 15 or 20 seconds, between each step), but you'll want to discuss that and any other issues you encounter with revone in the revone thread of course. ] I cant think of any negative side effects that i have experienced. And as those with hboot 1.55 have discovered, its always good to get S-OFF while you can. You may not have the chance later. Good luck.

Well obviously your looking to flash thngs,there are many options,this is why i said if you were just looking to root the device
Mindstar1 said:
Pardon my ignorance, but what would I gain by looking for more than root?
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse

Wonders_Never_Cease said:
Well obviously your looking to flash thngs,there are many options,this is why i said if you were just looking to root the device
Click to expand...
Click to collapse
Yeah, I want to flash. If all I do is root, am I still able to flash other ROMs? I can never keep straight what each of the different processes do.

NxNW said:
Go for it. I had 1.44 and eventually got revone to work. [ there is an undocumented tip that may help you (power off the device "hard", ie hold down power button for like 15 or 20 seconds, between each step), but you'll want to discuss that and any other issues you encounter with revone in the revone thread of course. ] I cant think of any negative side effects that i have experienced. And as those with hboot 1.55 have discovered, its always good to get S-OFF while you can. You may not have the chance later. Good luck.
Click to expand...
Click to collapse
Whats the deal with Revone and the HTC One tool kit here http://forum.xda-developers.com/showthread.php?t=2183942. My goal is to flash 4.2.2 roms and soon 4.3, so would I want to do both or just Revone.

Mindstar1 said:
Whats the deal with Revone and the HTC One tool kit here http://forum.xda-developers.com/showthread.php?t=2183942.
Click to expand...
Click to collapse
Here is an old article that covers some basic terminology, specifically geared toward HTC phones. Much of it applies to the HTC One (although the stuff about the difficulty flashing kernels in recovery does not pertain- we have it much easier).
http://www.pocketables.com/2012/08/...nlocked-bootloader-in-the-htc-evo-series.html
Also check out this famous post https://plus.google.com/103583939320326217147/posts/P1i8qzLfkTm
The second article clearly states you don't need S-Off to flash ROMs, but the first article also notes those who are going through the trouble of unlocking/rooting generally do S-OFF while they are at it.
As for hasoon's toolkit, I personally have avoided it. There are other ways to root.
For instance, if you install the latest version of a custom recovery such as TWRP or CWM, they actually give you a menu option to root whatever ROM is currently installed.
Check back again after you've gotten caught up on your reading.

NxNW said:
Here is an old article that covers some basic terminology, specifically geared toward HTC phones. Much of it applies to the HTC One (although the stuff about the difficulty flashing kernels in recovery does not pertain- we have it much easier).
http://www.pocketables.com/2012/08/...nlocked-bootloader-in-the-htc-evo-series.html
Also check out this famous post https://plus.google.com/103583939320326217147/posts/P1i8qzLfkTm
The second article clearly states you don't need S-Off to flash ROMs, but the first article also notes those who are going through the trouble of unlocking/rooting generally do S-OFF while they are at it.
As for hasoon's toolkit, I personally have avoided it. There are other ways to root.
For instance, if you install the latest version of a custom recovery such as TWRP or CWM, they actually give you a menu option to root whatever ROM is currently installed.
Check back again after you've gotten caught up on your reading.
Click to expand...
Click to collapse
Its funny, I came across the first article while looking for answers while I waited for your response. I never mess with radios so S-Off is not really important to me. The second article was even better and more clear so I think I know where I am now.
The last question for you is what you would suggest I use for the most trouble free rooting process. I am looking for a pretty low impact route, and you did seem to imply that it took some work to get revone working for you. The toolkit seems to be a good way to go, but it also says that it unlocks the boot, which I already have with the dev edition. Will that be a problem if the process tries to unlock an already unlocked phone?

Ok one last reading assignment, a good guide from the guy who does ARHD:
Read http://forum.xda-developers.com/showthread.php?t=2265618
For your case, my interpretation of his guide would go like this:
The dev edition came unlocked. A lot of "rooting guides" spend a long time explaining how to unlock since they assume you are not already. but if you *are* unlocked already then any time you stumble across any procedure that involves htcdev.com or "get identifier token" etc you can ignore it.
[If, at some time in the future, someone persuades you to "re-lock" your bootloader for some reason (and as far as i'm concerned there are very few good ones), fine, it won;t hurt anything, but later on if you ever wanted to be unlocked again you would need to go to htcdev.com and follow all those steps to re - un - lock your bootloader. but for now, you're unlocked, life is good.]
with an unlocked bootloader, you can flash a custom recovery.
you want to do this.
using a custom recovery is the simplest and easiest way to flash ROMs going forward.
the most reliable recovery available on the One is CWM non-touch version. so go to http://d-h.st/users/flyhalf205/?fld_id=11322#files and find a file with the highest version number (currently 6.0.x something) that does not say "touch" in it.
The basic steps to loading a custom recovery are
- make sure phone's bootloader is unlocked (with stock dev edition obviously you are already set)
- make sure your computer has android sdk installed and you know where the fastboot executable is
- once you have the latest recovery zip from location above, check its md5, and then rename it something simple like recovery.img and place it in the same folder as your fastboot executable
- on your phone, make sure "fast boot" feature is turned off
- boot phone into HBOOT then Fastboot
(in case it is not obvious, connect your phone now via USB and type the necessary commands into a terminal emulator on the computer)
- while phone is in fastboot, use command "fastboot erase cache"
- while phone is in fastboot, use command "fastboot flash recovery recovery.img" where recovery.img is the name you chose above
at this point you should be able to reboot the phone into your new recovery and have a look around.
first step is always make a backup (known as a "nandroid" backup).
if your goal was to root your existing ROM, then you don;t actually have to do the steps in the guide i linked to above anymore: as soon as you try to exit CWM it will notice you are not already rooted and prompt you if you want to root it.
But if you want to do it the old fashioned way where you go and flash your own super user zip and other useful files that go with it, just refer back to the guide above. If the crucial link to the "rooting tools" is still broken, let me paste it again for you here http://www.androidrevolution.nl/dow...le=Android_Revolution_HD_Root_and_BusyBox.zip
I'll let you read up on how to "flash a zip from recovery". It should be pretty straightforward. (download zip and put zip somewhere on phone, reboot into recovery, say you want to flash a zip, navigate to where it is on the phone, start flash, profit)
Once you have an unlocked bootloader, you can flash a custom recovery
Once you have a custom recovery, you can
- root an existing rom and/or
- flash a custom rom compatible with your setup, presumably one with root baked in
Once you have root on any rom, you can run titanium, wireless tether etc.
Hopefully this is enough to get you started down the right path.

NxNW said:
Ok one last reading assignment, a good guide from the guy who does ARHD:
Read http://forum.xda-developers.com/showthread.php?t=2265618
For your case, my interpretation of his guide would go like this:
The dev edition came unlocked. A lot of "rooting guides" spend a long time explaining how to unlock since they assume you are not already. but if you *are* unlocked already then any time you stumble across any procedure that involves htcdev.com or "get identifier token" etc you can ignore it.
[If, at some time in the future, someone persuades you to "re-lock" your bootloader for some reason (and as far as i'm concerned there are very few good ones), fine, it won;t hurt anything, but later on if you ever wanted to be unlocked again you would need to go to htcdev.com and follow all those steps to re - un - lock your bootloader. but for now, you're unlocked, life is good.]
with an unlocked bootloader, you can flash a custom recovery.
you want to do this.
using a custom recovery is the simplest and easiest way to flash ROMs going forward.
the most reliable recovery available on the One is CWM non-touch version. so go to http://d-h.st/users/flyhalf205/?fld_id=11322#files and find a file with the highest version number (currently 6.0.x something) that does not say "touch" in it.
The basic steps to loading a custom recovery are
- make sure phone's bootloader is unlocked (with stock dev edition obviously you are already set)
- make sure your computer has android sdk installed and you know where the fastboot executable is
- once you have the latest recovery zip from location above, check its md5, and then rename it something simple like recovery.img and place it in the same folder as your fastboot executable
- on your phone, make sure "fast boot" feature is turned off
- boot phone into HBOOT then Fastboot
(in case it is not obvious, connect your phone now via USB and type the necessary commands into a terminal emulator on the computer)
- while phone is in fastboot, use command "fastboot erase cache"
- while phone is in fastboot, use command "fastboot flash recovery recovery.img" where recovery.img is the name you chose above
at this point you should be able to reboot the phone into your new recovery and have a look around.
first step is always make a backup (known as a "nandroid" backup).
if your goal was to root your existing ROM, then you don;t actually have to do the steps in the guide i linked to above anymore: as soon as you try to exit CWM it will notice you are not already rooted and prompt you if you want to root it.
But if you want to do it the old fashioned way where you go and flash your own super user zip and other useful files that go with it, just refer back to the guide above. If the crucial link to the "rooting tools" is still broken, let me paste it again for you here http://www.androidrevolution.nl/dow...le=Android_Revolution_HD_Root_and_BusyBox.zip
I'll let you read up on how to "flash a zip from recovery". It should be pretty straightforward. (download zip and put zip somewhere on phone, reboot into recovery, say you want to flash a zip, navigate to where it is on the phone, start flash, profit)
Once you have an unlocked bootloader, you can flash a custom recovery
Once you have a custom recovery, you can
- root an existing rom and/or
- flash a custom rom compatible with your setup, presumably one with root baked in
Once you have root on any rom, you can run titanium, wireless tether etc.
Hopefully this is enough to get you started down the right path.
Click to expand...
Click to collapse
I ran into an issue following your directions (which were basically the same as the YouTube video about the "easiest way to install custom recovery for the htcone" that I got off another xda thread. I run the command to fastboot flash recovery, and my PC gives me an error saying that fastboot is not a valid command. I have the proper drivers installed, and I am in fastboot on my phone but it won't work. I did notice that on the thread you linked to above, they want my recovery file to be in some sdk folder or something. My directions didn't mention that and the directions you linked to mention an sdk file in the bootloader section, but it tells me to skip that if I have a dev edition. Is the sdk file the reason why my computer won't recognize the command? For what it's worth, I tried that toolkit and it did not seem to recognize my phone either.
Sent from my HTC One using Tapatalk 2

EDIT Just a general tip - you can copy the text of any error message you get and paste it into google and you will doubtless turn up a bunch of interesting info - you are very likely not the first person to encounter the issue.
Anyway here's what I think is happening:
Sometimes when you try to give a command from the command line, a computer doesn't know where the necessary executable file is.
If the SDK was installed ok , then somewhere on your computer is the actual fastboot.exe executable.
Find it.
If it is in a folder called C:\path\to\files\blah\blah then you need to actually type out C:\path\to\files\blah\blah\fastboot.exe to run it.
If you will be doing more commands in this location or any commands that refer to other files in the same location (and some if these procedures assume you will since you'll be putting the flashable image files in this location), you really should tell your terminal program to just change the "working directory" to that location: then whenever you refer to something the computer will look there first. Here's how that looks:
cd C:\path\to\files\blah\blah
fastboot
(Final note- going forward you can make it easier to launch executables by adding their location to your "PATH variable" - google it. )
Maybe you knew all this? But for the benefit of anyone else following these bread crumbs, here's the upshot: Most of these "procedures" that people write down assume some general knowledge of command line syntax. If you're not comfortable with that yet, you're going to need to be persistent and search google a lot.

Corrupt device really need help!

Problem fixed! Thank you for you help! I didn't know this message was just a google scare thing.
Thank you XDA! Please delete

Did you research at all? You are supposed to do this...In order: unlocked bootloader > Flash Custom Recovery > Flash SuperSU zip.
Can you provide a screenshot with another phone or type the code. First rule is don't panic. Also you might be to sideload a zip of Android n to boot into Android.
Sent from my Nexus 6 using XDA-Developers mobile app

nexus_6_user said:
I was trying to root my phone using Androidrootz tool but now my device says it is corrupt. I'm very confused about flashing etc etc and really need some help. I have a 64gb version that was unlocked. I don't know which factory image to use. If someone could explain adb and connecting my phone that might be a good start for me. I can get into boot loader and recovery.
Click to expand...
Click to collapse
Does the phone boot after it gives you the corrupt message? All that means is the phone detected the /system was modified which in a lot of rooting methods is commonplace. Also there's a guide around somewhere about how to flash factory images which is more indepth than I'd be willing to type up right now.

ignore the message that you see, its googles way of scaring you. that's all that is.

StykerB said:
Does the phone boot after it gives you the corrupt message? All that means is the phone detected the /system was modified which in a lot of rooting methods is commonplace. Also there's a guide around somewhere about how to flash factory images which is more indepth than I'd be willing to type up right now.
Click to expand...
Click to collapse
But with the bootloader being locked (I assume it is) him rooting it that specific way didn't corrupt it just sent trips of the bootloader police. Security checks fail.
Sent from my Nexus 6 using XDA-Developers mobile app