Guys, I'm having a tough time deleting a file or two that were recently installed in the root's /product folder and I guess I don't understand what I am doing wrong, or what security is in place to prevent me from doing this. I would greatly appreciate any help or suggestions here. I cannot change permissions to make the folder recursively rw. I first started with Root Explorer and Solid Explorer. Both are capable of changing permissions but failed saying it was a "system folder". I used terminal to setenforce to 0, and tried with su from terminal and could not manually change folder permissions using chmod either. I thought maybe TWRP would be the answer, so I booted recovery and tried mounting the data partition (I think it's on data) and used file manager to browse to the folder, but I cannot see the contents of the folder nor can I delete it. What am I missing here? Is the TWRP mount function busted atm? Last night I reflashed November's update with the -w thinking it might "overwrite" the folder, but there was no joy there either. I do have a couple of TWRP backups of the data folder and that is my next step. Before I apply the December image tonight, I'm going to restore the most recent /data partition backup. There has to be a way to get control of that folder and it's contents but so far it has eluded me.
Cheers and TIA.
As far as I'm aware, the only way currently to write to the product partition is to fastboot flash it. I've went as far as to modify TWRP fstab to mount it in recovery and use the file manager to replace the bootanimation only to have it either never write properly or for it to "correct" itself. Not sure which happened.
Sent from my Pixel 3 XL using Tapatalk
I appreciate the response... anything helps. Product is a folder in root also and that is what I am trying to access. Unless there is some kind of symlink linking that product folder to the product partition. I don't know. When I flashed the full image yesterday I would have thought that partition.img (nested in the zipfile) would have been flashed, too. Maybe I can try fastboot formating the product partition. Can't hurt. Thanks again!
Edit: Just found this thread where you also contributed. I'll try to flash that partition with the partition.img and see what happens. I just want to reset it to stock.
superchilpil said:
As far as I'm aware, the only way currently to write to the product partition is to fastboot flash it. I've went as far as to modify TWRP fstab to mount it in recovery and use the file manager to replace the bootanimation only to have it either never write properly or for it to "correct" itself. Not sure which happened.
Click to expand...
Click to collapse
I flashed product.img first and it rendered the phone unbootable... corrupt. I then went back into TWRP and wiped system and ran the flash-all script in fastboot and re-rooted. The net result is the product folder is unchanged. Everything is up and running just fine. That folder is just untouchable for me so far. Next I will format data and re-flash. I didn't fully understand what you meant about the custom kernel being the solution but so far EX is not working. May reach out to flar2 and see if he can make some kind of change to his kernel to support mounting this partition? Thanks again.
v12xke said:
I flashed product.img first and it rendered the phone unbootable... corrupt. I then went back into TWRP and wiped system and ran the flash-all script in fastboot and re-rooted. The net result is the product folder is unchanged. Everything is up and running just fine. That folder is just untouchable for me so far. Next I will format data and re-flash. I didn't fully understand what you meant about the custom kernel being the solution but so far EX is not working. May reach out to flar2 and see if he can make some kind of change to his kernel to support mounting this partition? Thanks again.
Click to expand...
Click to collapse
Yeah I have yet to be able to mount the product image to modify it, but I haven't tried all that much lately. I'm pretty sure it's fixable with a kernel edit but that's beyond my ability, and even if I could I have a 8 year old laptop that wouldn't be able to build it.
What are you trying to accomplish? The bootanimation?
Sent from my Pixel 3 XL using Tapatalk
superchilpil said:
Yeah I have yet to be able to mount the product image to modify it, but I haven't tried all that much lately. I'm pretty sure it's fixable with a kernel edit but that's beyond my ability, and even if I could I have a 8 year old laptop that wouldn't be able to build it. What are you trying to accomplish? The bootanimation?
Click to expand...
Click to collapse
No, I see boot animation in that folder, and yes we all used to use it, but this time it's just an apk from apkmirror that wrote to that system partition (don't ask me how) and now I can't uninstall or update it. com. breel.wallpapers18. I tried to uninstall it using pm uninstall, but it uninstalled it for user 0 so it remains as a system app, and not available to me. I can't uninstall it completely or upgrade... or even use it! It's just a fk'in set of Google live wallpapers I like, but now want to re-set. Waay too much time spent on this so I'm (just about) ready to flush and start over. Every year Google makes it harder for us (fans) to customize our own phones. wtf? Pissed.
Related
I have a problem when trying to change the lock screen sound in MIUI XJ 1.2.25.
I can copy the new lock sound to /system/media/audio/ui allright, everything seems fine.. But when i reboot, the sound (and all the files) go back to before i copied the new sound(s)..
I'm thinking it might be a "signing" problem, but i'm completely lost in how to do this... So a step by step guide would be nice, as i'm rather new to this whole rooting business
Been using root explorer and/or adb to push the files.
(Btw, when i try to change permissions for the new sound file, nothing happens after i click "ok" in roote explorer.. Any ideas?)
Oh, my device is a HTC Desire
Thanks!
Of you are S-ON, that's your problem. You must push the files via ADB, while in recovery to make them stay there after reboot.
Sent from my customized HTC Desire using TTP
Ok, I know i'm S-On.. I tried pushing the files via adb, which worked fine, but after reboot things were back to normal.. I tried to install a soundpack from a zip (via recovery), that worked well, the sounds didn't revert back to the original. But when i tried to do it manually, things get screwed up
Perhaps the zip file change some settings somewhere that i don't know of?
Guess i'll go S-off then, then i can also change the splash screen
-------
After some more research, i now understand that the soundpack zip-file i installed must have been signed, to pass the HTC security feature...thing.. Thus being able to install new system sounds without the phone reverting back to the original.. Isn't that right?
As I said, files remain there if you flash via ADB while in the custom RECOVERY! Not while the phone is booted & running. At least for me it's working.
Yeah i tried that, but with same result..
Actually, the reason i used adb in pushed the files while in recovery mode, was because i had some issues when using root explorer on the phone.
Sometimes (but not everytime!!?) i couldn't copy/paste the files from my SD card and into the system, it gave me a message about not having enough free space. Which was complpetely wrong, as i generally had about 90-100mb free space. And nothing would happen when i tried changing permissions on the files either.. I read some where that updating busybox could fix the problem with the free space issue, so i did.. Then i could copy the files, but then they wouldn't show up in the destination folder.. Really weird.. So i thought adb was the way to go..
As said, everything went fine until reboot. the files i pushed would still be there, but the originals would have come back too. Meaning i'd have 2 files with the same name, but different sizes, dates and permissions..
It makes much sense with the security feature, as you say..
I'm seriously considering to try an S-off procedure, to get full root and full control
Well then IDK, if I remove a file then push the version I want -it always stay there (via ADB in Recovery).
That's why I never tried S-Off, since I don't need resizing the NAND partitions, and copying to system via ADB always works.
Got tired of experimenting with this, so i made my phone S-off using Virtualbox method. Now everything works perfect!
I can change files and permissions in the system partition and everythings stays as i leave it when rebooting
Somehow the phone boots way faster now ?? But certainly welcome!
Thankyou for your replies
Yeah..as the title says.. 3 weeks ago this hacker hacked into my network..
placed rootkits in all my 3 computers and then hacked its way to my Desire and my wifes iphone. good thing i had wireshark running same time.
So.. 5 units hacked with the method in like 1 houre. Bad luck for me i guess.
And kaspersky didnt give me any warnings at all. bye bye kaspersky.
Anyway... i flashed my desire's HBOOT just to be sure. after i did a check with "AutoKiller Memory Optimizer" all kinds of malware services was attached to most of my apps.
1- downgraded HBOOT
2- flashed stock HBOOT from alpharev
3- Changed recovery from CWM to 4EXT as i suspected the recovery being infected somehow.
I checkd my log... the hacker had removed some files and moved shell files from an folder to another as well as busybox and so on. it was so many i thought il be better of installing new ROM.
I tried with Gingervillain first... everything installed fine..
checking with "root explorer" i see same files that had been moved and added was still there.
OK.. i tried again..
full wipe with 4ext and then installed Runnymede.. still.. when i check my root partition most of the files still there and i get same results doing a root check.
any idees...? im not sure if my kernel is right. it should be, when i installed Runnymede. when checking kernel v.
it says.. "[email protected] #11"
May be kernel rootkit? does the kernel start before recovery?
can someone plz confirm this?
baseband seem to be the same
any advise as for how to start from scratch will be much appreciated.
Clawsman said:
full wipe with 4ext and then installed Runnymede.. still.. when i check my root partition most of the files still there and i get same results doing a root check.
Click to expand...
Click to collapse
Full wipe wipes /cache, /data and /sd-ext to my knowledge. There is a possibility some of the files remain on /system. Use 4EXT to manually format each partition using format option.
Clawsman said:
it says.. "[email protected] #11"
Click to expand...
Click to collapse
That seems in order. Long name in attach marks modules added to that kernel.
Sent from my HTC Desire using Tapatalk
Ok
well.. i did the format manually in 4EXT.
I suspect some files still to be there..also some boot files containing malware script.
what file contains the boot script? i mean.. what file is the first to be triggered when booting in HBOOT. because many things in the recovery doesnt seem right. and the hboot fastrecovery starts with a delay.
Like when i want to partition or when i want to format all partitions except sd. Acts like it doesnt want to.
Anyway.. was just wondering if i could just adb and delete every file folder that is in in my phone and then flash recovery and ROM again.
Is that what RUU does?
is that something to recomend?
RUU is complete wipe of everything. /system, /hboot etc.
Download the correct one for your phone, *follow its instructions* (may need a gold card - google it) and run it on a clean pc.
Clean your pc ie format and reinstall after taking backups.
Then start again wit ha new hboot/rom setup.
Is that even possible? Infecting an Android phone via a Wi-fi network?
And Recovery shouldn't be able to get infected. I think ONLY /data can, and eventually /system if it's mounted as RW.
But on a wipe data gets deleted, and on a ROM install /system and boot (which holds the kernel and ramdisk) is deleted anyway.
RADIO starts before HBOOT. And there's absolutely no way they can be infected.
To be safe:
fastboot erase cache
fastboot erase system
fastboot erase boot
fastboot erase recovery *OVERKILL*
Then just do fastboot flash recovery {RECOVERY}
And there's nothing more you must do. HBOOT reflashing is 100% pointless.
Maybe top-notch hackers are shifting their interest from hacking NASA, FBI and similar organizations in the US to hacking Android phones. Or maybe it's one of their favourite ways to have fun in their idle time. Who knows?
Anyways, here's a Thanks from me, mr. Andrei, for your contribution to this community.
TVTV said:
Maybe top-notch hackers are shifting their interest from hacking NASA, FBI and similar organizations in the US to hacking Android phones. Or maybe it's one of their favourite ways to have fun in their idle time. Who knows?
Anyways, here's a Thanks from me, mr. Andrei, for your contribution to this community.
Click to expand...
Click to collapse
I do what i can. There are many devs that know much more than me. Your thanks are appreciated
For me it's still strange, tho. Only data and system could be "infected"
Take a look at this: http://forum.xda-developers.com/showthread.php?t=1399076
It's a scheme i made on how HTC and Nexus devices work. (How they boot, what are the individual partitions, etc)
Clawsman said:
Yeah..as the title says.. 3 weeks ago this hacker hacked into my network..
placed rootkits in all my 3 computers and then hacked its way to my Desire and my wifes iphone. good thing i had wireshark running same time.
So.. 5 units hacked with the method in like 1 houre. Bad luck for me i guess.
And kaspersky didnt give me any warnings at all. bye bye kaspersky.
Anyway... i flashed my desire's HBOOT just to be sure. after i did a check with "AutoKiller Memory Optimizer" all kinds of malware services was attached to most of my apps.
1- downgraded HBOOT
2- flashed stock HBOOT from alpharev
3- Changed recovery from CWM to 4EXT as i suspected the recovery being infected somehow.
I checkd my log... the hacker had removed some files and moved shell files from an folder to another as well as busybox and so on. it was so many i thought il be better of installing new ROM.
I tried with Gingervillain first... everything installed fine..
checking with "root explorer" i see same files that had been moved and added was still there.
OK.. i tried again..
full wipe with 4ext and then installed Runnymede.. still.. when i check my root partition most of the files still there and i get same results doing a root check.
any idees...? im not sure if my kernel is right. it should be, when i installed Runnymede. when checking kernel v.
it says.. "[email protected] #11"
May be kernel rootkit? does the kernel start before recovery?
can someone plz confirm this?
baseband seem to be the same
any advise as for how to start from scratch will be much appreciated.
Click to expand...
Click to collapse
An example of those infecting file?? What file in your root partition?? What path? Rom files are only on /system
Inviato dal mio Galaxy Nexus usando Tapatalk
I never use a anti virus and until now never have a problem...As i know!
Well it happened to me..
I have deleted everything.. I remember i checkd my log, and busybox files was moved to the system folder.. And all kinds of services was attached to Google map, calender, Facebook, wifi apps, market, etc..
And new apps installed like vpn, cam apps, recorders.. etc
Im currently using the free lookout...
And want to Buy a security tool.
Any advice Will be much appreciated.
Sent from my HTC Desire using xda premium
Hello fellow XDAers,
My wife replaced her Samsung Gravity Smart with the T-Mobile MyTouch Q, AKA the Huawei U8730 (not the older LG C800 model w/ the same name). She gave me the task of cleaning the junk APKs off of it to de-clutter it.
Rooting the phone was the first task. This method worked perfectly for me without any fuss (the app will return error 64, but after installing Superuser and rebooting, I had root access). I was able to use Titanium to remove much of the crap ware, but the most annoying bits gave the error "cannot find APK." Weird.
After digging around, I took an inventory of the apps in /data and /system.
The T-Mobile junk wasn't there.
I threw busybox on the phone and used the 'find' command, and I found where the apps were hiding: /cust/t-mobile/us/apps, which is a loopback-mounted ext3 partition. I tried to remount it read/write, but got 'permission denied' error. I figured something had the filesystem locked, so I ended all the apps that were running and tried again, but no luck.
However, I was able to remount the volume that held the ext3 image file read/write. It mounts to the /.cust_backup directory.
IMPORTANT NOTE: For those who will be following these steps themselves, at this point you will want to make sure to go into the Applications manager and uninstall any updates downloaded for the crapware you are going to remove. I will explain why below. It's not absolutely critical, but it will save you some head-scratching.
I remounted the partition read/write, grabbed the image file (located in /.cust_backup/image/cust.img), and uploaded the image file to a linux server.
On the linux server, I mounted the image, nuked the unwanted APKs, and unmounted the filesystem.
I created a backup of the original cust.img file, then overwrote the one in /.cust_backup/image
Last step was to reboot the phone, and most of the junkware was gone.
Here's where the head-scratching came in. A couple of the apps were still there, and I didn't know why. I double-checked the phone, and the APKs were in fact deleted. Then I realized: the app had received an update and I was seeing the update. When I uninstalled the update, the uninstall "failed" but the icon still disappeared. However, I had to reboot the phone again to fully remove it.
So, here's the process in a nutshell:
1. Uninstall all app updates for the crapware you plan to remove
2. Root the phone using This method .
3. copy down /.cust_backup/images/cust.img
4. Using a linux system, mount cust.img as a loopback device, then delete the unwanted APKs (they will be in t-mobile/us/apps)
5. Unmount the image (this writes your changes back into the cust.img you mounted in step #3)
6. On the phone, remount /.cust_backup r/w
7. overwrite /.cust_backup/images/cust.img with the modified version
8. Reboot the phone
That's it! Enjoy your uncluttered phone!
I know it's been a while since the original post, but I was wondering if OP has had any problems with the phone since then, or if anyone else has tried this with the Huawei u8730 and had success. My wife also wants all this crap removed from her phone, but she would probably murder me if I bricked it in the process.
Thanks!
Just on a side note here as I'm still using this device. How did you get around the non-working tethering on this device? Both the USB and Wifi hotspot won't work unless you've subscribed to the T-Mobile Smartphone Mobile HotSpot app option on your account? Mine is unlocked and being used with another carrier, but only recently wanted to tether to it so I can't figure out how to correct this one. Also still looking around for any working custom ROM for this. Thx.
Okay, I've rooted my n5110 8.0 and manually flashed 4.2.2 XXCMH3. I have reset the flash counter with triangle away. It shows software update is available. Is it possible to use OTA Root keeper to update the OTA update? IM me or answer here please no guesses. Thanks in advance.
capitoldach said:
Okay, I've rooted my n5110 8.0 and manually flashed 4.2.2 XXCMH3. I have reset the flash counter with triangle away. It shows software update is available. Is it possible to use OTA Root keeper to update the OTA update? IM me or answer here please no guesses. Thanks in advance.
Click to expand...
Click to collapse
Yes it should work fine, there have been issues with 4.3 but in a video I watched about the app the update from 4.2.1 to 4.2.2 went smoothly for him. Granted nothing is guaranteed. If you are using superSU you can buy the pro version and it has an OTA survival mode. Alternatively you could also flash the update via odin or recovery but since you're asking about OTA Root Keeper I'm sure that isn't something you are interested in. Make sure you follow the steps and make any other backups you can because you never know.
http://www.youtube.com/watch?v=ky5miA8ilr0&noredirect=1
That's the video I watched also I looked at other posts regarding known issues and it doesn't look like there are problems specifically with certain UI types (Touchwiz Sense etc). GOOD LUCK let me know how it goes
Thanks.
dwibbles33 said:
Yes it should work fine, there have been issues with 4.3 but in a video I watched about the app the update from 4.2.1 to 4.2.2 went smoothly for him. Granted nothing is guaranteed. If you are using superSU you can buy the pro version and it has an OTA survival mode. Alternatively you could also flash the update via odin or recovery but since you're asking about OTA Root Keeper I'm sure that isn't something you are interested in. Make sure you follow the steps and make any other backups you can because you never know.
http://www.youtube.com/watch?v=ky5miA8ilr0&noredirect=1
That's the video I watched also I looked at other posts regarding known issues and it doesn't look like there are problems specifically with certain UI types (Touchwiz Sense etc). GOOD LUCK let me know how it goes
Click to expand...
Click to collapse
Thanks for the response and link, I really appreciate it. I actually do have the pro version of superSU. I was unaware that superSU has that option.
capitoldach said:
Thanks for the response and link, I really appreciate it. I actually do have the pro version of superSU. I was unaware that superSU has that option.
Click to expand...
Click to collapse
Did it all work out?
dwibbles33 said:
Did it all work out?
Click to expand...
Click to collapse
Yeah I'd really like to hear back from the OP about this.
No it didn't
dwibbles33 said:
Did it all work out?
Click to expand...
Click to collapse
Although I do appreciate the time. I was unable to make it work. I was informed by Mr hyde, that this is one of the models that always have +1 if you have a custom recovery or any other changes to the device. Not sure though, because when I when I was on xxchm3 I tried the update and instead of saying device has been altered it said successfully registered. So I'm not sure what that means. Currently I'm having another issue I'm trying to figure out. I have a large amount of misc. Files taking up a few gbs of space. I have factory reset and wiped partition each time, but when I install superSU pro version it says needs to update binary. So I do, it restarts into cwm 6.x and says either erase disable stock recovery, I haven't accepted so I select go back on the bottom of the list, it restarts and everything appears to be working, but now I'm wondering if I am supposed to delete/disable stock recovery or if there's no way to get stock recovery back if I do erase/ disable. And also if that is where my misc. Memory is allocated or it is something else entirely, as when I backup I backup to external sd card. Thanks for the consideration and I will hit the button as well. It is really cool of you to follow up.
capitoldach said:
Although I do appreciate the time. I was unable to make it work. I was informed by Mr hyde, that this is one of the models that always have +1 if you have a custom recovery or any other changes to the device. Not sure though, because when I when I was on xxchm3 I tried the update and instead of saying device has been altered it said successfully registered. So I'm not sure what that means. Currently I'm having another issue I'm trying to figure out. I have a large amount of misc. Files taking up a few gbs of space. I have factory reset and wiped partition each time, but when I install superSU pro version it says needs to update binary. So I do, it restarts into cwm 6.x and says either erase disable stock recovery, I haven't accepted so I select go back on the bottom of the list, it restarts and everything appears to be working, but now I'm wondering if I am supposed to delete/disable stock recovery or if there's no way to get stock recovery back if I do erase/ disable. And also if that is where my misc. Memory is allocated or it is something else entirely, as when I backup I backup to external sd card. Thanks for the consideration and I will hit the button as well. It is really cool of you to follow up.
Click to expand...
Click to collapse
By +1 do you mean the flash counter? If you boot into download mode it'll show you a flash counter. For the binary update select the Normal install not the TWRP/CWM option. You shouldn't have to flash the binaries they SuperSU should be able to update within the app. As for the misc files it could be the partitions are messed up, if you use a root file explorer goto /data/media check those folders, your 0 folder should be your normal files but see if another 0 shows up or it might have a clockworkmod folder that has backups in it (I've seen the backups that are supposed to end up on the extSd end up there so its worth checking). Let me know if you want/need any more help I have worked my way through a lot of crap between my tablet and phone and I wish there was more help out there than there is so please let me know if I can help.
0 file in 0 file like 4 times each dated days I flashed different builds
dwibbles33 said:
By +1 do you mean the flash counter? If you boot into download mode it'll show you a flash counter. For the binary update select the Normal install not the TWRP/CWM option. You shouldn't have to flash the binaries they SuperSU should be able to update within the app. As for the misc files it could be the partitions are messed up, if you use a root file explorer goto /data/media check those folders, your 0 folder should be your normal files but see if another 0 shows up or it might have a clockworkmod folder that has backups in it (I've seen the backups that are supposed to end up on the extSd end up there so its worth checking). Let me know if you want/need any more help I have worked my way through a lot of crap between my tablet and phone and I wish there was more help out there than there is so please let me know if I can help.
Click to expand...
Click to collapse
Ok, so I started over with OUEMFI1 factory rest and wiped partition. I still have misc. files. So, I went to data/media I found the 0 file, inside that file is another 0 file, inside of that file another 0 file, and on and on all with different dates. Should I remove the 0 files within the 0 files, are they necessary, or they left over each time I flash? I did mean flash counter, but I haven't checked it via download mode, I will do that.
capitoldach said:
Ok, so I started over with OUEMFI1 factory rest and wiped partition. I still have misc. files. So, I went to data/media I found the 0 file, inside that file is another 0 file, inside of that file another 0 file, and on and on all with different dates. Should I remove the 0 files within the 0 files, are they necessary, or they left over each time I flash? I did mean flash counter, but I haven't checked it via download mode, I will do that.
Click to expand...
Click to collapse
Okay so what happened with all those 0 files is basically with the ability to change users that number changes if you add more users. For whatever reason when you flash a ROM it creates a new 0 file and pushes your old 0 file further in. If you go through those files you may see folders you used to have on other ROMs containing old stuff you had. So if you have stuff to keep then copy it to the /0 folder then delete the extras. I have been trying to modify a script from the GSIII that basically wipes everything except your external card but it didn't work last time. My advice would be to back your files up to your external, go into recovery and instead of a factory reset go into mounts and format /data (again be sure to back your stuff up because this will take it all out). That should wipe out everything (0 files and such) I would go as far as formatting system too. MAKE SURE you have a ROM on your external card because formatting /system will wipe out your existing ROM, but you will get a fresh start and at that point you know that nothing is hanging around from before.
Alright, I'm running CyanogenMod 11 with TWRP as my recovery. When I try to change my build.prop it tells me that the action is not allowed because the system folder is mounted as Read only and not as R/W. I have tried using the chmod syntax 755 while in recovery but, after rebooting nothing has changed. Using my file manager (Solid Explorer) I have tried changing the permissions to be R/W by using the same chmod syntax. What have I done or am I doing wrong? I have never crossed this issue before with any other ROM or phone and I would like to add some additional speed and smoothness tweaks to the ROM build.prop. Have I tried another ROM to see if the same thing continues to happen? Nope, I sure haven't. If I did though and something magically changes to where it would begin working using another ROM, I still would not know how to fix the issue that I'm faced with now. Will ya please help? Thank you for your time in advance as well!
The drive isn't being mounted by solid Explorer as read/write. I'm not familiar with the app so can't explain how to do it but it may be in the options somewhere or a button on the screen.
You could try es file Explorer. It's free and works for me.
-> Sent from my mind to your screen.
Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime.
Well, I just tried ES File Explorer and it said that I'm mounted as R/W on my system folder, same as it did on Solid Explorer, yet once I try to alter anything I still receive the same "Operation Failed......System Mounted as Read Only" message. I have even switched ROM's to see if maybe, just maybe, it was some sort of CM 11 bug. Everywhere I look online says to correct it through my recovery and since that doesn't work..........? I'm at a bit of a loss now! I have granted both file managers Superuser rights. Hell my Superuser auto-response is always set to grant all apps that permission. And as far as the form of Superuser I'm using goes, I'm just sticking with the CM stock Superuser because whenever I attempt to use SuperSU all sorts of stuff begins to fail.
Is your SD card formatted as FAT32....or EXFAT...???
Needs a possible format again it sounds like....IMHO..g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...
Haven't thought about it possibly being my SD's format being that I am trying to access my systems files (i.e.- build.prop, system apps, etc.) and not the external SD Card, but what the hell?! I reckon I can always give it a shot. Could very well be that simple since I just dropped $100.00 on a stupid Lexar 64 Gig. Micro SD about the same time this issue arose. Hope so even if i do end up feeling like a dumb ass later on. It's getting annoying! I've tried several different ROM's, file managers, running syntax in the emulator, and anything else I could dig up now and this isn't quite my first Android experience, still relatively new though, so I know I'm not flashing anything wrong or outta the ordinary. Give me bit to take care of some every day life crap and I'll report my findings back to ya.
Dead serious, I did not do anything different whatsoever and it began to allow me to change permissions on my system files or whatever else I wished to do to it......?! No Earthly idea what was/did go on for it not to allow me to for the time it didn't, but outta nowhere, as I said, it is working again. I did wipe and flash numerous ROM's without any luck and even had flashed the one that it is working on now, but it didn't work the first or second time I flashed it. Never even got the chance to reformat my SD Card. Hell, I don't know.....!
countryboy092782 said:
Dead serious, I did not do anything different whatsoever and it began to allow me to change permissions on my system files or whatever else I wished to do to it......?! No Earthly idea what was/did go on for it not to allow me to for the time it didn't, but outta nowhere, as I said, it is working again. I did wipe and flash numerous ROM's without any luck and even had flashed the one that it is working on now, but it didn't work the first or second time I flashed it. Never even got the chance to reformat my SD Card. Hell, I don't know.....!
Click to expand...
Click to collapse
Running Jellywiz Extreme Rom 4.3 for my Note 2 on Verizon, and ever since i updated it to 4.3 on an unstable original ROM (Davidson3680's OG 4.3 ROM pre-2014), i havent been able to mount system as R/W.
I keep coming back to the possibility that in both of these recent cases that the file structure is somehow corrupted...
A possible 4.3 return to stock using Zen Arcades 4.3 stock rom may correct the file issues and restore the external functionality...
I'm still perplexed about the differences in flashing success based on whether or not a user has taken an official 4.3 update versus a user who has not...and the variables in function using the exact same software's...
The Zen thread method seems to be the stable and reliable way back to full function...or at least the best way to build the file structures back within their respective partitions...
We are playing very near the partition level...but I don't think it's a partition/pit issue....rather the broken file structure inside...
I'd be interested in the results of that test using Zen's files in the attempt to repair the files...and path to the SD...
If you are willing to try that...and meet success...it would solve a good half dozen device issues across different users in one pass....g
Sent from my NOTE 2.750...
Courtesy of our amazing developers...