As I mentioned in the "request thread...
This should work for all carriers however I've only testing on Sprint.
The problem on Android N is with dm-verity. Follow the guide to get root as well as dm-verity disabled so you can make changes to build.prop through custom recovery.
Here's how:
1) Enable USB debugging
2) In a terminal on your PC
- adb shell
- settings put global tether_dun_required 0
3) Download this boot.IMG from phh, for build NPC56P here: https://superuser.phh.me/nexus/shamu...erity-r189.img
4) Flash it using fastboot:
- sudo fastboot flash boot *path-to-downloaded.IMG*
5) Then with the volume buttons select TWRP recovery.
Then: under "Mount" check 'system' to mount system partition
- sudo adb shell
- echo net.tethering.noprovisioning=true>>/system/build.prop
6) Reboot device and enjoy tethering.
Extra) If you want root, just download Phh's SuperUser from the play store.
Download your Files what you need to flash!
Download Patched Ramdisk and Nocheckimg (Pass: mrrib)
Unlock Your Bootloader
Boot into fastboot mode and flash nocheckrecovery and Patched Ramdisk
type
fastboot flash ramdisk mate20lite_patched_boot.img
fastboot flash recovery_ramdisk SNE_recovery_NoCheck.img
Boot into Android System enable adb debbuging in developer settings.
Rename and copy firmware files via MTP to your internal memory
update_data_full_public.zip -> update_data_public.zip
update.zip -> update.zip
update_full_SNE-LXX_hw_eu.zip -> update_all_hw.zip
Install Magisk Manager MagiskManager.apk
Copy OEM info binary file to internal memory oeminfo.bin
Start ADB
type one by one
adb shell
su
accept the prompt at your Mate 20 Lite
mkdir /data/local/tmp
mv /sdcard/oeminfo /data/local/tmp
cd /data/local/tmp
chmod +x oeminfo
Example for SNE-L21C432
./oeminfo SNE-L21 C432 hw/eu
mkdir /data/update/HWOTA
cd /sdcard/
mv *.zip /data/update/HWOTA
Paste recovery command(all lines at once) and wait for prompt to be shown before next step:
echo "--update_package=/data/update/HWOTA/update.zip" > /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_data_public.zip" >> /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_all_hw.zip" >> /cache/recovery/command
exit
exit
adb reboot recovery
Looks like this:
D:\Huawei\adb>adb shell
HWSNE:/ $ su
HWSNE:/ # mv /sdcard/oeminfo /data/local/tmp
HWSNE:/ # cd /data/local/tmp
HWSNE:/data/local/tmp # chmod +x oeminfo
HWSNE:/data/local/tmp # ./oeminfo SNE-L21 C432 hw/eu
HWSNE:/data/local/tmp # mkdir /data/update/HWOTA
HWSNE:/data/local/tmp # cd /sdcard/
HWSNE:/sdcard # mv *.zip /data/update/HWOTA
HWSNE:/sdcard # echo "--update_package=/data/update/HWOTA/update.zip" > /cache/recovery/command
HWSNE:/sdcard # echo "--update_package=/data/update/HWOTA/update_data_public.zip" >> /cache/recovery/command
HWSNE:/sdcard # echo "--update_package=/data/update/HWOTA/update_all_hw.zip" >> /cache/recovery/command
HWSNE:/sdcard # exit
HWSNE:/ $ exit
D:\Huawei\adb>adb reboot recovery
Phone will reboot and starts to install and Rebrand your Phone
ROOT ONLY
1.Unlock Your Bootloader
2.Root your Mate 20 Lite with Patched Ramdisk
3.Install Magisk Manager MagiskManager.apk
4. Update MagiskManager
So bad huawei costumers service refuse to provide me unlock code bootloader, it's time to leave
Envoyé de mon SNE-LX2 en utilisant Tapatalk
Hi, i enabled the developer option but it's not showing in the system settings. Is this a common problem? I've never experienced it on any phone before
mrrib said:
Download your Files what you need to flash!
Download Patched Ramdisk and Nocheckimg (Pass: mrrib)
Unlock Your Bootloader
Boot into fastboot mode and flash nocheckrecovery and Patched Ramdisk
type
fastboot flash ramdisk mate20lite_patched_boot.img
fastboot flash recovery_ramdisk SNE_recovery_NoCheck.img
Boot into Android System enable adb debbuging in developer settings.
Rename and copy firmware files via MTP to your internal memory
update_data_full_public.zip -> update_data_public.zip
update.zip -> update.zip
update_full_SNE-LXX_hw_eu.zip -> update_all_hw.zip
Install Magisk Manager MagiskManager.apk
Copy OEM info binary file to internal memory oeminfo.bin
Start ADB
type one by one
adb shell
su
accept the prompt at your Mate 20 Lite
mkdir /data/local/tmp
mv /sdcard/oeminfo /data/local/tmp
cd /data/local/tmp
chmod +x oeminfo
Example for SNE-L21C432
./oeminfo SNE-L21 C432 hw/eu
mkdir /data/update/HWOTA
cd /sdcard/
mv *.zip /data/update/HWOTA
Paste recovery command(all lines at once) and wait for prompt to be shown before next step:
echo "--update_package=/data/update/HWOTA/update.zip" > /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_data_public.zip" >> /cache/recovery/command
echo "--update_package=/data/update/HWOTA/update_all_hw.zip" >> /cache/recovery/command
exit
exit
adb reboot recovery
Looks like this:
D:\Huawei\adb>adb shell
HWSNE:/ $ su
HWSNE:/ # mv /sdcard/oeminfo /data/local/tmp
HWSNE:/ # cd /data/local/tmp
HWSNE:/data/local/tmp # chmod +x oeminfo
HWSNE:/data/local/tmp # ./oeminfo SNE-L21 C432 hw/eu
HWSNE:/data/local/tmp # mkdir /data/update/HWOTA
HWSNE:/data/local/tmp # cd /sdcard/
HWSNE:/sdcard # mv *.zip /data/update/HWOTA
HWSNE:/sdcard # echo "--update_package=/data/update/HWOTA/update.zip" > /cache/recovery/command
HWSNE:/sdcard # echo "--update_package=/data/update/HWOTA/update_data_public.zip" >> /cache/recovery/command
HWSNE:/sdcard # echo "--update_package=/data/update/HWOTA/update_all_hw.zip" >> /cache/recovery/command
HWSNE:/sdcard # exit
HWSNE:/ $ exit
D:\Huawei\adb>adb reboot recovery
Phone will reboot and starts to install and Rebrand your Phone
ROOT ONLY
1.Unlock Your Bootloader
2.Root your Mate 20 Lite with Patched Ramdisk
3.Install Magisk Manager MagiskManager.apk
4. Update MagiskManager
Click to expand...
Click to collapse
link for firmware please, all which I tried doesn't work with this oem (c432)
jvs60 said:
Hi, i enabled the developer option but it's not showing in the system settings. Is this a common problem? I've never experienced it on any phone before
Click to expand...
Click to collapse
Never heard anything like that
Hardreset and test again?
octopus82 said:
link for firmware please, all which I tried doesn't work with this oem (c432)
Click to expand...
Click to collapse
Here is a Firmware work for Singel Sim C432 -->LINK<--
./oeminfo SNE-L21 C432 hw/eu
mrrib said:
Never heard anything like that
Hardreset and test again?
Click to expand...
Click to collapse
I guess i'll try that. This is strange. Thanks
jvs60 said:
Hi, i enabled the developer option but it's not showing in the system settings. Is this a common problem? I've never experienced it on any phone before
Click to expand...
Click to collapse
I have the same problem too. i dont know any fix
neilsp said:
I have the same problem too. i dont know any fix
Click to expand...
Click to collapse
I had to factory reset to and try again for it to work. It's all good now
how can we unlock the bootloader?
mrrib said:
Here is a Firmware work for Singel Sim C432 -->LINK<--
./oeminfo SNE-L21 C432 hw/eu
Click to expand...
Click to collapse
Any firmware for dual sim?
Sent from my LYA-L29 using Tapatalk
still refuse all c432 firmware
what's wrong ?
Did i have to get unlock code to this way work or what?
Did i have to get unlock code to this way work or what ?? no response ??
essokam said:
Did i have to get unlock code to this way work or what ?? no response ??
Click to expand...
Click to collapse
off course, it does say in the instructions that you have to unlock the bootloader.
to bad that you can't get unlock codes, it was open a few days ago but now it's closed again.
Could someone tell me how to change the cust of my mobile to receive updates? Thank you.
{
"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"
}
Enviado desde mi SNE-LX1 mediante Tapatalk
Anyone knows how to debrand without bootloader unlock ? My friend has mate 20 lite Dual Sim with t mobile Poland brand.
The4anoni said:
Anyone knows how to debrand without bootloader unlock ? My friend has mate 20 lite Dual Sim with t mobile Poland brand.
Click to expand...
Click to collapse
If you do a search on ebay maybe you find but whit money, 5 euro i think.
Do we need an Unlocked bootloader for that or will the patched ramdisk unlock it ?
will this unlock network lock ?
Another method for unbricking EMUI 9 devices. For advanced users (not mentioning links to TWRP, to FullOTA factory images... there are other threads dedicated to that). Tested on Mate 20 Pro.
This method should help when:
1. Device has bootloader unlocked (unusable for locked bootloaders)
2. System fails to boot. HiSuite (HSTool) restore method does not work (fails in stage "Install recovery") nor does DLOAD method work (after VolUp+VolDn+Pwr action system continues booting or ends in 5% Installation and bootloops).
3. Fastboot mode is working
The reason might be wiped/corrupted eRecovery paritition.
Huge credits and thanks to @OldDroid for having educated me about eRecovery and about flashing it.
Steps:
1. Download FullOTA factory image
2. Extract UPDATE. APP file
3. Extract ERECOVERY_KERNE.img, ERECOVERY_RAMDI.img, ERECOVERY_VENDO.img, ERECOVERY_VBMET.img (guide:
OpenKirin - guide to extract partition images)
4. Boot into fastboot
5. Install and boot TWRP (
Code:
fastboot flash recovery_ramdisk twrp.img
)
6. Copy (e.g. via MTP, while connected to the computer) the 4 previously extracted images to internal storage or SD
7. Enter TWRP shell and execute:
Code:
ls -l /dev/block/bootdevice/by-name/
8. Check partition names, in case of Mate 20 Pro they are:
Code:
erecovery_kernel /dev/block/sdd37
erecovery_ramdisk /dev/block/sdd38
erecovery_vbmeta /dev/block/sdd53
erecovery_vendor /dev/block/sdd39
9. Copy the extracted files into corresponding partitions:
Code:
dd if=./ERECOVERY_KERNE.img of=/dev/blck/sdd37
dd if=./ERECOVERY_RAMDI.img of=/dev/blck/sdd38
dd if=./ERECOVERY_VENDO.img of=/dev/blck/sdd39
dd if=./ERECOVERY_VBMET.img of=/dev/blck/sdd53
10. Reboot to fastboot and flash stock recovery via
Code:
fastboot flash recovery_ramdisk stock_recovery.img
Now you should be good to go for DLOAD (recommended for soft-brick recovery) and HSTool methods.
Would this be for Error mode?
func no : 11 (recovery image)
error no : 2 (load failed!)
This error is what happens when I try Dload.
ReyneBow said:
Would this be for Error mode?
func no : 11 (recovery image)
error no : 2 (load failed!)
This error is what happens when I try Dload.
Click to expand...
Click to collapse
Depends on what is actually broken. If the error is caused by a broken eRecovery image, than this could help. I can't tell, the error codes displayed tell me nothing. One can also update eRecovery if it is extracted from a more recent firmware - e.g. EMUI 9.1.
I have a factory reset ALE-L21 (2015) with android 6. Firmware is ALE-L21C109B582, EMUI 4.0.3. I've gone through most guides on this site, and I can't find one that works.
https://forum.xda-developers.com/t/...nd-install-any-custom-rom-ale-l23-21.3977067/ suggests I should downgrade to android 5, but I can't copy anything to /dload as the filesystem is read-only (so adb tells me when I try to push).
I don't have su installed, so I can't run the command su -c "grep -m1 -aoE 'WVLOCK.{14}[0-9]{16}' /dev/block/mmcblk0p7 |grep -aoE '[0-9]{16}'" (which is also suggested in many places) to extract the unlock code (running without su gets a permission denied error, as expected).
I also don't have an external SD card (though I see there is a writable /sdcard directory in the filesystem).
Are there any options in my situation?
Try this:
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
homer5439 said:
I have a factory reset ALE-L21 (2015) with android 6. Firmware is ALE-L21C109B582, EMUI 4.0.3. I've gone through most guides on this site, and I can't find one that works.
https://forum.xda-developers.com/t/...nd-install-any-custom-rom-ale-l23-21.3977067/ suggests I should downgrade to android 5, but I can't copy anything to /dload as the filesystem is read-only (so adb tells me when I try to push).
I don't have su installed, so I can't run the command su -c "grep -m1 -aoE 'WVLOCK.{14}[0-9]{16}' /dev/block/mmcblk0p7 |grep -aoE '[0-9]{16}'" (which is also suggested in many places) to extract the unlock code (running without su gets a permission denied error, as expected).
I also don't have an external SD card (though I see there is a writable /sdcard directory in the filesystem).
Are there any options in my situation?
Click to expand...
Click to collapse
was there already a folder named dload at the root of the Internal Memory? I unlocked my phone when I was on Android 5 using KingRoot and that command. It should probably work too... If there's no "dload" folder then you need to create it and place the UPDATE.APP file on the folder...
After installing an operating system update on a phone with the Android operating system and A/B slots, Magisk can be installed in the boot partition of the inactive slot with the new operating system version using the "Install to inactive slot" installation option in the Magisk App.
Unfortunately this option is not available for TWRP.
Therefor I wrote a litlle script to install TWRP into the boot partition of the inactive slot with the new operating system version after an OS upgrade.
The method works on my ASUS Zenfone 8 and should in principle also work on other phones with the same architecture (Qualcomm CPU, A/B slots, and boot partitions with ram disks)
Looking at the source code for TWRP (https://github.com/TeamWin/android_bootable_recovery/blob/android-12.1/twrpRepacker.cpp) it can be seen that the installation of TWRP is in principle only the installation of a new ramdisk:
Spoiler: TWRP source code excerpt
C++:
bool twrpRepacker::Flash_Current_Twrp() {
if (!TWFunc::Path_Exists("/ramdisk-files.txt")) {
LOGERR("can not find ramdisk-files.txt");
return false;
}
PartitionManager.Unlock_Block_Partitions();
Repack_Options_struct Repack_Options;
Repack_Options.Disable_Verity = false;
Repack_Options.Disable_Force_Encrypt = false;
Repack_Options.Type = REPLACE_RAMDISK_UNPACKED;
Repack_Options.Backup_First = DataManager::GetIntValue("tw_repack_backup_first") != 0;
std::string verifyfiles = "cd / && sha256sum --status -c ramdisk-files.sha256sum";
if (TWFunc::Exec_Cmd(verifyfiles) != 0) {
gui_msg(Msg(msg::kError, "modified_ramdisk_error=ramdisk files have been modified, unable to create ramdisk to flash, fastboot boot twrp and try this option again or use the Install Recovery Ramdisk option."));
return false;
}
std::string command = "cd / && /system/bin/cpio -H newc -o < ramdisk-files.txt > /tmp/currentramdisk.cpio && /system/bin/gzip -f /tmp/currentramdisk.cpio";
if (TWFunc::Exec_Cmd(command) != 0) {
gui_msg(Msg(msg::kError, "create_ramdisk_error=failed to create ramdisk to flash."));
return false;
}
if (!Repack_Image_And_Flash("/tmp/currentramdisk.cpio.gz", Repack_Options))
return false;
else
return true;
}
Therefor to install TWRP via script after an OS version update two steps are neccessary:
Step one
First we must create the ramdisk with TWRP; this step must only be done once for each TWRP version.
Boot the phone from the TWRP image (NOT from a TWRP installed in the recovery!), e.g:
Bash:
adb rebboot bootloader
sudo fastboot boot /data/backup/ASUS_ZENFONE8/twrp/twrp-3.7.0_12-0-I006D-enhanced.img
Then open an adb session to the running TWRP on the phone and execute:
Bash:
# create the RAM disk
#
cd / && sha256sum --status -c ramdisk-files.sha256sum
if [ $? -eq 0 ] ; then
cd / && /system/bin/cpio -H newc -o < ramdisk-files.txt > /tmp/ramdisk_with_twrp.cpio && /system/bin/gzip -f /tmp/ramdisk_with_twrp.cpio
fi
# copy the RAM disk and magiskboot to a directory on the internal storage that supports the execution permission bit (not /sdcard/<something>)
#
mkdir -p /data/develop/twrp
cp /tmp/ramdisk_with_twrp.cpio.gz /data/develop/twrp/ramdisk_with_twrp.cpio
cp /bin/magiskboot /data/develop/twrp/
Notes:
It is recommended to store the files ramdisk_with_twrp.cpio and magiskboot also on the PC.
The executable magiskboot is only required if Magisk is not installed on the phone.
Now copy the script install_twrp_ramdisk.sh.sh to the phone; this script can be copied to any filesystem with write access on the phone.
That's it .
Step two
The next time an OS update should be done using these steps:
1. install the new OS version either manually or via OTA but do NOT reboot afterwards.
2. execute the script install_twrp_ramdisk.sh.sh to install TWRP into the boot partition for the inactive slot either in an shell on the phone or in an adb shell, e.g. (sh is only necessary if the script is on a filesystem that does not support the execution permission)
Bash:
sh /sdcard/Download/install_twrp_ramdisk.sh
Note that the script needs root access to read and write the boot partition
3. optional: Install Magisk into the new boot partition using the install option "Install to inactive slot" in the Magisk App
4. reboot the phone to activate the new OS version
Test Environment
ASUS Zenfone 8
OmniROM 13
Magisk v25.2
TWRP 3.7.0
Notes
Set the environment variable WORK_DIR before executing the script to use another directory with the image
Set the environment variable TWRP_RAMDISK_NAME before executing the script to use another filename for the ram disk image.
see How to add additional files to an TWRP image for how to add additional files to the TWRP image
see How to install TWRP via script for how to install TWRP with a script running on the PC
Usage for the script install_twrp_ramdisk.sh:
Spoiler: ./install_twrp_ramdisk.sh -H
Code:
./install_twrp_ramdisk.sh -H
Usage:
install_twrp_ramdisk.sh [-h|-H]
This script must run in a shell on the phone (or in an adb shell) after an OS update was installed (either manual or via OTA) but before rebooting the phone.
The script will then install TWRP into the inactive slot.
The script must be executed by the user "root"; if it's executed by a non-root user it will restart itself using "su - -c scriptname"
Supported environment variables
WORK_DIR
directory with the ram disk image and probably the executable magiskboot
TWRP_RAMDISK_NAME
name of the file with the ram disk image (without path)
Prerequisites
The script requires these files:
/data/develop/twrp/ramdisk_with_twrp.cpio
- the ram disk with TWRP
/data/develop/twrp/magiskboot or /data/adb/magisk/magiskboot
- the magiskboot executable
To create the ram disk with TWRP do:
Boot the phone from the TWRP image (NOT from a TWRP installed in the recovery!),
open an adb session to the running TWRP on the phone and execute:
cd / && sha256sum --status -c ramdisk-files.sha256sum
if [ $? -eq 0 ] ; then
cd / && /system/bin/cpio -H newc -o < ramdisk-files.txt > /tmp/ramdisk_with_twrp.cpio && /system/bin/gzip -f /tmp/ramdisk_with_twrp.cpio
fi
mkdir -p /data/develop/twrp
cp /tmp/ramdisk_with_twrp.cpio.gz /data/develop/twrp/ramdisk_with_twrp.cpio
cp /bin/magiskboot /data/develop/twrp/
Note:
It is recommended to store the files ramdisk_with_twrp.cpio and magiskboot also on the PC.
The file magiskboot is only required if Magisk is not installed on the phone.
The directory used for the files can be any directory on the phone on a filesystem supporting the execute permission bit.
But do not forget to change the directory used in the script below (variable WORK_DIR) also.
Update 04.06.2023:
see https://github.com/Magisk-Modules-Repo/twrp-keep for a Magisk module with a script to reinstall TWRP into the inactive boot partition after an OS Udate
Update 11.06.2023:
I successfully tested the Magisk Module twrp-keep on an ASUS Zenfone 8 with OmniROM 13, TRWP 3.7.0_12, and Magisk v26.2.
ToDo:
Create an App with GUI to execute the script