Database Info

My 577W got virus?

found out alot of my files on my storage card got renamed with "0da5aa84.menc" attached at the end of the file...is it a virus???
i tried to rename back to the original file but the file is not accessible after renamed....anyone faced this b4??? pls help...

allic said:
found out alot of my files on my storage card got renamed with "0da5aa84.menc" attached at the end of the file...is it a virus???
i tried to rename back to the original file but the file is not accessible after renamed....anyone faced this b4??? pls help...
Click to expand...
Click to collapse
Poor you, you must have set Encryption in the security options

i think i have enable that b4 ...i just perform the format and upgrade of the rom ...so...anyway to restore back the encrypted files??

Well, try to get back the original file name and remove the encryption

karhoe said:
Well, try to get back the original file name and remove the encryption
Click to expand...
Click to collapse
the file name is there..Eg. Filename.txt.0da5aa84.menc
so if i just remove the 0da5aa84.menc and remain the Filename.txt.. i still cant open the file. I've disable the encryption in the Security already but still the same. Any idea?

Full System Dump SM-G950N

To start this off I DID NOT extract this. I am just re-uploading a file I found on this forum. This contains everything for the S8's system. I also have some links to ODIN files from
The 3rd link from Mega and google drive contain EVERY system file. This is every APK and the framework-res.apk. This also has all the fonts and Cameradata and the new over the horizon song.
https://forum.xda-developers.com/showthread.php?t=3583672
I DO NOT TAKE CREDIT FOR ANY OF THIS. I am just making a thread to put all relevant links in one place.
SM-G950F ODIN:
https://www.androidfilehost.com/?fid=817550096634760122
SM-G955F ODIN:
https://www.androidfilehost.com/?fid=457095661767151824
SM-G950N SYSTEM:
https://drive.google.com/drive/u/0/folders/0B5lROw49g7TXam1GcHdEeDMzTWs
https://mega.nz/#!AUkBjLaB!eUxhyqXheS8bKn0EZRiSNs1tJR9Bnmhjhh0tlCWyuuk

Odin flash ?

hasanben35 said:
Odin flash ?
Click to expand...
Click to collapse
the SM-G955F and SM-G950F are both ODIN files for the S8 and S8+ for the UK.

thanks price s8 plus korean versıon 6 gb ram paid flash rom

Can someone just upload just the system/fonts folder please?

How do I extract the apps in the dump when it's odin files

milojoseph said:
How do I extract the apps in the dump when it's odin files
Click to expand...
Click to collapse
I was not able to get it, use sgs2toext4.jar. It was not working for me. In the .md5 of the odin file use winrar to extract the system.img file and put it into sgs2toext4.jar. It would work to give you an image to mount. I was not able to get it to work. Try using the last link i posted because it contains 99% of the system.

Uh oh, looks like the archive is corrupted. Can't extract w/ 7zip win 10

Mattwmaster58 said:
Uh oh, looks like the archive is corrupted. Can't extract w/ 7zip win 10
Click to expand...
Click to collapse
I used winrar and it was fine.

I have a question, can I install the firmware from SM-G950F to the SM-G950N? I have 5 file versions of firmware from SM-G950F which has polish language. Or maybe there is another method for uploading firmware with Polish menu and without brand?

Need Help With Magisk Boot Patching

I want to be able to root after erecovery and update to latest version. I know magisk can patch boot img for reflashing via fastboot.
Question is, how to extract original boot img?
I know there are tutorials, but they reference specific block that seems to be device dependent. Or am I making it too complicated?

papashex said:
I want to be able to root after erecovery and update to latest version. I know magisk can patch boot img for reflashing via fastboot.
Question is, how to extract original boot img?
I know there are tutorials, but they reference specific block that seems to be device dependent. Or am I making it too complicated?
Click to expand...
Click to collapse
You need the UPDATE.APP for the boot img.
You can find in Huawei Firmware Finder for your Version,download the Update.zip and unzip,inside is the UPDATE.APP.
Extract UPDATE.APP with Huawei Extractor https://forum.xda-developers.com/showthread.php?t=2433454
Copy extracted Boot on your Phone and install Magisk and Patch the File
The patched File save Magisk on internal Memory,copy on your Pc and flash via Fastboot.
Your Bootloader must be unlocked!

Thanks for the run down. I'll give it a go.

Looks like I need a note 10 profile for Huawei extractor. Anyone have that available?

papashex said:
Looks like I need a note 10 profile for Huawei extractor. Anyone have that available?
Click to expand...
Click to collapse
Do you have errors while unzipping?
Use this setting!

letschky said:
Do you have errors while unzipping?
Use this setting!
Click to expand...
Click to collapse
Yes, that's what I use with the unknown profile. I receive this error.
EDIT: I downloaded another file 8.2.0.158 and get same error, just different indices. I don't know if it makes a difference but most of the files found in FF are for C00B. My system info shows only C00. Could that be relevant?

papashex said:
Yes, that's what I use with the unknown profile. I receive this error.
EDIT: I downloaded another file 8.2.0.158 and get same error, just different indices. I don't know if it makes a difference but most of the files found in FF are for C00B. My system info shows only C00. Could that be relevant?
Click to expand...
Click to collapse
this generally works with Huawei,i use it with Note 10,Note 8,Honor View 10,Mediapad M3....
is Net Framework 4.6.1 installed on your Pc?

papashex said:
Yes, that's what I use with the unknown profile. I receive this error.
EDIT: I downloaded another file 8.2.0.158 and get same error, just different indices. I don't know if it makes a difference but most of the files found in FF are for C00B. My system info shows only C00. Could that be relevant?
Click to expand...
Click to collapse
Same Problem in 181 ,but in Settings uncheck :
1:Verify header checksum
and
2:Verifiy file checksum

Unchecking the 2 checksum checks you asked me to check opens up the update.app app-ropriately.
(couldn't resist )
Thanks for the help.

Baby stepping is driving me nuts.
I'm able to extract the update.app file but there is no "boot.img" in the several archives I looked at. Does it go by a different name? list attached.

papashex said:
Baby stepping is driving me nuts.
I'm able to extract the update.app file but there is no "boot.img" in the several archives I looked at. Does it go by a different name? list attached.
Click to expand...
Click to collapse
Ramdisk.img

I've finally had a moment to sit down and put it all together. Got my latest stock oreo rom rooted. Feel confident I can do PIE if it ever shows up for me in the US. Thanks for the tutorial Letschky.

As luck would have it, PIE update arrived after tweaking up the rooted Oreo. Ready to root PIE, but there is no "ramdisk.img" in my downloaded 9.0.0.181 archive.
Has the name changed for PIE or is it a bad archive?

How to find/extract/generate the device specific kernel defconfig file?

Hello there, noob here I am trying to compile/build a custom kernel for asus zenfone max pro m1 so i have downloaded the kernel source from the manufacturer website but i see that there is no defconfig file for X00T (my device code name) in the kernel/arch/arm64/configs folder so i tried different available config files but none of it is working... So can anybody please tell me how can i get that device specific defconfig file in order to build a custom kernel for the device?​

xswapsx said:
Hello there, noob here [emoji14] I am trying to compile/build a custom kernel for asus zenfone max pro m1 so i have downloaded the kernel source from the manufacturer website but i see that there is no defconfig file for X00T (my device code name) in the kernel/arch/arm64/configs folder so i tried different available config files but none of it is working... So can anybody please tell me how can i get that device specific defconfig file in order to build a custom kernel for the device?​
Click to expand...
Click to collapse
Have you tried finding the full stock firmware for the device also? If you have the stock firmware file, you might find the file you are looking for in the firmware file.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Have you tried finding the full stock firmware for the device also? If you have the stock firmware file, you might find the file you are looking for in the firmware file.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
Thank you Sir for your kind reply!
Yes, I do have stock firmware but I don't know where is the config file located or where it should be located

xswapsx said:
Thank you Sir for your kind reply!
Yes, I do have stock firmware but I don't know where is the config file located or where it should be located
Click to expand...
Click to collapse
Extract the firmware to access the different parts of the firmware, you can manually search through every folder until you find it or you can use the Windows file explorer's search feature to search the extracted files.
It will take some time but if go through it piece by piece, you'll find it.
There is not always a simple, easy way to do things. Sometimes you have to be willing to put in the time and the work to make things happen. Don't be afraid to do some work to figure it out.
Sent from my LGL84VL using Tapatalk

Droidriven said:
Extract the firmware to access the different parts of the firmware, you can manually search through every folder until you find it or you can use the Windows file explorer's search feature to search the extracted files.
It will take some time but if go through it piece by piece, you'll find it.
There is not always a simple, easy way to do things. Sometimes you have to be willing to put in the time and the work to make things happen. Don't be afraid to do some work to figure it out.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
OK Sir, I will try this!!!:fingers-crossed:

Question Joying 8.8 inch Android 10 JY-HQS01N4G-1 how to root

Has anyone been able to root the new Joying 8.8 inch Android 10 head unit? I’ve searched this forum everywhere and found a couple root files but 2019 release. I’ve attached pictures of my unit builds. I want to change the screen size a bit since it’s a little bigger than my bezel and covers the screen but I am unable to use any resizing apps without root permissions. Any help would be appreciated thanks a lot. JY-HQS01N4G-1
HowTo: Root Joying SC9853i Head Unit
First off a big thanks to the guys at {Mod edit} for doing all the hard work, I'm just writing this post as a guide for those who don't speak Russian - like myself :) Second thanks to all those on the Original Thread...
forum.xda-developers.com

If you have a firmware for your unit, you should use it to extract the boot image from it. Your 1280x480 "might" have a different boot image, although it is more like that this is in the config of the firmware. Building your own always gives you the right version.
Then you can simply follow the steps as mentioned in the document inside the developer.zip.

surfer63 said:
If you have a firmware for your unit, you should use it to extract the boot image from it. Your 1280x480 "might" have a different boot image, although it is more like that this is in the config of the firmware. Building your own always gives you the right version.
Then you can simply follow the steps as mentioned in the document inside the developer.zip.
Click to expand...
Click to collapse
so I should extract the boot image from the unit and just follow the steps mentioned in the developer.zip? So the old files that were posted on the tread I mentioned should work? Im trying my best to figure this out and see if it’s possible without bricking my unit. I just need to change the screen dimensions a little that’s all and I have no idea. Sorry I’m quite new to this.

wojas322 said:
so I should extract the boot image from the unit and just follow the steps mentioned in the developer.zip? So the old files that were posted on the tread I mentioned should work? Im trying my best to figure this out and see if it’s possible without bricking my unit. I just need to change the screen dimensions a little that’s all and I have no idea. Sorry I’m quite new to this.
Click to expand...
Click to collapse
If you have the original firmware, you extract the boot image from the firmware. If you don't have the original firmware: don't try this at all.
And yes: you can also extract the boot image as a raw partition from your unit using dd. But being not epxerienced I would not go that road.
I don't think the boot image contains the screen resolution.
If your system doesn't boot anymore, it will be a "soft-brick". It means that if you have the original firmware you can always flash your unit with that firmware. Reset it with a needle of so.
So make sure you have the original firmware!
Finally: Why do you even want to root your unit? My unit is not rooted as I don't see any added benefit.
For some options you don't need root at all.

surfer63 said:
If you have the original firmware, you extract the boot image from the firmware. If you don't have the original firmware: don't try this at all.
And yes: you can also extract the boot image as a raw partition from your unit using dd. But being not epxerienced I would not go that road.
I don't think the boot image contains the screen resolution.
If your system doesn't boot anymore, it will be a "soft-brick". It means that if you have the original firmware you can always flash your unit with that firmware. Reset it with a needle of so.
So make sure you have the original firmware!
Finally: Why do you even want to root your unit? My unit is not rooted as I don't see any added benefit.
For some options you don't need root at all.
Click to expand...
Click to collapse
ok that makes sense now. So basically do a backup of the original firmware.
thing is my the bezel In my car is covering a bit of the screen on the left side and covering the home button. I wanted to root it so the app “screen resizer” on google play store can have permission to change my screen size and shrink it a little. I wasent able to find any other way to change the visible screen size without rooting the unit.
I think I’ll leave it alone for now and just deal with not seeing a bit of the screen. I have no idea how to get the firmware backup. Thanks for the help, I might revisit this when I feel more comfortable doing it.

tried doing it today and no luck. I’ve updated the firmware to the latest version, took boot.img onto usb, patched file using magik app on unit, it made a patched boot img but it called it something else not a patched boot. I’ve done everything as mentioned under developer but no luck. Got an error when trying to update right away. I’ve revert the original firmware now back and unit works but root was unsuccessful. Maybe there are new restrictions on the new Android 10 setup or I’ve done something wrong.

wojas322 said:
tried doing it today and no luck. I’ve updated the firmware to the latest version, took boot.img onto usb, patched file using magik app on unit, it made a patched boot img but it called it something else not a patched boot. I’ve done everything as mentioned under developer but no luck. Got an error when trying to update right away. I’ve revert the original firmware now back and unit works but root was unsuccessful. Maybe there are new restrictions on the new Android 10 setup or I’ve done something wrong.
Click to expand...
Click to collapse
If you use the files from the developer.zip, you MUST name it patched_boot.img. Inside the 6521_1.zip is the META-INF folder. Some levels deep in that folder structure is the updater script. That one flashes the patched_boot.img, but only if it can find it of course.
So either you change the updater script (what I always do), or you name your patched boot image indeed patched_boot.img

surfer63 said:
If you use the files from the developer.zip, you MUST name it patched_boot.img. Inside the 6521_1.zip is the META-INF folder. Some levels deep in that folder structure is the updater script. That one flashes the patched_boot.img, but only if it can find it of course.
So either you change the updater script (what I always do), or you name your patched boot image indeed patched_boot.img
Click to expand...
Click to collapse
ok I will look into it today and give it another try. Also the other file that I suppose to have on the usb stick is a different number than the folder one. Do I change that name as well?

wojas322 said:
ok I will look into it today and give it another try. Also the other file that I suppose to have on the usb stick is a different number than the folder one. Do I change that name as well?
Click to expand...
Click to collapse
sorry, yes.
You are on a uis7862 unit: So in the document you have to change every occurrence of:
- sc9853i to uis7862
- 6521_1.zip to 6315_1.zip
- lsec6521update to lsec6315update
And most important:
First check the correct boot image partition of your uis7862. I'm almost sure it is not the same as the one mentioned in the sc9853i updater-script.
That could brick your unit. You really have to alter the updater-script for the boot partition.

surfer63 said:
You are on a uis7862 unit: So in the document you have to change every occurrence of:
- sc9853i to uis7862
- 6521_1.zip to 6315_1.zip
- lsec6521update to lsec6315update
And most important:
First check the correct boot image partition of your uis7862. I'm almost sure it is not the same as the one mentioned in the sc9853i updater-script.
That could brick your unit. You really have to alter the updater-script for the boot partition.
Click to expand...
Click to collapse
You can use attached zip file which should do it correct. I updated the updater-script.
Add your patched boot image as boot.img (not patched_boot.img or whatever other name) to the zip and sign the zip.

surfer63 said:
You can use attached zip file which should do it correct. I updated the updater-script.
Add your patched boot image as boot.img (not patched_boot.img or whatever other name) to the zip and sign the zip.
Click to expand...
Click to collapse
thanks a lot I will give it a try. So use your zip, add the patched boot file to it then add the lsec6315 update file to the usb and flash it. What do you mean by sign the zip file?

surfer63 said:
You can use attached zip file which should do it correct. I updated the updater-script.
Add your patched boot image as boot.img (not patched_boot.img or whatever other name) to the zip and sign the zip.
Click to expand...
Click to collapse

surfer63 said:
You can use attached zip file which should do it correct. I updated the updater-script.
Add your patched boot image as boot.img (not patched_boot.img or whatever other name) to the zip and sign the zip.
Click to expand...
Click to collapse
attached are the files that I tried it with. Your zip file with my patched boot file (renamed to boot.img) and the lsec6315update file.

wojas322 said:
attached are the files that I tried it with. Your zip file with my patched boot file (renamed to boot.img) and the lsec6315update file.
Click to expand...
Click to collapse
You did not sign the zip. Attached your zip, but now signed.

surfer63 said:
You did not sign the zip. Attached your zip, but now signed.
Click to expand...
Click to collapse
YOU ARE THE BEST! It worked! Changed my screen dimensions just like I wanted using resizer app. I cant thank you enough for all your help. Thank you very much for taking your time out the day to help me with the files!

Thanks everyone. Thanks to this and the thread OP linked, I was able to root mine as well (JY-UQ128N4G). Just in case anyone in the future has this model, I used Joying's 2021.1.19 firmware for my model above and created the attached signed zip.

Bonsoir, j'ai aussi un autoradio Android de 8,8 pouces. J'essaye aussi de le rooter pour pouvoir changer la résolution sur certaines applications
J'ai la même version mcu que dans le post photo 1. Puis-je prendre le fichier zip après quelques messages et rooter mon autoradio. D'un autre côté, ne pas avoir de bouton physique sur l'autoradio, comment êtes-vous entré en mode de récupération. Désolé pour mon anglais, je suis français

Stitch62 said:
Bonsoir, j'ai aussi un autoradio Android de 8,8 pouces. J'essaye aussi de le rooter pour pouvoir changer la résolution sur certaines applications
J'ai la même version mcu que dans le post photo 1. Puis-je prendre le fichier zip après quelques messages et rooter mon autoradio. D'un autre côté, ne pas avoir de bouton physique sur l'autoradio, comment êtes-vous entré en mode de récupération. Désolé pour mon anglais, je suis français
Click to expand...
Click to collapse
yes make sure you have the latest firmware installed on the unit first. Here is the link if you have the same unit as me and Android 10. After you are done with the firmware upgrade erase everything off the USB and place the two attached files onto it and it will auto update when plugged in. The two files are the ZIP ive attached and also a "lsec6315update" file that you copy from the latest downloaded firmware upgrade folder (link below)
Android 10.0 1280X480 Old UI 2021.1.19.zip
drive.google.com
I never had to get into recovery mode. When my unit soft bricked I just turned it off and after couple minutes would boot no problem, after booting I would re-install the latest firmware (link above) to make sure none of the files got damaged.

Hi- is the resizer still working well, and every app has been compatible with it? I've heard some issues with some popular apps not playing nice with resized screens, like Waze and Google Maps.
Btw, I have the same exact Joying unit in my C5 Corvette.

ArmchairA said:
Hi- is the resizer still working well, and every app has been compatible with it? I've heard some issues with some popular apps not playing nice with resized screens, like Waze and Google Maps.
Btw, I have the same exact Joying unit in my C5 Corvette.
Click to expand...
Click to collapse
To be honest I’m not sure. It works great on the apps I’m using but then again I mostly just listen to music and I use Sygic maps due to it being offline mode and they work great. You can always try using one of the other resizer apps, maybe newer resizer will work better with newer apps.