Hi guys I got the lollipop OTA for my nexus ( completely stock), never tinkered with it and the OTA installed but now its stuck on "google" screen and constantly bootloops. I have done some reading and I tried to unlock bootloader via Wugfresh toolkit and normal fastboot oem method but no avail, it gets stuck on the "yes" option.
Basically I have a locked bootloader which fails to unlock, and nexus stuck in google logo, any guidance will be much appreciated. Plz point me towards the right direction. :crying:
Try to unlock the bootloader from adb with OEM unlock command. The steps are posted above the factory images on Google's dev site.
yeah I tried that and tablet gets stuck on the yes option at unlock bootloader screen and nothing happens for 20 minutes , i have to restart it. I've read around and it seems like my emmc might have corrupted. Any pointers?
Nxpx said:
yeah I tried that and tablet gets stuck on the yes option at unlock bootloader screen and nothing happens for 20 minutes , i have to restart it. I've read around and it seems like my emmc might have corrupted. Any pointers?
Click to expand...
Click to collapse
Well I can only think of one thing. Buy a new nexus. There aren't any listings for the Wi-Fi version and the LTE on Swappa. However there is some other devices on Swappa.
Related
Hello all
I recently unlocked my phone and installed the viper ROM using twrp. It worked successfully. I then re-locked it to get the fingerprint scanner functionality back. After that I tried to unlock it again to add some of the audio mods. At this point my phone would not boot all the way. I was stuck between the bootloader and download mode after running the unlock command. This after only having the phone 5 days..lol. I managed to get the stock ruu from the htc site and reflashed it back to stock. It now works except I cant unlock it again. I am getting the 35 RU_PARTITION_NOT_SUPPORT unlocker error message after uploading the Unlock_code.bin. Has anyone seen this and/or figured it out? My apologies if this is the wrong area to post this. I am new here. Thanks for the help!
Edit:
Tried multiple unlock keys from HTC
Tried factory reset
Booting into recovery phone image comes up with red warning icon in it and nothing happens. Need to power down and restart. Seems the recovery partition is possibly hosed.
Dissectional said:
Hello all
I recently unlocked my phone and installed the viper ROM using twrp. It worked successfully. I then re-locked it to get the fingerprint scanner functionality back. After that I tried to unlock it again to add some of the audio mods. At this point my phone would not boot all the way. I was stuck between the bootloader and download mode after running the unlock command. This after only having the phone 5 days..lol. I managed to get the stock ruu from the htc site and reflashed it back to stock. It now works except I cant unlock it again. I am getting the 35 RU_PARTITION_NOT_SUPPORT unlocker error message after uploading the Unlock_code.bin. Has anyone seen this and/or figured it out? My apologies if this is the wrong area to post this. I am new here. Thanks for the help!
Click to expand...
Click to collapse
tried requesting for new unlock key from htc dev?
also you don't need to relock for enabling fingerprint scanner...
SacredDeviL666 said:
tried requesting for new unlock key from htc dev?
also you don't need to relock for enabling fingerprint scanner...
Click to expand...
Click to collapse
Yes. I tried a new unlock key. I even contacted htc support but they didnt want to help seeing as how my phone now works. As for the fingerprint scanner. I saw no options for it in viper and from what I searched a few sites said the fingerprint scanner was disabled in unlocked mode. But I will keep that in mind if I ever get past this. I should add also..my phone doesnt say LOCKED or UNLOCKED either. It says RELOCKED on top. Never saw that before either.
Thanks for the reply!
Dissectional said:
Yes. I tried a new unlock key. I even contacted htc support but they didnt want to help seeing as how my phone now works. As for the fingerprint scanner. I saw no options for it in viper and from what I searched a few sites said the fingerprint scanner was disabled in unlocked mode. But I will keep that in mind if I ever get past this. I should add also..my phone doesnt say LOCKED or UNLOCKED either. It says RELOCKED on top. Never saw that before either.
Thanks for the reply!
Click to expand...
Click to collapse
I haven't heard of the fingerprint scanner not working after the HTC One Max disabled it with a unlocked bootloader.
The fingerprint scanner on the 10 will work just fine with a unlocked bootloader, you should beable to unlock again to get rid of the relock if you want too
afuller42 said:
I haven't heard of the fingerprint scanner not working after the HTC One Max disabled it with a unlocked bootloader.
The fingerprint scanner on the 10 will work just fine with a unlocked bootloader, you should beable to unlock again to get rid of the relock if you want too
Click to expand...
Click to collapse
You may be right about the fingerprint scanner. I will look into that when I get it unlocked. That is the main goal right now.
If you are s-OFF the phone will show as "s-off, locked" but still, in fact, be unlocked.
the command to lock and unlock will not work.
I was confused to but when i checked the s-off thread i saw that it will ask if it should be "s-off unlocked or "s-off locked" and recomended Locked, but had no difference other then visual.
---------- Post added at 08:31 AM ---------- Previous post was at 08:30 AM ----------
And btw, lock status should not affect the fingerprint scanner.
Confirmed it doesn't I am s-0ff and unlocked, twrp and custom rom. Fingerprint working 100%
the exclamation on booting to recovery just indicates that you are on stock recovery...
try the steps here for recovery flashing... and unlocking again... if it might help... http://forum.xda-developers.com/showpost.php?p=66713447&postcount=1
You could try contacting Scotty, might have a way like on previous devices to lock/unlock your bootloader without htcdev.com once S-OFF (DO NOT use the codes for M7 M8 or M9)
http://forum.xda-developers.com/showthread.php?t=2470340
Shouldn't this work?
fastboot oem unlock
Are your developer options enabled right now. And did you check the box to allow bootloader unlock again?
Sent from my HTC 10 using XDA Labs
Some luck
Well.. First off I must say thanks for the reply's so far. Secondly I must apollogize... I have things working (unlocked, rooted and runing viper one) but my solution was a rather odd one.
After trying a few things suggested I went back and just tried reflashing the Unlock.bin. For whatever reason it worked this time after numerous fails mostly involving the dreaded error message found in the title of the post. I then tried to flash twrp but all attempts yielded the error: FAILED (remote: cannot flash this partition in s-on state. Which sucks because I cant get S-off without being root that I am aware of. For whatever reason I set up the tools (fastboot and adb) in another folder and voila! it worked! I am assuming this was also the issue with the Unlock.bin as well as I had switched to another folder at that time as well. Any ideas why that is? Just curious.
Well I am off to enjoy my tweaking (my phone that is)
Happy modding! And thanks for the help!
Dissectional said:
Well.. First off I must say thanks for the reply's so far. Secondly I must apollogize... I have things working (unlocked, rooted and runing viper one) but my solution was a rather odd one.
After trying a few things suggested I went back and just tried reflashing the Unlock.bin. For whatever reason it worked this time after numerous fails mostly involving the dreaded error message found in the title of the post. I then tried to flash twrp but all attempts yielded the error: FAILED (remote: cannot flash this partition in s-on state. Which sucks because I cant get S-off without being root that I am aware of. For whatever reason I set up the tools (fastboot and adb) in another folder and voila! it worked! I am assuming this was also the issue with the Unlock.bin as well as I had switched to another folder at that time as well. Any ideas why that is? Just curious.
Well I am off to enjoy my tweaking (my phone that is)
Happy modding! And thanks for the help!
Click to expand...
Click to collapse
glad its sorted for you and back to flashaholic mode
Dissectional said:
Well.. First off I must say thanks for the reply's so far. Secondly I must apollogize... I have things working (unlocked, rooted and runing viper one) but my solution was a rather odd one.
After trying a few things suggested I went back and just tried reflashing the Unlock.bin. For whatever reason it worked this time after numerous fails mostly involving the dreaded error message found in the title of the post. I then tried to flash twrp but all attempts yielded the error: FAILED (remote: cannot flash this partition in s-on state. Which sucks because I cant get S-off without being root that I am aware of. For whatever reason I set up the tools (fastboot and adb) in another folder and voila! it worked! I am assuming this was also the issue with the Unlock.bin as well as I had switched to another folder at that time as well. Any ideas why that is? Just curious.
Well I am off to enjoy my tweaking (my phone that is)
Happy modding! And thanks for the help!
Click to expand...
Click to collapse
Sounds like your Environmental PATH is set to just that one folder.
Windows?
There's some good threads here on XDA,
http://forum.xda-developers.com/showthread.php?t=1161776
Glad you got it working though!
Hello guys am basically a Noob when it comes to the new android 6.0+ security system that google included which changed the bootloader unlocking and rooting process a lil bit from the standert ( fastboot oem unlock ... fastboot flash twrp ... flash super su and voila )
let's get to my probleme with my nexus 5x when i unlocked the bootloader with the tool the device has to reboot but everytime i reboot i have to unlock my bootloader again the root works fine but the bootloader keeps getting locked everytime ... problem is that i messed with the boot img in order to disable forced encryption and now i can't flash stock because during the flashing the bootloader has to reboot and gets locked which make the flashing fails ... am on android nougat 7.0 if that matter and if someone have the 6.0.1 (mtc20k) boot image for noforce encrypte please share with me and thanks
You can update manually by flashing the different parts separately using fastboot commands. That way you can skip rebooting after flashing bootloadet
Skickat från min Nexus 5X via Tapatalk
I have the same problem. Bootloader gets relocked every time i reboot. Could not install cm14.1, i just get i bootloop (tried with latest twrp and vendor). Went back to stock with the seperate fastboot commands. It works but really annoying that the bootloader wont stay locked. It worked before i sent the phone to service (emmc problem) and got the motherboard changed. Is there a problem with the bootloader or is it a hardware problem?
Sounds like a HW problem, RMA it again.
RusherDude said:
Sounds like a HW problem, RMA it again.
Click to expand...
Click to collapse
Thanks!
Yeah thats what im thinking too. But what do i claim as the issue? Is a non unlockable bootloader a warranty issue? Bought it unlocked from a store.
frukten said:
Thanks!
Yeah thats what im thinking too. But what do i claim as the issue? Is a non unlockable bootloader a warranty issue? Bought it unlocked from a store.
Click to expand...
Click to collapse
Ask Google (you can open up a chat with them for example on https://support.google.com/nexus/answer/4582729?hl=en&ref_topic=6023296#contact=1 or other links), for me it's a clear issue, you have the right to unlock the bootloader, however not sure how to demonstrate a problem if you bought it on a store...
All phones that come back from service do so in that state. Seems it's a decision from LG. If you go to bootloader you'll probably see that is says "no rpmb" right after secure boot. This is what is causing the issue, from what I know it is because a certain portion is not flashed on the motherboard replacement
The same happend to me, e-mailed the service center asking why they did this but they never reply
Skickat från min Nexus 5X via Tapatalk
So basically, I have a Verizon note 4 with permanent root. I bought it second hand and it came with permanent root, but the problem is that I have no idea if it has an unlocked bootloader or not . It doesn't have any custom recovery on it aswell. But then it gets me to question how the heck did it get a Permanent ROOT without getting an unlocked bootloader. Oh and i also don't get shown a verizon logo when i reboot my device, only a samsung logo. And i live in South Asia btw, and can run a local
sim with 3g on it no problem as well....
Also worth mentioning is that on "About Device" in "Settings", it says SM-910F...but when i go to fastboot mode, it says SM-910V, and when i connect it to computer, it also says verizon model. Anyways, the real problem is finding out if my phone has bootloader or not. (READ BELOW ASWELL)
Any suggestions plez
PS: I tried to put a code in the dialer, something like *#*#7432XXXX*#*# (tried a lot of diff. codes in dialers aswell). PLUS, I also tried finding if i had an unlocked bootloader from adb and fast boot where u put this command in; "fastboot oem device-info" something like that, but I cant get "fastboot devices" to work (it doesn't give any result even with proper usb drivers and while in fastboot menu from phone) :crying: plez halp me....
MajorMcNugget said:
So basically, I have a Verizon note 4 with permanent root. I bought it second hand and it came with permanent root, but the problem is that I have no idea if it has an unlocked bootloader or not . It doesn't have any custom recovery on it aswell. But then it gets me to question how the heck did it get a Permanent ROOT without getting an unlocked bootloader. Oh and i also don't get shown a verizon logo when i reboot my device, only a samsung logo. And i live in South Asia btw, and can run a local
sim with 3g on it no problem as well....
Also worth mentioning is that on "About Device" in "Settings", it says SM-910F...but when i go to fastboot mode, it says SM-910V, and when i connect it to computer, it also says verizon model. Anyways, the real problem is finding out if my phone has bootloader or not. (READ BELOW ASWELL)
Any suggestions plez
PS: I tried to put a code in the dialer, something like *#*#7432XXXX*#*# (tried a lot of diff. codes in dialers aswell). PLUS, I also tried finding if i had an unlocked bootloader from adb and fast boot where u put this command in; "fastboot oem device-info" something like that, but I cant get "fastboot devices" to work (it doesn't give any result even with proper usb drivers and while in fastboot menu from phone) :crying: plez halp me....
Click to expand...
Click to collapse
Put it into download mode and see if it says, mode: Developer. If it does your bootloader is unlocked
dhplap said:
Put it into download mode and see if it says, mode: Developer. If it does your bootloader is unlocked
Click to expand...
Click to collapse
Well it doesn't say so ... sadly.
Anyways, I'm still wondering how the heck did someone install permanent root without unlocking this Verizon??? Like you have to do temporary root and then you unlock bootloader, and then you do perm root... how does one bypass that?
Ok first let me start off by saying that I'm an idiot and did something really stupid. I was rooted with an unlocked bootloader on Android 8.1 preview was trying to return to stock and stupidly I locked the bootloader before flashing a factory image. Now I'm stuck on the bootloader screen, if I try to boot it flashes the white screen with the Google logo for a split second then starts going into bootloops. When I tried fastboot oem unlock it says "remote oem unlock not allowed". Does anyone know if there is a way to recover my phone or did I make a very expensive mistake?
bbacon said:
Ok first let me start off by saying that I'm an idiot and did something really stupid. I was rooted with an unlocked bootloader on Android 8.1 preview was trying to return to stock and stupidly I locked the bootloader before flashing a factory image. Now I'm stuck on the bootloader screen, if I try to boot it flashes the white screen with the Google logo for a split second then starts going into bootloops. When I tried fastboot oem unlock it says "remote oem unlock not allowed". Does anyone know if there is a way to recover my phone or did I make a very expensive mistake?
Click to expand...
Click to collapse
From what I know across all devices, a very expensive mistake. :/.
For future reference, yet again, for everyone. PLEASE READ. If you want to relock the bootloader, only do so after you actually boot into the new OS.
Reboot into recovery and factory wipe it. That is your only chance, and it's slim.
RMA
Sideload ota through your recovery.
Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6
remialfa said:
Hello guys I have H815 and I can't proceed with unlocking bootloader cause my phone cannot boot into bootloader/fastboot mode. I'm not newbie, but with this phone everything goes ****ing different than in instruction.
I the instruction there is adb reboot bootloader. Of course my phone is seen in adb mode but after this command it just reboot to system. I tried also key combinations with no luck...
What to do?
My system is android 6
Click to expand...
Click to collapse
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode
auceto63 said:
Hi,
I'm the same...
looking for solution I found this on Youtube:
Pratically, you have to press vol up while connect USB on PC....
I haven't the G4 with my today and so I cannot test if this is a valid mode...
If you do this, let me know if you can enter in fastboot mode
Click to expand...
Click to collapse
I did that and yeah it entered this mode but it's not valid bootloader/fastboot mode. It's some service mode to update firmware. Anyway it's not visible in pc as a normal fastboot and I cannot proceed further with unlocking bootloader...
Edit: it's download mode... So as I said it's not fastboot mode.
Anyone can help?
Seriously nobody? I thought this phone has good community and support...
I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:
charith262 said:
I'm facing the exact same problem with my H810 on 6.0. Sick of not being able to root atleast.
Seriously hasn't anyone on earth found a way to boot this **** in fastboot? I mean there are a number of tutorials but everything goes different as F*** with this thing. Hope someone will update with good news. :fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
You can check out UsU. That is an unofficial bootloader unlock
ThePiGuy said:
You can check out UsU. That is an unofficial bootloader unlock
Click to expand...
Click to collapse
Thanks yeah I checked but that's for ARB<=2 devices. I forgot to mention earlier this godforsaken thing is ARB3.
I have an H811 (T-Mo) running firmware H81120p, ARB3. Doesn't seem to be much that can be done with it as far as rooting. It also has no stock recovery, only boots to system.
you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
if you use bank apps, install magisk before installing rom, do not get SU
samadee3 said:
you did follow this official guide right? it unlocked mine after a few angry moments
http://developer.lge.com/resource/mobile/RetrieveBootloader.dev
use minimal ADB https://forum.xda-developers.com/showthread.php?t=2317790
Only way to boot twrp later is to use fastboot with ADB, recovery with buttons doesn't work.
if the device wont boot a rom use adb to get back in recovery.
Click to expand...
Click to collapse
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.
SofaSpud said:
Only problem is that the info linked to above applies to ONE G4 variant only - the H815 international model. The rest of us are SOL. The bootloader on US carrier G4 - AT&T, T-Mo, VzW, etc (most later firmware revisions for G3 as well) models has been nailed down. The only exception is a G4 with ARB <= 2 can be hacked with UsU in order to root it and install a custom recovery.
Click to expand...
Click to collapse
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device
ThePiGuy said:
Tmo is very easy
Go to dev options and enable adb
Then run "adb reboot bootloader"
Once there, run "fastboot oem unlock" and voila, you have an officially unlocked bootloader with no restrictions related to UsU
Please be aware the above will factory reset your device
Click to expand...
Click to collapse
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Sent from my SAMSUNG-SM-G935A using Tapatalk
SofaSpud said:
Do you know anyone who has done it with H81120o or later? I've seen posts for two yrs about doing it that way, but I don't remember reading about it being done on 20o or later.
Click to expand...
Click to collapse
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too
ThePiGuy said:
Why v20o
Remember, this has nothing to do with UsU and therefore ARB etc doesn't matter
Edit: ps there are loads of H811 users in my Lineage thread and the other ROMs too
Click to expand...
Click to collapse
Got it. Guess that it makes sense. ARB prevents rolling back to earlier release than 20o, I'm ok. Will try the BL unlock today then.
Sent from my SAMSUNG-SM-G935A using Tapatalk
I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.
Florimer said:
I actually managed to get my LG V20 F800L into same situation after messing up my rooting process.
First i was stuck at logo and factory reset did nothing. Bootloader was working then.
Then i downloaded new firmware through "Download Mode", and after that i lost access to bootloader.
I know the phone model is different, but process seems to be very similar for all LG devices.
Trying to troubleshoot that atm, if i'll have results i'll post them here.
P.S. I know original poster long left (probably after throwing phone into a grinder), but maybe for someone with same problem as us in the future the info will be useful.
Click to expand...
Click to collapse
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.
Florimer said:
Ok, now i have to reply to my own post, since i believe i understand now something important:
LG phones usually dont have bootloader open to access. Until you use some exploits to do so.
I did not know that at the time of writing that reply.
Click to expand...
Click to collapse
Do you have more details about this? I seem to be in a similar situation than you and I'm struggling to make it work.