Related
Im trying to unpack system.IMG from the ruu and running into.issues.
Unyaffs.exe gives an error. And every other unpack tool I can think of fails.
Any ideas? Has anyone unpacked this yet?
Sent from my ADR6425LVW using XDA App
It doesn't use the yaffs filesystem. you need to unpack with explore2fs.exe on windows or in linux since it is ext4
Serinety said:
Im trying to unpack system.IMG from the ruu and running into.issues.
Unyaffs.exe gives an error. And every other unpack tool I can think of fails.
Any ideas? Has anyone unpacked this yet?
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Its EXT4.
The attached tool "should" do it for you. Its what I used...
I cannot however attrribute credit to the tool because I honestly do not know where it came from but its freeware GNU 3. The license is in the Help -> About.
Enjoy!
con247 said:
It doesn't use the yaffs filesystem. you need to unpack with explore2fs.exe on windows or in linux since it is ext4
Click to expand...
Click to collapse
I dont beleive explore2fs will read ext4. You need to use the one I posted above. Could be wrong as I am at work right now
scrosler said:
I dont beleive explore2fs will read ext4. You need to use the one I posted above. Could be wrong as I am at work right now
Click to expand...
Click to collapse
your the man, that worked I thought it was yaffs and nothing I did worked, it was driving me crazy lol.
2nd thing tho. the img file is 1.2gb, but after i extract it its about 697mb.. are there some hidden files that are not being extracted?
scrosler said:
I dont beleive explore2fs will read ext4. You need to use the one I posted above. Could be wrong as I am at work right now
Click to expand...
Click to collapse
It does I used it to extract the system image a couple weeks ago.
Serinety said:
your the man, that worked I thought it was yaffs and nothing I did worked, it was driving me crazy lol.
2nd thing tho. the img file is 1.2gb, but after i extract it its about 697mb.. are there some hidden files that are not being extracted?
Click to expand...
Click to collapse
Your saying JUST system.img is 1.2GB but extracts to /system/ as 697MB?
Thats some serisous backwards compression
700 Megs sounds about right for /systesm/ image. I can look when I get home. Maybe Con has it close by?
con247 said:
It does I used it to extract the system image a couple weeks ago.
Click to expand...
Click to collapse
What version do you have? I tried with the (what I thought was) latest and it wouldnt read it. I then tried with the other and it was fine. Can you post the version you have that read it?
scrosler said:
Your saying JUST system.img is 1.2GB but extracts to /system/ as 697MB?
Thats some serisous backwards compression
700 Megs sounds about right for /systesm/ image. I can look when I get home. Maybe Con has it close by?
Click to expand...
Click to collapse
File Name: system.img
Type: Disc Image File (.img)
Size on Disk: 1.21 GB (1,308,618,752 bytes)
Folder name: systemimg_upack
Type: Folder
Size on Disk: 697 MB (731,574,272 bytes)
Contains: 1,370 Files, 58 Folders
Serinety said:
File Name: system.img
Type: Disc Image File (.img)
Size on Disk: 1.21 GB (1,308,618,752 bytes)
Folder name: systemimg_upack
Type: Folder
Size on Disk: 697 MB (731,574,272 bytes)
Contains: 1,370 Files, 58 Folders
Click to expand...
Click to collapse
Wow, 500 Megs in slack? Now thats efficency!
But 700 megs sounds right to me for a sys img. I will in a few hours, at work now... Maybe can remopte desktop in... LMS...
Ok, RDP and 4G is AWESOME!
I can confirm what you are seeing is 100% correct.
I never noticed that before....
I also compared this with an Evo 3D ROM and it matches up proportionately....
scrosler said:
Ok, RDP and 4G is AWESOME!
I can confirm what you are seeing is 100% correct.
I never noticed that before....
I also compared this with an Evo 3D ROM and it matches up proportionately....
Click to expand...
Click to collapse
Wonder if its because Windows sees ext4 in a different way.. and mis represents its actual size
Sent from my ADR6425LVW using XDA App
Serinety said:
Wonder if its because Windows sees ext4 in a different way.. and mis represents its actual size
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
Windows is not looking at it as a ext4 file system. Its looking at it as a single IMG file that is 1.x GB's big.
I overwrote partition 23 thinking it was the recovery partition. See http://forum.xda-developers.com/showthread.php?t=1721584 for details.
Would anybody be willing to send me a copy of their partition so that I can fix mine?
Note, it contains the phone's serial number. If you don't want to share that (I wouldn't recommend it), then you'll need to be on eng hboot 0.98 so that you can change the serial number before you take a copy and then restore it back to its original value.
I'd prefer a copy from an Australian, unlocked Telstra phone, but an any unlocked phone would be ok.
If you are willing to do this and don't know how to do it, PM me and I'll provide instructions.
TIA
Edit: I managed to get a copy from another phone.
Sent from my Desire S
I don't have the partition, but I can't help wondering what on earth you're doing with your phone?! Lol! :what:
Sent from my HTC Desire S
Trying to work out how to flash things without using PG88IMG files, which I find a pain if you don't use ADB.
The dd =if =of looked really promising until I discovered I didn't have accurate descriptions of the partitions.
Sent from my Desire S
miz_pimp said:
I don't have the partition...
Sent from my HTC Desire S
Click to expand...
Click to collapse
What do you mean that you don't have that partition? You don't have a /dev/block/mmcblk0p23?
If you didn't have it you would have no serial id, no model id, and who knows what else.
Sent from my Desire S
BillGoss said:
What do you mean that you don't have that partition? You don't have a /dev/block/mmcblk0p23?
If you didn't have it you would have no serial id, no model id, and who knows what else.
Sent from my Desire S
Click to expand...
Click to collapse
No, no, I meant I don't have the partition for you Sorry, I should've clarified
Sent from my HTC Desire S
Ahh. That makes more sense. No problems.
Sent from my Desire S
Same partition problem...
Hi,
I've exactly the same problem as you had. And I desesperatly need to restore that partition.
I've tried several ones, but none of them really work (3G was not working). So I looked into the dump with HexEdit and found out that they were for different part numbers.
Would you mind sharing a copy of yours so I can try it?
I would really appreciate your help.
Cheers :laugh:
Happy to help.
http://db.tt/pkyRxIW9
Sent from my Nexus 7
Fyi, this partition has the following information stored in it:
mmcblk0p23 mfgdevice: WiFi MAC-address @x40, cid @x11098 x11140, imeid @x11130, mid @x1108c x110ac, serialno @x10030 x11000
If you find a way to set the MAC address back to its original value permanently, please let me know how you did so as I've not been able to do that.
Sent from my HTC Saga
I've had also the same problem when trying to restore the original MAC address. When you changed it in the partition, the file at the beginning of the partition seems to be restored to a "default" configuration with mac addr 00:11:22:33:44... . They might be a checksum somewhere !!
By the way, the mac address is also defined a offset x110BC
If I found a solution I'll let you know.
Anyway the mac address is not really a big deal as we will probably never connect to the same wireless lan at the same time
Yeah, we'd be very unlucky to want to access the same Wi-Fi network at the same time. Lol
By the way, the mac address at 110bc is the Bluetooth mac address, not the Wi-Fi address.
Sent from my Nexus 7
Update Wifi Mac Address
Hi Bill,
If you're still interrested by restoring your wifi mac address here is how I did for my phone:
1. Dump and pull the mmcblk0p18 and mmcblk0p23 partitions
Code:
adb shell dd if=/dev/block/mmcblk0p23 of=/data/local/tmp/mmcblk0p23.img
adb shell dd if=/dev/block/mmcblk0p18 of=/data/local/tmp/mmcblk0p18.img
adb pull /data/local/tmp/mmcblk0p23.img
adb pull /data/local/tmp/mmcblk0p18.img
2. Edit both files with HexEdit
The wlan configuration at the beginning of the mmcblk0p23 image (0x00000040) is "protected" by a CRC checksum (at address 0x00000010).
I was not able to reverse engenireed the CRC parameters but whenever you alter the content of this file it is restored to a "factory" default configuration with macaddr=00:11:22:33:44:55
And the factory default is located somewhere in the mmcblk0p18 image (HBOOT).
They are several "factory" defaults wlan configurations in this partition (depending on your board revision and other parameters I guess), so you must find the one which exactly match the one in your mmcblk0p23 image. (you can do a search in HexEdit)
2.a. Update the factory default configuration in mmcblk0p18.img with the mac address you want to use
Save the mmcblk0p18.img file.
2.b. Alter the configuration in mmcblk0p23.img so that the CRC checksum will fail. (Just change the macaddress)
Save the mmcblk0p23.img file
3. Reflash the mmcblk0p18 and mmcblk0p23 partitions with the modified images
Code:
adb push mmcblk0p23.img /data/local/tmp/
adb push mmcblk0p18.img /data/local/tmp/
adb shell dd if=/data/local/tmp/mmcblk0p23.img of=/dev/block/mmcblk0p23
adb shell dd if=/data/local/tmp/mmcblk0p18.img of=/dev/block/mmcblk0p18
4. Reboot and here you have you're new mac address !!!
Thanks! I'll give this a go.
Sent from my Nexus 7
Brilliant, absolutely brilliant.
I did it all from my phone as I don't like using ADB.
The one thing that is a *must* is that both partitions have to be written at the same time.
Let me say it again - brilliant work! !
Sent from my Nexus 7
I need to know if it's possible to pull old text messages off of a backup from an old phone. Before selling my HTC One S, I made an entire dump of it onto my computer.
Now I REALLY need some texts that might have been on the phone for a legal case I'm involved in. This is REALLY, REALLY, REALLY important. I don't know if it's possible to pull texts out of a backup made on a PC or not, but I REALLY need to see what texts are on there if nothing else at all.
I also used a couple different backup methods on the phone such as nandroid, titanium, Backup Everything, etc and would like to be able to go through those as well. Is there a way to emulate the phone so I can restore these backups? Is there another way to go through the data in them without having the phone?
ANY ANY ANY and ALL help greatly appreciated! Thanks!!
Install SMS backup from market
Sent from my HTC One S using xda app-developers app
flex420 said:
Install SMS backup from market
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
With all due respect, did you read my post? lol
I don't have the phone anymore. All I have is a file structure dump I did onto my computer before I sold it.
Yes, you can do it. You need a linux host (or a mac) with sqlite3 installed.
If you have a nandroid, then you have a tar file of your data partition. You have to untar it somewhere.
If you have a raw image, you have to mount it as an ext4. (In that case, a mac won't do, and you need a linux box.)
either:
tar -xf data.tar
or:
mkdir data
mount -t ext4 -o loop data.img data
Your precious data is in the following file:
data/data/com.android.providers.telephony/databases/mmssms.db
You can:
cd data/data/com.android.providers.telephony/databases/
sqlite3 mmssms.db "select * from sms;"
Edit to add:
I'm sure you can extract the file in question from a .tar on windows, and I bet there are also tools to extract it from an ext4 image, but I can't point you at any.
Also, I doubt that texts you pull from a dump are good for legal use. You may have to get the data from your network provider.
touch of jobo said:
Yes, you can do it. You need a linux host (or a mac) with sqlite3 installed.
If you have a nandroid, then you have a tar file of your data partition. You have to untar it somewhere.
If you have a raw image, you have to mount it as an ext4. (In that case, a mac won't do, and you need a linux box.)
either:
tar -xf data.tar
or:
mkdir data
mount -t ext4 -o loop data.img data
Your precious data is in the following file:
data/data/com.android.providers.telephony/databases/mmssms.db
You can:
cd data/data/com.android.providers.telephony/databases/
sqlite3 mmssms.db "select * from sms;"
Edit to add:
I'm sure you can extract the file in question from a .tar on windows, and I bet there are also tools to extract it from an ext4 image, but I can't point you at any.
Also, I doubt that texts you pull from a dump are good for legal use. You may have to get the data from your network provider.
Click to expand...
Click to collapse
Awesome. You rule.
I actually have 3 backups, all 3 of which have a file in them called "data.ext4.tar", and I can use my beloved Backtrack 5 machine (it's just so HANDY! lol) to do this. No problem.
So, I'd just untar it (this would give me an ext4 file system, right?) then mount the resulting ext4 file system and go from there?
I'm trying to get the texts from this AND from the provider.
rmp5s said:
So, I'd just untar it (this would give me an ext4 file system, right?) then mount the resulting ext4 file system and go from there?
Click to expand...
Click to collapse
Untarring the .tar file will give you a folder structure. You dont need to mount anything then. Just navigate to that mmssms.db file and query it with sqlite.
-Jobo
Thanks for the help!
Sent from my Nexus 4 using xda app-developers app
Could someone who has access to a windows machine and the SM-G920F 32 GB variant upload their PIT file to mega or something? I need it to root and can't extract it from my phone because of an apparent bug in Heimdall and jOdin on OS X.
You don't need a computer to do this, just terminal emulator. This is a example that may or may not work on the s6, I'll look into it when I get home.
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/GS6_model_storagesize.pit bs=8 count=580 skip=2176
Change "GS6_model_storagesize.pit" to match the dump so it looks like this example "GS6_SM-G920F_128gb.pit" you can rename it after the dump. I would upload mine to get the ball rolling but I'm not rooted. Hoping for a way to root and keep knox.
ThePagel said:
You don't need a computer to do this, just terminal emulator. This is a example that may or may not work on the s6, I'll look into it when I get home.
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/GS6_model_storagesize.pit bs=8 count=580 skip=2176
Change "GS6_model_storagesize.pit" to match the dump so it looks like this example "GS6_SM-G920F_128gb.pit" you can rename it after the dump. I would upload mine to get the ball rolling but I'm not rooted. Hoping for a way to root and keep knox.
Click to expand...
Click to collapse
This does not work on the s6, Samsung changed the partition mounting so that mmcblk0 isn't found, they use dev/sdaX now.
andrewk36 said:
This does not work on the s6, Samsung changed the partition mounting so that mmcblk0 isn't found, they use dev/sdaX now.
Click to expand...
Click to collapse
Interesting, any clue on how you dump it? This is what I get for being out of the samsung loop for so long.
ThePagel said:
Interesting, any clue on how you dump it? This is what I get for being out of the samsung loop for so long.
Click to expand...
Click to collapse
From what I understand, the only known way is via Heimdall on Windows. (Or jOdin, which does it for you using Heimdall on the backend). Odin, which is included with CF Auto Root works as well, but is windows only. Hence my problem, since I only have access to OS X, and don't want to buy a windows license for such an (overall) insignificant use case. So I'm hoping someone with windows can run Heimdall, extract the PIT file, and upload it.
With all the random qhsusb_bulk hardbricks coming around, I've decided to create a thread to share debrick.img files just in case. You do not need to create this, but if you ever need it, you'll be glad you did.
EXPLANATION:
If you ever HARDBRICK your phone, which can be caused by flashing an incompatible ROM, bad bootloader flash, or anything, your processor will fallback into a mode called USB_BULK mode. In this mode, it will await an SD card with a special image flashed to it, called debrick.img, and boot to that. Once booted from the SDcard, it will await a firmware flash from a computer (download mode.)
However, this image needs to be specific to the bootloader version the phone was running before the hardbrick occured. That's why I've created this thread: people on different bootloaders can share their debrick images.
HOW TO MAKE ONE:
Flash this in TWRP/FlashFire/SafeStrap
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card and share it here please for others who may need it
BACK THIS UP EVERYWHERE. Google drive, dropbox, mediafire, everywhere. DO NOT loose this.
HOW TO USE ONE:
If you ever have the unfortunate luck of needing to use a debrick image, here's what to do:
-Download Win32DiskImager
-Put your microsd into your PC (yes you will need an adapter in some cases)
-Use Win32DiskImager to write the debrick.img to the SD card
-Take battery out of phone
-Put the SDcard into the phone and put the battery back in
-Do Vol Dn+Power+Home
-Your device should boot into Download Mode, and you should see "SDCARD MODE" at the top right
-Flash stock firmware using Odin
Downloads will be added to the 2nd post
Downloads
PB1 BOOTLOADER DEBRICK
PD1 BOOTLOADER DEBRICK (thanks @klabit87)
PLEASE SHARE YOUR OWN DEBRICK IMAGES! I WILL ADD THEM HERE
Great thread to start!! Question, if i'm running PB1 firmware/kernel but I haven't taken any OTA's passed OC4. Would my debrick img be of the OC4 bootloader? Or do I need to flash the OC4 firmware/kernel to where everything is of OC4? This question may help people who are unsure of what's what.
al50 said:
Great thread to start!! Question, if i'm running PB1 firmware/kernel but I haven't taken any OTA's passed OC4. Would my debrick img be of the OC4 bootloader? Or do I need to flash the OC4 firmware/kernel to where everything is of OC4? This question may help people who are unsure of what's what.
Click to expand...
Click to collapse
It is completely based on bootloader version. You can use "Phone Info - Samsung" to confirm before creating an image.
This is great would be nice if you could create Bod5 img for us who are still able to downgrade
Sent from my SM-G900V using Tapatalk
When I get a chance I'll make one for the OC4. Just want to be sure to do it correctly. Since I'm on UL OC4 Bootloader, PB1 firmware
Nandr0idC0nsumer said:
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card
Click to expand...
Click to collapse
Just for clarification, your script doesn't create a file ending in .img:
Code:
#Unbrick-Creator.zip\tools\Unbrick.sh: Line 5
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
ben_pr said:
Just for clarification, your script doesn't create a file ending in .img:
Code:
#Unbrick-Creator.zip\tools\Unbrick.sh: Line 5
mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
Click to expand...
Click to collapse
yes but if you use an archiving program like winrar to open it there is a file called 200mb.img inside and that is the debrick image
I really appreciate ur efforts, but I have a question does it work on all devices ? I will be amuse to know.
Also how space does it requires? 2gb microsd ?
Sent from my SM-G900V using XDA-Developers mobile app
[email protected] said:
I really appreciate ur efforts, but I have a question does it work on all devices ? I will be amuse to know.
Also how space does it requires? 2gb microsd ?
Sent from my SM-G900V using XDA-Developers mobile app
Click to expand...
Click to collapse
200mb is all thats needed on sd.
Only for samsung devices.
Nandr0idC0nsumer said:
yes but if you use an archiving program like winrar to open it there is a file called 200mb.img inside and that is the debrick image
Click to expand...
Click to collapse
The file inside the archive just takes the name of the archive and excludes the ".gz". Since your script renames the file from "200mb.img.gz" to "Unbrick_IMG.gz", the file within the archive is simply named "Unbrick_IMG" and does not have an extension.
I can change the name of the archive to "Unbrick_IMG.img.gz", then extracting it results in a ".img" as expected. However, with the script you posted, users will have to do this last step manually. You could either not change the name in the script, or have the script include the ".img" to save users this last step.
ben_pr said:
The file inside the archive just takes the name of the archive and excludes the ".gz". Since your script renames the file from "200mb.img.gz" to "Unbrick_IMG.gz", the file within the archive is simply named "Unbrick_IMG" and does not have an extension.
I can change the name of the archive to "Unbrick_IMG.img.gz", then extracting it results in a ".img" as expected. However, with the script you posted, users will have to do this last step manually. You could either not change the name in the script, or have the script include the ".img" to save users this last step.
Click to expand...
Click to collapse
the non-extended extracted "UNBRICK_IMG" is the image file and simply adding .img to it will allow it to be flashed
Nandr0idC0nsumer said:
the non-extended extracted "UNBRICK_IMG" is the image file and simply adding .img to it will allow it to be flashed
Click to expand...
Click to collapse
Yes, sorry, but the reason I'm pointing this out is so that you might update the original post to accurately reflect the process.
Nandr0idC0nsumer said:
HOW TO MAKE ONE:
Flash this in TWRP/FlashFire/SafeStrap
Your debrick.img (may be named something else, look for the .img at the end) will be in your external SD card and share it here please for others who may need it
BACK THIS UP EVERYWHERE. Google drive, dropbox, mediafire, everywhere. DO NOT loose this.
Click to expand...
Click to collapse
People shouldn't be looking for a file ending in ".img", and they will also need to extract then rename "Unbrick_IMG.gz". Ideally, whoever created the Unbrick-Creator.zip should just fix the script inside and update the link. I'm not sure why the zipped file gets renamed at all, nor why the original image is called "200mb.img" instead of the expected "debrick.img".
The script could just look like this:
Code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
# Changing name of image from 200MB.img to debrick.img
# dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000; # Original
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/debrick.img bs=4096 count=50000; # Modified
busybox gzip /external_sd/Unbrick_Files/*;
# Removing the rename command
# mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
Then, to get the image file, the user simply needs to connect their phone, navigate to the "Unbrick_Files" folder, copy "debrick.img.gz" to their computer, and unzip the archive.
ben_pr said:
Yes, sorry, but the reason I'm pointing this out is so that you might update the original post to accurately reflect the process.
People shouldn't be looking for a file ending in ".img", and they will also need to extract then rename "Unbrick_IMG.gz". Ideally, whoever created the Unbrick-Creator.zip should just fix the script inside and update the link. I'm not sure why the zipped file gets renamed at all, nor why the original image is called "200mb.img" instead of the expected "debrick.img".
The script could just look like this:
Code:
#!/sbin/sh
mkdir -p /external_sd/Unbrick_Files/;
# Changing name of image from 200MB.img to debrick.img
# dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/200MB.img bs=4096 count=50000; # Original
dd if=/dev/block/mmcblk0 of=/external_sd/Unbrick_Files/debrick.img bs=4096 count=50000; # Modified
busybox gzip /external_sd/Unbrick_Files/*;
# Removing the rename command
# mv /external_sd/Unbrick_Files/200MB.img.gz /external_sd/Unbrick_Files/Unbrick_IMG.gz;
chmod -R 777 /external_sd/Unbrick_Files
Then, to get the image file, the user simply needs to connect their phone, navigate to the "Unbrick_Files" folder, copy "debrick.img.gz" to their computer, and unzip the archive.
Click to expand...
Click to collapse
Good point. I will update the OP later. This is not my package btw
Nandr0idC0nsumer said:
Good point. I will update the OP later. This is not my package btw
Click to expand...
Click to collapse
My mistake; I thought you made the zip!
Nandr0idC0nsumer said:
200mb is all thats needed on sd.
Only for samsung devices.
Click to expand...
Click to collapse
Thanks
Sent from my SM-G900V using XDA-Developers mobile app
ben_pr said:
My mistake; I thought you made the zip!
Click to expand...
Click to collapse
Lol nope. Usually I like to have it all in the updater-script so I wouldn't have had a seperate script
Could someone who has updated to the PD1 bootloader post an unbrick.img for that please?
I attempted to update; flashed the PD1 stock ROM and bootloader in muniz_ri's updated thread and ended up in a soft brick, so I decided to try a full stock PB1 reset, but something went horribly wrong and I'm currently in a hard brick state.
Since something must've gone wrong halfway through, I suspect I'm still holding onto the PD1 bootloader. I've tried the process with the PB1 unbrick.img provided earlier in this thread, but sadly it didn't do anything. Thanks for all the hard work!
akaplo said:
Could someone who has updated to the PD1 bootloader post an unbrick.img for that please?
I attempted to update; flashed the PD1 stock ROM and bootloader in muniz_ri's updated thread and ended up in a soft brick, so I decided to try a full stock PB1 reset, but something went horribly wrong and I'm currently in a hard brick state.
Since something must've gone wrong halfway through, I suspect I'm still holding onto the PD1 bootloader. I've tried the process with the PB1 unbrick.img provided earlier in this thread, but sadly it didn't do anything. Thanks for all the hard work!
Click to expand...
Click to collapse
"I've tried this process" is not specific enough. Please tell me EXACTLY what you did or I can't help.
Nandr0idC0nsumer said:
"I've tried this process" is not specific enough. Please tell me EXACTLY what you did or I can't help.
Click to expand...
Click to collapse
See my thread. http://forum.xda-developers.com/showpost.php?p=67159556&postcount=14