Database Info

[RECOVERY][MOD] MultiROM v33 + TWRP v3.1.1 for Xiaomi Mi MIX (lithium)

{
"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"
}
MultiROM is one-of-a-kind multi-boot mod. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from USB drive connected to the device via OTG cable. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the left image below and in gallery. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from USB drive attached via OTG cable
You can also watch a video which shows it in action.​
Warning!
It _is_ dangerous. This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong and you will have to flash factory images again. Make backups. Always.​
Installation
Firstly, there are videos on youtube. If you want, just search for "MultiROM installation" on youtube and watch those, big thanks to all who made them. There is also an awesome article on Linux Journal.
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
To decrypt your device:
Backup ALL your data if you need to recover later (TWRP backup to USB or copy to your PC)
In fastboot mode:
Code:
fastboot format userdata
In TWRP: Flash Magisk (recommended) or SuperSU to avoid auto-encryption in next boot.
MultiROM has 2 parts you need to install:
Modified recovery (TWRP). Flash it as usual TWRP (fastboot flash recovery, or any flasher app if you're rooted).
MultiROM. Install it as usual zip from modded TWRP once flashed.
Go into TWRP MultiRom settings and be sure that "Enable No-KEXEC Workaround" is enabled (enabled by default)
Your current rom will not be erased by the installation.​Adding ROMs
1. Android
Go to recovery, select MultiROM -> Add ROM. Select the ROM's zip file and confirm. As for the space, clean installation of stock 6.x after first boot takes 900+mb of space.​
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
MIUI ROM as Secondary <--- Latest versions fix this, so you shouldn't need it anymore
Install MIUI as secondary via MultiROM settings in TWRP
Boot into your (rooted) primary
Edit fstab.qcom file in /storage/emulated/multirom/roms//boot/ and add /cache partition entries:
Code:
/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait,check,formattable
/dev/block/bootdevice/by-name/cache /cache ext4 nosuid,nodev,noatime,barrier=1 wait,check,formattable
Alternatively you can use attached file "fstab.qcom.txt" (rename to: fstab.qcom without .txt ). Be sure to set proper permissions (copy from original fstab.qcom, after renaming to fstab.qcom.bak, don't delete it...)
DON'T FORGET to flash Magisk / SuperSU after flashing to avoid re-encryption if you're flashing stock (not modded).
Known issues
You must wait a few seconds (3-5) before you get touch screen responsiveness in TWRP and MultiROM. (fixed by 2017.08.01 build) -- USUAL WHEN SWITCHING FROM MIUI
Some FCs on some secondary ROMs: Try using multiromfix.zip, thx to @Startrek852 (to disable sdcardfs support in that secondary) -- USE MAGISK 13.5+
Issues with TWRP to boot on 4GB/128GB model... (Working on troubleshooting...) -- PRELIMINARY FIX HERE
Reporting issues
As you surely understand, a simply "it does NOT work" is not enough... so please, report your issue describing scenario as much as you can, try following this (as much as possible information is welcome, it's very tiring for me asking what this, what that, etc...):
Issue description (what, how, when, etc...)
Device model : 4GB or 6GB RAM
Decrypted? /cache and /data FSs ? (We assume IS decrypted becaues you're using MultiROM, and EXT4 FS for /cache and /data if you don't know or manually formatted to F2FS)
TWRP version + MultiROM version
Primary ROM (name, better with version)
Firmware version
Secondary ROM (the one with the issue, name and better version)
Custom kernel ? (name and version if so) <--- In theory, we shouldn't support scenarios with custom kernels.... (they can touch system stuff that make things more complex)
Xposed ? <--- Sorry we DON'T support MultiROM if you use Xposed
Google Apps (name, better with version)
Magisk / SuperSU (version and if you use it in Primary and/or Secondary and version)
Logs <--- This would be amazing great and helpful !!!! (you can get them via adb shell, terminal or using any tool)
*Original post and example in this post, please: ​
Download
You can download all stuff from here, where you can find latest TWRP and MultiROM. If you need to uninstall MultiROM, you can use this uninstaller.
MultiROM Manager (apk) available here.​
Source code
MultiROM - https://github.com/MultiROM-dev/multirom
Modified TWRP - https://github.com/multirom-dev/Team-Win-Recovery-Project
MultiROM device tree - https://github.com/BitOBSessiOn/android_device_xiaomi_lithium​
Special thanks to:
@Tasssadar for creating this awesome utility
@nkk71 for the No-KEXEC workaround
@AdrianDC and all MultiROM guys involved in its development
@jcadduono for TWRP port

We will have to try soon... It's the perfect set up for flashaholics

Great news [emoji847][emoji847]
Envoyé de mon MIX en utilisant Tapatalk

I can't make it work

fil0s0f0 said:
I can't make it work
Click to expand...
Click to collapse
The MultiROM app from market is only for official devices (I haven't updated the Android app, imo it's not very useful), So you must follow OP steps.
If you have some issue, please, describe your problem and we will try to help.
Keep in mind that you must have unlocked bootloader, decrypted device, etc...

Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback

fil0s0f0 said:
Device decrypted, bootloader unlocked, and well, there is no instructionbon op but, I figure out and I'll leave my feedback
Click to expand...
Click to collapse
Yes, there are, please, revise OP, and describe which steps have you followed to find out what's your issue. Thx

provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output

Superb, I missed it in this great smarphone

acasmc said:
provided TWRP wont boot into it after flash. shows some scrambled image, shows animation with MultiRom image but wont enter recovery
also command: fastboot flash userdata
gives this output
Click to expand...
Click to collapse
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.

BitOBSessiOn said:
Sorry:
fastboot format userdata
I correct OP.
The TWRP is tested... I will revise.
Click to expand...
Click to collapse
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.

acasmc said:
could it be, that while I'm encrypted TWRP will not work? flashed it with Rashr and fia Fastboot method. didnt work either way.
Click to expand...
Click to collapse
Too weird... I've just downloaded and flashed again with rashr and ok.
Which model do you own (128/256)? Primary rom...?
TWRP must work ok with encrypted /data (but you need decrypted for MultiROM).

I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.

acasmc said:
I'm on latest Miui China Beta Developer ROM (7.7.20), model is 128Gb/4Gb
Mr.Raines TWRP is working fine for me.
Click to expand...
Click to collapse
Can you try some of older versions in testing or backup folder in n AFH, please...?
Can you take a photo of error if it still occurs...?

there is only one TWRP in your folder. can you point me to another. I'll try no worries

acasmc said:
there is only one TWRP in your folder. can you point me to another. I'll try no worries
Click to expand...
Click to collapse
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564

Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]

Konsstantine34 said:
Great mod, I was been using Dual boot patcher app to boot into multiple roms(currently 5 roms). Hopefully this mod makes the things easier than before lol. I may give it a go when i feel a fully clean start. Thanks for providing the mod[emoji106]
Click to expand...
Click to collapse
Usually I don't start to develop for a device before I can use MultiROM....

BitOBSessiOn said:
You can see /bak and /testing folders here:
https://www.androidfilehost.com/?w=files&flid=201564
Click to expand...
Click to collapse
tried other two that are on that link. still the same. sadly don't have another phone with me, to take a picture.
guess gonna have to wait for an update. :/

BitOBSessiOn said:
Note 1: Your device must NOT be encrypted (hint: if you don't know what it is, then it is encrypted).
Click to expand...
Click to collapse
About encrypting, Is it enough to flash the "no-verity-opt-encrypt-5.1".zip?, And if its not, Is there a guide of how to encrypt my device?

Panasonic Eluga Note (MTK 6753) TWRP and root!

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I successfully ported TWRP to Panasonic Eluga Note (MTK6753) after a four day effort. Not a dev here. First time doing this.
<TLDR? skip this>
When I started using android in my HTC HD2, every ROM was pre rooted. I took it for granted.
So I get this cheapo MTK and breaking into it is like banging head against a wall!! I was frustrated with the battery drain: Device never sleeps since the last OTA!
So I learnt SP flash tools and downgraded. ( wiped nvram and created another mess in the process- which is a different story. I solved it)
I could spend this effort and time to stop that pesky "Panasonic" bootaudio too. And that's the first thing I deleted after I booted TWRP, even before rooting.
</TLDR? skipped this>
First things first, enable ADB, enable OEM unlock in developer options, and go to bootloader to unlock it <fastboot oem unlock> THIS WILL WIPE DATA!!
Second thing: Backup nvram.img by sp flash readback and learn how to flash it back (search XDA)- Sometimes you can learn from other's mistakes too! I spent a day and half writing back IMEI and WIFI Mac.
Process (if you don't trust me and want to reproduce the steps yourself)
1. Download stock firmware. (google knows)
2. Patch boot.img so that it doesn't overwrite TWRP with stock recovery on each boot (extract by Carliv Image kitchen and hash out the three lines 663, 664 and 665 mentioning "service flash_recovery /system/bin/install-recovery.sh" in init.rc). I created two copies in the same folder (boot.img, and boot-verified.img) and copied scatter into the same folder for flashing. That's what I saw in the firmware folder.
3. Port TWRP using Carliv Image Kitchen method. I downloaded TWRP from here https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861 but didn't use their method. It didn't work. The TWRP for this chip was stated as android N, but worked well.
4. Flash ported TWRP after copying scatter file to the Carliv Imagekitchen output folder and selecting that scatter in SP droid tools. I again created recovery.img and recovery-verified.img. Don't know if its needed that way. You could wait and flash boot and recovery together from the same folder.
5. That's it, you can enter custom recovery now. Get that pesky "panasonic" bootaudio off the system/media folder now! You can stay content after this or proceed to root.
<nandroid backup now, including Nvram and NVdata. Just in case>
6. Download Supersu zip flashable and flash it via TWRP. https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip?retrieve_file=1 worked for me.
7. Reboot, check root!
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
You're done!
I'll upload my boot.img and ported TWRP if anyone shows any interest in this.
Cheers!
(Bonus: this phone has built in IPtables support in the kernel! I used to flash custom kernel for this ability in other Stock ROMs. AFfirewall works "out of the box"- after rooting, of course!)
Edit: uploaded my modded boot.img and ported TWRP. find it here https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
If you want to go the easy route, unzip the folder and flash it with sp flash. You'll be able to boot into recovery and do the other steps for rooting.
Rememer ONLY DOWNLOAD, don't format, or format and download, or anything!

Brilliant Work man. I also was sort of in your situation as well . i have a panasonic Eluga A3 (Qmobile Noir E2) in my country. Stock Qmobile rom was horrendous. so i flashed the panasonic rom but hated the boot audio and the bloatware that came with it. so i decided to make a slimmed down version of it and successfully did it by using superr's kitchen. and also using the kitchen i removed the encryption on the boot.img and then patched it using magisk for easy rooting without recovery. when flashed together with the modded system.img and modded boot.img and twrp, i was totally in control of my device.
If you need any help with anything mtk send me a pm
also are you able to access internal storage in twrp or not ??

andromodgod said:
If you need any help with anything mtk send me a pm
also are you able to access internal storage in twrp or not ??
Click to expand...
Click to collapse
I can access internal storage in twrp. There's a choice to select the internal storage. Havent backed up to it or anything. But its there. I copied a file into it through TWRP now, and it works. I think its all about the fstab. If you don't get access to internal storage, see for any red errors in TWRP output. I can look into my fstab to see what's relevant.
I have a little hiccup though. Now my network drops (both sim at a time), even during a call. But maybe its because I swapped sim 1 and sim 2. I'll let things settle and see if it will persist. In the meanwhile, I swapped sims back to original.

bad.bid said:
I can access internal storage in twrp. There's a choice to select the internal storage. Havent backed up to it or anything. But its there. I copied a file into it through TWRP now, and it works. I think its all about the fstab. If you don't get access to internal storage, see for any red errors in TWRP output. I can look into my fstab to see what's relevant.
I have a little hiccup though. Now my network drops (both sim at a time), even during a call. But maybe its because I swapped sim 1 and sim 2. I'll let things settle and see if it will persist. In the meanwhile, I swapped sims back to original.
Click to expand...
Click to collapse
i wasn't able to access internal storage at first because device was encrypted beforehand. also sim issues might be caused by imei/nvram . check if your device imei matches your imei on the device box.

andromodgod said:
i wasn't able to access internal storage at first because device was encrypted beforehand. also sim issues might be caused by imei/nvram . check if your device imei matches your imei on the device box.
Click to expand...
Click to collapse
Ya, I fixed Imei issues. this one is like a signal drop once every 15 minutes.

bad.bid said:
I successfully ported TWRP to Panasonic Eluga Note (MTK6753) after a four day effort. Not a dev here. First time doing this.
<TLDR? skip this>
When I started using android in my HTC HD2, every ROM was pre rooted. I took it for granted.
So I get this cheapo MTK and breaking into it is like banging head against a wall!! I was frustrated with the battery drain: Device never sleeps since the last OTA!
So I learnt SP flash tools and downgraded. ( wiped nvram and created another mess in the process- which is a different story. I solved it)
I could spend this effort and time to stop that pesky "Panasonic" bootaudio too. And that's the first thing I deleted after I booted TWRP, even before rooting.
</TLDR? skipped this>
First things first, enable ADB, enable OEM unlock in developer options, and go to bootloader to unlock it <fastboot oem unlock> THIS WILL WIPE DATA!!
Second thing: Backup nvram.img by sp flash readback and learn how to flash it back (search XDA)- Sometimes you can learn from other's mistakes too! I spent a day and half writing back IMEI and WIFI Mac.
Process (if you don't trust me and want to reproduce the steps yourself)
1. Download stock firmware. (google knows)
2. Patch boot.img so that it doesn't overwrite TWRP with stock recovery on each boot (extract by Carliv Image kitchen and hash out the three lines 663, 664 and 665 mentioning "service flash_recovery /system/bin/install-recovery.sh" in init.rc). I created two copies in the same folder (boot.img, and boot-verified.img) and copied scatter into the same folder for flashing. That's what I saw in the firmware folder.
3. Port TWRP using Carliv Image Kitchen method. I downloaded TWRP from here https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861 but didn't use their method. It didn't work. The TWRP for this chip was stated as android N, but worked well.
4. Flash ported TWRP after copying scatter file to the Carliv Imagekitchen output folder and selecting that scatter in SP droid tools. I again created recovery.img and recovery-verified.img. Don't know if its needed that way. You could wait and flash boot and recovery together from the same folder.
5. That's it, you can enter custom recovery now. Get that pesky "panasonic" bootaudio off the system/media folder now! You can stay content after this or proceed to root.
<nandroid backup now, including Nvram and NVdata. Just in case>
6. Download Supersu zip flashable and flash it via TWRP. https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip?retrieve_file=1 worked for me.
7. Reboot, check root!
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
You're done!
I'll upload my boot.img and ported TWRP if anyone shows any interest in this.
Cheers!
(Bonus: this phone has built in IPtables support in the kernel! I used to flash custom kernel for this ability in other Stock ROMs. AFfirewall works "out of the box"- after rooting, of course!)
Edit: uploaded my modded boot.img and ported TWRP. find it here https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
If you want to go the easy route, unzip the folder and flash it with sp flash. You'll be able to boot into recovery and do the other steps for rooting.
Rememer ONLY DOWNLOAD, don't format, or format and download, or anything!
Click to expand...
Click to collapse
Can you please mention the steps and software needed for rooting the device plz plz plz

gt612 said:
Can you please mention the steps and software needed for rooting the device plz plz plz
Click to expand...
Click to collapse
No need to quote the whole post!
Download twrp and boot from here. https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
download super su from the link in original post. flash iso files in the twrp boot zip (they are for the updated latest version of android 6.0.1). flash supersu via twrp. search for how to do these things.

Hello. I have an Allveiw V2 Viper S (the romanian version fo the eluga note). I got a stock rom (not from my phone) from where i took and modified both the boot.img and the recovery.img and also used the scatter from here to. I couldn`t make mtk droid tools to see my device. I managed to unlock the bootloader, but when i tried to flash the boot and recovery spft gave me a " Obtain DRAM Faild" error. Can you please help?
Thanks!

madhogg said:
Hello. I have an Allveiw V2 Viper S (the romanian version fo the eluga note). I got a stock rom (not from my phone) from where i took and modified both the boot.img and the recovery.img and also used the scatter from here to. I couldn`t make mtk droid tools to see my device. I managed to unlock the bootloader, but when i tried to flash the boot and recovery spft gave me a " Obtain DRAM Faild" error. Can you please help?
Thanks!
Click to expand...
Click to collapse
This was an impulse project. I learned many things in the way. But I have left that effort behind. So, for now: no idea. Hope google helps!

bad.bid said:
I successfully ported TWRP to Panasonic Eluga Note (MTK6753) after a four day effort. Not a dev here. First time doing this.
<TLDR? skip this>
When I started using android in my HTC HD2, every ROM was pre rooted. I took it for granted.
So I get this cheapo MTK and breaking into it is like banging head against a wall!! I was frustrated with the battery drain: Device never sleeps since the last OTA!
So I learnt SP flash tools and downgraded. ( wiped nvram and created another mess in the process- which is a different story. I solved it)
I could spend this effort and time to stop that pesky "Panasonic" bootaudio too. And that's the first thing I deleted after I booted TWRP, even before rooting.
</TLDR? skipped this>
First things first, enable ADB, enable OEM unlock in developer options, and go to bootloader to unlock it <fastboot oem unlock> THIS WILL WIPE DATA!!
Second thing: Backup nvram.img by sp flash readback and learn how to flash it back (search XDA)- Sometimes you can learn from other's mistakes too! I spent a day and half writing back IMEI and WIFI Mac.
Process (if you don't trust me and want to reproduce the steps yourself)
1. Download stock firmware. (google knows)
2. Patch boot.img so that it doesn't overwrite TWRP with stock recovery on each boot (extract by Carliv Image kitchen and hash out the three lines 663, 664 and 665 mentioning "service flash_recovery /system/bin/install-recovery.sh" in init.rc). I created two copies in the same folder (boot.img, and boot-verified.img) and copied scatter into the same folder for flashing. That's what I saw in the firmware folder.
3. Port TWRP using Carliv Image Kitchen method. I downloaded TWRP from here https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861 but didn't use their method. It didn't work. The TWRP for this chip was stated as android N, but worked well.
4. Flash ported TWRP after copying scatter file to the Carliv Imagekitchen output folder and selecting that scatter in SP droid tools. I again created recovery.img and recovery-verified.img. Don't know if its needed that way. You could wait and flash boot and recovery together from the same folder.
5. That's it, you can enter custom recovery now. Get that pesky "panasonic" bootaudio off the system/media folder now! You can stay content after this or proceed to root.
<nandroid backup now, including Nvram and NVdata. Just in case>
6. Download Supersu zip flashable and flash it via TWRP. https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip?retrieve_file=1 worked for me.
7. Reboot, check root!
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
You're done!
I'll upload my boot.img and ported TWRP if anyone shows any interest in this.
Cheers!
(Bonus: this phone has built in IPtables support in the kernel! I used to flash custom kernel for this ability in other Stock ROMs. AFfirewall works "out of the box"- after rooting, of course!)
Edit: uploaded my modded boot.img and ported TWRP. find it here https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
If you want to go the easy route, unzip the folder and flash it with sp flash. You'll be able to boot into recovery and do the other steps for rooting.
Rememer ONLY DOWNLOAD, don't format, or format and download, or anything!
Click to expand...
Click to collapse
Brother i try this method at Panasonic eluga ray 700 (MT6753_EB_90S55ER7_V1008) flash complete and successful install problem my set dead not On so i install original Panasonic eluga ray 700 (MT6753_EB_90S55ER7_V1008) flash set is dead and not connecting to pc plz help me what i can do ......

andromodgod said:
Brilliant Work man. I also was sort of in your situation as well . i have a panasonic Eluga A3 (Qmobile Noir E2) in my country. Stock Qmobile rom was horrendous. so i flashed the panasonic rom but hated the boot audio and the bloatware that came with it. so i decided to make a slimmed down version of it and successfully did it by using superr's kitchen. and also using the kitchen i removed the encryption on the boot.img and then patched it using magisk for easy rooting without recovery. when flashed together with the modded system.img and modded boot.img and twrp, i was totally in control of my device.
If you need any help with anything mtk send me a pm
also are you able to access internal storage in twrp or not ??
Click to expand...
Click to collapse
Panasonic eluga ray 700 (MT6753_EB_90S55ER7_V1008) after flash set is dead and not connecting to pc plz help us expert......
....

Network drop
Hello dear friend I successfully flash twrp 3.0.2 but I see network signal problem signal drop many time..
Pls tell me how to resolve these issue..

Singnal drop
bad.bid said:
Ya, I fixed Imei issues. this one is like a signal drop once every 15 minutes.
Click to expand...
Click to collapse
Dear sir panasonic eluga note network signal drop many time a day after installing ur ported twrp ..Pls tell me how to resolve signal drop issue..

Really wanna do it but your steps sound way complicated for "non-MTK pro guy". I have that device lying unused. it would be awesome if you could throw a "readme" file in your drive or here with simpler guidance steps like other "TWRP & root installation guide" we have for other phones. Plus You seem like you could port/build a ROM for this device and make substratum friendly. I know it's a big ask & I have a feeling that you like dark UI for that device too . Hoping for the best response.

If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
I have a doubt about these two steps
Should i have to flash it twice and have to download two separate file which is one flashable zip and installer. And in the next step 9th which zip file should i flash.
My questions might sound silly but i am asking so because when last time i tried i installed xposed, installed its firmware and then downloaded a module it was cynolockscreen something and applied it. It asked ne to reboot i did but then my phone crashed. Screen was going on and off then i rebooted to recovery and did a factory reset amd since then i haven't done any thing in my phone not even flashed the SuperSU...
Can you please help me with the further steps...

rooting eluga note
can u pls tell me how to root eluga note? i've tried many apps to root it but nothing worked

[GUIDE] Manual Update P20 PRO with HuRUpdater and TWRP

If you have unlocked bootloader and TWRP, you can flash a newer firmware using HuRUpdater
This steps can be risky for your device if you don't know what you are doing, so try to read some guide about flashing first
before attempt these operations if you are a new to these things.
I don't take any responsability of catastrophic failures and loss of data.
-- I did a titanium backup before the upgrade, but in my case no restore was needed as all data were retained.
In this simple update no factory reset was triggered.
Please read the HUrupdater thread also for more informations.
- Install Unofficial TWRP by Pretoriano80
- Download HuRUpdater 0.3 and put it in a folder in your sdcard
-Search the firmware for your device with Firmware Finder
Make sure you download the correct firmware version for your device (type, region code)
wrong firmware can brick your device
I used updated firmware files APPROVED for my device checked with firmware finder app.
I don't know if flashing NOT APPROVED files will harm your device. You have been warned.
I successfully updated my device from CLT-L29C636B130 to CLT-L29C636B131
***Don't try to rebrand your phone with this method***
- Use FullOTA-MF images of the firmware and download the 3 files needed
in my case:
update.zip
update_data_full_public.zip
update_full_CLT-L29_hw_spcseas.zip
- rename the 3 files to:
update.zip
update_data_public.zip
update_all_hw.zip
and put the files in the same folder with HuRUpdater 0.3
(optional)
- The Update will overwrite your TWRP custom recovery so to retain it automatically rename the TWRP IMAGE
twrp_clt_0.1.img to recovery.img and put in the same folder with others files.
{
"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"
}
- Remove all security locks from your phone before rebooting to TWRP.
Go to System- Developer Options
Disable Screen lock (third row)
this will suffice to remove the security locks of the phone (sequences, pin,fingerprints)
-Reboot to TWRP
If you are rooted, remove Magisk first with its uninstaller. I don't know if it's needed but better don't have things like that
messing around during the update. You can reroot later anyway.
-Go to the folder with the files and flash the system using the HuRUpdater_0.3.zip ONLY
That great tool will do all the job needed. After system, it will reflash the TWRP recovery IMG you previoulsly renamed
overwriting again the stock ramdisk_recovery that comes with the firmware.
It will take some minutes, don't panic and let the process end.
You will see some red errors but don't worry,it's fine
- Reboot in your TWRP to check (from inside TWRP , reboot - recovery, be sure not to have a usb cable plugged or it will trigger stock EMUI e-recovery)
- Wipe dalvik and cache
- Reroot new system with Magisk
-Reboot to system and restore the security lock in developer options
- Restore your fingerprints and pins
- Enjoy the update.
Thanks to @zxz0O0 for this great Tool, works good on P20 pro too.
And obviously @Pretoriano80 for his recovery.

Reserved

Working adb sideload?

If an update is already approved by Huawei, can we just download the firmware through HFF and place it in the appropriate folder, go to SYSTEM to check for updates, and then install it?
mangusZen said:
If you have unlocked bootloader and TWRP, you can flash a newer firmware using HuRUpdater
This steps can be risky for your device if you don't know what you are doing, so try to read some guide about flashing first
before attempt these operations if you are a new to these things.
I don't take any responsability of catastrophic failures and loss of data.
-- I did a titanium backup before the upgrade, but in my case no restore was needed as all data were retained.
In this simple update no factory reset was triggered.
Please read the HUrupdater thread also for more informations.
- Install Unofficial TWRP by Pretoriano80
- Download HuRUpdater 0.3 and put it in a folder in your sdcard
-Search the firmware for your device with Firmware Finder
Make sure you download the correct firmware version for your device (type, region code)
wrong firmware can brick your device
I used updated firmware files APPROVED for my device checked with firmware finder app.
I don't know if flashing NOT APPROVED files will harm your device. You have been warned.
I successfully updated my device from CLT-L29C636B130 to CLT-L29C636B131
***Don't try to rebrand your phone with this method***
- Use FullOTA-MF images of the firmware and download the 3 files needed
in my case:
update.zip
update_data_full_public.zip
update_full_CLT-L29_hw_spcseas.zip
- rename the 3 files to:
update.zip
update_data_public.zip
update_all_hw.zip
and put the files in the same folder with HuRUpdater 0.3
(optional)
- The Update will overwrite your TWRP custom recovery so to retain it automatically rename the TWRP IMAGE
twrp_clt_0.1.img to recovery.img and put in the same folder with others files.
- remove all security locks from your phone before rebooting to TWRP.
Go to System- Developer Options
Disable Screen lock (third row)
this will suffice to remove the security locks of the phone (sequences, pin,fingerprints)
-Reboot to TWRP
-If you are rooted, remove Magisk first with its uninstaller. I don't know if it's needed but better don't have things like that
messing around during the update. You can reroot later anyway.
-Go to the folder with the files and flash the system using the HuRUpdater_0.3.zip ONLY
That great tool will do all the job needed. After system, it will reflash the TWRP recovery IMG you previoulsly renamed
overwriting again the stock ramdisk_recovery that comes with the firmware.
- It will take some minutes, don't panic and let the process end.
You will see some red errors but don't worry,it's fine
- Reboot in your TWRP to check (from inside TWRP , reboot - recovery, be sure not to have a usb cable plugged or it will trigger stock EMUI e-recovery)
- Wipe dalvik and cache
- Reroot new system with Magisk 16.4
-Reboot to system and restore the security lock in developer options
- restore your fingerprints and pins
- enjoy the update.
Thanks to @zxz0O0 for this great Tool, works good on P20 pro too.
And obviously @Pretoriano80 for his recovery.
Click to expand...
Click to collapse

ekremxx said:
Working adb sideload?
Click to expand...
Click to collapse
I have not tried that, it depends on the TWRP recovery, let us know if you try

sarichter said:
If an update is already approved by Huawei, can we just download the firmware through HFF and place it in the appropriate folder, go to SYSTEM to check for updates, and then install it?
Click to expand...
Click to collapse
I really don't know, and I don't think it will work.
As far as I know this is the only manual update method for now.
I just updated to unapproved .150 for my c636 and all seems fine

If I reinstall twrp by renaming it as recovery.img, will HuRUupdater install the twrp in recovery_ramdisk, or will it replace eRecovery instead?
If twrp doesn't replace eRecovery, how do I get to eRecovery? As of now, whenever I want to enter recovery, it will get to twrp.

sishafie said:
If I reinstall twrp by renaming it as recovery.img, will HuRUupdater install the twrp in recovery_ramdisk, or will it replace eRecovery instead?
If twrp doesn't replace eRecovery, how do I get to eRecovery? As of now, whenever I want to enter recovery, it will get to twrp.
Click to expand...
Click to collapse
eRecovery is not replaced.
To enter there try other volume button or with a cable plugged

Not working adb sideload... How I can install I not know...not have my phone micro SD card slot...puff

sishafie said:
If I reinstall twrp by renaming it as recovery.img, will HuRUupdater install the twrp in recovery_ramdisk, or will it replace eRecovery instead?
If twrp doesn't replace eRecovery, how do I get to eRecovery? As of now, whenever I want to enter recovery, it will get to twrp.
Click to expand...
Click to collapse
when booting there is a screen prompting to whether you want to go to eRecovery by pressing up or just boot into system and something ike that
---------- Post added at 04:23 PM ---------- Previous post was at 04:23 PM ----------
ekremxx said:
Not working adb sideload... How I can install I not know...not have my phone micro SD card slot...puff
Click to expand...
Click to collapse
why you want to do sideload ? guide clearly explained to install it using TWRP.
if you dont have TWRP, then install it first

I install twrp but how can I install whitour sd card I not have sd card slot my Huawei p20 pro one SIM card join no have sd card slot how I can install i not know.. when I try install abd sideload hrudader say cant find update.zip
update_data_public.zip
update_all_hw.zip

ekremxx said:
I install twrp but how can I install whitour sd card I not have sd card slot my Huawei p20 pro one SIM card join no have sd card slot how I can install i not know.. when I try install abd sideload hrudader say cant find update.zip
update_data_public.zip
update_all_hw.zip
Click to expand...
Click to collapse
The guide never said that you need sdcard
it said, that u need to put all those three files in same folder with the HuruUpdater.zip , and of course you can put it in your internal storage
i wont explain anything here. you better re-read the whole main post, as it already very clear
- put all files in one folder
- reboot to twrp
- flash huruupdater.zip
- boot to system
- reboot to twrp
- flash magisk to reroot
which step exactly that not understandable ? :silly:

I can install that's style orjinal filmware ty so much

Forgive me if this is not the appropriate forum, one question:
I have the Huawei P20, for this phone I only have 2 firmware files, the "Update .zip" and the "update_full_EML_L09_hw_eu.zip ".
Can't find the "update_data_public.zip"
Can I install the new firmware with Hurupdater anyway ? Thanks in advance.
Roberto

moghetto said:
Forgive me if this is not the appropriate forum, one question:
I have the Huawei P20, for this phone I only have 2 firmware files, the "Update .zip" and the "update_full_EML_L09_hw_eu.zip ".
Can't find the "update_data_public.zip"
Can I install the new firmware with Hurupdater anyway ? Thanks in advance.
Roberto
Click to expand...
Click to collapse
You should check and ask at P20 and HURupdater threads.
I don't know about P20.

Hello! Thank you very much for this tutorial .. A question.. I am in Chipset-boston 8.1.0. 001 (01DL) I have the bootloader open, just by installing the recovery that you say in the tutorial and then the other steps, I would not have a problem, right?

can I downgrade firmware safely with this method? im on 150 and want to go back to 130

Ferezesal19 said:
Hello! Thank you very much for this tutorial .. A question.. I am in Chipset-boston 8.1.0. 001 (01DL) I have the bootloader open, just by installing the recovery that you say in the tutorial and then the other steps, I would not have a problem, right?
Click to expand...
Click to collapse
You should not have problem, unless you are trying to rebrand.

Allesa said:
can I downgrade firmware safely with this method? im on 150 and want to go back to 130
Click to expand...
Click to collapse
I don't know about downgrading and I would not raccomend it

mangusZen said:
You should not have problem, unless you are trying to rebrand.
Click to expand...
Click to collapse
Thanks you. Only i want to Update... What firm you recommend That improves the duration of the battery?

[RECOVERY][ROOT]TWRP 3.3.1-1 Galaxy J4+/J415F/FN/G/DS

Unofficial release -TWRP recovery for the Galaxy J4 plus 2018 - SM-J415 MSM8917
{
"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"
}
TWRP 3.3.1-0 Released
May 22, 2019
TWRP 3.3.1-0 is out now for most currently supported devices.
What's new in 3.3.1-0:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
Update - 17/8/2019
TWRP 3.3.1-1 OO/PP build released
Current status - Beta
Treble supported
Bugs: brightness slider
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Plug in the USB cable and then hold POWER + VOL DOWN + VOL UP)
2. Load the respective file below into the AP slot, uncheck Auto-reboot(not required for twrp_3.3.1-1) and hit start.
twrp_3.2.3-1_sm-j415f_30319
twrp_3.3.1-1_j415x_17819
3. After flashing and ODIN reports PASS immediately force reboot to recovery. (Not required for twrp_3.3.1-1 as it should auto reboot to recovery). You should now see TWRP recovery.
Do NOT let the device boot to the OS.
4. Flash the V3 RMM bypass zip
https://forum.xda-developers.com/showpost.php?p=79745844&postcount=627
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT AND BECOMING RMM LOCKED FOR 7 DAYS.
I ALSO SUGGEST BACKING UP ANYTHING YOU NEED ON INTERNAL STORAGE. AT SOME POINT YOU MAY EXPERIENCE A 'VERIFICATION FAILED MESSAGE' .
THIS IS NORMAL, BUT WILL REQUIRE THE DATA PARTITION TO BE FORMATTED IN TWRP.
5. Reboot to TWRP (Do not boot to the OS yet)
***** ROOT INSTRUCTIONS:*****
OREO ONLY
1. Flash the Forced encryption disabler patch. This is only required if you wish to have full functionality in TWRP.
Flashing this will disable Samsung's forced encryption. Disabling encryption will allow TWRP to mount the data partition.
After flashing the patch it is necessary to *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
J4+J6+_oreo_forced_encryption_disabler
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
(NOTE: The DEFEX patched Oreo kernel below may be needed for full root support if certain apps do not work with root):
https://androidfilehost.com/?fid=1395089523397921797
3. Enjoy your rooted device.
PIE ONLY
1. Due to some new securities in Samsung's latest Pie kernels, root will not work with the stock kernel. The patched kernel below is required to gain root on Pie.
Features:
Dmverity, proca, five and defex disabled.
OTG and NTFS file system support.
Selinux permissive switchable.
This kernel may require the U4 bootloader.
(NOTE: flashing a custom kernel on PIe breaks the lockscreen. Ensure NO lockscreen is enabled before installing the kernel.)
J415FXXU4BSF7_patched_boot_318919
2. To root I suggest installing the latest Magisk beta as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/app...mless-t3473445
3. If you wish to have access to internal storage /DATA in TWRP then encryption will need to be disabled. See step 1 of the Oreo root instructions then instead of installing the J4+J6+_oreo_forced_encryption_disabler install the zip below with TWRP:
Disable_Dm-Verity_ForceEncrypt_Quota_08.02.2019
3. Reboot.
The device will take a good 10 mins to boot first time.
Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my tester @kapmino269 [MENTION=6037748]Zackptg5 for the DM-VERITY & FORCEENCRYPT DISABLER @teamwin, @corsicanu for RMM V3 bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU

kapmino269 said:
Thank you very much for building twrp but there are bugs :
1- After I make steps all is done I power off it but when I open it isnot boot & i see a message All the words I understood that "you flash unauthornized boot.img & recovery img and return the phone to the company to fix the phone" and phone didnot boot I recognize that when I open internet in phone samsung detect the change in phone so i solved it by:
:good: I repeat the steps but after i connect to internet , i activate magisk and close wifi and download afwall on my sdcard from appkpure by pc and install the app an enable firewall and solved but there message that rules not apply but in fact it is applied and all is done . SOLVED
2-When I close phone and recharge it, it isnot recharged but it continue rebooting not to system but just recharge windows and poweroff and agian to recharge window And so on .
I coulding solve but I sure the error is in boot.img or in another . NOT SOLVED
Sorry for my english.................
Click to expand...
Click to collapse
Thanks for all the info, but does TWRP actually boot?

kapmino269 said:
Twrp is very very good and backup and restore and mount are good but there are bugs in system not in recovery addition the last:
3- the percentage of battery when charging,it isnot change . NOT SOLVED
What is the reason ?
Click to expand...
Click to collapse
Percentage doesn't change in twrp or when power off?

kapmino269 said:
SORRY MR ashyx there isn't bugs in system my charger was cut and it is the reason of rebooting to recovery. But bugs in recovery brightness control and backup encryption.
And your build is good ask twrp.me to make it official.
Click to expand...
Click to collapse
You will need to Format (not wipe) /data to remove encryption and mount the data partition. Samsung encryption isn't supported yet by TWRP.
Brightness isn't a deal breaker, but I'll look into it.
Could you do me a favour and post the recovery.log so I can check it over?

kapmino269 said:
And I forget said that all afwall versions above 2.9.9 doesn't work and Samsung will lock the phone and you should download afwall with date 5/2018
Click to expand...
Click to collapse
What do you need AFwall for?

kapmino269 said:
To prevent Samsung apps detect the change on the boot.img and recovery.img and so on and I told you at first that after flashing and activate magisk I set wifi on and when I power off the device and open it ,I couldn't open phone on any mode ,there is message apear to me told if I boot to system it said as I remember and I understand that "there is boot.img flash to phone by unauthorized way please return device to company or someone you buy the device from him to fix the phone " and replacing when reboot recovery boot.img by recovery. img and as I remember the screen was blue and the text was written in black and red. so I flash sammobile stock with Odin and repeat your twrp installing steps and activate magisk and close wifi and put afwall 2.9.9 (above versions didn't work ) and the error didn't appear again .
Click to expand...
Click to collapse
I don't think that you need AFwall. When you see that message boot to TWRP and format your device, install Magisk and the Oreo encryption disabler.
This should prevent this message appearing again.
Also disable securitylogagent apk.

Can this be used to flash GSI?

Jason Grewal said:
Can this be used to flash GSI?
Click to expand...
Click to collapse
As posted in the OP :
Update 8/12/2018
Current status - Beta (Tested working)
Treble supported
Bugs: brightness slider
Click to expand...
Click to collapse

kapmino269 said:
sorry I see another error in restore in TWRP .
all partitions restored but when I finish restore twrp said unable to mount /system and I couldn't reboot system
Click to expand...
Click to collapse
Have you tried backing up only system again then immediately restoring?
Also which media are you restoring from?
Also need the recovery log after failure.

kapmino269 said:
A1 :No , I will try backup system and system image only.
A2 :I restore from usb otg .
A3 :It success in restore efs boot vendor and others but system not mount and tried to return system again .
££i flash sammobile rom and install magisk as you tell and restore all phone partitions Except system and system image ££ The phone open again.
###I will try restore system again and i will sent you recovery.log BUT WHICH MEDIA I SHOULD USE USB OTG OR SDCARD ###
I am sorry for disturb.
Click to expand...
Click to collapse
Can you try backing up just system, not system image to internal storage then try restore?

kapmino269 said:
ok, I will try .
I would ask you about something else but sending you private message unanable I need to ask you but i couldnot because the question is about something else twrp for j415f how to send the issue to you
Click to expand...
Click to collapse
If it's related to this device then just post it. I don't accept pm's.

kapmino269 said:
A-Restoring system only and other partition is done and succeed and faster from internal storage but if i copy it to pc or sdcard Is all files will copied or not or Error will apper after copy (restoring again).
Thanks for your help .
1- it is related to j415f some apps like busybox and linux deploy and afwall(new version) grant root access but didnot run.
2- #
Another problem :
no,it isnot .it related to wlan monitor mode for gt-i9500 (internal (bcm4335 ) or external (TL-WN22N) ) , I tried linux deploy kali hunter nexmon others ,and please reply if you could help me or reach me to someone help me .
#
please reply me quickly about (2) to delete it
SORRY I havenot any way to reach you except this .
Click to expand...
Click to collapse
1. Isn't really related to twrp but magisk itself. Better posting in the magisk thread.
2. Unfortunately can't help you with this as I don't mess around too much with that kind of stuff.

I wouldnt dare to do anything on this before everything is 100% clear and failproof. This phone behaves like its about to collapse every second idk why but it feels like that

kapmino269 said:
Thank you very much for your help and your interest .
Please ,Can you fix restoring system from usb otg ? and all files you need from me i will send you it ,
you must make your twrp ideal and make it official in #twrp.me# like Alberto86(recognise developer) : make gt-i9500 twrp and ge officialty .
surendrajat(member ) : Make SM-J737S twrp it is in #twrpbuilder.github.io#
I think you should publish the recovery in this sites at the nearest time. I think also you should make video on youtube to make your project spread out faster ,because there are people donot know xda ,I tried to make video but my presentation was very bad so i delete it from youtube .
And Sorry for distrubt
Click to expand...
Click to collapse
I don't think there is anything to fix regarding the restorating of a backup from OTG.
It's just simply a case of some media is not suitable for backup and restore.
I've even seen reports of certain MicroSD cards causing issues with TWRP.
It's likely that if you try a different USB stick you won't have any issues.
As regarding making it official. I will consider it. However I have many, many builds of TWRP for a lot of other devices that are not official either.
This is due to the fact I do not like the convoluted system of getting it made official.
I have discussed this previously with teamwin and asked for a proper submissions page to no avail.

kapmino269 said:
Ok as you like but you can improve twrp .
I mean :
1 -Could you compress encryption disable and
rmm bybass and recovery in twrp.tar file to flash it by odin in one step wihout following install steps that you write , Steps may be difficult with others , With me I try serval times to success and i know some skills about android but others may donot know .
2 - Why your twrp depend on magisk install
,if magisk doesnot install phone doesnot reboot system , I think twrp should not be depend on root & If some one need twrp and doesnot need root.
3 - Busy box i cannot install it in my phone why ,?
Click to expand...
Click to collapse
No I cannot make an all in one to flash in ODIN.
Firstly because its not possible. Odin cannot run scripts, only recovery can.
Secondly if people cannot follow instructions then maybe they shouldn't be attempting to modify their device.
TWRP doesn't depend on Magisk, your device does.
Samsung incorporate many security hurdles to prevent hacking and modification.
These security blocks need to be patched or the device will not boot.
These blocks can be patched manually, however Magisk can patch most of these during the root process.
I have no idea why you cannot install busybox on your device as you have not provided any info of the issue.
In any case busybox is included with Magisk. To use it install the busybox module by osm0sis.

kapmino269 said:
picture
Click to expand...
Click to collapse
I see what your saying, however I will keep things as they are. I'd prefer people to have an understanding of what they are installing and I believe it's simple enough.
Unfortunately I can't help with the busybox issue. However as I stated you can use the busy module provided by osm0sis.
He keeps everything up to date and is highly recommended.

kapmino269 said:
I face issue :
I test j4+ snd s4 security in lookscreen :
1- In j4+ : if I delete /data/system/locksetting.db or all contain locksetting name in twrp buy terminal or file manager or script.
2 -add delete *.key on s4 .
Is there solution from system or twrp to prevent lock screen crack or it hash stolen to crack not tell me (chattr).
Thank you
Click to expand...
Click to collapse
If I'm reading it correctly you want a way of preventing the lockscreen credentials from being deleted.
The only way is to remove TWRP Tbh so no one had access to the file system.
Also this isn't really a twrp related issue and a little off topic.
However I have been looking at possible ways to password TWRP thus preventing access at all.
But even that could be circumvented by simply flashing another version of TWRP.
The only safe way is to remove twrp, unroot your device and disable OEM unlock.

kapmino269 said:
1 - I donot have any ways to reach you and you is the developer of twrp for j4+ and Know all about it and you donot accept pm , I could make
thread and you answer me in it but this issue in twrp so all is well .
2 - I want twrp and root ,Is there any solve ,I have idea may success sent me it may be sucess or not
it is
1- make data partition not mount or read only on twrp .
2- when I need to install something I will mount it by writing command in system terminal only (that command or script or program doesnot be found in twrp ) to be mounted in recovery mode .
3- I mean that data not mount in twrp without enable mounting in system and twrp doesnot have permission to mount data without system access .
but how this will acheive without you man .
another idea the same but replace mounting by read only
Click to expand...
Click to collapse
If you don't want data to be mounted in twrp then why not just leave it encrypted. Then only you have access to it via the OS?
Failing that just remove the mount entry for /data from the fstab.
This way data will only be available and mountable by using terminal commands.
The other way is to only install twrp when you need it.
For example you could use a script which you could run to flash twrp when booted to the OS each time you need it or if you prefer use something like flashify.
When you are done with twrp, simply use the restore option to restore the stock recovery.
This way only you have access to /data.

how to do this on galaxy J4?pls. help
i have a lock bootloader in download mode

Has anyone tried any gsi?
I tried havoc os 2.0 didn't work.

[GSI][Android 10] Install AOSP 10 on Huawei Honor 6X.

POST - v14
(This number will increase every time the post is updated.)​What's new in v14?
Corrected some simple mistakes in procedure.​Modified overall post for better UX.​
​
Spoiler: Version Changelog
What's new in v13?
Modified Gapps part in requirements to make it more clear.​Added useful information section. for Pro Noobs and Ultra Noobs like me.​​What's new in v12?
Added User Contributions and feedback section.​Added Miscellaneous recommendations section.​Modified some steps in installation procedure to make it even more noob friendly.​Linked @lmaohelp's thread.​Decreased size of text in procedure.​​​
​
This ROM is based on Android 10 GSI builds of @phhusson (Thanks a ton to him).
Thanks to @Hami_Do for his hi6250 patches.
Thanks to Huawei for making their phones nearly unbrickable .
Thanks to @Djiban for his ideas on improving the thread.
Follow this thread only if you know what you're doing. I'm not responsibe for any damage or thermonuclear wars .
Read the post completely and understand it before doing anything ATLEAST FOR THE SAKE OF MANKIND .
This thread is best viewed in PC and is Noob Friendly.
Note that I was using flux substratum theme in the screenshots. Hence, icons and colors may vary on your device.​
Spoiler: Requirements
Requirements:
Huawei Honor 6X (Unlocked Bootloader. If not, follow this post (using PotatoNV) or YouTube video.
EMUI 8 (If not, you could follow this guide, direct file : link).
GSI from link (download system-quack-arm64-aonly-vanilla.img.xz, you could try others but arm64, a-only is must).
TWRP from attchments or link or any other TWRP recovery compatible with Honor 6X EMUI 8.
Gapps(Optional, I used nano OpenGapps, NikGapps gave an error during installing, You can also try others. You can directly try the img with gapps instead of vanilla but i prefer nano gapps over vanilla).
stock recovery.
Time.
PC.
ADB and Fastboot.
Patience.
Human Brain.
ALL IN ONE GUIDE : Check it out here. It contains every thing in detail all the way from bricked device -> EMUI 2 -> EMUI 5 -> EMUI 8 -> AOSP 10 (mentioned in this post). Thanks to @lmaohelp for his effort and describing everything in detail.
Useful Information :
What on the Earth is meant by Vanilla android? -> it is the stock / pure version of android without Google apps and services.​
What is OpenGapps? Check it out at OpenGapps.org!​
What is Nano (not the mathematical 10^-9) Gapps? It is a version of Gapps with Minimal installation which means only the core part of gapps is installed with very little major apps. They can be installed later.​
What is ARM64? it is a 64 bit operating system/platform.
What on the moon is AOSP? It stands for android open source project which is the purest form of android.
NOTE : My device bootlooped whenever I tried installing Magisk. So, better stick with the PHH-SuperUser that you get out-of-the-box with the system image.
NOTE : Skip every step with gapps if you are already using img with gapps.
What isn't working :
VoLTE (can't be fixed as per my knowledge), Camera (FIXED NOW | trying to find a fix, replacing libcamxxx could help), Flashlight (FIXED NOW | also trying to find a fix, fixing camera may fix this too).
CAMERA AND TORCH HAVE BEEN FIXED. Thanks to @Hami_Do (flash the attched patch file whenever you are bored, LOL)
What's Working :
Everything except the ones mentioned above VoLTE.
*Tell me if something else isn't working.
***If you have a bricked device/messed up somewhere during the process and unable to figure out what to do, follow this guide by @lmaohelp .***​Procedure :
Make sure your device is running EMUI 8.​
Extract downloaded image using some xz extractor(7zip can also do this), copy it to pc.​
Reboot your device to TWRP recovery.​
Format the data partition {Wipe > Format data > type "yes"}​
(Optional) In TWRP, choose wipe > advanced wipe > select system, data, cache and DALVIK and format them.​
Check if your device is detected by adb using
Code:
adb devices
.​
Move the img file using adb to device
Code:
adb push -p *img-name*.img /sdcard/
(the img file must be in adb directory).​
(Optional, only if you want nano gapps over vanilla) Move Gapps in the same manner
Code:
adb push -p *gapps-name*.zip /sdcard/
(the zip file must be in adb directory).​
Install img as system image {Install > Install Image > Select > Choose system image > Swipe➡}.​
(Optional, only if you want nano gapps over vanilla) Unmount and Remount system partition. Go to wipe > advanced wipe > Choose system > resize. Flash gapps.​
Flash stock recovery(also available in attachments) with twrp in the same way. push it with adb using
Code:
adb push -p STOCK_RECOVERY_RAMDISK.img /sdcard/
and flash it with twrp as "Recovery" after choosing install image.​
Disconnect your device from PC and reboot to recovery(stock one).​
Clear cache partition and perform a factory reset(You'll get an error during factory reset but you have to do it) (your device will bootloop if wiped with twrp itself).​
Reboot, Cross your fingers and wait.​
>If you flashed gapps over vanilla, the first boot would take about 5 mins. else, it would be very fast. Subsequent boots on both are quite fast.
>Sometimes, I observed that flashing gapps from internal storage caused bootloop(this is because of corrupt zip), in such case get back to EMUI 8, repeat the process by flashing gapps from micro sd.
*you'll get a warning that something wrong with your device every time you boot it. IGNORE IT.
Spoiler: Additionals
Additionals:
> If you messed up somewhere during installation, you can always recover your device by following this guide.
> If you have the update.zip file from the above mentioned EMUI 8 folder directly, you could just directly flash it after wiping data, system and cache(use adb push or microsd to transfer update.zip to device).
>Its better to charge your device to atleast 70% before doing anything as you'll have ample of time to recover it if you messed up something. If not, you can still charge your device in eRecovery mode and twrp but i found some issues like heating up and slow charging.
>Don't forget to set ringtone, notification and other sounds from settings after booting.
Spoiler: Updates
Updates :
I was able to install magisk by flashing unSU zip from @Hami_Do 's thread on hi6250 manual fixes and then flashing phh's magisk after deleting phh-su from /system/bin/ but sadly, I wasn't able to use quickswitch for other launchers as it needs magisk version of 20.4 (min.) but phh's magisk is 19.3 and substratum theme engine is not working (due to some error). So, I'm sticking with the root that comes out of the box and I recommend you to do the same. EXTRAS : The Phone and Messaging apps that came out of the box with the GSI stopped working after installing magisk. So, you are installing magisk, just replace these system apps from LineageOS ones or delete them and install the google phone and messaging from play store.
During multiple tests (installing, modifying and testing the GSI for its stability in multiple ways), I found that you need not always go back to stock EMUI 8 if you messed up something. This works without error but if you have some time, getting back to stock EMUI 8 is still recommended before installing some other ROM/GSI.
Try not to touch the finger print sensor when you are at the setup after first boot. This is making the finger print sensor not recognisable until next reboot.
User Feedback and Contributions :
Thanks to @OrionThyHunter for his feedback and some fixes :
Using the Greenify app will stop the finger print sensor from working. FIX : Disable "Alternative Screen Off Mode".
Thanks to @[email protected] for finding out he following issues :
Adaptive Brightness Doesn't work. Flash the attachment in this post to fix it.
To pass SafetyNet, follow this post.
Miscellaneous Recommendations :
Use Google Camera Go app for photos. Its much better than the GSI's stock one.
​
Happy Flashing !
{
"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"
}

thank you it worked, now waiting for volte and camera fix on next update.... please update soon.... waiting waiting waiting........

[email protected] said:
thank you it worked, now waiting for volte and camera fix on next update.... please update soon.... waiting waiting waiting........
Click to expand...
Click to collapse
I think VoLTE can't be fixed.
For camera, you have to replace each file in /system/lib/ starting with libcam(libcamxyz...) from stock emui 8 and check each possible combination with subsequent reboots. I'm a little bit busy right now as I'm working on AOSP 11(as I believe it'll run without much problems because it has been tested on other hi6250 devices) with @Djiban. You could just do this on your own. If you find any working combination, please post it in this thread.

[email protected] said:
thank you it worked, now waiting for volte and camera fix on next update.... please update soon.... waiting waiting waiting........
Click to expand...
Click to collapse
Finally, Fixed it dude(camera and torch) by replacing libraries! Found a patch that does the same thing. Updated the Original post.
Tried a lot to fix VoLTE but didn't work... will try again later.
CHECK IT OUT!
#endyourwait LOL!

Hi again, I got this installed using TWRP, and I still have TWRP installed because I don't have the stock recovery. The system boots but it is giving me an error saying encryption unsuccessful, with a button saying "erase all data" which does nothing, and I am unable to do anything.
I was having this error when I first installed EMUI 8 from EMUI 5 as well, but at least the button took me to eRecovery, where the factory reset would fail at 5-6%. Currently if I go into eRecovery and click factory reset, it just reboots and takes me to TWRP again. Also, when I go into eRecovery it asks me to reformat the partition because it is "corrupted", which somehow changes the file system for /data to f2fs, and causes the phone to be stuck on the android boot animation. When I change /data back to ext4 I am able to boot back to the screen of encryption unsuccessful.
How do I fix this issue and be able to use the phone? Attached is a screenshot of the error message the OS is giving me.

lmaohelp said:
Hi again, I got this installed using TWRP, and I still have TWRP installed because I don't have the stock recovery. The system boots but it is giving me an error saying encryption unsuccessful, with a button saying "erase all data" which does nothing, and I am unable to do anything.
I was having this error when I first installed EMUI 8 from EMUI 5 as well, but at least the button took me to eRecovery, where the factory reset would fail at 5-6%. Currently if I go into eRecovery and click factory reset, it just reboots and takes me to TWRP again. Also, when I go into eRecovery it asks me to reformat the partition because it is "corrupted", which somehow changes the file system for /data to f2fs, and causes the phone to be stuck on the android boot animation. When I change /data back to ext4 I am able to boot back to the screen of encryption unsuccessful.
How do I fix this issue and be able to use the phone? Attached is a screenshot of the error message the OS is giving me.
Click to expand...
Click to collapse
Did you flash stock recovery after flashing system image?
Get back to emui 8(if you have update.zip, you could directly flash it with twrp). Repeat the process. Flash stock recovery. Perform a factory reset. And boot it to the system for the first time. You could then flash twrp with fastboot.
***Do not do a factory reset with twrp! Its causing errors.***

Apparently it could be a faulty EMMC chip according to this website, which makes sense since TWRP is not able to mount the internal storage partition or the Dalvik / ART cache, and eRecovery is not able to reset the phone, which is a characteristic of EMMC failure, according to this website. I had to unplug the battery countless times when I was tinkering with the phone, because my power button is broken, and it definitely would've contributed to this failure according to what I have read. Well, guess I'm done with this phone lol
EDIT: Well I'm starting from scratch again but everything is installing fine so I guess nothing is wrong currently? Huawei factory reset even worked

Venkata Lochan Nune said:
Did you flash stock recovery after flashing system image?
Get back to emui 8(if you have update.zip, you could directly flash it with twrp). Repeat the process. Flash stock recovery. Perform a factory reset. And boot it to the system for the first time. You could then flash twrp with fastboot.
***Do not do a factory reset with twrp! Its causing errors.***
Click to expand...
Click to collapse
No, I don't know where to find the stock recovery file, where can I find it?
I managed to boot into EMUI 8 just fine since I did not have a password on the EMUI 5 OS before installing lol. Now I just need the stock recovery you are talking about so I can follow your steps.

do you mean, you testing ASOP 11 on honor 6x ? if yes wow......

[email protected] said:
do you mean, you testing ASOP 11 on honor 6x ? if yes wow......
Click to expand...
Click to collapse
Nope, not now. @Djiban is quite busy and for me to work, I'm not having a spare device. He'll do it when he's got free time.
I didn't find much noticeable differences between AOSP 10 and 11 execpt some ui improvements and under-the-hood improvements. So, I'll skip AOSP 11 and directly will work with AOSP 12 on future. I liked the new things introduced in android 12. So, I'll definitely work on it.

lmaohelp said:
No, I don't know where to find the stock recovery file, where can I find it?
I managed to boot into EMUI 8 just fine since I did not have a password on the EMUI 5 OS before installing lol. Now I just need the stock recovery you are talking about so I can follow your steps.
Click to expand...
Click to collapse
Do you have the update.zip file?
Or wait I'll attach one in few hours...

lmaohelp said:
Apparently it could be a faulty EMMC chip according to this website, which makes sense since TWRP is not able to mount the internal storage partition or the Dalvik / ART cache, and eRecovery is not able to reset the phone, which is a characteristic of EMMC failure, according to this website. I had to unplug the battery countless times when I was tinkering with the phone, because my power button is broken, and it definitely would've contributed to this failure according to what I have read. Well, guess I'm done with this phone lol
EDIT: Well I'm starting from scratch again but everything is installing fine so I guess nothing is wrong currently? Huawei factory reset even worked
Click to expand...
Click to collapse
This is because twrp on our phone doesn't support encryption-decryption things. So, they can only mount internal storage when you perform a complete data format by typing "yes".

Venkata Lochan Nune said:
Do you have the update.zip file?
Or wait I'll attach one in few hours...
Click to expand...
Click to collapse
I do, but I'm unfamiliar with how to get the recovery.img from the zip file. If you can tell me how to extract it or attach one that would be great!

lmaohelp said:
I do, but I'm unfamiliar with how to get the recovery.img from the zip file. If you can tell me how to extract it or attach one that would be great!
Click to expand...
Click to collapse
Actually, flashing it should replace twrp with stock one didn't it?
You can extract it with 7zip. It worked for me.

Venkata Lochan Nune said:
Actuall, flashing it should replace twrp with stock one didn't it?
You can extract it with 7zip. It worked for me
Click to expand...
Click to collapse
What do you mean by flashing it, the update file? I updated from EMUI 5 to EMUI 8 using a update.zip file and HWOTA method so I am not sure if that is the same thing as just flashing the update.zip file. Also, just extracting the files doesn't produce anything useful. I used a firmware extractor from this thread, which comes up with the files shown in the screenshot. Now I'm not sure which file is the stock recovery image. I also tried flashing Magisk for root access and using Flashify to backup the stock recovery image, but the app would just freeze, I'm not sure why.

lmaohelp said:
What do you mean by flashing it, the update file? I updated from EMUI 5 to EMUI 8 using a update.zip file and HWOTA method so I am not sure if that is the same thing as just flashing the update.zip file. Also, just extracting the files doesn't produce anything useful. I used a firmware extractor from this thread, which comes up with the files shown in the screenshot. Now I'm not sure which file is the stock recovery image. I also tried flashing Magisk for root access and using Flashify to backup the stock recovery image, but the app would just freeze, I'm not sure why.
Click to expand...
Click to collapse
Well you could directly flash update.zip with twrp.
Wail I'll attach it in a while. Just turned on my PC to search for it and this bloody "working on updates" came up.

lmaohelp said:
What do you mean by flashing it, the update file? I updated from EMUI 5 to EMUI 8 using a update.zip file and HWOTA method so I am not sure if that is the same thing as just flashing the update.zip file. Also, just extracting the files doesn't produce anything useful. I used a firmware extractor from this thread, which comes up with the files shown in the screenshot. Now I'm not sure which file is the stock recovery image. I also tried flashing Magisk for root access and using Flashify to backup the stock recovery image, but the app would just freeze, I'm not sure why.
Click to expand...
Click to collapse
Yeah I've faced the same problem with flashify and ofcourse other similar apps. The problem I usually get is that system partition isn't writable. After changing it to r/w, I get an error that boot image not found. (This doesn't happen in flashify, it just freezes). Not sure what the problem is maybe, huawei's anti modding measures...

This might be the stock recovery(its in between some 10 other recoveries so, not sure). Try it and inform me
EDIT : THIS IS NOT THE RIGHT ONE. STOCK RECOVERY WAS ATTACHED IN POST #1.

Venkata Lochan Nune said:
This might be the stock recovery(its in between some 10 other recoveries so, not sure). Try it and inform me.
Click to expand...
Click to collapse
I don't think that is the correct file, as I flashed it and "adb reboot recovery" just causes it to be stuck on the "your phone is unlocked" screen, and so does clicking the factory reset option in eRecovery. I tried extracting the RECOVERY_RAMDIS(K).img file and flashing it, which worked, and successfully failed (lol) to reset the phone.
EDIT: I got into the OS successfully. It is unexpectedly smooth, good job!

lmaohelp said:
I don't think that is the correct file, as I flashed it and "adb reboot recovery" just causes it to be stuck on the "your phone is unlocked" screen, and so does clicking the factory reset option in eRecovery. I tried extracting the RECOVERY_RAMDIS(K).img file and flashing it, which worked, and successfully failed (lol) to reset the phone.
EDIT: I got into the OS successfully. It is unexpectedly smooth, good job!
Click to expand...
Click to collapse
So you liked it?
And hey, attach the stock recovery for future reference if someone needs it.
Use the camera patch to fix cam and flashlight issues. It just replaces the libraries. Flash any emui 8 compatible twrp with fastboot. Take a migrate backup in case.
Google Camera GO app works like a charm and is better than the stock one so I recommended using it.
Enjoy your phone!