Database Info

How-to Theme Development

To create themes, or to edit themes to your liking, you will need a working knowledge of android, adb, how to resign apk's, knowledge of your own O/S.
Before you start be aware that you will probably end up wiping your phone once, if not more. So lets go over the things that you will need.
You will need JF's RC30, RC8, or ADP1 V1.3, depending on what version you intend to create for.
Here is the link to these: http://forum.xda-developers.com/showthread.php?t=466174
You will also want to get the dev bootloader installed on your phone and to HIGHLY suggest everyone trying your theme to install it as well.
Link to dev bootloader: http://forum.xda-developers.com/showthread.php?t=455860
You will also need to resign all the apks located in /system/app and framework-res.apk located in /system/framework. When you push all of these to your phone, you will need to do a wipe.
JesusFreke was kind enough to build a custom signing tool for me that would allow me to right click on an apk and resign it from there. I am posting it here for others to use as well. Note that this is a courtesy of JF, so thank him for it. I cannot stress how much time this has saved me and will save you.
Here is the link: Http://www.FightForthePits.com/testsign(2).zip
Before using this you need to know how to set this up:
I will assume that you have the sdk downloaded and extracted somewhere(if not, do that now), extract both files to the tools directory of your sdk.
Now you will need to add the tools dir of your sdk to the environment variable CLASSPATH.
To do this, right click on My Computer click properties, then choose the tab that says advanced. Click the button that says environmental variables. Go to system variables find the one that says CLASSPATH, double click it, go to the end of variable value. There should be a semicolon ; at the end. type in the path to the testsign.jar located in the tools directory of your SDK, for example the path to my testsign.jar was c:\sdk\android-sdk-windows-1.0_r1\tools\testsign.jar If CLASSPATH is not in your system variables then create it.
If you find the right click menu not working for some reason you can type the following in cmd to sign your files: java testsign whateverfiletosign
Now right click the reg file that you extracted and choose to install it, or merge.
Now, right click an apk, do you see an option that says ResignApk? If not hit the windows key and R at the same time. Type in regedit. go to HKEY_CLASSES_ROOT and expand it. Now find .apk and click it. Double click on (Default) and erase apk_auto_file. Hit ok and close the Reg editor. Now right click an apk and the option ResignApk should be there.
Now through doing this you have done two things, first off you have made the resigning process extremely easy, secondly you will not have to cd to the tools dir of the sdk to use adb or any other tool in the sdk.
You will also need a version of linux installed or running vmware with linux, so that you can create an update file which will install the theme onto the users phone.
You need to make sure that you do this correctly, because if you don't then you will have the potential to create problems for people trying to install your theme. You also need to be specific in addressing what version your theme is for, RC8, RC30, or ADP1. Make sure every file gets signed. Make sure you test the update.zip before you release it.
Every .apk contains the images relating to itself. However, every apk has the ability to use the images in framework-res.apk. The images for every apk is located inside of res and more specifically in folders that are named Drawable, drawable-land, drawable-port, etc. Some things you cannot edit unless you rebuild the entire apk from source, which we will not go into here.(another tutorial, another time) Just know that at this time you SHOULD NOT edit, or even open images with the extension .9.png. If you do you will have problems...Trust me. These are special images called ninepatch images and android resizes these images to fit wherever android, or any other apk, needs it to. if you do open them or edit them they will no longer render correctly when resized. I believe that in order to edit these you must do so and then put them into the source and rebuild the entire apk.
Before getting started you must also realize that you cannot simply resign one or two apk's and stick them in your phone and expect them to work. You must resign every apk inside of /system/app and framework-res.apk and put them on your phone at the same time.
To simplify this process for you though, I have provided an update which will do all of this for you. Note that these updates will not completely wipe your phone, your apps will be retained, however, they will require you to re-enter your Google info, and you will lose you call history.
Links down
Just put the correct update.zip, depending on what version you are running, onto your sd card, boot into recovery and hit alt + s.
Now you can push your own apk's one at a time without re-wiping your phone.
Now, your ready to start changing things up.
You will now need to open the apk, which you can do by adding .zip after .apk, effectively changing it to a zip. Note that if you are using windows you will need to unhide known file extension types.
See here to unhide known file extension types for Xp: http://www.mediacollege.com/microsoft/windows/extension-change.html
See here to unhide file extension types for Vista: http://maximumpcguides.com/windows-vista/how-to-change-a-file-extension/
After changing the apk to a zip open it go to res and copy the folders that have drawable in their name. Go to your desktop, or wherever, create a new folder called Images, or whatever. Open the folder, paste the drawable folders in there. Now you can see what the files look like without opening them. Btw, you may also want to add -frame, or -launcher, to the end of the folders you cope over to keep them separated from others.
Finally, you've edited the images put them all in the apk renamed it back to an apk and resigned it. Now it's time to push it to your phone and see the changes you've made.
Important! : Whenever pushing files to the phone NEVER do it while the phone is running. Do this in recovery mode! If you do this while the phone is running normally you will begin to lose space in /system.
So, boot into recovery plug your phone in and open a cmd prompt. From the cmd prompt type adb shell mount /system then type the following: adb push c:\whereveryourfileis\whateveryourpushing.apk /system/app (system/framework if your pushing framework-res.apk)
Now reboot your phone. If it doesn't boot, try doing a wipe, if that doesn't work reinstall an update and try again. There are alot of things people can do wrong, I can't explain them all here. If you get real stuck, you can ask for help here or contact me on Gtalk [email protected].
So now your theme is done and your ready to make an update.zip for others to install your theme.
This must be done in LINUX! Not WINDOWS! Yes it may work for you if you do it in windows but other people's phones will enter an indefinite loop! Just do it from Linux! If you absolutely cannot make your own update.zip, contact me and we'll see if I can make one up for ya.
I have created a template for you to make your own update.zip. Just download, open in Linux, and add the system apps to app, and framework to framework. Zip it up, SIGN IT, TEST IT YOURSELF, and then distribute it!
Empty update.zip template: Http://www.FightForthePits.com/Androidstuff/update_empty.zip
If anyone has any questions please try asking for help in this thread before emailing me for help Usually I will respond to questions in this forum.
I hope this Tutorial has been helpful. I will add on to it as needed.
Stericson
Links of interest:
Downloading SDK: http://code.google.com/android/intro/installing.html
Using ADB: http://code.google.com/android/reference/adb.html

Working with ninepatch should be straightforward if you use the draw9patch tool included in the SDK. Documentation on usage here:
http://code.google.com/android/reference/draw9patch.html
JF could also save theme users a wipe by resigning /system/app/* and /system/framework/framework-res.apk in his builds with the test keys. Nice tutorial, btw.

However it doesn't. I have used that to no avail. I believe you need to edit the images, put them in the source then rebuild the apks from the source.
As for JF's update, it does not currently wipe your phone after install. So, for him to do this he would have to have his update do a wipe. So technically, they would still have to do this initial wipe.
Stericson

Stericson said:
However it doesn't. I have used that to no avail. I believe you need to edit the images, put them in the source then rebuild the apks from the source.
Click to expand...
Click to collapse
Good point. I thought you could simply drop a similarly dimensioned PNG in but apparently there is some metadata that only the android tool can create.
As for JF's update, it does not currently wipe your phone after install. So, for him to do this he would have to have his update do a wipe. So technically, they would still have to do this initial wipe.
Click to expand...
Click to collapse
True, but a user who is upgrading to a JF update after having put in customized (and test-key signed) system apps will have to wipe again anyway =) Anyone using custom themes will have to wipe every time a JF update (or any update) comes out. However if JF resigns, custom theme users would not have to wipe and stock theme users only have to wipe once. (Nevermind the fact I think everyone should wipe when updating...)

thx stericson this will help big time how long before I can get resigned rc30 last night when you said all the apk. need to be resigned I was like this is going to be a long night but I see jf hooked you up save some big time with his resigning tool

jashsu said:
Good point. I thought you could simply drop a similarly dimensioned PNG in but apparently there is some metadata that only the android tool can create.
True, but a user who is upgrading to a JF update after having put in customized (and test-key signed) system apps will have to wipe again anyway =) Anyone using custom themes will have to wipe every time a JF update (or any update) comes out. However if JF resigns, custom theme users would not have to wipe and stock theme users only have to wipe once. (Nevermind the fact I think everyone should wipe when updating...)
Click to expand...
Click to collapse
Ah, good point
The resigned apps will be released maybye sometime tonight...I had them done but ran into a script problem on adp1 and I have yet to try the rc30 and rc8 ones yet. so I won't release those until I've tested them. If you want to be a Guinea pig however, just let me know
Stericson

Stericson said:
Ah, good point
The resigned apps will be released maybye sometime tonight...I had them done but ran into a script problem on adp1 and I have yet to try the rc30 and rc8 ones yet. so I won't release those until I've tested them. If you want to be a Guinea pig however, just let me know
Stericson
Click to expand...
Click to collapse
The resigned apps have been released, each update file will resign all of apps in /system/app and framework-res.apk. However, these updates make no changes to them whatsoever...Meaning your phone will look just like a brand new phone without any modifications.

rc30 works thx Stericson made it easy for use

Issues with using the update.zip above
Hi all,
I just wanted to point out that after I applied the update.zip above and rebooted applications kept force closing randomly and constantly even through the initial setup (where you have to click the green android to start).
Prior to this, I had JF's RC30 1.3, and the engineering bootloader V2 no sigcheck.
First I did just a alt+s then a alt-w and alt+s. And still nothing.
I'm new to all this so I'm not even sure where to begin troubleshooting. Should I be using the HardSPL?
Thanks in advance and I appologize if this isn't the right place for this post.
Update:
After reflashing with JF's 1.3 RC30 and the problem persisted I noticed that there was a new release 1.31 and this has fixed the problem. I hope this helps anyone else who runs into the same problem.
I still don't know what went wrong though, can anyone shed some light on this? thanks.

Truly there's no telling, sounds like J'f's update fixed it. Can I ask what version you tested?
I would also like to announce that now, thanks to JF, again, you do not have to wipe your phone completely to apply the resigned app updates. However, you will have to re-enter your google info and your call history and other minor things will be gone, but all of your apps will be retained.
Stericson

Stericson said:
Truly there's no telling, sounds like J'f's update fixed it. Can I ask what version you tested?
I would also like to announce that now, thanks to JF, again, you do not have to wipe your phone completely to apply the resigned app updates. However, you will have to re-enter your google info and your call history and other minor things will be gone, but all of your apps will be retained.
Stericson
Click to expand...
Click to collapse
Hey, I tested it with this one:
Rc30 resigned: http://www.fightforthepits.com/Andro...pdate_Rc30.zip
Update went fine, until I booted back up then the applications kept force quitting, without me even doing anything.
Thanks,
Limitlis

yes there is a temp problem with those right this moment I am on the problem as we speak, expect a fix tonight...
Stericson

Can we get the fix cuz it bricking fone I had to flash rc29 nbh
Edit: I forgot please.... feel kinda rude when ur helping me out lol but it bricking some phones and for our less experince members we don't global meltdown lol

These files have been fixed and uploaded.
Stericson

I found the cyclon boot effect images in in framework-res/assets/images,
is there any way to replace the android boot image with those images?

Is there anyway to make the theme with a custom boot screen? Also is there a way to change the second boot screen(The one that says Android and has the little robot)

i tried using the testkeys from JF to resign my apks, but the update still says there is not signature =[

hello, I used the tutorial and everything worked great. I'm trying to change the background to the notification section but I can't find that file. Could you tell me where it is? Thank you.

hey stericson, how do u create a theme for rc33?

Question about modifying signed Rom zip files

Can I modify an existing one by simply dropping in updated bootscreen files, rosie.apk, etc.. and signing the existing rom zip?
Any good guides on how to do one if not, and/or how to use Flipz kitchen tool to create a rom?
Ceger

I am pretty sure if you sign the file and you modify it after that you will have to resign it. At least thats how it goes for other things that are similar that I deal with.

Kcarpenter said:
I am pretty sure if you sign the file and you modify it after that you will have to resign it. At least thats how it goes for other things that are similar that I deal with.
Click to expand...
Click to collapse
I understand that, just wondering if I can add new files and they will move or does some master script need to be updated to know to move the files. In other words, is it done by directory or by file?
For example, if I add some apps to /data/app in the zip will they be there on the phone when I install the ROM zip, etc.. More specifically, I have added an alternate boot sequence. The rom does not have a boot1.gif. If I add the new sequence with XML, will the boot1.gif be installed as well or do I need to update something that directs the install of the ROM to move that file or is it automatic as the folder is moved over?
Ceger

Ceger said:
I understand that, just wondering if I can add new files and they will move or does some master script need to be updated to know to move the files. In other words, is it done by directory or by file?
For example, if I add some apps to /data/app in the zip will they be there on the phone when I install the ROM zip, etc.. More specifically, I have added an alternate boot sequence. The rom does not have a boot1.gif. If I add the new sequence with XML, will the boot1.gif be installed as well or do I need to update something that directs the install of the ROM to move that file or is it automatic as the folder is moved over?
Ceger
Click to expand...
Click to collapse
I have found that the easiest thing to do is just put the files that you want to use to replace the old ones into a signed zip and then flash just those files I have tried altering a rom file with no success

wtphoto said:
I have found that the easiest thing to do is just put the files that you want to use to replace the old ones into a signed zip and then flash just those files I have tried altering a rom file with no success
Click to expand...
Click to collapse
Oh well, was trying to have a one step zip. I guess I can make at least have a 2 step process which is better than 4-5.
Thanks,
Ceger

Yes you can modify just about anything in the rom and flash your zip as long as it is signed and the update script is correct. I always make all my changes to a rom before flashing it so i do not have to flash several different things etc.
The update script is located in RomName\META-INF\com\google\android\
Lets look at a very simple update script to show you what i mean.
In this update script it is to write something to /system
example:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progress 0.1 10
We see here that whatever is in the system folder within the signed zip will be written to the phone
in this case i am writing /system/app/mobiledefense.apk
That will be the only file written to the phone and will be written to /system/app
The update script is not specific to every file so you can have 1 thing in the system folder or 100 and it will write everything in there.
One thing that many people mess up on is not using a update-script file when they sign a .zip file. The recovery has to know what to flash or it will not flash anything.
So the answer is yes you can change many things and then flash the signed update.zip file.
Not everything can be done this way but most things will work.
But for example changing the boot sceen can be done even if the file names are different as long as the folder structure stays the same and the .XML file is the correct one for the boot screen. I opened the .zip of a rom deleted everything out of the boot screen folder and dropped in all the files from the nexus one hero hybrid boot screen re signed the zip and everything flashed perfect. I changed many other things as well in the .zip like rosie.apk, sound files, lockscreen files, busybox files, added apps to /system/app and just resigned the zip and everything flashed the way i wanted it to and works perfect.
The way to correctly zip a file is to extract the zip modify what you want then select everything inside the zip right after you open the folder and the highlight everything select add to archive and then zip it up now sign that .zip
so say you extract the ROM and it is named Rom123 now you will have a folder named Rom123 open that folder and select everything file or folder in there and then hit add to archive that will make another zip right there called Rom123.zip pull that zip out to the desktop and sign that zip file and thats it.
I Know that is confusing as it is late as hell and i am tired but wanted to answer this real quick.

zippy-man said:
Yes you can modify just about anything in the rom and flash your zip as long as it is signed and the update script is correct. I always make all my changes to a rom before flashing it so i do not have to flash several different things etc.
The update script is located in RomName\META-INF\com\google\android\
Lets look at a very simple update script to show you what i mean.
In this update script it is to write something to /system
example:
show_progress 0.1 0
copy_dir PACKAGE:system SYSTEM:
show_progress 0.1 10
We see here that whatever is in the system folder within the signed zip will be written to the phone
in this case i am writing /system/app/mobiledefense.apk
That will be the only file written to the phone and will be written to /system/app
The update script is not specific to every file so you can have 1 thing in the system folder or 100 and it will write everything in there.
One thing that many people mess up on is not using a update-script file when they sign a .zip file. The recovery has to know what to flash or it will not flash anything.
So the answer is yes you can change many things and then flash the signed update.zip file.
Not everything can be done this way but most things will work.
But for example changing the boot sceen can be done even if the file names are different as long as the folder structure stays the same and the .XML file is the correct one for the boot screen. I opened the .zip of a rom deleted everything out of the boot screen folder and dropped in all the files from the nexus one hero hybrid boot screen re signed the zip and everything flashed perfect. I changed many other things as well in the .zip like rosie.apk, sound files, lockscreen files, busybox files, added apps to /system/app and just resigned the zip and everything flashed the way i wanted it to and works perfect.
The way to correctly zip a file is to extract the zip modify what you want then select everything inside the zip right after you open the folder and the highlight everything select add to archive and then zip it up now sign that .zip
so say you extract the ROM and it is named Rom123 now you will have a folder named Rom123 open that folder and select everything file or folder in there and then hit add to archive that will make another zip right there called Rom123.zip pull that zip out to the desktop and sign that zip file and thats it.
I Know that is confusing as it is late as hell and i am tired but wanted to answer this real quick.
Click to expand...
Click to collapse
Perfect, just what I was looking for.
Thank you, just made my day!
Ceger

[ROM] [8/12] 1.45.401.2 OTA Stock Rooted | odex & deodex | Settings fixed

No one seemed to wanna help me so I had to figure this out myself
Started with the Europe RUU and patched the files from the OTA zip posted earlier today, rooted, the whole 9 yards.
What you get:
1.45.401.2 Android 2.3.4
disabled boot sound (I had to, sorry!)
rooted & busybox installed
odexed
unsecure boot.img
love
Deodexed version comes with all of the above plus:
busybox runparts support (init.d)
/data/app enabled
nano & bash shell
deodexed
extra love
Older kernels do not seem to work (2.3.3 ones), so you will have to stick with this stock kernel for now. I have a TMO US Sensation and everything seems to be working fine on my end (I AM running the new radio, btw).
Flash with CWM.
Note for odexed ROM!! - I mucked up the Settings.apk and included a wrong one. The correct files are in there but need to be renamed before you flash, or flash the file I linked below IMMEDIATELY after you flash the ROM (before rebooting). Deodexed version is unaffected. Sorry for the trouble!
Download Odexed -d40386a3258546ee1bd760588007d2bd
Odex Settings Flashable fix - flash immediately after
Downdload Deodexed - 71aeba2d1ae00813458b78bda5c188a0
Deodex Flashable Settings.apk fix - or just push this Settings.apk
Instructions for those not so sure which to download:
Download deodex version
Download Deodex Settings.apk flashable right below it
Place both on SD
reboot to recovery and make a nandroid backup
wipe dalvik cache (and data if you choose, I recommend doing so)
flash deodex
flash settings.apk fix
reboot

Nice one man, will be helpfull to many

yah now all will make a super mega uber fast .... rom
thanks for release, users who like all stock will be happy

Bug
(Do NOT Flash this ROM!) - FIXED
There is no Settings application!!!!!!!!
And in Menu also!!!

Am I missing something? What's so good about this. o_o

Good things ahead.

Great work. How did you apply the OTA patch "HTC_Europe_1.45.401.2-1.35.401.1" to "HTC_Europe_1.35.401.1" ?? Did you update your phone then backup and used that in the kitchen ?
Thanx

There is no settings app. Attempting to start settings from the status bar crashes the status bar process...
Nice :\
Flashed with CWM.

zmfl said:
There is no settings app. Attempting to start settings from the status bar crashes the status bar process...
Nice :\
Flashed with CWM.
Click to expand...
Click to collapse
+1 Same prob.

It's unanimous. Settings are missing.
Sent from my GT-P1000 using XDA Premium App. Waiting for my phone to restore.

Sorry fellas, was experimenting with one and forgot to get rid of it, you can run the following commands to get it back (it should be on your phone, I just renamed it, look at the zip ).
Open up your zip and delete Settings.apk in /system/app and rename Settings.apk.bak to Settings.apk and then rename Settings.odex.bak to Settings.odex then flash away.
Or the hard way:
Code:
roman$ adb remount
remount succeeded
roman$ adb shell
sh-3.2# cd /system/app
sh-3.2# rm Settings.apk
sh-3.2# mv Settings.apk.bak Settings.apk
sh-3.2# mv Settings.odex.bak Settings.odex
roman$ adb reboot recovery
**wipe dalvik cache in recovery**
reuploading a newer version.

teshxx said:
Great work. How did you apply the OTA patch "HTC_Europe_1.45.401.2-1.35.401.1" to "HTC_Europe_1.35.401.1" ?? Did you update your phone then backup and used that in the kitchen ?
Thanx
Click to expand...
Click to collapse
Ripped the patch zip apart, took out any references to firmware, flashed the patch file upgrade.
In the firmware.zip were the boot.img & radio.imgs i flashed among other things I was way too scared to touch

So any "reviews" on 2.3.4, is battery life better? Anything new?
Also a question.
If I install this, would I be able to extract my backup rom of Anroid Revolution and take the apps out aswell as other things like contacts and just slap em on my SD card or in System/apps and have it all work again?

willhub said:
So any "reviews" on 2.3.4, is battery life better? Anything new?
Also a question.
If I install this, would I be able to extract my backup rom of Anroid Revolution and take the apps out aswell as other things like contacts and just slap em on my SD card or in System/apps and have it all work again?
Click to expand...
Click to collapse
Just do a nandroid backup before, flash over, if you get no issues, great! If you start seeing issues, nandroid back, or do a /data wipe in recovery. But theoretically you should be able to.
Deodexed version is also up. flashed and seems to be working great.

birgertime said:
Just do a nandroid backup before, flash over, if you get no issues, great! If you start seeing issues, nandroid back, or do a /data wipe in recovery. But theoretically you should be able to.
Deodexed version is also up. flashed and seems to be working great.
Click to expand...
Click to collapse
I did it! Just flashed it over my old ROM and it worked like an update. Settings working, probably because old ones weren't overwritten. I'm gonna keep using it and report any problems.
Also I used root explorer to fix settings.
Sent from my GT-P1000 using XDA Premium App. Phone is restored.

You sure it'll work ok?
I've got Android Revolution HD with No Sense (So all HTC Sense is removed)
Still safe to just flash over?

It worked for me. I flashed over training wheels.
Sent from my HTC Sensation Z710e using XDA Premium App

willhub said:
You sure it'll work ok?
I've got Android Revolution HD with No Sense (So all HTC Sense is removed)
Still safe to just flash over?
Click to expand...
Click to collapse
Honestly no, but theoretically it SHOULD work. Do a nandroid, and then you have nothing to be scared of .

birgertime said:
Sorry fellas, was experimenting with one and forgot to get rid of it, you can run the following commands to get it back (it should be on your phone, I just renamed it, look at the zip )
Code:
roman$ adb remount
remount succeeded
roman$ adb shell
sh-3.2# cd /system/app
sh-3.2# rm Settings.apk
sh-3.2# mv Settings.apk.bak Settings.apk
sh-3.2# mv Settings.odex.bak Settings.odex
sh-3.2# reboot
reuploading a newer version.
Click to expand...
Click to collapse
Since I have to re-flash I renamed the files within the zip. Let's see if it works
Also, is it safe to just remove a couple of files from the zip? I'm thinking about bloatware naturally...
It might be a silly question, but I've never messed with roms before

i dont like you and all but thanks.

[Q] (Stock Deodexing) -- boot.img failure on update.zip flash? Fix, Replace? Re-Zip?

I have a ZTE990 avail.
Currently I'm rooted with no other roms installed, simply stock, and odexed.
I've tried to manually de-odex using baksmali, Xultimate, etc. All were a pain, all wouldn't work properly.
I found someone and downloaded someone who just simply uploaded a Stock_Deodex.zip rom. Sounded perfect.
So I boot into CWM, try to update and...
assert failed: write_raw_image("/tmp/boot.img","boot" android
Click to expand...
Click to collapse
Since I have stock.. and am just trying to De-Odex.
Can I just unzip the Stock_Deodex.zip, delete the current (apparently faulty) boot.img, and replace it with one of the ones created with the cwm recovery, re-zip and attempt to update as usual?
Or since (if my understanding is correct), the only thing necessary for a system to become deodex is the files in /system/app and /system/restore.
Obviously when I un-zip stock_deodex.zip I have access to them. Could I possibly just replace the two folders (somehow?) and be properly de-odexed?
Any other options that I could use that'd be best?
Much appreciated to anyone who helps, thanks!

Need Services.odex from /system/framework or 4.4 KTU84Q

I'm asking this because when doing an OTA manual update I'm getting this error and error code 7.
IDK how the framework got edited, never did anything on the rooted N5 but installed lucky patcher.
Also I do not have unlocked bootloader and want to retain my files, so I guess flashing is not an option here.
Other modified files are
Services.jar
Serviceitems.jar
I can give 0.2 BTC to who ever helps me. Please help me guys

I'm asking this because when doing an OTA manual update I'm getting this error and error code 7.
IDK how the framework got edited, never did anything on the rooted N5 but installed lucky patcher.

Other edited files are
Services.jar
Serviceitems.jar
Please help me people

please help me people.. It's a humble request.

Download the factory image and flash it but edit the flash-all.bat to remove the -w switch and it'll flash the factory image without wiping the phone. You can then do the OTA

Can you please explain it to me.. In detail.. I'm actually a noob

I can give 0.2 BTC to who ever help mes. Please help me guys

If you're a n00b why were you mucking about with your phone in the first place?
1. Download the KTU84Q factory image and extract it to your fastboot folder.
2. Open the flash-all-bat file in Notepad++ (download it if you need it) and edit the line flashing the ZIP file to remove the -w switch so it doesn't wipe the phone
3. Save the file and run it with the phone connected in fastboot mode and it'll reflash the factory image but not wipe the phone (it'll also remove any changes you've done)
4. Flash the OTA

If this works i need you BitCoin address Please PM me one