Database Develop

[Q] First Time Root Quick Question

Hey guys,
This is my first time wanting to root my phone and I wanna do it right. Can anyone provide me whats the best recovery images, mods and so on for rooting my google nexus one (AWS) running froyo with tutorials?
Thanks
Arber

arberthebarber said:
Hey guys,
This is my first time wanting to root my phone and I wanna do it right. Can anyone provide me whats the best recovery images, mods and so on for rooting my google nexus one (AWS) running froyo with tutorials?
Thanks
Arber
Click to expand...
Click to collapse
If want to keep bootloader lock..I would go to the alternate root that is posted.. it can root frf91 and amon-ra recovery and any rom ... bootloader staying lock keeps warranty intact

ilostchild said:
If want to keep bootloader lock..I would go to the alternate root that is posted.. it can root frf91 and amon-ra recovery and any rom ... bootloader staying lock keeps warranty intact
Click to expand...
Click to collapse
If I dont unlock the bootloader what can I not do?

you can root, and flash custom recovery and custom ROM.. jus as the same as unlockin the bootloader, only thing i know you can do with a locked bootloader is fastboot stuff but everything else would be the same... jus warranty stays on phone wiht lock bootloader
this is the alternate way i was talking about
http://forum.xda-developers.com/showthread.php?t=736271

lets say if I want: forum.xda-developers.com/showthread.php?t=730290
how would I do this? For me the warranty doesnt matter

arberthebarber said:
lets say if I want: forum.xda-developers.com/showthread.php?t=730290
how would I do this? For me the warranty doesnt matter
Click to expand...
Click to collapse
If warranty doesnt matter then do it the first and original way do oem unlock, fastboot flash recovery, do nandroid back up then wipe and flash rom...

ilostchild said:
If warranty doesnt matter then do it the first and original way do oem unlock, fastboot flash recovery, do nandroid back up then wipe and flash rom...
Click to expand...
Click to collapse
okay so I just unlocked the bootloader. How do I do the rest

arberthebarber said:
okay so I just unlocked the bootloader. How do I do the rest
Click to expand...
Click to collapse
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Nexus_One

ilostchild said:
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Nexus_One
Click to expand...
Click to collapse
Okay so ive done this successfully lets say if I wanna go back to the original how would I do this?

Once you unlock bootloader you cant relock it it stays unlock.. but there is a Tut on how to go back to stock.. man.. use the search feature..

[Experiment] Avoid the 2.3.3 Bootloader

Just a suggestion and I'm not sure of the long term implications of this, but I was thinking those who want to avoid the hassles of getting the new bootloader that prevents fastboot boot and flash on locked bootloaders could try the following.
Unzip the update patch file to a folder on your computer.
Delete the bootloader.img file.
Use a text editor to open the file called /META-INF/com/google/android/updater-script and edit out/delete the following lines at the very end of the file:
Code:
ui_print("Writing bootloader...");
assert(package_extract_file("bootloader.img", "/tmp/bootloader.img"),
write_raw_image("/tmp/bootloader.img", "bootloader"),
delete("/tmp/bootloader.img"));
Rezip the folder with the altered files in it.
Boot to clockwork recovery and apply the update zip file with CW (since it's now not signed properly and stock won't do it.
We've had success with this type of modification to the update patch file from Google with people who modded /system files (like replacing gmail or the market app) that got failed updates on 2.3.1 and 2.3.2 updates.
I'm a bit pressed for time, but I may try this myself this weekend. I'm not in a big rush to update yet, though. I'm waiting for things like my custom kernel to become 2.3.3 friendly.
I've made a zip file that has the two changes I suggested above if anyone's brave enough to try it: http://dl.dropbox.com/u/432767/NoBo...9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip

Bit late to the party i'm afraid, allready updated and flashed 2.3.3 update zip. I have lost my root and do not want to "fasboot oem unlock" yet...
My bad for being impatient as normal ^^
I will hold any actions and watch what solutions arise if any. Nice to see some methods being worked on

jamiemac1977 said:
Bit late to the party i'm afraid, allready updated and flashed 2.3.3 update zip. I have lost my root and do not want to "fasboot oem unlock" yet...
My bad for being impatient as normal ^^
I will hold any actions and watch what solutions arise if any. Nice to see some methods being worked on
Click to expand...
Click to collapse
Could you not flash back to stock using Odin and then apply the bootloaderless update after? Just an idea . . .

Is there any risk of bricking? If not I don't mind trying it.

Serious_Beans said:
Is there any risk of bricking? If not I don't mind trying it.
Click to expand...
Click to collapse
There is always a risk of bricking especially when playing with the bootloader.

kenvan19 said:
There is always a risk of bricking especially when playing with the bootloader.
Click to expand...
Click to collapse
But we're not messing with the bootloader per se, we're preventing the update script from checking it and reflashing/updating it.
Still, there's always the risk of bricking as you say.

Slightly off topic, buy why go to all the trouble when fastboot oem unlock is painless and 100% reversible? Why intentionally hobble along on a gimped locked bootloader?

mortzz said:
Slightly off topic, buy why go to all the trouble when fastboot oem unlock is painless and 100% reversible? Why intentionally hobble along on a gimped locked bootloader?
Click to expand...
Click to collapse
Because why not try? I'm not being sarcastic, ironic, facetious or anything rude, seriously; Why not? We have a phone that in terms of recent devices has an unprecedented amount of freedom in terms of rooting and unlocking of the device, why not push that to the limit and see just what can be done. Also, lets be honest, having your SD card wiped by the
Code:
fastboot oem unlock
command is kind of sucky. Sure you can copy all of your files to your computer then copy them all back but that isn't a short process and its boring as hell.
EDIT: @distortedloop: You know I trust you man, my point with my earlier comment is that running an outdated bootloader could very easily lead to an unbootable device, moreso than flashing a custom ROM so I was just being as honest and blunt as I could be

I updated the bootloader using:
fastboot flash bootloader bootloader.img
The bootloader stayed unlocked.

jamiemac1977 said:
Bit late to the party i'm afraid, allready updated and flashed 2.3.3 update zip. I have lost my root and do not want to "fasboot oem unlock" yet...
My bad for being impatient as normal ^^
I will hold any actions and watch what solutions arise if any. Nice to see some methods being worked on
Click to expand...
Click to collapse
You can replace the new bootloader in the update with the old bootloader, here's a link for the old bootloader Bootloader_I9020XXJK1

Has it been tested to work properly? It meaning the the old bootloader?
Sent from my MattedBlues CM7 Google Nexus S!

kenvan19 said:
Has it been tested to work properly? It meaning the the old bootloader?
Sent from my MattedBlues CM7 Google Nexus S!
Click to expand...
Click to collapse
I've been using it with 2.3.3 for the past day and it works perfectly, booting CWM and kernels without an OEM unlock.
Sent from my Nexus S using XDA App

Get Root Back With This Restore.
jamiemac1977 said:
Bit late to the party i'm afraid, allready updated and flashed 2.3.3 update zip. I have lost my root and do not want to "fasboot oem unlock" yet...
My bad for being impatient as normal ^^
I will hold any actions and watch what solutions arise if any. Nice to see some methods being worked on
Click to expand...
Click to collapse
if you have clockwork mod use this as a restore and you will have a rooted 2.3.3 its the easiest way to do it.
http://www.mediafire.com/?c1ww7zb837uycbk
just unzip and put the backup folder in your clockworkmod recovery folder boot into recovery and restore 2.3.3 takes 2 minutes and you will boot up with a rooted 2.3.3

also kept my bootloader unlocked. and i can flash back to any of my roms with no hassle keeping everything in tact.

reddv1 said:
You can replace the new bootloader in the update with the old bootloader, here's a link for the old bootloader Bootloader_I9020XXJK1
Click to expand...
Click to collapse
Ah thanks, I've been looking for that...
I'm going to link it in my root without unlock thread to help people who can't root now that they've updated with locked bootloaders.
kenvan19 said:
Because why not try? I'm not being sarcastic, ironic, facetious or anything rude, seriously; Why not? We have a phone that in terms of recent devices has an unprecedented amount of freedom in terms of rooting and unlocking of the device, why not push that to the limit and see just what can be done. Also, lets be honest, having your SD card wiped by the
Code:
fastboot oem unlock
command is kind of sucky. Sure you can copy all of your files to your computer then copy them all back but that isn't a short process and its boring as hell.
EDIT: @distortedloop: You know I trust you man, my point with my earlier comment is that running an outdated bootloader could very easily lead to an unbootable device, moreso than flashing a custom ROM so I was just being as honest and blunt as I could be
Click to expand...
Click to collapse
No worries on the outdated bootloader....that's why I said "I don't know the long term implications of this."
Everything you said, I couldn't have said better myself.

charlieb620 said:
if you have clockwork mod use this as a restore and you will have a rooted 2.3.3 its the easiest way to do it.
http://www.mediafire.com/?c1ww7zb837uycbk
just unzip and put the backup folder in your clockworkmod recovery folder boot into recovery and restore 2.3.3 takes 2 minutes and you will boot up with a rooted 2.3.3
Click to expand...
Click to collapse
But that defeats the whole point of not wanting to lose and restore your data, since the nandroid will write over all your stuff...
It also doesn't help those who end up with a locked bootloader and no root, since they can't access clockwork.

When I did it I kept my root and unlocked bootloader. If people didn't rush to update than they would have kept everything. I was able to restore my apps and all when I updated to the rooted 2.3.3
Sent from my Nexus S using XDA App

Will relocking bootloader wipe the phone?
I did "fastboot oem unlock" and everything is erased (it's not big deal as I always backup data).

mingkee said:
Will relocking bootloader wipe the phone?
I did "fastboot oem unlock" and everything is erased (it's not big deal as I always backup data).
Click to expand...
Click to collapse
No, the lock won't wipe it, just the unlock.

mingkee said:
Will relocking bootloader wipe the phone?
I did "fastboot oem unlock" and everything is erased (it's not big deal as I always backup data).
Click to expand...
Click to collapse
distortedloop said:
No, the lock won't wipe it, just the unlock.
Click to expand...
Click to collapse
Yes it will. Both locking and unlocking (via fastboot oem lock/unlock) will wipe your phone.

Unlock BL on Sprint Moto X

I'm considering unlocking my bootloader through Motorola. Other than voiding my warranty, is there any reason I shouldn't do it? What are your thoughts?

shaya4207 said:
I'm considering unlocking my bootloader through Motorola. Other than voiding my warranty, is there any reason I shouldn't do it? What are your thoughts?
Click to expand...
Click to collapse
That's the only negative reason...... warranty. Other then once you start messing with the system, it will break being able update via the OTA's. SO..... I would recommend doing a backup after unlocking the bootloader, flashing recovery, and the first boot up. Therefore you'll have a backup of 100% stock not midified. Then as long as custom recoveries will flash the OTA's, you can always have a quicke easy way to upgrade. Unlocking the bootloader also wipes everything. That's all I got.

gokart2 said:
That's the only negative reason...... warranty. Other then once you start messing with the system, it will break being able update via the OTA's. SO..... I would recommend doing a backup after unlocking the bootloader, flashing recovery, and the first boot up. Therefore you'll have a backup of 100% stock not midified. Then as long as custom recoveries will flash the OTA's, you can always have a quicke easy way to upgrade. Unlocking the bootloader also wipes everything. That's all I got.
Click to expand...
Click to collapse
So, by unlocking the bootloader you can't get any updates???
Sent from my XT1056 using Tapatalk

shaya4207 said:
So, by unlocking the bootloader you can't get any updates???
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
I think he meant you are able to flash the "zip" updates (via custom recovery).
Afaik, when you use a custom recovery, you should not take an update via OTA, or else your phone will boot loop.

xitake said:
I think he meant you are able to flash the "zip" updates (via custom recovery).
Afaik, when you use a custom recovery, you should not take an update via OTA, or else your phone will boot loop.
Click to expand...
Click to collapse
Oh, thanx, I really wanna do it, but I wanna make sure that I'm not getting screwed first
Sent from my XT1056 using Tapatalk

shaya4207 said:
Oh, thanx, I really wanna do it, but I wanna make sure that I'm not getting screwed first
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Unlocking your bootloader shouldn't affect your ability to take OTAs. Rooting or installing a custom recovery certainly might. But just unlocking the bootloader without then installing a custom recovery or rooting isn't very common. Most folks unlock the bootloader for one or both of those reasons.
http://forum.xda-developers.com/showthread.php?t=2446515 seems to have a lot of good info on getting a moto x back to stock, at which point you should be able to take an OTA. I've never used RSD Lite, just done various combinations of fastboot and clockworkmod/twrp (on other phones), but it appears either approach can work - which makes sense since RSD Lite seems to use fastboot behind the scenes.

jnichols959 said:
Unlocking your bootloader shouldn't affect your ability to take OTAs. Rooting or installing a custom recovery certainly might. But just unlocking the bootloader without then installing a custom recovery or rooting isn't very common. Most folks unlock the bootloader for one or both of those reasons.
http://forum.xda-developers.com/showthread.php?t=2446515 seems to have a lot of good info on getting a moto x back to stock, at which point you should be able to take an OTA. I've never used RSD Lite, just done various combinations of fastboot and clockworkmod/twrp (on other phones), but it appears either approach can work - which makes sense since RSD Lite seems to use fastboot behind the scenes.
Click to expand...
Click to collapse
Thanx
Sent from my XT1056 using Tapatalk

[Q] Entering recovery

Hi, maybe a noob question but, ever since I rooted my Moto X I cannot enter recovery mode. I believe that when the phone reboots on recovery mode it mounts /system as writable, but I wonder if there's a way to enter recovery mode at all after rooting. I have a locked bootloader on 4.2.2.

detesto said:
Hi, maybe a noob question but, ever since I rooted my Moto X I cannot enter recovery mode. I believe that when the phone reboots on recovery mode it mounts /system as writable, but I wonder if there's a way to enter recovery mode at all after rooting. I have a locked bootloader on 4.2.2.
Click to expand...
Click to collapse
yea you can still boot into stock recovery. just boot to the bootloader via volume down + power, then hit the volume down button only till you select recovery then hit volume up. and there is the stock recovery. enjoy.

You'd have to flash back to the stock recovery. However, I think you lose access to a writable system which leads to setting write protection off for good.

nhizzat said:
You'd have to flash back to the stock recovery. However, I think you lose access to a writable system which leads to setting write protection off for good.
Click to expand...
Click to collapse
i know for a fact you can enter the stock recovery after you root your device. i have done it many times before i flashed TWRP over my stock recovery
also when you root 4.4 you dont change the stock recovery so you should still be able to enter it.

That only applies if you have a Dev Edition or an unlocked bootloader.

nhizzat said:
That only applies if you have a Dev Edition or an unlocked bootloader.
Click to expand...
Click to collapse
well you learn something new every day.
did not know that having a unlocked bootloader would change if you could enter stock recovery after root or not.
thank you for the information.
guess i should of played around with the rooting and stuff before i unlocked my bootloader so i had some more knowledge on locked bootloader processes

nhizzat said:
You'd have to flash back to the stock recovery. However, I think you lose access to a writable system which leads to setting write protection off for good.
Click to expand...
Click to collapse
That's what I was thinking, when I enter to fastboot and select recovery, it just boots to system. I guess I should unlock the bootloader then, I feel a little paranoid not having recovery

detesto said:
That's what I was thinking, when I enter to fastboot and select recovery, it just boots to system. I guess I should unlock the bootloader then, I feel a little paranoid not having recovery
Click to expand...
Click to collapse
depending on what carrier your device is with depends on if you can unlock the bootloader or not.
if you cant unlock it then you can use safestrap here is the link
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/

dray_jr said:
depending on what carrier your device is with depends on if you can unlock the bootloader or not.
if you cant unlock it then you can use safestrap here is the link
http://rootzwiki.com/topic/104161-recovery-locked-safestrap-recovery-v365-2013-11-13/
Click to expand...
Click to collapse
I can unlock, I'm on telcel (Mexico) and I already checked the motorola web site. It's just that reading motorola saying I will no longer have warranty is a little harsh and I tried postponing unlocking it as long as I could (or at least until there's a ROM that catches my eye).
I looked into safestrap but it seems not many ROMS support this yet, or am I in the wrong here?

detesto said:
I can unlock, I'm on telcel (Mexico) and I already checked the motorola web site. It's just that reading motorola saying I will no longer have warranty is a little harsh and I tried postponing unlocking it as long as I could (or at least until there's a ROM that catches my eye).
I looked into safestrap but it seems not many ROMS support this yet, or am I in the wrong here?
Click to expand...
Click to collapse
rooting your phone removes stock recovery. it actually hijacks the stock recovery. it is part of the exploit giving you root. SS has worked on many devices even tho it may not say that it is supported. hashcode might be able to change something in SS to make it more compatible for your device if it isn't already.

detesto said:
I can unlock, I'm on telcel (Mexico) and I already checked the motorola web site. It's just that reading motorola saying I will no longer have warranty is a little harsh and I tried postponing unlocking it as long as I could (or at least until there's a ROM that catches my eye).
I looked into safestrap but it seems not many ROMS support this yet, or am I in the wrong here?
Click to expand...
Click to collapse
Technically, you already lost your warranty by rooting the phone. If you can unlock your bootloader, do it. That alone will save your ass more than a custom recovery.

Re locking boot loader.

Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!

H4X0R46 said:
Hello! I just got a nexus 6 a few days ago, and I love this phone! However, I just read on here that relocking your bootloader is a bad idea? Well, I rooted my device and installed PAC ROM on it, then reflashed a stock image back to my nexus and relocked the bootloader, my phone is fine, no bootloops and no issues, does this pose a problem with OTA updates? Thanks! I really need to know because i would NOT wanna brick this thing! Thanks!
Click to expand...
Click to collapse
Thing is, when your bootloader is unlocked, the device is almost unbrickable. Also, you can be unlocked, 100% stock and still get OTA's if you want. If you have a locked bootloader, mess something up and end up in a bootloop, and can't boot to android, you're stuck.

Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?

H4X0R46 said:
Are you saying that OTA updates work even if your boot loader is open? Does it just check your system files and recovery? In theory, if I did an OTA update right now, and my bootloader was unlocked, it would install without problems?
Click to expand...
Click to collapse
Yes to all your questions.
Unlock it, its free insurance and wont change or harm a thing.

you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.

simms22 said:
you can lock/unlock your bootloader anytime you want actually, you just have to make sure that you relock your bootloader sfter making sure that you can boot properly first. because if you can't boot, and your bootloader is locked, then you are just as good as bricked. because now, to unlock your bootloader, you have to enable allow oem unlock. and if you cant boot, you cant do that.
Click to expand...
Click to collapse
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.

danarama said:
That said, since 5.1.1, doesn't "allow oem unlock" remain ticked / selected after a reboot now? If so, it's fine to relock it, even if it doesn't boot if that is ticked.
Click to expand...
Click to collapse
Yes, but in the case of an "accidentally" wiped OS, well, you know.

Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6

Evolution_Tech said:
Yes, but in the case of an "accidentally" wiped OS, well, you know.
Click to expand...
Click to collapse
Well it shouldn't matter. When you tick that box, it writes the change to mmcblk0p18, which is OS independent. Now that booting the rom doesn't revert that partition, if it is ticked once, it shouldn't matter if there is an OS at all.

H4X0R46 said:
Alright guys, so I won't ever run into a problem with an OTA update with the bootloader unlocked? Thanks! You guys are awesome!
Sent from my Nexus 6
Click to expand...
Click to collapse
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.

cam30era said:
Correct. Bootloader status has no effect on OTA. Updated script checks boot.img (kernel), system.img, and recovery. All have to be unmodified. No root, no unencrypted kernel, stock 100%.
Click to expand...
Click to collapse
Scripts don't check recovery. It's just the OTA zip won't work without it.

-Jonny- said:
here you go!
Click to expand...
Click to collapse
Correct. Just taking this shortcut.

Great! Thanks guys! Appreciate all the help and support on this! I would HATE to brick a $700 device! Haha
Sent from my Nexus 6

Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?

H4X0R46 said:
Real quick easy noob question, no point in making a thread just for this so I'm asking here, is the Nexus 6 CPU an arm or arm64?
Click to expand...
Click to collapse
N6 is ARM. Arm 64 is for 64 bit devices such as the N9.

Clarification question
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?

alryder said:
A question for clarification, as long as the bootloader is already unlocked, the "OEM Unlocking - Allow the bootloader to be unlocked" setting under Developer options doesn't affect anything?
Click to expand...
Click to collapse
Correct.