Hi all,
I flashed the factory image from developer.google.com version 5.1 for my Nexus 6. After installing all my phone keeps rebooting and optimizing apps. It keeps doing this and i cant seem to find a way to get in my phone.
I relocked bootloader and cannot unlock it now because it says i need to check OEM unlock in developer options.
Any idea how i can fix this? it looks like im stuck and cannot find a way to unlock anymore to flash something else.
also, i went back into recovery and formatted data and cache. no effects after this.
help
haruryu said:
Hi all,
I flashed the factory image from developer.google.com version 5.1 for my Nexus 6. After installing all my phone keeps rebooting and optimizing apps. It keeps doing this and i cant seem to find a way to get in my phone.
I relocked bootloader and cannot unlock it now because it says i need to check OEM unlock in developer options.
Any idea how i can fix this? it looks like im stuck and cannot find a way to unlock anymore to flash something else.
also, i went back into recovery and formatted data and cache. no effects after this.
help
Click to expand...
Click to collapse
Did you use WUG's toolkit?
I had this, just had to reflash the image again but I didn't relock it first, so cant help with that.
Amos91 said:
Did you use WUG's toolkit?
I had this, just had to reflash the image again but I didn't relock it first, so cant help with that.
Click to expand...
Click to collapse
no this doesnt work
because i have no more unlocked bootloader.
@haruyu I'm in a similar situation ... Sadly I see no fix
Only thing I can think of is flashing something in stock recovery (if at all possible) ... But I don't if there is a stock recovery compatible files to flash
haruryu said:
no this doesnt work
because i have no more unlocked bootloader.
Click to expand...
Click to collapse
As yet, there is nothing we have found to fix this issue. I can't think if a fix anyway. maybe someone more familiar than me will find one but for now no-one has.
im guessing my phone is bricked.
haruryu said:
im guessing my phone is bricked.
Click to expand...
Click to collapse
Yes (and hopefully no) .... we can access fastboot, but that doesn't help because (as you know) we can flash stock images with a locked bootloader. I am hoping some of our brilliant devs can come up with a solution (they like a good challenge LOL) being we can get to fastboot, but if not, yes, we are essentially bricked
There's an option in advance that force flashes the stock image...trying going back to 5.01 then 5.1. I tried doing the flash files like some did and got stuck in a infinite bootloop so I went into the advanced thing and done it there.
HI all,
I also faced same issues Nexus 6 keep rebooting after updating to 5.1.
Locked Bootloader
any positive help would be highly appreciated
deeplyyoung said:
HI all,
I also faced same issues Nexus 6 keep rebooting after updating to 5.1.
Locked Bootloader
any positive help would be highly appreciated
Click to expand...
Click to collapse
You could try sideloading the Marshmallow update to see if that helps, sideload it and then factory reset. See if it boots fine then.
nms247 said:
You could try sideloading the Marshmallow update to see if that helps, sideload it and then factory reset. See if it boots fine then.
Click to expand...
Click to collapse
will check & revert
Related
Hello everyone!
I am really in a deseperate situation. My nexus 6 is in a bootloop. The biggest problem is that the bootloader is locked ( no option is ticked either) and usb debugging is not enabled. Is there any way I can reflash using fastboot or stock recovery?
Please help!
Rikodu said:
Hello everyone!
I am really in a deseperate situation. My nexus 6 is in a bootloop. The biggest problem is that the bootloader is locked ( no option is ticked either) and usb debugging is not enabled. Is there any way I can reflash using fastboot or stock recovery?
Please help!
Click to expand...
Click to collapse
No, no way to flash when locked other than trying to sideload an OTA. I suggest you boot to recovery and try a factory data reset.
Thank you for your reply. I have tried to hard reset but in vain. To sideload an OTA do I still need usb debugging enabled?
Rikodu said:
Thank you for your reply. I have tried to hard reset but in vain. To sideload an OTA do I still need usb debugging enabled?
Click to expand...
Click to collapse
I don't think so. What version of software were you on prior to this issue? Try to grab an OTA for your current version to the next available version if possible. Otherwise, your only option, if factory reset didn't work, is to RMA.
Evolution_Tech said:
I don't think so. What version of software were you on prior to this issue? Try to grab an OTA for your current version to the next available version if possible. Otherwise, your only option, if factory reset didn't work, is to RMA.
Click to expand...
Click to collapse
I will give it a try. Thank you very much. 5.1.1 on the phone...
I am trying to apply an update that was pushed to my Verizon Nexus 6. I was using Nexus Root Toolkit V2.0.5 developed by Wug, to do the unroot and re-lock the boot loader. It went fine no issues, have the correct build of android plugged into the toolkit. Rebooted, and I used root checker to verify that root is gone, and it is not, it is still rooted. I can unroot using supersu, and root checker confirms that root is gone. After locking the bootloader, I go and try to apply the update and it still fails. I am able to restart the phone and use it, but I do not understand what is going on with it. Anybody have any thoughts?
FireMedic1234 said:
I am trying to apply an update that was pushed to my Verizon Nexus 6. I was using Nexus Root Toolkit V2.0.5 developed by Wug, to do the unroot and re-lock the boot loader. It went fine no issues, have the correct build of android plugged into the toolkit. Rebooted, and I used root checker to verify that root is gone, and it is not, it is still rooted. I can unroot using supersu, and root checker confirms that root is gone. After locking the bootloader, I go and try to apply the update and it still fails. I am able to restart the phone and use it, but I do not understand what is going on with it. Anybody have any thoughts?
Click to expand...
Click to collapse
for the couple thousandth time it has been mentioned here, you can not apply an update if any stock files have been changed. with you having root at one point, your files have been changed. and to really unroot, you have to flash a factory image. otherwise, even tjough you unrooted, your files are still changed.
simms22 said:
for the couple thousandth time it has been mentioned here, you can not apply an update if any stock files have been changed. with you having root at one point, your files have been changed. and to really unroot, you have to flash a factory image. otherwise, even tjough you unrooted, your files are still changed.
Click to expand...
Click to collapse
Yeah hey thanks hadn't seen that a million times or so. I know updates cannot be flashed while rooted or unlocked. I am trying to unroot by flashing a factory image and it is not taking, no errors come up in the log and it reboots fine.
FireMedic1234 said:
Yeah hey thanks hadn't seen that a million times or so. I know updates cannot be flashed while rooted or unlocked. I am trying to unroot by flashing a factory image and it is not taking, no errors come up in the log and it reboots fine.
Click to expand...
Click to collapse
are you using fastboot while you are in your bootloader? oh, and you need an unlocked bootloader as well.
simms22 said:
are you using fastboot while you are in your bootloader? oh, and you need an unlocked bootloader as well.
Click to expand...
Click to collapse
Yes I am. I had locked the bootloader and tired to apply the update and that didn't work. I currently have an unlocked boot but did not root yet, was waiting for feedback from here.
FireMedic1234 said:
Yes I am. I had locked the bootloader and tired to apply the update and that didn't work. I currently have an unlocked boot but did not root yet, was waiting for feedback from here.
Click to expand...
Click to collapse
ok, boot into the bootloader, connwct via usb to your computer, the type fastboot devices. at that point, it should list your phone via a number. if it does, then its all connected right. then you can flash the factory image, but do not use the flash-all script, flash them all individually.
Ok thanks, Does it work the same if you do it through Wugs tool, clicking the flash stock + unroot button, and letting it run the scripts?
FireMedic1234 said:
Ok thanks, Does it work the same if you do it through Wugs tool, clicking the flash stock + unroot button, and letting it run the scripts?
Click to expand...
Click to collapse
ill be honest.. its best to do it the first time manually. that way you learn to do things that can fix your phone in the future, plus tool kits can and fo mess up occasionally, which make things hard to fix. i tell everyone that they can use toolkits, but they wont learn anything and will remain clueless. if you already know what you are doing, then tool kits are fine
I concur. I have used "the" toolkit to see what happens. Have had multiple failures using toolkit and always had to revert to fastboot to fix. Might as well use fastboot up front. Saves a lot of time and headaches.
simms22 said:
ill be honest.. its best to do it the first time manually. that way you learn to do things that can fix your phone in the future, plus tool kits can and fo mess up occasionally, which make things hard to fix. i tell everyone that they can use toolkits, but they wont learn anything and will remain clueless. if you already know what you are doing, then tool kits are fine
Click to expand...
Click to collapse
Gotcha thanks again!
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
You can drag and drop or copy/paste the image into the command line.
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
are you flashing with flash-all or are you flashing each image individually. dont use flash-all, flash them individually.
Share a screen print of the command prompt, with the command you executed, and the error message?
was doing the flash-all. is the command "fastboot flash system system.img" minus the quotes? If that doesn't work I will try and drop and drag see if that works
FireMedic1234 said:
was doing the flash-all. is the command "fastboot flash system system.img" minus the quotes? If that doesn't work I will try and drop and drag see if that works
Click to expand...
Click to collapse
Yes.
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
You don't need to put the system.img there. Please do read general > sticky roll-up thread > adb and fastboot...
...some time.
I guess my issue was in my head. I am so damn concerned that I am going to do something wrong and brick the phone that I am afraid to run the commands. I just flashed the system.img had it write in 4 different parts.... and it worked fine, rebooted and everything.... so far.
FireMedic1234 said:
I guess my issue was in my head. I am so damn concerned that I am going to do something wrong and brick the phone that I am afraid to run the commands. I just flashed the system.img had it write in 4 different parts.... and it worked fine, rebooted and everything.... so far.
Click to expand...
Click to collapse
Yes the flash-all.bat can't break up the image. Has something to do with how it sees the partition. Have heard that fastboot in SDK 23+ has fixed this problem. Have not confirmed as I do each individually anyway depending on what I want to do.
---------- Post added at 12:13 PM ---------- Previous post was at 12:07 PM ----------
Only way you're gonna possibly brick is flash wrong image to wrong partition. Not sure that even that can be corrected with fastboot as long as the one you bork isn't the bootloader.
Hello
After trying to do an OTA update which failed my phone won't boot normally. If I just turn it on it boots into stock recovery and if I reboot it from there it just boots back into recovery.
I have tried to do a factory reset but it won't work, it seems like the system partition has been messed up.
I keep reading that I just need to "run the RUU" but I have no idea where I can find a RUU for my phone, it's a EU 64Bit version with no carrier. The htcdev site just lists kernel sources for my device.
Any idea how I can fix this and get back to a stock system?
henning_ said:
Hello
After trying to do an OTA update which failed my phone won't boot normally. If I just turn it on it boots into stock recovery and if I reboot it from there it just boots back into recovery.
I have tried to do a factory reset but it won't work, it seems like the system partition has been messed up.
I keep reading that I just need to "run the RUU" but I have no idea where I can find a RUU for my phone, it's a EU 64Bit version with no carrier. The htcdev site just lists kernel sources for my device.
Any idea how I can fix this and get back to a stock system?
Click to expand...
Click to collapse
Download this...
http://dl4.htc.com/RomCode/Source_and_Binaries/a11ul-3.10.28-g930be6d.zip
Thanks for the reply but the link just takes me to the general download page, could you tell me what filter you used to find the correct download?
henning_ said:
Thanks for the reply but the link just takes me to the general download page, could you tell me what filter you used to find the correct download?
Click to expand...
Click to collapse
Just enter the desire 510 skip the carrier and version just EU in the region and download the first one.
MrMike2182 said:
Just enter the desire 510 skip the carrier and version just EU in the region and download the first one.
Click to expand...
Click to collapse
Ok, but those are all just kernel sources, that's the problem, I can't use any of those to restore my device.
henning_ said:
Ok, but those are all just kernel sources, that's the problem, I can't use any of those to restore my device.
Click to expand...
Click to collapse
Well the only way I think you're gonna be able to fix it now is to follow the thread that shows you how to root the phone and install a recovery called philz touch recovery for 64 bit and then you'll be able to install the back up recovery that other users have posted.
MrMike2182 said:
Well the only way I think you're gonna be able to fix it now is to follow the thread that shows you how to root the phone and install a recovery called philz touch recovery for 64 bit and then you'll be able to install the back up recovery that other users have posted.
Click to expand...
Click to collapse
Thanks, I just did this, but I installed an old backup I had made before rooting the phone earlier this year. Now I'm back!
henning_ said:
Thanks, I just did this, but I installed an old backup I had made before rooting the phone earlier this year. Now I'm back!
Click to expand...
Click to collapse
Glad you got it fixed because I couldn't find anything for you about the RUU for 64 bit... So I was pretty sure you could fix it by rooting it!
so here is what happened, i was rooted with an unlocked boot loader running chroma rom. i then tried to unroot my device to return completely back to stock. After the process was done, i formatted and wiped everything then did a reboot. when android started up chroma rom was still on there and i can't access developer settings to unlock my boot loader to flash stock image. so now i am stuck with a locked boot loader and a bootloop device. i have tried adb sideload and got back 2 errors that the footer is wrong and the signature. i don't know what to do now. so Please Help! thank you in advance.
another thing i should add, i only have access to stock recovery
i think this toolkit got a boot loop fix although i have never tried it
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
ChiefEli said:
so here is what happened, i was rooted with an unlocked boot loader running chroma rom. i then tried to unroot my device to return completely back to stock. After the process was done, i formatted and wiped everything then did a reboot. when android started up chroma rom was still on there and i can't access developer settings to unlock my boot loader to flash stock image. so now i am stuck with a locked boot loader and a bootloop device. i have tried adb sideload and got back 2 errors that the footer is wrong and the signature. i don't know what to do now. so Please Help! thank you in advance.
another thing i should add, i only have access to stock recovery
Click to expand...
Click to collapse
do you have twrp recovery, or the stock recovery?
i have stock recovery
linezero said:
i think this toolkit got a boot loop fix although i have never tried it
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Click to expand...
Click to collapse
ChiefEli said:
i have stock recovery
Click to expand...
Click to collapse
The only option is try and fastboot format userdata and fastboot format cache.
If they don't work, there is no fix. Nothing a toolkit can do.
yup, @danarama has the right explanation. problem is that with stock recovery it most likey will not work. sorry
simms22 said:
yup, @danarama has the right explanation. problem is that with stock recovery it most likey will not work. sorry
Click to expand...
Click to collapse
damn, well i will try it using the toolkit and let you know how it goes.
ChiefEli said:
damn, well i will try it using the toolkit and let you know how it goes.
Click to expand...
Click to collapse
good luck!
at the very least, it might help you fix the bootloop.
ChiefEli said:
damn, well i will try it using the toolkit and let you know how it goes.
Click to expand...
Click to collapse
Has to have unlocked bootloader for that toolkit option to work.
prdog1 said:
Has to have unlocked bootloader for that toolkit option to work.
Click to expand...
Click to collapse
simms22 said:
Click to expand...
Click to collapse
Here is the option. Direct from Wug's FAQ. "If you device is bootlooping or can’t boot up, use “Flash Stock + Unroot” with the “Soft-Bricked/Bootloop” option and follow the onscreen instructions for manually booting your device into bootloader mode and restoring your device."
Can't use flash stock option without an unlocked bootloader.
prdog1 said:
Here is the option. Direct from Wug's FAQ. "If you device is bootlooping or can’t boot up, use “Flash Stock + Unroot” with the “Soft-Bricked/Bootloop” option and follow the onscreen instructions for manually booting your device into bootloader mode and restoring your device."
Can't use flash stock option without an unlocked bootloader.
Click to expand...
Click to collapse
oh well, another "brick"..
simms22 said:
oh well, another "brick"..
Click to expand...
Click to collapse
Pretty much. I have to concur.
prdog1 said:
Pretty much. I have to concur.
Click to expand...
Click to collapse
its sad really. but this happens so often that i dont feel as bad about it anymore. now thats sad
simms22 said:
its sad really. but this happens so often that i dont feel as bad about it anymore. now thats sad
Click to expand...
Click to collapse
Why is this happening so often. Sorry but getting late to the party, I just bought my N6 from Best Buy and have been trying to get caught up on all the reading before it gets here. Is it user error or something else?
BTW, from what I see he can probably break it down and sell the parts on ebay then get close to a new one for $350.
byrdcfmma said:
Why is this happening so often. Sorry but getting late to the party, I just bought my N6 from Best Buy and have been trying to get caught up on all the reading before it gets here. Is it user error or something else?
BTW, from what I see he can probably break it down and sell the parts on ebay then get close to a new one for $350.
Click to expand...
Click to collapse
We don't know but this sucker likes to bootloop. Never relock the device till after it boots and running. Concerning relocking non-stock have seen it bork TWRP and kernel.
byrdcfmma said:
Why is this happening so often. Sorry but getting late to the party, I just bought my N6 from Best Buy and have been trying to get caught up on all the reading before it gets here. Is it user error or something else?
BTW, from what I see he can probably break it down and sell the parts on ebay then get close to a new one for $350.
Click to expand...
Click to collapse
because many people dont read and educate themselves beforehand.
I don't understand why people are re-locking their boot loader. Unless you are returning the device, what is the purpose of re-locking it? I don't get, in this particular thread, why or how the boot loader got locked?
BladeRunner said:
I don't get, in this particular thread, why or how the boot loader got locked?
Click to expand...
Click to collapse
And that is a key question.
I was trying to get ready to turn in my nexus 6 and so I flashed a stock rom (apparently minus the recovery) and relocked my device. I now have twrp but stock 5.1 installed. twrp boots okay but internal storage is 0mb and it appears unable to format partitions. any ideas on a resolution? very comfortable with fastboot (bootloader loads normally) but can't seem to get anything working otherwise.
my one plus 3t is bricked unbricked using msmtool but now i cant install or update the ROM into it.. please help me can someone help me using team viewer please or a remote might also help me.. please help me no wifi and bluetooth too as of now.
avnash09 said:
my one plus 3t is bricked unbricked using msmtool but now i cant install or update the ROM into it.. please help me can someone help me using team viewer please or a remote might also help me.. please help me no wifi and bluetooth too as of now.
Click to expand...
Click to collapse
not even a single reply.. this is not the way to treat a new member thanq
avnash09 said:
not even a single reply.. this is not the way to treat a new member thanq
Click to expand...
Click to collapse
There are a couple of reasons for people not replying.
First of all, the lack of details on your problem makes it impossible to determine the solution.
1. What do you mean bricked? Bootloop? Stuck on OnePlus logo? Hard brick? How did you get it bricked in the first place?
2. The restore tool removes TWRP. Have you installed it again?
3. What do you mean you can't install or the update the ROM? Is there an error message? Are you trying to flash a custom ROM in the stock recovery?
4. You waited less than 2 hours. You realize there are different time zones? Some people are sleeping, others are at work.
ast00 said:
There are a couple of reasons for people not replying.
First of all, the lack of details on your problem makes it impossible to determine the solution.
1. What do you mean bricked? Bootloop? Stuck on OnePlus logo? Hard brick? How did you get it bricked in the first place?
2. The restore tool removes TWRP. Have you installed it again?
3. What do you mean you can't install or the update the ROM? Is there an error message? Are you trying to flash a custom ROM in the stock recovery?
4. You waited less than 2 hours. You realize there are different time zones? Some people are sleeping, others are at work.
Click to expand...
Click to collapse
hi ,
i am a newbie here . my phone gets heated up after the ota install of 4.1.6 so i thought of factory resetting it. after resetting it. it got struck on the one plus logo and started booting again and again. so one of my friend asked to check the forum and i used [UNBRICK] Unbrick Tutorial For The OnePlus 3T!!!!!!!!! by Haris K. from the forum. it installed the os sucessfully. but i couldnt find wifi and bluetooth buttons enabled. so i thought of installing new roms but it gets struck on the one plus logo.. please help me. thanks in advance
avnash09 said:
not even a single reply.. this is not the way to treat a new member thanq
Click to expand...
Click to collapse
Hey you self-entitled prick, transfer a copy of the full ROM onto your phone through adb/USB OTG/MTP and flash it through the stock recovery. If you had previously unlocked your bootloader and have TWRP installed, use that to flash instead. If you do not know what any of the above means, look for it yourself through the forums.
Anova's Origin said:
Hey you self-entitled prick, transfer a copy of the full ROM onto your phone through adb/USB OTG/MTP and flash it through the stock recovery. If you had previously unlocked your bootloader and have TWRP installed, use that to flash instead. If you do not know what any of the above means, look for it yourself through the forums.
Click to expand...
Click to collapse
after flashing the rom i am getting a message decryprtion unsuccessful. the password is correct but the data is corrupt how to bypass this message
avnash09 said:
after flashing the rom i am getting a message decryprtion unsuccessful. the password is correct but the data is corrupt how to bypass this message
Click to expand...
Click to collapse
Get into the stock recovery and wipe both cache and userdata partitions before proceeding to troubleshoot further.
fareed_xtreme said:
Get into the stock recovery and wipe both cache and userdata partitions before proceeding to troubleshoot further.
Click to expand...
Click to collapse
after doing so my OS has started but wifi and bluetooth are greyed out. persist folder cannot find any data
.bt_nv.bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
no file exists .. is the answer i get
avnash09 said:
after doing so my OS has started but wifi and bluetooth are greyed out. persist folder cannot find any data
.bt_nv.bin
WCNSS_qcom_wlan_nv.bin
WCNSS_qcom_wlan_nv_calibration_persist.bin
WCNSS_qcom_wlan_nv_regulatory_persist.bin
no file exists .. is the answer i get
Click to expand...
Click to collapse
Reflash with the MSMtool after re-downloading everything and verifying all downloads first before proceeding. Use the tool I have posted at https://forum.xda-developers.com/oneplus-3t/how-to/guide-official-op3t-stock-reset-to-oos-t3598864
Ensure you verify before starting the flash. Also uninstall or deactivate any anti virus application installed on your PC.
should i change the data partitions and everything to f2fs or other thing. system to ext4 data to f2fs
For now, don't worry about the data partitions. As mentioned above, reflash from MSMTools, verify the downloaded package first, and then check. All your issues are probably caused by a bad file.