Database Users

[TUT] How To Create DUMP out of Stock Rom ( UP NOW )

Hello .
Posting a tutorial on how to create a dump out of your stock rom, in case you delete some apps or modify some settings.
ALRIGHT LETS START:
STEP ONE:
Alright, so you want to make a backup of your phone software, but dont know what to do. Its simple, download the package the Android SDK from google and copy it to C:\ drive. Once you have download it, make sure you have Java installed in your system or else it will not work. After everything is done, open the program and install these two packages:
1. Android SDK Tools, revision 6
2. USB Driver package, revision3 ([COLOR="Red"IMP: Its important that the USB driver installed shows up as Composite Android Debug Device, else it wont work. ][/COLOR]
What Android SDK ?? Read about it here: [url]http://developer.android.com/sdk/index.html[/url]
Why Android SDK ? Because: it has the [COLOR="red"]android debug shell[/COLOR] which you require before communicating with your android phone. So download it ! From here:
STEP TWO:
Download Busybox from here : http://rapidshare.com/files/407238531/busybox What is Busybox ?? Read about it here: http://www.busybox.net/
MD5 Signature: C5B76280434EEF49310AD8F1810B10B2
STEP THREE:
One you have downloaded busybox, copy it to the C:\ drive of your computer and then follow the next step. The next step is to open the Command Prompt ( type cmd in the Run prompt ) if using Vista right click on "Run as Administrator".
Assuming you are the root of C:\
Type: C:\cd android-sdk-windows
-> then
Type: C:\android-sdk-windows\ cd tools
-> if you have android debug shell and USB drivers properly installed
Type: adb devices
Now your device will show up as a binary number .. Success ! if it doesn't show up you need to install the drivers again or something else is wrong.
STEP FOUR:
Now once your device shows up, we will need to download the busybox from the computer to the phone. Since we can write anything in the /data/local portion of the android system we will copy the busybox file to the android device.
Type: adb push busybox /data/local/busybox
Once it has been copied to your device issue this command.
Type: adb shell This coomand is issued to go to your mobile's terminal where you can issue commands internally to the phone.
--> then
Type: cd /sdcard This command is given inorder to go to the sdcard ( i.e the internal storage of your phone )
--> then
Type: chmod 755 /data/local/busybox This command is issued to set user -rwxrwxr-x permissions to the file.
--> then
Finally, issue this command.
Type: /data/local/busybox tar cvf Samsung.tar /system This command is given to copy and tar the system folder where all the stock applications and programs are and to create a dump of that system folder.
STEP FIVE:
Job Done !!
The Samsung.tar file can be copied to the computer now. Have fun.

this is perfect, as i want to create a dump of my original ROM

A dump is simply a backup of your original ROM right?

thats good news if it is indeed a a backup of the stock firmware.
i want to back up my warranty firmware!

OrionTC said:
thats good news if it is indeed a a backup of the stock firmware.
i want to back up my warranty firmware!
Click to expand...
Click to collapse
it is only a backup of your stock apps and driver if so however it doesnt convert the files into a flashable rom version.

is there a way for us to backup the firmware?? (not just stock apps)

tids2k said:
it is only a backup of your stock apps and driver if so however it doesnt convert the files into a flashable rom version.
Click to expand...
Click to collapse
So this is not a tutorial of how you back up your stock rom but how you back up your stock apps and stock drivers?

droidwi said:
So this is not a tutorial of how you back up your stock rom but how you back up your stock apps and stock drivers?
Click to expand...
Click to collapse
Correct. We most likely won't be able to actually perform a complete backup until Nandroid works on the handset.

Too bad, the title was very promising but what you show is just an backup archive of the system.
BTW, there is no guarantee that restoring it will produce a usable phone, because kernel, datas, modem baseband etc won't be restored too !
But this can be useful to restore some file after a mistake done on /system files.

supercurio said:
Too bad, the title was very promising but what you show is just an backup archive of the system.
BTW, there is no guarantee that restoring it will produce a usable phone, because kernel, datas, modem baseband etc won't be restored too !
But this can be useful to restore some file after a mistake done on /system files.
Click to expand...
Click to collapse
im working on creating a stock rom ... may be some happy results and happy faces. who knows . keep sticked !

uploading dump again .. please wait.

So, Can i just select this dump in Odin and it will recover to stock firmware. Quite confused here.
The file size is 275 megs , so is it only for apps? Have you flashed with this dump. Nice work so far. THanks.
Edit: Just realised the dump option in Odin is for dumping my rom , not loading one.
So stuck with this until Samsung update. Huh!

Is this the same procedure as making a backup /efs?
I've been searching the forum for hours and this is the only thing I could find that looked anything like it.

This won't work
No, no and no !!
This procedure will not backup your stock ROM.
A complete rom consists in:
- a primary bootloader.
- a secondary bootloader.
- an initrd image with the kernel.
- a rootfs (the /system partition).
- an efs partition.
- a binary radio firmware.
There is no known method to backup all the flash partitions and transform them into proper files that can be reflashed with Odin or Heimdall.

Plinn said:
No, no and no !!
This procedure will not backup your stock ROM.
A complete rom consists in:
- a primary bootloader.
- a secondary bootloader.
- an initrd image with the kernel.
- a rootfs (the /system partition).
- an efs partition.
- a binary radio firmware.
There is no known method to backup all the flash partitions and transform them into proper files that can be reflashed with Odin or Heimdall.
Click to expand...
Click to collapse
+1.. The thread is misleading.. This doesn't accomplish anything! You really think people in the "Android Development" section don't know about tar?

Did anyone already managed to get the built-in dump function from Odin working?
With Odin v1.3 there was the possibility to decide whether to dump AP RAM or AP NAND (followed by an ID).
With Odin v1.52 you can't choose this anymore. It will only dump AP NAND.
But my first attempts were unfortunately not very promising

[Q] How to make a system folder into a system.img

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/

Nexus 6p stuck on Google screen during boot due to replacing build.prop

I Replaced the build.prop on my rooted Google nexus 6p running Android 7.0 with the build.prop file from the pixel to run Google Assistant.The phone is now stuck on the Google logo during boot,PLEASE HELP.

Did you make a backup copy of the file before replacing it, are you rooted, and have TWRP installed?
If so, reboot to recovery, use TWRP Terminal function to copy the backup of the build.prop to the modified one.

dratsablive said:
Did you make a backup copy of the file before replacing it, are you rooted, and have TWRP installed?
If so, reboot to recovery, use TWRP Terminal function to copy the backup of the build.prop to the modified one.
Click to expand...
Click to collapse
I did not make a back up but I am rooted and have Twrp installed.What can i do from here?

If you can boot to bootloader you should be able to replace the file with a standard one.

Alden1227 said:
I Replaced the build.prop on my rooted Google nexus 6p running Android 7.0 with the build.prop file from the pixel to run Google Assistant.The phone is now stuck on the Google logo during boot,PLEASE HELP.
Click to expand...
Click to collapse
same here please help.....freaking out

1. The build.prop contains the settings for a specific build for a specific phone. You can't just replace it from another build, not to mention another phone. Well, I guess, you already know this.
2. You should know exactly which build you were on. Exactly. Then:
* What I would do, is download the factory image from https://developers.google.com/android/nexus/images#angler
o Extract it, extract the image-angler-...zip, and mount the system.img, find the build.prop and adb push it to the phone.
o Reboot
* But you can also ask somebody who has the exact build as you do, and ask for the build.prop. Then push it to the phone.

Either restore from backup or edit the buildprop (if possible) I guess.
You only needed to edit 2 lines in the buildprop though, why replace the whole thing?

Alden1227 said:
I did not make a back up but I am rooted and have Twrp installed.What can i do from here?
Click to expand...
Click to collapse
First thing's first. Since you didn't just edit your build.prop, but replaced it with another, try setting permissions.
Step 1: Boot to TWRP > Mount > Select "System"
Step 2: Advanced > File Manager
Step 3: Navigate to /system/build.prop
Step 4: Select "chmod" and type "644" (don't include quotation marks)
Reboot and see if it works. If the permissions weren't right and you didn't change them, you'd most likely be in a boot loop. If this doesn't work you can just flash your system.img again. It won't wipe your internal storage, data (installed apps, etc.) If you have custom host files for ad blocking, you may need to apply them again.
If that does not work;
I'm going to assume you were on stock Nougat. Download the factory image (same build you were on before) and unzip the file. You'll end up with a folder with another zip archive in it. Unzip that as well. Inside you'll find a file named "system.img"
Move that system.img file to your ADB/fastboot folder. Shift+Right Click that folder and select "Open command window here"
Hold volume down + power to boot into the bootloader. Connect the phone to the PC and in the command prompt, type "fastboot devices" (no quotes again. ) It should show your devices serial number. If it does, perfect. If not, check your ADB/fastboot installation.
Once you get fastboot to show your serial number all you need to do is type;
Code:
fastboot flash system system.img
That should do it. If you need any more help, just reply back.
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/

RoyJ said:
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
Click to expand...
Click to collapse
It's a sparse image, you have to convert it to normal mage with simg2img. Then you can mount it normally.

istperson said:
It's a sparse image, you have to convert it to normal mage with simg2img. Then you can mount it normally.
Click to expand...
Click to collapse
Awesome, thanks!

Fixed the issue
frreak said:
same here please help.....freaking out
Click to expand...
Click to collapse
I got mine to work by flashing Android 7.0

same thing happened to me.... stuck on google even after flashing stock....

dadoc04 said:
same thing happened to me.... stuck on google even after flashing stock....
Click to expand...
Click to collapse
Flash stock boot, system and vendor img files.
Sent from my Pixel XL using XDA-Developers mobile app

Same thing happened to me at first (though I did not use the build prop from a Pixel). I just dirty flashed my ROM (Octo N) and it then got passed the Google screen and loaded with no problem. I updated my build prop manually in order to get Google Assistant to work, and it's been working great ever since.

RoyJ said:
First thing's first. Since you didn't just edit your build.prop, but replaced it with another, try setting permissions.
Step 1: Boot to TWRP > Mount > Select "System"
Step 2: Advanced > File Manager
Step 3: Navigate to /system/build.prop
Step 4: Select "chmod" and type "644" (don't include quotation marks)
Reboot and see if it works. If the permissions weren't right and you didn't change them, you'd most likely be in a boot loop. If this doesn't work you can just flash your system.img again. It won't wipe your internal storage, data (installed apps, etc.) If you have custom host files for ad blocking, you may need to apply them again.
If that does not work;
I'm going to assume you were on stock Nougat. Download the factory image (same build you were on before) and unzip the file. You'll end up with a folder with another zip archive in it. Unzip that as well. Inside you'll find a file named "system.img"
Move that system.img file to your ADB/fastboot folder. Shift+Right Click that folder and select "Open command window here"
Hold volume down + power to boot into the bootloader. Connect the phone to the PC and in the command prompt, type "fastboot devices" (no quotes again. ) It should show your devices serial number. If it does, perfect. If not, check your ADB/fastboot installation.
Once you get fastboot to show your serial number all you need to do is type;
That should do it. If you need any more help, just reply back.
Edit: @istperson, AFAIK, you cannot pick out files from a .img file like that. When I right click it on my system and choose mount it tells me the image file is corrupted. Tried downloading again and hashes match. Windows 10. I use 7zip as well, and that can't open it either. Is there another program to use or is something whacky on my end? Wouldn't doubt it. Just took a Win10 update yesterday and it's been acting up on me all day. :/
Click to expand...
Click to collapse
Chmod 755 worked too

Battery Capacity

To developers.
My question is simple. After years to discover where are the files to the nominal capacity of a battery, i know that the system stores this data in a file called charge_full_design.
In my s3 neo (I9301I) the original battery capacity is 2100 Mah and that file contents only a number (2100000).
My answer is very simple. What are i to do to change this number with the capacity of my battery (anker 7200 mah) in that file?. The system tell me that i Can't do.
Thanks.
My rom now CM 11 ( )
Sincerely Juan Carlos

I have same battery...
take a try on TWRP mode

needforszpit said:
I have same battery...
take a try on TWRP mode
Click to expand...
Click to collapse
How do I edit files in TWRP?

chmod 755...or use total commander to edit file(root mode)

needforszpit said:
chmod 755...or use total commander to edit file(root mode)
Click to expand...
Click to collapse
In total commander it keeps saying that it can't be saved because of not enough memory. And in TWRP mod I slide to apply chmod 755 but then nothing happens.

755 chmod enable write access...
try to rename the file and after create a file with 7200000 with original name

needforszpit said:
755 chmod enable write access...
try to rename the file and after create a file with 7200000 with original name
Click to expand...
Click to collapse
When I rename the file it stays the same and nothing happens. Also when I try to Change the value in it, it always changes back to the original value when I save. I have System read write but it´s not working.

dead end...

needforszpit said:
dead end...
Click to expand...
Click to collapse
Do you have a suggestion on how to solve this problem?

without I know where is file located on system is littlebit hard to say anything.
But.... the file was writed by code included on another file... it's needed to find it because probably include the needed function

needforszpit said:
without I know where is file located on system is littlebit hard to say anything.
But.... the file was writed by code included on another file... it's needed to find it because probably include the needed function
Click to expand...
Click to collapse
The file is located in sys/devices/qpnp-charger-e89dec00/power_supply/battery "charge_full" and "charge_full_design". I don´t know if this is the correct file that determines the recognized battery capacity.

I try a solution bu its not tested...
1. download and install: https://play.google.com/store/apps/details?id=com.battery.chargingstatus
Install termux: https://play.google.com/store/apps/details?id=com.termux
2. Save on PC framework-res.apk ( find it on: /sytem/framework directory) editable in apk: /res/xml/power_profile.xml U find a line with: battery.capacity 2100....change to 7200
For that action I use Kubuntu linux and MC(midnight commander).
Save ....
3.Upload to your phone the edited apk.
4.Start recovery mode...delete original framework-res.apk and copy the edited apk
5. reboot sytem.
6. Start Termux and use commands:
su
echo 7200000 /sys/class/power_supply/battery/charge_full_design
7. Reboot
8 Start battery status app and its show 7200

needforszpit said:
I try a solution bu its not tested...
1. download and install: https://play.google.com/store/apps/details?id=com.battery.chargingstatus
Install termux: https://play.google.com/store/apps/details?id=com.termux
2. Save on PC framework-res.apk ( find it on: /sytem/framework directory) editable in apk: /res/xml/power_profile.xml U find a line with: battery.capacity 2100....change to 7200
For that action I use Kubuntu linux and MC(midnight commander).
Save ....
3.Upload to your phone the edited apk.
4.Start recovery mode...delete original framework-res.apk and copy the edited apk
5. reboot sytem.
6. Start Termux and use commands:
su
echo 7200000 /sys/class/power_supply/battery/charge_full_design
7. Reboot
8 Start battery status app and its show 7200
Click to expand...
Click to collapse
So I´m stuck on uploading the edited apk to my phone. Everytime I replace the framwork-res.apk with the modded version I get stuck on the boot image. I don´t know what the problem is.

"echo 7200000 /sys/class/power_supply/battery/charge_full_design".....useless...its not rewrite the file...
Other....the rewrite of framework-res.apk its just a "looklike" thing...in chargingstatus looks battery like 7200 but on system works like an original
Solution NOT works

[fix] easy fix for balong issue

Hi!
i create a software to fix Balong issue after flashing a ROM.
Download the zip, extract the folder then only need to follow the steps in software!
Check the pictures bellow!
If fails check if cust image is properly installed before execute the software again.
Tell me if worked for you!
.

Thanks.

I've installed TWRP 3.1.1-0, but when I use your software it says "error: no devices/emulators found", even if I put the correct cust path

persona78 said:
Hi!
i create a software to fix Balong issue after flashing a ROM.
Download the zip, extract the folder then only need to follow the steps in software!
Check the pictures bellow!
If fails check if cust image is properly installed before execute the software again.
Tell me if worked for you!
.
Click to expand...
Click to collapse
Hi
After an update (official!) I re-encountered BALONG. After using your marvelous tool, it worked again, but there's no need to reset device (as written on CMD).
In addition, for the ones that get the error "no device attached" or something similar, you've only to reboot to TWRP, connect the phone to Windows and press Win+X, click on "device manager", look for "android device" or something similar. Right click on it and select "update driver", click the second option and than select that you already have the CD driver. You'll see a list: select "ADB composite device" and than finish: you've done!
Ah, I was about to forget: thank you!
Regards,
F

fixed
Hi.
Thanks for fast answer. I could fix the problem.
I downloaded the EMUI 3.1 as Magyar Telekom firmware from an arabic server cause ru huawei servers doesnt work lol. So I downloaded it I extracted boot, recovery, system, cust img files from UPDATE.APP with Huawei AppImage Extractor application. I flashed these with fastboot (Not TWRP, not huawei recovery). Fastboot from computer. Ok. But at the moment SIM does not work. I upgraded the system from Huawei update from settings (not recovery, system settings). After update the ROM and SIM is work perfectly.
Btw thanks your answer, topices too. This is a big help from you.
Have a nice day, Balázs.

How Can i use it for Meanaf Localization ????
How Can i use it for Meanaf Localization ????
@persona78
can you provide me Tool To fix Balong
Countryakistan
Mobile:ALE-L21
ROM:C185

Hello thanks for creating such tool
I've tried to use it but i get this error after TWRP boot :
mount: No such file or directory
mkdir: '/cust/hw': No such file or directory
ln: cannot create symbolic link from '/cust/hw/eu' to '/cust/hw/meafnaf': No such file or directory
Is there any solution for this?

-Mouhammad said:
Hello thanks for creating such tool
I've tried to use it but i get this error after TWRP boot :
mount: No such file or directory
mkdir: '/cust/hw': No such file or directory
ln: cannot create symbolic link from '/cust/hw/eu' to '/cust/hw/meafnaf': No such file or directory
Is there any solution for this?
Click to expand...
Click to collapse
Which Cust Path Do you Want?
hw/meafnaf?

MohmmadUzairKhan said:
Which Cust Path Do you Want?
hw/meafnaf?
Click to expand...
Click to collapse
The program detected this path : cust/hw/meanfaf
Is this what you mean?

-Mouhammad said:
The program detected this path : cust/hw/meanfaf
Is this what you mean?
Click to expand...
Click to collapse
What Do You Want?
hw/eu?

MohmmadUzairKhan said:
What Do You Want?
hw/eu?
Click to expand...
Click to collapse
Do you know what cuases this error?

Thank you its working excellent . And wipe is not needed. Tnx again ?

pls say me
how can i fix it with opened bootloader? must i flash cast?

Doesn't work. Did everything by the instructions. Twice.