Hello all.
I started to develop my edition of JB, but i had a problem. The system partition is about 600MB, and the deodexed version of stock samsung's JB rom is about 700+MB. (Odexed should be about 800MB)
Firstly i did extract system.img to deodex it but a problem occured. Many apk files (about the half!) were missing (.odex files were still there). I was stuck. So i did an "adb pull" from my phone and i had all the system files, strange huh? I deodexed them (=> smaller size), removed bloatware and the system folder was about 675MB. I zipped it and flashed it from recovery. Phone was booting and booting and booting for 15 minutes... I re-checked the files and i saw that the system files were bigger than the system partition.
Then i checked for a hidden partition to find the "extra" space required for system. In "CSC" tar file of JB there is a hidden.img. In GB there was a small video by samsung so i thought that it would be again the same video or similar. I was wrong. Inside this file there are many apk system files (about 200MB!). I checked the firmware in my phone with root explorer and i saw that there are many symlinks from /preload/simlink/system/app/ to /system/app/ . That explains the Samsung's logic. Anyway i think that this is a bit fail. Why samsung didn't resize the system partition so it can handle all system files? Anyway, i will make a flashable test rom with some files in /preload/ and then i will symlink them (in updater-script) to /system/app/.
So for conclusion there is:
-a /system partition about 600MB and
-a (fake system) /preload partition about 250MB to handle most of the /system/app/ folder.
Also, temporary CWM6 for JB is working fine to install zips or anything or for backup and restore.
I thought it will be useful info for any dev here.
I solved this major problem and i will focus in Kyrillosv6b JB rom this week. I have already done many mods for JB but i couldn't test them because of that.
Have a nice day.
Maybe they just used this solution for the xxmb2 test version and for the final version they will resize the partition table.
It's a "strange" solution but I think not that bad.
We still don't know where is the imei/simlock data it's possible they don't want to modify the partition layout if not really necessary, to keep important data safe.
Repartitioning the device is always risky...
Sent from my GT-I8160 using xda app-developers app
Szaby59 said:
Maybe they just used this solution for the xxmb2 test version and for the final version they will resize the partition table.
It's a "strange" solution but I think not that bad.
We still don't know where is the imei/simlock data it's possible they don't want to modify the partition layout if not really necessary, to keep important data safe.
Repartitioning the device is always risky...
Sent from my GT-I8160 using xda app-developers app
Click to expand...
Click to collapse
Hmm simlock and imei data are on /efs partition... But we did repartition the device for JB. There wasn't a "preload" partition on GB i think.
It's not on efs I erased my efs partition to try (ofc. I made backup first) and the imei was ok
I tried to restore efs from a different phone and nothing changed.
I remember there was something else not preload will check tomorow but I'm sure that unpartitioned space was only 10 MB and it's still 10 after Jb.
Probably preload in gb was named hidden just like the file and the video file was moved to internal sd or symlinked.
I know we had to rp but I can't see much difference, even the counter data is stored on the same offset.
Sent from my GT-I8160 using xda app-developers app
Yeah. 30 APKs were not deodexing on mine. permissions were rwxrwxrwx when I looked. some didn't have sizes, others had -1 bytes.
Is there any way we can deodex JB ROM? I don't know how to mod and odexed ROM.
Dr01nE said:
Yeah. 30 APKs were not deodexing on mine. permissions were rwxrwxrwx when I looked. some didn't have sizes, others had -1 bytes.
Is there any way we can deodex JB ROM? I don't know how to mod and odexed ROM.
Click to expand...
Click to collapse
I will upload the deodexed MB2 tomorrow. but as i said at the first post, it doesn't fit on /system partition.
kyrillos13 said:
I will upload the deodexed MB2 tomorrow. but as i said at the first post, it doesn't fit on /system partition.
Click to expand...
Click to collapse
I have completely deodexed it the problem is flashing. I also get stuck in bootanimation and it keeps vibrating.
Let me know when find a way to flash it. For the mean time, I'm back to GB for theming.
Dr01nE said:
I have completely deodexed it the problem is flashing. I also get stuck in bootanimation and it keeps vibrating.
Let me know when find a way to flash it. For the mean time, I'm back to GB for theming.
Click to expand...
Click to collapse
You should copy most of /system/app folder to /preload. Because system partition is small to handle all files.
kyrillos13 said:
You should copy most of /system/app folder to /preload. Because system partition is small to handle all files.
Click to expand...
Click to collapse
I'll try this one later, I need to finish my theme.
Will it have all Kyrillos V5 features?
Sent from my GT-I8160 using xda app-developers app
Here is a comparision between GB and JB (partition table).
There is no difference in size, I have no idea why was repartition required for XXMB2.
I think preload wasn't mounted in GB but I'm sure it's the "Hidden" partition.
malamharian said:
Will it have all Kyrillos V5 features?
Sent from my GT-I8160 using xda app-developers app
Click to expand...
Click to collapse
Yeap.
Szaby59 said:
Here is a comparison between GB and JB (partition table).
There is no difference in size, I have no idea why was repartition required for XXMB2.
I think preload wasn't mounted in GB but I'm sure it's the "Hidden" partition.
Click to expand...
Click to collapse
Hm interesting.
I'm testing that too.
The deodexed ROM boots but having too problems:
- The baseband is unknow and i can't recover it flashing modem or EFS partitions.
- I have a android core stop and can' t pass the first screen.
My deodexed ROM has 430 Mb but maybe is not complet and because that i have the android core problem.
http://forum.xda-developers.com/showthread.php?t=2030594
Messi10 said:
http://forum.xda-developers.com/showthread.php?t=2030594
Click to expand...
Click to collapse
So we need to create an APK which contains
Code:
Link: /preload/symlink/system/app/nameofapp.apk
Manually doing this will definitely take a lot of time.
But is there an easier way or hassle-free way of doing this?
Dr01nE said:
So we need to create an APK which contains
Code:
Link: /preload/symlink/system/app/nameofapp.apk
Manually doing this will definitely take a lot of time.
But is there an easier way or hassle-free way of doing this?
Click to expand...
Click to collapse
You have those symlibs apps in your System/app from system.img or backup. if you open the fake apk with some editor you can see it.
Because that you can't deodex it with the kitchen , you need the real apk from preload.
cbolumar said:
You have those symlibs apps in your System/app from system.img or backup. if you open the fake apk with some editor you can see it.
Because that you can't deodex it with the kitchen , you need the real apk from preload.
Click to expand...
Click to collapse
You cannot deodex the 30 APKs that are symlinked on preload using the system.img from leak fw. but copying them from /system/app/ to /sdcard/ gets you the real APK. What i want to know is how do I include preload links in flashing with script or is it better to do it manually. Because pushing a symlinked file directly causes and infinite bootloop and vibration. (-___-)
Dr01nE said:
You cannot deodex the 30 APKs that are symlinked on preload using the system.img from leak fw. but copying them from /system/app/ to /sdcard/ gets you the real APK. What i want to know is how do I include preload links in flashing with script or is it better to do it manually. Because pushing a symlinked file directly causes and infinite bootloop and vibration. (-___-)
Click to expand...
Click to collapse
Did you try the frapeti method?
We can also edit the pit file and resize system partition or remove some system apps,ringtones,boot animation... Till apps fit in
Sent from my GT-I8160 using xda app-developers app
Messi10 said:
We can also edit the pit file and resize system partition or remove some system apps,ringtones,boot animation... Till apps fit in
Sent from my GT-I8160 using xda app-developers app
Click to expand...
Click to collapse
yes , i'm doing that but i have some problem with some specific apk because i have a rom booting and another smaller not boot.
Related
Hey all.
Been searching XDA and Google for anything on the original framework-res.apk file for the EVO3D.
I dont know what happened but after I flashed this zip from recovery, I rebooted and only see the top status/battery/timebar. NOTHING ELSE. Power button activates screen only...no lockscreen, just black screen and top bar.
Can anyone lend a hand and help me figure out if this can be reversed or uninstalled? Phone works....just cant see the screen to take calls.
Much thanx in advance.
Just download the stock ROM on your computer and pull the original apk from it. Or download the ROM you fiddled with, and pull its apk from there. You can also just try reinstalling the ROM. Or reflash it over. Just clear cache and Dalvik, then flash.
Oh and post this is Q&A next time, or the hall monitors will come and give you a ticket. Oh, and I forgot to mention a tongue lashing.
I also forgot to mention to be aware of the troll patrols. They'll troll you alive!
Sent from my PG86100 using XDA App
DDiaz007 said:
Just download the stock ROM on your computer and pull the original apk from it. Or download the ROM you fiddled with, and pull its apk from there. You can also just try reinstalling the ROM. Or reflash it over. Just clear cache and Dalvik, then flash.
Oh and post this is Q&A next time, or the hall monitors will come and give you a ticket. Oh, and I forgot to mention a tongue lashing.
I also forgot to mention to be aware of the troll patrols. They'll troll you alive!
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
Thanx. Im downloading the stock rooted rom now.
The only reason I posted here was that the zip was a battery modification that for the life of me, I cant seem to remember where I got it from. Considering that it was a mod, I figured it would make sense in Themes and Apps...also figuring in that if someone who had used it as well would have knowledge of uninstall/removal.
Download's done. Will let u know if it worked. Thanx again DDiaz007!
zagman said:
Thanx. Im downloading the stock rooted rom now.
The only reason I posted here was that the zip was a battery modification that for the life of me, I cant seem to remember where I got it from. Considering that it was a mod, I figured it would make sense in Themes and Apps...also figuring in that if someone who had used it as well would have knowledge of uninstall/removal.
Download's done. Will let u know if it worked. Thanx again DDiaz007!
Click to expand...
Click to collapse
If your going to do a clean install. Your going to want to wipe...
Dalvik Partition
Cache partition
Data partition
System partition
Sent from my PG86100 using XDA App
DDiaz007 said:
If your going to do a clean install. Your going to want to wipe...
Dalvik Partition
Cache partition
Data partition
System partition
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
I understand that DD. I don't plan on doing a clean install. After all, I do have a backup from about a week ago that I could restore in Clockwork as a last resort. But seeing as I have done some installs and the backup is a week old, I wanted to see if this zip can be uninstalled. I found out its from Team Xron and I downloaded it on 7/20, 5 days after I got my 3D.
My confusion gets worse now that I see that when I flashed the zip, (its contents included below) it had a META-INF file besides the .apk file. And comparing the 2 META-INF files from here and the stock Rom...they differ in size, and contents. The stock ROM META-INF does not include the RSA, SF, & MF file as does the Mod zip. Also the binary and script files differ in size.
How would u suggest going about changing it back? Should I put the .apk on my sd and push it using ADB? OR create a zip with the Stock .apk and META-INF and flash it in Clockwork Recovery as I did initially?
META-INF / CERT.RSA RSA File 1.7 KB
META-INF / CERT.SF SF File 382 bytes
META-INF / MANIFEST.MF MF File 329 bytes
META-INF / com / google / android / update-binary File 249.9 KB
META-INF / com / google / android / updater-script File 196 bytes
framework / framework-res.apk APK File 3.0 MB
creating a zip with the Stock .apk and META-INF and flash it in Clockwork Recovery was unsuccessful.
"Installing Evo 3D base rom 1.0
unpacking system..
symlinks & pemissions...
"installing kernal...
assert failed: package_extract_file("boot.img. "/tmp/boot.img")
E: error in /sdcard/download/xxx.zip
(Status 7)
Installation aborted."
Although I backed up in CWM....think im just gonna restore back to last week. If i get a wild hair and some good tech support from Xron, I might flash back and troubleshoot again. Oh well....
zagman said:
creating a zip with the Stock .apk and META-INF and flash it in Clockwork Recovery was unsuccessful.
"Installing Evo 3D base rom 1.0
unpacking system..
symlinks & pemissions...
"installing kernal...
assert failed: package_extract_file("boot.img. "/tmp/boot.img")
E: error in /sdcard/download/xxx.zip
(Status 7)
Installation aborted."
Although I backed up in CWM....think im just gonna restore back to last week. If i get a wild hair and some good tech support from Xron, I might flash back and troubleshoot again. Oh well....
Click to expand...
Click to collapse
Stop......Explain what you're trying to do and I will help you.
You want a stock framework-res file?
freeza said:
Stop......Explain what you're trying to do and I will help you.
You want a stock framework-res file?
Click to expand...
Click to collapse
I flashed a battery mod from Xron and the screen was black all for notification bar on top. Trying to "undo" that. Ive extracted the framework-res.apk and the Meta-Inf folder from the stock rom and tried flashing. Not recognizable in CWM Rec. I used the original signed .zip and replaced the contents and the results are in my last post. What else can be done?
zagman said:
I flashed a battery mod from Xron and the screen was black all for notification bar on top. Trying to "undo" that. Ive extracted the framework-res.apk and the Meta-Inf folder from the stock rom and tried flashing. Not recognizable in CWM Rec. I used the original signed .zip and replaced the contents and the results are in my last post. What else can be done?
Click to expand...
Click to collapse
That updater script is trying to install more than what you have in the zip. Your best bet would be to push through adb
Enter-
Adb push (your framework-res.apk) /system/app/
No parenthancies
Sent from my PG86100 using XDA Premium App
I'v installed a 2nd rom with siyah 3.4.1, I see a hidden folder @ internal memory called '.secondrom' with size of 2.2 GB and only two img files: data&cache.
There is any way to browse the 'root' dir of the 2nd rom ?
I want to get into its system/etc folder, but these folders are only at the 'original' root (of the primary rom).
Another question -
Should I install every app (same apps) to each rom?
There is a simple way to install app to both roms at once or only separate to each rom?
About deleting 2nd rom:
After I'm doing a wipe date&cache to 2nd rom, what should I delete manualy from internal memory? (which folders?)
If you want to explore 2nd ROM files, you need to enter to "hidden" partition.
About deleting: just remove .secondrom folder.
You can't install one app at the same moment on both ROMs, cause the ROMs are independent of each other.
przemcio510 said:
If you want to explore 2nd ROM files, you need to enter to "hidden" partition.
About deleting: just remove .secondrom folder.
You can't install one app at the same moment on both ROMs, cause the ROMs are independent of each other.
Click to expand...
Click to collapse
Thanks for the answers!
What is the path of the hidden partition? there is any way to see it?
I'm using 'es file explorer' with all the root permissions enable, include enabled showing all the hidden files/folders... but can't see this partition. (if its possible of course)
PsyOr said:
What is the path of the hidden partition? there is any way to see it?
I'm using 'es file explorer' with all the root permissions enable, include enabled showing all the hidden files/folders... but can't see this partition. (if its possible of course)
Click to expand...
Click to collapse
Below the previous question -
If I'll update Siyah kernel or install other dual-boot kernel (for example dorimnax) will I have any problem with loading the 2nd rom?
anyone have any idea?
PsyOr said:
Below the previous question -
If I'll update Siyah kernel or install other dual-boot kernel (for example dorimnax) will I have any problem with loading the 2nd rom?
Click to expand...
Click to collapse
I don't think so because I believe that those kernels are based off Siyah in the first place.
Sent from my GT-I9100 using Tapatalk 2
PsyOr said:
Below the previous question -
If I'll update Siyah kernel or install other dual-boot kernel (for example dorimnax) will I have any problem with loading the 2nd rom?
Click to expand...
Click to collapse
No everything will be fine, I have even changed kernels to a non dual boot just to try them out and when I install SiyahKernel again it's just like I never changed and no need to set up the 2nd rom again as it's already there
Sent from my GT-I9100 using xda app-developers app
Awesome! Thanks for the answers!
Any answer to the other question:
There is any way to browse the 'root' dir of the 2nd rom ?
I want to get into its system/etc folder, but these folders are only at the 'original' root (of the primary rom). - all I can see is a folder @ internal sd .secondrom with 2.2gb - data & cache .img only...not all the other directories (system, ...)
What is the path of the hidden partition? there is any way to see it?
I'm using 'es file explorer' with all the root permissions enable, include enabled showing all the hidden files/folders... but can't see this partition. (if its possible of course)
[the folders of the 2nd rom as its shows like 1st rom]
/dev/block/mmcblk0p9 if I remember.
przemcio510 said:
/dev/block/mmcblk0p9 if I remember.
Click to expand...
Click to collapse
yeah I see it as a file [size 0] ,,, any way to get into this path [or there is other path to get into 2nd rom root?]
anyone have any idea ?
PsyOr said:
anyone have any idea ?
Click to expand...
Click to collapse
Swap 1 and 2 rom. After edit switch back
Gesendet von meinem GT-I9100 mit Tapatalk 2
accessing system root in 2nd rom
Its really very simple and you'll kick yourselves.
Boot into the second ROM.
Navigate to system in your file manager.
For dual boot the image file from your sd is mounted as the system so when you navigate to system while booted to second ROM it will be the contents of that file you are seeing.
For more info about how it works follow the link from the siyah website.
While we're on the topic can anybody help me to bind/symlink the standard app installation folder in data to the data folder in the second ROM to save duplicating installed apps? I understand that the data and dalvik will need to be desperate but surely the apk files don't need to be duplicated?
All hail gokhanmoral!
beetnubbin said:
Its really very simple and you'll kick yourselves.
Boot into the second ROM.
Navigate to system in your file manager.
For dual boot the image file from your sd is mounted as the system so when you navigate to system while booted to second ROM it will be the contents of that file you are seeing.
For more info about how it works follow the link from the siyah website.
While we're on the topic can anybody help me to bind/symlink the standard app installation folder in data to the data folder in the second ROM to save duplicating installed apps? I understand that the data and dalvik will need to be desperate but surely the apk files don't need to be duplicated?
All hail gokhanmoral!
Click to expand...
Click to collapse
I was thinking the same! Does anyone have a solution for this? it would be great if the apps on both roms would be the same!
Alexsk8.93 said:
I was thinking the same! Does anyone have a solution for this? it would be great if the apps on both roms would be the same!
Click to expand...
Click to collapse
The only way (as far as I know) is doing it via Titanium Backup...that what I did...
Hi all.
I'm trying to copy some files to the system partition after enabling write on read-only partitions and remounting it and everything is success, but when I restart the phone, files get deleted and partition back to original. I tried ES file explore and Total Commander.
Galaxy S2, cMIUI 2.10 JB
Hmm.. seems like a hard question!
Elancore said:
Hi all.
I'm trying to copy some files to the system partition after enabling write on read-only partitions and remounting it and everything is success, but when I restart the phone, files get deleted and partition back to original. I tried ES file explore and Total Commander.
Galaxy S2, cMIUI 2.10 JB
Click to expand...
Click to collapse
Elancore said:
Hmm.. seems like a hard question!
Click to expand...
Click to collapse
Hey,
no not a hard question but a bit confusing
So the copy to system works without probs?
Do u have root-enabled on it?
U can try Solid explorer once, too, to be sure.
CHEERS
I enabled root explorer and I mounted the file system to be writable, yes I have a rooted phone.
I can copy to system root folders anything (media files), the files stay there until I reboot the phone then they disappear, they get deleted maybe? how to disable that?
Thanks
Elancore said:
I enabled root explorer and I mounted the file system to be writable, yes I have a rooted phone.
I can copy to system root folders anything (media files), the files stay there until I reboot the phone then they disappear, they get deleted maybe? how to disable that?
Thanks
Click to expand...
Click to collapse
That listen like u have to save changes?!
Pls try the Solid explorer (for me the best explorer ever)
Copy files and have a look for root-acces request (should be asked for Solid, if it's new)
The copy/replace the file.
CHEERS
Thanks Hannibal for reply, I got no luck on doing it, they still get removed after reboot. Is there a way to flash these files that I want to copy to system as an update.zip?
Elancore said:
Thanks Hannibal for reply, I got no luck on doing it, they still get removed after reboot. Is there a way to flash these files that I want to copy to system as an update.zip?
Click to expand...
Click to collapse
Sure there's a way, but I can't help u with it, sorry.
With new Titanium Backup u can create flashable .zips but for sure only from isntalled apps.
Maybe u have a look at google. I remind for a tool which u just say what u wanna flash an it creates the flashable .zip.
Much success....
CHEERS
Edit: Sorry but couldn't answer u yesterday.
XDA had a prob for a while
What is this?
These are pre-rooted Stock ROM Base's for Developer to use to create modified stock ROMs or for the average Joe to restore their device's to working order if they are stuck in a bootloop. You must have an unlocked bootloader and a working Custom Recovery to use this.
Downloads:
T-Mobile / Retail US - 139.11.6 - Odex ***Tested, will not go past the boot logo.
Instructions:
Put the .zip on your internal storage.
Boot up to your Custom Recovery of choice (example: Clockworkmod Recovery).
Make a complete backup of your device using the Custom Recovery, and store that backup on a computer or alternative storage.
Wipe data using the Custom Recovery.
Mount system using the Custom Recovery.
Format system using the Custom Recovery.
Install the .zip from your internal storage using the Custom Recovery.
Reboot and enjoy! (If it asks to disable recovery install, tell it not to.)
Thanks:
My testers.
The Firmware Team.
mhous33 for the base script/binary for the RAZR M DST ROM.
I'll try to get some more bases up since we now have the means to install them and have them working correctly.
Amazing!
Thanks alot man. Never hurts to have an extra backup on my Google Drive or something should the worst happen.
Flashing in 15 minutes or so, when it's done downloading.
THANK YOU for this!
I'll need the /tmp/recovery.log after the flash if anyone could provide it
Something isn't going right so I'll need it to see what isn't.
Sent from my SGH-M919 using Tapatalk 2
mattlgroff said:
I'll need the /tmp/recovery.log after the flash if anyone could provide it
Something isn't going right so I'll need it to see what isn't.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
It's not booting, so I can't retrieve the file you need. Adb won't detect the device
Gonna have to restore my backup.
[edit] actually ADB is seeing it once I go to recovery... how do I retrieve the file you need?
figured it out, here is the file you requested: https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Extracted using adb while phone was in recovery, after flashing your file. Have to restore now =P
Thanks! Working on it.
Sent from my SGH-M919 using Tapatalk 2
mattlgroff said:
Thanks! Working on it.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Cheers. I can test the revised ROM whenever it's ready =)
Thanks again for your troubles, this will be the stepping stone all the ROM Cooks have been waiting for!
scorpion667 said:
Cheers. I can test the revised ROM whenever it's ready =)
Thanks again for your troubles, this will be the stepping stone all the ROM Cooks have been waiting for!
Click to expand...
Click to collapse
Updated the file, same link as OP.
I'll probably need the /tmp/recovery.log again if it fails.
Code:
adb pull /tmp/recovery.log
Thanks
mattlgroff said:
Updated the file, same link as OP.
I'll probably need the /tmp/recovery.log again if it fails.
Code:
adb pull /tmp/recovery.log
Thanks
Click to expand...
Click to collapse
On it. download eta 20 mins
No luck. Uploaded the new recovery.log https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Let me know if you need any other files/logs off the phone.
would a copy of my nandroid backup help you at all?
[Breakthrough?] After flashing your ROM I did Advanced Restore and selected to ONLY restore System (from my backup) and I managed to boot! No FC or anything - seems to work perfect. I suppose that's where the problem lies? [sidenote: I always follow the instructions in OP for flashing your ROM i.e wipe data, mount system, format system, just thought I'd mention I'm not taking any shortcuts]
I dunno when I flash the ROM it does it a little too fast (under 5s?)... faster than it took my N4 to flash a 96MB Rom lol. I wonder if it's writing to system at all.
It did that for me on the first rom, I don't know if Matt put something in the build prop to differentiate it from the stock rom
Sent on my Moto X
scorpion667 said:
On it. download eta 20 mins
No luck. Uploaded the new recovery.log https://www.dropbox.com/sh/l2s290vdcokf38i/Ej6iIe2dqK
Let me know if you need any other files/logs off the phone.
would a copy of my nandroid backup help you at all?
[Breakthrough?] After flashing your ROM I did Advanced Restore and selected to ONLY restore System (from my backup) and I managed to boot! No FC or anything - seems to work perfect. I suppose that's where the problem lies? [sidenote: I always follow the instructions in OP for flashing your ROM i.e wipe data, mount system, format system, just thought I'd mention I'm not taking any shortcuts]
I dunno when I flash the ROM it does it a little too fast (under 5s?)... faster than it took my N4 to flash a 96MB Rom lol. I wonder if it's writing to system at all.
Click to expand...
Click to collapse
Sounds like its not flashing to system at all
Shame the log isn't saying what is wrong with the ROM zip. Heck its not even showing it attempting to install the zip at all!
No sense.
Sent from my SGH-M919 using Tapatalk 2
Could it be a recovery issue? The updater script looks way different than what I usually see, normally the system is formated and flashed , sym links, permissions and finally the kernel is flashed
Sent from my A2109A using Tapatalk 4
flashallthetime said:
Could it be a recovery issue? The updater script looks way different than what I usually see, normally the system is formated and flashed , sym links, permissions and finally the kernel is flashed
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
If Superuser.zip flashes its the ROM.zip as the issue.
Sent from my SGH-M919 using Tapatalk 2
New updater script?
There's missing files also meta-inf folder?
Sent from my A2109A using Tapatalk 4
flashallthetime said:
New updater script?
There's missing files also meta-inf folder?
Sent from my A2109A using Tapatalk 4
Click to expand...
Click to collapse
Once an OTA update comes out for any Moto X variant we'll have a much better idea of the META-INF folder as a whole. In the meantime everyone feel free to keep playing with it to try to get it to work right. Making small updater-script changes to re-upload the entire ROM.zip is a huge pain. Soon enough we'll have the Dev Edition and more Developers will be joining us to get everything squared away.
Thanks testers!
What is the filesystem it (Moto X)?
Jovistyle said:
What is the filesystem it (Moto X)?
Click to expand...
Click to collapse
Code:
# mount point fstype device [device2] [length=]
/boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot
/cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery
/sdcard datamedia /dev/null
/data f2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
/system ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/modem ext4 /dev/block/platform/msm_sdcc.1/by-name/modem
/customize ext4 /dev/block/platform/msm_sdcc.1/by-name/customize
These,
seems pretty solid my co-worker tried it an seems great now
BLKWIDOW said:
seems pretty solid my co-worker tried it an seems great now
Click to expand...
Click to collapse
Wait, so it works now?
Sent from my XT1058 using Tapatalk 2
Is it deodex? No biggy if its not. Download link? Fantastic, getting flashing widthdrawls, shaking and i can't sleep at night
Sent on my Moto X
Running sense 5 rom version y5... situation : I play a game called imobsters so I need to copy files (.tff files) into system/fonts folder.. I do it everything copies.. I did it rw mounted method on es file explorer.. when I log back into imobsters.. on certain usernames it doesn't display their names.. all I see is blank spaces and empty boxes.. is there a fix for this or way around it on sense roms.. I had no problem copying these files on mean bean rom.. please help... an Thnx in advance
Need to figure out how to DISPLAY emoji not type it.. would be another way of saying this
Did you set proper permissions after copying the files?
Captain_Throwback said:
Did you set proper permissions after copying the files?
Click to expand...
Click to collapse
I mounted as rw when I did an even tried this method: drag files to any folder on your internal memory. boot into recovery, mount data n system, go to file manager n look for your files, click on the files n move it to system/font. wipe cache, reboot
chico260 said:
I mounted as rw when I did an even tried this method: drag files to any folder on your internal memory. boot into recovery, mount data n system, go to file manager n look for your files, click on the files n move it to system/font. wipe cache, reboot
Click to expand...
Click to collapse
Again, doesn't sound like you set permissions.
Captain_Throwback said:
Again, doesn't sound like you set permissions.
Click to expand...
Click to collapse
Would you happen to know the correct permissions
chico260 said:
Would you happen to know the correct permissions
Click to expand...
Click to collapse
No, but I'd use whatever permissions the other files in the folder have .
Captain_Throwback said:
No, but I'd use whatever permissions the other files in the folder have .
Click to expand...
Click to collapse
Tried an still didn't work.. would s-on be a factor?...
chico260 said:
Tried an still didn't work.. would s-on be a factor?...
Click to expand...
Click to collapse
Get Rom toolbox and go to the interface section and click on fonts. Now click Local fonts. Now you want to find the font you want on your SD card and install them in a click. So Simple. Much Easy. Fast. Such amazement. Wow. (Doge meme hahaha)
Sent from my EVO using Tapatalk