Database Users

one click root works for 2.2.1!

Just in case you haven't seen it http://forum.xda-developers.com/showthread.php?t=803682 here is the link for the (windows) only one click root app. I just used it on my Nexus One running 2.2.1 and it worked!. I did it on win. running on VMware on my mac, if you have issues with that, DM me.
http://goo.gl/ij77

Wow thanks for taking the time to post the great info glwinkler!
I was wondering about this since I'm not smart enough to root normally but the 1 click root method seems perfect for me. I just wasn't sure if it worked on the 2.2.1 so you answered my question
One more question, this unlocks the bootloader and voids the warranty right?
I've know there has been root methods that leave your bootloader locked (and warranty intact) but I'm not sure if this is one of them. Since I've had to swap 2 N1's I want to keep my warranty and won't root it away.

ap3604 said:
Wow thanks for taking the time to post the great info glwinkler!
I was wondering about this since I'm not smart enough to root normally but the 1 click root method seems perfect for me. I just wasn't sure if it worked on the 2.2.1 so you answered my question
One more question, this unlocks the bootloader and voids the warranty right?
I've know there has been root methods that leave your bootloader locked (and warranty intact) but I'm not sure if this is one of them. Since I've had to swap 2 N1's I want to keep my warranty and won't root it away.
Click to expand...
Click to collapse
It's using rageahainstthecage so if I'm not mistaken, it does not unlock your bootloader. I have not seen the unlocked symbol on my N1. But just to be safe THIS POST AND ITS OP ARE NOT RESPONSIBLE FOR YOUR BRICKED PHONE...BLAH BLAH BLAH...........

Definitely does not unlock it.

Yep, saw this SuperOneClick v1.4 (Root, Enable Non-Market App, Get UNLOCK code) over in N1 Q&A a few days ago...very impressive app!

yes, this worked for me without any hassles. thanks to whoever made it.

This worked great for me as well. I had to turn off the phone, then start the SuperOneClick program, and then boot the phone for it to work correctly. Couldn't have been much simpler. I highly recommend it!

I'll tell this to a friend whose android choose was Nexus One an he's been bugging me about if he could "root it" easily, really don't know why he wants to do it, he really doesn't need a rooted phone

The only issue I had was using windows, because I know nothing about windows. The unlockr video was helpful, they have notes under the video on their site. If anyone uses VMware, make sure you choose to have your device connect to windows every time or just unplug and replug your device after it says "OK, waiting for phone" or something like that.

[Q] Can someone please explain the rooting on this phone to me?

I apologize if there is already a thread like this, but the search wasnt working.. I know what i can do with my phone once it is rooted, I am just interested in what happens tot he actual phone. I could be wrong, but once i root it isnt it always possible to tell that i rooted it even if i unroot it so therefor all warantees are voided? sorry if im being unclear, i cant think of another way to explain it haha.

The K-Zoo Kid said:
I apologize if there is already a thread like this, but the search wasnt working.. I know what i can do with my phone once it is rooted, I am just interested in what happens tot he actual phone. I could be wrong, but once i root it isnt it always possible to tell that i rooted it even if i unroot it so therefor all warantees are voided? sorry if im being unclear, i cant think of another way to explain it haha.
Click to expand...
Click to collapse
The language on the "warranty void" screen says that unlocking the bootloader "may" void your warranty. On the Nexus One, HTC usually honored the warranty if the issue was with anything hardware related and could not have been the result of software tampering. Granted, that's them and this is Samsung.
Further, unless there is something hidden in the system files that counts the number of times you unlock the bootloader, you can always relock it prior to sending it in for repair with fastboot oem lock.

unremarked said:
The language on the "warranty void" screen says that unlocking the bootloader "may" void your warranty. On the Nexus One, HTC usually honored the warranty if the issue was with anything hardware related and could not have been the result of software tampering. Granted, that's them and this is Samsung.
Further, unless there is something hidden in the system files that counts the number of times you unlock the bootloader, you can always relock it prior to sending it in for repair with fastboot oem lock.
Click to expand...
Click to collapse
So there is a way to kind of undo the root without them knowing? THanks a lot btw. I figured it was something like this.

The K-Zoo Kid said:
So there is a way to kind of undo the root without them knowing? THanks a lot btw. I figured it was something like this.
Click to expand...
Click to collapse
unlocking the bootloader and rooting are two different things

jblade1000 said:
unlocking the bootloader and rooting are two different things
Click to expand...
Click to collapse
Ahh i have no idea what unlocking the bootloader does then.

The K-Zoo Kid said:
Ahh i have no idea what unlocking the bootloader does then.
Click to expand...
Click to collapse
In a nutshell, unlocking the bootloader means you will be allowed to flash non-Google/custom files to the system partition and more or less enables superuser access(aka root). Once thats done, then you "root" the device, push the Superuser.apk which will enable the rooted apps. Please check out the rooted section of my stickied FAQ for more detail on how to do this if you decide to. There are two great threads I link to.
Once you lock the bootloader, you lose access to the system partition and superuser I believe which effectively unroots it.

unremarked said:
In a nutshell, unlocking the bootloader means you will be allowed to flash non-Google/custom files to the system partition and more or less enables superuser access(aka root). Once thats done, then you "root" the device, push the Superuser.apk which will enable the rooted apps. Please check out the rooted section of my stickied FAQ for more detail on how to do this if you decide to. There are two great threads I link to.
Once you lock the bootloader, you lose access to the system partition and superuser I believe which effectively unroots it.
Click to expand...
Click to collapse
So basically if you want to do any sort of mods, flash roms, etc. you need to unlock the bootload and root. Thanks a lot for explaining that. I think i understand it now, but just to clarify, if i unlock the bootloader and root will i be able to get the phone back to stock without samsung knowing that i rooted/unlock the bootloader?

The K-Zoo Kid said:
So basically if you want to do any sort of mods, flash roms, etc. you need to unlock the bootload and root. Thanks a lot for explaining that. I think i understand it now, but just to clarify, if i unlock the bootloader and root will i be able to get the phone back to stock without samsung knowing that i rooted/unlock the bootloader?
Click to expand...
Click to collapse
Yes, to mod/flash roms you need to unlock the bootloader. It's possible that sometime down the road someone may develop a method of gaining root access on the phone without touching it, but it's unlikely given the fact that we can both unlock and lock the bootloader very easily.
Right now, the answer is... more or less. If you make a NAND backup in Clockwork Recovery/Rom manager of your stock ROM, you can restore back to that, fastboot flash the closest thing we have currently to the stock recovery(check development section for this), then relock the bootloader. This will give the phone all appearances of being stock. Unless Samsung has something deep in the system files tracking the number of times you've unlocked/locked(which I doubt, since I'm sure such a system would have been found by now), you should be good to go.
Most people who have returned the phone to Best Buy have noted that they don't even power on the device or check to see if the bootloader is unlocked or if there's a custom recovery on there. But your mileage may vary.

Interesting stuff. I was under the impression that once clockworkmod is flashed there is no way to remove it at this time.
Reading this thread I'm guessing and hoping this is not the case?

I had clockworkmod installed but used rom manager to flash the 2.3.1 update and i've now got the stock bootloader back. I guess the ota update does the same? It would seem that getting back to stock is pretty easy.
Sent from my Nexus S using XDA App

xspyda said:
Interesting stuff. I was under the impression that once clockworkmod is flashed there is no way to remove it at this time.
Reading this thread I'm guessing and hoping this is not the case?
Click to expand...
Click to collapse
My apologies, I posted that before I came to the same understanding regarding the stock recovery.
Like the poster above me mentioned there is a NAND backup of stock 2.3.1 you could restore to which has the stock recovery.
Sent from my Nexus S using XDA App

Thanks for the clarification. I'll do some more reading in the dev section

Thanks a lot, this really helped me out a lot. I will proceed to rooting

So, just want to make sure I have this straight... You unlock the bootloader, load custom recovery, SU, and now phone is rooted. If you lock the bootloader, you lose root?
For me, I'm not big on custom roms since I just don't have time to keep things up to date or participate in the bug process, but I do like to maintain backups with Titanium (my primary reason for rooting). So by locking the bootloader down I will not be able to use Titanium. Furthermore, unlocking the bootloader wipes the device. So is there a reason one would not want to keep the bootloader unlocked? Have I completely misunderstood the system?

[Q] How can I LOCK my Bootloader?

Hey guys,
I want to unlock my bootloader so that I could try some of the awesome ROMs the devs have made/ported to the RAZR M.
I wanted to find out if I could RELOCK my bootloader in the case of needing to take it back to Verizon or Motorola in the case of it being damaged or something. I know how to unroot on the RAZR and how to do it all on my Nexus 7, just cant find hardly anything for this phone.
Thanks in advanced!!!

lukkypuggy said:
Hey guys,
I want to unlock my bootloader so that I could try some of the awesome ROMs the devs have made/ported to the RAZR M.
I wanted to find out if I could RELOCK my bootloader in the case of needing to take it back to Verizon or Motorola in the case of it being damaged or something. I know how to unroot on the RAZR and how to do it all on my Nexus 7, just cant find hardly anything for this phone.
Thanks in advanced!!!
Click to expand...
Click to collapse
Nope it's impossible to relock and once it's unlocked all your warranties are void
Sent from my XT907 using Tapatalk 2

Is this true for any device? Or just certain ones at this point?
Because I can Relock my Nexus 7 and my DROID Incredible just fine, in fact Verizon has accepted one of my former phones that was previously rooted and had the bootloader unlocked, then all was returned to stock of course.

lukkypuggy said:
Is this true for any device? Or just certain ones at this point?
Because I can Relock my Nexus 7 and my DROID Incredible just fine, in fact Verizon has accepted one of my former phones that was previously rooted and had the bootloader unlocked, then all was returned to stock of course.
Click to expand...
Click to collapse
It's specific to this line of devices so far (RAZR HD, RAZR MAXX HD, RAZR M, ATRIX HD). The unlock method (both on the dev. and consumer phones) invloves blowing a physical fuse in the phone which cannot be repaired. Google qfuse if you want to learn more.

Coronado is dead said:
It's specific to this line of devices so far (RAZR HD, RAZR MAXX HD, RAZR M, ATRIX HD). The unlock method (both on the dev. and consumer phones) invloves blowing a physical fuse in the phone which cannot be repaired. Google qfuse if you want to learn more.
Click to expand...
Click to collapse
thanks!

yes! it is!
lukkypuggy said:
thanks!
Click to expand...
Click to collapse
was unlocked now its fn locked and stuck in ap!!!

Yeah, I can confirm that Motorola released an update or something that relocked my previously unlocked boot loader (before anyone asks, yes it was definitely unlocked before ). Unfortunately the update failed on my phone and now I'm stuck in AP Fastboot with an error about "downgraded security version" and "update got_main version failed" errors.
So yeah, definitely possible for Motorola to relock the boot loader.
Attached is a picture of what it looks like now. I don't know of any SBF that would work to fix this.

phantomsniper773 said:
Yeah, I can confirm that Motorola released an update or something that relocked my previously unlocked boot loader (before anyone asks, yes it was definitely unlocked before ). Unfortunately the update failed on my phone and now I'm stuck in AP Fastboot with an error about "downgraded security version" and "update got_main version failed" errors.
So yeah, definitely possible for Motorola to relock the boot loader.
Attached is a picture of what it looks like now. I don't know of any SBF that would work to fix this.
Click to expand...
Click to collapse
Well, that picture speaks for itself, but I have to imagine that your situation is the exception, not the rule. It almost looks like somehting else went wrong with it. The qfuse is a physical fuse from what I have read, so maybe it got bridged, or the system isn't even making it to that check because of some other error.
Very strange indeed.

Coronado is dead said:
Well, that picture speaks for itself, but I have to imagine that your situation is the exception, not the rule. It almost looks like somehting else went wrong with it. The qfuse is a physical fuse from what I have read, so maybe it got bridged, or the system isn't even making it to that check because of some other error.
Very strange indeed.
Click to expand...
Click to collapse
Unless the tiny update did something with the bootloader to possibly IGNORE the qfuse state and simply keep it encrypted, blown qfuse or not. Maybe the final 'hurrah' from Verizon to try to kill off the Razr M development. Kinda reminds me of what they did with the Droid X and Droid 2 when they released the system version .621.. the ONLY thing the update did, was patch the current root methods and change the bootloader a tiny bit (version didn't even change) so it couldn't SBF to ANY previous build. TONS of Droid Xs and 2s were bricked until eventually a 621 SBF was released, and after forever, another root method.
EDIT: I found This thread which describes the same situation, but SBFing back to an earlier version seems to fix it. Apparently, the latest OTA REQUIRES a locked bootloader, unless flashed by other means (possibly TWRP or manual fastboot of img files?)

Skreelink said:
Unless the tiny update did something with the bootloader to possibly IGNORE the qfuse state and simply keep it encrypted, blown qfuse or not. Maybe the final 'hurrah' from Verizon to try to kill off the Razr M development. Kinda reminds me of what they did with the Droid X and Droid 2 when they released the system version .621.. the ONLY thing the update did, was patch the current root methods and change the bootloader a tiny bit (version didn't even change) so it couldn't SBF to ANY previous build. TONS of Droid Xs and 2s were bricked until eventually a 621 SBF was released, and after forever, another root method.
EDIT: I found This thread which describes the same situation, but SBFing back to an earlier version seems to fix it. Apparently, the latest OTA REQUIRES a locked bootloader, unless flashed by other means (possibly TWRP or manual fastboot of img files?)
Click to expand...
Click to collapse
Interesting theory. I personally had to RSD back to 4.1.2 (q66) to install since I had removed the Audio Level Warning apk (which just restores stock apps, kernel, boot image and boot animation but leaves data intact). I then let the update installer run on its own with the stock recovery and it remained unlocked.

Coronado is dead said:
Well, that picture speaks for itself, but I have to imagine that your situation is the exception, not the rule. It almost looks like somehting else went wrong with it. The qfuse is a physical fuse from what I have read, so maybe it got bridged, or the system isn't even making it to that check because of some other error.
Very strange indeed.
Click to expand...
Click to collapse
Yeah, I've only seen this occur on the few devices that had the update fail. I think it's striclty a software thing because it goes back to unlocked after the indviduals were able to recover the phone.

RikRong said:
Yeah, I've only seen this occur on the few devices that had the update fail. I think it's striclty a software thing because it goes back to unlocked after the indviduals were able to recover the phone.
Click to expand...
Click to collapse
Confirming my dad's phone is still unlocked after the update. He didn't do anything with root but I did manage to convince him to root and unlock. Updated yesterday and he's still unlocked. It's gotta be related to the flash failures...
EDIT: stock recovery too...
Sent from my Nexus 7 using Tapatalk 4

sloosecannon said:
Confirming my dad's phone is still unlocked after the update. He didn't do anything with root but I did manage to convince him to root and unlock. Updated yesterday and he's still unlocked. It's gotta be related to the flash failures...
EDIT: stock recovery too...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, possibly. Does anyone know if RSDLite works with a locked boot loader? I tried it earlier and it wouldn't flash, giving an error about GPT partition or something. I didn't really look into it much though, because my phone is still under warranty.

phantomsniper773 said:
Yeah, possibly. Does anyone know if RSDLite works with a locked boot loader? I tried it earlier and it wouldn't flash, giving an error about GPT partition or something. I didn't really look into it much though, because my phone is still under warranty.
Click to expand...
Click to collapse
RSD will work, but you'll only be able to flash the most recent update.

Is my boot loader unlocked? And other questions.

Forgive my lack of knowledge.
Before reading the drawbacks I attempted to unlock the boot loader on my X Compact, I received a few errors and now I am unsure as to whether it is unlocked or not. Is there a way to test this?
I intended to root the phone but I have not root a phone for years, the last one was a Samsung S5 and things seem to have got more complicated since then.
So my questions are, how do I check if the boot loader is unlocked?
If I have lost the DRMs, how do I replace them?
What actual effect does losing them create?
I have read dozens of threads but can't find a straight answer, If you know, I'd appreciate it.
I am still considering the root.

wyzzy said:
Forgive my lack of knowledge.
Before reading the drawbacks I attempted to unlock the boot loader on my X Compact, I received a few errors and now I am unsure as to whether it is unlocked or not. Is there a way to test this?
I intended to root the phone but I have not root a phone for years, the last one was a Samsung S5 and things seem to have got more complicated since then.
So my questions are, how do I check if the boot loader is unlocked?
If I have lost the DRMs, how do I replace them?
What actual effect does losing them create?
I have read dozens of threads but can't find a straight answer, If you know, I'd appreciate it.
I am still considering the root.
Click to expand...
Click to collapse
It's been a while, but I think you open the phone app and dial *#*#7378423#*#*, then go to service info>configuration, and in the info there it will tell you.
If you lost drm, they're gone for good. Back them up first, or no hope. The affect is a loss of certain Sony camera functions.

It says
"Bootloader unlock allowed: Yes"
but I read somewhere that sometimes this does not change after it is unlocked, is there a way to be sure?
What camera functions are lost? I read a lot of talk about it but nobody seemed to be able to pin down what the difference is.
Also how do I back up the DRM?
Im running Oreo

wyzzy said:
It says
"Bootloader unlock allowed: Yes"
but I read somewhere that sometimes this does not change after it is unlocked, is there a way to be sure?
What camera functions are lost? I read a lot of talk about it but nobody seemed to be able to pin down what the difference is.
Also how do I back up the DRM?
Im running Oreo
Click to expand...
Click to collapse
I think that if it is unlocked, it will say "status unlocked" or something. Your message only indicates that it's possible to unlock it, (sometimes it's not). The difference is subtle, but noticeable. There are certain camera features specific to Sony that make the pictures nicer. I never looked too much into it, since I'm not too much into photography. If you aren't too hung up on the finer aspects of photography, you probably won't miss it. Still a good idea to back up, though, just in case. I'm pretty sure you can't do it without downgrading to MM first. Then you can use dirtydirty-cow tool, then upgrade back to O if you want - http://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236 You might be able to do it manually from O with dd command, or something, but I'm not sure... You will need to find a MM ftf, shouldn't be too hard, might even be one on Xperifirm still... Now that I think about it, I think ta backup is possible on newer versions of twrp, but you still have to make the backup, and extract the img from the backup, so maybe not any quicker...

[Q] Flash counter?

Hi.
I just bought myself a used nexus 6p and im thinking of rooting it to get some more customization done
Before i only used Samsung phones which had this flash counter thing and then knox that kept the number of flashes to void the warranty and all. Is there this kind of measure on 6p or it's just the same as it was before {no triangles or anything) when i flash stock and lock the bootloader after i change my mind?

McXred said:
Hi.
I just bought myself a used nexus 6p and im thinking of rooting it to get some more customization done
Before i only used Samsung phones which had this flash counter thing and then knox that kept the number of flashes to void the warranty and all. Is there this kind of measure on 6p or it's just the same as it was before {no triangles or anything) when i flash stock and lock the bootloader after i change my mind?
Click to expand...
Click to collapse
No, only samjunk does stupid **** like that.
If your BL is unlocked which it should be if you are on anything other than stock, you will see a warning message each time you boot the phone. And before you act like you have ocd or something, NO that message can not be removed.

Lawlrus said:
No, only samjunk does stupid **** like that.
If your BL is unlocked which it should be if you are on anything other than stock, you will see a warning message each time you boot the phone. And before you act like you have ocd or something, NO that message can not be removed.
Click to expand...
Click to collapse
I haven't unlocked the bl yet as there was no point since I didn't want to root before I got the answer from you. I know how to read tutorials and I'm very familiar with flashing so that's no probs for me. Doesn't the message disappear after you lock the bootloader? (Just assume that I went to custom ROM didn't like it got back to stock ROM and locked the bl) will the message still be there? Because I think it says 'your phone can't be checked for corruption" but it says so only if the bl is unlocked not all the time after it's been unlocked doesn't it?

McXred said:
I haven't unlocked the bl yet as there was no point since I didn't want to root before I got the answer from you. I know how to read tutorials and I'm very familiar with flashing so that's no probs for me. Doesn't the message disappear after you lock the bootloader? (Just assume that I went to custom ROM didn't like it got back to stock ROM and locked the bl) will the message still be there? Because I think it says 'your phone can't be checked for corruption" but it says so only if the bl is unlocked not all the time after it's been unlocked doesn't it?
Click to expand...
Click to collapse
Right, it shows that message when the BL is unlocked, once you relock your BL that *should* go away, never tried it because I don't plan on even being back on stock with no root.
If you do any modifications to the device even root, or using a stock custom ROM like we have, it is suggested to NOT relock your BL, while on it. Keep that in mind.
You want to go back to full stock to lock it, then reflash the factory image