Database Info

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

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

TEST SM-G950F Downgrade Android Pie 9.0 U5 XEU to Android Oreo 8.0 U5 XEU with TWRP

Iam happy to get a second SM-G950F so i could try out some testst.
With the second one I try the Update to Android Pie 9.0 U5, yes i know now that i better go only to U4 but **** happens.
I could not Downgrade the Pie 9.0 U5 to any Oreo 8.0 U4 so i try to test with my first G950F what still have the Oreo 8.0 U4.
I make backups from the Partitions with TWRP, copy the Partitions to my SD-Card put the Card in the second G950F and recover only 4 Partitions, and it works. I getr an SM-G950F Oreo 8.0 U5 (On the EFS and Baseband from the Pie 9.0 U5)
{
"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"
}
If anyone like to test it, only on your Own risk!! Here is all you Need!!
In order iam new here i could not post any link but if you need the files send me an pm and i send you the links.
SM-G950F Downgrade Android Pie 9.0 U5 XEU to Android Oreo 8.0 U5 XEU with TWRP Partition Backup (Untouched EFS & Baseband)
## Based on an TWRP-G950F-PHN-Oreo-U4 Partition Backup
## and TWRP-G950F-DBT-Oreo-U5_&_Pie-U5 Partition Backup
## FW G950FXXU4CRI5-v8_U4_PHN and G950FXXS5DSJ1-v9_U5_DBT
-* All what you do now is on your OWN RISK *-
-* Know that you can Crash/Brick your Mobile *-
## Included Partitions ##
# Boot
# Recovery
# System
# Data
## What we need?
+32GB SDHC Card
# Windows Software (Latest Versions)
# Samsung Smart Switch
# Samsung Odin3
# Android Software (Latest Versions)
# TWRP as flashable dreamlte.img.tar
# TWRP as APK
# SuperSU as flashable zip
# SuperSU as APK
# SM-G950F-XEU-v8.0_TWRP_Stok_Factory_Reset_Partition_Backup
1. Make a Full-Backup from your Data via SmartSwitch on your PC.
2. Is the latest TWRP Version installed?
Than go to the TWRP Recovery Mode (Bixbi+VolUp+PWR), go to
"Save" mark all Partitions and swipe to save a compleate Partition Backup from your running Android Version to could Backup if its Crashed.
Wait til the Backup is finished and go Back to the MainMenu in TWRP.
3. Connect your Mobile to your PC and go to the following Folder
"\YourPC\Galaxy S8\Micro SD-Card\TWRP\Backups".
Inside here is the Folder with your Original Backup.
Move the Folder "2019-00-00--R16NWG950F....." to your PC.
4. Download your favorite "XEU-v8.0_TWRP_Stok_Factory_Reset_Partition_Backup"
extract the file on your PC, copy the Folder to your SD-Card
"\YourPC\Galaxy S8\Micro SD-Card\TWRP\Backups".
5. Copy the latest Version of SuperSu to your SD-Card
"\YourPC\Galaxy S8\Micro SD-Card".
6. Go in TWRP on "Recover", in normal case the backup would found automaticly.
Chose/Mark all of the 4 Partitions and swipe to Recover them.
7. If the installation is finished, swipe to restart the System.
### First Boot Take some Time !!!
### Hang on Logo with Blue LED !! WAIT !!
### Could take more than 5 minutes !!
8. If the first Boot is Finished you get an fresh Factory-Resetted S8 with Android 8.0 Oreo and TWRP-Boot but non Root. So you have to make all the steps... Developer Mode, SuperSU install via TWRP and APK and TWRP APK instal to Root it again!
9. Now you could also play your Backup back to your Phone with SmartSwitch and go back on work with your Data!
Finished, enjoy your Downgraded S8 Oreo with the Pie Baseband
In order iam new here i could not post any link but if you need the files send me an pm and i send you the links.

I need help>>>sim card is not recognizing on my s8g950f
Sorry but this doesnt has nothing to do with this post but i have a s8 g950f with a anroid pie 9.0 wit binary v6 and its not recognizing the sim card i already have been in others pi versions like the one with binary 5/4/3/2/1 but none of them worked for me so a tought that updating to binary 6 would fix but it was the same..... But when i was on andorid 8 it recognized my sim card it was running normal so i managed to f**k up everything so i dont know what to do... I have already tried to do a downgrade but, ended up with no sucess cause of the binarys rules i have to find a andoid 8 with the same binary version to use and android 8 finishes in binary 4. So i cant do a downgrade... I was hoping that someone could help me..... I didnt try do downgrade unsing twrp cause i coudnt find a 8.0 fiwmware via twrp but im searching fot it....so plz does anyone know how to fix this issue...............plz.p-lz.plz. And sorry for my horrible english thats not my native language....

Is it possible to go further? I mean back to nougat?

Joia01 said:
Sorry but this doesnt has nothing to do with this post but i have a s8 g950f with a anroid pie 9.0 wit binary v6 and its not recognizing the sim card i already have been in others pi versions like the one with binary 5/4/3/2/1 but none of them worked for me so a tought that updating to binary 6 would fix but it was the same..... But when i was on andorid 8 it recognized my sim card it was running normal so i managed to f**k up everything so i dont know what to do... I have already tried to do a downgrade but, ended up with no sucess cause of the binarys rules i have to find a andoid 8 with the same binary version to use and android 8 finishes in binary 4. So i cant do a downgrade... I was hoping that someone could help me..... I didnt try do downgrade unsing twrp cause i coudnt find a 8.0 fiwmware via twrp but im searching fot it....so plz does anyone know how to fix this issue...............plz.p-lz.plz. And sorry for my horrible english thats not my native language....
Click to expand...
Click to collapse
It may be that they used a eng.boot to sim unlock it while the updates erased it and relocked your device. As far as flashing non official binaries on pie firmware is beyond my knowledge.

BossBGM said:
Is it possible to go further? I mean back to nougat?
Click to expand...
Click to collapse
if you have one working SM-G950G running an nougat and you rooted it with TWRP than i think its possible, but i only could down to #2018-10 #8.0.0 #G950FXXU4CRJ5 thats the oldest version on on of the two phones and i could not downgrade more without a phone with an working clean version of any earlyer version.
so i think it could if you have a source phone ... but anytime on own risk!

Joia01 said:
Sorry but this doesnt has nothing to do with this post but i have a s8 g950f with a anroid pie 9.0 wit binary v6 and its not recognizing the sim card i already have been in others pi versions like the one with binary 5/4/3/2/1 but none of them worked for me so a tought that updating to binary 6 would fix but it was the same..... But when i was on andorid 8 it recognized my sim card it was running normal so i managed to f**k up everything so i dont know what to do... I have already tried to do a downgrade but, ended up with no sucess cause of the binarys rules i have to find a andoid 8 with the same binary version to use and android 8 finishes in binary 4. So i cant do a downgrade... I was hoping that someone could help me..... I didnt try do downgrade unsing twrp cause i coudnt find a 8.0 fiwmware via twrp but im searching fot it....so plz does anyone know how to fix this issue...............plz.p-lz.plz. And sorry for my horrible english thats not my native language....
Click to expand...
Click to collapse
you could try the latest Android8 Binary v5 backup from me to make a Android 8 running on Binary 6 on own risk! but if the problem is the Binary i think it wouldn´t help. and you dont could downgrade the Binary.

I don't understand the purpose of the file:
2019-01--R16NWG950FXXS4CSB1-XEU-v8.0_TWRP_Stok_Factory_Reset_Partition_Backup
1. Do I need to use this?
2. Can I just copy the partitions from the donor backup?
Thanks!
---------- Post added at 07:21 PM ---------- Previous post was at 06:58 PM ----------
Also, which partitions do I need to restore? (System, Data, boot, cache -- is that right?)
Thanks!

Hi There,
the file "2019-01--R16NWG950FXXS4CSB1-XEU-v8.0_TWRP_Stok_Factory_Reset_Partition_Backup" is the last Android 8 clean TWRP-Backup without the partitions for EFS & Baseband.
1. So yes if zou would downgrade your S8 with Android 9 to Android 8 you need this files.
You could find all informations at this txt file hxxps://doonuts.stackstorage.com/s/bS1wpjuERB5FRgd.
2. You Can Copy the Partitions "System, Data, Boot, Cache" to Restore the Partitions. (WITH TWRP)
scuba1999 said:
I don't understand the purpose of the file:
2019-01--R16NWG950FXXS4CSB1-XEU-v8.0_TWRP_Stok_Factory_Reset_Partition_Backup
1. Do I need to use this?
2. Can I just copy the partitions from the donor backup?
Thanks!
---------- Post added at 07:21 PM ---------- Previous post was at 06:58 PM ----------
Also, which partitions do I need to restore? (System, Data, boot, cache -- is that right?)
Thanks!
Click to expand...
Click to collapse

Ok friends. Hopefully this doesn't jinx it, but I followed Doonuts guide, and it looks like it worked (so far, please say a prayer it persists).
My motivation was to downgrade from Pie, and I wasted 3 full days on combination file efforts, thanks to this seductive post
https://forum.xda-developers.com/galaxy-s8/help/method-to-downgrade-galaxy-s8-to-oreo-t3946240
.. but I am not expert.
The combination file efforts were unsuccessful. I tried to downgrade from Android 9 on this stock ROM, from new sealed purchased S8 G950FXXU5DSFB _CSC G950FXOXM5DSFB to oreo using this COMBINATION_FA70_G950FXXU5ASF1_CL12792727_QB24208030_REV00_user_mid_noship.tar .
Without dwelling on that further, I can report that following Doonuts instructions worked, except that instead of using his suggested backup firmware, I restored the backup I made of my existing running G950F (which was on bootloader U2). I restored Boot, System, Cache and Data from a TWRP backup.
So I now have Android 8.0 running on a new S8 with the S5 bootloader (it came with Android 9). Received 2 force closes that happen after each reboot (3 boots so far). Otherwise, phone call worked. Will report any other probs.
I'm attaching screenshots of the software / baseband and errors. Let me know any questions, as I'd like to be helpful.
---------- Post added at 02:58 AM ---------- Previous post was at 02:54 AM ----------
Errors:
---------- Post added at 03:00 AM ---------- Previous post was at 02:58 AM ----------
1. Make a Full-Backup from your Data via SmartSwitch on your PC.
2. Is the latest TWRP Version installed?
Than go to the TWRP Recovery Mode (Bixbi+VolUp+PWR), go to
"Save" mark all Partitions and swipe to save a compleate Partition Backup from your running Android Version to could Backup if its Crashed.
Wait til the Backup is finished and go Back to the MainMenu in TWRP.
3. Connect your RUNNING Mobile to your PC and go to the following Folder
"\YourPC\Galaxy S8\Micro SD-Card\TWRP\Backups".
Inside here is the Folder with your Original Backup.
Move the Folder "2019-00-00--R16NWG950F....." to your PC.
4. Download your favorite "XEU-v8.0_TWRP_Stok_Factory_Reset_Partition_Backup"
extract the file on your PC, copy the Folder to your SD-Card
"\YourPC\Galaxy S8\Micro SD-Card\TWRP\Backups".
5. Copy the latest Version of SuperSu to your SD-Card
"\YourPC\Galaxy S8\Micro SD-Card".
6. IN NEW MOBILE, Go in TWRP on "Recover", in normal case the backup would found automaticly.
Chose/Mark all of the 4 Partitions OF THE BACKUP (FROM RUNNING MOBILE SOURCE) and swipe to Recover them.
7. If the installation is finished, swipe to restart the System.

Does anyone more experienced have any thoughts on this method? I've done a lot of searching on XDA over the years and am very surprised that'd I hadn't come across something like this, given how easy it was.
My build is still working. Still getting the FC's mentioned above, but working without any issues.

Ok-- it looks like Bluetooth will not start on the phone with the pie baseband and oreo system. I tried installing the oreo version of the Bluetooth app, and kept getting an "unable to parse package" error, even after editing the minimum sdk version and making it a system app. Probably giving up at this point on downgrading my Pie galaxy S8's. If anyone reads this, please let me know:
1. Is it possible to purchase a galaxy S8 that is still running Oreo (I tried and failed on Ebay-- the two I bought (sealed) were running U5 of bootloader on Pie out of the box)?
2. Is it possible to achieve root on a Pie S8 with v5 of bootloader?
(these are questions I've failed at finding by searching)
Thx

Oukitel WP5

This is a great rugged phone, perfect for the outdoors (I'm a keen mountaineer). I couldn't see a thread so I thought I would start one! A couple of posts re. rooting to follow....

Hey @dwastell, I know this thread is a couple months old, so I wanted to see if you have any root instructions?
Do you think the process for rooting the OUKITEL K13 here on the forum will work on the WP5?

Rooted!
Hi all,
I rooted my WP5. Sorry for not having time to write a full tutorial, only a concise story. Of course this is ONLY for experienced users...
My phone is 4GB version Android 10, build 10.0_V02_20200508.
1) download the firmware from oukitel website: https://oukitel.com/pages/download-center (1)
2) download and install SP Flash Tools https://spflashtool.com/download/
3) download and install Android Platform Tools https://developer.android.com/studio/releases/platform-tools
4) connect the phone to PC and verify that adb is working
5) WARNING: make a backup af your data!
6) unlock the bootloader:
- in Developer options enable the unlock
- adb reboot bootloader
- fastboot flashing unlock
- fastboot reboot
Now the phone restarts and is completely virgin!
7) shutdown the phone.
8) using SP Flash Tools readback the following partitions:
- boot
- recovery (2)
- vbmeta
9) download the attached patched_vbmeta.img
10) transfer the boot.img that you just readback to the phone download folder
11) install Magisk Manager (today 7.5.1)
12) Use Magisk Manager to patch the boot.img and copy back to PC
13) flash the images:
- fastboot flash --disable-verification vbmeta patched_vbmeta.img
- fastboot flash boot magisk_patched.img
- fastboot reboot
14) if the phone boots up run Magisk Manager to check if it's installed.
14b) if the phone goes in bootloop... flash back the original images you have read back (do not use the firmware you downloaded from Oukitel, it's necessary only to have the scatter file (the partition table).
Enjoy
Nicola
Notes:
(1) actually there are 2 firmware available and despite having different names are the same. This fw is Android 9.
(2) not used now but may be useful in the future

Rooting the WP5
totallybeachin said:
Hey @dwastell, I know this thread is a couple months old, so I wanted to see if you have any root instructions?
Do you think the process for rooting the OUKITEL K13 here on the forum will work on the WP5?
Click to expand...
Click to collapse
I eventually succeeded in rooting my WP5 with Magisk. For a while, the firmware was not available but once the official ROM was published, I managed to patch boot.img and install via fastboot. My phone is the 4 GB version -copies of the stock and patched boot image are available at: github.com/dwastell/Oukitel_WP5_magisk
I have experienced some complications as detailed in my next post...
Cheers, Dave

Rooting the WP5
Thanks for your post Nicola. You'll see that I did succeed in rooting my phone (Android 9) with Magisk, once I was able to get hold of the stock firmware. All is working though there are a couple of points worth noting.
The phones is SAR ("system-as-root") and the magisk instructions suggest that recovery.img is patched rather than boot.img. I proceeded by patching boot.img, as in your instructions, as this seemed a better solution - and it works fine.
One problem has occurred with updates. Magisk manager appears to assume that the recovery partition is the one that has been patched. When you do the direct install for the update, partition 2 is flashed (recovery) rather than partition 26 (boot). On rebooting the phone inevitably goes into boot loop.
To avoid this, I go for "select and patch a file" option, and then install again via fastboot as per the original installation. A bit of a hassle but better than the alternative!

Does this mean you were able to root the phone but revert to android 9? Both of you mention Android 9 in your posts.

vivekiny2k said:
Does this mean you were able to root the phone but revert to android 9? Both of you mention Android 9 in your posts.
Click to expand...
Click to collapse
No. No need to revert.
I rooted an Android 10. But cited the stock Android 9 only because the scatter file (ie. the partition table) is the same.
@dwastell rooted the Android 9.
Please read better my tutorial, if something is not clear... I'm here!
N
---------- Post added at 20:10 ---------- Previous post was at 19:59 ----------
dwastell said:
The phones is SAR ("system-as-root") and the magisk instructions suggest that recovery.img is patched rather than boot.img. I proceeded by patching boot.img, as in your instructions, as this seemed a better solution - and it works fine.
Click to expand...
Click to collapse
This phone is NOT a SAR. Neither Android 9 nor 10. The proof is that patching the boot.img worked!
One problem has occurred with updates.
Click to expand...
Click to collapse
Have you unrooted before applying the update?
Which kind of update? Not all are the same!

Android version
vivekiny2k said:
Does this mean you were able to root the phone but revert to android 9? Both of you mention Android 9 in your posts.
Click to expand...
Click to collapse
My phone was originally Android 9 so no reversion...

SAR
Both "Treble Check" and "Magisk Manager" confirm that the phone is SAR. I agree this is odd.... your thoughts?
The update I was referring to is the Magisk update, handled by Magisk Manager. Given that the phone is seen as SAR, it attempts to patch recovery.img, with an ensueing boot loop.
No, I don't unroot the phone
nicolap8 said:
No. No need to revert.
I rooted an Android 10. But cited the stock Android 9 only because the scatter file (ie. the partition table) is the same.
@dwastell rooted the Android 9.
Please read better my tutorial, if something is not clear... I'm here!
N
---------- Post added at 20:10 ---------- Previous post was at 19:59 ----------
This phone is NOT a SAR. Neither Android 9 nor 10. The proof is that patching the boot.img worked!
Have you unrooted before applying the update?
Which kind of update? Not all are the same!
Click to expand...
Click to collapse

Thanks Nicola for your tutorial. I'm eager to root my WP5 Pro with Magisk, but first I need a backup of boot vbmeta and recovery. I have made extensive use of SP Flash Tools but never to readback partitions so I'm having some problems here. Could you please detail your technique to extract such files? Thank you
Michele
Build number OUKITEL_WP5Pro_EEA_V01-20200624 CPU MT6762D, 8 cores,64 Gb ROM, 4 Gb RAM.

wallace108 said:
Thanks Nicola for your tutorial. I'm eager to root my WP5 Pro with Magisk, but first I need a backup of boot vbmeta and recovery. I have made extensive use of SP Flash Tools but never to readback partitions so I'm having some problems here. Could you please detail your technique to extract such files? Thank you
Michele
Build number OUKITEL_WP5Pro_EEA_V01-20200624 CPU MT6762D, 8 cores,64 Gb ROM, 4 Gb RAM.
Click to expand...
Click to collapse
Beware: your phone is different! So I don't know:
1) Android version.
2) which kind of booting are using, read here https://topjohnwu.github.io/Magisk/install.html#knowing-your-device
Before writing an image you MUST have a backup of it!
To read back a partition with SP Flash Tools you need to know the start address end the length of the partition. This information is available only (because your phone is not yet rooted) from the scatter file (from the SAME phone).
In the Readback page hit "Add" then input a name for the image file. Follows a new dialog "Readback block start address" where you have to write the values.
After this you can give the Read Back command. If it doesn't start shutdown the phone.
N

Thank you all for
the data to root! I just got a 4/32 android 10 version. Is there a custom recovery yet? Been a looooong time since I have dabbled but want to root it and customise. I have replaced most of google apps or disabled them already but want more room. I have never created a TWRP but have been reading about it and they already have many Oukitel versions, so should I wait? TIA

Thanks, it's clear.
I bought it for my son, don't have plans to root it yet. will probably wait till later.
nicolap8 said:
No. No need to revert.
I rooted an Android 10. But cited the stock Android 9 only because the scatter file (ie. the partition table) is the same.
@dwastell rooted the Android 9.
Please read better my tutorial, if something is not clear... I'm here!
Click to expand...
Click to collapse

No Joy with
Hardware : MT6761V/WE
Model : WP5
Build number : OUKITEL_WP5_NOEEA_V01_20200701
Build date UTC : 20200701-071441
Android v : 10
Baseband v: MOLY.LR12A.R3.MP.V114.9,MOLY.LR12A.R3.MP.V114.9
Kernel v : 4.9.190+ ([email protected]) (Android (5484270 based on r353983c) clang version 9.0.3 (based on LLVM 9.0.3svn)) #2 SMP Wed Jul 1 15:19:21 CST 2020
It seems locked down as I lose adb in fastboot and even patching the boot.img I create fails. MTKdroid tools can't create scatter.

vivekiny2k said:
I bought it for my son, don't have plans to root it yet. will probably wait till later.
Click to expand...
Click to collapse
Remember that you will lose ALL YOUR DATA! Usually it's better to root before start using the phone...
oncouch1 said:
No Joy with
Build number : OUKITEL_WP5_NOEEA_V01_20200701
It seems locked down as I lose adb in fastboot and even patching the boot.img I create fails. MTKdroid tools can't create scatter.
Click to expand...
Click to collapse
You have to describe well what you have done and error messages.
Note also that your firmware is never... maybe there is some difference.
N

As of today the firmware for the WP5 PRO has not been posted yet. I'll wait. Meanwhile I want to ask Nicolap8: what does the vbmeta file do? Why is it important to patch it. Isn't patching the boot enough? Thanks

TWRP for WP5 (Pie, 4GB)
If anyone wants to install TWRP, I've built and tested it for my WP5 (Android 9.0, 4GB). A copy of the image may be found in the MISC folder at: https://github.com/dwastell/TWRP_Oukitel_WP5
Note that the data partitiion is not accessible due to encryption (not a major limitation), and that the null version of vbmeta (thanks Nicola) does need to be flashed. Also, I have had problems flashing some versions of Magisk - please read the README.md.

nicolap8 said:
Remember that you will lose ALL YOUR DATA! Usually it's better to root before start using the phone...
You have to describe well what you have done and error messages.
Note also that your firmware is never... maybe there is some difference.
N
Click to expand...
Click to collapse
Sorry it has been a while I HAD WRONG USB DRIVERS! I got bootloader unlocked and will try again.
---------- Post added at 07:13 PM ---------- Previous post was at 07:09 PM ----------
A WP5 (android 10) .zip file is now on the site. It contains less files though?

For some reason the images taken in windows are corrupt. Magical fails to run on them. The one taken in llinux patches fine. One question though the original image is 32 meg the magical patches is only 10 meg is that correct? Also the vbmeta is 8 meg off the phone but the patches 256 k?

oncouch1 said:
For some reason the images taken in windows are corrupt. Magical fails to run on them. The one taken in llinux patches fine.
Click to expand...
Click to collapse
Strange but... with W all is possible!
One question though the original image is 32 meg the magical patches is only 10 meg is that correct? Also the vbmeta is 8 meg off the phone but the patches 256 k?
Click to expand...
Click to collapse
Both are correct.
The Magisk patched image is not "filled" to the partition size.
The vbmeta also is smaller because it's empty (is present only the "index").
N

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