Database Users

Lickonn's Recovery Image for Acer A1 Liquid V 0.3.1

Im posting this since its vital for development,just quoting lickonn from the modaco thread:
"This is my recovery image for Acer Liquid !
I build it for my own use, but i'm sure it can also help you !
Rebuild and modified with my own stuff from Cyanogen's sources. Thanks for this great job Cyanogen !
Update : 0.3.1
- fix a small bug on app2sd partition in recovery mode
Update : 0.3
- improved speed of functions
Update : 0.2
- Auto fsck on /dev/block/mmcblk0p1 and /dev/block/mmcblk0p2
- reboot after a wipe
- fix some little bugs
Features of my recovery are :
- update rom with update.zip system (update.zip, or other, in root of sdcard)
- nandroid backup (note : a bug can loop the backup/restoration. Please remove the usb cable before launching the backup/restore, and plug it again after backup/restore)
- nandroid restore (note : a bug can loop the backup/restoration. Please remove the usb cable before launching the backup/restore, and plug it again after backup/restore)
- mount/umount sdcard
- enable/disable root on current system
- split SD for app2sd (be carrefull ! this will erase all you sdcard, include nandroid backup...PLEASE BACKUP YOUR SDCARD BEFORE)
- move app2sd ! (you must use lickonn rom to use it) (you can delete /data/app.back and /data/app-private.back after)
- fix uid
- wipe data (include app2sd data) - auto reboot after wipe
- wipe only dalvik cache (usefull sometimes)
- copy the recovery log to your sdcard
Included :
- Busybox 1.15
- ADB root
- Nandroid Mobile
- SDParted
- Fix permissions script by Cyanogen
- APP2SD script from Cyanogen
- Parted
- Sqlite
A small screenshot from ddms :
Reduced 60%
Attached Image
480 x 800 (8.33K)
How to use it ?
- Put your device in bootloader mode
- Extract the recovery image
- Flash the recovery.img file : fastboot -i 0x0502 flash recovery recovery.img "
- Reboot in recovery mode
Download in original thread
http://android.modaco.com/content/a...om/299060/06-01-0-3-1-lickonn-recovery-image/

[D855] [GUIDE] One Click ROOT+TWRP Recovery for Lollipop Stock Firmware [20H/20P/20G]

One Click ROOT+TWRP Recovery for Lollipop Stock Firmware ​-----------------------------------------------------------------------
I recommend you to use AutoRec For Lollipop 20H from @[B]bender_007[/B]
@ingoljosh includes all version of autorec (D855, D852, D850, LS990 ...) in his post : Flash TWRP With AutoRec
​
First use OneClic Script ( by @avicohh ) to root your G3
Then install and use AutoRec to install the recovery custom
-----------------------------------------------------------------------​Only for D855​Only Lollipop (not KitKat)
(16GB/2GB and 32GB/3GB variants)​Use only this tuto in case of failure with the previous quoted method​Credit
- @6ril1 for all his advice and convinced me to publish this method here
- @somboons and his post for the LG G2 : [TOOLS] One Click ROOT+TWRP Recovery for Lollipop Stock Firmware
Somboons have modified One Root Script ROOT KitKat / Lollipop firmware that for One Click ROOT+TWRP D802 firmware 30a/30d and I have updated his work for the LG G3 D855
- @avicohh for his One click script
- @thecubed for Bumps!
- @Unjustified Dev for send_command and his New Root Method for LG Devices
- @Chainfire for SuperSU
- G3 tuto on Frandroid
---------------------------------------------​Download Link for Lollipop 20H:
Mega LGG3-D855-OneClickRootRecoveryV1.1.zip
Box LGG3-D855-OneClickRootRecoveryV1.1.zip
Dropbox LGG3-D855-OneClickRootRecoveryV1.1.zip
md5 : 33c50a727eecc9402ae1551e818b9615
---------------------------------------------
NEW​
Download Link for Lollipop 20P:
Mega LGG3-D855-OneClickRootRecovery-V20P.zip
Dropbox LGG3-D855-OneClickRootRecovery-V20P.zip
md5 : a5f1776215dc6e9792e57efae400dcae
Download Link for Lollipop 20G:
Mega LGG3-D855-OneClickRootRecovery-V20G.zip
Dropbox LGG3-D855-OneClickRootRecovery-V20G.zip
md5 : 624a30b28037a6ed7023ea1f245c2aa8
@6ril1 thank to him for the bump of the 20P and 20G boot :good:
20P and 20G --> If you are not root having applied this tool, copy UPDATE-SuperSU-v2.46.zip on your SDCARD , restart on recovery mode and flash UPDATE-SuperSU-v2.46.zip
For those who used the LGG3-D855-OneClickRootRecoveryV1.1.zip version (for 20H) on the firmware:
- 20P download this file : Kernel fixed by @6ril1 (v20p) --> http://forum.xda-developers.com/showpost.php?p=60770468&postcount=1019
- 20G download this file : Kernel fixed by @6ril1 (v20G) --> http://forum.xda-developers.com/showpost.php?p=60940277&postcount=220
And use Flashify or your custom recovery to install this boot
For more informations see here : http://forum.xda-developers.com/showpost.php?p=60913483&postcount=23
Thank's @black_horse_88
---------------------------------------------​
changelog:
http://forum.xda-developers.com/showpost.php?p=59926518&postcount=91
older version:
Mega LGG3-D855-OneClickRootRecovery.zip
Box LGG3-D855-OneClickRootRecovery.zip
Dropbox LGG3-D855-OneClickRootRecovery.zip
md5 : 9f0dfaa556e33457163cb7d57ebc6b1d
(recovery includes in LGG3-D855-OneClickRootRecovery.zip file: TWRP 2.8.6.1 w. Splash Screens/Modem/F2FS)
Backup Data on SDCARD Before doing everything​
How to install
1 - Install LG drivers if they are not installed yet.
2 - Make sure you are enable USB Debuging Mode . (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging)
{
"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"
}
3 - Connect your phone to pc on PTP mode
4 - Extract LGG3-D855-OneClickRootRecovery.zip and double click on the OneClick_ROOT_RECOVERY.bat file, to run the script.
5 - Follow the instructions.
If the phone not recognize, try to switch between MTP and PTP options.
Watch the screen of your smarphone you could see this popup asking you to access to the G3
Of course, accept
Your G3 reboot several times.
If you see this message , reboot the G3 manually into Download mode
6 - Enjoy ROOT+TWRP on Lollipop Firmware
7 - Verify if you are root, you have custom recovery and working Download Mode
Problems and solutions
​1 - @somboons describes the manual procedure on his original publication for the LgG2. If you have errors during the script you can try the manual procedure.
somboons said:
Normally If doesn't work for people please checking port that connecting between device and computer or checking LG driver and Re-run script again or use Manual method
What does the automate script do ?
(For people can't use automate script we have to use manually ROOT+TWRP)
Make sure you are enable USB Debuging Mode . See this Method > Enable Debugging Mode
1. Pushing all stuff files
Run file
Command Prompt.bat
Click to expand...
Click to collapse
It will be show command DOS windows
C:\Users\M\Desktop\LGG3-D80230a-OneClickRootRecoveryV1.1>
Click to expand...
Click to collapse
Using command as below to push files to device
adb.exe push busybox /data/local/tmp/ && adb.exe push lg_root.sh /data/local/tmp/ && adb.exe push UPDATE-SuperSU-v2.46.zip /data/local/tmp/
adb.exe push aboot.img /data/local/tmp/aboot.img
adb.exe push laf.img /data/local/tmp/laf.img
adb.exe push boot.img /data/local/tmp/boot.img
adb.exe push recovery.img /data/local/tmp/recovery.img
Click to expand...
Click to collapse
2. Reboot to Download mode
3. When enter to Download mode successfully.We need to send command to connect device with computer
Send_Command.exe \\.\COM_PATH
Click to expand...
Click to collapse
COM_PATH . we can find with ports.bat command
Ex.
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>ports.bat
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>reg query HKLM\hardware\devicemap\SERIALCOMM
HKEY_LOCAL_MACHINE\hardware\devicemap\SERIALCOMM
\Device\LGANDNETMDM0 REG_SZ COM3
\Device\LGANDNETDIAG1 REG_SZ COM4
A command that send to device when connecting to computer with Download Mode is
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>Send_Command.exe \\.\COM4
Click to expand...
Click to collapse
4. When we see this prompt
C:\Users\M\Desktop\LGG3-D855-OneClickRootRecoveryV1.1>Send_Command.exe \\.\COM4
Author : blog.lvu.kr
SPECIAL COMMAND : ENTER, LEAVE
#
Click to expand...
Click to collapse
Try to use this command to ROOT+TWRP
# sh /data/local/tmp/lg_root.sh dummy 1 /data/local/tmp/UPDATE-SuperSU-v2.46.zip /data/local/tmp/busybox
Click to expand...
Click to collapse
5. When we see this message
ui_print - Disabling OTA survival
ui_print - Removing old files
ui_print - Placing files
ui_print - Post-installation script
ui_print - Unmounting /system and /data
ui_print - Done !
Please press Ctrl+C, and then type N and ENTER to reboot.
#
Click to expand...
Click to collapse
Try to use LEAVE command to restart device.
#LEAVE
Click to expand...
Click to collapse
6. Enjoy ROOT+TWRP
Click to expand...
Click to collapse
2- If you always have errors or blockings try this other manual method
1 - Apply this tuto : [GUIDE] New Root Method for LG Devices
2 - Then this one : http://forum.xda-developers.com/showpost.php?p=59931455&postcount=104
3 - If your G3 don't boot on system but you can go on Recovery and Download Mode
Your boot is not correctly flash and we have to make it by line of commands
Tuto here : http://forum.xda-developers.com/showpost.php?p=59962266&postcount=127

Good find, good job m8

Thanks for this solution and for the work done.

Hi, I'm currently rooted on stock lollipop but do not have recovery. Can I run this to give me custom recovery? Cheers

Smowza said:
Hi, I'm currently rooted on stock lollipop but do not have recovery. Can I run this to give me custom recovery? Cheers
Click to expand...
Click to collapse
+1
Sent from my LG-D855 using Tapatalk

Smowza said:
Hi, I'm currently rooted on stock lollipop but do not have recovery. Can I run this to give me custom recovery? Cheers
Click to expand...
Click to collapse
Yes you can
it's the twrp 2.8.6.1 version

Nice work.
Thx for the credit.

Huge Improvement!
HI @jac10000,
This is great! Way better than what I have posted.
I assume that this can be repackaged to cater to other LG G3 variants, by simply replacing aboot.img, laf.img, boot.img (users need to have this "bump'd" prior), and recovery.img (need to be "bump'd" prior as well) from those of their respective LG G3 variants, correct?
EDIT: I have promoted your approach in my how-to thread: http://forum.xda-developers.com/showpost.php?p=59897649&postcount=455

topet2k12001 said:
HI @jac10000,
This is great! Way better than what I have posted.
I assume that this can be repackaged to cater to other LG G3 variants, by simply replacing aboot.img, laf.img, boot.img (users need to have this "bump'd" prior), and recovery.img (need to be "bump'd" prior as well) from those of their respective LG G3 variants, correct?
EDIT: I have promoted your approach in my how-to thread: http://forum.xda-developers.com/showpost.php?p=59897649&postcount=455
Click to expand...
Click to collapse
Yes I think it's possible. I don't know the others models of G3 and their specific characteristics for installing custom recovery

jac10000 said:
Yes I think it's possible. I don't know the others models of G3 and their specific characteristics for installing custom recovery
Click to expand...
Click to collapse
HI @jac10000,
Great to hear.
Based on my experience in the Imageprep thread, installation of custom recovery is the same. I'll go ahead and try it out with my D858HK. Will let you know!

Does it make any difference if I have the LG G3 D855 16GB/2GB variant?
Can anyone report back?

@afilbit It work for 16go/2go and 32go/3go variants

Any other host for the file? Mega is blocked in India :/

@alsiladka Ok I do that , just a moment
https://app.box.com/s/qyquibqpnsh6tiq0kf8a7on2kyelvmf7

jac10000 said:
@alsiladka Ok I do that , just a moment
Click to expand...
Click to collapse
What would I need to provide to make this work on a f460k G3 Cat6? I have not found a bump'd boot.img to start with and don't fully understand how to make one myself.

Works great for my LG G3 D855 16GB. Big thanks! [emoji2]

Has anybody tried it on D855TR Turkish version?

BoredKender said:
What would I need to provide to make this work on a f460k G3 Cat6? I have not found a bump'd boot.img to start with and don't fully understand how to make one myself.
Click to expand...
Click to collapse
I do not know the specific obligations for the f460k. But for the D855 I extracted from kitkat Kdz the aboot.img and laf.img and copy them in the tools folder. I think you must use specific recovery Twrp for the f460k. For the bump boot, I have ever install recovery and bump boot by this method and I use here le boot.img includes in it.

Bump stock lp kernel can be made with linux :
http://forum.xda-developers.com/showthread.php?p=59806620
You need unpackbootimg and mkbootimg bin (you can compile them from source).
For the recovery, open bump in linux or the windows tool made for open bump should do the job

Success
Successfully completed process. TWRP installed and Download mode works. LG Stock OS (V20h-EUR-XX) was rooted before using "No Downgrade" method.
Details of my phone -
LGD855
32GB (European Model),
Software Version: V20h-EUR-XX
Thank you OP! You have just opened a new world for me.

[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.

SM-T380/T385 Root?

Is anyone working on rooting this device? I just bought one and it seems to be a really nice tablet, except I'd prefer something other than touchwiz. Although I'd be perfectly happy with just rooting at least.
If there's no one rooting it, could someone help me find the resources to learn how to possibly root this device myself? I'm a beginner with modding android but I pick up things quickly so I'd like to at least give it a shot.

Yesterday I has rooted it via Magisk Manager APK v.5.5.3 & Magisk 15.2.
Procedure:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!

Mefody said:
Yesterday I has rooted it via Magisk Manager APK v.5.5.3 & Magisk 15.2.
Procedure:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
Click to expand...
Click to collapse
Thank you so much! It worked perfectly!
You should post a thread detailing your instructions. Hell, I'll do it if you're too busy

shahmir_k said:
Thank you so much! It worked perfectly!
You should post a thread detailing your instructions. Hell, I'll do it if you're too busy
Click to expand...
Click to collapse
OK! Make this thread, cause I'm working now on TWRP for this tablet.
Please after thread creating place here link to it... :good:

Thank you for the solution
Mefody said:
Yesterday I has rooted it via Magisk Manager APK v.5.5.3 & Magisk 15.2.
Procedure:
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
Click to expand...
Click to collapse
Thank you so much. I am a newbie to the whole rooting android thing. I came across this post when trying to root my SM-T385 tab and thought it was too complicated. I tried many other simpler methods and nothing worked. Finally, I took my time figure out your solution and lo-behold it actually works.:good:
I am now a proud owner of a rooted android tablet.

Thank you for the detailed write-up. Just got a new SM-T380 (already on 7.1.1) and would like to have root.
I followed the instructions and got to the Odin Flash part and the tablet came up with "Only official released binaries are allowed to be flashed". Had to hard reset to get it to boot again (w/o root).
Anyone know of a workaround or why didn't work on this one?

crewdog said:
Thank you for the detailed write-up. Just got a new SM-T380 (already on 7.1.1) and would like to have root.
I followed the instructions and got to the Odin Flash part and the tablet came up with "Only official released binaries are allowed to be flashed". Had to hard reset to get it to boot again (w/o root).
Anyone know of a workaround or why didn't work on this one?
Click to expand...
Click to collapse
You should activate "Developer mode" & in developers menu unlock OEM bootloader.

Mefody said:
You should activate "Developer mode" & in developers menu unlock OEM bootloader.
Click to expand...
Click to collapse
Thanks. I don't see "OEM unlock" in the developer now, so think I'm in the penalty box for a week. Bummer.

Mefody said:
You should activate "Developer mode" & in developers menu unlock OEM bootloader.
Click to expand...
Click to collapse
What's the firmware build number?

Im having the same issue, help please?
ashyx said:
What's the firmware build number?
Click to expand...
Click to collapse
My SM-T380 build number is: NMF26X.T380DXU1AQI7
Can't find a way to boot T380 to fastboot mode to run "fastboot oem unlock" unless it can somehow be done with ADB.
Thanks!!!

ashyx said:
What's the firmware build number?
Click to expand...
Click to collapse
I'm on T385XXU1AQJ3-20171116091340 now:
PDA/AP Version - T385XXU1AQJ3
CSC Version - T385OXE1AQJ1
MODEM/CP Version - T385XXU1AQHE
Build Date - 2017-10-30
OS - Nougat 7.1.1
Link to original firmware.
Link to patched "boot.img".
I see, You are guru in TWRP assembling . . .
So here is some sources & technical infos:
Link to kernel OpenSource.
Tablet technical name: gta2slte
Partition sizes from command "dd i= ... o= ..."
BOARD_BOOTIMAGE_PARTITION_SIZE := 33554432
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 33554432
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 3674210304
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053993984
BOARD_CACHEIMAGE_PARTITION_SIZE := 314572800
BOARD_PERSISTIMAGE_PARTITION_SIZE := 33554432

joeyw007 said:
Can't find a way to boot T380 to fastboot mode to run "fastboot oem unlock" unless it can somehow be done with ADB.
Thanks!!!
Click to expand...
Click to collapse
There is no "Fastboot Mode" in this model, like in many other from Sansung, HTC ets. Samsung also insert absolutely bad for ROM-creators KNOX system.
So here is S-shot for OEM is unlocked (and tablet is rooted)... But there no chances for "fastboot"
{
"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"
}
Under Linux I use Heimdall. Here is screen, where device are detected & ready to be flashed.
One thing about Heimdall... Version from repos didn't work with our device. So we have to compile it from Benjamin-Dobell github where this bug are fixed yet.
Building source is trivial:
Code:
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
make

OEM Unlock Enabled On New Update
I contacted Samsung and spoke with them about the OEM unlock feature missing from developer options and explained I needed to root my table for development purposes for work. They gave me the usual reply of we don't support rooting. I replied I'm not asking you to. I'm asking you to unlock the boot loader on a device I bought, belongs to me and should be allowed to modify as I see fit. I am aware of security and warranty issues please do something about this. Remember Apples DE boggle. A few days later an OTA update puts the feature in my developer options. Coincidence or did they listen? Who knows. I will be trying the root procedure as soon as the new rom downloads and I can get the boot.img from the AP Block. I'll let you guys know how it comes out.

Root Achieved!!! For Cellular South Build T380XAR1AQK3
1. Unpack stock firmvare ***.tar.md5 that is currently installed on your tablet (they MUST BE the same!!!).
2. Then unpack AP-block from step 1 to obtain "boot.img" file.
3. Download & install on tablet MM APK.
4. Put "boot.img" on SDCARD.
5. Run MM, in setiings set "Patch kernel", then setup the Magisk zip (Wi-Fi must be connected to Internet ).
6. When asked, point MM to place on SDCARD where "boot.img" saved.
7. After some time You will get "OK".
8. Find on SDCARD file "patched_boot.img". Copy in on PC & rename to "boot.img". Then archive it to "<any name>.tar".
9. Set tablet to download mode & flash above tar-file via AP-slot of Odin-programm.
10. Tablet will reboot & ask to wipe all data to factory's params. Do it... Be noticed, that all passwords, setting, google regisery will be wiped.
11. After wiping & reboting install MM APK again... And YEAH!!! You got root!
OK with the new update the boot loader can be unlocked from dev options and the above method for rooting is %100 successful. Just make sure to tell Magisk Manager under settings to output patched boot.img to odin mode "img.tar" then just flash the patched_boot.img.tar via the AP slot with Odin.

joeyw007 said:
Who knows. I will be trying the root procedure as soon as the new rom downloads and I can get the boot.img from the AP Block. I'll let you guys know how it comes out.
Click to expand...
Click to collapse
I know at last 3 person with the same situation... Sometimes, when we try to change region of firmware or try to root it out by progs like Kingo, Kingroot & CF-Autoroot it seems to Samsung, that You are dangerous hacker - and it set the 1-week "penalty" mode. So OEM-unblocking became disabled during this penalty period.

Like I said Who Knows, I am Curious...
I am curious if anyone missing the OEM Unlock feature in dev options running build T380DXU1AQI7 before this morning received an OTA update to build number T380XAR1AQK3 with the ability to unlock your bootloader from dev options. I haven't changed regions successfully flashed anything to this tablet and have had it for a month. OEM unlock appeared after OTA update this morning. Now I'm rooted and all is well. Before restarting your tablet if you root this build I would suggest turning OEM Unlocking on again after rooting, as it wipes your tablet, otherwise you will get an error message about not being able to boot unauthorized binaries and have to repeat the process.

Mefody said:
I'm on T385XXU1AQJ3-20171116091340 now:
PDA/AP Version - T385XXU1AQJ3
CSC Version - T385OXE1AQJ1
MODEM/CP Version - T385XXU1AQHE
Build Date - 2017-10-30
OS - Nougat 7.1.1
Link to original firmware.
Link to patched "boot.img".
I see, You are guru in TWRP assembling . . .
So here is some sources & technical infos:
Link to kernel OpenSource.
Tablet technical name: gta2slte
Partition sizes from command "dd i= ... o= ..."
BOARD_BOOTIMAGE_PARTITION_SIZE := 33554432
BOARD_RECOVERYIMAGE_PARTITION_SIZE := 33554432
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 3674210304
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053993984
BOARD_CACHEIMAGE_PARTITION_SIZE := 314572800
BOARD_PERSISTIMAGE_PARTITION_SIZE := 33554432
Click to expand...
Click to collapse
If you could try this build of TWRP out. It's built using the T380 kernel, but should work for the T385 also.
https://androidfilehost.com/?fid=889964283620778312
.

ashyx said:
If you could try this build of TWRP out. It's built using the T380 kernel, but should work for the T385 also.
Click to expand...
Click to collapse
Thanks a lot!!! It works commonly fine!
Two moments:
1. CPU Temperature too high, as for me May be path to termal probe not correct.
2. /data partition are unmount. I think it's due to uncorrect "footer".
I started on github TWRP repo, but I have no enough experience - my build on minimal twrp-7. 1. manifest builds OK, but after flashing I have boot-loop.
Maybe You will kindly find some time to look at this repo: https://github.com/mefody1971/android_device_samsung_gta2slte
Some info regardly temperature & /data partition
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053977600 # 8053993984 - 16384 (footer)
TARGET_USE_CUSTOM_LUN_FILE_PATH := "sys/class/android_usb/android0/f_mass_storage/lun/file"
TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
TW_CUSTOM_CPU_TEMP_PATH := /sys/devices/virtual/thermal/thermal_zone1/temp
In attachment I put recovery.log

Mefody said:
Thanks a lot!!! It works commonly fine!
Two moments:
1. CPU Temperature too high, as for me May be path to termal probe not correct.
2. /data partition are unmount. I think it's due to uncorrect "footer".
I started on github TWRP repo, but I have no enough experience - my build on minimal twrp-7. 1. manifest builds OK, but after flashing I have boot-loop.
Maybe You will kindly find some time to look at this repo: https://github.com/mefody1971/android_device_samsung_gta2slte
Some info regardly temperature & /data partition
BOARD_USERDATAIMAGE_PARTITION_SIZE := 8053977600 # 8053993984 - 16384 (footer)
TARGET_USE_CUSTOM_LUN_FILE_PATH := "sys/class/android_usb/android0/f_mass_storage/lun/file"
TW_BRIGHTNESS_PATH := /sys/class/leds/lcd-backlight/brightness
TW_CUSTOM_CPU_TEMP_PATH := /sys/devices/virtual/thermal/thermal_zone1/temp
In attachment I put recovery.log
Click to expand...
Click to collapse
The errors you are seeing are due to an encrypted data partition. TWRP doesn't support Samsungs encryption method yet.
To mount DATA you need to FORMAT the DATA partition and flash my encryption patch to disable encryption which you can find in my sig.
When I post a proper thread all instructions will be there. For now you can consult any one of my TWRP threads for more info.

ashyx said:
The errors you are seeing are due to an encrypted data partition. TWRP doesn't support Samsungs encryption method yet.
To mount DATA you need to FORMAT the DATA partition and flash my encryption patch to disable encryption which you can find in my sig.
When I post a proper thread all instructions will be there. For now you can consult any one of my TWRP threads for more info.
Click to expand...
Click to collapse
OK! Thanks a lot!!! Will find all available info and try to play with formatting /data partition & setting on Your patch.
Awaiting Your special thread for this device. Anyway - You did a great job :good:

[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