Related
Hello XDA, I'm kind of new to ROMs etc. and would appreciate some help. I am trying to install mikegapinski's 2.3.7 ROM (v5) through fastboot and whereas in the past I have seen a boot.img and a system.img, there is a boot.img and a system folder. Is there a way to make the folder into a system.img file that I could flash onto my GT540?
In short, how do you make a system.img file out of a folder with system files in them?
hey there !
(system.img + boot.img) is for fastboot
fastboot flash boot boot.img
fastboot flash system system.img
and the (system folder + boot.img) is for recovery
use any recovery
select zip from sdcard
select the zip
i dont think you can convert the folder to a .img(or the other way around) . and if the rom you are talking about mike's aosp v5 then i wont recommend it as for now there are problems with the ram and so it becomes very laggy. i would recommend mur4iks swiftdroid asis but the choice is yours
I know you can 'extract' images using 'unyaffs' but I never made an image from a folder (except when dumping partitions). I think there is a way though.
If you have Linux on your PC, then you can use the 'yaffs' tool. Search it on Google.
This is how even AOSP compiles system folder into system.img
Sent from my LG GT540 Swift using XDA App
I list found this. Should work!
http://db.tt/ROQSWTW6
Sent from my LG GT540 Swift using Tapatalk
can someone please help me to make system.img from system extraxted folder.
my phone its dead and i can find right rom for it
allway hang on boot logo
Please
link for download
https://www.dropbox.com/s/c99ashouw0fb4hp/system.rar
PS
will if neeed no problem
I got it. If you use Linux, you can create an iso file of the system folder, and then convert it to .img. Just follow it:
In a terminal(CTRL+ALT+T):
Code:
mkisofs -o /path/to/the/system/folder ~/system.iso
dd if=~/system.iso of=~/system.img
rm ~/system.iso
Your system.img will be on your home directory.
and it work's too ? (when you flash it from fastboot)
y2yu said:
can someone please help me to make system.img from system extraxted folder.
my phone its dead and i can find right rom for it
allway hang on boot logo
Please
link for download
https://www.dropbox.com/s/c99ashouw0fb4hp/system.rar
PS
will if neeed no problem
Click to expand...
Click to collapse
pls if you find a solutuon please pm me. And do you think flashing the system.img will solve booting probz?
suggestion
take a look at this url, and examine the zip file contained.
you could boot into cwm and install the zip (not suggesting, its what i did)
if u make a zip file in the same layout you could install your zip and it will update the system partition.
as you have a desire, heres whats required
on phone: place phone into fastboot mode
on computer: unzip to a folder , place the img file in such folder,
open a command prompt, (navigate to folder using the cd command)
and type: fastboot boot bravo-cwm.img
mount sd card, toggle usb storage, place your zip in root of sdcard.
then untoggle, go back, select option to install zip from sdcard.
choose select zip file.
find your zip.
tap on the file, and it will install...
you SHOULD by this point have an updated phone as you desired (lol)
if it does not work as you expected, have a look for a standard system.img for your phone, and put that into a zip
name the zip (i put it in caps, weather needed i dont know) PM99IMG.zip
place it into root of sdcard, and put phone into the first screen of recovery menu, the white screen.
it will analyze your zip and ask you to install, press up to flash and then the required option to reboot when its done to revert your phone back to normal.
hope this helps there buddy,
ill most likley forget to check back, so if u need any help pm me and ill see what i can do,
Is this working
Edu_Renesto said:
I got it. If you use Linux, you can create an iso file of the system folder, and then convert it to .img. Just follow it:
In a terminal(CTRL+ALT+T):
Code:
mkisofs -o /path/to/the/system/folder ~/system.iso
dd if=~/system.iso of=~/system.img
rm ~/system.iso
Your system.img will be on your home directory.
Click to expand...
Click to collapse
HI Bro,
Is the output file system.img after flash into the rom?
phone stuck in usb logo... i have zenfone 4
Yaffey for Windows Might Help
tejasjadhav said:
If you have Linux on your PC, then you can use the 'yaffs' tool. Search it on Google.
This is how even AOSP compiles system folder into system.img
Sent from my LG GT540 Swift using XDA App
Click to expand...
Click to collapse
And if you have Windows on your PC, try Yaffey! http://www.xda-developers.com/yaffey-for-all-your-yaffs2-needs/
Can anyone please help me recover from a boot problem after implementing the boot animation fix below. My phone now gets stuck at the end of the boot animation and will not go any further. It might be caused because I didn't do the last bit and "change number of loops (usually 0 - after the word p in second line) in bootanimation.zip" I have tried to copy in a new boot animation using android commander, but it won't let me mount /system/media as read and write. What tool and procedure could i use to access the phone file system as writeable? I have never used a shell tool. Is there a graphical tool I could use that would mount the system folder so I can write a file to it?
Can someone please advise on a fix?
I did this procedure below, but forgot to change the number of loops
"1. Rename samsungani in /system/bin to anything
2. Copy bootanimation in /system/bin into this folder and rename it into samsungani
3. Copy your bootanimation.zip into /data/local or /system/media
* this method wont work if there's more than 1 folder in bootanimation.zip
* and don't forget to change number of loops (usually 0 - after the word p in second line) in bootanimation.zip, file part.desc into 1 or more than save it. Otherwise you will get into boot loop in bootanimation "
Simply reflash stock ROM with PC Odin
Yeah reflashing the rom can get you out of the bootloop.
But be sure u r on a Safe Kernel.
Speedmod k3-3 or Chainfire kernel v > 5.6
Before you change the rom,
try this
Before using android commander (I assume that your android commander has not obtained root access)
Open the windows command prompt
Locate your adb.exe and run the command from the same folder as follows.
c:\ADB> adb root
restart android commander
and then try to mount in RW mode
Reflashing ROM why need to have safe kernel??
Oh right u need safe kernel only if ur wiping.
Sent from my GT-N7000 using XDA Premium HD app
Guyz plz help me I accidentally delete build.prob file and after that my phone not bootup samsung galaxy grand logo shows and the screen goes blank nothing work. I try flashing stock firmware again but problem remain same. HELP PLZ.....!!!!
Try From Recovery Mode
sumit227 said:
Guyz plz help me I accidentally delete build.prob file and after that my phone not bootup samsung galaxy grand logo shows and the screen goes blank nothing work. I try flashing stock firmware again but problem remain same. HELP PLZ.....!!!!
Click to expand...
Click to collapse
It seems like you have root access & afcource unlock bootloader
Use custom recovery mode ex. CWM to find that file exist or not using cwm file manager link below...
http://forum.xda-developers.com/showthread.php?t=1646108
Let me know if file exist or not.... This app is free and you have full access to file system
Good Luck
I installed aroma file manager and navigate to system folder but the folder is empty.
sumit227 said:
Guyz plz help me I accidentally delete build.prob file and after that my phone not bootup samsung galaxy grand logo shows and the screen goes blank nothing work. I try flashing stock firmware again but problem remain same. HELP PLZ.....!!!!
Click to expand...
Click to collapse
sumit227 said:
I installed aroma file manager and navigate to system folder but the folder is empty.
Click to expand...
Click to collapse
The /system folder is empty because you didn't mount it in recovery.
1. Unzip and copy this build.prop to your phone's internal memory - View attachment build.zip
(This is from I9082XXUBMK3, it will work with other 4.2.2 firmware too but would display the info of K3)
2. Boot into recovery. Go to Mounts and storage>Mount /system
3. Install aroma file manager.zip
4. Go to /sdcard and copy the build.prop file
5. Go back to /system and scroll down to check if you can see all the folders now (also check if build.prop is there)
6. If build.prop is not there then paste the one you just copied
7. Select the build.prop file, go to options and select Change Permission
8. Set the following permissions:
User - Read Write
Group - Read
Others - Read9. Exit aroma and clear cache/dalvik then reboot.
iceyhotguy said:
The /system folder is empty because you didn't mount it in recovery.
1. Unzip and copy this build.prop to your phone's internal memory - View attachment 2543835
(This is from I9082XXUBMK3, it will work with other 4.2.2 firmware too but would display the info of K3)
2. Boot into recovery. Go to Mounts and storage>Mount /system
3. Install aroma file manager.zip
4. Go to /sdcard and copy the build.prop file
5. Go back to /system and scroll down to check if you can see all the folders now (also check if build.prop is there)
6. If build.prop is not there then paste the one you just copied
7. Select the build.prop file, go to options and select Change Permission
8. Set the following permissions:
User - Read Write
Group - Read
Others - Read9. Exit aroma and clear cache/dalvik then reboot.
Click to expand...
Click to collapse
Thanks man by pushing build.prop to system folder atleast my phone starts but after 1-2 min my phone freezes nothing works.
sumit227 said:
Thanks man by pushing build.prop to system folder atleast my phone starts but after 1-2 min my phone freezes nothing works.
Click to expand...
Click to collapse
I can't check what other system modifications you did that is making your phone misbehave.
Backup your data and try to do a clean flash. Wipe your data, cache, dalvik, then go to Mounts and storage and Format /system before flashing the firmware/ROM.
iceyhotguy said:
I can't check what other system modifications you did that is making your phone misbehave.
Backup your data and try to do a clean flash. Wipe your data, cache, dalvik, then go to Mounts and storage and Format /system before flashing the firmware/ROM.
Click to expand...
Click to collapse
After flashing stock firmware again my phone working again.
Thanks bro for helping me... :good:
What IS this post about?
Firmware restore of 4.4.4 using RSD Lite, but for unlocked boots, the recovery flashed is custom & the logo used is the normal M-multi color rather than the warning version. Comes in Philz & Twrp flavors. Upon rebooting, Philz or TWRP will root for you.
User data is retained, not erased.
Note: After this restore you may notice problems because you kept data-just wipe data from recovery & reboot. Keeping data like this is non standard.
The logo used is from here.
First 2 attachments are about 10 MBs. There are 3 modded files to extract: MOD...xml (RSD instructions), recovery & logo to paste into your unzipped/extracted FXZ/XML folder. You may want to rename the stock recovery & logo so they will not be overwritten. Here is the usual fxz Source, which you may have already.
Do not paste the source xml folder contents into mine.
The 2 last attachments are modded full FXZs, 900 MB.
Choose the mod xml from RSD Lite 615. Moto drivers are here. There is no getvar or erase userdata as the X firmware has-which is strange for the stock XML. So use of the modded or source FXZ will leave user data alone.
Settings/Developer Options: Enable USB debugging to use RSD.
If you want a fresh restore just wipe data from stock or custom recovery before you use get into the bootloader/apfastboot screen
Note: step 2 is ap/fastboot (RSD mode) & step 6 (recovery) is where to wipe data.
Faster Mega server full versions can be downloaded for regular use on locked xt-1080s as each modded Full fxz can be easily put back to normal. Recovery.img.orig 10.5 MB & logo.bin.orig 2.6 MB just need renaming, as well as the modded ones renamed: recovery.img.mod Philz: 10.4 MB, TWRP: 8.6 MB & logo.bin.mod 2.6 MB. Then run the original xml (included)(not the one labeled MOD). Again there is no data wipe in this original firmware.
A better backup
Full 444 xml with Philz recovery is up.
It is easily converted back to the normal fxz for locked boot users.
But why? Mega is much faster than the sbf/xml storehouse site.
So if your un Rooted this is useful how?
PILLMUZIK3600 said:
So if your un Rooted this is useful how?
Click to expand...
Click to collapse
Just a faster download of the fxz, is all. Then you must convert the xml folder to normal.
Thanx
Big thanx for this solution. Now I have fully rooted and System RW on Verizon Moto Droid Ultra. I was on OTA updated to 4.4.4, and Root was broken. And now all - OK
dschewchenko said:
Big thanx for this solution. Now I have fully rooted and System RW on Verizon Moto Droid Ultra. I was on OTA updated to 4.4.4, and Root was broken. And now all - OK
Click to expand...
Click to collapse
How did this help keep WP off?
I have not unlocked the bootloader I already have stock android 4.4.4 on my droid maxx, I do not read English well, tell me know if I can flash this rom to get root without problems?
aviwdoowks said:
How did this help keep WP off?
Click to expand...
Click to collapse
I don't know. All apps have full access to system partition, but Safestrup cann't to be installed
luisdev said:
I have not unlocked the bootloader I already have stock android 4.4.4 on my droid maxx, I do not read English well, tell me know if I can flash this rom to get root without problems?
Click to expand...
Click to collapse
No way but a boot unlock. 444 has no exploit for rooting.
This helps unlocked phones only.
dschewchenko said:
I don't know. All apps have full access to system partition, but Safestrup cann't to be installed
Click to expand...
Click to collapse
Why don't you share all the details here.
Solution
aviwdoowks said:
Why don't you share all the details here.
Click to expand...
Click to collapse
Before this thread, I have 4.4.4 with broken root after OTA update (without system RW and SuperSU crash)
My way:
-Install RSD and drivers
- do solutions from head from head
- download file from 1 attach
- replace files
- flash it and see on phone error about size of recovery
- reboot
- wipe data and cache
- reboot
- see SuperSU in Menu
- check wp and su with terminal and adb - all OK
- run Root-Explorer, all permissions apply
- can edit and write files in system folders =)
dschewchenko said:
Before this thread, I have 4.4.4 with broken root after OTA update (without system RW and SuperSU crash)
My way:
-Install RSD and drivers
- do solutions from head from head
- download file from 1 attach
- replace files
- flash it and see on phone error about size of recovery
- reboot
- wipe data and cache
- reboot
- see SuperSU in Menu
- check wp and su with terminal and adb - all OK
- run Root-Explorer, all permissions apply
- can edit and write files in system folders =)
Click to expand...
Click to collapse
Do you have a locked or unlocked bootloader?
aviwdoowks said:
Do you have a locked or unlocked bootloader?
Click to expand...
Click to collapse
I have locked verizon moto droid ultra
dschewchenko said:
I have locked verizon moto droid ultra
Click to expand...
Click to collapse
What build did it come with? Please post all info & steps!! Did you use any exploits?
aviwdoowks said:
What build did it come with? Please post all info & steps!! Did you use any exploits?
Click to expand...
Click to collapse
I have Verizon XT1080 with Locked BL, on 4.4.2 was root and WP off, after WiFi updating to 4.4.4 all was broken, and after that I wrote upper I'm now with root and system read/write permission, but safestrap see that WP ON and crashes after tapping somewhere. After updating SuperSU root will be lost.
For system R/W you may go to Terminal and run:
- su
- mount -o rw,remount /dev/block/platform/msm_sdcc.1/by-name/system /system
and than with mount command check if /system have rw. After reboot you may to remount
P.S. Sorry for my english, I'm from Ukraine =)
Very bad that Moto with cutted language pack =(
dschewchenko said:
Before this thread, I have 4.4.4 with broken root after OTA update (without system RW and SuperSU crash)
My way:
Click to expand...
Click to collapse
-Install RSD and drivers
- do solutions from head from head
???
- download file from 1 attach
Was that the small?
- replace files
This must have been recovery, logo & the mod.XML.
- flash it and see on phone error about size of recovery
Details?
- reboot
- wipe data and cache
- reboot
- see SuperSU in Menu
In app drawer?
- check wp and su with terminal and adb - all OK
- run Root-Explorer, all permissions apply
- can edit and write files in system folders =)
I have no idea how you kept root if RSD succeeded properly.
aviwdoowks said:
-Install RSD and drivers
- do solutions from head
???
in head of this thread
Here is an alternate method to flash 444 "pre-recovery'ed" and thereby pre-rooted. Comes in Philz & Twrp flavors.
3 modded files: ...xml (RSD instructions), recovery & logo to paste into your unzipped FXZ/XML folder. Source.
Flash from RSD Lite 615. Moto drivers. There is no getvar or erase userdata as the X firmware has-which is strange for the stock XML. Added custom recovery & stock (boot) logo.
Settings/Developer Options: Enable USB debugging to use RSD.
If you want a fresh restore just wipe data from stock or custom recovery before you use get into the bootloader/apfastboot screen
Note: step 2 is ap/fastboot (RSD mode) & step 6 (recovery) is where to wipe data.
Paste the 3 files to your xml folder. You may want to rename the stock recovery & logo so they will not be overwritten.
Faster Mega server (but slow uploads, 1 a day. 2 Ultra & 2 X) full versions soon. 10 MB vs 900 MB.
Note for locked users: each modded Full fxz can be easily put back to normal. Recovery.img.orig & logo.bin.orig just need renaming. Then run the original xml (included). Again there is no data wipe in this original firmware.
A better backup
ATTACHED FILES
File Type: txt Philz_6.57.9_NO ERASE_user.data_stkBOOTlogo_1FF-obake_verizon-user-4.4.4-SU4.21-MEGA.xml.zip.txt - [Click for QR Code] (112 Bytes, 9 views)
File Type: txt Twrp-2.8.0.1_NO ERASE_user.data_stkBOOTlogo-1FF-obake_verizon-user-4.4.4-SU4.21-MEGA.xml.txt - [Click for QR Code] (111 Bytes, 13 views)
File Type: txt Full_Philz_6.57.9_NO ERASE_user.data_stkBOOTlogo1FF-obake_verizon-user-4.4.4-SU4.21.xml.zip.txt - [Click for QR Code] (110 Bytes, 3 views)
Click to expand...
Click to collapse
- download file from 1 attach
Was that the small?
this -> "Philz_6.57.9_NO ERASE_user.data_stkBOOTlogo_1FF-obake_verizon-user-4.4.4-SU4.21-MEGA.xml.zip.txt"
- replace files
This must have been recovery, logo & the mod.XML.
files from downloaded archive
- flash it and see on phone error about size of recovery
Details?
-standart flashing with RSD-Lite. When recovery uploading , on phone screen was error about incorrect size of recovery, and then I reboot phone to recovery(stock with VOL-DOWN and POWER), then I do full wipe, thenreboot to clean system, in menu I see SuperSU, then download and run Terminal, tap in Terminal "su", all OK, try to remount system to RW, all OK, then download Root Explorer, root permission applied and go to system for manipulate with files =)
- reboot
- wipe data and cache
- reboot
- see SuperSU in Menu
In app drawer?
- check wp and su with terminal and adb - all OK
- run Root-Explorer, all permissions apply
- can edit and write files in system folders =)
I have no idea how you kept root if RSD succeeded properly.
Click to expand...
Click to collapse
=)
dschewchenko said:
=)
Click to expand...
Click to collapse
So you flashed the mini version without system, motoboot, boot, gpt & etc.
It is still confusing so for everyone's benefit maybe, in time, your sweet time, you could be more clear about the exact steps.
Thank you.
aviwdoowks said:
So you flashed the mini version without system, motoboot, boot, gpt & etc.
It is still confusing so for everyone's benefit maybe, in time, your sweet time, you could be more clear about the exact steps.
Thank you.
Click to expand...
Click to collapse
I don't change xml, from downloaded archive I replace files with source Source (from head of thread) And in RSD check xml file that from archive Philz
dschewchenko said:
I don't change xml, from downloaded archive I replace files with source Source (from head of thread) And in RSD check xml file that from archive Philz
Click to expand...
Click to collapse
Just to be clear, I intended the attachments to overwrite the source. You overwrote the attachment with the source!! (If I read you right)
The Q is did you achieve something good by your mistake?
Sagit Logo Generator
notice:
someone reported(firmware version global 071019) getting random reboot after changed boot logo, and flash [china firmware 0908/0907] solved it. Use it at your own risk.
First download this File View attachment GenLogo.zip
How to use (Windows)
1. Download this project and goto GenLogo folder.
2. Edit these 5 bmp files, do not change filename or format.
3. Run GenLogo.exe and you get logo_new.img.
4. flash through fastboot
HTML:
fastboot flash logo logo_new.img
5. Enjoy!
How to use (Linux&Unix)
1. Download this project and goto GenLogo folder.
2. Edit these 5 bmp files, do not change filename or format.
3. Run python genlogo.py and you get logo_new.img (python3).
4. flash through fastboot
HTML:
fastboot flash logo logo_new.img
5. Enjoy!
How to restore
Just flash logo.img in official fastboot ROM View attachment logo.zip.
Source: https://github.com/moonheart/sagit-logo-gen
Thanks @huhu2207 for advice (binwalker).
Anyone tested it to confirm its working?
ermacwins said:
Anyone tested it to confirm its working?
Click to expand...
Click to collapse
Works Flawlessly.
Google Pixel 2 Boot Logo
---
You can install the same mod from kenzo to your bootanimation.
https://androidfilehost.com/?fid=673368273298932636
Enjoy
moonheartmoon said:
Sagit Logo Generator
notice:
someone reported(firmware version global 071019) getting random reboot after changed boot logo, and flash [china firmware 0908/0907] solved it. Use it at your own risk.
First download this File View attachment 4316668
How to use (Windows)
1. Download this project and goto GenLogo folder.
2. Edit these 5 bmp files, do not change filename or format.
3. Run GenLogo.exe and you get logo_new.img.
4. flash through fastboot
HTML:
fastboot flash logo logo_new.img
5. Enjoy!
How to use (Linux&Unix)
1. Download this project and goto GenLogo folder.
2. Edit these 5 bmp files, do not change filename or format.
3. Run python genlogo.py and you get logo_new.img (python3).
4. flash through fastboot
HTML:
fastboot flash logo logo_new.img
5. Enjoy!
How to restore
Just flash logo.img in official fastboot ROM View attachment 4316673.
Source: https://github.com/moonheart/sagit-logo-gen
Thanks @huhu2207 for advice (binwalker).
Click to expand...
Click to collapse
Hi,
in the instructions you indicate that i have to edit the 5 images that appear in the folder. I just want to create the logo on boot that by default mi.com appears. Have I to edit all the images with the same image I want to put in the boot or just one of them? Thanks in advance and soory for my bad english.
Guillemi said:
Hi,
in the instructions you indicate that i have to edit the 5 images that appear in the folder. I just want to create the logo on boot that by default mi.com appears. Have I to edit all the images with the same image I want to put in the boot or just one of them? Thanks in advance and soory for my bad english.
Click to expand...
Click to collapse
Yes, you can just edit one of them.
moonheartmoon said:
Yes, you can just edit one of them.
Click to expand...
Click to collapse
Thanks. i'll give a try.
Thank you!
It works wonderfully!
Can someone propose in which .bmp editor pictures should be edited. I was try with Photoshop, but without succes. I suppose Logo generator is working, because after I edited just one pic, main boot logo 4.bmp, I've got a change, but if I edit all images I got a black screen instead of boot logo.
Which tool you using and which settings for .bmp images saving?
Thanks.
EDIT: Guys, please ignore this post, not sure what I have screwed last time, this working as expected. .bmp pictures edited in Photoshop.
Up. Is this guide still working for MIUI 10 ? (8.6.21 .eu) ???
pi4a7a said:
Up. Is this guide still working for MIUI 10 ? (8.6.21 .eu) ???
Click to expand...
Click to collapse
Yes
Is it device dependent ? Or it can work on similar specs Mi Mix 2? If not, any changes I can do to make it work?
Thanks!
moonheartmoon said:
Sagit Logo Generator
Click to expand...
Click to collapse
Thank you for the mi6 logo. Could you make a logo for mi note 3?
offset0 = 0x4000
offset1 = 0x4200
offset2 = 0x2A200
offset3 = 0x1C0200
offset4 = 0x1EE000
offset5 = 0x7DCE00
sagit
UP
Is this guide still working for miui 11?
edit: yes it works