Related
In the process of setting up a Honeycomb image on my SD card, I accidentally executed this:
Code:
iMac:desktop bedoig$ dd if=nookhoney02a.img of=/devrdisk1 bs=1m
as opposed to:
Code:
iMac:desktop bedoig$ dd if=nookhoney02a.img of=/dev[B][COLOR="Red"]/[/COLOR][/B]rdisk1 bs=1m
Question is, where did that disk image go, and how do I fix/erase it?
Thanks!
the image is in a folder in your root directory called 'devrdisk1' just delete it normally.
Cool. Thanks!
I am having an issue where my Nook Color will only boot to recovery.
What happened that possibly caused this: While booting up CM9 on emcc, I held the N button down to go into fattire's u-boot menu, I accidentally chose to Alternate boot and I have no alternate boot. The u-boot menu froze for several minutes. I then forced a hard power off by holding the power button. Since then the device will only boot to recovery regardless of the u-boot menu choices.
I have never dual booted and never ran any dual boot scripts. All of the attempts to fix this result in the Nook booting only to recovery. My Nook *will* boot from a bootable CW usd, that I have used for repair attempts of my emcc. I used the most updated CWR version possible. Additionally booting to a "Nookie Froyo" (remember that?) bootable card for repair attempts.
So to be clearer; I can boot to a bootable usd card, but all attempts to boot from emcc result in a boot into recovery.
I have tried:
Full wipe, reflash CM9, clear caches fix permissions.. etc. several times.
Full wipe reflash Cm7, then CM9 respectively.
Manually via adb, removing and installing CWR. (Results in boot to u-boot screen, all menu options lead to boot to blank screen)
Flashed back to stock. (Results in booting to stock recovery, and then fails)
Repartioned boot via flashable zip.
Restore to stock via flashable zip.
Recreated stock boot partitions manually via ADB, fdisk, dd etc..
Recreated all partitions via ADB, and checked the contents and the format structures and sectors.
From stock 8 failed boots, fails.
From stock adb 8 failed boot count. (**All results to revert to stock results in booting to stock recovery and then fails to update**)
Made sure the bootable usd I was useing was latest ver CWR
Tried an eyeballer CWR zip to fix exiting CW.
Installed latest experimental CM9 CWR to emcc and tried all above, and still only boots to recovery.
Made sure no encore or update zips were on the root of my sdcard.
Flashed several iterations of fattire's u-boot.bin, even tho I know it is installed with any encore update.zip
Tried all of the above several times and all the standard tricks to recover that I have learned over the past year.
**All of the above results in a Nook that wants to boot to recovery, any recovery, weather recovery is present or not.**
This leads me to consider the 2nd (rom) partition that can contains 2 (or more?) private files that can control boot that will look for recovery only. I belive BCB and another boot count file I cannot recall..
I would like to reset theses files, if indeed this is the problem, and bring back my Nooks emcc normal boot. Being private files they do not seem to be accessible via normal ADB comands and this is where I start to get over my head.
This is no longer my primary tablet, this is my Android learning device and it continues to be fun. However this issue has me stymied.
So.., If anyone with a deeper understanding of this issue could help me, that would be nice.
Thanks.
12
12paq said:
This leads me to consider the 2nd (rom) partition that can contains 2 (or more?) private files that can control boot that will look for recovery only. I belive BCB and another boot count file I cannot recall..
I would like to reset theses files, if indeed this is the problem, and bring back my Nooks emcc normal boot. Being private files they do not seem to be accessible via normal ADB comands and this is where I start to get over my head.
This is no longer my primary tablet, this is my Android learning device and it continues to be fun. However this issue has me stymied.
So.., If anyone with a deeper understanding of this issue could help me, that would be nice.
Thanks.
12
Click to expand...
Click to collapse
Try this from recovery... we'll use /data as a mount point but you'll really be mounting /rom (p2). First make sure that /data isn't aready mounted, then try this:
mount /dev/block/mmcblk0p2 /data
cd /data
ls
(make sure that this is in fact rom with the bcb and bootcnt so forth)
mv BootCnt BootCnt.bak
mv BCB BCB.bak
dd if=/dev/zero of=/data/BootCnt bs=1 count=4
dd if=/dev/zero of=/data/BCB bs=1 count=1088
reboot
Hope something like this works and doesn't make it worse, but maybe it's worth trying. If it doesn't work, you can always move the backup files back...
Okay, I have seen this sitting here and puzzled on it awhile. I have a couple links for you.
This first is someone who seems to have the same problem you do. They burst into internet-tears after everyone who was trying to help them got pissy and left. He was unfairly lashing out, but they were being kinda condescending.
http://forum.cyanogenmod.com/topic/...ry-boot-after-cm7-install-cant-get-to-the-os/
I only include it so you could see if the problems line up. This guy was about to give up, and this finally worked. There is a second pagebof posts, that is where I found what appears to be a solution..
The zip at this link (from XDA, of course. I don't know xawen but it is his/her work).
This will repair the B&N bootloader.
http://forum.xda-developers.com/showthread.php?t=958748
I hope this works. I crow to my old lady about how this device is basically unbrickable, and it would dash my hopes to see your emmc unrecoverable...
Edit: Note the clockwork version! You may have to enter into your device through the sd card and first flash the correct CWM versiin
Thanks for your time!
ok when I:
C:\android-sdk-windows\platform-tools>adb shell
~ # mount /dev/block/mmcblk0p2 /data
mount /dev/block/mmcblk0p2 /data
~ # cd /data
cd /data
/data # ls
ls
BCB
/data #
ut oh.
No other files show up.
I am wondering since this is not a restore to stock adventure, which of those missing files do I really need?
EDIT:
I'm to going to back up & reset bcb file and see how far that gets me.
C:\android-sdk-windows\platform-tools>adb shell
~ # mount /dev/block/mmcblk0p2 /data
mount /dev/block/mmcblk0p2 /data
~ # cd /data
cd /data
/data # ls
ls
BCB
/data # mv BCB BCB.bak
mv BCB BCB.bak
/data # dd if=/dev/zero of=/data/BCB bs=1 count=1088
dd if=/dev/zero of=/data/BCB bs=1 count=1088
1088+0 records in
1088+0 records out
1088 bytes (1.1KB) copied, 0.078582 seconds, 13.5KB/s
/data #
yeah, with backing up and resetting BCB as ^^ above, I still can only boot into recovery.
Edit:
I guess I need a Bootcnt file.
No dice on the recoveryfix zips? They are meant to repair issues where people cannot boot into recovery, but I believe it may replace the boot files you are looking for. Maybe not, but a couple threads I found had people with your exact problem, trying everything they could, and this turned out to work. I spent a little minute looking into it.
Edit: well, I downloaded and looked into thebzips, and it is the uboot.bin and the recImages which I guess you tried. If you know exact missing file (I located the mmcblkOp2 file, although it breaks down no further in root explorer) could i just pull it out of my device and email/pm it to you?
mateorod-
Yeah, thanks man. I did try all those links and zips before but, thanks for the effort.
I am actually very close to getting this done thru ADB. I have all the files needed. It's just not a simple push from ADB to get them there.
The good news is I am entrenched deep in new stuff and learning and having fun.
I'll keep you posted. Thanks again.
Yeah, I'm interested for sure. Good luck and tell us how you did it.
Fattire-
This what I achieved tonight:
~ # mount /dev/block/mmcblk0p2 /data
mount /dev/block/mmcblk0p2 /data
~ # cd /data
cd /data
/data # ls
ls
BCB BCB.bak BootCnt
/data # mv BootCnt BootCnt.bak
mv BootCnt BootCnt.bak
/data # dd if=/dev/zero of=/data/BootCnt bs=1 count=4
dd if=/dev/zero of=/data/BootCnt bs=1 count=4
4+0 records in
4+0 records out
4 bytes (4B) copied, 0.004242 seconds, 942B/s
/data # dd if=/dev/zero of=/data/BCB bs=1 count=1088
dd if=/dev/zero of=/data/BCB bs=1 count=1088
1088+0 records in
1088+0 records out
1088 bytes (1.1KB) copied, 0.018737 seconds, 56.7KB/s
/data # reboot
reboot
reboot returned
/data # exit
exit
C:\android-sdk-windows\platform-tools>adb reboot
I still can't boot normaly from emcc, it roles right into CWR.
Any other ideas?
Thanks for your time!
ran everything again as seen here:
C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
0000000000000000 recovery
C:\android-sdk-windows\platform-tools>adb shell
~ # mount /dev/block/mmcblk0p2 /data
mount /dev/block/mmcblk0p2 /data
~ # cd /data
cd /data
/data # ls
ls
BCB BCB.bak BootCnt BootCnt.bak tombstones
/data # dd if=/dev/zero of=/data/BootCnt bs=1 count=4
dd if=/dev/zero of=/data/BootCnt bs=1 count=4
4+0 records in
4+0 records out
4 bytes (4B) copied, 0.000702 seconds, 5.6KB/s
/data # dd if=/dev/zero of=/data/BCB bs=1 count=1088
dd if=/dev/zero of=/data/BCB bs=1 count=1088
1088+0 records in
1088+0 records out
1088 bytes (1.1KB) copied, 0.016968 seconds, 62.6KB/s
/data # reboot
reboot
reboot returned
/data # exit
exit
C:\android-sdk-windows\platform-tools>adb reboot
I still cannot get the devices to boot into anything but recovery.
Any help would be greatly appreciated.
Ok so this same exact thing happened to me as well. What I did to fix it was make a bootable sd recovery then slapped cm7 on it. Doesn't matter what one. Slapped meaning the flashable zip, after the sd was made to be a bootable recovery. Then wend though an formated everything but the emmc and then installed cm7 and bam it worked again. No problems still.
Sent from my PG06100 using Tapatalk
This all happened fro.m some thing that went wrong during a cm9 install? That's what caused mine.
Sent from my PG06100 using Tapatalk
Pm me if you need further instruction
Sent from my PG06100 using Tapatalk
halrulez said:
Pm me if you need further instruction
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Thanks, but I am guessing you did not read my op, I have tried that multiple times and ways. But thanks anyway.
12paq said:
Thanks, but I am guessing you did not read my op, I have tried that multiple times and ways. But thanks anyway.
Click to expand...
Click to collapse
Sorry I forgot to not that I used TWRP2.0 to do all this. Cwm has never seemed to format anything correctly. So make it a bootable sd recovery of twrp I tried cwm and it didn't work.
Sent from my PG06100 using Tapatalk
halrulez said:
Sorry I forgot to not that I used TWRP2.0 to do all this. Cwm has never seemed to format anything correctly. So make it a bootable sd recovery of twrp I tried cwm and it didn't work.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
Mmm.. well that's worth a try, at this point. I did use Neimath's experimental CWR that's more likely to not have problems with 2nd or Rom partition boot count files, but no go.
So, thanks.
Doh!
Double post.
I hope it works for you.
Sent from my PG06100 using Tapatalk
Any word on your nookie?
Sent from my PG06100 using Tapatalk
halrulez said:
Ok so this same exact thing happened to me as well. What I did to fix it was make a bootable sd recovery then slapped cm7 on it. Doesn't matter what one. Slapped meaning the flashable zip, after the sd was made to be a bootable recovery. Then wend though an formated everything but the emmc and then installed cm7 and bam it worked again. No problems still.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
so to be clear, so no one will fubar their boot partition, when you say, "format everything but emcc" you meant everything but boot and emcc, right?
Use:
The main purpose is to make a file that contains all data in android specific partition. This is really handy in case of dumping leak firmwares.
Pr-requirement:
- Rooted device.
- Knowledge of how to use adb or Terminal Emulator.
The first step of making dump files out of device partitions is to locate its mounting points..!!
So in our tutorial, we will make it in 2 sections. Section 1 for how to get mounting points, and section 2 for how to get partition dumped..
Keep in mind that this is xda-university; so my target is to show beginners how to do that manually, without the aid of any tool, so they can get the concept behind it.. OK let's begin..!!
Section 1:
Getting mounting pointsThere are several methods to achieve this, but we will discuss the easiest methods that give efficient information about the partition that you want to know its mounting point.
All these methods will be described using adb shell.
Way #1
Code:
adb shell
cat /proc/partitions
This one needs from you to figure out which block belong to which partition name.!!
{
"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"
}
Way #2
Code:
adb shell
ls -al /dev/block/platform/[B][COLOR="Blue"]dw_mmc[/COLOR][/B]/by-name
This one will give you info about the dev block names WITH their familiar names (i.e, boot, recovery, system... etc)
This command is not universal between devices, and you will need to gather its pieces (/dev/block/platform/dw_mmc/by-name).
How?
- In your device, use any explorer that can get you to the device root (personally I use ES Explorer, by pressing on "/" on navigation bar).
- Go to "/dev/block/platform/" folder
- Here you will see some files and folders, we need to open folders and search for the folder called "by-name" inside one of them; in my situation it was "dw_mmc" folder which has the folder "by-name" inside it.
- At the end, my targeted piece info will be (/dev/block/platform/dw_mmc/by-name)
- Now open adb shell and put that command..
Way #3
By pushing parted binary to /system/bin folder and run it (you can find it in attachment).
Code:
adb remount
adb shell "su" "" "mount -o remount,rw /system"
adb push parted /system/bin/parted
adb shell
chmod 0755 /system/bin/parted
parted /dev/block/[B][COLOR="Blue"]mmcblk0[/COLOR][/B]
print
Here, your mounting points will start with /dev/block/mmcblk0p* where (*) is the number shown in the table above for each partition.
example:
The hidden partition mounting point will be mmcblk0p10
The radio partition mounting point will be mmcblk0p7
The system partition mounting point will be mmcblk0p9
The recovery partition mounting point will be mmcblk0p6
and so on
Don't forget to "quit" the parted action after grasping your device mounting points.
N.B:
- You may need to run first:
Code:
adb shell
cat /proc/partitions
to know what is the initial name for your device partition.. In the example above, it was mmcblk0.
- Also to be able to do adb push to /system partition for parted binary, you will need insecure boot.img used in your ROM or adbd insecure installed in your device (Check this thread for that app), or just push parted binary manually by any root explorer and then fix permissions to rwxr-xr-x (755).
***
Section 2:
Dumping ROM partitionAfter locating the mounting point of the partition you want to dump, open adb shell command prompt and type:
Code:
adb shell
su
dd if=[B][COLOR="Blue"]/yourMountingPoint[/COLOR][/B] of=[B][COLOR="Green"]/yourDestination[/COLOR][COLOR="Red"]/partitionType[/COLOR][/B]
Let's say I want to take a dump out of system partition from above example. So the adb commands will be:
Code:
adb shell
su
dd if=[B][COLOR="Blue"]/dev/block/mmcblk0p9[/COLOR][/B] of=[B][COLOR="Green"]/sdcard[/COLOR][COLOR="Red"]/system.img[/COLOR][/B]
This may take a while to complete the dumping process, depending on the size of your dumped partition; so be patient..
Note:
If the partition is formatted as ext3/4 then the dumped partition will have .img as an extension.
Other partition dumps have different extensions; examples:
radio.bin
param.lfs
Sbl.bin
zImage (without extension)
***
Optional:
Read Partition ImageAfter dumping an image from android partition, you can mount it to extract a particular file for sharing, or the whole dump content in case the ROM chief wants to make a ROM out of dump files..
For Linux Users:
- Open terminal and type:
Code:
su -
mkdir -p /mnt/disk
mount -o loop [B][COLOR="Red"]yourImage.img[/COLOR][/B] /mnt/disk
cd /mnt/disk
ls -l
For Windows Users:
- Download LinuxReader from this site here.
- Open it -> Drives -> Mount Image -> Then choose your dumped image and hit Mount. A new driver will appear that contains all files inside the dumped image called "Linux native Volume 1". Just double click it to get inside the dumped image.
I hope you will find this tutorial beneficial,,,
Yours;
Actions Explanation
★ Tutorial Legends ★
In this post, I will try to explain the use of each binary used in the tutorial, so you can make sense of each action taken.
#1
Code:
adb shell
Run remote shell interactively, as if you are in linux terminal.
Click to expand...
Click to collapse
#2
Code:
cat /proc/partitions
cat binary is used to concatenate file(s) and print them to standard output display. In our example, it prints the content of partitions file which is found in proc folder to screen display.
Click to expand...
Click to collapse
#3
Code:
ls -al /dev/block/platform/dw_mmc/by-name
ls binary is used to list directory contents.
-al is the used option for ls which means to include entries that started with "." in long listing format. There are a lot of options for ls binary. You can always print ls --h to display help menu for other options available.
Click to expand...
Click to collapse
#4
Code:
adb remount
Remounts the /system partition on the device read / write. This has been disabled in some devices (those with secure boot image); so you need to make sure that you have patched adbd that can run this command effectively.
Click to expand...
Click to collapse
#5
Code:
su
Used to get super-user privilege.
Click to expand...
Click to collapse
#6
Code:
mount -o remount,[B][COLOR="Red"]rw[/COLOR][/B] /system
Specific command to mount the /system partition on the device read / write (rw).
If you change rw to ro, you will get /system partition mounted as read only.
Click to expand...
Click to collapse
#7
Code:
adb push parted /system/bin/parted
adb push is used to copy file/dir from your local computer to android device. The usual format is adb push <local> <remote>
Click to expand...
Click to collapse
#8
Code:
chmod 0755 /system/bin/parted
chmod binary is used to set permissions for the specified file/dir.
The number after chmod is the permission used. See the next box for better understanding of chmod formatting:
Code:
[CENTER][B][COLOR="Red"]----------------
| CHMOD SCHEME |
----------------[/COLOR][/B][/CENTER]
[B] r w x[/B]
[B]4 2 1 [COLOR="Green"]= 7 (Full Permissions)[/COLOR][/B]
User ( ) ( ) ( ) [B][COLOR="Green"]--> 2nd digit[/COLOR][/B]
Group ( ) ( ) ( ) [B][COLOR="Green"]--> 3rd digit[/COLOR][/B]
Other ( ) ( ) ( ) [B][COLOR="Green"]--> 4th digit[/COLOR][/B]
Special UID GID STK
( ) ( ) ( ) [B][COLOR="Green"]--> 1st digit, ignored on most cases or put 0[/COLOR][/B]
In the above example, it is set to 0755 which means the following scheme:
Code:
[B] r w x[/B]
[B]4 2 1[/B]
User ([B][COLOR="Red"]*[/COLOR][/B]) ([B][COLOR="Red"]*[/COLOR][/B]) ([B][COLOR="Red"]*[/COLOR][/B]) [B][COLOR="Green"]--> This equals to 7 (rwx)[/COLOR][/B]
Group ([B][COLOR="Red"]*[/COLOR][/B]) ( ) ([B][COLOR="Red"]*[/COLOR][/B]) [B][COLOR="Green"]--> This equals to 5 (r-x)[/COLOR][/B]
Other ([B][COLOR="Red"]*[/COLOR][/B]) ( ) ([B][COLOR="Red"]*[/COLOR][/B]) [B][COLOR="Green"]--> This equals to 5 (r-x)[/COLOR][/B]
Special UID GID STK
( ) ( ) ( ) [B][COLOR="Green"]--> This equals to 0 (---)[/COLOR][/B]
As you can see, if you said 0755, it will be as same as saying ---rwxr-xr-x
Click to expand...
Click to collapse
#9
Code:
dd if=/dev/block/mmcblk0p9 of=/sdcard/system.img
dd binary is used to copy a file with converting and formatting.
if means input file; here we pointed to the whole partition, not specific file.
of means outputting file to specific destination path; here it is to sdcard with system.img name.
Click to expand...
Click to collapse
#10
Code:
mkdir -p /mnt/disk
mkdir binary is used to make folder dir.
-p is mkdir option which means to create folder with sub-folder at the same time. Here we want to create mnt folder that contains disk sub-folder in it. If the folder and or sub-folder(s) are already exists, it will not give error but nothing will be created.
Click to expand...
Click to collapse
#11
Code:
mount -o loop yourImage.img /mnt/disk
This is linux way to mount images into specific directory (/mnt/disk in this example).
Click to expand...
Click to collapse
#12
Code:
cd /mnt/disk
cd used to get inside specific dir path.
Click to expand...
Click to collapse
#13
Code:
ls -l
ls binary is used to list directory contents as described above.
-l is the used option for ls which means to list contents in long listing format.
Click to expand...
Click to collapse
Cheers
another way to get common names
on way #2, I've often used:
Code:
cat /proc/emmc
on a few devices to reveal similar info.
Rob
can i able to mount boot.img in android itself...actually i wanted to extract boot.img frm mobile without any tools or without the help of PC...if there be any possibilities..??
hasan4791 said:
can i able to mount boot.img in android itself...actually i wanted to extract boot.img frm mobile without any tools or without the help of PC...if there be any possibilities..??
Click to expand...
Click to collapse
if you mean extract to modify boot.img, then I don't think there is away to do that from device itself in the moment..
if you mean dumping boot.img then yes you can, just install terminal emulator from Google play and you can run adb shell commands directly from the device
Great guide hopefully makes it easier for us to get dumps! if you add logcats etc, i find they have trouble executing "adb logcat >> log.txt" -.-
also you should teach them the easy tar method, so while booted "tar -c /system/* >> /sdcard/system.tar" or via adb shell
ricky310711 said:
Great guide hopefully makes it easier for us to get dumps! if you add logcats etc, i find they have trouble executing "adb logcat >> log.txt" -.-
also you should teach them the easy tar method, so while booted "tar -c /system/* >> /sdcard/system.tar" or via adb shell
Click to expand...
Click to collapse
Yup that is possible and easy to extract but it is only for partitions that is shown in android os,,, you can't use it for boot.img, sbl.bin, modem.bin...etc right
majdinj said:
Yup that is possible and easy to extract but it is only for partitions that is shown in android os,,, you can't use it for boot.img, sbl.bin, modem.bin...etc right
Click to expand...
Click to collapse
ofcoarse, i actually had a project going where it detects all partitions(modems, boot.img, system etc..) that archives itself into a .zip
it was going well until i did something in the script, now it only works on the s3 it shall be continued one day!
Such great tutorial, this is definitely going to come in handy for me. I have a question, how can you dump (extract) a bootloader? Can i use the same method as dumping the ROM?
Could you explain how to extract stock recovery image please?
Sent from my HTC One using xda app-developers app
Where did the parted binary come from?
For Gods Sake
http://forum.xda-developers.com/sho...IDE] Unpack/repack ext4 Android system images
http://forum.xda-developers.com/sho... Creator (deployable over all kernel sources)
http://forum.xda-developers.com/sho...ipt]Backup all paritions on i9505 to odin rom
http://forum.xda-developers.com/sho...al 4.3 TW Custom Rom/ The ORIGINAL WIFI TRICK
... use Forum Search Engine first, then start asking all your 'important' questions
¤ GT-I9505 - powered by KitKat ¤
insink71 said:
on way #2, I've often used:
Code:
cat /proc/emmc
on a few devices to reveal similar info.
Rob
Click to expand...
Click to collapse
Thx for this. On my HTC One there is no "by-name" folder. It only has "by-num". cat /proc/emmc works fine though.
Cheers.
I also wrote a guide, It just using the "by-name"
and needs root
[HOWTO] dump your rom
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/storage/extSdCard/system.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/storage/extSdCard/recovery.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/param of=/storage/extSdCard/param.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/storage/extSdCard/boot.img
Hi,
I tried this on my I-9505G. It is NOT rooted, so I thought I could enter the system through Clockworkmod Recovery.
I did it, but at first I didn't mount the DATA partition (later on I did through CWM Recovery); I still ran the command:
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/data/media/TEST/system.img
Thought I hadn't mounted anything, the media folder was still there, I only created the TEST folder.
After the image was created I typed the "ls" command and the system.img file was in /data/media/TEST/.
I then rebooted once again in CWM and ran the "adb shell" command once again, I entered /data/media/ e neither the img file nor the TEST folder I had created were there.
My question is: where have they gone?? Are they still occupying some of my space or they just got deleted automatically when I rebooted??
Please let me know as I'd like to free that extra unuseful 1.2 Gb system.img file.
Anyway, just as side information, I later on mounted the /data through CWM interface and was able to see the folders ("/data/media/0/") I can see by plugging the phone normally to the computer. I then dumped the image.
I have some other questions:
I can I mount the /data folder (or the external SD) via command?
What extention should I give to the other partitions? (All of them)
Why did you say that it's MANDATORY that the phone be rooted if it can be done this way?
Are the images I'm dumping flashable through fastboot?
Thank you all for your time!
Anybody? Please.
•I can I mount the /data folder (or the external SD) via command?
I have not been able to find the SD card in clockwork on the I9505G, hence one of my rooting procedures send the root file vi "adb sideload".
I might be able to pull the data from the phone but the clockwork recovery is still not working 100% when fastbooting it.
•What extention should I give to the other partitions? (All of them)
.img are fine.
•Why did you say that it's MANDATORY that the phone be rooted if it can be done this way?
currently it is required that the phone be unlocked. Something need to be fixed in clockwork to make it work any other way.
•Are the images I'm dumping flashable through fastboot?
They should be, but I have not been able to flash anything on the I9505G vi fastboot because of the secure boot.
without a full official image this make my playing around a little concerning (slowing me down).
I will look into this at my leisure. I would love to be able to pull a rom off a phone with only unlocking it.
I will test some stuff using my old galaxy nexus.
I actually dumped everything WITHOUT being rooted. I only unlocked the bootloader... So it works.
Further, I tried to run "fastboot boot recovery.img" with recovery.img being the image file I dumped. The phone froze and I had to pull the battery... So I assume they're not flashable as well, though I'd like other feedbacks.
I've not clearly understood what "secure boot" means. Any guide or wiki?
Thanks!
---------- Post added at 06:56 PM ---------- Previous post was at 06:55 PM ----------
I actually dumped everything WITHOUT being rooted. I only unlocked the bootloader... So it works.
Further, I tried to run "fastboot boot recovery.img" with recovery.img being the image file I dumped. The phone froze and I had to pull the battery... So I assume they're not flashable as well, though I'd like other feedbacks.
I've not clearly understood what "secure boot" means. Any guide or wiki?
Thanks!
Hey, great guide! I need some help but. I can't retrieve the common names / labels of my devices partitions. It's a GT-i8150 and there is no 'by-name' sub directory. Furthermore, parted does not work on mmcblk0 for some reason (unable to satisfy partition restraints or something). I also have no emmc file in proc.
Does anyone know how some other methods for getting the names of the partitions?
EDIT:
Another question - using ADB shell, is it possible to dump a partition straight from the phone onto the computers hard drive? My little 2GB sd card isn't coping! Thanks
a very basic but good guide
Sent from my GT-P1000 using xda app-developers app
Typically users beat me to the punch on things such as this. But no one has yet to do so, so here it is.
How to extract your param partition:
Code:
It's located in /dev/block/sda4. On device terminal or in adb terminal as root run,
dd if=/dev/block/sda4 of=/sdcard/param.bin bs=4096
Now that your param partition has been dumped you can copy it off the device as I do to work with it. Untar it with this command on linux:
Code:
mkdir /param
cd param
tar xf /path/to/param.bin
Once its untared to the param directory, you will see the contents. logo.jpg being the file you wish to change.
Once you have found/made a proper logo/splash in the proper resolution of 1440x2560 copy it to the param folder overwriting the old logo.jpg, and run this command in the param folder to pack it back up:
Code:
tar cf - `ls | sort -t.` > /path/to/where/you/want/to/save/param.bin
NOTE: The param partition has limited space, so keep this in mind. I have successfully used a 400kb jpeg with out issues. I wouldn't go much more then that.
Place the param.bin back on your sdcard and run the following to flash it:
Code:
dd if=/sdcard/param.bin of=/dev/block/sda4 bs=4096
Reboot and enjoy.
Users wishing to deploy all these commands on device (if you don't run linux) here is a script I made, tested and working to do so. Place files on device accordingly.
Code:
#!/sbin/busybox sh
# Extracting param partition
dd if=/dev/block/sda4 of=/sdcard/param.bin bs=4096
mkdir /sdcard/param
cd /sdcard/param
tar xf /sdcard/param.bin
# Replaceing logo.jpg, repacking and writing back to device
cp -f /sdcard/logo.jpg /sdcard/param/logo.jpg
rm -f /sdcard/param.bin
tar cf - `ls | sort -t.` > /sdcard/param.bin
dd if=/sdcard/param.bin of=/dev/block/sda4 bs=4096
Attached you will find a flashable zip of a custom boot screen i made. You're all welcome to use. As well as the Stock param.bin in case users wish to go back. And the image I made for the custom boot splash I'm attaching.
-Mr. X- said:
Typically users beat me to the punch on things such as this. But no one has yet to do so, so here it is.
How to extract your param partition:
Code:
It's located in /dev/block/sda4. On device terminal or in adb terminal as root run,
dd if=/dev/block/sda4 of=/sdcard/param.bin bs=4096
Now that your param partition has been dumped you can copy it off the device as I do to work with it. Untar it with this command on linux:
Code:
mkdir /param
cd param
tar xf /path/to/param.bin
Once its untared to the param directory, you will see the contents. logo.jpg being the file you wish to change.
Once you have found/made a proper logo/splash in the proper resolution of 1440x2560 copy it to the param folder overwriting the old logo.jpg, and run this command in the param folder to pack it back up:
Code:
tar cf - `ls | sort -t.` > /path/to/where/you/want/to/save/param.bin
NOTE: The param partition has limited space, so keep this in mind. I have successfully used a 400kb jpeg with out issues. I wouldn't go much more then that.
Place the param.bin back on your sdcard and run the following to flash it:
Code:
dd if=/sdcard/param.bin of=/dev/block/sda4 bs=4096
Reboot and enjoy.
Users wishing to deploy all these commands on device (if you don't run linux) here is a script I made, tested and working to do so. Place files on device accordingly.
Code:
#!/sbin/busybox sh
# Extracting param partition
dd if=/dev/block/sda4 of=/sdcard/param.bin bs=4096
mkdir /sdcard/param
cd /sdcard/param
tar xf /sdcard/param.bin
# Replaceing logo.jpg, repacking and writing back to device
cp -f /sdcard/logo.jpg /sdcard/param/logo.jpg
rm -f /sdcard/param.bin
tar cf - `ls | sort -t.` > /sdcard/param.bin
dd if=/sdcard/param.bin of=/dev/block/sda4 bs=4096
Attached you will find a flashable zip of a custom boot screen i made. You're all welcome to use. As well as the Stock param.bin in case users wish to go back. And the image I made for the custom boot splash I'm attaching.
Click to expand...
Click to collapse
Very nice! Thanks
If your phone is showing the "Custom (unlocked)" icon, will this override that?
Does this overwrite the carrier boot screen.
cambunch said:
If your phone is showing the "Custom (unlocked)" icon, will this override that?
Click to expand...
Click to collapse
In download mode? no it will not.
Thoth33 said:
Does this overwrite the carrier boot screen.
Click to expand...
Click to collapse
If the carrier put their logo in the param yes. if its a kernel boot animation no.
-Mr. X- said:
In download mode? no it will not.
Click to expand...
Click to collapse
During a regular boot. This is the first image that you see when powering on a phone, correct?
cambunch said:
During a regular boot. This is the first image that you see when powering on a phone, correct?
Click to expand...
Click to collapse
correct
This looks awesome! I'll have to prep an image to try out!
Edit:
After giving this a try, I appear to have managed to brick my phone. It seems that the only thing I can boot into is Download mode, and reflashing the firmware has not fixed this. Any ideas on how to resolve this? Much appreciated!!
Edit 2:
I saved myself with the Smart Sync (or whatever it's called) program on my PC. I was only able to do it though because I had written down the "Serial Number" for "just in case" purposes some time ago. I'm actually going to do a separate post to make this point for anyone who has similar issues but not from modifying boot splash.
The attached zip files work perfect on my S6 Edge. I unzipped the file, copied param.bin to my sdcard and used dd from the shell. Still trying to get a custom image to work. Getting a grey screen when I replace logo.jpg with my own. Any ideas?
Thanks again for sharing this -Mr. X-.
@-Mr. X-
Could you tell me which software you used to make your custom logo.jpg? I'm using photoshop on mac, however, everything made on this leads to the gray screen.
Thank you.
Can you please add 'powered by android' with new bugdroid icon on the bootsplash
Sent from my SM-G920I using Tapatalk
Will this work on the 925T edge?
I used Gimp, then i opened the picture in Microsoft Paint and re-saved it. I also ran into this but didn't know if Gimp was the cause but., this method worked for me.
It should also work on the edge but ensure your param partition is sda4 just to be safe.
-Mr. X- said:
I used Gimp, then i opened the picture in Microsoft Paint and re-saved it. I also ran into this but didn't know if Gimp was the cause but., this method worked for me.
It should also work on the edge but ensure your param partition is sda4 just to be safe.
Click to expand...
Click to collapse
Will do
The grey screen seems to be an issue while packing the files back with tar on Mac. I used photoshop on mac to make logo.jpg and packed it using tar on ubuntu. Works on 925I. And sda4 is the partition on edge as well for the bootsplash. Thanks for the help.
How to you get this to work little confused. Do you unzip the file or do you flash the zip
UAAO
Enviado desde mi SM-N910C mediante Tapatalk
Confuse bro .
Splaind tutorial
Can seone explaim how to change the splash screen thanls
ob1silvia said:
Can seone explaim how to change the splash screen thanls
Click to expand...
Click to collapse
Hi,
You can flash the zip file in post 1, with custom recovery..
Work perfect here, thx @-Mr. X-
How to backup - let's say boot - partition to a fastboot flashable file (*.img) format?
For example:
Code:
dd if=/dev/block/platform/hi_mci.0/by-name/boot of=/sdcard/boot.img
and so on.
Kostyan_nsk said:
For example:
Code:
dd if=/dev/block/platform/hi_mci.0/by-name/boot of=/sdcard/boot.img
and so on.
Click to expand...
Click to collapse
Thanks. So fastboot is using dd images. Please do confirm.
Regards.
You can use only boot and recovery images extracted by dd for flashing via fastboot.
Kostyan_nsk said:
You can use only boot and recovery images extracted by dd for flashing via fastboot.
Click to expand...
Click to collapse
Thanks
Kostyan_nsk said:
For example:
Code:
dd if=/dev/block/platform/hi_mci.0/by-name/boot of=/sdcard/boot.img
and so on.
Click to expand...
Click to collapse
I have done the backup to the image file as you have suggested.
I have copied image file to the linux computer, but when I try to mount the image file I get:
mount -o loop boot_orig_B830.img /mnt/boot/
mount: /dev/loop0 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/loop0,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so.
What is the file system for this image?
Length of the image file is:
ls -l boot_orig_B830.img
-rw-rw-r-- 1 test test 16777216 Lis 13 22:04 boot_orig_B830.img
For Linux: google "unpackbootimg", "gunzip" and "cpio".
For Windows: google "AndImgTool".