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
I everyone!
I just tried to connect my Nexus 4 to my windows 8.1 laptop and the phone is not recognised by the PC. It gives me Code 43 error, I tried everything, form fresh driver install to cable change. I also tried on another W7 laptop and nothing pops up there. The phone charges but in Device Manager it is not listed under Google ADB devices but appears with an exclamation mark under USB controllers saying Device Descriptor Request Failed. I fear it is an hardware problem and RMA is the only option left. However, my phone is Rooted, Stock but with modified build.prop, with TW touch recovery and unlocked. Since I have no access to ADB I cannot use the Android SDK tools or anything to flash the factory img. Is there any way in which I could flash back the sock image and lock the bootloader via recovery only?
Thanks everyone :crying::crying:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
Wouldnt it be possible to flash the 4.3 stock rom zip in his custom recovery, root it and flash the stock recovery with flashify, and then unroot the device?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
This was what I was thinking, however, the main issue would be locking the bootloader again
simms22 said:
you dont need adb to flash the factory img. you need fastboot to flash it, via your bootloader. but, fastboot still needs to see your device, so thd driver still nedds to be installed.
Click to expand...
Click to collapse
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
c0sk said:
This was what I was thinking, however, the main issue would be locking the bootloader again
I dont think is a driver problem, I had driver issues before but i got different errors and solved them easily. I do believe is an hardware failure this time
Click to expand...
Click to collapse
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
mrhiab said:
READ THIS 1st
http://forum.xda-developers.com/showthread.php?t=2010312
Scroll down to the 2nd post.
Click to expand...
Click to collapse
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
c0sk said:
Thanks, exactly what I was looking for! :victory:
However, since I am already on stock andshould have a backup of the build.prop (i just added a line to get rid of the on screen buttons) would you recommend flashing everything again or just lock bootloader, unroot and flash stock recovery only?
Click to expand...
Click to collapse
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
efrant said:
Restoring the original build.prop, locking the bootloader, remove root and flash stock recovery will be just fine.
Click to expand...
Click to collapse
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
c0sk said:
Ok! I did a very stupid thing, I did restore my build.prop but without any backup files. The system does not boot up now! Root has been removed and bootloader locked, however, the custom recovery is still there and I did not copy the stock image! Is there any other way in which I could restore the stock recovery or am I screwed??
Click to expand...
Click to collapse
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
efrant said:
When you restored your build.prop, did you set the proper permissions, i.e., 644? If not, does your recovery allow you to do so? Try it and see if you boot.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
c0sk said:
I fixed that problem in a different way, more barbaric but effective. I booted it up and managed to get JDQ39 files on the phone via dropbox: odexed image, boot and recovery. I flashed the first 2 (wanted to keep the recovery for safety and flash the stock one at a second stage). Booted successfully and removed root via SuperSu settings. Once flashed stock recovery, am I right to assume it will be completely stock and therefore ready for RMA? Moreover, can I accept OTA since is fully stock?
Thanks!!!!!
edit: Su installer app was there after flashed recovery and did factory reset
Click to expand...
Click to collapse
The way you removed SuperSU must have not worked properly. (I've never tried doing it from the SuperSU settings.) In any case, there's nothing more you can do now, so might as well send it in for RMA.
Hi
Earlier today I was running 7.0.0. Stock No root with unlocked bootloader, all of a sudden random reboots. Until it no longer wanted to go past Google screen. Plugged into nexus root toolkit, tried flashing stock, downgrading to marshmallow, locking bootloader, unlocking again, multiple times and tries with no luck. The device now will only allow me to get into bootloader when I plug it to charge and immediately press power & -volume. I would appreciate it any help I can get in this.
Thanks
roelmmata said:
Hi
Earlier today I was running 7.0.0. Stock No root with unlocked bootloader, all of a sudden random reboots. Until it no longer wanted to go past Google screen. Plugged into nexus root toolkit, tried flashing stock, downgrading to marshmallow, locking bootloader, unlocking again, multiple times and tries with no luck. The device now will only allow me to get into bootloader when I plug it to charge and immediately press power & -volume. I would appreciate it any help I can get in this.
Thanks
Click to expand...
Click to collapse
Just about everyone in this thread is in similar boat. I think there is one that was on 6.0, but most on npd90x I believe. There might be something useful to help you with. What version of twrp are you using? 3.0.2-1 has a bug with efs partition.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Fe Mike said:
Just about everyone in this thread is in similar boat. I think there is one that was on 6.0, but most on npd90x I believe. There might be something useful to help you with. What version of twrp are you using? 3.0.2-1 has a bug with efs partition.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Click to expand...
Click to collapse
I had tried to flash twrp but had gotten an error saying I wasn't in adb recovery and never got that to work.
roelmmata said:
I had tried to flash twrp but had gotten an error saying I wasn't in adb recovery and never got that to work.
Click to expand...
Click to collapse
You mean flash to install TWRP or you were trying to install via ADB and your phone wasn't in recovery? You flash the TWRP image to install it from your bootloader via fastboot commands. You can load other files onto your phone via ADB sideload while in recovery. It is helpful to be clear on the forums so people can better help.
Sent from my Nexus 6P using Tapatalk
ultyrunner said:
You mean flash to install TWRP or you were trying to install via ADB and your phone wasn't in recovery? You flash the TWRP image to install it from your bootloader via fastboot commands. You can load other files onto your phone via ADB sideload while in recovery. It is helpful to be clear on the forums so people can better help.
Click to expand...
Click to collapse
I had been trying to install twrp onto my phone through the toolkit, using the "root and install custom recovery option" but then it got the error and cancelled.
roelmmata said:
I had been trying to install twrp onto my phone through the toolkit, using the "root and install custom recovery option" but then it got the error and cancelled.
Click to expand...
Click to collapse
Again, without knowing what you have/haven't done in advance, it's hard to be of much help. To run ADB commands, you need to have USB debugging enabled on the device from settings. So, if you haven't done that, you can't do anything via ADB/fastboot and prior to that, I see you said you did have an unlocked bootloader.
Beyond those two things, which are reiterated within it, I'd strongly recommend following Heisenberg's guide at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 to do any flashing on your phone. This begins by ensuring you get a working version of the drivers installed to your machine via the Android SDK. Since your BL is unlocked, you should be able to flash TWRP via fastboot command. Also, ensure you are installing version 3.0.2-3, the latest 'unofficial' that is bug-free.
Fe Mike said:
Just about everyone in this thread is in similar boat. I think there is one that was on 6.0, but most on npd90x I believe. There might be something useful to help you with. What version of twrp are you using? 3.0.2-1 has a bug with efs partition.
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921
Click to expand...
Click to collapse
Thanks I try it out!
ultyrunner said:
Again, without knowing what you have/haven't done in advance, it's hard to be of much help. To run ADB commands, you need to have USB debugging enabled on the device from settings. So, if you haven't done that, you can't do anything via ADB/fastboot and prior to that, I see you said you did have an unlocked bootloader.
Beyond those two things, which are reiterated within it, I'd strongly recommend following Heisenberg's guide at http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928 to do any flashing on your phone. This begins by ensuring you get a working version of the drivers installed to your machine via the Android SDK. Since your BL is unlocked, you should be able to flash TWRP via fastboot command. Also, ensure you are installing version 3.0.2-3, the latest 'unofficial' that is bug-free.
Click to expand...
Click to collapse
Hey again
I used guide specifically to go back to stock, combined with a couple times of wiping in stock recovery I finally got the phone to boot up! However I've learned something new, the phone will only stay on if I'm plugged into charger, and as soon as it's unplugged it turns off. Any other suggestions?
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
HI
I WAS ON 7.1.2 PURE NEXUS rom and...
i've decided to flash the stock image based on 6.0.1
i pluged my 6p to PC and head straight to NexusRootToolkit and i pick up my wanted image and the procces goes well untill the 6p bootloping in google screen . i changed the image and didnt work
one thing has killin me the bootloader was locked before i do that BUT THE PHONE IN bootloader menu shows me that device is unlocked
any help ... i want to go back to 6.0.1 safely
thank you. lol i swear if the issue got fixed i'll never ever rooting anymore loool
Try to flash the image with fastboot, if the bootloader is unlocked, don't use such tools.
Edit: it doesn't matter that your device was rooted, and why you want to flash old marshmallow image, flash the latest nougat.
Use the heisenberg guide. Adb shell using fastboot commands has never failed me.
coremania said:
Try to flash the image with fastboot, if the bootloader is unlocked, don't use such tools.
Edit: it doesn't matter that your device was rooted, and why you want to flash old marshmallow image, flash the latest nougat.
Click to expand...
Click to collapse
OMG! what a Stupid Problem, i just flashed Nougat version not MM and it works ..
i checked the OEM it says bootloader is already unlocked.
is it safe now to go back to MM via Nexus Root toolkit?
Abdulaziz6p said:
OMG! what a Stupid Problem, i just flashed Nougat version not MM and it works ..
i checked the OEM it says bootloader is already unlocked.
is it safe now to go back to MM via Nexus Root toolkit?
Click to expand...
Click to collapse
I advice you to use fastboot, yes you have to read a little bit for this, but you will know what you are doing. And as long as you're flashing your phone don't lock your bootloader.
Sure you can move to mm, if you want to do it with toolkits I can't give you any support because I don't use them.
Better you read a little bit and you will understand what you are doing.