Related
I have seen quite of few people screw up their devices by not knowing what they are doing. So I am making this thread to simply tell people not familiar with fastboot what they should and should not do.
1. Fastboot oem unlock will unlock your bootloader and do a complete wipe of your device. As far as I know the only way for something to go wrong here is if you're device is low on battery and shuts off during the process. Either plug it in or have a "good" amount of juice left in your battery. To be 100 percent sure plug it in.
Before I get into oem lock IMHO you should only use this command for one thing only. Getting the device ready to send into motorola for the LGT upgrade or a another warranty repair or some sort. When done properly it is completely safe but there is no reason to do to go back to "stock".
2. Fastboot oem lock. Do not issue this command unless you are absolutely sure you have the correct software on your device. The correct software is what you get from the motodev site for your device. You need the official sofware images for your specific device AND REGION. If it is not released then DO NOT re-lock the device. If you have a OTA installed you will need to flash back to the motodev images first.
All this info is all ready on the forums in various threads already but I wanted to put in one place since I noticed quite a few users botch up the devices trying to update to 3.1 The last thing we need are a bunch of people bricking the devices and sending them in moto. I suspect if enough people do it they will end up changing their minds on the entire encrypted bootloader situation.
I know you have to unlock to flash "non-stock" images, but do you have to unlock if you are only going to flash the "stock" motodev images?
If I am currently just unlocked, not rooted do I need to lock in order to get the 3.1 update?
ccogan said:
If I am currently just unlocked, not rooted do I need to lock in order to get the 3.1 update?
Click to expand...
Click to collapse
NO. the update only checks for stock files, not lock or unlock.
Blaisun said:
I know you have to unlock to flash "non-stock" images, but do you have to unlock if you are only going to flash the "stock" motodev images?
Click to expand...
Click to collapse
before you can flash anything you will need to unlock the bootloader.
how to lock the bootloader????
albundy2010 said:
I have seen quite of few people screw up their devices by not knowing what they are doing. So I am making this thread to simply tell people not familiar with fastboot what they should and should not do.
1. Fastboot oem unlock will unlock your bootloader and do a complete wipe of your device. As far as I know the only way for something to go wrong here is if you're device is low on battery and shuts off during the process. Either plug it in or have a "good" amount of juice left in your battery. To be 100 percent sure plug it in.
Before I get into oem lock IMHO you should only use this command for one thing only. Getting the device ready to send into motorola for the LGT upgrade or a another warranty repair or some sort. When done properly it is completely safe but there is no reason to do to go back to "stock".
2. Fastboot oem lock. Do not issue this command unless you are absolutely sure you have the correct software on your device. The correct software is what you get from the motodev site for your device. You need the official sofware images for your specific device AND REGION. If it is not released then DO NOT re-lock the device. If you have a OTA installed you will need to flash back to the motodev images first.
All this info is all ready on the forums in various threads already but I wanted to put in one place since I noticed quite a few users botch up the devices trying to update to 3.1 The last thing we need are a bunch of people bricking the devices and sending them in moto. I suspect if enough people do it they will end up changing their minds on the entire encrypted bootloader situation.
Click to expand...
Click to collapse
Question for you, how do I go about entering this command? My knowledge is basic. I have unrooted, restocked a Nexus 7. Trying to do oem lock without being able to use the screen. Cannot enable USB debugging because the screen is nonoperational. Any advice?
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?
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Durvid said:
Hey there.
So I tried to use the Nexus Root Toolkit to sideload the OTA, but now when I try to boot my phone it just shows the white google screen and doesn't do anything. I can use ADB and fastboot and get into the bootloader but I can't flash the factory image because I never checked the "Allow OEM Unlock" tick since I didn't plan on unlocking the bootloader. Can anyone help me out here?
Click to expand...
Click to collapse
This is exactly why you should never mess with updates or flashing anything with a locked bootloader. If a factory reset doesn't fix it you're likely out of luck.
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
I'll attempt this. Weirdly enough when I look at device info in adb it shows it as being on the newest version. But Yeah I'll attempt to flash what I was on before.
Yeah, I mean I've done this before with no issues on my Nexus 6 and there were no issues but that was unlocked when I got it. I just thought you didn't have to unlock the bootloader to sideload OTA's? I may be wrong.
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
Click to expand...
Click to collapse
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Durvid said:
Yeah like I thought, "Device is locked. Cannot Flash Images"
I wish I had known they added that "Allow OEM Unlock" Switch in Lollipop. Would have solved my problem if I had that toggled.
Click to expand...
Click to collapse
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
hutzdani said:
if your bootloader is locked still I can't see how flashing an OTA would effect this.
Have you tried to flash just the original bootloader from the android version on your device ( not the version you wish to update to )
Fastboot flash bootloader bootloader.img
DON'T USE A TOOL KIT ! UNLESS YOU KNOW WHAT YOU ARE DOING ! There where clear instructions on how to flash OTA's on this site and likely in the toolkit.
Unfortunately this is a case of NOT reading before doing things, I have yet to see anyone recover from this.
Best of luck tho, but it might be a lesson learned the hardway a.k.a RMA
Click to expand...
Click to collapse
akellar said:
You just said you had a nexus 6 unlocked, how did you not know the switch existed?
Click to expand...
Click to collapse
I bought it used on /r/hardwareswap and whoever I got it from had already unlocked it.
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Heisenberg said:
I know someone advised you to try to flash a bootloader, but it isn't going to work of your bootloader is locked. What build were you on and which OTA zip did you try to flash?
Click to expand...
Click to collapse
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Durvid said:
I started on 6.0 MDB08L and was trying to flash 6.1 MMB29M
Click to expand...
Click to collapse
OK, but I need the name of the zip please.
Heisenberg said:
OK, but I need the name of the zip please.
Click to expand...
Click to collapse
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Heisenberg said:
OK, just needed to make sure you had the right one. What have you done to troubleshoot so far?
Click to expand...
Click to collapse
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Durvid said:
I've tied to flash stock, but can't do that due to the bootloader being locked, tried to just hard reset but it just does the same thing where it gets stuck on the Google logo. I checked the manufacture info in the toolkit and everything is clean. Tried to flash the old bootloader but like you said I can't flash since I'm locked. Not really sure what else to do :/
Click to expand...
Click to collapse
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Heisenberg said:
Honestly, I think you're pretty much screwed unfortunately. You could talk to Google support and see if they'll RMA the phone.
Click to expand...
Click to collapse
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Durvid said:
Yeah I think they would do it since I technically didn't void any warrantys or anything. I appreciate the help. What do I need to make sure to do if I do this again in the future? Definitely "Allow OEM Unlock", and do I have to unlock the bootloader? I was under the impression that you didn't have to to flash an OTA.
Click to expand...
Click to collapse
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Durvid said:
Sorry, it's
533df5ddfa4297997634a8553f0122be5cca4c09.signed-angler-MMB29M-from-MDB08L.zip.
Grabbed it from here: https://www.reddit.com/r/Nexus6P/comments/3w6qzd/easy_how_to_sideload_ota_601/
Click to expand...
Click to collapse
Hilarious that the top comment is mine telling you why doing this is a bad idea
Heisenberg said:
Definitely unlock the bootloader, it isn't needed to flash an update via the stock recovery, but it is needed to get out of sticky situations like this. If your bootloader was unlocked now you'd be up and running in ten minutes.
Click to expand...
Click to collapse
Yeah, I'll probably wait for the update over the air for a while and maybe if I feel reallly eager I'll just make sure I unlock and such. Annoying that you can't unlock via fastboot anymore without that toggle. I get that Google is trying to make Android super secure but It's not too useful for folks like us. Sure it's bricked a lot of devices.
akellar said:
Hilarious that the top comment is mine telling you why doing this is a bad idea
Click to expand...
Click to collapse
I've done it before with other devices. I wouldn't say it's inherently bad. It's just that there was one toggle that I wasn't aware of that caused the issue. You live and you learn.
THIS IS NOT MY IDEA !
I found this in a N9 thread and it worked according to the user with the issue, apply this with the correct t factory image ( do it with the version you have on your device not the one you tried to update to ! )
This might not work but its worth a try ! Before doing this read about ADB and Fastboot !!!!!!!!!!!!!!!! Try and understand the basics and know what the commands are doing to help backtrack e.C.t
If it does work - go to settings and allow OEM Unlock and USB debug !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Then go read from reputable sources how to flash images manually via adb !!!!!!!!!!!!!!!!!!!!!!!
I'd follow vomers guides.
Had this problem with another device cool thing to remeber is that on locked devices the only thing that is different is that there is a signature before the MAGIC header so the solution is to pull the android stock images from https://developers.google.com/android/nexus/images. Once done extract the images in both the zip and the tar that is inside the zip. You will see recovery.img inside the tar. One thing about the boot process of TWRP is that it enables adb in preboot meaning while in the boot loop you should have access to adb. With access to adb all you need to do is dd the images over the corresponding partitions: i.e.
PLEASE NOTE NOT FOR THE FEINT OF HEART. I AM NOT RESPONSIBLE FOR YOU BRICKING YOUR DEVICE.
Quote:
adb push recovery.img recovery.img
adb shell dd if=recovery.img of=/dev/block/<recoverymmcblock>
I dont know if the default recovery has adb push update so id probably recommend doing this on every partition thats inside the tar, i.e. system, boot.
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...