yashsingh1/xdaforums huggingface dataset:
[Magisk] jututt:
I renamed the old toybox, so I could restore it from recovery.

Btw, I get this with ls -lZ

-rwxr-xr-x 1 0 2000 ? 825176 2023-01-29 07:34 /system/bin/toybox

Seem to have lost context there.

Thanks for your quick replies.
[Magisk] alecxs:
either you're on Jelly bean or you lost secontext. repair with chcon

chcon u:object_r:toolbox_exec:s0 /system/bin/toybox
[Magisk] jututt:
You are right, new toybox does not have specific Android applet, like chcon or restorecon.

So, please correct me if I'm wrong, I reboot in TWRP, restore old toybox.

Then should I run chcon / restorecon or reboot straight away?

I lost secontext in all root dirs /, /system, /vendor, /sdcard...
[Magisk] alecxs:
not sure what ROM you're talking about. maybe you used ls of wrong toybox?
[Magisk] jututt:
Don't understand your answer, what ROM are you referring to?

If I ./"toybox old" restorecon I get restorecon: Needs 1 argument (see "restorecon --help")

If I restorecon I get toybox: Unknown command restorecon (see "toybox --help")

Please advise me if it's right to restore old toybox via TWRP and reboot to system or there's the need to chcon / restorecon, thanks
[Magisk] alecxs:
please give the output of

grep ro.build.fingerprint /system/build.prop /system*/system/build.prop

it's very unlikely you lost every secontext. either it never existed or you just can't view.

restorecon won't help you much. only restoring TWRP backup could restore secontext as it was before.
[Magisk] jututt:
grep ro.build.fingerprint /system/build.prop

ro.build.fingerprint=Xiaomi/cepheus_eea/cepheus:10/QKQ1.190825.002/V11.0.9.0.QFAEUXM:user/release-keys

ro.build.fingerprint_real=Xiaomi/cepheus/cepheus:10/QKQ1.190825.002/20.7.2:user/release-keys/1593694646
[Magisk] alecxs:
so your ROM is stock ROM Android 10 it must have secontext of course. in case it's true you lost every secontext best is download cepheus_eea_global_images_V11.0.9.0.QFAEUXM_20200421.0000.00_10.0_eea_31715f4bd1.tgz and flash_all_except_storage.bat

(you can backup boot in TWRP beforehand and flash boot.emmc.win from fastboot right after)

edit: build.prop usually is in /system(_root)/system/build.prop on new devices, so most likely what you think is build.prop is just from the TWRP image used.

maybe you didn't mount System?
[Magisk] jututt:
Resolved

Rebooted into TWRP, restored original toybox, deleted my symlinks, checked secontexts ok, rebooted to system, all fine.

Thank for your support
[Magisk] alecxs:
you can place toybox in /data/adb/modules/toybox/system/xbin/toybox, make a diff and only symlink missing applets in there.

then create modules.prop, reboot and done.
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] rehfore:
What do you guys think, would it be worth it to buy this from ali express for much cheaper? They say some things are not supported but shouldn't they work with magisk?
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] XDRdaniel:
This is s30 not x30
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] rehfore:
true, this is the x30 pro though, could be still worth no?
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] Killuminati91:
You can get it cheaper from tradingshenzhen, bludiode or wondamobile. But not worth 600€ imho. Id rather go for the Oneplus 11 at that price.
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] tute123456:
You should check the seller's review, ratings, store verification and others
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] blackhawk:
I wouldn't trust making a purchase this large from that company. caveat emptor.
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] keaheng:
Got x30 pro brand new from AliExpress for $480. Immediately flash eu rom. the best deal ever.
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] XDRdaniel:
It's fine, I multiple phones and tablets from them. Just pay with PayPal if you want to be sure
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] tute123456:
What is the advantage of paying with PayPal instead of using a credit/debit card?
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] blackhawk:
You can do charged backs with Visa and MC, no problem over the phone.

I boycott woke Paypal and the raw deals its handed out to some of it's conservative customers. They screwed me over 10 years ago. Don't feed the beast.
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] XDRdaniel:
Quick refund
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] tute123456:
thx
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] rehfore:
any drawbacks? does everything work normal?
[Motorola Edge 30 Ultra / Motorola Moto X30 Pro] blackhawk:
Well here's a satisfied AE customer... not.

Resolution, if any... pending.
[Introductions] phils80:
Hi I'm Filip from Poland, registered to find some support with my Asus Zenfone 8, but hoping also to help others and find interesting information.
[Introductions] galaxys:
Welcome to XDA and enjoy the forums!🙂📱💻

Cheers
[Wing, P4350 General] Ronboi3:
is there anyway u can get the gettin started cd software from over the internet or do u just have to get the cd like everytime i connect my phone to the computer through usb it asks for a cd i dnt have so is there a back door or something :confused:
[Wing, P4350 General] Mooberry:
All you should have to do is install Microsoft Activesync on the PC and you should be good to go.
[Realme X7 Max 5G] necroblazer9029:
Hey guys. Could someone explain to me the procedure to install the Realme X7 Max 5G rom on my Realme GT Neo FE? I already unlocked the bootloader, what's the next step? And which rom exactly should I download to do this? Which program should I also use?
[Samsung Galaxy Tab S5e Questions & Answers] Montisaquadeis:
Here is the deal both Google and System UI crashed on my S5e last night while I was reading and now I am unable to reboot/power down the tablet using either the Power button or the onscreen controls. As you can see it is just the 2 onscreen buttons that I get and n othing happens expect they dissapear when I try and tap either. Also I am unable to use ADB in this sitution to force a reboot/power down as can be seen in the second image. At this point I am at a lost on what to do besides wait for the tablet battery to die which in its current state could take days if not a week+ considering that nothing is showing up.
[Samsung Galaxy Tab S5e Questions & Answers] blackhawk:
You try a 20+ second long press on the power button (if that's correct for that model) to do a hard reboot?
[Samsung Galaxy Tab S5e Questions & Answers] Montisaquadeis:
Yes I have I have held the button for a bloody minute aka 60 seconds and no reboot/poweroff
[Samsung Galaxy Tab S5e Questions & Answers] blackhawk:
The only other thing you can do is physically disconnect the battery or wait for it to discharge.

If you get it to reboot go into safe mode and backup all critical data. Then factory reset.

If that fails it will need reflashed or the hardware issue causing it fixed.
[Samsung Galaxy Tab S5e Questions & Answers] Montisaquadeis:
That is what I thought and as I said it can take up to a week+ for this to discharge since it was nearly full when it happened
[Samsung Galaxy Tab S5e Questions & Answers] blackhawk:
If you used a SD card as a data drive and it's not encrypted at least the data can be salvaged.

It may not be as bad as it looks but I'm thinking a mobo failure. I've never seen this type of behavior with any of my Samsung's.

Recertified ones can be had for $200 or so but will likely be upgraded to the latest OS version for it. If you're running on Pie you may not like it.
[Samsung Galaxy Tab S5e Questions & Answers] Montisaquadeis:
I bought this one for $275 back in 2021 and ended up receiving a used one when Amazon said it was suppose to be new so yeah something like this was bound to happen sooner or later
[Samsung Galaxy Tab S5e Questions & Answers] blackhawk:
I would've returned it. I use one vendor where I got a new N10+ a little over a year ago. His prices aren't real low but he's trustworthy. Their price is $600 for your model. He buys lots of unsold new devices. There's lots of scamming going on, something I noticed when I was shopping.
[Samsung Galaxy Tab S5e Questions & Answers] Montisaquadeis:
Apparently you have to hold power and volume down to force power off a Samsung device so you missed a step there. Also the tablet seems to be working fine now after doing so
[Samsung Galaxy Tab S5e Questions & Answers] blackhawk:
Correct. Hard reset is both buttons; something I never have to use. However long pressing just the power should force it to shut down.

Try clearing the system cache from the recovery menu.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Flominator:
reserved
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
Hi Flominator

First off, thanks for working on custom ROMs for the A3. It's my favorite phone even if hardware limitations have forced me to switch model. The upshot is that I (almost) no longer care about bricking the A3.

As such, I have tried installing this ROM, but I have failed. I hope you're willing to help with that.

I have the A320FL as far as I know.

I have tried installing your ROM, taking the following steps:

1) Started on the LineageOS 17.1 build from MartinYTCZ, latest version maintained by someone else now, so not Stock Oreo. Started from Orange Fox recovery

2) Flashed the repartition script from the link above, converting me to TWRP.

3) Formatted Cache, Vendor, System, Data by switching file system to ext3, then back to ext4. Can't seem to find an easy way to make it redo ext4 without going that route.

4) Running your installer from TWRP.

I get an error message about failing to patch system image almost instantly. Of course, I was too dumb to write it all down before flashing back to what I had before, but I can go over it all again and upload logs if you would like.

If it's about not coming from the Stock Oreo, do you know anywhere I can get that as a backup rather than for USB flashing? I no longer have Windows at home, so I can't really get at ODIN without a lot of hassle.

Otherwise, is there anything else I may have missed?

I am willing to work with you and try things if you want me to. Like I said, I (almost) don't care about bricking the device by now.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Flominator:
1. Big thanks, for reporting this to me

2. you already where on a treble recovery with orangefox before (if you still have orage fox image you coud revert to orangefox), (I shoud mark Instuctions more clearly in thread above)

3. now you have to select Cache, Vendor, System, Data each by Itself and by changeing back to ext 4

after that normal install instuctions shoud work

from now on

If you still get issues get back to me :)

best regards Flominator
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
I have verified that system, vendor, data and cache are all ext4 file system (As mentioned in my previous post, I switched to ext3 and then back to ext4 to force format).

Attached is a log of an install attempt. I hope that can shed some light on why it's not working. Something to keep in mind may be that my current Android has changed partition sizes along the way. I also get issues immediately after using the repartition script linked above though, so that may not be the issue.

EDIT: I cannot attach, so here goes as spoiler:

Spoiler content hidden.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Flominator:
after repetition script was run data needs to be formated, as listed in instructions by Astrako, did you do that?

If you still get issues you can try my personal TWRP image for installation. It handles PATITIONS way better, than the old orange fox and twrp.

Downloads for : Samsung Galaxy A3 (2017) | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

androidfilehost.com
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
I'm sure I did format data, cache, system and vendor. I have now tried again. Flashed repartitioner, rebooted, formatted the partitions data, vendor, cache, system, then rebooted, then tried your installer.

Edit: Just downloaded and verified that the files I'm using aren't corrupted (repartitioner and your installer)

Edit: Clarified exactly the order of what I tried.

Spoiler content hidden.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
Also, just noticed your plug for your TWRP image. There was some trouble where repartitioning with the repartitioner, then installing your TWRP, then formatting wouldn't let me do anything with /data. Repartitioning, then formatting with that TWRP, then installing your image, then formatting ext4 again with your image, then running your installer gave the following log:

Spoiler content hidden.

By the way, your TWRP image seems to have a problem with MTP where I can see the two root folders, (Internal and Micro SD), but as soon as I try listing files from them, the entire mount drops. I have the same problem with the latest Orange Fox, but not with the older TWRP 3.3.1-0 from the repartitioner script. I'm using gvfs-mtp and gio, not that I expect you to do anything about it. :)
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Flominator:
That seems about fine, Ill take a look at mtp, Still don't get why the error with patitions. So I am asking if you coud provide a step by step guide that lead to error with messed up patitions, so I can replicate too and find a fix for that softbrick. That others don't get the same error, as I never encountered it.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
It turns out that the error I got trying to format was from the partition script for installing the LineageOS that I had before, I must have fat-fingered the wrong script. Still odd since it worked when I originally installed that ROM. Now I wanna find out why that happens. It's possible, I guess, that the error is because the script expects another starting point (There were a few repartitions in the chain of upgrades on that ROM). Seems like running that repartition script again fixed it, or maybe it was dropping to ext2 instead of ext3, then back up to ext4? I dunno. Will do more attempts at getting a consistent path to the error, or getting your ROM installed later.

So far, thanks a lot for your help with trying to get this to work.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
From some poking around in the logs and googling, I have found some posts which seem to indicate that the size of the system partition may be wrong? According to TWRP, my system partition is 2396MB with the partitioner for the other ROM and around 1500 with the partitioner you linked. Can you tell me if that seems usable?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Flominator:
Use the patitioner for the other rom then 1.5 GB is too less I guess, (tell me if if it worked with yours and ill will link it instead of original Astrakos ones, so no one have to fixup their patitions after).
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
It's not working with that one either. Is there any way that I can play around with partition sizes?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
The partitioning script for the LineageOS ROM was very well structured and easy to modify to make a 3000MB system partition, after which I can apparently patch system in there. Now vendor is failing. I'm going to try playing with that size as well.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
Oh man. This hole is deep.

Here's where I'm at: I've got the system partition installing on 2900MB. I don't know for sure, but from looking at the scripts, I'm guessing that's the appropriate size. What is your System partition size where you have successfully installed this ROM?

Anyway, I didn't understand why I couldn't get Vendor to resize properly. By my rough guesstimate, 440MB should fit your ROMs vendor. But nothing I did would make it resize from 160MB. It turns out that sgdisk lists between 15 and 20 partitions for Vendor, some of which are smack in the middle of other partitions. Now I gotta figure out how to clean those up. Probably gonna be a bunch of very shaky-handed manual sgdisk work. I almost don't care about bricking... Almost...

I'll let you know how that goes. Anyway, what are your partition sizes, in MB and in sectors?
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
Oh man, that was a trip.

At some point in my various custom ROM installations, some repartitioning script has created a double vendor partition. I suspect that the one you link to adds one blindly, and I've run that more than once. Other scripts, like the one for the Lineage ROM, that I've been modifying here, will check for Vendor partition and delete it if it's there. But this one, at least, only works if there's ONE vendor partition, not multiple. With multiple, it also just adds a new Vendor partition. That's how I ended up with all of those vendors. I rewrote the script to clean up all rogue vendor partitions, and now I can play with partition sizes. It also freed up some 6+GB of storage that I didn't understand where had gone.

Along the way, I had some oversights and accidentally removed my system partition entirely, so now I'm unsure whether I have the right partition code for it when I recreated it. I would be much obliged if you could let me know your partition code for the system partition.

However, at the end of it all, I've gotten your ROM isntalled! Yay!

I got it installed with the following raw sizes for system and vendor partitions:

System: 2900MB

Vendor: 440MB

Like I said, my estimate is that Vendor needs to be that big, but I would love to get your raw sizes if possible. Really, just the output of the command "sgdisk --print /dev/block/mmcblk0" would be very helpful.

I hope all of this helps you or someone else. Later today, I will see about playing around with the actual ROM, for now I need a break. I am willing to help you with other stuff, testing and such if you need it.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Flominator:
Thanks a lot! For your patience 😉

BOARD_BOOTIMAGE_PARTITION_SIZE := 33554432

BOARD_CACHEIMAGE_PARTITION_SIZE := 209715200

BOARD_CACHEIMAGE_FILE_SYSTEM_TYPE := ext4

BOARD_RECOVERYIMAGE_PARTITION_SIZE := 39845888

BOARD_SYSTEMIMAGE_PARTITION_SIZE := 2871279104

BOARD_USERDATAIMAGE_PARTITION_SIZE := 54618209280

BOARD_VENDORIMAGE_PARTITION_SIZE := 434596224

BOARD_VENDORIMAGE_FILE_SYSTEM_TYPE := ext4

About patition sizes and file system hope it helps

best gegards Flominator
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
Yeah, those are the sizes that I estimated from the scripts. This still doesn't give me the partition code, though. My System partition currently has code 0700. Oh well, it's working.

I would recommend that you make a partitioning script for this install process, I don't see anyone without quite a lot of technical know how and unix experience doing the partitions themselves.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Flominator:
Is it possible that you can provide your script for patitions? It's a one thing need. I would have to dig up the stuff I once used more then a year ago, when I started android 11 development on a3y17lte 😉 and I know you'res is working fine.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
I am hesitant for two reasons:

1) Copyright/licensing. I've modified the script provided by @TheObcd I think, from the July 2022 release of https://github.com/debie-A320FL/OTA/releases. I haven't checked his licensing terms.

2) Risk of bricking anybody elses device. I just modified parts of an existing larger script. I don't know how it was originally generated. There are parts of the package that I don't understand and therefore haven't touched and cannot vouch for. I don't know if what I did may cause damage on other devices.

Here's what I did: I unpacked the zip, modified the line fetching the Vendor partition number adding a head -1 command between the grep and awk. Then I changed the if on vendor to a while and re-fetched the vendor partition within that loop after delete to clear out any duplicate vendor partitions. Finally, I also modified the sizes declared in the global variables at the top of the script. I can get you a diff later.

I also updated the META-INF script to report my changed target partition sizes. There's also a binary file in there. I don't know what that does.

Then I zipped it up again and ran it on the phone. Seemed to work.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
I guess if we could get him to implement those changes and release them, that would be a boon for his stuff, and then you can reference that.

EDIT: I guess he wouldn't have the sizes your ROM requires.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
Here's the diff of his repartition script (extracted zip file) and mine:

diff -r old/META-INF/com/google/android/updater-script new/META-INF/com/google/android/updater-script
34,35c34,35
< ui_print(" SYSTEM: 2500MB");
< ui_print(" VENDOR: 160MB");
---
> ui_print(" SYSTEM: 2900MB");
> ui_print(" VENDOR: 440MB");
diff -r old/repartition.sh new/repartition.sh
20,21c20,21
< SYSTEMSIZE=2500
< VENDORSIZE=160
---
> SYSTEMSIZE=2900
> VENDORSIZE=440
36c36
< VENDOR=`$SGDISK --print $DISK | grep VENDOR | awk '{printf $1}'`
---
> VENDOR=`$SGDISK --print $DISK | grep VENDOR | head -1 | awk '{printf $1}'`
53,54c55,56
< if [ ! -z $VENDOR ]; then
< VENDORPART=`$SGDISK --print $DISK | grep VENDOR | awk '{printf $1}'`
---
> while [ ! -z $VENDOR ]; do
> VENDORPART=`$SGDISK --print $DISK | grep VENDOR | head -1 | awk '{printf $1}'`
56c58,59
< fi
---
> VENDOR=`$SGDISK --print $DISK | grep VENDOR | head -1 | awk '{printf $1}'`
> done

I left the vendor partition cleanup in there. I could definitely see other people having flashed repartition scripts repeatedly trying to install something and ending up with a bunch of vendor partitions like I did.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] TheObcd:
The script has been made by @Astrako and shared intially in his post.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
Thanks! Well that indicates that the changes I have made are safe. He only recommends changing the partition target sizes, so it is apparently safe to do nothing else. The multi-vendor cleanup is safe as well, as far as I can tell. Maybe I should mention the option of updating the official script with that in that thread.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Flominator:
Thread is updated with some more details about instructions, that hopefully pervent people, from falling in the pit messing up their patitions
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
I think the best instructions would be to get on the latest treble-capable recovery, then point them towards the thread pointed at by TheObcd with the sizes necessary. That script is safe to use unless the partitions are already messed up.

Now that I have (tried to) set up my phone as I would have it if it were my daily driver, I have noticed two features not working:

1) Adaptive charging - It happily charges beyond the stated max charge.

2) LiveDisplay cannot be turned on. The mode picker will reflect my choice, but settings will remain grayed out, and when I leave and come back, the picker is back to "Off".
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Firngrod:
Also, lock screen auto rotation cannot be toggled separately from auto rotation in general. I cannot get it to not auto rotate if auto rotate in general is on.
[Samsung Galaxy A3, A5, A7 (2017) ROMs, Kernels, Re] Flominator:
I look at roms featuresets soon

auto rotate shoud be fixed now

not loading livedisplay too (dont expect all modes to be working for now, enabled all avaiable ones for now)

about Adaptive charging I have to do some fruther debuggig