Database Info

having fun in recovery... (and messing with Red5)

So, I'm playing with recovery... In particular, I'm working on replacing the stock recovery with CWM Recovery. A good nandroid backup is always the first step to hacking an android device.
I've managed to repack the recovery partition (finally) as unsecure (meaning I can boot into recovery, adb shell into the device, and have root access.) While in here, I'm just noticing something different on the tablet:
It appears that the firmware update from kies has added some odd bloat: the default factory recovery starts by copying several items from a "preload" partition to your /sdcard partition. How nice of Samsung to add even more addition BLOAT to our devices. (I'll be removing that aspect of recovery, I promise.)
Another oddity I'm finding is that, normally with these devices when they are booted normally (and adb is able to connect), the commandline "adb reboot recovery" will reboot the device into recovery mode. That does NOT happen with this tablet (but I'm not sure why.) I have to power down and power back on with the proper volume switch held down.
Okay... time for me to build a copy of CWM Recovery that'll (hopefully) work on this tablet. Wish me luck!
Gary

Thanks in advance! Always glad to hear the interesting finds in a new device.
Sent from my GT-P6210 using Tapatalk

ah, yes... the "new" shared partitions in honeycomb (and ICS.) No longer is there supposed to be dedicated space for /data and /sdcard partitions. They are supposed to use the same space.
Actually, that makes sense. You never have to use something like app2sd, because it's all really the same space. How it gets there, however, is annoying (when trying to reverse engineer a gingerbreak CWM recovery to a honeycomb device.) There is no /sdcard parition on this thing. /sdcard is actually a remap of the /data/media directory. Nice.
My problem is getting CWM Recovery to understand that. pfft.
I wish I could find some source for a CWM recovery partition for another honeycomb tablet. that'd make my life easier, I think.

WARNING: Playing "world of goo" is a major distraction to getting other things accomplished.

have recovery making a nandroid. This would probably be easier if I knew what I was doing. Oh, btw, who wants to test this stuff for me?

garyd9 said:
have recovery making a nandroid. This would probably be easier if I knew what I was doing. Oh, btw, who wants to test this stuff for me?
Click to expand...
Click to collapse
Hey,
I'm also working on it, I'm an dev who ported CWM to the Galaxy Note.
Wait a few hours and you will have CWM

netchip said:
Hey,
I'm also working on it, I'm an dev who ported CWM to the Galaxy Note.
Wait a few hours and you will have CWM
Click to expand...
Click to collapse
I might have just beat you to it. I'll give you a hint, though: honeycomb does some things with partitioning thats very different from previous android versions. CWM tries to take some of that into account, but because of how /data is set up in recovery.fstab, it's not detected that /sdcard should really be /data/media. (I'm rambling.. heh..)
Anyway, pershoot worked this out, so if you pull a specific changeset from his github (https://github.com/pershoot/android...mmit/6dacf061b8476c3e3e2857ca078df95706d62770), and apply it to the CWM in the current cyanogen 7.2, everything should work.
Well, so far everything appears to be working. I've validated the backup works, but haven't verified the restore. I've also modified the code to discourage people from partitioning their sdcards (and it's a bug in CWM that they can choose that option when /sdcard is just a symlink to /data/media)
Anyway, I'll dump the image someplace if anyone wants to mess with it. I honestly have NO idea how to build any kind of package to automate installing it. I've been using "dd" all night long.

On second thought, maybe I'll go to bed... (been awake for over 24 hours)
I'm in the middle of testing the nandroid restores, and there's no way I'll post anything until I'm sure it works. Considering how tired I am, I'll feel better testing this when I'm rested.
One issue I'm REALLY getting annoyed by: For some reason, when I do a "adb reboot recovery", the tablet doesn't reboot into recovery. Even if I'm in a root shell, "reboot recovery" isn't taking me into recovery.
Good night!
Gary

garyd9 said:
On second thought, maybe I'll go to bed... (been awake for over 24 hours)
I'm in the middle of testing the nandroid restores, and there's no way I'll post anything until I'm sure it works. Considering how tired I am, I'll feel better testing this when I'm rested.
One issue I'm REALLY getting annoyed by: For some reason, when I do a "adb reboot recovery", the tablet doesn't reboot into recovery. Even if I'm in a root shell, "reboot recovery" isn't taking me into recovery.
Good night!
Gary
Click to expand...
Click to collapse
I think the kernel is not connected with HC
ICS == almost HC.
There we also don't need the patch

thank you guys so much! great job!

chrisrotolo said:
thank you guys so much! great job!
Click to expand...
Click to collapse
Is on this device the Download mode?
I compile my kernels from source, now I need a tester who don't care about warranty.
I use a module of the SGS2, I've contacted a few people experieced in param.lfs, and they say if the kernel can't mount it it says "logo.jpg not found" and it still boots further.
PM me if you are interested!

posted CWM Recovery.

this is habit forming.
the upcoming version will, in addition to being in a nice update.zip, will also install 'su' so you can root your tab and install recovery all at once.
I am _not_, however, installing the SuperUser application (which is needed as well.) That can easily be done from the market after installing this update file.
All will be documented soon.

I could swore I had an sdcard partition, under it's own or external
Sent from my GT-P6210 using xda premium

For the internal, it's not a real partition. The "/mnt/sdcard" mount is a FUSE link to /data/media. (It's a real parition on the external sdcard if you have one installed.)

I'm working with someone to get copies of the recovery and normal boot kernel partitions from the P6200 (international 3g.) Once I have that, and assuming my blind kernel compiles actually work, we'll have CWM recovery for that tablet as well.
Take care
Gary

I have an international 6200. If you tell me what you need and maybe some help in how to get it, I will dump whatever you want.
Z.

garyd9 said:
I'm working with someone to get copies of the recovery and normal boot kernel partitions from the P6200 (international 3g.) Once I have that, and assuming my blind kernel compiles actually work, we'll have CWM recovery for that tablet as well.
Take care
Gary
Click to expand...
Click to collapse
BTW, have you confirmed that recoveries are incompatible between variants? The 10.1 was "one recovery fits all".

Entropy512 said:
BTW, have you confirmed that recoveries are incompatible between variants? The 10.1 was "one recovery fits all".
Click to expand...
Click to collapse
Currently, they all share the same "recovery" binary (entire /sbin directory, actually), but they need different recovery.fstab files in the initramfs due to different /system (and /data, I think) locations. I'm not at home, so I can't check if it was only 'system' or both.
That one file being different causes them to have a different initramfs, and therefore a different zImage (recovery.img.) I once considered using init.rc to dynamically put a different recovery.fsab into place based on the tablet model at runtime, but how would I be able to determine the tablet model dynamically? default.prop would be useless (as it's also part of the recovery initramfs) and it wouldn't be a good idea for the RECOVERY to rely on the existance of valid data on any other partition. There are ways to take educated guesses based on partition counts and other strange things, but I don't think it's worth the risks.
I do have to admit that I've been having fun messing with this stuff.
Take care
Gary

Ah, that's odd/rare - kind of disappointing.

Team Win Recovery Project for the LG G Pad X 8.0 (V521, V522, V525)

[RECOVERY] TWRP 2.8.7.0 - TeamWin Recovery Project
TeamWin is proud to present TWRP v3.0.2.0 for the LG G Pad X 8.0 (V521, V522, V525)
Youtube video: http://www.youtube.com/watch?v=RIvWVS_Rkxo
Full TeamWin credits are on the TWRP page on the TeamWin website: http://teamw.in/project/twrp2
Introduction:
Team Win Recovery Project or twrp for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for new features
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/omnirom/android_bootable_recovery
Gerrit for TWRP Official Device Configs - http://gerrit.twrp.me
Gerrit Instance - http://gerrit.omnirom.org
If you have made your own twrp build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
b3 Device Config: https://github.com/Shabbypenguin/android_device_lge_b3
DOWNLOAD:
http://www.t2h-gh0st-is-garbage.xyz/TWRP-V521-3.0.2.0.img
Support:
Only ask for support in the chat for general twrp issues, not device specific problems.
Click http://webchat.freenode.net/?channels=twrp for live support or join us in #twrp on Freenode IRC servers[/QUOTE]

8/21/2016
updated the link, same file name fixed internal storage mount and a few other minor issues
8/20/2016 - initial release
Youll need to use flashify to flash the image after rooting. this should work on all b3 models, aka lg v525, v521 etc
For the test version i had of 2.7.8.0 i had to do this, since i have already done it i cant confirm if you need to on 3.0.2.0 or not. ----- data/internal storage wont mount/work until you go to wipe> format data and format without encryption reboot recovery and then do a factory reset. this will wipe your ENTIRE device but allow you to use twrp normally.

Thanks a lot, i'll flash it soon. Any idea if xposed would work on this device?

shabby is the man

emilyrugburn said:
Thanks a lot, i'll flash it soon. Any idea if xposed would work on this device?
Click to expand...
Click to collapse
I dont use or follow xposed development (my last 3 personal phones werent even rooted) i dont see any reason why it wouldnt we have twrp as well as stock kdz so you can mess things up pretty bad and still recover.

shabbypenguin said:
I dont use or follow xposed development (my last 3 personal phones werent even rooted) i dont see any reason why it wouldnt we have twrp as well as stock kdz so you can mess things up pretty bad and still recover.
Click to expand...
Click to collapse
Xposed looks to work just fine. Thanks again

emilyrugburn said:
Xposed looks to work just fine. Thanks again
Click to expand...
Click to collapse
glad to hear it
i grabbed the tablet as it was a great deal and ive loaded it up with apps for my daughter who is the primary user for it so i wont be doing much with it but its good to see the community finally taking off .

Please add the installation instructions - http://www.xda-developers.com/how-to-install-twrp/
Also, add a 'Donation' segment if you're interested in accepting them

avishah395 said:
Please add the installation instructions - http://www.xda-developers.com/how-to-install-twrp/
Also, add a 'Donation' segment if you're interested in accepting them
Click to expand...
Click to collapse
there is a donate to me button under my name and those instructions dont apply to this device. i specify how to use this in the second post.

IF POSSIBLE, please add your thread to our device ET so we can get a full thread eventually - http://forum.xda-developers.com/t/lg-g-padx
Also, update the version number in the title. I was able to get TWRP working, you do still need to wipe to clear the encryption (it says it does this in red). Then, you can continue using it normally.

avishah395 said:
IF POSSIBLE, please add your thread to our device ET so we can get a full thread eventually - http://forum.xda-developers.com/t/lg-g-padx
Also, update the version number in the title. I was able to get TWRP working, you do still need to wipe to clear the encryption (it says it does this in red). Then, you can continue using it normally.
Click to expand...
Click to collapse
i was on that page and clicked new thread, not sure why it didnt work or how exactly you are supposed to do it as that logically made the most sense to me.
i know you need to wipe to clear the encryption, but i wasnt sure if you needed to clear the encryption in order to use twrp properly as i had already done it on an older version. good catch on the version number

shabbypenguin said:
i was on that page and clicked new thread, not sure why it didnt work or how exactly you are supposed to do it as that logically made the most sense to me.
i know you need to wipe to clear the encryption, but i wasnt sure if you needed to clear the encryption in order to use twrp properly as i had already done it on an older version. good catch on the version number
Click to expand...
Click to collapse
I'm not entirely sure about clearing encryption to use TWRP. I know when I did it, TWRP functioned normally.
Ill ask XDA about the ET, maybe it has a second page that isn't showing.
UPDATE: To add our tag, look for "Edit Tags" (CTRL+F) or use this URL http://forum.xda-developers.com/threadtag.php?t= {add thread id - yours is 3443944}. Our ET/tag is "lg-g-padx"

If it could be made as flashable .dz or .tot, that would be excellent.

mingkee said:
If it could be made as flashable .dz or .tot, that would be excellent.
Click to expand...
Click to collapse
as previously mentioned, only people who have leaked lg tools can make flashable tots etc. i spent hours researching it, testing out different methods and reflashing stock kdz a bunch of times.
the only way i could streamline this is if i submitted this to be made official so once rooted you could use twrp manager, but the submission process isnt exactly one that is a lot of fun to do. especially considering with flashify you only have to do like 3 clicks anyways.

Got something for you, shabbypenguin.
My intitial partitions-being-unmountable-due-to-unknown-error-150 likely because of faulty .tot file. the 1.4GB one works. of course after flashing 10c
Device still reports as LG V510 via MTP. Not a huge deal.
In TWRP file browser, internal storage is mounted as /emmc ?!
SD Card will not mount, log attached. Complete. /external_sd is not /dev/block/mmcblk0p1. It's /dev/block/mmcblk1p1 I manually mounted it there and it works.
Some errors about /sdcard as well. Probably cant mount /data/media/0 there. is my guess.
OTG does not mount properly as well, in recovery it shows up at /dev/block/sda1, recovery's fstab points at /usb-otg?
Was gonna put the output of mount/df from recovery and android but thought that wouldn't help.

eriklion said:
Got something for you, shabbypenguin.
My intitial partitions-being-unmountable-due-to-unknown-error-150 likely because of faulty .tot file. the 1.4GB one works. of course after flashing 10c
Device still reports as LG V510 via MTP. Not a huge deal.
In TWRP file browser, internal storage is mounted as /emmc ?!
SD Card will not mount, log attached. Complete. /external_sd is not /dev/block/mmcblk0p1. It's /dev/block/mmcblk1p1 I manually mounted it there and it works.
Some errors about /sdcard as well. Probably cant mount /data/media/0 there. is my guess.
OTG does not mount properly as well, in recovery it shows up at /dev/block/sda1, recovery's fstab points at /usb-otg?
Was gonna put the output of mount/df from recovery and android but thought that wouldn't help.
Click to expand...
Click to collapse
thanks for the info, my sdcard is provisioned as internal storage so it doesnt show up as a micro sdcard in recovery, not sure how i got it so mixed up but ill push an updated version out later tonight
what do you mean it shows up as emmc?

shabbypenguin said:
thanks for the info, my sdcard is provisioned as internal storage so it doesnt show up as a micro sdcard in recovery, not sure how i got it so mixed up but ill push an updated version out later tonight
what do you mean it shows up as emmc?
Click to expand...
Click to collapse
When you're browsing for things to flash/etc, theres the path/directory /emmc, you enter it and it contains things that are supposed to be in /data/media/0

Confused About Install Instructions
shabbypenguin said:
8/20/2016 - initial release
Youll need to use flashify to flash the image after rooting. this should work on all b3 models, aka lg v525, v521 etc
For the test version i had of 2.7.8.0 i had to do this, since i have already done it i cant confirm if you need to on 3.0.2.0 or not. ----- data/internal storage wont mount/work until you go to wipe> format data and format without encryption reboot recovery and then do a factory reset. this will wipe your ENTIRE device but allow you to use twrp normally.
Click to expand...
Click to collapse
I have flashed TWRP many times in the past on many devices. Yet for the 1st time after using Flashify, it obviously did not install properly as it didn't mount internal storage on this pad. It doesn't even recognize show that there's anything available in internal storage to back up to. Frankly, I don't understand your above instructions on how to property install it.
Typing clear instructions would be greatly appreciated as I can't use it. But do appreciate the time you put into it and will make a donation once this has been fixed.

pressmoon said:
I have flashed TWRP many times in the past on many devices. Yet for the 1st time after using Flashify, it obviously did not install properly as it didn't mount internal storage on this pad. It doesn't even recognize show that there's anything available in internal storage to back up to. Frankly, I don't understand your above instructions on how to property install it.
Typing clear instructions would be greatly appreciated as I can't use it. But do appreciate the time you put into it and will make a donation once this has been fixed.
Click to expand...
Click to collapse
you need to go to wipe > format data. your devices data is by default encrypted and twrp cant decrypt it. once youve wiped data, reboot recovery and then do a factory reset. your device will boot and function as normal and youll have a fully working twrp

eriklion said:
When you're browsing for things to flash/etc, theres the path/directory /emmc, you enter it and it contains things that are supposed to be in /data/media/0
Click to expand...
Click to collapse
ive uplaoded a version taht fixed that, but im unable to mount external_sd or usb otg. sda1 doesnt show up for me in /dev/block and even manually trying to mount sdcard to mccblk1p1 fails due to an invalid arguement, how did you mount yours?

Samsung Galaxy M21 2021 Edition (SM-M215G/DS)

I own some old samsung Galaxy models like J7 Prime and had tried good Custom ROMs on them but up recent I purchased this Samsung Galaxy M21 2021 Edition (SM-M215G/DS) a few days ago thinking that it's going to be same as Galaxy M21 2019 (SM-M215F) model, to my horor its bootloader & recovery seems to work differently from J7 prime (with bar codes in download mode) . So it's a differrent model. The bootloader unlock process on this Galaxy M21 2021 Edition is same as mentioned in Galaxy M21 2019 thread ( https://forum.xda-developers.com/t/rom-full-oneui-10-totsukaos-q-for-galaxy-m21.4219975/ ) but none of the unofficial TWRP recoveries work nor does Magisk boot.img patch method work for rooting this model. Samsung does not support Fastboot as I understand & everything ends with Error : Signature verification failed. The only option left to me is sell off this phone but its so new.
If any developer can help me with some Custom Recovery that could install itself for rooting and perhaps custom ROM (I know I'm asking for too much ) for this device (SM-M215/DS), I will gladly donate $20.00/month for a year (Pls consider the bad times of pandemic we all are in). As right now I've put up this device (SM-M215G/DS) for sale. I've attached a few screenshots of the device maybe it could help any Dev who's interested (Hopefully ).

To root Android a Custom Recovery isn't required at all.

jwoegerbauer said:
To root Android a Custom Recovery isn't required at all.
Click to expand...
Click to collapse
jwoegerbauer said:
Firstly, I THANK YOU for replying to my desperate post. I'm delighted that Dev (jwoegerbauer) wanted to help.
Coming to the topic, Yes I was aware that rooting didnt require Custom Recovery.
1> I had tried to install Magisk_V23.zip via command [adb sideload magisk.zip] but the
response I had got was [Error: Signature verification failed, Error: Aborted.] on this device
(SM-M215G/DS).
2> When I flashed couple of TWRPs (one official for Galaxy M20 from www.twrp.me & few
unofficial TWRP builds from the net) via latest ODINv14.3 , ODIN displayed PASS! and
rebooted as I had kept Auto Reboot & F.Reset Time ON. But Native Android revovery came
on with Custom Binary Error. Again, I did the same with F.Reset Time & Auto Reboot OFF this
time and when I manually rebooted to recovery (Vol UP + Power) it was back to native
android recovery. I had to factrory reset to get the samsung logo then booted into welcome
screen.
3> I have checked the link ( https://forum.xda-developers.com/t/...al-adb-fastboot-
drivers.4185535/post-83851013 ) you provided. Awesome work! My questions are will it
enable FASTBOOT on SAMSUNG? Because when I select Reboot to Bootloader option in Anroid Recovery the phone does go into Fastboot Mode but apparently Fastboot seems
disabled by Samsung because from the PC it does not recognise the Fastboot Devices. So,
as a noob if I've understood whats mentioned in the link you provided is that Samsung didnt
provide the Native Samsung Fastboot Drivers for the Galaxy M21 2021 DELIBERATELY? So,
the link you provided will help me install the required Fastboot Drivers? & then I can flash
TWRP.img or Magisk.img?
Thanks in advance
Click to expand...
Click to collapse

jwoegerbauer said:
To root Android a Custom Recovery isn't required at all.
Click to expand...
Click to collapse
Followup 1:
Hi, I tried your ADB-FASTBOOT-Installer but it doesnt seem to go beyond "Waiting for devices" screen.
1> I tried installing magisk v.19.3.zip (renamed to just "OTA") using command (adb sideload OTA)
first error i got was (adb: failed to read command: No error)
2> second time i tried installing from another folder belonging to 15-seconds-adb and it showed [ (0.01x) success ] something like that
3> I installed magisk manager 2021.4.9 Magisk v22.1 by Package Installer method not sideload method. When i rebooted & checked magisk manager it wasnt rooted so I tried boot.img patch method and got error: unable to unpack boot.img
I have attched some screenshots of the errors but what I understand from this is that the new Samsung devices might have img files written in some new format i guess because why else would magisk manager fail to unpack and patch a boot.img file, ususally it does fine.
I have also attached a copy of the device stock boot image file (hope i'm not breaking some xda rules here about posting img files , i just joined yesterday so )
Maybe its of some help to some Dev who might need these to find a workable solution.
The stock firmware I downloaded is flashing well on the device (SM-M215G/DS), the link is here- https://samfrew.com/download/Galaxy__M21__2021__Edition__/lOg2/INS/M215GDDU1AUG2/M215GODM1AUF3/

Also Magisk isn't needed to root a phone's Android: that's a widespread misconception,1000 times reported on the Internet and also here on XDA .

jwoegerbauer said:
Also Magisk isn't needed to root a phone's Android: that's a widespread misconception,1000 times reported on the Internet and also here on XDA .
Click to expand...
Click to collapse
Well what necessarily needed for rooting an android phone is just modifying some files in /system? I have seen the phrase 'toybox 0.8.5' a multiple times in your posts, not sure what is that.

LR7875 said:
Well what necessarily needed for rooting an android phone is just modifying some files in /system? I have seen the phrase 'toybox 0.8.5' a multiple times in your posts, not sure what is that.
Click to expand...
Click to collapse
Toybox is a replacement for many Linux command-line utilities that is targeted at embedded systems - similar to BusyBox. It was created by Rob Landley, who is also a former BusyBox maintainer. Toybox is merged into any Android starting with version 6.

jwoegerbauer said:
Toybox is a replacement for many Linux command-line utilities that is targeted at embedded systems - similar to BusyBox. It was created by Rob Landley, who is also a former BusyBox maintainer. Toybox is merged into any Android starting with version 6.
Click to expand...
Click to collapse
Oh learned something more.
Well what is the definition of root then?

LR7875 said:
Oh learned something more.
Well what is the definition of root then?
Click to expand...
Click to collapse
Sorry to barge in LR7875, to my knowledge (I have rooted & installed Roms on some older Samsung/Redmi/Laptops etc.) rooting is the process through which we gain Admin Rights / Super User on Linux devices. Correct me if I'm wrong. Im not a programmer by any means so.

jwoegerbauer said:
Also Magisk isn't needed to root a phone's Android: that's a widespread misconception,1000 times reported on the Internet and also here on XDA .
Click to expand...
Click to collapse
Hi there jwoegerbauer, thanks for responding. If im not being bothersome , I'll need to stalk you on XDA for some help on this issue of rooting this device, if it s okay with you . Pray tell me what else other than magisk could root this stubborn Samsung model ? Im getting some good offers for this device on the local online market but i really didnt want to sell it off just wanted to root & install roms like before.. Other than magisk I just know of SuperSU by chainfire which I think stopped working well post android 8 oreo but will it work for Android 11? No way any changes to /system/Priv-app and the phones factory reset themselves. One-Click Root only takes calls & they charge $50 for rooting, but whats the guarantee if we pay up that theyll root it properly & taht too it would be just root not Recovery or ROMs. I'm lost.

Installing Magisk DOESN'T ROOT Android. Installing SuperSU DOESN'T ROOT Android. POV.
To have said it:
Magisk is successor to XPosed, means a software framework what once get added to Android allows you to systemless apply modules, means some functionalities modders are missing on standard Android. The crux with Magisk is it patches device's bootloader.
SuperSU simply is a per-app root-access management tool, nothing else: it requires Android got rooted.

OldNoobOne said:
...
The stock firmware I downloaded is flashing well on the device (SM-M215G/DS), the link is here- https://samfrew.com/download/Galaxy__M21__2021__Edition__/lOg2/INS/M215GDDU1AUG2/M215GODM1AUF3/
Click to expand...
Click to collapse
How are you "flashing"?
Why do you say it "is flashing well"?
As far as I know, you need to use Odin (on a PC) to "flash" a Samsung device. Samsung does not support fastboot -- no amount of updating drivers on your PC will make a Samsung device start supporting fastboot.
Magisk is much more than just a way to root, but a side effect of installing Magisk is that you will be rooted.
If you have installed the Magisk Manager app and tried to patch the AP.tar of the stock firmware, and you are getting an error, you should look through the main Magisk thread, and maybe ask there.

J.Michael said:
Magisk is much more than just a way to root, but a side effect of installing Magisk is that you will be rooted.
Click to expand...
Click to collapse
IMO you're WRONG: Magisk DOESN'T ROOT Android, but you additionally can install MagiskSU app what grants elevated rights ( AKA SU ) to Magisk.

jwoegerbauer said:
Magisk is successor to XPosed, means a software framework what once get added to Android allows you to systemless apply modules, means some functionalities modders are missing on standard Android. The crux with Magisk is it patches device's bootloader.
Click to expand...
Click to collapse
I need to hop on and correct a few details here...
Magisk is not a successor to Xposed. That's like comparing apples and oranges. If you want to know how Magisk came to be John has written about that in a couple of places, here for example:
Spoiler
https://www.reddit.com/r/Android/comments/7oem7o
And Magisk does not patch the bootloader, but the ramdisk which can be found in either the boot or recovery image depending on your device. Details about that here:
https://topjohnwu.github.io/Magisk/boot.html

OldNoobOne said:
Sorry to barge in LR7875, to my knowledge (I have rooted & installed Roms on some older Samsung/Redmi/Laptops etc.) rooting is the process through which we gain Admin Rights / Super User on Linux devices. Correct me if I'm wrong. Im not a programmer by any means so.
Click to expand...
Click to collapse
Oh I see, it is used to do something that are restricted originally, e.g. access system files, delete system apps, etc.

Didgeridoohan said:
I need to hop on and correct a few details here...
And Magisk does not patch the bootloader, but the ramdisk which can be found in either the boot or recovery image depending on your device.
Click to expand...
Click to collapse
Correct: it should also have been called boot.img instead of bootloader. Sorry for this.

LR7875 said:
Oh I see, it is used to do something that are restricted originally, e.g. access system files, delete system apps, etc.
Click to expand...
Click to collapse
True . Don't quote me, (In a nut shell ) up from Andoid 9 (Pie) modification to /system /app etc. is difficult per my knowledge, thats why probably magisk sits in the boot partition, no one dare touches the system partition anymore while the gadget is ON. Only Gugle stays in the system partition im sure. The Custom Recoveries do wipe the device but are unable to erase the core andoid OS inside . Even 'Fastboot Erase' command cant get andoid out completely (exception Linux-phones i think). So practically Andoid devices are just gadgets that are 'leased' to the so-called 'owner' of the device (without explicitly mentioning the term 'leased' by gugle). The cost of the smart-gadget is practically the 'Down Payment' we pay to Gugle & OEMs then the rest of the revenue they make from Ads etc. which goes as 'Rent/lease payment' to them ultimaately & we never get to own the devices we purchase EVER! .
My sixth-sense says The chinese OEMs allowing Fastboot Mode only for now but only to make inroads into the smart-gadget market, once they have made everyones profile Gugle & pentgon might just make the softwares on these smart-gadgets wholly tamper-proof & focus more on 'managing' or keeping an eye on their 'subjects' [given that the whole gugle business,- 'search-engine', 'smart-device' etc. started officially in 2004 which was POST the 9.11 ATTACK].
So they're probably maintaining the Big-Data on everyone who uses their devices & 2014 is when data-warehousing became the need if i remember correctly; so, it was all about compressing the Big-data gathered & then Analytecs took the spotlight by 2016-17 coz they needed to analyize all the data collected & remove the junk from it then home in on pentgons targets. It's Obvious . No wonder they're pushing PX-Xperience ROMs through the ROM channels to cover the gap created by chinese OEMs eating into their market share. Why else do they charge other OEMs $2 for OTG-support while Shamshung (and now MYUI) already had native OTG-support on their devices shipped? so that's what Sekure-folder all about, YOUR DATA LOADED & LOCKED real-time then SHIPPED back to Gugle-Analytecs. Obvious.

Well so root is basically... Removing those ads and trackware up to the bare bones of the phone, to ensure all your data isn't used to make the spammy advertisements?

Android is nothing else then a derivated Linux. In the world of Linux the Root User is the user that has all rights esp. accessing / modifying system files, it's comparable to the Administrator in the world of Windows.
In the world of Linux this Root User typically is called superuser ( commonly abbreviated: SU ). In the world of Android such a superuser isn't in general implemented by default: it must get added to Android by modding it, means adding a SU ( read: Switch User ) binary - in whatever form - to Android what is systemwide accessible. In the world of Android an user root exists what is the user with user ID 0.

[ deleted ]

Huawei Partition Kit - Enlarge system partition

Huawei Partition Kit​
This kit allows you to enlarge/reduce (2Go->5Go) the system partition on a Huawei kirin 65x, 960 or 970 phone. You can do it from a Huawei android 9 rom, a Lineage 18.1, 19.1, 20, or an AOSP 11,12 or 13. The kit reinstalls all the partitions, so if you are for example under the huawei stock rom, you come back under the huawei stock rom but with more space for the system. It has been tested on a dozen models (PRA, ANE, STF, POT, FIG, AGS, etc.) under EMUI 8, 9 or 9.1.
It supports erofs partitions.
WARNING:
RUN THIS TOOL CLEAR ALL DATA FILES IN YOUR DEVICES. IF POSSIBLE, DO A BACKUP FIRST. USE IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE FOR ANY BROKEN RELATED TO IT.
Installation
1) Unzip the zip file on your PC.
2) In the kit directory, read the readme file in the language of your choice (french, english, russian) and execute the step
Version
Last version is 0.62
Requisites
Custom twrp
10 Go free on your PC
Download
Here

AltairFR said:
Download
Here
Click to expand...
Click to collapse
Hi, you might have linked the wrong file...
I am getting an apk
https://sourceforge.net/projects/altairfr-huawei/files/HWGSIPartitionKit/HWGSIPartitionKit.zip/download
I believe this is what you wanted to post...

Nicknackpaddywack101 said:
Hi, you might have linked the wrong file...
I am getting an apk
https://sourceforge.net/projects/altairfr-huawei/files/HWGSIPartitionKit/HWGSIPartitionKit.zip/download
I believe this is what you wanted to post...
Click to expand...
Click to collapse
https://sourceforge.net/projects/altairfr-huawei/files/HWGSIPartitionKit/HWGSIPartitionKit.zip/download
Thanks, i have set correct link

Thank you dear friend, it really works. I managed to increase the system partition on Huawei Nova 2s on Kirin 960 from 2700mb to 3500mb. In the HWGSIPartition program, I got errors, as I understand it in section B, but in the end everything went well.I wanted to ask you how much you can increase the system partition, in the HWGSIPartition program, there is a figure of 5GB.

Great Dragon said:
Thank you dear friend, it really works. I managed to increase the system partition on Huawei Nova 2s on Kirin 960 from 2700mb to 3500mb. In the HWGSIPartition program, I got errors, as I understand it in section B, but in the end everything went well.I wanted to ask you how much you can increase the system partition, in the HWGSIPartition program, there is a figure of 5GB.
Click to expand...
Click to collapse
Hi great dragon
I have fix errors, in my build of yesterday. To correct on your phone, just flash preavs, preas img in your twrp.
You can also flash with dd tools

The preavs, preas partition are not use in aosp or lineage since android 11. You can also make dload reset to restore huawei stock rom and try last release of my tools

For the size of system, it depend if you use erofs gsi or ext4, or ext4 share block

thank you for an awesome tool. sometimes my stock recovery fails to format but on second attemp it works well. this was a life saving and good relief for huawei device with small system size. now everyone could flash pe a13 etc etc. thank you.

Yes it seems to me that there is a small problem with the formatting, I am testing a version 0.63 which should correct this problem

Hi,
I'm trying to install your LeaOS rom on my P8lite 2017. The phone is unblocked, and I a have already install TWRP. The actually rom is EMUI 8.0.0.410 than I'm trying to reinstall the system partition like you said, before installing your LeaOS.
I saw the Readme.txt where I read than I have to run a script by cmd. I guess it works on Windows system. I'm a Linux user, so I wonder if this script could work on Linux?

RickeF said:
Hi,
I'm trying to install your LeaOS rom on my P8lite 2017. The phone is unblocked, and I a have already install TWRP. The actually rom is EMUI 8.0.0.410 than I'm trying to reinstall the system partition like you said, before installing your LeaOS.
I saw the Readme.txt where I read than I have to run a script by cmd. I guess it works on Windows system. I'm a Linux user, so I wonder if this script could work on Linux?
Click to expand...
Click to collapse
Script is only a dos script, but you can adapt it to bash syntax

Thank for your answer. I'm not familiar with this exercice. I will looking to do that.

Having had terrible experiences in the past resizing the partitions on my Mediapad M5, I am a bit afraid of trying your tool. Has anyone tested it on a Kirin 960s CMR-W09 with android 9/EMUI 9.1.0?

Hello, I've made it to the "5-FlashIMG.cmd" but I can't find that script to execute in the download folder up above. I'm new to this so its most likely I missed something.
I'd appreciate some help!

What files are there in HW and HW-IMG?

*Edit I figured it out. I'm just unexperienced.
Thanks AltairFR for quick reply again. Cheers

!Solved
the script got stuck in middle, asking for yes or no input. after that device is unable to boot or even restore from e-recovery. is there any way to revert the changes done by this script?

abhinavprateek said:
!Solved
the script got stuck in middle, asking for yes or no input. after that device is unable to boot or even restore from e-recovery. is there any way to revert the changes done by this script?
Click to expand...
Click to collapse
You can effectively restore from E-Recovery or with dload method.
But do you have log ?
Original img are in the HW-IMG folder..perhaps just flash it with twrp or fastboot cmd

AltairFR said:
You can effectively restore from E-Recovery or with dload method.
But do you have log ?
Original img are in the HW-IMG folder..perhaps just flash it with twrp or fastboot cmd
Click to expand...
Click to collapse
used dload to flash and revert the changes. for some reason, HW-IMG folder didnt get created
no logs unfortunately, will get it when I try it next time

Hello, can this tool be used on my Honor 6x (BLN)？Because the system of this phone is too small, only 2457MB, I can't flash dotos, thanks!

Problem with TWRP on Ulefone power armor 13

Hi everyone
I've been trying to install a few different GSI ROMs on my Ulefone power armor 13 and after getting nowhere with ADB/fastboot I swapped to trying via TWRP.
After some trial and error I managed to get it installed along with rooting the phone with magisk but the system partition I wasn't on list in the the advanced wipe or install image sections. I've tried most of the things I could find online to resolve it but nothing's worked.
Does anyone have an idea what could be the matter?
One other piece of info, system does show up in the mount section but there isn't a tick box for read only or read write as some of the help articles mention.

Star_Eagle said:
Hi everyone
I've been trying to install a few different GSI ROMs on my Ulefone power armor 13 and after getting nowhere with ADB/fastboot I swapped to trying via TWRP.
After some trial and error I managed to get it installed along with rooting the phone with magisk but the system partition I wasn't on list in the the advanced wipe or install image sections. I've tried most of the things I could find online to resolve it but nothing's worked.
Does anyone have an idea what could be the matter?
One other piece of info, system does show up in the mount section but there isn't a tick box for read only or read write as some of the help articles mention.
Click to expand...
Click to collapse
Do you can link from the twrp img file you tried?
You know about Android 10+ with super partition in RO mode?
So that's cannot modified super partitions (system;vendor;product).
TWRP can mount supeqr but without modified RO to RW mode so that's not apply your choices.
Try this:
Thread '[MAGISK][TWRP][ARM32/64][A8+]Universal Read Only to Read Write for android (RO2RW) | Auto converting SUPER "system partitions" to read/write mode' https://forum.xda-developers.com/t/...system-partitions-to-read-write-mode.4521131/
[Closed] Universal SystemRW / SuperRW feat. MakeRW / ro2rw (read-only-2-read/write super partition converter)
Welcome to the one and only, the original, universal, System-RW / Super-RW feat. Make-RW / ro2rw (read-only-2-read/write super partition converter) by lebigmac Also known as: THE-REAL-RW, FULL-RW, EXT4-RW, EROFS-RW, EROFS-2-RW, F2FS-RW...
forum.xda-developers.com

Hi lopestom
Thanks for taking the time to help a lost noob, I got the img files from here https://forum.xda-developers.com/t/...ith-trp-recovery-and-magisk-included.4351643/.
There wasn't much choice and getting something from an XDA forum thread seemed the least sketchy option.
I had heard/read about super partitions but not the full extent of what needs to be done to access it, most of the how to guides I found online did not mention the extra work.
thanks again for the help

Star_Eagle said:
Hi lopestom
Thanks for taking the time to help a lost noob, I got the img files from here https://forum.xda-developers.com/t/...ith-trp-recovery-and-magisk-included.4351643/.
There wasn't much choice and getting something from an XDA forum thread seemed the least sketchy option.
I had heard/read about super partitions but not the full extent of what needs to be done to access it, most of the how to guides I found online did not mention the extra work.
thanks again for the help
Click to expand...
Click to collapse
You only want install GSI?
You can install with stock recovery & fastboot/fastbootD.

I thought that was the case but every attempt I've made has ended with the phone blowing raspberries at me.
The two possible reasons I can think of are either I'm doing something wrong or theres something about the phone that the image file doesn't like.
The first seems quite likely as this is my first time trying this and the second seems possible given that its using a mediatek chip and it seems to be an obscure choice for people to support.
I've also tried to install using TWRP instead of stock recovery but that's not possible as the system partition doesn't show in the wipe menu

Star_Eagle said:
I thought that was the case but every attempt I've made has ended with the phone blowing raspberries at me.
The two possible reasons I can think of are either I'm doing something wrong or theres something about the phone that the image file doesn't like.
The first seems quite likely as this is my first time trying this and the second seems possible given that its using a mediatek chip and it seems to be an obscure choice for people to support.
I've also tried to install using TWRP instead of stock recovery but that's not possible as the system partition doesn't show in the wipe menu
Click to expand...
Click to collapse
I not know What TWRP file you flashed.... I think is not from me.....
I hope you have unlocked bootloader. You can use stock boot.img ( called ramdisk-recovery) to install any GSI file. What you need know: the size of the stock system. If GSI.img have size more than the stock system, format product partition can solve that. But if not solve so need resize GSI.img or increase the stock system partition.
For install GSI so search arm64 ab files. Look about fastboot & fasbtootD mode. Read this for example: https://forum.xda-developers.com/t/...om-rom-on-a-blu-g90-pro.4253737/post-84737393
Spoiler: Install GSI
Looking for a walkthrough on installing a custom ROM on a BLU G90 PRO
I need WIFI calling enabled and non of the unlocked phones they sell at Best Buy or Amazon come with the feature activated. It is literally not listed in the settings I am looking at installing a custom ROM with WIFI calling activated like it is...
forum.xda-developers.com
If you using the TWRP from https://forum.xda-developers.com/t/...ith-trp-recovery-and-magisk-included.4351643/
so I can't help because very users as https://forum.xda-developers.com/t/...ery-and-magisk-included.4351643/post-87413379
not know about new structure mode in Android 10+
My TWRP has all fixed and funcional (encrypt/decrypt need change fstab file in vendor.img \vendor\fstab*). But I not put here on xda. You can find that in my github profile and Ulefone Power Armor 13 released file repository.
But as I wrote you not need TWRP for install GSI.
Good lucky............