[Request] HAM2 Stock OEMInfo File - Huawei Ascend Mate 2

Hello,
I've been trying to return my CC HAM2 to Huawei Stock HAM2 and according to one user, I need two files; oeminfo partition file and custom.bin from someone with the Huawei Stock HAM2 (not the CC variant) that is rooted. Here are the steps you can use to get these files:
1. oeminfo partition
Connect your device to PC and backup your oeminfo partition with these commands:
Code:
Code:
adb shell su -c "dd if=/dev/block/platform/<device>/by-name/oeminfo of=/sdcard/oeminfo"
adb pull /sdcard/oeminfo oeminfo
adb rm -f /sdcard/oeminfo
Execute them from ADB folder. It's three commands, run them separately. Don't forget to replace <device> with your existing folder.
Now you should get oeminfo file in ADB folder. Check it, if OK, then save it somewhere else.
2. Custom.bin
This file can be located at: /data/custom.bin

medwatt said:
Hello,
I've been trying to return my CC HAM2 to Huawei Stock HAM2 and according to one user, I need two files; oeminfo partition file and custom.bin from someone with the Huawei Stock HAM2 (not the CC variant) that is rooted. Here are the steps you can use to get these files:
1. oeminfo partition
Connect your device to PC and backup your oeminfo partition with these commands:
Code:
Code:
adb shell su -c "dd if=/dev/block/platform//by-name/oeminfo of=/sdcard/oeminfo"
adb pull /sdcard/oeminfo oeminfo
adb rm -f /sdcard/oeminfo
Execute them from ADB folder. It's three commands, run them separately. Don't forget to replace with your existing folder.
Now you should get oeminfo file in ADB folder. Check it, if OK, then save it somewhere else.
2. Custom.bin
This file can be located at: /data/custom.bin
Click to expand...
Click to collapse
I think the OEMInfo Partition (mmcblk0p8, size 67,108,864) contains IMEI and SN info, it is not worth the risk to mess up with them.

Thanks for your reply. I don't really know that much about the internal make up of android devices, so maybe that's why I asked requested that file. I was told by a user [Kostyan_nsk] in one of the threads I created asking how to flash the stock HAM2 OEM over the CC version and the guy said I need the OEMINFO file from someone with a stock phone (not CC). I really had no idea why but in his procedure, getting the OEMINFO file was essential to the process. Now, I wonder how I can get of the CC version !!!!

xordos said:
I think the OEMInfo Partition (mmcblk0p8, size 67,108,864) contains IMEI and SN info, it is not worth the risk to mess up with them.
Click to expand...
Click to collapse
I was replacing whole partition from other device, but my IMEI and SN stayed the same. So it's not in there.
Well, may be in your device its size is 64MB if you are not confused blocks. In mine it's mmcblk0p9 and has 32MB size.

Kostyan_nsk said:
I was replacing whole partition from other device, but my IMEI and SN stayed the same. So it's in there.
Well, may be in your device its size is 64MB if you are not confused blocks. In mine it's mmcblk0p9 and has 32MB size.
Click to expand...
Click to collapse
Its 64MB. Pooffff goes flashing the stock rom !

Let me know about your result.

Kostyan_nsk said:
Let me know about your result.
Click to expand...
Click to collapse
Result ? I don't have the oeminfo file.

xordos said:
I think the OEMInfo Partition (mmcblk0p8, size 67,108,864) contains IMEI and SN info, it is not worth the risk to mess up with them.
Click to expand...
Click to collapse
I always thought it was stored in the phone hardware.

medwatt said:
Result ? I don't have the oeminfo file.
Click to expand...
Click to collapse
Still nobody responded to your request?
Strange. There's no any personal information to be afraid to reveal.

Still kinds of worried because I have seen mixed answered about the OEMInfo partition has sensitive info or not.
My MT2L03 unlocked OEMInfo image:
ls -l : 67108864 Oct 9 00:45 mmcblk0p8.img
md5sum: d9c1a0287bb94b7b0d5d83e0________ mmcblk0p8.img
I have masked the last 8 digit of my md5, if anyone else can confirm the md5sum is same as mine, I will share the image.
Sorry if this looks too much. I just want to be super careful that my phone IMEI/SN will not got flashed to other phone, and maybe lots of phones if it got published.
This is the post that I got scared of:
http://www.modaco.com/topic/362644-is-there-a-way-to-copy-an-officially-unlocked-ics-bootloader/
"The only way to do what you are asking is to use the oeminfo partition from another phone that has unlocked bootloader, and that will make you lose your imei number after installing an update.app."
So, it is possible you may not see any problem right away after flashing, but only found your IMEI lost after an update which maybe months later.
So, anyone can check your vanilla MT2L03 md5sum of the mmcblk0p8.img, please confirm.

Well, and according to this post about successfull backup and restore of IMEI, it seems to be in 'nvme' partition.
And I was not lost my imei after flashing update.app with replaced from other device oeminfo partition.
I'm just curious where was it started from that imei is in oeminfo?
In addition: I have found Board ID, SN, MAC WLAN, MAC Bluetooth, Bootloader unlock code, but IMEI still not found.
I'm starting to think it's stored in hardware and cannot be changed. Seems like it was stored in partition in previous, early devices, but now it's not.

medwatt said:
Hello,
...
1. oeminfo partition
Connect your device to PC and backup your oeminfo partition with these commands:
Code:
Code:
adb shell su -c "dd if=/dev/block/platform/<device>/by-name/oeminfo of=/sdcard/oeminfo"
...
...
Click to expand...
Click to collapse
Code:
C:\Users\User>adb devices
List of devices attached
9cc1722xxxxx device
C:\Users\User>adb shell su -c "dd if=/dev/block/platform/9cc1722xxxxx/by-name/oe
minfo of=/sdcard/oeminfo"
/dev/block/platform/9cc1722xxxxx/by-name/oeminfo: cannot open for read: No such
file or directory
C:\Users\User>
I masked my serial number but that's what I get when I run that.

arcadesdude said:
Code:
I masked my serial number but that's what I get when I run that.[/QUOTE]
The by-device field is a folder name - not your serial number. Its one of the folders in /dev/block/platform/. For example, in my CC variant it is: msm_sdcc.1
It might be the same for your phone. In fact if you have root explorer or some other software just enter /dev/block/platform/<device>/by-name/ and you can copy the oeminfo file without the need for adb. Try it.
Click to expand...
Click to collapse

xordos said:
Still kinds of worried because I have seen mixed answered about the OEMInfo partition has sensitive info or not.
My MT2L03 unlocked OEMInfo image:
ls -l : 67108864 Oct 9 00:45 mmcblk0p8.img
md5sum: d9c1a0287bb94b7b0d5d83e0________ mmcblk0p8.img
I have masked the last 8 digit of my md5, if anyone else can confirm the md5sum is same as mine, I will share the image.
...
Click to expand...
Click to collapse
Used root explorer to copy the files and hashmyfiles to generate the md5:
{
"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"
}
Looks quite different.

By the way, I have found where IMEI is.
So now I can confidently declare that it's not in OEMInfo.

Kostyan_nsk said:
By the way, I have found where IMEI is.
So now I can confidently declare that it's not in OEMInfo.
Click to expand...
Click to collapse
Hey, what phone do you have? I see in the other thread the cc to oem instructions step 1 is get full oem update.app, but I dont think mt2l03 have this.
---------- Post added at 08:06 AM ---------- Previous post was at 07:57 AM ----------
arcadesdude said:
Used root explorer to copy the files and hashmyfiles to generate the md5:
Looks quite different.
Click to expand...
Click to collapse
Can you list the file size as well, I am confused you have oeminfo and p8 different, these two suppose is same thing.

xordos said:
Hey, what phone do you have? I see in the other thread the cc to oem instructions step 1 is get full oem update.app, but I dont think mt2l03 have this.
---------- Post added at 08:06 AM ---------- Previous post was at 07:57 AM ----------
Can you list the file size as well, I am confused you have oeminfo and p8 different, these two suppose is same thing.
Click to expand...
Click to collapse
PHONE:
I have the stock carrier unlocked MT2-L03 from Amazon/Huawei.
SIZE:
12/30/2014 11:48 PM 67,108,864 oeminfo 1 File(s) 67,108,864 bytes
12/30/2014 11:48 PM 67,108,864 mmcblk0p8 1 File(s) 67,108,864 bytes
(64mb)
COMPARED:
I used UltraCompare Lite on the files in binary mode...they are exactly the same except for the names. The contents are identical.
MD5:
I'm not sure why they seemed different before. Maybe a copy error.

arcadesdude said:
PHONE:
I have the stock carrier unlocked MT2-L03 from Amazon/Huawei.
SIZE:
12/30/2014 11:48 PM 67,108,864 oeminfo 1 File(s) 67,108,864 bytes
12/30/2014 11:48 PM 67,108,864 mmcblk0p8 1 File(s) 67,108,864 bytes
(64mb)
COMPARED:
I used UltraCompare Lite on the files in binary mode...they are exactly the same except for the names. The contents are identical.
I'm not sure why they seemed different before. Maybe a copy error.
Click to expand...
Click to collapse
Thanks, actually, Today I tried to fetch the OEM info again, it changes, maybe because one is before update, the newer one is after, but still it is not matching with yours.
819ee97207511c78f1a46dfb________ oeminfo_1231.img
Anyway, read some where that the OEMInfo pretty much is a data storage partition, that it stores different regions/carrier info/settings of the phone. So, how many unique info is stored here, I am not sure, maybe IMEI is not here, but if other MT2L03 image is not same as mine, I am not comfortable to share mine. Sorry.

xordos said:
Hey, what phone do you have? I see in the other thread the cc to oem instructions step 1 is get full oem update.app, but I dont think mt2l03 have this.
Click to expand...
Click to collapse
Well, if there is no full UPDATE.APP for MT2-L03, then the idea of replacing oeminfo is useless.

xordos said:
Thanks, actually, Today I tried to fetch the OEM info again, it changes, maybe because one is before update, the newer one is after, but still it is not matching with yours.
819ee97207511c78f1a46dfb________ oeminfo_1231.img
Anyway, read some where that the OEMInfo pretty much is a data storage partition, that it stores different regions/carrier info/settings of the phone. So, how many unique info is stored here, I am not sure, maybe IMEI is not here, but if other MT2L03 image is not same as mine, I am not comfortable to share mine. Sorry.
Click to expand...
Click to collapse
Yeah I'm not willing either if there is personal info there it's not good to clone that.
Sent from my MT2L03 using Tapatalk

Related

Team Infernal FakeCid AUTOMATIC bootloader unlock

First of all i want to thank captainrewind without his help and his device this wouldnt be possible, i didnt even own the device myself im just planning to buy it and with him offering himself to test everything, well we combined knowledges and made it all you need to do is simple:
Anyone wanting to know how this Started read http://forum.xda-developers.com/showthread.php?t=1984936
mdmower experienced issues with ril(calls and else) and contacts not syncing so i worked with him and we discovered supercid is responsable for this so the only thing you got to do is reverse cid(thats option number 3 on script) and you are ready to go, no need to relock bootloader!!, they are 2 versions of script one with recovery one without its your choice, the recovery one is pretty big 8mb and without only a few kbytes, screenshots below
the one with recovery
{
"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 one without recovery
mdmower said
mdmower said:
I have another script update. The temproot method is no longer used to change the cid after you're unlocked. Those procedures now assume you have superuser installed (root) and are much faster and more reliable.
My package still does not include a recovery image to reduce the size of the download, but I have included a menu option to install recovery - you simply need to download either CWM or TWRP and put recovery.img in the same directory as the script.
Special Note: If you run the script multiple times, be sure to remove mmcblk0p4 and mmcblk0p4.backup from the directory each time. I purposely leave these in case you want to make a backup. mmcblk0p4 corresponds to SuperCID and mmcblk0p4.backup corresponds to VZW__001.
Click to expand...
Click to collapse
Also please note as mdmower said Special Note: If you run the script multiple times, be sure to remove mmcblk0p4 and mmcblk0p4.backup from the directory each time. I purposely leave these in case you want to make a backup. mmcblk0p4 corresponds to SuperCID and mmcblk0p4.backup corresponds to VZW__001.
The script is attached below, script unlocks bootloader and installs a recovery for you, not root but you can find intructions on next post
THANKS:
Bin4ry for temproot method
Grankin01 for the cid base
mdmower for correcting script
Superdave for discovering temp root(forgot to mention before sorry)
The manual way!!!!
DO AN ADB BACKUP BEFORE STARTING AS THIS WILL RESTORE TO FACTORY DEFAULTS!
EVERYTIME WE SAY TYPE IT MEANS TYPING THE CODE AND PRESSING ENTER
SOME USERS ARE HAVING ISSUES TEMPROOTING. IF SO PLEASE DO FACTORY RESET AND/OR REINSTALL THE RUU BEFORE STARTING. Also, verify you are NOT using a USB 3.0 port by looking at the inside of the port itself on your computer. If it's blue, it's USB 3.0 and you need to use a different port.
Requirements:
•A hex editor
•Android sdk(fastboot and adb at least)
•Recommended 50% battery or more and usb debugging on
•Be updated to the latest ruu with sense 4.1 (version 2.17.605.2)
Quick how-to temproot (written by captainrewind):
Read here for some detail (FOR REFERENCE ONLY, all instructions are below): http://forum.xda-developers.com/showthread.php?t=1886460
Download the file http://ul.to/h44f6vni
So lets start:
First, if you haven't already, download and install the HTC drivers.
On your phone, go to Settings -> Developer options, and enable USB debugging.
Next, go to Settings -> Connect to PC and change Default connection type to Disk drive and disable Ask me.
Plug your phone into the computer, and wait until it pops up asking what you want to do with the newly plugged in phone.
Close the pop ups and go press the Start button and type "cmd". It should pop up with "cmd.exe". Right click on it and click Run as Administrator.
Download this file with the fake backup in it.
Once downloaded, unzip it to C:\Root.
Navigate to the folder in the command Prompt by typing
Code:
cd c:\Root\stuff
Now that you're there, type:
Code:
adb devices
If your phone pops up in the list, you're good to go!
Next, type
Code:
adb restore fakebackup.ab
DO NOT click OK to the restore on the device just yet!
Now type:
Code:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done"
(errors will appear, ignore)
Accept the restore on the device, then type:
Code:
adb reboot
(At this time, you are temprooted, and the phone UI will be in an unusable state, with temproot shell.)
After reboot type:
Code:
adb shell
Verify that the prompt is "#" (meaning root) or "$" (meaning normal user). If it's not "#", please start over.
At this point, you can optionally do this ONLY if you want to revert changes:
Code:
rm /data/local.prop
exit
adb reboot
if everything went right proceed to second part
2nd part(written by me)
Obtaining supercid
type
Code:
dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4
Close cmd and start a new one then type
Code:
adb pull /sdcard/mmcblk0p4
Open the file (mmcblk0p4) with your hex editor.
Look for offset 00000210 and you should see VZW__001 with your imei on the right
Change VZW__001 to 11111111 and save the file as mmcblk0p4MOD
Now go back to your command prompt and type
Code:
adb push mmcblk0p4MOD /sdcard/mmcblk0p4MOD
Type
Code:
adb shell
Type
Code:
dd if=/sdcard/mmcblk0p4MOD of=/dev/block/mmcblk0p4
If suceeded close the window and start a new one and type "adb reboot bootloader" then "fastboot oem readcid" and that should show you 11111111
Now, go to htcdev.com website, sign up, login, and select the "Unlock Bootloader" option from their site and follow the instructions, selecting other supported devices from their dropdown menu.
bugs:
If you experience issues with com.android.phone crashing when placing/receiving calls or your contacts refuse to sync, you may need to change your cid back to its origintal state (VZW__001). This is proceure 3 in the script and will not affect your unlock or data (perform a backup just in case though!).
After that you can install a recovery or root the rom following captainrewind post below
Honorable mention goes to superdave for discovering the temproot method by Bin4ry works after the latest RUU.
This is no joke people and it shows what a lot of support from those who came before us, a little persistence to try a combination of things, and collaboration can accomplish.
I made a new friend today as well. NOW BRING ON THE CUSTOM ROMS!
I've now successfully flashed TWRP and SU binary and Superuser.apk. Here's how:
CM Recovery:
See this thread for details on the CWM Recovery.
TWRP:
THANKS TO ANDYBONES FOR THE UPDATED TWRP LINKS AND INSTRUCTIONS!
TWRP Download:
http://dl.dropbox.com/u/26383143/HTC Incredible 4G/TWRP2.2_recovery.img
TWRP Instructions:
Code:
adb reboot bootloader
Once in the bootloader:
Code:
fastboot flash recovery TWRP2.2_recovery.img
Code:
fastboot reboot
Once TWRP is flashed:
Download the Superuser apk and binaries from here:
http://androidsu.com/superuser/
Then, push them to your EXTERNAL SD:
Code:
adb push "Superuser-3.1.3-arm-signed.zip" /sdcard/ext_sd
Then, reboot into recovery:
Code:
adb reboot recovery
From the TWRP Recovery, use the "Install" feature to select and install the zip.
Reboot
YOU ARE NOW ROOTED!
bad ass guys!! i knew somneone out in xda land could figure it out!!
I flipping love you guys
So why don't we have cm10 yet?
Sent from my ADR6410LVW using Xparent Blue Tapatalk 2
now this is f***ing awesome!!
great job guys!
http://www.youtube.com/watch?v=VLnWf1sQkjY&sns=em
Sent from my Nexus 7 using Tapatalk 2
i think we should wait for yall to finish whatever yall are doing before we (especially me) start asking boot questions about how to use this
---------- Post added at 07:04 PM ---------- Previous post was at 06:42 PM ----------
But seriously what does this mean
, and cd to the stuff/ dir inside the zip
So what do you recommend for a hex editor?
brycekerr said:
So what do you recommend for a hex editor?
Click to expand...
Click to collapse
I use this one,
download.cnet.com/HxD-Hex-Editor/3000-2352_4-10891068.html
check out our ViperROM once rooted!
---------- Post added at 07:15 PM ---------- Previous post was at 07:11 PM ----------
Should def do a shout out to
Bin4ry
in the OP.
without that exploit this wouldn't be possible
Perfect, thanks! And that's why I wanted root lol, I ran that on my Rez
Error:
"while is not recognized as an internal/external command"
Is that the error we are supposed to ignore? and also I need a device encryption password to restore, anybody know what it is?
brycekerr said:
So what do you recommend for a hex editor?
Click to expand...
Click to collapse
UltraEdit is a 30-day trial, download here: http://www.ultraedit.com/.
If you've used it before and are outside the 30-days, go OpenSource and use Frhed: http://frhed.sourceforge.net/en/
---------- Post added at 05:22 PM ---------- Previous post was at 05:19 PM ----------
Linch89 said:
i think we should wait for yall to finish whatever yall are doing before we (especially me) start asking boot questions about how to use this
---------- Post added at 07:04 PM ---------- Previous post was at 06:42 PM ----------
But seriously what does this mean
, and cd to the stuff/ dir inside the zip
Click to expand...
Click to collapse
Jose is updating it... it just means after you unzip it and open terminal to CD to the c:\path\of\unzipped\file\stuff\ dir
---------- Post added at 05:28 PM ---------- Previous post was at 05:22 PM ----------
brycekerr said:
Perfect, thanks! And that's why I wanted root lol, I ran that on my Rez
Error:
"while is not recognized as an internal/external command"
Is that the error we are supposed to ignore? and also I need a device encryption password to restore, anybody know what it is?
Click to expand...
Click to collapse
Whoops, sorry that's my mistake... that needs to be run from adb shell. Hang on, Jose is fixing. Encryption password should be blank.
tried from adb shell, get a looping error
"link failed no such file or directory"
brycekerr said:
tried from adb shell, get a looping error
"link failed no such file or directory"
Click to expand...
Click to collapse
You should get that, just ignore it and click restore the backup on the phone and those messages should go away.
Does this void the warranty through the htcdev unlock? Not a big deal just curious
Sent from my Nexus 7 using Tapatalk 2
Works great , nice work guys!
Upon reboot my phone starts to boot into the OS....I can see its connected to the network and stuff in the notification bar, but all I can see is the wallpaper and the screen is completely unresponsive
This is after adb reboot
jamminjon82 said:
Does this void the warranty through the htcdev unlock? Not a big deal just curious
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Yes
brycekerr said:
Upon reboot my phone starts to boot into the OS....I can see its connected to the network and stuff in the notification bar, but all I can see is the wallpaper and the screen is completely unresponsive
This is after adb reboot
Click to expand...
Click to collapse
That is expected, the OP has been updated with that detail.
Edit: NVM
the file has no MOD on the end...should it just read mmcblk0p4?
brycekerr said:
Edit: NVM
the file has no MOD on the end...should it just read mmcblk0p4?
Click to expand...
Click to collapse
you would need to cd to the directory where the MOD file (the one you altered with the hex editor) lives.

[Q] transferring TWRP Nandroids to Mac

Hi,
So I have a bootloader-unlocked and rooted (otherwise stock) AT&T HTC One with the latest TWRP.
When you generate a Nandroid with TWRP it creates ".ext4.win" files. I cannot find any possible way to get these files on to a Mac (iMac w/ OS X 10.8.3 Mountain Lion). I'm guessing it's because of the ".ext4" part -- so they are probably .ext4 Linux-style files that cannot be saved on the Mac's HFS+ file system.
I had hoped that I could just zip up my whole TWRP nandroid backup directory and then transfer the .zip to my Mac. No dice. The zip function of ES File Explorer errors on the ext4.win files. That I find a bit weird since the files are clearly ok on the phone's file system.
Does anyone out there use TWRP and a Mac and have a way of saving their TWRP Nandroids to Mac?
Google's "Android File Transfer" and "adb pull" would work for me on all other kinds of files but not these ".ext4.win" files. Similarly I could not get Bluetooth or Airdroid file transfer to work on those files either.
The only solution I could come up with was to use ES File Explorer to upload the nandroid files to Google Drive. That works but is really slow.
It would be great to save them to my Mac over USB or Wifi.
Any ideas?
thanks,
Matt
p.s.
I suppose this could be an argument to switch to CWM if its nandroid files are Mac-storable. I did find one post on here that seems to indicate this, but I like the touch-GUI of TWRP -- I'd like to continue using it if possible.
ShivaSmith said:
Hi,
So I have a bootloader-unlocked and rooted (otherwise stock) AT&T HTC One with the latest TWRP.
When you generate a Nandroid with TWRP it creates ".ext4.win" files. I cannot find any possible way to get these files on to a Mac (iMac w/ OS X 10.8.3 Mountain Lion). I'm guessing it's because of the ".ext4" part -- so they are probably .ext4 Linux-style files that cannot be saved on the Mac's HFS+ file system.
I had hoped that I could just zip up my whole TWRP nandroid backup directory and then transfer the .zip to my Mac. No dice. The zip function of ES File Explorer errors on the ext4.win files. That I find a bit weird since the files are clearly ok on the phone's file system.
Does anyone out there use TWRP and a Mac and have a way of saving their TWRP Nandroids to Mac?
Google's "Android File Transfer" and "adb pull" would work for me on all other kinds of files but not these ".ext4.win" files. Similarly I could not get Bluetooth or Airdroid file transfer to work on those files either.
The only solution I could come up with was to use ES File Explorer to upload the nandroid files to Google Drive. That works but is really slow.
It would be great to save them to my Mac over USB or Wifi.
Any ideas?
thanks,
Matt
p.s.
I suppose this could be an argument to switch to CWM if its nandroid files are Mac-storable. I did find one post on here that seems to indicate this, but I like the touch-GUI of TWRP -- I'd like to continue using it if possible.
Click to expand...
Click to collapse
This must be something to do with newer TWRP. I mistakenly told you it works fine for me, but in order to try to replicate your problem I made a twrp backup using 2.6.0.1 and like you said I can't copy it to my mac.
I never had issues with this before. I'd say use the older version of twrp if you could find it, but if you're running newer firmware from either the google ediiton conversion or 2.24 then touch won't work in twrp.
It's a shame because I prefer twrp's interface too.
maybe we should alert teamwin about this issue. or whoever built this version of twrp.
---------- Post added at 09:33 AM ---------- Previous post was at 09:28 AM ----------
Here's something odd, I plugged the flashdrive I always use via otg into my mac and am able to copy twrp backups from it to the Mac.
I bet it's an android file transfer problem.
it's an ongoing problem with the new twrp.
so either use OTG or switch to cwm
Hey Gunnyman,
Thanks so much for the independent confirmation of the issue! Much appreciated! Now I know I'm not crazy .
I'd also been speaking with the dev. of AFV (Android File Verifier) because that App also cannot compute .md5 sums on the ext4.win files from the latest TWRP. It appears to be some kind of file permission error:
{
"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"
}
But yet I have root, and the files have read permission, so that's very weird. Ok, I just tried a command suggested by the AFV dev., and the output is very interesting:
Code:
$ adb shell ls -a -l /storage/sdcard0/TWRP/BACKUPS/**********/2013-07-18--13-37-53
-rw-rw-r-- root sdcard_rw 16777216 2013-07-18 14:37 boot.emmc.win
-rw-rw-r-- root sdcard_rw 48 2013-07-18 14:37 boot.emmc.win.md5
-rwSrwSr-- root sdcard_rw 55296 2013-07-18 14:37 cache.ext4.win
-rw-rw-r-- root sdcard_rw 49 2013-07-18 14:37 cache.ext4.win.md5
-rwSrwSr-- root sdcard_rw 1349282304 2013-07-18 14:39 data.ext4.win
-rw-rw-r-- root sdcard_rw 48 2013-07-18 14:39 data.ext4.win.md5
-rw-rw-r-- root sdcard_rw 16776192 2013-07-18 14:39 recovery.emmc.win
-rw-rw-r-- root sdcard_rw 52 2013-07-18 14:39 recovery.emmc.win.md5
-rw-rw-r-- root sdcard_rw 287235 2013-07-18 14:41 recovery.log
-rwSrwSr-- root sdcard_rw 1529744384 2013-07-18 14:41 system.ext4.win
-rw-rw-r-- root sdcard_rw 50 2013-07-18 14:41 system.ext4.win.md5
Look at those funky execute permissions... Regarding the "S" --
Wikipedia indicates: "S or T: setuid/setgid or sticky, but not executable".. not sure why that causes issues tho'.
Additionally, although I was able to transfer my first TWRP 2.6.0.1 nandroid backup to Google Drive using ES File Explorer, the 2nd nandroid I made last night would not transfer! It wouldn't work in either ES File Explorer or in the Google Drive App. That makes me wonder about the stability of the files being produced, but yet Ti Backup can open up the nandroids ok, so I don't think the files are corrupted... just seems like a permission issue
I will see if the OTG route will work for me -- that's a great idea which I hadn't tried yet.
Contacting TWRP sounds like a good idea to me, so I sent a message on their site, and pointed them to this thread, but haven't heard back from them yet. If there is any other better way to let them know -- or if we could PM them on XDA, we should. I'm not sure who to contact.
thanks,
Matt
gunnyman said:
it's an ongoing problem with the new twrp.
so either use OTG or switch to cwm
Click to expand...
Click to collapse
Hey Matt!
Thought I'd respond to you over here (I'll ping you on email later, too ).
I did a real quick search for the "S" bit (didn't know too much about it) and found this: http://www.unix.com/tips-tutorials/19060-unix-file-permissions.html:
The passwd file is writable only by root (Remember, root is special. It can write a file that has no write permissions set). The shadow file, which is where passwords are stored, cannot even be read by ordinary users. But joe wants to change his password. He can do that by running /usr/bin/passwd. Notice those r-s permissions. The passwd program has the suid and sgid bits set. This turns the x's into s's. In octal, it would be 6555. The passwd program is owned by root. When joe runs it, it does not run as "joe". Instead, it runs as it owner which is root. So the passwd program can change joe's password for him. The sgid bit works the same way, except it causes the passwd program to run with the group sys instead of joe's group. The suid and sgid do not get their own position in the ls. When the suid bit is set, ls displays a s rather than a x for the owner execute permission. What if the suid bit is set, but the owner execute bit is off? ls will display a capital S in the case. The sgid bit is displayed in a similiar manner, except that it interacts with the group execute permission. (The set uid concept was invented by Dennis Ritchie as he was developing Unix.)
Click to expand...
Click to collapse
I'm guessing that TWRP is setting the suid but not setting (or removing?) the x (execute permission) bit for some reason (pardon me for not being up-to-date on this issue w/TWRP) and this is leading to a read permission error in my AFV app.
Can you use/try another app to read this file (another file manager like ES File Explorer) and see if it can?
The currently available release of my app is not root-enabled (I have a version that I'm still testing), but this particular file should not require root access.
-SA
Hey SA,
Thanks for the "S" bit research info!
Gunnyman found some great info over in an HTC One International thread regarding PC's. This may make things work Mac. I'm about to try some of the chmod ideas from here:
http://forum.xda-developers.com/showthread.php?t=2357819
Matt
scary alien said:
Hey Matt!
Thought I'd respond to you over here (I'll ping you on email later, too ).
I did a real quick search for the "S" bit (didn't know too much about it) and found this: http://www.unix.com/tips-tutorials/19060-unix-file-permissions.html:
I'm guessing that TWRP is setting the suid but not setting (or removing?) the x (execute permission) bit for some reason (pardon me for not being up-to-date on this issue w/TWRP) and this is leading to a read permission error in my AFV app.
Can you use/try another app to read this file (another file manager like ES File Explorer) and see if it can?
The currently available release of my app is not root-enabled (I have a version that I'm still testing), but this particular file should not require root access.
-SA
Click to expand...
Click to collapse
I can confirm that TWRP 2.6.0.1 did actually restore my bootloader-unlocked, rooted (otherwise stock -- 4.2.1) AT&T HTC One properly...
I had just accidentally rebooted into safe mode and then later when I rebooted normally, my live wallpaper was gone (it was reset to the original wallpaper), and so were some home screen folders and icons. It seems like just booting into safe mode one time did that.
I'm still pretty new to Android -- I assumed that booting into safe mode would be like on a PC -- it shouldn't actually change your system. But apparently it did... which is good to know. Luckily I had a recent Nandroid, and the TWRP restore appears to have worked perfectly and my phone is back to exactly how it was... awesome.
So even tho' there are these weird permission things going on, the restore worked fine (as far as I can tell), which is great to know.
=============================================
And even better, the technique from the following post works on Mac's too!! Yay!! --
http://forum.xda-developers.com/showthread.php?p=43453295
Just did this in Terminal on my Mac:
Code:
$ adb shell
[email protected]:/ $ su
[email protected]:/ # chmod -R 777 /data/media/TWRP
[email protected]:/ # exit
[email protected]:/ $ exit
$ adb pull /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53
pull: building file list...
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/recovery.log -> ./recovery.log
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/system.ext4.win.md5 -> ./system.ext4.win.md5
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/system.ext4.win -> ./system.ext4.win
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/recovery.emmc.win.md5 -> ./recovery.emmc.win.md5
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/recovery.emmc.win -> ./recovery.emmc.win
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/data.ext4.win.md5 -> ./data.ext4.win.md5
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/data.ext4.win -> ./data.ext4.win
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/cache.ext4.win.md5 -> ./cache.ext4.win.md5
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/cache.ext4.win -> ./cache.ext4.win
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/boot.emmc.win.md5 -> ./boot.emmc.win.md5
pull: /storage/sdcard0/TWRP/BACKUPS/............/2013-07-18--13-37-53/boot.emmc.win -> ./boot.emmc.win
11 files pulled. 0 files skipped.
2825 KB/s (2912922874 bytes in 1006.604s)
Nandroid safely stored off-phone on Mac! Mission accomplished .
Matt
I use Root Explorer to set the permissions to "rw_rw_r__" on all of the files in the backup folder, and then you can copy them off to your PC or Mac without any problems.
guyd said:
I use Root Explorer to set the permissions to "rw_rw_r__" on all of the files in the backup folder, and then you can copy them off to your PC or Mac without any problems.
Click to expand...
Click to collapse
Same issue with the protected backup files here! Unfortunately won't let me edit permissions, assume it's cause I'm running the stock Rom. I'm hesitant to flash a new one until I can copy the backup to my pc, otherwise my stock backup might be gone for good!
I actually prefer Cwm but for some reason can't get to work correctly on my One. Backups are made just fine but my file explorer can't seem to find them, so again can't copy to my pc! (they're definitely there as taking up valuable sdcard space!)
Neil
nstirton said:
Same issue with the protected backup files here! Unfortunately won't let me edit permissions, assume it's cause I'm running the stock Rom. I'm hesitant to flash a new one until I can copy the backup to my pc, otherwise my stock backup might be gone for good!
I actually prefer Cwm but for some reason can't get to work correctly on my One. Backups are made just fine but my file explorer can't seem to find them, so again can't copy to my pc! (they're definitely there as taking up valuable sdcard space!)
Click to expand...
Click to collapse
I was able to edit the permissions of the TWRP backup files on the Stock ROM just fine using Root Explorer!
Make sure you navigate to your backup folder via the /data/media/0 path!
You must have root to do it of course.
guyd said:
I was able to edit the permissions of the TWRP backup files on the Stock ROM just fine using Root Explorer!
Make sure you navigate to your backup folder via the /data/media/0 path!
You must have root to do it of course.
Click to expand...
Click to collapse
Thanks for the reply! Odd, I am rooted (confirmed by root checker from the market) but root explorer is telling me I'm not, and so can't amend the files. Am I missing something? Put me out of my misery!
EDIT: After a reset it appears to have worked! Thank you so much for your help!
TWRP needs to avoid puting the problematic S permission on .win files
gunnyman said:
it's an ongoing problem with the new twrp.
so either use OTG or switch to cwm
Click to expand...
Click to collapse
I'm having the same issues, I use the Rsync app to copy my nandroids to my linux box, but the rwSrwSr-- permissions on the win files result in "permission denied" when the app tries to read them. So I've been using the chmod utility of the TWRP 2.6.6.0 recovery itself to change the permissions to 0664, but it's highly annoying having to remember and do that after every backup.
Does anyone know if the TWRP folks have plans to fix the permissions issue and avoid putting the S bit ?
ShivaSmith said:
Hey Gunnyman,
Thanks so much for the independent confirmation of the issue! Much appreciated! Now I know I'm not crazy .
I'd also been speaking with the dev. of AFV (Android File Verifier) because that App also cannot compute .md5 sums on the ext4.win files from the latest TWRP. It appears to be some kind of file permission error:
. . .
Click to expand...
Click to collapse
I can confirm this. I was using Dropsync to auto-backup my backups. They wouldn't upload; shared the log and sync history with the Dropsync developer. He/she confirmed a permission issue; this was validated by moving the files that wouldn't upload to a different directory, where they started syncing correctly. I tried CWM and no such issue exists (even though it backs them up to data/media). I wish I had saw the quoted post below; sounds like the remedy (thanks guyd). I may try it when I get my patience back. I'm all about automation so I wouldn't want to manually do that every time I made a backup. I could probably get it done automatically with Tasker and some shell commands.
guyd said:
I use Root Explorer to set the permissions to "rw_rw_r__" on all of the files in the backup folder, and then you can copy them off to your PC or Mac without any problems.
Click to expand...
Click to collapse
nstirton said:
Same issue with the protected backup files here! Unfortunately won't let me edit permissions, assume it's cause I'm running the stock Rom. I'm hesitant to flash a new one until I can copy the backup to my pc, otherwise my stock backup might be gone for good!
I actually prefer Cwm but for some reason can't get to work correctly on my One. Backups are made just fine but my file explorer can't seem to find them, so again can't copy to my pc! (they're definitely there as taking up valuable sdcard space!)
Neil
Click to expand...
Click to collapse
As stated, it seems to backup to a different directory. For me, the backup folder defaults to data/media (and not data/media/0).
guyd said:
Make sure you navigate to your backup folder via the /data/media/0 path!
Click to expand...
Click to collapse
Thanks, that was the key for me!
I ran into the same problem, noticed the suid permission, but a chmod 0664 just wouldn't fix it. Turned out I cd'ed into TWRP's backup path via /sdcard/TWRP/... and not /data/media/0.
To summarize: in a terminal window I was able to
Code:
su
chmod -R 0664 /data/media/0/TWRP
(reproduced from memory)
and then adb pull the files via the command prompt from my Nexus 4 (same issue here as on the One) to my PC (same issue here as on a Mac).
Thanks again
Alex
As stated, it seems to backup to a different directory. For me, the backup folder defaults to data/media (and not data/media/0).
Click to expand...
Click to collapse
/data/media = Android 4.1.2
/data/media/0 = Android 4.2.2
If you are running 4.2.2 and TWRP still puts the backup in the wrong path, then delete the ".twrps" file in the twrp folder, and that should take care of it.
guyd said:
/data/media = Android 4.1.2
/data/media/0 = Android 4.2.2
If you are running 4.2.2 and TWRP still puts the backup in the wrong path, then delete the ".twrps" file in the twrp folder, and that should take care of it.
Click to expand...
Click to collapse
I was talking about CWM when I said that. TWRP backed up to the correct location but had the file permission issue.
Simba501 said:
I was talking about CWM when I said that. TWRP backed up to the correct location but had the file permission issue.
Click to expand...
Click to collapse
I wonder when they will fix the permissions issue, anyone know? I'll stay with 2.5.0.0 till then.
sordna said:
I wonder when they will fix the permissions issue, anyone know? I'll stay with 2.5.0.0 till then.
Click to expand...
Click to collapse
Hm. I didn't know it was fine on 2.5.0.0.
Sent from my HTC One
Simba501 said:
Hm. I didn't know it was fine on 2.5.0.0
Click to expand...
Click to collapse
If you have the latest touch pad drivers (2.24.401.1 firmware) you may run into touch problems with that older version of TWRP.
guyd said:
I use Root Explorer to set the permissions to "rw_rw_r__" on all of the files in the backup folder, and then you can copy them off to your PC or Mac without any problems.
Click to expand...
Click to collapse
It works! But do we need to revert the permissions of the files when restoring? Sorry, n00bs here. ;p

[IMPORTANT] How To Do EFS Backup And Restore For GT-I8552

[IMPORTANT] HOW TO DO EFS BACKUP AND RESTORE FOR GT-I8552​
I Got PM Very Long Ago For Way To Backup Of "EFS" But In Last Two Weeks I Started Getting Request Again So Here Is The Simple Way I Wanna Share "How To Backup "EFS" For GT-I8552
As There Is No CWM For Our Device That Supports "EFS" Backup And Also Third Party Apps Ain't Working Now What To Do
So Here We Go Then :-
Q :- What is "EFS" ?
A :- "EFS" Folder Is The Very Sensitive System Folder That Contains Phone-Specific Information Such As The IMEI, Wireless Devices MAC Addresses, Product Code, And Much More. If This Thing Not Handled Properly, Can Turn Your Device Completely Useless As It Will No Longer Be Recognized By Your Carrier.
Problem Is, Flashing Custom ROMs Sometime Can Corrupt Contains Within "EFS" Folder. That’s Why Backing Up "EFS" Folder Is Very Important If You Love To Flash New ROM.
NOTE :- ROOT IS REQUIRED..!!
INSTRUCTIONS :-
EFS BACKUP
1. Download Android Terminal Emulator Or Download ROM Toolbox Pro Or ROM Toolbox Lite.
2. Open Terminal Emulator Or Terminal Emulator In ROM Toolbox App.
3. Use This Code To Backup "EFS"
Code:
su
dd if=/dev/block/mmcblk0p16 of=/sdcard/efs.img
And hit Enter In Keyboard..
4. You Will Get efs.img In Your SDCard, Copy It To PC Or Upload On Storage Sites Like 4shared.com , Mediafire.com etc
EFS RESTORE
1. Download Android Terminal Emulator Or Download ROM Toolbox Pro Or ROM Toolbox Lite.
2. Open Terminal Emulator Or Terminal Emulator In ROM Toolbox App.
3. Use This Code To Restore "EFS"
Code:
su
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p16
And hit Enter In Keyboard..
4. Guess What You Restored Your "EFS"
Please Hit "THANKS" or "DONATE" To Support.
bro did u try restoring ? r u sure it restore successfully?
tonyjs007 said:
bro did u try restoring ? r u sure it restore successfully?
Click to expand...
Click to collapse
Yes buddy it will restore u need root access for that thats all :good:
I already flashed jasp hd Rom before backing up efs partition now what should I do
ZANKRUT.DOSHI said:
I already flashed jasp hd Rom before backing up efs partition now what should I do
Click to expand...
Click to collapse
Np u can backup now efs.img just in case
We have to put backup of efs (.img file in internal storage or external while restoring it?? :|
Sent from my GT-I8552 using XDA Premium 4 mobile app
Jaspreet_Singh said:
Yes buddy it will restore u need root access for that thats all :good:
Click to expand...
Click to collapse
Bro did u restore it by this way? And can u tell me which information stored on mmcblk0p3 ?
Sent from my GT-I8552 using Tapatalk
kinchit1495 said:
We have to put backup of efs (.img file in internal storage or external while restoring it?? :|
Sent from my GT-I8552 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
internal as above command is for internal only
coolkoushik07 said:
Bro did u restore it by this way? And can u tell me which information stored on mmcblk0p3 ?
Sent from my GT-I8552 using Tapatalk
Click to expand...
Click to collapse
yes its working and p3 is for modem for our device..
Jaspreet_Singh said:
internal as above command is for internal only
yes its working and p3 is for modem for our device..
Click to expand...
Click to collapse
Ur given command is wrong. There is no sdcard directory, it would be sdcard0 or extSdCard. By the way can u tell me what is the work of bs command. Somewhere i saw people use bs=4096 while using dd command. Can u please explain it?
{
"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"
}
Sent from my GT-I8552 using Tapatalk
---------- Post added at 08:42 PM ---------- Previous post was at 07:53 PM ----------
Edit : my bad. Ur code is working too. I did a mistake by /storage/sdcard/ so it gave error. So ignore that part. But if u can please explain bs parameter.
Sent from my GT-I8552 using Tapatalk
I think it ws wrong it should be sdcard0
Sent from my GT-I8552 using XDA Premium 4 mobile app
kinchit1495 said:
I think it ws wrong it should be sdcard0
Sent from my GT-I8552 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope. mine works fine, the output should be efs.img
I think bs stands for block size. But can anyone explain what it does?
Sent from my GT-I8552 using Tapatalk
thnxs bro for great in gt-i8552
Gt-i8552 rocksss!!!
coolkoushik07 said:
Ur given command is wrong. There is no sdcard directory, it would be sdcard0 or extSdCard. By the way can u tell me what is the work of bs command. Somewhere i saw people use bs=4096 while using dd command. Can u please explain it?
Sent from my GT-I8552 using Tapatalk
---------- Post added at 08:42 PM ---------- Previous post was at 07:53 PM ----------
Edit : my bad. Ur code is working too. I did a mistake by /storage/sdcard/ so it gave error. So ignore that part. But if u can please explain bs parameter.
Sent from my GT-I8552 using Tapatalk
Click to expand...
Click to collapse
The /sdcard/ *should* be universal on many samsung devices (at least I know it IS like that on the Galaxy Ace and on the Galaxy Win, i8550L that I own).
Regarding the bs operand of the dd command, in this case you don't need it, as you're acting directly over the EFS partition. In the use of this command the bs operand is used for when you're working with a whole disk.
Technical stuff below:
For example, if you don't have the precise /dev/block/mmcblk0pXXX of a partition (taking in consideration that /dev/block/mmcblk0 is the disk you want to read from), you can use dd in this way:
Code:
dd if=/dev/block/mmcblk0 bs=4096 of=/sdcard/kernel.img
In the example, we're backing up the Kernel part of the phone (note that this is not real information, just an example, so don't blame me if you try to dump that command back in the phone assuming things you don't know xD), as you may (or may not) know, a disk is comprised of many blocks, you can google about that later it's quite late and don't wanna go on too deep so i'll try to be brief; if your disk is 512 mb in size, probably the first 32MB would be for boot, kernel, recovery, modem and NVRAM (not to be confused with modem), these 32 MB might be distributed this way:
1-1024MB Bootloader
1024-6144 Kernel+Recovery
6144-18432 Modem
18432-32768 NVRAM
and so on
Long story short, don't mess with DD
Backing Up EFS Partition
Dear Jaspreet,
Myself and CoolKoushik07 tested this procedure long before. However this is not working solution. This is due to the natture of the EFS filesystem.
Please go through my Post # 39,40,41,42,43,44.
http://forum.xda-developers.com/showthread.php?t=2541198&page=5
Please correct me if I am wrong.
Regards
Arinio said:
Dear Jaspreet,
Myself and CoolKoushik07 tested this procedure long before. However this is not working solution. This is due to the natture of the EFS filesystem.
Please go through my Post # 39,40,41,42,43,44.
http://forum.xda-developers.com/showthread.php?t=2541198&page=5
Please correct me if I am wrong.
Regards
Click to expand...
Click to collapse
Check ur command "dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img"
and mine "dd if=/dev/block/mmcblk0p16 of=/sdcard/efs.img"
Two mistakes ? first is our mounting point for efs is mmcblk0p16 and there is no storage "of=/storage/extSdCard/efs.img" it shud be either to sdcard directly or of=/extSdCard/efs.img
Jaspreet_Singh said:
Check ur command "dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img"
and mine "dd if=/dev/block/mmcblk0p16 of=/sdcard/efs.img"
Two mistakes ? first is our mounting point for efs is mmcblk0p16 and there is no storage "of=/storage/extSdCard/efs.img" it shud be either to sdcard directly or of=/extSdCard/efs.img
Click to expand...
Click to collapse
Just a lil correction.. /storage/extSdCard/ is not wrong directory..
Sent from my GT-I8552 using Tapatalk
Backing Up EFS Partition
Dear Jaspreet,
Please check my Post #43.
Regards
Jaspreet_Singh said:
[IMPORTANT] HOW TO DO EFS BACKUP AND RESTORE FOR GT-I8552​
Click to expand...
Click to collapse
hello @Jaspreet_Singh
Im forget to make a backup by my efs folder I8552 again after formated my PC.
Now its empyt cause i had troubles flashing test by custom rom
Important
Except the stock lockscreen and stock setupwizard inicial everything works even empty folder cause I managed to recreate the mac adress, retrieve the IMEI
3G signal ok
calls Ok
IMEI ok
IP/Wi fi ok
Is it something can u do , like send files folders attachment and i using sdk put my mac adress, ip and imei to restore files?
tks
@mjraogr....
Add facebook.
https://m.facebook.com/GlaMsP?ref=bookmark
I also had the same problem, I was looking for solutions to this problem and in one of these search found an EFS file from another machine and tried their luck to restore my folder ..
Following the steps in this link posted by @manojkumar8552 my work out and now is working perfectly.
Download these files, extract the desktop.
https://drive.google.com/file/d/0B6t2vRswL0dHVXRKYXZncGd1WVU/view?usp=sharing
1 - run the Backup_EFS ...
2 - Once completed Backup your EFS.img, rename such as EFS MY or something.
3 - Inside the folder contains another file (efs Restore.img) change the name to EFS.img.
4 - Run the Restore_EFS ...
5 - Restart the device ...
6 - Enter the ROOT folder with Explorer, find the EFS / Factoryapp folder, edit the file (factorymode) will contain OFF switch to ON all upper case, reset the unit ....
Good luck ... these steps have worked in the mine, hope it helps ...
NOT TO THANK !!

[TOOL][LINUX] mmcblk0 Extractor (v1.0.1 - 3/16/16)

Disclaimer: I am not responsible for anything bad that may occur from the use of this tool, but I will take all the credit you can give me if it works for you
{
"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 tool in intended to extract the full disk image from your Android device (mmcblk0). Once extracted, it allows you to open the image in testdisk to extract individual partitions.
Source
Commits/Changes
XDA:DevDB Information
mmcblk0 Extractor, Tool/Utility for the Chef Central
Contributors
SuperR.
Version Information
Status: Stable
Created 2016-02-02
Last Updated 2016-03-16
Usage:
In your terminal, type the following where "/home/user/extractor/" is the directory where the tool lives:
Code:
cd /home/user/extractor/
./extract
NOTE: the above code is 2 separate commands and requires ENTER to be pressed after each command
OR
Double-click the extract file and choose "Run in Terminal" if your OS supports it.
reserved2
Awesome.
Testing it
I'm not sure mmcblk0 is a full disk image. And once you have it, what do you do with it?
jayvl said:
I'm not sure mmcblk0 is a full disk image. And once you have it, what do you do with it?
Click to expand...
Click to collapse
I am sure. And the OP says what you can do with it.
SuperR. said:
I am sure. And the OP says what you can do with it.
Click to expand...
Click to collapse
What about hidden sectors? the partition table? i.e. stuff that is not inside the supervolume but still occupies NAND memory? For example using MTK droid tools, or just browsing an OEM firmware folder, I can see more data than that listed in the mmcnlk0 partitions.
jayvl said:
What about hidden sectors? the partition table? i.e. stuff that is not inside the supervolume but still occupies NAND memory? For example using MTK droid tools, or just browsing an OEM firmware folder, I can see more data than that listed in the mmcnlk0 partitions.
Click to expand...
Click to collapse
This tool does exactly what it says. Nothing more, nothing less. If it is useful for you feel free to use it. If not I won't have hurt feelings
My point is that mmcblk0 is not the same as a "full disk image" because it does not include every sector on the NAND. So it does not do exactly what it says.
jayvl said:
My point is that mmcblk0 is not the same as a "full disk image" because it does not include every sector on the NAND. So it does not do exactly what it says.
Click to expand...
Click to collapse
Ok, you win
So this will work exactly how?
It dd the partition to internal storage? Then pulls the file from storage. Little confused. If so you might want to add that you'll need a x.xxGB space
The tool looks interesting though
LastStandingDroid said:
So this will work exactly how?
It dd the partition to internal storage? Then pulls the file from storage.
Click to expand...
Click to collapse
Correct. The point was to get aboot, boot, modems, system, recovery ect.. All in one pull.
Sent from my N9515 using Tapatalk
LastStandingDroid said:
So this will work exactly how?
It dd the partition to internal storage? Then pulls the file from storage. Little confused. If so you might want to add that you'll need a x.xxGB space
The tool looks interesting though
Click to expand...
Click to collapse
In addition to what @bcrichster said, if you choose the custom recovery booted option it does not pull to sdcard first. It adb pulls directly from device to pc. If you choose the Android booted option, it uses dd to sdcard, then adb pull to pc.
edit: Just pushed an update adding info about space requirements to the Android booted option
Thank you @SuperR. your contribution is appreciated as always man
Extra help pls.
I downloaded your zip, and on unzipping, found 2 files and 3 directories.
06/03/2016 01:17 PM <DIR> .
06/03/2016 01:17 PM <DIR> ..
03/16/2016 03:51 PM 5,239 extract
03/16/2016 03:52 PM 496 README.md
06/03/2016 01:17 PM <DIR> tools
2 File(s) 5,735 bytes
3 Dir(s) 115,831,672,832 bytes free
I cannot execute the ./extract command that you instructed. I am running Window7. Please give me a pointer, thanks.
forever_naive said:
I downloaded your zip, and on unzipping, found 2 files and 3 directories.
06/03/2016 01:17 PM <DIR> .
06/03/2016 01:17 PM <DIR> ..
03/16/2016 03:51 PM 5,239 extract
03/16/2016 03:52 PM 496 README.md
06/03/2016 01:17 PM <DIR> tools
2 File(s) 5,735 bytes
3 Dir(s) 115,831,672,832 bytes free
I cannot execute the ./extract command that you instructed. I am running Window7. Please give me a pointer, thanks.
Click to expand...
Click to collapse
I think you missed the [LINUX] in the thread title.....
forever_naive said:
I downloaded your zip, and on unzipping, found 2 files and 3 directories.
06/03/2016 01:17 PM <DIR> .
06/03/2016 01:17 PM <DIR> ..
03/16/2016 03:51 PM 5,239 extract
03/16/2016 03:52 PM 496 README.md
06/03/2016 01:17 PM <DIR> tools
2 File(s) 5,735 bytes
3 Dir(s) 115,831,672,832 bytes free
I cannot execute the ./extract command that you instructed. I am running Window7. Please give me a pointer, thanks.
Click to expand...
Click to collapse
In Windows a .exe extension stands for executable (code is hard coded into the binary). That's why you can just double click on windows os and a .exe will self execute (also why you get tons of viruses if you don't know what your doing ).
In Linux os when you put a ./ in front of shell script or binary and depending if it already has the correct permissions coded in or it's intended for the end user to do this you chmod a+x (0755-77) and that's basically the equivalent of being on windows and double clicking a .exe
@SuperR.
Wait a second...
This is in your sources:
Code:
$adb shell su -C "dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img bs=64k"
Think about this for a second. If you have a 32GB device, and /sdcard is on the INTERNAL STORAGE, than how do you put a 32GB file on a 32GB device that's not empty? You're going to run out of storage, right? Am I just crazy or what?
Lightn1ng said:
@SuperR.
Wait a second...
This is in your sources:
Code:
$adb shell su -C "dd if=/dev/block/mmcblk0 of=/sdcard/mmcblk0.img bs=64k"
Think about this for a second. If you have a 32GB device, and /sdcard is on the INTERNAL STORAGE, than how do you put a 32GB file on a 32GB device that's not empty? You're going to run out of storage, right? Am I just crazy or what?
Click to expand...
Click to collapse
There is a warning to be sure you have enough space. Alternatively you can use the custom recovery option and transfer the data directly to your pc bypassing the space requirements on your device.
SuperR. said:
There is a warning to be sure you have enough space. Alternatively you can use the custom recovery option and transfer the data directly to your pc bypassing the space requirements on your device.
Click to expand...
Click to collapse
Is mmcblk0 the same size as the device storage? (e.g. a 16gb phone would have a 16gb mmcblk0.img)?

Nubia z7 nx506j qcn backup

Greetings to everyone here.
I have a Nubia Z7 NX506j and tried to flash it with nubia tool. The flash completed successfully but I lost both my IMEIs. Unfortunately I didn't know that nubia tool keeps a QCN backup and coincidentally formatted my pc. I found a guide about how to hex edit a QCN backup and insert both IMEIs but only for Z7 mini and Z7 max. Can someone please post a working QCN backup of a NX506J and I will make sure to erase the previous IMEIs and insert mine. I will also make sure to post a guide on how I restored it if someone is kind enough to share it.
Thank you!
EDIT: Managed to fix it with the precious help of www.androidbrick.com
Guide coming soon!
Ok, so here goes:
1) First of all you need a qcn backup from a working phone of the same model. I had the luck to ask the owner of www.androidbrick.com to share with me one.
2) You need a hex editor to open the qcn backup
3) Based on these two guides http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/ and http://4pda.ru/forum/index.php?showtopic=596441&st=8180#entry40033587 and adapting them to the qcn i had in my hands, I deleted the IMEIs and MEID from the backup and inserted the ones printed in my phone box
4) Because the IMEIs and MEID on my phone were not "0" but "NULL" i couldn't restore the modified QCN backup, and had to first delete the partitions that hold this kind of information. Based on this guide http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/ i found the partitions (modemst1, modemst2 and fsg) according to the partition table on our device (mmcblk0p10, mmcblk0p11 and mmcblk0p20) accordingly and deleted them with the dd commands found on the above guide (I had to first root the device in order to do that).
5) After i deleted I could successfully restore the QCN backup using QPST (more info on the guide above)
6) Reboot, and voila! The IMEIs and MEID have been restored successfully and phones, calls and mobile data working again!
tassos_chry said:
Ok, so here goes:
1) First of all you need a qcn backup from a working phone of the same model. I had the luck to ask the owner of www.androidbrick.com to share with me one.
2) You need a hex editor to open the qcn backup
3) Based on these two guides http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/ and http://4pda.ru/forum/index.php?showtopic=596441&st=8180#entry40033587 and adapting them to the qcn i had in my hands, I deleted the IMEIs and MEID from the backup and inserted the ones printed in my phone box
4) Because the IMEIs and MEID on my phone were not "0" but "NULL" i couldn't restore the modified QCN backup, and had to first delete the partitions that hold this kind of information. Based on this guide http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/ i found the partitions (modemst1, modemst2 and fsg) according to the partition table on our device (mmcblk0p10, mmcblk0p11 and mmcblk0p20) accordingly and deleted them with the dd commands found on the above guide (I had to first root the device in order to do that).
5) After i deleted I could successfully restore the QCN backup using QPST (more info on the guide above)
6) Reboot, and voila! The IMEIs and MEID have been restored successfully and phones, calls and mobile data working again!
Click to expand...
Click to collapse
My IMEIs are "NULL" so I have to follow your guide.
Can you please tell me the commands for the command window?
This isn't working:
ls -al /dev/block/platform/soc/624000.ufshc/by-name
IceTea7 said:
My IMEIs are "NULL" so I have to follow your guide.
Can you please tell me the commands for the command window?
This isn't working:
ls -al /dev/block/platform/soc/624000.ufshc/by-name
Click to expand...
Click to collapse
Type "ls -al /dev/block/platform/" and according to what appears on the terminal continue to that path until you find the partition table of your device
Sent from my Nexus 5X using Tapatalk
tassos_chry said:
Type "ls -al /dev/block/platform/" and according to what appears on the terminal continue to that path until you find the partition table of your device
Click to expand...
Click to collapse
If I type "ls -al /dev/block/platform/"it shows the following result:
drwxr-xr-x root root 1970-01-08 03:04 msm_sdcc.1
But I don't know what to do next.
If I add soc or the other things of that line the result is that there is no such file.
Then you should type "ls -al /dev/block/platform/msm_sdcc.1" and continue accordingly. But if you lack basic terminal knowledge I highly suggest that you shouldn't go on as you could really mess up your device
Sent from my Nexus 5X using Tapatalk
Yes, I lack of basic knowledge but as long as I don't delete anything, I can't do any damage, right?
But that's the point of the tutorial. To delete the partitions needed in order for your IMEIs to become "0". If you by accident delete the wrong partition, the device could possibly never power on again
Sent from my Nexus 5X using Tapatalk
First I have to find the partitions.
The tutorial is pretty clear to me, so I think I will delete the right things.
---------- Post added at 01:37 PM ---------- Previous post was at 01:23 PM ----------
Just to make things clear.
This is my current situation.
{
"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"
}
IMEI and MEID are NULL but they need to be 0, right?
IceTea7 said:
First I have to find the partitions.
The tutorial is pretty clear to me, so I think I will delete the right things.
---------- Post added at 01:37 PM ---------- Previous post was at 01:23 PM ----------
Just to make things clear.
This is my current situation.
IMEI and MEID are NULL but they need to be 0, right?
Click to expand...
Click to collapse
Yes that's right, I just realized I made a typo in my previous post
I have found the lines and have followed the guide but my Z7 still shows null instead of 0.
I have tried it a second time but no change.
Still null instead of 0.
tassos_chry said:
Yes that's right, I just realized I made a typo in my previous post
Click to expand...
Click to collapse
I'm still not able to set my Z7 into DIAG-Mode. Do yu have any advice for me?
Drivers should be installed correctly.
I have no clue why it's not working.
IceTea7 said:
I'm still not able to set my Z7 into DIAG-Mode. Do yu have any advice for me?
Drivers should be installed correctly.
I have no clue why it's not working.
Click to expand...
Click to collapse
I'm pretty sure the command I told you was right, so I guess it's a driver issue.
What OS are you using? Have you disabled driver signature enforcement, if on Windows 8.1 or 10? If neither of the above help try on another computer with driver signature enforcement disabled
Sent from my Nexus 5X using Tapatalk
tassos_chry said:
I'm pretty sure the command I told you was right, so I guess it's a driver issue.
What OS are you using? Have you disabled driver signature enforcement, if on Windows 8.1 or 10? If neither of the above help try on another computer with driver signature enforcement disabled
Click to expand...
Click to collapse
I'm using Windows 10.
Disabling driver signature is a good hint. I will see if I have disabled it.
tassos_chry said:
I'm pretty sure the command I told you was right, so I guess it's a driver issue.
What OS are you using? Have you disabled driver signature enforcement, if on Windows 8.1 or 10? If neither of the above help try on another computer with driver signature enforcement disabled
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Now I have been finally able to set my Z7 into DIAG mode mode but the QPST tool still doesn't recognize my phone.
Hi, I have the same problem with my nx506j, none of the nubia tools will recover my bricked z7 Max. Could you share the qcn file you received so that I can try your guide?
Many thanks
Ade
Hi .please if anyone can help me with a qcn file backup for a nubia z7. i'l be much obliged Thank you
tassos_chry said:
Ok, so here goes:
1) First of all you need a qcn backup from a working phone of the same model. I had the luck to ask the owner of www.androidbrick.com to share with me one.
2) You need a hex editor to open the qcn backup
3) Based on these two guides http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/ and http://4pda.ru/forum/index.php?showtopic=596441&st=8180#entry40033587 and adapting them to the qcn i had in my hands, I deleted the IMEIs and MEID from the backup and inserted the ones printed in my phone box
4) Because the IMEIs and MEID on my phone were not "0" but "NULL" i couldn't restore the modified QCN backup, and had to first delete the partitions that hold this kind of information. Based on this guide http://www.androidbrick.com/ultimate-guide-qualcomm-snapdragon-imei-baseband-repair-fix-part-2/ i found the partitions (modemst1, modemst2 and fsg) according to the partition table on our device (mmcblk0p10, mmcblk0p11 and mmcblk0p20) accordingly and deleted them with the dd commands found on the above guide (I had to first root the device in order to do that).
5) After i deleted I could successfully restore the QCN backup using QPST (more info on the guide above)
6) Reboot, and voila! The IMEIs and MEID have been restored successfully and phones, calls and mobile data working again!
Click to expand...
Click to collapse
Hello,
I know this is an old thread, I have the same the problem as you but my device is Z7 mini, can anyone help to have the qcn file of this model so that I can restore my EMEI. Thanks.
isbou said:
Hello,
I know this is an old thread, I have the same the problem as you but my device is Z7 mini, can anyone help to have the qcn file of this model so that I can restore my EMEI. Thanks.
Click to expand...
Click to collapse
Sorry do not have anymore qcn of these phones. Perhaps you can contact androidbrick.com

Categories

Resources