Hello guys, this Thread is dedicated to updating the stock Rom on the Pixel with unlocked Bootloaders and have made changes to their system (custom Kernel, Root, TWRP)
To keep in Mind:
As you might know, with a unlocked Bootloader and changes that have been made to system you are not able to recive OTA updates.
This will overrite your Kernel, Bootloader, Root and Recovery with stock standarts.
Your Bootloader has to be unlocked in Order to proceed.
And you will have to do that, everytime you want to update.
You need to download the System Image for your device here:
https://developers.google.com/android/images
How to do:
Read the instructions that google provides on their site.
After you are in the Folder you have downloaded, you see some "flash-all.sh" and "flash-all.bat" files.
The .sh file is for Linux Distros and the .bat file is for Windows.
If you dont want your device to be wiped when you try to install that, edit the file as so:
Somewhere in the script (open it with any text-editor) there will be a -w, remove this and save the file.
Now you can continue like it explains on googles site, without wiping your device.
Alternative Method (for getting the OTA Updates and flash them instead):
To keep in Mind:
If you choose this method, you will only install the OTA you receive via your Device.
This will overrite your Kernel, Bootloader, Root and Recovery with stock standarts.
This .zip is flashable, and you can flash that directly via ADB Sideload in Recovery (TWRP not needed) or with TWRP via "Install" function:
You can download this OTA .zip files from here:
https://developers.google.com/android/ota
Just read the instructions that google provides on their site.
Hope you like it. Thanks
I'm rooted stock with unlocked bootloader, TWRP RC1, have downloaded and unzipped January full Pixel XL stock image, edited and saved the flash-all.bat script to remove the -w on the line where the system image zip is fastboot flashed using Notepad++.
I have placed the bootloader image, radio image and system image.zip in my platform-tools folder along with the edited flash-all.bat.
To be sure, all I have to do is run the script in fastboot and my data and internal storage will not be wiped?
Yes, if you have removed the w then you should be good to go. You need to copy all the files from the firmware zip package, there are six files if I count right.
Thank you. Would you mind telling me which 6 files? I have the package fully unzipped and there are a lot more than the Nexus images lol.
Bootloader.img
Radio.img
Flash-all
Image-marlin.zip
What other two? I suppose the safest thing is to place them all in platform tools.
Edit: sorry misread. I got you. All the files in the image.zip
I may be mistaken, but I thought if you just unlocked the bootloader and did nothing else you can still take OTA updates?
JU57US said:
I may be mistaken, but I thought if you just unlocked the bootloader and did nothing else you can still take OTA updates?
Click to expand...
Click to collapse
Correct.
TonikJDK said:
Correct.
Click to expand...
Click to collapse
That's what I thought, thanks for confirming. Then this guide shouldn't use the term "and/or" as to unlocked bootloaders, as it could cause people to believe that they can't take an OTA with an unlocked bootloader. There seem to be plenty of people using dePixel8 on their VZW Pixels simply to keep options open, and without making any other customizations or obtaining root. (When I receive mine, I'll be one of them). OTA's will work perfectly fine in that situation.
Actually his terminology is correct.
The "and/or" refers to the root part. However its unlikely you would have root without an unlocked bootloader.
But I don't want to get into a grammar war...
Scott said:
Actually his terminology is correct.
The "and/or" refers to the root part. However its unlikely you would have root without an unlocked bootloader.
But I don't want to get into a grammar war...
Click to expand...
Click to collapse
I don't want a grammer war either, but I disagree with your assessment. When using "and/or" you have to think about it as two separate sentences to understand it correctly as "both variables" or "either variable". Unlocked bootloader and rooted. Unlocked bootloader or rooted. So in the "or" sense, it could mean "just an unlocked bootloader".
Also, as you pointed out, I was under the impression that with the Pixel it was impossible to be rooted without an unlocked bootloader. I may be wrong about that, but if I'm not, then the "or" can only refer to the "unlocked bootloader" variable. (If I am wrong, please let me know. I don't want to make assumptions based upon bad information)
In any case, I understood it (right or wrong) to include situations with "just an unlocked bootloader", so the phrase can be unintentionally confusing to someone who has a dePixel8ed VZW bootloader with no customizations. I'm a noob here, and I have made my fair share of noob questions and seeking of confirmations about these processes that can possibly brick our phones (see above, lol), precisely because there are some posts that use language which can be confusing. I was just hoping to clear that up to prevent anyone else from being confused like I was. This forum has, in my short experience, been extremely helpful and polite, though I'm sure that behind the screens some of the more seasoned and/or experienced members can tire of noobish questions and insecurities based on inexperience. I really appreciate people taking the time to publish quickie guides like this.
All u have to do is extract the factory image zip . Remove the -w from the flash-all.bat and then run the bat.
I did it today with the Jan update. Didnt have to extract any more files etc. Worked a charm
Maybelle said:
I'm rooted stock with unlocked bootloader, TWRP RC1, have downloaded and unzipped January full Pixel XL stock image, edited and saved the flash-all.bat script to remove the -w on the line where the system image zip is fastboot flashed using Notepad++.
I have placed the bootloader image, radio image and system image.zip in my platform-tools folder along with the edited flash-all.bat.
To be sure, all I have to do is run the script in fastboot and my data and internal storage will not be wiped?
Click to expand...
Click to collapse
Nothing will be wiped. In fact, im not sure if you have to reinstall Root, Kernel or so (because Kernel could he replaced), but just in case, boot into OS and check. If you have to install something, make sure its compatible with the update.
Gesendet von meinem Pixel XL mit Tapatalk
JU57US said:
I may be mistaken, but I thought if you just unlocked the bootloader and did nothing else you can still take OTA updates?
Click to expand...
Click to collapse
No, you wont get any updates.
Gesendet von meinem Pixel XL mit Tapatalk
Scott said:
Actually his terminology is correct.
The "and/or" refers to the root part. However its unlikely you would have root without an unlocked bootloader.
But I don't want to get into a grammar war...
Click to expand...
Click to collapse
But its possible, that some lock their Bootloader after they are rooted.
Gesendet von meinem Pixel XL mit Tapatalk
prot- said:
All u have to do is extract the factory image zip . Remove the -w from the flash-all.bat and then run the bat.
I did it today with the Jan update. Didnt have to extract any more files etc. Worked a charm
Click to expand...
Click to collapse
Correct.
Gesendet von meinem Pixel XL mit Tapatalk
JU57US said:
I don't want a grammer war either, but I disagree with your assessment. When using "and/or" you have to think about it as two separate sentences to understand it correctly as "both variables" or "either variable". Unlocked bootloader and rooted. Unlocked bootloader or rooted. So in the "or" sense, it could mean "just an unlocked bootloader".
Also, as you pointed out, I was under the impression that with the Pixel it was impossible to be rooted without an unlocked bootloader. I may be wrong about that, but if I'm not, then the "or" can only refer to the "unlocked bootloader" variable. (If I am wrong, please let me know. I don't want to make assumptions based upon bad information)
In any case, I understood it (right or wrong) to include situations with "just an unlocked bootloader", so the phrase can be unintentionally confusing to someone who has a dePixel8ed VZW bootloader with no customizations. I'm a noob here, and I have made my fair share of noob questions and seeking of confirmations about these processes that can possibly brick our phones (see above, lol), precisely because there are some posts that use language which can be confusing. I was just hoping to clear that up to prevent anyone else from being confused like I was. This forum has, in my short experience, been extremely helpful and polite, though I'm sure that behind the screens some of the more seasoned and/or experienced members can tire of noobish questions and insecurities based on inexperience. I really appreciate people taking the time to publish quickie guides like this.
Click to expand...
Click to collapse
But some people may lock their bootloader after they have rooted, for some reason.
Gesendet von meinem Pixel XL mit Tapatalk
Shadow of Destiny said:
But some people may lock their bootloader after they have rooted, for some reason.
Gesendet von meinem Pixel XL mit Tapatalk
Click to expand...
Click to collapse
bad idea
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
Shadow of Destiny said:
No, you wont get any updates.
Gesendet von meinem Pixel XL mit Tapatalk
Click to expand...
Click to collapse
You still get OTA updates with as unlocked bootloader. If you're rooted you won't but with just an unlocked bootloader you still get them
deuce_biggins said:
bad idea
https://forum.xda-developers.com/pixel-xl/how-to/psa-read-relocking-bootloader-t3494615
Click to expand...
Click to collapse
My post was just in case, and I didnt recommend to lock the bootloader anyway (but there is no real reason).
Still thanks for pointing that out.
Gesendet von meinem Pixel XL mit Tapatalk
aholeinthewor1d said:
You still get OTA updates with as unlocked bootloader. If you're rooted you won't but with just an unlocked bootloader you still get them
Click to expand...
Click to collapse
As I heard from some reports, the update will crash.
Gesendet von meinem Pixel XL mit Tapatalk
Shadow of Destiny said:
As I heard from some reports, the update will crash.
Gesendet von meinem Pixel XL mit Tapatalk
Click to expand...
Click to collapse
Those reports are incorrect. Those people had to either have root, TWRP, or custom kernel. It's been discussed multiple times in tons of threads. If you simply unlock but you are 100% stock then you will still receive OTA updates and they install just fine. I've done all the updates OTA and I have a Verizon pixel with unlocked bootloader
Related
Sorry if this has already been posted.
Superboot for N1 GRI40
Tested and working
http://android.modaco.com/content/google-nexus-one-nexusone-modaco-com/298782/08-mar-superboot-erd79-gri40-rooting-the-nexus-one/
super easy method for rooting.
Not a "super easy" way to root the Nexus, just 'cause you have to unlock the bootloader first...and there're plenty of post about having problems after that. I prefer to wait for a Gingerbreak, or a "SuperOneClick" for the GRI40.
Worked on my phone like a charm. Bootloader unlocked.
flixos said:
Not a "super easy" way to root the Nexus, just 'cause you have to unlock the bootloader first...and there're plenty of post about having problems after that. I prefer to wait for a Gingerbreak, or a "SuperOneClick" for the GRI40.
Click to expand...
Click to collapse
What are these problems you speak of regarding unlocking the bootloader? I am curious because ever since I unlocked, my phone will not seem to keep settings such as alternate keyboards or what the default action for the home key is. If you can point me to a thread it would be much appreciated.
jimbobalu said:
What are these problems you speak of regarding unlocking the bootloader? I am curious because ever since I unlocked, my phone will not seem to keep settings such as alternate keyboards or what the default action for the home key is. If you can point me to a thread it would be much appreciated.
Click to expand...
Click to collapse
I've seen post at modaco about people having issues after using Superboot. I'm not telling that those issues are only about the app, probably there are another issues involved.
Hi I am an new user with a rooted N1 running GRI40, I want to root mine to enable navigation outside US and install the latest release of Google Maps.. but I don-t want to mess with the bootloader.. is there a z4root kinda method yet?
No z4 style method available yet, but you can roll back to an older version of android and use z4 or whatever. Once rooted you can install a pre-rooted version of 2.3.3...
Sent from my Nexus One using XDA Premium App
flixos said:
I've seen post at modaco about people having issues after using Superboot. I'm not telling that those issues are only about the app, probably there are another issues involved.
Click to expand...
Click to collapse
Flashing modaco's superboot has nothing to do with how the phone behaves because of unlocking the bootloader. They are independent. Unlocking the bootloader does NOT affect anything other than allowing you to use fastboot commands to flash full partition images to your device. That's it.
And you shouldn't be using modaco's superboot unless you need/want insecure boot. You should use ChainsDD's superuser zip (link in my sig), which justs roots your device, without flashing an insecure boot.img
efrant said:
Flashing modaco's superboot has nothing to do with how the phone behaves because of unlocking the bootloader. They are independent. Unlocking the bootloader does NOT affect anything other than allowing you to use fastboot commands to flash full partition images to your device. That's it.
And you shouldn't be using modaco's superboot unless you need/want insecure boot. You should use ChainsDD's superuser zip (link in my sig), which justs roots your device, without flashing an insecure boot.img
Click to expand...
Click to collapse
Yep, i understand that; but, under a stock Nexus One, in order to flash superboot, you have to unlock the bootloader first (if i'm not wrong).
I'm going to have a look to your ChainDD's stuff right now.
flixos said:
Yep, i understand that; but, under a stock Nexus One, in order to flash superboot, you have to unlock the bootloader first (if i'm not wrong).
I'm going to have a look to your ChainDD's stuff right now.
Click to expand...
Click to collapse
I don't think you understand what I'm trying to say: It's superboot that is likely messing things up with people's phones, NOT unlocking the bootloader.
Like I said, unlock your bootloader, and flash ChainsDD superuser package, and you will have a stock ROM with root, perfectly stable. (The only thing that the package does is adds two files to your device that give you root. That is all.)
If you don't want to unlock (and I can't understand/imagine why people would not, given that many folks have already shown that HTC still honors the warranty), then ignore everything I'm saying.
Thanks so much, got it
By the way, i will wait for another SuperOneClick...developer said that it's just a matter of time to make it work on Gingerbread.
Good Afternoon All,
Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
The QFuse does not blow when you unlock or relock the bootloader. Many reviews and Android news sites spouted that nonsense without having tried it. There are many screenshots of Google CSRs saying that they don't know what the QFuse is for, but unlocking the bootloader/rooting/alterring software is fine as long as it's not so bricked you can't reflash stock images before sending it in to them.
Link to a thread discussing this issue.
Scyntherei said:
The QFuse does not blow when you unlock or relock the bootloader. Many reviews and Android news sites spouted that nonsense without having tried it. There are many screenshots of Google CSRs saying that they don't know what the QFuse is for, but unlocking the bootloader/rooting/alterring software is fine as long as it's not so bricked you can't reflash stock images before sending it in to them.
Link to a thread discussing this issue.
Click to expand...
Click to collapse
+1 the QFuse status didn't change when unlocking the bootloader. The media exaggerated about the qfuse and nothing has happened. Everything about the phone still works properly.
Thanks very much, I wasn't aware of this, I should read more. Awesome news.
But to answer the first question.
Very few people put in effort to root a phone with an unlocked bootloader, not matter what fuses are blown.
A phone with an unlocked bootloader has root by default.
Swatto86 said:
Good Afternoon All,
Do you think it may be possible that we can get root access without unlocking the bootloader - I'm a little reluctant to unlock the bootloader because of the QFuse blowing.
Click to expand...
Click to collapse
last i read you have to flash a kernel in order to root the phone therefore you need to unlock the bootloader to do so, i would like to just root myself but i don't know if you can.
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Why people are afraid to unlock the bootloader? Nexus devices don't lose the warranty when you unlock it, you can also lock it again.
Enviado desde mi Nexus 7 mediante Tapatalk
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
No
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
The answer is no.
To do what you want, someone would need to develop and exploit.
There is no motivation to do that when all one has to do is unlock the bootloader.
On phones where a bootloader unlock exists, root methods require unlocking the bootloader.
This is to install a custom recovery so yiou can flash SU.
Unlocked bootloader = root, no matter what.
You will need to invest the time and backup your device.
@TS, did you read the unlock/root guide in general section? It clearly states you need an unlocked bootloader + custom recovery to root your device..
Sent from my Nexus 5X using XDA-Developers mobile app
I think this should be possible now with Quadrooter vulnerabilities?
sushah23 said:
I think this should be possible now with Quadrooter vulnerabilities?
Click to expand...
Click to collapse
DOA.
But nobody is going to put in time and effort.
What is the point? Unlock the bootloader and flash. It does not void the warranty.
There is even a defined method to get the monthly security update.
With the exploit, it will only work until the next OTA patches it.
I was hoping to root without unlocking the boot loader also. I am definitely not willing to do this since I believe that is what wrecked my previous 6P. It was fine until I used Nexus Root toolkit. I unlocked the boot loader, installed TWRP and rooted then minutes after this the phone locked up, rebooted and was stuck in a permanent boot loop. I couldn't get into recovery or even install any recovery. That phone is currently at the Huawei repair center in Texas and they are sending me a new device. They believe the internal ROM failed and I have suspicions of everything I did with the Toolkit did this. I am afraid to try it on my current 6P that I got from a friend. I have no root now and the phone is massively stable. 400+ hours uptime with no reboot and no slowdowns. But if I were able to root with no unlocking of the boot loader or installing any custom recovery I probably would do it. I hate that I am scared to do all that again with this other phone haha. Sorry for sounding paranoid but ****, see where am I coming from?
LiquidAlloy said:
I was hoping to root without unlocking the boot loader also. I am definitely not willing to do this since I believe that is what wrecked my previous 6P. It was fine until I used Nexus Root toolkit. I unlocked the boot loader, installed TWRP and rooted then minutes after this the phone locked up, rebooted and was stuck in a permanent boot loop. I couldn't get into recovery or even install any recovery. That phone is currently at the Huawei repair center in Texas and they are sending me a new device. They believe the internal ROM failed and I have suspicions of everything I did with the Toolkit did this. I am afraid to try it on my current 6P that I got from a friend. I have no root now and the phone is massively stable. 400+ hours uptime with no reboot and no slowdowns. But if I were able to root with no unlocking of the boot loader or installing any custom recovery I probably would do it. I hate that I am scared to do all that again with this other phone haha. Sorry for sounding paranoid but ****, see where am I coming from?
Click to expand...
Click to collapse
As good as toolkits are, put in the extra time and avoid using them because you are never in full control of what is being done to your device. Take a little extra time and learn adb and fastboot. It's actually really simple and you can get so much done without the need for using a toolkit.
Jammol said:
As good as toolkits are, put in the extra time and avoid using them because you are never in full control of what is being done to your device. Take a little extra time and learn adb and fastboot. It's actually really simple and you can get so much done without the need for using a toolkit.
Click to expand...
Click to collapse
I have tried that only a few times. I understand what you're saying. I guess convenience can be more destructive. :/
LiquidAlloy said:
I have tried that only a few times. I understand what you're saying. I guess convenience can be more destructive. :/
Click to expand...
Click to collapse
In all honesty it's not even more convenient. Once you've used the command line you'll never go back to a toolkit. It's actually easier, much faster and you have way more control over what you do.
PetrichorXFi said:
No answer?
I would like to get Root on my Nexus 6p but currently do not want to invest the time for full bootloader unlock/fresh install.
So... I will ask again, is it possible to get Root access on Nexus 6P with stock kernel and leaving bootloader in factory locked state? If yes... are there any guides to do this?
Click to expand...
Click to collapse
Use Helium app for individual apps backup. Worked great to backup a few apps/data when I changed from one Nexus 6P to another. Might be a bit buggy to get working to get the backup, but after that everything is fine.
you can do it with KINGROOT
https://developers.google.com/android/nexus/images?hl=en
I haven't even gotten MDB08L via OTA yet. Has anyone else gotten either of the two?
I'm still on MDB08I too. Went through the "about phone" to check for an update and it says there isn't one. Don't really want to flash this seeing as i'm not rooted or unlocked.
Very strange that they'd release two images simultaneously. Can't recall seeing something like this before.
I think MDB08x is just carrier specific I I got notified for mdb08i when I first booted the phone up with no sim. After I put my verizon sim in, it said I was up to date. But when I put a tmobile sim in and right away prompted me to update.
FYI
MDB08M uses MDB08I boot image, so feel free to flash and root.
k.s.deviate said:
FYI
MDB08M uses MDB08I boot image, so feel free to flash and root.
Click to expand...
Click to collapse
Hi - I may be misinterpreting, but when I look at the boot.img files in the two system images with 7zip, the CRCs are different. Doesn't that mean they're not the same? Just don't want to bork my phone! Thanks.
sgravel said:
Hi - I may be misinterpreting, but when I look at the boot.img files in the two system images with 7zip, the CRCs are different. Doesn't that mean they're not the same? Just don't want to bork my phone! Thanks.
Click to expand...
Click to collapse
I see the same thing, but I reflashed the "systemless" rooted boot image and it booted up just fine. Differences are minimal, I guess?
I can't seem to find the changelogs for the factory images. I'm I just missing it or is it hidden somewhere?
Thanks!
jm.kloz said:
I can't seem to find the changelogs for the factory images. I'm I just missing it or is it hidden somewhere?
Thanks!
Click to expand...
Click to collapse
https://groups.google.com/forum/#!msg/android-security-updates/n1aw2MGce4E/jhpVEWDUCAAJ
k.s.deviate said:
FYI
MDB08M uses MDB08I boot image, so feel free to flash and root.
Click to expand...
Click to collapse
delete
To restate, I'm running the MDB08M build. And I'm rooted.
I used the systemless bullhead boot.img from http://forum.xda-developers.com/showpost.php?p=63197935&postcount=2
I did however use the factory image script to wipe the phone clean when I flashed it. That was the only vaguely strange thing I did.
Not noticed any strange behaviour, but this phone isn't my daily driver yet.
Added some screengrabs
Is the update file available anywhere so you can update without a data wipe? New to the nexus world.
Sent from my Nexus 5X using Tapatalk
adrialk said:
Is the update file available anywhere so you can update without a data wipe?
Click to expand...
Click to collapse
I haven't found an OTA zip link yet, but I'm sure they'll come. What I don't get it why Google doesn't post the OTA links themselves.
adrialk said:
Is the update file available anywhere so you can update without a data wipe? New to the nexus world.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
If your bootloader is already unlocked, yes by flashing the factory image's system.img manually. If not unlocking the bootloader would trigger a wipe.
You'll be able to adb sideload once someone captures an OTA for it, but in theory the OTA should start rolling out to everyone gradually.
If my bootloader is unlocked is it impossible to accept an ota update? The only other nexus I messed with is my mom's N7 2013 and it's a royal pain to install updates on it. Have to manually do everything to save the data.
Unlocked bootloader has no effect on ota update.
Sent from my Nexus 5X using Tapatalk
Looks like the change logs have been posted
MDB08L is the Security Update and MDB08M is the WLAN patch below.
https://android.googlesource.com/platform/hardware/broadcom/wlan/+/25e0325
Anyone still on mda89e? Got the phone on Friday, manufacture date Oct. On Verizon and still says I'm up to date.
Only thing I've done is unlocked bootloader. Haven't flashed a modified boot.img or put a custom recovery.
antiseen said:
Anyone still on mda89e? Got the phone on Friday, manufacture date Oct. On Verizon and still says I'm up to date.
Only thing I've done is unlocked bootloader. Haven't flashed a modified boot.img or put a custom recovery.
Click to expand...
Click to collapse
Im on Verizon and still on MDA89E. Im still completely stock. Im reading up on bootloader unlock, recovery and root so I dont EFF anything up
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Durvid said:
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Click to expand...
Click to collapse
This is exactly why you should never mess with updates or flashing anything with a locked bootloader. If a factory reset doesn't fix it you're likely out of luck.
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
I'll attempt this. Weirdly enough when I look at device info in adb it shows it as being on the newest version. But Yeah I'll attempt to flash what I was on before.
Yeah, I mean I've done this before with no issues on my Nexus 6 and there were no issues but that was unlocked when I got it. I just thought you didn't have to unlock the bootloader to sideload OTA's? I may be wrong.
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Durvid said:
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Click to expand...
Click to collapse
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
akellar said:
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
Click to expand...
Click to collapse
I bought it used on /r/hardwareswap and whoever I got it from had already unlocked it.
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Heisenberg said:
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Click to expand...
Click to collapse
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Durvid said:
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Click to expand...
Click to collapse
OK, but I need the name of the zip please.
Heisenberg said:
OK, but I need the name of the zip please.
Click to expand...
Click to collapse
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Heisenberg said:
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Click to expand...
Click to collapse
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Durvid said:
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Click to expand...
Click to collapse
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Heisenberg said:
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Click to expand...
Click to collapse
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Durvid said:
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Click to expand...
Click to collapse
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
Hilarious that the top comment is mine telling you why doing this is a bad idea
Heisenberg said:
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Click to expand...
Click to collapse
Yeah, I'll probably wait for the update over the air for a while and maybe if I feel reallly eager I'll just make sure I unlock and such. Annoying that you can't unlock via fastboot anymore without that toggle. I get that Google is trying to make Android super secure but It's not too useful for folks like us. Sure it's bricked a lot of devices.
akellar said:
Hilarious that the top comment is mine telling you why doing this is a bad idea
Click to expand...
Click to collapse
I've done it before with other devices. I wouldn't say it's inherently bad. It's just that there was one toggle that I wasn't aware of that caused the issue. You live and you learn.
THIS IS NOT MY IDEA !
I found this in a N9 thread and it worked according to the user with the issue, apply this with the correct t factory image ( do it with the version you have on your device not the one you tried to update to ! )
This might not work but its worth a try ! Before doing this read about ADB and Fastboot !!!!!!!!!!!!!!!! Try and understand the basics and know what the commands are doing to help backtrack e.C.t
If it does work - go to settings and allow OEM Unlock and USB debug !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Then go read from reputable sources how to flash images manually via adb !!!!!!!!!!!!!!!!!!!!!!!
I'd follow vomers guides.
Had this problem with another device cool thing to remeber is that on locked devices the only thing that is different is that there is a signature before the MAGIC header so the solution is to pull the android stock images from https://developers.google.com/android/nexus/images. Once done extract the images in both the zip and the tar that is inside the zip. You will see recovery.img inside the tar. One thing about the boot process of TWRP is that it enables adb in preboot meaning while in the boot loop you should have access to adb. With access to adb all you need to do is dd the images over the corresponding partitions: i.e.
PLEASE NOTE NOT FOR THE FEINT OF HEART. I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE.
Quote:
adb push recovery.img recovery.img
adb shell dd if=recovery.img of=/dev/block/<recoverymmcblock>
I dont know if the default recovery has adb push update so id probably recommend doing this on every partition thats inside the tar, i.e. system, boot.
I'm new to xda and obviously I'm not a dev. I just want to root my Axon 7 so I can download root apps. I'm not tech savvy at all and I've created this thread because I have no idea what to do with this page : http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 . Can anyone give a step by step tutorial on how to root my phone?
I feel so so out of place here... please don't scold me :x
inb4 banned cuz didn't read the rules or stickies
I'm running B29.
What version are you running? B20/B27/B29
If you are not tech savvy, do not attempt the root method. It's for advance user and too many people have bricked their phone already. Just read the threads and you will know what I mean.
S8ntsHaz3 said:
What version are you running? B20/B27/B29
Click to expand...
Click to collapse
I'm running B29.
And yes I can probably guess the amount of people who bricked their phones. But what if everything were to be laid out simple and I follow the directions in every respect? I'm not going to start rooting until I know what I'm doing. So don't worry. I'm stupid but I'm not THAT stupid.
No your fine lmao I started with this phone so we're pretty much same level. As to my understanding it is possible but I would wait just a bit for the b29 stuff to come out.
Don't worry, you're not the only one. I've been reading these tutorials and it's all gibberish, lol.... Every phone I have has been rooted within the first day, this phone I've had over 2 months, and I still can't get it. So you're not alone, lol...
There definitely needs to be some cleaning done on this forum, with far too many threads covering the same topics and many OPs being out of date.
Best rooting guide I found was buried in a thread, but is now also out of date if you're running B29.
http://forum.xda-developers.com/showpost.php?p=68302434&postcount=157
It might help if you're still on B27. I used it, had root and bootloader still locked, updated to B29 for the security patch, and was able to keep TWRP but lost root. Having TWRP still allows me to flash all the Google pixel stuff though, which is nice
Bolandk said:
There definitely needs to be some cleaning done on this forum, with far too many threads covering the same topics and many OPs being out of date.
Best rooting guide I found was buried in a thread, but is now also out of date if you're running B29.
http://forum.xda-developers.com/showpost.php?p=68302434&postcount=157
It might help if you're still on B27. I used it, had root and bootloader still locked, updated to B29 for the security patch, and was able to keep TWRP but lost root. Having TWRP still allows me to flash all the Google pixel stuff though, which is nice
Click to expand...
Click to collapse
I'm looking closely at this phone now myself...
I've seen the bootloader thread: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204
I'm only interest in this if I can successfully unlock the bootloader and stock root is possible...from what I've read, BOTH can be done. According to the root thread, the model I need (A2017G) is listed as unlockable, correct? What's the difference between a2017g B02 and B03??
RoOSTA
totalFX said:
I'm new to xda and obviously I'm not a dev. I just want to root my Axon 7 so I can download root apps. I'm not tech savvy at all and I've created this thread because I have no idea what to do with this page : http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 . Can anyone give a step by step tutorial on how to root my phone?
I feel so so out of place here... please don't scold me :x
inb4 banned cuz didn't read the rules or stickies
I'm running B29.
Click to expand...
Click to collapse
OK I have read far too many of these questions here about root on B29 - so here goes.
1. Go to the ZTE website, download the stock B20, and install it.
2. http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204 use this to get TWRP installed on your phone - don't worry about root.
3. http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165 UNLOCK the bootloader
4. http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2 flash boot file, system file, and SuperSU 2.65
Now please relax - anyone here with any dev skills whatsoever are neck deep in other projects (like CM13). B29 hasn't been out long and the only stock image we have from ZTE is B20, which doesn't give us a ton to work with
I also very new to android smartphone and I also feel so so out of place too.
I wish someone make a video how to root this axon 7 phone.
search around youtube jailbrake iPhone is so easy root samsung phone is so easy.... but root axon 7 nothing
I love axon 7 so much now but if I know it's so hard to root i'm just gonna buy samsung phone .
so F..... tired of this youtube ads
ads block is the only reason why I want to root
and that is the only reason why I jailbrake all my ideviese
For me, also with B29, the best and easy way was this from rczrider (thanx a lot). http://forum.xda-developers.com/showpost.php?p=69507226&postcount=766
But one issue after root: I have no access to system, i noticed that, as i install Gsam Battery Monitor root companion, that will install in priv-app but i was write protect. Also RootExplorer was not possible to copy/delete files in system, because write protect. How to change that?
tasar said:
For me, also with B29, the best and easy way was this from rczrider (thanx a lot). http://forum.xda-developers.com/showpost.php?p=69507226&postcount=766
But one issue after root: I have no access to system, i noticed that, as i install Gsam Battery Monitor root companion, that will install in priv-app but i was write protect. Also RootExplorer was not possible to copy/delete files in system, because write protect. How to change that?
Click to expand...
Click to collapse
I forgot to add a final step to that list. I've updated it and here's the new one:
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Flash TWRP (recovery) using the method in the OP (B27 file is fine). You don't need to flash the boot image.
Unlock the bootloader (B27 is fine): http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Boot phone, set it up, whatever
*Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, a fully functioning TWRP (no data encryption issue), and rooted B29. You will not be able to receive OTAs.
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
---------- Post added at 08:45 ---------- Previous post was at 08:02 ----------
In case anyone stumbles across this thread, here's a "Newbie's Guide to Unlocking and Rooting the Axon 7": http://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234
It will be updated as necessary and contains a step-by-step process with links to the appropriate threads.
So are they still releasing a new bootloader unlock tool? Or should I just go ahead and do these steps?
Sent from my ZTE A2017U using Tapatalk
polar2792 said:
So are they still releasing a new bootloader unlock tool? Or should I just go ahead and do these steps?
Click to expand...
Click to collapse
Yes, ZTE still supports bootloader unlocking on the Axon 7. It is currently on hold, but yes, our understanding is that they will be releasing a new process (likely with Nougat).
I can't think of any reason not to unlock now because you can always re-lock if you want to. Who knows what the new process will entail.
rczrider said:
[*] *Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
Click to expand...
Click to collapse
Thanks, reboot disemmcwp fixed my write access to /system
rczrider said:
Yes, ZTE still supports bootloader unlocking on the Axon 7. It is currently on hold, but yes, our understanding is that they will be releasing a new process (likely with Nougat).
I can't think of any reason not to unlock now because you can always re-lock if you want to. Who knows what the new process will entail.
Click to expand...
Click to collapse
Yea well I was hoping the new tool wouldn't kill the warranty but that's wishful thinking, and after some thought I highly doubt that will happen. So time to unlock the bootloader,l and flash TWRP.....soon as I get off work in 9 hours.
Sent from my ZTE A2017U using Tapatalk
polar2792 said:
Yea well I was hoping the new tool wouldn't kill the warranty but that's wishful thinking, and after some thought I highly doubt that will happen. So time to unlock the bootloader,l and flash TWRP.....soon as I get off work in 9 hours.
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I think ZTE will eventually put out a bootloader unlock without killing the warranty. But, yeah, either way it's easy enough to do it on your own now.
rczrider said:
I forgot to add a final step to that list. I've updated it and here's the new one:
Copy everything off your internal storage that you don't want to lose.
Get all of the files you need from the steps below and put them on your microSD card.
Flash TWRP (recovery) using the method in the OP (B27 file is fine). You don't need to flash the boot image.
Unlock the bootloader (B27 is fine): http://forum.xda-developers.com/axon-7/how-to/guide-how-to-unlock-bootloader-stay-t3461165
Flash B29: http://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Boot phone, set it up, whatever
*Reboot to TWRP, go to Advanced > Terminal and type: reboot disemmcwp
This will leave you with an unlocked bootloader, a fully functioning TWRP (no data encryption issue), and rooted B29. You will not be able to receive OTAs.
*This disables write protection and allows your changes (such as AdAway) to stick with reboot. You need to run this before your changes will stick. You don't have to use TWRP (you could also use a terminal emulator or ADB), but I find that since you have to reboot anyway, it's just as easy to do it in TWRP.
---------- Post added at 08:45 ---------- Previous post was at 08:02 ----------
In case anyone stumbles across this thread, here's a "Newbie's Guide to Unlocking and Rooting the Axon 7": http://forum.xda-developers.com/axon-7/how-to/newbies-guide-to-unlocking-rooting-axon-t3496234
It will be updated as necessary and contains a step-by-step process with links to the appropriate threads.
Click to expand...
Click to collapse
Thank you; thank you, THANK YOU!!!!! I tried for an hour or two, using both ADB and Terminal Emulator to apply this "reboot disemmcwp" fix, and I just couldn't get it to work (I'm on B29). Then, I saw your instructions to use TWRP and followed them, and it worked first time, like a charm!
Thanks again - I'm a very happy camper. You da' man, LOL!
Dennis