Hey guys,
So, I was trying to change my DPI on my OnePlus Two on the new Oxygen OS 3.0, and long story short, I deleted my build.prop.
Can someone share the stock build.prop here? Or is there any other way to regenerate the file without messing up my data and apps?
Thanks.
dirty flash your current rom.
kenboyles72 said:
dirty flash your current rom.
Click to expand...
Click to collapse
Thanks,
but I found a tool to extract the system.new.dat file and just copied the build.prop from that. cheers. :good:
Related
Hi there
I've got a quick question: Right now I'm using Franco's Kernel with the stock 4.4.2 ROM. I also want to test experimentalX (i heard it's a tad snappier). Is it correct that instead of flashing from Franco directly to experimentalX, I install the stock kernel again with TWRP. After that i can flash to experimentalX.
I also use Xposed with a few modules. Is that going to be a problem?
Cheers!
2mnyshp said:
Hi there
I've got a quick question: Right now I'm using Franco's Kernel with the stock 4.4.2 ROM. I also want to test experimentalX (i heard it's a tad snappier). Is it correct that instead of flashing from Franco directly to experimentalX, I install the stock kernel again with TWRP. After that i can flash to experimentalX.
I also use Xposed with a few modules. Is that going to be a problem?
Cheers!
Click to expand...
Click to collapse
Yes You can directly flash experimental X from FRANCO kernel ...
Try yourself and tell us whether it gives a problem or not ?!!! :sly:
Sent from my Nexus 5 using Tapatalk
ok thanks! I'll try it this evening
rahil3108 said:
Yes You can directly flash experimental X from FRANCO kernel ...
Try yourself and tell us whether it gives a problem or not ?!!! :sly:
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
2mnyshp said:
Hi there
I've got a quick question: Right now I'm using Franco's Kernel with the stock 4.4.2 ROM. I also want to test experimentalX (i heard it's a tad snappier). Is it correct that instead of flashing from Franco directly to experimentalX, I install the stock kernel again with TWRP. After that i can flash to experimentalX.
I also use Xposed with a few modules. Is that going to be a problem?
Cheers!
Click to expand...
Click to collapse
You can be sure about flashing the stock boot.img first simply looking at the zip of your already installed kernel.. If the zip includes boot.img file you should flash the stock boot.img first, then your new custom kernel.
if the zip just includes kernel.img then you can flash your custom kernel over it safely.
Xposed isn't related to the kernel flashing, it won't cause any issue
Inviato dal mio Nexus 5 utilizzando Tapatalk
Hi,
Have you read the OP of ElementalX kernel?
NOTE: If you have been using a different custom kernel, please reflash your ROM without wiping data prior to installing this kernel. This will ensure you have all the necessary system files and that customizations from other kernels do not interfere.
Click to expand...
Click to collapse
With Francisco's kernel some system files are modified so better is to dirty flash your rom or at least the stock kernel before...
Just in case for the stock kernel: http://forum.xda-developers.com/showthread.php?t=2518816.
EDIT: too late...
OK, that's the way I would've done it; I put the stock kernal zip on my phone, flash that with TWRP and after that flash ElementalX. I'm not sure about the dirty stock rom flash: Can i just extract the system.img from the official android hammerhead download, put the img on my phone and flash that over my current rom?
Sorry for these trivial questions but the answers to such topics in other threads are sometimes a bit unclear.
Re,
If you have already flashed the stock kernel (so the boot.img) it should be enough... But Francisco's kernel rename some system files like /system/lib/hw/power.msm8974.so or /system/bin/thermal-engine-hh so with a dirty flash of your current rom all the files are replaced (and you won't loose anything, just wipe Dalvik cache and cache partition, just in case then reflash your rom).
Check if the files I mentioned don't have a .bak extension (with a file explorer follow the path above), if not all is fine. If yes, and if you are convenient, delete the .bak extension by yourself.
If you are not convenient with this (I mean delete some extension in system files), dirty flash your rom, reboot (as always just in case, to be sure, etc...), flash your new kernel... And you're good to go!
viking37 said:
Re,
If you have already flashed the stock kernel (so the boot.img) it should be enough... But Francisco's kernel rename some system files like /system/lib/hw/power.msm8974.so or /system/bin/thermal-engine-hh so with a dirty flash of your current rom all the files are replaced (and you won't loose anything, just wipe Dalvik cache and cache partition, just in case then reflash your rom).
Check if the files I mentioned don't have a .bak extension (with a file explorer follow the path above), if not all is fine. If yes, and if you are convenient, delete the .bak extension by yourself.
If you are not convenient with this (I mean delete some extension in system files), dirty flash your rom, reboot (as always just in case, to be sure, etc...), flash your new kernel... And you're good to go!
Click to expand...
Click to collapse
Thanks! And for the dirty flash i can use the System.img which i extracted with TWRP after i cleaned the dalvic cache, right?
2mnyshp said:
Thanks! And for the dirty flash i can use the System.img which i extracted with TWRP after i cleaned the dalvic cache, right?
Click to expand...
Click to collapse
Re
I don't understand what you mean here, you are on full stock rom? You have not flashed a rom from a zip file?
viking37 said:
Re,
If you have already flashed the stock kernel (so the boot.img) it should be enough... But Francisco's kernel rename some system files like /system/lib/hw/power.msm8974.so or /system/bin/thermal-engine-hh so with a dirty flash of your current rom all the files are replaced (and you won't loose anything, just wipe Dalvik cache and cache partition, just in case then reflash your rom).
Check if the files I mentioned don't have a .bak extension (with a file explorer follow the path above), if not all is fine. If yes, and if you are convenient, delete the .bak extension by yourself.
If you are not convenient with this (I mean delete some extension in system files), dirty flash your rom, reboot (as always just in case, to be sure, etc...), flash your new kernel... And you're good to go!
Click to expand...
Click to collapse
viking37 said:
Re
I don't understand what you mean, you are on full stock rom? You have not flashed a rom from a zip file?
Click to expand...
Click to collapse
yes, stock 4.4.2 only with a custom kernel (franco's as of now)
Yes, or at least just take a look at the files I mentioned following the path with a file explorer to see is there is still not the .bak extension. And after flashed ElemantalX kernel, obviously.
As far as I know it should be the only modified system files, I mean renamed since in Francisco's kernel they are not used, that "could" caused issues...
Hi everyone! First of all, sorry for my english.
My question is very simple. I am going to flash Aero Kernel into my Moto G xt1034.
In case something goes wrong or i want to go back to stock kernel, does reflash the rom via fastboot replaces the kernel? I mean, Aero Kernel is ereased and replaced by the stock kernel?
Thank you very much in advance!
Yep, boot.img is your kernel, so you need to flash that at least. But, I think aero is replacing your kernel modules too (eg the WiFi driver), so you need to flash the system image too. Or backup the original modules from the /system/lib/modules directory.
Rhyn said:
Yep, boot.img is your kernel, so you need to flash that at least. But, I think aero is replacing your kernel modules too (eg the WiFi driver), so you need to flash the system image too. Or backup the original modules from the /system/lib/modules directory.
Click to expand...
Click to collapse
Thank you. Does flashing stock Rom replaces those modules ?
neucoas said:
Thank you. Does flashing stock Rom replaces those modules ?
Click to expand...
Click to collapse
If you mean by flashing is fastboot flash etc, then yes. The system.sparesechunk.0-3 files contains your full system partition including the kernel modules. But if you do a cwm backup from your stock system partition before flashing aero and flash that back, that will work too.
Edit: if you just do a backup from /system/lib/modules directory, you should include /system/lib/hw/power.msm8226.so too, hence aero installer also deletes that too.
Usually if you uncertain what a flashable zip do, you can always examine the META-INF/com/google/android/updater-script file. Thats the installer, you can open it with a simple text editor. Usually not too hard to understand, its quite a simple language.
Rhyn said:
If you mean by flashing is fastboot flash etc, then yes. The system.sparesechunk.0-3 files contains your full system partition including the kernel modules. But if you do a cwm backup from your stock system partition before flashing aero and flash that back, that will work too.
Edit: if you just do a backup from /system/lib/modules directory, you should include /system/lib/hw/power.msm8226.so too, hence aero installer also deletes that too.
Usually if you uncertain what a flashable zip do, you can always examine the META-INF/com/google/android/updater-script file. Thats the installer, you can open it with a simple text editor. Usually not too hard to understand, its quite a simple language.
Click to expand...
Click to collapse
Thank you very much! :victory:
Does anyone have, or know where I can find, a copy of the 4.4.3 stock mail & exchange apps?
I'm running modded versions, which I need to restore to stock before I can apply the 4.4.4 update (getting bored of seeing the notification now) - and have misplaced my own backup copies.
Thought a factory restore would have done the job - but didn't!
Thanks
The factory update zip would be a good place to look
pepdavies said:
The factory update zip would be a good place to look
Click to expand...
Click to collapse
Thanks, I'll give that a go - not extracted files from a factory image before, but do have the image so I'll give it a try!
aldredd said:
Thanks, I'll give that a go - not extracted files from a factory image before, but do have the image so I'll give it a try!
Click to expand...
Click to collapse
Would be easier to find a rooted stock flashable zip file. The factory images have .img files which take effort to extract
http://forum.xda-developers.com/goo...t/rom-stock-4-4-3-ktu84m-odex-deodex-t2771010
rootSU said:
Would be easier to find a rooted stock flashable zip file. The factory images have .img files which take effort to extract
http://forum.xda-developers.com/goo...t/rom-stock-4-4-3-ktu84m-odex-deodex-t2771010
Click to expand...
Click to collapse
Cheers, I will call that one plan B then - I've managed to extract the files - just moving the to app folder now!
(this link was very useful for the extract process http://forum.xda-developers.com/showthread.php?t=2294909)
Fab, was able to get it all to work using the extracted files - and learnt something new in the process (how to extract from an image)
thanks for the help.
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..
Hello! I'm working on making a debloated ROM for the samsung galaxy j7 (j700p) model. I have these files: https://gyazo.com/24b7abcb91a62cfaa0e8fd80ca6731be
I can still always create a new system image.
I was wondering, how would one include things like Xposed and SuperSU as system apps? Here's a picture of the system. https://gyazo.com/341a4bd5ebc0d4fd49a0368520a9df4c
With Xposed, I'm not sure how to put in META-INF. Everything else is in. Not sure what to do with that folder.
I'm not sure where to get the app folder. I was going to put it in the app directory.
How do I get the image pre-rooted? I'm not too sure on that either.
Finally, what files do I need to create the final ROM? I have those files, but I'm not sure if I'm supposed to have anything else or something.
Thanks for the help in advance!
minz1 said:
Hello! I'm working on making a debloated ROM for the samsung galaxy j7 (j700p) model. I have these files: https://gyazo.com/24b7abcb91a62cfaa0e8fd80ca6731be
I can still always create a new system image.
I was wondering, how would one include things like Xposed and SuperSU as system apps? Here's a picture of the system. https://gyazo.com/341a4bd5ebc0d4fd49a0368520a9df4c
With Xposed, I'm not sure how to put in META-INF. Everything else is in. Not sure what to do with that folder.
I'm not sure where to get the app folder. I was going to put it in the app directory.
How do I get the image pre-rooted? I'm not too sure on that either.
Finally, what files do I need to create the final ROM? I have those files, but I'm not sure if I'm supposed to have anything else or something.
Thanks for the help in advance!
Click to expand...
Click to collapse
Use superr kitchen it can do all this
messi2050 said:
Use superr kitchen it can do all this
Click to expand...
Click to collapse
What files does super kitchen need to make a rom?
minz1 said:
What files does super kitchen need to make a rom?
Click to expand...
Click to collapse
stock samsung rom
messi2050 said:
Use superr kitchen it can do all this
Click to expand...
Click to collapse
Pm me for ROM advice
messi2050 said:
stock samsung rom
Click to expand...
Click to collapse
Hey I'm getting some error with not having permission with a system .sh file. Any help?