I flash "mmcblk0p7" partition by mistake.
May anyone use this code to help me recover:crying:
Code:
adb shell
su
dd if=/dev/block/mmcblk0p7 of=/sdcard/mmcblk0p7
I could get you an edited copy but you would need to insert your IMEI and your providers ID (ORANG001, TMOB etc, etc)
I am unsure it would work, possibly with SIMLOCK and unlock and related codes.
Do you know how you will have to flash the image as well?
Bashing away at my HTC Desire C
Related
First things first, I did NOT write this; however I am reposting this here because I think it's extremely important everyone do this. Find OP here, guide was originally written by Candanga. Please hit thanks on his post and show him love for the write up.
-----------------------------------------------------------------------------------
I’ve compiled a quick guide to instruct how to make a copy of the /efs folder. I’ve found in many threads suggestions about backing up this folder but the methods itself are very general. Most of the times they suggest to “root and copy the folder” with Root Explorer or similar, but usually it’s not that easy or it just doesn't work for everyone (my case).
This guide ASUMES you have read this Excellent Guide by Darkstrikerfirst:
H E R E <-- Make sure to read the ADB Guide.
I recommend doing this with a Mobile just taken out of the box or with any Official ROM of its Service Provider. If you have already Flashed your phone with another ROM but its working fine, then you can use that /efs also.
Why the /efs folder?
This is a very sensitive system folder that contains Phone-specific information such as the IMEI (encrypted in the nv_data.bin), wireless devices MAC addresses, product code (also in the nv_data.bin), and much more. Often users trying to change product codes or trying to unlock the mobile will end up corrupting data in this location.
Why back it up?
Well, let’s resume it saying that backing-up this little folder will keep you away from Samsung service centers.
***WARNING: I take no responsibility to any damage caused by the methods cited and/or written here. Their sole purpose is to back-up data and not to alter in any way the integrity of the original files of the mobile***
Please don’t ask how to recover your IMEI if you have previously messed your SGS without backing up this folder. I’m not familiar with such methods plus it is UNRELATED to this thread.
What you will need:
Rooted SGS to get permissions as a SU (Super User) and perform the backup
I would suggest learning a little about the terminal commands used (in case you are not familiar with them), as it’s better to know what you are doing rather than typing strings like a little chimp without knowing what they are; if you are a little lazy, then you have a good chance bricking your mobile.<- Busybox Commands(or Google them)
Terminal Emulator by Jack Palevich (available from the market) <-Terminal Emulator or use ADB which is included in the SDK Development Tools
--------------------------------------
Backup commands
--------------------------------------
Depending on the type of root, you might have to use “busybox” at the beginning of the sting or just the string:
The standard prompt of terminal (adb) is a $ sign. Once you enter “SU” it will become a # Sign.
***NOTE: Make sure to keep an eye on the screen of your SGS during this process, because it will request SU permissions; else, you will get an error (just if it’s the first time). In Terminal Emulator you will need to reset the app after granting permissions cause it usually freezes***
*Remember: to use ADB you need to enable USB DEBUGGING under Applications/Development in your SGS. Once you are finished with the files, you need to turn it off so you can get the files.
Code:
su
tar zcvf /sdcard/efs-backup.tar.gz /efs or
busybox tar zcvf /sdcard/efs-backup.tar.gz /efs
After this, you will end up with the file efs-backup.tar.gz in your INTERNAL SDCARD, which is a “tarball” or a ZIP of the /efs folder. That file is your backup. You can expand it with Winrar.
In another forum I also saw a recommendation to back up the st13 under /dev/block which can support greatly to recoveryour IMEI in case of a screw-up:
Code:
su
cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img or
busybox cat /dev/block/stl3 > /sdcard/efs_dev-block-stl3.img
Same thing, the target is the INTERNAL SDCARD, so go ahead and copy the file.
----------------------------
nv_data.bin - Restore
----------------------------
In case you screwed your IMEI by playing with the nv_data.bin and you are experiencing issues like:
Fake IMEI (usually 004999010640000)
Unable to download apps from the market
Unable to unlock your SIM card using your PIN
Weird apps are downloading automatically from the market
Blinking SIM card icon on the top tray… ETC
You may want to upload your fresh copy of this file back to the phone. Use this commands:
(thanks to Methyldioxide method to recover the product code http://forum.xda-developers.com/showthread.php?t=780509 )
Copy the file from your backup (efs-backup.tar.gz) and paste it in the INTERNAL SDCARD:
Code:
cp /sdcard/nv_data.bin /efs/nv_data.bin
rm -rf /efs/nv_data.bin.md5
Reboot your SGS
The md5 hash/signature is removed (rm) as the system will generate a new one.
**Most likely your SIM code won’t work after this and you won’t be able to log into the phone**
Pop off your SIM card, boot your SGS and execute the following commands to change ownership of the file under ADB or Terminal as well:
Code:
su
busybox chown 1001:1001 /efs/nv_data.bin or
chown 1001:1001 /efs/nv_data.bin
Hope this can help anyone with doubts. Cheers!
I use SGS Toolbox to back up my efs; is that sufficient?
It's on the market for less than $2, and has a ton of other features so well worth the money regardless.
Sent from my rough sketch of a Vibrant on a brick.
Droidificator said:
I use SGS Toolbox to back up my efs; is that sufficient?
It's on the market for less than $2, and has a ton of other features so well worth the money regardless.
Sent from my rough sketch of a Vibrant on a brick.
Click to expand...
Click to collapse
yeah that should do it, but it never hurts to do it again
I read this from the original op, back then when I was trying to change the IMEI. But good you posted this, easier to find.
Does anybody has a dump of the whole NAND flash of a rootable chromecast? (ideally while still in the original factory state)
If not, could someone with a rooted chromecast dump the bootloader (partition)? (basically the first couple of blocks/megabytes)
Any help would be very welcome
To help, if they manage to get adb over wifi working, run
Code:
adb shell su -c 'dd if=/dev/block/platform/*/*/by-name/bootloader' > ccbootloader.bin
. This command should, as root, write the bootloader to stdout, which we will take and write to a local file. (For the non-technical people, it makes a bootloader dump and puts it on your computer) please note that this requires your chromecast to be rooted and have adb working over wifi.
Sent from my iPod touch using Tapatalk
Definitely talk to @rekids - they've been working on this stuff.
I no longer have this phone!
---
Are you having problems flashing custom ROMs and then getting bootloops? Are you sick of using the Stock ROM?
I found that it is caused by accidentally wiping the PDS partition in some versions of CWM an TWRP.
By going into Settings > About > Status the serial number will no longer be shown. (Unknown or Error.)
A long time ago, someone posted their PDS (yay!) here.
The second post has an extracted PDS.
You will need to download both the pds.img and efi.zip for this tutorial.
To see where the PDS is located for the XT890, look here. (mmcblk0p12)
~
Note: I've attached some pics to help - see below.
Step One:
While booted into Android, you need to use the following commands: (Make sure you enable USB Debugging.)
Code:
adb push pds.img /data/local/tmp
adb shell
su
chmod 777 /data/local/tmp/pds.img
dd if=/data/local/tmp/pds.img of=/dev/block/mmcblk0p12
exit
exit
adb reboot
At this point, if you boot into fastboot, you'll notice the PDS is fixed, but it will not show YOUR serial number.
Step Two:
Extract efi.zip
Open up efi\factory\fti using a hex editor (I use XVI32)
Find the decimal address (Address > Goto) 21
Insert your serial number as a text string T********H (Edit > Insert string)
Remember, the serial number is TEN characters.
Remove the old serial number using Delete on the keyboard.
You should end up with your serial number and EA4 on the end.
Save the file and copy it to your phone.
Using a root explorer file manager (I use ES File Explorer) mount / as RW
Browse to /pds/factory/, copy your edited fti file and overwrite.
Step Three:
Restart the phone and boot into fastboot.
Code:
fastboot erase cache
fastboot reboot-bootloader
fasboot should now show the correct serial number.
Congrats!
I hope this has helped you, please give feedback.
Good find. Thanks for the contribution
So my Serialnumber is the MSN on my phonebox right, the one right above the IMEI? Cause mine is not beginning wit a "T", but it has 10 characters.
Btw, the Serialnumber is not the only thing that is unique - the mac adress is saved in the pds too. I will try to change mine later, should work with the same method, i just create a new one i guess - dont know how to get my old one.
I lost my box a long time ago, but had my serial number saved in a screenshot from when I unlocked the phone's bootloader.
Thanks for the info on the MAC address, I'll look into it later.
Sent from my XT890
Worth a try with the Moto X Style?
AlertRobotdude said:
Worth a try with the Moto X Style?
Click to expand...
Click to collapse
Maybe, but not this one. Do know u are in the "Razr I" forums of XDA and not in the "Moto X Style" forums.
Dear Friends in XDA forums, I'm from China, I just got a KFSOWI device with fire OS 4.5.2 (452004220) system and I want to update it to CM12, and I followed the steps which are searched from the Internet, but unfortunately, it doesn't display anything and no reaction when I press any button or insert the USB cable.
Here are the commands that I have done before:
adb push u-boot.bin /sdcard/
adb push twrp.img /sdcard/
adb shell
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p5
dd if=/sdcard/u-boot.bin of=/dev/block/mmcblk0p2
reboot
After reboot, the screen never light again.....Then I found a person to help me get it repaired
He dismantled and checked, then told me that I put wrong files and covered the MISC partition, and he need MISC partition file to replace, I don't know where to find this file, so I could only consult in the forum, if any friend have this file please send to me, or if you know any other method to repair, please told me.
Thank you very much for your attention。
Welcome! Nice to see so many different people from different countrys here.
To your topic: I search here for a solution to find out wich partition needs wich img or bin file from the source-of firmware.
I can provide you a MISC partition dump of my brciked Fire HD 7" 3rd gen tablet SOHO, but it is a 16GB version.
How did your friend connect to the board? Did he solder some pins?
Perhaps you can help me too, I need the model & number of this IC with 8 legs:
http://forum.xda-developers.com/kin.../kindle-fire-hd-7-3rd-gen-2013-soho-t3367780/
What is/hold the misc partition?:
Misc This partition contains miscellaneous system settings in form of on/off switches. These settings may include CID (Carrier or Region ID), USB configuration and certain hardware settings etc. This is an important partition and if it is corrupt or missing, several of the device’s features will will not function normally.
Click to expand...
Click to collapse
Source
Greetings by Idijt
Hi Guys,
I was flashing a custom rom on my Le2 X526 Snapdragon version, somehow I've managed to Delete the IMEI details. The Mobile Network section is grayed out, Although the Wifi and BT are working fine.
No, I didn't perform a backup before flashing.
The bootloader is unlocked, the phone is rooted. It turns on and everything just no network.
I've tried flashing IMEI number using Qualcomm Flashing tools and QFIL, they seem to get stuck at Connecting and ultimately fail. Although I can see my device connected in DIAG Mode in Device Manager (Qualcomm HS-USB Android DIAG 901D - COM !=1X)
I've also tried the method which included the following adb shell commands:
dd if=/dev/zero of=/dev/block/mmcblk0p13
dd if=/dev/zero of=/dev/block/mmcblk0p14
dd if=/dev/zero of=/dev/block/mmcblk0p16
These give me a weird Write Error saying "write error: No space left on device"
Even though there is plenty of space.
Can anyone suggest some things which can be done to investigate this further, can it be some other issue pertaining to partions or something like that.
Any leads and suggestions would be appreciated,
Thanks