Related
I am trying to install MintLinux, but problem persists on normal ubuntu install disk.
Below is the output of fdisk
Code:
[email protected] ~ $ sudo fdisk -l
Disk /dev/sda: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xffffffff
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 102400 7 HPFS/NTFS
Partition 1 does not end on cylinder boundary.
/dev/sda2 13 13643 109478946 7 HPFS/NTFS
Partition 2 does not end on cylinder boundary.
/dev/sda3 20048 77825 464101785 7 HPFS/NTFS
Partition 3 does not end on cylinder boundary.
/dev/sda4 13644 20047 51440130 83 Linux
Partition table entries are not in disk order
Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xc4ee2648
Device Boot Start End Blocks Id System
/dev/sdb1 1 121602 976759808 7 HPFS/N
I followed thisgrub install guide after the install from a live cd.
The problem is grub does not install after the OS install. Windows will load up automaticlly, the install is fine and I can see the files from the live cd.
Code:
[email protected] ~ $ sudo grub
Probing devices to guess BIOS drives. This may take a long time.
[ Minimal BASH-like line editing is supported. For
the first word, TAB lists possible command
completions. Anywhere else TAB lists the possible
completions of a device/filename. ]
grub> find /boot/grub/stage1
find /boot/grub/stage1
(hd0,3)
grub> root (hd0,3)
root (hd0,3)
grub> setup (hd0)
setup (hd0)
Checking if "/boot/grub/stage1" exists... yes
Checking if "/boot/grub/stage2" exists... yes
Checking if "/boot/grub/e2fs_stage1_5" exists... yes
Running "embed /boot/grub/e2fs_stage1_5 (hd0)"... 17 sectors are embedded.
succeeded
Running "install /boot/grub/stage1 (hd0) (hd0)1+17 p (hd0,3)/boot/grub/stage2 /boot/grub/menu.lst"... failed
Error 22: No such partition
grub>
Above is the output of the guide for installing grub. It seems to file creating the grub menu.lst file, which is not found in the /boot/grub/ directory.
Thanks for any help.
Maybe your linux isn't using legacy Grub, (which would explain why you don't see the menu.lst file) it could be using grub2.
It works a bit differently.
http://www.dedoimedo.com/computers/grub-2.html
Edit--
Well if this is based off of Ubuntu 9.10 then it has grub2. It looks like there are 2 drives, which one has the windows install and which has the linux ?
Its possible they are both sata drives, and it's possible that you have the BIOS set to boot from the windows drive. (of course they could both be on the same drive).
I had a problem sort of like this, but I actually got the GRUB menu and then it would poo poo.
Yeah, yeah. Sounds like a million other posts. I am a unix/linux sort of guy, so I'm quite familiar with navigating and working in *nix based operating systems.
Here is the synopsis:
Without an SD card, the device will not boot. I can hear the USB cycle and I'm stuck at a black screen. Sounds normal so far.
After booting up CWM, I can adb in. My first step was to check devices.
/dev/block # cd /dev/block
cd /dev/block
/dev/block # ls
ls
loop0 loop5 mmcblk0p2 ram10 ram15 ram6
loop1 loop6 mmcblk1 ram11 ram2 ram7
loop2 loop7 platform ram12 ram3 ram8
loop3 mmcblk0 ram0 ram13 ram4 ram9
loop4 mmcblk0p1 ram1 ram14 ram5
As you can see, there are a few missing block devices. I proceeded to mount each of these. Only mmcblk0p1 had anything on it: the boot partition, as I expected. Mmcblk1 was the device name for the SDCard, which deviates from what I would have expected. Blk0p2 contained nothing and was not mountable.
Next, I tried to do a 'mknod' to create the devices. This was successful to a degree, but did not actually create working devices. I attempted to mkfs.ext2 on them, that failed. For grins, I tried it on p1 and p2. The only one that worked was p1.
At this point, I decided to try and flash the boot.img I retrieved from here: "mrm3.net/nook-color-recover-any-bricked-device/" and see what I could do to get the device up and running - any self booting would be an improvement, I thought. This too failed. The 'dd' was successful and the partition now contained boot info, but when i tried to boot up, I still received a black screen:
/dev/block # dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
144522+0 records in
144522+0 records out
73995264 bytes (70.6MB) copied, 44.914978 seconds, 1.6MB/s
/dev/block #
When I try to flash ANY rom, I get failures - obviously because there's no place for them to flash to.
'dmesg' doesn't contain any useful information. The device seems hosed. The last rom I was running was Cyanogen nightly #69, which wouldn't allow me to mount SDCard or do anything useful. When I tried to install nightly #80, I found that the device was no longer usable.
Hopefully this was thorough enough, I refrained from typing out the obvious stuff, but please feel free to suggest things. I'm stumped. I still think it can be saved, but I don't have a ton of hope.
Thanks a lot for giving this a read. I really hope someone can help out.
--
j.k
Ill add you to the list with everyone else here of people who are more advanced than I. But one of the fist things I learned about the Nook is that its pretty much impossible to brick. I'm sure someone from the list will be by to help soon.
I really hope so.
Logically, if the device nodes can be recreated, I could flash a new mod in. Perhaps I'm going about that the wrong way.
sangandongo said:
Next, I tried to do a 'mknod' to create the devices. This was successful to a degree, but did not actually create working devices. I attempted to mkfs.ext2 on them, that failed. For grins, I tried it on p1 and p2. The only one that worked was p1.
Click to expand...
Click to collapse
Have you verified that the partition table is actually intact/correct? No point trying to create device nodes if the underlying devices aren't there. What does "fdisk -l /dev/block/mmcblk0" give you, and how does it compare to the standard layout?
Maybe check notes with the OP of this thread -- appears that both of you have essentially the same problem.
jll544 said:
Have you verified that the partition table is actually intact/correct? No point trying to create device nodes if the underlying devices aren't there. What does "fdisk -l /dev/block/mmcblk0" give you, and how does it compare to the standard layout?
Maybe check notes with the OP of this thread -- appears that both of you have essentially the same problem.
Click to expand...
Click to collapse
Sorry, I should have included that earlier. The partition table is b0rked. I also had attempted applying the zips from the [ZIP][RECOVERY] EMMC Recovery Repair thread to no avail.
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
4 heads, 16 sectors/track, 242432 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 15260 488312 b Win95 FAT32
/dev/block/mmcblk0p2 15261 242432 7269504 83 Linux
Not to sounds like a smartass (or maybe a dumbass) but have you tried to restore back to stock?
Yes. In my initial post, I stated that no restoring via zip works.
Currently I am attempting to rebuild the partition table as mine is hosed. I get the following output though, which is troubling by comparison to what I should be seeing:
~ # busybox fdisk /dev/block/mmcblk0
busybox fdisk /dev/block/mmcblk0
The number of cylinders for this disk is set to 242432.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
4 heads, 16 sectors/track, 242432 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 15260 488312 b Win95 FAT32
/dev/block/mmcblk0p2 15261 242432 7269504 83 Linux
Command (m for help): d
d
Partition number (1-4):
Right, virtually all .zip restore files are filesystem-level recovery and assume that the partition table is unchanged.
Try forcing the geometry using "fdisk -H 255 -S 63 /dev/block/mmcblk0"
Before I write this, does the following look like what you'd expect? I mean, it makes sense considering...
Code:
~ # fdisk -H 255 -S 63 /dev/block/mmcblk0
fdisk -H 255 -S 63 /dev/block/mmcblk0
Code:
Command (m for help): p
p
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 61 488312 b Win95 FAT32
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 1, 1) logical=(0, 0, 17)
Partition 1 has different physical/logical endings:
phys=(1023, 3, 16) logical=(60, 202, 14)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 61 966 7269504 83 Linux
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(1023, 3, 16) logical=(60, 202, 15)
Partition 2 has different physical/logical endings:
phys=(1023, 3, 16) logical=(965, 205, 8)
Partition 2 does not end on cylinder boundary
jll544 said:
Right, virtually all .zip restore files are filesystem-level recovery and assume that the partition table is unchanged.
Try forcing the geometry using "fdisk -H 255 -S 63 /dev/block/mmcblk0"
Click to expand...
Click to collapse
What he said. Texas Instrumentss OMAP devices such as the nook require that media, whether sd, mmc, etc, be formatted with particular geometry. One that's set up, you can create the partitions normally and forget it ever happened. Remember that the first partition should be FAT, and this is where the kernel (uImage) and ramdisk (uRamdisk) as well as bootloader (u-boot.bin) and pre-bootloader (mlo) go.
See here for more info.
I believe the version of busybox available to me on this 3.0.2.8 CWR SD image is too old to accomplish what the instructions on this post state: http://forum.xda-developers.com/showpost.php?p=13971291&postcount=110
I've been unable to find a bundle of the binaries yet, but I'm still looking. That being said, I changed the geometry of the partition table and wrote the changes, then tried to dd again - fail.
sangandongo said:
Before I write this, does the following look like what you'd expect? I mean, it makes sense considering...
Code:
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 61 488312 b Win95 FAT32
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(0, 1, 1) logical=(0, 0, 17)
Partition 1 has different physical/logical endings:
phys=(1023, 3, 16) logical=(60, 202, 14)
Partition 1 does not end on cylinder boundary
<snip>
Click to expand...
Click to collapse
You mean you wrote the partition table as shown above? That won't work. You need to run fdisk with the corrected geometry, delete the existing partitions, and create new ones. Those warnings say that your partition LBA's are still aligned to the incorrect geometry.
What happens when remove all if the partitioning on the emmc, format it, and repartition it? For some reason ive found linux has a tendency to corrupt storage bits of memory chips altogether and the only way to restore was to completely start over clean. Also, anyone tested for bad blocks? One of my laptops decided to take a **** and the only way I'm able to install an os on it is by installing ubuntu on half the hard drive. Maybe if it is bad blocks we could repartition around them?
Sent from my PC36100 using Tapatalk
RileyGrant said:
What happens when remove all if the partitioning on the emmc, format it, and repartition it? For some reason ive found linux has a tendency to corrupt storage bits of memory chips altogether and the only way to restore was to completely start over clean. Also, anyone tested for bad blocks? One of my laptops decided to take a **** and the only way I'm able to install an os on it is by installing ubuntu on half the hard drive. Maybe if it is bad blocks we could repartition around them?
Click to expand...
Click to collapse
Save the FUD for somewhere else....
RileyGrant said:
For some reason ive found linux has a tendency to corrupt storage bits of memory chips altogether and the only way to restore was to completely start over clean.
Click to expand...
Click to collapse
LOL, just about any operating system will write an unsuitable partition table if the end user commands it to do so. No, the OP has omitted details about what he did to get into his situation, but there is no chance it just happened on its own (i.e., his partition layout is technically valid but unbootable by OMAP). If we're going to hazard wild guesses, I'd say he was trying to install Backtrack or some other non-Android Linux distribution.
Hahah I only used linux as an example because ubuntu its all I have run for a coupe years now. but you sir are completely oblivious too the fact that evo users, thunderbolt users and now nook users have reported the same issue and symptoms, always on gingerbread. A self corruption of internal memory.
Sent from my PC36100 using Tapatalk
jll544 said:
LOL, just about any operating system will write an unsuitable partition table if the end user commands it to do so. No, the OP has omitted details about what he did to get into his situation, but there is no chance it just happened on its own (i.e., his partition layout is technically valid but unbootable by OMAP). If we're going to hazard wild guesses, I'd say he was trying to install Backtrack or some other non-Android Linux distribution.
Click to expand...
Click to collapse
In this case, I believe it was caused either by "fixing permissions" while using Rom Manager, or by doing it in CWM. This was in an attempt to get out of CM7 nightly #69, which all but rendered my system inoperable.
I agree with you though: there's likely no reason why linux would cause corruption on a disk. If anything, an app might be to blame, but it would have to explicitly do so.
That aside, I am very close to getting my Nook fixed. I rebuilt the partition table this morning after loading busybox 1.18 onto my SD card. ran 'fdisk' with the proper geometry, deleted the existing partitions, built each out to standard specs, then changed the filesystem id for each. After that I did a mkfs.vfat and mke2fs on the appropriate partitions and wrote the configuration.
I rebooted, did a dd of a 1.0.1 boot image to mmcblk0p1 and of a system image to mmcblk0p5 and tried to boot, but I'm still getting a black screen.
Here is my current partition table after I resized it and marked the partitions with their respective types:
Code:
/busybox fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 7944 MB, 7944011776 bytes
255 heads, 63 sectors/track, 965 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 9 72261 c Win95 FAT32 (LBA)
/dev/block/mmcblk0p2 10 18 72292+ c Win95 FAT32 (LBA)
/dev/block/mmcblk0p3 19 56 305235 83 Linux
/dev/block/mmcblk0p4 57 965 7301542+ 5 Extended
/dev/block/mmcblk0p5 57 114 465853+ 83 Linux
/dev/block/mmcblk0p6 115 789 5421906 83 Linux
/dev/block/mmcblk0p7 790 834 361431 83 Linux
/dev/block/mmcblk0p8 835 965 1052226 c Win95 FAT32 (LBA)
I made the Fat32 Partitions using mk.vfat and the linux partitions with mke2fs -j -L <label>. Something still just isn't right.
Blah. I get so OCD about this sort of ****. I need to just go outside and play, this is driving me nuts.
sangandongo said:
Blah. I get so OCD about this sort of ****. I need to just go outside and play, this is driving me nuts.
Click to expand...
Click to collapse
It's not booting because you're missing your /rom partition. There is no data in /mmcblk0p2, which init calls for all your device info. Hopefully you have a backup of that as well. Without it, you won't be able to run any roms with your nook color.
And unfortunately that is a partition that is not good to share with anyone else besides each individual nook owner because is contains all the unique Device identifiers for your Nook. If two people would have the same Device info and you're both logged into your B&N stock, it will error out on the B&N server side and de-register your device and the other person as well.
If you need further guidance, PM me and I'll see what I can do to help to resolve your /rom partition issue.
-Racks
I DD'd every partition off my friend's Nook. Every one. Just to see if I could get this puppy running. Still black.
OK, so I have been at this for a while now, trying to figure out how to pull boot.img. We need this in order to get a custom recovery image made.
The problem is that most of the help that's out there refers to doing a dump based on identifying the proper /proc/MTD. It's never that simple though. This phone doesn't have it (and we don't have a map of where to go from here).
Here is the partition info:
Code:
major minor #blocks name
7 0 13545 loop0
7 1 202829 loop1
7 2 31217 loop2
7 3 18743 loop3
7 4 13545 loop4
179 0 15679488 mmcblk0
179 1 2048 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 7168 mmcblk0p3
179 4 1 mmcblk0p4
179 5 28672 mmcblk0p5
179 6 204800 mmcblk0p6
179 7 4096 mmcblk0p7
179 8 24576 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 4096 mmcblk0p10
179 11 4096 mmcblk0p11
179 12 1024000 mmcblk0p12
179 13 1572864 mmcblk0p13
179 14 12288 mmcblk0p14
179 15 12599296 mmcblk0p15
179 16 15622144 mmcblk1
179 17 15621120 mmcblk1p1
254 0 13545 dm-0
254 1 202828 dm-1
254 2 31216 dm-2
254 3 18742 dm-3
254 4 13545 dm-4
Can anyone with a few more years on me in this racket give me a heads up on this? Perhaps a mapping for us to get started? Yeah, I know I'm totally wet behind the ears, but someone has to get this thing rolling. Hopefully that doesn't mean I'll be the first to brick my phone (had a close call tonight).
See what's mounted by typing "mount" first. It'll show you what mmcblk0pX maps to what (mounted, that is).
thecubed said:
See what's mounted by typing "mount" first. It'll show you what mmcblk0pX maps to what (mounted, that is).
Click to expand...
Click to collapse
ok, so here was the output (of what i assume is the relevant part):
Code:
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mmcblk0p12 /system ext3 ro,relatime,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p6 /cache ext3 rw,nosuid,nodev,relatime,errors=continue,data=ordered 0 0
/dev/block/mmcblk0p5 /persist ext3 rw,nosuid,nodev,relatime,data=ordered 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/extasec tmpfs rw,relatime,mode=755,gid=1000 0 0
So 12 is system, 13 is data, 6 is cache, and 5 is persist. What I'm not seeing is boot. Am I missing anything here?
To find unnamed partitions, you might want to dump them to your SD card and try mounting the partitions on your PC.
You can copy a partition to a file on your SD card by using "dd if=/dev/block/mmcblk0pX of=/sdcard/mmcblk0pX.img bs=1024"
Then on your desktop, you can try running fdisk to see what the partition type is and issue a "mkdir /mnt/test" then "mount -o loop -t <type of partition from fdisk> /path/to/mmcblk0pX.img /mnt/test".
From there, you should be able to investigate what's in those partitions by poking around in /mnt/test on your desktop. Once you're done, "umount /mnt/test" to close the image file.
Referring to your list of partitions and sizes, partitions of 2048 blocks or less are probably not worth your time investigating, however I may be wrong.
Also, quick tip: mmcblk0 (with no pX) is the entire onboard storage as one unit. Don't bother dumping that to your SD card, since it contains all partitions, but will be a really big file and a big mess to figure out the partitions and mount it.
Good luck!
Outstanding, and THANKS A MILLION for the help. I've been banging my head against the wall here...
I should probably hit the sack, but I had started pulling those already, so I've got a head start.
Okay, good luck! I don't have this device, but a friend is getting one here soon (not sure how soon though) so I'm interested in getting CWM ported and some groundwork laid for CM7/etc on it.
Whenever you get time, I'm interested in seeing what you find the partitions are...
Thanks!
Went ahead and put a little more time into it...
used your method for dumping each individual partition.
A listing with file sizes:
Code:
2048 mmcblk0p1 4096 mmcblk0p11 2048 mmcblk0p2 4 mmcblk0p4 24576 mmcblk0p8
4096 mmcblk0p10 12288 mmcblk0p14 7168 mmcblk0p3 4096 mmcblk0p7 8192 mmcblk0p9
My common fdisk result (for all files) is:
Code:
fdisk -l mmcblk0p11
Disk mmcblk0p11: 0 MB, 0 bytes
255 heads, 63 sectors/track, 0 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xf6908d66
Disk mmcblk0p11 doesn't contain a valid partition table
Maybe I need to look at this again when I'm a little less tired, but this is the result of every image file.
P11 looks to be just a placeholder partition. Try p3, p8, p9, and p14.
Usually /boot is a lower number partition...
If you could upload the dumps of those partitions somewhere, I may be able to tell you which is which. (PM the link, don't post public- I'm not sure how XDA would feel about that).
This shouldn't be too hard to identify which is which. If you're well versed in hex editing, you could run those images through a hex dumper and check the file's magic numbers. I'm not too familiar with this device, but I'd say it can't be much different than the HTC boot.img format. Grab a boot.img from somewhere and see if the first couple of bytes match up on the dumps you've got.
From there, that should give you a clue with which is which. I'm betting you'll find which is the kernel by just doing a "strings" on the dumps and looking for things like "kernel" or "linux".
Good luck!
EDIT: after doing some reading, looks like some of the partitions are the fastboot type. Fastboot images = kernel + ramdisk. And, at least one of those partitions will be the Qualcomm AMSS partition for the radio chipset. Do a "strings <filename> | grep -i qualcomm" (or replace qualcomm with things like 'amss' or 'radio') to find which is which.
QualComm didn't turn up anything, so I changed the search to "comm." I don't have much time to look at this, but here's a quick dump:
mmcblk0p1 = radio?
Code:
mmcblk0p1 | grep -i comm
Device Transfer: Failed to queue the transfer command
DMOV Issue Cmd: Command issued
DMOV Request not Valid: Command list not on 64-bit boundary
DMOV Request not Valid: Invalid number of commands
DMOV Get Chan %d Error: Command error occured
DMOV Get Chan %d Error: Command-phase bus error occured
DMOV Stop Handler: cannot stop channel %d, commands pending
DMOV Stop Handler: cannot stop channel %d, issuing commands
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
DMOV Request not Valid: Boot and Tools should allocate their own command list memory
mmcblk0p2 = boot?
Code:
strings mmcblk0p2 | grep -i comm
QC_SMEM_PROC_COMM_CQ
ip_uint32 idev_comm_open( void )
dt_uint32 dt_CommOpen( void )
void idev_comm_close(ip_uint32 h)
void dt_CommClose(dt_uint32 h)
ip_commStatus_e idev_comm_queryCloseStatus(ip_uint32 h)
ip_commStatus_e idev_comm_queryConnectStatus(ip_uint32 h)
dt_CommStatus dt_QueryConnectStatus(dt_uint32 h)
const ip_int16 idev_comm_secureInitContext( void )
const dt_int16 dt_CommSecureInitContext( void )
void idev_comm_secureDeleteContext( void )
void dt_CommSecureDeleteContext( void )
EP0 command reply was not sent correctly %d [%d:%d]
Device Transfer: Failed to queue the transfer command
[AUE] update common code block (size):
[AUE] update common code block do_a_swap_ccb(size):
[AUE] Error: get common code block range
[AUE] Error: get common function block range
DMOV Issue Cmd: Command issued
DMOV Request not Valid: Command list not on 64-bit boundary
DMOV Request not Valid: Invalid number of commands
DMOV Get Chan %d Error: Command error occured
DMOV Get Chan %d Error: Command-phase bus error occured
DMOV Stop Handler: cannot stop channel %d, commands pending
DMOV Stop Handler: cannot stop channel %d, issuing commands
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot_local.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_partition.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_hash_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_dload_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/unified_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/osbl_prog_boot_mproc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_wm_ldr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_android_ldr.c
void idev_comm_connect(ip_uint32 h, ip_char* addr, ip_uint16 PortNum, ip_int32 TimeOut)
void dt_CommConnect(dt_uint32 h, dt_char* addr, dt_uint16 PortNum, dt_int32 TimeOut)
void idev_comm_send(ip_uint32 h, ip_char* SendBuf, ip_uint32 SendLen, ip_int32 TimeOut)
void dt_CommSend(dt_uint32 h, dt_char* SendBuf, dt_uint32 SendLen, dt_int32 TimeOut)
ip_commStatus_e idev_comm_querySendStatus(ip_uint32 h, ip_uint32* SentLen)
dt_CommStatus dt_QuerySendStatus(dt_uint32 h, dt_uint32* SentLen)
void idev_comm_recv(ip_uint32 h, ip_char* RecvBuf, ip_uint32 RecvLen, ip_int32 Timeout)
void dt_CommRecv(dt_uint32 h, dt_char* RecvBuf, dt_uint32 RecvLen, dt_int32 Timeout)
ip_commStatus_e idev_comm_queryRecvStatus(ip_uint32 h, ip_uint32* RecvLen)
dt_CommStatus dt_QueryRecvStatus(dt_uint32 h, dt_uint32* RecvLen)
const ip_int16 idev_comm_setSecureInfo( ip_int32 protocolID, ip_uint32 cipherSuites[], ip_int32 cipherSuitesSize, ip_char certificate[], ip_int32 certificateSize)
const dt_int16 dt_CommSetSecureInfo( dt_int32 protocolID, dt_uint32 cipherSuites[], dt_int32 cipherSuitesSize, dt_char certificate[], dt_int32 certificateSize)
ip_commStatus_e idev_httpTerminateAsync( ip_httpInterface_s *httpInterface )
CH9: Received vendor specific command for device, but no handlers registered
CH9: Received reserved command for device, but no handlers registered
[AUE] Info: no common code block, this is not ARM region, do zipping instead
Info: no common func block, this is not ARM region, do zipping instead
DMOV Request not Valid: Boot and Tools should allocate their own command list memory
cdc_handle_encapsulated_command
encapsulated_command_complete
hfat_common.c
EP0 command reply was not sent correctly %d [%d:%d]
CH9: Received vendor specific command for device, but no handlers registered
CH9: Received reserved command for device, but no handlers registered
The others returned nothing.
Just for shoots and giggles
I expanded the search for the word boot on 02, and here is what it revealed:
Code:
strings mmcblk0p2 | grep -i boot
/sys_boot/keystore/key.str
/sys_boot/keystore/store.pt
sys_boot
; Time Stamp unavailable from boot loader.
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_mc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash_dev_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash_dev_nand_mproc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_error_handler.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_aarm_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_hash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_hw_init.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_mc_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_flash_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_setup_mpu_dal.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_adsp_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_load_ramfs.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_sd_img_update.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot_local.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_partition.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_hash_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_dload_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/unified_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/osbl_prog_boot_mproc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_wm_ldr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_android_ldr.c
DMOV Request not Valid: Boot and Tools should allocate their own command list memory
boothw_target.c
sys_boot
smem_boot_init: version %x does not match all procs!
boot_elf_loader
boot_elf_loader_factory
boot_sec_elf_loader
boot_sec_elf_loader_factory
boot_flash_trans_nand
boot_flash_trans_nand_factory
boot_flash_trans_nor
boot_flash_trans_nor_factory
boot_flash_trans_sdcc
boot_flash_trans_sdcc_factory
boot_flash_dev_nor
boot_flash_dev_nand
boot_flash_dev_sdcc
clkrgm_mpss_boot.c
/mmc1/IMAGE/APPSBOOT.MBN
/mmc1/IMAGE/BOOT.IMG
/mmc1/IMAGE/EMMCBOOT.MBN
EMMCBOOT.MBN
BOOT.IMG
/sys_boot/IMAGE/
/sys_boot/IMAGE2/
/sys_boot/IMAGE3/
bootsymmetrickey
E/boot/qcsbl
F/boot/oemsbl
F/boot/osbl
G/boot/appsbl
H/boot/apps
I/boot/modem
J/boot/modem_fs1
K/boot/modem_fs2
L/boot/fota
M/boot/qcsbl_cfg
P/boot/adsp
01, same search:
Code:
trings mmcblk0p1 | grep -i boot
sys_boot
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_mc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_error_handler.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_flash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_configure.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_partition.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_auth.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_target_accessor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_parser.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_onenand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_sflashc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_shared.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_clk.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_clk_settings.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_onenand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ddr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
DMOV Request not Valid: Boot and Tools should allocate their own command list memory
sys_boot
smem_boot_init: version %x does not match all procs!
E/boot/qcsbl
F/boot/oemsbl
F/boot/osbl
G/boot/appsbl
H/boot/apps
I/boot/modem
J/boot/modem_fs1
K/boot/modem_fs2
L/boot/fota
M/boot/qcsbl_cfg
P/boot/adsp
02 - search for "home"
Code:
strings mmcblk0p2 | grep -i home
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_mc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash_dev_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_flash_dev_nand_mproc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_error_handler.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_aarm_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/shared/src/osbl_hash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_hw_init.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_mc_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_flash_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_setup_mpu_dal.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_adsp_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_load_ramfs.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/osbl/target/msm7x30/src/osbl_sd_img_update.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_sec_elf_loader_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_clobber_prot_local.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_trans_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nand_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_partition.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_hash_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_dload_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/unified_boot.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/osbl_prog_boot_mproc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_nor_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_flash_dev_sdcc_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_wm_ldr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_android_ldr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/wiredconnectivity/hsusb/core/src/jslave/core/jusb_core.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/wiredconnectivity/hsusb/core/src/jslave/dcd/dcd_tdi_4x.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/wiredconnectivity/hsusb/core/src/jos/jos_bus.c
01 search for home
Code:
strings mmcblk0p1 | grep -i home
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_mc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_error_handler.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_flash.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_configure.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_partition.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_loader.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_auth.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_target_accessor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/shared/src/dbl_parser.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_target.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_onenand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_sflashc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_shared.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_clk.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_clk_settings.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_nand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_onenand.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ebi2_nor.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_ddr.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/dbl/target/msm7x30/src/dbl_flash_sdcc.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/shared/src/boot_auth_if.c
/home/hd.mo/vs910_froyo_ZV4_04/modem/AMSS/products/7x30/core/boot/secboot2/common/target/msm7x30/src/boot_pbl_accessor.c
Remembering that factory reset is the sole function of the boot-loader on this device, I did a search for "factory"
02:
Code:
mmcblk0p2 | grep -i factory
boot_elf_loader_factory
boot_sec_elf_loader_factory
boot_flash_trans_nand_factory
boot_flash_trans_nor_factory
boot_flash_trans_sdcc_factory
01 - no results
I think we have a winner? I'd *almost* place money on 2 being boot, but I need a little insight here.
I should be able to pass you these files tonight. I'm just limited right now as I'm at work and remoting in on a slow connection.
Great work!
A few possible corrections:
Thought #1: From what I've read, AMSS (the radio) has multiple 'nvram partitions' where configuration is stored. The partitions with size 2048 look like those.
My updated guess:
P1 = hardware bootloader (like HBOOT on a HTC device)
P2 = second stage bootloader (references to android and wm_ldr)
The actual AMSS firmware is usually above 10MB in size, so the radio firmware is most likely a larger partition.
Thought #2: /boot is quite possibly a fastboot image. Those are usually compressed, hence you will not find any strings in it. It would be all binary.
If you can, run "hexdump -n 32 <filename>" on each of the dumps, and paste the output here.
With that hexdump information, I can tell you which partitions have the fastboot magic number and which are AMSS configuration partitions or ext3 filesystems.
As a side note, I wonder if this device supports fastboot commands... you could potentially try something like "fastboot reboot recovery" which should be harmless to see. Of course, you'd need Google's fastboot tools on your machine first though. (http://android-dls.com/wiki/index.php?title=Fastboot)
If it turns out that fastboot works, a nondestructive way of testing if the device is signed would be to extract the recovery image and replace it's ramdisk with one containing Clockwork. It may be as simple as "fastboot boot <newimage>" to boot the new image without actually changing anything on the phone.
Anyway, get those hex dumps, then we'll see where that leads...
Great work!
Alright - I'll get on that tonight when I get home (probably about another 2.5 hours from now including dinner).
The other thing that's been rattling around in my head, and I know I shouldn't be jumping this far ahead (nor do I want to derail this thread), is I (and the entire community) need to make some modifications to the android.policy.jar thus completing the migration from Bing on this phone. One string would make all the difference Unfortunately, it is odexed. I'm guessing this has many dependencies, and the best method to go about this would be to pretty much deodex the entire O.S.. Obviously, that's not something I feel comfortable with doing until we are completed with this, but my thought process is on track for what I need to do, right?
I also need to research if it is possible to dump my entire phone as an image as part of an Android AVM, so I don't end up bricking my phone. I had my entire phone lockup and go black last night. About had a heart attack.
Obviously, this takes precedence, but just wanted to throw all that out there while it was fresh in my mind (things get lost quickly - I have twenty browser windows open juggling about a dozen different thought processes).
Hex Dumps
P1:
Code:
0000000 dcd1 844b 1034 73d7 435a 7d0b ffff ffff
0000010 ffff ffff ffff ffff ffff ffff ffff ffff
0000020
P2:
Code:
0000000 000b 0000 0003 0000 0000 0000 0000 0450
0000010 31f8 0013 31f8 0013 31f8 0463 0000 0000
0000020
I'll have to do the fastboot install at home.
majorpay said:
Alright - I'll get on that tonight when I get home (probably about another 2.5 hours from now including dinner).
The other thing that's been rattling around in my head, and I know I shouldn't be jumping this far ahead (nor do I want to derail this thread), is I (and the entire community) need to make some modifications to the android.policy.jar thus completing the migration from Bing on this phone. One string would make all the difference Unfortunately, it is odexed. I'm guessing this has many dependencies, and the best method to go about this would be to pretty much deodex the entire O.S.. Obviously, that's not something I feel comfortable with doing until we are completed with this, but my thought process is on track for what I need to do, right?
I also need to research if it is possible to dump my entire phone as an image as part of an Android AVM, so I don't end up bricking my phone. I had my entire phone lockup and go black last night. About had a heart attack.
Obviously, this takes precedence, but just wanted to throw all that out there while it was fresh in my mind (things get lost quickly - I have twenty browser windows open juggling about a dozen different thought processes).
Click to expand...
Click to collapse
I believe I saw that it has been deodexed on stetsonaw's Twitter page. You may want to get in touch with him
Yeah, I saw he had claimed that over on androidforums. I should start checking that area more often. I put a post out to feel it out and see if he might be willing to throw it my way I think ultimately he is waiting patiently in the wings waiting for us to get done with this so he can release the ROM he is working on.
Just wanted to say keep up the good work. I plan to look into this more when I get home but sounds like you are definitely on the right track. Excited to see more progress soon.
I just got into the scene as this is my first droid phone but I have been reading up as quickly as possible to contribute to making roms.
OK, so I am back in the saddle.
I have run a ./fastboot reboot, and as expected, no response. (says waiting for device) I believe I still need to modify my hosts.
I expect you've seen my hex dumps. Any thoughts?
Edit: Phone went into "Download is in progress. Do not disconnect cable."
Real? I don't know, but this is hindering me from moving forward.
majorpay said:
P1:
Code:
0000000 dcd1 844b 1034 73d7 435a 7d0b ffff ffff
0000010 ffff ffff ffff ffff ffff ffff ffff ffff
0000020
P2:
Code:
0000000 000b 0000 0003 0000 0000 0000 0000 0450
0000010 31f8 0013 31f8 0013 31f8 0463 0000 0000
0000020
I'll have to do the fastboot install at home.
Click to expand...
Click to collapse
Great- now I just need hexdumps of the other partitions I listed: P3, P8, P9, and P14.
P1 and P2 are of little interest to us, we're looking for the one containing recovery and the main kernel+ramdisk.
As soon as we identify which is the recovery partition, we'll be super close to finding whether recovery is signed and one step closer to porting CWM.
PS: Fastboot reboot may have put your phone in download mode. If you're stuck in it, just try using "fastboot reboot recovery", then from there you should be able to select "reboot" and end up in Android again...
p3
Code:
0000000 ffff ffff ffff ffff ffff ffff ffff ffff
*
0000020
p8
Code:
0000000 0000 0000 0000 0000 0000 0000 0000 0000
*
0000020
p9
Code:
0000000 4e41 5244 494f 2144 66ac 0038 8000 0020
0000010 fb21 002f 0000 0120 0000 0000 0000 0110
0000020
p14
Code:
0000000 4e41 5244 494f 2144 66ac 0038 8000 0020
0000010 8cd9 0033 0000 0120 0000 0000 0000 0110
0000020
And ./fastboot devices consistently shows nothing. I added the device per Ubuntu guide, and restarted udev, but still nada.
Edit... I missed something on fastboot (I added the wrong device). I'll go back and recheck.
Edit 2: Still no luck.
As an update, it appears that holding the power button with the volume button up puts the device into what looks like a fastboot state (only when plugged into usb).
Edit: Maybe this is just a recovery mode / Emergency mode.
It is designated by a sign that reads: "Download is in progress. Do not disconnect cable."
According to my usb device information, it shows up as a LGE USB CDMA Modem.
Code:
lsusb
Bus 001 Device 025: ID 1004:6200 LG Electronics, Inc.
51-android.rules
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="1004", MODE="0666", OWNER="<my username>"
SUBSYSTEM=="usb", ATTRS{idVendor}=="1004",ATTR{idProduct}=="6200", OWNER="<my username>"
"./fastboot devices" shows nothing
Hi,
I am wondering if there might be a way reading the backups made with "Droid 2 Bootstrap Recovery" on a PC, i.e. mounting it as a loop image in Linux or with IMDisk under Windows? I've been searching for a while already but I could not find any info about it.
CU,
Mészi.
Update...
Code:
# losetup /dev/loop1 data.img
# fdisk -l /dev/loop1
Disk /dev/loop1: 516 MB, 516592640 bytes
255 heads, 63 sectors/track, 62 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xffffffff
Disk /dev/loop1 doesn't contain a valid partition table
Ok, the IMG file is no disk image. But what is it?
meszi1977 said:
Update...
Code:
# losetup /dev/loop1 data.img
# fdisk -l /dev/loop1
Disk /dev/loop1: 516 MB, 516592640 bytes
255 heads, 63 sectors/track, 62 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xffffffff
Disk /dev/loop1 doesn't contain a valid partition table
Ok, the IMG file is no disk image. But what is it?
Click to expand...
Click to collapse
It is a YAFFS image. I use unyaffs or dsixda's Kitchen to extract it, and mkyaffsimage (I cant find the link, but you'll have to compile it yourself) to repack (I never tested this one).
Just on Linux... for Windows I don't know a working method.
PS: The thread is in the wrong forum, no one comes here...
I use common MSM8960 unbrick tool to flash my phone which connect to computer display QHSUSB_DLOAD, and driver install complete, but i flash the data, it display:
D:\刷机\blankflash>qflash -com3 -ramload MPRG8960.hex -mbn 33 MSM8960_bootloader
_singleimage.bin -v -o
Motorola qflash Utility version 1.3
COMPORT :COM3
RAMLOADER :MPRG8960.hex
type is 0x21
7 mbn file name MSM8960_bootloader_singleimage.bin type 33
verbose mode on
Motorola qflash dll version 1.6
RAMLOADER VERSION: PBL_DloadVER2.0
------------------------------------------------------
DEVICE INFORMATION:
------------------------------------------------------
Version : 0x8
Min Version : 0x1
Max Write Size: 0x600
Model : 0x90
Device Size : 0
Description : Intel 28F400BX-TL or Intel 28F400BV-TL
------------------------------------------------------
Using passed in packet size, changing from 0x600 -> 0x600
EXTENDED_LINEAR_ADDRESS_REC @ 0x2a000000
Write 65536 bytes @ 0x2a000000
100EXTENDED_LINEAR_ADDRESS_REC @ 0x2a010000
Write 11840 bytes @ 0x2a010000
100START_LINEAR_ADDRESS_REC @ 0x2a000000
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
No data read from USB. This may not be an error. Trying again...
Still no data, giving up!
dmss_go : failed to receive ACK
Error loading MPRG8960.hex into device
why can't ?