Database Info

[ROM][SGH-S730M] Stock deodexed + rooted + overclocked

This is a DEV thread, this is not yet working
This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.
Instructions:
1. reboot into cwm / twrp, whichever you use
2. full wipe (do not come with issues if you dirty flashed)
3. install zip.
4. Enjoy!
Download link:
Stock deodexed + rooted + overclocked

problem
Ok, i try to instal this rom but i am unable to install it. I have downloaded the file that you put in link. My device is rooted. I boot my device with vol+ and power button. I wipe data/factory reset. Then i reboot normally(reboot system now). After, i put the file in the phone file(usb debogging), but not in a specify directory. I redo the operation of booting with vol+ and power button. I try apply update from external storage...but it doesnt works. So i rename the file, update.zip. And redo booting. But it doesnt work. So i dont know what to do. You specify a method ( reboot into cwm...), but i dont know how to do it. So...

problem
Restl3ss said:
This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.
Instructions:
1. reboot into cwm / twrp, whichever you use
2. full wipe (do not come with issues if you dirty flashed)
3. install zip.
4. Enjoy!
Download link:
[/URL]
Click to expand...
Click to collapse
Ok, i try to instal this rom but i am unable to install it. I have downloaded the file that you put in link. My device is rooted. I boot my device with vol+ and power button. I wipe data/factory reset. Then i reboot normally(reboot system now). After, i put the file in the phone file(usb debogging), but not in a specify directory. I redo the operation of booting with vol+ and power button. I try apply update from external storage...but it doesnt works. So i rename the file, update.zip. And redo booting. But it doesnt work. So i dont know what to do. You specify a method ( reboot into cwm...), but i dont know how to do it. So...

E signature verification keeps failing

bil4554lel said:
Ok, i try to instal this rom but i am unable to install it. I have downloaded the file that you put in link. My device is rooted. I boot my device with vol+ and power button. I wipe data/factory reset. Then i reboot normally(reboot system now). After, i put the file in the phone file(usb debogging), but not in a specify directory. I redo the operation of booting with vol+ and power button. I try apply update from external storage...but it doesnt works. So i rename the file, update.zip. And redo booting. But it doesnt work. So i dont know what to do. You specify a method ( reboot into cwm...), but i dont know how to do it. So...
Click to expand...
Click to collapse
Not sure, haven't tried to install this yet, BUT when in recovery, given you have a custom recovery installed, you shouldn't be trying to "apply update from zip" you should be selecting "install from zip". If you are using a stock recovery, you won't be able to flash a ROM. You need to flash a custom recovery such as twrp or cwm using Odin from a PC.
---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------
Restl3ss said:
This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.
Instructions:
1. reboot into cwm / twrp, whichever you use
2. full wipe (do not come with issues if you dirty flashed)
3. install zip.
4. Enjoy!
Download link:
Stock deodexed + rooted + overclocked
Click to expand...
Click to collapse
I have this old gem of a phone and have been looking forever for a custom ROM. Don't know where you pulled the stock from as I've been trying to dump it off the phone unsuccessfully to mod with Android kitchen. I'll flash this and update with my results

I get
Code:
E: Error in /sdcard/STOCK-overclocked-deodexed-rooted-S730m.zip (Status 255)
Installation aborted.
Using CWM 6.0.2.8

atmu5fear said:
I get
Code:
E: Error in /sdcard/STOCK-overclocked-deodexed-rooted-S730m.zip (Status 255)
Installation aborted.
Using CWM 6.0.2.8
Click to expand...
Click to collapse
Hi, i get too the same error. I used CWM 6.0.3.1
What we can do it for help you and stabilize ROM ?

Bibounet said:
Hi, i get it too, and same error. I used CWM 6.0.3.1
What we can do it for help you and stabilize ROM ?
Click to expand...
Click to collapse
I'm definitely interested in developing a custom ROM for this phone. I bought this phone nearly two years ago, and although I have since upgraded, I seem to always have use it as a back up when my t989 has issues. I know there is a ton of demand for a custom ROM for this phone. I was reading a bunch about META-INF folders and Android kitchen for developing a ROM without having a current base to work with. I'll look into it a bunch more throughout the week, this weekend etc. See if I can get a flashable zip after deodexing and overclocking using the thread the OP of this one used. I read on another forum, after googling "cwm status 255" that this has to do with the updated-binary file in the META-INF folder. The suggestion that worked for the op of that thread was to take the updated-binary file from another flashable zip (for the same phone) and use it to replace the updated-binary file in the zip giving the 255 error. So I took the file from the deodexing zip for this phone and replaced it, not expecting it work, but just to see. Cwm no longer gives the 255 code, but still aborts the installation, with no code given. So it seems this very well could be a start.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

Restl3ss said:
This is a stock ROM for the Samsung Galaxy Discover SGH-S730M in flashable zip format. This ROM has exactly 4 modifications; it's rooted, it's deodexed, it's overclocked to 1 ghz, and it has busybox installed. Other than that this ROM is completely stock. Even so, I welcome you to the first available ROM for the samsung galaxy discover to my knowledge. Hopefully this will encourage others to make their own custom ROMs for this device, as this ROM is now here as a base for anyone who wants to use it. Flashing instructions and download link below.
Instructions:
1. reboot into cwm / twrp, whichever you use
2. full wipe (do not come with issues if you dirty flashed)
3. install zip.
4. Enjoy!
Download link:
Stock deodexed + rooted + overclocked
Click to expand...
Click to collapse
Did you pull your META-INF folder from this thread
I'm thinking the ARM binary is different from x86, so the updater-binary file is what's causing the problem

atmu5fear said:
Did you pull your META-INF folder from this thread
I'm thinking the ARM binary is different from x86, so the updater-binary file is what's causing the problem
Click to expand...
Click to collapse
That may very well be it, I'm gonna change it and reupload
Check back in a bit. Appreciate the help

I used the same meta-inf that I use for my tab 3 10.1 work, I just changed the partition table to fit this phone. I never really thought about the x86 vs arm argument, may definitely play a role

I just threw together a flashable zip of this rom quickly on android kitchen. I used the META-INF folder from the thread I previously linked to. It's been deodexed and rooted, but I didn't bother with the overclock. Once we can get a flashable zip that works, i figure we'll go from there. I'm going to flash it to the phone now, and see if it will complete and boot.
I'm getting a status 0 error code. I'm going to rebuild without converting to edify. Will update

Hi Restl3sss, can you doing new ROM without overclock, it's more safe. And it's possible used tools later (ex: No-Frills CPU control) for try overclock if people want live dangerously . ty for your great work.

Bibounet said:
Hi Restl3sss, can you doing new ROM without overclock, it's more safe. And it's possible used tools later (ex: No-Frills CPU control) for try overclock if people want live dangerously . ty for your great work.
Click to expand...
Click to collapse
The overclock is built into the kernel, clocks it from 800mhz to 1000mhz, any one who wants to run it without the higher clock, can just use any CPU control app and set the max to 800.
Without modding the kernel you actually can't overclock past 800mhz using any CPU control app.
---------- Post added at 03:28 AM ---------- Previous post was at 03:20 AM ----------
Restl3ss said:
I used the same meta-inf that I use for my tab 3 10.1 work, I just changed the partition table to fit this phone. I never really thought about the x86 vs arm argument, may definitely play a role
Click to expand...
Click to collapse
The Tab 3 runs on intel and the discover runs on ARM.
From everything I can find this is definitely the problem. Although just replacing the binary itself, and rebuilding hasn't seemed to accomplish anything other than no longer giving the error code. Just aborts. I've read your updater-script and none of the ui messages show up or anything from within that script during install.

@Restl3ss I swapped out the binary from another flashable zip for the same phone, from within the kitchen using your flashable zip. Kept your updater script and other than that the only other change was I zipaligned. I rebuilt it, flashed it. The install doesn't abort, and completed. But none of your ui code from script appears during install, and nothing actually installed to the phone, it just boots straight into recovery. Since I have no idea how to decipher what I'm reading in the binary using notepad++, I'll leave it to your expertise to sort out the rest. I'm only just getting into this developing bit and so far have reached my limit of what I can help you with, as far as getting a base to flash and install successfully. I tried to get a report using adb logcat after it kept booting into recovery but the log remained empty.
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

just tried it now with the files in the OP and got "E:Error in /sdcard/STOCK-overclocked-deodexed-rooted-s730M.zip (Status 255)
Installation aborted."

Joel-Tang said:
just tried it now with the files in the OP and got "E:Error in /sdcard/STOCK-overclocked-deodexed-rooted-s730M.zip (Status 255)
Installation aborted."
Click to expand...
Click to collapse
x86 binary was used. Solutions are being looked at. I managed to rebuild it with another binary, and it completed the flash, but nothing was successfully moved to the system partition. It's in the works tho
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

atmu5fear said:
x86 binary was used. Solutions are being looked at. I managed to rebuild it with another binary, and it completed the flash, but nothing was successfully moved to the system partition. It's in the works tho
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
do you know if the boot image successfully flashed? if so I might have the partition table wrong for system.
if boot flashed successfully you should be able to set your cpu to 1000 mhz

Restl3ss said:
do you know if the boot image successfully flashed? if so I might have the partition table wrong for system.
if boot flashed successfully you should be able to set your cpu to 1000 mhz
Click to expand...
Click to collapse
I pulled the recovery log using adb, and according to the log, the boot.img flashed. But I'll have to check the phone tmrw. Because it said it completed, I believed it, so to be sure I formatted the system folder and data/cache, re flashed, and nothing installed. Your partition table is right tho. Mmcblk0p8 for boot, p16 for system and p18 for data, it's all what it should be. I'll restore my stock cwm back up tmrw, re flash the zip and see if I can set the clock to 1000mhz. If you want, I'll pull as much info I can from the phone partition table, and pm you. To me it's a mystery as to why it won't boot. I'll send the error log and whatever I can gather as well. If I don't get around to it tmrw, it'll be Thursday night
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app

atmu5fear said:
I pulled the recovery log using adb, and according to the log, the boot.img flashed. But I'll have to check the phone tmrw. Because it said it completed, I believed it, so to be sure I formatted the system folder and data/cache, re flashed, and nothing installed. Your partition table is right tho. Mmcblk0p8 for boot, p16 for system and p18 for data, it's all what it should be. I'll restore my stock cwm back up tmrw, re flash the zip and see if I can set the clock to 1000mhz. If you want, I'll pull as much info I can from the phone partition table, and pm you. To me it's a mystery as to why it won't boot. I'll send the error log and whatever I can gather as well. If I don't get around to it tmrw, it'll be Thursday night
Sent from my SAMSUNG-SGH-T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the more information you can get me the better, thanks a ton for the help

Twrp recovery - 2.8.4.0 Rev -2 - xolo q3000

TWRP RECOVERY - 2.8.4.0 Rev 2- XOLO Q3000 with OTG support​
Procedure to follow
download the recovery.
then flash recovery using sptools /flashify /mobileuncle tool using these guides.
OR
if ur using any custom recovery from this thread then
visit this thread to get a flashable recovery which can be flashed from current recovery.
Just reboot to recovery for confirmation.
This is working recovery - tested by me.
flashed JB & KK rom.
Backup and restore without any issues.
OTG is also working properly - FAT/FAT32 formatted USB drives only.
As u all know our device has 6mb recovery partition size.
So while porting i need to trim the actual recovery.
U will not be able to partition ur sd card using this recovery.
Also u wont be able to root using this recovery.
For above issues we have better solutions.
Try and report.
​
For official change logs, see here:
http://teamw.in/project/twrp2
Credits:-
needrom for base recovery.
@z31s1g for TWRP themes.

OTG working normally.

You did it finally...

aaayush_singh said:
You did it finally...
Click to expand...
Click to collapse
Still doing some work on TWRP 2.8.5.0
Almost around 6.12 MB, it has at most tobe 5.99 MB.
Lets see.

avi3230 said:
Still doing some work on TWRP 2.8.5.0.....
Click to expand...
Click to collapse
is twrp v2.8.4.0 rev 2 flashable zip available only in dark theme? how to get the theme shown in the attached pic? will you be releasing other themed zips for twrp v2.8.4.0 rev 2?

m0han said:
is twrp v2.8.4.0 rev 2 flashable zip available only in dark theme? how to get the theme shown in the attached pic? will you be releasing other themed zips for twrp v2.8.4.0 rev 2?
Click to expand...
Click to collapse
Sir all themes working well. i just uploaded dark theme.
u can use rev 1 themes also on rev 2.
working on TWRP 2.8.5.0 so forgot to upload other themes.
u can download from here.
Eventually i increase the action message font and i forgot which ui.xml i used, still searching for it.
TWRP 2.8.5.0 booting but cant flash any ROM but recovery flash, wiping is working normally.
If u can help me with that i can try it.
Thanks.
I would love to see u pressed thanks button sometimes.

just wondering if the rev 2 recovery.img file can be placed inside your TWRP_2.8.2.0_Q3000 play.zip file replacing the twrp v2.8.2.0 recovery.img there.
will flashing that give twrp v2.8.4.0 rev 2 play theme? just a noob-guess! . btw, the ui.zip inside the dark theme zip file of twrp v2.8.4.0 rev 2 is pretty big (8,221,418 bytes).
---------- Post added at 12:57 PM ---------- Previous post was at 12:35 PM ----------
avi3230 said:
....all themes working well......u can download from here.
....i increase the action message font and i forgot which ui.xml i used, still searching for it......
....help me with that i can try it.....would love to see u pressed thanks button sometimes...
Click to expand...
Click to collapse
xolo q3k is not with me. i posted that i've changed my device. so, i don't think i can help you much.
but, when i see some solid work, i hope to get the xolo q3k for testing for a short period.
you know that i've lent you much positive-critical support. and i owe you a lot for helping me in toubled times.
please get that ui.xml and increase the action message font for this rev 2 as well as all your future releases. :good:
p.s.: i see you're doing great. recognised contributor! keep it up! :highfive:
btw, you seem to be in a rush to get to the next level.

waiting for response
m0han said:
....if the rev 2 recovery.img file can be placed inside your TWRP_2.8.2.0_Q3000 play.zip file replacing the twrp v2.8.2.0 recovery.img there.
will flashing that give twrp v2.8.4.0 rev 2 play theme?.... the ui.zip inside the dark theme zip file of twrp v2.8.4.0 rev 2 is ....8,221,418 bytes....
..please get that ui.xml and increase the action message font for this rev 2 as well as all your future releases......
Click to expand...
Click to collapse
@avi3230, expecting you to respond. i checked out your link; but, not sure how to use the template(?). suggest you upload the themed zips.

m0han said:
@avi3230, expecting you to respond. i checked out your link; but, not sure how to use the template(?). suggest you upload the themed zips.
Click to expand...
Click to collapse
Sir first flash the recovery with dark theme (flashble zip is attached so u can flash from any recovery)
Download play theme zip from above given link.
Rename this zip to ui.zip.
Now copy and replace in ur
Internal storage/twrp/theme/ folder.
Or replace in dark themed recovery.zip inside
Emmc/twrp/theme. Folder
In both cases u will find ui.zip already there u need to just replace.
I am in transit so cant upload now.
Wil upload after 9 pm only.
Thank you
Sorry for inconvinence.

m0han said:
@avi3230, expecting you to respond. i checked out your link; but, not sure how to use the template(?). suggest you upload the themed zips.
Click to expand...
Click to collapse
here r the flashble zips - also updated on thread of flashble zip
TWRP 2.8.4.0 Rev 2 -------2.8.4.0 rev 2 dark theme-------2.8.4.0 Rev 2 light theme-------2.8.4.0 Rev 2 Play theme

avi3230 said:
here r the flashble zips - also updated on thread of flashble zip.....2.8.4.0 Rev 2 Play theme
Click to expand...
Click to collapse
tried this, and boy, was i in for some shock! think i'll let the screenshots speak for themselves....
TWRP v2.8.4.0 Rev.1 (2) brought woes.
TWRP v2.8.2.0 brought back relief! :good:
mounting usb otg in TWRP v2.8.4.0 Rev.1 (2) is cumbersome. no way to get back to the previous screen after mounting, except by clicking the back key of the device. the back arrow at the top left does not work.
and i couldn't find the usb otg drive listed anywhere (as opposed to the case of TWRP v2.8.2.0, where you see it listed everywhere). others can try this recovery and correct me if i'm wrong.
more importantly, it'd help the dev do things better/properly. (although i took a screenshot it doesn't seem to have worked.) the device is back on 'twrp v2.8.2.0 play edition by avi3230'.
not sure when i can test further, but i'll be willing to help when possible. in the meantime avi3230 can concentrate on quality rather than quantity, imho. thanks, anyway.

@m0han
Yeah u r correct sir.
First its my mistake - as i used the zip of rev 1 and i replaced the zip and not the recovery in flashble zip so u see its rev 1.
U cant see some buttons cause the theme is meant for rev 2.
In each update of TWRP there is change in backup folder (which i cant define) so it wont detect previous backups.
u need to manually move the backup to respective folder when u upgrade.
Dont worry usb otg works properly in rev 2. u need to use back button to go back. I already made a video of that but not uploaded.
This happens because no one has even tested the recovery. There are more than 70 downloads of the img file but no one even reported.
Sorry for the inconvenience caused.
I am also learning by mistake, hope u understand what i am saying.

avi3230 said:
....u r correct.....no one has even tested the recovery. .....more than 70 downloads of the img file but no one even reported.....
Click to expand...
Click to collapse
that's sad. but, i think i know the reason - and i've stated it before. you're dishing out stuff (even partly cooked) in such quick succession that people can't even decide what to go with. i'm sure you yourself don't get time to test your work - you don't have the device with you full-time. and, frankly, the responses to your releases show that your users are not entirely satisfied. if you're keen to do a better/proper job, you may consider my advice suggestion in the proper spirit - "concentrate on quality rather than quantity". i notice that quite a few others have also opined so.
avi3230 said:
....As the number is more there bound to be the issue of repetitiveness and similarities.....
Click to expand...
Click to collapse
also, the issue of errors/bugs.....
lastly, just want to make a subtle observation: although i was the first among 70+users to give you a detailed feedback, which you found 'correct', you haven't 'thanks'ed me. i usually press thanks for work that has benefitted me as well as the user community for any device or some post that throws light on a matter of general/popular interest. so, continue your good work and the thanks will gush forth. just don't keep looking out for it. don't thank me just 'cos i said this; you know i'm not the kind who solicits thanks.

@m0han
Thanks for trying the recovery and pointing out the mistakes.
Links are corrected with proper recovery version.
I am just trying to learn things here nothing else so mistakes will happen from my side, i apologize for it.
I am just trying my level best.
The sad part is users only replay when they are not satisfied.
Right now i cant thank u cause my today's quota of thanks is already over.

avi3230 said:
.....Links are corrected with proper recovery version.....trying to learn things here....trying my level best.....
Click to expand...
Click to collapse
just go easy on releasing and hard on learning. forget thanking me. :good:.
a couple of suggestions:
1. provide md5 checksums. (i got d9e07dfe97cc26795f1f5f374df89ed0 for the latest one.) would help distinguish the various versions, esp. if there's no change of filename
2. please provide screenshots - at least the ones of the troublesome screens, if not exactly like mine.
"in each update of TWRP there is change in backup folder" - are backup location and usb implementation hard-coded in the recovery? i ask again what i asked here: what could happen if the (rev 2) recovery.img file is placed inside your TWRP_2.8.2.0_Q3000 play.zip file replacing the img file there and flashed? will that give me Q3000 backup folder and the usb otg implementation? . these are noob thoughts, but, i await your answer.

hi @avi3230, i've just sent you a pm. please respond. thanks.. posted in (common) recovery collection thread.

md5 mismatch
avi3230 said:
TWRP RECOVERY - 2.8.4.0 Rev 2- XOLO Q3000 with OTG support....
Click to expand...
Click to collapse
the 'TWRP 2.8.4.0 rev 2.img' from this op has md5 c5d180bc6cdde26541421a220e1a37d9.
the 'recovery.img' inside the '2.8.4.0 Rev 2 Play theme' linked to here has md5 c3b809c3081cd04b4a77446fe69db590.
there is a mismatch. which one is the proper fully-working 'TWRP 2.8.4.0 Rev 2'?
@avi3230 / somebody, please confirm which file (img or zip) to use to avoid troubles. thanks.

None of the two files have any trouble.

Using this recovery, it's working fine, thanks ?

[Guide] How to get rid of force encryption/dm-verity on Huawei MediaPad T3 10 (AGS-W0

I was frustrated by the huawei encryption and decided to get rid of it once and for all.
At first I faced many bootloops but i finally figured out what was going on. Formatting user data through TWRP is not enough because after booting the device, encryption is still there. This happens because the kernel encrypts the device when booting up. Simply modifying the boot.img file to remove file encryption also doesn't work because you still boot into an already encrypted stock user data. So the answer was pretty obvious by now.
The trick is to format data using TWRP AND THEN boot to bootloader to flash a modified boot without encryption. So let's get to it.
How to create a modified boot.img without file encryption/dm-verity
1. Find and download your current firmware from Huawei Firmware Finder Dtabase (Team MT), or from a source that you trust. (Using a firmware with different cust version or a different update will most likely not work).
2. Download Huawei Update Extractor and use it to extract the stock boot.img file from UPDATE.APP
3. Download ASSAYYED_KITCHEN.
4. Place your stock boot.img file in the "WORK" folder of ASSAYYED_KITCHEN.
5. Launch ASSAYYED and select the 12th option (KERNEL/RECOVERY MENU) and then the 1st one (Unpacking Kernel).
6. The ASSAYYED options don't work for me so i did it manually. Go to your work folder and open the folder boot_unpacked\ramdisk.
7. You will see a file named "fstab.qcom", open it using WordPad.
8. Find the line:
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check,fileencryption
and delete ",fileencryption".It should now look like that:
Code:
/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,inline_data,inline_xattr wait,check
9. (This step is optional,follow it only if you also want dm-verity removed) Use the same method to remove dm-verity.
Code:
/dev/block/bootdevice/by-name/system /system ext4 ro,barrier=1 wait, verify
/dev/block/bootdevice/by-name/vendor /vendor ext4 ro,barrier=1 wait, verify
/dev/block/bootdevice/by-name/product /product ext4 ro,barrier=1 wait, verify
(Just delete the ",verify" part.)
10. Save the file.
11. Launch ASSAYYED and select the 12th option (KERNEL/RECOVERY MENU) and then the 2nd one (Packing Kernel).
12. Follow the instructions below to properly flash your modified boot.img and get rid of encryption.
Removing file encryption/dm-verity from the device
1. Unlock your device.
2. Flash this TWRP on AGS-W09 or the appropriate custom recovery for your device.
3. Boot to TWRP and FORMAT user data (note that it is very important to format data and not just wipe it). •WARNING• this will delete all your data!
4. Go back to the reboot menu of TWRP and select reboot booloader (it's important to not allow your device to boot into system yet).
5. Using fastboot, flash your modified boot.img that you created earlier.
6. Reboot your device (you might get a bootloop on the first boot but force rebooting your device again by holding the power button will fix that).
7. After booting up, your device should not be encrypted anymore.
8. You can now use the root method that you like to root your device and internal storage should be visible on TWRP. TWRP backup should also work normally.
How to fix Magisk modules not showing up on Magisk Manager (! /data/adb/magisk_merge.img mount failed error)
I am not going to get into the technical staff you can find more info here
Edit: As of Magisk 19.0, the following method becomes obsolete. Magisk modules should now work as expected without issues. This method now concerns those who want to stick to an older version of Magisk
1. Download f2fsfix-2018.9.2.zip provided by VR25 on the thread above.
2. Download all the magisk modules that you need to flash and place them on your device.
3. Download the latest Magisk uninstaller along with the latest installer.
4. Boot to TWRP and flash Magisk uninstaller. (If you don't have Magisk already installed, skip this step)
5. Wipe Davlik Cache.
6. Install the latest Magisk.
7. Wipe Davlik Cache.
8. Flash the "f2fsfix-2018.9.2.zip" immediately followed by your modules.
9. Reboot (it should take more than usual).
10. Open Magisk Manager and check your Modules. Hopefully they'll show as installed and function correctly.
Note: This method should also work on similar devices. Just make sure you know how to recover your device in case something goes wrong.

I can confirm this worked for me. I was able to run a full nandroid, but haven't tried to restore. Wasn't running any magisk modules, so haven't tried that part of the guide. Flashed Xposed in TRWP and installed greenify, etc Seems to be working. So far no errors. Be warned, this is like a restore. You'll be starting from scratch again.
Also thanks for the boot image trick Thanostsak. I couldn't find stock fimware for my version (AGS-L03) anywhere. He suggested to use the Magisk's boot image backup. Worked like a charm. Still looking for AGS-L03 stock if anyone has one, knows where to get one please post!

TRS_80 said:
I can confirm this worked for me. I was able to run a full nandroid, but haven't tried to restore. Wasn't running any magisk modules, so haven't tried that part of the guide. Flashed Xposed in TRWP and installed greenify, etc Seems to be working. So far no errors. Be warned, this is like a restore. You'll be starting from scratch again.
Also thanks for the boot image trick Thanostsak. I couldn't find stock fimware for my version (AGS-L03) anywhere. He suggested to use the Magisk's boot image backup. Worked like a charm. Still looking for AGS-L03 stock if anyone has one, knows where to get one please post!
Click to expand...
Click to collapse
Glad it worked for you. Yes this is the downside. The device already comes with an encrypted userdata, so it needs to be formatted. So anything you do before that becomes obsolete. That's why this procedure is much more convenient when it happens after the unlock,when the userdata is wiped by the stock recovery to get a stock condition.

AGS-L09 LTE
I just followed your detailed guide to my tablet and finished all the processes perfectly.
Working..Twrp, Magisk, removed encryption & verify from boot.img and from Data successfully.
A big THANKS for your guide, links and trick all in one post!!!!.

Thanks for the info.
I am new to android (but have jailbroken iOS for years).
I have received a Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) today.
I have managed to unlock and install TWRP 3.2.1 but also want to install SuperSU, but of course the filesystem is encrypted, which brings me here.
I have searched all over for Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) firmware which contains boot.img but cannot find it. Even the rom on the AGS-W09 thread on this forum doesnt contain the .img file. Am I missing something ?
Any help is appreciated.
Thanks again

mr_fingy said:
Thanks for the info.
I am new to android (but have jailbroken iOS for years).
I have received a Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) today.
I have managed to unlock and install TWRP 3.2.1 but also want to install SuperSU, but of course the filesystem is encrypted, which brings me here.
I have searched all over for Huawei MediaPad T3 AGS-W09 (AGS-W09C100B278) firmware which contains boot.img but cannot find it. Even the rom on the AGS-W09 thread on this forum doesnt contain the .img file. Am I missing something ?
Any help is appreciated.
Thanks again
Click to expand...
Click to collapse
I strongly suggest using Magisk to root your device instead of SuperSU. The good thing about Magisk is that everything happens systemlessly, so it doesn't matter if the kernel is encrypted in order of it to work. If you still want to use SuperSU though, my guide should provide all the info you need.
To answer your question you can find two OTA firmware updates for your device here. If that doesn't work (if the OTA updates don't include the boot.img file ) i will let you know how to use magisk to get a copy of your current boot.img

Thanostsak said:
I strongly suggest using Magisk to root your device instead of SuperSU. The good thing about Magisk is that everything happens systemlessly, so it doesn't matter if the kernel is encrypted in order of it to work. If you still want to use SuperSU though, my guide should provide all the info you need.
To answer your question you can find two OTA firmware updates for your device . If that doesn't work (if the OTA updates don't include the boot.img file ) i will let you know how to use magisk to get a copy of your current boot.img
Click to expand...
Click to collapse
Thanks for the info.
I have been looking down the Magisk avenue too.
My plan is, decrypt is then root it.
I did download those firmware files earlier but as you say, no .img files.
I have tried to follow a guide on youtube from rootjunky but got as far as running the info gathering piece to gather mount points, but it fell over. Don;t know if thats because I was using adb sideloading via TWRP .. ?
I attempted to run the commands from the batch file direct but no joy.
It would be really appreciated if you could point me to a guide to extract the img. It's my day 1 of this device and Android (already voided warranty from Amazon within 1 hour ha) but as I say, I have experience in most of what is needed from my iOS jailbreaking and bringing phones back from bootloops and the brink of bricks.
When you mention rooting with Magisk .. Can that be achieved in the state my device is in now, which is TWRP'd but encrypted ?
I also notice the "Ultimate Backup Tool, No Root Required" thread (cant put URL's yet as I'm a n00b member). Could that export my boot.img ?
I am done for today. I am working from home and it the device got delivered at 9:30 ish. I was hacking around with it all day and did about 20 min work. I'm fried now :-O
Thanks again

mr_fingy said:
Thanks for the info.
I have been looking down the Magisk avenue too.
My plan is, decrypt is then root it.
I did download those firmware files earlier but as you say, no .img files.
I have tried to follow a guide on youtube from rootjunky but got as far as running the info gathering piece to gather mount points, but it fell over. Don;t know if thats because I was using adb sideloading via TWRP .. ?
I attempted to run the commands from the batch file direct but no joy.
It would be really appreciated if you could point me to a guide to extract the img. It's my day 1 of this device and Android (already voided warranty from Amazon within 1 hour ha) but as I say, I have experience in most of what is needed from my iOS jailbreaking and bringing phones back from bootloops and the brink of bricks.
When you mention rooting with Magisk .. Can that be achieved in the state my device is in now, which is TWRP'd but encrypted ?
I also notice the "Ultimate Backup Tool, No Root Required" thread (cant put URL's yet as I'm a n00b member). Could that export my boot.img ?
I am done for today. I am working from home and it the device got delivered at 9:30 ish. I was hacking around with it all day and did about 20 min work. I'm fried now :-O
Thanks again
Click to expand...
Click to collapse
I get what you are saying. Going from iOS to android is a big step. Since the firmware files don't contain the boot.img and having in mind that you want to decrypt, getting a boot.img file is a must.
There are ways to get the boot.img without root but the ones i tried don't work. But there is an easy way that i know of that requires installing Magisk. When you flash Magisk from TWRP it roots your device. However, apart from rooting it also creates a backup of your boot.img in case something goes wrong.
Decrypting requires formatting your device, so Magisk will be removed too. So its only purpose for now is to provide you with a boot.img file.
Here is what you need to do
1. Download the latest magisk installer from the magisk threat
2. Save the file in your SD card (internal storage is encrypted)
3. Flash the Magisk installer from TWRP
4. Boot your device and navigate to /data
5. There should be a stock boot_xxx.img.gs file in there. Copy it to your storage, move it to a computer and extract it. You should get a boot.img file that you could use to decrypt.
6. Follow my guide to decrypt the boot.img and then flash it from bootloader
7. Since your device is now formatted from the decryption, you can choose the root method that you like.

Thanostsak said:
I get what you are saying. Going from iOS to android is a big step. Since the firmware files don't contain the boot.img and having in mind that you want to decrypt, getting a boot.img file is a must.
There are ways to get the boot.img without root but the ones i tried don't work. But there is an easy way that i know of that requires installing Magisk. When you flash Magisk from TWRP it roots your device. However, apart from rooting it also creates a backup of your boot.img in case something goes wrong.
Decrypting requires formatting your device, so Magisk will be removed too. So its only purpose for now is to provide you with a boot.img file.
Here is what you need to do
1. Download the latest magisk installer from the magisk threat
2. Save the file in your SD card (internal storage is encrypted)
3. Flash the Magisk installer from TWRP
4. Boot your device and navigate to /data
5. There should be a stock boot_xxx.img.gs file in there. Copy it to your storage, move it to a computer and extract it. You should get a boot.img file that you could use to decrypt.
6. Follow my guide to decrypt the boot.img and then flash it from bootloader
7. Since your device is now formatted from the decryption, you can choose the root method that you like.
Click to expand...
Click to collapse
Makes total sense. I just installed Magisk now from SD, thing is, the only spare SD I had was 128MB !! So I dont know if the .img was saved correctly. I will look into it tomorrow. My other large SD is corrupted but I have a 32GB one in the dashcam I will use tomorrow.
That leads me to a question. Is the auto created .img saved on the card or the internal storage ? I am assuming its card but I could not see it.
Will look more tomorrow.
Thanks

mr_fingy said:
Makes total sense. I just installed Magisk now from SD, thing is, the only spare SD I had was 128MB !! So I dont know if the .img was saved correctly. I will look into it tomorrow. My other large SD is corrupted but I have a 32GB one in the dashcam I will use tomorrow.
That leads me to a question. Is the auto created .img saved on the card or the internal storage ? I am assuming its card but I could not see it.
Will look more tomorrow.
Thanks
Click to expand...
Click to collapse
It is actually on the internal storage. Now that you are rooted you can use a root file explorer to get it. (128mb should be enough for this task)

Thanostsak said:
It is actually on the internal storage. Now that you are rooted you can use a root file explorer to get it. (128mb should be enough for this task)
Click to expand...
Click to collapse
On it now before work
Extracted stock_boot_(IDremoved).img.gz which contains the img
Will run your guide against this img
---------- Post added at 09:20 AM ---------- Previous post was at 08:33 AM ----------
All done. Nice and easy
No issues other than sweaty palms on Huawei long boot screen after flash :silly:
No reboot loop and no Magisk errors
Much appreciated for the help

Correction,
Magisk is giving the the errors when installing modules.
Followed your guide and all good

mr_fingy said:
Correction,
Magisk is giving the the errors when installing modules.
Followed your guide and all good
Click to expand...
Click to collapse
Great! If you need anything feel free to ask.

Well... I followed your steps to remove force encryption and install Magisk, everything seems to be perfect. The Magisk and modules are funtional. However after reboot all modules are dispeared, but magisk is still recognized by magisk manager. I don't know where is the problem...
Model: AGS-W09
f2sffix version: 2018.10.9
magisk version: 17.2 (At first I used the latest 18.0 version, but after this problem appeared, I noticed that f2sffix-20181009 only support magisk version 17.2 or older, so I retry your method with magisk 17.2, but the problem remains.)

TimYuan said:
Well... I followed your steps to remove force encryption and install Magisk, everything seems to be perfect. The Magisk and modules are funtional. However after reboot all modules are dispeared, but magisk is still recognized by magisk manager. I don't know where is the problem...
Model: AGS-W09
f2sffix version: 2018.10.9
magisk version: 17.2 (At first I used the latest 18.0 version, but after this problem appeared, I noticed that f2sffix-20181009 only support magisk version 17.2 or older, so I retry your method with magisk 17.2, but the problem remains.)
Click to expand...
Click to collapse
You should use the latest version of f2sffix (10.9) and then follow the procedure again. After your first boot follow VR25's recommendation and you should be good to go.
VR25 said:
Those getting everything broken after a second reboot, try the following workaround...
After the first reboot (right after installing), remove </sbin/.core/img/f2fs*bla*bla/service.sh>, </data/adb/magisk_merge.img> and </cache/magisk_merge_.img>.
Note that after doing this, you'll only be able to install modules and update Magisk from TWRP.
Click to expand...
Click to collapse

Thanostsak said:
You should use the latest version of f2sffix (10.9) and then follow the procedure again. After your first boot follow VR25's recommendation and you should be good to go.
Click to expand...
Click to collapse
It works!!! You are my hero!

TimYuan said:
It works!!! You are my hero!
Click to expand...
Click to collapse
Glad it worked for you.
Kudos to VR25 for making this amazing module even though he is not personally benefited by it.

Thanostsak said:
Glad it worked for you.
Kudos to VR25 for making this amazing module even though he is not personally benefited by it.
Click to expand...
Click to collapse
what if there is no fstab.qcom in kernel but stored in vendor/etc partition?
i've already edited the fstab, but still my system partition become ro (read only) when i made a change in system. all file manager error even previously has root.
please take a look at attachment . thanks in advance

an-_-dro said:
what if there is no fstab.qcom in kernel but stored in vendor/etc partition?
i've already edited the fstab, but still my system partition become ro (read only) when i made a change in system. all file manager error even previously has root.
please take a look at attachment . thanks in advance
Click to expand...
Click to collapse
I believe that what you are missing is after changing forceencrypt=footer into encryptable=footer you should also do a full data format through TWRP.

Thanostsak said:
I believe that what you are missing is after changing forceencrypt=footer into encryptable=footer you should also do a full data format through TWRP.
Click to expand...
Click to collapse
encryption is not a problem. since the first place already done with that data partition.
my problem is system partition, every time i made a change to system (for example deleting chrome.apk), something triggered that makes my system weird (magisk forceclose, all file manager become malfunction because system become read only). something lock my system partition if system change.
i thought change fstab.qcom <mnt_flags and options> ro,errors=panic to >> errors=continue (deleting ro/read only) will change my system behaviour, but it's not

s8 g950f lineage os 15.1

https://androidfilehost.com/?w=search&s=dreamlte

i flash this but cant boot stuck in s8 splash screen

That's interesting
Can't find any Github links of it
EDIT: This might use Albe96XDA's sources, but can't confirm

Do not have any videos?

manousos1 said:
i flash this but cant boot stuck in s8 splash screen
Click to expand...
Click to collapse
same here

https://www.cyanogenmods.org/forums/topic/lineage-os-15-1-for-galaxy-s8-android-oreo-8-1/

The latest unofficial doesn't seem to boot, seems there is a problem with the bootloader. I will try the first unofficial and see if it works. The uploader of the Rom has made previous roms for other devices so there is hope finally for our Galaxy S8

Omg this is real? Pls work on g955f too

Crossing my fingers !!!

Can any dev check the validity of this rom?

GeorgeChilian said:
The latest unofficial doesn't seem to boot, seems there is a problem with the bootloader. I will try the first unofficial and see if it works. The uploader of the Rom has made previous roms for other devices so there is hope finally for our Galaxy S8
Click to expand...
Click to collapse
test done with both rom unsuccessful - that of 21/11/2018 gives a black screen - that of 22/11/2018 gives a problem with the bootloader.
And you ?

tboguizmo said:
test done with both rom unsuccessful - that of 21/11/2018 gives a black screen - that of 22/11/2018 gives a problem with the bootloader.
And you ?
Click to expand...
Click to collapse
I have the same issue. The problem seems to be with the bootloader, i might be completely wrong. Is there any dev that can check the rom?
---------- Post added at 03:41 PM ---------- Previous post was at 03:33 PM ----------
The same dev also uploaded 2 AICP nightlies for our device. Or the developer confused code names for devices and this is not meant for our device

This is indeed for our device because dev has mentioned it is for "Galaxy S8" but highly doubt it is any different from the ROMs we already have that are not in a condition for daily use

I kept playing around with the rom for the past couple days and I pulled a tombstone file and it seems there is an openGL error. I have attached the tombstone file below. I'm not experienced enough to know what all of that stuff means lol
https://drive.google.com/open?id=1RZRV94t4UuZhcCDMCJuaFNe78DUNtVnN

GeorgeChilian said:
I kept playing around with the rom for the past couple days and I pulled a tombstone file and it seems there is an openGL error. I have attached the tombstone file below. I'm not experienced enough to know what all of that stuff means lol
https://drive.google.com/open?id=1RZRV94t4UuZhcCDMCJuaFNe78DUNtVnN
Click to expand...
Click to collapse
It seems there are other problems with the ROM, not just the OpenGL thing
"dlopen failed: library "/vendor/lib64/egl/get_process_name.so" not found"
You can try finding that file and placing it into the .zip file manually, unfortunately I can't test it because I have S8 plus, but no guarantee that it'll work

Kizoky said:
It seems there are other problems with the ROM, not just the OpenGL thing
"dlopen failed: library "/vendor/lib64/egl/get_process_name.so" not found"
You can try finding that file and placing it into the .zip file manually, unfortunately I can't test it because I have S8 plus, but no guarantee that it'll work
Click to expand...
Click to collapse
What about copying the whole of the vendor folder?
And placing them in the rom after the installation through the Twrp file manager?

GeorgeChilian said:
What about copying the whole of the vendor folder?
And placing them in the rom after the installation through the Twrp file manager?
Click to expand...
Click to collapse
That would work too.

Kizoky said:
That would work too.
Click to expand...
Click to collapse
So I just tried it and nothing changed which was weird. Then I go back to twrp and check the files and they're gone. They seem to get deleted every time the phone reboots for some reason I believe

GeorgeChilian said:
So I just tried it and nothing changed which was weird. Then I go back to twrp and check the files and they're gone. They seem to get deleted every time the phone reboots for some reason I believe
Click to expand...
Click to collapse
Yeah, that's why I usually like to replace/add something from/to the .zip file itself, nothing like that will happen

Kizoky said:
Yeah, that's why I usually like to replace/add something from/to the .zip file itself, nothing like that will happen
Click to expand...
Click to collapse
The zip has inside it a system.new.dat.br where all the system stuff are and I can't open it. Would I be able to just place the vendor files in the root of the zip and just update the updater-script?

August Security Patch Rolling Out

[Global] Mi A2 Lite V11.0.10.0.QDLMIXM rolling out!

Wow. That's gotta be some kind of record for Xiaomi
Mine is only 13M though. Must be a tiny update.

Wow! First time ever that this Android One device is actually up to date security wise.
Yes, from July update only 13MB.

Maybe it was there before, but after updating I noticed a native screen recorder icon.
Updated: It is not native. I have a screen recorder app installed.

Direct share not yet available.

penahj said:
Maybe it was there before, but after updating I notice a native screen recorder icon
Click to expand...
Click to collapse
strange i dont have this one and never had screen recording option

Antho02 said:
strange i dont have this one and never had screen recording option
Click to expand...
Click to collapse
You are right. It's not a native app. I have a screen recordering app installed. Sorry for the wrong news.

Does someone know how to install an OTA Update without using the System Update App? It always says Installation Problem. Installation failed.
I'm rooted with magisk, that's the reason i guess.
I found the 13mb Update as a zip file, but it's not flashable via twrp... Any Suggestions?
Best regards
Alex

Alibabara said:
Does someone know how to install an OTA Update without using the System Update App? It always says Installation Problem. Installation failed.
I'm rooted with magisk, that's the reason i guess.
I found the 13mb Update as a zip file, but it's not flashable via twrp... Any Suggestions?
Best regards
Alex
Click to expand...
Click to collapse
+1 I am also looking for this

Alibabara said:
Does someone know how to install an OTA Update without using the System Update App? It always says Installation Problem. Installation failed.
I'm rooted with magisk, that's the reason i guess.
I found the 13mb Update as a zip file, but it's not flashable via twrp... Any Suggestions?
Best regards
Alex
Click to expand...
Click to collapse
with twrp/magisk i always do
1-xiaomiflash rom (keep user files)
2-boot and install twrp
3-boot and install magisk
no problem this way

Antho02 said:
with twrp/magisk i always do
1-xiaomiflash rom (keep user files)
2-boot and install twrp
3-boot and install magisk
no problem this way
Click to expand...
Click to collapse
So you Flash the whole Rom (~1.2gb) and not just the Update?
I would like to find a way to Flash just the Update since your method is taking too long for me...
Best regards
Alex

If you only have Magisk, the standard process should work for you.
https://forum.xda-developers.com/mi-a2-lite/how-to/guide-install-magisk-proper-support-ota-t3836952
If it's not working and you have somehow modified some other partition, it will be written to the logcat.
adb logcat | grep update_engine

My Problem is, even with magisk 'uninstalled' the Update App from xiaomi still says 'Installation failed: Installation Problem'
That even happens with totally Stock rom, no root and no twrp.
I dont know why. But is there any other way to Update manually without flashing the whole Big Rom file? Just the Update file...
There must be a reason why there is an update file in zip Format which is 13mb Big.
Best regards
Alex

Alibabara said:
My Problem is, even with magisk 'uninstalled' the Update App from xiaomi still says 'Installation failed: Installation Problem'
That even happens with totally Stock rom, no root and no twrp.
I dont know why. But is there any other way to Update manually without flashing the whole Big Rom file? Just the Update file...
There must be a reason why there is an update file in zip Format which is 13mb Big.
Best regards
Alex
Click to expand...
Click to collapse
Alex, You don't have to flash the whole big rom file, but you do have to download it though. You can get it from here: https://mirom.ezbox.idv.tw/en/phone/daisy/roms-global-stable/
You then have to extract the files that you need with payload_dumper which you get from here:
https://androidfilehost.com/?fid=818070582850510260
NB that is the Windows 64bit version so make sure that is the OS your pc is using.
You then have to find which partition it is that is causing the problem for which you have to use a1291762's advice:
Code:
adb logcat | grep update_engine
and read very carefully through the results because the offending entry will be difficult to spot amongst the dozens of others.
You then flash the partition mentioned in the logcat. For example if 'system' is mentioned in the logcat as having an incorrect hash (that is always the reason for the failures) you would have to extract 'system.img' with payload_dumper and run
Code:
fastboot flash system system.img
Then try the update again. If it works you will also probably have to reinstall Magisk from scratch again as flashing system will probably remove it.
Yes it is complicated - far too complicated, but the simple measure you call for - just flash an update file - has, to the best of my knowledge never been possible, so there must be some reason why that is so, but I don't know what it is.
Incidentally, the reason I am able to respond to this question is that I had a torrid time yesterday trying to update my A2 lite on which I had not one, but 3 errors. aboot hash incorrect, system hash incorrect, and before any of that the normal Magisk uninstall told me it had no images to restore and so had to be uninstalled completely. It took me hours and it wasn't that much fun.

Alibabara said:
There must be a reason why there is an update file in zip Format which is 13mb Big.
Click to expand...
Click to collapse
The update is only 13M because it contains only changes. But for that to work, your partitions must be unmodified.
The larger update zip has complete partitions so it can work even if you have changes. You may be able to do the recovery update method with that file...
The even larger fastboot image has every partition.

thanks everyone for the help!
I did it as you said viking777 and it worked.
It's sad, that for an 13mb update this procedure is necessary, but thats how it is..
So thanks again everyone for the help

Antho02 said:
with twrp/magisk i always do
1-xiaomiflash rom (keep user files)
2-boot and install twrp
3-boot and install magisk
no problem this way
Click to expand...
Click to collapse
Can I do this with out installing TWRP as I haven't installed it already.

Aadil Gillani said:
Can I do this with out installing TWRP as I haven't installed it already.
Click to expand...
Click to collapse
sure, even more quick if u dont need twrp
flash last rom with xiaomi flash (save user data selected)
then boot patched.img and install magisk, less than 10 mins and no need to worries about uninstall magisk or any mod before

Antho02 said:
sure, even more quick if u dont need twrp
flash last rom with xiaomi flash (save user data selected)
then boot patched.img and install magisk, less than 10 mins and no need to worries about uninstall magisk or any mod before
Click to expand...
Click to collapse
I have some questions it would be a be a pleasure if you could answer.
Q1 will the modules remain or not ?
Q2 how to make make patched boot img I mean should I make my self using Magisk Manager app
Q3 Also which TWRP do you use and if it has any problems
Q4 should I use zip file or tgz for mi flash