Hey guys,
I want to unlock my bootloader so that I could try some of the awesome ROMs the devs have made/ported to the RAZR M.
I wanted to find out if I could RELOCK my bootloader in the case of needing to take it back to Verizon or Motorola in the case of it being damaged or something. I know how to unroot on the RAZR and how to do it all on my Nexus 7, just cant find hardly anything for this phone.
Thanks in advanced!!!
lukkypuggy said:
Hey guys,
I want to unlock my bootloader so that I could try some of the awesome ROMs the devs have made/ported to the RAZR M.
I wanted to find out if I could RELOCK my bootloader in the case of needing to take it back to Verizon or Motorola in the case of it being damaged or something. I know how to unroot on the RAZR and how to do it all on my Nexus 7, just cant find hardly anything for this phone.
Thanks in advanced!!!
Click to expand...
Click to collapse
Nope it's impossible to relock and once it's unlocked all your warranties are void
Sent from my XT907 using Tapatalk 2
Is this true for any device? Or just certain ones at this point?
Because I can Relock my Nexus 7 and my DROID Incredible just fine, in fact Verizon has accepted one of my former phones that was previously rooted and had the bootloader unlocked, then all was returned to stock of course.
lukkypuggy said:
Is this true for any device? Or just certain ones at this point?
Because I can Relock my Nexus 7 and my DROID Incredible just fine, in fact Verizon has accepted one of my former phones that was previously rooted and had the bootloader unlocked, then all was returned to stock of course.
Click to expand...
Click to collapse
It's specific to this line of devices so far (RAZR HD, RAZR MAXX HD, RAZR M, ATRIX HD). The unlock method (both on the dev. and consumer phones) invloves blowing a physical fuse in the phone which cannot be repaired. Google qfuse if you want to learn more.
Coronado is dead said:
It's specific to this line of devices so far (RAZR HD, RAZR MAXX HD, RAZR M, ATRIX HD). The unlock method (both on the dev. and consumer phones) invloves blowing a physical fuse in the phone which cannot be repaired. Google qfuse if you want to learn more.
Click to expand...
Click to collapse
thanks!
yes! it is!
lukkypuggy said:
thanks!
Click to expand...
Click to collapse
was unlocked now its fn locked and stuck in ap!!!
Yeah, I can confirm that Motorola released an update or something that relocked my previously unlocked boot loader (before anyone asks, yes it was definitely unlocked before ). Unfortunately the update failed on my phone and now I'm stuck in AP Fastboot with an error about "downgraded security version" and "update got_main version failed" errors.
So yeah, definitely possible for Motorola to relock the boot loader.
Attached is a picture of what it looks like now. I don't know of any SBF that would work to fix this.
phantomsniper773 said:
Yeah, I can confirm that Motorola released an update or something that relocked my previously unlocked boot loader (before anyone asks, yes it was definitely unlocked before ). Unfortunately the update failed on my phone and now I'm stuck in AP Fastboot with an error about "downgraded security version" and "update got_main version failed" errors.
So yeah, definitely possible for Motorola to relock the boot loader.
Attached is a picture of what it looks like now. I don't know of any SBF that would work to fix this.
Click to expand...
Click to collapse
Well, that picture speaks for itself, but I have to imagine that your situation is the exception, not the rule. It almost looks like somehting else went wrong with it. The qfuse is a physical fuse from what I have read, so maybe it got bridged, or the system isn't even making it to that check because of some other error.
Very strange indeed.
Coronado is dead said:
Well, that picture speaks for itself, but I have to imagine that your situation is the exception, not the rule. It almost looks like somehting else went wrong with it. The qfuse is a physical fuse from what I have read, so maybe it got bridged, or the system isn't even making it to that check because of some other error.
Very strange indeed.
Click to expand...
Click to collapse
Unless the tiny update did something with the bootloader to possibly IGNORE the qfuse state and simply keep it encrypted, blown qfuse or not. Maybe the final 'hurrah' from Verizon to try to kill off the Razr M development. Kinda reminds me of what they did with the Droid X and Droid 2 when they released the system version .621.. the ONLY thing the update did, was patch the current root methods and change the bootloader a tiny bit (version didn't even change) so it couldn't SBF to ANY previous build. TONS of Droid Xs and 2s were bricked until eventually a 621 SBF was released, and after forever, another root method.
EDIT: I found This thread which describes the same situation, but SBFing back to an earlier version seems to fix it. Apparently, the latest OTA REQUIRES a locked bootloader, unless flashed by other means (possibly TWRP or manual fastboot of img files?)
Skreelink said:
Unless the tiny update did something with the bootloader to possibly IGNORE the qfuse state and simply keep it encrypted, blown qfuse or not. Maybe the final 'hurrah' from Verizon to try to kill off the Razr M development. Kinda reminds me of what they did with the Droid X and Droid 2 when they released the system version .621.. the ONLY thing the update did, was patch the current root methods and change the bootloader a tiny bit (version didn't even change) so it couldn't SBF to ANY previous build. TONS of Droid Xs and 2s were bricked until eventually a 621 SBF was released, and after forever, another root method.
EDIT: I found This thread which describes the same situation, but SBFing back to an earlier version seems to fix it. Apparently, the latest OTA REQUIRES a locked bootloader, unless flashed by other means (possibly TWRP or manual fastboot of img files?)
Click to expand...
Click to collapse
Interesting theory. I personally had to RSD back to 4.1.2 (q66) to install since I had removed the Audio Level Warning apk (which just restores stock apps, kernel, boot image and boot animation but leaves data intact). I then let the update installer run on its own with the stock recovery and it remained unlocked.
Coronado is dead said:
Well, that picture speaks for itself, but I have to imagine that your situation is the exception, not the rule. It almost looks like somehting else went wrong with it. The qfuse is a physical fuse from what I have read, so maybe it got bridged, or the system isn't even making it to that check because of some other error.
Very strange indeed.
Click to expand...
Click to collapse
Yeah, I've only seen this occur on the few devices that had the update fail. I think it's striclty a software thing because it goes back to unlocked after the indviduals were able to recover the phone.
RikRong said:
Yeah, I've only seen this occur on the few devices that had the update fail. I think it's striclty a software thing because it goes back to unlocked after the indviduals were able to recover the phone.
Click to expand...
Click to collapse
Confirming my dad's phone is still unlocked after the update. He didn't do anything with root but I did manage to convince him to root and unlock. Updated yesterday and he's still unlocked. It's gotta be related to the flash failures...
EDIT: stock recovery too...
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Confirming my dad's phone is still unlocked after the update. He didn't do anything with root but I did manage to convince him to root and unlock. Updated yesterday and he's still unlocked. It's gotta be related to the flash failures...
EDIT: stock recovery too...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Yeah, possibly. Does anyone know if RSDLite works with a locked boot loader? I tried it earlier and it wouldn't flash, giving an error about GPT partition or something. I didn't really look into it much though, because my phone is still under warranty.
phantomsniper773 said:
Yeah, possibly. Does anyone know if RSDLite works with a locked boot loader? I tried it earlier and it wouldn't flash, giving an error about GPT partition or something. I didn't really look into it much though, because my phone is still under warranty.
Click to expand...
Click to collapse
RSD will work, but you'll only be able to flash the most recent update.
Related
Hello! I have been searching through the forums and have found several similar issues to mine, but I have some questions/concerns as to whether the solutions mentioned apply to exactly my situation.
I have a Motorola Droid R2D2 edition. I Did not do anything to it. I did not root, I did not side load anything, I did not try to roll back anything. I was minding my own business and received a message regarding a firmware update OTA. I assumed this was going to fix the horrible behavior introduced by the previous OTA, (random reboots etc) So excitedly.. I let it do its thing.
Big Mistake...
I think THIS: http://support.verizonwireless.com/pdf/system_update/droid_r2d2.pdf is the update I was installing.
Now it is stuck on a black boot loader screen. Here are my concerns about the other post.
1.) A similar problem was had with a normal Droid 2, but his boot loader was version D2.35 Mine says D2.37 Can I use the same tools that were mentioned here: http://forum.xda-developers.com/showthread.php?t=849658 ?
2.) My error code is different, his says Err:A5,70,00,1F Mine says A5,70,00,00,23
What does this code mean? These kinds of things intrigue me
3.) I do not have that mem_map message.
My screen looks exactly like this:
Bootloader
D2.37
Err:A5,70,00,00,23
Battery OK
OK to Program
Connect USB
Data Cable
Can I just do what the other guy did in the above mentioned post? Or do I have to do something else? I'd prefer not to take a 25 mile drive to the nearest Verizon store to beat them..err I mean.. ask them to re-flash it, if I can just do that myself.
P.S. Already tried a battery pull no luck :'(
That's unfortunate.
The OTA killed my root, as one would expect. I re-ran the Motorola One Click Root, but this time, it didn't root it. I wonder if Verizon blocked this exploit? I'll have to try again and report back.
One more question
IS there a precedent for installing Windows phone on a Droid 2? Can I do that since I have to flash something on anyway?
NOtanXDANoob said:
IS there a precedent for installing Windows phone on a Droid 2? Can I do that since I have to flash something on anyway?
Click to expand...
Click to collapse
no you cant install windows phone on the droid 2, when did u get this update? were you previously on gingerbread or froyo.. best bet is to use rsdlite and flash the newest r2d2 sbf or droid 2 sbf .601 in that case you just wont have all the stupid r2d2 noises ;/
merlot2k1 said:
That's unfortunate.
The OTA killed my root, as one would expect. I re-ran the Motorola One Click Root, but this time, it didn't root it. I wonder if Verizon blocked this exploit? I'll have to try again and report back.
Click to expand...
Click to collapse
I am waiting to see if/how somebody gets ROOT back on their R2-D2 before I update with the OTA 2.3.4
So far I have found nothing on it and I wonder if our precious R2-D2 is too old for people to crack it....
merlot2k1 said:
That's unfortunate.
The OTA killed my root, as one would expect. I re-ran the Motorola One Click Root, but this time, it didn't root it. I wonder if Verizon blocked this exploit? I'll have to try again and report back.
Click to expand...
Click to collapse
Is the one-click root you're talking about the same thing as 'Pete's Motorola root tools'? I know that works great on newer droids (e.g. droid pro, droid 3) I don't know if the update the R2D2 got would mess up Pete's exploit.
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
dreamersipaq said:
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
Click to expand...
Click to collapse
If your build is prior to may 24 '13 there is the apk in my goodies. If its equal or later there is no point.
Go to the 1st link below.
dreamersipaq said:
I searched the forums, and didn't really find an answer I'm looking for. I'm hoping that someone can quickly help me without too much bashing :laugh:
Is there a way I can test to see if my BL is unlocked without bricking anything if it's actually locked? I bought a phone off of ebay, and the person stated that nothing was ever done to it. However, after rooting / VooDoo, and not doing anything else to it, it wouldn't take the .94 update... kept getting the EMMC:boot error. Had to use matt's utility to RSD to stock (even though it was already stock) and root / VooDoo again.... after which it took update.
So, since the person may have lied about it not being rooted before, maybe they unlocked the BL, and just covered it up...
I DO show Bootloader Locked: Status 0 though in AP mode. I'm just wondering if I can run Motocopylis (or whatever it's called) without fear of bricking anything if it's still locked, and what kind of message or error I'd get if it's already unlocked.
Click to expand...
Click to collapse
I'm no expert at all but I ran motoapocolyps and if didn't do anything. It will either fail and your phone will be fine or, depending on what update you last took, unlock it. My phone is past due for unlocking the bootloader unless there is a way to downgrade it.
Hi
aviwdoowks said:
If your build is prior to may 24 '13 there is the apk in my goodies. If its equal or later there is no point.
Go to the 1st link below.
Click to expand...
Click to collapse
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
dreamersipaq said:
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
Click to expand...
Click to collapse
You said it already:
""I DO show Bootloader Locked: Status 0 though in AP mode.""
With the knowledge that the build is may 24 or later means no unlock.
Build before May, 24 and running the UL apk results in an UL'ed boot.
status 0: never rooted
1: rooted previously but not now.
3 : rooted
dreamersipaq said:
Hi, Thanks for the reply! I don't think my question came across right. I know I can't unlock on my build. I guess I'm asking what i can do to test if it's already been unlocked and covered up by someone before...
Thanks!
Follow up question:
What would be the difference in the output on the screen that you get of
1) if you run Motocopylis and you're already unlocked
vs.
2) if you run Motocopylis and failing since you're locked and on the May build
Thanks!
Click to expand...
Click to collapse
You can't cover up a BL unlock. Like Avi said, it shows locked on you AP Fastboot screen, so that means you're locked.
aviwdoowks said:
You said it already:
""I DO show Bootloader Locked: Status 0 though in AP mode.""
With the knowledge that the build is may 24 or later means no unlock.
Build before May, 24 and running the UL apk results in an UL'ed boot.
status 0: never rooted
1: rooted previously but not now.
3 : rooted
Click to expand...
Click to collapse
do you mean unlocked or rooted?
I'm rooted, but I show status 0
Thanks for your reply!
RikRong said:
You can't cover up a BL unlock. Like Avi said, it shows locked on you AP Fastboot screen, so that means you're locked.
Click to expand...
Click to collapse
"You can't cover up a BL unlock." <- THANK YOU! That is what I was trying to confirm....
I was thinking that since you can do this to cover up the unlocked bl warning: http://forum.xda-developers.com/showthread.php?t=1901444
that you can also do something to cover up the AP screen as well.
Since I'm rooted, and this phone is supposed to get 4.4, I'm not too upset that I can't unlock (Though with 4.4 I'll probably lose root ).. The stock rom is pretty nice on these, and root gives me pretty much anything I want for customization.
Thanks!
dreamersipaq said:
do you mean unlocked or rooted?
I'm rooted, but I show status 0
Thanks for your reply!
Click to expand...
Click to collapse
I am the one confused! I need to learn my codes.
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
If you feel you absolutely must relock your bootloader (at your own risk) please boot the phone up to check it works properly before doing this. If you intend flashing roms and kernels or custom recoveries, locking the bootloader is not a good idea
Please also see the below link provided by @efrant
https://support.google.com/nexus/answer/6172890?hl=en
This goes into more detail about how google have enhanced device security with 5.1 and some other pitfalls that you may wish to avoid. This is pretty salient information, so do give it a read.
Good advice, i would add to that NEVER LOCK YOUR BOOTLOADER. ???
Sent from my Nexus 9 using XDA Free mobile app
ChristianJay said:
Good advice, i would add to that NEVER LOCK YOUR BOOTLOADER.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
And I would add that I completely disagree with this statement. Coming from an infosec standpoint, I keep my bootloader locked, and just suffer the reset when I need to tweak. If you don't, anyone - not just you - can replace your system partition or boot a random IMG which could inject functionality. This may not be the most common mechanism for attack as it requires physical access, but it basically obviates the encryption with a deepfreeze style boot IMG.
Additionally, when you think about this in context of the border crossing exemptions many countries, including the US, have to protections against unwarranted search, I would recommend that anyone with proprietary or sensitive business data who crosses international borders keeps their bootloader locked when not modifying the system. Also, until custom recoveries include security features, I recommend using stock.
Why are we making our phones so insecure just to have root? Not cool.
So just to be clear the correct procedure would be to boot the device after updating enable the setting and then go and lock your bootloader? Or just keep it unlocked overall.
Personally I keep mine unlocked but for those wanting to take full advantage of androids new device protection a locked bootloader would serve a purpose. Preventing someone from just flashing a custom rom and keeping your device.
:thumbup:
I thought I really #$# up
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
xander45 said:
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
Click to expand...
Click to collapse
im so new to this but im rooted with an unlocked bootloader but im running full stock android. i only rooted just so i can chance the provision to get free tethering with my unlimited data. i have the wugfresh nexus tool kit and cant for the life of me figure out how to upgrade my nexus 6 to 5.1. Is there in anyone that can get me a step by step on how to update so i can take advantage of hd calling and silmutaneous voice and data... ive been waiting tooooooooooo long for this update..
rootSU said:
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
Click to expand...
Click to collapse
Hi root,
I saw that thread yesterday ...
I thought this was already covered when the N6 came out, to get the bootloader unlocked you had to do a 1st boot of the device and ENABLE OEM Unlock, then you were good to go to get into fastboot and unlock.
The reason was google put the option there for 5.0, vice all our previous versions which had no toggle for it.
I think it was people jumping the gun and not doing that first boot, but immediately jumping into fastboot and flashing, and that caused it, yes? Because the BL wasn't unlocked, they couldn't flash the OTA and boot img ...
daijizai said:
And I would add that I completely disagree with this statement. Coming from an infosec standpoint, I keep my bootloader locked, and just suffer the reset when I need to tweak. If you don't, anyone - not just you - can replace your system partition or boot a random IMG which could inject functionality. This may not be the most common mechanism for attack as it requires physical access, but it basically obviates the encryption with a deepfreeze style boot IMG.
Additionally, when you think about this in context of the border crossing exemptions many countries, including the US, have to protections against unwarranted search, I would recommend that anyone with proprietary or sensitive business data who crosses international borders keeps their bootloader locked when not modifying the system. Also, until custom recoveries include security features, I recommend using stock.
Why are we making our phones so insecure just to have root? Not cool.
Click to expand...
Click to collapse
This is nonsense.
You need *physical* access to it in order to carry out such an attack.
If your phone leaves your PHYSICAL access, then you already know not to trust what is on it, whether or not it has an unlocked bootloader.
xander45 said:
Thank you for posting this...when 5.1 was dropping, I attempted to return to stock...all the way.to be able to take Verizon's OTA...when i locked the boot loader, i was stuck in a boot loop with the android guy and the gear box spinning FOREVER.....its is not easy to get out of the loop, but i managed to boot back up into boot loader mode, and force a stock image using toolkit.
I am now unlocked, running 5.1 on Verizon, have full LTE/VOLTE, can speak and surf at same time...i have not rooted yet...but just glad it was not me....had a heart attack two nights ago...
Click to expand...
Click to collapse
kng60ft said:
im so new to this but im rooted with an unlocked bootloader but im running full stock android. i only rooted just so i can chance the provision to get free tethering with my unlimited data. i have the wugfresh nexus tool kit and cant for the life of me figure out how to upgrade my nexus 6 to 5.1. Is there in anyone that can get me a step by step on how to update so i can take advantage of hd calling and silmutaneous voice and data... ive been waiting tooooooooooo long for this update..
Click to expand...
Click to collapse
There is no need to lock the device to take an OTA. You can keep it unlocked and do an ota
doitright said:
This is nonsense.
You need *physical* access to it in order to carry out such an attack.
If your phone leaves your PHYSICAL access, then you already know not to trust what is on it, whether or not it has an unlocked bootloader.
Click to expand...
Click to collapse
Not nonsense. Yes you need physical access to carry out the attack, but with a locked bootloader and the new precautions against unlocking and fastboot it makes locked bootloaders fairly bulletproof.
I cannot recommend unlocked bootloaders to anyone that works SCIF'd and leaves their phone in a shared box during the day, anyone that crosses international borders, or anyone whose phone might contain IP or trade secrets and could be a target of theft.
This is as much about trusting the phone afterwards as it is about protecting your data on the phone - even when encrypted.
y2whisper said:
So just to be clear the correct procedure would be to boot the device after updating enable the setting and then go and lock your bootloader? Or just keep it unlocked overall.
Personally I keep mine unlocked but for those wanting to take full advantage of androids new device detection a locked bootloader would serve a purpose.
Click to expand...
Click to collapse
Just keep it unlocked
rootSU said:
Guys,
We've seen several people have flashed system.img's and OTA's and ended up in a bootloop.. Not the end of the world really, BUT for some reason, before you can unlock your bootloader using fastboot, you must enable OEM unlock in Developer options in Android settings - which you cannot do if you are bootlooping.
If you still have a custom recovery, you'll be fine but if you're 100%, locked bootloader and bootlooping, we haven't found a fix yet so please do not lock your bootloader.
If you feel you absolutely must relock your bootloader (at your own risk) please boot the phone up to check it works properly before doing this. If you intend flashing roms and kernels or custom recoveries, locking the bootlaoder is not a good idea
Click to expand...
Click to collapse
I had this boot loop also, but clearing Cache and Dalvik seemed to fix the loop for me.
nyteryder79 said:
I had this boot loop also, but clearing Cache and Dalvik seemed to fix the loop for me.
Click to expand...
Click to collapse
Thats good.
http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
This may help if you got stuck in a bootloop.
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
darren.wlsn1 said:
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
Click to expand...
Click to collapse
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Marcellus1 said:
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=58201783&postcount=106
should help
darren.wlsn1 said:
is there a fix if my mem shows i own a 32g device when i bought a 64g device, im unlocked/rooted and on custom rom?
Click to expand...
Click to collapse
Marcellus1 said:
I'd like to know too. I'm unrooted, stock everything, with 64GB Blue, but it shows 23GB total space for the device with 16GB available. Was fine before the 5.1 update.
Click to expand...
Click to collapse
Factory reset?
Not really the thread to ask this though.
rootSU said:
Factory reset?
Not really the thread to ask this though.
Click to expand...
Click to collapse
Thanks, and sorry
The majority of my phones have been HTC so not really sure if unlocking the bootloader is normal procedure for a Motorola phone to obtain root. So i have a couple of questions on rooting this device, I'm happy to stay on a rooted stock so don't really see the point/need of unlocking the bootloader at this time.
1) Do you have to unlock the bootloader to root? or is there a method to root without unlocking the bootloader.
2) If the bootloader does get unlocked can it be relocked at a later date and would it show it had been unlocked?
Thanks in advance.
rnscotch said:
1) Do you have to unlock the bootloader to root? or is there a method to root without unlocking the bootloader.
Click to expand...
Click to collapse
Yes, at this time there's no way to obtain root without unlocking the bootloader.
rnscotch said:
2) If the bootloader does get unlocked can it be relocked at a later date and would it show it had been unlocked?
Click to expand...
Click to collapse
It can be relocked but then it'll be just "re-locked" not "locked", that means it'll have a different status.
Also note that you void the warranty just by obtaining the unlock code from Motorola; it doesn't matter if you've actually applied it to your device
If I unlock the bootloader and root, will I lose OTA updates, right? So, if I do this, how will I update to Marshmallow, when it's available?
LuizHenrique91 said:
If I unlock the bootloader and root, will I lose OTA updates, right? So, if I do this, how will I update to Marshmallow, when it's available?
Click to expand...
Click to collapse
With root you'll lose ota updates if I'm not wrong, but you can always flash the updated full firmware through fastboot or rsd.
If you're rooted, you're free to install any ROM you like. The Devs here at XDA got your back when it comes to updates. Every time the latest Android version came out for my past 2 devices I got it through ROMs from here way quicker than the carriers delivered it. That's not certain for every device, especially older ones, but it's up to you.
I will say since Motorola has kept the Android OS "pure," there may be a chance that this device gets Android M fairly quickly. However in my experience, developers on XDA seem to be able to squash the bugs so much quicker than the carriers.
Good luck in whatever you decide. Myself, I haven't unlocked or rooted since I just got this phone a few days ago. I'm keeping an eye on the forums to see some more ROMs come into play and the tweaking to be more common place with solid procedures. Though, I am itching to root just to get a working LED light. I'm not crazy about this Moto Display that blinks once with a notification and if I missed the blink, I never know something is waiting for me.
eskamhl said:
With root you'll lose ota updates if I'm not wrong, but you can always flash the updated full firmware through fastboot or rsd.
Click to expand...
Click to collapse
But if I flash the full firmware with the new version, I'll need to install the recovery and root again or will the phone stay rooted?
---------- Post added at 04:30 PM ---------- Previous post was at 04:28 PM ----------
ooklathemok said:
If you're rooted, you're free to install any ROM you like. The Devs here at XDA got your back when it comes to updates. Every time the latest Android version came out for my past 2 devices I got it through ROMs from here way quicker than the carriers delivered it. That's not certain for every device, especially older ones, but it's up to you.
I will say since Motorola has kept the Android OS "pure," there may be a chance that this device gets Android M fairly quickly. However in my experience, developers on XDA seem to be able to squash the bugs so much quicker than the carriers.
Good luck in whatever you decide. Myself, I haven't unlocked or rooted since I just got this phone a few days ago. I'm keeping an eye on the forums to see some more ROMs come into play and the tweaking to be more common place with solid procedures. Though, I am itching to root just to get a working LED light. I'm not crazy about this Moto Display that blinks once with a notification and if I missed the blink, I never know something is waiting for me.
Click to expand...
Click to collapse
Yes.. I'm considering to root mine X Play for be able to change the kernel and get the LED working (and maybe some optimizations). It's not prioritary, but I want. I won't install a custom ROM, because I like Moto Voice to much and I know we lost it.
LuizHenrique91 said:
But if I flash the full firmware with the new version, I'll need to install the recovery and root again or will the phone stay rooted?
Click to expand...
Click to collapse
Of course in that case you'll need to install the recovery and root, but as ooklathemok said you'll be able to update through a stock rooted rom simply from recovery
How do I fix this problem
So I fastboot stock firmware for my xt1563 from a rooted rim 6.0 to 5.1
And it all went good until I seen I lost root and recovery
So I re booted to bootloader and flashed
Fastboot flash recovery recovery img
Said okay and installed
I rebooted os
Then rebooted bootloader
Tried to go to recovery mode and the little android dude was there and below him says no command
What am I going wrong
deaksfrost said:
How do I fix this problem
So I fastboot stock firmware for my xt1563 from a rooted rim 6.0 to 5.1
And it all went good until I seen I lost root and recovery
So I re booted to bootloader and flashed
Fastboot flash recovery recovery img
Said okay and installed
I rebooted os
Then rebooted bootloader
Tried to go to recovery mode and the little android dude was there and below him says no command
What am I going wrong
Click to expand...
Click to collapse
Do not reboot to OS after flashing recovery, just reboot to recovery. If you reboot to OS after flashing twrp the stock Rom will over write recovery
Do Custom OS support Active/Moto Display and Moto voice?
yekollu said:
Do Custom OS support Active/Moto Display and Moto voice?
Click to expand...
Click to collapse
No, custom Roms do not support moto voice nor will they ever. Active display is all custom Roms provide.
This is my second moto x, I had the original moto x from 2013 and hated moto display.
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
.G33K said:
Hi There,
My colleague complained that he had an OTA update on his Nexus 6P and the after the update it was stuck in a boot loop where the Google logo keep on displaying.
When he bought back, he had showed it a shop already which they said they couldn't fix. However, the phone was later given to me for help and I have somehow manage to connect the device on fastboot and adb. Tried all the possible options such as unlocking the bootloader, loading .img's one by one... sideloading... etc.
No matter what I do, it keeps on doing the same boot loop. And when I leave the bootloader unlocked, it gives an error at first, then again goes back to the same.
Not sure whether what I am doing wrong or whether am I choosing the wrong build or so... would anyone care to advise?
Click to expand...
Click to collapse
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Heisenberg said:
So the bootloader is unlocked? Exactly which build have you attempted to flash with fastboot? Have you tried flashing one of the full OTA zips with the stock recovery?
PS. Whatever you do don't lock the bootloader. And don't worry about the warning you get with the bootloader unlocked, that's normal.
Click to expand...
Click to collapse
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
.G33K said:
Thank you for the reply.. I have only locked the bootloader when I'm done with flashing... etc as it was giving me error. Regardless of the bootloader state, it kept on going through the bootloop like it didn't care.
I tried to flashing the factory image which is MTC19T and also tried the OTA which is MTC19V as said in here.
Still there's not luck!
Click to expand...
Click to collapse
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Heisenberg said:
Don't worry about the warning and definitely don't lock the bootloader because if it gets stuck locked you'll really be screwed. Go to my guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Follow the instructions in section 10 (use the latest MTC19X build). Skip the part at the beginning about performing a factory reset because you can't actually get the phone to boot to do that. Make sure you include the "fastboot format userdata" command at the end (this will erase all data on the device). Leave the bootloader unlocked.
Click to expand...
Click to collapse
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
.G33K said:
I have actually tried doing what section 10 says but with a different stock build.. Does that effect as well? However, let me give another shot with your said build and post back.
Click to expand...
Click to collapse
Did you format userdata? It's worth a try.
Heisenberg said:
Did you format userdata? It's worth a try.
Click to expand...
Click to collapse
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
.G33K said:
Yes, sire! I did all the possible things I could do without harming or bricking the device... Read each and every instruction carefully to do... but turned with no luck... however, I'm due to try the method and build you have suggested, I shall try that and get back to you!
Click to expand...
Click to collapse
It probably won't work, any build should work, but it's worth a try. If that fails I can only suggest flashing TWRP recovery and trying to flash a custom ROM to see if that works.
So long as you have the bootloader.img and radio.img files, you can try to format boot as well, however Heisenberg may yell at me for even typing that
I had a similar issue - bootloop, but it was getting to the boot animation for about 3 seconds, then rebooting. When I formatted all the areas before flashing them from the stock image, it allowed me to boot up as normal. Stable ever since.
Hi There,
Coming back to the issue, I have just downloaded the build that was suggested by "Heisenberg" and tried it. It was still the same, as in the Google logo keep on flashing but the android bot just appeared once with the logo. But still there not luck as the device stays with Google logo but does nothing.
However, I'm able to see the device on fastboot. Nevertheless, I cannot seem to use adb command.. it doesn't even list on devices. Does that mean the adb isn't working?
Meanwhile, all my fastboot commands are working with no issues at all.
EDIT: When I tried the TWRP recovery, I can flash the recover, but I can seem to go to the recovery window at all as the device keep on showing "The device software can't be checked for corruption". When I pass that also the same boot loop.
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
Unfortunately yes. Unless you enabled OEM Unlocking in the developers menu before your phone went sideways you probably have a hard bricked phone. Is it under warranty?
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
TemplesOfSyrinx said:
I went through this in November with a completely stock Nexus 6P. I was 3 days past my one year warranty! Google would not send me a new phone. It was completely bricked by the OTA update I received! I was put in touch with Huawei. I had to send the bricked phone to them. 10 days later I received a working model back. Unacceptable that an OTA update trashes a one year old $650 phone. Luckily I had my OnePlus One still, and was able to use that while I waited. I was even able to update that to 7.1.1 since it was rooted. Obviously there is some sort of issue that we are not being told of regarding the dangers of accepting OTA updates on a stock/bootlocked phone.
Click to expand...
Click to collapse
Bootloop issues are common on the 6P even with custom ROMs--it just happens to be much more likely you can recover with the custom ROMs installed since the bootloader is unlocked. I think it's a hardware issue with the 6P rather than an OTA issue. It's probably not an accident that Huawei didn't make the Pixels.
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
This happened to my wife's phone, sent back to Bell. Will see what happens.
TemplesOfSyrinx said:
Doesn't seem right that I have to "void" my warranty and install a custom ROM on an unlocked, rooted phone in order to recover from a hardware defect. That's BS pure and simple. I want to use the latest software, that's why I bought a Nexus. I want to use all the conveniences like Android Pay. That's why I don't unlock or root anymore. I rooted every Android phone I ever had until now, starting with the original Motorola Droid. Now that security is so important to Google, and you can't use all the Android features with an unlocked bootloader, they need to step up to fix these problems.
Click to expand...
Click to collapse
Unlocking the bootloader doesn't void the warranty on the Nexus 6P. If you are under warranty then just RMA the phone if an OTA bootloops your phone. It's your choice whether to keep the bootloader locked or not but if you keep the bootloader locked it's probably impossible to recover from a bootloop. Google keeps factory images for Nexus and Pixel phones on its website but you can't flash those images with a locked bootloader. Why would they provide the images if using them voided your warranty?
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
bcjk8210 said:
I too am having the bootloop issue on my stock Nexus 6P. Is there a way to unlock the device from the bootloader? I'm unable to carry out step one on Heisenberg's guide because I'm unable to actually boot up my phone past the Google logo. Am I pretty much screwed?
Click to expand...
Click to collapse
What Android version you had on your phone? What's your emmc name and ram name in bootloader? What's the manufacturing date in bootloader?
TemplesOfSyrinx said:
You are missing my point. If I unlock my bootloader so I can recover from a boot loop that may happen, I will no longer be able to use a huge feature of the phone. Android Pay will no longer function. In days passed the rumour was your warranty was void if you unlock. I assume that was started to keep people from doing it. All I know is I paid good money for a phone that is a disaster waiting to happen it seems.
If having an unlocked bootloader is so important to recover from a bricked phone, why do they lock it in the first place? And why won't Android Pay work with it unlocked? The answer is that you no longer have a secure phone if you unlock the bootloader.
Click to expand...
Click to collapse
I think you bought the wrong phone. Nexus devices were never available commercially through carriers and were made for developers and people who like to flash things with their phones. There are ways to use Android Pay with an unlocked bootloader if you are so inclined. You are right that an unlocked bootloader is considered less secure but if you only install apps from Google Play or another trusted source you shouldn't have problems. You can also simply enable allow Oem Unlock in the developer menu. This doesn't actually unlock your bootloader but makes it possible for you to unlock it via fastboot if you get bootlooped and need to flash a factory image to restore. This way you can unlock the bootloader in an emergency but your phone is still secure. I think this should be enabled by default when the phones are shipped. Too many people with locked bootloaders end up with hard bricked phones where the Nexus 6P is concerned. Honestly, you would probably be better off selling your Nexus and getting something else that's more stable and made for people who have no Interest in flashing anything.