This an incredibly easy way to OEM unlock your G4.
**NOTE** This software feature might not be avaliable on the carrier based versions of the G4 like, Verizon, Sprint ect.
If you have a preview unit or carrier unlocked version of the G4 then this will be very simple.
1. Enable Developer Settings, going into the software version info in the settings and then clicking on the build number 5 times.
2. Go back to the settings and you'll find the developer settings tab at the bottom by about phone, if you setting menu is in list view.
3. Go into the developer settings and you'll see Enable OEM unlock right under Enable Bluetooth HCI snoop log near the top.
4. When you click on OEM unlock it will prompt you that device protection features will not work while this is enabled.
5. Click Yes and reboot the phone.
6. Now you can OEM Unlock your G4!
Cm9aphla said:
This an incredibly easy way to OEM unlock your G4.
**NOTE** This software feature might not be avaliable on the carrier based versions of the G4 like, Verizon, Sprint ect.
If you have a preview unit or carrier unlocked version of the G4 then this will be very simple.
1. Enable Developer Settings, going into the software version info in the settings and then clicking on the build number 5 times.
2. Go back to the settings and you'll find the developer settings tab at the bottom by about phone, if you setting menu is in list view.
3. Go into the developer settings and you'll see Enable OEM unlock right under Enable Bluetooth HCI snoop log near the top.
4. When you click on OEM unlock it will prompt you that device protection features will not work while this is enabled.
5. Click Yes and reboot the phone.
6. Now your OEM unlocked!
Click to expand...
Click to collapse
What will change after this?
danromania said:
What will change after this?
Click to expand...
Click to collapse
This will Unlock the Boot loader on the G4, which will make rooting very easy.
Cm9aphla said:
This will Unlock the Boot loader on the G4, which will make rooting very easy.
Click to expand...
Click to collapse
Hello
You've tried this ? It works ? What's your carrier phone ?
Cm9aphla said:
This will Unlock the Boot loader on the G4, which will make rooting very easy.
Click to expand...
Click to collapse
How to root ?!
scumpicule said:
Hello
You've tried this ? It works ? What's your carrier phone ?
Click to expand...
Click to collapse
I use AT&T but my model is a preview unit AKA the Korean Model.
hoangnova said:
How to root ?!
Click to expand...
Click to collapse
You probably still needs to wait for someone to write a custom recovery for the phone and use it to flash SuperSU. Shouldn't take very long though as long as the phone is unlocked.
That is very nice from LG side to easy unlock bootloader, it will really easy to mods, custom recoveries, roms etc
Looks cool times for G4 development theard
shouldn't it be possible to integrate supersu to the kernel? in ramdisk or wherever chainfire said it was going to be put in custom kernels
Cm9aphla said:
This an incredibly easy way to OEM unlock your G4.
**NOTE** This software feature might not be avaliable on the carrier based versions of the G4 like, Verizon, Sprint ect.
If you have a preview unit or carrier unlocked version of the G4 then this will be very simple.
1. Enable Developer Settings, going into the software version info in the settings and then clicking on the build number 5 times.
2. Go back to the settings and you'll find the developer settings tab at the bottom by about phone, if you setting menu is in list view.
3. Go into the developer settings and you'll see Enable OEM unlock right under Enable Bluetooth HCI snoop log near the top.
4. When you click on OEM unlock it will prompt you that device protection features will not work while this is enabled.
5. Click Yes and reboot the phone.
6. Now your OEM unlocked!
Click to expand...
Click to collapse
Ok, done!!! Now how to I enter fastboot mode?
Works on tmobile?
gsxcorey said:
Works on tmobile?
Click to expand...
Click to collapse
Yes. But now what can I do with this at this point?
{
"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"
}
MicroMod777 said:
Yes. But now what can I do with this at this point?
Click to expand...
Click to collapse
In fastboot you can push supersu. Then dowload twrp.img flash it. Then you got root with custom recovery. Boom, bam, bing.
dontbeweakvato said:
In fastboot you can push supersu. Then dowload twrp.img flash it. Then you got root with custom recovery. Boom, bam, bing.
Click to expand...
Click to collapse
Ok, how do I get to fastboot? adb reboot bootloader doesn't work, just reboots device.
From what I understand. And I may be wrong. This doesn't actually unlock the bootloader, it just allows it to be unlocked.
Until LG release the unlock.bin or someone finds a workaround it won't work.
There's also no TWRP for this device yet.
Coming from a Nexus 5 which was easy as pie it's taking me some getting my head around.
That said it's early days and in sure we'll get root soon enough.
MicroMod777 said:
Ok, how do I get to fastboot? adb reboot bootloader doesn't work, just reboots device.
Click to expand...
Click to collapse
With device off hold down power and vol down, then plug in usb cable while connect to adb terminal. But i wouldn't try this unless you know what your doing, or if your rich and have another device when you brick this one...... Its happened already.
MicroMod777 said:
Ok, how do I get to fastboot? adb reboot bootloader doesn't work, just reboots device.
Click to expand...
Click to collapse
for me on H815 this command really works rebooting on fastboot mode : adb reboot bootloader
sure,after checked OEM unlock bootloader option
H818P is working.
Cm9aphla said:
This an incredibly easy way to OEM unlock your G4.
**NOTE** This software feature might not be avaliable on the carrier based versions of the G4 like, Verizon, Sprint ect.
If you have a preview unit or carrier unlocked version of the G4 then this will be very simple.
1. Enable Developer Settings, going into the software version info in the settings and then clicking on the build number 5 times.
2. Go back to the settings and you'll find the developer settings tab at the bottom by about phone, if you setting menu is in list view.
3. Go into the developer settings and you'll see Enable OEM unlock right under Enable Bluetooth HCI snoop log near the top.
4. When you click on OEM unlock it will prompt you that device protection features will not work while this is enabled.
5. Click Yes and reboot the phone.
6. Now your OEM unlocked!
Click to expand...
Click to collapse
That just "allows" for oem unlock that doesn't mean it's actually unlocked. You have to do the same thing on nexus 6 before you run the unlock command line. To my knowledge though the g4 is the same. It's a lollipop feature that you have to check that before you unlock bootloader.
Isn't OEM unlock just so you can use another sim? I don't think that unlocks the bootloader?
Related
Go to http://www.emui.com/plugin.php?id=unlock&mod=detail
Create account, press the green lock button in case it doesn't direct your to this page:
{
"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"
}
After unlock code generated, just restart in fastboot and: fastboot oem unlock <<generated unlock code>>
Congrats you unlocked your bootloader without waiting for a e-mail response
Hi all, I have a problem, I lost my phone box and the serial number I am entering is not letting me get the code.
My phone's model is G7-L03 (which I don't see on that website, and those guys from Huawei support don't answer my emails, it's been over a month and I sent several emails.
Any other way for me to unlock this?
Unlock code fails!
Actual webpage of online unlock bootloader tool by Huawei, does not working at all, always give 14 days error.
Support people just answer "Please use online unlock tool" and they don't know answer anything else.
Conclusion: This company sucks, I tried every method avalaible and no success.
Thank you. It worked for me.
thank you for helping us
i got the unlock code successfully
but i didnt understand what to do next
i am using g7 l01 with stock marshmallow
can any one plz write steps...
You have to reboot to fastboot mode, there are two ways:
First enable developer setting tapping 7 time on build number in phone's information. Open developer setting and enable USB debug.
Download fastboot driver, you can find it on Google.
Then:
1) Open CMD from fastboot folder and type
fastboot reboot bootloader
Click to expand...
Click to collapse
Or turn off your phone, then press power button + volume down
2)Wait for the phone to reboot into fastboot mode
3)Type in CMD
fastboot oem unlock "your code"
Click to expand...
Click to collapse
4)Then you unlocked your phone and you can reboot typing:
fastboot reboot
Click to expand...
Click to collapse
for anyone having trouble unlocking bootloader for g7-L01 ive tried on two different g7-L01 and worked perfect
ive also included twrp and stock recovery too for flashing via fastboot
download these files
https://www.mediafire.com/folder/agrehokgvf3b5/unlock_bootloader
make sure usb debugging is selected by tapping on build until developer option comes available then select developer menu and turn on usb debugging
now first you need to make sure your on lollipop for serial number to show properly (doesn't show on KitKat for some reason )
now lets get started open new folder I have put on here and select huaweiproductIDGenerator
under product model select HUAWEI Y300-0100
make sure to copy product model on to notepad as you will need this
type on on phone *#06# for iemi and input it under Product IEMI/MEID:
now copy and paste product id to notepad as you will need this for later
on your phone go to settings/about phone then status and make a record of your serial number on notepad too
now go to this website and make sure you login if not then sign up http://emui.huawei.com/en/plugin/hwdownload/download
now go to download then bootloader unlock it will take you to another page agree and continue
(IMPORTANT) under product model will be this HUAWEI Y300-0100
then serial number then iemi now finally input the new product id you took note of earlier and fill in verification code and then select commit.
you should now see your bootloader unlock code at the bottom.
Turn off phone then holding vol down and power until you get fastboot screen then connect to PC by USB.
Once connected open cmd and type fastboot devices to see if your device shows
Now type. fastboot oem unlock (yourunlockcode) then press enter.
By now your g7 should reset and wipe everything as it does when unlocking bootloader.
I found this guide on youtube not my work just making it a bit easier for people to understand.
hopes this helps in any way
Hello, ineed bootloader unlock code please send me
Thank you for supporting Huawei
My
Guys all you gotta do is email Huawei xxx (xxx = name of your country) and ask them for a bootloafer unlock code.
They'll ask for your phone info so then you reply to them with the phone's info and get the code to unlock the bootloader.. Violla.
trick not working
Please make sure the verification code and model number are correct. If your device has multiple IMEIs or MEIDs, please try another IMEI or MEID.
Help me withI a sosoftware that can unlock boot loader.
Hello members,
I have been trying to unlock boot loader with my huawei g7L01. But without success.
Number one problem, my computer does not allow me toto open cms.exe. I have installed Android studio with Nougat 7.1.1 and 8.0.
II want to upgrade to nougat.
My phone does not connect well I tried to red stall drivers nothing worked with Hsuite.
If any help I will appreciate especially with a software I can use to install in a the phone and unlock bootlodare, I havesee the unlock code but the all instructions I tried my pphone doesn't connect well with Hsuite, but before it was, after I installed Kingroot, itor doesn't
I am here for help as I want my phone faster, is too slow internet and everything is slow.
Thank you in advance.
McCrintosh said:
Hello members,
I have been trying to unlock boot loader with my huawei g7L01. But without success.
Number one problem, my computer does not allow me toto open cms.exe. I have installed Android studio with Nougat 7.1.1 and 8.0.
II want to upgrade to nougat.
My phone does not connect well I tried to red stall drivers nothing worked with Hsuite.
If any help I will appreciate especially with a software I can use to install in a the phone and unlock bootlodare, I havesee the unlock code but the all instructions I tried my pphone doesn't connect well with Hsuite, but before it was, after I installed Kingroot, itor doesn't
I am here for help as I want my phone faster, is too slow internet and everything is slow.
Thank you in advance.
Click to expand...
Click to collapse
Did you enabled debug USB in developer options?
Did youyou enable debug
Yes I did from developers options.
I could access the phone from huawei (Hsuites) before I installed Kingsport. But afterward I can't success it using hsuite.
The I connect it says USB cable Debug connected. Then I chose MTP. Or H suite now H suite not working.
Thanks for asking.
McCrintosh said:
Yes I did from developers options.
I could access the phone from huawei (Hsuites) before I installed Kingsport. But afterward I can't success it using hsuite.
The I connect it says USB cable Debug connected. Then I chose MTP. Or H suite now H suite not working.
Thanks for asking.
Click to expand...
Click to collapse
You have to use terminal to unlock the bootloader
Using ternimsls
Please help me explain little bit how do I go about it. Instruct or description would help me understand, where to start. If there is a link to that I can find the explanation would help also. Bless.
Thank you.
---------- Post added at 07:39 PM ---------- Previous post was at 07:39 PM ----------
Thank you inin advance.
Which download is for G7-l01 as ia can't find from the chinese emui
Hello help me I want to download the G7-L01 but from chinese site I don't see the G7-L01
Thanks a lot for those who know, maybe I am missing something.
Thanks.
G7-L01 boot loader help not seeing it on chinese emui site
Take a look at the twoback I am not sure if one of them can be used for G7-L01 to unblock the Boot loaderloader.
All Honor devices currently shipped with a locked bootloader. As long as manufacturers provide a way to unlock, then we're down with that - it helps keep your device secure and means that if you lose it, it's harder for people to steal your data (the process of unlocking the bootloader wipes the phone).
There are two ways to unlock your Honor phones bootloader, which will then allow you to install things like custom recoveries, custom kernels / ROMs etc. The first is using the official Honor method, which is free, and the second is using a third party, which costs €4 Euros, but may be the quickest option if the official method isn't working for you.
The official method
In order to unlock your Honor device using the official method, complete the following steps:
Visit https://www.emui.com/en/plugin.php?id=unlock&mod=detail and either create a new account or login with an existing Huawei account.
In the form displayed after logging in, enter:
Your phone model (PLK-L01 for the Honor 7)
Your phone serial number (this can be found in Settings -> About -> Status)
Your phone IMEI1 (this can be found in Settings -> About -> Status)
Your phone product ID (to find this, open the dialler and enter *#*#1357946#*#*)
The captcha code
Press the 'Submit' button.
At this point you will either be provided with a code, or you will receive an error such as 'The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.' If you get the error, you will need to use the unofficial method below.
Open a command window on your PC / Mac, which needs to have 'adb' and 'fastboot' installed from the Android SDK.
Enable USB debugging by tapping the build number in Settings -> About 5 times, then going back and selecting the option from the Development menu.
Enable OEM unlock in the Development menu.
Connect your phone to the PC and approve the security prompt on the device screen.
In the command window on your PC / Mac, enter 'adb reboot bootloader' to enter fastboot mode'.
In the command window on your PC / Mac, enter 'fastboot oem unlock [insertnumberhere]', of course using the number provided by the Huawei site.
YOUR PHONE WILL WIPE ITSELF AT THIS POINT!
That's it! You're done!
{
"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"
}
The unofficial method
In order to unlock your Honor device using the unofficial method, if for example you receive the '14 day' error from the Huwei site, complete the following steps:
On a Windows PC, download and install DC-unlocker from https://www.dc-unlocker.com/.
On your phone, enter Manufacturer Mode - open the dialler and enter *#*#2846579#*#*. In the app that then opens, select Project Menu -> Background settings -> USB ports settings -> Manufacturer Mode.
Download the Huawei driver pack from https://files.dc-unlocker.com/share.html?v=share/88D4A98C154D4E19AF9D4A1EF09BA620.
Install the Huawei driver pack by extracting the file you just downloaded (using WinRAR or similar) and running 'DriverSetup'
After installing the driver pack, connect your phone to the PC. In Device Manager, after the automated driver install, you should have no 'Unknown Devices'.
Launch the previously downloaded DC-unlocker application.
From the drop down lists, select 'Huawei Phones' and 'Auto Detect Model'.
Press the magnifying glass icon - the app will then search for your phone.
You should see an image like the one below showing your phone is found. At this point, press the 'Buy Credits' option to set up your DC-Unlocker account and purchase the 4 credits required for code retrieval (this will cost €4). You can also do this directly from the DC-Unlocker website.
After your credit purchase is complete, click the 'Server' section and enter your new DC-unlocker login details. Press 'Check Login' to validate the details (if the server is busy, this may take multiple attempts).
Click the 'Unlocking' section, and click 'Read Bootloader Code'. Do NOT click 'Unlock'. Again, if the server is busy, this may take multiple attempts. The white area of the app will now display the bootloader code. Screen grab this just in case!
Open a command window on your PC, which needs to have 'adb' and 'fastboot' installed from the Android SDK.
Enable USB debugging by tapping the build number in Settings -> About 5 times, then going back and selecting the option from the Development menu.
Enable OEM unlock in the Development menu.
Connect your phone to the PC and approve the security prompt on the device screen.
In the command window on your PC / Mac, enter 'adb reboot bootloader' to enter fastboot mode'.
In the command window on your PC / Mac, enter 'fastboot oem unlock [insertnumberhere]', of course using the number provided by the DC-Unlocker process.
YOUR PHONE WILL WIPE ITSELF AT THIS POINT!
That's it! You're done!
Did anyone succefuly try the 2nd method with a PLK-AL10 (64 GB) version?
I think it should work. Let us know if you try!
P
Sent from my SM-G928F using Tapatalk
Unofficial method works for 16GB! But be very careful to click on the right button when you retrieve the Unlock Code from the DC Unlocker software.
I spent an additional 4 euros just to get it right the second time. You need the bootloader code unlock, not the unlock codes.
After that proceed to this link to root the phone. Works even when you have the latest B180 EMU rom too!
http://forum.xda-developers.com/honor-7/development/recovery-twrp-2-8-7-0-hwplk-plk-l01-t3290306
gtee said:
Unofficial method works for 16GB! But be very careful to click on the right button when you retrieve the Unlock Code from the DC Unlocker software.
I spent an additional 4 euros just to get it right the second time. You need the bootloader code unlock, not the unlock codes.
After that proceed to this link to root the phone. Works even when you have the latest B180 EMU rom too!
http://forum.xda-developers.com/honor-7/development/recovery-twrp-2-8-7-0-hwplk-plk-l01-t3290306
Click to expand...
Click to collapse
same with me..haha
Correct me if I'm wrong, but as I read it on the official Huawei site, they will drop the warranty if I ask them for the unlock code. So my question is, if I unlock my device using the second method, will Huawei know that? DC Unlocker get the code from Huawei? And can I relock the bootloader to get OTAs and unlock it again using the code that DC gives me?
ShaneDiNozzo said:
... if I unlock my device using the second method, will Huawei know that?
Click to expand...
Click to collapse
YES, they will be able to see that! And no, if you relock your device it is relocked and not locked! You will have a notification about that if you are in fastboot mode! Maybe that HUAWEI deny there warranty but you should have 2 years EU warranty anyway. And last but not least: no risk, no fun!
Probleme to unlock
Problem to unlock because when i'm loggin on it he sent me on a new page of emui 5.0..
Im get stucked on step 12. Dont find adb
I got a chinese honor 8 (FRD-AL00) and im having problems with the official update (FRD-L19C432B131).
It seems that the updates outside China corresponds to other version. Phone has multiple restarts ans errors.
Enable OEM unlock in the Development menu. ( my Honor 8 no have the option in developer )
is there a way to make it so some stuff stays and not everything gets wiped. also im gonna use this but i dunno what im gonna do after to root.
so can someone give me a link to a guide.
ShaneDiNozzo said:
Correct me if I'm wrong, but as I read it on the official Huawei site, they will drop the warranty if I ask them for the unlock code. So my question is, if I unlock my device using the second method, will Huawei know that? DC Unlocker get the code from Huawei? And can I relock the bootloader to get OTAs and unlock it again using the code that DC gives me?
Click to expand...
Click to collapse
You do get OTAs. There arw lot of confusion on this but yes you get for sure.
How can I unlock bootloader on my Honor 7S ( DUA-L22 ) for free ? Thanks for help guys
I tried method 1 and contacted Huawei mobile services but they told me that the botloader unlock service has been stopped on 25th of July 2018!
Anyway method 2 worked like a charm, thanks a lot for the Guide
kubesak97 said:
How can I unlock bootloader on my Honor 7S ( DUA-L22 ) for free ? Thanks for help guys
Click to expand...
Click to collapse
You can not anynore. Its all paid services now
shashank1320 said:
You can not anynore. Its all paid services now
Click to expand...
Click to collapse
It is still doable for free for phones with rollback to Android 5.x available (The Kingroot way). I just did it on my old Honor 7 (PLK-L01).
maciopa said:
It is still doable for free for phones with rollback to Android 5.x available (The Kingroot way). I just did it on my old Honor 7 (PLK-L01).
Click to expand...
Click to collapse
But doesn't that question was for 7S? Which is new device and can not ve rolled back to Android 5.X
Started with device on July 5th security patch Android Oreo 8.1. 100% Verizon device. Got replacement phone in the mail. No SIM inside. Turned it on. Plugged it in to a computer. Skipped past everything on setup. Turned on Developer options. OEM Unlock was grayed out.
Turned off automatic system updates in dev options. Turned on USB Debugging. Keep screen awake while charging. Ran ADB "adb shell pm uninstall --user 0 com.android.phone". Turned on wifi and waited a couple minutes in the chrome browser. Returned to Developer options and OEM Unlock was no longer grayed out. Ticked it.
Kept phone running for a few minutes. Turned device off and booted to fastboot. Still locked. Returned to system from bootloader. OEM Unlock still blue. Let apps update and also logged into Google account. Noticed OEM Unlock was staying unlocked through a couple reboots.
Decided to upgrade to Pie. Did it OTA. OEM Unlock stuck through the update. Shut down phone from system. Once phone was off I held down power button and the volume down button to take me to Fastboot mode. Ran "fastboot flashing unlock". BOOM! Got the the screen to say yes or no to bootloader unlock.
Device was erased because I chose yes. OEM Unlock grayed out again but in unlocked position? Hmm...ok with me. The strangest thing happened when I checked my IMEI when I was done. I had checked before I started also and I could have sworn there was different information than what I ended up with at the last check. Im tired..maybe just trippin out. The OEM Unlock toggle is available to toggle again.
hallr88 said:
Started with device on July 5th security patch Android Oreo 8.1. 100% Verizon device. Got replacement phone in the mail. No SIM inside. Turned it on. Plugged it in to a computer. Skipped past everything on setup. Turned on Developer options. OEM Unlock was grayed out.
Turned off automatic system updates in dev options. Turned on USB Debugging. Keep screen awake while charging. Ran ADB "adb shell pm uninstall --user 0 com.android.phone". Turned on wifi and waited a couple minutes. Returned to Developer options and OEM Unlock was no longer grayed out. Ticked it.
Kept phone running for a few minutes. Turned device off and booted to fastboot. Still locked. Returned to system from bootloader. OEM Unlock still blue. Let apps update and also logged into Google account. Noticed OEM Unlock was staying unlocked through a couple reboots.
Decided to upgrade to Pie. Did it OTA. OEM Unlock stuck through the update. Shut down phone from system. Once phone was off I held down power button and the volume down button to take me to Fastboot mode. Ran "fastboot flashing unlock". BOOM! Got the the screen to say yes or no to bootloader unlock.
Device was erased because I chose yes. OEM Unlock grayed out again but in unlocked position? Hmm...ok with me. The strangest thing happened when I checked my IMEI when I was done. I had checked before I started also and I could have sworn there was different information than what I ended up with at the last check. Im tired..maybe just trippin out.
Click to expand...
Click to collapse
Go to this link http://www.imeipro.info/check_lg.html and plug in your IMEI number. What does it say under buyer code and buyer name? Don't stop with the unlock command, you need to also unlock_critical. This will also wipe your device again but it is needed to flash the bootloader and to be "fully" unlocked.
Same site wrong checker
v12xke said:
Go to this link http://www.imeipro.info/check_lg.html and plug in your IMEI number. What does it say under buyer code and buyer name? Don't stop with the unlock command, you need to also unlock_critical. This will also wipe your device again but it is needed to flash the bootloader and to be "fully" unlocked.
Click to expand...
Click to collapse
\
{
"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"
}
https://imgur.com/a/mEKLSbZ
I didnt have to do the unlock_critical. Just the regular one.
So is finally unlocked? Maybe we can try after a factory reset on Pie?
siggey said:
So is finally unlocked? Maybe we can try after a factory reset on Pie?
Click to expand...
Click to collapse
I've already done a few factory resets in Pie and its holding tough.
siggey said:
So is finally unlocked? Maybe we can try after a factory reset on Pie?
Click to expand...
Click to collapse
I tried many ways to get in with Pie. If you can do it. Props
hallr88 said:
I tried many ways to get in with Pie. If you can do it. Props
Click to expand...
Click to collapse
I really think it can be done ,9nce that toggle is cooperating ,there is like there's some other step to enforce that toggle,like doing an OEM_UNLOCK permission or state change in the bootloader.I ran fastboot getvar all when toggle was enabled,there is a OEM unlock id =yes, how to pull that id idk,but I think there's still a way.
Aslo I inserted the sim with the OEM toggle enabled,but my sim was never recgonized,I guess uninstalling the com.andriod.phone is the radio,or modem? I feel like I was as close as ever just missing something Stoopid.
djmouse said:
I really think it can be done ,9nce that toggle is cooperating ,there is like there's some other step to enforce that toggle,like doing an OEM_UNLOCK permission or state change in the bootloader.I ran fastboot getvar all when toggle was enabled,there is a OEM unlock id =yes, how to pull that id idk,but I think there's still a way.
Aslo I inserted the sim with the OEM toggle enabled,but my sim was never recgonized,I guess uninstalling the com.andriod.phone is the radio,or modem? I feel like I was as close as ever just missing something Stoopid.
Click to expand...
Click to collapse
I tried as many permissions that I could think of when I got to that point. When I uninstalled the system app I realized that I had to get it back eventually so I did a factory reset with the toggle on and it stuck through it. I was like omg. lol Keep at it!
I also had the SIM unrecognized when I uninstalled com.android.phone. Stopped the connection to Verizon servers I think. Spoof server? JK. There's gotta be some type of encryption in whatever it says to Verizon.
i will try this if it is indeed working.
hallr88 said:
I tried as many permissions that I could think of when I got to that point. When I uninstalled the system app I realized that I had to get it back eventually so I did a factory reset with the toggle on and it stuck through it. I was like omg. lol Keep at it!
I also had the SIM unrecognized when I uninstalled com.android.phone. Stopped the connection to Verizon servers I think. Spoof server? JK. There's gotta be some type of encryption in whatever it says to Verizon.
Click to expand...
Click to collapse
I never did a factory reset when the toggle was in the blue,I figured that would reinstall com.andriod.phone.a factory reset will make you have to.go back and enable Dev options ,and your saying OEM toggle was on? I'm not sure that even happens on a Google varient .
djmouse said:
I never did a factory reset when the toggle was in the blue,I figured that would reinstall com.andriod.phone.a factory reset will make you have to.go back and enable Dev options ,and your saying OEM toggle was on? I'm not sure that even happens on a Google varient .
Click to expand...
Click to collapse
I think I may have updated to Pie before I actually did the factory reset. I knew I should have recorded my screen. Ok, I remember. I did the update to see if it would give me back my phone use and it didn't. So I ended up saying just factory resetting in Pie and it stuck and gave me phone use.
Anyone else try this, it's been two days...
Sent from my Pixel 2 XL using Tapatalk
gcodori said:
Anyone else try this, it's been two days...
Click to expand...
Click to collapse
I'm going to try today
---------- Post added at 10:59 PM ---------- Previous post was at 10:59 PM ----------
I have a replacement waiting for me at home
so the device is on 8.0..tried the method and no go
shooterlgk said:
so the device is on 8.0..tried the method and no go
Click to expand...
Click to collapse
Dang. Shoulda Skyped r sumthin. Hate good thoughts that come a little too late.
hallr88 said:
Dang. Shoulda Skyped r sumthin. Hate good thoughts that come a little too late.
Click to expand...
Click to collapse
well i still have it without a sim..i havent quit yet
Hmu
Tried it on pie, no sim, but I was active before. Oem unlock became blue, I could toggle it... But upon going into fastboot, all I got was when doing "fastboot flashing unlock" or unlock_critical was "flashing not allowed
Update: left it charging all day, upon checking up again after hours, the toggle became grey again.
Update 2: Indeed, all i get is FAILED (remote: Flashing Unlock is not allowed) and upon reboot oem unlock becomes grey again
hork-bajir12 said:
Tried it on pie, no sim, but I was active before. Oem unlock became blue, I could toggle it... But upon going into fastboot, all I got was when doing "fastboot flashing unlock" or unlock_critical was "flashing not allowed
Update: left it charging all day, upon checking up again after hours, the toggle became grey again.
Update 2: Indeed, all i get is FAILED (remote: Flashing Unlock is not allowed) and upon reboot oem unlock becomes grey again
Click to expand...
Click to collapse
So u had service on ur phone already, and u tried his method and u got that far?
shooterlgk said:
So u had service on ur phone already, and u tried his method and u got that far?
Click to expand...
Click to collapse
Had but not for couple months.
Hi there,
I am openning a new thread about this subject, because all the other threads are seem to be outdated.
I have tried below approaches:
Installed Minimal ADB and Fastboot to PC. Tried to install TWRP, but had an error because the phone is locked.
Installed KingoRoot to PC and phone. Tried to root from PC, but had an error possibly about the phone is locked.
]Installed DC Unlocker to PC and phone, paid for 4 credits. Tried to connect from PC, but unable to connect to the phone because the phone is using Android 8.
E-mailed Huawei and asked them to send me unlock code. No luck.
I have found a thread where if the phone uses Android 5.0, the owner of the thread says unlock code can be fetched from the internal files of the phone by running sudo codes from adb shell. However, had no luck downgrading the phone to Android 5.0, possibly about the phone is locked.
I appreciate if anyone can make an up-to-date suggestion.
Thank you anyways.
As far i know, there is no way to do it free. I never tested but there are sites providing paid unlock codes.
Part of them are using bug before security patches (maybe DC Unlocker too? And it's why it's not working).
The sites promise to unlock even after patches, so you can always try it. There is probably no other option, but i don't know if it works.
You can't downgrade android and do anything with phone, because phone is locked as it says - so verdict is easy - you are stuck.
Donio3d said:
As far i know, there is no way to do it free. I never tested but there are sites providing paid unlock codes.
Part of them are using bug before security patches (maybe DC Unlocker too? And it's why it's not working).
The sites promise to unlock even after patches, so you can always try it. There is probably no other option, but i don't know if it works.
You can't downgrade android and do anything with phone, because phone is locked as it says - so verdict is easy - you are stuck.
Click to expand...
Click to collapse
Thank you for the response @Donio3d.
I have downloaded official stock rom with Android 7.0 EMUI 5.0 and will try to install it via Huawei recovery (volume+, volume-, power buttons). If I could successfully install this ROM, I am expecting DC Unlocker to work because it is clearly saying on the app that it is only working with OS below Android 8.0.
Huawei recovery shouldn't let you downgrade EMUI, but try it and post results
Donio3d said:
Huawei recovery shouldn't let you downgrade EMUI, but try it and post results
Click to expand...
Click to collapse
Despite saying that it does not work with Android 8.0, I was able to successfully unlock after a few trials with DC Unlocker.
did you follow any specific guide? I want to unlock too.
corvx said:
did you follow any specific guide? I want to unlock too.
Click to expand...
Click to collapse
Enable developer mode by pressing on Build Number 8-10 times in Settings->Specifications->About Phone.
Enable OEM Unlock and USB Debugging in Settings->Specifications->Developer Options.
Enable Manufacture Mode and keep the menu open by dialling *#*#2846579*#*# and selecting Background Settings->USB Port Settings.
Open DC Unlocker and press Find Phone.
If successfully found phone, click Unlocking->Read Bootloader Code.
Open Minimal ADB tool in command prompt and enter
Code:
adb reboot bootloader
When bootloader screen opens, enter
Code:
fastboot oem unlock CODE_YOU_HAVE_GOT
yenerunver said:
Open DC Unlocker and press Find Phone.
If successfully found phone, click Unlocking->Read Bootloader Code.
Click to expand...
Click to collapse
I get stuck here. I think phone is not recognized properly. DC unlocker does not output any information regarding my phone. It only states that the "Application port" has been recognized, nothing else. Any ideas?
corvx said:
I get stuck here. I think phone is not recognized properly. DC unlocker does not output any information regarding my phone. It only states that the "Application port" has been recognized, nothing else. Any ideas?
Click to expand...
Click to collapse
If it has found the working port and said, for example, "COM 7" that means the connection is successfull. Because of Android 8, some features of DC Unlocker is not working. You can try to get Bootloader code as soon as you get the application port.
yenerunver said:
Despite saying that it does not work with Android 8.0, I was able to successfully unlock after a few trials with DC Unlocker.
Click to expand...
Click to collapse
Wait, so what did you do? Unlocked from android 8 or downgraded in some way?
When i tried to do that, the DC Unlocked doesn't recognize my phone.
yenerunver said:
If it has found the working port and said, for example, "COM 7" that means the connection is successfull. Because of Android 8, some features of DC Unlocker is not working. You can try to get Bootloader code as soon as you get the application port.
Click to expand...
Click to collapse
Do you recall what build were you in when doing this procedure?
I can confirm the procedure by yenerunver works. My phone was on the latest build: WAS-LX3 8.0.0.370(C605).
This was my output from DC-Unlocker version 1.00.1422:
Code:
Before detection Huawei Android phones, enable 'Manufacture' mode:
in dial pad type *#*#2846579#*#* for Qualcomm and Kirin based models, or *#*#14789632#*#* for MTK, then select
'ProjectMenu',
'Background settings',
'USB ports settings',
'Manufacture mode'.
Step by step guide for other Huawei phone unlock:
https://www.dc-unlocker.com/huawei_phones_detect_unlock_tutorials
===================================================================
DC - Unlocker 2 Client 1.00.1422
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM4
Phone not found !
===================================================================
===================================================================
DC - Unlocker 2 Client 1.00.1422
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM4
Phone not found !
===================================================================
===================================================================
DC - Unlocker 2 Client 1.00.1422
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM4
===================================================================
Check account status
User : MY_USER_REDACTED
Credits left : 4
Activated features:
Software debugger
Unlock Auto detect (recommended) cost 4 cr
Service text tutorial: https://www.dc-unlocker.com/huawei-android-hisilicon-unlock-guide
===================================================================
===================================================================
DC - Unlocker 2 Client 1.00.1422
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Applications port COM4
===================================================================
Reading bootloader code...
Bootloader code : MY_CODE_REDACTED
===================================================================
As you can see, I tried detecting my phone a couple of times. And only when "Phone not found !" wasn't shown anymore then I proceeded to read the bootloader unlock code.
My suggestion is to disable HiSuite from opening upon phone connection and to close it completely so that it doesn't switch the "Manufacture mode" back to "HiSuite mode".
Donio3d said:
Wait, so what did you do? Unlocked from android 8 or downgraded in some way?
When i tried to do that, the DC Unlocked doesn't recognize my phone.
Click to expand...
Click to collapse
I have unlocked from Android 8.0. I followed the steps above several times and somehow managed to unlock the phone.
yenerunver said:
I have unlocked from Android 8.0. I followed the steps above several times and somehow managed to unlock the phone.
Click to expand...
Click to collapse
I'm stuck on detecting the COM port. Phone is recognized as always, then after turning on Manufacturer it shows in Windows explorer as "CD Drive" and in device manager as "WAS-LX1" tripple times and one time HDB Interface on "other devices" sections. Any ideas? Phone is recognized by minimal adb, but still not by DC Unlocker. I also tried reinstalling Google ADB drivers and allowing debugging in charging mode.
Build: WAS-LX1 8.0.0.390(C432)
{
"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"
}
Donio3d said:
I'm stuck on detecting the COM port. Phone is recognized as always, then after turning on Manufacturer it shows in Windows explorer as "CD Drive" and in device manager as "WAS-LX1" tripple times and one time HDB Interface on "other devices" sections. Any ideas? Phone is recognized by minimal adb, but still not by DC Unlocker. I also tried reinstalling Google ADB drivers and allowing debugging in charging mode.
Build: WAS-LX1 8.0.0.390(C432)
Click to expand...
Click to collapse
Do you have the latest HiSuite installed? You might want to reinstall it, the included drivers were the only ones I needed.
1 install latest hisuite
2 open developer options and enable oem unlock and usb debugging
3 open dial pad and enter this code*#*#2846579*#*# and in background settings >usb port settings enable manufacturer mode but dont go back just stick to this menu and connect to pc and open dc unlocker and it should detect your phone.
i unlocked mine with this method with same 370 version.
I'm impressed, because it actually worked... I just needed to reinstall HiSuite and buy 4 credits for 4€.
Hi
Sorry for a basic question, i am very new to all this
1) What does this method do? Does it provide you a code to unlock bootloader or do you have to already have a code from somewhere else to use this?
I have a noob question, after aplying this procedure, is there a way to unlock the device to make it work with other carriers than tho one it's blocked in?
Theopsis said:
I have a noob question, after aplying this procedure, is there a way to unlock the device to make it work with other carriers than tho one it's blocked in?
Click to expand...
Click to collapse
I think you can use the option in DC that says "Read Unlock Codes" not "Read bootloader Code".
When unlocking mine, I clicked there and it gave me some unlock codes (Lost my 4€...).
Asked to DC and they said that the codes are for unlock the network of the phone.
Cheers!
Hi, this is my first post.
My Device: Samsung Galaxy Note 4
Model Number: SM-N910F
Build: MMB29M.N910FXXS1DQFB
Version: N910FXXS1DQFB//N910fXXS1DQA3
Android Version: 6.0.1
Qualcomm Snapdragon 805 APQ8084
My first attempt flashing my note4 ended with a brick, now it works again, but i don't know what went wrong. I already activated developer options, but there is no "oem unlock". I read a lot on XDA Forum and it is emphasized that it is important to unlock OEM/bootloader in order to modify the device. I already know that some Note 4 devices have a locked bootloader and some don't, an i assume i haven't a locked bootloader on my device, but i'm not sure.
Can anyone confirm that my Note 4 has already an unlocked bootloader?
Older phones do not have OEM.
To verify if your bootloader is unlocked read these steps.
Open the Phone app or the Dialer.
Enter the code: *#*#7378423*#*#
This should automatically open a new window.
Tap the Service info.
Open Configuration.
You should see one of the two messages:
– Bootloader Unlocked Allowed – Yes
– Bootloader Unlocked – Yes
@Samarimama -thank you, but this doesn't work without sim-card i guess?
I'm sorry, but the code doesn't work with my sim card.
Ok, take off your SIM card and try it again.
I've tried with and without SIM card: "Invalid USSD-Code". Any other options?
Try with ADBCheck from Your PCTo check your bootloader status from your PC, you’ll need to use an ADB and fastboot tool. Until recently, you needed to download the full Software Development Kit (SDK) to get to ADB and fastboot. But now, you can get this lightweight tool separately.
Step 1: Setting Up the Command PromptWhen you install the tool, you should:
Locate the path to the ADB and fastboot folder.
Click on the Start Menu and type ‘cmd’ until the Command Prompt icon appears.
{
"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"
}
Type the path to the ADB and fastboot folder in your Command Prompt. For example:
C:UsersUsernameDownloadsADB and fastboot
Step 2: Turning on the Fastboot ModeOnce the Command Prompt is set, you should set your phone to fastboot mode. To do this:
Turn your Android phone off.
Hold the Volume Down and Power/Unlock buttons at the same time until the phone turns on again.
When it turns on, release the Power button, but hold the Volume Down key until you see the bootloader menu. It should display the little Android bot lying on its back on a dark background, with a text under it.
Connect the computer and your phone with a data cable.
Step 3: Checking the StatusNow that everything is set, you can use the Command Prompt to check the status of your bootloader. To do this, you should:
Enter the ‘./adb devices’ command into the Command Prompt to check if ADB can locate your device. This should list your phone.
Execute the ‘./adb bootloader’ command to boot into bootloader.
Once you are in the bootloader, type the ‘fastboot devices’ command in the Command Prompt and execute it. If it lists a code, that means that the system can detect your phone.
Enter the ‘fastboot oem device-info’ command and run it. It should list some device data, including the bootloader information.
Look for ‘Device Unlocked’ from the info.
If it says ‘true’ next to it, it means that your device is unlocked. If it says ‘false,’ it means that that it’s still locked.
Sometimes, you can see this information right away in the bootloader display of your Android phone.
I agree with @Samarimama . Bootloaders are usually not locked on older phones, and the option to unlock it can not be found in developer options. However, my understanding is that bootloaders could be locked on carrier tied phones, most often USA-based, but those versions are usually not F, but some other letters. Unsure about the version you have.
I do believe tho that you should try and first update the firmware on that phone, since that does not seem to be the latest version. N910FXXU12DRI2, is the latest one, i have worked with several CSC-versions of it, and have yet to encounter one with locked bootloader.
I also figure that it should not be possible to flash any custom binary on to a phone with a locked bootloader, you should just get error while trying. So if you managed to actually flash something on to your phone, it is unlikely that the bootloader on your phone is locked. Then it is rather a question of how you went about while flashing that resulted in bricking the device. And what you mean by "bricked".
It is why we need to unlock the bootloader to flash a ROM.
prkfsz said:
I agree with @Samarimama . Bootloaders are usually not locked on older phones, and the option to unlock it can not be found in developer options. However, my understanding is that bootloaders could be locked on carrier tied phones, most often USA-based, but those versions are usually not F, but some other letters. Unsure about the version you have.
I do believe tho that you should try and first update the firmware on that phone, since that does not seem to be the latest version. N910FXXU12DRI2, is the latest one, i have worked with several CSC-versions of it, and have yet to encounter one with locked bootloader.
I also figure that it should not be possible to flash any custom binary on to a phone with a locked bootloader, you should just get error while trying. So if you managed to actually flash something on to your phone, it is unlikely that the bootloader on your phone is locked. Then it is rather a question of how you went about while flashing that resulted in bricking the device. And what you mean by "bricked".
Click to expand...
Click to collapse
I got my Note 4 from a friend in Austria, but i live in Germany, so i made a reset and this is why i never knew there is a firmware update for my Note 4. I only use it in Germany, and after the reset i have N910FXXS1DQFB//N910fXXS1DQA3. Is it really neccessary to flash the newer austrian firmware? It's a bit confusing for me, excuse me for being so dumb.
Samarimama said:
Try with ADBCheck from Your PCTo check your bootloader status from your PC, you’ll need to use an ADB and fastboot tool. Until recently, you needed to download the full Software Development Kit (SDK) to get to ADB and fastboot. But now, you can get this lightweight tool separately.
Step 1: Setting Up the Command PromptWhen you install the tool, you should:
Locate the path to the ADB and fastboot folder.
Click on the Start Menu and type ‘cmd’ until the Command Prompt icon appears.
Type the path to the ADB and fastboot folder in your Command Prompt. For example:
C:UsersUsernameDownloadsADB and fastboot
Step 2: Turning on the Fastboot ModeOnce the Command Prompt is set, you should set your phone to fastboot mode. To do this:
Turn your Android phone off.
Hold the Volume Down and Power/Unlock buttons at the same time until the phone turns on again.
When it turns on, release the Power button, but hold the Volume Down key until you see the bootloader menu. It should display the little Android bot lying on its back on a dark background, with a text under it.
Connect the computer and your phone with a data cable.
Step 3: Checking the StatusNow that everything is set, you can use the Command Prompt to check the status of your bootloader. To do this, you should:
Enter the ‘./adb devices’ command into the Command Prompt to check if ADB can locate your device. This should list your phone.
Execute the ‘./adb bootloader’ command to boot into bootloader.
Once you are in the bootloader, type the ‘fastboot devices’ command in the Command Prompt and execute it. If it lists a code, that means that the system can detect your phone.
Enter the ‘fastboot oem device-info’ command and run it. It should list some device data, including the bootloader information.
Look for ‘Device Unlocked’ from the info.
If it says ‘true’ next to it, it means that your device is unlocked. If it says ‘false,’ it means that that it’s still locked.
Sometimes, you can see this information right away in the bootloader display of your Android phone.
Click to expand...
Click to collapse
ADB does not recognize my Note 4. Debugging mode is already acitivated.
Me too I have this problem with the same phone. My PCs do not recognize him
prkfsz said:
I also figure that it should not be possible to flash any custom binary on to a phone with a locked bootloader, you should just get error while trying. So if you managed to actually flash something on to your phone, it is unlikely that the bootloader on your phone is locked. Then it is rather a question of how you went about while flashing that resulted in bricking the device. And what you mean by "bricked".
Click to expand...
Click to collapse
I already had twrp on my phone and i simply panicked while flashing a rom. After that it had a permanent bootloop, after taking out batteries it was impossible to switch it on. It happened some years ago, i used recovery software, made a factory reset and it works. And I still want to install a system that is not as old as 2017. I have a lot of patience, and i will find a way - if the bootloader is unlocked. Therefore i try to figure out if Note 4 has a locked bootloader or not. You say, Note 4 is that old, it hasn't any, and because twrp was on the phone already, it is unlocked. Then it seems to be a waste of time to try to use ADB to be sure. Instead i could try to flash it right now and don't care about unlocking something that doesn't exist on Note 4.
If you can go to TWRP, install the ROM you want with your phone and flash it with Gapps.
Old Lady said:
I got my Note 4 from a friend in Austria, but i live in Germany, so i made a reset and this is why i never knew there is a firmware update for my Note 4. I only use it in Germany, and after the reset i have N910FXXS1DQFB//N910fXXS1DQA3. Is it really neccessary to flash the newer austrian firmware? It's a bit confusing for me, excuse me for being so dumb
Click to expand...
Click to collapse
You're not dumb for not knowing something.. ;-)
It's hard to say if updating is totally necessary but it's almost always recommended to update your phone to the latest firmware before flashing custom ROMs. And I would say, especially since the last made firmware seems to have been made more that a year after the firmware you actually have on your phone I would strongly recommend updating to the latest firmware. It's not difficult, you go to settings and find where you choose to update and let the phone find the latest update itself while being connected to internet.
After that, if you already have TWRP installed, which I understand you do, just try and flash the custom ROM you want. But please remember to before that back up everything you want to save from the phone. And also make a twrp backup of the phone so you can restore it if something goes wrong. And read the suggested flashing procedure several times before actually doing it so you are familiar with it. If something goes wrong go to twrp and restore it from there.
Old Lady said:
I already had twrp on my phone and i simply panicked while flashing a rom. After that it had a permanent bootloop, after taking out batteries it was impossible to switch it on. It happened some years ago, i used recovery software, made a factory reset and it works. And I still want to install a system that is not as old as 2017. I have a lot of patience, and i will find a way - if the bootloader is unlocked. Therefore i try to figure out if Note 4 has a locked bootloader or not. You say, Note 4 is that old, it hasn't any, and because twrp was on the phone already, it is unlocked. Then it seems to be a waste of time to try to use ADB to be sure. Instead i could try to flash it right now and don't care about unlocking something that doesn't exist on Note 4.
Click to expand...
Click to collapse
What do you mean "panicked while flashing a ROM"? What did you do while flashing?
It is not a serious problem.
prkfsz said:
What do you mean "panicked while flashing a ROM"? What did you do while flashing?
Click to expand...
Click to collapse
Phone showed a litte red android while flashing but nothing seemed to happen for a long time, so i disconnected phone and pc. After that my phone didn't work anymore, now everthing is fine and soon i will try it once more - without disconnecting.