Related
So I bought a N1 yesterday, cant wait till it gets here, The phone is rooted and has 2.2 on it, Is there anyway I can un root it and just be at the latest stock android? I just prefer to be at the normal stock updates, never really been big into rooting and ROMS etc unless I have too, anyway so yea thats my question and is it difficult?
Thanks in advance!
Take a look in the Development board, there is a sticky that shows you how to restore stock 2.1. Then it will prompt you to upgrade to Froyo.
solidkevin said:
So I bought a N1 yesterday, cant wait till it gets here, The phone is rooted and has 2.2 on it, Is there anyway I can un root it and just be at the latest stock android? I just prefer to be at the normal stock updates, never really been big into rooting and ROMS etc unless I have too, anyway so yea thats my question and is it difficult?
Thanks in advance!
Click to expand...
Click to collapse
Yeah, you can't re-lock the bootloader, but you can load up the stock ROM as the post above says. But since it's all already done, you might consider looking into a ROM which fits you. There are several which are "almost stock" but have nice enhancements, like the Enom rom.
I too am an unrooted stock ROM kinda guy, I don't have the time or patience to deal with fiddly stuff on my phone anymore, as I need to pull it out, see where my next meeting is, and get there. Not pull it out and realize it's in a Standby of Death or some other random problem. There are pluses and minuses to using a non-stock ROM, weigh them.. I'm starting to myself... I want a black notification bar and a handful of other small things, but to get them it requires a lot of work (unlock, flash new rom, set up all of my apps again, figure out new stuff in ROM, etc..)
Yeah you could also use modaco ROM. Those are stock ROMs with a few extras like super user access, which is a must have. Etc.
Is rooting similar or at least easy like the HD2? I had one of those and putting Custom ROMS was so simple!
Should be fairly simple if cyanogen is on it.
Sent from my Nexus One using XDA App at 35000 feet
uberamd said:
Take a look in the Development board, there is a sticky that shows you how to restore stock 2.1. Then it will prompt you to upgrade to Froyo.
Click to expand...
Click to collapse
Can you please link the thread, Ive looked and looked and I cant find a unrooting tutorial.
Nexus One Android Development -> Original Shipping - Tutotrial
The thread is stuck right at the top of the forum -_-
GldRush98 said:
Nexus One Android Development -> Original Shipping - Tutotrial
The thread is stuck right at the top of the forum -_-
Click to expand...
Click to collapse
WOW....I feel dumb....thanks lol
I am assuming you know how to use ADB and Fastboot
Hmm, Is there a thread explaining those 2 things?
solidkevin said:
I am assuming you know how to use ADB and Fastboot
Hmm, Is there a thread explaining those 2 things?
Click to expand...
Click to collapse
If all you want to do is flash stock rom, you don't even need to know what those two are. The stickied tutorials are dead simple.
Can somoene confirm Im gonna be doing this correctly.
Step 1. Disable backup my settings under privacy settings.
Step 2. unzip the original shipping ROM and put it somewhere you can find.
Step 3. Plug in Nexus One with USB to computer (enable usb and debug modes)
Step 4. adb reboot bootloader (which will boot into the bootloader)
Step 5. Confirm fastboot connection fastboot devices
Step 6*. fastboot erase userdata
Step 7*. fastboot erase cache
*If step 6 and 7 does not work, and if you have Amon_RA's recovery installed, you can do a factory data wipe from there.
Alternately, you can also do a factory data wipe within Android. Settings => Privacy Settings => Factory Data Reset.
Thanks to Brian and setzer715.
Step 8. Go to the directory that you stored your unzipped files.
Step 9. fastboot flash userdata userdata.img
Step 10. fastboot flash boot boot.img
Step 11. fastboot flash system system.img
Step 12. Skip to step 13 if you want to keep recovery (assuming you have a modified recovery such as Amon_RA's recovery). If not fastboot flash recovery recovery.img
Step 13. fastboot reboot
Step 14. After the system boots up and while setting up skip setting up with the google account and you can setup accounts later. This will prevent the phone from pulling down the previous settings (downloaded apps, wallpaper etc) from google.
Step 15. You are done. Enjoy.
Ok so I downloaded, installed and updated Android SDK, it seems to be all set, now when I follow those steps, I connect the phone first then for instance step 4 I should start "adb" then type in reboot bootloader, and for step 5 I should start up "fastboot" then type devices, etc etc? Is that correct?
thanks in advance.
Anyone? Please.
solidkevin said:
Anyone? Please.
Click to expand...
Click to collapse
look here to learn how to setup adb
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Bought a new Nexus 7 because my wife and I have them and love them. We had bought our daughter a cheap 'funtab' from walmart just so she could play a few games she loves and hopefully leave ours alone, the funtab was a complete POS so it was returned to WM and just bought her a N7 instead.
When booted, the tablet it immediately notified me of the update from 4.1.2 to 4.2.1. Each time it tried to update it would fail partially through, not sure why. So I thought I'd download and use the toolkit to force the update. After unlocking, rooting, installing busybox and so on. I choose the option to flash stock image. The update process started OK there but part way through gave an error, something about needing to be 'X' but is instead 'x' before going back to the home screen. Now the tablet is stuck in fastboot mode, and cant boot to either recovery or android. I think I may be in trouble here.... Any suggestions?
#1 reason why people shouldn't use tool kits to root. You have no idea what went wrong or where the problem occurred.
I'm assuming that your tablet is unlocked so you need to download a custom recovery and install it via fastboot.
Then download the Stock 4.2.1 ROM from the Android development section and flash it in the recovery.
This should give you an idea of how to do it.
http://www.androidcentral.com/how-unlock-bootloader-and-root-your-nexus-7
Sent from my Nexus 7
I've done more research and I'm currently working on getting the android sdk going. I've downloaded it, jdk, the proper factory image (i think I f'd up by accidentally downloading the factory image for the hspa model). My question now is can the factory image be flashed from what appears to be fastboot mode, or do i need to flash custom recovery first (via the sdk)? I can confirm that the bootloaded is unlocked.
Ok so I was able to flash the stock image using the instructions found at http://forum.xda-developers.com/showthread.php?t=1907796
This process went extremely well once I had all my ducks in a row. Thanks for the help.
So for the past weeks I've been looking in to flashing PA ROM on my nexus 4 , Honestly I'm kind of nervous that I will end up Bricking it... its completely Stock ATM . I noticed a few people saying not to use a toolkit, but to me it seems a lot easier, even to get it back to stock if I needed to . So how many have used a toolkit ? Any Problems Major issues ?
Sent from my Nexus 4 using xda app-developers app
yes
Sent from my Nexus 4 using xda app-developers app
Did you use this one?
http://forum.xda-developers.com/showthread.php?t=1995688
Toolkits aren't bad it's when people use them but have no idea what it is doing that is bad.
Your phone goes into a bootloop then you don't know how to fix it. If you don't know the 6 partitions in the Google.imgs how to use adb or fastboot don't use a toolkit
Edit: http://forum.xda-developers.com/showthread.php?t=1469909
The Dangers of Tool Kits and One Click Root Methods + Mini Rant
Sent from my Nexus 4
g2uzer said:
Did you use this one?
http://forum.xda-developers.com/showthread.php?t=1995688
Click to expand...
Click to collapse
I used Mr Skip's and it worked really well, most important thing to get right is installing the drivers on your PC, I donated to him cause it has so many options and worked so well
Never have and never will. Once you learn fastboot it's too much fun playing in the command prompt lol.
spaceman860 said:
Toolkits aren't bad it's when people use them but have no idea what it is doing that is bad.
Your phone goes into a bootloop then you don't know how to fix it. If you don't know the 6 partitions in the Google.imgs how to use adb or fastboot don't use a toolkit
Edit: http://forum.xda-developers.com/showthread.php?t=1469909
The Dangers of Tool Kits and One Click Root Methods + Mini Rant
Sent from my Nexus 4
Click to expand...
Click to collapse
Yeah I have read about phone going in to bootloop and it seems like a easy fix from what I read, the only phone I have rooted was a g2x thru a kit, so yeah I'm mostly a noobie, I've done a lot of reading but I usually ask my friend to do it for me since he knows A LOT more than me , I seen him unlock,rooot a few phones with out kits,,but to me it seems a lot more steps and there for more chances of me messing something up, so the only possibility you have thru rootkit is your phone going to boot loop ?
I have read mrskip but seems that this one looks easier (I think so )
http://forum.xda-developers.com/showthread.php?t=1766475
g2uzer said:
Yeah I have read about phone going in to bootloop and it seems like a easy fix from what I read, the only phone I have rooted was a g2x thru a kit, so yeah I'm mostly a noobie, I've done a lot of reading but I usually ask my friend to do it for me since he knows A LOT more than me , I seen him unlock,rooot a few phones with out kits,,but to me it seems a lot more steps and there for more chances of me messing something up, so the only possibility you have thru rootkit is your phone going to boot loop ?
I have read mrskip but seems that this one looks easier (I think so )
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4
spaceman860 said:
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4
Click to expand...
Click to collapse
i disagree with you..
instead of using "done", id use "profit" :silly:
spaceman860 said:
After you install the drivers its this simple
fastboot oem unlock
fastboot flash recovery recovery.img
Then flash the SU.zip in recovery
Done
Sent from my Nexus 4
Click to expand...
Click to collapse
Good i found this thread, ill get an n4 soon and just wanted to check things out. I am comfortable with fastboot, and ADB(done everything with one v).
So its like this right?
fastboot oem unlock (cant believe its this simple, you have to use an unlock token to unlock an HTC boot loader)
fastboot flash recovery recovery.img same with the one v
Root by flashing zip.
After that simply enjoy flashing. Am i right? Also, do you need to flash kernels while changing ROMs like on hTC phones?
Just read, someone mentioned that if you don't know the 6 partitions you better not flash. Which 6 partitions?
Sent from my One V using xda app-developers app
soham_sss said:
Good i found this thread, ill get an n4 soon and just wanted to check things out. I am comfortable with fastboot, and ADB(done everything with one v).
So its like this right?
fastboot oem unlock (cant believe its this simple, you have to use an unlock token to unlock an HTC boot loader)
fastboot flash recovery recovery.img same with the one v
Root by flashing zip.
After that simply enjoy flashing. Am i right? Also, do you need to flash kernels while changing ROMs like on hTC phones?
Just read, someone mentioned that if you don't know the 6 partitions you better not flash. Which 6 partitions?
Sent from my One V using xda app-developers app
Click to expand...
Click to collapse
yup, thats it. fastboot oem unlock, fastboot flash a custom recovery, flash a custom rom or the su binaries via your new custom recovery, then reboot and profit. you dont have to flash kernels since all custom roms include them. but, you can and should flash custom kernels to better your device
simms22 said:
yup, thats it. fastboot oem unlock, fastboot flash a custom recovery, flash a custom rom or the su binaries via your new custom recovery, then reboot and profit. you dont have to flash kernels since all custom roms include them. but, you can and should flash custom kernels to better your device
Click to expand...
Click to collapse
Is there a updated video doing it this method? ( not using any rootkit) I'm more of a visual learner
Can't seem to find one.
After unlocking every thing I know how to flash ROMs, just the unlocking is what got me nervous .
Thanks
Sent from my Nexus 4 using xda app-developers app
g2uzer said:
Is there a updated video doing it this method? ( not using any rootkit) I'm more of a visual learner
Can't seem to find one.
After unlocking every thing I know how to flash ROMs, just the unlocking is what got me nervous .
Thanks
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I'd like a video of this too.
Can you brick your phone while unlocking? Or just while flashing?
g2uzer said:
So for the past weeks I've been looking in to flashing PA ROM on my nexus 4 , Honestly I'm kind of nervous that I will end up Bricking it... its completely Stock ATM . I noticed a few people saying not to use a toolkit, but to me it seems a lot easier, even to get it back to stock if I needed to . So how many have used a toolkit ? Any Problems Major issues ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
use the nexus 4 toolkit by msskip..
its the best one so far and very easy to use...and dont worry abt bricking..
post if any issues,,.
No toolkit. It's important to know how to use fastboot.
Sent from my Nexus 4 using Tapatalk 4 Beta
Unlocking the bootloader and rooting for new users
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:
sparkplugDev said:
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:
Click to expand...
Click to collapse
Thanks a lot ! When I get home I'm going to read this for the 3rd time .
So if I want to go back completely stock I can use a toolkit ?
Sent from my Nexus 4 using xda app-developers app
g2uzer said:
Thanks a lot ! When I get home I'm going to read this for the 3rd time .
So if I want to go back completely stock I can use a toolkit ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah, like I said, the toolkit makes it a lot easier to flash a factory image and frankly, I think it's safer. Less room for mistakes. The less you toy around with flashing the bootloader and the radio, the better chance you have of not bricking your device. Fortunately, when your bootloader is unlocked, as long as you aren't doing anything crazy, you will have a hard time bricking your device. If you have any further questions while you're working on it shoot me a PM and I will try to help. Good Luck!
sparkplugDev said:
The only thing I've ever used toolkit for in the past is restoring my Nexus devices to a factory image and the only reason I did that is because I didn't care to figure out how to decompile those things. But yeah, just like others have said above it is extremely easy to root a nexus device. Since my N4 already has the bootloader unlocked I can't really give you a real video anyway so I will give you an very detailed instruction list.
Before you start, install the N4 drivers. More simply, you can download and install the clockworkmod universal adb drivers from kouch. Everything below assumes that drivers are installed and working.
1. Get your supplies - download a custom recovery (most these days prefer TWRP and for simplification, today, so will you) You will also need a superSU.zip which I will also provide below. You will notice that it is a bit old but it can be updated easily once you reboot back into android. Lastly, but most importantly you will need the fastboot interface which will be in the mini_adb.zip file that I have also provided on mediafire. Keep in mind that there are a lot of tools in that folder that could be useful for you at some point down the road but today all you need is fastboot.
Link to Team Win Recovery for mako
MediaFire link to Superuser.zip
Mediafire link to miniadb_inc.zip
2. Set up your environment - first you need to unzip miniadb_inc.zip and for the sake of making things easier take the folder inside of the same name and drop it into the root of your C: drive. Again, to make things easier, go ahead and drop the twrp.img into the miniadb_inc folder. If you don't follow these instructions exactly then my commands won't work as written.
3. Turn off your phone and boot into the bootloader. To do this, when the phone is off hold down the power, vol-up, and vol-down buttons simultaneously until the phone viabrates once. You should see a picture of an Android lying on it's back with it's front opened up and a big start button on top. Connect your phone and then set it aside for a moment and open command prompt on your PC. Input the following commands:
Code:
cd /
cd /miniadb_inc
this changes your active directory to the miniadb_inc folder. Next input this command:
Code:
fastboot oem unlock
this sends the command to your phone to unlock the bootloader. At this time you should look at your phone and see a prompt regarding unlocking the bootloader. Click accept to unlock the bootloader or if you're freaking out too much to continue at the moment you can click that you don't accept the terms and then click the power button and boot back into android and go about your day.
If you were bold enough to get to this point then you will now need to boot back into android anyway. Your phone will have reset and these instructions assume that you aren't flashing a custom ROM at this time so go ahead and take a minute to sign in and get things like you want them. While you're booted into Android take a moment to transfer superuser.zip to your SD partition on your phone. When you're done get back to the bootloader like you did earlier and input the following command:
Code:
fastboot flash recovery twrp.img
this command tells your computer to push the twrp recovery that you downloaded earlier to your phone and to flash it, effectively removing the stock recovery from your device.
4. Using the volume keys scroll through the bootloader options until you see recovery at the top of your phone and then click the power key to confirm. This will boot you into TWRP for the first time. Now select the install button in TWRP and then find the superuser.zip file that you put on your phone in the previous step.
5. Select the reboot button and your phone should reboot back into Android and will now be rooted! Update the su binary within the SuperSU app and update SuperSU through the Play Store like any other app. Congratulations, you're done!
6. Profit. :laugh:
Click to expand...
Click to collapse
Superb, all this I know already as I did this with one v
But, I read in some tutorial that if you don't reboot to stock recovery and data reset your phone AFTER you've unlocked the boot loader, you will end up with a soft brick? Is it true?
Sent from my Nexus 4 using xda app-developers app
I've been playing g with androids for a long time and dozens of devices. Personally have never used a toolkit and its hard for me to recommend or knock them.
My view is a toolkit teaches you nothing
If a toolkit was made so was another method
Everyone will have an issue with something at some point, so the more you learn now the less freaking out latter
Learning to do thongs yourself will always be safer, I mean yes manually typing a dd command can be dangerous but if you know what you are doing you know when to be cautious, there will always be an example for either argument on this, but I truly can't see a reason to believe a tool kit is safer
But I'm a to each their own sorta guy, but also one who feels the need to learn as much as possible so will promote as much manually methods for anything in life and will do my best to stay away from auto-just-about-anything.... Just a my $.02
Sent from my Nexus 7 using xda premium
So I was a noob when I first joined this to unlock my opt but now I have a nexus 6p and am trying to sell my opt. So i thought i might as well reset it back so that whoever buys it is not stuck with a rooted device if they don't want one. Well me not being so skilled with the processes I tried to unroot it through the command prompt and that worked but I couldn't factory reset it for some reason. So i tried to root it again and sell it as rooted because I'm sure someone would buy it like that but now it goes into a reboot loop where it shows the oneplus boot logo and shuts off and then shows it again. I'm able to get into fastboot mode but when I type in the command prompt about the status of the device it shows rooted as false and tampered as true so i think that i'm in trouble. SO i need help trying to get the tampered message to read false again and trying to get the device either back to a normal rooted or a normal unrooted state. Also should mention I think i did something to twrp so that its not showing up and I can't get into the recovery stage of the reboot. Any help would be wonderful!!!!
Check this thread, might be useful http://forum.xda-developers.com/showthread.php?t=3290707
[GUIDE][RESET][UNBRICK] Stock Reset to OxygenOS 2.2.0
If you are using Mac or Linux, Hit me up and I will guide you through how to do it on there. Otherwise the guide provided by @aymahalawa will get you there no problems at all.
Just flash twrp, first time make sure it boot in recovery then flash full zip for oxygen os
Sent from my ONE A2005 using Tapatalk
Thanks guys, I will try what @aymahalawa suggested, and I have windows
So finally followed the process and it worked after trying like 3 times!!!! currently selling on ebay if anyone is interested
After using the megapixel rom. I tried flash back to stock with root tool kit.
During the process it told me I had to manual boot in recovery to a factory restore. That would not work so I ended up soft bricking my phone. I was able to side load twrp and the latest build and flash it (thank god). No when I do oem lock boot loader, my nexus 6p won't boot. As soon as I oem unlock, it will boot. Any ideas what could be cause that?
If you did not restore the recovery it probably throws a flag and says the configuration is invalid. You need to restore completely (recovery, boot, system, vendor, etc) through fastboot so that it is truly stock.
Cheers,
B.D.
This is a perfect time to remind folks that "locking" the bootloader is something that should be done with great care. There are dozens, if not hundreds of "my phone is bricked" threads centered around locking their bootloader without understanding the requirements and risks. If you don't have a reason to do it, leave it unlocked. If I need to do it, I flash 100% back to stock using a full factory image before locking.
Sent from my Nexus 6 using XDA-Developers Legacy app
BostonDan said:
If you did not restore the recovery it probably throws a flag and says the configuration is invalid. You need to restore completely (recovery, boot, system, vendor, etc) through fastboot so that it is truly stock.
Cheers,
B.D.
Click to expand...
Click to collapse
So you wouldn't recommend using the Nexus toolkit to flash factory? Can you give me the string in order that I would use to flash factory via fastboot? Fast boot is also hit or miss with the commands for me.
Blackfish77 said:
So you wouldn't recommend using the Nexus toolkit to flash factory? Can you give me the string in order that I would use to flash factory via fastboot? Fast boot is also hit or miss with the commands for me.
Click to expand...
Click to collapse
No offense intended, but this always irks me quite a bit.
Absolutely DO NOT use toolkits for anything at all, ever. They're not easier, they're not faster. It's just doing fastboot / adb with a UI that has buttons you can click instead of typing in fastboot.
This. This is the exact reason you shouldn't use toolkits. Especially if you don't know the manual way. It borks something up and now you need to wait possibly hours to get a working phone again when the solution would only take about 15 seconds to fix.
You need to fully familiarize yourself with this guide here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
ADB/Fastboot is absolutely not "hit or miss." If you have trouble with it then you need to make sure that your drivers are properly installed and you're entering commands correctly. Also make sure to ALWAYS keep your ADB & fastboot drivers up to date via the Android SDK. All of this is covered in the link above.
As far as your bootloader issue. You cannot return to a locked bootloader with anything other than 100% complete unadulterated stock factory images. No TWRP, no root, no Xposed, no Magisk, no build.prop edits etc., ...Nothing.
Use fastboot to flash your factory images you downloaded. You can use the flash all bat file or individually flash each separate. Again it's all covered in the link I posted above.
Also, what do you mean you couldn't wipe/reset from stock recovery? When you flash stock recovery and boot to it, you will see an Android on its back with an exclamation mark in a red triangle. You may or may not see text that reads "No Command". Either way, from that point hold down the power button and then press and release volume up. You will boot to stock recovery where you can wipe your data.
Not for nothing, but as mentioned above, people have hard bricked their 6P from locking bootloader's on combos besides stock. You got extremely lucky you didn't as well. Please take some time to read and fully understand what you're doing with your ~600$ device.
This is also, for the most part, pretty standard stuff as far as flashing / modding goes. At least since 2010 when I got into it. If you want to know the exact string of fastboot commands please read and use the guide I linked. It teaches you literally everything. There's nothing it doesn't cover and once you get used to it you will never use a toolkit again.
Hope I didn't come off rude, but basically since 2010 when I got into this across all my devices I try to help out in the Q+A sections. I've probably participated in hundreds and hundreds of "help, I used a toolkit and my phone is bricked and I have no idea how to fix it, I just wanted cool stuff on my phone" threads. They're absolutely 100% not worth the trouble and headaches from them. Especially if you have no idea what they're doing on the back end. Know Fastboot and ADB like the back of your hand and just prefer to use them? That's a different story, if something fails then you fix it yourself in 10 seconds. But for the love of God, please please please please please stop using toolkits if you don't know how to fix issues on your own. You will eventually hard brick. I've seen it happen dozens of times. Thread turns into a circlej*rk about whether toolkits are bad or not, OP hard bricks their phone and commits fraud, which is illegal by trying to RMA it. Just don't use them. It's simple enough without them. Why reinvent the wheel when it works just fine?
You should only lock bootloader when you are on stock factory image from nexus developers site. Either use flash_all script or flash everything manually. As others said keep away from toolkits.. You never know what can go wrong or what they re doing in background.
As I understand you restored TWRP and Megapixel rom and tried to lock the bootloader when you had that combination installed on your phone? That can not be done. You are either full stock (rom, kernel, recovery...) and locked bootloader or unlocked bootloader and any combo of kernel, rom, recovery that you want.
RoyJ said:
No offense intended, but this always irks me quite a bit.
Absolutely DO NOT use toolkits for anything at all, ever. They're not easier, they're not faster. It's just doing fastboot / adb with a UI that has buttons you can click instead of typing in fastboot.
This. This is the exact reason you shouldn't use toolkits. Especially if you don't know the manual way. It borks something up and now you need to wait possibly hours to get a working phone again when the solution would only take about 15 seconds to fix.
You need to fully familiarize yourself with this guide here;
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
ADB/Fastboot is absolutely not "hit or miss." If you have trouble with it then you need to make sure that your drivers are properly installed and you're entering commands correctly. Also make sure to ALWAYS keep your ADB & fastboot drivers up to date via the Android SDK. All of this is covered in the link above.
As far as your bootloader issue. You cannot return to a locked bootloader with anything other than 100% complete unadulterated stock factory images. No TWRP, no root, no Xposed, no Magisk, no build.prop edits etc., ...Nothing.
Use fastboot to flash your factory images you downloaded. You can use the flash all bat file or individually flash each separate. Again it's all covered in the link I posted above.
Also, what do you mean you couldn't wipe/reset from stock recovery? When you flash stock recovery and boot to it, you will see an Android on its back with an exclamation mark in a red triangle. You may or may not see text that reads "No Command". Either way, from that point hold down the power button and then press and release volume up. You will boot to stock recovery where you can wipe your data.
Not for nothing, but as mentioned above, people have hard bricked their 6P from locking bootloader's on combos besides stock. You got extremely lucky you didn't as well. Please take some time to read and fully understand what you're doing with your ~600$ device.
This is also, for the most part, pretty standard stuff as far as flashing / modding goes. At least since 2010 when I got into it. If you want to know the exact string of fastboot commands please read and use the guide I linked. It teaches you literally everything. There's nothing it doesn't cover and once you get used to it you will never use a toolkit again.
Hope I didn't come off rude, but basically since 2010 when I got into this across all my devices I try to help out in the Q+A sections. I've probably participated in hundreds and hundreds of "help, I used a toolkit and my phone is bricked and I have no idea how to fix it, I just wanted cool stuff on my phone" threads. They're absolutely 100% not worth the trouble and headaches from them. Especially if you have no idea what they're doing on the back end. Know Fastboot and ADB like the back of your hand and just prefer to use them? That's a different story, if something fails then you fix it yourself in 10 seconds. But for the love of God, please please please please please stop using toolkits if you don't know how to fix issues on your own. You will eventually hard brick. I've seen it happen dozens of times. Thread turns into a circlej*rk about whether toolkits are bad or not, OP hard bricks their phone and commits fraud, which is illegal by trying to RMA it. Just don't use them. It's simple enough without them. Why reinvent the wheel when it works just fine?
Click to expand...
Click to collapse
I ended up using fastboot to flash factory. I then re locked bootloader and everything booted without and issue. I was happy about that. I re rooted and everything is working great. :good:
I can say I learned a lot from this experience. Thanks to everyone for your advice. I am now comfortable using the fastboot method. Almost bricking my phone was scary but it taught me a lesson. Cheers everyone.