Database Users

How To: Unlock bootloader and Root using a Mac

This process is very similar to how its done on Windows but I thought I would go ahead and post it here for those who have never rooted or used terminal before. I know the first time I rooted an Android device I was very happy to have a Mac specific guide to follow . Many of you may think this is simplified too much but, like I said, I created this with first time rooters in mind. If a Mod would like to sticky it thats fine. Also, I've tried to be very careful and thorough with the instructions, but if anyone notices a problem please let me know.
As always, I am not responsible if something goes wrong and your device gets bricked. I will try to be as specific as possible and this process worked for me. Also, I don't claim to have the knowledge to fix any problems you may encounter along the way. There are a lot of very talented people here who have extensive knowledge of Android, but I am not one of them. I can unlock my bootloader and root my device but that's about it. So if you do encounter a problem I will try to help but there is no guarantee I can fix the issue (in fact the odds are that I can't fix the issue). Proceed with caution!
Important: Unlocking your bootloader will wipe your device! Please backup anything that is important (pics, vids, documents, etc)!
This guide only applies to the 2013 Nexus 7
A. Prep
1. Charge the Nexus 7 to at least 80% so it doesn't turn off during the process
2. Unlock developer options by navigating to -- settings > about tablet -- and then click the build number 7 times
3. Enable USB Debugging by navigating to -- settings > developer options -- and select the USB Debugging box
4. Download the Android SDK for Mac here and unzip it once it has downloaded. DO NOT use the link posted below for the sdk. It does not contain fastboot and you will not be able to complete the rooting process. Please use the full sdk from Google that I have linked here. EDIT: Google has changed the download for the SDK. Please see posts 73-75 on page 8 for instructions regarding how to get everything you will need for the SDK.
5. Download the latest TWRP for your device here and place it in the platform-tools folder of the SDK. Make sure the TWRP file you download is for the 2013 Nexus 7...not the 2012 version. To find the platform-tools folder -- open the adt-bundle-mac folder you downloaded and unzipped > sdk > platform-tools -- place the TWRP file here. Other files in the platform-tools folder should include adb, api, fastboot, notice.txt, and a few others.
B. Unlock the Bootloader - Warning--This will wipe your device! Backup anything important!
1. With your device powered on, plug it into your Mac
2. Open up terminal and navigate to the platform-tools folder which has the adb, fastboot, and TWRP files. An easy way to do this is to type "cd" (without the quotes) into terminal, add a single space, and then drag and drop the platform-tools folder onto terminal and then press enter.
3. Type this command into terminal: ./adb reboot bootloader
4. If you correctly navigated to the platform-tools folder, you should get an error message saying the device is unauthorized. Go to the Nexus 7 and there should be a dialogue box asking you to authorize the computer. Authorize the computer.
5. Re-type the command: ./adb reboot bootloader
6. Your device should now boot into fastboot mode. On your N7, the word "start" will be at the top in green and you can also see a lot of your device information on this screen
7. Type into terminal: ./fastboot oem unlock
8. Your Nexus 7 will now display a message about unlocking your device. Use the volume button to select the option to unlock the device and then press the power button to confirm the choice.
9. Your device will return to the fastboot mode screen and you can now see in the device information section near the bottom that the device is unlocked. While on this screen, press the power button to select the green "start", which will reboot your device. You must restart your device here or you will run into a softbrick issue during the root process!
10. Congrats! Your device is now unlocked. If you want to root proceed to the next section.
C. Rooting
1. Once your device has rebooted from the unlocking process, everything will have been wiped and reset. You will have to go back and unlock developer options again and you will also have to enable USB debugging again, which can be found part A. Prep of this guide.
2. Download the current version of SuperSU to your Nexus 7. It will go to the download folder on your N7. It can be found here. (Note: The version of SuperSU I have linked to is 1.93, but it gets updated from time to time. You might want to look around and see if a more current version is available. The thread for SuperSU can be found here.)
3. Turn your N7 off and then boot into fastboot mode by pressing the Volume Down button while also pressing the Power Button to turn the device on. If done correctly you should see the green "start" again at the top and the device information near the bottom.
4. Plug the N7 into the computer and make sure terminal is still directed to your platform-tools folder. For instructions on how to navigate to the platform-tools folder see part B. Unlock the bootloader.
5. Type the following into terminal: ./fastboot flash recovery nameofTWRPrecovery.img
5a. For the nameofTWRPrecovery.img part above, you must type the exact file name of whatever TWRP (or other) recovery you've decided to use. This is the same file that you downloaded and placed in the platform-tools folder in Part A. Step 5. above. For me the file name I had to type was openrecovery-twrp-2.6.0.0-flo.img and the total command looked like this: ./fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
6. In terminal you should see the process taking place and it will tell you when its finished and how long it took (less than a second).
7. Now, while still in fastboot mode, use the volume button to navigate to Recovery and press the power button.
8. The N7 will boot into TWRP which we just installed.
9. Using the touch screen, select install and then navigate to the download folder where you saved the SuperSU file
10. Select the SuperSU file using the touchscreen and then swipe to flash it. You will see the rooting process occur on the screen.
11. Congrats! You are now rooted. Select Reboot System and you are done!

Your instructions couldn't be any simpler. I am unlocked and rooted now. This is my first Android device. Thank you very much.

Glad it was helpful for you!

Is there any step involved to install drivers here which I saw mentioned while using Windows system?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

Very nice guide! Well done
Sent from my Nexus 7 2013 using xda app-developers App

redhat_123 said:
Is there any step involved to install drivers here which I saw mentioned while using Windows system?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
No, you don't need any drivers for the Mac (which makes it simpler than the Windows process in my opinion). I've included links in the how-to for everything you will need .

geckocavemen said:
No, you don't need any drivers for the Mac (which makes it simpler than the Windows process in my opinion). I've included links in the how-to for everything you will need .
Click to expand...
Click to collapse
Thanks a lot. This is the first time I used MAC to unlock and root a device and it was very quick. Appreciate your effort in putting up the detailed steps.

I just saw this post so I figured I may as well chime in. I've been rooting devices and using adb for years, so the issues wasn't a lack of experience.
I was having an issues with my device being reported as 'Offline'. Despite downloading the SDK several times I was unable to get the latest version.
I posted a thread last week with the updated version of adb needed for OS X in case anyone runs into this same issues that I did: http://forum.xda-developers.com/showthread.php?t=2390999

wad3g said:
I just saw this post so I figured I may as well chime in. I've been rooting devices and using adb for years, so the issues wasn't a lack of experience.
I was having an issues with my device being reported as 'Offline'. Despite downloading the SDK several times I was unable to get the latest version.
I posted a thread last week with the updated version of adb needed for OS X in case anyone runs into this same issues that I did: http://forum.xda-developers.com/showthread.php?t=2390999
Click to expand...
Click to collapse
Hi wad3g, was the problem you ran into related to the link for the Mac sdk I posted in the guide? If it was with my link I'd like to fix it so others don't have the same issue. Thanks!
EDITED TO ADD: Please only use the link in the how-to for the full sdk from Google. wad3g's link only has adb but not fastboot. To complete the rooting process you will need fastboot also.

geckocavemen said:
Hi wad3g, was the problem you ran into related to the link for the Mac sdk I posted in the guide? If it was with my link I'd like to fix it so others don't have the same issue. Thanks!
Click to expand...
Click to collapse
Yes, it is from the same link as above on Google's developer site. They hadn't updated the SDK yet, so each time I downloaded ADB v1.0.29 - ADB for 4.2. I was finally able to find ADB & Fastboot v1.0.31 for Android 4.3. Also, just so you know, the .zip on my thread is not the full SDK. If you're not a developer you don't need the full SDK, so for most the rooter's here my zip will be all that is needed.
You may just want to mention checking what version of ADB you're running prior to start or if you're having any issues. If you're running an older version than 1.0.31 you need to update.
{
"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"
}
Hope this helps! Let me know if you have any other questions.

Thanks wad3g. But just to clarify, Google updated the Mac version of the sdk on the 29th of July so the link in the original how-to will work for any version of Android. It's the same thing I used to download the sdk and I'm running version 1.0.31. Also, as mentioned it does contain more than is strictly necessary for unlocking and rooting. However, the original link in the how-to will provide you with the most up-to-date version of the Mac sdk that Google has released, should they update it in the future.

Please Help!!!
Hi I followed all your instructions and right when i was ready and tried to flash the recovery, I get this list of options after waiting for device:
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address. default: 0x10000000
-n <page size> specify the nand page size. default: 2048
-S <size>[K|M|G] automatically sparse files greater than
size. 0 to disable
I don't understand what I should pick or if I should pick any. Please help as soon as possible.
EDIT: The reason I got this list is because I dragged in the fastboot into the terminal because when I tried to enter ./fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img, it said this: -bash: fastboot: command not found

Don't worry you haven't broken anything. What you saw is basically just a message that says you entered an incorrect command and then it presents a list of acceptable commands. Just start the section C. Rooting over again and don't move the recovery file into the command window...just type the full name of the recovery file instead.
EDIT...I think I didn't understand your edit properly the first time. I think you got the bash message because terminal was no longer pointed at the platform-tools folder. To do the rooting process you must make sure terminal is still directed at platform-tools folder. It should still be if you didn't close terminal or do anything else in terminal after the unlocking process. However, if terminal is not directed to the platform-tools folder you can use the "cd" command found in part B. of the how-to to get terminal pointed to the right place again. Once you've done that you can just start Part C. again and all should be fine. When I rooted I just left terminal open after completing the unlocking process and it was still directed at platform-tools. If you closed terminal it wouldn't be pointed at the right location where fastboot is.
One other thing: Are you sure there is a fastboot file in your platform-tools folder? It should look just like the adb file except it will be named fastboot instead.
LAST EDIT PLEASE READ: I'm assuming you used wad3g's download because I just checked and it does not have a fastboot file in it and that is why you got the -bash message. Please use the link in the how-to to download the full sdk from google. Pull out the fastboot file from Google's sdk and put it wherever you put your adb file that you got from wad3g. At that point you will be able to continue with Part C. Rooting.

Hope that last edit of mine helped out. Just follow the how-to step by step (including my links) and you'll be ok.

Thanks So Much But One Last Question
geckocavemen said:
Don't worry you haven't broken anything. What you saw is basically just a message that says you entered an incorrect command and then it presents a list of acceptable commands. Just start the section C. Rooting over again and don't move the recovery file into the command window...just type the full name of the recovery file instead.
EDIT...I think I didn't understand your edit properly the first time. I think you got the bash message because terminal was no longer pointed at the platform-tools folder. To do the rooting process you must make sure terminal is still directed at platform-tools folder. It should still be if you didn't close terminal or do anything else in terminal after the unlocking process. However, if terminal is not directed to the platform-tools folder you can use the "cd" command found in part B. of the how-to to get terminal pointed to the right place again. Once you've done that you can just start Part C. again and all should be fine. When I rooted I just left terminal open after completing the unlocking process and it was still directed at platform-tools. If you closed terminal it wouldn't be pointed at the right location where fastboot is.
One other thing: Are you sure there is a fastboot file in your platform-tools folder? It should look just like the adb file except it will be named fastboot instead.
LAST EDIT PLEASE READ: I'm assuming you used wad3g's download because I just checked and it does not have a fastboot file in it and that is why you got the -bash message. Please use the link in the how-to to download the full sdk from google. Pull out the fastboot file from Google's sdk and put it wherever you put your adb file that you got from wad3g. At that point you will be able to continue with Part C. Rooting.
Click to expand...
Click to collapse
Again in a bit of a sticky pickle. I got it to work because my problem was that I didn't direct the terminal to the folder. Now I am booted into TWRP but I don't understand what you mean by the SuperSu file. I it just the whole folder titled UPDATE-SUPERSU-v1.51?
EDIT: OMG IT WORKED!!! Thanks so much I got it rooted and it works awesome now!!!

Best tutorial for mac ever
I found this so helpful and easy! My nexus 7 is rooted now!:good:

:good::good::good::good:
thanks a lot

Thanks for the guide.

Want to say thanks for your very detailed explanations.
If I may, I would like to suggest one more step after the final step. Make a Nandroid backup. That really helps a lot for people who screwed stuff up.

Yes, creating a nandroid backup is very important and can definitely save you when flashing Roms and stuff if something goes wrong. Creating a nandroid before rooting could get you back to stock with an unlocked botloader too. But I guess that isn't as important now that Google has released the factory images.
Sent from my Nexus 7 using xda app-developers app

[GUIDE] OnePlus One - How to Unlock Bootloader, Install Custom Recovery and Root

{
"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"
}
Setup, Preparation and Prerequisites
I know there are already a few root guides out there for this phone, but I found that they weren't very detailed. This guide is thorough and explains each and every step in a noob-proof manner.
Basic tasks that I may refer to throughout this guide:
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
Enter fastboot mode- Turn the phone off. Hold volume up + power until the "fastboot" screen appears.
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components here
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery - Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long (5-15 minutes), but its best to have enough charge in case something goes wrong.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
Driver Installation - Download and install the Universal ADB Driver. Alternatively, use this method.
Downloads
Download a custom recovery and the SuperSU zip below. Place both files (recovery image and root zip) in the platform-tools folder located on your desktop within the android-sdk-windows folder.
Custom Recovery:
TeamWin Recovery Project (TWRP)
Root:
SuperSU
Information
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.
Installing a Custom Recovery: A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your NAND (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Rooting: You can gain root by either flashing via recovery a pre-rooted custom rom, or flashing a zip containing the SuperSU binaries. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed, and the phones bootloader will be unlocked. This, in my opinion, is the most practical and beneficial method for rooting your phone. It gives you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of what is going on. Also this method will work regardless of what android version your phone has.
If you are confused by anything in this guide, I would highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also I'd suggest that you read over the whole thread a few times before actually doing anything to the phone.
Understand? Good...lets begin:
1. Unlocking Bootloader
Turn the phone off. Then boot it into fastboot mode by holding volume up + power. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
Plug the phone into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
Code:
fastboot oem unlock
After the above command has finished excuting, run the following
Code:
fastboot reboot
The phone will reboot. Wait until the phone has fully booted up into android, then adjust the following settings on the phone:
USB Debugging - On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Disable CM Recovery Protection - On your phone go to Settings > Developer options. Then disable the 'Update recovery with system updates' option.
Close the command prompt window and proceed onto the next section of the guide.
2. Installing a Custom Recovery
Turn the phone off. Then boot it into fastboot mode by holding volume up + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* Remember that this file should be placed in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Open a new command prompt and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot flash recovery recovery.img
Once the flash has completed type the following command to reboot the phone:
Code:
fastboot reboot
After the phone has booted back up, turn it off. Now to enter your newly installed custom recovery, hold volume down + power. The phone should boot into recovery mode. Now that you have a custom recovery, you may continue to the final step.
Close the command prompt window.
3. Rooting
Now that your phone has an unlocked bootloader and a custom recovery installed you have a two options to gain root (Pick one or the other. You don't need to do both)
Option A) Flash SuperSU binaries which will give you root with the stock ROM
Confirm that you have downloaded the SuperSU zip from the downloads section above and that it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Turn the phone off then boot into recovery mode by holding volume down + power. Leave the phone at the main screen of the custom recovery for now.
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
adb push UPDATE-SuperSU-v[COLOR="Red"]X[/COLOR].[COLOR="red"]XX[/COLOR].zip /sdcard/
This will copy the SuperSU zip onto your phone. Once the command has completed continue.
Instructions for TeamWin Recovery Project (TWRP):
Install > browse to SuperSU zip and select the it
Swipe to confirm the installation. Then reboot.
Instructions for ClockworkMod (CWM):
install zip from sdcard > choose zip from sdcard.
Next, browse to the location where you previously copied the SuperSU zip and select the it.
To confirm the installation, scroll down to "Yes" and select it. The installation shouldn't take very long, and once it has completed you may reboot.
Option B) Flash a custom rom which will come pre-rooted
Note that not all custom roms will be pre rooted, however the majority of them are. Read the OP of the ROM thread to see what the verdict is.
Copy a custom rom (you can find these in the ONE Android Development and ONE Original Android Development section) onto the phone (remember the location of where you copy it to)
Turn the phone off then boot into recovery mode by holding volume down + power. To install a custom ROM the general procedure to follow is: factory reset, wipe cache + dalvik cache, flash ROM, flash GApps. Here are the recovery specific instructions:
Instructions for TeamWin Recovery Project (TWRP):
Wipe > Swipe to Factory Reset
Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
Install GApps using same process as ROM, then reboot.
Instructions for ClockworkMod (CWM):
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
install zip from sdcard > choose zip from sdcard > navigate to the location of the ROM > select the ROM > confirm the installation by selecting "Yes"
After that you may install the GApps using the same method for flashing the ROM, and finally reboot the phone.
Keep in mind that the first boot after installing a custom ROM & wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot stuff.
Congrats! That is all! Your phone now has an unlocked bootloader, a custom recovery installed and is rooted. Enjoy

Reserved.

Thanks Dude For making this Helpful... Sure it will help us with our one plus one..........

Nice guide!!
Sent from Mallorca to your face

Great guide! Will definitely follow when my OPO arrives! :victory:

Thanks a lot for the thread sir ! Btw have some problems I m running and old XP and seems the commands don't work for me .. Would you show me a pics of your root folder on your desktop for the sdk please ?
And I have kies installed before .. Maybe drivers aren't working together ?

pro castinato said:
Thanks a lot for the thread sir ! Btw have some problems I m running and old XP and seems the commands don't work for me .. Would you show me a pics of your root folder on your desktop for the sdk please ?
And I have kies installed before .. Maybe drivers aren't working together ?
Click to expand...
Click to collapse
What do you mean the commands don't work? Could you explain if you are getting an error, what the error is, etc.

Chromium said:
What do you mean the commands don't work? Could you explain if you are getting an error, what the error is, etc.
Click to expand...
Click to collapse
Hum , so I will try to translate my commands from French lol
First I try to install 15 seconds adb installer and failed . Told me all files already copied and "stex" is missing .
After I install the sdk as you said , I put the folder on my desktop and try to get adb worked with the test entry . But my command said that there is a invalid way

pro castinato said:
Hum , so I will try to translate my commands from French lol
First I try to install 15 seconds adb installer and failed . Told me all files already copied and "stex" is missing .
After I install the sdk as you said , I put the folder on my desktop and try to get adb worked with the test entry . But my command said that there is a invalid way
Click to expand...
Click to collapse
Could you post a screenshot of the command prompt output? Thanks.

Chromium said:
Could you post a screenshot of the command prompt output? Thanks.
Click to expand...
Click to collapse
Yeah of course man , let me an hour I will show you all with pics . Thanks a lot again for helping us and for the thread sir ! I just received my One 64GB official this morning . Damn I love CM11S and this beast don't leave my hand since this morning ahah . Hope your like yours too ...
Can't wait for great PA , Carbon , Omni roms on dat crazy phone

pro castinato said:
Yeah of course man , let me an hour I will show you all with pics . Thanks a lot again for helping us and for the thread sir ! I just received my One 64GB official this morning . Damn I love CM11S and this beast don't leave my hand since this morning ahah . Hope your like yours too ...
Can't wait for great PA , Carbon , Omni roms on dat crazy phone
Click to expand...
Click to collapse
Nice, you're lucky I dont even have the phone yet...hopefully I can get my hands on it in the next couple of weeks or so, otherwise I'll probably have to go with a Nexus 5. Once you've installed a custom recovery check out my SlimRom build. I'm also planning on compiling Carbon, but first I'd like to make sure that Slim is functioning properly.

Chromium said:
Nice, you're lucky I dont even have the phone yet...hopefully I can get my hands on it in the next couple of weeks or so, otherwise I'll probably have to go with a Nexus 5. Once you've installed a custom recovery check out my SlimRom build. I'm also planning on compiling Carbon, but first I'd like to make sure that Slim is functioning properly.
Click to expand...
Click to collapse
Awesome man! Thanks for the help and ports ! If you need I should get like 3 invites this week or less so if you need one let me know , give me your mail address and I will send one your way to thank you

Hey man so here is the problem . I can recognize my One with adb , but can't fasboot after on my mac ...
Here are the commands :
macbook:android NikonografferZ$ ./adb devices
List of devices attached
51cf713e device
macbook:android NikonografferZ$ fasboot devices
-bash: fasboot: command not found
macbook:android NikonografferZ$
And if I plug my phone in Fastboot mode from start on my mac he don't recognize it ..

pro castinato said:
Hey man so here is the problem . I can recognize my One with adb , but can't fasboot after on my mac ...
Here are the commands :
macbook:android NikonografferZ$ ./adb devices
List of devices attached
51cf713e device
macbook:android NikonografferZ$ fasboot devices
-bash: fasboot: command not found
macbook:android NikonografferZ$
And if I plug my phone in Fastboot mode from start on my mac he don't recognize it ..
Click to expand...
Click to collapse
>macbook:android NikonografferZ$ fasboot devices
>fasboot

pro castinato said:
Hey man so here is the problem . I can recognize my One with adb , but can't fasboot after on my mac ...
Here are the commands :
macbook:android NikonografferZ$ ./adb devices
List of devices attached
51cf713e device
macbook:android NikonografferZ$ fasboot devices
-bash: fasboot: command not found
macbook:android NikonografferZ$
And if I plug my phone in Fastboot mode from start on my mac he don't recognize it ..
Click to expand...
Click to collapse
You are missing the "t" in fastboot. You wrote "fasboot", but it should be "fastboot". If that doesnt work, try adding the ./ prefix. ie: "./fastboot devices".

Chromium said:
You are missing the "t" in fastboot. You wrote "fasboot", but it should be "fastboot". If that doesnt work, try adding the ./ prefix. ie: "./fastboot devices".
Click to expand...
Click to collapse
Man I win i Unlock Bootloader and I flash TWRP but is it normal when I restart in recovery I still have the Cyanogen Simple Recovery ?? Damn .....
EDITED !!!! FINALLY ROOTED MY ONE PLUS ONE !!!!!!! Finally read read read 18536 threads and I win ahahha

pro castinato said:
Man I win i Unlock Bootloader and I flash TWRP but is it normal when I restart in recovery I still have the Cyanogen Simple Recovery ?? Damn .....
Click to expand...
Click to collapse
Open settings > developer options. Then look for an option that says 'Update recovery with system updates' and disable it.

Thank you for this guide, it was very easy to follow. I am now rooted and ready to spice this phone up
Sent from my One using Tapatalk

pro castinato said:
l
EDITED !!!! FINALLY ROOTED MY ONE PLUS ONE !!!!!!! Finally read read read 18536 threads and I win ahahha
Click to expand...
Click to collapse
Haha, nice. What got it to finally work?
Sent from my HTC Desire using XDA Free mobile app

Chromium said:
Haha, nice. What got it to finally work?
Sent from my HTC Desire using XDA Free mobile app
Click to expand...
Click to collapse
Some problems with the T of fastboot lol nope some drivers weird to install .. I needed to install driver even for fastbooted device with Pda.net app who work really fine !! I really thanks the pdanet software <3

[GUIDE] Return your M9 (WWE) to 100% Stock - S-OFF REQUIRED

This brief guide will allow you to return your M9 WWE to Stock rom and:
Bootloader LOCKED
**Software Status: Official***
OPTIONAL - S-ON
REQUIRED:
- S-OFF
- Root
- ADB/fastboot
- install HTC drivers
- Battery at least 30% ( but recommended 50-70%)
- SDcard (max 32GB)
Link to Ruu.zip (1.32.401.8) : https://drive.google.com/file/d/0B17smFr95pleMjhDVXVlTjlmX0U/view?usp=sharing - thanks @djluisbento
list of supported CID/MID
modelid: 0PJA10000
cidnum: HTC__001
cidnum: HTC__J15
cidnum: HTC__031
cidnum: HTC__102
cidnum: HTC__A07
cidnum: HTC__032
cidnum: HTC__M27
cidnum: HTC__016
cidnum: HTC__002
cidnum: HTC__Y13
0. RUU.zip = Full Data Wipe from your phone
1. Change your CID ( reboot to DOWNLOAD MODE) for example:
HTML:
fastboot oem writecid HTC__032
fastboot reboot
1a OPTIONAL. Change your MID ( reboot to DOWNLOAD MODE) - thanks @scotty1223
HTML:
fastboot oem writemid 0PJA10000
fastboot reboot
2. LOCKED Bootloader ( to flag LOCKED not RELOCKED) - thanks @scotty1223
HTML:
adb shell
su
echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
exit
exit
3. Download "RUU.zip" ( 1.32.401.8) , rename to 0PJAIMG and put in SDcard
4. Reboot to download mode:
5. Press VOL UP to start flash.
6. After the end of the process, select the "power" and run devices
7. Profit
OPTIONAL: If you want your device was S-ON ( reboot to Download MODE)
HTML:
fastboot oem writesecureflag 3
***I am not responsible for any problems during process to return stock romu ***

Thanks!
Enviado desde mi HTC One M9

More RUU's can be found here >> http://www.androidruu.com/?developer=M9
And I posted my collection of AT&T and Developer Edition RUU's here >> https://www.androidfilehost.com/?w=files&flid=28823
You would of coarse have to adjust the commands to match your CID and MID requirements

The rom in OP works but it doesn't let me change brightness, enable power save/extra power save or airplane mode.
Also this keeps popping up every 30-45 seconds
{
"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"
}
and it comes from an app called Demo which you can't delete. This rom is more than likely taken out from a display unit.
clsA said:
More RUU's can be found here >> http://www.androidruu.com/?developer=M9
And I posted my collection of AT&T and Developer Edition RUU's here >> https://www.androidfilehost.com/?w=files&flid=28823
You would of coarse have to adjust the commands to match your CID and MID requirements
Click to expand...
Click to collapse
I changed the CID & MID back to what it was originally (DEV edition) but it wouldn't find the flie for some reason while in download mode, had to change the CID & MID back to the ones on the list and it did pick it up but then it gives me an error while flashing (failed: -2, 7: fail to flash via downloadzip).

haZethew0rld said:
The rom in OP works but it doesn't let me change brightness, enable power save/extra power save or airplane mode.
Also this keeps popping up every 30-45 seconds and it comes from an app called Demo which you can't delete. This rom is more than likely taken out from a display unit.
I changed the CID & MID back to what it was originally (DEV edition) but it wouldn't find the flie for some reason while in download mode, had to change the CID & MID back to the ones on the list and it did pick it up but then it gives me an error while flashing (failed: -2, 7: fail to flash via downloadzip).
Click to expand...
Click to collapse
you have to use the included htc_fastboot or
You can also use the 0PJAIMG.ZIP method
rename the RUU.zip to 0PJAIMG.ZIP, place it on ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree
If you have problems with the normal fastboot flashing any RUU you'll have to use the htc_fastboot pulled from the RUU.EXE
you can download it here >> https://www.androidfilehost.com/?fid=96039337900114016 >> Thanks go to @Sneakyghost for sharing
With the phone in download mode
htc_fastboot oem rebootRUU
htc_fastboot flash zip RUU.zip
htc_fastboot flash zip RUU.zip <this may not be needed it might restart on it's own>
htc_fastboot reboot
Click to expand...
Click to collapse

clsA said:
you have to use the included htc_fastboot or
You can also use the 0PJAIMG.ZIP method
rename the RUU.zip to 0PJAIMG.ZIP, place it on ext sd card formatted in FAT32 (a 16 or 32gig one should work), reboot into DOWNLOAD_MODE, agree
Click to expand...
Click to collapse
It fails doing the 0PJAIMG.zip method. I noticed htc_fastboot is an exe program, I will try it on my Windows side and will report back in a few.
EDIT: just changed the CID & MID back to their original developer edition status, and it seemed to have worked

haZethew0rld said:
It fails doing the 0PJAIMG.zip method. I noticed htc_fastboot is an exe program, I will try it on my Windows side and will report back in a few.
EDIT: just changed the CID & MID back to their original developer edition status, and it seemed to have worked
Click to expand...
Click to collapse
was your ext sdcard fat32 - 16 or 32 gig ?

clsA said:
was your ext sdcard fat32 - 16 or 32 gig ?
Click to expand...
Click to collapse
It's 32gb not sure if fat or ntfs, I've only formatted it through the phone, so I'm guessing fat. Thanks anyways.

haZethew0rld said:
It's 32gb not sure if fat or ntfs, I've only formatted it through the phone, so I'm guessing fat. Thanks anyways.
Click to expand...
Click to collapse
if you formatted it with the phone it is likely exfat and it won't work. It must be fat32

clsA said:
if you formatted it with the phone it is likely exfat and it won't work. It must be fat32
Click to expand...
Click to collapse
Hmm. Anyways I'm already back on the dev edition software, so I guess it wasn't as important anyways. Thanks

Whats the difference betwen WWE and stock?
Sent from my HTC One M9 using XDA Free mobile app

This works on T-Mobile variant too. I did this a few days ago thanks to Scotty1223 & Behold_This and others in that other forum thread.

magnum15 said:
Whats the difference betwen WWE and stock?
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
WWE- World Wide English ( unbranded version X.XX.401.X)
STOCK- clean,unmodified rom from HTC
So- Stock rom WWE ( x.xx.401.x) - rom unbranded /variant europen form HTC

Nice guide,sir. Just wanted to throw out here folks need to make sure the phone is charged prior to flashing an ruu via any method.

scotty1223 said:
Nice guide,sir. Just wanted to throw out here folks need to make sure the phone is charged prior to flashing an ruu via any method.
Click to expand...
Click to collapse
Thx.
Good point I add information about this in #1 post

Is it necessary to lock bootloader while flashing RUU in S-OFF devices ? I've flashed RUU many times in UNLOCKED position with M7.
Can we flash 0PJAIMG.zip from fastboot:
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip 0PJAIMG.zip
and again:
Code:
fastboot flash zip 0PJAIMG.zip
Is this RUU suitable with HTC__M27 CID devices or can we modify android-info.txt in RUU.zip to flash RUU properly?

coolberry said:
Is it necessary to lock bootloader while flashing RUU in S-OFF devices ? I've flashed RUU many times in UNLOCKED position with M7.
Click to expand...
Click to collapse
No, lock it's not necessary to flash RUU (but if you want to have your phone out of the box it as )
coolberry said:
Can we flash 0PJAIMG.zip from fastboot:
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip 0PJAIMG.zip
and again:
Code:
fastboot flash zip 0PJAIMG.zip
.
Click to expand...
Click to collapse
Of course we can flash rom.zip via fastboot but this method will not restore ***status : official*** ( I checked it several times)
coolberry said:
Is this RUU suitable with HTC__M27 CID devices or can we modify android-info.txt in RUU.zip to flash RUU properly?
Click to expand...
Click to collapse
probably yes, but I can't confirm

And whats the benefit stock vs. Wwe?
Sent from my HTC One M9 using XDA Free mobile app

my device is now locked, official and s-on
big thanks to @Mutasek24 and @scotty1223 :good:

I'm guessing that flashing the official RUU (regardless of variant, as long as you flash the correct RUU for the given variant) removes the red "development' text from the HTC splash screen?
Thank you so much for this guide!

[Guide For Beginners] - How To Root, Update, Tweak, and Fix Honor 7

Huawei Honor 7
– Complete Guide For Beginners –
Optimized For (PLK-L01)
Updating | Rooting | Tweaking | Fixing
​
In this guide, you will learn the following:
Part I - How to install the latest full ROM for Huawei Honor (PLK-L01).
Part II - How to root Huawei Honor 7.
Part III - How to fix bootloops if things did not go as expected.
Part IV - The most used adb commands.
Part V - The most used fastboot commands.
Part VI - How to change the default boot animation.
Part VII - How to change the default splash screen.
Appendix A - Honor 7 Key Combinations Summary.
Appendix B - How to update Huawei Honor 7 from (B100) to (B180).
Appendix C - Available Custom ROM(s).
Appendix D - Extra Resources.
Appendix E - All Important Downloads.
Notes & Credits:
This guide is written for the absolute beginners who had hard times reading other tutorials on this forum that explains the same set of topics.
This guide is primary written for Microsoft Windows users. Many sections though can be applied to other operating systems.
There are other great guides on this forum that teaches the same stuff but not in a very detailed beginner-friendly way. Special credits go to @piskr for his guide on this topic.
Additional credits go to @DigiGoon and @sminki for their contribution on fixing and updating this guide.
Special credits go to @Ziolek67 and @Kostyan_nsk for their original posts on the splash screen topics.
Special thanks to the Labinator team for their support throughout this guide.
If you have something to add or improve on this guide, please reply to this post and we will be more than happy to update it.
Warning: No one is responsible for what happens to your device while attempting to follow the below guide. Create backups before every section and know the risks before starting out.
Part I - How To Install The Latest Full ROM For The Model (PLK-L01)​
Step 1: Download the latest full ROM for Honor 7 from the below link:
http://www.modaco.com/forums/topic/375942-roms-honor-7-stock-rom-images/
Step 2: Extract the (.zip) file and copy the "UPDATE.app" file to your (dload) folder in your external SD card.
Step 3: Make sure the current recovery that is installed is the default stock one and not a custom recovery like TWRP. If you have TWRP installed, make sure to flash the stock recovery before you attempt the update process.
Step 4: Turn off your phone, then press both the Volume Up + Volume Down + Power Key. Then release the power key as soon as you see the initial splash screen.
Step 5: The Huawei eRecovery will start and will update your device from the "UPDATE.app" file that you had placed in your (dload) folder automatically.
Part II - How To Root Huawei Honor 7​
Stage 1 – Unlock The Bootloader
Part 1.1 – Getting The Unlock Password
Step 1: Login by clicking here.
Step 2: Click on “Unlock Bootloader”.
Step 3: Accept the unlocking agreement.
Step 4: Fill up the unlock password form as follows:
Product: Smartphone.
Model: (e.g. PLK-L01)
Product Serial Number: Settings -> Status -> Serial Number - > (e.g. H8WDU15814000010)
Product IMEI/MEID (IMEI 1): Settings -> Status -> IMEI1 -> (e.g. 867898020305536)
Product ID: Open the dial up and type: *#*#1357946#*#* -> (e.g. 88429554)
Verification Code: Type the Captcha.
Step 5: Press submit and obtain the unlocking password in red (e.g. 1078018121593242).
Step 6: Store the code obtained in step 5 somewhere safe.
Part 1.2 – Preparations
Step 6: Download and install the latest version of the "15 Seconds ADB Installer”. You can find the download link at >
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
Step 7: Download and install the latest version of “HiSuite – Android Smart Device Manager”.
You can find the download link at >
http://consumer.huawei.com/minisite/HiSuite_en/
Step 8: Enable the “Developer options” by going to:
Settings -> About Phone -> Build Number
Tap on the build number 10 times quickly. A message must appear alerting you that the developer mode has been enabled.
Go to the “Developer options” and enable “USB debugging”.​
Part 1.3 – Booting into Fastboot Mode
Step 9: Power the phone off.
Step 10: Boot the phone into “fastboot mode” by pressing the below keys.
[Volume Down] + [Tap on Power Button]. You can release the power button as soon as you see the initial splash screen.​
Note 1: You must enter the fastboot mode directly after pressing the above keys.
Note 2: In case (Step 10) did not work, then turn off your phone again then insert the USB cable and connect it with your computer. After that, press the same combination mentioned above for 10 seconds. Note 3: You can also boot into the fastboot mode using the following command >​
Code:
adb reboot bootloader
​
Step 11: Connect your phone with your PC. Use a USB cable to connect your phone with your computer while your phone is in the fastboot mode.
Step 12: Open your “Command Prompt (cmd)” and type >
Code:
fastboot devices
Note: The second command must show that your device is in fastboot mode.​
Part 1.4 – Perform The Unlock Command
Step 13: Perform the unlock command > fastboot oem unlock ***, where *** is the 16 characters unlock code.
Code:
fastboot oem unlock 1078018121593242
Note: You need of course to replace "1078018121593242" with your unique 16 characters unlock code.
Step 14: Wait for the phone to get unlocked. It will automatically restart if you have entered the correct code.
Step 15: Test if the phone is successfully unlocked by entering the following command >
Code:
fastboot oem get-bootinfo
Case 1: If you have got the message of “Bootloader Lock State: UNLOCKED”, then your phone has been successfully unlocked.
Case 2: If you have got the message of “Bootloader Lock State: LOCKED”, then your phone is still locked.​
Note: if you want to re-lock the phone, please check this thread for more details on that. Thanks to @sminki for posting that up and highlighting this point.​
Stage 2 – Install Custom Recovery
Step 16: Open your command prompt, and navigate to the right directory where your recovery image file is located. You can do that using this command:
Navigate to the right directory:
[“Directory Letter”]:
Examples: D:, C:, or E:
Navigate to the right folder:
cd [“Full Path Of Directory”]
Example: cd /Users/User1
​
Step 17: Test if your device is detected by typing the following command while you are in the bootloader mode:
Code:
fastboot devices
​ > If you got the right messages that your device is properly connected, then you can proceed to step 18.
​
Step 18: Type the following command to flash the recovery image (TWRP). The recovery image is in English and you can download it from this link. Make sure to download it and place it in the right directory before typing the below command line.
Code:
fastboot flash recovery recovery.img
​ After the completion of that, simply reboot your device using the following command >
Code:
fastboot reboot
Note: “recovery.img” is the name of the TWRP recovery image. You need to replace this name with the name of your recovery image (e.g. twrp-3.0.2-0-plank.img).​
Stage 3 – Root The Device
Step 19: Download the latest SuperSU version from this link and place it on your hard disk then copy it to your phone. You can copy the file from your computer to your device using this command >
Code:
adb push SuperSU-vX.zip /sdcard/
​Note 1: You must be in the right directory of the “SuperSU” file or else the above command will not work.
Note 2: You must replace "SuperSU-vX" with the right name of your SuperSU file (e.g. BETA-SuperSU-v2.71-20160331103524.zip)​
Step 20: When the process of flashing the recovery is done, reboot your device into the recovery mode using the following command >
Code:
adb reboot recovery
​
Step 21: After finishing step 20 successfully, your phone would have been booted into the recovery mode. You will be able to see the TWRP home screen. From there, click on the “Install” option then navigate to your /sdcard/ directory where you have copied or pushed your "SuperSU-vX.zip" file.
Step 22: Find the "SuperSU-vX.zip" file and install it.
Step 23: Navigate back to the home page of TWRP then click on the “Reboot” button in order to boot into the system.
Step 24: Double check if your device has been rooted successfully by testing it using one of those root checker applications. There are many of them around the Google Play store.
Part III - Useful ADB Commands​
Code:
adb devices
adb reboot
adb reboot bootloader
adb reboot recovery
adb push [source] [destination]
adb pull [source] [destination]
adb backup
adb shell
Part IV - Useful Fastboot Commands​
Code:
fastboot devices
fastboot reboot
fastboot reboot-bootloader
fastboot boot recovery recovery.img
fastboot flash [Partition] [Image]
fastboot oem unlock [Unlock Code]
fastboot oem relock [Relock Code]
Note: Use your favorite search engine to search the above commands and learn more about them.
Part V - How To Fix Bootloops​
Breaking out of bootloops depends on your device state and what kind of problem you are having. In this section, we are going to focus on the popular case where you can’t access neither the system nor the recovery partitions.
Step 1: Turn off the phone.
Step 2: Press the following buttons:
[Volume Down] + [Tap on Power Button]. You can release the power button as soon as you see the initial splash screen.
Step 3: Head to your computer and download and install the following tool:
http://forum.xda-developers.com/showthread.php?t=2433454
Step 4: Download the latest complete update file (B121) or (B330b) depending on which system you had installed before the bootloop problem. You can download it from:
http://www.modaco.com/forums/topic/375942-roms-honor-7-stock-rom-images-updates-121115-b140/
Then, extract it and get its UPDATE.app file.
Step 5: Use the Huawei Update Extractor to extract the (BOOT.img), (SYSTEM.img), (RECOVERY.img), (CACHE.img), (CUST.img), and (USERDATA.img) from the UPDATE.app file that you have extracted from Step 4.
Step 6: Open your command prompt, and navigate to the right directory where you have extracted the image files. Use the “cd” and “..” commands to do so.
Step 7: Type the following commands and execute them one by one >
Code:
fastboot flash boot BOOT.img
fastboot flash system SYSTEM.img
fastboot flash recovery RECOVERY.img
fastboot flash cache CACHE.img
fastboot flash cust CUST.img
​
Step 8: You can also erase the user data if you like by typing and executing the following >
Code:
fastboot flash userdata USERDATA.img
​
Step 9: Reboot your device using the following command >
Code:
fastboot reboot
​
Step 10: You must be able to boot successfully into the system.
Step 11: After booting successfully, apply again the steps mentioned in Part I.
Important Note 1: If the "fastboot flash" is reporting "FAILED <remote: command not allowed>", you need to unlock your device again even if the bootloader is stating that your device has already been unlocked.
Important Note 2: When breaking out of bootloops or frozen splash screens, you need always to flash the right partitions that match up with the previous partitions that you had installed on your system before the occurrence of the bootloop.
Part VI - How To Change The Boot Animation​
Step 1: Root Your Device.
Step 2: Create a full Nandroid backup.
Step 3: Create your own animation or download one online. Note that you need the resolution to be (1080 x 1920 pixels). It should not last more than 10-12 seconds at most.
Step 5: Your animation files must be compressed and renamed as: “bootanimation.zip”.
Step 6: Change the permissions of your .zip file to (rw-r-r).
Step 7' - (In case you are running Android 5.x): Navigate to /Cust/Preinstalled/Public/Media and backup the original “bootanimation.zip” file somewhere safe on your hard drive or sdcard.
Step 7'' - (In case you are running Android 6.x): Navigate to /system/etc/media and backup the original “bootanimation.zip” file somewhere safe on your hard drive or sdcard.
Step 8' - (In case you are running Android 5.x): Copy your newly created bootanimation.zip file to the directory /Cust/Preinstalled/Public/Media and replace the original file.
Step 8'' - (In case you are running Android 6.x): Copy your newly created bootanimation.zip file to the directory /system/etc/media and replace the original file.
Step 9: Reboot and check up your new boot animation.
My original post of this section is available at: http://forum.xda-developers.com/showpost.php?p=63828825&postcount=2
Part VII - How To Change The Splash Screen​
Requirements:
Your device must be rooted. Follow the steps in Part II in case you have not rooted your device yet.
You must have downloaded and installed the latest version of the "15 Seconds ADB Installer”.
You can find the download link at: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
You need to make a complete backup or a nandroid backup before starting up. You can create a nandroid backup using the custom recovery of TWRP.
Steps:
Turn on your device and connect it to your computer then open the command prompt or your terminal as an administrator.
Make sure your computer can read the data on your phone and all the drivers are installed properly.
Make sure the following command is returning the name of your device:
Code:
adb devices
Save your "oeminfo" to your SDCard:
Code:
adb shell su -c "dd if=/dev/block/platform/hi_mci.0/by-name/oeminfo of=/sdcard/oeminfo"
Download this zip file and extract it to your desktop or any location of your choice.
From your opened command prompt, navigate to the extracted zip folder that you have downloaded in Step 5. Use the "cd" command to do that.
Create your new splash screen logo as follows:
Step 1: Open your Adobe Photoshop and create a new file that has the following parameters
Width: 1080 pixels
Height: 1920 pixels
Resolution: 72 pixels/inch
Color Mode: RGB Color, 8-bit
Step 2: After creating your new image, save it as follows:
Extension: *.bmp
From the "Advanced Options", select R5 G6 B5 from the 16-bit depth options.
Save your newly created image in Step 7, in the same folder that you have extracted in Step 5.
From your command prompt, type the following command:
Code:
OEM_logo.exe oeminfo your_logo.bmp
Replace "your_logo.bmp" with the name of your logo.
The above command will create a new oeminfo for you that has your new logo. It will also replace the old one in the same folder.
Copy your newly created oeminfo to your sdcard by typing the following command:
Code:
adb push oeminfo /sdcard/oeminfo
Copy your oeminfo from your sdcard to the right partition on your device:
Code:
adb shell su -c "dd bs=32768 if=/sdcard/oeminfo of=/dev/block/platform/hi_mci.0/by-name/oeminfo"
Reboot your device and check the new splash screen.
Note: The original post of this section can be found at this link.
Credits: Special credits goes to @DigiGoon, @sminki, @Ziolek67, and @Kostyan_nsk for their amazing contribution in writing, testing, and adjusting on the original post of this section of the guide.
Appendix A - Honor 7 Key Combinations Summary​
[Without Plugging The Device]:
Volume Down + Tap Power Button -> Normal Boot.
Volume Up + Tap Power Button -> Recovery Mode (e.g. TWRP).
Both Volume Buttons + Tap Power Button -> Flash (dload) Image From External MicroSD Card.
[While Connecting The Device To Your Computer]
Volume Down + Power On -> Fastboot Mode - (Tip: You can exit from this mode with a long power button press).
Volume Up + Power On -> Huawei eRecovery.
Both Volume Buttons + Power On -> Flash Image via HiSuite.
Appendix B - How To Update From B100 to B180
For The Model (PLK-L01)​
Important Note: Please update your device before rooting it. You will lose your root access if you attempt to update after rooting your device.
Step 1: Download the latest stock ROM for Honor 7 from the below link:
http://www.modaco.com/forums/topic/375942-roms-honor-7-stock-rom-images/
Step 2: Download the B121 EMUI 3.1 update package.
Step 3: Download the B180 incremental update package (B121 to B180).
Step 4: Extract the B121 update zip file and get the UPDATE.app file from it.
Step 5: Copy the UPDATE.app file from your computer to the /sdcard/dload/ directory.
Step 6: Launch your device and go to: Settings -> Updater -> Menu -> Local Update and choose the UPDATE.app file.
Step 7: Install the update and wait until it reboots again. Check if the update is working successfully.
Step 8: Copy the B180 (B121 to B180) incremental update zip file from your computer to the /sdcard/dload/ directory.
Step 9: Make sure the name of your update zip file is “update.zip”.
Step 10: Apply the update by going to: Settings -> Updater -> Menu -> Local Update and choosing the update.zip file.
Step 11: Install the update and wait until it reboots again. Check if the update is working successfully.
Step 12: Delete the update.zip file from your /sdcard/dload/ directory.
Appendix C - Available Custom ROM(s)​
r3 - Custom Rom Starter Template: http://forum.xda-developers.com/honor-7/development/r1-custom-rom-starter-template-honor-7-t3337901
r2 - MoDaCo Custom Kernel: http://forum.xda-developers.com/honor-7/development/kernel-r1-modaco-custom-kernel-t3365909
MoDaCo Custom Rom: http://forum.xda-developers.com/honor-7/development/r1-custom-rom-starter-template-honor-7-t3337901
YodaRom: http://forum.xda-developers.com/honor-7/development/rom-6-0-x-yodarom-v1-0-mm-rooted-ads-t3338179
DigiRom: http://forum.xda-developers.com/honor-7/development/rom-digirom-gpe-v1-t3365391
H7T Rom: http://forum.xda-developers.com/honor-7/development/rom-codename-h7t-t3396002
You can view all available custom ROM(s) at: http://forum.xda-developers.com/honor-7/development
Appendix D - Extra Resources​
How to build your own kernel for Honor 7: http://forum.xda-developers.com/honor-7/general/guide-how-to-build-kernel-honor-7-t3363894
Honor 7 Multi-Tool: http://forum.xda-developers.com/honor-7/general/honor-7-multi-tool-t3281176
Spectrum Pure Theme: http://forum.xda-developers.com/honor-7/themes-apps/theme-spectrum-pure-base-theme-t3321234
Appendix E - All Important Downloads​
All Stock ROMs and OTA Updates: http://www.modaco.com/forums/topic/...ck-rom-images-updated-1st-april-2016-plk-l01/
The Latest Version Of "TWRP": https://dl.twrp.me/plank/
The Latest Version Of "SuperSU": https://download.chainfire.eu/supersu
The Latest Version Of "15 Seconds ADB Installer": http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
The Latest Version Of "Huawei Update Extractor": http://forum.xda-developers.com/showthread.php?t=2433454
Access the "Huawei Bootloader Unlocker": https://hwid5.vmall.com/oauth2/portal/cloud_login.jsp

Awesome and very helpful guide @kenshiwara

Thank you for this guide.
If I understand, we can update if twrp is installed?
Envoyé de mon Nexus 5

No offence but this is just @piskr 's thread re-typed with some serious errors added to it.
Did you try "fastboot oem relock"? I started a thread on that, it doesn't work.
Did you try any of the "fastboot erase" commands? As when I tried it wouldn't - "Command not allowed"
The Huawei extract tool doesn't get the names of the images on the current full ROMS (tested on B121 and a few of the Chinese ROMS) it doesn't have the mappings for these. However it has worked with incremental patches..
Extracting the files and only flashing a few like system will leave you with and inconsistent device (if from different versions). Those 20+ files have a reason - modem, sensorhub, trustfirmware, teeos (whatever that is!), etc.. There are actually something like 40 block devices on the H7 (/dev/block/platform/hi_mci.0/by-name/). To run an official update on that system would almost certainly result in failure. (I have tried)
..and flashing a whole system doesn't fix a boot-loop. That's flashing the whole system, it goes away because whatever was causing it has been deleted/wiped. If that's the idea, better off flashing Huawei's recovery and doing a full UPDATE.APP of B100 / B121 and moving up.
Oh and just one more minor thing - holding the power button isn't required, turn the phone on and hold either down (with usb data connected) for boot-loader, or up for recovery
Sorry... I know you mean well, however posting things in good faith is dangerous. Especially in a guide aimed at beginners.

sminki said:
No offence but this is just @piskr 's thread re-typed with some serious errors added to it.
Did you try "fastboot oem relock"? I started a thread on that, it doesn't work.
Did you try any of the "fastboot erase" commands? As when I tried it wouldn't - "Command not allowed"
The Huawei extract tool doesn't get the names of the images on the current full ROMS (tested on B121 and a few of the Chinese ROMS) it doesn't have the mappings for these. However it has worked with incremental patches..
Extracting the files and only flashing a few like system will leave you with and inconsistent device (if from different versions). Those 20+ files have a reason - modem, sensorhub, trustfirmware, teeos (whatever that is!), etc.. There are actually something like 40 block devices on the H7 (/dev/block/platform/hi_mci.0/by-name/). To run an official update on that system would almost certainly result in failure. (I have tried)
..and flashing a whole system doesn't fix a boot-loop. That's flashing the whole system, it goes away because whatever was causing it has been deleted/wiped. If that's the idea, better off flashing Huawei's recovery and doing a full UPDATE.APP of B100 / B121 and moving up.
Oh and just one more minor thing - holding the power button isn't required, turn the phone on and hold either down (with usb data connected) for boot-loader, or up for recovery
Sorry... I know you mean well, however posting things in good faith is dangerous. Especially in a guide aimed at beginners.
Click to expand...
Click to collapse
Thank you for your comments and notes. It is great to see your contribution up there.
This was actually my personal guide that i wrote to help myself around while operating on this device (PLK-L01). Based on your comments, there are several sections that require fixing. Would you mind taking the time to re-write those sections in a step-by-step fashion in order to update the guide?
You disagree with the section of "How to fix the bootloop when you can't access neither the system nor the recovery partitions". My solution - which worked for me - was to erase and flash the main partitions. Still though, if you have a better method, please share it with the whole community in a step-by-step fashion. Everyone will be grateful.
We mainly need the following:
1. How to re-lock the phone if the command of "fastboot oem relock" is not working on some models?
2. How to break out of bootloops if we can't access the system or the recovery partitions? (and flashing the main partitions from fastboot is not a stable solution in your opinion).
If you can provide a detailed step-by-step guides addressing the above two points, i would surely be more than happy to update them in the guide. Please note that the above guide is mostly tested on PLK-L01. Please, always mention your model number when writing your notes.
Thanks again for sharing your results with the community and hope you can send us a better version on the above sections based on your findings.

Freebob94 said:
Thank you for this guide.
If I understand, we can update if twrp is installed?
Click to expand...
Click to collapse
TWRP is not required at all if you are just updating. You should root your device after applying all the updates rather than before.
Thank you for comment!

sminki said:
Did you try "fastboot oem relock"? I started a thread on that, it doesn't work.
Did you try any of the "fastboot erase" commands? As when I tried it wouldn't - "Command not allowed"
Click to expand...
Click to collapse
Well me and @kenshiwara both tried it after stucking in bootloop and those commands worked like a charm

kenshiwara said:
Thank you for your comments and notes. It is great to see your contribution up there.
Thanks again for sharing your results with the community.
Click to expand...
Click to collapse
I'm glad you too my reply as intended and not just an angry rant!
DigiGoon said:
Well me and @kenshiwara both tried it after stucking in bootloop and those commands worked like a charm
Click to expand...
Click to collapse
Guessing by your location, you have the Indian single sim version?

sminki said:
I'm glad you too my reply as intended and not just an angry rant!
Guessing by your location, you have the Indian single sim version?
Click to expand...
Click to collapse
No, I have European model PLK-L01, thanks to @kenshiwara
---------- Post added at 07:48 PM ---------- Previous post was at 07:46 PM ----------
sminki said:
I'm glad you too my reply as intended and not just an angry rant!
Click to expand...
Click to collapse
LOL, yeah, some people or developers would have taken it as angry rant but we all are here to learn and help each other.

OK, well I also have an EU PLK-L01 with unlocked bootloader. I re-tested the following today to confirm my initial findings:
fastboot oem get-bootinfo
Code:
...
[COLOR="Green"][B](bootloader) unlocked[/B][/COLOR]
OKAY [ 0.000s]
finished. total time: 0.000s
fastboot erase system
Code:
erasing 'system'...
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
finished. total time: 0.000s
fastboot erase userdata
Code:
erasing 'userdata'...
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
finished. total time: 0.000s
fastboot -w
Code:
Erase successful, but not automatically formatting.
[B]Can't determine partition type.[/B]
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
Erase successful, but not automatically formatting.
[B]Can't determine partition type.[/B]
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
erasing 'userdata'...
[COLOR="Red"][B]FAILED (remote: Command not allowed)[/B][/COLOR]
finished. total time: 0.000s
This was the same for any of the B1xx firmwares.
DigiGoon said:
Well me and @kenshiwara both tried it after stucking in bootloop and those commands worked like a charm
Click to expand...
Click to collapse
You locked the bootloader to fix boot-loop? That's a bad idea!

sminki said:
You locked the bootloader to fix boot-loop? That's a bad idea!
Click to expand...
Click to collapse
Never locked it, just flashed SYSTEM.img by executing
Code:
fastboot flash system SYSTEM.IMG
and it worked.

DigiGoon said:
Never locked it, just flashed SYSTEM.img by executing
Code:
fastboot flash system SYSTEM.IMG
and it worked.
Click to expand...
Click to collapse
Well, in post #7 you wrote this:
------------------------------------------
{
"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"
}
------------------------------------------
However, your answer above says otherwise. Erase and flash are not the same thing
One of my main criticisms on the original post was that fastboot erase doesn't work, I went a long way to back this up in post #10

sminki said:
Well, in post #7 you wrote this:
------------------------------------------
------------------------------------------
However, your answer above says otherwise. Erase and flash are not the same thing
One of my main criticisms on the original post was that fastboot erase doesn't work, I went a long way to back this up in post #10
Click to expand...
Click to collapse
Sorry, that was my mistake but I never erased the partition, directly flashed it

DigiGoon said:
Sorry, that was my mistake but I never erased the partition, directly flashed it
Click to expand...
Click to collapse
Cool thanks. I can sleep easy now :highfive:

sminki said:
Cool thanks. I can sleep easy now :highfive:
Click to expand...
Click to collapse
I have updated the original thread highlighting your comments while fixing it according to our latest tests. Please read it up again and inform us if you have anything else to improve on it.
Out of 500 views, only you decided to take few minutes and help in improving this guide. Thank you for your time and know that your support will be appreciated by all the community of XDA-Developers.

Hi there beautiful people.
I'm getting some error updating after installing tw recovery.
Code:
Checking MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to start
E:Error executing updater binary in zip '/external_sd/dload/update.zip
E:Error installing zip file '/external_sd/dload/update.zip
Now backupping, i'm going to try to flash the zip (i'ts a stupid thing?).
Edit: Did not work either. Cannot update using twrp; the update app reboots directly in the custom recovery.
Currently on B121, it already had it. PLK-L01 europe.
Also, do you really think Haweii will public codes? I'm not so optimistic.

Smokehrbar88 said:
Hi there beautiful people.
I'm getting some error updating after installing tw recovery.
Code:
Checking MD5 file...
Skipping MD5 check: no MD5 file found
file_getprop: failed to start
E:Error executing updater binary in zip '/external_sd/dload/update.zip
E:Error installing zip file '/external_sd/dload/update.zip
Now backupping, i'm going to try to flash the zip (i'ts a stupid thing?).
Currently on B121, it already had it. PLK-L01 europe.
Also, do you really think Haweii will public codes? I'm not so optimistic.
Click to expand...
Click to collapse
If that update.zip is from Huawei it won't work in TWRP.
You need Huawei recovery to install Huawei updates.

sminki said:
If that update.zip is from Huawei it won't work in TWRP.
You need Huawei recovery to install Huawei updates.
Click to expand...
Click to collapse
Indeed, it sounds pretty logic. So i should revert the stock recovery, update and then reinstall twrp.
Can I do it simply pushing trough adb? And where should I find the recovery.img?
Thanks for the help.

Smokehrbar88 said:
Indeed, it sounds pretty logic. So i should revert the stock recovery, update and then reinstall twrp.
Can I do it simply pushing trough adb? And where should I find the recovery.img?
Thanks for the help.
Click to expand...
Click to collapse
You have to extract them from the UPDATE.APP file!
I've done the work for you.. B121 recovery attached
Unizp, then
Code:
fastboot flash recovery B121_recovery.img
(like you did with twrp)
Then put TWRP back on.
I forgot to add - if the system partition is altered (su) then the official update may well fail..

sminki said:
I've done the work for you.. B121 recovery attached
Click to expand...
Click to collapse
I was downloading the full rom myself, but my internet speed is so slow. My savior, thank you. I hope to not bother you again with my low-tier noob problems.

[Guide] Tired of EMUI ? Here's a full guide on how to install a Treble Rom

So I was tired of EMUI, the UI design isn't really that bad but it really clashed with Android's Material Design, so since our Mate 9 is Treble compatible, I decided to try a few Treble ROMs. After many fails and factory resets, I finally settled on Havoc-OS. Here I made a guide on how to switch to a Treble Rom.
So a few things to note :
There's no (fully) compatible TWRP recovery for Kirin devices. Either they work but cannot flash OpenGApps or they simply don't work with Treble ROMs.
Huawei's eRecovery seems to work. For me at least, it didn't work before. So as usual, BACKUP ALL OF YOUR DATA(Titanium Backup or HiSuite for apps if needed). You can also use TWRP with stock EMUI if you want to backup your partitions in case something goes really bad.
Make sure you're using stock kernel, ramdisk and recovery_ramdisk before starting anything.
A Micro SD card is optional but useful for restoring things or if you don't want to transfer all of your backup data to your PC
USB Debugging isn't really needed.
-------------------Requirements-------------------
- Your phone, obviously. Has to be a Mate 9 (Pro) updated to Android 8.0 Oreo.
- An unlocked bootloader (Since Huawei stopped giving unlock codes, I can't help you on that one. Sorry boys)
- A PC and a USB Type-C cable.
-------------------A. First things first-------------------
Enable OEM Unlocking
An easy thing to do, otherwise you won't be able to flash anything on your phone (FRP will be "Lock" on bootloader screen). You may think that this is kind of a mandatory thing to do since you've unlocked your bootloader, but you can get it back to disabled and greyed out anytime, so here's a reminder.
1. Enable developer options by going to Settings > System > About Phone and taping multiple times on Build Number
{
"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"
}
2. Once that's done, go to Developer Options and enable OEM Unlocking.
-------------------B. Downloads-------------------
1. Download and install Minimal ADB
Click here to download Minimal ADB
2. Download your ROM, right now there are two fully compatible ROMs :
- OpenKirin Builds : https://openkirin.net/download/
- Havoc-OS : https://forum.xda-developers.com/mate-9/development/rom-havoc-os-t3826470
You'll get an img file that you must put inside where you installed Minimal ADB.
3a. For later : Download Huawei Firmware Finder and Huawei Update Extractor
- Huawei Firmware Finder
- Huawei Update Extractor > If you're not running Windows (Mac, Linux) (Thanks to irony_delerium)
- Also download Magisk Manager (This is an APK)
--- OR ---
3b. Download this patched Ramdisk with Magisk included so that you don't have to download all of the above. CREATED WITH BUILD NUMBER MHA-L29 8.0.0.370(C432). USE AT YOUR OWN RISK IF IT DOESN'T EXACTLY MATCH YOUR PHONE BUILD.
Here (name is patched_boot.img)
-------------------C. Installation-------------------
Now that you've got your Rom img and Minimal ADB, we can start installing it.
1. Turn off your phone.
2. Plug your phone into your PC AND hold down the volume down button until you get a (terrible) white screen saying you're in fastboot&rescue mode.
3a. Open a command prompt (with admin rights if possible) on your PC and get to your Minimal ADB directory. By default, it should look like this :
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
3b. If you installed Minimal ADB on a different drive, then type this :
Code:
cd /d {DRIVELETTER}:/{MINIMAL ADB DIRECTORY/}
4. Make sure your phone is detected by typing :
Code:
fastboot devices
This should show up.
5. Now you can start flashing your ROM by typing :
Code:
fastboot flash system {IMGFILE}.img
Your ROM should start flashing with the message 'target reported max download size of 494927872 bytes'
It should take a minute.
Once you see 'finished. total time: times', that means your ROM has been flashed.
Don't reboot just yet. Things won't work
6. Reboot to recovery by turning off your phone (hold down power button for ~5 seconds) and holding volume up.
7. Now that you are in EMUI recovery, do the following :
- Wipe cache
- Wipe data/factory reset
You MUSTdo this otherwise you will have multiple issues.
8. You're done for the installation. Now reboot to system and start your phone first config (again).
-------------------D. Root-------------------
Your Treble Rom isn't rooted by default. But the Treble Rom itself triggers the SafetyNet flag, which means even if your phone is super clean, it is not certified. So it is obviously completely optional, by it is extremely recommended to install Magisk.
If you downloaded the patched_boot.img file in the attachment
The install process will be extremely easy. It will install Magisk 16.7 (only Beta works with Treble right now). So all you have to do is :
Get to fastboot mode by turning off your phone, plugging it to your PC while holding volume down button. Then, type the following command in the same command prompt window :
Code:
fastboot flash recovery_ramdisk patched_boot.img
It should take around 5 seconds. Now you can reboot and download Magisk Manager. But Safetynet will still trigger (if it doesn't, tell me). You'll have to follow E. SAFETYNET.
If you're not using the attachment
1. Check your phone Android version and build number. It is in Settings > About phone. Write it down, you'll need it.
2. (Install and) Open Huawei Firmware Finder. Get in the 'Common Base' tab and type in your phone build number.
3. Find the matching build number in the list. Make sure its type is 'FullOTA-MF' and its size is 2Go+. Then click on the blue link in the 'Filelist' column. Copy paste the first (ending with 'update.zip') in your browser to download the zip file. It should take some time.
4. Once it's downloaded, open it with 7Zip/WinRar and extract the file named 'UPDATE.APP'.
5. Open Huawei Update Extractor, go to the Settings tab and untick everything.
6. Now, go to the Extract tab and click on the dots on the right and select your extracted 'UPDATE.APP'. A ton of files should appear.
7. Right click on 'RAMDISK', and 'Extract selected'. Put it somewhere on your PC, you'll need it.
8. Plug your phone on your computer and put your RAMDISK.IMG in a folder on your phone.
9. On your phone, download and install Magisk Manager. If it prompts you to do so, do not install it. Then go to Settings tab and change 'Update Channel' to 'Beta'.
10. Now go back and tap 'Install', then choose 'Patch Boot Image File' and select your RAMDISK.IMG that you transferred to your phone. Then let Magisk do its thing.
11. Once it's done, on your PC, go to Your Phone/Internal Store/MagiskManager, and transfer the file 'patched_boot.img' to your Minimal ADB folder.
12. Turn off your phone and get to fastboot mode. You know how to do it now, don't you ?
13. In the same command prompt on your PC, type :
Code:
fastboot flash recovery_ramdisk patched_boot.img
It should take around 5 seconds. Now you can reboot and BAM, you're rooted. But Safetynet will still trigger (if it doesn't, tell me). You'll have to follow E. SAFETYNET.
-------------------E. SafetyNet-------------------
Magisk may be installed, but with a Treble Rom, SafetyNet should trigger anyway. So you'll have to do a few things.
1. In Magisk Manager, go to the Downloads tab and search for 'MagiskHide Props Config'. Install it, then reboot your phone.
2a. Once your phone is rebooted, download Terminal Emulator on the Play Store
--- OR ---
2b. Go to developer options and enable 'Local Terminal'.
3. Open your terminal, then type :
Code:
su
(Accept root request)
Code:
props
Things should appear. Woah.
4. Type 1 (Edit device fingerprint), then f, then choose a vendor and a model by typing the right number, then press y. Don't reboot yet (press n)
5. Type 6 (Script settings), then 1, then y. Now you can reboot (press y). Once it's done, make sure that 'boot stage' is 'currently post-fs-data'. Otherwise SafetyNet will still trigger.
THERE YOU GO ! Your phone should pass SafetyNet. You can check this by trying to search for the Netflix app on the Play Store or going into the Play Store settings and making sure your device is Certified'.
If you have any question/bug, do ask/report all of dem to me.

I haven't rooted or done anything with this device since I've bought it coming from all Samsung devices previously. This guide is awesome! Nice work!

About Firmware Finder:
You don't need to install this as a desktop app:
http://pro-teammt.ru/firmware-database/
The page itself is in Russian, but Chrome usually offers to automatically translate, and it's not terribly complex anyway.
There is also the Firmware Finder app in Google Play. Either work.
(This also makes it accessible to those of us who don't run windows as a primary desktop.)
--
If you're not on Windows (Linux, Mac, BSD):
The following GitHub repo contains a Perl script for extracting the contents of UPDATE.APP:
https://github.com/marcominetti/split_updata.pl
Run:
splitupdate UPDATE.APP
The full image will be extracted into a subdirectory "output".

i install Havoc via fastboot ok
but i return stock huawei , install system.img of update.app ok
but now after install stock huawei system my phone lost language portuguese Brazil ...no more all languages

irony_delerium said:
About Firmware Finder:
You don't need to install this as a desktop app:
http://pro-teammt.ru/firmware-database/
The page itself is in Russian, but Chrome usually offers to automatically translate, and it's not terribly complex anyway.
There is also the Firmware Finder app in Google Play. Either work.
(This also makes it accessible to those of us who don't run windows as a primary desktop.)
--
If you're not on Windows (Linux, Mac, BSD):
The following GitHub repo contains a Perl script for extracting the contents of UPDATE.APP:
https://github.com/marcominetti/split_updata.pl
Run:
splitupdate UPDATE.APP
The full image will be extracted into a subdirectory "output".
Click to expand...
Click to collapse
Yup, I'm aware of the Play Store app, but IMO, having everything directly on your PC is more convenient. Also what you said is useful for people not running Windows, so kudos to you for that.

aureliomilitao said:
i install Havoc via fastboot ok
but i return stock huawei , install system.img of update.app ok
but now after install stock huawei system my phone lost language portuguese Brazil ...no more all languages
Click to expand...
Click to collapse
Huh, that's a strange issue. I'd suggest you do this :
- If you don't care about all you data being lost (you got a backup), get to Huawei eRecovery by rebooting your phone and holding volume up button for 3 seconds on the screen saying your bootloader has been unlocked. Then follow the indications on screen, by choosing 'Download latest version'
- The fact that you can't choose any language is odd, as all languages are included in system.img. So you probably got a... kind of faulty system.img from your update.app, which is also strange.

Deytron said:
Huh, that's a strange issue. I'd suggest you do this :
- If you don't care about all you data being lost (you got a backup), get to Huawei eRecovery by rebooting your phone and holding volume up button for 3 seconds on the screen saying your bootloader has been unlocked. Then follow the indications on screen, by choosing 'Download latest version'
- The fact that you can't choose any language is odd, as all languages are included in system.img. So you probably got a... kind of faulty system.img from your update.app, which is also strange.
Click to expand...
Click to collapse
i extract system.img in update.app ...and lost Brazil language

aureliomilitao said:
i extract system.img in update.app ...and lost Brazil language
Click to expand...
Click to collapse
Well... I'm sorry, but I can't help you on that one. It just doesn't make sense. You can't "lose" a language. As I said, try to use Huawei eRecovery to completely restore your phone.

Solved