Database Users

Can't Re-Unlock the Bootloader

I read through the similar thread from yesterday, but this is a different issue...
I had unlocked, installed TWRP, and had been running a custom ROM (BadBoyz 1.2). This morning I re-locked so I could flash the updated firmware (v1.80) and now I am unable to re-unlock.
When I issue the command fastboot flash unlocktoken Unlock_code.bin, it works without errors, and the phone goes to the "Are you sure you want to unlock your bootloader?" screen.
However, at that screen, the volume buttons do nothing. I can't select yes OR no, it just sits there. Eventually it times out and just shows the battery charging on a black screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When I flashed the firmware, it removed TWRP, and with a locked bootloader, I can't re-flash it.
I was able to get a fully stock rom up and running, so I'm not in brickville anymore (had a few hours of panic earlier today), and I've been able to confirm that the OEM Unlock option is checked. I've even unchecked and re-checked to be sure. Everything works except the ability to confirm my choice and move on. I'm kind of afraid that it's a glitch in the new firmware, at this point...
Anyone got any ideas?
Thanks!!

deleted

So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app

have you tried running RUU.exe? i took that route and was able to unlock my bootloader again, flash twrp and upgrade to bb 2.0 with no problems

I had the same problem and had to flash a stock rom back on the phone before the unlocker would work.

I figured it out! I can't explain WHY it worked, but it worked...
I had re-flashed several times using the official RUU, and the results never changed...
Then yesterday I went through a mental checklist of what was different when I unlocked the first time... and the only thing, was that I hadn't put my SD Card in the phone yet when I unlocked the first time. So I went through the motions again to verify that it still didn't work, and it didn't. Then I ejected the SD Card and tried it - and BOOM, I was able to unlock!
The only thing I can think of is that the SD Card did have the Firmware .zip on it, which the phone auto-detected and asked if I wanted to install... even though I said no. As soon as I tried it without the card, it worked like it always had, I'm back to unlocked, and back to the custom ROM I had been enjoying so much...
Thanks for the tips, everyone, and I hope this thread helps someone else who finds themselves in the same boat!

scottspa74 said:
So, it removed TWRP and replaced the stock recovery? And now you can't reinstall TWRP because bootloader is locked? Is that where you're at?
Sent from my 2PS64 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, that is EXACTLY where I was at. However, finally found the way out of the mess.. (see above post)

Last hope to rescue Nexus 6p stuck in Bootloop of death(BLOD)

As you know lots of devices are facing this issue where the device is in bootloop and the bootloader is locked.
I have last hope that if anyone can help me with any one of the solution, I can rescue my nexus 6p.
Device info:
Rom: Android 7.1.1 stock rom
Bootloader: Locked (OEM unlocking not enabled in developer options)
Warranty: Ended on 14th feb 2017
Huawei said motherboard will cost Rs.28000 i.e $400 approx.
I can boot into bootloader menu and recovery as well.
I tried sideloading the OTA zips from google, it flashes successfully but still bootloops.
Note: My device didn't reboot after 90 seconds when it was in bootloader menu also I as I can sideload OTAs successfully, I don't really think that its an hardware issue.
I have 2 options as my last resort.
1. I've read that if you unenroll from Android BETA program, you get an OTA update which wipes your entire device.
BUT for this I must be able to boot which I cannot.
HELP: Can anyone provide me the BETA unenrolled OTA link so that I can try sideloading it?
2. I've also read that we can flash all partitions of nexus 6p in EDL mode refer:https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Files included in zip are attached below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
HELP: As per thread only way to boot into EDL mode is by ADB which I can't access as my phone doesn't boot up.
Can anyone help me with booting my device into EDL mode so that I can try flashing this file.
* I CAN'T AFFORD NEW MOTHERBOARD, I'm just a student.

aakash dabrase said:
I have 2 options as my last resort..
Click to expand...
Click to collapse
Sorry, but your only option is a new phone.

v12xke said:
Sorry, but your only option is a new phone.
Click to expand...
Click to collapse
me i have the same prob but my phone unloked and i can enter in fastboot mode i have chance to rescue my phone

leroilion02 said:
me i have the same prob but my phone unloked and i can enter in fastboot mode i have chance to rescue my phone
Click to expand...
Click to collapse
You are hijacking another thread. Back in the first thread you started on this same topic: https://forum.xda-developers.com/member.php?u=5737579 Enter those commands in fastboot and capture the resulting text. Please post the results in your original post. Not here.

v12xke said:
You are hijacking another thread. Back in the first thread you started on this same topic: https://forum.xda-developers.com/member.php?u=5737579 Enter those commands in fastboot and capture the resulting text. Please post the results in your original post. Not here.
Click to expand...
Click to collapse
please bro can you tell me what i can do step by step

Have you tried to wipe data and cache I recovery?

leroilion02 said:
please bro can you tell me what i can do step by step
Click to expand...
Click to collapse
I already did 3 days ago in the first thread you started on this:
https://forum.xda-developers.com/showpost.php?p=71699404&postcount=15

I have the same problem with my Nexus 6p. I have switched to an iphone 7.
Is Google a serious organization to let so many users suffer because of their problems? I mean this really HAS to be seriously unethical company to do this. As for Huawei, well- we should have known and expected such behavior. At the end of the day it is a Chinese brand... so it needs to maintain its low levels of reputation to be worthy of its fine name.

Unable to flash stock rom via Odin from custom ROM (Renovate ICE)

Hello,
I have on my S8 (G950F) Renovate ROM for almost one year, I will switch to new phone soon and I want give my current phone to my sister, so I wanted flash stock firmware and unroot device. Unfortunatelly I am not able do it. I tried manage it on two laptops, I use originanal USB-C cable, I tried few different last firmware from https://www.sammobile.com/firmwares/, and this one as well- https://forum.xda-developers.com/galaxy-s8/development/rom-galaxy-s8-t3749171.
Odin software is 3.13.1 and drivers on my laptops should be okay because I am able flash TWRP. But when I tried flash stock firmware, I am getting some errors:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On screen on phone in Downlading mode after failed flash is showing:
sw rev. check fail device: 4. binary: 1
or
sw rev. check fail device 3 binary 2
Everything what I can do is flash custom ROMS from TWRP but I really want go back to Stock ROM so only Odin can do it I guess.
Thank you so much for your tips and help.
Veronika

Just a hint:
a had a similar behaviour on my Samsung tab S2.
The only thing that helped was flashing an really old stock ROM, specifically that one which was on the device at the time i bought it.
Maybe you could try it with an 7.0 Stock ROM.
You can get them from Here: https://updato.com/firmware-archive-select-model?q=SM-G950F&rpp=15&order=date&dir=asc&exact=1

Thank you.
I already tried flash custom Nougat ROM but I got same errors in Odin later.
https://forum.xda-developers.com/galaxy-s8/development/rom-batstock-rom-v1-0-t3598853.
So now I will try download first stock Nougat ROM from my carrier on sammobile site

VeronikaV said:
Thank you.
I already tried flash custom Nougat ROM but I got same errors in Odin later.
https://forum.xda-developers.com/galaxy-s8/development/rom-batstock-rom-v1-0-t3598853.
So now I will try download first stock Nougat ROM from my carrier on sammobile site
Click to expand...
Click to collapse
Your issue is you are trying to flash older firmware (bootloader) version than what is on your phone. You will need the latest version with boot loader version 4
The firmware version should look like this G950FXXU4CRI5.

Thanks!
So this one should help me?
https://forum.xda-developers.com/galaxy-s8/how-to/g950fxxu4cri5-oreo-super-slow-mo-ar-t3844015

VeronikaV said:
Thanks!
So this one should help me?
https://forum.xda-developers.com/galaxy-s8/how-to/g950fxxu4cri5-oreo-super-slow-mo-ar-t3844015
Click to expand...
Click to collapse
As long as it is for your region ( and carrier ). If not sure I would.use a program called samfirm. At the moment I am having issues pasting links so you will have to do a search or use sammobil or updato.

Done, firmware from link was correct and I was able flash it.
Thank you so much for your help.

There is a simple reason for this. If you came from TWRP as "reboot to download", this creates the problem. Turn off the phone. Go to download mode with Vol_Down+Bixby+Power and then press Vol_Up button. When I enter download mode like this, it flashes without any problems.

I have some t350's with issues recovery/MDM/black screen and bootloops

I recently found at the dumps a box of t350's 6/18 didnt like combination flashing the mdm away/new firmware install. 3 failed the same way while putting on newest firmware with odin now they say mdm mode in odin again and i have no debug access. 1 black screens in bootloader and when booting no debug access mdm mode in odin again. BUT ! I have 1 with debug access and see it in ADB BUT it fails to install due to signature verifcation of the ROM's I've tried. I think the later is savable EZ just need a a little help getting TWRP onto it I guess and I'm good. I'll worry about the others later but any ideas ? my brain hurts from trying cables/roms/adb versions lol

Maybe the rom is incorrect have you checked the region and model number etc?

Kenora_I said:
Maybe the rom is incorrect have you checked the region and model number etc?
Click to expand...
Click to collapse
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time

TDIfrogman said:
the issue is the MDM mode seems like, it fails to write. only time i every got them to flash was after the combination flash the download menu popped up very slow after it was working hard to explain..... i have 7.1.1 on all the working one's which seem finebut i ****ed up i shouldve TWRP them first, one of them i successfully did get twrp on and lineage after the fact and i tried again with now another boot looping tablet SMH. idk what i did to do it the first time
Click to expand...
Click to collapse
no matter what i write to it twrp any firmware just fails like it did when it was mdm locked

Could you provide ODIN logs?

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

it shows mdm locked and the odin log reflects that BUT they where unlocked at some point im, afraid to try and flash the other and they'll end up like this one

TDIfrogman said:
View attachment 5364601
Click to expand...
Click to collapse
They might have NAND flash erros because they arent able to write to it.

Kenora_I said:
They might have NAND flash erros because they arent able to write to it.
Click to expand...
Click to collapse
hmmmm how can i fix it ?

It could be hardware issue, I'm not sure how to fix hardware issues. Thats probably the reason they were all together in a box.

no they where in a box because they came from a school and they didn't take knox off, there was 1000+ of them I just grabbed a tray full they have these crazy polycarbonate cases on them too with security screws. they all worked until i flashed knox away with varying results 12/18 working fine 18 worked prior but in knox

Oh that info is noted.
May I help you later. Its pretty late and I have to get off.
Ill help in the mornin

Question Help……Is there still warranty for brick the phone

This machine got bricked by me… Stuck at fast boot not turning on

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Purchase, Root, Use, Brick, Contact For Support, Just in one day……

how did you brick it?

Just wait for the factory or full OTA image to unbrick

Qiyue_ said:
Purchase, Root, Use, Brick, Contact For Support, Just in one day……
Click to expand...
Click to collapse
I warn you to wait slowly with your root without test another things.
You are not brick, you must only reinstall rom, you can always access fastboot/Bootloader
Have you tried to access to Recovery ?

Me also bricked my nothing phone 1 but it's bootloader is locked
I have only access to fastboot
When i try to boot in recovery or system it's boot into fastboot
I was trying to install dynamic system update from developer option. While phone was installing dsu phone has turned off for rebooting and never turned on again.
How can i get full rom for nothing os and flash tool

Pho3nX said:
I warn you to wait slowly with your root without test another things.
You are not brick, you must only reinstall rom, you can always access fastboot/Bootloader
Have you tried to access to Recovery ?
Click to expand...
Click to collapse
I tried to use fastbootd for accessing system_b but after once I tried I can’t open this mode again, same as recovery.

Qiyue_ said:
I tried to use fastbootd for accessing system_b but after once I tried I can’t open this mode again, same as recovery.
Click to expand...
Click to collapse
And right now it’s just bootloader, the warn of the bootloader unlock sigh didn’t even come up

Displax said:
Just wait for the factory or full OTA image to unbrick
Click to expand...
Click to collapse
You also need the unbricking tool like MsmDownloadTool to flash full rom right? Having the rom file isn't enough.

Displax said:
Just wait for the factory or full OTA image to unbrick
Click to expand...
Click to collapse
Pheggas said:
You also need the unbricking tool like MsmDownloadTool to flash full rom right? Having the rom file isn't enough.
Click to expand...
Click to collapse
You will find the latest Full Nothing OS 1.1.0 HERE
@Displax , I don't know if MsmDownloadTools is operationnal for the Phone(1) because it mainly concerns all devices produced by the BBK Electronics consortium.
I don't know if someone want to try, you will find here the link to MsmDownloadTools