Hallo, I´ve problems installing UOT Themes via the recovery (clockwork mod 5.0.2). Trying to install the .zip files throws me "error 0". In the kitchen I have read to substitute a certain file from the rom, but having done this the installer aborts without doing anything. I can manually substitute the framework.res file via rootexplorer, but this isn´t elegant and annyoing.
Does anybody have experiences with this problem or a solution to this?
TIA
Marcus4Aspern
Yeah what I do is once I've done the theme downloaded it I get the update-binary file from the rom I'm using which is here in the zip file \META-INF\com\google\android\ and then exchange it with the one in the zip file from the kitchen and then flash it with CWM. I've done that with every theme I've done and its worked every time
I searched for this before posting the thread. I recently installed 'SkyROCKeteer-2.0-Alpha1-112311-signed' on my i727R (http://forum.xda-developers.com/showthread.php?t=1343185). And I noticed he has small zip files on his thread for things like battery mods and icon fixes but they're .zip files. My question is how would i install this to my phone? I tried installing the individual .apk apps but that didn't work.
Reboot into CWM recovery flash it like you did the ROM itself.
So i am some what of a noob but not an idiot. I have googled and feel that i have turned up with nothing. besides the updater-script what else do i have to change in META-INF folder to make my rom flashable. if someone could help point me in the right way that be great. My zip consists of a data folder, a system folder and a boot.img. i already know how to sign the zip. i just need help with the code to flash it.i keep getting error 6 in cwm
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.
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
I wish I could help...but I dont have any experiane in developing ROM's:crying:
all developers are busy in making their Roms...
they should collaborate on the real thing....
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
can i look at your device/kernel tree?
please I want one thing
I want please Android (5. 0) for Samsung galaxy core prime
any updatets regarding this roam
Any Updates?
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
Any progress?
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
please help him ....anybody so we can have rom for our PHONE.....
I'm working on the prime for verizon. If you open BoardConfig.mk there are a few lines to change. I'm not sure what yours will look like but one of them is the TARGET_BOARD_PLATFORM line. You also need to check the locations and block sizes for the partitions. Should work then. I'm still working on mine so don't quote me.