Related
So, yeah. This is deodexed & zipaligned System. It will overwrite your /system partition so any changes you have made (theme, hosts file, etc...) will be lost. In addition to the deodexed /app and /framework folders this will add a transparent notification bar and ad blocking host file. Why? Cause, I made this for myself, so it's the way I like it. Flash this if you want, I'm not forcing you to. Nor will I be held responsible if it eats your first born or tries (succeeds) to commit suicide. You've been warned. If you just want the deodexed files, I'll leave the manual method below and you can do it the hard way. Maybe I'll get the update-script working at some point, but I don't know. If you're good with the new sytax for CWM's update script, hit me up in IRC, I'm stumped.
Note: As I said, this formats your /system partition. Not your /data partition, so all your apps and such will still be there.
So, Once More
What you get:
Deodexed & zipaligned (ready to theme) system
Transparent Notification Bar
Ad blocking host file
No warranty
No mobileprint apk. I couldn't get it deodexed no matter what I tried and can't be bothered to try anymore. Never used it. Never will.
Nandroid Recovery Method
YOU MUST HAVE CWM RECOVERY INSTALLED
use either the bootstrapper from the market or follow his instructions found HERE be careful and use this at your own risk, it is very beta. I recommend doing a backup from it before you flash this as well.
How To Flash
extract the folder to /sdcard/clockworkmod/backup
Boot in to CWM Recovery go to advanced restore, select restore /system only. Once that is complete clear the cache, reboot. you can then delete your dalvik cache (note: clearing the dalvik cache doesn't work via CWM currently). That's it.
If you have anything go wildly crazy, lemmie know. Also, I doubt it's success on any other carriers version of Tab, but if you feel like it, go ahead, I already gave you responsibility for your own actions. Do what you want with it. If it works though, let us know.
Oh yeah- Download if you feel like it.
ODIN Restore Method
Flash via Odin PDA PDA PDA PDA PDA PDA PDA
If you need any more instructions on how to flash via odin, search.
Download the tar HERE
OLD PITA BORING MANUAL METHOD
FIRST
So, Back up your system first. Wait, yeah, you can't in recovery yet, so seriously people- don't touch this yet unless you know what you're doing since you won't have a supersimplehappynice backup to revert to if you mess up. Only the cold, cold darkness that is Factory Reset.
I haven't been able to manually deodex these successfully yet. If anyone has, please, hook me up and I'll update the package (or I'll update it when I get around to deodexing them).
What are these for???
These files will allow you to theme your Tab, some say it speeds up your system and others say it allows you to get all the ladies and even others think it's a threat to democracy so PROCEED WITH CAUTION.
What do I do with these???
Okay, this isn't hard, but it's easy to get a negative result if you skip a step so keep reading, follow the directions and don't blame me if you are singled out for the 3D imaging system at the airport.
Basically you want to use ADB push or Root explorer to delete the apks/jars/odex/*.* in /system/app and /system/framework and then replace them with the files from the archive (the archive has an app and a framework folder for you, I think you know where each belongs).
Now if you use root explorer to delete everything from /framework, things will get sticky for a minute and you'll get some FC's and such, but I was able to copy all the files over, so just be patient.
Also, remember how I told you to read the directions? KEEP READING OR YOU'LL MISS IMPORTANT STUFFS. So, hi there. You shake the boredom out of between your ears and giving me your full attention again? Good. Now is important. You are really going to want to clear both your normal, and dalvik chache. Otherwise you're going to reboot and your phone is going to be slower than an Audi R8. You can do this with cache cleaner, recovery (if you're running noobln's script) or adb. I used recovery for standard cache and this adb command.
Code:
adb remount
adb shell rm -rf /system/sd/dalvik-cache
Then just reboot and start porting some themes over for me (revolution plzkthx).
A couple of notes:
All these are from a VZW Tab. Will they work on your T-mobile one? Well, find out, if you want, or not. I don't care. Just don't come crying to me if you screw up your phone. I did not put a gun to your head and force you to use these files.
Also, if you screw up your Tab, for the love of the gawds, it's not bricked, calm down.
I suppose you want the download link, huh.
Here you go for the manual files.
Finally, if you like my work, donate to me so I can donate money to devs that make my world easier (and therefore yours).
cheers for the upload
any chance of a deodexed email.apk as it's not in there?
Any screenshots of what the themed versions can potentially look like? Need to weigh up the pro's / con's of being "experimental"
Thanks
Johnston411 said:
cheers for the upload
any chance of a deodexed email.apk as it's not in there?
Click to expand...
Click to collapse
Darn it, I'm sorry, I meant email.apk and not browser.apk. I haven't been able to deodex that apk yet. Sorry I should have it done soon but in the mean time you can use gmail or go back to an odexed FS. Original post updated.
risq said:
Any screenshots of what the themed versions can potentially look like? Need to weigh up the pro's / con's of being "experimental"
Thanks
Click to expand...
Click to collapse
They look exactly the same as on your Tab, just without being odexed. This is not a theme, nor does it change the appearance of any of these applications. It changes the way they function within the OS and allows for the ability to theme.
I mean absolutely zero offense by this, but if you're weighing out the pros/cons of doing this, you probably shouldn't. Just wait a while longer for recovery to be functional, then people will start putting out easily flashable ROMs and themes.
Sorry i misunderstood.
I thought they had been edited / themed already from the initial description..
Its been a long day. Im a risk taker anyways but ill pass for time being.
Keep up the good work.
Sent from my GT-P1000 using XDA App
Johnston411 said:
cheers for the upload
any chance of a deodexed email.apk as it's not in there?
Click to expand...
Click to collapse
Actually, I just got email deodexed.
HERE YOU GO
I'll have the other remaining apks out soon.
very kind.
I want to try it on my dell streak but the odexed email.apk kept force closing.
Let me know if it works.
f.c. as soon as you launch it.
i'll see if it needs any framework stuff added to work tomorrow.
Hi Boushh,
After removing files in both folders it FCs many and froze. It won't reboot now. Let me know what I did wrong. No compliants like you mentioned. Any rescue?
Thanks
Like I said, you'll get that, I was able to copy them over with root explorer between the FC's. If you can not easily do that, plug it in and adb push it.
Added a flashable zip to the first post, happy holidays guys and gals!
I tried the flashable zip with CWM, but it aborts when install.
How can I clear cache & dalvik cache in CWM. There is only with the clear data/factory reset.
Can you tell me the exact error that recovery prints?
I'm almost positive *clear cache* is in the root of recoveries settings and then *clear dalvik cache* is under advanced.
Error is "Installation aborted"
I use the CW Bootstrap recovery, then reboot recovery that purchased from Market for "Bootstrap for Tab".
Select install zip in SD card. Wipe clear cache & in advance for clear dalvik cache. It's still installation aborted.
Okay, I need to change something in the install script, illtry and do it in the next couple hours.
If you ever get the other apk's integrated into the update.zip, I'd be happy to give a test run on my VZW tab.
I did the manual files delete and paste before, but froze the Tab and non bootable anymore. I'm on my second tab, definitely need the update zip for this.
Sent from my SCH-I800 using XDA App
Just an update- I got back from vacation last nightand need a day to recover but I plan in fixing the zip tomorrow.
Also, regarding the mobile print apk, I have tried using every resource possible to deodex it without success so I've given up on it. I blame bad coding, lol.
If any of you care about quadrant scores (which I don't) I was recently asked what I was getting, around 1150-1170. So a bit better I than stock I suppose bit I only deodex for themes really.
I have searched the entire forum and haven't found the answer to my problem...I have even asked in the rom specific thread (where other people have had a similar problems) but my question (and theirs) just gets overlooked!!
So here it is.
I have both radio S-off and the End Hboot and have flashed three different custom roms on my HD (the Core Droid, Revolution HD and LeeDroid) all giving me the same problem.....I cannot set the system as r/w using apps such as Root Explorer and SUFBS!
I tried entering the mount command by itself in a terminal on the phone and I get:
# mount
mount: no etc/mtab
I can however mount the system from adb shell by inputting: mount -o remount,rw /dev/block/mmcblk0p25 /system
but that isn't really a solution!
I have a nandroid backup of my original stock rom which I have rooted and I can mount the system fine using root explorer and do not get this 'no etc/mtab' message when I type mount in the terminal.
I find it odd that it occurs with three different custom roms but not on my original stock rom so maybe it could be the way I flash the roms? ...I always use the Full_Wipe.zip with CWM recovery which formats the boot, system, data and cache partitions and then I apply the rom.
I've been pulling my hair out over this...and I know it must be something simple, but I've been stuck with this problem with no solution for a week!
Does anyone have any ideas?
EDIT: It turns out that some of the custom roms have limits in place that prevent editing the system and therefore were causing errors. Have tried the Cyanogen rom and have not encountered the errors/restrictions so it was definitely due to those custom roms. Not really a solution, but found the 'cause' of the problem.
Hmmm....looks like I'm the only one with this problem. Has no one else had anything similar?
your not the only one, i hbave had this too, this prevents you from removing apps doesnt it, now is it the 1.72 rom or the 1.34 rom
try to download Root Tools and go to Extras and then go to MIscellaneous and select "mount system read/write". if it does not work i guess that you have an issue with phone.
if its a 1.72 rom then you wont be able to mount it, i think HTC have decided to change the mount partition or something along that line, there isnt an issue with the phone, its just HTC have plugged up the root boothole that there was.
mariosraptor said:
try to download Root Tools and go to Extras and then go to MIscellaneous and select "mount system read/write". if it does not work i guess that you have an issue with phone.
Click to expand...
Click to collapse
Just tried that option and it does work as it succesfully mounts the system as r/w. However, if I go into root explorer it doesn't allow me to toggle the system as r/o....so the mount commands from my currently installed apps are not working. Could it be something to do with restoring the apps from my old Milestone onto the Desire HD using totanium backup? Actually restoring through titanium backup shouldn't be a problem since it works with the stock rooted rom.
fkofilee said:
if its a 1.72 rom then you wont be able to mount it, i think HTC have decided to change the mount partition or something along that line, there isnt an issue with the phone, its just HTC have plugged up the root boothole that there was.
Click to expand...
Click to collapse
I've heard about that problem too....but my current rom is based on the 1.34 rom (Core Droid V1.5), so its not that...
after doing what you have to do you can go again to Root Explorer and remount as read only.
fl4r3 said:
Just tried that option and it does work as it succesfully mounts the system as r/w. However, if I go into root explorer it doesn't allow me to toggle the system as r/o....so the mount commands from my currently installed apps are not working. Could it be something to do with restoring the apps from my old Milestone onto the Desire HD using totanium backup? Actually restoring through titanium backup shouldn't be a problem since it works with the stock rooted rom.
I've heard about that problem too....but my current rom is based on the 1.34 rom (Core Droid V1.5), so its not that...
Click to expand...
Click to collapse
mariosraptor said:
after doing what you have to do you can go again to Root Explorer and remount as read only.
Click to expand...
Click to collapse
I guess thats the best option for now...not a complete solution, but a work around that doesn't require a pc at least.
Would still be good to find the cause and fix it!
I've got the same issue! Are you sure the error you receive is 'no etc/mtab' and not 'no etc/fstab'?
Anyway I've been using the App 'Mount System (rw/ro)' as my solution for now and it works a treat. Still, as you can imagine it is not a permanent solution!
The only thing I feel may have contributed to the problem was my original root attempy via Visionary failed and I had to wait until the R13 before I could unroot and root again. Possibly something got borked along the way. Did you have any similar issues?
Will be keeping my eye on this thread and if I do find a solution I'll let you know.
Regards.
It’s definitely a ‘no /etc/mtab’ error.
When I rooted I used Visionary r14 and the only hiccup I had was that it didn’t permaroot on the first try so I had to redo it.
It’s odd that my nandroid backup of stock doesn’t give me the error and its only the custom roms that do! I have a feeling it might be something to do with an incorrect/incompatible Busybox installation with the custom roms...
sounds more app related as you can use another app to mount the system, but not with root explore. i know this is obverse an you probably done it ,have you uninstalled root explore and reinstalled from market as you said you used titanium backup.
you could copy /etc/mtab from stock an place on sdcard and paste it in the custom.
not a solution but more see if its just a file that's missing
the only file i could find was vold.fstab and my base rom is 1.72.405.3 and root explore works fine.
cattleprod said:
sounds more app related as you can use another app to mount the system, but not with root explore. i know this is obverse an you probably done it ,have you uninstalled root explore and reinstalled from market as you said you used titanium backup.
you could copy /etc/mtab from stock an place on sdcard and paste it in the custom.
not a solution but more see if its just a file that's missing
the only file i could find was vold.fstab and my base rom is 1.72.405.3 and root explore works fine.
Click to expand...
Click to collapse
I've tried looking for /etc/mtab in my stock rom but its not present..I don't think its a physical file thats why it can't be copied....
But I think you may be right about it being an app based problem...just tried LeeDroid V1.3 (based on 1.72 rom) out of curiosity and root explorer still wasn't working. I then wiped again but installed root explorer fresh from the market instead of titanium backup and it is now working!! YAY!!
However, SUFBS still does not work and returns 'no /etc/mtab' when I type 'mount' in its terminal and reinstalling (either from titanium backup or fresh from the market) does not make a difference. Since root explorer is now working I believe that the dev for SUFBS needs to update his app maybe?..or is there still something wrong with my system?
yes sir !!! that is where your correct !!!
the current custom roms bar... Cyanogenmodm dont allow the current installed apps to be changed due to your error message.
IF YOU ARE CONFIDENT WITH ADB COMMANDS; you can have ago at pushing and pulling and mount it that way using a PC
but be very careful as you can damage your phone by doing this
fkofilee said:
yes sir !!! that is where your correct !!!
the current custom roms bar... Cyanogenmodm dont allow the current installed apps to be changed due to your error message.
IF YOU ARE CONFIDENT WITH ADB COMMANDS; you can have ago at pushing and pulling and mount it that way using a PC
but be very careful as you can damage your phone by doing this
Click to expand...
Click to collapse
Ahhhh, if thats true then it makes sense! Thats why the custom roms were giving me trouble but not my rooted stock rom and why adb commands from a pc work. I guess its a precaution but still an inconvenience...especially when I want to make changes/do something away from the pc.
......the question is: is it true? are you 100% sure the custom roms don't allow changes?
its 100% true, well most of the new ones anyway, CM was built from open source code and is completly there creation BUT
custom roms created from stock are basically modded ROMS
Just tried Cyanogenmod rom 6.1.2 and have had no issues at all! So it seems fkofilee is right...some of the custom roms just don't allow changes to the system.
So not really a solution but atleast found the 'cause' of the problem.
I noticed you said you used the full wipe .zip has everyone else used it ??? As I did not use it the first Rom I flashed was leedroid 1.2 and then 1.3 the only thing I used was cw recovery wipe/factory reset and my root explorer never failed can toggle between the two and when I first booted all my apps synced back via market did not use titanium backup not keen on it also I've read a few posts problems with titanium not restoring apps also read somewhere the full wipe zip doesn't always work right maybe its the wipe and titanium that causing it
Just a thought
Sent from my leedroid v1.3a DhD via xda app
I use full wipe. Zip but I never have problems with root explorer. Been using more than 1 Rom. ( Modaco r 2, leedroid 1. 3, Hd revolution. And also I have modded them a lot to look aosp.
Sent from my LeeDroided Desire HD
First off I'd like to start off by saying that I am kind of an idiot...with that said; I like to mess around with important files on my device(Acer a100) even though I have absolutely no clue what I'm doing.
Using titanium backup I uninstalled that download system apk. The one with the green icon and the white arrow pointing down. Now when I try to restore it through tit. Backup it will just freeze and keep saying that it is restoring and I have to finally force close titanium. I have also tried messing around with permissions in root explorer, fixing permissions in rom manager, navigating to system/app and installing it manually through a file explorer( get message install fail), and hard resetting.
The main problem is that everything I download will show in my notification bar and after I close/exit them they come back 5-30 min later. If I click on the download in my notification(not on the x) then my notification bar just closes. I can kinda fix this by turning my notifications off or cleaning data/cache on ?download storage? Apk/app.
Does anyone know of an easy fix for restoring this system apk. For there are no custom roms or recovery sources for this device that I have seen yet.
Thank-you, Robb
Get the system.apk file from the roms here
http://forum.xda-developers.com/showthread.php?t=1307046
i tried downloading those recovery files and twice they came back saying they were corrupted, is there any way someone can just upload the system file i need from their a100...its the downloads apk. the green icon with a white arrow pointing down
RobbandJenica said:
i tried downloading those recovery files and twice they came back saying they were corrupted, is there any way someone can just upload the system file i need from their a100...its the downloads apk. the green icon with a white arrow pointing down
Click to expand...
Click to collapse
PM me with your email address, I'll email you the apk from my A100, I'm still running the stock rom that I pulled it out of the box with.
You can download it straight to your tab from your email, beforee you do, get a file manager (like es file manager) from the market. You will be able to get to your downloads folder from there and install it.
ummmmm............ could you repeat that?
6stringandy said:
PM me with your email address, I'll email you the apk from my A100, I'm still running the stock rom that I pulled it out of the box with.
You can download it straight to your tab from your email, beforee you do, get a file manager (like es file manager) from the market. You will be able to get to your downloads folder from there and install it.
ummmmm............ could you repeat that?
Click to expand...
Click to collapse
He's got Root Explorer, that should do the trick.
To the OP: You are mounting the system partition R/W in Root Explorer when you try this, aren't you? Hate to ask a dumb question but.....
Yes I am hitting that button up top on root explorer changing it from r/w to r/o but I think some how I just got the wrong apk....after titanium wouldn't restore it I think I remember copying apk. From my phone (g2x) and attempting to restore those...dumb, I know I might of tried changing the names of the apk. Too,..like I say I f*** with s*** I have no business Fu****** with. I will p.m. my email now maybe I can get a screen shot of the system files if anyone feels up to it, so I can cross check proper name and sizes
How about just reinstalling the 3.2.1 update that is in the developer section. There should be no reason to factory reset since it is the same version. I have soft bricked mine a few times and I have just did the update again.
I even upgraded from whatever version the device shipped with to 3.2.1 without wiping the data.
A100 development section??? I see three a100 recovery downloads and one a101 recovery in our development section but when I download them i t says they were corrupted...if those are what your talking about...which one exactly should I use and what do I do with the file after words???
----sorry two that say a101 and two a100
So should I use file Id # 115,116,117,or 109
Use the one in this post. It is already decrypted. The ones in the frist post need to be decrypted using the Acer decryption tool. I have used the one I linked to probably 20 times. Once you run the update you will have to re-root the tablet.
thank-you all..recovered and fixed!!!
I was able to fix my problem by using the recovery update zips. But I want to thank everyone that helped, and remind people from experience to freeze unwanted system apps instead of uninstlling in titanium backup.u
Very important advice also is to search and read before starting new posts. I could have saved some time and headache just by doing that...the answers were just a couple paragraphs away the whole time.
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...
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.