Related
I've looked at a few threads but they seem to involve flashing before rooting...
Is there a way to root without flashing? if so... how?
Thanks
You can unlock the bootloader without flashing by booting into Bootloader modem (power off device, then power on while holding Power+VOL UP) and typing fastboot oem unlock into ADB from your computer.
But you cannot gain root access, use a custom recovery, or use a custom ROM without flashing. The "Flashing" you're hearing about is via Fastboot which allows the flashing of custom recoverys, or boot.imgs.
The one-click methods that might have allowed this in the past were based on exploits in the stock ROM/kernel. The Nexus S might contain similiar flaws to be exploited later(no current methods work fyi), but right now the easiest way to gain root is by doing what I said above or from the threads in the development section dedicated to it (also linked in the stickied FAQ if you don't know where to start).
Given that it's also possible to just as easily relock the bootloader(e.g. for warranty purposes), it's likely it will be some time before the exploits are searched for/discovered.
unremarked said:
You can unlock the bootloader without flashing by booting into Bootloader modem (power off device, then power on while holding Power+VOL UP) and typing fastboot oem unlock into ADB from your computer.
But you cannot gain root access, use a custom recovery, or use a custom ROM without flashing. The "Flashing" you're hearing about is via Fastboot which allows the flashing of custom recoverys, or boot.imgs.
The one-click methods that might have allowed this in the past were based on exploits in the stock ROM/kernel. The Nexus S might contain similiar flaws to be exploited later(no current methods work fyi), but right now the easiest way to gain root is by doing what I said above or from the threads in the development section dedicated to it (also linked in the stickied FAQ if you don't know where to start).
Given that it's also possible to just as easily relock the bootloader(e.g. for warranty purposes), it's likely it will be some time before the exploits are searched for/discovered.
Click to expand...
Click to collapse
abit confused by what your saying...
I'm interpreting what your saying as
"you can boot a boot loader/recovery without actually flashing it. It just boots that as a temporary and then apply superuser.apk, su" ???
sinatosk said:
abit confused by what your saying...
I'm interpreting what your saying as
"you can boot a boot loader/recovery without actually flashing it. It just boots that as a temporary and then apply superuser.apk, su" ???
Click to expand...
Click to collapse
The bootloader is built into the phone, there's nothing to flash for that.
Think of it as a pre-recovery. Fastboot is a feature in the Android SDK which works with the bootloader to flash things such as recovery, or boot.imgs prior to actually having a custom recovery/root. However, it does require the bootloader to be unlocked which is where the fastboot oem unlock command comes in. Once you have a custom recovery on your phone, you flash things like normal.
From the stickied FAQ:
unremarked said:
Q: How do I root/unroot the Nexus S?
Check the development section links below for more detail, but you gain root on the Nexus S by booting the phone into fastboot (aka the bootloader) mode and typing "fastboot oem unlock." This will wipe your phone and it's SD card partition. To unroot it, again boot into fastboot mode and type "fastboot oem lock."
Step 1: http://forum.xda-developers.com/showthread.php?t=878786
Step 2: http://forum.xda-developers.com/showthread.php?t=875875
Click to expand...
Click to collapse
The first step helps you set up the SDK and drivers. The second step will tell you how to root, install recovery, and flash Superuser.
Out of interest is there a step 3 that tells us how to reverse all of the above in the event of having to return the phone?
xspyda said:
Out of interest is there a step 3 that tells us how to reverse all of the above in the event of having to return the phone?
Click to expand...
Click to collapse
No, I'll add one, but generally Best Buy employees don't check things like the recovery or bootloader to see if a phone is rooted or not.
Anyhow, if you if you flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 it will restore you completely to stock, including the recovery. After that, it's just a matter of going back into the boatloader/fastboot mode and typing fastboot oem lock.
That is the only way to return to stock until Google puts out the official recovery stuff.
Fair enough, thanks for that. One question, will this actually restore to a state my nexus s was received in? Reason I ask is that I thought this was an adapted nand - although I understand this is the only option right now.
My retailer is perhaps a little more clued up than the the average best buy employee so is there anything in the software that can identify this as being a none original Google image?
Thanks again.
unremarked said:
No, I'll add one, but generally Best Buy employees don't check things like the recovery or bootloader to see if a phone is rooted or not.
Anyhow, if you if you flash the NAND backup found here: http://forum.xda-developers.com/showthread.php?t=884093 it will restore you completely to stock, including the recovery. After that, it's just a matter of going back into the boatloader/fastboot mode and typing fastboot oem lock.
That is the only way to return to stock until Google puts out the official recovery stuff.
Click to expand...
Click to collapse
this is why I started this thread... Google not released the official recovery
I already have the SDK setup, I code android applications ... no fastboot in there though. May have to compile that myself or use the one from the thread
thanks for your help...
xspyda said:
Fair enough, thanks for that. One question, will this actually restore to a state my nexus s was received in? Reason I ask is that I thought this was an adapted nand - although I understand this is the only option right now.
My retailer is perhaps a little more clued up than the the average best buy employee so is there anything in the software that can identify this as being a none original Google image?
Thanks again.
Click to expand...
Click to collapse
It will restore your phone to the state it was received in if it had shipped with Android 2.3.1. The OTA should be fairly well known to anyone you're returning it to.
I don't think so. It's entirely possible that Samsung might have something tucked away deep inside the phone, either hardware or software, but I highly doubt it. And, if there were, I think only their technicians who are trained in the intricacies of this device would know about it. As far as I understand, that NAND is completely stock without any modifications. I'll admit I haven't read the entire thread. At the very most, it may have the Superuser.apk and related binaries but I don't think so.
sinatosk said:
this is why I started this thread... Google not released the official recovery
I already have the SDK setup, I code android applications ... no fastboot in there though. May have to compile that myself or use the one from the thread
thanks for your help...
Click to expand...
Click to collapse
Ah, sorry, I'm having a hard time with explaining stuff. Some threads I'll jump in to try and help assuming the guy knows about ADB, root, system vs SD partitions, et al then find out not so much. Other threads, I'll end up making myself look silly.
Fastboot should just be an .exe file within the SDK's tool's section. You don't actually have to run it, though. Everything involving fastboot operates through CMD just like ADB, only you begin the obviously differently. (fastboot flash blahblahblah vs adb push blahblabhlah).
unremarked said:
It will restore your phone to the state it was received in if it had shipped with Android 2.3.1. The OTA should be fairly well known to anyone you're returning it to.
I don't think so. It's entirely possible that Samsung might have something tucked away deep inside the phone, either hardware or software, but I highly doubt it. And, if there were, I think only their technicians who are trained in the intricacies of this device would know about it. As far as I understand, that NAND is completely stock without any modifications. I'll admit I haven't read the entire thread. At the very most, it may have the Superuser.apk and related binaries but I don't think so.
Ah, sorry, I'm having a hard time with explaining stuff. Some threads I'll jump in to try and help assuming the guy knows about ADB, root, system vs SD partitions, et al then find out not so much. Other threads, I'll end up making myself look silly.
Fastboot should just be an .exe file within the SDK's tool's section. You don't actually have to run it, though. Everything involving fastboot operates through CMD just like ADB, only you begin the obviously differently. (fastboot flash blahblahblah vs adb push blahblabhlah).
Click to expand...
Click to collapse
well yeah I know about ADB... just nothing about rooting
Hmm the phone shipped with 2.3 and I have yet to update but as 2.3.1 is an official update I can't see that being reason not to accept a return.
Hi, I just registered on this forum hoping to learn the ins and outs of rooting. Been doing a lil research reading a couple of sites on the topic. Bear with me, but I feel like a complete noob cause a lot of the language is sailing straight over my head. I think I have the gist of it, but it seems a lot of the information are scattered and there's a lot of different ways to root.
I just recently got the Nexus S (Sprint's 4G version) and I have been reading some of the ROMs aren't compatible with the 4G version yet. This has me a little worried...would rooting the phone be any different since its a 4G model? I really don't want to brick my phone on my first try. Is there a comprehensive guide with easy step by step instructions on how to root this particular version of the phone?
I do agree the 4G version needs its own tab to prevent confusion since a lot of the guides here are for the regular Nexus S. Many thanks in advance.
If you look in the developers section there is a sticky at the top for the Sprint variant of the Nexus S. In it there are rooting instructions and such.
fraspas said:
Hi, I just registered on this forum hoping to learn the ins and outs of rooting. Been doing a lil research reading a couple of sites on the topic. Bear with me, but I feel like a complete noob cause a lot of the language is sailing straight over my head. I think I have the gist of it, but it seems a lot of the information are scattered and there's a lot of different ways to root.
I just recently got the Nexus S (Sprint's 4G version) and I have been reading some of the ROMs aren't compatible with the 4G version yet. This has me a little worried...would rooting the phone be any different since its a 4G model? I really don't want to brick my phone on my first try. Is there a comprehensive guide with easy step by step instructions on how to root this particular version of the phone?
I do agree the 4G version needs its own tab to prevent confusion since a lot of the guides here are for the regular Nexus S. Many thanks in advance.
Click to expand...
Click to collapse
It's actually quite hard to brick the Nexus devices. The gist of it is as follows:
Boot into fastboot (hold pwr up and turn the phone one).
Fastboot oem unlock to unlock the device (this wipes)
Install a custom recovery via fastboot (fastboot flash recovery downloaded-image.img)
flash the su binary package via recovery
This is the same process for all variants of the phone - there's nothing 4G specific about it other than don't try to use an old version of CWM (the i9023 can't either).
Guides are here for the 4G though: http://forum.xda-developers.com/showthread.php?t=1071500
The only way you are going to brick your device is:
- Flashing a GSM radio to your CDMA device
- Pulling the battery DURING a radio flash
- Using ODIN and flashing a full rom package not meant for your device.
fraspas said:
Hi, I just registered on this forum hoping to learn the ins and outs of rooting. Been doing a lil research reading a couple of sites on the topic. Bear with me, but I feel like a complete noob cause a lot of the language is sailing straight over my head. I think I have the gist of it, but it seems a lot of the information are scattered and there's a lot of different ways to root.
I just recently got the Nexus S (Sprint's 4G version) and I have been reading some of the ROMs aren't compatible with the 4G version yet. This has me a little worried...would rooting the phone be any different since its a 4G model? I really don't want to brick my phone on my first try. Is there a comprehensive guide with easy step by step instructions on how to root this particular version of the phone?
I do agree the 4G version needs its own tab to prevent confusion since a lot of the guides here are for the regular Nexus S. Many thanks in advance.
Click to expand...
Click to collapse
pretty sure I used this guide.
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
then i deleted a bunch of stuff i had no use for and am happy.
good luck
krohnjw said:
...
The only way you are going to brick your device is:
- Flashing a GSM radio to your CDMA device
- Pulling the battery DURING a radio flash
- Using ODIN and flashing a full rom package not meant for your device.
Click to expand...
Click to collapse
I've actually seen people unbrick after flashing the wrong radio... LOL pretty amazing.
I could really use some help please. Im using these guides to root and I've gotten the bootloader unlocked, but when I get to the part where I flash CWM recovery in the command prompt, I get a message that says:
cannot load recovery-clockwork-3.0.2.4-crespo
That is the file they said to download, and I inserted it into the tools section of android sdk folder. Any ideas? The unlock bootloader command worked perfectly, but Im getting stuck at this step.
EDIT: I figured out my problem. I wasn't placing the recovery file in the Platform-tools folder, I was putting it into the regular tools folder. I have my moments.
dazednconfused1144 said:
I could really use some help please. Im using these guides to root and I've gotten the bootloader unlocked, but when I get to the part where I flash CWM recovery in the command prompt, I get a message that says:
cannot load recovery-clockwork-3.0.2.4-crespo
That is the file they said to download, and I inserted it into the tools section of android sdk folder. Any ideas? The unlock bootloader command worked perfectly, but Im getting stuck at this step.
EDIT: I figured out my problem. I wasn't placing the recovery file in the Platform-tools folder, I was putting it into the regular tools folder. I have my moments.
Click to expand...
Click to collapse
Make sure you rename the image too.
wild1z said:
Make sure you rename the image too.
Click to expand...
Click to collapse
I finally got it. Worked like a charm once I figured out what I was doing wrong. Do we still have to rename the file (install-recovery.sh and rename to install-recovery.sh.bak) in root explore to make it stick? I have rebooted several times and it is still there so I was just wondering.
These are pretty great instructions, especially the link. Since Sprint shipped with version 2.3.4 of Android with the build GRJ22, do the rooting instructions still work for our model?
dazednconfused1144 said:
I finally got it. Worked like a charm once I figured out what I was doing wrong. Do we still have to rename the file (install-recovery.sh and rename to install-recovery.sh.bak) in root explore to make it stick? I have rebooted several times and it is still there so I was just wondering.
Click to expand...
Click to collapse
Got no idea. I was referring to renaming the clockwork image file. But I think you answered your own question since root has um... rooted. Cheers.
fraspas said:
These are pretty great instructions, especially the link. Since Sprint shipped with version 2.3.4 of Android with the build GRJ22, do the rooting instructions still work for our model?
Click to expand...
Click to collapse
I rooted mine just fine. You should be good.
Which method did you use? I'm reading a lot about bootloader being unlocked/locked and some methods requiring a backup and some without. This really adds to the confusion. Then there's a Superboot method which seems a lot easier but it doesn't seem to have the GRJ22 model. I'm pretty sure its easy once I get to it, but the overwhelming information makes it extremely difficult to follow lol. Information overload.
Hello. As you can see, I'm a new member here and I'm also a new Android user; I bought my Nexus S (GT-i9020A) last week.
After a few days, I started thinking about jailbreaking my phone(rooting in Android's case) but I'm not really sure where to start, what rooting/flashing/ROM/etc means so I am just dumbfounded.
I want to customize my phone, make it look cool, etc.
Help would be greatly appreciated, thanks a lot in advance
1. Root = Unlock to change operating system
2. Install Recovery = Tool to install alternate operating system (ROM)
=> http://forum.xda-developers.com/showthread.php?t=931865
3. Install ROM = Modify the operating system
Then you can change kernel (link betwen operating system and the processor) or radio (link betwen operating system and radio communication).
Consult this : http://forum.xda-developers.com/showthread.php?t=1067813
anremi said:
1. Root = Unlock to change operating system
2. Install Recovery = Tool to install alternate operating system (ROM)
=> http://forum.xda-developers.com/showthread.php?t=931865
3. Install ROM = Modify the operating system
Then you can change kernel (link betwen operating system and the processor) or radio (link betwen operating system and radio communication).
Consult this : http://forum.xda-developers.com/showthread.php?t=1067813
Click to expand...
Click to collapse
Just to add a bit more info, rooting allows you full system access to your phone, where as stock prevents you from accessing certain areas. Some Apps that need to work with the phone on a low level need this root access.
A ROM is not really an operating system, its just the UI that sits on top of it, so different ROMS are custimized etc, lots to choose to your taste.
The recovery allows you to flash these ROM's , but it also allows you to backup your phone, access your storage etc in the case you can not boot.
'one more thing', root =! jailbreak, for god sake! android is 'jailbreaked' by default! =o)
bringonblink said:
Just to add a bit more info, rooting allows you full system access to your phone, where as stock prevents you from accessing certain areas. Some Apps that need to work with the phone on a low level need this root access.
A ROM is not really an operating system, its just the UI that sits on top of it, so different ROMS are custimized etc, lots to choose to your taste.
The recovery allows you to flash these ROM's , but it also allows you to backup your phone, access your storage etc in the case you can not boot.
Click to expand...
Click to collapse
Okay, that explained a lot. But what about the version of my phone? Most guides I see are for 2.3.3 but my phone is 2.3.4?
3doncrack said:
Okay, that explained a lot. But what about the version of my phone? Most guides I see are for 2.3.3 but my phone is 2.3.4?
Click to expand...
Click to collapse
The rooting process is the same for 2.3.3 & 2.3.4.
Maximilian Mary said:
The rooting process is the same for 2.3.3 & 2.3.4.
Click to expand...
Click to collapse
okay. Does phone model matter? Like i9020A or i9020T etc.?
3doncrack said:
okay. Does phone model matter? Like i9020A or i9020T etc.?
Click to expand...
Click to collapse
It should be the same for all the GSM models. Using an NS4G (D720) guide will not work.
(If you start flashing full roms, then you might want to use one specific to your exact model.)
Maximilian Mary said:
It should be the same for all the GSM models. Using an NS4G (D720) guide will not work.
(If you start flashing full roms, then you might want to use one specific to your exact model.)
Click to expand...
Click to collapse
It's not,
9020 rooting is different as 9023/9020A are different. They're similar but there is a minor difference.
And rooting != flashing.
Rooting permits you administrative access to change anything within Android (/system). HOWEVER, it doesn't give you permission to change the recovery. Changing the recovery isn't rooting. Rooting is step one of it but it is not the ability to flash a custom recovery.
The "rooting" process is for ANY android OS. Android OS will not be changing how the bootloader functions unless a new version of the bootloader is changed but it shouldn't significantly change.
zephiK said:
It's not,
9020 rooting is different as 9023/9020A are different. They're similar but there is a minor difference.
Click to expand...
Click to collapse
Pray tell what this difference is.
And rooting != flashing.
Rooting permits you administrative access to change anything within Android (/system). HOWEVER, it doesn't give you permission to change the recovery. Changing the recovery isn't rooting. Rooting is step one of it but it is not the ability to flash a custom recovery.
Click to expand...
Click to collapse
I thought it was the other way around: flashing a custom recovery is step one (well, two) of rooting.
The "rooting" process is for ANY android OS. Android OS will not be changing how the bootloader functions unless a new version of the bootloader is changed but it shouldn't significantly change.
Click to expand...
Click to collapse
Are you saying that the rooting process for the Nexus S will work for any android phone (for example the Hero or the Droid Charge)? Really?
Maximilian Mary said:
Pray tell what this difference is.
I thought it was the other way around: flashing a custom recovery is step one (well, two) of rooting.
Are you saying that the rooting process for the Nexus S will work for any android phone (for example the Hero or the Droid Charge)? Really?
Click to expand...
Click to collapse
For one, when the I9020A was announced, they were using the 9020T method to root and it didn't work. Hence there are two separate threads for rooting respective to that particular phone.
That's why one of the guides say,
[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020T only)
Second: It depends. Some phones you can root with using the stock recovery. For example, the Galaxy S. You just download su.zip, rename it to update.zip go into stock recovery. Reinstall updates and BAM! you're rooted, you then proceed to get ROM manager and download Clockwork Recovery from there.
Edit: For example if you wanted to, you could totally unlock the bootloader and rename su.zip to update.zip and flash that in the stock recovery. It'll do nothing but add superuser.apk into /system/app. Because when I rooted my Nexus S. I didn't flash Clockwork Recovery yet, I wanted to make sure my phone didn't have any defects before changing it (this was before Google added a script to flash the stock recovery). Most guides make you flash Clockwork Recovery first, but in reality, it doesn't matter the order. But if you're a novice user, I'd just follow the guide.
It should be the same for all the GSM models. Using an NS4G (D720) guide will not work.
(If you start flashing full roms, then you might want to use one specific to your exact model.)
Click to expand...
Click to collapse
Third: No, by using common sense and process of elimination. I was clearly talking about the Nexus S due to its ability to unlock and lock the bootloader.
Also, you said "GSM models" and referred a "NS[4G]" and you said charge and hero.. so, you're kind of contradicting yourself here.
Again, process of elimination.
Thanks for trying to push my buttons though, didn't really work. Having said, not to say anything else. I have 2400+ posts, you figure I would know what I'm talking about. Nice try
zephiK said:
For one, when the I9020A was announced, they were using the 9020T method to root and it didn't work. Hence there are two separate threads for rooting respective to that particular phone.
That's why one of the guides say,
[GUIDE] Step by Step ROOT Nexus S via ClockworkMod Recovery image (i9020T only)
Click to expand...
Click to collapse
I could only find two differences between these guides. One is a patch for the 9023 drivers. I'm assuming Google has fixed this by now. (Can anyone confirm this?)
The other difference is the recoveries they use. Thanks to j_r0dd, you no longer need a separate recovery for the 9023.
Perhaps I should have said "Any up to date GSM Nexus S guide should work."
.
Second: It depends. Some phones you can root with using the stock recovery. For example, the Galaxy S. You just download su.zip, rename it to update.zip go into stock recovery. Reinstall updates and BAM! you're rooted, you then proceed to get ROM manager and download Clockwork Recovery from there.
Edit: For example if you wanted to, you could totally unlock the bootloader and rename su.zip to update.zip and flash that in the stock recovery. It'll do nothing but add superuser.apk into /system/app. Because when I rooted my Nexus S. I didn't flash Clockwork Recovery yet, I wanted to make sure my phone didn't have any defects before changing it (this was before Google added a script to flash the stock recovery). Most guides make you flash Clockwork Recovery first, but in reality, it doesn't matter the order. But if you're a novice user, I'd just follow the guide.
Click to expand...
Click to collapse
That is freaking cool. I'm going to unroot and try it. Do you need to do anything special in recovery, or just put the zip in the right place?
Third: No, by using common sense and process of elimination. I was clearly talking about the Nexus S due to its ability to unlock and lock the bootloader.
Also, you said "GSM models" and referred a "NS[4G]" and you said charge and hero.. so, you're kind of contradicting yourself here.
Again, process of elimination.
Thanks for trying to push my buttons though, didn't really work. Having said, not to say anything else. I have 2400+ posts, you figure I would know what I'm talking about. Nice try
Click to expand...
Click to collapse
The xda app doesn't show post counts. I figured thumping you in the chest would cover all the bases.
Is there a purely stock, rooted, fully functional rom for the Relay out there? I know how to use ADB and prefer doing so as opposed to odin and other methods. Not interested in CWM either. I just need root[for firewall and backup utility reasons] and will debloat manually after installation.
The only method to root the Relay is by using a custom Recovery of some form and ODIN or heimdal. We can not use adb to flash a Relay, it does not have fastboot. ODIN or heimdall are used to flash a Samsung device.
I made a stock rooted, debloated rom. On the Relay, I think you will want to use heimdall (or Odin) to flash CWM. From there, you can root the stock rom or flash custom roms.
The other option would be finding a root exploit.
Magamo said:
The only method to root the Relay is by using a custom Recovery of some form and ODIN or heimdal. We can not use adb to flash a Relay, it does not have fastboot. ODIN or heimdall are used to flash a Samsung device.
Click to expand...
Click to collapse
Magamo, You are VERY wrong. I have used ADB to flash my relay from the original T-699UVLH1 to the rooted version. So using a "custom recovery" is most definately not the only way to do it. Perhaps you lack the knowledge to properly use ADB. And I just re-verified, The Relay does indeed have "fastboot". Your post was wrong on so many levels...
gee one said:
I made a stock rooted, debloated rom. On the Relay, I think you will want to use heimdall (or Odin) to flash CWM. From there, you can root the stock rom or flash custom roms.
The other option would be finding a root exploit.
Click to expand...
Click to collapse
Ya, not interested in heimdall, odin and CWM methods. Just looking for a purely stock rom with stock recovery, both in the rooted state.
Well if you can root via adb, then just flash back to 4.1.2 and root it.
lexluthermiester said:
Magamo, You are VERY wrong. I have used ADB to flash my relay from the original T-699UVLH1 to the rooted version. So using a "custom recovery" is most definately not the only way to do it. Perhaps you lack the knowledge to properly use ADB. And I just re-verified, The Relay does indeed have "fastboot". Your post was wrong on so many levels...
Click to expand...
Click to collapse
I'm not really certain what you are trying to prove here. If you have a better way, then post your steps so that we all might learn from your awesome knowledge, oh great one. Meanwhile, I'll stick to doing things the proven way for our phone that doesn't involve things that have been unproven, and risky. More than likely, the only way you'll be able to root the relay using ADB only, is by having a modified kernel installed, which... Means you will have had to have rooted the phone already. So you're talking yourself into a catch 22 already. But please, post your process. I'd love to verify the veracity of this.
@lexluthermiester
I'm actually curious on this, I bought a relay months ago but was too busy to play with it much. I can't think of any way to root it solely with adb, are you attempting to push psneuter or some other program to root this way? I guess I just don't see it happening, but please tell as I'm a curious learner
Also how did you re-verify the relay has fastboot? I only know a handful of Samsung devices that have a bootloader capable of using fastboot and am shocked to know this phone does, can you please tell me how you were able to do this?
And for the record I'm not trying to instigate you I just don't see how anything you are saying works, maybe the kernel allows for a simple push of busybox and then you can push superuser into /system/apps after you mount it writeable, I don't see how but would really like to see this method, but mostly I would like to know how to use fastboot on this phone as it would open more possibilities. Did you need to flash a new bootloader to get it to work? If so where did you get it?
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
@lexluthermiester
I'm actually curious on this, I bought a relay months ago but was too busy to play with it much. I can't think of any way to root it solely with adb, are you attempting to push psneuter or some other program to root this way? I guess I just don't see it happening, but please tell as I'm a curious learner
Also how did you re-verify the relay has fastboot? I only know a handful of Samsung devices that have a bootloader capable of using fastboot and am shocked to know this phone does, can you please tell me how you were able to do this?
And for the record I'm not trying to instigate you I just don't see how anything you are saying works, maybe the kernel allows for a simple push of busybox and then you can push superuser into /system/apps after you mount it writeable, I don't see how but would really like to see this method, but mostly I would like to know how to use fastboot on this phone as it would open more possibilities. Did you need to flash a new bootloader to get it to work? If so where did you get it?
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I first learned how to root on my old LG C800[My Touch Q] here: http://forum.xda-developers.com/showthread.php?t=1752704
I ultimately decided that I didn't like the CWM parts and looked for a way to just push the ROM and recovery to the C800. Then looked up a tutorial on how to use ADB properly[can't remember were that was] because of problems with the C800 recovery and discovered in said process, that MOST[dare I say all?] Android phones have a fastboot mode as it is part of the recovery runtime mode. This includes Samsung devices. After finally successfully installing a rooted stock recovery on the C800 I discovered the problem I was having with it was not something I could fix as it was software problem on LG's side[headphone volume issue]. Got rid of it and bought a Relay.
After finding a few different methods rooting the Relay, I decided to use the ADB method I already knew would work. I downloaded a stock rooted ROM[UVLH1, found here on XDA] and painlessly installed it using more or less same methods and procedures that were used on the C800. Installing the recovery was equally as painless. I have had zero problems with the Relay and love it. Have been curious about the update to JB though and have been looking for the aforementioned purely stock rooted ROM. Thing is I like and use a few of T-mobile's preinstalled apps so a debloated ROM is useless to me. I know which software to remove[CarrierIQ for a start] and which to freeze and prefer to do so on my own. So Gee One's rooted ROM doesn't have what's needed. I can fully value and appreciate his work though.
To answer one of your questions directly, I did not use a new bootloader. While CWM is a very handy tool, I don't ROM switch enough and haven't changed the ROM on this Relay since getting the rooted UVLH1 on it.
As for the "instigate" remark, I think the word you likely were looking for is "provoke". You are asking honest questions presented in a lucid and civilized fashion. My response to "Magamo" was invoked because he/she/it came off as a complete dolt and posting woefully inaccurate information, which not only does a dis-service to anyone reading this post, but makes himself look like a monkey diddling football.
Magamo said:
I'm not really certain what you are trying to prove here. If you have a better way, then post your steps so that we all might learn from your awesome knowledge, oh great one. Meanwhile, I'll stick to doing things the proven way for our phone that doesn't involve things that have been unproven, and risky. More than likely, the only way you'll be able to root the relay using ADB only, is by having a modified kernel installed, which... Means you will have had to have rooted the phone already. So you're talking yourself into a catch 22 already. But please, post your process. I'd love to verify the veracity of this.
Click to expand...
Click to collapse
Not trying prove anything. And it's not MY "awesome knowledge". ADB was created by, let's think.... OH ya - Google, for use on and for the Android platform. As for your proven/unproven comments, can you be any more misinformed? I've rooted 2 of my own personal phones and dozens of others for family, friends and coworkers, all using ADB. Hmmm.... Your above statement only proves you don't understand or know how to use ADB properly[if at all]. Here's a great idea for you, read a tutorial about how to use ADB and verify it yourself.
And FYI, I did read your message before you edited it, and if this is the kind of help you have to offer on regular basis, kindly DON'T in future. You have my sincerest thanks!
gee one said:
Well if you can root via adb, then just flash back to 4.1.2 and root it.
Click to expand...
Click to collapse
I simply used ADB to flash a pre-rooted ROM[UVLH1] to the Relay. I'm currently on 4.0.4 and would like to try 4.1.2, but need a few things you seem to have removed from the ROM you posted. If you happened to have a stock + rooted ROM, could you post it? And if you do would you all like me to post a step by step for installing it using ADB?
There is a stock mc5 rom that has all the stuff that I took out. You could use that to add back in the pieces that I took out of my version. I think you might need simg2img to convert the stock system to an ext4 img file that can be loop mounted,
I think the http://samsung-updates.com/ site should have the JB rom.
@lexluthermiester
I'm not seeing where this hostility toward Magamo is coming from, I'm sure he knows how to use adb as he appears to be on team apex who devs for this phone. But I still am not sure how you were able to root your relay just with adb, I guess I just wasn't able to find the method you used looking through the mytouch q thread. Again not trying to instigate or rather provoke you but could you lay it out for me, just not wrapping my head around this
And also I only know of three or so Samsung devices with fastboot capabilities, all of which are nexus devices, can you explain how to get into fastboot, this would be super cool to me, as for answering your question on stock jellybean ROM can you not just update your phone via ota or did your root method break this, thanks
Sent from my Nexus 7 using XDA Premium 4 mobile app
gee one said:
There is a stock mc5 rom that has all the stuff that I took out. You could use that to add back in the pieces that I took out of my version. I think you might need simg2img to convert the stock system to an ext4 img file that can be loop mounted,
I think the http://samsung-updates.com/ site should have the JB rom.
Click to expand...
Click to collapse
I've posted a stock MC5 Image that's been run through simg2img on the Stock ROM thread. It's in update.zip form, it also contains a boot.img simply unzip that, and there you go. I've also posted a stock recovery in the same post.
And lexluther, you still haven't posted the steps you took. I'm still quite interested in verifying the veracity of this, considering that the stock image and kernel has adb root access disabled, so how did you enable fastboot, especially since as we all on TeamApexQ who have disassembled both the software and hardware of the relay never found a way to, hence my posts. Instead of being insulting, confrontational and provocative with me, how about you just be rational and helpful, hmmm? Saying you did it on a completely different phone by a different manufacturer is ... less than helpful.
@lexluthermiester
I know you confirmed once and then reconfirmed but I'm still not seeing any fastboot option for this phone, maybe you could help me out on this
And I feel I'm well versed in adb but I still can't find a wat to root this phone without a custom kernel or recovery, I would really like to know how. Are you sure you can't just write out these steps quick for me, thanks again
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
@lexluthermiester
I know you confirmed once and then reconfirmed but I'm still not seeing any fastboot option for this phone, maybe you could help me out on this
And I feel I'm well versed in adb but I still can't find a wat to root this phone without a custom kernel or recovery, I would really like to know how. Are you sure you can't just write out these steps quick for me, thanks again
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry mate, I would have if I'd ever seen this message. Sadly I don't have the Relay anymore, battery popped and killed the phone with it. If memory serves you needed to have a stock rom[before the update] and then pushed the rooted rom to it through adb, then letting it update itself that way, but I'm not sure as it's been so long.
demkantor said:
@lexluthermiester
I know you confirmed once and then reconfirmed but I'm still not seeing any fastboot option for this phone, maybe you could help me out on this
And I feel I'm well versed in adb but I still can't find a wat to root this phone without a custom kernel or recovery, I would really like to know how. Are you sure you can't just write out these steps quick for me, thanks again
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You may also wish to check out this thread;
http://forum.xda-developers.com/showthread.php?t=2256821
demkantor said:
@lexluthermiester
I know you confirmed once and then reconfirmed but I'm still not seeing any fastboot option for this phone, maybe you could help me out on this
And I feel I'm well versed in adb but I still can't find a wat to root this phone without a custom kernel or recovery, I would really like to know how. Are you sure you can't just write out these steps quick for me, thanks again
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And/Or this one;
http://forum.xda-developers.com/showthread.php?t=2528752
I'm very new to the process of modifying android/firmware/rooting/etc... I want to regain FoxFi (wifi tether) functionality on my Verizon HTC One M8, which was lost with Lollipop. I had been fighting the update for months but it forced itself on me a few weeks ago. I believe my only real option is downgrading to Kit Kat.
I have a long post typed up with my plethora of questions after browsing around a number of forums and blogs the last few weeks, but there are so many basic terms, commands and things I don't understand... I figured it might make things go smoother if I just ask my stupid questions first and then proceed. Plus, I'm an engineer and am generally good with technology, and have wanted to pick up the skills needed to do software version changes/rooting etc for years now. I'll keep the other post typed up (took a while), but won't send it until I get some feedback here... so as to avoid undue spam and clutter.
So, with that all said, dumb question time. Please be kind, lol. Note - if there is an entry level video/picture-laden tutorial that will likely explain all of this, please point me that way and I'll get up to speed as much as i can on my own. There seem to be many tutorials out there but almost all of the One M8 ones seem to have lots of terminology in them I don't get ,yet:
1) What is an RUU?
2) What is the CID? (appears to just be a build # or software version associated with new updates)
3) What is the fastboot folder? What is "hboot"
4) Whats an ADSP?
5) Which SDK/Sync manager will I need on my PC? I have the basic HTC Sync manager (some links suggest its needed)
More questions as they occur to me, thanks all!
Well, hate to burst your bubble, but even after understanding all of these terms you can't downgrade to kit kat after taking the lollipop update. On Verizon htc ones, all system partitions/folders/files are write protected and cannot be modified with fastboot or RUU's in order to downgrade. As of right now, the only way to remove the write protection on lollipop is with an HTC Java card (this process / state is called s-off). Several people on xda have them and might help you out, particularly dottat.
Sorry for ignoring the main question here, I'm just offering what I know and I'll leave the explaining to someone a bit more knowledgeable with htc stuff to answer those questions. (I'm stuck in the same "lollipop lockdown" boat as you)
zphantom55 said:
Well, hate to burst your bubble, but even after understanding all of these terms you can't downgrade to kit kat after taking the lollipop update. On Verizon htc ones, all system partitions/folders/files are write protected and cannot be modified with fastboot or RUU's in order to downgrade. As of right now, the only way to remove the write protection on lollipop is with an HTC Java card (this process / state is called s-off). Several people on xda have them and might help you out, particularly dottat.
Sorry for ignoring the main question here, I'm just offering what I know and I'll leave the explaining to someone a bit more knowledgeable with htc stuff to answer those questions. (I'm stuck in the same "lollipop lockdown" boat as you)
Click to expand...
Click to collapse
Appreciated, no worries!
I had noticed dottat was a prominent figure in many of the downgrade threads, so perhaps I'll try to reach out to him directly.
SadbutTrue999 said:
Appreciated, no worries!
I had noticed dottat was a prominent figure in many of the downgrade threads, so perhaps I'll try to reach out to him directly.
Click to expand...
Click to collapse
For the time being, check the post here. Working solution
Apparently someone successfully rooted verizon htc one m8
Link to steps
You can downgrade back to 4.4.4 as long as you are S-off. It takes some patience to root and get sunshine to S-off. Just make sure you do not try to run an RUU (Rom Update Utility) of an earlier version if you are still S-ON. I would say that if you just want to wifi tether, S-off your phone, flash a recovery, then just flash a 5.1 Rom that has wifi tether working out of the box.
crmcsh01 said:
You can downgrade back to 4.4.4 as long as you are S-off. It takes some patience to root and get sunshine to S-off. Just make sure you do not try to run an RUU (Rom Update Utility) of an earlier version if you are still S-ON. I would say that if you just want to wifi tether, S-off your phone, flash a recovery, then just flash a 5.1 Rom that has wifi tether working out of the box.
Click to expand...
Click to collapse
So the order of operations is:
1) disable fastboot
2) root
3) unlock bootloader
4) go s-off
5) use RUU
?
As far as what i'm looking for... with Lollipop, tethering itself works, but they make you go through the verizon service (whereas past Android versions could be bypassed with some certificate trickery, which is what Foxfi did), and I don't want to pay $30/mo for something i was getting for free the last 3 years. I also want to root the phone for a few other applications.
I'm not sure what 5.1 Roms would support FoxFi on this phone out of the box (i've heard Samsung's Galaxy S6 continues to support foxfi with verizon and Lollipop, but i'm not sure i could use that rom), which is why 4.4.4 might be easier.
Questions:
1) Is the above order right?
2) Can you disable fastboot with Lollipop? I didn't see the option when i tried.. and i'm seeing some places online saying you can't. What then?
3) I downloaded ADB.. how to you get a command prompt up when connected to the one that lets you send commands to it? Seems basic but ADB has a milllion settings.
4) What else am i forgetting?
Just trying to figure out the first steps... its easy for a newbie to get buried in walkthroughs and new terms. Thanks again!
SadbutTrue999 said:
So the order of operations is:
1) disable fastboot
2) root
3) unlock bootloader
4) go s-off
5) use RUU
?
As far as what i'm looking for... with Lollipop, tethering itself works, but they make you go through the verizon service (whereas past Android versions could be bypassed with some certificate trickery, which is what Foxfi did), and I don't want to pay $30/mo for something i was getting for free the last 3 years. I also want to root the phone for a few other applications.
I'm not sure what 5.1 Roms would support FoxFi on this phone out of the box (i've heard Samsung's Galaxy S6 continues to support foxfi with verizon and Lollipop, but i'm not sure i could use that rom), which is why 4.4.4 might be easier.
Questions:
1) Is the above order right?
2) Can you disable fastboot with Lollipop? I didn't see the option when i tried.. and i'm seeing some places online saying you can't. What then?
3) I downloaded ADB.. how to you get a command prompt up when connected to the one that lets you send commands to it? Seems basic but ADB has a milllion settings.
4) What else am i forgetting?
Just trying to figure out the first steps... its easy for a newbie to get buried in walkthroughs and new terms. Thanks again!
Click to expand...
Click to collapse
When it comes time to flash a ROM, I'd humbly suggest CleanROM. It's stock ROM with the Verizon bloatware removed, and it's already rooted for your convenience. Like you, my primary reason for installing a custom ROM was to be able to use my phone as a hotspot. (Verizon will have to pry my unlimited data plan from my cold, dead hands.) CleanROM's native tethering app works out of the box, so there's no need to even install a third-part app like FoxFi. Sadly, it appears that the developer is no longer supporting this ROM, but it's suiting my needs for the time being.
Anyway, I just purchased a used M8 running stock Lollipop last week and here's what I did:
1. Followed the directions here to achieve s-off. (There's nothing in these directions about disabling fastboot.)
2. RUU (because the phone was used and I have no idea what the previous owner did to this thing and I want to start fresh); I followed dodtat's instructions for Option 1, plopped the 0P6BIMG.zip file on my SD card, and let the phone do the rest.
3. Installed a custom recovery (the latest version of TWRP - installation instructions are on the linked page)
4. Installed CleanROM via TWRP
5. Enjoyed free tethering
Good luck!
dbrits said:
Like you, my primary reason for installing a custom ROM was to be able to use my phone as a hotspot. (Verizon will have to pry my unlimited data plan from my cold, dead hands.) CleanROM's native tethering app works out of the box, so there's no need to even install a third-part app like FoxFi. Sadly, it appears that the developer is no longer supporting this ROM, but it's suiting my needs for the time being.
Click to expand...
Click to collapse
Glad I'm not alone! :hifive:
Anyway, I just purchased a used M8 running stock Lollipop last week and here's what I did:
1. Followed the directions here to achieve s-off. (There's nothing in these directions about disabling fastboot.)
2. RUU (because the phone was used and I have no idea what the previous owner did to this thing and I want to start fresh); I followed dodtat's instructions for Option 1, plopped the 0P6BIMG.zip file on my SD card, and let the phone do the rest.
3. Installed a custom recovery (the latest version of TWRP - installation instructions are on the linked page)
4. Installed CleanROM via TWRP
5. Enjoyed free tethering
Good luck!
Click to expand...
Click to collapse
Thank you! That ought to get me started, I would think.
SadbutTrue999 said:
So the order of operations is:
1) disable fastboot
2) root
3) unlock bootloader
4) go s-off
5) use RUU
?
As far as what i'm looking for... with Lollipop, tethering itself works, but they make you go through the verizon service (whereas past Android versions could be bypassed with some certificate trickery, which is what Foxfi did), and I don't want to pay $30/mo for something i was getting for free the last 3 years. I also want to root the phone for a few other applications.
I'm not sure what 5.1 Roms would support FoxFi on this phone out of the box (i've heard Samsung's Galaxy S6 continues to support foxfi with verizon and Lollipop, but i'm not sure i could use that rom), which is why 4.4.4 might be easier.
Questions:
1) Is the above order right?
2) Can you disable fastboot with Lollipop? I didn't see the option when i tried.. and i'm seeing some places online saying you can't. What then?
3) I downloaded ADB.. how to you get a command prompt up when connected to the one that lets you send commands to it? Seems basic but ADB has a milllion settings.
4) What else am i forgetting?
Just trying to figure out the first steps... its easy for a newbie to get buried in walkthroughs and new terms. Thanks again!
Click to expand...
Click to collapse
You can use tethering for free on lollipop with s-off.
Not sure about foxfi but with the stock Verizon app.
andybones said:
You can use tethering for free on lollipop with s-off.
Not sure about foxfi but with the stock Verizon app.
Click to expand...
Click to collapse
dbrits said:
Anyway, I just purchased a used M8 running stock Lollipop last week and here's what I did:
1. Followed the directions here to achieve s-off. (There's nothing in these directions about disabling fastboot.)
2. RUU (because the phone was used and I have no idea what the previous owner did to this thing and I want to start fresh); I followed dodtat's instructions for Option 1, plopped the 0P6BIMG.zip file on my SD card, and let the phone do the rest.
3. Installed a custom recovery (the latest version of TWRP - installation instructions are on the linked page)
4. Installed CleanROM via TWRP
5. Enjoyed free tethering
Good luck!
Click to expand...
Click to collapse
Just to be clear... the 3rd step (of 21) in that first link you show is "RUU". Does this mean I should do it twice (and if so.. with different versions?), or will one RUU do it?
Sounds like his method to achieving S-off is just a series of checking the right buttons within a factory reset phone. Is that right?
andybones said:
You can use tethering for free on lollipop with s-off.
Not sure about foxfi but with the stock Verizon app.
Click to expand...
Click to collapse
Hmm, really? Interesting. Stock verizon app works fine, only used foxfi because in the past its met my needs.
Quick question... I've downloaded the java developer kit, ADB, and Android Studio. How do I verify they're working when i connect the phone? Is there a way to send a harmless ping/command/etc to the phone to check?
Few more questions regarding the s-off instructions:
1. Just did a factory reset. Also deleted everything on the SD card. Questions
a) Is a straight delete on the sd card ok or do i need to format? IF the latter, what do i format to?
b) How to I check the 'status' of the bootloader? Is that in one of the hard reset/fastboot menus? Or can i just let the thing start up and check it in the system menu somewhere?
2)
And if I do option 1, as you did... its the file here: https://www.androidfilehost.com/?fid=95916177934537709
that i rename 0P6BIMG.zip
right?
3) Both kingroot and TWRP seem like they can be downloaded to the phone after the fact. And both seem fairly straight forward. Do I need to do anything else for them to work?
4) Lastly... I believe i can do this all with the SIM card out? (seems like perhaps that is ideal, actually)
Just followed quite the droid root alice in wonderland rabbit hole...
Found some old S-off procedures but they appear to be defunct, which led me back to the 'sunshine' s-off approach you listed.
I followed the sunshine approach listed (the one here: http://forum.xda-developers.com/showpost.php?p=61920423&postcount=3652)
and get to:
File Manager App -> Install KingRoot (accept google checking apps)
Open KingRoot - Hit Root (read notes section at this point) and repeat until it says you have it in this app.
Back out of KingRoot, and uninstall the P~~~ whatever app and the KingUser app it installed by dragging from the app drawer into the uninstall icon.
File Manager App -> Install the SuperSU posted
Click to expand...
Click to collapse
Kingroot is installed, but reports "root is not available" (ostensibly because security is still on). So I still don't know how to turn S-oFF. I'm also not sure what the "P~~~~~ whatever" app he refers to is.
Help appreciated Phone not bricked yet
Just to be clear... the 3rd step (of 21) in that first link you show is "RUU". Does this mean I should do it twice (and if so.. with different versions?), or will one RUU do it?
Click to expand...
Click to collapse
I didn't RUU twice. I just did a factory reset before following the s-off instructions. You actually have to be s-off before using the specific RUU that I linked to.
Quick question... I've downloaded the java developer kit, ADB, and Android Studio. How do I verify they're working when i connect the phone? Is there a way to send a harmless ping/command/etc to the phone to check?
Click to expand...
Click to collapse
I googled "android adb" and this was the third link. I'm sure there are some great tutorials here on xda too.
a) Is a straight delete on the sd card ok or do i need to format? IF the latter, what do i format to?
Click to expand...
Click to collapse
SD card should be formatted FAT32.
And if I do option 1, as you did... its the file here: https://www.androidfilehost.com/?fid=95916177934537709 that i rename 0P6BIMG.zip right?
Click to expand...
Click to collapse
No, that's the wrong file. Use that standalone zip if you want to RUU, but you have to be s-off before using the standalone zip that dodtat posted.
Kingroot is installed, but reports "root is not available" (ostensibly because security is still on). So I still don't know how to turn S-oFF. I'm also not sure what the "P~~~~~ whatever" app he refers to is.
Click to expand...
Click to collapse
Keep trying to get root with Kingroot. It will eventually work, but it takes time and patience. And Purity is the name of the app that Kingroot will install after it gains root.
http://forum.xda-developers.com/showpost.php?p=61920423&postcount=3652 - this is the s-off instruction right?
Kingroot is part of those instructions... do I need to root before using sunshine? And is sunshine what finally achieves the s-off?
Will kingroot work prior to achieving s-off? (seems like it would have to given the instructions in the link above.. given enough tries). My first attempt using kingroot said root wasn't available, but the link above suggests I may need to just keep trying / uninstall+reinstall / etc to get it to work.
Thanks again!
Ok... some progress!
After 4 tries, Kingroot finally did its thing and reports I'm rooted.
In the link to achieve S-off, the app Sunshine is mentioned. Just bought a sunshine license for $25... why not.
Or not.
Despite Kingroot saying its rooted and Sunshine initially saying it had gained root and that my phone had passed all the pre-tests, now that i've spent the $25 its saying its "Unable to gain root access to your device. You may need to gain "TEmpRoot" or "PermRoot" through some other means. For HTC devices, unlocking with HTCDev.comand rooting with a custom recovery may work."
Grr. Any ideas?
I have an HTCDev account but when I get to step 5 in the unlocking bootloader process, I haven't been able to get my command propt commands to work. See images below...
By re-rooting with Kingroot Sunshine did its thing... after it finished the app disappeared. When I do a Volume down+power, it does show my software status as "modified", so I guess I'm making progress.
So is now when I put the said 0P6BIMG.zip on the sd card and let the phone find it? And as specific as we can be as to which file this needs to be is appreciated... thanks
lol so I re-rooted (again) and re-downloaded sunishine (because, like i said, after it did its thing it deleted itself), and its confirmed I'm S-Off.
I'm downloading dottat's "DOTTAT_VZWM8_S_OFF_5.0.1_RUU.zip", which is about 1.6GB. This is what I put on the SDcard, rename 0P6BIMG.zip, and 'flash' that right?
Appreciate you bearing with me (though it seems like i'm in a closet talking to myself a bit, which is ok)
Make sure the BIMG.zip is in the root of your sd card (in no folder) then load hboot and it'll detect the .zip and flash from there. Yes.