Database Users

[Q] How to make custom ROMs?

I want to know how to develop my own ROM for LG Optimus.

custom roms are available so why not instead of coding do it based of another one like i did

ok, and how can I make my rom based on onther custom rom?
I tryed to unpack system.img with unyaffs, and pack it again with mkfs but my phone stuck in boot loop, or superuser doesn't work...
can somebody please write shor tutorial how to develop roms...

dont repack
instead apply in a zip in recovery

pashinator said:
custom roms are available so why not instead of coding do it based of another one like i did
Click to expand...
Click to collapse
So, that's what I'm asking: how to make a custom ROM based on another one?

pashinator said:
dont repack
instead apply in a zip in recovery
Click to expand...
Click to collapse
what tool I should use? I tried htc kitchen from xda (it should work on gt540), but I can not even boot my phone...

reflash my rom for example then adb pull whatever you want to edit
then put in zip with an update script and apply in recovery
then create a backup in recovery and that system img and boot img is what you can upload for other people to install
dont give the data img because its personal

pashinator said:
reflash my rom for example then adb pull whatever you want to edit
then put in zip with an update script and apply in recovery
then create a backup in recovery and that system img and boot img is what you can upload for other people to install
dont give the data img because its personal
Click to expand...
Click to collapse
Thanks for the tip!

pashinator said:
reflash my rom for example then adb pull whatever you want to edit
then put in zip with an update script and apply in recovery
then create a backup in recovery and that system img and boot img is what you can upload for other people to install
dont give the data img because its personal
Click to expand...
Click to collapse
tnx. I'm from Croatia, so sry because of my bad eng.
I knew most of this things, but I don't know how to make update script.
I updated kitchen and try another rom and it seems to work now...

[Q] Shot self in foot, edited build.prop now N7 won't boot

I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.

lbloo said:
I was testing tablet UI mode by editing the /system/build.prop file. The N7 went into Tablet UI mode OK but I didn't like it so I reedited the /system/build.prop file to undo my edits, and now the N7 doesn't boot properly. It goes to a black screen and just sit there.
I can boot into recovery and I can get adb to work. I used the pull command to get a copy of the build.prop file and it seems OK but I'm not 100% sure if I made any other edits by mistake. Of course like a fool I didn't make a backup of the original.
Can anyone make some suggestions on how to fix my N7?
Thanks.
Click to expand...
Click to collapse
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.

I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?

lbloo said:
I'm rooted but on stock. Can I just download a copy of the stock rom and flash that with CWM?
Click to expand...
Click to collapse
rooted stock ROM yea. I've also flashed a pure aosp ROM over stock without any reprocussions.

Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.

lbloo said:
Before I go ahead and reflash I just want to make sure I'm getting it right. I've downloaded the stock rom, extracted image-nakasi-jro03d.zip. I should push this file to my internal storage, then use CWM to flash? Or should I just find a pure aosp ROM and flash that?
Sorry for all the questions, I just don't want to make things worse.
Click to expand...
Click to collapse
I don't know what you picked up, but here's a stock/rooted ROM that you can flash in your cwm recovery http://forum.xda-developers.com/showthread.php?t=1776330
Aosp works too, its your choice

if you know how to use adb you can just boot to recovery and push the stock build.prop to your tab

I downloaded a stock copy of the stock build.prop, used the adb push command to push it into /system rebooted and nothing. Still hangs on black screen upon boot.
I then downloaded the stock ROM which simms22 kindly pointed me to, used the adb push command to copy the zip file into /data/media/Firmware, used CWM v6.0.1.0 to "install zip file from sdcard" and I got an error, here is the output:
Installing:/sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
Finding update package...
Opening update package...
Installing update package...
E:Error in /sdcard/Firmware/Nexus7 - JRo03d-Odexed-ROOT_4.1.1_signed.zip
(Status 0)
Installation aborted.
I tried both the Odexed and Deodexed files, both gave same results.
Am I missing a step in the process?

It's working now!
I was afraid I was messing up some of the adb commands so I downloaded the Nexus 7 Toolkit 2.0 (Great tool for someone like me)
- via Toolkit re-transferred the odexed and deodexed ROM files, reflashed, same errors as above
- via Toolkit re-installed CWM Recovery 6.0.1.0, reflashed, same errors as above
- via ADB Shell used CHMOD to modify file rights of the ROM files (stab in the dark), same errors as above
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Not sure why the other ROMS would not flash, but at this point I'm not going to mess around to try to figure it out.
Many thanks to simms22 and PhxkinMassacre for getting me pointed in the right direction.

prly a bad download.
after pushing the file you need to set the correct mode:
Code:
adb shell chmod 644 /system/build.prop

Me too - also hosed my own build.prop
lbloo said:
- downloaded stock image from CWM site (JRO03D_grouper.zip), pushed via tool kit, flashed via CWM....WORKED!!!
Everything is as it was before, no need for a full wipe! I'm going to do a backup right now!
Click to expand...
Click to collapse
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack

Looking back I don't recall resetting the file rights after modifying the file and that was likely the root cause of my problems.
You should try the chmod command a couple of posts back.

JackinNC said:
Ok, I did the exact same thing and followed these instructions but haven't had any luck.
First, thanks lbloo and the folks who have responded for all the info here. I have downloaded JRO03D_grouper.zip and I am grateful for the tip to the toolkit.
When I have pushed JRO03D_grouper.zip to the N7, it appears to have worked, but I can't find it on the sdcard. I am pushing from the default location to /sdcard/. I then select "install zip from sdcard" and "choose zip from sdcard" but the only zip there is supersu (from Day 1).
For reference, this is CWM Recovery v 6.0.0.6.
Thanks in advance for any help anyone can offer.
Jack
Click to expand...
Click to collapse
What location did you push it to? /sdcard/?
Sent from my Nexus 7 using xda app-developers app

mvmacd said:
What location did you push it to? /sdcard/?
Click to expand...
Click to collapse
Yes. And, to further test, I created a little zip file called test.zip and pushed it to the tablet. I can see it just fine. It's just the grouper zip that I can't find.
Thanks
Jack

I just noticed a diff in filesize between the JRO03D_grouper.zip file I am using and one shown in a Youtube video entitled "how to put a rom to flash on a semi-bricked nexus 7 with recovery" by Youtube user metroid031993. (I'm too green to post outside links on XDA)
Mine is 261814702 bytes, the one shown in the video is 32650144 bytes.
Perhaps this is my problem, an invalid zip file. What do you think? And, can someone please tell me the correct size of JRO03D_grouper.zip?
Thanks
Jack
[Note to moderator(s): If I am heading off track in this thread, please don't hesitate to move it or to instruct me to create a new thread. I think the issue may have changed, but I have stayed here since this is where the conversation is for my root issue. Thx!]

JackinNC said:
can someone please tell me the correct size of JRO03D_grouper.zip?
Click to expand...
Click to collapse
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.

Visa Declined said:
Not sure what's up with the youtube video you're using, but 261814702 bytes is the correct size.
Click to expand...
Click to collapse
Thanks for the confirmation.
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
---------- Post added at 11:19 AM ---------- Previous post was at 10:51 AM ----------
JackinNC said:
Ok, back to trying to figure out why it doesn't appear in CWM Recovery after I've pushed it...
Click to expand...
Click to collapse
Well, I got the grouper zip into /sdcard/ and was able to upgrade without losing anything. w00t!
Theory:
I was in the same adb "session" this time since I was using adb from the command line. Meaning, the daemon was still running from the first push I did. So, while I couldn't see the grouper zip after the first push (consistent with your experience, dark_samus), I could see it and upgrade with it after second push (also consistent). And, perhaps my previous attempts didn't work before because I was closing and opening the Nexus 7 Toolkit each time, therefore stopping and restarting the daemon, which meant that each push attempt was the first attempt for that "session."
I don't have any solid technical basis to support or refute that theory, it's just one possible theory that, if true, would result in the experience I had.
My problem is resolved. Thanks to everyone who contributed to this, I truly appreciate your help!
Jack

simms22 said:
reflash your ROM. it'll replace your build.prop with a good copy. don't wipe a thing, just reflash.
Click to expand...
Click to collapse
how to put the stock image if my n7 doesnt boot to android? pls help
i have CWM already

Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Either replace the complete system partition using 'fastboot flash',
or, probably less intrusive, boot into recovery mount system partition writeable and push build.prop manually using 'adb push'.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
my bad i already flash a fresh stock rom again, but thanks anyways...

Set Dpi to 160, now phone wont boot!

So i got curious as to what 160 DPI would look like and now the phone is stuck on the boot image. Could someone be so kind and upload a flashable zip of the build.prop for initial 4.1.2 release?
Unless theres a way to edit build.prop somehow from cwm??

b0uncyfr0 said:
So i got curious as to what 160 DPI would look like and now the phone is stuck on the boot image. Could someone be so kind and upload a flashable zip of the build.prop for initial 4.1.2 release?
Unless theres a way to edit build.prop somehow from cwm??
Click to expand...
Click to collapse
Have you backup of original build.prop?
If you have it you can install trwp and replace file build.prop on system
You also can use aroma FM for CWM, but I didnt try it

St.Noigel said:
Have you backup of original build.prop?
If you have it you can install trwp and replace file build.prop on system
You also can use aroma FM for CWM, but I didnt try it
Click to expand...
Click to collapse
Does it have to be TWRP? Im using philz rocovery. ill look into these tonight and see if any of them work.

b0uncyfr0 said:
Does it have to be TWRP? Im using philz rocovery. ill look into these tonight and see if any of them work.
Click to expand...
Click to collapse
For more info look here - http://forum.xda-developers.com/showthread.php?t=2201860
and install aroma FM

So a bit of an update. Nano refuses to install, it always gives me an installation aborted even though i followed the instructions on the thread. I managed to copy across build.prop from an old backup i had (still the same base rom) and overwrote the corrupted one and sadly this didint work. My guess is LCD Density modder did something else the rom didint like.
Im currently loading my old twrp backup onto the phone to work from there. Ive lost a few things but this is just too much of a hassle. Thanks for the assistance St.Noigel.

Problem Recovery

Suddenly my recovery has stopped working whenever i want to go to recovery is shows me that image with a dead android robot.
Is there any way to flash TWRP again without ADB because i can't get it working,
I tryed twrp manager but it needs root and i lost it.

RootNightmareX said:
Suddenly my recovery has stopped working whenever i want to go to recovery is shows me that image with a dead android robot.
Is there any way to flash TWRP again without ADB because i can't get it working,
I tryed twrp manager but it needs root and i lost it.
Click to expand...
Click to collapse
Try using a toolkit.. for example wugsfresh nexus root toolkit! There's an option to flash the last twrp version..

RootNightmareX said:
Suddenly my recovery has stopped working whenever i want to go to recovery is shows me that image with a dead android robot.
Is there any way to flash TWRP again without ADB because i can't get it working,
I tryed twrp manager but it needs root and i lost it.
Click to expand...
Click to collapse
Without root you would need ADB to flash it...
Your recovery will get over-ridden on each boot unless you rename/delete /system/recovery-from-boot.p to recovery-from-boot.bak or something.
You will need to use fastboot to flash recovery again, then boot TWRP and go into the file manager and rename the file I mentioned above. Sorry, no way to flash recovery without working adb or root.

acejavelin said:
Without root you would need ADB to flash it...
Your recovery will get over-ridden on each boot unless you rename/delete /system/recovery-from-boot.p to recovery-from-boot.bak or something.
You will need to use fastboot to flash recovery again, then boot TWRP and go into the file manager and rename the file I mentioned above. Sorry, no way to flash recovery without working adb or root.
Click to expand...
Click to collapse
I solved with an easy root based on adb program
I rooted the phone and reflashed with twrp from play store. Is there anything I must delete now ?
But whatcould have caused this problem. I was using art clean flashed this morning..... It Never happened for me on any device this problem its first time

RootNightmareX said:
I solved with an easy root based on adb program
I rooted the phone and reflashed with twrp from play store. Is there anything I must delete now ?
But whatcould have caused this problem. I was using art clean flashed this morning..... It Never happened for me on any device this problem its first time
Click to expand...
Click to collapse
You must rename/delete the file I mentioned above if it is a stock ROM, otherwise it reflash the stock recovery on the next boot.
Sent from my Nexus 4 using Tapatalk

acejavelin said:
You must rename/delete the file I mentioned above if it is a stock ROM, otherwise it reflash the stock recovery on the next boot.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I rebooted and still I have twrp. Should I still search the file n delete it?

RootNightmareX said:
I rebooted and still I have twrp. Should I still search the file n delete it?
Click to expand...
Click to collapse
It flashes it on boot, so the next time it might be gone. Most AIO tools take care of it for you.
Your call I guess, is the file there?
Sent from my Nexus 4 using Tapatalk

acejavelin said:
It flashes it on boot, so the next time it might be gone. Most AIO tools take care of it for you.
Your call I guess, is the file there?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I have that recovery bak file. What should i do with it ?

RootNightmareX said:
I have that recovery bak file. What should i do with it ?
Click to expand...
Click to collapse
Personally, I just added a .bak extension to the file, but you could delete it. The nice part about keeping it is if you are basically stock and want to get an OTA, you can just take off the .bak extension, reboot, have stock recovery back, then take the OTA... but I haven't been stock for some time, and returning to stock is fairly simple anyway.

acejavelin said:
Personally, I just added a .bak extension to the file, but you could delete it. The nice part about keeping it is if you are basically stock and want to get an OTA, you can just take off the .bak extension, reboot, have stock recovery back, then take the OTA... but I haven't been stock for some time, and returning to stock is fairly simple anyway.
Click to expand...
Click to collapse
That image can actually lock bootloader back too ?

No, just reflash recovery... It can't relock boot loader, that doesn't have to be locked to take an OTA.
Sent from my Nexus 4 using Tapatalk

RootNightmareX said:
I solved with an easy root based on adb program
I rooted the phone and reflashed with twrp from play store. Is there anything I must delete now ?
But whatcould have caused this problem. I was using art clean flashed this morning..... It Never happened for me on any device this problem its first time
Click to expand...
Click to collapse
what program did you use to root?
Sent from my Nexus 4 using xda app-developers app

[Solved] xdabbed's backup file for d802-20d FW

Hi everybody,
First post ! unfortunately it is because I need help...
I recently upgrade my firmware and I was about to reinstall the xdabbed's camera mod but I unfortunately backup the already modified file system.
Therefore, it would be really helpfull if someone could send me their backup of the system folder.
thanks!

izanaghi said:
Hi everybody,
First post ! unfortunately it is because I need help...
I recently upgrade my firmware and I was about to reinstall the xdabbed's camera mod but I unfortunately backup the already modified file system.
Therefore, it would be really helpfull if someone could send me their backup of the system folder.
thanks!
Click to expand...
Click to collapse
Do you have access to custom recovery ?

bender_007 said:
Do you have access to custom recovery ?
Click to expand...
Click to collapse
the phone is rooted but I haven't installed any custom recovery.
I thought i could be possible to grab someone's backup system archive and use the xdabbed apk to restore default applications.
Actually I should describe a bit more the problem, the camera is there, the player is there but the gallery has disappeared.
There is an LGgallery.apk that comes with xdabbed package but i can't install it. When I try a manual install (just launch the apk), it is just telling me that the app couldn't be installed.
hope we can do something from it, otherwise I'll install a custom recovery and follow any advises you might have,
Thanks,

The thing is:
I can provide you with a restore package(also apk) but I wouldn't advise it. (it's unsafe replacing files on a LIVE android system)
If something happens and you don't have a custom recovery then your only solution is to flash a kdz.
So the best thing would be to install recovery.
If you want the apk I'll send it to you, until now it worked 2 of 2 times for restoring. Again..i would advise the recovery.
+you don't install the lggallery.apk, you copy it to /system/priv-app and chmod 644
first delete the lggallery.odex

bender_007 said:
The thing is:
I can provide you with a restore package(also apk) but I wouldn't advise it. (it's unsafe replacing files on a LIVE android system)
If something happens and you don't have a custom recovery then your only solution is to flash a kdz.
So the best thing would be to install recovery.
If you want the apk I'll send it to you, until now it worked 2 of 2 times for restoring. Again..i would advise the recovery.
+you don't install the lggallery.apk, you copy it to /system/priv-app and chmod 644
first delete the lggallery.odex
Click to expand...
Click to collapse
Ok so i replaced the old LGgallery, remove the odex, changed permission and reboot but no luck with that.
installing a custom recovery sounds quite complex and I am ready to take a risk and try your archive. (hope it'll do the trick)
Otherwise I'll resort to install a recovery,
Many thanks

Actually it's 1 click and it's installed. If the apk fails and you bootloop then you can't install recovery(or boot).
Sent from my LG-D802 using Tapatalk
:
If you want to risk:
modified xdabbeb's installer(install the stock files)
If you want the recovery way(installing recovery is one click job) tell me

bender_007 said:
Actually it's 1 click and it's installed. If the apk fails and you bootloop then you can't install recovery(or boot).
Sent from my LG-D802 using Tapatalk
If you want to risk:
modified xdabbeb's installer(install the stock files)[/URL]
If you want the recovery way(installing recovery is one click job) tell me
Click to expand...
Click to collapse
I am usually stubborn but I listen the advise this time, could you advise me on the best way to do it or direct me to an appropriate thread?

Since you are already rooted.
first: download this
It's the flashable zip for the camera(thx to bruce) (put it on sdcard(internal storage))
then
1. AutoRec d802 You say you've got the d802 right ? Then this one.
Install..Run..Press YES. Allow permissions. Press Flash, wait.. When it says it's done then it's done.
Then press "to recovery" see if it reboots. If it does, you should see TWRP..just press install zip, choose the newly dloaded file.

bender_007 said:
Since you are already rooted.
first: download
It's the flashable zip for the camera(thx to bruce) (put it on sdcard(internal storage))
then
1. You say you've got the d802 right ? Then this one.
Install..Run..Press YES. Allow permissions. Press Flash, wait.. When it says it's done then it's done.
Then press "to recovery" see if it reboots. If it does, you should see TWRP..just press install zip, choose the newly dloaded file.
Click to expand...
Click to collapse
Many thx to Bruce and yourself but I did as described installed TWRP (worked), install the zip (worked), reboot (updated 1 app) but still no sign of the damned Gallery????
What am I missing?

let me see first. 1 minute please.
EDIT: ahh I see.. there is no gallery inside..Wait a min.
Additionally flash this (gallery)

bender_007 said:
let me see first. 1 minute please.
EDIT: ahh I see.. there is no gallery inside..Wait a min.
Additionally flash (gallery)
Click to expand...
Click to collapse
Downloaded it, flashed it, loved it!
Thank you very much for your (and Bruce? ) time, patience and expertise .
First post great support
Again many many thanks :highfive:

No problem