Related
I've been reading all day and I'm confused and looking for some direction.
I have a mostly stock Droid Bionic that had been rooted using the motofail method. All was fine, and then I attempted to make the edit to my mount_ext3.sh file, but must have done something wrong.
At reboot, phone is stuck at the red Moto splash screen.
I thought I could use adb to pull / push the mount_ext3.sh script to edit out my error and put the file back. For some reason I am not able to do this. I believe I have the correct drivers installed, and I am able to see the adb device in my device manager. RSD lite also sees the device when in fastboot mode. But adb devices shows no device.
Can someone tell me if it's possible to use adb to restore this mount_ext3.sh file? I'd prefer to not factory wipe if possible.
Also, I notice that a lot of links and files referenced in rsd restore methods are gone or invalid. Although I have found them elsewhere (such as bionic_minimal_fxz.tar.gz) .. but I'm not sure my best course from here. Seems like the small edit should be easier to un-do. Can I boot from an SD card or mount the /system/ partition some other way?
Thanks, and if this belongs elsewhere, please let me know and I'll move it.
Thanks,
Chris
Are you using the factory cable from Motorola? Also are you using the latest drivers from Motorola? Make sure you using the correct drivers for 32 or 64 bit OSs.
Gosh .. factory cable. I'm not sure .. I have so many cables laying around.
The cable has several sticky labels that say:
Model: DICMUSB / DC1012 ..
Hmm .. this might be from my old Incredible - It has the following model numbers on the cable:
adr6300vw
adr6225vw
adr6226vw
mwp6985
Jimmeny Crickets. Now I can't seem to be able to get the phone to do much of anything. Sheesh .. indicator light on the front is steady white when usb connected. Did I read somewhere that you basically need a full battery for a lot of this stuff? Swell. Guess I'll home and get the wife's battery.
Majority of people's problem's i've noticed was people not using the factory cable. Motorola's cable are different from other manufacture cables as I've found out recently. I've had issues in the past using other cables and usually using the factory cable resolves my issue.
Link to post about motorola cable:
http://forum.xda-developers.com/showthread.php?t=1077414&highlight=motorola+factory+cable
adb
So I am using the correct cable, I believe I have the correct drivers. I've installed the SDK and am using the ADB from the Android platform_tools.
RSD Lite 5.6 recognizes the device as:
Fastboot CDMA_TARGA S
Does that confirm anything (like that I have the correct ADB driver installed) ..
I've tried all the usual adb commands like adb shell, wait-for-device, kill-server/start-server, etc.
I always get
error: device not found
or in the case of adb devices:
I just get an empty set. ARGG! Really frustrated. I can't believe I started all this with a fatfinger on a forever root script edit. I really thought I would be able to adb pull/push the /system/bin/mount_ext3.sh file in a case like this.
Thanks,
Chris
bionic minimal
Does anyone have any recent experience with this bionic_minimal fxz file:
http://forum.xda-developers.com/showthread.php?p=17560174
I wonder if I can flash that and get back?
Thanks,
Chris
I am going to assume you were previously on 902 or 905. You could do SamuraiHL's no dataloss fxz script to 902. Should prevent any data from your internal memory from being wiped: http://www.droidforums.net/forum/mot...ml#post2173723. I believe there used to be a link in there to the original fxz 902 file that prevented your memory from being wiped. Since you can see your phone via RSDLite and not adb.
Btw...i never mentioned to ask but are you booting into AP Fastboot or staying at the splash screen when trying to adb?
Hi,
My GF broke the screen on her Galaxy S i9000 today. Completely black with She would like to get a copy of what's in the internal memory. Initially I thought I'd install CWM and copy it out using ADB. However, ADB does not work. It will intermittently be able to see the device with adb devices, but adb shell fails, and so does adb backup. After trying three different USB cables (two of which I know to bee good) and two different cf-root recoveries (CF-Root-XW_NEE_JVH-v3.2 and CF-Root-XX_OXA_JW4-v4.4-CWM3RFS) I have concluded this is most likely because the USB port on the phone was damaged on the trip to the ground, and is unable to keep a connection. Heimdall kernel flashing succeeded two of three times though, so it is strange. However, it was impossible to connect to the phon with both Kies and as Mass Storage device while it was still booted into Android, so it is most likely the USB port that's the problem.
Anyway, I can see one possible solutions that is likely to succeed:
Is it possibly to, by way of init scipts or similar, to make CWM copy everything from the internal SDcard to the external one, as well as everything on the /data partition?
Have someone already made such/ sa similar script a script, or could anyone possibly be willing to write one?
Note: I can't flash CWM.zips on the phone, I can only flash imagefiles via heimdall (which is like Odin). Is it a all possible? I guess I COULD flash another CWM, come to think of it, by putting it on the sdcard and follwing keyprrss instructions.
Thanks for any help or suggestions in advance, they will be appreciated.
Please put pit files for SM-G800F online... i erased efs file without make a Backup... i cant make and receive calls and i dont have network.... please any solution ??? Can i type my imei manually into phone?
Factory reset then reflash stock firmware via Odin. Should regenerate EFS.
No.. I make it but no successfull
Using the EFS of another device would be illegal as the IMEI goes with it. Are you absolutely sure you performed a factory reset from recovery, wiped cache and reflashed firmware form SamMobile? This worked on a Note 2 the last time I had this problem...
Phone info+ app show me no build date, no product code, no Hardware rev. and show me wrong imei number..... its curios.. i make varies factorys resets, hard resets and i flash via odin stock rom....
EFS PIT ??
Could you post the result of the following command in a terminal on your phone?
Code:
mount | grep efs
In the terminal i put your command... without su and with su .. .. I have busybox installed....
Partition itself seems fine then. The following should just return blank. If not, you need to wipe the partition again.
Code:
su -t ls /efs
Efs
Terminal
Till now the commands gives answer... Till now everything fine my friend?
Your imei is ok, not generic number or empty....
The IMEI should be fine if the command returns non-blank. The IMEI I saw on your previous screenshot looked like that of a demo model, which means it was generate due to the EFS partition being unreadable. If you still cannot connect you may try EFS profressional if you haven't already.(Backup current on backup tab, head over to Samsung Tools tab and in other tools select "Format EFS folder". After this flash firmware file in Odin before booting up again). Otherwise I'm afraid to say you may need to take it to a service center.
I did a tutorial for backup in two ways, search in general threads
Did a little research. Seems Samsung (or carriers) has made IMEI repair impossible for S5 and up(including all variants) without a service box. Seems like a service centre is the only option for now in the absence of a backup. Apologies.
I have the same problem with my S5 SM-G900F, IMEI NULL and i think the EFS partition was deleted without backup, more infos in the screenshots.
I dont know what to do guys, help plz.
zicozack said:
I have the same problem with my S5 SM-G900F, IMEI NULL and i think the EFS partition was deleted without backup, more infos in the screenshots.
I dont know what to do guys, help plz.
Click to expand...
Click to collapse
Again, the only way to repair the EFS on newer Samsung devices is by using a certified Samsung service box, which, unfortunately, costs money. Samsung service centers will have this equipment, but will obviously charge for its usage too. If you manage to get your hands on one via other means, there are plenty of video tutorials around showing how to use it. It should only be a matter of time before a tool is designed for use on a PC, but for now, there is no other option. Sorry for your inconvenience and please ensure you use the correct subforum next time as per XDA rules.
Background
Okay so the glass on my 2013 Moto X broke on September 27th I ordered a new one and while changing it I accidentally broke the digitizer so I disconnected the digitizer and the phone turned on while my digitizer with disconnected then i had no way of turning it off while my digitizer was disconnected the phone started to vibrate every 3 seconds until the battery died... so I was forced to switch over to my Nexus 6 because at the time that was my backup phone because I love the performance of my Moto X.. now a few months later yesterday to be exact my new digitizer arrived and I brought my Moto X back to life powers on and performs just fine
Problem
My wrist twitch to activate camera doesn't work
My dual chop to activate led doesn't work
Whenever I make a phone call or receive a phone call my screen turns off automatically but the phone call works just fine once the phone call has ended my screen does not turn back on I have to reboot the phone to turn on the display again
Phone info
2013 moto x on 5.1.1 stock rom locked bootloader rooted using crashes method with ultra slim root
any help or tip is greatly appreciated
Maybe, but it really depends what's actually wrong. The Moto has a TI MSP430 chip that handles all that 'motion, wave-to-wake, chop-chop' stuff and it's loaded from a /firmware folder or partition (have forgotten at this point). @masterifla figured out which files it was on 4.4.4 & 5.1 that got uploaded to the 430 and wrote a .zip file to change from 4.4.4's "wave to wake" to 5.1 "chop chop" or vice versa. I fixed some little bug in it, and stuck the working .zips up in this post although they may be elsewhere as well: (so :: these zips contain the firmware that actually does the wave-to-wake stuff and can be 'recovery-flashed')
http://forum.xda-developers.com/showpost.php?p=63616790&postcount=17
At least if that works, you'll know that it was the firmware for that chip, and if not, it might actually be the 430 chip(which you can see in the teardown). The post by me and anything by masterifla should be pretty well explained.
Cheers.
but have a locked bootloader I can't flash anything...but you gave hope maybe if I use rsd lite to flash stock I can fix this
BADDINOROX99 said:
but have a locked bootloader I can't flash anything...but you gave hope maybe if I use rsd lite to flash stock I can fix this
Click to expand...
Click to collapse
There still might be a way. I keep trying to have people get this to work, but I'm not sure of the outcome yet, so give it try if you like: Here's some steps:
1) Locked bootloader / no root means mostly that you can't write system, but I'm pretty sure you should be able to temporarily boot into a PC-based copy of twrp. Once in twrp (for one time say) you are root, and you have access to anything on your gizmo. In theory, you should be able to mount system read-write and change something in the file system.
2) Get the correct copy of twrp and adb (from dev forum for this box) and put it on a PC with fastboot in the same folder. To make this easy, called twrp "twrp.img" and call "fastboot" or "mfastboot" fastboot.exe (I am for some reason assuming you've got a PC, not a mac or linux, but the ideas are similar.
3) quick explain of the files in the .zip from above ^^ : 8 files prefixed by MSP that are located when on the moto in /system/etc/firmware. Unzip them and stick them in that same folder.
4) Tricky part : (I think) : reboot into the twrp.img on your PC by getting your device into fastboot / bootloader mode: (so .. volume-up&down&power keys all held down for ~10 seconds perhaps, then if you've gotten it right (it's touchy), you'll be in the bootloader where it has a small tiny text list of stuff like "continue, recovery, etc).
5) you're good with the phone if you've made it here: now on the PC from that folder, type in "fastboot boot twrp.img" and good luck. If it works, your phone will be in TWRP with root access. If not, I don't know another option at the moment.
6) Probably the rest is most easily done from the PC command (or shell) window where the files are. Since your device is in the bootloader and awaiting further instruction, you should be able to use adb to talk to recovery now. so carry on:
7) (get the files from your PC (the MSP prefixed ones) onto the device, so first remount system r/w):
Code:
a) "adb remount" // supposedly should remount system toggling the read attribute to write
b) "adb push msp* /system/etc/firmware/" // copies files to device unless I've got syntax wrong, try one at a time if doesn't work.
c) "adb shell ls -al /system/etc/firmware/" // list all files, and post them back here to see if it even worked.
d) "adb remount" // system partition back to normal ro state.
d) "adb reboot" // moment of truth, a reboot.
8) after things settle post-reboot, check out "wave-to-wake" , camera twist, etc. This works on 4.4.4 or 5.1 (if this other stuff above works).
Note: I could be way off on my idea that rebooting into recovery will give you enough functionality to do this, but I'm not sure what other choices you've got without being able to root. I guess another thing I'm wondering about is why you wouldn't be able to root the phone from recovery regardless of how you booted into it. You still can't unlock bootloader, but I'm not clear on what difference it makes at the moment.
Good luck. It's a "hail mary" pass.
thanks I got my stuff working again ? I screwed up in the file install part freaked out and reflashed stock and rerooted so everything is good now once again thanks
Your current stage : qualcomm hs-usb qdloader 9008 in your network devices ,when you connect your phone.(if not, get your
google to findout how to get here).
Attention Moto G 2nd generation users. Unbrick using SD card dump
Can anybody create the following file from working Moto g(2014). ?.It will save Many devices. Please give a google drive link.
Reference from below Threads.....
http://forum.xda-developers.com/showthread.php?t=2549068
http://forum.xda-developers.com/showthread.php?t=2660566
The following guide is for S3 but it will work for All the Qualcomm based devices. No need to have Linux os to perform this back up.Can be done using the windows.
Insert memory card into working & rooted Moto g and issue the following command using ADB
->adb.exe shell dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920
increase the count if you face any problem. Compress and Upload the debrick.bin in google drive and leave a link.
Explanation:
How to UNBRICK:
Credit goes to these guys in this thread, I thought i was onto something origional, however after doign some searching i found others have figured this out for a different Variant of the S3
What you did:
Bricked downgrading the bootloader after upgrading to the 4.3 bootloader. The 4.3 bootloader appears to blow efuses that stop previous boot loaders from booting. Now your EMMC has non booting garbage on/in it. YAY! not...
What we are doing:
What we will be doing is writing the Partition layout (Partition.mbn) among other things to the SD so the phone will boot from it after it fails to boot from the EMMC. According to my research the CPU is designed to cascaded from one storage device to the other in the event of failure on the first device. This also means if your EMMC is smoked, you could technically run the whole rom and everything from the sd card, or that's my assumption.
What you need:
- A Micro SD card 16GB or larger. this will no work on smaller cards, i tried a 2GB 4 GB and 8GB for the sake of testing and it fails.
- A working Dump that includes the SBL1, SBL2, SBL3, aboot, TZ and RPM from a working device that matches your DEVICE MODLE ie: I747U or I747M If you wanto t create your own dump from a friends device the command in a rooted adb shell would be as follows but not exact depending where you want the dump file to end up being on your sd cards. "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920" That is what I used my my co-workers CM 10.2 rom to get the 4.3 bootloader/debrick dump. NOTE: the device has to be rooted with a working busybox that supports the dd command.
- The ability to write the dump image to the micro sdcard.
If this method works, my hardbricked Moto G 2014 will thank you!
Anyway, thank you so much for your hard work trying to help every user with a bricked Moto G 2014!
Pleaseeeeeeeeee! help in xt1069 to!
Help me too! I have Moto g xt1069.
Tnx
help
ByReverso said:
If this method works, my hardbricked Moto G 2014 will thank you!
Anyway, thank you so much for your hard work trying to help every user with a bricked Moto G 2014!
Click to expand...
Click to collapse
hey guy has to offer me of your moto g2 files. Please mine too this in this state
@lets_do_it,
In Brazil has a group on Facebook with over 1000 (all witch hardbrick) people and we are trying to get the files but it's pretty hard ):
lets_do_it said:
Your current stage : qualcomm hs-usb qdloader 9008 in your network devices ,when you connect your phone.(if not, get your
google to findout how to get here).
Attention Moto G 2nd generation users. Unbrick using SD card dump
Can anybody create the following file from working Moto g(2014). ?.It will save Many devices. Please give a google drive link.
Reference from below Threads.....
http://forum.xda-developers.com/show....php?t=2660566
http://forum.xda-developers.com/show....php?t=2549068
The following guide is for S3 but it will work for All the Qualcomm based devices. No need to have Linux os to perform this back up.Can be done using the windows.
Insert memory card into working & rooted Moto g and issue the following command using ADB
->adb.exe shell dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920
increase the count if you face any problem. Upload the debrick.bin in google drive and leave a link.
Explanation:
How to UNBRICK:
Credit goes to these guys in this thread, I thought i was onto something origional, however after doign some searching i found others have figured this out for a different Variant of the S3
What you did:
Bricked downgrading the bootloader after upgrading to the 4.3 bootloader. The 4.3 bootloader appears to blow efuses that stop previous boot loaders from booting. Now your EMMC has non booting garbage on/in it. YAY! not...
What we are doing:
What we will be doing is writing the Partition layout (Partition.mbn) among other things to the SD so the phone will boot from it after it fails to boot from the EMMC. According to my research the CPU is designed to cascaded from one storage device to the other in the event of failure on the first device. This also means if your EMMC is smoked, you could technically run the whole rom and everything from the sd card, or that's my assumption.
What you need:
- A Micro SD card 16GB or larger. this will no work on smaller cards, i tried a 2GB 4 GB and 8GB for the sake of testing and it fails.
- A working Dump that includes the SBL1, SBL2, SBL3, aboot, TZ and RPM from a working device that matches your DEVICE MODLE ie: I747U or I747M If you wanto t create your own dump from a friends device the command in a rooted adb shell would be as follows but not exact depending where you want the dump file to end up being on your sd cards. "dd if=/dev/block/mmcblk0 of=/storage/sdcard1/debrick.bin bs=1024 count=81920" That is what I used my my co-workers CM 10.2 rom to get the 4.3 bootloader/debrick dump. NOTE: the device has to be rooted with a working busybox that supports the dd command.
- The ability to write the dump image to the micro sdcard.
Click to expand...
Click to collapse
Help
ByReverso said:
If this method works, my hardbricked Moto G 2014 will thank you!
Anyway, thank you so much for your hard work trying to help every user with a bricked Moto G 2014!
Click to expand...
Click to collapse
the links do not work
It days trying to solve this problem, mine is xt1068
thirtytwoob said:
the links do not work
It days trying to solve this problem, mine is xt1068
Click to expand...
Click to collapse
Links for the thread is updated. you can view the reference now
ripizud said:
@lets_do_it,
In Brazil has a group on Facebook with over 1000 (all witch hardbrick) people and we are trying to get the files but it's pretty hard ):
Click to expand...
Click to collapse
If someone creates this image it will be helpful. since it requires basic rooting of the device (busy box installed)
and adb pull and need to compress the image.i got the seperate files like tz,sb1,..etc from another thread but i dont know how to create each partition using mini partition wizard. Because there are around 36 partitions ,cannot perform this manually
Reference links won't work
JeffDrk said:
Reference links won't work
Click to expand...
Click to collapse
click my original post.i can able to access
Good morning friends!!!
This link here from a web site development:
https://github.com/MotorolaMobilityLLC
estou com uma aparelho xt1068
tenho duvida de esse procedimento poderia danificar o aparelho de teste ?
UP my thread is my only hope.. Please can someone link the 1068 files
Could you detail the procedure is to provide the files used my Moto G2 does not start the recovery.
In that format should be the sdcard? (FAT32, NTFS, EXFAT)?
If someone finds out that this solution actually does work, and tests it on a hardbricked device with success:
WALL OF TEXT INCOMING:
I would like to help, but I only have a working XT1072 and my debrick.img would be useless here. But it should work, and you can get technical details by dissasembling recovery.img and checking recovery.fstab But I might make sooner or later an XT1072 debrick.img and place it in a thread with multiple debrick images for multiple images. We could make these from rooted devices running a stable ROM with a specified bootloader version, and gather them listing them in the following format, along with usage instructions:
D_V_B_A_T_debrick.zip
Device Codename
V:Variant
B:Bootloader version
A:Android version
T:TWRP version
Example:
thea_XT1072_48.21_5.1.1_3.0.2-0_debrick.zip with an mmc0blk0.img file inside.
just like this thread http://forum.xda-developers.com/galaxy-s4-verizon/help/help-plz-starting-debrick-img-t3003027
If this does really work, then Moto users won't live in fear anymore. A prosperous, brick-free glorious era awaits...
But it's not guaranteed to work, because Motos have been never recovered from a Lollipop hardbrick and this method surely had to be tested before (or was never tested and we had the solution AT OUR EYES). We need cooperation from everyone, and testers with both bricked and working devices from the same variant will be thanked in the post main page. Once the process is perfected, I will send my own debrick to be the second one in the list Someone please unbrick any Moto and then post the IMG and how did you make it (block size, count)
Please OP read this and make a debrick test thread! My device works OK but anything can happen.
benjausen said:
If someone finds out that this solution actually does work, and tests it on a hardbricked device with success:
WALL OF TEXT INCOMING:
I would like to help, but I only have a working XT1072 and my debrick.img would be useless here. But it should work, and you can get technical details by dissasembling recovery.img and checking recovery.fstab But I might make sooner or later an XT1072 debrick.img and place it in a thread with multiple debrick images for multiple images. We could make these from rooted devices running a stable ROM with a specified bootloader version, and gather them listing them in the following format, along with usage instructions:
D_V_B_A_T_debrick.zip
Device Codename
V:Variant
B:Bootloader version
A:Android version
T:TWRP version
Example:
thea_XT1072_48.21_5.1.1_3.0.2-0_debrick.zip with an mmc0blk0.img file inside.
just like this thread http://forum.xda-developers.com/galaxy-s4-verizon/help/help-plz-starting-debrick-img-t3003027
If this does really work, then Moto users won't live in fear anymore. A prosperous, brick-free glorious era awaits...
But it's not guaranteed to work, because Motos have been never recovered from a Lollipop hardbrick and this method surely had to be tested before (or was never tested and we had the solution AT OUR EYES). We need cooperation from everyone, and testers with both bricked and working devices from the same variant will be thanked in the post main page. Once the process is perfected, I will send my own debrick to be the second one in the list Someone please unbrick any Moto and then post the IMG and how did you make it (block size, count)
Please OP read this and make a debrick test thread! My device works OK but anything can happen.
Click to expand...
Click to collapse
I have the files of all partition gathered from other thread but i don't know ,how to create 36 partition on sd card i mean file system differ for each partition.like FAT,ext4,.Thatswhy i require a debrick image file which has partition information.once it is available i can "dd" the files to each partition.
But can you please post your files ?. Xt1072 files are okay. our devices are bricked because of different partition size from kitkat to lollipop so
your help is required.i can change the partition size later i have the partition table information with me.
http://forum.xda-developers.com/moto-g-2014/help/help-partition-layout-info-dump-xt1068-t3333342
I am available for testing
benjausen said:
If someone finds out that this solution actually does work, and tests it on a hardbricked device with success:
WALL OF TEXT INCOMING:
I would like to help, but I only have a working XT1072 and my debrick.img would be useless here. But it should work, and you can get technical details by dissasembling recovery.img and checking recovery.fstab But I might make sooner or later an XT1072 debrick.img and place it in a thread with multiple debrick images for multiple images. We could make these from rooted devices running a stable ROM with a specified bootloader version, and gather them listing them in the following format, along with usage instructions:
D_V_B_A_T_debrick.zip
Device Codename
V:Variant
B:Bootloader version
A:Android version
T:TWRP version
Example:
thea_XT1072_48.21_5.1.1_3.0.2-0_debrick.zip with an mmc0blk0.img file inside.
just like this thread http://forum.xda-developers.com/galaxy-s4-verizon/help/help-plz-starting-debrick-img-t3003027
If this does really work, then Moto users won't live in fear anymore. A prosperous, brick-free glorious era awaits...
But it's not guaranteed to work, because Motos have been never recovered from a Lollipop hardbrick and this method surely had to be tested before (or was never tested and we had the solution AT OUR EYES). We need cooperation from everyone, and testers with both bricked and working devices from the same variant will be thanked in the post main page. Once the process is perfected, I will send my own debrick to be the second one in the list Someone please unbrick any Moto and then post the IMG and how did you make it (block size, count)
Please OP read this and make a debrick test thread! My device works OK but anything can happen.
Click to expand...
Click to collapse
The model of my cell phone and the XT1078, however he is full brick, if you can find the backup.img the XT1072 I could do a test here in my. I would be very agradesito.
ByReverso said:
If this method works, my hardbricked Moto G 2014 will thank you!
Anyway, thank you so much for your hard work trying to help every user with a bricked Moto G 2014!
Click to expand...
Click to collapse
Please tutorial??
lets_do_it said:
I have the files of all partition gathered from other thread but i don't know ,how to create 36 partition on sd card i mean file system differ for each partition.like FAT,ext4,.Thatswhy i require a debrick image file which has partition information. once it is available i can "dd" the files to each partition.
But can you please post your files ?. Xt1072 files are okay. our devices are bricked because of different partition size from kitkat to lollipop so
your help is required.i can change the partition size later i have the partition table information with me.
http://forum.xda-developers.com/moto-g-2014/help/help-partition-layout-info-dump-xt1068-t3333342
Click to expand...
Click to collapse
I will try to help. I currently cannot post my own files, also I need to know information like the block size for the DD command. Also a document with recovery.fstab will help because I run Windows right now. Android phones use ext4 by default, so use this.
---------- Post added at 03:33 PM ---------- Previous post was at 03:31 PM ----------
eliezer.system said:
The model of my cell phone and the XT1078, however he is full brick, if you can find the backup.img the XT1072 I could do a test here in my. I would be very agradesito.
Click to expand...
Click to collapse
I will try to take a partition dump from my own phone, but I am afraid I will mistype the command and ruin the phone. I will try anyway and when I have time I will post the IMG.