Related
Hi guys, this is the first post i upload and want to take the occasion to greet you all.
In these days i bought a Samsung Infuse 4G...i really like this phone but want to be able to use it with some special features such as connecting various USB devices to the phone and other juicy stuff.
I read that the builtin ROM is not capable of such this thing, and Ice Cream Sandwitch, witch should allow to do that, is not available for this smartphone model. At least not officially.
My choice fell upon CM7 LinuxBozo ROM ( http://forum.xda-developers.com/showthread.php?t=1311960 ).
I rooted my device. I'm sure of that because i am able to use the root explorer with root privileges and the root menu shows up among my applications.
I then followed the instructions here ( http://forum.xda-developers.com/showthread.php?t=1107881 ) in order to install the ClockWorkMod Flashing Menu but I am not sure whether anything went allright or not as, after trying both the methods shown on the guide, nothing happened (in the first case, the automatic install through ROM Manager seems to work, a message appears on the screen confirming anything went smooth but when i reboot i see the normal reboot menu, no advanced menu nor CWM menu; in the second case i tried to manually load the CWM menu by placing the update file in the SD and renaming it to update.zip, the update gets stuck somewhere saying something about a bad or wrong signature, tried it a few times and with different CWM update versions but nothing to do).
I then stumbled into a workaround to fix that issue by an even more manual procedure ( http://www.youtube.com/watch?v=PkMo8rBehHg&feature=related ) basically consisting in copying the "recovery" executable from the CWM update archive to the directory /system/bin and of course chmodding it to rwxr-xr-x and chowning it to the root.
Now the CWM screen appears but, as i attempt to flash the CM7 ROM, the flashing gets stuck at "Finding update package". I read here ( http://forum.xda-developers.com/showthread.php?t=821499 ) that it could happen sometimes and it's just a matter of trying and trying again... I tried at least ten times up to now but it keeps getting stuck...maybe it's not my case.
Hope someone will help me out...i really need that USB reading feature. Thank you.
baareem said:
Hi guys, this is the first post i upload and want to take the occasion to greet you all.
In these days i bought a Samsung Infuse 4G...i really like this phone but want to be able to use it with some special features such as connecting various USB devices to the phone and other juicy stuff.
I read that the builtin ROM is not capable of such this thing, and Ice Cream Sandwitch, witch should allow to do that, is not available for this smartphone model. At least not officially.
My choice fell upon CM7 LinuxBozo ROM ( http://forum.xda-developers.com/showthread.php?t=1311960 ).
I rooted my device. I'm sure of that because i am able to use the root explorer with root privileges and the root menu shows up among my applications.
I then followed the instructions here ( http://forum.xda-developers.com/showthread.php?t=1107881 ) in order to install the ClockWorkMod Flashing Menu but I am not sure whether anything went allright or not as, after trying both the methods shown on the guide, nothing happened (in the first case, the automatic install through ROM Manager seems to work, a message appears on the screen confirming anything went smooth but when i reboot i see the normal reboot menu, no advanced menu nor CWM menu; in the second case i tried to manually load the CWM menu by placing the update file in the SD and renaming it to update.zip, the update gets stuck somewhere saying something about a bad or wrong signature, tried it a few times and with different CWM update versions but nothing to do).
I then stumbled into a workaround to fix that issue by an even more manual procedure ( http://www.youtube.com/watch?v=PkMo8rBehHg&feature=related ) basically consisting in copying the "recovery" executable from the CWM update archive to the directory /system/bin and of course chmodding it to rwxr-xr-x and chowning it to the root.
Now the CWM screen appears but, as i attempt to flash the CM7 ROM, the flashing gets stuck at "Finding update package". I read here ( http://forum.xda-developers.com/showthread.php?t=821499 ) that it could happen sometimes and it's just a matter of trying and trying again... I tried at least ten times up to now but it keeps getting stuck...maybe it's not my case.
Hope someone will help me out...i really need that USB reading feature. Thank you.
Click to expand...
Click to collapse
what color is your cwm screen?
this may be a simpler way of gettin cwm:
http://forum.xda-developers.com/showthread.php?t=1220090
specifically, the CWM instructions set.
I see that the instructions you suggested me would mean to start the process almost from scratch. I will do that as soon as i finish studying the nazis for my school report .
And maybe after getting the next answer from you
The boot screen is green text on black backgroud.
Holding audio and power buttons for 10 seconds doesn't prompt me to the red boot screen if it was what you meant and if I read the instructions provided well (witch i didn't as i have no time now)... don't get me wrong. Just trying to provide you as more information as possible.
baareem said:
I see that the instructions you suggested me would mean to start the process almost from scratch. I will do that as soon as i finish studying the nazis for my school report .
And maybe after getting the next answer from you
The boot screen is green text on black backgroud.
Holding audio and power buttons for 10 seconds doesn't prompt me to the red boot screen if it was what you meant and if I read the instructions provided well (witch i didn't as i have no time now)... don't get me wrong. Just trying to provide you as more information as possible.
Click to expand...
Click to collapse
if you still have root, download from market
sgs kernel flasher and the flash the gingerbread kernel to give you RED recovery and flash the rom of your choice after a factory reset and usual wipes
Cool... i'm now running CM7 !
Here is what i missed for anyone who would have the same problem in the future (you can find the download links here: http://forum.xda-developers.com/showthread.php?t=1220090 ):
CWM Installation Instructions:
1) You must be rooted.
2) If you have a /Voodoo folder on your internal SD card, delete it and reboot.
3) If you're already running a custom ROM with Voodoo lagfix FULLY enabled, you can skip to step 7.
4) Download CWM-community-kernel-v8.zip if you're on Froyo or CWM-infused-v2.0.1-kernel.zip if you're on Gingerbread and place it on your internal SD card.
5) Install SGS Kernel Flasher from the Market.
6) Open SGS Kernel Flasher, select choose kernel, select the file you downloaded, and select flash kernel. Your phone will reboot and begin to enable Voodoo lagfix. Let it do that and boot all the way up. It will take a while (5-10 minutes) because it's converting all partitions to ext4.
7) Download update-infused-v2.X.X-full.zip and place it on your internal SD card.
8) Power off your phone.
9) With the phone powered off, hold both volume keys and the power button for about 10 seconds and then release. This should boot you into RED CWM.
10) Select "install zip from sdcard" and select update-infused-v2.X.X-full.zip.
11) Once that finishes, select "wipe data/factory reset".
12) Select "reboot system now".
13) Do NOT restore system data with Titanium Backup. Do NOT restore ALL apps with data. If you absolutely must restore something with Titanium Backup, only restore MISSING apps with data.
Click to expand...
Click to collapse
Now just another question: i noticed different errors when running the market and other old built-in apps... I just need to reinstall gapps right?
yeah, that is why it's stickeyed.
you just had to read/search them.
market wise, there's a market fix
or you can also factory reset and wipe cache and dalvik in cwm
Thanks. You helped me solving this and now anything works fine. Have a good day.
Thread (NOT) SOLVED.
--------
(Edited after realizing gapps still don't show up as installation didn't really worked)
baareem said:
Thanks. You helped me solving this and now anything works fine. Have a good day.
Thread SOLVED.
Click to expand...
Click to collapse
np. take it easy, bro.
I was too quick saying it worked.
The Infuse just booted up but nothing changed. I then tried to do the zip installing through rom manager again but invane.
When trying with the manual install it promts me with this error:
E: Can't open /emmc/gapps-gb-xxxxxxx-signed.zip
(bad)
Installation aborted.
Click to expand...
Click to collapse
I tried different versions of gapps including the one suggested in the CM wiki but with no luck. I guess the problem is somewhere else.
PS: now i see the blue on black bootscreen as in order to install gapps with rom manager i was asked to reinstall CWM trough it...
baareem said:
I was too quick saying it worked.
The Infuse just booted up but nothing changed. I then tried to do the zip installing through rom manager again but invane.
When trying with the manual install it promts me with this error:
I tried different versions of gapps including the one suggested in the CM wiki but with no luck. I guess the problem is somewhere else.
PS: now i see the blue on black bootscreen as in order to install gapps with rom manager i was asked to reinstall CWM trough it...
Click to expand...
Click to collapse
what version of ROM were you running when you tried this?
Stock FRoyo?
Cyanogenmod 7 ... exactly this version : http://forum.xda-developers.com/showthread.php?t=1311960
Kernel version is 2.6.35.7 , android v 2.3.7.
The old, OOB version i had was froyo 2.2.6 if i well remember.
baareem said:
Cyanogenmod 7 ... exactly this version : http://forum.xda-developers.com/showthread.php?t=1311960
Kernel version is 2.6.35.7 , android v 2.3.7.
The old, OOB version i had was froyo 2.2.6 if i well remember.
Click to expand...
Click to collapse
I haven't played with CM7, it's not an infuse based rom.
I recall some installation issues with it.
I remember an unsuccess reboot intially and pull battery thing..not sure.
If you're looking to install another rom, odin back to stock and start over.
check out my sig line for some useful links
Hello everyone
I am unable to flash the cm10 rom on my tf300t using TWRP 2.3.3.0. Most forums i read have cwm, but I am having some other issues with cwm so i have to use TWRP. The error is status 7, see attachment below. (I have already verified and md5 is alright)
Any help or pointers are appreciated.
Sent from my Galaxy Nexus using xda app-developers app
the screenshot says no MD5 file is found. Not saying that is your issue, but just an observation since you said you checked it.
Also, it appears the zip file is inside a directory? try moving it to the root of the SD card. sometimes the paths for various functions of the flash assume that you are operating out of the root directory on the SD card.
thorrules said:
Hello everyone
I am unable to flash the cm10 rom on my tf300t using TWRP 2.3.3.0. Most forums i read have cwm, but I am having some other issues with cwm so i have to use TWRP. The error is status 7, see attachment below. (I have already verified and md5 is alright)
Any help or pointers are appreciated.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Please see the line assert failed: getprop("
If you are using a tf300t then your error is in your build.prop file. It does not identify your unit as such.
The file you are trying to flash is the first cm10 download for the JB bootloader. I don't believe you will be pleased with that version.
If you still want to use it you will need to edit your zip to remove the asserts!
tobdaryl said:
Please see the line assert failed: getprop("
If you are using a tf300t then your error is in your build.prop file. It does not identify your unit as such.
The file you are trying to flash is the first cm10 download for the JB bootloader. I don't believe you will be pleased with that version.
If you still want to use it you will need to edit your zip to remove the asserts!
Click to expand...
Click to collapse
Why do you say I would not be pleased with that version? As per http://get.cm/?device=tf300t it seems to have been released on 13-Nov. I was looking for a stable CM10 and that is the most stable I found. Also why does it not identify my unit? Is that an issue with the TWRP? FYI -- TWRP was the first recovery I had flashed, but since it gave status 7 error, I flashed CWM. CWM gave me some MBR signature errors, and it was completely useless, since it would not even take backup of my ROM, so I again moved back to TWRP. Thanks by the way.
mike-y said:
the screenshot says no MD5 file is found. Not saying that is your issue, but just an observation since you said you checked it.
Also, it appears the zip file is inside a directory? try moving it to the root of the SD card. sometimes the paths for various functions of the flash assume that you are operating out of the root directory on the SD card.
Click to expand...
Click to collapse
Actually I had verified MD5 when I downloaded it on the phone (using FileManager app). I will try moving to the root directory, but I feel like that is not the issue. Thank you for your response.
thorrules said:
Why do you say I would not be pleased with that version? As per http://get.cm/?device=tf300t it seems to have been released on 13-Nov. I was looking for a stable CM10 and that is the most stable I found. Also why does it not identify my unit? Is that an issue with the TWRP? FYI -- TWRP was the first recovery I had flashed, but since it gave status 7 error, I flashed CWM. CWM gave me some MBR signature errors, and it was completely useless, since it would not even take backup of my ROM, so I again moved back to TWRP. Thanks by the way.
Actually I had verified MD5 when I downloaded it on the phone (using FileManager app). I will try moving to the root directory, but I feel like that is not the issue. Thank you for your response.
Click to expand...
Click to collapse
That cm10 was released prior to the first cm10 nightly. If I remember correctly it didn't support gps and may not have supported wifi. It was placed in stable because it couldn't be released in nightlies at that point.
The md5 failure is normal if you don't have a properly named md5 file in the same directory as the zip and have the option set to use it.
tobdaryl said:
That cm10 was released prior to the first cm10 nightly. If I remember correctly it didn't support gps and may not have supported wifi. It was placed in stable because it couldn't be released in nightlies at that point.
The md5 failure is normal if you don't have a properly named md5 file in the same directory as the zip and have the option set to use it.
Click to expand...
Click to collapse
Thanks. So I guess that CM10 was not useful to me anyway, I was looking for a stable and complete ROM. I think I will then try something else, maybe superclean, have read that it is stable too. Personally I do not like stock, instead prefer AOKP or CMs but I guess I have no choice then. Any other ROM that you had recommend? (stable + complete)?
About md5, thanks for that, I wasnt really worried about md5, since I had verified it already (before flashing).
thorrules said:
Thanks. So I guess that CM10 was not useful to me anyway, I was looking for a stable and complete ROM. I think I will then try something else, maybe superclean, have read that it is stable too. Personally I do not like stock, instead prefer AOKP or CMs but I guess I have no choice then. Any other ROM that you had recommend? (stable + complete)?
About md5, thanks for that, I wasnt really worried about md5, since I had verified it already (before flashing).
Click to expand...
Click to collapse
I know it says nightly but the recent cm10.1 releases are stable and everything I have used works properly. I don't have a dock so I can't address that. It is a good daily driver for my use.
Some people are bothered by having a 0 directory on the internal sdcard for the first user. Yes it is multi-user. Android 4.2.
tobdaryl said:
I know it says nightly but the recent cm10.1 releases are stable and everything I have used works properly. I don't have a dock so I can't address that. It is a good daily driver for my use.
Some people are bothered by having a 0 directory on the internal sdcard for the first user. Yes it is multi-user. Android 4.2.
Click to expand...
Click to collapse
I dont use a dock either, so that should work for me. I have never tried 4.2 ROM, will look for more details (esp the multi-user thingy) and then try it.
thorrules said:
I dont use a dock either, so that should work for me. I have never tried 4.2 ROM, will look for more details (esp the multi-user thingy) and then try it.
Click to expand...
Click to collapse
OK, that is the reason I mentioned 4.2 and multi-user.
Good Luck!
Hey ME301 users.
I have decided to move this information over to a Q&A thread so we don't bung up CROMBI thread with this. It seems that there is something that is not letting ME301 users install and run the latest 4.4.3 version of CROMBI and of course we are hoping to do something about that.
I will post a few test zips to try and see if they can allow you to boot on to CROMBI.
As the users who are testing this out there are a few things that I ask of you when troubleshooting:
When installing CROMBI, please make sure you do a factory reset wipe in TWRP and also wipe cache and dalvik cache
Please do not choose any options in the installer for running data2sd, rom2sd or f2fs. If you have f2fs on your internal /data I could possibly make up a test for that. I am going to stick to EXT4 for now.
Make sure you choose ME301 in the installer, and choose do not install a kernel
Flash one of the test zips provided below once you finish installing CROMBI and before you reboot your tablet
If it fails to boot, please indicate whether it boot loops at black Asus logo screen or at the bootanimation
If it is bootlooping at the bootanimation, then please send me a logcat as well as a last_kmsg and attach it to this thread. If you do not know how to do this there are many guides on XDA that can explain it much better than I can.
That should be about all for now. Let the testing begin!
EDIT/UPDATE - Tests 1-4 = FAIL, how about test 5?
hardslog said:
Hey ME301 users.
I have decided to move this information over to a Q&A thread so we don't bung up CROMBI thread with this. It seems that there is something that is not letting ME301 users install and run the latest 4.4.3 version of CROMBI and of course we are hoping to do something about that.
I will post a few test zips to try and see if they can allow you to boot on to CROMBI.
As the users who are testing this out there are a few things that I ask of you when troubleshooting:
When installing CROMBI, please make sure you do a factory reset wipe in TWRP and also wipe cache and dalvik cache
Please do not choose any options in the installer for running data2sd, rom2sd or f2fs. If you have f2fs on your internal /data I could possibly make up a test for that. I am going to stick to EXT4 for now.
Make sure you choose ME301 in the installer, and choose do not install a kernel
Flash one of the test zips provided below once you finish installing CROMBI and before you reboot your tablet
If it fails to boot, please indicate whether it boot loops at black Asus logo screen or at the bootanimation
If it is bootlooping at the bootanimation, then please send me a logcat as well as a last_kmsg and attach it to this thread. If you do not know how to do this there are many guides on XDA that can explain it much better than I can.
That should be about all for now. Let the testing begin!
Click to expand...
Click to collapse
Test 1 & 2 both bootloop at the bootanimation Crombi-KK logo. I cannot pull logcat or last_Kmsg as my command prompt shows device as "offline" and after entering the commands it just reads "waiting for device".
DrBeaker said:
Test 1 & 2 both bootloop at the bootanimation Crombi-KK logo. I cannot pull logcat or last_Kmsg as my command prompt shows device as "offline" and after entering the commands it just reads "waiting for device".
Click to expand...
Click to collapse
If you reboot into TWRP, you can go into 'advanced' and then 'file manager' and then go into the 'proc' folder and in there you can find the last_kmsg. If you select it, it will allow you to copy it to your sd card.
hardslog said:
If you reboot into TWRP, you can go into 'advanced' and then 'file manager' and then go into the 'proc' folder and in there you can find the last_kmsg. If you select it, it will allow you to copy it to your sd card.
Click to expand...
Click to collapse
I have attached zip that contains test 1 and test 2 results.
DrBeaker said:
I have attached zip that contains test 1 and test 2 results.
Click to expand...
Click to collapse
Uploaded test 3 and test 4 to the OP
hardslog said:
Uploaded test 3 and test 4 to the OP
Click to expand...
Click to collapse
@hardslog thank you for your continued attempts to get this moving.
I have tried 3 and 4 with same results. Boots to Crombi bootanimation and remains there.
Attached is zip of Last_Kmsg for zips 3 and 4.
I hope they are helping.
DrBeaker said:
@hardslog thank you for your continued attempts to get this moving.
I have tried 3 and 4 with same results. Boots to Crombi bootanimation and remains there.
Attached is zip of Last_Kmsg for zips 3 and 4.
I hope they are helping.
Click to expand...
Click to collapse
Is it possible that instead of zipping the files, to rename them to a .txt and upload them uncompressed? It seems that when they get zipped the encoding gets messed up.
Test 4 stuck at Crombi-KK bootanim. Last_kmsg is 0 kb ?
hardslog said:
Is it possible that instead of zipping the files, to rename them to a .txt and upload them uncompressed? It seems that when they get zipped the encoding gets messed up.
Click to expand...
Click to collapse
I found the same thing myself, was hard to view.
I have taken the files, copied to SD then simply added .txt to the end of the file.
Attached are the results.
Let me know what i can do to assist further.
OK,
Here is what I need....
Someone with a me301t that boots, turn on adb either in rom or boot into recovery and run this command
Code:
adb pull proc/config.gz
Upload the file somewhere so I can download it......
Thx Josh & Team CROMBI
lj50036 said:
OK,
Here is what I need....
Someone with a me301t that boots, turn on adb either in rom or boot into recovery and run this command
Code:
adb pull proc/config.gz
Upload the file somewhere so I can download it......
Thx Josh & Team CROMBI
Click to expand...
Click to collapse
I cannot get ADB function to initialize while instlaling this rom. It boot loops at Crombi logo, and ADB indicates "device offline" and will not accept any commands.
While in recovery, ADB mode does not seem to be enabled. Best we can do at this time is browse to folders on the tab using the advanced/File Manager.
I have pulled that file and attached in its raw format and a copy with .txt on the end (which appears unreadable).
Any progress on the logs or attempts at ME301T tab?
DrBeaker said:
Any progress on the logs or attempts at ME301T tab?
Click to expand...
Click to collapse
not really. We are pretty stumped on this one right now, sorry to say.
hardslog said:
not really. We are pretty stumped on this one right now, sorry to say.
Click to expand...
Click to collapse
Do we need any more logs of something?
- I just got back from a vacation and now have access to a computer again so I could probably do some tests with my tablet while in front of the tv enjoying the World Cup
(thought this thing with adb would be some real scary **** from my linux netbook instead of my Windows partition but it turned out to be easier than I thought to get it set up)
/gosa
DrBeaker said:
Any progress on the logs or attempts at ME301T tab?
Click to expand...
Click to collapse
hardslog said:
not really. We are pretty stumped on this one right now, sorry to say.
Click to expand...
Click to collapse
Test 5 up in the OP. You know the drill. :laugh:
Result from test 5. Still stuck on boot logo (CROMBi-KK) .
Uploading last_kmsg taken from twrp. (take away .txt)
On my way out, so adb logcat will have to wait a bit more.
-Thanks for working on this!
hardslog i got it working ...
Test 1: failed (Rom booted but much of error's ,fc and apps stopped working.)
1. flashed the new version and selected in aroma installer tf300.
2. Flashed without kernel and flashed "[Kernel][ME301T] KitKat Compatibility Pack V2.5 [May 13 2014]"
Test 2: succes booting and working :laugh: :good:
1.Flashed the new verson (4.4.4) and selected in aroma installer tf300.
2.Flashed without kernel and with your test5.zip
I can confirm latest version with test 5 works.
archspijkenisse said:
I can confirm latest version with test 5 works.
Click to expand...
Click to collapse
Good to know that we have it working again. Now I can look into restoring overclocking and all that fun stuff
Great work guys. It's running very smooth.
https://androidfilehost.com/?w=search&s=dreamlte
i flash this but cant boot stuck in s8 splash screen
That's interesting
Can't find any Github links of it
EDIT: This might use Albe96XDA's sources, but can't confirm
Do not have any videos?
manousos1 said:
i flash this but cant boot stuck in s8 splash screen
Click to expand...
Click to collapse
same here
https://www.cyanogenmods.org/forums/topic/lineage-os-15-1-for-galaxy-s8-android-oreo-8-1/
The latest unofficial doesn't seem to boot, seems there is a problem with the bootloader. I will try the first unofficial and see if it works. The uploader of the Rom has made previous roms for other devices so there is hope finally for our Galaxy S8
Omg this is real? Pls work on g955f too
Crossing my fingers !!!
Can any dev check the validity of this rom?
GeorgeChilian said:
The latest unofficial doesn't seem to boot, seems there is a problem with the bootloader. I will try the first unofficial and see if it works. The uploader of the Rom has made previous roms for other devices so there is hope finally for our Galaxy S8
Click to expand...
Click to collapse
test done with both rom unsuccessful - that of 21/11/2018 gives a black screen - that of 22/11/2018 gives a problem with the bootloader.
And you ?
tboguizmo said:
test done with both rom unsuccessful - that of 21/11/2018 gives a black screen - that of 22/11/2018 gives a problem with the bootloader.
And you ?
Click to expand...
Click to collapse
I have the same issue. The problem seems to be with the bootloader, i might be completely wrong. Is there any dev that can check the rom?
---------- Post added at 03:41 PM ---------- Previous post was at 03:33 PM ----------
The same dev also uploaded 2 AICP nightlies for our device. Or the developer confused code names for devices and this is not meant for our device
This is indeed for our device because dev has mentioned it is for "Galaxy S8" but highly doubt it is any different from the ROMs we already have that are not in a condition for daily use
I kept playing around with the rom for the past couple days and I pulled a tombstone file and it seems there is an openGL error. I have attached the tombstone file below. I'm not experienced enough to know what all of that stuff means lol
https://drive.google.com/open?id=1RZRV94t4UuZhcCDMCJuaFNe78DUNtVnN
GeorgeChilian said:
I kept playing around with the rom for the past couple days and I pulled a tombstone file and it seems there is an openGL error. I have attached the tombstone file below. I'm not experienced enough to know what all of that stuff means lol
https://drive.google.com/open?id=1RZRV94t4UuZhcCDMCJuaFNe78DUNtVnN
Click to expand...
Click to collapse
It seems there are other problems with the ROM, not just the OpenGL thing
"dlopen failed: library "/vendor/lib64/egl/get_process_name.so" not found"
You can try finding that file and placing it into the .zip file manually, unfortunately I can't test it because I have S8 plus, but no guarantee that it'll work
Kizoky said:
It seems there are other problems with the ROM, not just the OpenGL thing
"dlopen failed: library "/vendor/lib64/egl/get_process_name.so" not found"
You can try finding that file and placing it into the .zip file manually, unfortunately I can't test it because I have S8 plus, but no guarantee that it'll work
Click to expand...
Click to collapse
What about copying the whole of the vendor folder?
And placing them in the rom after the installation through the Twrp file manager?
GeorgeChilian said:
What about copying the whole of the vendor folder?
And placing them in the rom after the installation through the Twrp file manager?
Click to expand...
Click to collapse
That would work too.
Kizoky said:
That would work too.
Click to expand...
Click to collapse
So I just tried it and nothing changed which was weird. Then I go back to twrp and check the files and they're gone. They seem to get deleted every time the phone reboots for some reason I believe
GeorgeChilian said:
So I just tried it and nothing changed which was weird. Then I go back to twrp and check the files and they're gone. They seem to get deleted every time the phone reboots for some reason I believe
Click to expand...
Click to collapse
Yeah, that's why I usually like to replace/add something from/to the .zip file itself, nothing like that will happen
Kizoky said:
Yeah, that's why I usually like to replace/add something from/to the .zip file itself, nothing like that will happen
Click to expand...
Click to collapse
The zip has inside it a system.new.dat.br where all the system stuff are and I can't open it. Would I be able to just place the vendor files in the root of the zip and just update the updater-script?
Hi,
Since a few days I'm unable to see any data in my phone via gallery or file manager or any application, and I'm unable to save any data to internal storage. (example: I'm able to use whatsapp for texting, but I can't receive/send any audio/picture and I can't access the old ones).
And I keep getting this error message:"com.android.providers.media.MediaApplication keeps stopping."
I don't know if that's what causing it or if that's just a consequence of not being able to access internal storage.
I can still see all the used storage from settings though.
Phone has unlocked bootloader, but no root/custom rom/recovery.
I saw other Oneplus users started getting the same error these days... (I have a Oneplus 6, but others have different models like Oneplus Nord).
Someone resolved by wiping system and they were able to retrieve storage content and functionality, but they lost apps data, I'm trying to find another way since I have an unlocked bootloader.
A user on stackoverflow suggested I should clean the com.android.providers.media.MediaApplication app data to regenerate the database, but I couldn't figure out how to do it
I tried cleaning media and media.module packages (not media.MediaApplication) from adb but no luck even if successful.
I tried removing "com.android.providers.media" (not media.MediaApplication, I couldn't find that one) folder from data/data with twrp file manager but no luck...
Is there a way to specifically clean "com.android.providers.media.MediaApplication"?
If anyone has any other suggestion on things to try, post it here please.
Have you modified any system settings recently? Or might be just some unorganized drivers.
Conect pc and make bakup your stuff...
Then on settings make Factory Reset...
Zxalilh said:
Have you modified any system settings recently? Or might be just some unorganized drivers.
Click to expand...
Click to collapse
Not at all... I never did any modding, and I saw it happened to people that were completely stock as well
Mord0rr said:
Conect pc and make bakup your stuff...
Then on settings make Factory Reset...
Click to expand...
Click to collapse
I wanted to try to avoid that route...
0xCuter said:
Not at all... I never did any modding, and I saw it happened to people that were completely stock as well
Click to expand...
Click to collapse
Maybe it's just a common error, you could search it up on youtube but I guess you will have to backup and reset your device
Zxalilh said:
Maybe it's just a common error, you could search it up on youtube but I guess you will have to backup and reset your device
Click to expand...
Click to collapse
I already looked everywhere but there is not much about it other than other users that are having the same issue
0xCuter said:
I already looked everywhere but there is not much about it other than other users that are having the same issue
Click to expand...
Click to collapse
Try this?
Zxalilh said:
Try this?
Click to expand...
Click to collapse
Already tried... didn't work unfortunately
You need to flash a fila called "SdcardFixPermissions-singed" and will be work again
anhenrique said:
You need to flash a fila called "SdcardFixPermissions-singed" and will be work again
Click to expand...
Click to collapse
Did you have the same problem or is it just speculation? I don't to want to break more stuff...
0xCuter said:
Did you have the same problem or is it just speculation? I don't to want to break more stuff...
Click to expand...
Click to collapse
I had the same problem, and this is how I solved it. But it's your own risk.
anhenrique said:
I had the same problem, and this is how I solved it. But it's your own risk.
Click to expand...
Click to collapse
Sorry, I see your message only now... Do you remember when did you have this problem? And was it this exact message on a Oneplus 6?
I have the problem of not being able to save anything in the storage or having a broken zip, always after using msmtool 10.3.5, I saw it in a post here about this file and it solved.
[SCRIPT/FIX] Internal sdcard permissions (/data/media/)
This should be applicable to any ROM on devices which share internal storage for applications and the internal "sdcard" (Note II, SGS3, probably others). Symptoms may include inability to take screenshots and other failures, and will usually show...
forum.xda-developers.com
the file was developed by a senior member and recognized @osm0sis