Related
i got my hands to some stuff that might be useful for others , i'll update this topic. (Please do not mirror any links)
Training VCD:
LEO_Assembly_VCD.wmv
Code:
http://rapidshare.com/files/348289342/LEO_Assembly_VCD.wmv
Size: 157544 KB
LEO_Disassembly_VCD.wmv
Code:
http://rapidshare.com/files/348326227/LEO_Disassembly_VCD.wmv
Size: 138503 KB
MEGA-Assembly.wmv
Code:
http://rapidshare.com/files/348370098/MEGA-Assembly.wmv
Size: 68406 KB
MEGA-Disassembly.wmv
Code:
http://rapidshare.com/files/348387543/MEGA-Disassembly.wmv
Size: 74246 KB
MEGA-Tips.wmv
Code:
http://rapidshare.com/files/348402056/MEGA-Tips.wmv
Size: 60782 KB
HTC_Rhodium-assembly.wmv
Code:
http://rapidshare.com/files/348406542/HTC_Rhodium-assembly.wmv
Size: 20711 KB
HTC_Rhodium-disassembly.wmv
Code:
http://rapidshare.com/files/348410493/HTC_Rhodium-disassembly.wmv
Size: 19700 KB
HTC_Rhodium-Tips.wmv
Code:
http://rapidshare.com/files/348412964/HTC_Rhodium-Tips.wmv
Size: 12640 KB
HTC_Topaz-assembly.wmv
Code:
http://rapidshare.com/files/348418504/HTC_Topaz-assembly.wmv
Size: 27457 KB
HTC_Topaz-disassembly.wmv
Code:
http://rapidshare.com/files/348422865/HTC_Topaz-disassembly.wmv
Size: 22100 KB
HTC_Topaz-tips.wmv
Code:
http://rapidshare.com/files/348426289/HTC_Topaz-tips.wmv
Size: 11238 KB
Soft/Hard Reset User guide (V1.05)
Code:
http://rapidshare.com/files/348428239/UM___QSG.rar
Size: 2707 KB
Windows application program - ASP Calibration station 1.1+offline
Windows application program - ASP Calibration station 1.1+offline
Code:
http://rapidshare.com/files/348428770/ASPCalibrationStation_11_Offline.zip
Size: 2665 KB
Diagnostic Program for ASP or S58i
Diagnostic Program for ASP or S58i
ELF
Code:
http://rapidshare.com/files/348238831/ELF.rar
Size: 157 KB
Leo
Code:
http://rapidshare.com/files/348238956/Leo.rar
Size: 117 KB
Leo 2
Code:
http://rapidshare.com/files/348239043/Leo_2.rar
Size: 116 KB
Mega
Code:
http://rapidshare.com/files/348239093/Mega.rar
Size: 107 KB
PHAROS
Code:
http://rapidshare.com/files/348239144/PHAROS.rar
Size: 117 KB
Rhodium
Code:
http://rapidshare.com/files/348239196/Rhodium.rar
Size: 58 KB
VOX
Code:
http://rapidshare.com/files/348239243/VOX.rar
Size: 88 KB
Hotfix S.A
1_The_definition_of_new_failure_code_for_display
Code:
http://rapidshare.com/files/348430035/1_The_definition_of_new_failure_code_for_display.rar
Size: 100 KB
2_The_definition_of_new_failure_code_for_display
Code:
http://rapidshare.com/files/348431303/2_The_definition_of_new_failure_code_for_display.rar
Size: 85 KB
DOC-00068952_Repair_Notice_for_LEO_Chassis
Code:
http://rapidshare.com/files/348431367/DOC-00068952_Repair_Notice_for_LEO_Chassis.pdf
Size: 89 KB
LEO_hotfix_for_Leo_Camera_Reddish_view_issue
Code:
http://rapidshare.com/files/348432823/LEO_hotfix_for_Leo_Camera_Reddish_view_issue.rar
Size: 694 KB
Leo_Hotfix_for_LEO_SMS_issues
Code:
http://rapidshare.com/files/348433397/Leo_Hotfix_for_LEO_SMS_issues.rar
Size: 2570 KB
LEO_Hotfix_for_LEO_SMS_Message_delay_issue
Code:
http://rapidshare.com/files/348434267/LEO_Hotfix_for_LEO_SMS_Message_delay_issue.rar
Size: 3999 KB
LEO_Hotfix_for_micro_SD_capacity_over_8G
Code:
http://rapidshare.com/files/348434376/LEO_Hotfix_for_micro_SD_capacity_over_8G.rar
Size: 405 KB
LEO_Hotfix_for_Outgoing_sound_volume_too_loud
Code:
http://rapidshare.com/files/348434476/LEO_Hotfix_for_Outgoing_sound_volume_too_loud.rar
Size: 130 KB
Topaz_Handwriting_recognition
Code:
http://rapidshare.com/files/348435874/Topaz_Handwriting_recognition.rar
Size: 186 KB
LEO_Hotfix_for_week_calendar_view_of_HTC_calendar_issue
Code:
http://rapidshare.com/files/348435971/LEO_Hotfix_for_week_calendar_view_of_HTC_calendar_issue.rar
Size: 320 KB
Leo_new_repair_process_notice_for_Leo_zero_cold_boot
Code:
http://rapidshare.com/files/348436000/Leo_new_repair_process_notice_for_Leo_zero_cold_boot.rar
Size: 85 KB
LEO_repair_notice_for_leo_chassiss_replacement
Code:
http://rapidshare.com/files/348437420/LEO_repair_notice_for_leo_chassiss_replacement.rar
Size: 78 KB
Leo_repair_tools_notice_for_Leo_project
Code:
http://rapidshare.com/files/348437474/Leo_repair_tools_notice_for_Leo_project.rar
Size: 87 KB
Leo_RTV_parts_definition
Code:
http://rapidshare.com/files/348437504/Leo_RTV_parts_definition.rar
Size: 31 KB
Leo-Hotfix_for_LEO_SMS_issues
Code:
http://rapidshare.com/files/348438113/Leo-Hotfix_for_LEO_SMS_issues.rar
Size: 2834 KB
Mega_cannot_unlock_Phone_issue
Code:
http://rapidshare.com/files/348439456/Mega_cannot_unlock_Phone_issue.rar
Size: 240 KB
Mega_hot_key_to_perform_T.P_calibration
Code:
http://rapidshare.com/files/348439497/Mega_hot_key_to_perform_T.P_calibration.rar
Size: 125 KB
Mega_hotfix_release_for_canUt_update_the_weather_data_issue
Code:
http://rapidshare.com/files/348441859/Mega_hotfix_release_for_canUt_update_the_weather_data_issue.rar
Size: 12811 KB
Mega_Intermittent_no_ring_tone_during_incoming_call
Code:
http://rapidshare.com/files/348442039/Mega_Intermittent_no_ring_tone_during_incoming_call.rar
Size: 621 KB
Raphael_how_to_test_if_the_screen_responding_inaccuartely_to_stylus
Code:
http://rapidshare.com/files/348442073/Raphael_how_to_test_if_the_screen_responding_inaccuartely_to_stylus.rar
Size: 197 KB
Repair_tools_notice_for_Leo_Project_LEO
Code:
http://rapidshare.com/files/348442093/Repair_tools_notice_for_Leo_Project_LEO.rar
Size: 89 KB
Topaz_cannot_unlock_phone_or_owner_inf_icon_disapear
Code:
http://rapidshare.com/files/348442146/Topaz_cannot_unlock_phone_or_owner_inf_icon_disapear.rar
Size: 272 KB
RF Testing Software
R_S_test_Program_and_Install_program_SOP__Add_LEO
Code:
http://rapidshare.com/files/348239572/R_S_test_Program_and_Install_program_SOP__Add_LEO_.rar
Size: 1206 KB
Willtek_test_SOP_and_test_script_for_ASP__Add_Leo
Code:
http://rapidshare.com/files/348246758/Willtek_test_SOP_and_test_script_for_ASP__Add_Leo_.rar
Size: 26146 KB
Battery Rundown Tool for All PDA model
Battery_Rundown_Tool_for_All_PDA_model
Code:
http://rapidshare.com/files/348238172/Battery_Rundown_Tool_for_All_PDA_model.rar
Size: 11 KB
Troubleshooting guide
Mega_Troubleshooting_Guide_A04.xls
Code:
http://rapidshare.com/files/348426336/_DOC-00067454_Mega_Troubleshooting_Guide_A04.xls
Size: 82 KB
LEO_Troubleshooting_Guide_A01.xls
Code:
http://rapidshare.com/files/348427571/LEO_Troubleshooting_Guide_A01.xls
Size: 58 KB
LEO_Troubleshooting_Guide_A02.xls
Code:
http://rapidshare.com/files/348427618/LEO_Troubleshooting_Guide_A02.xls
Size: 59 KB
Mega_Troubleshooting_Guide_A02.xls
Code:
http://rapidshare.com/files/348427654/Mega_Troubleshooting_Guide_A02.xls
Size: 50 KB
Capability list report
Diamond_Bluetooth.rar
Code:
http://rapidshare.com/files/348238680/Diamond_Bluetooth.rar
Size: 54 KB
Diamond_WLAN.rar
Code:
http://rapidshare.com/files/348238762/Diamond_WLAN.rar
Size: 57 KB
Application
Diamond_capsensor_tester_1.00.00
Code:
http://rapidshare.com/files/348238363/Diamond_capsensor_tester_1.00.00.rar
Size: 4 KB
Leo_audio_test_1.00
Code:
http://rapidshare.com/files/348238470/Leo_audio_test_1.00.rar
Size: 344 KB
Leo_light_sensor_calibration_tool
Code:
http://rapidshare.com/files/348238499/Leo_light_sensor_calibration_tool.rar
Size: 23 KB
Polaris_hotfix_00438
Code:
http://rapidshare.com/files/348238514/Polaris_hotfix_00438.rar
Size: 12 KB
Polaris_hotfix_00443.rar[/code]
Code:
http://rapidshare.com/files/348238536/Polaris_hotfix_00443.rar
Size: 19 KB
Topaz
Code:
http://rapidshare.com/files/348238624/Topaz.rar
Size: 226 KB
WinCe_application_program_for_GPS_function_test
Code:
http://rapidshare.com/files/348238644/WinCe_application_program_for_GPS_function_test.rar
Size: 22 KB
Oh jeebus...a mole in the company ?
Ather said:
Oh jeebus...a mole in the company ?
Click to expand...
Click to collapse
hehehe maybe i hacked a mole lol
i have some other stuff which are very very wanted but i wont share atm
Quite the haul :O
Damnit! I hate rapidshare!
i think it would be best if make a torrent of all these files
also, uploading the videos to youtube would be nice. everyone hates rapidshare
I second tha idea of uploading tha vids to youtube.. I don't want to download these to my device..lol
i am ok if you guys upload the vids in youtube,
but i cant do it atm, if some1 can plz go on
Hi to all. yesterday i was tried to flash the new radio 2.22.23.02 on my old 26I.
I have 32B HTC G1.
with default hboot version: 1.42.0000
when i tried to flash new radio, it was all fine, but after trying to reboot into recovery again (after flashing) i got some error about There is not enough free space tra-la-la. And after reboot there is no changes and there is no some effect. After this i have a problem while restoring old rom's back up (ezterry's 2.2.1 ota)... Than i installed CM6 RC3. All fine, but a quality of my calls is like a fck ****!
Sometimes i speak with my friends like usual, but sometimes my friends and me hear crazy noise!
I know that its because my failed trying to flash another radio...
Hboot says to me that my version of radio is my oldest one - 26I.
What i can do now?
I can't flash any radio (26I and 23.02) always have the same trouble with the space (i think?)
Before the flashing i tried to 'fastboot erase system -w'
and after - wipe all... there is no effect.
How to fix? Thx for attention.
recovery.log in attach!
and via fastboot i have a:
Code:
Arthur-Malachevski:ota-radio-2_22_19_26I antihazard$ fastboot-mac flash radio radio.img
sending 'radio' (21504 KB)... OKAY
writing 'radio'... INFOsignature checking...
FAILED (remote: signature verify fail)
Arthur-Malachevski:ota-radio-2_22_19_26I antihazard$
maybe somebody have any suggestion?
SO ... here is more info:
Code:
Arthur-Malachevski:~ antihazard$ adb shell cat /proc/meminfo
MemTotal: 98700 kB
MemFree: 3332 kB
Buffers: 8 kB
Cached: 15248 kB
SwapCached: 5884 kB
Active: 40492 kB
Inactive: 33888 kB
Active(anon): 29008 kB
Inactive(anon): 30624 kB
Active(file): 11484 kB
Inactive(file): 3264 kB
Unevictable: 292 kB
Mlocked: 0 kB
SwapTotal: 17760 kB
SwapFree: 1556 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 54772 kB
Mapped: 14108 kB
Shmem: 204 kB
Slab: 5524 kB
SReclaimable: 1184 kB
SUnreclaim: 4340 kB
KernelStack: 2016 kB
PageTables: 4540 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 67108 kB
Committed_AS: 1177444 kB
VmallocTotal: 802816 kB
VmallocUsed: 54976 kB
VmallocChunk: 721924 kB
and mtd partitions:
Code:
Arthur-Malachevski:~ antihazard$ adb shell cat /proc/mtd
dev: size erasesize name
mtd0: 00040000 00020000 "misc"
mtd1: 00500000 00020000 "recovery"
mtd2: 00280000 00020000 "boot"
mtd3: 09100000 00020000 "system"
mtd4: 00800000 00020000 "cache"
mtd5: 038c0000 00020000 "userdata"
help...guys...
yesterday i was tried to erase radio via fastboot... no result...
ANtiHazarD said:
when i tried to flash new radio, it was all fine, but after trying to reboot into recovery again (after flashing) i got some error about There is not enough free space tra-la-la. And after reboot there is no changes and there is no some effect. After this i have a problem while restoring old rom's back up (ezterry's 2.2.1 ota)... Than i installed CM6 RC3. All fine, but a quality of my calls is like a fck ****!
Click to expand...
Click to collapse
I hope you have Test2 (test1 on the dream I didn't test calls but I'd not be socked to hear it sounded like **** (forgot the dream Audio settings.. I've heard the phone operate like that before it quite crappy)
However I believe you needed to use CustomMTD to install in that way; so what you really need to do is:
* nandroid backup;
* Uninstall custom MTD (use flash_image from recovery to re-flash your current recovery without the customMTD command line changes);
* then flash the an eng SPL (SPL 1.33.2003 will work fine as long as you have a 2.22 radio);
* then you can use fastboot to flash the new radio and
* 'fastboot erase system -w' to clean anything else up;
* last restore CustomMTD if needed and restore nandroid and boot normal.
yes, i used test2
okey, thx to you very much! I will try this way...
i hope thats my strange hboot 1.42.0000 will be reflashed by 1.33.2003 very fine.
Anyway i will have a possibility to change the 1.33.2003 spl without any fail and brick while a bad flashing (in case when i will try to flash 2003 spl and it will be, for example, with error) ?
i asked this questions because it's very strange for me - my version of phone. It's from South Africa (), yeap... I use customMTD, i flashed all ROM's, gained the root (The method with RC29, RC7 - NOT working with my phone) and all fine... but this phone have very strange default spl. Thats why i have a some fear about it
ezterry, thx you god.
Howdy folks,
I'm running the latest brd kernel as well as the tiamat rom on a US wifi xoom. I was digging around /proc and noticed this:
$ cat meminfo
MemTotal: 736968 kB
MemFree: 12516 kB
Buffers: 51832 kB
Cached: 121508 kB
SwapCached: 0 kB
Active: 298208 kB
Inactive: 302252 kB
Active(anon): 212220 kB
Inactive(anon): 216712 kB
Active(file): 85988 kB
Inactive(file): 85540 kB
Unevictable: 288 kB
Mlocked: 0 kB
HighTotal: 0 kB
HighFree: 0 kB
LowTotal: 736968 kB
LowFree: 12516 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 427416 kB
Mapped: 54424 kB
Shmem: 1524 kB
Slab: 16448 kB
SReclaimable: 9428 kB
SUnreclaim: 7020 kB
KernelStack: 5400 kB
PageTables: 13900 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 368484 kB
Committed_AS: 5913120 kB
VmallocTotal: 122880 kB
VmallocUsed: 61380 kB
VmallocChunk: 17412 kB
$
I was under the impression that the xoom had 1 gig of ram. Is this not correct?
I'm very new to the android platform, so forgive me if this is an inane questionor android abstracts some of the physical ram.
Sent from my Xoom using XDA Premium App
As far as i know, some of this 1Gb is reserved for GPU.
Looking for an ODIN flashable SC02COMKF2 baseband as I borked mine.
Por Favor!
http://forum.xda-developers.com/showthread.php?t=1131950
jje
JJEgan said:
http://forum.xda-developers.com/showthread.php?t=1131950
jje
Click to expand...
Click to collapse
SC02COMKF2 in there?
nakagusukumike said:
SC02COMKF2 in there?
Click to expand...
Click to collapse
Have you looked ??
But post was meant to indicate that was the best place to ask as i don't believe what you are asking for exists .
SC02COMKF2 no
KF2 modem/baseband/radio yes .
jje
JJEgan said:
Have you looked ??
But post was meant to indicate that was the best place to ask as i don't believe what you are asking for exists .
SC02COMKF2 no
KF2 modem/baseband/radio yes .
jje
Click to expand...
Click to collapse
Yes, of course I've looked. I would not have posted this request thread if I had not already searched for the baseband (which DOES exist, BTW) in the "Here are all your basebands" thread.
Request remains.
If I end up finding one locally and extracting with ADB, I'll post it up for others with SC02C phones to revert back to.
Yes, of course I've looked.
One of the few then .
Have to assume on SGS2 that the majority don't know what a search button is for .
jje
don't let your pessimism fill threads with detrimental posts
In other news, I've got access to a stock but rooted phone with a baseband intact. Gonna try to dd the block devices out to SD and try to inject with ODIN.
Hmmm.... I wonder if the phone would get pissed off if you just dd'd the good file you want back into the block device! hahahahha
example:
on the stock phone: dd if=/dev/block/mybadassbaseband of=/sdcard/basebandbackupSC02COMFK2.img
then cart the file over to the busted phone and,
dd if=/sdcard/basebamdbackupSC02COMFK2.imb of=/dev/block/bustedbaseband
I know it works in linux if you know EXACTLY what you're doing. hahahah
Not mine, but:
Code:
$ df
df
Filesystem Size Used Free Blksize
/dev 418M 76K 418M 4096
/mnt/asec 418M 0K 418M 4096
/mnt/obb 418M 0K 418M 4096
/mnt/usb 418M 0K 418M 4096
/app-cache 7M 680K 6M 4096
/system 602M 447M 154M 4096
/cache 98M 5M 92M 4096
/efs 19M 8M 11M 4096
/data 1G 164M 1G 4096
/mnt/.lfs: Function not implemented
/mnt/sdcard 11G 160M 11G 32768
/mnt/sdcard/external_sd 7G 1G 5G 32768
/mnt/secure/asec: Permission denied
$ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=111 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
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/usb tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /app-cache tmpfs rw,relatime,size=7168k 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p9 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p7 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
nil /sys/kernel/debug debugfs rw,relatime 0 0
/dev/block/mmcblk0p10 /data ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p4 /mnt/.lfs j4fs rw,relatime 0 0
/dev/block/vold/179:11 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
/dev/block/vold/179:17 /mnt/sdcard/external_sd vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:17 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,noatime,nodiratime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/external_sd/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
maybe just dump all the block devices and see which ones are between... say 6-20MB?
so i opened all of the block devices with fdisk and found that they are sized as follows:
/dev/block/mmcblk0 15.7GB
/dev/block/mmcblk0p1 20MB /efs ext4
/dev/block/mmcblk0p2 1MB ??
/dev/block/mmcblk0p3 1MB ??
/dev/block/mmcblk0p4 8MB /mnt/.lfs j4fs???
/dev/block/mmcblk0p5 8MB ??
/dev/block/mmcblk0p6 8MB ??
/dev/block/mmcblk0p7 104MB /cache ext4
/dev/block/mmcblk0p8 16MB ??
/dev/block/mmcblk0p9 641MB /system ext4
/dev/block/mmcblk0p10 2147MB /data ext4
/dev/block/mmcblk0p11 12.3GB ??
/dev/block/mmcblk0p12 432MB ??
so I'm guessing either partition 4,5,6 or 8 is the baseband
should have this figured out shortly.
Here's the info for my borked baseband (i9100)
I'm hoping to find someone with an intact baseband and dump the baseband image (and figure out WHERE the baseband image is
Here's what I've got on my phone (which does NOT have the SC02C baseband on it anymore)
Disk /dev/block/mmcblk0p2: 1 MB, 1310720 bytes
4 heads, 16 sectors/track, 40 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p3: 1 MB, 1310720 bytes
4 heads, 16 sectors/track, 40 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p4: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p5: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p6: 8 MB, 8388608 bytes
4 heads, 16 sectors/track, 256 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p7: 104 MB, 104857600 bytes
4 heads, 16 sectors/track, 3200 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p8: 16 MB, 16777216 bytes
4 heads, 16 sectors/track, 512 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p9: 641 MB, 641728512 bytes
4 heads, 16 sectors/track, 19584 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p10: 2147 MB, 2147483648 bytes
4 heads, 16 sectors/track, 65536 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p11: 12.3 GB, 12356419584 bytes
4 heads, 16 sectors/track, 377088 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk ./mmcblk0p12: 432 MB, 432013312 bytes
4 heads, 16 sectors/track, 13184 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
md5sums are:
6ced0bf7a897e05810253c7efd0fe2d8 /mnt/sdcard/mmcblk0p2.img
1045bfd216ae1ae480dd0ef626f5ff39 /mnt/sdcard/mmcblk0p3.img
7b8b44f05f7844b1f0814c92fac020be /mnt/sdcard/mmcblk0p4.img
84c09574f43239af4d635cf34d9bf335 /mnt/sdcard/mmcblk0p5.img
96995b58d4cbf6aaa9041b4f00c7f6ae /mnt/sdcard/mmcblk0p6.img
67f7f82e16890cd86237d30c79b988b5 /mnt/sdcard/mmcblk0p8.img
did some testing and I feel confident that p8 is the partition that is the modem/baseband on this phone.
I dd'd out all of my small block devices to .img files in the sdcard then MD5 summed them. Then I changed ONLY baseband from KF2 to KE4 and dd'd out ALL of the files, all over again. md5sum on all of them all over again, and only partition 8 changed sums.
NOW, I'm about to dd inject my OLD KF2 baseband image INTO the block device, and see if the OS doesn't take a **** when it reboots...
wish me luck..
Code:
# md5sum ./*.img
6ced0bf7a897e05810253c7efd0fe2d8 ./mmcblk0p2.img
1045bfd216ae1ae480dd0ef626f5ff39 ./mmcblk0p3.img
7b8b44f05f7844b1f0814c92fac020be ./mmcblk0p4.img
84c09574f43239af4d635cf34d9bf335 ./mmcblk0p5.img
96995b58d4cbf6aaa9041b4f00c7f6ae ./mmcblk0p6.img
f8b0f155f86fe161b6b3501ee2bfd20d ./mmcblk0p8.img
#md5sum ./basebands/*.img
md5sum: can't open './basebands/*.img': No such file or directory
# cd ./basebands
/mnt/sdcard/basebands
# ls
i9100KF2
# md5sum ./i9*/*.img
6ced0bf7a897e05810253c7efd0fe2d8 ./i9100KF2/mmcblk0p2.img
1045bfd216ae1ae480dd0ef626f5ff39 ./i9100KF2/mmcblk0p3.img
7b8b44f05f7844b1f0814c92fac020be ./i9100KF2/mmcblk0p4.img
84c09574f43239af4d635cf34d9bf335 ./i9100KF2/mmcblk0p5.img
96995b58d4cbf6aaa9041b4f00c7f6ae ./i9100KF2/mmcblk0p6.img
67f7f82e16890cd86237d30c79b988b5 ./i9100KF2/mmcblk0p8.img
#
so I just did:
Code:
dd if=/mnt/sdcard/basebands/i9100/mmcblk0p8.img of=/dev/block/mmcblk0p8
after it completed I pulled the battery and restarted the phone
MY PHONE HAS IN FACT REVERTED BASEBANDS BY DOING THIS ACTION!!!!!
SOOOO... my buddy (who still isn't here yet...) who still has the docomo baseband... I'll be extracting his and posting it for you all. hopefully soon.
We'll see if this fixes my ****ty reception and GPS not working. I know it won't fix 1seg though.
CHEERS MOFOS!!!
or is there anybody out there with a rooted SC02C still showing an SC02C baseband who feels like doing this:
Code:
su -
dd if=/dev/block/mmcblk0p8 of=/mnt/sdcard/mmcblk0p8.img
then send me the mmcblk0p8.img file that's on your SD card?
I'd be forever grateful!!
I'll try to do that tonight or tomorrow morning (I have only rooted, not changed CSC or for that matter even the rest of PDA). PM me an address to send to you at.
evildave_666 said:
I'll try to do that tonight or tomorrow morning (I have only rooted, not changed CSC or for that matter even the rest of PDA). PM me an address to send to you at.
Click to expand...
Click to collapse
PM Sent, thanks man!
IT WORKED, I'm back on
Baseband: SC02COMKF2
THANKS.
Will post the file in a few.
reception went up 2 or 3 bars at the same battery level and location in my house. Still no GPS on my ROM though, reverting back to stock backup and will see if I get GPS back...
GPS is still not working with the new baseband, but the reception is soooooooooooo much better.
Any chance I could get someone on a rooted, stock image to grab these:
Code:
su -
dd if=/dev/block/mmcblk0p2 of=/mnt/sdcard/mmcblk0p2.img
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/mmcblk0p3.img
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/mmcblk0p4.img
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/mmcblk0p5.img
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/mmcblk0p6.img
and send them to me? I'll figure out which one is GPS.
I'm gonna go to litening rom now and put the docomo baseband on.
battery life has been amazing on this baseband!
nakagusukumike said:
GPS is still not working with the new baseband, but the reception is soooooooooooo much better.
Any chance I could get someone on a rooted, stock image to grab these:
Code:
su -
dd if=/dev/block/mmcblk0p2 of=/mnt/sdcard/mmcblk0p2.img
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/mmcblk0p3.img
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/mmcblk0p4.img
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/mmcblk0p5.img
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/mmcblk0p6.img
and send them to me? I'll figure out which one is GPS.
I'm gonna go to litening rom now and put the docomo baseband on.
Click to expand...
Click to collapse
Any way to package this solution into something flashable for the rest of us? still having the GPS problem?
This is my first foray into Wear OS. I seem to always end up with some locked down devices. It Always teaches me a thing or two though! Because all is not lost it seems. I've been trying to compile what I can see from the device into one spot. Information on this series of watches is spread out all over the place. Let me explain what I've found out about The MK Access Bradshaw, that makes me think there is a light at the end of the tunnel. If you have experience with these watches or the Fossil Q sister series, please share. Links to the Fossil Q firmware would be amazing at this point.
Code:
----------------------------------------------
Michael Kors Access Bradshaw Device Info
----------------------------------------------
MODEL: MKT5006
CHIPSET: SD Wear 2100
RAM: 512 MB
STORAGE: 4 GB
SCREEN: 1.4 inch
RESOLUTION: 320x290 pixels (309 ppi)
WEAR OS: 2.6
BUILD: fossil/gar/gar
8.0.0/OWD6.180205.022/53356216
user/release-keys
----------------------------------------------
1. FASTBOOT MODE
[adb reboot bootloader]
----------------------------------------------
PRODUCT_NAME - gar
VARIANT - PFW2
PHASE - SA
BOOTLOADER VERSION - GAR.EINSTEIN_0.083.00
BASEBAND VERSION - N/A
HW_CONFIG - 1
SERIAL NUMBER - XXXXXXXXX (9 Digits)
** A Direct Pin Connection is Needed
to utilize the Fastboot Protocol.
** Fastboot appears active and functional
and only missing a physical connection
** A Pin Connection can be made.
Now, when we finally make it into the recovery mode, we are presented with standard Android Oreo Recovery options. Including the Recovery Logs. It is in these logs I have found A LOT of Information. They have the Log Daemon configured to 'eng'. But I noticed that simply using the 'adb reboot recovery' command, would start recovery mode but never show the recovery menu before rebooting back to the system.
The recovery menu only ever appears for me when I boot into recovery mode from fastboot mode.
Code:
----------------------------------------------
2. RECOVERY MODE
[Boot to Recovery from Bootloader]
----------------------------------------------
* The Recovery Log displays the Recovery FSTAB
* Build.Prop Contents Can also been seen.
* ro.logd.kernel=eng
It is very verbose. But without actual access to the cache partition there is no way to copy & paste, or pull the logs from the watch. My "last_log" entry is from when I updated the device from WearOS 2.2 to version 2.6. In that log, so much of the nitty gritty partition details are revealed, here are a few I've wrote down so far:
Code:
/cache/recovery/last_log:
-----------------------------
0 /system ext4 /dev/block/platform/soc/7824900.sdhci/by-name/system 0
1 /cache ext4 /dev/block/platform/soc/7824900.sdhci/by-name/cache 0
2 /data ext4 /dev/block/platform/soc/7824900.sdhci/by-name/userdata -16384
3 /sdcard vfat /dev/block/mmcblk1p1 0
4 /boot emmc /dev/block/platform/soc/7824900.sdhci/by-name/boot 0
5 /recovery emmc /dev/block/platform/soc/7824900.sdhci/by-name/recovery 0
6 /misc emmc /dev/block/platform/soc/7824900.sdhci/by-name/misc 0
7 /oem ext4 /dev/block/platform/soc/7824900.sdhci/by-name/oem 0
8 /tmp ramdisk ramdisk 0
ro.sys.fw.use_trim_settings=true
ro.sys.fw.trim_enable_memory=1073741824
ro.sys.fw.trim_empty_percent=100
ro.sys.fw.trim_cache_percent=100
ro.sys.fw.empty_app_percent=50
ro.sys.umsdirtyratio=20
ro.boot.hardware=gar
ro.boot.baseband=apq
ro.boot.console=null
ro.boot.ceibootmode=0
ro.boot.bootdevice=7824900.sdhci
ro.board.platform=msm8909
ro.build.host=abfarm648
ro.product.cpu.abi=armeabi-v7a
ro.boot.verifiedbootstate=green
ro.boot.authorized_kernel=true
ro.logd.kernel=eng
ro.bootimage.build.date=Thu Aug 9 00:39:05 UTC 2018
[11.364486]Verifying update package...
I:comment is 1476 bytes; signature is 1458 bytes from end.
I:signature (offset: 10127db, length: 5ac):
That log continues on with all of the signature, but on the watch screen it is quite a few pages long. But continues on during the whole verification process. And it really does say in so many words what it is doing and when. The log explains exactly what data it is putting where, and where the developers forgot to set expected values that the system must choose a default for.
What I need to do now is go through the log with an OCR App that can take pictures of the screen and extract the text. I believe the two most recent log files on my watch could explain just how to get at the bootloader & kernel. They definitely tell you where to go find the eFuse. Because even though it has Green Verified Boot Status, the boot log shows a few things for verified boot were never actually implemented. I'm working on getting these logs now.
Enable Developer Options:
Settings > System > About > Tap Build Number until it unlocks.
Connecting to ADB:
1.) Enable Developer Options
2.) Disable Bluetooth
3.) Connect Device to Wi-Fi
4.) Settings > Dev Options > ADB Debugging
5.) Settings > Dev Options > Debug Over Wi-Fi
6.) From a command line, start the adb server and then use this command with the watch's wifi ip address: "adb connect <ip_address>:5555"
7.) Run command "adb devices" and hit the yes button on the watch face to accept the connection.
Replacement 1st Gen Fossil Watch Chargers (2016-2017 Watches):
1.) 1st Party Marc Jacob's MJT0001/MKT0001
2.) 3rd Party Soarking Fossil Charger
Once I find a repair manual or schematic to this thing, I think I'm going to work on creating a cable to connect to the board for fastboot access.
MEMINFO
Code:
MemTotal: 455000 kB
MemFree: 8228 kB
MemAvailable: 179528 kB
Buffers: 2216 kB
Cached: 179400 kB
SwapCached: 7136 kB
Active: 153580 kB
Inactive: 154504 kB
Active(anon): 63348 kB
Inactive(anon): 64340 kB
Active(file): 90232 kB
Inactive(file): 90164 kB
Unevictable: 256 kB
Mlocked: 256 kB
SwapTotal: 338936 kB
SwapFree: 222520 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 125548 kB
Mapped: 78400 kB
Shmem: 1216 kB
Slab: 41732 kB
SReclaimable: 13440 kB
SUnreclaim: 28292 kB
KernelStack: 8544 kB
PageTables: 20392 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 566436 kB
Committed_AS: 26409868 kB
VmallocTotal: 499712 kB
VmallocUsed: 95544 kB
VmallocChunk: 291668 kB
MOUNTS
Code:
rootfs / rootfs ro,seclabel,size=205932k,nr_inodes=51483 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=221356k,nr_inodes=55339,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime,gid=3009,hidepid=2 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,seclabel,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt tmpfs rw,seclabel,relatime,size=221356k,nr_inodes=55339,mode=755,gid=1000 0 0
none /config configfs rw,relatime 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
pstore /sys/fs/pstore pstore rw,seclabel,relatime 0 0
adb /dev/usb-ffs/adb functionfs rw,relatime 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/system /system ext4 ro,seclabel,relatime,discard 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/cache /cache ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/persist /persist ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/modem /firmware vfat ro,context=u:object_r:firmware_file:s0,relatime,uid=1000,fmask=0337,dmask=0227,codepage=437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/oem /oem ext4 rw,seclabel,nosuid,nodev,noatime,data=ordered 0 0
/dev/block/platform/soc/7824900.sdhci/by-name/userdata /data ext4 rw,seclabel,nosuid,nodev,noatime,discard,noauto_da_alloc,errors=panic,data=ordered 0 0
tmpfs /storage tmpfs rw,seclabel,relatime,size=221356k,nr_inodes=55339,mode=755,gid=1000 0 0
/data/media /mnt/runtime/default/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid 0 0
/data/media /storage/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=1015,multiuser,mask=6,derive_gid 0 0
/data/media /mnt/runtime/read/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=23,derive_gid 0 0
/data/media /mnt/runtime/write/emulated sdcardfs rw,nosuid,nodev,noexec,noatime,fsuid=1023,fsgid=1023,gid=9997,multiuser,mask=7,derive_gid 0 0
PARTITIONS
Code:
major - minor - #blocks name
-------------------------------------
254 - 0 - 262144 zram0
179 - 0 - 3817472 mmcblk0
179 - 1 - 65536 mmcblk0p1
179 - 2 - 512 mmcblk0p2
179 - 3 - 512 mmcblk0p3
179 - 4 - 512 mmcblk0p4
179 - 5 - 512 mmcblk0p5
179 - 6 - 768 mmcblk0p6
179 - 7 - 768 mmcblk0p7
179 - 8 - 1024 mmcblk0p8
179 - 9 - 1536 mmcblk0p9
179 - 10 - 1536 mmcblk0p10
179 - 11 - 1536 mmcblk0p11
179 - 12 - 1 mmcblk0p12
179 - 13 - 1024 mmcblk0p13
179 - 14 - 8 mmcblk0p14
179 - 15 - 10240 mmcblk0p15
179 - 16 - 32 mmcblk0p16
179 - 17 - 16 mmcblk0p17
179 - 18 - 32768 mmcblk0p18
179 - 19 - 32768 mmcblk0p19
179 - 20 - 512 mmcblk0p20
179 - 21 - 1024 mmcblk0p21
179 - 22 - 1024 mmcblk0p22
179 - 23 - 32768 mmcblk0p23
179 - 24 - 32768 mmcblk0p24
179 - 25 - 1024 mmcblk0p25
179 - 26 - 512 mmcblk0p26
179 - 27 - 512 mmcblk0p27
179 - 28 - 16384 mmcblk0p28
179 - 29 - 256 mmcblk0p29
179 - 30 - 256 mmcblk0p30
179 - 31 - 256 mmcblk0p31
259 - 0 - 256 mmcblk0p32
259 - 1 - 65536 mmcblk0p33
259 - 2 - 655360 mmcblk0p34
259 - 3 - 2310127 mmcblk0p35
179 - 32 - 4096 mmcblk0rpmb
DF Utility
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
---------------------------------------------------------------------------
rootfs 205932 3460 202472 2% /
tmpfs 221356 532 220824 1% /dev
tmpfs 221356 0 221356 0% /mnt
/dev/block/mmcblk0p34 645056 630224 0 100% /system
/dev/block/mmcblk0p33 60400 1632 57460 3% /cache
/dev/block/mmcblk0p1 65488 22240 43248 34% /firmware
/dev/block/mmcblk0p28 12016 64 11628 1% /oem
/dev/block/mmcblk0p35 2237680 690400 1530896 32% /data
/data/media 2237680 690400 1530896 32% /storage/emulated
Since making this thread, this update no longer seems to be available. I think I am also leaving XDA, my words here have caused me too much trouble.