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
Related
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
Dear Admins,
Could we get a forum setup for the Cube U27GT WiFi version? I dug around on the site a bit beforehand but didn't see one, I apologize if I missed it and please direct me there if I did.
I have this tablet and I am doing some initial basic firmware development for it and want a proper place to start putting threads.
Dear Dev Community,
I can't root this bloody thing... At least, not the rom itself. Let me explain...
I can flash the stock rom from Cube and that can be rooted using Kango Root. --Fine...
However, I can't figure out how to replicate this when I make my own rom.
Thus far, here is what I have attempted...
1. Setup dsixda's excellent kitchen on my Ubuntu workstation.
2. Unpack the rom, clean things up, manually put the boot image into the dsixda unpacked working rom folder, run dsixda's root functionality (which add SU binary to xbin and SuperSu apk file to app folder as well as do some things with the boot image file).
3. Rather than using repack with Dsixda (which makes an update.zip image which I can't use because the stock recovery environment on this device can't flash zip update files and I can't for the life of me figure out how to get and or make a working CWM or TWRP recovery image for this unit)...
4. What I do is I run commands in linux to unpack the stock rom to another directory and mount that directory, then clear out a bunch of folders and then manually copy in my files from dsixda's working folder, then repackage up my unpacked stock rom into a new system.img file.
5. Then copy my now modified boot image, system image, and also userdata image (I modify that as well as that is where most all of the chinese bloatware is loaded from) to my SP_Flash_Tool, generate new checksum.ini file and flash normally...
What I get as a result...
1. As long as I am really careful with how I copy files into my new image, the new system flashes okay (if I am not careful, after flash USB storage for some reason has a format error and the system will boot but can't mount USB storage and other odd issues ensue as a result).
2. Assuming everything flashes okay, and no issue with USB storage partition, I have SuperSU installed and when I go to use an app (ES File Explorer or Root Checker) that require's root, I do get the prompt. However none of the root functions actually work and Root Checker tells me I am not rooted.
That is as far as I have got. So as a result, I have a really nice, westernized, cleaned up rom but with no root.
Anyone have any ideas?
This is my first adventure into mod'ing MTK roms so I am sure I am doing all kinds of things wrong . I had a good bit of experience on Rockchip SoC's before this though.
Kind regards and thanks in advance!
Roman
Figured it out!
So I finally did the following rather hackish work-around...
1. Flash stock firmware...
2. Root with Kingo Root
3. Enabled ADB
4. Attach to PC and fire up MTK Droid Tools
5. Take a full backup
6. Modify the system image from the backup and make changes
7. Put that in new firmware flash package
8. Flash new firmware
YAY - Cleaned up rom, modified, with root!
Once I get it all packaged up and uploaded to mtkfirmware.com I will post a link for anyone that wants a cleaned up rom with root!
The only downfall of the above method is that it absolutely requires that the developer have a device on hand because you can't just root the stock image file (at least, I couldn't figure out how... - bleh...
Kind Regards,
Roman
Dear roman,
Thanks for your hard work.
I have a simple question (I think) and if you have the time to reply or -any other android guru- I would be thankful.
My later issue was with a U27GT cube tablet, but I have others, one for each kid, and this is more of general question.
I am reading this and other forums about how to flash tablets from PC. My question is:
Can the flashing process be done from a SD card?
Thanks a lot and regards,
Fernando
SKorea
Flashing Issues | Will not pass Android Logo
I have have the T-Mobile version of the S5 and it is currently running XtreStolite rom on lollipop. I have been messing around with the SystemUI and framework apks. (getting them to work every now and again)
However, I was searching around and tried to push the apk files through adb at first, instead of a complete reflash with the modified apks inside, with no luck. Adb says that the files were successfully sent but are not there and no changes are made. I then stumbled across a method using a flashable zip that is supposed to just replace the files I need.
I n doing so, after reboot the phone just sits at the Android Logo on powerup, them I have to reflash or restore my recovery. My question is this: Is there a method that allows me to setup a flashable zip with the system/priv-app/systemui/systemui.apk so that it will only replace those files and not the whole system folder itself?
There may be some more information that I am leaving out, sorry I have not slept all night and I am about to go to class.
Thanks in advance, if I have posted incorrectly, please advise.
RockyCaballero said:
I have have the T-Mobile version of the S5 and it is currently running XtreStolite rom on lollipop. I have been messing around with the SystemUI and framework apks. (getting them to work every now and again)
However, I was searching around and tried to push the apk files through adb at first, instead of a complete reflash with the modified apks inside, with no luck. Adb says that the files were successfully sent but are not there and no changes are made. I then stumbled across a method using a flashable zip that is supposed to just replace the files I need.
I n doing so, after reboot the phone just sits at the Android Logo on powerup, them I have to reflash or restore my recovery. My question is this: Is there a method that allows me to setup a flashable zip with the system/priv-app/systemui/systemui.apk so that it will only replace those files and not the whole system folder itself?
There may be some more information that I am leaving out, sorry I have not slept all night and I am about to go to class.
Thanks in advance, if I have posted incorrectly, please advise.
Click to expand...
Click to collapse
Here download this https://www.androidfilehost.com/?fid=24052804347782219
Extract and Add whatever directories/folders you want inside the system folder and flash. The script just extracts the system folder as a whole so as long as you make the correct folders, file names, directories etc it'll flash everything to the right spot.
Delete the jar file out of system/framework/ tho since it's a 5.1.1 jar file I did
Much obliged sir, worked perfectly. I'm sure it was the coding. [emoji2]
Dear fellas,
I replaced my build.prop file to an another one and my phone is not booting up anymore.
I have a rooted Xiaomi Mi 5s Plus, with custom recovery.
Can anyone advise what to do without wiping the phone completely and flashing a new ROM?
What I've tried doing:
- I had the original build.prop that the phone had before it got stuck.
- I used the file explorer in custom recovery, copied that file to the system folder in root.
- Rebooted the device, still no luck!
- After rebooting, when I reopen the recovery, and navigate to the system folder again, I don't find the file I copied to the system folder!
Any thoughts on the matter please? Thanks in advance!
Have you tried writing original Rom to the phone. Don't have much experience with that kind best I can suggest
Sent from my SM-G930V using Tapatalk
black_hawk1990 said:
Dear fellas,
I replaced my build.prop file to an another one and my phone is not booting up anymore.
I have a rooted Xiaomi Mi 5s Plus, with custom recovery.
Can anyone advise what to do without wiping the phone completely and flashing a new ROM?
What I've tried doing:
- I had the original build.prop that the phone had before it got stuck.
- I used the file explorer in custom recovery, copied that file to the system folder in root.
- Rebooted the device, still no luck!
- After rebooting, when I reopen the recovery, and navigate to the system folder again, I don't find the file I copied to the system folder!
Any thoughts on the matter please? Thanks in advance!
Click to expand...
Click to collapse
Try mount system read/write first then copy og build prop file in system partition and reboot or use aroma file manager.