Related
According to this review, the Australian Razr M can be bootloader unlocked.
http://ausdroid.net/2012/10/30/motorola-razr-m-review/
I went on motodev and can't find any instructions pertaining. I assume this is not the developer version, so how do we unlock or check whether its possible? Does anyone know / has anyone tried on an Australian Razr M?
Is it as simple as fastboot oem unlock? I tried that and this is what happened
C:\Users\jlo.APBC\Dropbox\android\fastboot>fastboot devices
TA676001L3 fastboot
C:\Users\jlo.APBC\Dropbox\android\fastboot>fastboot oem unlock
...
(bootloader) fastboot oem unlock [ unlock code ]
OKAY [ 0.014s]
finished. total time: 0.014s
??? I didn't get any prompt to unlock or anything.
This is for the RAZR i, but the process is the same. You have to get the Device ID, enter that on Motorola's website, and then it will give you the data you need to unlock. Just follow their instructions, and use the thread as a guide also.
http://forum.xda-developers.com/showthread.php?t=1928551
thanks, got the code in my hand
Waiting for some goodies to actually come out ROM wise before taking the plunge, also run the hardware in a bit and be sure 100% no hardware issues
Does anyone know, does simply unlocking the bootloader bar the path for future OTAs? (if you don't do anything else).
Hmm...just by getting the code, you may have already voided your warranty. I'm not sure, though, so don't quote me on that.
As far as OTAs go, no, you will still be able to get OTAs. You would only not be able to get OTAs if you rooted and uninstalled some stock apps, or if you installed a custom ROM. I wouldn't be doing either of those right now, anyway, since I don't think there's a fastboot for the Australian M yet. Once somebody puts that up, you're safe to do whatever you want.
freak4dell said:
Hmm...just by getting the code, you may have already voided your warranty. I'm not sure, though, so don't quote me on that.
As far as OTAs go, no, you will still be able to get OTAs. You would only not be able to get OTAs if you rooted and uninstalled some stock apps, or if you installed a custom ROM. I wouldn't be doing either of those right now, anyway, since I don't think there's a fastboot for the Australian M yet. Once somebody puts that up, you're safe to do whatever you want.
Click to expand...
Click to collapse
Yep by fastboot you mean fastboot flashable system image right?
Always been my rule as well.
I just reread the fine print and it does seem that they want to screw you out of it if you even request the code. That is so lame...
(I get mixed up between different vendors and methods lol... RUU for HTC... fastboot image for moto... odin image for sammy etc.)
wintermute000 said:
Yep by fastboot you mean fastboot flashable system image right?
Always been my rule as well.
I just reread the fine print and it does seem that they want to screw you out of it if you even request the code. That is so lame...
(I get mixed up between different vendors and methods lol... RUU for HTC... fastboot image for moto... odin image for sammy etc.)
Click to expand...
Click to collapse
Yup, a fastboot is a flashable image. The stock fastboots allow you to go back to stock just in case you flash something else and you can't boot up again. It's a good rule to have. Hopefully, the devs here will get the fastboot. I think there's a way to make a fastboot from a stock phone, so even if we don't get a leak, maybe that's a possibility. If you think you might be interested in helping, talk to mattlgroff or p3droid (jimmydafish on here).
And yeah, I figured that would be how they determined to void the warranty. Motorola doesn't have a way to know that you actually did unlock your bootloader, because you can technically relock it. So, the request for the code is their way of keeping track. Lame, but I can understand the reasoning.
freak4dell said:
Yup, a fastboot is a flashable image. The stock fastboots allow you to go back to stock just in case you flash something else and you can't boot up again. It's a good rule to have. Hopefully, the devs here will get the fastboot. I think there's a way to make a fastboot from a stock phone, so even if we don't get a leak, maybe that's a possibility. If you think you might be interested in helping, talk to mattlgroff or p3droid (jimmydafish on here).
And yeah, I figured that would be how they determined to void the warranty. Motorola doesn't have a way to know that you actually did unlock your bootloader, because you can technically relock it. So, the request for the code is their way of keeping track. Lame, but I can understand the reasoning.
Click to expand...
Click to collapse
Well for HTC if you relock, it says 'relocked' not 'locked' in hboot.
Still I guess they warned you but in small print, I was expecting to not pop my warranty until I actually flashed my damned unit.
I'm curious about how much dev work we'll get bearing in mind we're a different variant to the US razr M and different radio, or we will get ROMs that don't touch the radio, etc. etc.
freak4dell said:
Yup, a fastboot is a flashable image. The stock fastboots allow you to go back to stock just in case you flash something else and you can't boot up again. It's a good rule to have. Hopefully, the devs here will get the fastboot. I think there's a way to make a fastboot from a stock phone, so even if we don't get a leak, maybe that's a possibility. If you think you might be interested in helping, talk to mattlgroff or p3droid (jimmydafish on here).
Click to expand...
Click to collapse
OK so I'm unlocked and have recovery installed. I'm keen to help others and make a flashable fastboot of Telstra's stock ICS system. Can anyone give me any tips on how to do it if it's not too difficult and I'll then upload for everyone to safeguard their phones.
pjcons said:
OK so I'm unlocked and have recovery installed. I'm keen to help others and make a flashable fastboot of Telstra's stock ICS system. Can anyone give me any tips on how to do it if it's not too difficult and I'll then upload for everyone to safeguard their phones.
Click to expand...
Click to collapse
I recently purchased a Telstra RAZR M (My first Android) and am keen to look into flashing a custom rom. I'm willing to help out with an upload of the stock rom as well if needed, lets get this ball rolling.
pjcons said:
OK so I'm unlocked and have recovery installed. I'm keen to help others and make a flashable fastboot of Telstra's stock ICS system. Can anyone give me any tips on how to do it if it's not too difficult and I'll then upload for everyone to safeguard their phones.
Click to expand...
Click to collapse
This is a rather uncomplicated thing and I'd be glad to help you get stock images. would you care to get me a little information?
P3Droid made an app that backs up the partition images into and XML.zip and we can use it to make a set of images from the Telstra M.
We are particularly interested in the radio image to see if its possible to flash onto VZW hardware to have an unlocked GSM/HSPA radio.
The process is very simple, you just run the app and it creates the zip file and then you can upload the images for examination.
These images can then also be used in fast boot to restore your phone as well, of course.
Edit: I see he has responded above. Thanks!
Ok will check the app and get to work.
Can't seem to find the app... Any help?
Sent from my Razr M machine
---------- Post added at 06:57 AM ---------- Previous post was at 06:52 AM ----------
jimmydafish said:
This is a rather uncomplicated thing and I'd be glad to help you get stock images. would you care to get me a little information?
Click to expand...
Click to collapse
What info u want? Unlocked, rooted Razr M (Australian version) running stock telstra firmware. Have recovery installed.
Sent from my Razr machine
pj i'm guessing as you have changed your recovery whatever you extract can't be the 100% stock all in one fastboot image though probably possible if you reflash the stock telstra recovery. just guessing
I'm sorry, the app is not available in the market. He posted instructions in the thread in the general forum for the AU fastboot images for pulling the radio image.
He will probably release the app soon too, I was just suggesting it as an easy way to get this done...and now it has been taken care of.
Thanks!
so back to basics: how/when can we get a fastboot stock Aussie M image so paranoid/scaredy cat guys like me can unlock and flash with peace of mind of having an easy stock image rollback option?
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
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Why would you want to do this?
psandeepn said:
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Click to expand...
Click to collapse
Yes you can do it as many times as you want but 1: Why would you relock afterwards 2: You will have to deal with a factory reset every time
PS: I dont know about the unlock key but most likely you can use the same
Is there any way to remove the Bootloader unlock warning ⚠ without relocking bootloader?
Sent from my XT1572 using Tapatalk
psandeepn said:
Hi Guys
I have 3 questions regarding Moto X Style Bootloader unlocking.
Can we unlock the Moto X Style bootloader after locking it after first unlock?
Can this process be repeated multiple times if we need to?
Can we use the same unique unlock key that we received while unlocking the bootloader for the first time?
Thank you
Click to expand...
Click to collapse
Theres no reason really to relock it. Once its unlocked, the bootloader will show that it was unlocked regardless if you relock it.
atishey23 said:
Is there any way to remove the Bootloader unlock warning without relocking bootloader?
Sent from my XT1572 using Tapatalk
Click to expand...
Click to collapse
Yes
Pyramid Head said:
Yes you can do it as many times as you want but 1: Why would you relock afterwards 2: You will have to deal with a factory reset every time
PS: I dont know about the unlock key but most likely you can use the same
Click to expand...
Click to collapse
Thanks for your reply.
The reason for attempting to re-lock bootloader is to get the OTA update from Motorola till date, especially Reliance Jio VoLTE support...But if I wish to make any further changes to my phone with any custom rom I should be able to do it by unlocking the bootloader again.
Thanks
psandeepn said:
Thanks for your reply.
The reason for attempting to re-lock bootloader is to get the OTA update from Motorola till date, especially Reliance Jio VoLTE support...But if I wish to make any further changes to my phone with any custom rom I should be able to do it by unlocking the bootloader again.
Thanks
Click to expand...
Click to collapse
You don't have to lock the bootloader to take an OTA. You just need to be in a completely unmodified stock state: stock recovery, unmodified system, no root, etc. Bootloader can be unlocked.
jason2678 said:
You don't have to lock the bootloader to take an OTA. You just need to be in a completely unmodified stock state: stock recovery, unmodified system, no root, etc. Bootloader can be unlocked.
Click to expand...
Click to collapse
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
psandeepn said:
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
Click to expand...
Click to collapse
That might work. Frankly I'm not sure. I haven't actually taken successfully an OTA on any phone since sometime in 2013 honestly.
I once flashed this phone totally back to stock. Every partition but logo, and it failed to take an OTA. I don't know if it failed because I had a modified logo, or maybe I had mounted system r/w. Not sure.
Hopefully someone more knowledgeable on this topic will chime in.
psandeepn said:
Thanks for your reply.
I have unlocked bootloader, TWRP recovery and rooted. If I unroot and flash stock recovery, I will be able to get OTA? Do I need to take care of anything else?
Click to expand...
Click to collapse
The answer is maybe... it depends what you have changed and what this OTA updater script actually checks for.
We know that a stock bootloader (which can be unlocked, that is not relevant), stock recovery, and stock system image are required to take an OTA. If the system image has been modified it can fail, and we know the updater has the ability to see if /system has EVER been mounted R/W and can fail for that condition although so far it doesn't seem Moto is going that extreme.
We do know a modified logo does not affect an OTA, in fact, you can even relock the bootloader with a modified logo so it must not be a significant check.
jason2678 said:
That might work. Frankly I'm not sure. I haven't actually taken successfully an OTA on any phone since sometime in 2013 honestly.
I once flashed this phone totally back to stock. Every partition but logo, and it failed to take an OTA. I don't know if it failed because I had a modified logo, or maybe I had mounted system r/w. Not sure.
Hopefully someone more knowledgeable on this topic will chime in.
Click to expand...
Click to collapse
On my father's moto e lte I received OTA without issue with unlocked bootloader, I just flashed stock image and it was ready to update, btw I'm not sure but I've seen somewhere info that you can change bootlogo even with locked bootloader so I don't think that's the issue.
Btw after you once unlock bootloader you won't be able to truly lock it again, next time you will be able to unlock it without any code so you lose some security in this process, frp won't be working anymore.
iks8 said:
On my father's moto e lte I received OTA without issue with unlocked bootloader, I just flashed stock image and it was ready to update, btw I'm not sure but I've seen somewhere info that you can change bootlogo even with locked bootloader so I don't think that's the issue.
Btw after you once unlock bootloader you won't be able to truly lock it again, next time you will be able to unlock it without any code so you lose some security in this process, frp won't be working anymore.
Click to expand...
Click to collapse
You still need code to unlock each time, but it's the same code, and if you relock OEM Unlocking gets turned off and you would have to turn it on again... So if something fails on the first boot after relocking, your f*cked, no way to unlock.
And FRP definitely works if the bootloader is unlocked, it is just much easier to bypass.
acejavelin said:
You still need code to unlock each time, but it's the same code, and if you relock OEM Unlocking gets turned off and you would have to turn it on again... So if something fails on the first boot after relocking, your f*cked, no way to unlock.
And FRP definitely works if the bootloader is unlocked, it is just much easier to bypass.
Click to expand...
Click to collapse
You're right sorry
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.
Hi there! I've always been a Samsung user and I'm familiar with chainfire rooting method, Odin, the damn knox and all the tools that people need to achieve the beloved full control of our phones.
Let's go straight to the point: I need to buy a new phone for a friend of mine and the P9 Lite seems the most complete and suitable but I've read that if you unlock the bootloader and root it you obviously loose your warranty. The phone is unrootable by flashing a fresh OS image, but the bootloader will stay unlocked, tripping the useful warraty.
Is there any damn way to revert everything to stock in case there should be the need to send the phone to the customer service?
Thanks for the infos!
exnokiafan said:
Hi there! I've always been a Samsung user and I'm familiar with chainfire rooting method, Odin, the damn knox and all the tools that people need to achieve the beloved full control of our phones.
Let's go straight to the point: I need to buy a new phone for a friend of mine and the P9 Lite seems the most complete and suitable but I've read that if you unlock the bootloader and root it you obviously loose your warranty. The phone is unrootable by flashing a fresh OS image, but the bootloader will stay unlocked, tripping the useful warraty.
Is there any damn way to revert everything to stock in case there should be the need to send the phone to the customer service?
Thanks for the infos!
Click to expand...
Click to collapse
You can relock the bootloader if you reinstall a stock rom and revert to stock recovery, just fyi... Also there have been reports that the warranty is not void if the issue was not caused by a faulty software. Also if you are new to Huawei, be careful. And READ! A lot of people don't read, and mess up their phone...
Instead of making a new thread about the same issues I'll pitch in here too. What is the safest way to root and unroot in case of warranty? LIke the OP I came from the Samsung ecosystem too but I get the feeling if I don't at least ask about Huawei's one I'll probably **** something up.
dariomrk said:
You can relock the bootloader if you reinstall a stock rom and revert to stock recovery, just fyi... Also there have been reports that the warranty is not void if the issue was not caused by a faulty software. Also if you are new to Huawei, be careful. And READ! A lot of people don't read, and mess up their phone...
Click to expand...
Click to collapse
Simply flashing stock rom will lock bootloader but Huawei have your data of unlocking bootloader.
undercontr said:
Simply flashing stock rom will lock bootloader but Huawei have your data of unlocking bootloader.
Click to expand...
Click to collapse
That way you could say that when i get the code, i void my warranty without actually unlocking the bootloader...
dariomrk said:
That way you could say that when i get the code, i void my warranty without actually unlocking the bootloader...
Click to expand...
Click to collapse
Huawei says they "could" apply fee on unlocked phones. Maybe relocking it restores warranty? I tried to ask them but damn Chinese they don't reply.
They could, but the chance of that happening is really low, especially if your device is 100% bricked, and it needs a motherboard swap
dariomrk said:
They could, but the chance of that happening is really low, especially if your device is 100% bricked, and it needs a motherboard swap
Click to expand...
Click to collapse
If it's hardbricked and bootloader is unlocked and the problem is not related to bootloader or a process you made that requires unlocked bootloader, I think they won't fee you because it has nothing to do with bootloader. But of course a company will always choose cheaper way. If a phone goes download mode or fastboot mode it's already saved anyway.
undercontr said:
If it's hardbricked and bootloader is unlocked and the problem is not related to bootloader or a process you made that requires unlocked bootloader, I think they won't charge you
Click to expand...
Click to collapse
Exactly
undercontr said:
If a phone goes download mode or fastboot mode it's already saved anyway.
Click to expand...
Click to collapse
I wish... I can't seem to be able to save mine, even though it shows up on fastboot on the pc. The phone itself won't turn on at all. I can't seem to lock the bootloader either, anything I flash now seems to have no effect. I just hope the Huawei service fixes it.
Makishima said:
I wish... I can't seem to be able to save mine, even though it shows up on fastboot on the pc. The phone itself won't turn on at all. I can't seem to lock the bootloader either, anything I flash now seems to have no effect. I just hope the Huawei service fixes it.
Click to expand...
Click to collapse
If you have access to fastboot mode, you can flash anything. You dont have to flash an img permenantly if you want to save your phone. Use
Code:
fastboot boot boot.img
you can boot your recovery without rooting your phone. You can even open your custom recovery and flash your system.img or stock boot.img.
undercontr said:
If you have access to fastboot mode, you can flash anything. You dont have to flash an img permenantly if you want to save your phone. Use
Code:
fastboot boot boot.img
you can boot your recovery without rooting your phone. You can even open your custom recovery and flash your system.img or stock boot.img.
Click to expand...
Click to collapse
I tried fastboot flash boot boot.img (and similarly, recovery.img, system.img, any partition I could flash, multiple times with multiple files) but the phone did not boot at all. Not even into the bootloader nor recovery. It was completely unresponsive. Now the phone is not in my hands so any suggestion is too late...