Database Users

[TOOL][LINUX]COPERFIELD ROM MAKER create system.img for some devices

[TOOL][LINUX] COPERFIELD ROM MAKER v.0.0.2
DOWNLOAD TOOL
Suport:
Samsung Galaxy S
Samsung Galaxy Tab 7.0
Samsung Galaxy SII I9100
Samsung Galaxy SIII I9300
Samsung Galaxy NoteI N7000
Samsung Galaxy Tab 7.7 P6800
Google Nexus 7
1. Required LINUX and Root access on the device ...
2. Enable debug mode on the device and connect the USB to the PC.
3. Extract the file from the archive with the tool to check just in case the right of scripts and binaries folder /tools - all must be executed ...
4. From the root folder of the tool to run in a terminal script menu:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Configure the tool to claim 1 (necessary only once after the start of the tool):
6. Select the appropriate device, the program will create the device image of the system partition, download to PC and convert it to an image suitable for flashing Odin and put it in the out.
7. Select the package in the image archive .tar.md5 for flashing via Odin or fast boot (if necessary, may be placed in a folder out the rest of the ROM - the tool will pack them with the system image), enter the name new firmware and press Enter, the tool will create the firmware and display a report:
8. May be further packed in zip with maximum compression, to achieve the smallest size ...
9. The ability to create cache.img
10. Cache.img empty images in the folder empty (before flashing renamed cache.img)

the s2 and s3 system.img will be ext4 format ?

globula_neagra said:
the s2 and s3 system.img will be ext4 format ?
Click to expand...
Click to collapse
Of cause, kernels don't support different file systems...

Lol...I just started making script...here.But you finished it here perfectly with many devices supported .Good to see it.Let me see If I can anything better
---------- Post added at 10:13 AM ---------- Previous post was at 09:15 AM ----------
Just a little idea for you...If you make an empty data partition too,You can make sure that the rom does a factory reset while its been flashing

vijai2011 said:
Lol...I just started making script...here.But you finished it here perfectly with many devices supported .Good to see it.Let me see If I can anything better
Click to expand...
Click to collapse
Yes, I do not mind
Just a little idea for you...If you make an empty data partition too,You can make sure that the rom does a factory reset while its been flashing
Click to expand...
Click to collapse
I do not quite understand what you mean, but in order to reset a user's data is sufficient to add to the cache.img command wipe data...

as i9000 said:
Yes, I do not mind
I do not quite understand what you mean, but in order to reset a user's data is sufficient to add to the cache.img command wipe data...
Click to expand...
Click to collapse
I will pm you shortly with what I meant along with commands for you to understand it better
Sent from my GT-N7000 using xda app-developers app

Please can you help a noob - ROM seems extremely small
Hi I have been hunting for a tool to do a "complete" backup of my S3 so I can restore it in one go after playing with other ROMS and get back to Stock easily. So seeing this looked fantastic. I have run steps 1 , 4 and 10 .
The ROM i get is only 27,161 KB , and as the stock rom I flashed was over 1 gb I wonder if I have done something wrong and I am afraid to try flashing this with Odin . Especially when I did a NANDROID Backup from S3 Toolkit and this is 1.6gb .
Any advice would be well received .

plug_it_in said:
Hi I have been hunting for a tool to do a "complete" backup of my S3 so I can restore it in one go after playing with other ROMS and get back to Stock easily. So seeing this looked fantastic. I have run steps 1 , 4 and 10 .
The ROM i get is only 27,161 KB , and as the stock rom I flashed was over 1 gb I wonder if I have done something wrong and I am afraid to try flashing this with Odin . Especially when I did a NANDROID Backup from S3 Toolkit and this is 1.6gb .
Any advice would be well received .
Click to expand...
Click to collapse
You forgot step 5! configure tool, compile and install zlib and compile ext4_utils, and got empty image system.img...

is there a chance of a port to cygwin?

I like how the title says it supports any device and then the first post says it supports less than 10 devices.

Creating .tar.md5 will create images that increase binary counter ?
Edit:
Only with custom recovery

gianptune said:
I like how the title says it supports any device and then the first post says it supports less than 10 devices.
Click to expand...
Click to collapse
Sorry, it all my bad english, of cose isn't any but some...
I did chang it...

Is there any apps like this for W8??
Sent from my E16i using xda premium

Hi and thx for a great tool
1. Any chance when I run 6. that it stops when it is mounted and I can edit/add content in the output.img before it creates a system.img?
Would be nice to be able to edit before system.img
2. Possible to edit a factory system.img that I have on pc?
Thx for your time

Nandroid Backup Without Booting Into Recovery

Hello I found this interesting thread where you can make a nandroid backup without booting into recovery! Credit goes all to the developer..
Here is the link to his thread
Link to his thread here
ameer1234567890 said:
Nandroid backups are usually performed in recovery mode. This means you would have to turn off your phone and reboot in recovery mode, which wastes a whole lot of time rebooting and a lot more time offline. For me, this has been a killer as I do regular nandroid backups. Having to reboot in recovery and finding missed calls, sms from my wife and friends is totally not accepatable for me. So, I set to develop an online nandroid backup tool, namely Online Nandroid, which can do nandroid backups without switching off my phone.
Today, I am releasing it to public, as it may serve good for some others too. Originally I developed Online Nandroid specifically for Xperia devices, but now I am releasing it for all android devices.
This tool, eventhough called "Online Nandroid", does not upload/save backups to any online/cloud services. Online here means that it does backup while phone is live or still running Android.
The short name onandroid is meant to be pronouced as o-nandroid or o'nandroid and NOT on-android.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Requirements:
1. Rooted android phone
2. A terminal emulator installed on phone
3. Latest version of Busybox
4. A working CWM, TWRP or 4EXT based recovery installed
5. Some patience
Installation:
1. Download and copy zip file to SD card
2. Reboot into recovery
3. Choose install zip from SD card, select zip and flash
4. Reboot
Usage:
1. Open terminal emulator
2. Type su to obtain root
3. Type onandroid
4. Wait and watch
Twitter: @OnlineNandroid
Source: http://bit.ly/OnlineNandroid
Issue Tracker: http://bit.ly/OnlineNandroid-issues
Older Versions: http://bit.ly/OnlineNandroid-downloads
Click to expand...
Click to collapse

To make life a lot easier just go to Google Play and get Online Nandroid Backup * ROOT
https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup
The GUI developed by Thomas Otero makes it much more user friendly (and of course he properly credits Ameer for his work). It even checks for updated versions of the script.

Help please

Hello I just bought a Samsung Galaxy S4 GI9505 used locked to EE.
I wanted to unlock it and found on ebay unlocking for £5...
from
http://www.ebay.co.uk/itm/271624591845
So I thought I'd try that.
Then it required the phone to be rooted so I rooted it with towelroot and everything was fine...
Then I selected gi9505 to unlock my phone it came up with a error...
22:55:19 - ADB Device: GT-I9505
22:55:19 - SW Version: I9505XXUFNC4 (Android: 4.4.2)
22:55:19 - Checking SU Root Access..
22:55:22 - ROOT Access: True (SuperUser) Processing..
22:55:22 - Searching modem on COM9 Please Wait..
22:55:23 - Backupping NVM Now Please Wait..
22:57:31 - Found M9KEFS1 at /dev/block/mmcblk0p13
22:57:31 - Found M9KEFS2 at /dev/block/mmcblk0p14
22:57:31 - Found M9KEFS3 at /dev/block/mmcblk0p15
22:57:31 - Backupping Blocks to SDCard..
22:57:35 - Current Device Imei: --------------
22:57:36 - Current MSLADDR: RF1D562D8P
22:57:37 - Rebooting phone.. please wait...
22:59:38 - MSL Bypass: Failed Restoring Backup
22:59:38 - Restore Done, Rebooting phone..
ERROR: Bypass Failed.. Please try again
Now when I put a sim card in I get a white no entry signal icon instead of the option to put the sim card unlock code in box?
Please can someone help
IMEI number above..deleted by me for safety.
Thanks

Hello, I answer here to help also someone that may have your same problem.
Go in Settings>Device info and see "Baseband version", paste here the code that you see

AntaresOne said:
Hello, I answer here to help also someone that may have your same problem.
Go in Settings>Device info and see "Baseband version", paste here the code that you see
Click to expand...
Click to collapse
Exactly My PM! @AntaresOne
His baseband is I9505XXUFNC4
Sent from my GT-I9500 using XDA Free mobile app

@DeepankarS
As I wrote in PM:
Sounds like a bad efs, a backup should ALWAYS be made before touching the simlock things.
In S4 EFS contains IMEI, simlock infos, some radio calibration data, gyroscope sensor calibration data, bluetooth & wifi MAC addresses, some carrier things, DRM stuff and some other things..
Click to expand...
Click to collapse
@XDA00000
Download Root Browser from Play Store and go in efs folder, take a screenshot and upload here
Inviato dal mio GT-I9505

Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AntaresOne said:
@DeepankarS
As I wrote in PM:
@XDA00000
Download Root Browser from Play Store and go in efs folder, take a screenshot and upload here
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
@AntaresOne, @DeepankarS
Thanks you both for your kind help...
Here is as requested the screenshots.
Many thanks, hope you can help
Cheers

update
@AntaresOne, @DeepankarS
Just an update, the phone works fine ( can make / receive calls, send text etc) with the network it is locked to EE UK.
Only the IMEI number comes up unknown insettings / or *#060# dialer IMEI number comes up as 01
Thanks

Transfer NANDROID Backup from broken D5803 Device to another intact D5803 Device

Hi, I used TWRP to create the following NANDROID Backup:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The backup source phone ( D5803_No1 ) has a touchscreen that does not work anymore.
I have another z3c phone ( lets call it D5803_No2 ) with a partially broken touchscreen and an intact z3c ( D5803_No3 ).
I used the same software stack to install a rootable stock 5.1.1 ROM, root and install TWRP on device D5803_No1, D5803_No2 and D5803_No3 ( the fully intact one )
That means all on all 3 Phones:
I used flashtool-0.9.20.0-windows.exe to flash D5803_23.4.A.1.264_1289-4696_R8C.ftf ( which was a modified 5.1.1 ROM that I could root with giefroot_v3.1 ) and then install XZDualRecovery.
Phone D5803_No1 was the one I used on a daily basis before the touchscreen broke.
Now I tried the following:
Restore a fully NANDROID Backup ( as seen in the screenshot above ) that I created with my broken daily use Phone D5803_No1 to the blank rooted D5803_No2.
I did not wipe anything on D5803_No2 before and I checked to restore all 5 Paritions that I backed up.
To recover a backup from a foreign device I had also to do the following step TWRP recovery doesn't show the backup file. Problem with restoring nandroid.
When it came to the /data partition I got an error in TWRP ( I think something like "cannot wipe /data" but not sure anymore ) and my only option was to reboot the phone.
Now it is bricked, not discovered by flashtool anymore.
I read here that you will hard brick your device if you try to flash the TA from one device to another ( what I tired to do ).
My question is:
1. Has anybody any experience with transferring a NANDROID Backup from one phone to another ( same model of course )
2.
If there is not the answer "it is definitely not possible to transfer a backup to another phone"
Which partitions should I try to recover from D5803_No1 to D5803_No3 ( the fully intact one ) to minimize the chance of a ( soft/hard) brick ? Should I wipe some partitions before recovering ?

Yes, flashing a TA backup from another Z3c will hard-brick the phone.
You could try to restore only the data partition on your 3rd z3c and wipe cache + dalvik. From what I read on the forums it should work and boot, but it is very likely that the camera won't work because of some device-specific DRM settings that are stored on the data partition. So actually this isn't recommendable either.
I would advise you to get a USB OTG cable to connect a PC mouse to your 1st z3c and then take a Titanium Backup of all your apps and settings. After this, restore everything you need on your 3rd Z3c.
Good luck! :fingers-crossed:

[RECOVERY][ROOT]TWRP 3.2.3-1 - Galaxy J2 Grand Prime SM-G532F/G/M

Unofficial release -TWRP recovery for the Samsung Galaxy J2 Grand Prime SM-G532F/G/M/DS - Mediatek MT6737T​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This device forces encryption.
To disable forced encryption, mount internal storage(DATA) and disable dm-verity you must flash the boot patcher below:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patcher:
no-verity-no-encrypt_ashyx
XDAevDB Information
TWRP Recovery, Tool/Utility for the SM-G532F/G/M
Contributors
kiruha_21, TeamReloaded
Version Information
Status: Stable
Current Stable Version: 3.2.3.1
Last Updated 2018-10-02
Downloads: TWRP_by_kiruha_21

I have corrected mistakes who put, I ask to pump over

Does it work in TV version? 532MT 16GB

Thanks, I've wanted a newer version of TWRP for a while!

Hi..
Is this ready to be flashed or does it still need to be ported?
my phone is Samsung Galaxy J2 Prime SM-G532G..

mike7486 said:
Hi..
Is this ready to be flashed or does it still need to be ported?
my phone is Samsung Galaxy J2 Prime SM-G532G..
Click to expand...
Click to collapse
This one is unstable.
(The fact that this include fstab.ranchu/goldfish for emulators instead of regular fstab.mt6735 means OP takes little effort to do extensive testing..)
Might you want the list of bugs:
[This was tested during my LineageOS testing]
1. It is unable to boot to TWRP if phone powered off
2. Restore EFS failed (almost trash my phone)
3. Sometimes /data and /system won't mount.

Prove N. said:
This one is unstable.
(The fact that this include fstab.ranchu/goldfish for emulators instead of regular fstab.mt6735 means OP takes little effort to do extensive testing..)
Might you want the list of bugs:
[This was tested during my LineageOS testing]
1. It is unable to boot to TWRP if phone powered off
2. Restore EFS failed (almost trash my phone)
3. Sometimes /data and /system won't mount.
Click to expand...
Click to collapse
indeed, i tried to port it manually using Image Factory app, replaced Zimage, uevend.rc, default.prop & added fstab.mt6735 from my stock bootimg, but when i boot to recovery, both internal & external storage cannot be mounted.

Hello reply me please
hello friend, this twrp works on the J2 Prime SM-G532MT 16GB Version? even if it does not read the internal memory and works, it has been able to read Pendrives Via OTG Or Ate The Memory Card?

LucasNamikaze said:
hello friend, this twrp works on the J2 Prime SM-G532MT 16GB Version? even if it does not read the internal memory and works, it has been able to read Pendrives Via OTG Or Ate The Memory Card?
Click to expand...
Click to collapse
my first contribution :victory:
is working on the G532MT
but I realized that it only worked after wipe / data
I had to reboot, and only after that he allowed access to mount OTG and SD, even in other versions I had this problem, but solved that way with this TWRP.
I'm sorry about the writing , I'm brazilian, and to ensure the best understanding I used translate
I also leave here my thanks to all of XDA, for their strength in helping everyone with dedication and responsibility.
God bless you all

thank you, can it be for j2 prime right bro?
Sent from my SM-G532G using Tapatalk

LeonidasRodrigues said:
my first contribution :victory:
is working on the G532MT
but I realized that it only worked after wipe / data
I had to reboot, and only after that he allowed access to mount OTG and SD, even in other versions I had this problem, but solved that way with this TWRP.
I'm sorry about the writing , I'm brazilian, and to ensure the best understanding I used translate
I also leave here my thanks to all of XDA, for their strength in helping everyone with dedication and responsibility.
God bless you all
Click to expand...
Click to collapse
I'm Brazilian too, thanks for the information

No mirrors found when downloading...

LucasNamikaze said:
I'm Brazilian too, thanks for the information
Click to expand...
Click to collapse
BIG troubles with 3.1.1.0 version... almost useless...
What version do you indicar???
I'm brasilian too...