Related
Mine says the upgrade to 4.5.141 is available to download. My Atrix is rooted with locked bootloader, I presuming I am going to lose root with the upgrade.
If so, what rooting method will work?
Thanks for your help.
PS: Will this worK?
https://market.android.com/details?id=org.projectvoodoo.otarootkeeper
charlyee said:
Mine says the upgrade to 4.5.141 is available to download. My Atrix is rooted with locked bootloader, I presuming I am going to lose root with the upgrade.
If so, what rooting method will work?
Thanks for your help.
PS: Will this worK?
https://market.android.com/details?id=org.projectvoodoo.otarootkeeper
Click to expand...
Click to collapse
Just unlock your bootloader and flash a new ROM on your phone. Most of the ROMs available for our phone have that update or better already on the ROM.
Sent from Neutrino, a planet far, far away...
cwburns32 said:
Just unlock your bootloader and flash a new ROM on your phone. Most of the ROMs available for our phone have that update or better already on the ROM.
Sent from Neutrino, a planet far, far away...
Click to expand...
Click to collapse
Thanks, but I don't want to take the route of custom ROMs, sorry.
I had to unlock my bootloader first using RSDlite and the small .sbf file (pudding.rar) Click here to download
My bootloader was supposed to be already unlocked but I guess the updated firmware didn't realize it. I couldn't run fastboot flash without getting an error
I then rooted by flashing preinstall.img and running commands to install the superuser binary and .apk. Instructions here
I don't know of a way to root 4.5.141 without unlocking the bootloader first. If you find a way let me know
http://briefmobile.com/motorola-atrix-4g-root should work.
lauterm said:
http://briefmobile.com/motorola-atrix-4g-root should work.
Click to expand...
Click to collapse
Same thing I used... different source. Still it requires an unlocked bootloader to flash images.
I believe the OP is looking for a root option that will work with a locked bootloader.
charlyee said:
Thanks, but I don't want to take the route of custom ROMs, sorry.
Click to expand...
Click to collapse
Just wondering.. Why not? ;o
nthon9 said:
Just wondering.. Why not? ;o
Click to expand...
Click to collapse
It's kind of a "Been there, done that" kind of thing from my Win Mob days. lol
I am pefectly happy with stock Atrix ROMs, and just want to be able to retain root or re root to use a couple of apps like Titanium Backup.
Has anyone with an unlocked bootloader/rooted Atrix tried the update?
I like to stick with the stock rom for now but I haven't found directions for updating to 141 yet. I'd like to keep root and not hard brick my Atrix...After the 2nd time Moto might get suspicious
I wasn't able to use the OTA updates once I rooted (even before I unlocked my bootloader). Of course, that could be Bell building in a check. I even tried unrooting (using GingerBreak) and that still wouldn't allow me to use an OTA update.
I would think you'll have to root, unlock bootloader, and then flash an firmware file from this tread: http://forum.xda-developers.com/showthread.php?t=1125944.
Actually, you're right in that the OTA update will probably fail without me going to a more "out of the box" state. I suppose I'd have to first create a nandroid, a titanium backup then flash my phone with a 4.5.91 stock image using fastboot, do the OTA, then re-root, and restore the titanium backup to get back to where I was. And if anything fails restore from my nandroid.
Does that sound right?
I've heard there could be issues relating to going back to a locked bootloader file. So I'm not sure on specifics there. I just run CyanogenMod to avoid all that stuff.
penderway said:
Same thing I used... different source. Still it requires an unlocked bootloader to flash images.
I believe the OP is looking for a root option that will work with a locked bootloader.
Click to expand...
Click to collapse
preinstall fastboot method works on a locked bootloader...at least it does for me (locked, rooted and on 141).
gnahc79 said:
preinstall fastboot method works on a locked bootloader...at least it does for me (locked, rooted and on 141).
Click to expand...
Click to collapse
So...in fastboot mode, you were able to run fastboot flash preinstall preinstall.img and thus successfully create the "preinstall\" partition with the necessary files on your phone without getting an error message???
My bootloader was unlocked long ago but I still couldn't flash the preinstall partition without running the pudding unlock .sbf first. Idk
I wasn't even able to boot into fastboot without unlocking the bootloader first.
penderway said:
So...in fastboot mode, you were able to run fastboot flash preinstall preinstall.img and thus successfully create the "preinstall\" partition with the necessary files on your phone without getting an error message???
Click to expand...
Click to collapse
yep, followed all of the steps and every one is successful. I'm very risk-averse when it comes to messing with my phone, so I've never unlocked my phone. Only root.
I love how no one is answering your question just telling you to unlock your bootloader...
I downloaded the ota update, installed and got failed to boot 4 starting rsd node.. i had unlocked bootloader before update help please!! I pulled the battery for now.
gnahc79 said:
yep, followed all of the steps and every one is successful. I'm very risk-averse when it comes to messing with my phone, so I've never unlocked my phone. Only root.
Click to expand...
Click to collapse
Well then, that settles it. The OP (who also doesn't have an unlocked bootloader) should be able to do the same.
gnahc79 said:
yep, followed all of the steps and every one is successful. I'm very risk-averse when it comes to messing with my phone, so I've never unlocked my phone. Only root.
Click to expand...
Click to collapse
Is there any way to get step by step instructions for this
Hello,
after I've unlocked the bootloader can I still get OTA updates?
I'll just be on stock ROM with root. I also make a backup with nothing on except TWRP.
Lets hope so
LanceM said:
Lets hope so
Click to expand...
Click to collapse
have you tried it?
Yes you'll be able to get new updates with unlock bootloader.
DrakenFX said:
Yes you'll be able to get new updates with unlock bootloader.
Click to expand...
Click to collapse
Can you elaborate on this? The last I heard unlocking the bootloader (using the official procedure) stops OTA. Has this changed ?
mh127 said:
Can you elaborate on this? The last I heard unlocking the bootloader (using the official procedure) stops OTA. Has this changed ?
Click to expand...
Click to collapse
I never said Official getting OTA's , but i believe this is going to change staring with the new Unlock Bootloader procedure.
DrakenFX said:
I never said Official getting OTA's , but i believe this is going to change staring with the new Unlock Bootloader procedure.
Click to expand...
Click to collapse
OK, but AFAIK even with the unofficial unlock (with TWRP and root) the OTA will fail - unless you unroot and go back to locked stock bootloader. Correct me if I am wrong.
mh127 said:
OK, but AFAIK even with the unofficial unlock (with TWRP and root) the OTA will fail - unless you unroot and go back to locked stock bootloader. Correct me if I am wrong.
Click to expand...
Click to collapse
In my experience, what makes the difference - so far - is the recovery. Official ZTE updates and ROMS only flash through the stock recovery.
Unlocked bootloader has made no difference to me.
mh127 said:
OK, but AFAIK even with the unofficial unlock (with TWRP and root) the OTA will fail - unless you unroot and go back to locked stock bootloader. Correct me if I am wrong.
Click to expand...
Click to collapse
If you try to flash Official OTA yes will fail, cuz isn't modded to skip partitions check.
DrakenFX said:
If you try to flash Official OTA yes will fail, cuz isn't modded to skip partitions check.
Click to expand...
Click to collapse
This is getting confusing. "Getting OTA updates" (as OP asks) usually means that the update installs "on its own" by tapping notification rather than flashing via recovery, which is a bit more complicated process.
So back to the OP question: With root and TWRP can one get over-the-air official updates from ZTE without going to the recovery manually? I believe the answer to that is NO.
That said, there is probably a work around in getting the update, probably by manually flashing partitions that have changed in the update.
Is this right?
mh127 said:
This is getting confusing. "Getting OTA updates" (as OP asks) usually means that the update installs "on its own" by tapping notification rather than flashing via recovery, which is a bit more complicated process.
So back to the OP question: With root and TWRP can one get over-the-air official updates from ZTE without going to the recovery manually? I believe the answer to that is NO.
That said, there is probably a work around in getting the update, probably by manually flashing partitions that have changed in the update.
Is this right?
Click to expand...
Click to collapse
Well OPs Question actually was if OTA Updates are possible with unlocked boot-loader...
Root and TWRP is a whole different scenario and won't work with OTA for sure as OTA needs stock recovery and will check for unmodified system (not rooted)...
But if you are on stock with unlocked bootloader you should get notified about OTAs (as until now it did not check for bootloader lock status, but that could change in future) although I don't know if it will install correctly
Gachmuret said:
Well OPs Question actually was if OTA Updates are possible with unlocked boot-loader...
Root and TWRP is a whole different scenario and won't work with OTA for sure as OTA needs stock recovery and will check for unmodified system (not rooted)...
But if you are on stock with unlocked bootloader you should get notified about OTAs (as until now it did not check for bootloader lock status, but that could change in future) although I don't know if it will install correctly
Click to expand...
Click to collapse
OP mentioned that he used TWRP to make a backup, I assumed he has replaced stock recovery with TWRP, but that may not necessarily be the case.
If your device has an bootloader that was unlocked "unofficially" (either via sideloading the official unlock method or DrakenFX & Unjustifieddev's method), but is still completely stock (stock System, stock Boot, stock Recovery, stock everything besides the unlocked bootloader), you can still receive and apply OTAs. However, if you changed any of the partitions, like boot.img (root), recovery.img (TWRP), system.img (changes to system), you will still receive the OTA, but you won't be able to apply it, the update will fail. If you went through the official bootloader unlocking process, which involved you submitting a form to ZTE with your device's IMEI, you would no longer be able to receive OTAs.
What I did was sideload the official B20_Boot on by B20 device, unlocked my bootloader, flashed TWRP, flashed the TWRP Stock B20 dumps that were posted here on XDA, and reflashed stock recovery. This made my device completely stock B20 besides the unlocked bootloader. I then applied the official B27 OTA update, and it installed fine. I then reflashed TWRP (since my bootloader was still unlocked) and re-rooted my device.
If a new update comes out, I can just reflash the stock B27 TWRP dump posted here on XDA, reflash stock recovery, (if needed, reflash stock fastboot), and apply OTA.
xtermmin said:
...
What I did was sideload the official B20_Boot on by B20 device, unlocked my bootloader, flashed TWRP, flashed the TWRP Stock B20 dumps that were posted here on XDA, and reflashed stock recovery. This made my device completely stock B20 besides the unlocked bootloader. I then applied the official B27 OTA update, and it installed fine. I then reflashed TWRP (since my bootloader was still unlocked) and re-rooted my device.
If a new update comes out, I can just reflash the stock B27 TWRP dump posted here on XDA, reflash stock recovery, (if needed, reflash stock fastboot), and apply OTA.
Click to expand...
Click to collapse
So, with this procedure, do you lose all the app installations/other customizations? I believe that all of the application data is on a non-system partition (/data?) but did you need to go through all of the setting up of the phone after you did the upgrade this way?
rayman2k1 said:
So, with this procedure, do you lose all the app installations/other customizations? I believe that all of the application data is on a non-system partition (/data?) but did you need to go through all of the setting up of the phone after you did the upgrade this way?
Click to expand...
Click to collapse
Yes. Unlocking the bootloader does a factory reset, and doing a TWRP restore of a stock image (which overwrites your current partitions) overwrites what you had before.
EDIT: Actually, I think Internal Storage gets erased as well, but your microSD card will be fine.
xtermmin said:
Yes. Unlocking the bootloader does a factory reset, and doing a TWRP restore of a stock image (which overwrites your current partitions) overwrites what you had before.
EDIT: Actually, I think Internal Storage gets erased as well, but your microSD card will be fine.
Click to expand...
Click to collapse
Hmm, had guessed as much. I knew the bootloader unlocking did a wipe, but was hoping that recovery-flashing would do a backup/restore, as if the update had been applied through the in-ROM update procedure. Unless the OTA process only gets deltas and flashes them, leaving fs intact.
rayman2k1 said:
Hmm, had guessed as much. I knew the bootloader unlocking did a wipe, but was hoping that recovery-flashing would do a backup/restore, as if the update had been applied through the in-ROM update procedure. Unless the OTA process only gets deltas and flashes them, leaving fs intact.
Click to expand...
Click to collapse
Yeah, the OTA doesn't straight-up replace partitions, it checks and patches the existing partitions, so if a partition has been changed, the OTA install will fail.
Hello friends
My phone is HTC One m8w
There isn't "update" in
Setting
About
Android version,
5.0.1
Software number
1.0.0.m8w
Build number
4.19.1402.15 CL458284 release-keys
Please help me for this problem
How can I update my phone?
Thanks a lot
Hello, I experienced something similar- complete absence of system update! A little digging revealed that any modifications to the system partition would render the device un-updateable, so naturally I downloaded the complete marshmallow package update for my device, booted into standard recovery, and updated from sd card
Hope this helps
Ta3miyyasandwich said:
Hello, I experienced something similar- complete absence of system update! A little digging revealed that any modifications to the system partition would render the device un-updateable, so naturally I downloaded the complete marshmallow package update for my device, booted into standard recovery, and updated from sd card
Hope this helps
Click to expand...
Click to collapse
There isn't any update for my build number
Sent from my HTC_M9pw using Tapatalk
if you are willing to, just root your phone and flash the marshmallow rom on to your phone and use titanium backup to backup everything before you do so.
you can root your phone,flash twrp recovery,flash Marshmallow rom.
lmentor said:
you can root your phone,flash twrp recovery,flash Marshmallow rom.
Click to expand...
Click to collapse
That's exactly what I just said
justinchao740 said:
if you are willing to, just root your phone and flash the marshmallow rom on to your phone
Click to expand...
Click to collapse
You don't need root to install TWRP, nor to install a custom ROM.
Exception is Verizon, where you need root to s-off, and then unlock bootloader; as bootloader unlock by HTCDev.com is not supported for that version alone.
redpoint73 said:
You don't need root to install TWRP, nor to install a custom ROM.
Exception is Verizon, where you need root to s-off, and then unlock bootloader; as bootloader unlock by HTCDev.com is not supported for that version alone.
Click to expand...
Click to collapse
If you get bootloader unlocked, you basically rooted your device cause now you are allowed to modify the system data and make modification that can result in unusable phone. Plus if you are willing to take the risk of unlocking your bootloader, why don't you just root anyways, its just a matter of flashing super su zip.
justinchao740 said:
If you get bootloader unlocked, you basically rooted your device cause now you are allowed to modify the system data and make modification that can result in unusable phone .
Click to expand...
Click to collapse
No, you didn't. Root is a very specific thing. You either have root (SU) priviledge, or you don't. Unlocked bootloader does not give you root privilege. It only allows you to flash unsigned zips to certain partitions.
justinchao740 said:
Plus if you are willing to take the risk of unlocking your bootloader, why don't you just root anyways, its just a matter of flashing super su zip.
Click to expand...
Click to collapse
Because it would be a wasted step (completely unnecessary), if you are going to flash a custom ROM.
redpoint73 said:
No, you didn't. Root is a very specific thing. You either have root (SU) priviledge, or you don't. Unlocked bootloader does not give you root privilege. It only allows you to flash unsigned zips to certain partitions.
Because it would be a wasted step (completely unnecessary), if you are going to flash a custom ROM.
Click to expand...
Click to collapse
Think of it this way. If you flashed a cm ROM without root in the first place, you would get root. I'm not saying unlocking bootloader immediately give you root access but it allows almost anything that you flash to have root access
justinchao740 said:
Think of it this way. If you flashed a cm ROM without root in the first place, you would get root. I'm not saying unlocking bootloader immediately give you root access but it allows almost anything that you flash to have root access
Click to expand...
Click to collapse
Some folks keep incorrectly stating that you need root to flash custom recovery on this device (on some devices, you do - but not this one). I'm just trying to make sure that misinformation doesn't keep getting conveyed (the post after yours said it, too).
Stating the process precisely, is the best way to do that.
redpoint73 said:
Some folks keep incorrectly stating that you need root to flash custom recovery on this device (on some devices, you do - but not this one). I'm just trying to make sure that misinformation doesn't keep getting conveyed (the post after yours said it, too).
Stating the process precisely, is the best way to do that.
Click to expand...
Click to collapse
Agreed plus my post never stated anything about rooting.
justinchao740 said:
Agreed plus my post never stated anything about rooting.
Click to expand...
Click to collapse
While my intent is not to be the guy that always has the last word; I also can't let you state a complete falsehood.
justinchao740 said:
if you are willing to, just root your phone and flash the marshmallow rom
Click to expand...
Click to collapse
Hi,
So quick summary of what happened. I went to make coffee, came back to desk and my N6P has been stuck in boot loop.
It was running the latest Android 7.1.1 build (NPF26F)
I can access fastboot and recovery fine. However, I can't flash anything from fastboot as the device wasn't unlocked.
I tried wiping data / factory & cache from fastboot and recovery with no difference in result.
I also can't seem to sideload anything as all the OTA's from google come back with 'Can't install this package (%Date of build%) over newer build.
The latest OTA i can find is: 7.1.1 NMF26F (angler-ota-nmf26f-61b4a915.zip)
I also tried the official 7.0 NBD91K (angler-ota-nbd91k-32c2eac8.zip) with the same result.
Is there a different OTA I can use or can I force it to sideload an older version or any other suggestions?
I really don't want to have to deal with my telco. I'll be without a phone for weeks if I have to :'(
I have a phone with the same problem. Haven't gotten an answer yet. I am starting to wonder if it's an issue with the build.
bkgovols said:
I have a phone with the same problem. Haven't gotten an answer yet. I am starting to wonder if it's an issue with the build.
Click to expand...
Click to collapse
When you say haven't gotten an answer yet.... you posted it somewhere? I bet an easy fix for google would be to release a newer full OTA... but unless they respond in a day, i'll be returning phone...
gunigugu said:
Hi,
So quick summary of what happened. I went to make coffee, came back to desk and my N6P has been stuck in boot loop.
It was running the latest Android 7.1.1 build (NPF26F)
I can access fastboot and recovery fine. However, I can't flash anything from fastboot as the device wasn't unlocked.
I tried wiping data / factory & cache from fastboot and recovery with no difference in result.
I also can't seem to sideload anything as all the OTA's from google come back with 'Can't install this package (%Date of build%) over newer build.
The latest OTA i can find is: 7.1.1 NMF26F (angler-ota-nmf26f-61b4a915.zip)
I also tried the official 7.0 NBD91K (angler-ota-nbd91k-32c2eac8.zip) with the same result.
Is there a different OTA I can use or can I force it to sideload an older version or any other suggestions?
I really don't want to have to deal with my telco. I'll be without a phone for weeks if I have to :'(
Click to expand...
Click to collapse
You can unlock bootloader if you have fast boot. The computer needs to recognise your phone. Then just follow the steps in the beginner's guide.
tropical cactus said:
You can unlock bootloader if you have fast boot. The computer needs to recognise your phone. Then just follow the steps in the beginner's guide.
Click to expand...
Click to collapse
No, unfortunately, you can no longer unlock nexus devices from just the bootloader. You need access to Android OS.
gunigugu said:
No, unfortunately, you can no longer unlock nexus devices from just the bootloader. You need access to Android OS.
Click to expand...
Click to collapse
Install Android SDK or find adb mini bundle. Download latest factory images from Google's website. Run this command to sideload the factory image. You DON'T need unlocked bootloader for this command.
HTML:
adb sideload yourFactoryImagesFile
gunigugu said:
Hi,
...I can access fastboot and recovery fine. However, I can't flash anything from fastboot as the device wasn't unlocked....
Click to expand...
Click to collapse
You never went into Developer Options and toggled the "allow OEM Unlock"? If not, you will not be able to unlock bootloader via fastboot.
And are you positive you did a proper "factory reset" from recovery? From stock, this should get you out of a boot loop. The naming convention Google used for DP2/Public Release was screwed up and I've seen others reporting the inability to flash OTA's but the solution was to flash the full Google image. As someone else suggested, until a new OTA hits with a newer (higher) number, you may be out of luck. Maybe someone with more experience can help with perhaps altering the OTA signature?
fapste said:
Install Android SDK or find adb mini bundle. Download latest factory images from Google's website. Run this command to sideload the factory image. You DON'T need unlocked bootloader for this command.
HTML:
adb sideload yourFactoryImagesFile
Click to expand...
Click to collapse
Unfortunately as mentioned in original post 'I also can't seem to sideload anything as all the OTA's from google come back with 'Can't install this package (%Date of build%) over newer build'
v12xke said:
You never went into Developer Options and toggled the "allow OEM Unlock"? If not, you will not be able to unlock bootloader via fastboot.
And are you positive you did a proper "factory reset" from recovery? From stock, this should get you out of a boot loop. The naming convention Google used for DP2/Public Release was screwed up and I've seen others reporting the inability to flash OTA's but the solution was to flash the full Google image. As someone else suggested, until a new OTA hits with a newer (higher) number, you may be out of luck. Maybe someone with more experience can help with perhaps altering the OTA signature?
Click to expand...
Click to collapse
Yup never did it :'(
Didn't think I needed to unlock / root my devices anymore since I can get all the functionality out of stock android these days. Though now I feel like I'm being punished for not unlocking it :'(
I'm positive I did a factory reset from recovery. I do believe flashing a full google image would fix the issue, but im unable to from fastboot as device is locked and sideload images appear to be older :'(
Really sorry to hear this, and I know being without the phone even for a day or two is inconvenient at best. Could be critical for your work or school. Most every bootloop I have encountered, I've been able to fix by re-flashing the kernel. Either stock or custom... like EX Kernel. Have you ever played with WugFresh's NRT? You can temp flash TWRP and maybe temp flash or flash the kernel? This probably won't work with a locked bootloader If you could just start the OS, you could toggle the OEM unlock. At a minimum, TWRP will give you a file manager, MTP file transfer, wiping and other tools. If you have time, it may be worth a try. Other than that, successfully altering the signature of the OTA may work, but I've not seen any work on this, but have never had to look. I'd keep searching for ppl having the difficulty of going from DP2 to Public Release (older/newer) and see if there was another solution other than flashing the full image, which obviously you can't do right now. Good luck, and let us know if you make any progress.
Edit : Read here for possible help. This may work in conjunction with getting TWRP installed via NRT.
gunigugu said:
Unfortunately as mentioned in original post 'I also can't seem to sideload anything as all the OTA's from google come back with 'Can't install this package (%Date of build%) over newer build'
Click to expand...
Click to collapse
How can flashing the latest factory images released on 6 December can give this error? Make sure you download the 6 December factory images
fapste said:
How can flashing the latest factory images released on 6 December can give this error? Make sure you download the 6 December factory images
Click to expand...
Click to collapse
Many ppl have had problems sideloading the OTA coming from DP2 to Public Release NPF26F->>NMF26F and not just the 6P. Because the Public release numerically is "older" the OTA will not flash. When unlocked, the solution was to flash the full Google image, rather than the OTA. Why in their infinite wisdom Google did this I have no idea. Options are very slim when your bootloader is locked and you are stuck in a boot loop. OP cannot flash a full image when the NMF26F OTA is parsed as being "older".
fapste said:
How can flashing the latest factory images released on 6 December can give this error? Make sure you download the 6 December factory images
Click to expand...
Click to collapse
I believe it's because the latest OTA on https://developers.google.com/android/ota is 7.1.1 (NMF26F) and my phone is already running 7.1.1 build (NPF26F).
v12xke said:
Many ppl have had sideloading OTA coming from DP2 to Public Release NPF26F->>NMF26F and not just the 6P. Because the Public release numerically is "older" the OTA will not flash. When unlocked, the solution was to flash the full Google image, rather than the OTA. Why in their infinite wisdom Google did this I have no idea. Options are very slim when your bootloader is locked and you are stuck in a boot loop. OP cannot flash a full image when the NMF26F OTA is parsed as being "older".
Click to expand...
Click to collapse
This guy gets it!!! Yeah, I've unlocked a lot of my older devices and am comfortable with 'messing' my devices, but I didn't with the 6p as the stock experience is great now. But now I feel like I'm being punished because my device is dead with no recourse for action. Unless google release a newer full OTA.
If you haven't given up yet and gone back to the carrier with the phone, try the NRT toolkit to temp flash TWRP, and then FORMAT each partition, then try to reflash OTA with TWRP. Under "Advanced Utilities".
v12xke said:
If you haven't given up yet and gone back to the carrier with the phone, try the NRT toolkit to temp flash TWRP, and then FORMAT each partition, then try to reflash OTA with TWRP. Under "Advanced Utilities".
Click to expand...
Click to collapse
This will work on a locked device? I'll give it a crack and report back.
v12xke said:
If you haven't given up yet and gone back to the carrier with the phone, try the NRT toolkit to temp flash TWRP, and then FORMAT each partition, then try to reflash OTA with TWRP. Under "Advanced Utilities".
Click to expand...
Click to collapse
Yeah failed :'( (remote: unlock device to use this command)
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work i encountered a problem like this too
boxguy1 said:
[Guide] Fool/Noob proof way to do clean installs on Nexus Devices
http://forum.xda-developers.com/nexu...talls-t3518311
try this clean install should work i encountered a problem like this too
Click to expand...
Click to collapse
Firstly your link is broken: It's http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311
Secondly as I've mentioned a few times including the OP. The device is locked. You need access to Android OS to unlock. It can not be done just from bootloader. So this does not work, but thanks for posting the suggestion anyway.
Deleted
---------- Post added at 05:53 AM ---------- Previous post was at 05:34 AM ----------
gunigugu said:
Firstly your link is broken: It's http://forum.xda-developers.com/nexus-6p/general/guide-fool-noob-proof-to-clean-installs-t3518311
Secondly as I've mentioned a few times including the OP. The device is locked. You need access to Android OS to unlock. It can not be done just from bootloader. So this does not work, but thanks for posting the suggestion anyway.
Click to expand...
Click to collapse
Sorry I thought it would have worked you should wait until the January security patch as all the other users said best of luck
In short, phone is stuck in a bootloop for no reason that I would know.
Out of warranty, so that option isn't available.
I really just need to get the bootloader unlocked, but I can't access the main screen.
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
I need to be able to flash a full factory image, which is why I need the bootloader unlocked.
Thank you!
matistight said:
In short, phone is stuck in a bootloop for no reason that I would know.
Out of warranty, so that option isn't available.
I really just need to get the bootloader unlocked, but I can't access the main screen.
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
I need to be able to flash a full factory image, which is why I need the bootloader unlocked.
Thank you!
Click to expand...
Click to collapse
Hi... Did the bootloop came from nowhere or what were you doing when it happened?
What error do you get when you sideload the ota?
Tried formatting cache or factory reset?
Edit: You can't downgrade with a locked bootloader.
matistight said:
I can access the recovery and bootloader, but when I tried doing an ota update through recovery, (even with NUF26K) it kept failing.
Click to expand...
Click to collapse
You will not be able to unlock the bootloader without booting the OS and entering Dev Options to allow "OEM Unlocking". Now that the 7.1.2 beta is out, that OTA is worth giving a shot. I'd certainly try the suggestions above if the beta OTA fails. If a factory reset does not work, you may be able to fastboot format userdata and cache and try the OTA route again.
v12xke said:
You will not be able to unlock the bootloader without booting the OS and entering Dev Options to allow "OEM Unlocking". Now that the 7.1.2 beta is out, that OTA is worth giving a shot. I'd certainly try the suggestions above if the beta OTA fails. If a factory reset does not work, you may be able to fastboot format userdata and cache and try the OTA route again.
Click to expand...
Click to collapse
Completely gave up on this, but I will give you the error when I get home, it was somewhat contradicting.
I have a Oneplus X I am using now, but the screen size is killing my hands! Atleast I am not out a phone
Maybe there is a way to erase/corrupt the system and bootloader and ota with a 6.0.x? I didnt really like android N
matistight said:
Completely gave up on this, but I will give you the error when I get home, it was somewhat contradicting.
I have a Oneplus X I am using now, but the screen size is killing my hands! Atleast I am not out a phone
Maybe there is a way to erase/corrupt the system and bootloader and ota with a 6.0.x? I didnt really like android N
Click to expand...
Click to collapse
If you erase or corrupt the bootloader then the phone is hard bricked (if it already isn't). I think you need an unlocked bootloader to do that anyways. Any flashing or erasing command in fastboot is going to need an unlocked bootloader. Even if you did somehow manage to delete the bootloader, without the phone being unlocked you can't flash a new one = hard brick.
If your phone is BL locked, you can't access Android, recovery doesn't help, you're mostly out of luck. Some people have said that using MSkips toolkit recovered their phones, but others had no such luck. There's a lot of people in the same boat as you. Others have tried calling Google about the issue despite their warranty status. Your phone is locked and a stock OTA took it out, from the sounds of it. Maybe they'll be willing to work with you. The worst they can do is say no, can't hurt to try. Good luck!
Why do you want to downgrade?
rchtk said:
Why do you want to downgrade?
Click to expand...
Click to collapse
Never really like 7.x and it has been the only OS that has bricked my phone without being rooted.
Unfortunately you can neither use an OTA to downgrade nor flash a factory image without BL unlocked.
And I'm not sure that would help either. Your device corrupted itself for a reason and that might be the flash failing (which the Nougat update exhibited, but Nougat isn't the root cause probably). You could rather wait for a higher OTA and hope.
Any recovery log to post?
How old is the phone? 1 year?