Hi!
I noticed that all change i made in system or vendor build.prop are ignored, or in some other xml files, even if i made a factory reset!
I try to add camera2 API and doesn´t work as example, APN changes to, etc...
The files i add, Change after boot still like stock but if i mount it on twrp it shows the changes i made!
Why?!
After some research i think there is no way to tweak system or vendor.
In some way i think vendor and system are writed in data when is flashed and stay in encriped data partition and when it boot only read data.
I read in some where that images only are use for fast update like dual images something problably the tweak image is not the one in use...
https://source.android.com/devices/tech/ota/ab/
Only customs ROMs will work maube because it have their own boot images and works in a diferent way.
I think it is the end of stock mods... :\
Thanks
Hello i had the same problem in android 10 miui 11.0.3 // you will need to reinstall your stock rom from https://xiaomifirmwareupdater.com/miui/platina/ fastboot rom using mi flash tool
After flash done flash twrp / magisc / install root explorer.
After that you should be able to edit again these files.
Or you can use twrp file manager to edit that .xml files // find a recovery that have the ability to edit those files.
Related
Is there a way to modify cyanogenmod before I install it, so that after the installation, is already configured with my settings/preferences?
NucleusMS said:
Is there a way to modify cyanogenmod before I install it, so that after the installation, is already configured with my settings/preferences?
Click to expand...
Click to collapse
i dont think the same is posible before installing the same(Cynogenmod) for sure
Settings are stored at data partition in db files, so you can modify the zip, include those files into it and modify updater-script. After that, flash the zip, and your settings should be.
But I do not recommend to do this, because you can end with a bootloop.
Anyway, what's the problem to set the phone again? That's only 2 minutes.
Phone is a Star X19i
Now I'm looking at getting a system to allow me to back up the rom and re-flash if needed.
Post 4 has attachments of my boot, recovery and scatter files.
Old issue: (Solved)
Stupid thing I did I renamed the mtklockscreen.odex to mtklockscreen.odex1 just as a test in a half asleep phase to see if I would get the stock lockscreen loading.
Suffice to say the phone no longer boots.
Really don't think I can get into ADB and rename the file to get the phone booting again unless anyone knows a way.
Android was 2.3.6 and I asked the seller if it was possible to get the rom incase anything like happened which they didn't.
So anyone have any ideas?
I have attached the stock recovery and boot images made with cat and a scatter file I made to post 4.
As I have no idea about modifying these for hard root can anyone take a look?
I don't know the specifics of the phone, but if you can go into recovery mode maybe you can get adb working, or use a flashable zip to rename the file by installing it from recovery (just need to edit the zips' updater script)
dxppxd said:
I don't know the specifics of the phone, but if you can go into recovery mode maybe you can get adb working, or use a flashable zip to rename the file by installing it from recovery (just need to edit the zips' updater script)
Click to expand...
Click to collapse
I got into built in Factory mode and can see the file I renamed through ADB and android commander but cannot rename it back due to not having hard root access.
I also have a copy of the boot and recovery partitions 5 and 6 respectively I made in the adb shell yesterday as I was half looking at getting hard root access.
ren mtklockscreen.odex1 mtklockscreen.odex
ren: permission denied
I read you can do a custom recovery with root using SP Tools still so can anyone help me do this?
I know about system root etc and stuff and have flashed roms before on other tablets and have been a PC I.T tech (wouldn't think it due to the stupid mistake) but this recovery and scatter files etc is kinda new to me.
I have a scatter file now I just made if anyone is interested in helping me.
Yes I have a MTK6573 but the scatter file came from the MT6516 Rom Studio which I read works the same for the 6573.
Attached is also my stock boot and recovery partitions I made with cat yesterday if there usable to anyone to help.
Well I got it working and fixed.
I had to go into adb shell and su and mount the file system as writable, as I have used linux before I didn't know about android and what needed to be done and permission locks etc.
The stock boot, recovery and scatter files will remain on this thread if anyone wants to help create or find a recovery which can allow me to create backups and flash custom roms.
I may be able to provide a dump of android 2.3.6 for those that want it once I'm provided with a backup solution as I have read a few people wanting this updated android rom.
This got too close to what I would like liked with bricking this phone.
And I'm not comfortable unless I have a rom backup of this.
Rooting Advice: For anyone with a MTK6573 on Android 2.3.6 trying to root but having issues with super one click make sure you only turn on USB debugging after Android has loaded and just before you plug the usb cable in to run super one click.
I have seen a few thread and posters here about not being able to root the phone and this is the cause that debug needs to be switched on right before you connect and try to root.
Original seller has agreed to send the firmware and flashing stuff on cd for me so I can upload it for you all.
This is a win for MTK6573 Star X19i owners as I'll have the updated 2.3.6 Gingerbread firmware to release for you all root modify etc in a week or so.
Be careful with ROM studio. I believe it is not compatible with MT6573.
You want to read this: http://bm-smartphone-reviews.blogspot.com/2012_04_01_archive.html
cybermaus said:
Be careful with ROM studio. I believe it is not compatible with MT6573.
You want to read this: http://bm-smartphone-reviews.blogspot.com/2012_04_01_archive.html
Click to expand...
Click to collapse
That's what I read and did to get my scatter as I used cat then used the program linked in that thread to generate the scatter.
Hello everyone.
Guys, I am interested in turn the stock rom of my phone in a ready-to-install rom. I mean, roms usually are .zip files with scripts that writes the customized files to the system file, overwriting the old files. I want to know how to take the stock rom of my phone and turn it in a intallable .zip file, like a customized rom.
After a normal installing the phone would be like the phone with the original rom, without changes. Do you know what I mean?
I am interested in this for make changes and costumizations in the stock rom for then reinstall it. Normally, rom porting is made by taking a compatible rom (like CM) and taking the wished to port rom and changing directories like /system, /data, etc... Am I right? Well, if a would take the original rom of my phone and would turn it in a installable .zip, I could make ports, right?
Well, this is my doubt, how can I do this?
Up.
What's wrong? No one cares about?
Noob reporting here !
You can start by installing ADB (from android sdk).
When you have ADB correctly installed , you can "rip" your phone's complete /system partition by using the "adb pull /system system/" command.
This will rip /system to a subfolder called "system" (example c:/adb/adb.exe -> c:/adb/system)
I haven't come further myself, as i`m also in the learning (reading) phase.
you can use dsixda's kitchen for that, just use a firmware file for your phone, and extract that using the kitchen, after that you can use it to make a zip file
How to flash only stock recovery? how to convert "recovery.img.lz4" to "recovery.tar"
Hi all,
I am fairly newb in installing custom ROMs, so apologies if Im misusing any terms. Some time ago I wanted to move a priv-app to system-app, without rooting. I managed to flash TWRP on my Samsung S8 G-950F, and from there moved private app to system app.
Now I would like to go back to the stock recovery img, but I don't know how or if it's even possible. The reason behind this is that my company is deploying Android Work Profile and it is detecting the custom ROM (I assume it is specifically detecting the custom recovery partition)
I tried to find the respective recovery.img for my current stock ROM, but was unable to find it. I can only find for older versions, and from what I read, you can't install older recovery with newer ROM
I can only find the full stock ROM, in .tar.md5 format. opening this with 7zip, I can see the recovery.img.lz4
How do I flash this without altering the OS partition?
Thank you in advance,
Rhaswar
@Rhaswar
Look inside here.
thank you @jwoegerbauer, I have seen this article and it mentions a file called recovery.tar
I don't have that, what I have is the recovery.img.lz4
Is there a conversion that can be done?
Thank you
@Rhaswar
Watch this video: https://www.youtube.com/watch?v=OfrMo1_Rgxc
Hi,
I have recently been pulling build.prop from my phone using a booted twrp and mounting the system folder using twrp.
I am on linux, and the file appears in my home folder.
---fine--
I am no expert when it comes to the android system so can anyone explain this?
If I flash stock to my sony experia z2, I can pull build . prop from /system/build.prop.
However, after flashing lineage over stock, I seem to have two systems, and I pull build.prop from /system/system/build.prop?
Even if prior to flashing the stock rom with TWRP, I erase the stock rom ''system'' folder, after flashing I still have to navigate past two systems in order to get to build.prop?
I am guessing that is normal? - or am I doing something wrong?.
pootler
Thread closed on request of OP @pootler