I just checked my emails and saw a reply from LG, containing the official unlocking procedure
alright, so here you go:
Requirements
- Linux: no drivers, only adb and fastboot (Linux is preferable, because drivers can't mess something up I've used Xubuntu 12.10 BTW)
- Windows: all drivers (including fastboot drivers) installed and functioning
- a working and updated ADB (for installing ADB, search for tuts here on xda )
- a unlockable firmware which is flashed several hours before trying to unlock the bootloader (and also being connected to the network)
- be willing to recycle all your warranty papers
- and most important: a brain with the ability to read
The Steps
1) charge your phone to 100% (not mentioned by LG, but it helped for me)
2) connect your phone in LG software mode (every mode with an activated adb should work, too)
3) if you have the path to your adb defined, then goto 3a). if not, then goto 3b)
3a) open a terminal and type
Code:
adb reboot oem-unlock
{
"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"
}
3b) open a terminal and type
Code:
cd ~/android-sdk/platform-tools
in Linux or
Code:
cd C:\...
on windows (if you've installed the android-sdk in your home directory under "android-sdk". if not, change it to the directory you've installed it)
then type
Code:
adb reboot oem-unlock
4) now you should see this on your phone:
do i wanna unlock it? of course i do so press the vol + button ATTENTION: there is no further warning, your whole /data/ partition will be formatted!!!
5) now you should see this, and your BL is unlocked and your /data/ partition is wiped
6) now pull out your usb cable and your battery, too
7) put your battery back in and boot
8) set up your system
9) now go to the hidden menu and check your BL status (dialer: 3845#*880# --> Bootloader Unlock Check --> Bootloader Unlock Check --> Unlock)
Some people still think that
Code:
adb reboot bootloader
fastboot oem unlock
is the right command, but guess what: it isn't so please don't use it
Please follow below directions to unlock bootloader.
1. Turn on the phone with SIM card, and wait for connection to the real network.
2. Wait for couple of hours.
3. Connect your handset to local PC with USB cable.
4. Enter "adb reboot oem-unlock" in DOS command window.
5. Reboot handset and you can see the bootloader unlock guide on your phone.
6-1. If you press volume up key, handset is bootloader unlock status.
You can download custom image using fastboot command.
6-2 If you press power on key, user doesnot accept unlock bootlaoder and handset normally power on.
Click to expand...
Click to collapse
so this was the official way now we're gonna take a look into the way, that can unlock every bootloader (at least we've heard nothing opposite )
download this attatched BL_unlock file and extract it
execute the BL-unlock.bat
your bootloader is now unlocked
so what it does:
it copys the calue of the fuse "odm_reserved" to a temporary folder in /data/local
changes the value to an "unlocked" one
and it pushes the changed value back to the fuse
Be aware, that whatever you do, you do it on your own responsibility. I am not responsible for any damage that might occur.
Also keep in mind, that there is no way to relock it. So think before doing anything.
No matter which version?
I asked for the official unlock method, and lg said that only euro-open would be unlockable. But i guess it will work on some other firmwares too.
Sent from my LG-P880 using xda premium
Ask about uk too? Since you got a response and I didn't. Or make a modded kdz that always flashes to eur-xxx since you have mad skills lol
Sent from my rooted P880
@non4 said:
Ask about uk too? Since you got a response and I didn't. Or make a modded kdz that always flashes to eur-xxx since you have mad skills lol
Sent from my rooted P880
Click to expand...
Click to collapse
It is not kdz that should be moded it is the kdz flash program...
There must be something which controls the device ID or IMEI, because it is no longer possible to unlock. Allways stack on [LGE_SECURITY] Unlock permission denied. I did tried already all possibility including drivers, differen adb versions, downgrading, updating e.g.
It is done on Optimus G...maybe someone could contact developer of that app.
https://play.google.com/store/apps/details?id=edu.shell.freegee&hl=hr
Also XDA dev.
http://forum.xda-developers.com/showthread.php?t=2094696
Doesn't work on 234. Security error.
On 232.14 - Unlock Permission Denied.
So with a branding you cannot unlock your boot loader. Maybe someone can find a workaround.
i have tried it on kubuntu with ADB.
nedooo said:
It is not kdz that should be moded it is the kdz flash program...
Click to expand...
Click to collapse
Yeah I'm thinking that, maybe we can spoof the region to lg flashtool or something, if its just flags in the kdz that are read by the flashtool it shouldn't be too hard to patch. Hopefully someone can :thumbup:
Sent from my rooted P880
@non4 said:
Yeah I'm thinking that, maybe we can spoof the region to lg flashtool or something, if its just flags in the kdz that are read by the flashtool it shouldn't be too hard to patch. Hopefully someone can :thumbup:
Sent from my rooted P880
Click to expand...
Click to collapse
German, Euro Open and Czech fw have same size and I don't think so, that they released difeffrent versions for several countries. But what I think is somewhere some specific RIL's region list what BL check before unlocking process.
In cmd.exe when i enter 'adb reboot oem-unlock' it returns 'adb' is not a valid command.
Sorry for being a noob
mastershefis said:
German, Euro Open and Czech fw have same size and I don't think so, that they released difeffrent versions for several countries. But what I think is somewhere some specific RIL's region list what BL check before unlocking process.
Click to expand...
Click to collapse
that's what i'm thinking too. i guess there's the same BL on every firmware version. when trying to unlock the phone, the bootloader checks a file and "decides" then if it's unlockable or not...
Emin3ms said:
In cmd.exe when i enter 'adb reboot oem-unlock' it returns 'adb' is not a valid command.
Sorry for being a noob
Click to expand...
Click to collapse
you need to execute the command in a folder, where your adb is
Emin3ms said:
In cmd.exe when i enter 'adb reboot oem-unlock' it returns 'adb' is not a valid command.
Sorry for being a noob
Click to expand...
Click to collapse
Sounds like you havent installed it to CMD. Instead you can type cd C:/(name of adb directory) and hit enter, now adb commands should work. If you don't know what adb is do some research before messing with it
Sent from my rooted P880
I think that I need a little help with this process. I've entered the "Bootloader unlock mode" where I can see the warranty disclaimer etc, pressed "Vol Up" key to accept the terms and to continue with the process...after that, a red text appeared - "Download mode !!!". What should I do now, enter some commands in adb or...?
teddyxfire said:
I think that I need a little help with this process. I've entered the "Bootloader unlock mode" where I can see the warranty disclaimer etc, pressed "Vol Up" key to accept the terms and to continue with the process...after that, a red text appeared - "Download mode !!!". What should I do now, enter some commands in adb or...?
Click to expand...
Click to collapse
just do nothing the phone is making a factory reset and will reboot when it's done.
if it doesn't reboot itself, but says that it's done, just pull the battery and boot it manually
Ok I got 'unlock permission denied' si I cannot unlock or what i'm supposed to do?
laufersteppenwolf said:
just do nothing the phone is making a factory reset and will reboot when it's done.
if it doesn't reboot itself, but says that it's done, just pull the battery and boot it manually
Click to expand...
Click to collapse
Is it normal that this process takes a long time to complete? I think that it's been running for about 15 minutes now...
teddyxfire said:
Is it normal that this process takes a long time to complete? I think that it's been running for about 15 minutes now...
Click to expand...
Click to collapse
it was done in about 15 sec for me... try pulling the battery and boot it up. if it's unlocked, be happy, if not, try it again
Hello strange i have unlock denied message but i am on the Eur-xxx software non branded , ( polish software ) is there an option to open it ?:
Related
-This guide is going to help you with step-by-step instructions that will get you an unlocked bootloader on your Nexus 4.
-Keep in mind that unlocking the bootloader will erase all the data on your phone (every single thing, including internal storage), hence it is preferable to unlock the bootloader when the phone is new, as then you don’t have to go through the hassle of re-installing everything.
Compatibility
This guide is applicable only for the LG Nexus 4. Do not try this on any other device.
Warning!
The methods and procedures discussed here are considered risky and you should not attempt anything if you don’t know completely what it is. If any damage occurs to your device, I won’t be held liable.
How to Unlock Bootloader on Nexus 4
1. Backup everything on your phone, including the data on the internal storage, as unlocking the bootloader will erase every single thing on the phone.
2. Download and install the Android SDK → from here. This will install the necessary drivers for the phone on your computer. ( The drivers for your phone can be installed manually by other methods too, they are mandatory ) For the fastboot driver to install (and for fastboot commands to work), your device must be booted in fastboot mode.
3. Download Fastboot, which will be used for unlocking the bootloader.
Download Fastboot here .
4. Extract the Fastboot.zip file on your computer to get a folder named Fastboot with four files inside it. To keep things easy, extract the Fastboot folder to your C: drive.
5. Turn off your Nexus 4. Then, boot into fastboot mode by holding down the Volume down and Power buttons together till the screen turns on and shows “Start” written in big green letters.
6. Then, connect your Nexus 4 to the computer with your USB cable, then wait for Windows to finish installing the drivers (drivers will be installed only the first time). For reliability, ensure that you use a USB port at the back if you are using a desktop computer, as the front panel ports can be loose and cause problems.
7. Click on Start menu » All Programs » Accessories » right-click on Command Prompt and click on Run as administrator. If you are using Windows 8, this can be done by right-clicking on the extreme bottom left corner of the taskbar, then selecting “Command Prompt (admin)”
8. Now, perform the following steps in the command prompt to unlock the bootloader (check the screenshot after step 8.3 for reference)
8.1. Navigate to the Fastboot folder which you obtained in step 4. For example, if the Fastboot folder is in drive C on your computer, enter cd C:\Fastboot in command prompt (and press Enter) to navigate to the folder.
8.2. Then, enter fastboot devices. If your Nexus 4 has been detected properly, you will see a device ID show up in command prompt. If nothing comes up, make sure you have installed the drivers (step 2).
8.3. Finally, to unlock the bootloader, enter fastboot oem unlock in command prompt. You will get a prompt on the phone asking whether you want to unlock the bootloader. Just select Yes. Remember that this will wipe all your data, so make sure you took a backup.
{
"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"
}
9. The phone will then reboot, and once it starts up, you can set up your phone.
10. To re-lock the bootloader, simply follow the entire procedure again from step 5 to 8, but in step 8.3, enter fastboot oem lock. This will re-lock the bootloader.
The bootloader on your Nexus 4 is now unlocked, and you can start installing custom ROMs and make other modifications to the phone. Have fun!
SOURCE
. . .anticpating the release date for purchasing . .
TheDarkDefender said:
-This guide is going to help you with step-by-step instructions that will get you an unlocked bootloader on your Nexus 4.
-Keep in mind that unlocking the bootloader will erase all the data on your phone (every single thing, including internal storage), hence it is preferable to unlock the bootloader when the phone is new, as then you don’t have to go through the hassle of re-installing everything.
Compatibility
This guide is applicable only for the LG Nexus 4. Do not try this on any other device.
Warning!
The methods and procedures discussed here are considered risky and you should not attempt anything if you don’t know completely what it is. If any damage occurs to your device, I won’t be held liable.
How to Unlock Bootloader on Nexus 4
1.Backup everything on your phone, including the data on the internal storage, as unlocking the bootloader will erase every single thing on the phone.
2.Download and install the Android SDK → from here. This will install the necessary drivers for the phone on your computer.
3.Download Fastboot, which will be used for unlocking the bootloader.
Download Fastboot here
4.Extract the Fastboot.zip file on your computer to get a folder named Fastboot with four files inside it. To keep things easy, extract the Fastboot folder to your C: drive.
5.Turn off your Nexus 4. Then, boot into fastboot mode by holding down the Volume down and Power buttons together till the screen turns on and shows “Start” written in big green letters.
6.Then, connect your Nexus 4 to the computer with your USB cable, then wait for Windows to finish installing the drivers (drivers will be installed only the first time). For reliability, ensure that you use a USB port at the back if you are using a desktop computer, as the front panel ports can be loose and cause problems.
7.Click on Start menu » All Programs » Accessories » right-click on Command Prompt and click on Run as administrator. If you are using Windows 8, this can be done by right-clicking on the extreme bottom left corner of the taskbar, then selecting “Command Prompt (admin)”
8.Now, perform the following steps in the command prompt to unlock the bootloader (check the screenshot after step 8.3 for reference)
8.1.Navigate to the Fastboot folder which you obtained in step 4. For example, if the Fastboot folder is in drive C on your computer, enter cd C:\Fastboot in command prompt (and press Enter) to navigate to the folder.
8.2Then, enter fastboot devices. If your Nexus 4 has been detected properly, you will see a device ID show up in command prompt. If nothing comes up, make sure you have installed the drivers (step 2).
8.3Finally, to unlock the bootloader, enter fastboot oem unlock in command prompt. You will get a prompt on the phone asking whether you want to unlock the bootloader. Just select Yes. Remember that this will wipe all your data, so make sure you took a backup.
9.The phone will then reboot, and once it starts up, you can set up your phone.
10.To re-lock the bootloader, simply follow the entire procedure again from step 5 to 8, but in step 8.3, enter fastboot oem lock. This will re-lock the bootloader.
The bootloader on your Nexus 4 is now unlocked, and you can start installing custom ROMs and make other modifications to the phone. Have fun!
SOURCE
Click to expand...
Click to collapse
Exact same as Nexus S and GNex: Go to bootloader, run "fastboot oem unlock"
Waiting to get my hands on the new Nexus 4. I'll be back soon. \m/
Sent from my GT-N7000 using xda premium
Guides go in the "General" section
jacklebott said:
Guides go in the "General" section
Click to expand...
Click to collapse
what? this is development related. I did check a few other device forums before I posted here. Guides like rooting,unlocking,etc. always are in the dev section. Let the moderator decide that.
this is awesome, but any way for a mac version?
thanks
I'm going to be doing this as soon as I get my N4. Hopefully they get sold out so I can wait a few days and CM will be released so I won't have to worry about setting everything up coming from stock
killman2659 said:
I'm going to be doing this as soon as I get my N4. Hopefully they get sold out so I can wait a few days and CM will be released so I won't have to worry about setting everything up coming from stock
Click to expand...
Click to collapse
How can you be sure that the CM devs got their phones? I don't think they have special channels do they?
On a separate note,
Awesome. First thing to do when I get that thing delivered. (and hopefully don't brick it.)
Correct me if I'm wrong, but you can root without unlocking the bootloader, right? If so, why the need?
eep2378 said:
Correct me if I'm wrong, but you can root without unlocking the bootloader, right? If so, why the need?
Click to expand...
Click to collapse
Only if the security isn't good enough.
FISKER_Q said:
Only if the security isn't good enough.
Click to expand...
Click to collapse
An example being.....? I guess I'm just looking for clarification. Why not just root then flash custom roms, kernels, etc? I've never owned a Nexus device so never really needed to unlock bootloader.
eep2378 said:
An example being.....? I guess I'm just looking for clarification. Why not just root then flash custom roms, kernels, etc? I've never owned a Nexus device so never really needed to unlock bootloader.
Click to expand...
Click to collapse
To get root you need root access, this does not come standard with Android, therefor the only supported way to get root access is by unlocking the bootloader, flashing an insecure boot image and installing the superuser files manually. A locked bootloader should prevent flashing of the insecure boot image, and Linux should prevent unauthorized users from becoming root, in the case of Android that means everybody.
However that is of course far from the reality, there are various vulnerabilities in the Linux Kernel and Android that can allow elevation which in turn then allows installation of the superuser binaries and the superuser android app. That in turn will usually allow flashing of custom recoveries, but a properly locked/secure bootloader can actually prevent changes to those partitions regardless of root access, i believe there's been a few of such devices in the past.
That's what I figured. Thanks. My current device(s2) there was no need to unlock bootloader to gain root access.
This should be stickied.
Ajfink said:
This should be stickied.
Click to expand...
Click to collapse
I have requested the moderator. I haven't received a reply yet.
What do you suggest I backup with? I thought a full nandroid backup could only be done once rooted?
Sent from my Galaxy Nexus using xda premium
*** Please remove***
TheDarkDefender said:
well..for starters,you could use titanium backup. And you can take a nand backup after rooting,which doesn't require unlocking.
Click to expand...
Click to collapse
That post is confusing since you need to be unlocked to gain root.
Sent from my Galaxy Nexus using Tapatalk 2
*** Disregard ***
hello guys
i have moto nexus 6 xt1100 int i think its 6.0
i cant unlock boot loader i tried with SkipSoft ToolKit and with nexus root toolkit and with fastboot but not work
any help
thanx
:silly:
Questions that say effectively "I have a problem" but don't say what exactly you've done to resolve it have no chance of being answered.
Start with fastboot. What did you do?
dahawthorne said:
Questions that say effectively "I have a problem" but don't say what exactly you've done to resolve it have no chance of being answered.
Start with fastboot. What did you do?
Click to expand...
Click to collapse
hello sir
thanx to replay
i do
fastboot oem unlock
C:\Users\pc\Desktop\platform-tools>fastboot flashing unlock
...
FAILED (remote: Unknown command)
finished. total time: 0.002s
C:\Users\pc\Desktop\platform-tools>fastboot oem unlock
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.006s
C:\Users\pc\Desktop\platform-tools>
The answer is in the output. You must go into Settings > Developer Options and select "Enable OEM Unlock" before you can unlock the bootloader.
i cant go to setting to open oem lock becuase pbone after upgrade ota 60 now cant open still hung google nexus screen plz hlp plz
any one help me plz
Can't you get into twrp and do a restore of made backup? Then after booting go to Developer Options and select "Enable OEM Unlock" then unlock the bootloader and leave it unlocked and leave the OEM Unlock setting in Developer options enabled.
TMG1961 said:
Can't you get into twrp and do a restore of made backup? Then after booting go to Developer Options and select "Enable OEM Unlock" then unlock the bootloader and leave it unlocked and leave the OEM Unlock setting in Developer options enabled.
Click to expand...
Click to collapse
im sorry to late phone is locked plz be fix and not open just google screen not work even after wip frm recvry
Do you have TWRP installed? If so, move a custom rom zip to the phone and flash it in TWRP. After that you can boot the phone and enable OEM unlock and proceed to unlock your phone (and then flash stock or whatever you would like to use). Your phone will be wiped (no way to save your data anyway, unless you have a previous backup), but it'll work.
If you only have stock recovery, you are out of luck and have a nice new desk ornament.
Didgeridoohan said:
Do you have TWRP installed? If so, move a custom rom zip to the phone and flash it in TWRP. After that you can boot the phone and enable OEM unlock and proceed to unlock your phone (and then flash stock or whatever you would like to use). Your phone will be wiped (no way to save your data anyway, unless you have a previous backup), but it'll work.
If you only have stock recovery, you are out of luck and have a nice new desk ornament.
Click to expand...
Click to collapse
No, if he's on stock he can sideloade the N preview one OTA through ADB in stock recovery. Doesn't need fastboot for the OTA zip. The links somewhere here. After that he can enroll in the N preview program and then select the option to either unenroll or roll back I can't remember what it is. It will then push an OTA for the latest 6.0.1.
Harry44 said:
No, if he's on stock he can sideloade the N preview one OTA through ADB in stock recovery. Doesn't need fastboot for the OTA zip. The links somewhere here. After that he can enroll in the N preview program and then select the option to either unenroll or roll back I can't remember what it is. It will then push an OTA for the latest 6.0.1.
Click to expand...
Click to collapse
True... Didn't think of that. That's a good workaround until N is released.
Harry44 said:
No, if he's on stock he can sideloade the N preview one OTA through ADB in stock recovery. Doesn't need fastboot for the OTA zip. The links somewhere here. After that he can enroll in the N preview program and then select the option to either unenroll or roll back I can't remember what it is. It will then push an OTA for the latest 6.0.1.
Click to expand...
Click to collapse
hello sir
again so sorry to late and thanx to replay
i think no bady undrstand my prob my brop is after update ota 60 phone was like photo under long time all day just like this photo oky i do wip data factory reset from recovery not work
and i tried to flash other fimrware from all toolkit nexus but need unlock boot but cant unlock
please can u help me
im here wating every bady
{
"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"
}
please brothers help me
------------------------------------------------------------------------------------
Follow the Instructions on the devices screen to Unlock your BootLoader.
Enable the developer options screen by going to the settings, about screen and
clicking on build number at the bottom 7 times. Then go to developer options and
tick USB debugging so the procedure to continue.
If you get stuck on 'Waiting for USB debugging to be enabled' and have already
enabled USB debugging then just unplug/replug the usb cable and it should proceed.
IF NOTHING HAPPENS TRY PULLING DOWN THE NOTIFICATION SCREEN AT THE TOP LEFT WITH
THE DEVICE CONNECTED, THEN CLICK ON 'CONNECTED AS' AND CHANGE TO PTP MODE.
On Android 4.2 or later when you replug the usb cable after enabling usb debugging
for the first time you will get a popup asking you to authenticate your pc.
Tick 'Always allow' then click 'ok' and everything should carry on as normal.
LASTLY BEFORE STARTING, LOOK IN DEVELOPER OPTIONS IF YOU NEED TO CHECK THE
'ENABLE/ALLOW OEM UNLOCKING' OPTION TO ALLOW THE DEVICE TO BE BOOTLOADER UNLOCKED.
------------------------------------------------------------------------------------
Are you ready to start? Type y[yes] or n[no]:y
Device detected in FASTBOOT MODE
Device Serial Number is: ZX1G4244LL
When prompted, Press the 'Volume up' button to highlight Yes on the screen, then
press the 'Power' button to select it and Unlock your Bootloader. If you are
already unlocked then this will just be skipped and your device will not be wiped.
ERROR: The device cannot be bootloader unlocked in its present state
You need to enable OEM Unlock in developer options in Developer options..
Once the device has rebooted to Android do this and the Unlock routine should work
any help
Ok... You need to stop trying to unlock your bootloader. You can't.
You have a couple of options:
1 - If you have TWRP recovery installed, flash a custom rom and you'll be good to go.
2 - If you do not have a custom recovery, try flashing the N OTA from here: http://developer.android.com/preview/download-ota.html. After that, go here https://www.google.com/android/beta and enroll and then unenroll your device. Soon after (up to a day, probably) you'll get an OTA for Marshmallow.
You might want to unlock your bootloader while you're in the N preview, so you won't have to go through this again...
Edit: Reading your post again I realised you probably don't have TWRP installed, since you wouldn't have gotten that far with an OTA in that case.
C:\android>adb sideload <ota-package>
The syntax of the command is incorrect.
C:\android>
thanx to replay
but not work with me cannot read update zip:crying:
I'm assuming you know the basics here, so I'm not going to go into much detail.
Before starting, make sure you have the ADB drivers installed and have ADB in a directory on the PC.
Rename the OTA file to something simple, e.g. n6ota.zip.
Go here and follow the steps, including the Option 2 instructions here to factory reset the device.
After the factory reset, enter recovery once again and make sure the recovery is set to adb sideload mode. If you don't have it set to this mode the OTA will not install.
Open a command prompt in the directory where ADB is located and type "adb sideload [filename.zip]", replacing filename.zip with the name of the OTA file. For example, using the name I gave above for the OTA file, the command would be "adb sideload n6ota.zip".
Strephon Alkhalikoi said:
I'm assuming you know the basics here, so I'm not going to go into much detail.
Before starting, make sure you have the ADB drivers installed and have ADB in a directory on the PC.
Rename the OTA file to something simple, e.g. n6ota.zip.
Go here and follow the steps, including the Option 2 instructions here to factory reset the device.
After the factory reset, enter recovery once again and make sure the recovery is set to adb sideload mode. If you don't have it set to this mode the OTA will not install.
Open a command prompt in the directory where ADB is located and type "adb sideload [filename.zip]", replacing filename.zip with the name of the OTA file. For example, using the name I gave above for the OTA file, the command would be "adb sideload n6ota.zip".
Click to expand...
Click to collapse
apply update from ADB
not work
{
"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"
}
This is my first walkthrough so I will do my best to do this properly. The Honor Note 8 does not have a forum yet, and this is the third thread for this phone. Hopefully we can get a forum up soon.
PLEASE NOTE THAT UNLOCKING BOOTLOADER WILL WIPE YOUR DEVICE AND POSSIBLY VOID YOUR WARRENTY!!!
I'M NOT RESPONSIBLE IF SOMETHING DOESN'T WORK.
Unlock Bootloader
Follow the steps here to begin the Bootloader Unlock process:
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
1. a) Install the application
1. b) Follow the steps on the above page to put phone into "Manufacture Mode"
1. c) Under "Select Manufacturer", choose "Huawei Phones" and under "Select Model", choose the model of your phone
1. d) Click on "Buy Credits". You should end up being emailed a username and password, return to the Unlocker Client, and input those two
1. e) The Unlocker Client should return the bootloader unlock code
2. a) Enable Developer Options by clicking on the build number multiple times
2. b) Turn on USB Debugging
3. Prepare TWRP custom recovery before preceeding further. You can get it from here: https://drive.google.com/open?id=0B4xzs81XsmURVTRnUDJHdl9CQlE
3. Prepare and install ADB and Fastboot tools. I used this one http://forum.xda-developers.com/showthread.php?t=2588979
4. Go into the folder with your recovery and open a CMD (if you used system-wide ADB as linked above, otherwise place recovery in your ADB folder)
5. Put the phone into Bootloader mode with:
Code:
adb reboot bootloader
. This will take you to the bootloader mode (white screen with some small text)
6. Now type:
Code:
fastboot oem unlock <UNLOCK_CODE>
where
Code:
<UNLOCK_CODE>
is the bootloader code that the Unlocker Client gave you
Loading TWRP Custom Recovery
7. Your phone may reboot when the process is complete. We want to go back into Bootloader mode, so follow Step 5 again to go back to bootloader mode
8. Now type:
Code:
fastboot flash recovery <NAME_OF_YOUR_RECOVERY.img>
The recovery will flash over to your device. We want to reboot into the recovery mode.
9. Now type:
Code:
fastboot reboot
but just before you hit ENTER on that command, start holding VOLup and VOLdown at the same time (as explained below)
This phone has two recoveries on it, which is great since it makes it really hard to brick. In order to access custom recovery, you need to hold down both VOL buttons during boot process (from the very beginning) in order to access the custom recovery.
Once you have entered TWRP, you will most likely notice that it is in CHINESE. If you don't read chinese, follow the steps below to change to English UI in TWRP:
Change to English UI in TWRP
10. TWRP has two columns of 4 buttons, 8 buttons total. I have labeled the buttons as per their position as below:
1 2
3 4
5 6
7 8
11. Click button 6 to go to the Settings, then click on the "Globe" icon, then switch to english and click the button in the bottom right corner.
BACKUP!!
12. I highly recommend you now do a TWRP backup and place the backup on an External SD card (not the internal memory). This will save your ass if you mess anything up or it doesn't work for you. Do a full backup (select ALL of the options).
Installing Xposed
Grab the Installer APK here: http://forum.xda-developers.com/showthread.php?t=3034811
and the Framework zip here: http://dl-xda.xposed.info/framework/sdk23/arm64/
Put both files onto your SD card.
13. Boot into your rom, install the APK file (you may need to enable "unknown sources")
14. Then boot back into TWRP. Do this by restarting the phone, and just as the screen goes black, hold down both VOL buttons until you see text on the screen.
15. Install the framework, wipe cache/dalvik and reboot the phone
ROMs
There are several roms, all of which can be found here: http://forum.xda-developers.com/general/general/huawei-honor-note-8-roms-t3487575
I will try to update this post with instructions on how to install them once I have the process down properly.
Thanks to:
@benmeroff for his posting of all of those ROMs and his work on the original thread.
The link to the xposed installer is dead
jdantow said:
Installing Xposed
Grab the Installer APK here: http://forum.xda-developers.com/show....php?t=3034811
Click to expand...
Click to collapse
Just another small reminder this Xposed apk link is broken. Could I just download any Xposed apk or was this link for a specific version for the Note 8?
Thanks
remix435 said:
The link to the xposed installer is dead
Click to expand...
Click to collapse
Thank you! I updated the link, can you confirm it is working now from your end? Thanks so much!
The thread ID is 3034811 so if you take
Code:
http://forum.xda-developers.com/showthread.php
and add
Code:
?t=3034811
it should work for you
jlomein said:
Just another small reminder this Xposed apk link is broken. Could I just download any Xposed apk or was this link for a specific version for the Note 8?
Thanks
Click to expand...
Click to collapse
Thank you! I updated the link, can you confirm it is working now from your end? Thanks so much!
The thread ID is 3034811 so if you take
Code:
http://forum.xda-developers.com/showthread.php
and add
Code:
?t=3034811
it should work for you
Hopefully either a camera port or a camera hack can come about from developing. Anybody know about possible camera hack thats the only thing (IMO) this phone needs
jdantow said:
Thank you! I updated the link, can you confirm it is working now from your end? Thanks so much!
Click to expand...
Click to collapse
Thanks, downloaded Xposed 3.1.1 apk from that link now.
Cheers
hi
after i flashed trwp and did back up i stuck in bootloop
tried to flash kingvip rom - no luck. tried to recover from back up but stil in boot loop.
can anyone help me, please
Anyone happen to have the img for the modem? I believe mine may be corrupted.
hi i will my boodloader unlock my Note 8. The phone will not unlock. I have the ulock key. I hvae the Build Nummber B027.
Hi guys, a question...
The is no way I can install this drivers that are required... if I click the setup icons nothing happens at all, and if i try manually all i get is 4x "Android device" in the device manager, and locating drivers in the designated folders does not help, it still says "windows did not find the driver for your device...."
Anyone maybe had a similar problem/solution?
Thanksss
Bubreg said:
Hi guys, a question...
The is no way I can install this drivers that are required... if I click the setup icons nothing happens at all, and if i try manually all i get is 4x "Android device" in the device manager, and locating drivers in the designated folders does not help, it still says "windows did not find the driver for your device...."
Anyone maybe had a similar problem/solution?
Thanksss
Click to expand...
Click to collapse
Just google huawei drivers.... I had the same question but when i installed HiSuite the drivers was inside - it work fine, but it will always pop up when you connecting phone...
falc1 said:
Just google huawei drivers.... I had the same question but when i installed HiSuite the drivers was inside - it work fine, but it will always pop up when you connecting phone...
Click to expand...
Click to collapse
Thank you man, worked like a charm! I got the bootloader code... but since it's gonna wipe everything if I unlock it, I'm gonna wait until the next weekend most probably, too busy these days.
Hi guys,
i was able to unlock the bootloader but i can't flash the recovery and every time i try it display "remote: command not allowed".
Good morning.
I hope for Christmas to be a holder of Honor Note 8.
To unlock the bootloader you need to pay 4 euro through dc-unlocker.com program?
Thank you
m3sari0 said:
Hi guys,
i was able to unlock the bootloader but i can't flash the recovery and every time i try it display "remote: command not allowed".
Click to expand...
Click to collapse
Same thing happend to me
I relocked the bootloader then unlock it again and it works
player1990 said:
Same thing happend to me
I relocked the bootloader then unlock it again and it works
Click to expand...
Click to collapse
thanks man it worked.
TWRP - changing language
OP - thank you for this thread. Was able to follow the steps and get most of the things accomplished.
One thing that i am having trouble with is - changing the TWRP language from Chinese to English. In button #6, the globe icon is not even clickable. All others are, but that one is not. Any ideas? Thanks!
EDIT: I got it to work. It seems some icons in the corners of the screen can be a little hard or slow to respond... if you (a future reader) are having the same issue - try kind of mini swiping in circles over that icon and it will eventually respond.
Hi,
I requested the unlock code on the Huawei site but I get this error:
The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.
How can I do?
Some might apply to me
MarkAndroid said:
Hi,
I requested the unlock code on the Huawei site but I get this error:
The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.
How can I do?
Some might apply to me
Click to expand...
Click to collapse
You have to wait 14 days or pay for the credits on DC-unlocker app
Hey,
I just received an old tablet (SM-T813) that the IT department at work was selling off. However, when I went to setup the tablet, I was met with the Google Verification Screen. I went to the department and they had no idea whose email it previously belonged to so there is no way I can find out who to reach out to to sign in. I have looked online and seen the old ways to bypass it but it seems they've all been patched. I tried
1.) Turn off hot spot when it says software update
2.) Use rootjunky/Realterm to open dialer (I have wifi only so dialer doesnt show up)
3.) Sidesync (Doesnt show up on phone even though phone is recognized on computer)
4.) I have tried using Odin and flashing the newest firmware from Sammobile but the verification screen still shows up during setup
5.) Access to get to settings from Google keyboard or Voice doesnt seem to work.
I know this has been posted before but I wanted to know if there has been any new tricks or tips since new patches have come out. I'm running 6.0.1 Marshmellow and just want to be able to use this tablet. I dont have any data on it so I am willing to 100% wipe it. Thanks
skatekid1792 said:
Hey,
I just received an old tablet (SM-T813) that the IT department at work was selling off. However, when I went to setup the tablet, I was met with the Google Verification Screen. I went to the department and they had no idea whose email it previously belonged to so there is no way I can find out who to reach out to to sign in. I have looked online and seen the old ways to bypass it but it seems they've all been patched. I tried
1.) Turn off hot spot when it says software update
2.) Use rootjunky/Realterm to open dialer (I have wifi only so dialer doesnt show up)
3.) Sidesync (Doesnt show up on phone even though phone is recognized on computer)
4.) I have tried using Odin and flashing the newest firmware from Sammobile but the verification screen still shows up during setup
5.) Access to get to settings from Google keyboard or Voice doesnt seem to work.
I know this has been posted before but I wanted to know if there has been any new tricks or tips since new patches have come out. I'm running 6.0.1 Marshmellow and just want to be able to use this tablet. I dont have any data on it so I am willing to 100% wipe it. Thanks
Click to expand...
Click to collapse
I'll come back to you in a bit. I'm at work right now. I have something you can try.
Which firmware build are you running?
I was able to reset a tab A SM-T580 as your description in (1), however after a software upgrade, I test this method again and it failed. Samsung fix it by not letting me continue without Wifi connection to verify the Google account. You can try but I am not able to find the newest working method to bypass this FRP. I did more than 10 times but failed miserably until using my ID and password used with this tablet to unlock it.
Anyway, if you don't mind pay $10 for someone do the work
http://www.ebay.com/itm/Remote-Goog...848348?hash=item4b07596d1c:g:EYoAAOSwmfhX73K8
ashyx said:
I'll come back to you in a bit. I'm at work right now. I have something you can try.
Which firmware build are you running?
Click to expand...
Click to collapse
When I boot to the recovery screen it says I'm running 6.0.1/MMB29M/T813XXU2APK6.
skatekid1792 said:
When I boot to the recovery screen it says I'm running 6.0.1/MMB29M/T813XXU2APK6.
Click to expand...
Click to collapse
1. Install T813XXU1APD4_eng_boot.tar via ODIN
The device should boot with ADB Enabled. Connect the USB cable and use the command below using ADB in a Terminal. I suggest to copy and paste.
adb devices
adb shell netcfg
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
2. Now Open Settings and then from about menu tap 7 times on build number to get devolper mode enabled . Enable OEM Unlocking, now Factory Reset From Settings .
3. If Above command does not work try the following commands:
adb shell am start -n com.google.android.gsf.login/
or
adb shell am start -n com.google.android.gsf.login.LoginActivity
You can also try the tool below after installing the eng boot:
GSM Flasher ADB Bypass FRP Tool
.
Does your file work only for the T813 ? When install using Odin, it's for BL or AP ?
Beut said:
Does your file work only for the T813 ? When install using Odin, it's for BL or AP ?
Click to expand...
Click to collapse
Yes T813, flashed in AP.
Why do you ask?
I tried to flash the ADB enable file which for SM-T580 and it failed to install
FRP is enable, not allow to download non-FRP boot binary
{
"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"
}
Beut said:
I tried to flash the ADB enable file which for SM-T580 and it failed to install
FRP is enable, not allow to download non-FRP boot binary
Click to expand...
Click to collapse
Where did you get it and which firmware is your device running?
ashyx said:
Where did you get it and which firmware is your device running?
Click to expand...
Click to collapse
My current firmware is the latest AP_T580UEU2APL4 for Tab A 10.1, SM-T580. It seems Samsung has patched all loopholes from recent update. I have tried various methods but none is working.
The enable ADB I downloaded from here
http://www.gsmplayer.com/adb-enable-files/
Beut said:
My current firmware is the latest AP_T580UEU2APL4 for Tab A 10.1, SM-T580. It seems Samsung has patched all loopholes from recent update. I have tried various methods but none is working.
The enable ADB I downloaded from here
http://www.gsmplayer.com/adb-enable-files/
Click to expand...
Click to collapse
So what is your current status, you are blocked at Google verification?
Can you post that file so I can take a look?
ashyx said:
So what is your current status, you are blocked at Google verification?
Can you post that file so I can take a look?
Click to expand...
Click to collapse
Yes it's blocked at Google verification, the new firmware will not allow to go further without internet connection. Reconnect, it will go back to previous steps until the step of Google verification,
ashyx said:
1. Install [] via ODIN
The device should boot with ADB Enabled. Connect the USB cable and use the command below using ADB in a Terminal. I suggest to copy and paste.
adb devices
adb shell netcfg
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
2. Now Open Settings and then from about menu tap 7 times on build number to get devolper mode enabled . Enable OEM Unlocking, now Factory Reset From Settings .
3. If Above command does not work try the following commands:
adb shell am start -n com.google.android.gsf.login/
or
adb shell am start -n com.google.android.gsf.login.LoginActivity
You can also try the tool below after installing the eng boot:
[]
.
Click to expand...
Click to collapse
After I flash T813XXU1APD4_eng_boot.tar with Odin onto my tablet, it gets stuck in a boot loop. When I power it on, it shows the Samsung Logo screen and then the battery power screen. I cant get the setup process to start so that I can use a Terminal to type in those commands.
skatekid1792 said:
After I flash T813XXU1APD4_eng_boot.tar with Odin onto my tablet, it gets stuck in a boot loop. When I power it on, it shows the Samsung Logo screen and then the battery power screen. I cant get the setup process to start so that I can use a Terminal to type in those commands.
Click to expand...
Click to collapse
Looks like the boot.img is not compatible with your firmware build.
I'll see what I can do about getting the up to date eng boot.
skatekid1792 said:
After I flash T813XXU1APD4_eng_boot.tar with Odin onto my tablet, it gets stuck in a boot loop. When I power it on, it shows the Samsung Logo screen and then the battery power screen. I cant get the setup process to start so that I can use a Terminal to type in those commands.
Click to expand...
Click to collapse
If you need the stock BL ( Boot Loader ) , use Odin and load it to BL, then start.
http://www.mediafire.com/file/7k0ohync9eeslnb/SM-T813+Bootloader.rar
BL_T813XXU2APK6_CL9829844_QB11715585_REV00_user_low_ship_MULTI_CERT.tar
Beut said:
If you need the stock BL ( Boot Loader ) , use Odin and load it to BL, then start.
http://www.mediafire.com/file/7k0ohync9eeslnb/SM-T813+Bootloader.rar
BL_T813XXU2APK6_CL9829844_QB11715585_REV00_user_low_ship_MULTI_CERT.tar
Click to expand...
Click to collapse
even with the boot loader put into Oden, it is still having the same issues.
skatekid1792 said:
even with the boot loader put into Oden, it is still having the same issues.
Click to expand...
Click to collapse
You can try the AP and BL, AP is from Sammobile. If it works fine before, it should boot normally after re flash the stock AP and BL.
ashyx said:
Looks like the boot.img is not compatible with your firmware build.
I'll see what I can do about getting the up to date eng boot.
Click to expand...
Click to collapse
where could I find the eng boot that is compatible with my firmware build? Even when I recovery boot and go to the "apply update from adb", the commands I run all say error:closed in the terminal
I'm in the same boat sm-t580 usa version with a frp lock and since it doesn't have a sim you can't get the dialer to work or any of the other techniques. The question is will it let you via odin downgrade the software or not. Are there any other things to try to get a browser window to pop up, even if I could get the sandbox browser I usually can get past that but right now I can't get anything to work.
thanks
Update I downgraded to an earlier august release via Odin but still none of the old ways to break in are working, anyone have any suggestions please let me know.
Thanks
STORY: My TA-1004 autoupdate to Android Pie on 22Dec after I turn off my phone to charge battery.
and I follow this " https://forum.xda-developers.com/nokia-8/development/android-9-0-pie-patched-boot-img-t3875977 " to try flash "fastboot flash boot "NB-01-551-b05-Magisk-TWRP" for flash TWRP and magisk to my TA-1004 pie. and I stuck on "nokia logo" after flash, someone said "Factory reset" , I try to use "wipe>format data" in TWRP, until now, I can boot in to download mode only.
I also try this "https://forum.xda-developers.com/nokia-8/how-to/guide-restore-nokia-to-stock-t3867646 "
to restore to oreo and stuck on "Next is greyed out, click on "Edit Phone Information", you will get an error message after a while, clik on OK, BUT Next is still greyed" . Can anyone help me please?
Please check that you have the correct fastboot drivers installed. Open Windows Device manager, and check the properties of your Fastboot device. Do you see HMD Global as the manufacturer? If not, the drivers may not be correct and you should install the Nokia drivers.
singhnsk said:
Please check that you have the correct fastboot drivers installed. Open Windows Device manager, and check the properties of your Fastboot device. Do you see HMD Global as the manufacturer? If not, the drivers may not be correct and you should install the Nokia drivers.
Click to expand...
Click to collapse
thx for reply first,
I can check "Fastboot Device" in Windows Device manager , HMD Global as the manufacturer.
I can check "fastboot devices" by adb/fastboot.exe
kelvin31 said:
thx for reply first,
I can check "Fastboot Device" in Windows Device manager , HMD Global as the manufacturer.
I can check "fastboot devices" by adb/fastboot.exe
Click to expand...
Click to collapse
It should work in that case. Give a try to the NOST tool shared in the Nokia 8 forums itself.
singhnsk said:
It should work in that case. Give a try to the NOST tool shared in the Nokia 8 forums itself.
Click to expand...
Click to collapse
NOST is it means Nokia OST (Online Service Tool) latest version and I need download android pie rom first?
kelvin31 said:
NOST is it means Nokia OST (Online Service Tool) latest version and I need download android pie rom first?
Click to expand...
Click to collapse
NOST" - short for "No Service Tool"
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
You should use the existing NB0 which you have for the Nokia 8. I think it is on Oreo only. I hope you do have it.
singhnsk said:
It should work in that case. Give a try to the NOST tool shared in the Nokia 8 forums itself.
Click to expand...
Click to collapse
singhnsk said:
NOST" - short for "No Service Tool"
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
You should use the existing NB0 which you have for the Nokia 8. I think it is on Oreo only. I hope you do have it.
Click to expand...
Click to collapse
THx
let me study it first,
thank you very much
singhnsk said:
NOST" - short for "No Service Tool"
https://forum.xda-developers.com/no...t-improved-version-ost-la-6-0-4-v0-4-t3875574
You should use the existing NB0 which you have for the Nokia 8. I think it is on Oreo only. I hope you do have it.
Click to expand...
Click to collapse
hello, I m stuck on unlock_critical, do you have any idea?
{
"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"
}
kelvin31 said:
hello, I m stuck on unlock_critical, do you have any idea?
Click to expand...
Click to collapse
You need to be flashing the actual unlock.bin file you used to unlock the Nokia 8. As you see in your CMD window, the command did not work out.
Make sure you're CMDing in the directory of your unlock file. Then send the command
Code:
fastboot flash unlock UnlockFile.bin
Remember to replace UnlockFile.bin with the name of actual unlock file in your PC.
singhnsk said:
You need to be flashing the actual unlock.bin file you used to unlock the Nokia 8. As you see in your CMD window, the command did not work out.
Make sure you're CMDing in the directory of your unlock file. Then send the command
Code:
fastboot flash unlock UnlockFile.bin
Remember to replace UnlockFile.bin with the name of actual unlock file in your PC.
Click to expand...
Click to collapse
unlock.bin is it provide by HMD that one?
I have receive my nokia 8 unlock bootloader file before by HMD,
name called unlock.key
is it this one? should I rename it to unlock.bin ?
thank you
kelvin31 said:
You need to be flashing the actual unlock.bin file you used to unlock the Nokia 8. As you see in your CMD window, the command did not work out.
Make sure you're CMDing in the directory of your unlock file. Then send the command
unlock.bin is it provide by HMD that one?
I have receive my nokia 8 unlock bootloader file before by HMD,
name called unlock.key
is it this one? should I rename it to unlock.bin ?
thank you
Click to expand...
Click to collapse
Yes, that's the one. You don't have to rename it. Just pass it the way you did earlier.
fastboot flash unlock unlock.key
When it gets accepted, then run:
fastboot flashing unlock_critical
singhnsk said:
Yes, that's the one. You don't have to rename it. Just pass it the way you did earlier.
fastboot flash unlock unlock.key
When it gets accepted, then run:
fastboot flashing unlock_critical
Click to expand...
Click to collapse
its work,
I need to flash unlock.key again even I unlocked my bootloader in september.
but I need flash again after auto update..
I also fastboot flashing unlock_critical, work too.
but got another problem.....
NOST tool error code: 0xa24b
ERROR= BATTERY_VOLTAGE_TOO_LOW_FAIL (0xA24B).
I can't charge or very very slow maybe.
I charge it over 1 hour still lower than NOST tool requirement(30%)...
my TA-1004 can not power off since first flash fail....
I keep saw "download mode" over light and I can't power off...
I did try volup + power, it turn off 2 sec and auto start again boot into download mode...
how can I force power off it?
thank you
kelvin31 said:
its work,
I need to flash unlock.key again even I unlocked my bootloader in september.
but I need flash again after auto update..
I also fastboot flashing unlock_critical, work too.
but got another problem.....
NOST tool error code: 0xa24b
ERROR= BATTERY_VOLTAGE_TOO_LOW_FAIL (0xA24B).
I can't charge or very very slow maybe.
I charge it over 1 hour still lower than NOST tool requirement(30%)...
my TA-1004 can not power off since first flash fail....
I keep saw "download mode" over light and I can't power off...
I did try volup + power, it turn off 2 sec and auto start again boot into download mode...
how can I force power off it?
thank you
Click to expand...
Click to collapse
You can power off the phone from the stock recovery or TWRP. That is, if you are able to boot into any of them. If you have the stock recovery file, then flash it to the phone. After that force reboot it and continue to hold the keys and it should go into recovery mode. The phone will essentially start faster in recovery mode. Or you can also choose the "Power off" option in recovery to power off the phone.
If you cannot get into recovery, then you cannot power it off. And in that case you will have to bear this slow charge only. Just plug it into a wall charger and leave it for a few hours. You can then check the battery capacity after connecting to the PC and sending the following command:
Code:
fastboot oem battery getcapacity
Start NOST and flash the phone if it is higher than the required
singhnsk said:
You can power off the phone from the stock recovery or TWRP. That is, if you are able to boot into any of them. If you have the stock recovery file, then flash it to the phone. After that force reboot it and continue to hold the keys and it should go into recovery mode. The phone will essentially start faster in recovery mode. Or you can also choose the "Power off" option in recovery to power off the phone.
If you cannot get into recovery, then you cannot power it off. And in that case you will have to bear this slow charge only. Just plug it into a wall charger and leave it for a few hours. You can then check the battery capacity after connecting to the PC and sending the following command:
Code:
fastboot oem battery getcapacity
Start NOST and flash the phone if it is higher than the required
Click to expand...
Click to collapse
THanks for help.
I charge it over 10 hrs, I did, I can flash NB1-488B Oreo 8.1 back, I can use my phone right now, thank you very much