Database Info

[HOW TO] Open CGs

Hi all :
I try open all CGs for see the files, but i only know to open CG39 and some more..
sudo mount -o loop CG.39.smg CG39
But the others ¿¿
Some one have the answer ¿?¿?¿?

There is a Perl script which can unpack boot and recovery (CG35 & CG47) in this thread: http://forum.xda-developers.com/showthread.php?t=443994

Filipitripi said:
Hi all :
I try open all CGs for see the files, but i only know to open CG39 and some more..
sudo mount -o loop CG.39.smg CG39
But the others ¿¿
Some one have the answer ¿?¿?¿?
Click to expand...
Click to collapse
CG64.smg & CG65.smg: partition tables that you can open using fdisk/sfdisk
CG33.smg is a CDROM ISO file!
iirc one or two of them are the splash image (not 100% sure now)

Filipitripi said:
Hi all :
I try open all CGs for see the files, but i only know to open CG39 and some more..
sudo mount -o loop CG.39.smg CG39
But the others ¿¿
Some one have the answer ¿?¿?¿?
Click to expand...
Click to collapse
how to repack cg39.smg
if you have any details on windows 7 how to open repack do send me.

rachit2588 said:
how to repack cg39.smg
if you have any details on windows 7 how to open repack do send me.
Click to expand...
Click to collapse
http://sourceforge.net/projects/ext... 2.2 (Latest)/ext2explore-2.2.71.zip/download
It will allow you opening ext3 images inside Windows

^very good idea

danimagrin said:
http://sourceforge.net/projects/ext... 2.2 (Latest)/ext2explore-2.2.71.zip/download
It will allow you opening ext3 images inside Windows
Click to expand...
Click to collapse
so now i can see files on cg39.smg using ext2reader but the thing is now how to get system image from cg39.smg to system.img ??

rachit2588 said:
so now i can see files on cg39.smg using ext2reader but the thing is now how to get system image from cg39.smg to system.img ??
Click to expand...
Click to collapse
System.img to be restored with Nandroid? If yes you have to extract all files with ext2reader then use mkyaffs2image to build system.img.

danimagrin said:
System.img to be restored with Nandroid? If yes you have to extract all files with ext2reader then use mkyaffs2image to build system.img.
Click to expand...
Click to collapse
with mkyaffs2image its jus showing me a cmd windows for some less thn 1 sec and its jus goes away...please upload the version you are using...also let me know if it needs any prerequisite software to be installed.

It's because mkyaffs2image is a command line app, just like in the DOS days... To use it you should open a cmd window (type cmd at Windows menu and press enter), go to the directory right before the one you extracted files (you use cd "dirname" to enter in a directory and "cd .." to leave it. So when you are in the directory right before the one in which you've extracted files type "mkyaffs2image CG39extracteddir system.img"

danimagrin said:
It's because mkyaffs2image is a command line app, just like in the DOS days... To use it you should open a cmd window (type cmd at Windows menu and press enter), go to the directory right before the one you extracted files (you use cd "dirname" to enter in a directory and "cd .." to leave it. So when you are in the directory right before the one in which you've extracted files type "mkyaffs2image CG39extracteddir system.img"
Click to expand...
Click to collapse
oh , ok.. its working..thanks

danimagrin said:
It's because mkyaffs2image is a command line app, just like in the DOS days... To use it you should open a cmd window (type cmd at Windows menu and press enter), go to the directory right before the one you extracted files (you use cd "dirname" to enter in a directory and "cd .." to leave it. So when you are in the directory right before the one in which you've extracted files type "mkyaffs2image CG39extracteddir system.img"
Click to expand...
Click to collapse
ok last doubt...after creating system.img can it be restored via custom recovery..??
how to add md5 check sums for that so that custom recovery can identify as proper nandorid..!!??

rachit2588 said:
oh , ok.. its working..thanks
Click to expand...
Click to collapse
You welcome!
Sure you can use it with nandroid, you must download md5sum.exe, place it together with mkyaffs2image, after you used mkyaffs2image then type "md5sum system.img" and it will generate checksum. Create a file called "nandroid.md5" and paste what md5sum returned. You can open a nandroid.md5 file of another backup and you'll understand better how it's done..

excellent..i got it

@danimagrin help me how to add root files if our cg39 image is unrooted..??
ie how to manually add root files from some rooted cg39 image to some non rooted original image..which files and folders are required to add/replace..?? ne thoughts..

rachit2588 said:
@danimagrin help me how to add root files if our cg39 image is unrooted..??
ie how to manually add root files from some rooted cg39 image to some non rooted original image..which files and folders are required to add/replace..?? ne thoughts..
Click to expand...
Click to collapse
I know how to do it on Linux, because you've to run chmod and chown to set su and Superuser.apk permissions. I'll see if it's possible to do it inside Windows and I'll answer you asap.
Where did you get mkyaffs2image for Windows? Are you running it with -f flag or not? Have you already made an image and restored it and did it really work? I'm afraid if will not work because of the same problem above...

danimagrin said:
I know how to do it on Linux, because you've to run chmod and chown to set su and Superuser.apk permissions. I'll see if it's possible to do it inside Windows and I'll answer you asap.
Where did you get mkyaffs2image for Windows? Are you running it with -f flag or not? Have you already made an image and restored it and did it really work? I'm afraid if will not work because of the same problem above...
Click to expand...
Click to collapse
yes i have made an system.img with md5 nandroid check sum...but still not restored with CWM Recovery...yeah mkyaffs2image works on windows...find out in the attached IMG depacker

rachit2588 said:
yes i have made an system.img with md5 nandroid check sum...but still not restored with CWM Recovery...yeah mkyaffs2image works on windows...find out in the attached IMG depacker
Click to expand...
Click to collapse
I'll test it as soon as I get home and then I tell you!

[GUIDE] Official HBOOT v2.xx Downgrade to OLD HBOOT

UPDATED as of 18 DEC 2012 clarified and fixed some things..
Worldwide disclaimer not held responsible if something went wrong blah blah blah goes here..
Click to expand...
Click to collapse
THIS GUIDE WILL VOID YOUR WARRANTY BECAUSE OF THE HTC-DEV UNLOCK METHOD!!! And you can only use this guide if you are on HBOOT v2.xx
Click to expand...
Click to collapse
This guide may also be used for DEBRANDING your phone..
Click to expand...
Click to collapse
Check my sig first, then these for proper and additional information:
[GUIDE] Possible FIX for the infamous eMMC problem..
[Q] Bricked my phone?
NOTE:
RUUs with v1.xxx have HBOOTs with v0.98.000, while v2.xxx have HBOOTs with 2.00.002, and the ICS RUU has the only HBOOT v2.02.002
Click to expand...
Click to collapse
I will not supply the necessary files that is needed, you MUST know how to use SEARCH. I also suggest to give THANKS to those who originally made/uploaded the files.
Requirements:
Common Sense
- it helps A LOT
HTC Sync for Desire S - Installed
- for its drivers and such, or you may just install the "naked" drivers
Android Windows Tools - Installed
- for adb, fastboot commands
HTC-Dev unlocked
- to change recovery and ROM
Custom recovery
- to flash Root Access
SuperSU or SuperUser flashable zip
- to have Root Access
Root Access
- to change phone version
misc_version file (attached)
- file needed to change phone version
GoldCard
- to flash any version of RUUs
RUU executable file
- to DOWN/UPgrade
Click to expand...
Click to collapse
Quick tip:
Copy-Paste the cmd codes for you to not have any problem. 1 typo error (extra digit on misc_version) will render your phone unable to RUU.
Click to expand...
Click to collapse
Preparations
a. Create a folder "downsaga" on your C:
b. Copy misc_version, recovery.img(custom) on that folder.
c. Copy SuperSU's or SuperUser's flashable zip to your SD card.
Click to expand...
Click to collapse
Creating a Gold Card (use below or attn1's GoldCard Method)
a. Install Goldcard Helper from the market on your phone
b. Run it and copy the CID for MMC2, or email the info to yours
c. This number has already been reversed so go to http://psas.revskills.de/?q=goldcard, fill out the required fields.
d. Download the image file that was emailed to you.
e. Connect phone as a "Disk drive" using USB cable.
f. Use Gold Card Tool to flash your image file to your phone's SD card. (you might need to reformat it first with Panasonic's SD Formatter)
g. Disconnect safely from the PC.
NOTE:Your sd card is now a GoldCard unless you reformat it again. You should now be able to RUU to any version you would like given that the bootloader is LOCKED.
Click to expand...
Click to collapse
Unlocking the bootloader
a. Go to htcdev.com/bootloader
b. Proceed and follow every step on the guide
c. You just need to install Android Windows Tools files for it. No need to download the SDK and JAVA.
d. Once done, boot on bootloader and you should be able to notice if its UNLOCKED.
Click to expand...
Click to collapse
Flashing Custom Recovery
a. The phone must be on bootloader, then go to fastboot
b. Open up command prompt then type:
Code:
fastboot flash recovery C:\downsaga\recovery.img
fastboot reboot-bootloader
d. Access recovery
Click to expand...
Click to collapse
Flashing Root Access
a. Flash SuperSU or SuperUser
b. Reboot the phone normally
Click to expand...
Click to collapse
Modifying the version of your phone
a. Connect the phone using USB cable using "Charge ONLY" and USB Debugging is ON.
b. Open command prompt and input these codes:
Code:
adb push C:\downsaga\misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
su
cd /data/local/tmp
./misc_version -s 1.27.405.6
exit
adb reboot-bootloader
c. Your phone should now be read as the version you've placed there (but not visible to settings)
Click to expand...
Click to collapse
Locking the bootloader
a. You should be on fastboot
c. In cmd use this command to lock the bootloader:
Code:
fastboot oem lock
c. You might receive an error message on your CMD but don't mind it. The phone should restart itself automatically on bootloader, and you should be able to notice at the top saying "***RE-LOCKED***", and might also has *Security Warning*. Just ignore.
Click to expand...
Click to collapse
Downgrading
a. Make sure you are still on fastboot with the above message.
b. Open the RUU that you've chosen to install on your phone
c. The RUU must detect your phone version as 1.27.405.6
d. If you have received errors, then you've done something wrong. Review everything that you've done and check the guide again.
Click to expand...
Click to collapse
If everything went well, you should have successfully downgraded your phone and your HBOOT.

Hey man it seems you did it! So HTC official unlocker can be handy after all.
Great job! I assume that now you will use Revolutionary to gain S-OFF and back to flashing?

amidabuddha said:
Hey man it seems you did it! So HTC official unlocker can be handy after all.
Great job! I assume that now you will use Revolutionary to gain S-OFF and back to flashing?
Click to expand...
Click to collapse
yes sir'ree!

And howto flash your hboot in recoverymode
Use flash_image to flash your hboot to older version.
flash_image /dev/block/mmcblk0p18 )(path to an older hboot file)

NikMel said:
Use flash_image to flash your hboot to older version.
flash_image /dev/block/mmcblk0p18 )(path to an older hboot file)
Click to expand...
Click to collapse
You wouldn't be able to do that on an official, latest S-ON HBOOT. I have already tried that but will just give you an INFOsignature error.

Skanob said:
Step 1: Creating a Gold Card
a. Install Goldcard Helper from the market
b. Run it and copy the CID for MMC2, or email the info to yours
c. This number has already been reversed so go to http://psas.revskills.de/?q=goldcard, fill out the required fields.
d. Download the image file that was emailed to you.
e. Connect phone as a "Disk drive" using USB cable.
f. Use Gold Card Tool to flash your image file to your phone's SD card. (you might need to reformat it first with Panasonic's SD Formatter and then format it with the Gold Card Tool again)
g. Disconnect safely from the PC, and disconnect the cable.
Click to expand...
Click to collapse
Why would you use such an obsolete method to make a gold card?
after temproot,
windows batch script ( example filename: gc.cmd ):
Code:
adb push goldcard /data/local/tmp/
adb shell chmod 777 /data/local/tmp/goldcard
adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid > tcid
set/p cid= < tcid
del tcid
adb shell /data/local/tmp/goldcard -c %cid% -o /data/local/tmp/goldcard.img
adb shell dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1
Linux shell script (example filename: gc.sh ):
Code:
adb push goldcard /data/local/tmp/
adb shell chmod 777 /data/local/tmp/goldcard
cid=`adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid`
adb shell /data/local/tmp/goldcard -c $cid -o /data/local/tmp/goldcard.img
adb shell dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1
get the android goldcard binary here:
Thanks to Revskills for the algorythm and to GenePoole for the Android binary.
With this, the entire process can be scripted.

Skanob said:
You wouldn't be able to do that on an official, latest S-ON HBOOT. I have already tried that but will just give you an INFOsignature error.
Click to expand...
Click to collapse
You can do that in recoverymode within adb shell #
I use 4ext recoverymode

attn1 said:
Why would you use such an obsolete method to make a gold card?
after temproot,
windows batch:
Code:
adb push goldcard /data/local/tmp/
adb shell chmod 777 /data/local/tmp/goldcard
adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid > tcid
set/p cid= < tcid
del tcid
adb shell /data/local/tmp/goldcard -c %cid% -o /data/local/tmp/goldcard.img
adb shell dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1
Linux Shell:
Code:
adb push goldcard /data/local/tmp/
adb shell chmod 777 /data/local/tmp/goldcard
cid=`adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid`
adb shell /data/local/tmp/goldcard -c $cid -o /data/local/tmp/goldcard.img
adb shell dd if=/data/local/tmp/goldcard.img of=/dev/block/mmcblk1
get the android goldcard binary here:
Thanks to Revskills for the algorythm and to GenePoole for the Android binary.
With this, the entire process can be scripted.
Click to expand...
Click to collapse
well, that obsolete-method for me is a hell-of-a-lot easier and noob-proof. no code needed. and also leaves you a copy of your goldcard.img

NikMel said:
You can do that in recoverymode within adb shell #
I use 4ext recoverymode
Click to expand...
Click to collapse
That didn't worked for me. Prior to downgrading, check my sig. I'm using the official S-ON, not the ENG S-OFF leaked.

Skanob said:
well, that obsolete-method for me is a hell-of-a-lot easier and noob-proof. no code needed. and also leaves you a copy of your goldcard.img
Click to expand...
Click to collapse
No way is it easier or noob proof. When I used this method on the Ace Hack Kit goldcard errors dropped to none. Since you are already running adb commands and pushing crap to the phone, what's the big deal with this?
With this, there is no need for hacky tools, not mounting/dismounting the sdcard (risking corruption from unflushed write buffers and improper dismounts), and no need to go to the revskills website.
This runs in about a second and it's done.

attn1 said:
No way is it easier or noob proof. When I used this method on the Ace Hack Kit goldcard errors dropped to none. Since you are already running adb commands and pushing crap to the phone, what's the big deal with this?
With this, there is no need for hacky tools, not mounting/dismounting the sdcard, and no need to go to the revskills website or copy files back from email. This runs in about second and it's done.
Click to expand...
Click to collapse
I believe that that is based on your preference. Which I observed really knows a lot about adb.
And what is in the guide is based on my own preference. Which for me does not know much about adb.
They still can follow which ever method they would like.
Well, it would still give us the same result. Having a GoldCard.

Skanob said:
I believe that that is based on your preference. Which I observed really knows a lot about adb.
And what is in the guide is based on my own preference. Which for me does not know much about adb.
They still can follow which ever method they would like.
Well, it would still give us the same result. Having a GoldCard.
Click to expand...
Click to collapse
Mine is based on real results after thousands of uses of the Ace Hack Kit, which formerly did things the obsolete way.
Yours is based on preference.
But you are right, either way will result in a goldcard if executed properly.

attn1 said:
Mine is based on real results after thousands of uses of the Ace Hack Kit, which formerly did things the obsolete way.
Yours is based on preference.
But you are right, either way will result in a goldcard if executed properly.
Click to expand...
Click to collapse
yeah. I'll update the guide with your method aswell. Thanks aswell!
High five!

Skanob said:
yeah. I'll update the guide with your method aswell. Thanks aswell!
High five!
Click to expand...
Click to collapse
You're welcome.
Make a note that those are the contents of a script - .cmd or .sh.
FYI, if you try this to make the goldcard image, the one generated should match the md5 of one you got from Revskills.
Once you do it this way, you will never go back.

@Scanob
Since you change your guide in step 6 to run RUU instead of PG88IMG.zip than the Goldcard is no longer needed isn't it?

misc_version not found error....

I don't know how to find this official recovery.img. (Yes I try to find it...)
Step 4: Flashing official recovery.img

amidabuddha said:
@Scanob
Since you change your guide in step 6 to run RUU instead of PG88IMG.zip than the Goldcard is no longer needed isn't it?
Click to expand...
Click to collapse
You will still need it. Even the PG88IMG.zip method uses checks as exactly the same as doing an RUU.

hekermeker said:
misc_version not found error....
Click to expand...
Click to collapse
barthdvs said:
I don't know how to find this official recovery.img. (Yes I try to find it...)
Step 4: Flashing official recovery.img
Click to expand...
Click to collapse
Re-check the guide after a few

@barthdvs
Getting the Official files
a. Download the HTC_EUROPE_2.10.401.5 RUU file.
b. Run the file and do not close
c. Go to your temp folder on your computer and find the rom.zip file.
d. Copy it somewhere else.
e. Extract the rom.zip and you should now have the official .img files from the RUU.
f. Use the respective files needed for the guide.
or the files is here (files exrtract from HTC_EUROPE_2.10.401.5 RUU file)
Boot.img : http://www.multiupload.com/JME2WRDQEQ
recovery.img : http://www.multiupload.com/MX64VDUICI

RUU File for RADIO-26.17.14.11_M

Hi,
I have the HTC Inspire 4g with:
Software #: 3.20.502.52 710RD
Android Version 2.3.5
HTC Sense 3.0
Baseband version: 12.69a.60.29u_26.17.14.11_M
I have unlocked the bootloader using htcdev and have successfully rooted the the device but i'm still S-ON. I have tried installing some custom ROMs however after flashing the device did not boot. I understand that I have to flash the boot.img file located in the .zip file of the custome ROM. That I know how to do... My concern is that I want to try out some ROMs but as a precaution I would like to have the stock RUU file for the type device I have should I need to restore it.
I did create a backup of my ROM and have used it previously to restore the phone after installing the custom roms that haven't boot. I just want to know if I flash the boot.img file will a restore bring it back to where it was before the flash or do i need the RUU file to restore stock?
If the later please advice where I can find that particular file as I've searched but can't seem to find the one to use.
Thanks a million.
360fifa

360fifa said:
Hi,
I have the HTC Inspire 4g with:
Software #: 3.20.502.52 710RD
Android Version 2.3.5
HTC Sense 3.0
Baseband version: 12.69a.60.29u_26.17.14.11_M
I have unlocked the bootloader using htcdev and have successfully rooted the the device but i'm still S-ON. I have tried installing some custom ROMs however after flashing the device did not boot. I understand that I have to flash the boot.img file located in the .zip file of the custome ROM. That I know how to do... My concern is that I want to try out some ROMs but as a precaution I would like to have the stock RUU file for the type device I have should I need to restore it.
I did create a backup of my ROM and have used it previously to restore the phone after installing the custom roms that haven't boot. I just want to know if I flash the boot.img file will a restore bring it back to where it was before the flash or do i need the RUU file to restore stock?
If the later please advice where I can find that particular file as I've searched but can't seem to find the one to use.
Thanks a million.
360fifa
Click to expand...
Click to collapse
RUU 3.20.502.52

Thank you kindly for taking the time to respond and also help.

Hi Gizmoe,
is there a rooted and s-off RUU file I could use as well?
Thanks again..

360fifa said:
Hi Gizmoe,
is there a rooted and s-off RUU file I could use as well?
Thanks again..
Click to expand...
Click to collapse
RUU 's can not be modified. You will not lose s off however by running an ruu. After you run ruu just pd98img a recovery and flash away.

Gizmoe said:
RUU 's can not be modified. You will not lose s off however by running an ruu. After you run ruu just pd98img a recovery and flash away.
Click to expand...
Click to collapse
So are you saying that I would need to unlock the bootloader again then following the same steps I have now? I had the impression based off could threads I've read that there's a way to root the device while gaining S-OFF that will allow me to avoid having to manually flash the boot.IMG everytime i install a custom rom. If there's a thread I can read or a guide to follow please provide a link so that I can proceed. Oh, does all the pd98img file the same?
Thanks again.
360fifa

360fifa said:
So are you saying that I would need to unlock the bootloader again then following the same steps I have now? I had the impression based off could threads I've read that there's a way to root the device while gaining S-OFF that will allow me to avoid having to manually flash the boot.IMG everytime i install a custom rom. If there's a thread I can read or a guide to follow please provide a link so that I can proceed. Oh, does all the pd98img file the same?
Thanks again.
360fifa
Click to expand...
Click to collapse
Yeah that's right. Your not s off. Well here is the only method left for the inspire. It may be a bit intimidating but really isn't that hard. Here is link.
http://tau.shadowchild.nl/attn1/?cat=6

Gizmoe said:
Yeah that's right. Your not s off. Well here is the only method left for the inspire. It may be a bit intimidating but really isn't that hard. Here is link.
Click to expand...
Click to collapse
Your're right very intimidating, however I'm willing to try my only concern is what is dd highlighted below "High Level Steps (some detail deliberately NOT included)
htc dev unlock, install cwm recovery and root ONLY
dd the stock boot image to /data/local/tmp and pull it to your pc HD (/dev/block/mmcblk0p22 is boot)
adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img"?
Also i navigated to the folder on my device however it doesn't show any boot.img file. Just a init.rc file. Could you explain just this part of it please?
Thanks again,
360fifa

360fifa said:
Your're right very intimidating, however I'm willing to try my only concern is what is dd highlighted below "High Level Steps (some detail deliberately NOT included)
htc dev unlock, install cwm recovery and root ONLY
dd the stock boot image to /data/local/tmp and pull it to your pc HD (/dev/block/mmcblk0p22 is boot)
adb shell dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img"?
Also i navigated to the folder on my device however it doesn't show any boot.img file. Just a init.rc file. Could you explain just this part of it please?
Thanks again,
360fifa
Click to expand...
Click to collapse
DD is copy and convert. It will copy boot files and convert it into boot.img. Use adb shell to do it as shell works within phone directories. Then pull it from pc using adb pull. He is giving you the exact adb commands to do both.
Code:
adb shell
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img

Gizmoe said:
DD is copy and convert. It will copy boot files and convert it into boot.img. Use adb shell to do it as shell works within phone directories. Then pull it from pc using adb pull. He is giving you the exact adb commands to do both.
Code:
adb shell
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot.img
adb pull /data/local/tmp/boot.img
Click to expand...
Click to collapse
Lol... I figured those were the commands to use, was just wondering what dd stand for.. ( copy and convert ). So let me see if i understand whats happening in the code.
So firstly I need to have the the HTC drivers installed and have the Android SDK on the root of c drive. Basically the same folder used when I unlocked to bootloader. In that folder I have the adb files, should I also add the files listed in the zip file he provided? If so let me explain the code, if no please shed some light.
So adb shell starts the emulator with the device
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot will copy and convert the mmcblk0p22 file if it is found in the /dev/block folder on the device and place it to the /data/local/tmp/ folder and call it boot.img
adb pull /data/local/tmp/boot.img I'm thinking that the computer is going to pull the boot.IMG file from the /data/local/tmp folder however where is it putting it? In the same folder that I started the command prompt from? That is the Android folder on my c drive?

360fifa said:
Lol... I figured those were the commands to use, was just wondering what dd stand for.. ( copy and convert ). So let me see if i understand whats happening in the code.
So firstly I need to have the the HTC drivers installed and have the Android SDK on the root of c drive. Basically the same folder used when I unlocked to bootloader. In that folder I have the adb files, should I also add the files listed in the zip file he provided? If so let me explain the code, if no please shed some light.
So adb shell starts the emulator with the device
dd if=/dev/block/mmcblk0p22 of=/data/local/tmp/boot will copy and convert the mmcblk0p22 file if it is found in the /dev/block folder on the device and place it to the /data/local/tmp/ folder and call it boot.img
adb pull /data/local/tmp/boot.img I'm thinking that the computer is going to pull the boot.IMG file from the /data/local/tmp folder however where is it putting it? In the same folder that I started the command prompt from? That is the Android folder on my c drive?
Click to expand...
Click to collapse
You will want to work out of the platform-tools directory.
Yes adb pull will always pull to your working directory unless another path is specified. Adb shell will need root. So if you type adb shell and don't see a # sign type su to get it. When done in adb shell you will need exit so you can pull to computer. If you had to take two steps to get a # prompt then you will type exit twice.

Gizmoe said:
You will want to work out of the platform-tools directory.
Yes adb pull will always pull to your working directory unless another path is specified. Adb shell will need root. So if you type adb shell and don't see a # sign type su to get it. When done in adb shell you will need exit so you can pull to computer. If you had to take two steps to get a # prompt then you will type exit twice.
Click to expand...
Click to collapse
Kool, thats the directory i'm referring to... I'm sure i'm already rooted. But your saying that when i send the command "adb shell" if I don't see the # sign then i should type su. Are you then saying that if I had to type su twice then I need to hit exit twice to pull to pc?
Oh before I forget should i run ruu before attempting this or remain as is? Also, do I need cmw recovery installed or can i remain on twrp 2.6.0.0?
Thanks again bro..
360fifa

360fifa said:
Kool, thats the directory i'm referring to... I'm sure i'm already rooted. But your saying that when i send the command "adb shell" if I don't see the # sign then i should type su. Are you then saying that if I had to type su twice then I need to hit exit twice to pull to pc?
Oh before I forget should i run ruu or remain as is?
Thanks again bro..
360fifa
Click to expand...
Click to collapse
Yes you would need to type su to see #. Adb shell root access works independently of phone root. It needs root access over adb which without an UN-secure boot img will need the su command. Exit for each level. Once for su and once for shell itself. You want to exit until you are back at Windows directory. Adb shell is at the phones root directory. The dd command is moving files within the phone, while Adb pull would be used to copy from phone to pc. I would not run that ruu if you are going to try and s off. I would run 2.47.502.7. Which I posted a link in the att stock Rom thread.
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
http://forum.xda-developers.com/showthread.php?p=50027824

Gizmoe said:
Yes you would need to type su to see #. Adb shell root access works independently of phone root. It needs root access over adb which without an UN-secure boot img will need the su command. Exit for each level. Once for su and once for shell itself. You want to exit until you are back at Windows directory. Adb shell is at the phones root directory. The dd command is moving files within the phone, while Adb pull would be used to copy from phone to pc. I would not run that ruu if you are going to try and s off. I would run 2.47.502.7. Which I posted a link in the att stock Rom thread.
---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------
http://forum.xda-developers.com/showthread.php?p=50027824
Click to expand...
Click to collapse
Do i need to run a ruu or can I proceed as is? If so u recommend running the 2.47.502.7 ruu before going thru the adb commands, y?
Thanks again..

360fifa said:
Do i need to run a ruu or can I proceed as is? If so u recommend running the 2.47.502.7 ruu before going thru the adb commands, y?
Thanks again..
Click to expand...
Click to collapse
Yes go ahead and proceed as is. You should not have any issues. If not successful then try ruu. You may not be able to run the older ruu if your bootloader is newer. Which in that case just run the newer one. I beleive I used this process on a phone with the newer software but the older works for sure.

Gizmoe said:
Yes go ahead and proceed as is. You should not have any issues. If not successful then try ruu. You may not be able to run the older ruu if your bootloader is newer. Which in that case just run the newer one. I beleive I used this process on a phone with the newer software but the older works for sure.
Click to expand...
Click to collapse
Gizmoe you have been very patient and very helpful i thank you a million times. If i encounter any other issues I'll definitely let you know.
Thanks again..
360fifa

360fifa said:
Gizmoe you have been very patient and very helpful i thank you a million times. If i encounter any other issues I'll definitely let you know.
Thanks again..
360fifa
Click to expand...
Click to collapse
I encountered an issue while trying to pull the boot.img file from /data/local/tmp/. The command used was adb pull /data/local/tmp/boot.img I then got a msg saying the adb is not a command, if I remove the adb and send the command with just pull it says pull is not a command.
If I exit su "#" it brings me to $ and if I send the command again it says that I don't have permission. Can you advise what I might be doing wrong? Oh, I got the mmcblk0p22 file to copy and convert into the boot.img file. I was able to see it using ES File explorer on my phone.
Do I need to go in fastboot usb, does unknown sources need to be checked?
Thanks again.

360fifa said:
I encountered an issue while trying to pull the boot.img file from /data/local/tmp/. The command used was adb pull /data/local/tmp/boot.img I then got a msg saying the adb is not a command, if I remove the adb and send the command with just pull it says pull is not a command.
If I exit su "#" it brings me to $ and if I send the command again it says that I don't have permission. Can you advise what I might be doing wrong? Oh, I got the mmcblk0p22 file to copy and convert into the boot.img file. I was able to see it using ES File explorer on my phone.
Do I need to go in fastboot usb, does unknown sources need to be checked?
Thanks again.
Click to expand...
Click to collapse
You need to exit one more time so you can see c prompt with your platform tools folder. Your still in shell therefore still in phone and not actually pulling to your pc. Only the pc uses Adb commands so you have to be at your platform tools folder. If you restart your phone temp empties too so if you can't see boot img anymore that's why.

Gizmoe said:
You need to exit one more time so you can see c prompt with your platform tools folder. Your still in shell therefore still in phone and not actually pulling to your pc. Only the pc uses Adb commands so you have to be at your platform tools folder. If you restart your phone temp empties too so if you can't see boot img anymore that's why.
Click to expand...
Click to collapse
Okay.. I am going to try that now, I swore I did that as well but lets see.

360fifa said:
Okay.. I am going to try that now, I swore I did that as well but lets see.
Click to expand...
Click to collapse
Here's what it said "failed to copy '/data/local/tmp/boot.img' to ' ./boot.img': Permission denied

[TUT]Custom Splash screen - S7 Flat/Edge

Hi all. I just want to share how to change your splash screen, if ever you want a customized one. I created my own, for SuperMan-Rom. So without further ado, here's the tutorial:
NOTE: Tested perfectly on SuperMan-Rom without any problems.
Pre-requisites:
- PC
- Android SDK
- ADB
- Knowledge in adb codes
- Rooted device
- Back up!
Steps:
1.) Open CMD on your PC - make sure your phone is connected and has usb debugging enabled.
2.) Now type adb devices - this will serve as confirmation that your device is detected in adb.
3.) Allow any request for superuser permission in your phone.
now for the codes:
4.)On CMD, type:
adb shell
Click to expand...
Click to collapse
5.)Now type:
su
Click to expand...
Click to collapse
6.)Now it's time to pull out the param.bin, which contains the splash logo:
dd if=/dev/block/sda4 of=/sdcard/param.bin bs=4096
Click to expand...
Click to collapse
7.)Now we must create a folder on main sd card:
mkdir /sdcard/param
Click to expand...
Click to collapse
8.)Then enter the directory:
cd /sdcard/param
Click to expand...
Click to collapse
9.)And untar the param.bin into the created folder:
tar xf /sdcard/param.bin
Click to expand...
Click to collapse
If all goes well, you can see a param folder in your main sdcard (mine is in internal memory), which has all the bootloader's images. Just copy the logo.jpg to your PC.
10.)Now you can edit the logo.jpg to your liking - note that the background should remain black, and the size should not be more than 400KB.
11.)Once done editing, copy your customized logo.jpg on main sd card
12.)Then, we have to paste it inside /sdcard/param folder, and retar param.bin:
cp -f /sdcard/logo.jpg /sdcard/param/logo.jpg
rm -f /sdcard/param.bin
cd sdcard/param
tar cf - `ls | sort -t.` > /sdcard/param.bin
Click to expand...
Click to collapse
13.)Lastly, we need to return param.bin in system:
dd if=/sdcard/param.bin of=/dev/block/sda4 bs=4096
Click to expand...
Click to collapse
After these steps, reboot!
VOILA! Now you have your won splash image!
I created some for SuperMan-Rom below for those who want it. Also attached default splash image.
Credits to all that needs to be credited!

Bro I need S7 Stock Boot Logo

parth111999 said:
Bro I need S7 Stock Boot Logo
Click to expand...
Click to collapse
Here it is.

@MitoTakatori where's your stock param.bin? i need that, thanks

MitoTakatori said:
Here it is.
Click to expand...
Click to collapse
Bro i Need S7 boot Logo
Not Animation

Hello
it does not work .
I receive this mistake
Tar: warning_L. Jpg: cant open: Read-only file system
Tar: chow 1000: 1000 'warning_L. Jpg ': No such file or directory

HELP! I can't untar the param.bin file!
MitoTakatori said:
Hi all. I just want to share how to change your splash screen, if ever you want a customized one. I created my own, for SuperMan-Rom. So without further ado, here's the tutorial:
NOTE: Tested perfectly on SuperMan-Rom without any problems.
Pre-requisites:
- PC
- Android SDK
- ADB
- Knowledge in adb codes
- Rooted device
- Back up!
Steps:
1.) Open CMD on your PC - make sure your phone is connected and has usb debugging enabled.
2.) Now type adb devices - this will serve as confirmation that your device is detected in adb.
3.) Allow any request for superuser permission in your phone.
now for the codes:
4.)On CMD, type:
5.)Now type:
6.)Now it's time to pull out the param.bin, which contains the splash logo:
7.)Now we must create a folder on main sd card:
8.)Then enter the directory:
9.)And untar the param.bin into the created folder:
If all goes well, you can see a param folder in your main sdcard (mine is in internal memory), which has all the bootloader's images. Just copy the logo.jpg to your PC.
10.)Now you can edit the logo.jpg to your liking - note that the background should remain black, and the size should not be more than 400KB.
11.)Once done editing, copy your customized logo.jpg on main sd card
12.)Then, we have to paste it inside /sdcard/param folder, and retar param.bin:
13.)Lastly, we need to return param.bin in system:
After these steps, reboot!
VOILA! Now you have your won splash image!
I created some for SuperMan-Rom below for those who want it. Also attached default splash image.
Credits to all that needs to be credited!
Click to expand...
Click to collapse
So I tried multiple times your steps and deleted the files all over again. I keep getting stuck at this part
[email protected]:/sdcard/param # tar xf /sdcard/param.bin
tar: invalid tar format
1|[email protected]:/sdcard/param #

silentwind827 said:
So I tried multiple times your steps and deleted the files all over again. I keep getting stuck at this part
[email protected]:/sdcard/param # tar xf /sdcard/param.bin
tar: invalid tar format
1|[email protected]:/sdcard/param #
Click to expand...
Click to collapse
Hi. So you are using T Mobile? I have not tried it with T Mobile, but were you able to fetch your param.bin file?

pendor24 said:
Hello
it does not work .
I receive this mistake
Tar: warning_L. Jpg: cant open: Read-only file system
Tar: chow 1000: 1000 'warning_L. Jpg ': No such file or directory
Click to expand...
Click to collapse
Hi. What ROM are you in and what device model do you have?

zainifame said:
@MitoTakatori where's your stock param.bin? i need that, thanks
Click to expand...
Click to collapse
Why do you need my param.bin?

parth111999 said:
Bro i Need S7 boot Logo
Not Animation
Click to expand...
Click to collapse
I'll try to extract the image. Remember, it is in qmg format.

MitoTakatori said:
Hi. What ROM are you in and what device model do you have?
Click to expand...
Click to collapse
S7 bord nougat XXU1DPLT

pendor24 said:
S7 bord nougat XXU1DPLT
Click to expand...
Click to collapse
You mean stock nougat?

Yes Slightly deified with deodex, 3 minit, and other customizations

pendor24 said:
Yes Slightly deified with deodex, 3 minit, and other customizations
Click to expand...
Click to collapse
I see. S7 flat?

G935f ,
flat?

pendor24 said:
G935f ,
flat?
Click to expand...
Click to collapse
Oh, sorry. It should work as long as you are rooted and usb debugging is enabled. On your PC, you should have adb installed, with android SDK.

Param.bin
MitoTakatori said:
Hi. So you are using T Mobile? I have not tried it with T Mobile, but were you able to fetch your param.bin file?
Click to expand...
Click to collapse
Yes I can extract the param.bin file and also put it on my pc if you need me to. I just need to unzip it. It keeps failing for some reason. Maybe Im grabbing the wrong file and naming it param.bin within the code you provided?

silentwind827 said:
Yes I can extract the param.bin file and also put it on my pc if you need me to. I just need to unzip it. It keeps failing for some reason. Maybe Im grabbing the wrong file and naming it param.bin within the code you provided?
Click to expand...
Click to collapse
Hi. When you extract param.bin, it will be on your main sd card(internal memory), and it's name will be param.bin. When you execute the code, check first in your internal memory if it copied the param.bin. And no need to copy it to PC for extraction.
Just to be sure you can attach the param.bin you extracted and I'll take a look!

MitoTakatori said:
Hi. When you extract param.bin, it will be on your main sd card(internal memory), and it's name will be param.bin. When you execute the code, check first in your internal memory if it copied the param.bin. And no need to copy it to PC for extraction.
Just to be sure you can attach the param.bin you extracted and I'll take a look!
Click to expand...
Click to collapse
Well yeah. I see the file. When I try to extract the file from the param.bin to /sdcard/param/ it fails. HELP!

Help with relocking the bootloader, HAVE TA

Hi.
I am pretty new to the world of Sony and I want to relock my bootloader so I can get stock firmware from my region so it looks legit (Reselling)
I have taken a TA backup but I don't know how to flash it again. Tried TWRP with no luck and I also read som other threads around here that didn't make sense to me.
I am on Windows 10 and have the single SIM Xperia XZ.

https://forum.xda-developers.com/showpost.php?p=69972315&postcount=20
First push TA.img to the folder he mentions.
Do not flash TWRP.
Boot it. fastboot boot TWRP.img
After restoring your TA-Partition flash a stock ROM. If you reboot your phone before flashing stock it will bootloop.

DHGE said:
https://forum.xda-developers.com/showpost.php?p=69972315&postcount=20
First push TA.img to the folder he mentions.
Do not flash TWRP.
Boot it. fastboot boot TWRP.img
After restoring your TA-Partition flash a stock ROM. If you reboot your phone before flashing stock it will bootloop.
Click to expand...
Click to collapse
Okay. But the part I was wondering about is:
- Pushed TAbackup.img (I renamed it) to /data/local/tmp and verified md5sum is same as original backup. (Data/local/tmp - Is this on the phone? How?)

KazuhiraDokky said:
Okay. But the part I was wondering about is:
- Pushed TAbackup.img (I renamed it) to /data/local/tmp and verified md5sum is same as original backup. (Data/local/tmp - Is this on the phone? How?)
Click to expand...
Click to collapse
Follow this instruction, i was restored my TA successfully. Boot into TWRP and enter adb command
https://forum.xda-developers.com/showpost.php?p=70903982&postcount=256

THANK YOU!
Haha christ I see it now. Never noticed before I can push commands when it is in TWRP. Thank you so much. Been wondering about this for quite some time.

Would this also work ?
Flash stock ROM using Emma -> Temporally boot TWRP (fastboot boot TWRP.img) -> dd TA Partition ->reboot.

_mow_ said:
Would this also work ?
Flash stock ROM using Emma -> Temporally boot TWRP (fastboot boot TWRP.img) -> dd TA Partition ->reboot.
Click to expand...
Click to collapse
Have not used emma personally...
But: yes, as I wrote above for Flashtool.

Thank you for your answer.
I was just wondering if there is any particular reason for first restoring TA and then flashing the Stock ROM.

flashing ROM first is safer
I just posted the link where I read about the first sucsessful restore.
It is less dangerous (no potential boot loop) to flash the ROM first and then restore the TA partition.
The only thing you have to remember that way is to enable adb (developer options) and only boot into recovery and not flash it.

Flashing Stock first with Emma worked for me. However on the first boot-up I was asked to enter my password (i didn't set a password) so I had to enter 30 random Passwords until the Phone resets itself. But now everything seems to work.
Thank you.

_mow_ said:
Flashing Stock first with Emma worked for me. However on the first boot-up I was asked to enter my password (i didn't set a password) so I had to enter 30 random Passwords until the Phone resets itself. But now everything seems to work.
Thank you.
Click to expand...
Click to collapse
For me, i flashed rom with flashtool, i checked wipe all (apps_log, userdata, ssd,....). On first boot-up it doesn't ask me for the password .

rain_effect said:
Follow this instruction, i was restored my TA successfully. Boot into TWRP and enter adb command
https://forum.xda-developers.com/showpost.php?p=70903982&postcount=256
Click to expand...
Click to collapse
I tried this but it's not working. I backed up the TA img and cant restore it. I am in twrp recovery mode and did the adb devices to check if it showed up and it does. It's when I put the command "adb push TAbackup.img /data/local/tmp/TAbackup.img" it gives me an error saying "adb: error: cannot stat 'TAbackup.img': No such file or directory". I installed the minimal and fastboot drivers under C drive. I moved the backup up TA img to this folder and running the adb commands from this folder. It keeps on failing regardless. Please can anyone help me with this?

You need to change tabackup.img with the Real file name of your ta Backup

Bitti09 said:
You need to change tabackup.img with the Real file name of your ta Backup
Click to expand...
Click to collapse
so I shouldn't rename it ? All the guides say to rename it. I don't remember the original name of my backup since I renamed it to TAbackup.img

breakwaterr said:
so I shouldn't rename it ? All the guides say to rename it. I don't remember the original name of my backup since I renamed it to TAbackup.img
Click to expand...
Click to collapse
then
adb push TAbackup.img /data/local/tmp/TAbackup.img
and
adb shell dd if=/data/local/tmp/TAbackup.img of=/dev/block/bootdevice/by-name/TA
should work if you renamed the backup to TAbackup.img

Bitti09 said:
then
adb push TAbackup.img /data/local/tmp/TAbackup.img
and
adb shell dd if=/data/local/tmp/TAbackup.img of=/dev/block/bootdevice/by-name/TA
should work if you renamed the backup to TAbackup.img
Click to expand...
Click to collapse
I already renamed it to TAbackup.img and it doesn't work. it says no directory file error

breakwaterr said:
I already renamed it to TAbackup.img and it doesn't work. it says no directory file error
Click to expand...
Click to collapse
are you doing the commands in same folder as the TAbackup file is ?
If you use Windows its possible that windows is hiding the file extension so that you've possible renamed the file to TAbackup.img.img which is shown as TAbackup.img

Bitti09 said:
are you doing the commands in same folder as the TAbackup file is ?
If you use Windows its possible that windows is hiding the file extension so that you've possible renamed the file to TAbackup.img.img which is shown as TAbackup.img
Click to expand...
Click to collapse
OMG thank you so much man. renaming the file to only TAbackup worked. THANK YOU SO MUCH!!