Restore Nexus One for Dummies? - Nexus One Q&A, Help & Troubleshooting

I bought my phone used and I used the universal androot app to root it without locking the bootloader. I want to take it back to just the way it was when it came out of the box. Are there easy to follow step by step directions anywhere? I've searched but everything says it assumes you know how to use adb and fastboot. I don't. Do directions exist for dummies? It sure was a piece of cake to restore my old iPhone.

Yeah, I had the same problem a few weeks ago. My suggestion is look at some tutorials for installing custom ROMs and then reverse engineer those once you've learned how to use adb and fastboot.

You mean something like this -->
http://androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/

cymru said:
You mean something like this -->
http://androidspin.com/2010/05/06/guide-unrooting-your-nexus-one-its-like-it-never-happened-almost/
Click to expand...
Click to collapse
Kind of like that, but this part confused me.
"Once you have this installed, add a folder path for the ADB utility to your System Environment Variables “path” variable."

Ok, when I get to step 7, the command prompt says "FAILED (remote: not allowed)"
What's up with that? HELLLLLLP!

I did a manual erase user data, but now when I go to Type 'fastboot flash userdata userdata.img'
the command prompt tells me FAILED (remote: signature verify fail)
Help?

Okay, sounds like you're panicking.
There's kinda like a fix everything button, and that's a passimg.
Grab it here: (remove the spaces, I'm not allowed to post links)
w w w . megaupload . com/?d=7JQU3MV0
All you gotta do is put that on the root of your SD card. Boot into bootloader mode (hold down trackball when powering) and select recovery. That's all. It'll detect passimg, and fix everything.
The caveat here, is that you'll be on EPE76 - which was super duper annoying to actually upgrade from (but I eventually found a FRF91 rom that worked - I'll see if I can find it and post it for you).
But yeah. Download that. Fix everything. Enjoy

From EPE76 can't you just do an OTA update to upgrade to Froyo? And what exactly does this passimg do and how does it work? I got adb and fastboot working and everything, I just get errors when I try to flash. Do you have to have an unlocked bootloader to do this stuff? I just used the universal androot app to gain root, so the bootloader wasn't actually unlocked.

No. the passimg will just automatically flash radio, recovery, etc. so you don't have to. If you've got it working manually now, no need to use it.

The passimg does pretty much what you were asking about. The Nexus One has the code name "Passion", so "pass/img" is the original factory shipping image for the Nexus One. The OTA should then** come to your phone, maybe in a few hours, but maybe not for a while.

And if I do the passimg it shouldn't screw up the phone since I'm already running froyo and this will kick me back to 2.1?

Read - Nexus One Wiki, "Unroot / Restore your Nexus", PASSIMG.ZIP method.
Written especially to avoid threads like this one.

Well it worked perfectly and now I'm running 2.1 EPE76. Is there a way to force it to update to Froyo?

you should be able to open up your dialer and type
*#*#CHECKIN#*#*
or
*#*#2432546#*#*

scgolfer7 said:
you should be able to open up your dialer and type
*#*#CHECKIN#*#*
or
*#*#2432546#*#*
Click to expand...
Click to collapse
That's a negative. It just says checkin result success, but doesn't download any update. When I go to about phone and system updae it says my system is up to date.
If I was reading correctly I should upgrade from EPE76 to FRF85B and then I should get the FRF91 OTA? Can anyone confirm this?

I got everything working and I'm back to completely stock Froyo FRF91 and I just wanted to thank everyone who contributed to this thread for guiding my annoying newbie ass through the process and teaching me a wealth of knowledge about the Android OS along the way. Thanks again!

For future reference, if you want to restore your phone while having no issues accessing it, just get Rom Manager. Use it to download and install a stock unrooted Froyo rom (just make sure to select wipe data and do not select the rooting options).
Very easy to restore. The passimg method comes in very handy if you cannot even boot into the OS.

Related

n1 issues

hi everyone, im new to these forums. i want to love my n1, but cant. my service is horrible here in miami florida. so bad that tmobile keeps giving me free months of service instead of a solution.
i was told about holding the phone a certain way, but its so unnatural. but i understand that a few firmware updates helped out the signal issues. me and my sons nexus ones are fluctuating 20-50 dB's at a time.
so i try to root using the cyanogen wiki's instructions. the second i type in adb devices into my windows 7 cmd window, i get the following. "adb is not recognized as an internal or external command"
i repeated the steps in the wiki and have no idea what i am doing wrong.
can anyone assist please?
Mod, if i posted in the wrong section i am sorry; feel free to move thread.
thanks all!
Here bro, this might help... "How to set up adb"
http://theunlockr.com/2010/01/02/how-to-root-the-nexus-one/
Did you run the adb command from the sdk directory?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
You need to download the SDK and use the adb from the SDK directory....
MaximReapage said:
Did you run the adb command from the sdk directory?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
No I used the windows cmd window. I saw the android cmd window but it wouldn't let me type in it. Was I supposed to type in the android window?
Before you go and unlock the phone and install cyanogen, are you sure you want to go down that road? I don't think there are any reception improvements in any of the custom ROMs, so if that's what you are hoping for you might be disappointed.
You may lose your warranty if you do it, and you are going to permanently lose the over-the-air upgrade system that Google uses to push upgrades out with.
sheek360 said:
No I used the windows cmd window. I saw the android cmd window but it wouldn't let me type in it. Was I supposed to type in the android window?
Click to expand...
Click to collapse
You need to read up a lot more on how your computer works, and directory structures, and cmd windows and all that. If you are already confused you could just end up breaking your phone. First thing is to install the SDK. Get that done, then read some more, etc. Do it slowly.
Clarkster said:
You need to read up a lot more on how your computer works, and directory structures, and cmd windows and all that. If you are already confused you could just end up breaking your phone. First thing is to install the SDK. Get that done, then read some more, etc. Do it slowly.
Click to expand...
Click to collapse
Thanks for the heads up. The sdk is definately installed.
I heard that the other radios perform better. I need a miracle, I drop 60% of my calls according to tmo. So does my sons n1's. My daughters cliq and wife's bold9700 are always on 3g
What Baseband version do you have installed on your phone? It's under Settings -> About phone.
You should be running the newest radio firmware already I would think.
PrawnPoBoy said:
What Baseband version do you have installed on your phone? It's under Settings -> About phone.
You should be running the newest radio firmware already I would think.
Click to expand...
Click to collapse
I don't know it off the top of my head. But its definately current.
Well if you want to check it out, I believe "32.26.00.24U_4.04.00.03_2" is the newest. If that's what your phone has then I don't think there is any value in unlocking.
An update from Google should be coming or announced before the end of the month, so maybe it'll have some fixes for you. If not, than at that point I would go ahead and unlock it.
i went ahead and successfully unlocked the boot loader. im trying to load the recovery.img via a terminal app on my phone but i get a message saying permission denied. i heard that there was a way of loading the recovery.img through rom manager, so i tried it.i got a message saying an error occurred while attempting to run privileged commands.
any ideas?
thanks!
seems like i dont have superuser.....
Yup, when I type su in terminal I get a message telling me that I don't have those privaleges. Any ideas? I'm Googling but can't find results.
i find the instructions in here relatively newb friendly. But read all carefully before rushing into action.
Stock to Root:
http://forum.xda-developers.com/showthread.php?t=636795
Recovery Image:
http://forum.xda-developers.com/showthread.php?t=611829
CM ROM (if that is what you would like to have)
http://forum.xda-developers.com/showthread.php?t=623496
and... do all the above first, before you mess with the radio image. all over the above is relatively safe/cannot brick your phone but wrongly flashing radio image can brick your phone permanently (especially if you run out of power or pull the battery during the radio update process)
Thanks. I'm er27. Do I flash with or without himen?
to make it very simple, i'd just recommend first:
1) flash Amon_Ra's recovery image 1.70 (i sent you the link earlier)
2) flash Cyanogen CM5.0.6 (I sent you the link earlier)
3) flash CM's google-addon (on the same page)
CM5.0.6 includes Himem, no need to flash separately.
See how it goes.... THEN you can try flashing radio to EPE54B, but please read all related to that careful. the command is simple, but if you pull your battery during the update, or the phone runs out of power, or you otherwise try to interrupt the process, your phone WILL BE permanently broken. Sometimes the radio update takes a long while (15 min or so), and it seems unresponsive, then you have 2 automatic reboots - those moments can be frightening. best would be to leave the phone plugged into the power socket while you doing it
shmigao said:
to make it very simple, i'd just recommend first:
1) flash Amon_Ra's recovery image 1.70 (i sent you the link earlier)
2) flash Cyanogen CM5.0.6 (I sent you the link earlier)
3) flash CM's google-addon (on the same page)
CM5.0.6 includes Himem, no need to flash separately.
See how it goes.... THEN you can try flashing radio to EPE54B, but please read all related to that careful. the command is simple, but if you pull your battery during the update, or the phone runs out of power, or you otherwise try to interrupt the process, your phone WILL BE permanently broken. Sometimes the radio update takes a long while (15 min or so), and it seems unresponsive, then you have 2 automatic reboots - those moments can be frightening. best would be to leave the phone plugged into the power socket while you doing it
Click to expand...
Click to collapse
damn you just scared me straight. is it possible that future cm roms include new radios?
sheek360 said:
damn you just scared me straight. is it possible that future cm roms include new radios?
Click to expand...
Click to collapse
just achieved root! but my google apps arent in the phone. gotta get epe54b in
All done. Thank you all for your help!8

Froyo Fatigue

Dear members, Like always i first of all would like to thank you all for the great effort and hard work all of you have put into this wonderful site.
I am a noob with a rooted nexus one. ( i was begining to think of myself a step above noob recently but trying to update my phone to froyo made me realize i still am a noob.
I so want to update to froyo NOW without waiting for the OTA update but i just cant figure out how to. i downloaded the FR50 ( with and without radio ) but both failed. SO i figured it must be due to stock recovery. So i went to Amon Ra's thread to flash the new recovery image using terminal but after placing the image on the sdcard when i enter the flash image command , it says " image not found " when its most definitely there on the sdcard and i checked the spellings over and over again but it just wont flash and as a result i still cant enjoy froyo
I am sooooo sorry if i posted this thread in the wrong section but i really could use some guidance from the most intelligent Android people i know .
Regards,
Nadeem
It's basically a 4 step process, but make sure you did all of them.
1) Unlock Bootloader
2) Apply Root. I used this method, quick and painless: http://android.modaco.com/content/g...-erd79-frf50-superboot-rooting-the-nexus-one/
3) Flash Recovery using ADB.
3a) Recommended: Do a Nandroid backup image of your Stock 2.1u1, just in case something wierd happens during your flash.
4) Flash FRF50 ROM w/Radio. You want the version with the new Radio, as I believe 2.2 won't work with the 2.1 radio without tinkering.
ATnTdude said:
as I believe 2.2 won't work with the 2.1 radio without tinkering.
Click to expand...
Click to collapse
It works for the most part, but you'll get a crash if you try to record video without updating the radio.
Wait...you put the Recovery image on your SDCard? It should be on your harddrive. You push the the image from the HDD to the phone. Unless there's some other way I don't yet know about.
caliwolv said:
It works for the most part, but you'll get a crash if you try to record video without updating the radio.
Click to expand...
Click to collapse
Well, I'm glad I at least the gist of the material is sticking. I browse this place just about every day trying to keep myself from bricking my phone. If I do, it's back to my Nokia E71, and being forced to use Symbian after Android 2.2...not pleasant at all.
I highly appreciate the super quick response ATnTDUde
The first two steps in your method describe how to get root i presume....
Actually i already rooted my Nexus 1 and i am fairly certain the bootloader is unlocked too ( i see a small padlock unlocked every time i turn my N1 on)
Oh so i am going to have to flash the AMon Ra recovery image using ADB. actually on Amon's thread there was another method of flashing the image using terminal which i tried and failed at. I'll most definitely try ADB method once i get back home.
Just wanted to ask you a quick question Sir.
Once i flash Amon Ra's recovery image i assume i wont be getting any OTA updates from google ???? right ....
Also if i want to go to the stock recovery image ( is there a way to do so ? ) will i start getting OTA updates
Please some one help with the two questions above coz i cant start the process without knowing.
nadeemhasnaat said:
......
Once i flash Amon Ra's recovery image i assume i wont be getting any OTA updates from google ???? right ....
Also if i want to go to the stock recovery image ( is there a way to do so ? ) will i start getting OTA updates
Click to expand...
Click to collapse
1) right
2) yes
ATnTdude said:
Wait...you put the Recovery image on your SDCard? It should be on your harddrive. You push the the image from the HDD to the phone. Unless there's some other way I don't yet know about.
Click to expand...
Click to collapse
Yeah, its very easy.
adb shell flash recovery /sdcard/Amon-Ra.img
or whatever the thing is.
or you can
fastboot flash recovery C:\android\tools\wha\tev\er\Amon-Ra.img
The path just has to be correct wheter o

[Q] Questions about ADP1

so my friend recently gave me his old G1, and i did some searching around and discovered that HTC made a dev version. now, being new to android, i have absolutely no clue what the differences are. i want to update my adp1 to froyo, but i get lost when i look up stuff about rooting or whatever. can anyone dumb it down for me or link me to an easy to follow walkthrough? i'm not sure whether or not guides for the g1/dream can be applied to the dev version. please help a noob in need
ADP1 shipped with bootloader 0.95.3000 whereas non-ADP shipped with 0.95.0000. 3000 let you flash unsigned images. That is the difference.
Note that all 0.95 SPLs are obsolete now.
dhkr123 said:
ADP1 shipped with bootloader 0.95.3000 whereas non-ADP shipped with 0.95.0000. 3000 let you flash unsigned images. That is the difference.
Note that all 0.95 SPLs are obsolete now.
Click to expand...
Click to collapse
so how would i go about putting 2.2 on it?
http://forum.xda-developers.com/showthread.php?t=831139
http://forum.xda-developers.com/showthread.php?t=717874
http://forum.xda-developers.com/showthread.php?t=811620
dhkr123 said:
http://forum.xda-developers.com/showthread.php?t=831139
http://forum.xda-developers.com/showthread.php?t=717874
http://forum.xda-developers.com/showthread.php?t=811620
Click to expand...
Click to collapse
x_x wow thanks
going to try and decipher these forum posts now
http://wiki.cyanogenmod.com/index.php?title=Dream:Rooting
^
That is the way that most of us rooted our phones. It's reasonable simple, downgrade, type teldnetd, open telnet app, install a recovery, update radio, set boot partitions(if using customMTD)/install danger SPL, and flash CM. If you would like to get as much performance as possible from your phone, I suggest using ezterry's rom, but for that you will need to update the radio and spl through adb and fastboot, which is a little bit more advanced. If you need anything don't be afraid to ask.
mejorguille said:
http://wiki.cyanogenmod.com/index.php?title=Dream:Rooting
^
That is the way that most of us rooted our phones. It's reasonable simple, downgrade, type teldnetd, open telnet app, install a recovery, update radio, set boot partitions(if using customMTD)/install danger SPL, and flash CM. If you would like to get as much performance as possible from your phone, I suggest using ezterry's rom, but for that you will need to update the radio and spl through adb and fastboot, which is a little bit more advanced. If you need anything don't be afraid to ask.
Click to expand...
Click to collapse
hm so i'm looking at the instructions on the link you gave me; i won't be able to login to my google account without a 3g plan huh? i guess i'll have to get that before i do anything?
and it doesn't matter that i have the ADP1 instead of just a regular G1?
pandapus said:
hm so i'm looking at the instructions on the link you gave me; i won't be able to login to my google account without a 3g plan huh? i guess i'll have to get that before i do anything?
and it doesn't matter that i have the ADP1 instead of just a regular G1?
Click to expand...
Click to collapse
Well in that case use this link, since your bootloader is already factory unlocked, you can use the fastboot commands to flash a recovery image. You will need to have adb and fastboot from the android sdk installed on your computer. There are guides in the rom bible on the development forum to help you with that.
EDIT: and try this trick for skipping the initial login so that you can use wifi to sign in if you have to.
mejorguille said:
Well in that case use this link, since your bootloader is already factory unlocked, you can use the fastboot commands to flash a recovery image. You will need to have adb and fastboot from the android sdk installed on your computer. There are guides in the rom bible on the development forum to help you with that.
EDIT: and try this trick for skipping the initial login so that you can use wifi to sign in if you have to.
Click to expand...
Click to collapse
unfortunately that trick does not work with the ADP1 =(
i flashed with DREAIMG.nbh and cannot bypass the setup thing; then i discovered this article: http://forum.xda-developers.com/showthread.php?t=532719
which i completed up until the "installing drivers" step that i don't know how to complete because the computer doesn't even recognize that a device is plugged in, so now my phone thinks it's a G1 and i cannot get past the login screen and i cannot complete the ADB setup with my phone. what do i do?
---------------
EDIT: alright so i bypassed the login by swapping SIMs with a friend who has a 3G plan, but anyhow, when i plug it into my comp, i don't get an option to "Install drivers from my pc" according to the guide i referenced earlier in this post....

[Q] PASSIMG.ZIP Really Screwing Me Up

I've rooted my Nexus One a long long time ago, and eventually reverted to it's original state. Let's skip ahead a year..
I wan't to use my Nexus One again until I can get my hands on a Nexus 4. I'm trying to root this bad boy, but run into a problem with every method. I got the one click method to work, but it wouldn't boot up. And when I try to go into Bootloader for recovery, it checks for the PASSIMG.ZIP file and then updates. If I click no, it makes no difference, it doesn't let me do anything. Updating will restore the phone to stock(unrooted). So I deleted PASSIMG.ZIP from the SD card. Ever since, I can actually click on Recovery, but I run into trouble(see further below). S is ON btw, I don't remember what this was, but I'm sure I had it OFF before? I have been using an iPhone for the past year and a half, so I apologize for being a noob. I'm not to tech savvy when it comes to these terms, either.
Short explanation:
One Click Root - I can root it, but when I go to Bootloader Recovery it shows the Android guy and a triangle around !
Using the old school method using Windows terminal, recovery-clockwork-5.0.2.0-passion.img was flashed without problem.
But I can't access Recovery!
In the end I'm trying to at least have an ICS ROM, or Jellybean(Really wanna try Google Now or whatever) if possible.
Check the Wiki for instructions on how to bootloader unlock your phone. Much easier. You can then flash everything you want using fastboot (so make sure you have the fastboot driver installed correctly).
Btw, the triangle means you still have stock recovery.
tommert38 said:
Check the Wiki for instructions on how to bootloader unlock your phone. Much easier. You can then flash everything you want using fastboot (so make sure you have the fastboot driver installed correctly).
Btw, the triangle means you still have stock recovery.
Click to expand...
Click to collapse
The unlock padlock icon means the bootloader is unlocked, correct? I've done that. And I actually went through that, and flashed the custom Recovery, still the same result. I'll retry it again.
I figured it out, but I don't get it...
I did this in kind of a different route, so just incase someone runs into a similar problem some how:
I rooted the phone using the one click root software on a windows PC, the N1 was successfully rooted.
However, same error recovery, even after adb flashing recovery(followed wiki and unlockr tutorial).
What I did different to fix the issue, was after the root, I downloaded Rom manager(yes I've done this before too, but...), I flashed the recovery via Rom Manager. After it didn't work(sadface).
I tried it again, but just out of frustration I re-flashed it after flashing. So I flashed the recovery twice, back to back. And poof, I check bootloader, go into recovery, and there it is(just like it used to be).
Close this I guess, (an embarrassing)problem has been solved.

[Q] First Nexus

So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Cf auto root does not remove all data per se, but unlocking your phone will if it is not.. And it's part of the process.
Rooting probably doesn't affect OTAs, and if it does, can easily be undone.
Yes, I haven't found a common root app that isn't compatible.
Dankchild said:
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Click to expand...
Click to collapse
1. No it does not wipe your data unless your bootloader was locked.
2. It has no effect. You'll be able to accept the OTA and lose root (you can enable a survival script).
3. Yes.
Dankchild said:
So this is my first Nexus device. I'm coming from and S4 followed by a Note 3 so I'm kinda used to the samsung environment and don't want to screw anything up. I have a couple of questions.
First, if I root with CF-Auto Root, does the tool wipe all of the current data?
Second, how will rooting the phone affect the OTA updates and their availability?
Third, are the root apps already compatible with 5.0/Nexus 6?
Thank you!
Click to expand...
Click to collapse
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
TheSkillfulTroll said:
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
Click to expand...
Click to collapse
People modify the OTA zip to remove the abort of installation if any system files are modified/removed. Of course this can lead to problems, but can also be successful most of the times. Depends on what the user modifies.
Nexus Root Toolkits, I highly do not encourage users to use this. As easy as they are, they prevent users from learning about fastboot and adb. They are essential things to learn and relying on a program to do them for you is not good practice especially when it is quite easy to do it manually. If everybody used the toolkit then no body would understand how its done.
The part about custom ROMs, I recommend using custom ROMs. There are many to browse through, it depends on what you're looking for. Its very exciting to look at all the ROMs to select one to try, just to be eager to try another ROM for fun.
You can read more about toolkits @ http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Very good read.
zephiK said:
People modify the OTA zip to remove the abort of installation if any system files are modified/removed. Of course this can lead to problems, but can also be successful most of the times. Depends on what the user modifies.
Nexus Root Toolkits, I highly do not encourage users to use this. As easy as they are, they prevent users from learning about fastboot and adb. They are essential things to learn and relying on a program to do them for you is not good practice especially when it is quite easy to do it manually. If everybody used the toolkit then no body would understand how its done.
The part about custom ROMs, I recommend using custom ROMs. There are many to browse through, it depends on what you're looking for. Its very exciting to look at all the ROMs to select one to try, just to be eager to try another ROM for fun.
You can read more about toolkits @ http://forum.xda-developers.com/galaxy-nexus/general/dangers-tool-kits-one-click-root-t1469909
Very good read.
Click to expand...
Click to collapse
the toolkit helps alot of new comers who have no idea on what to do, sure they can try the manual way, but doing so can end up very bad as its not easy to revert, while the toolkit helps by being able to bring you back from bricks. i started off using the toolkit and now i just use flashify for rom installations, if anything goes wrong (a brick) i just have tbe option to use the toolkit to set me back to pure stock and factory condition.
TheSkillfulTroll said:
the toolkit helps alot of new comers who have no idea on what to do, sure they can try the manual way, but doing so can end up very bad as its not easy to revert, while the toolkit helps by being able to bring you back from bricks. i started off using the toolkit and now i just use flashify for rom installations, if anything goes wrong (a brick) i just have tbe option to use the toolkit to set me back to pure stock and factory condition.
Click to expand...
Click to collapse
Its very easy to do manually, if it was a long and tedious step such as G1 rooting or manually exploiting a phone then a toolkit is reasonable.
For Nexus 6, its as simple as.
1. install drivers & fastboot.
2. bootloader mode (vol down + power)
3. fastboot oem unlock
4. fastboot flash recovery <name-of-recovery>.img
5. flash supersu
A very good sticky guide is posted, http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
And we all know that regardless if you use a Root Toolkit, you MUST read before you do anything.
Toolkit doesn't really help you bring you back from bricks, in fact I would argue that it does the opposite. You're relying on a program to do what you're supposed to do. In my experience of helping people in XDA forums, they've used toolkits and got themselves into bad positions and wasn't sure how to fix their problem or the toolkit soft-bricking their device. They had to learn fastboot / adb to resolve their issue.
Read the dangers of toolkits, they're not as fancy as people view it to be. Its not difficult to do the tasks manually. Very easy to do. I was able to root/unlock my N6 in a minute since I already had the environment set up.
Think of it this way, you have math homework. You can either go input it into the calculator and have the answer. Congrats, you have the answer but did you understand how they got to that step? No not really.
Its imperative for any user on XDA to learn the fastboot/adb step, its not difficult as I've mentioned time and time again. It takes some reading, but it'll save you time because later down the line you'll understand why you did what you did and you can get yourself out of situations instead of going to Q&A and asking for someone help on how to get back to factory or a soft-brick situation.
A snippet from the link above,
The people who are using these scripts aren't learning what is actually happening when they press 1 on their keyboard. Boom, their phone is unlocked, su-binaries and cwm recovery installed. Then, they flash a rom without creating a nandroid. What happens if something goes wrong and they didn't place any safety nets to help them? They post a thread saying their phone is bricked. People take time out of their day to help these people out, but since the user doesn't understand what the helper is talking about, they can't fix it.
Just last weekend I spent 30 minutes replying to a PM with step by step instructions how to flash stock images and including links to files and resources. The person replied back. Instead of fixing his phone himself, he said he "claimed his phone as stolen and will be getting sent a new one lol". WTF?! Not only is that morally wrong, it's also insurance fraud. And we wonder why carriers and OEM's are trying as hard as they can to lock down non-nexus phones.
Please, take the time to learn how to get yourself out of a mess before you are in a mess.
Click to expand...
Click to collapse
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
For information sake (I have already rooted via TK) your post actually does prove a point. For myself and maybe others, would you be willing to P.M me the instructions to do it via ADB/Fastboot just in case , I , myself get screwed over. Thanks Z
Sent from my Nexus 6 using XDA Free mobile app
flash you phone manually you will learn a lot about how the toolkits work.
I find it faster to flash manually than to use a tool kit.
once an OTA is available you can grap the image from the google site and flash the files manually.
There is a way to manually flash you phone and save userdata so you keep all your apps.
One you learn and get a little practice It will be so easy you will be able to flash like it is second nature. (I was a noob that came from iphone and jailbreaking)
I can actually flash the files manually faster that an OTA can update a phone and I type with maybe a total of 6 fingers. because i never took a typing class
zephiK said:
Its very easy to do manually, if it was a long and tedious step such as G1 rooting or manually exploiting a phone then a toolkit is reasonable.
For Nexus 6, its as simple as.
1. install drivers & fastboot.
2. bootloader mode (vol down + power)
3. fastboot oem unlock
4. fastboot flash recovery <name-of-recovery>.img
5. flash supersu
A very good sticky guide is posted, http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
And we all know that regardless if you use a Root Toolkit, you MUST read before you do anything.
Toolkit doesn't really help you bring you back from bricks, in fact I would argue that it does the opposite. You're relying on a program to do what you're supposed to do. In my experience of helping people in XDA forums, they've used toolkits and got themselves into bad positions and wasn't sure how to fix their problem or the toolkit soft-bricking their device. They had to learn fastboot / adb to resolve their issue.
Read the dangers of toolkits, they're not as fancy as people view it to be. Its not difficult to do the tasks manually. Very easy to do. I was able to root/unlock my N6 in a minute since I already had the environment set up.
Think of it this way, you have math homework. You can either go input it into the calculator and have the answer. Congrats, you have the answer but did you understand how they got to that step? No not really.
Its imperative for any user on XDA to learn the fastboot/adb step, its not difficult as I've mentioned time and time again. It takes some reading, but it'll save you time because later down the line you'll understand why you did what you did and you can get yourself out of situations instead of going to Q&A and asking for someone help on how to get back to factory or a soft-brick situation.
A snippet from the link above,
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
Click to expand...
Click to collapse
Can you provide to me instructions on a manual way? Like the other poster said I would like to learn to manually flash OEM unlucks and root and Roms (if possible) thanks Z! P.M ME if you decide to thanks!
Sent from my Nexus 6 using XDA Free mobile app
if you have drivers installed already from first link above then you can follow these steps:
Download the required factory image files to your computer and extract them
1) Create an empty directory. All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory; (it is easier this way)
2) If all you want to do is unlock your bootloader, skip to step 6 in this section.
3) Download the version of Android you want to your new directory. Make sure you are using a nexus 6 image.
4) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
5) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;
6) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
7) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt. In Ubuntu just cd to the directory.
Type in the commands into the command prompt
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-some-description-number.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-some-description-number.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
10) Optional, but read note. Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.
11) Flash the kernel/ramdisk: fastboot flash boot boot.img
12) Flash the recovery partition: fastboot flash recovery recovery.img
13) Erase the cache partition: fastboot format cache
14) Reboot: fastboot reboot
15) Done! The first boot will likely take quite a bit longer than you are used to, as Android builds the cache.
Now you have a fully stock image on your device. The only thing that is different from out-of-the-box condition is that your bootloader is unlocked.
No you can root or decrypt. Search for directions on the forum or the internet.
I'm not the original writer of these instructions, but I found these helpful to people wanting the step by step instructions.
TheSkillfulTroll said:
Can you provide to me instructions on a manual way? Like the other poster said I would like to learn to manually flash OEM unlucks and root and Roms (if possible) thanks Z! P.M ME if you decide to thanks!
Click to expand...
Click to collapse
Read the first couple of posts of the following threads. The first talks about how to root, and the other, about how to flash the factory images. Very detailed.
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
If someone can't take a couple minutes out of their time to follow a step-by-step guide then they shouldn't be tinkering with their device.
Click to expand...
Click to collapse
How true. I certainly don't want a paper weight...
Larzzzz82 said:
How true. I certainly don't want a paper weight...
Click to expand...
Click to collapse
Exactly, and if they believe that everything is magical and click on a button "yay I rooted, unlocked my bootloader." Sure you saved time by clicking a button rather than following a step-by-step guide which is quite easy, what happens when you encounter a problem like a soft brick? Questions on whether or not you can flash a older radio etc?
A toolkit can't do that for you, by finding out why something works this way will be better in the long run. I don't mind answering questions but what I do mind is when people use toolkits for something that is already so easy. For Samsung and other manufacturers that lock down their bootloaders, I fully understand why toolkits are needed because they are not unlockable via bootloader mode (unless its HTC, OnePlus, and some other exception) and requires a exploit to obtain root access (e.g. Towelroot).
For Nexus devices (and HTC/OnePlus/etc) devices where the company gave you a "fastboot oem unlock." Use it very simple to do. The hardest part is installing a driver and fastboot executable, which if you have a mac you don't even need the driver. Once you do it once, you're set for life on that computer. When I unlocked my N6, I just literally plugged it in... activated the OEM unlock via developer options and went into bootloader mode and typed fastboot oem unlock.
Finished that all in one minute.
zephiK said:
Exactly, and if they believe that everything is magical and click on a button "yay I rooted, unlocked my bootloader." Sure you saved time by clicking a button rather than following a step-by-step guide which is quite easy, what happens when you encounter a problem like a soft brick? Questions on whether or not you can flash a older radio etc?
A toolkit can't do that for you, by finding out why something works this way will be better in the long run. I don't mind answering questions but what I do mind is when people use toolkits for something that is already so easy. For Samsung and other manufacturers that lock down their bootloaders, I fully understand why toolkits are needed because they are not unlockable via bootloader mode (unless its HTC, OnePlus, and some other exception) and requires a exploit to obtain root access (e.g. Towelroot).
For Nexus devices (and HTC/OnePlus/etc) devices where the company gave you a "fastboot oem unlock." Use it very simple to do. The hardest part is installing a driver and fastboot executable, which if you have a mac you don't even need the driver. Once you do it once, you're set for life on that computer. When I unlocked my N6, I just literally plugged it in... activated the OEM unlock via developer options and went into bootloader mode and typed fastboot oem unlock.
Finished that all in one minute.
Click to expand...
Click to collapse
I agree the hardest part for me was on windows trying to get the stupid drivers to work correctly.
Dumped windows for Linux and followed the manual steps i found on XDA and never looked back.
No drivers needed in Linux either.
TheSkillfulTroll said:
some people here are wrong, will it wipe data? for the first time (when unlocking the OEM) yes. Lollipop now has a different way to check ROOTING, once it detects you modified ANY file in the system core files, it aborts. To work around this, either use a ROM and upgrade via FLASHING (which i do) or use NEXUS ROOT TOOLKIT. Using the toolkit (which is very noob friendly) allows everything to be done by a click. BUT, to upgrade via toolkit, (ota) you need to flash stock which in the toolkit completely wipe system, then unroot, then update, then reroot and flash whatever ROM you want, which would again wipe your device. the way i do it is easier, it requires no wiping and i get to keep my ROM at all times and i get earlier versions (depending on ROM creators) then OTA, i currently have 5.0.2 on my nexus 6, which isnt ven out yet OTA. :fingers-crossed:
Click to expand...
Click to collapse
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
miike1106 said:
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
Click to expand...
Click to collapse
Say you flashed SimpleAosp which is currently 5.0.2, whenever 5.0.3 comes out you need to Download it on your phone, open flashify and boot into TWRP, in there you need click install then DONT WIPE, find the updated version and flash over the current one, reboot and bam, you have new version and you didn't lose anything. Only do this method if you are transition from the same ROM to a new one, if you decided to go from SimpleAosp to liquidsmooth you need to wipe.
Sent from my Nexus 6 using XDA Free mobile app
TheSkillfulTroll said:
Say you flashed SimpleAosp which is currently 5.0.2, whenever 5.0.3 comes out you need to Download it on your phone, open flashify and boot into TWRP, in there you need click install then DONT WIPE, find the updated version and flash over the current one, reboot and bam, you have new version and you didn't lose anything. Only do this method if you are transition from the same ROM to a new one, if you decided to go from SimpleAosp to liquidsmooth you need to wipe.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Ah ok, this is what i was looking for.
miike1106 said:
Ah ok, this is what i was looking for.
Click to expand...
Click to collapse
Or... You could live dangerously and try a dirty flash first every time... Worst case... You go back and wipe in recovery
miike1106 said:
Yes, this is my main concern. Back in my Samsung days, i remember flashing ROMs everyday, but the whole wiping got really annoying. When i got my Nexus 5 i just kept it stock. Now I do want to root to use the double tap to wake and the LED, but i don't want to wipe everytime there's an update. From what I remember, whenever you flash a ROM you have to wipe the phone. So is there a way around having to wipe your phone completely everytime there's an update?
Click to expand...
Click to collapse
You can dirty flash but this is only the case when you update from the same ROM to a newer update of the version.
When we say wipe, it only wipes the OS not internal storage.

Categories

Resources