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.
Related
The best feature of Android - It's open. You can modify Android to have the best performance from your phone. My previous Atrix's hardware had some problem. So I didn't root my/unlock my Atrix. However, after seeing the upcoming CM10 for my set &; a battery friendly ROM yet 100% stable ROM, I finally decided to flash a custom ROM. What's great? I'm successful.
Yesterday, I was determined to unlock my bootloader & flash MROM on it. But I was afraid if I do anything wrong, my phone will not boot. I've not any other phone other than this & it's very precious to me. It's my beloved Atrix. I was unrooted, unlocked. Meant - I didn't do any modification at all. If you're on AT&T 4.5.141 (OTA Upgraded) then this tutorial is for you. (Bell/International users close your tab now!)
I'll not be responsible if you do any harm to your device
(You know the drill )
How to Unlock Motorola Atrix Bootloader (4.5.141) AT&T
I'm a noob. So I was searching for a perfect & easy tutorial. The automatic bootloader unlock seems really confusing to me. So I decided to do it manually. It's more easy &; clear than the automatic version.
I'll be writing this tutorial only for AT&T Atrix running 4.5.141 - Android 2.3.6 version. This tutorial will also work for AT&T 4.5.91 version.
But don't try this on AT&T 4.5.145/Bell/other international version. Once you flash CM7, don't flash Motorola's ROM with SBF. It'll brick the phone..
(Means your phone is dead!)
{
"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"
}
We'll be flashing a custom ROM directly after unlocking the bootloader. So please download a custom rom &; it's Google Apps to your internal memory/SD Card. The main purpose of unlocking bootloader is to flash roms. So I don't care whether Motorola's buggy, laggy, sluggish, default blur ROM works or not.
Pre Requirements
We'll be needing a couple of tools.
We need the drivers for Atrix 4G. Download &; install it from here*(31.60 MB)
We'll need fastboot to unlock. Download fastboot from here (4.73 MB)
We'll need RSDLite. Download RSDLite 5.3.1 (4.33 MB)
Only for AT&T Atrix running 4.5.91/4.5.141 -*We'll need the 1.1 MB Unlocker Only SBF for AT&T Atrix. This tool will make ready your smartphone to unlock via fastboot command.
How to Unlock Bootloader Now?
If you've rooted already, take a backup of your apps with Titanium Backup. If not, then you're gonna loose all your apps.
Unlocking Atrix 4G Bootloader 4.5.141 Step-by-step
First of all, install RSDLite & extract the file*4547-fix-try2.sbf on your desktop.
Extract fastboot to C://fastboot.
Open RSDLite.
Power off your phone. Press power button+volume down together. You'll see a text "fastboot". Then start pressing the volume down again &; and again until you see "RSD". Once it comes, press volume up button. It'll say "Starting RSD Protocol"
You'll see that RSDLite has detected your phone in the menu. (SE Olympus or something like that)
Now Click the "..." button in RSDLite &; navigate the*4547-fix-try2.sbf file from your desktop.
Click Start.
Wait 5/6 minutes It'll restart your phone. You'll maybe see a boot error. (Just ignore it. Cause we're gonna flash a new ROM anyway).
After waiting some minutes, it'll say it's saying "starting fastboot protocol"
We're half done. We've extracted our fastboot files in C://fastboot
Open Command Prompt with Admin Privilege
Code:
Type "cd.."
Code:
Type "cd.."
Code:
Type "cd fastboot"
Type "
Code:
fastboot devices
".You'll see if your devices gets recognized or not.
Now type "
Code:
fastboot oem unlock
it'll give you a unique ID to unlock your phone.
Type "
Code:
fastboot oem unlock "XXXXXXXXXXXX (Unique ID)"
BAAAAMMM!!! WE'RE UNLOCKEDDD BABY!!!!
Flashing ClockWorkMod Recovery
(I've downloaded the latest recovery from romracer from here & placed it into the fastboot folder already)
Reboot your phone into fastboot mode again. (If power button doesn't do it, do a battery pull. To get into fastboot, Press power button+volume *down together until you see fastboot &; then press volume up)We're in the command prompt still.
So write*
fastboot erase recovery
Then write
fastboot flash recovery recovery.img
YAY!!! BOOM! We've flashed unlocked the bootloader & flashed recovery!
To flash a rom now, go to recovery mode (Press power button+volume *down together until you see*fastboot*&; then keep pressing volume down &; until you see "Android Recovery". Once you see it, press volume up.
The ROM flashing guide is easy. Choose install zip from SD card &; select your rom package &; it'll be installed. Reboot to enjoy your first custom ROM
Previously Published on my site http://saifhassan.info!
Emergency AT & T Atrix 4g (2.3.6) 4.5.145 Original 4547-fix-try2.sbf
Friends, let me urgent need to file 4547-fix-try2.sbf. Phone "failed to boot one" has failure. then the first term is no longer soft.As I understand it from RSD lite rom (4547-fix-try2.sbf) need to install. I'm searching, but I could not find. Links are broken. URGENT PLEASE HELP
(I'm sorry for my english is bad.)
saiftheboss7 said:
...BAAAAMMM!!! WE'RE UNLOCKEDDD BABY!!!!...
Click to expand...
Click to collapse
Finally) I'm done! 10ks!
Help please
Bit of help please, get to the step of RSD lite, it says pass. the phone is left on. I turn it off and then back on + volume down and enter fastboot.
the screen says "Starting Fastboot protocol support"
I type in the stuff in cmd and get to "fastboot oem unlock" and the cmd says "-waiting for device-" and sticks there.... for hours if I leave it!
Why?
Please help! In noob form too please
Thanks
ukmed said:
Bit of help please, get to the step of RSD lite, it says pass. the phone is left on. I turn it off and then back on + volume down and enter fastboot.
the screen says "Starting Fastboot protocol support"
I type in the stuff in cmd and get to "fastboot oem unlock" and the cmd says "-waiting for device-" and sticks there.... for hours if I leave it!
Why?
Please help! In noob form too please
Thanks
Click to expand...
Click to collapse
try "fastboot devices" to make sure your device is connected and recognized.
lehjr said:
try "fastboot devices" to make sure your device is connected and recognized.
Click to expand...
Click to collapse
Tried that, nothing happens...
Help!?
ukmed said:
Tried that, nothing happens...
Help!?
Click to expand...
Click to collapse
Make sure you download the USB Driver for WIndows. I posted the link in the OP. Read it thoroughly.
i need help
all my volume buttons are not functioning, how can u help me unlock........
If you have root, you might be able to use adb and the internal reboot command to reboot into various modes (recovery, fastboot...).
Tonyanaky said:
all my volume buttons are not functioning, how can u help me unlock........
Click to expand...
Click to collapse
Just flash TWRP after download, rename it to recovery & replace with the one that comes with fastboot extracted folder.
help
my 4547-fix-try2.sbf failed to work......what do i do???
Can't get any bootloader unlock methods to work?
RSD does nothing when I click start?
Xfire68 said:
Can't get any bootloader unlock methods to work?
RSD does nothing when I click start?
Click to expand...
Click to collapse
***Tip*** I was not able to get any methods to work with a Windows 7 64bit OS with correct drivers. Loaded up a old laptop with 32bit Vista and the Automatic Bootloader Unlock and Root worked perfect.
It seemed to be a issues with RSD Lite? When I would get to that stage RSD would open up but never connected to device. I guess we have to wait a few more years for 64bit to be mainstream?
Some of you are wondering why I am wasting time on this older phone but, I like to by older tech that was once "Top tier" at a bargain price.
Running MROM-Olympus right now and it's pretty nice so far.
Thanks a ton to the DEVs of this program!
Xfire68 said:
***Tip*** I was not able to get any methods to work with a Windows 7 64bit OS with correct drivers. Loaded up a old laptop with 32bit Vista and the Automatic Bootloader Unlock and Root worked perfect.
It seemed to be a issues with RSD Lite? When I would get to that stage RSD would open up but never connected to device. I guess we have to wait a few more years for 64bit to be mainstream?
Some of you are wondering why I am wasting time on this older phone but, I like to by older tech that was once "Top tier" at a bargain price.
Running MROM-Olympus right now and it's pretty nice so far.
Thanks a ton to the DEVs of this program!
Click to expand...
Click to collapse
there is a set of drivers that are for win 7 64 bit that i found early this morning via the droid x forum. I'm not at home right now, but i will post the link here when i do get home. hopefully it helps with issues with this os setup
Edit
File uploaded. even thought it says droid, it should still work
Works for 4.5.141 ?
Hi! Does this method work for Atrix 4G AT&T 4.5.145 as well? I want to get bootloader unlocked of my phone and install any ROM which supports 2-way Call Recording. Kindly suggest a stable ROM also that supports call recording function.
I am bit confused as the thread title says for 4.5.141 only.
Thanks in advance!!! :good:
Hi! No idea. You should see what changes between releases.l and if they can affect the process.
Stable.. it depends on how do you define stable. Roms where everithing works are the ones based on motorola"s stock gb rom.
Without webtop, cm7 (i prefer official unmodified cm7)
Enviado desde mi MB860 usando Tapatalk 2
andresrivas said:
Hi! No idea. You should see what changes between releases.l and if they can affect the process.
Stable.. it depends on how do you define stable. Roms where everithing works are the ones based on motorola"s stock gb rom.
Without webtop, cm7 (i prefer official unmodified cm7)
Click to expand...
Click to collapse
Thanks for your quick reply!
I was wondering if some fellow who successfully unlocked his AT&T Atrix 4G running on OTA 4.5.145 can guide me.
sony108 said:
Thanks for your quick reply!
I was wondering if some fellow who successfully unlocked his AT&T Atrix 4G running on OTA 4.5.145 can guide me.
Click to expand...
Click to collapse
yes, its called read post #1 and delete the recovery.sh in your phone before flashing cwm
I am sitting dead in the water with an EVGA Tegra Note 7 that can't turn on Wireless and won't let me install drivers to move further or even do a restore.
First off I am using Tomsgt Super Tool: http://forum.xda-developers.com/showthread.php?t=2627654
So my device was continuing to fail an OTA update so I was going to use this device to reinstall the basic 4.4.2. However during the process Fastboot.exe gave a failed message in Windows, but it showed fastboot after the device name. I continued to let it Restore Tegra Note 7 to Android 4.4.2 and first of all it did it way too fast and once it was finished I couldn't get the Wireless to enable. I read another person with the same problem that had to redo the process. Well I can't get past reinstalling ADB and Fastboot, now not even ADB..
I tried uninstalling the device from Windows letting it reinstall and then checking it again. No matter what I do the USB Driver Scan fails over and over. I got this issue the first time, but somehow I got it to catch the device once and install ADB.
1) Yes USB Debugging in Enabled
2) Yes Anti-Virus is Off
3) Bootloader unlocked
4) Tried Different USB Ports
So what the hell is going on here?? All I wanted to do was run a damn OTA update.. Now I have a tablet with no wireless and I obviously can't do an OTA update now.
{
"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"
}
I was thinking about not using the tool and doing it all manually like I used to do, but all the tool does is auto execute files/folders in specific orders, basically an elaborate .bat file. So if it is failing at ADB, it is going to fail for me manually too.
Please give me some idea of what to do. I don't see how relocking the bootloader would do anything, but aside from that it was a non-rooted stock 4.4.2 OS running.
Is there something I need to do in order to get Impactor to work?
So then I plug the device into a 9 year old laptop with Windows XP and Impactor sees the device on the first try and installs the driver (it takes 2-3 minutes). Then it finishes and I close impactor, but I get an error next saying device not found. I restart the machine and now it is exactly like my desktop, Impactor can't see the device at all.
What in the hell is going on here? If I had known all this was going to happen I would have skipped their damn OTA update that continued to fail.
BTW with XP I can prevent Windows from installing any type of driver, so I did. Should I let XP search for a driver and see what happens?
Someone throw me some ideas, you can see a full explanation of what is happening if you scroll up to my screenshot. I basically have a dead device because I wanted to use this tool to do a recovery...
Wireless refuses to turn on, it just sits there for hours if I let it.
Someone please give me guidance, I was out of the Android scene for a while and I've forgotten a lot of the tricks I used to know.
If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.
share_needles said:
If your computer is recognizing the fastboot mode that is all you need. Forget the supertool for now.
Can you use the tablet to get into the Fastboot Protocol? It so that will put it in fastboot mode even if it doesn't look like it.
If that works, you can run TWRP or a custom recovery by using ADB and the fastboot command "fastboot boot TWRP_recover.img"
Notice the fastboot "boot", that will only run TWRP once so if you want to on your tablet for good you replace boot with "flash". fastboot flash TWRP_recover.img
You have to make sure the filename is correct with the custom recovery you downloaded.
At this point, put the update you want on your SD card, put that card in the tablet, and go to TWRP or your custom recover and upload the new software.
It sounds complicated but it isn't.
Click to expand...
Click to collapse
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again. I believe there is a quick message that flashes the first time I try to select Fastboot, however it's way too fast to read. When I do it again after that is when I will see a black flash, but apparently from what I have heard that is all Fastboot kernel is supposed to do??
How do I verify Fastboot is working before I flash the damn thing?
NCSUZoSo said:
Thanks for the suggestions, but I don't think Fastboot has completely installed on my tablet. When I hit Fastboot kernel all I get is a black flash and back to the bootloader again.
How do I verify Fastboot is working before I flash the damn thing?
Click to expand...
Click to collapse
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.
share_needles said:
That is what I was saying when I said you wouldn't even know you're in fastboot. The black-screen with message flashes for a milisecond and goes back to the same screen so it looks like nothing happened when it is actually in fastboot mode.
You can verify this by running your super tool and it will say "fastboot device"
Do you know how to use the ADB command prompt?
Using that, I flashed a custom recovery and then put the below 4.3 zip file on my SD card and going through the tablet I used the TWRP custom recovery to upload 4.3 on the tablet.
I used this old backup of 4.3:
Forum post and links: forum.xda-developers.com/showthread.php?t=2580287
Backupfile name: productionbl_signed_tn7_114gp_2923379__4.3.zip
FYI,
I was in your same situation and that worked for me. I could not get my computer to recognize my device in anything other than fastboot mode.
Click to expand...
Click to collapse
Can I get some official links for the newest/compatible versions of TWRP and the latest stock ROM I can install that is the most up to date (with Google Apps)?
Sorry to ask, but I am short on time most of the time and I might have an hour or so to work on it tomorrow.
Sorry I don't have official links but it would take you 10mins to find them through google. Good luck.
I have two files which I believe are correct except the TWRP file has an odd extension..
"Shaky156-TWRP-recovery.img.exe"
the other that is supposed to have GApps is: Stock-4.4.2-2.5-TegraNote7.zip
If that zip is only like 440 MB is that even possible? Can someone point me in a better direction if this sounds wrong.
Sources, TWRP: http://forum.xda-developers.com/showthread.php?t=2586432
Actually thinking about it and I bet with having things specific to img files like IMGBurn and other software it may create a .exe so it's easier to emulate it as a disk.
Do we have any good custom ROMs these days you'd suggest over stock? Are any that stable yet? If not can anyone find me a complete download if a 440MB zip is too small to have GApps in it.
I used Fastboot commands to get TWRP installed and Android is "upgrading.." now, so hopefully this will fix it.
I have the tablet up and running going into Google Play now.
I used this thread's link for the latest TWRP (2.7.1.0): http://forum.xda-developers.com/showthread.php?t=2586432
I got a completely stock version of 4.4.2 and OTA shows this as the most up to date version. I got my copy of the 4.4.2 ROM out of the Super Tool's folder that you can find here: http://forum.xda-developers.com/showthread.php?t=2627654
The tricky part to this my first time was I forgot you can open a command window inside the folder that contains TWRP/Fastboot/etc. (hold Shift and Right Click in the folder where all the data is and hit open command window)
Obviously everything came off a SD Card installed into the TN7.
answer for dummies
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks
aimeymarie said:
Hi
Is anyone able to explain how to rectify wifi being turned off constantly in basic non technical talk?
I am not a tech pro and am unsure what to do
All of the above answers are like a different language to me .
Thansks
Click to expand...
Click to collapse
Your best bet is to find someone you know who the above is not a foreign language to. I mean it could be broken down step by step as basic as possible and you may still not understand parts.
OK, first, I have searched the internet and XDA for help.
Currently, I'm stuck on The black screen with Google. It shows the unlocked Bootloader icon as well. Earlier today I was stuck in a boot with CM boot animation, but that's apparently gone now. I can fastboot, so I'm pretty sure it's recoverable. In TWRP, it says unable to mount /system, /data/ cache/ storage, basically everything. Using NRT i've flashed stock everything, which didn't work, so I tried flashing the kernel, which also didn't work, so I tried the bootloader and system, but they all result in the google splash screen. I am completely out of ideas.
Question: How do i fix it?
Edit: It stayed on the splash screen for at least 4 hours and it wasn't caused by anything I did. No ROM flashes, nothing. It was working then it wasn't.
a.child said:
OK, first, I have searched the internet and XDA for help.
Currently, I'm stuck on The black screen with Google. It shows the unlocked Bootloader icon as well. Earlier today I was stuck in a boot with CM boot animation, but that's apparently gone now. I can fastboot, so I'm pretty sure it's recoverable. In TWRP, it says unable to mount /system, /data/ cache/ storage, basically everything. Using NRT i've flashed stock everything, which didn't work, so I tried flashing the kernel, which also didn't work, so I tried the bootloader and system, but they all result in the google splash screen. I am completely out of ideas.
Question: How do i fix it?
Edit: It stayed on the splash screen for at least 4 hours and it wasn't caused by anything I did. No ROM flashes, nothing. It was working then it wasn't.
Click to expand...
Click to collapse
If you are using NRT, try to flash stock with soft-bricked/Bootloop option.
{
"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 restore, perform a wipe data/factory reset in stock recovery before booting to android.
Best of luck
joegestes said:
If you are using NRT, try to flash stock with soft-bricked/Bootloop option.
After restore, perform a wipe data/factory reset in stock recovery before booting to android.
Best of luck
Click to expand...
Click to collapse
Thanks for the help, you even edited a screenshot :') haha unfortunately, no luck. But some interesting stuff happens when I do the stock flash.
First time I tried (yesterday), I went through the instructions just how they're listed, I erased all user data and rebooted, still stuck. This time, though, I couldn't get it to boot the stock recovery. Tried pwr+Vol Up like the directions say, but it gets stuck on splash. Tried Pwr+Vol down and I could boot into TWRP which informed me that it was still unable to mount any partitions and that there was no OS installed.
Edit: Looked closer at the command prompt log from the flash and noticed it failed to write any of the images. Sending is OKAY but writing FAILED.
a.child said:
Thanks for the help, you even edited a screenshot :') haha unfortunately, no luck. But some interesting stuff happens when I do the stock flash.
First time I tried (yesterday), I went through the instructions just how they're listed, I erased all user data and rebooted, still stuck. This time, though, I couldn't get it to boot the stock recovery. Tried pwr+Vol Up like the directions say, but it gets stuck on splash. Tried Pwr+Vol down and I could boot into TWRP which informed me that it was still unable to mount any partitions and that there was no OS installed.
Edit: Looked closer at the command prompt log from the flash and noticed it failed to write any of the images. Sending is OKAY but writing FAILED.
Click to expand...
Click to collapse
Hmmm.
Its possible your cable is no good, but it could be something else like a driver issue or charging port failure.
Try using a known good, high quality data cable. Also try connecting to a different USB port on PC.
Just so I understand better.
What version of android did you attempt to flash?
Were you using NRT to flash when the flashing's failed?
Was Force Flash enabled in NRT? .......Try that.
Did you try flashing a different version of STOCK android?
Do you have Android ADB/fastboot installed on PC aside from the one in NRT?
If so, does fastboot detect your phone when running the command "fastboot devices" while in the bootloader?
Is ADB able to detect your phone when running the command "ADB devices" while in TWRP?
I'm at work now, but I'll try new cables and ports when I get home as well as the adb commands.
I was trying to flash 5.0.1 , and was running some CM12 nightly when it failed. To be clear, the ROM was working fine until it wasn't.
I was using NRT and I had force flash selected (recommended settings I think), but I'm not 100% sure post flash factory reset was checked but in the CMD log I did see it wipe and attempt to write userdata.
I have not tried a different version of stock.
I believe ADB is installed outside of NRT abd i have to manually set my path variable to C:/ADB (which screws up normal command prompt, but idk how to fix that) for NRT to work. I have a 2013 nexus 7 and used the same setup to flash PA a while back without any issues.
NRT doesn't detect my phone when displaying the splash screen, but idk about TWRP.
joegestes said:
Hmmm.
Its possible your cable is no good, but it could be something else like a driver issue or charging port failure.
Try using a known good, high quality data cable. Also try connecting to a different USB port on PC.
Just so I understand better.
What version of android did you attempt to flash?
Were you using NRT to flash when the flashing's failed?
Was Force Flash enabled in NRT? .......Try that.
Did you try flashing a different version of STOCK android?
Do you have Android ADB/fastboot installed on PC aside from the one in NRT?
If so, does fastboot detect your phone when running the command "fastboot devices" while in the bootloader?
Is ADB able to detect your phone when running the command "ADB devices" while in TWRP?
Click to expand...
Click to collapse
So the computer does not recognize a fastboot device while in TWRP, but does in the BL.
I attempted to flash 5.0 with the settings mentioned, no luck
a.child said:
So the computer does not recognize a fastboot device while in TWRP, but does in the BL.
I attempted to flash 5.0 with the settings mentioned, no luck
Click to expand...
Click to collapse
If you are absolutely certain your cable is a good one, it is possible you have a driver issue, but I doubt it.
You could try deleting/uninstalling you current ADB driver set and then install the following ADB clockworkmod universal drivers . It might help.
64bit
32bit
If you decide to install the drivers. make sure you select "Android Composite ADB Interface"
after installing the driver set
If that does not help, I am sorry to say, you are likely looking at a hardware failure of the charging port(Dock Connector &Flex Cable)
It looks easy and economical to replace. I found the part here, but you could Google around. I have no experience with the following site.
http://www.repairsuniverse.com/lg-nexus-4-e960-dock-connector-flex-cable-replacement.html
If it were my N4(still great phone), I'd replace the part and attempt to re-flash.
Best of luck.
joegestes said:
If you are absolutely certain your cable is a good one, it is possible you have a driver issue, but I doubt it.
You could try deleting/uninstalling you current ADB driver set and then install the following ADB clockworkmod universal drivers . It might help.
64bit
32bit
If you decide to install the drivers. make sure you select "Android Composite ADB Interface"
after installing the driver set
If that does not help, I am sorry to say, you are likely looking at a hardware failure of the charging port(Dock Connector &Flex Cable)
It looks easy and economical to replace. I found the part here, but you could Google around. I have no experience with the following site.
http://www.repairsuniverse.com/lg-nexus-4-e960-dock-connector-flex-cable-replacement.html
If it were my N4(still great phone), I'd replace the part and attempt to re-flash.
Best of luck.
Click to expand...
Click to collapse
Thanks for the links, I might give it a go.
I bought an original Moto x last night for $100 and I was going to root the potatoes out of it, but who knew non-nexus phones were so difficult to unlock? Damn AT&T....
I sort of suspected it was a hardware issue when I was getting nowhere with NRT, but I wanted confirmation from someone more knowledgeable than me. Any idea on the likelyhood it is something other than the port? The bit that concerns me is that TWRP was unable to mount any partitions, but then again, if i couldn't connect while in TWRP, sort of sounds like a port issue.
oh well...
a.child said:
Thanks for the links, I might give it a go.
I bought an original Moto x last night for $100 and I was going to root the potatoes out of it, but who knew non-nexus phones were so difficult to unlock? Damn AT&T....
Click to expand...
Click to collapse
LOL....That's why I mostly stick with Nexus devices. No carrier garbage, global bands, unlockable and plenty of potatoes:laugh:
a.child said:
Any idea on the likelyhood it is something other than the port?.
Click to expand...
Click to collapse
Could be a bad eMMC but I doubt that. Port failure is more likely to be the issue based on your inability to ADB devices in TWRP.
a.child said:
The bit that concerns me is that TWRP was unable to mount any partitions, but then again, if i couldn't connect while in TWRP, sort of sounds like a port issue
Click to expand...
Click to collapse
Its harder know exactly when using NRT.
That is one reason why, IMO, it is far better to use Fastboot commands to flash instead of relying on toolkit automation.(I do think NRT is the best toolkit)
My guess is NRT sends erase commands to a partition before flash attempts which then failed or sometimes, when a port goes bad,
it is intermittent, a partial flash occurs which would also explain why TWRP can,t mount a particular partition.
For ten bucks delivered on eBay its a no brainier to change out the port. It will probably fix it and if not, you'll have learned something.
joegestes said:
LOL....That's why I mostly stick with Nexus devices. No carrier garbage, global bands, unlockable and plenty of potatoes:laugh:
Could be a bad eMMC but I doubt that. Port failure is more likely to be the issue based on your inability to ADB devices in TWRP.
Its harder know exactly when using NRT.
That is one reason why, IMO, it is far better to use Fastboot commands to flash instead of relying on toolkit automation.(I do think NRT is the best toolkit)
My guess is NRT sends erase commands to a partition before flash attempts which then failed or sometimes, when a port goes bad,
it is intermittent, a partial flash occurs which would also explain why TWRP can,t mount a particular partition.
For ten bucks delivered on eBay its a no brainier to change out the port. It will probably fix it and if not, you'll have learned something.
Click to expand...
Click to collapse
Well i replaced the port and the battery and i'm having the same problem. And I did check to make sure I didn't reinstall the old port.
Guess she's dead :'(
Hmmm... You can connect in fastboot mode, right?
How about re-locking and unlocking the bootloader? It helped me several times...
You'll have to search about how to use fastboot. Connect your phone to your pc while in fastboot mode, and type this into terminal window :
fastboot oem lock
(Press enter)
(bootloader will be locked)
fastboot oem unlock
(Press enter)
(Phone's screen will display sth, use volume keys and power keys to unlock the bootloader)
(It will erase itself)
ddaggebi said:
Hmmm... You can connect in fastboot mode, right?
How about re-locking and unlocking the bootloader? It helped me several times...
You'll have to search about how to use fastboot. Connect your phone to your pc while in fastboot mode, and type this into terminal window :
fastboot oem lock
(Press enter)
(bootloader will be locked)
fastboot oem unlock
(Press enter)
(Phone's screen will display sth, use volume keys and power keys to unlock the bootloader)
(It will erase itself)
Click to expand...
Click to collapse
Thanks for the suggestion, but it didn't work. I was able to lock and unlock the bootloaded again, but it didn't have any effect.
Have you tried flashing Jellybean or kitkat stock rom by fastboot?
If that doesn't work, then the problem is within EMMC. You'll have to let her go...
ddaggebi said:
Have you tried flashing Jellybean or kitkat stock rom by fastboot?
If that doesn't work, then the problem is within EMMC. You'll have to let her go...
Click to expand...
Click to collapse
Looking at other forums, pretty sure the emmc is dead, but I'll try flashing an older version.
Why rooting Honor 7?
Huawei Honor 7 is one great Chinese phone, on design and performance side I might say that one of the best. But then, like most of branded phones, it comes with its own UI, precisely Emotions 3.1. As this UI might have a few useful options, it is generally (as many others) unwanted modification of AOSP. Most of adaptions and additional applications are adapted to the Chinese taste and feels strange to westerners.
Therefore I suggest potential buyers from the West to wait for European model which is expected to be available in early September. It may come without additional Chinese applications though it keeps Emotions UI for sure. The only way to change this at least partially is to root the phone.
In the beginning I had replaced the most inconvenient essential applications like dialer, messenger and calendar with Google’s ones and had removed all Chinese apps. But later, due to really frequently OTA updates I got tired of reverting system applications, returned all Chinese, froze them and kept only 3 additional Google apps, which I removed from the system before every update and pushed them back after.
I advise you to push desired system apps as apk files with the appropriate explorer (i.e. Root Explorer) rather than flash zip. Flashing zip according to my experience might cause bootloop (allegedly due to the inappropriate graphic parameters).
How to root Honor 7?
In the beginning I must warn you that rooting your device might be risky, especially if you don’t follow instructions. Hence, do your homework first, read everything carefully and make a nandroid after every new alternation of the system.
I’m not taking any responsibility for your device. You should be aware that it is your device and your own responsibility. I’m not a developer and therefore I might not be able to advice you if something goes wrong. I’ve just used the method described below and succeed without any issues or damage. I strongly believe that you’ll benefit from this method too If followed correctly. Do not improvise or omit any instruction.
I must apologize to not insert pictures into text, I was to short to do it in reasonable amount of time with my current knowledge. Pictures are numbered and attached.
Part 1: Unlock your bootloader
In order to root your phone, you have to unlock the bootloader first. Surprisingly, unlike in my previous cases, unlocking Honor 7 bootloader doesn’t factory reset the phone. Anyway, like always, I do not take credit for any of this material or information, so backup your contacts, texts, pictures, etc. to the computer before unlocking.
Unlocking (and relocking) procedure
Register to Huawei and obtain an unique unlock code here:
https://hwid5.vmall.com/oauth2/port...huawei.com/en/source/plugin/hwlogin/login.php
Unlock your bootloader following this procedure (Google translate from Huawei web instructions):
Step 1: Preparation Work
1. Install the phone driver is properly on a PC, driver download Huawei Terminal official website.
2. Download the ADB toolkit provided by Google and installed on your PC, such as the installation to D: \ adb_tools-2.0 directory, make sure the directory with fastboot.exe file.
Step 2: Unlock Operation
1. Put the phone into fastboot mode:
First phone off (note need to be in the setup menu, close the "Quick Start" feature, or unplug the battery after shutdown, more than two seconds and then re-inserted), and then press the power button and the volume down key (flat simultaneously Press the volume keys and power button), and maintain more than 10 seconds, you can enter the fastboot mode.
If this does not enter fastboot mode, try the following steps:
Phone off (note need to be in the setup menu, close the "Quick Start" feature, or unplug the battery after shutdown, more than two seconds and then re-insert), then insert the USB cable, followed by pressing the volume down and power button key, holding more than 10 seconds, you can enter the fastboot mode.
2. Connect your phone and a PC:
Use USB cable to connect your phone and PC, open the PC command line window, enter the ADB installation directory, make sure your phone and PC is connected, confirm method in the command line window, type fastboot devices, you can see the normal connection information, such as: 9e42530e fastboot.
picture 1
3. Perform the unlock command:
Enter the PC command line window fastboot oem unlock ****************, * No. 16 unlock code, for example: fastboot oem unlock 1234567812345678.
picture 2
4. Wait for the phone to unlock:
After entering the unlock code, the phone will automatically restart, if you enter the correct password, the phone will enter restore factory settings mode. Restoring the factory setup is complete, the phone automatically restart, enter the standby interface, complete the unlocking operation. If the user enters the password information is incorrect, the phone will prompt an error message, and enters the standby interface.
5. Test if the phone is unlocked sucesfully:
Repeat steps 1 and 2, and then enter the fastboot oem get-bootinfo, phone bootloader will display the current status information, such as the PC command line window "Bootloader Lock State: LOCKED", indicates bootloader is still locked, please re-unlock operation or confirm the password is correct and then conduct; If "Bootloader Lock State: UNLOCKED", means that the phone has been unlocked, you can brush machine operation.
picture 3
Note: After unlocking success, if you want to re-lock the phone, follow these steps: First, upgrade via SD card, will be restored to Huawei mobile version of the official release version; then, enter fastboot mode, the command line at PC Enter the command fastboot oem relock ****************, * No. 16 unlock code. The phone will automatically reboot, bootloader converted to "RELOCKED" state.
Part 2: Install custom recovery
All credits go to Chinese developer Wang Hao, who invented this procedure, I’m only the interpreter.
Go to the site: http://pan.baidu.com/share/link?shareid=1067948446&uk=3020839592, use password: nwae and download the file. Extract and open the map: 荣耀7root工具包. Make sure that you have proper USB driver installed and ADB debugging enabled. Start command line in map 荣耀7root工具包(shift + right click of mouse simultaneously): Power off the phone and connect it with USB to the computer. On the phone pres volume down + power simultaneously. It will boot to the fastboot. Then type in the command line on the computer:
fastboot devices
if your device is recognized, type in the command line:
fastboot flash recovery TWRP.img
when process is finished, type:
fastboot reboot
You’ll boot the system. You’ll have installed TWRP recovery in CHINESE LANGUAGE and you won’t understand anything. Luckily there is not much to understand. Configuration of the recovery is the same as in English:
picture 4
Find an English description of TWRP if you want to use more functions. For the beginning we want to root the phone so the instructions is be only about installing the SU.
Part 3: Root your phone
Copy zip file BETA-SuperSU-v2.49 from the map荣耀7root工具包 to the phone internal memory or sdcard if you have one (wherever, just remember, where it is copied) and boot to recovery: turn down your phone, wait a few secs, simultaneously press volume up and power buttons. If you can’t do it, turn phone off, wait a few secs, connect it to the computer with USB cable and press simultaneously volume up and power.
In TWRP press install (first button up and left), select zip file, where you put BETA-SuperSU-v2.49 and press the only button for installing. Then go back to the main TWRP screen, find reboot (lower right button) and boot the system (upper left button).
That’ll be all. Install Play Store from web if you don’t have it already, Busybox and one explorer with root capability (i.e. Root Explorer) for desired modification of the system. And most importantly: ALWAYS MAINTAIN AN ESCAPE LINE. DO NANDROID BEFORE ANY MODIFICATION OF THE SYSTEM.
Accepting OTA requires restoration of the original system and flashing stock recovery. Stock recovery could be flashed following procedure for TWRP flashing and could be obtained from ROM for your respective phone from the site: http://www.needrom.com/?s=honor+7&sa=search&scat=0, following procedure described in http://forum.xda-developers.com/showthread.php?t=2433454 thanks to the developer worstenbrood.
Serious advice: Don’t try to accept OTA with modified system or custom recovery installed. In first case OTA will be refused, in second case you might experience TWRP bootloop.
Is this really working? for which model of HONOR 7? 16GB or 64GB?
Is this really working? for which model of HONOR 7? 16GB or 64GB?
Thanks
almohanad said:
Is this really working? for which model of HONOR 7? 16GB or 64GB?
Thanks
Click to expand...
Click to collapse
It's real. I did it, turned back to stock, flashed the new rom and rooted it again. I have 16 GB PLK-UL00, but the method is universal for all Honor 7 models.
piskr said:
It's real. I did it, turned back to stock, flashed the new rom and rooted it again. I have 16 GB PLK-UL00, but the method is universal for all Honor 7 models.
Click to expand...
Click to collapse
Please help, the model of Honor 7 is not listed in the models so i can get the unlock code. which model should i use?
You can find your respective phone model in -settings-about phone-model number. Just register and follow the procedure at: https://hwid5.vmall.com/oauth2/port...huawei.com/en/source/plugin/hwlogin/login.php
To make procedure easier, I'm attaching the TWRP recovery img and SU zip file. If you have android platform tools already installed or can find them somewhere else, you don't need to seek them on pan.baidu.com, you can flash TWRP.img from any platform tools following the description above and flash SU.zip after from TWRP.
I'm not able to obtain unique unlock key because there is not listed our cell on that web site. in the list of all models.
Lucki_X said:
I'm not able to obtain unique unlock key because there is not listed our cell on that web site. in the list of all models.
Click to expand...
Click to collapse
OK. Let's start from the very beginning. Do you know what model of the phone you have? My is PLK-UL00 and I'm deriving instructions on this model. So: go to http://emui.huawei.com/, change language to English (picture 1). You'll get to http://emui.huawei.com/plugin.php?id=hwdownload. Enter your phone model and you'll jump to the menu: http://emui.huawei.com/cn/plugin.php?id=unlock&mod=detail (picture2). Now enter requested data. In first column choose smartphone. In second enter your model. In third the product serial number as marked on the box containing your phone. Next enter IMEI of the first SIM. Then product identification code (dial *#*#1357946#*#* and you'll get it (picture3)). Enter Captha as seen at last column and enter submit. You are done and you'll get unlock code.
Use google translate on pages to understand the text. If you are unable to follow instructions you can still write Huawei for code to email address seen in attached picture (mobile.huawei.com).
Hope I helped. Good luck
Lucki_X said:
I'm not able to obtain unique unlock key because there is not listed our cell on that web site. in the list of all models.
Click to expand...
Click to collapse
Hi,
I also had this problem - the site does not seem to list my model (PLK-AL10) on the english language one. It does list it on the Chinese one, but gives me a cryptic error and wont give me a code.
I've emailed support but no response yet.
I'll update here if I get a response from them
--Alex
achard said:
Hi,
I also had this problem - the site does not seem to list my model (PLK-AL10) on the english language one. It does list it on the Chinese one, but gives me a cryptic error and wont give me a code.
I've emailed support but no response yet.
I'll update here if I get a response from them
--Alex
Click to expand...
Click to collapse
I tried and i don't feel that you can't obtain the unlock code. Did you register correctly? I found that your model is listed as well in drop down menu, just credentials, which logically I don't have, are to be entered.
My model is PLK-TL01H, the site doesn't seem to list my model. I've found it in chinese version, but my IMEI is not connected with my Huawei cloud account. I'll try it tomorrow again. Thanks for advice to try Chinese version of site.
piskr said:
I tried and i don't feel that you can't obtain the unlock code. Did you register correctly? I found that your model is listed as well in drop down menu, just credentials, which logically I don't have, are to be entered.
Click to expand...
Click to collapse
Yes, i tried the links you provided, they are working but for some reason i am receiving the message you see in attachment,
{
"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"
}
I am 100% sure that i have entered the right info.
It seems that i have to send an email to Huawei support to gain the unlock code..
I'm not able to received unique unlockable code. It's because my phone number is not connected with my Huawei IMEI. I can't do it manually because in the list of countries isn't my country code and is not possible to enter my own. so I'll try to write to support. Probably I would have to try it later or another method.
Odesláno z mého PLK-TL01H pomocí Tapatalk
Lucki_X said:
I'm not able to received unique unlockable code. It's because my phone number is not connected with my Huawei IMEI. I can't do it manually because in the list of countries isn't my country code and is not possible to enter my own. so I'll try to write to support. Probably I would have to try it later or another method.
Odesláno z mého PLK-TL01H pomocí Tapatalk
Click to expand...
Click to collapse
Hi,
Great news!
It took them a week, but they did eventually respond and send me the unlock password
So yeah, email them and wait a week.
Best of luck,
Alex
I can't find my phone also !
I have HONOR 7 v64B, PLK-AL10C00B150
achard said:
Hi,
Great news!
It took them a week, but they did eventually respond and send me the unlock password
So yeah, email them and wait a week.
Best of luck,
Alex
Click to expand...
Click to collapse
hmm ok next question.
What build of TWRP is this? Is there an english one available?
achard said:
Hi,
Great news!
It took them a week, but they did eventually respond and send me the unlock password
So yeah, email them and wait a week.
Best of luck,
Alex
Click to expand...
Click to collapse
Many thanks for info.
I'll write them ASAP and let you know a resolution.
Your phone is PLK-AL10. And such is listed in all forums and producer's site.
It's Chinese, the last one. I put the instruction how to handle it. As far as I know in English exist only CWM for now, but CWM appeared always less reliable in the last time.
Always nothing for plk-al10 ??
raphzel said:
Always nothing for plk-al10 ??
Click to expand...
Click to collapse
You have to use version in chinese language. For me in my country is that gateway probably blocked with my model PLK-TL01H. In Chinese version it almost worked but my phone number is not connected with IMEI of Huawei cloud because of lack of my country code in list of countries in entering form for phone number.
hi there! first time posting, hope i wont break any rule.
so, my "issue" here is that when i unlocked the bootloader about 12 hours ago i did not have any alert or timestamp to follow until the time when the bootloader closes or something.
a bit of context: as far as i know once the bootloader its unlocked there should have been a timestamp at the mi unlock program saying how many hours will it take to do some kind of evaluation, so, if that proceeds correctly the bootloader would be unlocked. i did not have that timestamp thing.
in fact i checked the developer settings after the reset and the mi lock option shows an unlocked icon.
Now, with all that being said, am i able to install a recovery like twrp? should i wait for a week as i have watched at a couple of tutorials?
thanks in advance and have a nice day!
akirapearl said:
hi there! first time posting, hope i wont break any rule.
so, my "issue" here is that when i unlocked the bootloader about 12 hours ago i did not have any alert or timestamp to follow until the time when the bootloader closes or something.
a bit of context: as far as i know once the bootloader its unlocked there should have been a timestamp at the mi unlock program saying how many hours will it take to do some kind of evaluation, so, if that proceeds correctly the bootloader would be unlocked. i did not have that timestamp thing.
in fact i checked the developer settings after the reset and the mi lock option shows an unlocked icon.
Now, with all that being said, am i able to install a recovery like twrp? should i wait for a week as i have watched at a couple of tutorials?
thanks in advance and have a nice day!
Click to expand...
Click to collapse
C'mon. Where did you read about 'evaluation'. Do you expect some men in black coming to your house to do inspection?!
Usually when you applied for unlocking the Bootloader, you had to be notified to wait 168 hours = 7 days before proceeding. That's the only 'timestamp'. And at any time in between, it would tell you how many hours have remained to wait
If you followed the proper procedure (instructions about unlocking bootloders for Xiaomi phones can be found everywhere, incl. here also on XDA), your Bootloader should be unlocked now.
Btw, while unlocking, the phone had to do a factory reset (and you could not miss that?!)
You can install ADB and Fastboot package to your PC (google if needed what/how/where - again, instructions are everywhere), connect your phone to PC, boot to Fastboot and execute from the PC:
Code:
fastboot devices
fastboot oem device-info
First command must give you the id of your phone (confirming that fastboot connection, drivers and everything are ok)
Second command will give you status of your Bootloder, like:
Code:
(bootloader) Device unlocked: true
Edit: It was 2+ years ago, I do not recall details, but I strictly followed one of the guides like below, and I successfully unlocked Bootloader on my Mi 9T with no issues or ambiguities:
https://c.mi.com/thread-1857937-1-1.html
or guides from XDA:
How to unlock the bootloader, root, and install TWRP on the Xiaomi Mi 9
Max from XDA TV has shared a tutorial video about how to unlock the bootloader, install TWRP, and root with Magisk on the Xiaomi Mi 9.
www.xda-developers.com
[Guide] Unlock bootloader and flash Xiaomi.eu Rom
Hi guys. I haven't found any thread that was tutorial to unlock bootloader and flash rom so i decided to make one. First of all you need to know that this MAY brick your device and don't try it if you don't know what you are going to do. Do it...
forum.xda-developers.com
[Unlock Bootloader + TWRP + ROOT + CUSTOM ROM] Working on Xiaomi Mi 10T/Pro
[CONFIRMED] ( WORKING ON XIAOMI MI 10T/PRO ) |-Full tutorial for everything-| /** * Your warranty is now void. * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app...
forum.xda-developers.com
zgfg said:
C'mon. Where did you read about 'evaluation'. Do you expect some men in black coming to your house to do inspection?!
Click to expand...
Click to collapse
I dont really know how to answer this, im pretty sure i did read that, might missunderstood that tho, its a very reasonable posibility.
zgfg said:
If you followed the proper procedure (instructions about unlocking bootloders for Xiaomi phones can be found everywhere, incl. here also on XDA), your Bootloader should be unlocked now.
Btw, while unlocking, the phone had to do a factory reset (and you could not miss that?!)
Click to expand...
Click to collapse
I did actually made a backup etc because of that, so yeah, i knew about the factory reset.
zgfg said:
You can install ADB and Fastboot package to your PC (google if needed what/how/where - again, instructions are everywhere), connect your phone to PC, boot to Fastboot and execute from the PC:
Code:
fastboot devices
fastboot oem device-info
First command must give you the id of your phone (confirming that fastboot connection, drivers and everything are ok)
Second command will give you status of your Bootloder, like:
Code:
(bootloader) Device unlocked: true
Click to expand...
Click to collapse
Thanks for the commands, will check asap.
Edit: this is the actual output
{
"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"
}
zgfg said:
Edit: It was 2+ years ago, I do not recall details, but I strictly followed one of the guides like below, and I successfully unlocked Bootloader on my Mi 9T with no issues or ambiguities:
https://c.mi.com/thread-1857937-1-1.html
or guides from XDA:
How to unlock the bootloader, root, and install TWRP on the Xiaomi Mi 9
Max from XDA TV has shared a tutorial video about how to unlock the bootloader, install TWRP, and root with Magisk on the Xiaomi Mi 9.
www.xda-developers.com
[Guide] Unlock bootloader and flash Xiaomi.eu Rom
Hi guys. I haven't found any thread that was tutorial to unlock bootloader and flash rom so i decided to make one. First of all you need to know that this MAY brick your device and don't try it if you don't know what you are going to do. Do it...
forum.xda-developers.com
[Unlock Bootloader + TWRP + ROOT + CUSTOM ROM] Working on Xiaomi Mi 10T/Pro
[CONFIRMED] ( WORKING ON XIAOMI MI 10T/PRO ) |-Full tutorial for everything-| /** * Your warranty is now void. * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app...
forum.xda-developers.com
Click to expand...
Click to collapse
I will check them, thank you! Matter of fact i think i actually saw that the lock icon inside settings > developer settings > mi unlock status seems to be opened, so i guess i'll wait until next Friday so i will be able to get a recovery etc
zgfg said:
you had to be notified to wait 168 hours = 7 days before proceeding.
Click to expand...
Click to collapse
Also little mention to this, hope its not an annoying question or something but, am i right about the waiting for a week thing until i do anything else? i mean, (might be a little repetitive here, just trying to feel 100% sure) when i did unlock the bootloader there was not "Wait 168 hours" thing at the gui tool, as i said before i will check the commands you told me about, i dont want to mess things up with my phone tho, thats it.
Again, thanks a lot for your quick and really helping response, so much appreciated. Have a nice day!
akirapearl said:
I dont really know how to answer this, im pretty sure i did read that, might missunderstood that tho, its a very reasonable posibility.
I did actually made a backup etc because of that, so yeah, i knew about the factory reset.
Thanks for the commands, will check asap.
Edit: this is the actual output
View attachment 5491469
I will check them, thank you! Matter of fact i think i actually saw that the lock icon inside settings > developer settings > mi unlock status seems to be opened, so i guess i'll wait until next Friday so i will be able to get a recovery etc
Also little mention to this, hope its not an annoying question or something but, am i right about the waiting for a week thing until i do anything else? i mean, (might be a little repetitive here, just trying to feel 100% sure) when i did unlock the bootloader there was not "Wait 168 hours" thing at the gui tool, as i said before i will check the commands you told me about, i dont want to mess things up with my phone tho, thats it.
Again, thanks a lot for your quick and really helping response, so much appreciated. Have a nice day!
Click to expand...
Click to collapse
Per your fastboot response, your phone should be already unlocked
Make sure you have enabled Developer options and OEM Unlocking there and try to flash TWRP (download the latest official, from TWRP.me for davinci - assuming you have Xiaomi Mi 9T / Redmi K20):
Download TWRP for davinci
Download TWRP Open Recovery for davinci
dl.twrp.me
Code:
adb wait-for-device devices
PAUSE
adb reboot-bootloader
PAUSE
fastboot devices
PAUSE
fastboot getvar product
PAUSE
fastboot getvar anti
PAUSE
fastboot oem device-info
PAUSE
fastboot flash recovery twrp-3.6.0_9-0-davinci.img
PAUSE
fastboot oem reboot-recovery
For every PAUSE, press Enter on the PC (and on adb reboot-bootloader, wait for phone to reboot to Fastboot)
Upon the last command, forcing the phone to reboot to the newly installed TWRP, you will have to enter your Android home-screen unlock pin/password (or draw the pattern if you use it instead of the pin), the same you enter every time when rebooting to Android/system
Without that, TWRP cannot read (decrypt) Internal memory and Data (and instead of the folders and file names it would show some 'random' garbage)
zgfg said:
Per your fastboot response, your phone should be already unlocked
Make sure you have enabled Developer options and OEM Unlocking there and try to flash TWRP (download the latest official, from TWRP.me for davinci - assuming you have Xiaomi Mi 9T / Redmi K20):
Download TWRP for davinci
Download TWRP Open Recovery for davinci
dl.twrp.me
Code:
adb wait-for-device devices
PAUSE
adb reboot-bootloader
PAUSE
fastboot devices
PAUSE
fastboot getvar product
PAUSE
fastboot getvar anti
PAUSE
fastboot oem device-info
PAUSE
fastboot flash recovery twrp-3.6.0_9-0-davinci.img
PAUSE
fastboot oem reboot-recovery
For every PAUSE, press Enter on the PC (and on adb reboot-bootloader, wait for phone to reboot to Fastboot)
Upon the last command, forcing the phone to reboot to the newly installed TWRP, you will have to enter your Android home-screen unlock pin/password (or draw the pattern if you use it instead of the pin), the same you enter every time when rebooting to Android/system
Without that, TWRP cannot read (decrypt) Internal memory and Data (and instead of the folders and file names it would show some 'random' garbage)
Click to expand...
Click to collapse
Ok, im facing a screen at twrp that says "Keep system read only?", should i keep that or just allow modifications? it also has a checkbox saying "never show this screen during boot again", should i assume that twrp will ask me this every time i access it?
Edit: I just allowed it, should i do something else or am i ready to install any rom i want?
akirapearl said:
Ok, im facing a screen at twrp that says "Keep system read only?", should i keep that or just allow modifications? it also has a checkbox saying "never show this screen during boot again", should i assume that twrp will ask me this every time i access it?
Edit: I just allowed it, should i do something else or am i ready to install any rom i want?
Click to expand...
Click to collapse
To install a ROM you need to enable modifications
If you are already going to install a custom ROM, you are on your own now, you must know which ROM you are installing and how, etc - and be prepared for unbricking if things go wrong
E.g. upon installing a ROM and BEFORE rebooting to system you will HAVE TO Format Data (not just Wipe Data) and Wipe Cache while still in TWRP, before rebooting to system - without that you will have troubles with the new ROM
Due to that formatting, "never show this screen during boot again" will have no effect (whatever TWRP saved this time to Internal memory will be wiped)