Now we have two distinct root methods for the N1. 1) Unlock the bootloader using fastboot and proceed accordingly. 2) Use the new method described with adb in recovery mode.
Going forward, certain tutorials and methods may only be applicable to one method and not the other, or will provide separate methods for each case. So maybe we need some new terminology.
Original root method using fastboot = "boot-rooted"?
New root method using adb in recovery mode = "rec-rooted"?
Feel free to get more imaginative.
Good idea. But are there any differences between the two methods other than the locked bootloader thing?
aboda7es said:
Good idea. But are there any differences between the two methods other than the locked bootloader thing?
Click to expand...
Click to collapse
Well one thing I notice is that some of the modding threads (e.g. how to restore your Nexus One to stock) contain instructions that involve Fastboot. I'm assuming that if your bootloader is still locked, you won't be using Fastboot to accomplish this step.
I believe you can still use PASSIMGs on a locked bootloader,so some of those guides could still work on a rec-rooted Nexus.
How about fast-root and hacked-root?
N3xt2N0N3 said:
How about fast-root and hacked-root?
Click to expand...
Click to collapse
Sounds Good...it has my vote
Fast-root works...
Hacked-root I'm not sure about - cause really, both methods are pretty hacktastic
How about true-root and lazy-root?
In any case, functionality of the root access is still the same - the only difference is whether your bootloader is unlocked or not. I don't think two different terminologies are required - a tutorial can just have two sections; one for people having unlocked bootloader, and other for locked.
I dont see why it makes a difference but
oem-root for fastboot oem unlock
and
sd-root for the sdcard loop one (hmm sounds like it could be confused with sd root directory)
or
loop-root
N3xt2N0N3 said:
How about fast-root and hacked-root?
Click to expand...
Click to collapse
Sounds Great!
rohandhruva said:
In any case, functionality of the root access is still the same - the only difference is whether your bootloader is unlocked or not. I don't think two different terminologies are required - a tutorial can just have two sections; one for people having unlocked bootloader, and other for locked.
Click to expand...
Click to collapse
considering that those with unlocked bootloaders can use the same method as those with locked loaders, i think the unroot tut itself should be changed to use the PASSIMG.zip
theres no need to go through all the hassle of doing a nandroid restore imo
Related
Does the hardware on the HTC Flyer check the bootloader's digital signature?
Can anyone answer this?
I am bumping this thread again.
Will someone please answer this question?
It comes from the store locked, but you can unlock it by going to
http://www.htcimeiunlock.com/
They will allow an unlock, but you lose your warranty.
quickquest88 said:
It comes from the store locked, but you can unlock it by going to
http://www.htcimeiunlock.com/
They will allow an unlock, but you lose your warranty.
Click to expand...
Click to collapse
He means if the boot loader is locked, not the carrier. And also to the OP, do you mean read-write access to the boot loader or something else?
I want to know if the first stage bootloader is signature checked by the HTC Flyer's boot ROM. If it isn't then the locked bootloader problem can be solved by simple overwriting it. And yes, read/write access would be required to overwrite the bootloader.
Master Melab said:
I want to know if the first stage bootloader is signature checked by the HTC Flyer's boot ROM. If it isn't then the locked bootloader problem can be solved by simple overwriting it. And yes, read/write access would be required to overwrite the bootloader.
Click to expand...
Click to collapse
Well i would say no. You can't get a custom boot loader to load 2 roms or anything yet. No access at all, read or write.
Master Melab said:
I want to know if the first stage bootloader is signature checked by the HTC Flyer's boot ROM. If it isn't then the locked bootloader problem can be solved by simple overwriting it. And yes, read/write access would be required to overwrite the bootloader.
Click to expand...
Click to collapse
No it isn't, it's actually easy to edit a bootloader, it's getting it onto the device that's hard.
I still would like to know if the bootloader itself is signature checked.
well then read my last post.
The only thing your previous post tells me is that accessing the area where the bootloader resides is difficult.
The the "no it isn't" doesn't mean anything?
Sorry. I thought you were talking about simple read/write access.
Master Melab,
PM me is you have specific questions, you can post a summary after that if you want.
I messaged you my questions.
curious about what youre getting at,so subscribing
Master Melab said:
I messaged you my questions.
Click to expand...
Click to collapse
yep, got it. I'll try to reply this evening.
Thank you.
globatron said:
No it isn't, it's actually easy to edit a bootloader, it's getting it onto the device that's hard.
Click to expand...
Click to collapse
if its fairly easy to edit a bootloader, is it not possible to patch the HC hboot to think the radio is s-off(like the revolutinary does),then simply install that hboot in place of the real one,when following the HC install guide?
seems after one roots GB with revolutionary,it should be fairly easy to get an s-off HC hboot for someone who knows how to do such things what am i missing?
Ok, with all of the confusing data here, what is relevant and working for the Photon in regards to:
Rooting:
Unlocking:
Flashing:
First of all, this should be in the "Q&A" or "General" section because it does not contribute to the development of Photon.
Rooting: Can be done.
Unlocking: Can be done, but breaks 4G.
Flashing: Can be done after unlocking and then re-locked to gain 4G.
tuxytuxy said:
First of all, this should be in the "Q&A" or "General" section because it does not contribute to the development of Photon.
Rooting: Can be done.
Unlocking: Can be done, but breaks 4G.
Flashing: Can be done after unlocking and then re-locked to gain 4G.
Click to expand...
Click to collapse
Oh, so 4G does work after relocking? I wasn't totally sure.
Fail much?! http://forum.xda-developers.com/showthread.php?t=1227867
It's on the first page of this forum too.
tuxytuxy said:
Fail much?! http://forum.xda-developers.com/showthread.php?t=1227867
It's on the first page of this forum too.
Click to expand...
Click to collapse
That's been superceeded by nopudding4u, trying to find that thread.
READ ALL
http://forum.xda-developers.com/showthread.php?t=1216999
ping33tx said:
http://forum.xda-developers.com/showthread.php?t=1216999
Click to expand...
Click to collapse
Been looking at that. Also used http://forums.acsyndicate.net/showt...lash-Roms-Kernels-Themes!-(11-videos)-9-28-11 to root the phone so far (and do the locked bootstrap). About to attempt a look at the unlocking.
just so I know the procedure can goes as follows , Root, Custom Recovery, then Unlock Bootloader correct?
kusanagi-sama said:
Been looking at that. Also used http://forums.acsyndicate.net/showt...lash-Roms-Kernels-Themes!-(11-videos)-9-28-11 to root the phone so far (and do the locked bootstrap). About to attempt a look at the unlocking.
Click to expand...
Click to collapse
The one click root works perfect just make sure you have ur device in debugging mode checked.and run pudding sbf file to unlock and install Tenfar system recovery and then use that recovery and you can install CWM instead of running fastboot on adb.
Jo_795 said:
just so I know the procedure can goes as follows , Root, Custom Recovery, then Unlock Bootloader correct?
Click to expand...
Click to collapse
No, root, unlock bootloader, custom recovery.
Sorry if this is posted before or buried in the mountain of threads, but from what i've read so far, does the root method actually give you S-OFF? I don't want to root it if i wont be able to flash roms. Also, when i plugged in my device the driver updated and its 2.0.7.3. Does that mean i dont need to download the drivers?
tampered just means rooted if you want to unlock your bootloader so you can flash custom roms.click on the link below and it has instructions.
http://forum.xda-developers.com/showthread.php?t=1690919
Check out this thread:
http://forum.xda-developers.com/showthread.php?t=1690919
There is no S-Off for this phone as of yet, but I don't think we'll need it. Root is different than S-Off.
S-Off is closer to an Unlocked bootloader, which the post I directed to you does. With this method you'll be able to flash roms using TWRP.
wobbies said:
Sorry if this is posted before or buried in the mountain of threads, but from what i've read so far, does the root method actually give you S-OFF? I don't want to root it if i wont be able to flash roms. Also, when i plugged in my device the driver updated and its 2.0.7.3. Does that mean i dont need to download the drivers?
Click to expand...
Click to collapse
Currently there is no S-Off method available for this phone (as of right now). But we've come to find out that we don't need S-Off that much on this phone.
Even with S-On, you can flash roms, mods, tweaks, etc. Hell you can even flash Radios now (which use to be reserved for S-Off).
The current method is HTCDev Unlock. It does mark your bootloader as 'tampered'. But when am I going to actually use a manufacturer warranty or somebody like Sprint is actually going to check the Bootloader. But even that is different from root. You can root, which will give you root access. Then if you want you can unlock the bootloader which will allow you to flash a custom recovery which will allow you to flash Roms, etc.
Edit: I've been ninja'd.
Thank you very much guys
So in order to flash custom ROMs I have to unlock the bootloader (and void the warranty)?
sracercelica said:
So in order to flash custom ROMs I have to unlock the bootloader (and void the warranty)?
Click to expand...
Click to collapse
yes, but you can make it seem as if you never unlocked by ruu'ing. sprint will never know... if it gets that bad, "somebody stole it."
Rydah805 said:
yes, but you can make it seem as if you never unlocked by ruu'ing. sprint will never know... if it gets that bad, "somebody stole it."
Click to expand...
Click to collapse
Well sprint only gives 30 days warranty anyways so I am actually worried about HTC's warranty. I dont have the insurance through Sprint (which I heard is going to increase to 10 bucks a month).
So what is the easiest method to root and unlock bootloader to flash a custom recovery?
Now I thought att/htc were getting stricter about making it easier to modify devices, did they change their minds because if so I'm getting this device if its gotten easier.
I would say to use hasoon2000's toolkit
http://forum.xda-developers.com/showthread.php?t=2699065
SysAdmNj said:
So what is the easiest method to root and unlock bootloader to flash a custom recovery?
Now I thought att/htc were getting stricter about making it easier to modify devices, did they change their minds because if so I'm getting this device if its gotten easier.
Click to expand...
Click to collapse
Yes, that is the easiest way. Verizon is the only one blocking the unlock at the moment.
SysAdmNj said:
So what is the easiest method to root and unlock bootloader to flash a custom recovery?
Click to expand...
Click to collapse
Easiest or best way? Two very different things.
Unlocking the bootloader and installing custom recovery "manually" is easy. All the toolkit does is automate the steps, which robs you of a valuable learning experience. Doing it manually teaches you a lot. And if you haven't used adb/fastboot before, they are important tools to know how to use when things do go quite right while modding the phone (as they invariably do, no matter how careful you are).
SysAdmNj said:
Now I thought att/htc were getting stricter about making it easier to modify devices, did they change their minds because if so I'm getting this device if its gotten easier.
Click to expand...
Click to collapse
AT&T did not even allow bootloader unlocking on the One X (EVITA). So that has gotten better.
Locked bootloaders aren't going away anytime soon. At least not until folks stop bricking their phones out of their own negligence, and claiming "warranty issues".
Hello, so I've been trying for a while to unlock my bootloader and at this point I'm quite confused. For whatever reason the power button + volume down combo nation does not load my phone into the bootloader from the off state. Instead it boots my phone regularly. This itself is is not a problem because I can boot it into the bootloader using adb. But inside the bootloader I can move up and down using the list but can't use my power button to select anything. I've also tried booting into recovery and the volume and the power button to choose works fine. I'm just confused at this point and a little frustrated because all I would like to do is install paranoid android, and have not had any problems with past devices. Any help would be appreciated! Thank you.
That is some strange behavior, I agree.
Its been a long while since I unlocked the bootloader, so I don't completely remember what is required. I assume you need to use the vol and/or power buttons to select to unlock; and that is your main problem?
If so, that is a tough one. One thought is to RUU to stock, to eliminate the possibility of some software glitch causing your problem.
Otherwise, plan B is to use sunshine to s-off, than unlock the bootloader. Not sure if that would work, and its an expensive experiment to try ($25). But if it does work, s-off is a nice thing to have. Not expressly needed to flash ROMs, of course. But s-off does allow some other nice tricks, like being able to flash radios, modified hboots, change CID/MID, and removed the requirement to relock the bootloader to RUU.
redpoint73 said:
That is some strange behavior, I agree.
Its been a long while since I unlocked the bootloader, so I don't completely remember what is required. I assume you need to use the vol and/or power buttons to select to unlock; and that is your main problem?
If so, that is a tough one. One thought is to RUU to stock, to eliminate the possibility of some software glitch causing your problem.
Otherwise, plan B is to use sunshine to s-off, than unlock the bootloader. Not sure if that would work, and its an expensive experiment to try ($25). But if it does work, s-off is a nice thing to have. Not expressly needed to flash ROMs, of course. But s-off does allow some other nice tricks, like being able to flash radios, modified hboots, change CID/MID, and removed the requirement to relock the bootloader to RUU.
Click to expand...
Click to collapse
I think I've seen RUU before but for whatever reason I couldn't find it for my phone. Would it make any difference that the phone is AT&T, because from what I've seen people who have the AT&T smartphone tend to run into problems, just not mine.
EDIT: I just took a look at sunshine and am confused, is it an android app that does the s-off? Sorry for what I assume are common knowledge. Looking at sunshine, running 5.1.1 it looks like I need to have to bootloader unlocked to root the phone.
Jkaspar said:
I think I've seen RUU before but for whatever reason I couldn't find it for my phone.
Click to expand...
Click to collapse
All AT&T RUUs are linked on my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
Be aware that you can only run the RUU version same or higher than what is on the phone (no "downgrading" unless you have s-off).
Jkaspar said:
Would it make any difference that the phone is AT&T, because from what I've seen people who have the AT&T smartphone tend to run into problems, just not mine.
Click to expand...
Click to collapse
There isn't any reason why ATT would be any harder to bootloader unlock than any other version M8, if that is what you mean.
Jkaspar said:
EDIT: I just took a look at sunshine and am confused, is it an android app that does the s-off? Sorry for what I assume are common knowledge. Looking at sunshine, running 5.1.1 it looks like I need to have to bootloader unlocked to root the phone.
Click to expand...
Click to collapse
Yes, sunshine is an app that will s-off the phone, and then also has the option to unlock the bootloader without HTCDev.com (which is fairly trivial once s-off, think it can also by done via adb commands).
Latest Android version for the ATT M8 is 5.0 (.1 or .2, I can't remember exactly).
I'm not sure which versions will work with sunshine without prior root. But you can always install the sunshine app, and it will tell you whether it can s-off or not (and you won't be charged any $ unless it can s-off).
If you do need root before sunshine, some folks have had luck with towelroot (might be temp root, I can't recall). But yes, it complicates what is already just an idea, and not a sure fix by any means.
Sunshine from what I just tried requires root to be installed for the current android I am on. I also just tried using towelroot and it said that my phone was not supported. I am currently in school but I will try the RUU when I get a chance.
Okay so I did the RUU and it worked fine. Booted into the boot loader and nada. Still no luck with the power button. Choosing in recovery still works however. Is there a way to do it purely using adb commands?
You have to unlock with fastboot commands
Like to the screen where it gives me an option to either unlock the bootloader or not? I can get there fine, I just can't choose the yes I want to unlock option.
Jkaspar said:
Like to the screen where it gives me an option to either unlock the bootloader or not? I can get there fine, I just can't choose the yes I want to unlock option.
Click to expand...
Click to collapse
No, that requires button response from the phone
Right which is my main problem