Stock rom without root or unlock only can enter bootloader - Nexus 6 Q&A, Help & Troubleshooting

My nexus 6 using stock rom and update to the latest version thru OTA, without root or unlock bootloader. Yesterday it suddenly reboot and only allow to boot into bootloader. Cannot select recovery or factory mode, check the bootloader log show failed to validate the boot image or recovery image.
I've read many threads and try many methods to unloock the bootloader and flash the factory image but failed.
Anyone can help to get the nexus 6 back, thanks so much.

Probably going to have to do an RMA, you can't use any of the recovery options (fastboot, custom recoveries) with a locked bootloader, that is the whole point of it being locked.

Since we're now suggesting RMA, I have to ask...
Have you tried in the bootloader screen "fastboot oem unlock"?
Maybe you have, but your problem description is really pretty vague.
scryan, not trying to tread on your toes, and I may be completely wrong (about to fall asleep) but isn't the whole point of "fastboot oem unlock" that it runs in bootloader specifically to unlock it?

dahawthorne said:
Since we're now suggesting RMA, I have to ask...
Have you tried in the bootloader screen "fastboot oem unlock"?
justMaybe you have, but your problem description is really pretty vague.
scryan, not trying to tread on your toes, and I may be completely wrong (about to fall asleep) but isn't the whole point of "fastboot oem unlock" that it runs in bootloader specifically to unlock it?
Click to expand...
Click to collapse
I am sorry as this is my 1st post here. My Nexus 6 was not rooted and even not enable "usb debug" or "oem unlock" setting.
I've already tried "fastboot oem unlock" and failed. I've also tried "fastboot flashing unloock", it said ok but restart the bootloader and it still show locked.
I've also tried the Nexus Root Tools too to unlock or flash the factory image, recovery image or boot to twrp but all failed too.

Then you have no choice but to request a RMA. To be able to unlock the bootloader so you can then flash a stock ROM, you have to enable Developer Options, then in Developer Options enable both USB Debugging and OEM Unlock.

Have you tried the hardbrick tread? Not sure if this will work with locked bootloaders. http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:06 PM ---------- Previous post was at 08:50 PM ----------
Have you tried fastboot reboot-recovery to enter recovery? With or without the "-", I forget the proper form. With locked bootloaders I don't think u can flash anything from recovery. Plus it may be a hardware issue not necessarily software related.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
But if you can enter recovery maybe you can factory reset and at least get it to boot!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:03 PM ---------- Previous post was at 09:07 PM ----------
What version of fastboot are you using, old fastboot may not work properly.
Sent from my Nexus 6 using Tapatalk

Jnewell05 said:
Have you tried the hardbrick tread? Not sure if this will work with locked bootloaders. http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:06 PM ---------- Previous post was at 08:50 PM ----------
Have you tried fastboot reboot-recovery to enter recovery? With or without the "-", I forget the proper form. With locked bootloaders I don't think u can flash anything from recovery. Plus it may be a hardware issue not necessarily software related.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
But if you can enter recovery maybe you can factory reset and at least get it to boot!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:03 PM ---------- Previous post was at 09:07 PM ----------
What version of fastboot are you using, old fastboot may not work properly.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thx so much for your reply, I've tried the hard-brick thread but can't install the qualcomm driver.
I plan to contact the Google see whether it can help me since I am in HK and my Nexus 6 is not directly bought from HK Google.
It really quite depress me since I do nothing with the phone, I do not flash any custom rom, do not root or unlock bootloader, just normal use it then suddenly crashed .... >_<

this exact same thing happened to my wife's phone just a month ago... and the sad thing is the phone was just bought new for only 2 months or so. never installed any custom roms, never rooted, etc. and now i wish that i did so that i could have at least turned ON that option in Developers Option to "allow OEM Unlock" and if i did, it should've been an easy fix.
i never had this kind of issue before thats why i thought there is nothing important to turn on in the Developers Option. they should've made that information more available and even point it out on the Update but they didn't which sucks.
i also tried to contact Motorola US but since im not in the US, even though the phone is bought in the US via Ebay, they weren't able to help and sent me to another Motorola site for my region. i'm trying it now and i still cant go through the site...
it's really depressing when this kind of things happen... i hope in the future there would be some kind of fix for this. i heard if we can get a signed System that we could flash into the phone then there's a chance it could work but as of now, i keep checking for information about this and hoping someone came up with something...
hope this thing won't happen to anyone else and if you got a Nexus 6, make sure to turn On "Allow OEM Unlock" on your phone.

quinceyr said:
this exact same thing happened to my wife's phone just a month ago... and the sad thing is the phone was just bought new for only 2 months or so. never installed any custom roms, never rooted, etc. and now i wish that i did so that i could have at least turned ON that option in Developers Option to "allow OEM Unlock" and if i did, it should've been an easy fix.
i never had this kind of issue before thats why i thought there is nothing important to turn on in the Developers Option. they should've made that information more available and even point it out on the Update but they didn't which sucks.
i also tried to contact Motorola US but since im not in the US, even though the phone is bought in the US via Ebay, they weren't able to help and sent me to another Motorola site for my region. i'm trying it now and i still cant go through the site...
it's really depressing when this kind of things happen... i hope in the future there would be some kind of fix for this. i heard if we can get a signed System that we could flash into the phone then there's a chance it could work but as of now, i keep checking for information about this and hoping someone came up with something...
hope this thing won't happen to anyone else and if you got a Nexus 6, make sure to turn On "Allow OEM Unlock" on your phone.
Click to expand...
Click to collapse
Hi, quinceyr, I've just tried the below thread and restore my Nexus 6 back and only draw back is updated to Android N preview version. I've tested for a while seems work fine and will keep monitor for a period.
http://forum.xda-developers.com/nexus-6/help/command-device-corrupt-update-t3362317/page2
Hope your Nexus 6 will recover back.

Related

[Q] Sprint update bricked my phone. More details in post, need some desperate help.

Hi guys so this is a little embarrassing but I'm fairly certain sprint update has bricked my phone. Sprint pushed the update to 4.4 2 nights ago for me and everything was going fine. My phone is rooted and custom recovery so I slapped on the stock recovery to process the update. The update starts off fine and dandy until about halfway through the dreaded red triangle/exclamation mark popped up. I instantly cursed and watched as my phone entered into an infinite boot loop. I thought it might have worked at first because the lock screen popped up, but when you unlock the phone the white htc logo is still there and the phone reboots after 10 seconds. So after making sure something went astronomically wrong with the update, I went into the boot loader and adb pushed twrp back onto the phone. the update somehow updated my hboot to 1.55 so my s-off is now s-on and I have no wawy to tell if the kernal for the phone is functioning. My only guess to this matter is that the boot sector for the phone is corrupt, but I tried to restore the stock twrp backup i have, and nothing. It boots, the lockscreen unlocks, but it still reboots. Now it was unlocked long enough for me to get into settings and see that it wiped ALL of my phones id info. All the meid, meie, carrier, everything is blank. So it seems that the phone crashed somewhere in the update where it was in the process of wiping things? I then tried to flash a completely different rom on there to see how that went. I first tried viperone 5.0.0 then the newer 5.8.0 and neither would boot (waited 1 hour each to make sure). Then I tried arhd 61 and again, no boot. So I'm not quite sure where to go from here. My stock backups aren't working at restoring, new rom flash isnt working, I can't take it into sprint to check on it since its rooted, I can't update the kernel due to s-on (correct me if im wrong). I'm smart enough to know when I'm out of my depth and I'm clearly trying to tread water in the middle of the ocean in this instance. So please if someone could give me a hand I would appreciate it so much.
xanex18 said:
Hi guys so this is a little embarrassing but I'm fairly certain sprint update has bricked my phone. Sprint pushed the update to 4.4 2 nights ago for me and everything was going fine. My phone is rooted and custom recovery so I slapped on the stock recovery to process the update. The update starts off fine and dandy until about halfway through the dreaded red triangle/exclamation mark popped up. I instantly cursed and watched as my phone entered into an infinite boot loop. I thought it might have worked at first because the lock screen popped up, but when you unlock the phone the white htc logo is still there and the phone reboots after 10 seconds. So after making sure something went astronomically wrong with the update, I went into the boot loader and adb pushed twrp back onto the phone. the update somehow updated my hboot to 1.55 so my s-off is now s-on and I have no wawy to tell if the kernal for the phone is functioning. My only guess to this matter is that the boot sector for the phone is corrupt, but I tried to restore the stock twrp backup i have, and nothing. It boots, the lockscreen unlocks, but it still reboots. Now it was unlocked long enough for me to get into settings and see that it wiped ALL of my phones id info. All the meid, meie, carrier, everything is blank. So it seems that the phone crashed somewhere in the update where it was in the process of wiping things? I then tried to flash a completely different rom on there to see how that went. I first tried viperone 5.0.0 then the newer 5.8.0 and neither would boot (waited 1 hour each to make sure). Then I tried arhd 61 and again, no boot. So I'm not quite sure where to go from here. My stock backups aren't working at restoring, new rom flash isnt working, I can't take it into sprint to check on it since its rooted, I can't update the kernel due to s-on (correct me if im wrong). I'm smart enough to know when I'm out of my depth and I'm clearly trying to tread water in the middle of the ocean in this instance. So please if someone could give me a hand I would appreciate it so much.
Click to expand...
Click to collapse
Oh man.. this is rough. If you can get into fastboot, I would say try RUUing. That's what always fixed my problems haha
Sent from my HTCONE using Tapatalk
---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------
I recommend this RUU
http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my HTCONE using Tapatalk
Bairdog35 said:
Oh man.. this is rough. If you can get into fastboot, I would say try RUUing. That's what always fixed my problems haha
Sent from my HTCONE using Tapatalk
---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------
I recommend this RUU
http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
I will Definitely check it out. I was hesitant to try an RUU because all the ones I was looking at were talking about flashing modded kernels and needing s-off and such. But I will definitly try it and update if it works.
Bairdog35 said:
Oh man.. this is rough. If you can get into fastboot, I would say try RUUing. That's what always fixed my problems haha
Sent from my HTCONE using Tapatalk
---------- Post added at 11:08 PM ---------- Previous post was at 11:04 PM ----------
I recommend this RUU
http://forum.xda-developers.com/showthread.php?t=2658910
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Alright mate, I'm gunna need a mailing address to send my first born son to. You are a god send with that link. It worked perfectly
xanex18 said:
Alright mate, I'm gunna need a mailing address to send my first born son to. You are a god send with that link. It worked perfectly
Click to expand...
Click to collapse
I'm glad it worked ?
Sent from my HTCONE using Tapatalk

Fingerprint scanner not working

I've tried 3 different Roms and get this error..an error has occurred. ..try restarting etc etc.
Searching will give you full answer. Basically you have to go back to stock and start over.
here is the answer to you ur problem i had the same issue
http://forum.xda-developers.com/showthread.php?t=2919478
I tried that and still can not get it to work
jjr3211 said:
I tried that and still can not get it to work
Click to expand...
Click to collapse
Did you flash the latest modem NJ7?
As far as I know I did I flashed the the whole firmware package for nj7 still no luck
---------- Post added at 10:08 PM ---------- Previous post was at 10:05 PM ----------
Is there a place to check just to make sure
jjr3211 said:
As far as I know I did I flashed the the whole firmware package for nj7 still no luck
---------- Post added at 10:08 PM ---------- Previous post was at 10:05 PM ----------
Is there a place to check just to make sure
Click to expand...
Click to collapse
Get the phone info app from the market
jjr3211 said:
As far as I know I did I flashed the the whole firmware package for nj7 still no luck
---------- Post added at 10:08 PM ---------- Previous post was at 10:05 PM ----------
Is there a place to check just to make sure
Click to expand...
Click to collapse
settings about device baseband version
Well it is nj7 I have factory reset it a couple of times Odin back to stock a couple of times as well and still can not get it to work
[/COLOR]
jjr3211 said:
Well it is nj7 I have factory reset it a couple of times Odin back to stock a couple of times as well and still can not get it to work
Click to expand...
Click to collapse
I bought my white note 4 on Oct 30 or 31, can't remember, I read all the problems with this fingerprint scanner stuff, but I did not root for 2 days. and the past 2 days I did everything I was on NIH, and when testing my stock odexed roms, I had the fingerprints saved, but when I flashed, I couldn't log in, so when I deleted the saved fingerprints is when this happened, the error messages,
I did the firmwares so many times for the NIH, did not work... :crying: I then upgraded the firmware to NJ7 same thing, could not get it working...
I went to another tmobile store, and the guy went into downloader mode.. shocked me,, but he said I need to goto where I bought the phone to change it out, he didn't have any note 4... but he went and reset the phone and didn't work...
when I got home, I called tmobile 611... and went through the process and they said, they don't have any replacements, since I didn't buy the phone from them, they can't send a new phone, for me to goto the tmobile store I bought the phone, but no one has the note 4.. call back next week and we can send a replacement.
I called the corporate store today, they had 2 in black, I really wanted the white, but I took the black anyway.. lucky they were so busy, they didn't check the phone and swapped everything out.
I guess im gonna wait a bit before rooting and flashing the phone, to see what everyone finds out.
I have the same problem with my note 4. tried everything already so it may be hardware related. will buy a home button replacement from ebay hopefully that helps will update if successful

Unlocking bl without wipe

Basically what the title says. Is it possible. Also if not will it wipe my sd card. Internal obviously to save some smart arse! The nexusunlckr app on playstore don't support the 6.
Thanks
Sent from my Nexus 6 using Tapatalk
Mr_S said:
Basically what the title says. Is it possible. Also if not will it wipe my sd card. Internal obviously to save some smart arse! The nexusunlckr app on playstore don't support the 6.
Thanks
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
It will factory reset and wipe data but should leave internal sd intact.
Mr_S said:
Basically what the title says. Is it possible. Also if not will it wipe my sd card. Internal obviously to save some smart arse! The nexusunlckr app on playstore don't support the 6.
Thanks
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
not possible. aa soon as you unlock the bootloader, itll delete everything thats in your storage. everything.
---------- Post added at 02:50 PM ---------- Previous post was at 02:49 PM ----------
prdog1 said:
It will factory reset and wipe data but should leave internal sd intact.
Click to expand...
Click to collapse
not true. as soon as you unlock the bootloader, itll wipe every single bit of your storage, and even warns you before you press yes.
simms22 said:
not possible. aa soon as you unlock the bootloader, itll delete everything thats in your storage. everything.
---------- Post added at 02:50 PM ---------- Previous post was at 02:49 PM ----------
not true. as soon as you unlock the bootloader, itll wipe every single bit of your storage, and even warns you before you press yes.
Click to expand...
Click to collapse
Been so long couldn't remember if actually wiped storage or just user data.
oh, the n6 doesnt have a sd slot, so cant wipe it. but it does wipe all of your storage. no ifs, ands, or buts..
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
prdog1 said:
Been so long couldn't remember if actually wiped storage or just user data.
Click to expand...
Click to collapse
thats usually one of my problems, doing stuff so long ago that i forget. but this one i dont forget, since every one of my nexus has to go through it, once.
simms22 said:
oh, the n6 doesnt have a sd slot, so cant wipe it. but it does wipe all of your storage. no ifs, ands, or buts..
---------- Post added at 02:54 PM ---------- Previous post was at 02:52 PM ----------
thats usually one of my problems, doing stuff so long ago that i forget. but this one i dont forget, since every one of my nexus has to go through it, once.
Click to expand...
Click to collapse
N9 does it on relock also. Not sure about N6. Never relocked it. Lol
prdog1 said:
N9 does it on relock also. Not sure about N6. Never relocked it. Lol
Click to expand...
Click to collapse
i think the n6 does it on relock as well, but ive also never ever relocked a bootloader.
simms22 said:
i think the n6 does it on relock as well, but ive also never ever relocked a bootloader.
Click to expand...
Click to collapse
Yup, it wipes the device (N6) when locking the BL too
Mr_S! I had to deal with this too. I simply copied the files on my n6 to pc, unlocked and moved everything back to the phone when I couldn't find a way to unlock the BL without wiping.
Please don't feel stalked, but if I remember correctly, this has to be the third, if not fourth device we share. Anyway, nice to see you
Gesendet von meinem Nexus 6 mit Tapatalk
nitrousĀ² said:
Mr_S! I had to deal with this too. I simply copied the files on my n6 to pc, unlocked and moved everything back to the phone when I couldn't find a way to unlock the BL without wiping.
Please don't feel stalked, but if I remember correctly, this has to be the third, if not fourth device we share. Anyway, nice to see you
Gesendet von meinem Nexus 6 mit Tapatalk
Click to expand...
Click to collapse
Wow! My friend from the one x days! Hello[emoji1] never managed to s-off that thing lol. Anyway thats what im thinking of doing. Another thing. I used to flash custom roms to get the latest version of android but courtesy of the mrs ive now got a 6. However there are some things i miss ie. Customisable toggles, hold back to kill, percent in clock ect so in peoples opinions is it worth it weighing up the pros and cons.... Are there any con's?
Ps i know there's apps what can do what i desire
Sent from my Nexus 6 using Tapatalk
Mr_S said:
Wow! My friend from the one x days! Hello[emoji1] never managed to s-off that thing lol. Anyway thats what im thinking of doing. Another thing. I used to flash custom roms to get the latest version of android but courtesy of the mrs ive now got a 6. However there are some things i miss ie. Customisable toggles, hold back to kill, percent in clock ect so in peoples opinions is it worth it weighing up the pros and cons.... Are there any con's?
Ps i know there's apps what can do what i desire
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
On the software side, I miss the One-Handed-Mode from Samsung sometimes as it made it very easy to deal with the big screen. Other than that, there are no cons as it's just what I wanted all the time but couldn't afford. On the hardware side though, coming from years of quality Samsung AMOLED panels, there's the outdated and disappointing AMOLED screen with weird colors and burn ins. But I can live with that. At least I don't have to deal with s-off and TouchCrap and stuff :laugh: If I'd make a list, the pros would outweigh significantly.
Sorry for going OT here =)
My thread mate feel free no ot here!
Btw. What cons have you noticed on custom over stock? Anyone else care to pipe up. For example on exynos chips cause they don't release drivers for gps ect some ROMs would gps issues.
Sent from my Nexus 6 using Tapatalk
I really can't tell you since I'm on CM since day 1. But from what I hear and saw on my N5, there's no real difference performance wise. I think at this time it all comes down to extending Android rather than improving performance. Sure there's the encryption thing on the N6 but I'm fine with that. I tried using it decrypted for a couple of days but there's absolutely NO impact on everyday usage/performance I could notice. And I have to tell you, I'm on CyanogenMod only because of the Theme Engine and App Permissions (Xprivacy isn't nearly as convenient).
To sum it up; No critical cons, wait, no cons at all I can think of using a custom ROM.
Mr_S said:
Wow! My friend from the one x days! Hello[emoji1] never managed to s-off that thing lol. Anyway thats what im thinking of doing. Another thing. I used to flash custom roms to get the latest version of android but courtesy of the mrs ive now got a 6. However there are some things i miss ie. Customisable toggles, hold back to kill, percent in clock ect so in peoples opinions is it worth it weighing up the pros and cons.... Are there any con's?
Ps i know there's apps what can do what i desire
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
If you know what you`re doing and what you want rooting has no downside* imo, it opens doors to many options and features and enhances the look and performance of the phone. There i said it
* Warranty on devices may regionaly be rejected if the phone is turned in for service/repair with root privileges and/or custom software.
@Mr_S have you unlocked your BL already? I can't relock the BL. Whenever I try to relock the BL I get this error message
Code:
...
(bootloader) FAIL: Please run fastboot oem lock begin first!
(bootloader) sst lock failure!
FAILED (remote failure)
finished. total time: 0.012s
Turns out I have to type
Code:
fastboot oem lock begin
first, then flash a factory image and end the process with
Code:
fastboot oem lock
However that doesn't work as upon finishing flashing BL and radio .imgs, the updater script tells me that system.img is missing, press any key to exit. The process aborts. Ending this process with
Code:
fastboot oem lock
gives out the same error message as above. Flashing the factory image manually and it's the same all over again. Now I'm desperate for a solution.
No not yet so can't help you mate
Sent from my Nexus 6 using Tapatalk

Bootloader unlocking theory

Agimax recently discovered a way into fast boot mode
Agimax said:
Ok, so i've been able to nuke my LAF partition and get into Fastboot mode. This gives access to all fastboot commands, but removes ability to use Download Mode. I am on ZV6 / UltraPOP. Once you backup your laf partition, you can reboot like you would for download mode but goes to fastboot. You can restore LAF partition from the backup you make and get back access to download mode.
I tried to see if our bootloader will unlock like the way they do it in the T-Mobile forums by checking the OEM Unlock in the developer menu, then booting to Fastboot and running 'Fastboot.exe oem unlock', but unfortunately it will not work. The phone does not recognize the unlock command like it does for the T-Mobile versions. See screenshots. I'm still working on this. Keep in mind, if you do something wrong, you will NOT have the ability to TOT without the download mode until you restore the LAF back to the phone!
Instructions: (only try if you are an advanced tester!)
1.) Backup your LAF partition command from ADB
* copy this in a safe place before nuking your LAF partition. Like on a flashdrive or computer.
Code:
dd if=/dev/block/bootdevice/by-name/laf of=/sdcard/laf.img
2.) Nuke your LAF partition command from ADB
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/laf
* now you can boot into fastboot mode by booting like you would into download mode (up-volume and power on with usb plugged in)
Note: Once you are in fastboot mode, you must update the drivers on your computer by opening device manager and clicking on the ADB device and updating driver over internet. Reboot back into fastboot mode and commands will work.
To restore your LAF partition command from ADB
Code:
'dd of=/dev/block/bootdevice/by-name/laf if=/sdcard/laf.img'
* you may also restore the laf partition from fastboot if you wish, but they are different commands
My thoughts are -if we were able to Nuke the LAF partition on 6.0 M, we would be able to copy the partitions from the phone we would need to make rooted system images and also modem and kernel. This should allow us to copy partitions to a phone running 5.1 and switch between by just flashing the 3 partitions back and forth.
Click to expand...
Click to collapse
Im wondering if we can get the unlock files from one of the other models and hexing out the unlock bin from imei numbers and zeros, maybe we can unlock our device by replacing them with our imei and serial number??
Who knows. I'm not a developer so maybe someone can try it. There's just not enough attention from developers for this device.
LaughingCarrot said:
Who knows. I'm not a developer so maybe someone can try it. There's just not enough attention from developers for this device.
Click to expand...
Click to collapse
That is some constructive feedback...
jaxbierley said:
That is some constructive feedback...
Click to expand...
Click to collapse
Just throwing something in to make conversation is all.
sorry to bothering you meaby would be better if you post all your unlock bootloader ideas on lg4 general forum...http://forum.xda-developers.com/g4/general where are more people to see it.
Awesomeslayerg said:
Agimax recently discovered a way into fast boot mode
Im wondering if we can get the unlock files from one of the other models and hexing out the unlock bin from imei numbers and zeros, maybe we can unlock our device by replacing them with our imei and serial number??
Click to expand...
Click to collapse
it's safe to nuke recovery and get the same result....so if anything does wrong you still have download mode!!!!
Any idea yet why the command "fastboot flashing unlock" is not recognized? It seems no commands are recognized...
thetruejay20 said:
Any idea yet why the command "fastboot flashing unlock" is not recognized? It seems no commands are recognized...
Click to expand...
Click to collapse
Its killing me not having fastboot. i have backed up all my bootloader partitions and have been skimming through trying to get my device id no. I have a random unlock.bin but that dont help none realy. All it doez is give me the hex adresse that are modified. But there diffrent on every one. From what it get is that the bootloader aint no more locked than any other. The partitions that the boooader resides in are what the issue is. they are encrypted i guess with a 256 bit security. From what i have read the unlock.bin decrypts the partitions so oem unlock can be applied. Now if im wrong or been misinformed please somone correct me.
TheMadScientist420 said:
Its killing me not having fastboot. i have backed up all my bootloader partitions and have been skimming through trying to get my device id no. I have a random unlock.bin but that dont help none realy. All it doez is give me the hex adresse that are modified. But there diffrent on every one. From what it get is that the bootloader aint no more locked than any other. The partitions that the boooader resides in are what the issue is. they are encrypted i guess with a 256 bit security. From what i have read the unlock.bin decrypts the partitions so oem unlock can be applied. Now if im wrong or been misinformed please somone correct me.
Click to expand...
Click to collapse
Yes I spent hours reading up on it yesterday, you're pretty much right on.
thetruejay20 said:
Yes I spent hours reading up on it yesterday, you're pretty much right on.
Click to expand...
Click to collapse
Now i found a tool windroid toolkit check it out i atempt to use the tool and it attemps to reboot me to fastboot i guess to attempt to get me identifier key but ofcoarse the phone just reboots. I guess i need to nuke my laf and try to see if i can get that key from my own device. My prob is im not to good with dd comands im rusty been a while. I have a backup of my laf cant find the post that shows me how to nuke and restore when im done testing is the instructions at top rite on doing it
---------- Post added at 11:58 AM ---------- Previous post was at 11:53 AM ----------
Im assuming that the toolkit prob uses a diffrent algorothim than g4 does to do unlocks but it asks what type of phone i click g4 never asks for a sub model
---------- Post added at 12:01 PM ---------- Previous post was at 11:58 AM ----------
And this is y lg needs to unlock them here we go trying extremes because of them.
---------- Post added at 12:33 PM ---------- Previous post was at 12:01 PM ----------
I guess we need to figure out how sprint lcked us out of fastboot. Thats the first step im back on it im at work rite now. So i aint got my comput near me.
TheMadScientist420 said:
I guess we need to figure out how sprint lcked us out of fastboot. Thats the first step im back on it im at work rite now. So i aint got my comput near me.
Click to expand...
Click to collapse
God speed to you man. I would love to pitch in, but I have no clie on how to crack a bootloader. Is there anything anywhere that I can learn from?
Quickdraw996 said:
God speed to you man. I would love to pitch in, but I have no clie on how to crack a bootloader. Is there anything anywhere that I can learn from?
Click to expand...
Click to collapse
I have been readin up on old lg bootloaders i use to to a lotta nes roms hack which is differ of coarse but. They do hex edit to mod them. Biggest think is craking the 256 bit encryption. Only thing i ask of any of u is read and inform me too we can hopefully figure this out. I aint no dev but anything is possible the solution is sometimes the dumbest thing rite in front of u. Were looking so deep that it might be rite in front of our faces. I. Need to get to fastboot without nuking my laf partition i need it working. Trying to figure how sprint locked us out of fast boot
TheMadScientist420 said:
I have been readin up on old lg bootloaders i use to to a lotta nes roms hack which is differ of coarse but. They do hex edit to mod them. Biggest think is craking the 256 bit encryption. Only thing i ask of any of u is read and inform me too we can hopefully figure this out. I aint no dev but anything is possible the solution is sometimes the dumbest thing rite in front of u. Were looking so deep that it might be rite in front of our faces. I. Need to get to fastboot without nuking my laf partition i need it working. Trying to figure how sprint locked us out of fast boot
Click to expand...
Click to collapse
Well I nuked my recovery partition to get into fastboot mode, but no fastboot commands are recognized in fastboot mode.
---------- Post added at 03:57 PM ---------- Previous post was at 03:52 PM ----------
TheMadScientist420 said:
Now i found a tool windroid toolkit check it out i atempt to use the tool and it attemps to reboot me to fastboot i guess to attempt to get me identifier key but ofcoarse the phone just reboots. I guess i need to nuke my laf and try to see if i can get that key from my own device. My prob is im not to good with dd comands im rusty been a while. I have a backup of my laf cant find the post that shows me how to nuke and restore when im done testing is the instructions at top rite on doing it
---------- Post added at 11:58 AM ---------- Previous post was at 11:53 AM ----------
Im assuming that the toolkit prob uses a diffrent algorothim than g4 does to do unlocks but it asks what type of phone i click g4 never asks for a sub model
---------- Post added at 12:01 PM ---------- Previous post was at 11:58 AM ----------
And this is y lg needs to unlock them here we go trying extremes because of them.
---------- Post added at 12:33 PM ---------- Previous post was at 12:01 PM ----------
I guess we need to figure out how sprint lcked us out of fastboot. Thats the first step im back on it im at work rite now. So i aint got my comput near me.
Click to expand...
Click to collapse
I checked out that windroid toolkit, and the only supported LG G4 devices is the H815. But definitely a good find!

[Help] Soft-bricked or hard-bricked?

So my N6 (64GB) has now stopped working. It is stuck in a boot loop, constantly flashing the charging icon (battery w/ lightning bolt) when plugged in. When not plugged in, it is unresponsive. I can boot into fastboot, but attempting to select any of the options from there brings me back to the boot loop. I can't boot into recovery mode, and attempting to wipe from fastboot give me the 'bootloader is locked' error. Is there anything I can do, or is RMA the only option? I am on 6.0.1, but I was experiencing similar problems on 6.0 and 5.1.1.
Locked bootloader+stock recovery (No TWRP)= RMA.
mikeprius said:
Locked bootloader+stock recovery (No TWRP)= RMA.
Click to expand...
Click to collapse
That's a shame. I RMA'd it though, and have another on the way. Thanks anyway!
Nexus are never bricked
Sent from my Nexus 6 using Tapatalk
Have you tried unlocking the bootloader and then flashing the factory image from Google via fastboot?
bryantjopplin said:
Nexus are never bricked
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Really? Or was this for the ten first posts?
---------- Post added at 08:21 AM ---------- Previous post was at 08:18 AM ----------
YungCharlemagne said:
So my N6 (64GB) has now stopped working. It is stuck in a boot loop, constantly flashing the charging icon (battery w/ lightning bolt) when plugged in. When not plugged in, it is unresponsive. I can boot into fastboot, but attempting to select any of the options from there brings me back to the boot loop. I can't boot into recovery mode, and attempting to wipe from fastboot give me the 'bootloader is locked' error. Is there anything I can do, or is RMA the only option? I am on 6.0.1, but I was experiencing similar problems on 6.0 and 5.1.1.
Click to expand...
Click to collapse
What similar problems were with 6.0 or 5.1? How stock are you? Was Enable OEM Unlocking ticked or not? Did you try fastboot oem unlock? Did you try turning it off and on again?
istperson said:
Really? Or was this for the ten first posts?
---------- Post added at 08:21 AM ---------- Previous post was at 08:18 AM ----------
What similar problems were with 6.0 or 5.1? How stock are you? Was Enable OEM Unlocking ticked or not? Did you try fastboot oem unlock? Did you try turning it off and on again?
Click to expand...
Click to collapse
Well not really but what most people do to it won't brick it. Unless he is changing stuff that most of don't even know how to. What he is describing sounds very fixable
Sent from my Nexus 6 using Tapatalk
bryantjopplin said:
Well not really but what most people do to it won't brick it. Unless he is changing stuff that most of don't even know how to. What he is describing sounds very fixable
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Then you must be new to the Nexus 6. Which is alright, but then please don't promise what you can't keep.
So, the Nexus 6 was the first Nexus that had an 'Enable OEM Unlocking' switch in the settings. And if it's unticked, and your bootloader is locked, and you can't boot your system, and you have stock recovery, then you're boned. And this is a fact.
People started bricking their Nexuses just following the instructions on Google's development site, because Google put there that the last step when going stock is locking the bootloader. Now flashing everything reverts the 'Enable OEM Unlocking' switch, but flashing everything does not guarantee that it will actually boot up. And if you lock the bootloader before checking if it boots, you've got a brick only by following Google's own basic instructions.
And no secret stuff was changed at all.
istperson said:
Then you must be new to the Nexus 6. Which is alright, but then please don't promise what you can't keep.
So, the Nexus 6 was the first Nexus that had an 'Enable OEM Unlocking' switch in the settings. And if it's unticked, and your bootloader is locked, and you can't boot your system, and you have stock recovery, then you're boned. And this is a fact.
People started bricking their Nexuses just following the instructions on Google's development site, because Google put there that the last step when going stock is locking the bootloader. Now flashing everything reverts the 'Enable OEM Unlocking' switch, but flashing everything does not guarantee that it will actually boot up. And if you lock the bootloader before checking if it boots, you've got a brick only by following Google's own basic instructions.
And no secret stuff was changed at all.
Click to expand...
Click to collapse
Does the qhsub_bulk fix not work for this? And I'm sure an sbf doesn't work either. And no I've had the n6 since last December.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 08:48 AM ---------- Previous post was at 08:47 AM ----------
bryantjopplin said:
Does the qhsub_bulk fix not work for this? And I'm sure an sbf doesn't work either. And no I've had the n6 since last December.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Also he didn't say he tried flashing stock images
Sent from my Nexus 6 using Tapatalk
bryantjopplin said:
Does the qhsub_bulk fix not work for this? And I'm sure an sbf doesn't work either. And no I've had the n6 since last December.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 08:48 AM ---------- Previous post was at 08:47 AM ----------
Also he didn't say he tried flashing stock images
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=59561963&postcount=2
ccfries said:
First, fastboot flash partition gpt.bin
Then, fastboot reboot-bootloader
Then flash the other images.
If you just bricked by downgrading bootloader, the persist and modem calibration should still be happily where it was when you started.
This won't help you if you're stuck with Allow OEM Unlock. Be careful locking on 5.1. There's accurate information elsewhere in the forum on that.
-Chris
Click to expand...
Click to collapse

Categories

Resources