Develop Bugs

[Q] Hboot 2.02 and /system/ partition size

My old evo decided to commit suicide
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyway got a new evo in, trying to get it rooted. Got as far as getting S-OFF which seems to be important:
Supersonic EVT2-3 SHIP S-OFF
Hboot 2.02.0000
Click to expand...
Click to collapse
Flash MISC, run the pc36img. Everything seems sane, then i do the rageagainstthecage exploit again, load on a recovery image. as soon as i reboot to recovery my /system/ partition size gets cut in half and then i can never boot again because random files are missing. Also flashing images fails because half the files dont copy. same with nandroid restores.
results from df before:
/system: 358400K total, 270140K used, 88260K available (block size 4096)
results from df inside recovery after mount -a
/dev/block/mtdblock4 179200 131460 47740 73%
Click to expand...
Click to collapse
I cant seem to find anyone else with this problem, ive tried it several times with different recovery images. WTF am i missing?

Have you tried unrevokeds unrooter? I used it when i got my second evo with 2.2 on it and i had no problems. Maybe the root method is causing the problems.

I had the same problem. I ran RUU using fastboot and it restored me to stock.

Same issue...
I was able to get su with hboot Super one click.. I can post a place to download if needed. My issue is with the crappy quality of this hardware ver (003) my wife has the original and i love it.

also
I also cannot get any roms to load... I used the traditonal push with no success... Although i have noticed on significant thing that seems to keep happening.... its always fails with the boot.img. I tried loading Fresh through the Rom manager and all it would do is kick me to recovery.... try to do it manually and all roms fail on the boot img.

Help with SD bug of 4.2

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm a little confused here with this one. I have all the contents of my sd card at 3 places. As you can see I have SDcard0 and emulated and inside emulated I have 2 folders 0 and legacy all 3 folders contain the same 55 items which are the contents of my SD. Which ones I have to delete? I have the same free storage as before so the files aren't duplicated.
Sent from my Galaxy Nexus using Tapatalk 2

They're symlinked, don't delete any of them.
Google has made a little bit of backward compatibility is all, it has the files where Google wants them, and then has places they've previously been linked to that so that old programs don't break and the files still go where they belong.

This stuff is just symlinked behind the scenes. Just use /sdcard as allways, which will show all the files as well.
And no it has nothing to do with support for legacy apps(as mentioned these allways just refer to /sdcard). This has to due with the addition of multiple users on Android tablets, and hench the filesystem will need to make place for several storages with one for each account.(with you being the only user, number 0 in this case)
And no do not touch any of them..

Well... the symlinking was in there long before 4.2, it's on every data media device since Honeycomb. It does serve the function of legacy app control, or more accurately, it serves the function of making data media devices compatible with SDcard devices. It seems Google is putting it to further use by having multi-user symlink /sdcard to the /data section that belongs to the current user.
http://teamw.in/DataMedia
EDIT: sorry this was kind of off topic. The short answer being that it's like that for a variety of reasons and it's ok for it to do that.

Thanks for the replies. so if i change something to any of these folders the other 2 will change as well?

arvylas said:
Thanks for the replies. so if i change something to any of these folders the other 2 will change as well?
Click to expand...
Click to collapse
yes. any changes you make in one will reflect in all

Can't recover all my formatted stuff.

Hi guys this is my first post in xda developers but i've always solved my troubles with your help. But now i really need to expose my problem, cause actually i can't find a solution even if there are many posts about it.
I changed my clockworkmod from 6.0.1.0 to 6.0.4.5 to flash a 4.4 android version rom on my galaxy w.
everything went okay, i guess but i had some issues with photo gallery (kinda everything duplicated, so i had a bunch of ''useless-double-files'').
One day later I decided to go back to my 4.0 rom and here the mess begins. I tried a restore from cwm but i couldn't because there was an error about restoring /data (but there's still the recovery date in that list) so I re-flash the 6.0.1.0 cwm and the 4.0 android rom, but when i turn off my phone all my pictures was GONE.
I plug my device to my computer and it says that the available space is almost full, like when the mess wasn't happen, but when i browse the pictures i can't find them. :crying:
I tried this and everything goes til this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(even if my .raw is only 8mb???? )
edit: i looked up in partitions of my phone here and i re-did all this but downloading mmcblk0 instaed of mmcblk0p12 that was only 8mb. this is goin over 1,80 gb. is this the correct partition?
how can I turn .raw file in files?
Please help me guys, i literally waste my all day.
(Sorry for my bad english tho)

(sorry for double posting) i've got news..
i finally got my .raw / .vhd files. they are
mmcblk0p28 (that is my mnt/sdcard stuff 1,7 gb like my internal storage phone is. it's 100% full but i didn't find much.. only small pictures)
mmcblk0p17 (that is /data and i find not much pictures in this)
then i tried mmcblk0 that was the largest file (the whole phone i guess?) but when I attach it as a vhd in disk management it comes already partitioned and allocated. what does it mean??
should i give up? i will never get my pictures back? :crying:

Question Need to restore photo editor app

Hi all,
I have deleted default photo editor in my A52s 5g phone using adb because I want to install photo editor from elsewhere which may support object eraser which the default app was not supporting.
Since then, i am not able to install it back and get the error message as shown in attach images. I have tried apk mirror and tried to install same version number.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The same photo editor app is working fine in secure mode. The version i can see there is 3.1. 09.41.
I'm using Android 13, One UI 5.
Kernel version
5.4.147-qgki-25280849-abA528BXXU1DVK5
#1 Thu Nov 10 10:56:13 KST 2022. Build number
TP1A.220624.014.A528BXXU1DVK5.
Is there any method with which I can install/restore get this photo editor app?
Thanks for any suggestion/help!

It's not deleted so you can reinstall it. Enable it with the correct ADB command. Or a factory reset will purge the ADB edits from the user partition. The app still resides on the rom, it's simple not loading at start up.

blackhawk said:
It's not deleted so you can reinstall it. Enable it with the correct ADB command. Or a factory reset will purge the ADB edits from the user partition. The app still resides on the rom, it's simple not loading at start up.
Click to expand...
Click to collapse
Can you please tell me the adb command to enable it back? Because I can't afford to factory reset the phone.
Thank you!

nitin29 said:
Can you please tell me the adb command to enable it back? Because I can't afford to factory reset the phone.
Thank you!
Click to expand...
Click to collapse
No clue, sorry. I run a Package Disabler instead.
Some others here likely know though. Try this thread.

Thanks again for giving a clue in your previous comment that the apps still in the rom and it is not completely gone from the phone and correct adb command can bring it back. With that, I searched more and found a video how to do it correctly and photo editor is back...finally!
For those who are in same situation, the adb command in the adb shell:
Code:
pm install-existing package
where package is name of the app, in my case it was: com.sec.android.mimage.photoretouching
The post can be marked solved now by admins.

Question 70GB system space

Hi. Anyone know why latest OneUi 5.0 takes 70GB system storage?
I believe that system should take about 10-15GB like clear Android 13 (Mi9T Pro - 12GB, MiPad 5 - 16GB), but not 70.
Anyone know what is happening in the system directories?
Spoiler: Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Mine says 39gb so I think both are wrong

I have mine at 106GB, wiping cache didn't do anything.

Mine is extremely debloated, I wonder if that has anything to do with mine being so low comparatively...

spart0n said:
Mine is extremely debloated, I wonder if that has anything to do with mine being so low comparatively...
Click to expand...
Click to collapse
I have the standard A13 ROM from Samsung (not debloated) and it's 40GB.

~63 Gb after the last uodate

19 gb after december update
everyone with more than 25 gb sistem files please try file guardian GL module to clear old android sistem files

AndrOmega said:
guardian GL module
Click to expand...
Click to collapse
Is it a magisk module?

goodlock module is it

Nevermind

Tempus Fugit

I trust the OS. As long as I have a lot of free space, I don't care how much the system takes.

Is there another vesy to remove old system files? Why are they there, short of a system recovery?

annson08 said:
I have mine at 106GB, wiping cache didn't do anything.
Click to expand...
Click to collapse
I tried cleaning my internal storage a while ago and noticed my system storage increased to 110GB, lmao.

Update on this: I did a factory reset to see if it'll do anything.
From 111GB, it went down to 38GB, but after completely restoring all my apps, files and everything, it went back up to 58GB. Not bad considering I freed up 50GB+.
I suspect the reason my system files bloated like that is because I have a habit of flashing roms without wiping, especially when the beta came out.