Database Info

ADB And other questions

Hello. I've used ADB to extract from the system folder the hole files of my android. I would like to know if is possible for me to make a ROM from there.
Also i would like to ask if i can use the META-INF and boot.img wich is on other roms into this one, in order to create a zip file ready for use of flasshing. Thanks

jgcaap said:
Hello. I've used ADB to extract from the system folder the hole files of my android. I would like to know if is possible for me to make a ROM from there.
Also i would like to ask if i can use the META-INF and boot.img wich is on other roms into this one, in order to create a zip file ready for use of flasshing. Thanks
Click to expand...
Click to collapse
It may be possible but certainly not recommended.
This is actually no different than taking the /system folder from the rom that you had flashed.
The best way is compiling your rom from source (which of course requires Linux).
The problem with using another rom's boot.img is that the kernel and drivers may not necessarily match those called by those in /system which may cause a lot of errors and instability that is assuming you can get it to boot.

Caution: UOT kitchen

Guyz, Do not ever flash the zip file obtained from UOT kitchen directly to the galaxy r. The Manifest and settings.uot files in the UOT zip file have the wrong configurations ie. not compatible with our phone. The assumed busybox location in the settings and Manifest file is wrong as a result when you flash the zip file it will only delete the original framework-res.apk, systemui.apk and twframework.apk but would not replace them with the modified ones from the UOT zip file. So when you reboot.....---> BOOT LOOP...dead end. I would suggest you to manually push the modified files to their respective locations. I myself ended up into a boot loop yesterday and as luck would have it even my nandroid backup had become corrupt...so had to flash a stock rom through odin..atleast it saved me.

Thanks saurabh.khare for the info.

i've used UOT kitchen many time and i didn't face any problem, when you are flashing the wrong zip file you will have these kind of issues for eg: once i've uploaded the stock ROM framework and flashed it on custom ROM then i faced these kind of issue's..

Yup me too, I've flashed uot-files several times. Never faced such issues.

mj.vikram said:
i've used UOT kitchen many time and i didn't face any problem, when you are flashing the wrong zip file you will have these kind of issues for eg: once i've uploaded the stock ROM framework and flashed it on custom ROM then i faced these kind of issue's..
Click to expand...
Click to collapse
Buddy I'm very much sure that I did nothing wrong. I extracted the files out of a rooted stock ROM(XWKI5) and flashed the cooked zip file over the same rooted Stock ROM through CWM. I have attached the file for you reference...If you could go through and point out where I went wrong I would be very glad

saurabh.khare1000 said:
Guyz, Do not ever flash the zip file obtained from UOT kitchen directly to the galaxy r. The Manifest and settings.uot files in the UOT zip file have the wrong configurations ie. not compatible with our phone. The assumed busybox location in the settings and Manifest file is wrong as a result when you flash the zip file it will only delete the original framework-res.apk, systemui.apk and twframework.apk but would not replace them with the modified ones from the UOT zip file. So when you reboot.....---> BOOT LOOP...dead end. I would suggest you to manually push the modified files to their respective locations. I myself ended up into a boot loop yesterday and as luck would have it even my nandroid backup had become corrupt...so had to flash a stock rom through odin..atleast it saved me.
Click to expand...
Click to collapse
I have flashed files from UOT several times on Galaxy R without any errors(Both Stock Odex and Deodex ones). Not sure why you had issues.

[Q] Lollipop Development

Hi,
I have tried developing a Lollipop rom using CM 12, but after the build it didn'd form a .zip file but i have got system.img, userdata.img, ramdisk.img, recovery folder and others. Then later i have created the zip file by creating boot.img, update-script and signed it.
The problem is why it didn't create a zip file and boot.img by itself (I have given the kernel path in boardconfig.mk and I'm using Java 1.7). When I tried to install my rom, it got installed (I used aroma installer) and I was able to see the files copying into the memory, but when I rebooted, "SAMSUNG" image displayed and it started rebooting again and again. Whats the problem and how to correct these.
Someone help me out, so that I can bring out a ROM with the new Lollipop version.
Thank you

Vignesh Prasad said:
Hi,
I have tried developing a Lollipop rom using CM 12, but after the build it didn'd form a .zip file but i have got system.img, userdata.img, ramdisk.img, recovery folder and others. Then later i have created the zip file by creating boot.img, update-script and signed it.
The problem is why it didn't create a zip file and boot.img by itself (I have given the kernel path in boardconfig.mk and I'm using Java 1.7). When I tried to install my rom, it got installed (I used aroma installer) and I was able to see the files copying into the memory, but when I rebooted, "SAMSUNG" image displayed and it started rebooting again and again. Whats the problem and how to correct these.
Someone help me out, so that I can bring out a ROM with the new Lollipop version.
Thank you
Click to expand...
Click to collapse
bro try using twrp recovery ... normal cwm has some bugs of bottlooping phone into recovery again and again

Aman.k said:
bro try using twrp recovery ... normal cwm has some bugs of bottlooping phone into recovery again and again
Click to expand...
Click to collapse
Dude, in CM 12 CWM is replaced with cyanogenmod recovery and i tried with twrp recovery
Thank you

Unpack system.new.dat

Hi guys, I was able to extract system.new.dat from a rom (purity lollipop) and now I have the old good system with folders, so I can change whatever I want. But I tried to flash the zip and only the boot.img gets installed, the rest seems to be ignored.. What should I change in the zip on order to get it to install correctly?

carlese said:
Hi guys, I was able to extract system.new.dat from a rom (purity lollipop) and now I have the old good system with folders, so I can change whatever I want. But I tried to flash the zip and only the boot.img gets installed, the rest seems to be ignored.. What should I change in the zip on order to get it to install correctly?
Click to expand...
Click to collapse
Look at the updater-script

Lethargy said:
Look at the updater-script
Click to expand...
Click to collapse
Can I use the updater from the same rom but kitkat version? The things I install are the same I think..

[Resolved] Help Creating a Flashable Zip for AOSP MMS (5.0)

Before the eye rolling starts, please note i've Googled and searched for a solution on XDA extensively, with very little help concerning creating a flashable Zip file for Lollipop. Most of the guides and results dealt with KK and lower...
I'm attempting to create a flashable zip for the modified version of the Lollipop AOSP MMS app (located here: https://www.androidfilehost.com/?fid=95832962473398790). I've done this in the past with Jellybean and KitKat, but this time the app, for whatever reason just simply won't flash. No errors come up in recovery, but upon reboot, the app won't be installed.
I've concluded that the reason the app won't flash is the way I have my flashable zip structured.... Or the Updater Script is written wrong.. I've had this problem in the past and rectified it by placing the corresponding META-INF file into the apk itself before placing it in a flashable zip, but this hasn't fixed the issue this time around. The apk in the link above installs itself into the following directory when installed using a file explorer:
Code:
/data/app/com.android.mms-1
If I place the modified apk into the same exact directory in a flashable zip (along with the META-INF folder). An example of what I've done can be downloaded Here, for those interested in dissecting the zip. The only difference is the apk loaded in that zip is the original apk that I know works, not my modified one, as it isn't complete yet.
For reference, I took a look at the CM12 Gallery flashable zip which installs itself in this directory:
Code:
/system/app/Gallery2
Please note that the apk decompiles and recompiles with no issue, so unless APKtool (newest version) screws something up without throwing an error, I doubt that's the issue.
Really need some guidance on this one. I'm excited to see what I can do with this MMS app as I have done in the past with the KK AOSP MMS application. Any help would be greatly appreciated.
Resolution:
I've constructed a perfectly functioning flashable zip (not the ones above) after a few more trial runs. The problem actually seems to be with Apktool not compiling or decompiling the apks correctly. Basically the problem is APKtool.