Hello all,
Basically i want to know if there is anyway to flash a modem besides to odin, like from within the phone and no need for computer connection.
Thanks
dd from a terminal session.
Code:
su
dd if=/sdcard/modem.bin of=/dev/block/mmcblk0p8 bs=4096
reboot
Did it that way myself already, worked fine.
Thanks for you reply! Will definately try that once i figure out what does "dd from a terminal session" mean exaclty, sorry I am a noob lol
It means:
Download a "Terminal" App from the Market (that App gives you kind of a console screen where you can enter commands) and type what I posted above into it.
But make sure you actually copy the modem software you want to flash to /sdcard/modem.bin first.
You are my hero.
Hi xda,
i bought myself a I9100 with the following Specs:
Android-Version: 2.3.5
PDA: I9100BHKJ1
Phone: I9100XXKI4
CSC: I9100 XEGKJ1
Baseband: I9100XXKI4
Kernel-Version: 2.6.35.7-I9100BHKJ1-CL630390 [email protected] #2
Buildnumber: GINGERBREAD.BHKJ1
PCode: GT-I9100LKAXEG
It has a branding from the German Provider 1&1
I am interested in doing a Backup (nandroid, EFS, Kernel) of my Phone whenever i experience Problems with the Software. Additionally i am (of course) interested in trying new roms or get the soon to come ICS early.
My Problem is, that i cant do that because i have no Download-Source for that Rom to get my Phone back to stock.
So i think the only way would be to Backup the existing Software on the Phone. What would be the right way to do it? I cant flash a rooted Kernel because i will lose my original one. I cant put CWM/Titanium on the Phone without root. And how would i deinstall CWM?
Is there maybe a possibility to use the Guarantee from Samsung directly, when i use another stock Rom?
Help would be highly appreciated.
btw: Merry Christmas and thanks for any Answers
There's a few ways of achieving what you want, but none are guaranteed to keep your warranty, as it's obviously done at your own risk.
You could achieve temp root by using the zergRush exploit. From there you could dump the current kernel, then either flash a kernel which comes with CWM recovery and do a nandroid backup, or dump the whole filesystem without changing kernel at all.
If you're comfortable with adb, see http://forum.xda-developers.com/showthread.php?p=15670403#post15670403 (ignore the part about flashing an insecure kernel, as zergRush should make that part unnecessary).
Thank you for the advice. I think that is what i need to do.
I have to add one more thing (no im not the Ghost of Steve Jobs ). I dont have experience on adb-Shell or Linux in General.
But i would like to try that with your help.
If i did understand it right the way could be:
get root on my stock Kernel with Zergrush
[
How do i get into the Shell?]
Dump all images [Are the command in the mentioned Thread correct? My SGS2 has no SD-Card inside, will that be a problem?]
Alternatively Dump the Kernel only
Install rooted CWM'ed Kernel [How?]
Use Nandroid/Titanium/EFS-Backup
How will i bring all the Images back to the Phone when needed? Respectively the Kernel Only if i used CWM for Backup?
Maybe there exists a detailed howto, because i dont have the maybe needed experience?
I think getting Root with Doomlord/Zergrush is no problem.
When i got root, where exactly i paste the commands shown here (http://forum.xda-developers.com/showthread.php?p=15670403#post15670403)
When i dump the Kernel it will be a rooted dump and i will have to unroot it after putting it back?
How exactly will i have to do the "putting it back" when i need to?
I did not find a Guide (for Noobs like me) or maybe a Tool like HC-kTool (but its for EFS only), that could make things easy. If someone could explain some of these things to me i am willing to learn
How to backup your Phone without Flashing anything by using the Zergrush Exploit
(Now with temp-root method, look at the Bottom)
high chance backups might not work, because the sources are mounted in this guide, doing this i a unmounted state (recovery console from cwm) should work
You need:
Android SDK (to get adb.exe)
Zergrush Doomlord V3 ROOT (Android 2.2 and 2.3)
Zergrush Doomlord V1 UNROOT
Installed Drivers for your Phone
Have all Programs deactivated that use your Device (like Kies)
Your brain, because you do this at your own Risk.
BACKUP your Phone (tested on I9100)
1
Root your Device with Doomlord V3 ROOT following all his hints
http://forum.xda-developers.com/showthread.php?t=1312859
2
Start your command prompt (cmd) and use cd.., dir and cd [Folder] to move to your Folder with adb.exe
type
adb shell [Enter]
su [Enter]
3
Dump the Partitions following all hints from HellcatDroid:
http://forum.xda-developers.com/showthread.php?p=15670403#post15670403
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/p1-EFS.img bs=4096
dd if=/dev/block/mmcblk0p4 of=/sdcard/p4-PARAM.img bs=4096
dd if=/dev/block/mmcblk0p5 of=/sdcard/p5-KERNEL.img bs=4096
dd if=/dev/block/mmcblk0p8 of=/sdcard/p8-MODEM.img bs=4096
dd if=/dev/block/mmcblk0p9 of=/sdcard/p9-FACTORYFS.img bs=4096
dd if=/dev/block/mmcblk0p12 of=/sdcard/p12-HIDDEN.img bs=4096
You can exit the su and the adb shell with "exit".
Hint: p9 and p12 are big, the Copying did run 70 Seconds for me
4
Unroot your Device again with Doomlord V1 UNROOT following all his Hints
http://forum.xda-developers.com/showthread.php?t=1321582
When everything is done you can deactivate the USB debugging-Mode and copy the Backups from your internal SD-Card to any safe Positions.
Put back your Backups [untested]
1
Have a rooted Kernel / Flash a rooted Kernel / Root with Doomlord V3 ROOT
put the Images back directly onto the Phone
2
Start your command prompt and use cd.., dir and cd [Folder] to move to your Folder with adb.exe
type
adb shell [Enter]
su [Enter]
3
(Information taken from HellcatDroids posts
http://forum.xda-developers.com/showpost.php?p=16052607&postcount=61 and
http://forum.xda-developers.com/showthread.php?p=15670403#post15670403 )
Code:
dd if=/sdcard/p1-EFS.img of=/dev/block/mmcblk0p1 bs=4096
dd if=/sdcard/p4-PARAM.img of=/dev/block/mmcblk0p4 bs=4096
dd if=/sdcard/p5-KERNEL.img of=/dev/block/mmcblk0p5 bs=4096
dd if=/sdcard/p8-MODEM.img of=/dev/block/mmcblk0p8 bs=4096
dd if=/sdcard/p9-FACTORYFS.img of=/dev/block/mmcblk0p9 bs=4096
dd if=/sdcard/p12-HIDDEN.img of=/dev/block/mmcblk0p12 bs=4096
4
Unroot your Device again with Doomlord V1 Unroot following all Hints there
http://forum.xda-developers.com/showthread.php?t=1321582
Credits to: HellcatDroid, Revolutionary for the Zerglings, oinkylicious, DooMLoRD, paxChristos, MistahBungle (for the extra Motivation )
I think it would help everyone if you could make a full backup of your very own device instead of having to download a Rom and Kernel that hopefully fits your device. With this method we leave minimal traces
Without Doomlord (no su etc needed)
I tested the Tip from oinkylicious. It worked!
You dont need Doomlord ROOT and UNROOT for this Procedure (but its the best for permanently rooting your Kernel)
At the Points in my Guide where i use Doomlord, you can use the Zergrush-Method directly. And you dont need the unrooting-step (tested with titanium backup). In addition you dont need the su-command from step 2.
Follow the points here (thanks to paxChristos):
1) Put a fresh (just formatted with no data on it) SD Card into your phone (this helps with some roots, not all, but better safe than sorry)
2) On your phone, goto settings -> applications -> development and check "USB debugging"
3) Plug your phone into your computer
4) Download zergRush
5) unzip zergRush
6) navigate to android sdk (varies from computer to computer, my (win7) install location was c:\Android-SDK-x86 (or something like that)
7) (If you've already downloaded all the sdk tools, you don't need this one) Download and install any missing sdk tools (i.e. adb) (i just selected most of the and let my computer sit overnight to install everything)
8) run command prompt (in windows 7, press windows flag + r to open up the run command, then type cmd, hit enter)
9) Navigate to the "platform-tools" folder inside of your android-sdk folder
10) type in "adb push C:\[location of zergRush]\zergRush /data/local"
11) type in "adb shell"
12) type in chmod 755 /data/local/zergRush
13) type in "/data/local/zergRush"
14) Good luck, it works on some phones, but not others!
Gänsebraten...
I've been watching this thread develop over the past day or so & just wanted to quickly say I reckon you've done a fantastic job with these instructions mate
I know you'll say you had a lot of help (which you did), but initially, you asked the "right" questions (You knew where you wanted to go, but you didn't quite know how to get there, if you know what I mean ?), you persevered and in the space of one day, you've come up with a really useful reference for anyone who wants to backup their phone purely by using Zegrush.
Well done mate. Fantastic job
Hi, thanks
Indeed i had much Help. I think putting some known Information together can bring a new Usefulness. (Just like how our Phones use some Sensors and some Code and some Internet and form something cool like Google Sky Map)
I'm a bit trained in findind Solutions in General due to my Education and Job, which helps a lot. And im reading and collecting Information and Software on the Topic since 2 days.
Currently im trying to find out how to put the Backup back and if it is enough to be prepared (asked HellcatDroid)
I think this could be the simplest way to backup your phone and be independant from Downloads or Tools (ofc. you need Root somehow)
I added a way to flash back the Images. But i gathered it from the Forum and did not test it myself. Anybody can confirm it? Maybe someone tested it?
gänsebraten said:
I think this could be the simplest way to backup your phone and be independant from Downloads or Tools (ofc. you need Root somehow)
Click to expand...
Click to collapse
I notice you went with a permanent root rather than temp root method, which means your backup will also be rooted and thus not stock. If you go for temp root instead (i.e. not pushing busybox, su, superuser) then the backup would be as close as you're likely to get to stock. In case you missed it, I specifically linked you to temp root (http://forum.xda-developers.com/showthread.php?t=1296916) rather than DoomMLoRD's perma-root script (http://forum.xda-developers.com/showthread.php?t=1321582)
thanks oinky, i did not get, that it was a temp root
What exactly makes it temp? Will it unroot when the Phone restarts?
I really missed that point Well i'll test that tomorrow.
Can you confirm my way of "using" the Backup? Will i have 100% of my old status back (except the rooting thing ofc.)? Can i start happy flashing now?
Sorry i have to ask again. Did someone already test flashing the Backups back?
I also would appreciate a confirmation that the restoration via this method works fine.
can anyone confirm this? probably mr. oinkylicious? you seem to me very sagacious.
added the direct use of zergrush in my Guide. now you'll leave even less traces (Although i found no traces with using Doomlord). The Zergrush-File we adb-pushed is gone, too
But one thing we dont know yet:
Will the backups work and be 100% sufficient when done correctly? I'm asking for someone who can confirm or has tested that
Additional Tips i found:
boomsh error at second zergrush:
http://eitwebguru.com/tag/cannot-copy-boomsh-permission-denied/
To fix this issue you have to delete two files i.e. /data/local/tmp/boomsh and /data/local/tmp/sh. Following are the commands to remove the files
E:\ADB\adb.exe shell
$ rm /data/local/tmp/boomsh
$ rm /data/local/tmp/sh
I did a compare (cmp imagefile and directory) and got several problems e.g. "differ byte 1036"
Also i found a thread where someone got Problems with dd
http://forum.xda-developers.com/showthread.php?t=1149714
might be unsafe
gänsebraten said:
Additional Tips i found:
boomsh error at second zergrush:
http://eitwebguru.com/tag/cannot-copy-boomsh-permission-denied/
To fix this issue you have to delete two files i.e. /data/local/tmp/boomsh and /data/local/tmp/sh. Following are the commands to remove the files
E:\ADB\adb.exe shell
$ rm /data/local/tmp/boomsh
$ rm /data/local/tmp/sh
I did a compare (cmp imagefile and directory) and got several problems e.g. "differ byte 1036"
Also i found a thread where someone got Problems with dd
http://forum.xda-developers.com/showthread.php?t=1149714
might be unsafe
Click to expand...
Click to collapse
oh no, this would be such a nice method
gänsebraten said:
thanks oinky, i did not get, that it was a temp root
What exactly makes it temp? Will it unroot when the Phone restarts?
I really missed that point Well i'll test that tomorrow.
Can you confirm my way of "using" the Backup? Will i have 100% of my old status back (except the rooting thing ofc.)? Can i start happy flashing now?
Click to expand...
Click to collapse
Well as for the guarantee I have bad news for you.
The bad news is that your current backup is useless, if you did a permanent root, not a temporary root, which means that the backup is rooted and therefore not stock.
In that case unroot and make another one.
Besides that I'm curious...
I got my phone from o2 Germany and already had it replaced twice AFTER flashing it.
Does 1&1 have a special branding? What sort of branding do you have? o2 had none and therefore I just flashed a ROM from Intratech's thread before returning it and reset the custom binary counter.
Sent from my GT-I9100 using XDA App
hi sniperfan,
my backup is not useless, just look at my guide where the unroot is implemented. I have now a temp-rooted backup, too.
The Branding is a modified starting-screen, some apps (mail etc.), an own market, starting page in browser.
In Addition i do not find any ROMS/Kernels to download (look at my post 1). There must be a way how the branded ones were created. I would love to see the List to be completed.
gänsebraten said:
There must be a way how the branded ones were created.
Click to expand...
Click to collapse
Thats the point gänsebraten!
how are the branded ROMs being created? there must be a way to produce them!
how it is achieved and how can we do it?
Yay, lot's of good info in this thread already
Yeah, doing "raw dumps" via "dd" of all(!) partitions is the perfect thing to do, I did that myself before I flashed anything (except the kernel, but for my initial ROM the kernel was available for download).
So you should end up with a bunch of dd images, the ones you really need are:
- mmcblk0p1 => EFS
- mmcblk0p4 => param.lfs (contains the bootscreen and some tiny other bits)
- mmcblk0p5 => kernel
- mmcblk0p8 => modem FW
- mmcblk0p9 => system
- mmcblk0p10 => userdata
Do *NOT* overwrite these onw when restoring:
- mmcplk0p2 and p3 => SBL, bootloaders, don't touch them, just leave them allone, this is the ONE way to really, unrecoverably BRICK the device, breaking these buddies.
What you "can" backup/restore, but don't really need to:
- mmcblk0p7 => cache
- mmcblk0p11 => "internal SD card"
- mmcblk0p12 => some preinstall stuff
To restore something / everything, just reverse the dd command, so if you used
Code:
dd if=/dev/block/mmcblk0p9 of=/sdcard/system.img bs=4096
to dump/backup a partition, use
Code:
dd if=/sdcard/system.img of=/dev/block/mmcblk0p9 bs=4096
to restore it.
Another note on that:
Once you dd'ed the kernel, you should really flash a CWM kernel and then do all the other dd's from recovery mode via ADB.
Reason being: dd'ing a mounted filesystem (i.e. while the system is running and accessing it) can (usually WILL) lead to an unclean/corrupted image that doesn't work properly anymore when restored.
gänsebraten said:
hi sniperfan,
my backup is not useless, just look at my guide where the unroot is implemented. I have now a temp-rooted backup, too.
The Branding is a modified starting-screen, some apps (mail etc.), an own market, starting page in browser.
In Addition i do not find any ROMS/Kernels to download (look at my post 1). There must be a way how the branded ones were created. I would love to see the List to be completed.
Click to expand...
Click to collapse
Sorry I got that wrong.
As for your question:
Here is one way. (Note: NOT for that galaxy s2 in this thread, so command may differ)
http://forum.xda-developers.com/showthread.php?t=1082288
I will test it tomorrow...eeehhhhhm....later. xD
They simply compose their own updates with added apps and "tweaked" configurations.
Sent from my GT-I9100 using XDA App
Someone, please, with a rooted device, execute the following...
Code:
adb shell su -c "mkdir /sdcard/output; dd if=/dev/block/platform/dw_mmc/by-name/BOOT of=/sdcard/output/boot.bin ; dd if=/dev/block/platform/dw_mmc/by-name/HIDDEN of=/sdcard/output/hidden.img ; dd if=/dev/block/platform/dw_mmc/by-name/PARAM of=/sdcard/output/param.bin ; dd if=/dev/block/platform/dw_mmc/by-name/RADIO of=/sdcard/output/modem.bin ; dd if=/dev/block/platform/dw_mmc/by-name/RECOVERY of=/sdcard/output/recovery.img ; dd if=/dev/block/platform/dw_mmc/by-name/SYSTEM of=/sdcard/output/system.img ; dd if=/dev/block/platform/dw_mmc/by-name/TOMBSTONES of=/sdcard/output/tombstones.img"
then do an adb pull /sdcard/output in a good folder. zip the files up and upload to hotfile.com or something.
I'm having big problems with even getting the device to boot because we don't have this. I'm mis-matching files from several different people/builds. I really need this set of files from a single working device.
IRC channel
I'm doing it now and im in the irc channel
Left you a PM in the IRC channel with a link to where to download it
Additional source left. That should help in the quest.
For those of us who don't know anything about development fill us in a bit Assuming this is bootloader work being done.
bose301s said:
For those of us who don't know anything about development fill us in a bit Assuming this is bootloader work being done.
Click to expand...
Click to collapse
Im pretty sure that he is just trying to make a working stock odin file
Sent from my SCH-I605 using Tapatalk 2
Hey guys... using IRC is great, but it impedes the flow of information. When you use the Forums or Google+, it's searchable by google and colaborative effort is possible.
here are the links I got on IRC.
http://dl.dropbox.com/u/88471315/Outler.rar
http://daxterfellowesservers.com/adamoutler/
Also, there is another one coming soon which is official, but this should be enough to get me up and running.
jellydroid13 said:
Im pretty sure that he is just trying to make a working stock odin file
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
That's exactly the goal. I need a stock firmware because my device is beyond booting and all currently available firmwares are improper for the device. So, my idea is to get some firmwares then create an Odin and a Heimdall package.
Hey Adam, what part of LA are you from?
Hi! First post. I'm a 33-year-old kid and my old fascinate is my playground. There is nothing in particular that I want to do. I have a background in programming and linux, but I'm new to android internals. I want to know everything. But lest I overwhelm you, I'll just start with Odin.
So I dove into many articles and read a lot of things and experimented with various things. I have several different versions of Odin on my computer and successfully used it to flash CWM and install some zips to root my device and used adb shell to su and poke around. That was fun. But before I make significant changes, I started experimenting with backups. I got a nandroid backup via CWM and then used a slick little article to create my own Odin-compatible (I hope) backup of 6 different partitions/devs. Here's my notes below:
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096 (ROM:/system)
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096 (Kernel)
dd if=/dev/block/bml8 of=/sdcard/recovery.bin bs=4096 (Recovery)
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096 (Cache:/cache)
dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096 (DBData:/dbdata)
dd if=/dev/block/mmcblk0p1 of=/sdcard/movinand.bin bs=4096 (Data:/data)
The article just basically had me tar them all together and generate an MD5 to append to the file. But another article had a tutorial that warned against flashing more than one file at once. So that makes me aware of just how little I know about Odin. So here's some more specific questions to get me started:
1) How does Odin know if something is meant for recovery vs system? Are the file names within the tarball special?
2) How does Odin know how to flash the recovery space, for example? Is it partition or /dev/block/<device> aware or is it abstracted via some sort of android API?
3) While we're at it, what protocol does Odin or the Samsung drivers use to communicate with the android device? Is it documented?
4) Is there a commandline equivalent to Odin that uses this protocol or drivers?
5) Is there a problem with flashing more than one file at once?
6) Is there a way to backup the boot section or radios or whatever else that I might flash? There's a LOT of devices under /dev/block, and I don't know what they mean.
So please, give me your best stabs at the above questions and anything else you know. Again, I want to know everything.
My best advice for you is to find the Heimdall thread and read it. Heimdall is an open-source alternative to Odin, created by an XDA user. Odin's code is proprietary, and the program was not originally intended for use outside of Samsung. Because it is leaked software, there is no support or manual for it's use from Samsung, and how it works is a company secret. I suspect it was intentionally leaked to stimulate development without assuming liability for it's use. Since there is an opensource alternative (and because I don't use windows), I have steered clear of using such a powerful program of questionable origin, and was an early adapter of command-line Heimdall (first to use it on the Fascinate...)
Andive said:
Hi! First post. I'm a 33-year-old kid and my old fascinate is my playground. There is nothing in particular that I want to do. I have a background in programming and linux, but I'm new to android internals. I want to know everything. But lest I overwhelm you, I'll just start with Odin.
So I dove into many articles and read a lot of things and experimented with various things. I have several different versions of Odin on my computer and successfully used it to flash CWM and install some zips to root my device and used adb shell to su and poke around. That was fun. But before I make significant changes, I started experimenting with backups. I got a nandroid backup via CWM and then used a slick little article to create my own Odin-compatible (I hope) backup of 6 different partitions/devs. Here's my notes below:
dd if=/dev/block/stl9 of=/sdcard/factoryfs.rfs bs=4096 (ROM:/system)
dd if=/dev/block/bml7 of=/sdcard/zImage bs=4096 (Kernel)
dd if=/dev/block/bml8 of=/sdcard/recovery.bin bs=4096 (Recovery)
dd if=/dev/block/stl11 of=/sdcard/cache.rfs bs=4096 (Cache:/cache)
dd if=/dev/block/stl10 of=/sdcard/dbdata.rfs bs=4096 (DBData:/dbdata)
dd if=/dev/block/mmcblk0p1 of=/sdcard/movinand.bin bs=4096 (Data:/data)
The article just basically had me tar them all together and generate an MD5 to append to the file. But another article had a tutorial that warned against flashing more than one file at once. So that makes me aware of just how little I know about Odin. So here's some more specific questions to get me started:
1) How does Odin know if something is meant for recovery vs system? Are the file names within the tarball special?
2) How does Odin know how to flash the recovery space, for example? Is it partition or /dev/block/<device> aware or is it abstracted via some sort of android API?
3) While we're at it, what protocol does Odin or the Samsung drivers use to communicate with the android device? Is it documented?
4) Is there a commandline equivalent to Odin that uses this protocol or drivers?
5) Is there a problem with flashing more than one file at once?
6) Is there a way to backup the boot section or radios or whatever else that I might flash? There's a LOT of devices under /dev/block, and I don't know what they mean.
So please, give me your best stabs at the above questions and anything else you know. Again, I want to know everything.
Click to expand...
Click to collapse
So helpful I may toy with my fassy I really needed to know where movinand.bin goes now we linux users can flash it since heimdall doesnt and we need it or recovery acts strange and so will the device
I have a Motorola Moto E (2nd Gen) Dual SIM [XT1521] [BOOTLOADER UNLOCKED]
I used fastboot erase all while installing stock rom which erased hob,dhob,carrier,keystore,fsc parititions of my phone.
Because of this my phone is is showing IMEI 0 when I enter *#06#, resulting in no network.
I have searched the internet an tried everything (even 4 different ROMs, 3 versions of stock ROMs), nothing works.This is the only chance to bring back my phone.
All the other partitions are flashed during stock rom installstion,but the hob,dhob,carrier,keystore,fsc partitions are not available any where in the internet.
I need images of these partition so I can flash them again.
Someone PLEASE HELP me out
These are the commands, I dont know which one works, both are same -
Code:
dd if=/sdcard/dhob.img of=/dev/block/mmcblk0p22
dd if=/sdcard/fsc.img of=/dev/block/mmcblk0p24
dd if=/sdcard/hob.img of=/dev/block/mmcblk0p21
dd if=/sdcard/keystore.img of=/dev/block/mmcblk0p36
dd if=/sdcard/carrier.img of=/dev/block/mmcblk0p38
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/hob" of=/sdcard0/imei_backup/hob.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/dhob" of=/sdcard0/imei_backup/dhob.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/fsc" of=/sdcard0/imei_backup/fsc.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/carrier" of=/sdcard0/imei_backup/carrier.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/keystore" of=/sdcard0/imei_backup/keystore.img
These are the threads I refferred -
https://forum.xda-developers.com/moto-g/help/imp-imei-backup-scripts-moto-g-eall-t3174569
https://forum.xda-developers.com/moto-g/help/hob-dhob-fsc-dumps-moto-g-lte-t3288862
https://forum.xda-developers.com/2015-moto-g/help/tuto-fastboot-erase-signal-t3451362
*****THANKS IN ADVANCE*****
same problem of you..no solution ?
Does this copy my IMEI in your device???
No bro..It does not copy your imei.The imei will remain as zero itself.So please upload those files.