Nexus 5X relocks bootloader but dosn't say NO RPMB - Nexus 5X Q&A, Help & Troubleshooting

Hello,
So I had a dead Nexus 5X and got another motherboard for it from china. I have mannaged to flash a coustom ROM but the motherboard relocks after reboot. Is there any solution to run OEM unlock every time(which wipes the phone)? It would mean I could update my OS which would be cool. Also, when I do flash some files like NanoDroid(which touches /system) it fails sometimes. Is there any soloution to this? I have seen somethings about NO RPMB online but that dosn't show up for me on the bootloader/fastboot screen. Any help would be super cool!
Thanks,
TransQuinnzel
EDIT:
Just to say, sorry if this has already been awnsered but I couldn't find anything online.

No matter what " No RPMB " on display or not, your board is most likely refurbish product by LG after notorious bootloop.
It's mean bootloader would no longer stay unlocked. Maybe LG(or the seller) fixed and deleated the message " No RPMB ".
I'm on the same boat. Unfortunately there seems to be no solution as far as I searched.
You should better send back the board to the seller and ask to replace unlockable or unlocked board.
Please read these articles. You will find what you can do with locked device and costom recovery.
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader
https://www.quora.com/What-are-the-main-differences-between-rooting-and-unlocking-a-bootloader

Related

Stuck at Boot. S-ON.

@4m8 since you are the only guy here who knows best about HTC Desire 300.
Well my friend gave his Desire 300 to me for repair. i thought its going to be easy as like 1,2,3. but guess i was wrong.
I tried several options already.
USB DEBUGGING might be off as well since my friend doesnt know about flashing or unlocking bootloaders. i cant unlock the bootloader i think.
Its S-ON. (Dont know what it actually means).
I tried going to recovery but it shows me a PHONE with A RED ''DOWNLOAD MODE ARROW'' i think recovery is corrupted?
i tried already flashing boot.img and recovery.img over FASTBOOT. but it says ''failed remote signature verify fail''. its just isnt like my sony device which says OKAY all the time lol. those two files were found on a Google drive website.
i have no other options left to revive this phone.
Help will be a very good option :good: thanks in advance.
Well i read a lot of sites which says stuck at boot. and i cant find a Official Stock firmware for this device. is it that HTC didnt released one?
That sounds really bad. So let's recap to see if I understand your situation correctly:
Phone doesn't boot, can't enter recovery and will only load the bootloader. (b-loader status is S-ON Locked)
Now unless you are able to unlock the bootloader (which you aren't as you have stated) there is no way to flash a custom recovery.
The locked bootloader will prevent it because it requires anything you want to flash to be signed by HTC.
The only way out is to flash an actual official update by HTC which afaik is not available for this device.
To make matters worse, if the phone is branded you couldn't even revive it this way because some providers, like mine, actually force HTC
to prevent those phones from flashing an official HTC update that is not branded.
But there is a bright side to your situation. Since you weren't able to unlock the bootloader your friends warenty should still be intact.
And even if this was a branded phone try to claim a replacement from the manufacturer, that way you might have the chance to get
an unbranded device in return for the trouble you and your friend had to endure. :fingers-crossed:
Sorry if I had to shatter the last piece of hope that you were clinging on to but without an unlocked bootloader the only option that
remains is getting a replacement or begging HTC to release an update or the version that is installed by default as a RUU exe
PS:
Just to be certain, you did try the factory reset option in the bootloader before giving up, right?
4m8 said:
That sounds really bad. So let's recap to see if I understand your situation correctly:
Phone doesn't boot, can't enter recovery and will only load the bootloader. (b-loader status is S-ON Locked)
Now unless you are able to unlock the bootloader (which you aren't as you have stated) there is no way to flash a custom recovery.
The locked bootloader will prevent it because it requires anything you want to flash to be signed by HTC.
The only way out is to flash an actual official update by HTC which afaik is not available for this device.
To make matters worse, if the phone is branded you couldn't even revive it this way because some providers, like mine, actually force HTC
to prevent those phones from flashing an official HTC update that is not branded.
But there is a bright side to your situation. Since you weren't able to unlock the bootloader your friends warenty should still be intact.
And even if this was a branded phone try to claim a replacement from the manufacturer, that way you might have the chance to get
an unbranded device in return for the trouble you and your friend had to endure. :fingers-crossed:
Sorry if I had to shatter the last piece of hope that you were clinging on to but without an unlocked bootloader the only option that
remains is getting a replacement or begging HTC to release an update or the version that is installed by default as a RUU exe
PS:
Just to be certain, you did try the factory reset option in the bootloader before giving up, right?
Click to expand...
Click to collapse
Yes i did. Factory reset. But still no luck.
Yes, i cant enter recovery as well.
Well it actually started ones it told me "Process System Not Responding". And on that point i knew the system files are corrupted.
My friend told me, he left the phone in deep sleep after that it didnt turned on again.
Thanks for your help @4m8 :laugh: :good: (IT ISNT MINE SO I DONT HAVE A PROBLEM) I will give this phone back to my friend.
*FACEPALM TO HTC FOR NOT RELEASING A OFFICIAL FIRMWARE*

No rpmb and impossibility to unlock my bootloader

Hi everyone. My device just came back from lg, and apparently I've got a brand new mother board. There is a problem though: my rpmb is gone (fastboot states "no rpmb" right next to the secure boot string), and I guess that is what makes my device fail to unlock its bootloader. Now, doing a little searching on the net, what I get is that really little people also encountered this problem, and ALL of them seem to have sent their device to lg from Italy (as have I). Have I got any chance to fix it? Or maybe just take it back to lg for a check? What could I possibly say to them?
Note that I know pretty well how to unlock bootloaders under normal circumstances, as I have already unlocked many nexus devices of mine in the past, so that is not the problem.
Hey there! I found a solution to get root access, here's my post on Reddit about it:
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
Hope this helps!

Weird bootloader behavior ... please help !!

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

Bootloader unlock vs bootlop warranty

Hello,
is it worth to unlock the bl under warranty (till august) or recommended to keep it locked? I want to try custom roms and kernels but if i'll get a bootlop i can't relock it.
Please post your opinion, thanks
I could be wrong on this, but there are two assumptions you're making, that I believed the opposite to be true.
The first is that Google won't warranty the device is that the bootloader is unlocked. I thought they would?
The second is that a software bootloop can't be fixed. If the device is bootlooping because of a hardware issue, there's no hope. I was under the impression that a software glitch could be repaired by putting it in a firmware download mode, and fastboot flashing the whole system?
crazyates said:
I could be wrong on this, but there are two assumptions you're making, that I believed the opposite to be true.
The first is that Google won't warranty the device is that the bootloader is unlocked. I thought they would?
The second is that a software bootloop can't be fixed. If the device is bootlooping because of a hardware issue, there's no hope. I was under the impression that a software glitch could be repaired by putting it in a firmware download mode, and fastboot flashing the whole system?
Click to expand...
Click to collapse
I talked about the hw bootloop.
My question is : can I relock the bootloader if I get a hw bootlop? I know it will stuck at google logo but maybe the bl reachable...
If you have a hardware related bootloop you may be able to re-lock the bootloader, however the phone may be completely unresponsive (mine was completely unresponsive when I had the hw related bootloop). The phone also may respond for a bit then become unresponsive again.
Did you buy your device from Google? If so, they are not concerned about an unlocked bootloader (at least the two reps I talked to when both of my devices bootlooped said that it was not a problem and both of my devices have been replaced out of warranty).
beefynick said:
If you have a hardware related bootloop you may be able to re-lock the bootloader, however the phone may be completely unresponsive (mine was completely unresponsive when I had the hw related bootloop). The phone also may respond for a bit then become unresponsive again.
Did you buy your device from Google? If so, they are not concerned about an unlocked bootloader (at least the two reps I talked to when both of my devices bootlooped said that it was not a problem and both of my devices have been replaced out of warranty).
Click to expand...
Click to collapse
No, not from the Google
In reverse If you get bootloop you cannot unlock bootloader.
Sent from my Nexus 5X using Tapatalk
Duckscreen said:
In reverse If you get bootloop you cannot unlock bootloader.
Click to expand...
Click to collapse
I want to relock it. So sad i cant use a custom rom/kernel because off the fkin bootlop failure.
I am interested in this also. I was planing to buy new Nexus 5X now, but all bootloop thing is making me consider. I am not sure if it is worth to gamble. But as I see over forum, it is not like 50% of phones bootloops. It is a lot less percent.

Nexus 5X bootloader locked, PIN locked, & bootloop

Hello,
I'm in a rather peculiar situation. I bought a Nexus 5X from eBay recently (I know) which was advertised as having the common bootloop issue, of which I saw there seems to be a fix for. After receiving the phone I found that not only does it bootloop, but the bootloader is still locked and the previous owner has set up the phone and used a PIN lock on the lockscreen, leaving me unable to get into the settings to enable Developer settings and unlock the bootloader. Does anyone know of any kind of fix for this? Just to reiterate, I cannot flash any stock rom, and there is no custom recovery on the device. I am not new to unlocking bootloaders and flashing custom firmware, and I have contacted the previous owner to no avail. Any help in this issue would be greatly appreciated.
I have searched the forums but as my situation is compounded of multiple problems (locked BL, no custom recovery and PIN lock) I feel like I have hit a dead end.
I am with ya
I have the exact situation i would love to know if you have figured it out. i have two of them as a package deal from ebay. Both 5x.
advertised as bootloop. wont go past the google screen.. one them i actually got to fire up but then ran into the pin thing...
Can you get in fastboot mode ? If so, you can try flashing a custom recovery

Categories

Resources