I have an old laptop with Wacom touch panel (Penabled). I am able to boot Remix OS fine but touch isn't working.
How to make touchscreen work?
Edit: Fixed by myself
View post #6 link: http://forum.xda-developers.com/showpost.php?p=65159778&postcount=6
The hardware must be unsupported.
TheBasterd said:
The hardware must be unsupported.
Click to expand...
Click to collapse
Nevermind, I fixed it myself
Care to share with the rest of us in case this issue comes up more often?
I would also be happy to know how to make a Wacom digitizer work on Remix OS as I'm looking into getting a Lenovo X61t to use with Remix OS.
YassinTP said:
I would also be happy to know how to make a Wacom digitizer work on Remix OS as I'm looking into getting a Lenovo X61t to use with Remix OS.
Click to expand...
Click to collapse
My laptop (Fujitsu T730) has Wacom digitizer with both touch input and pen. Using my method only touchscreen works (pen doesn't but I don't care )
You need to create live usb pendrive from official Android-X86 4.4 r4, run it live (without install) and copy from it inputattach file inside system/bin folder to Remix OS system/bin folder (you need rooted Remix OS for this) and set correct permissions.
Download from Play Store Terminal Emulator for Android and run:
su
inputattach --w8001 /dev/ttyS0 &
And touchscreen works
I have no idea why this file is missing in Remix OS while it is present in Android-X86 (Remix is based on Android-X86 after all)
It would be great if Remix developers could include it in next releases because as it is now you have to copy it every time you upgrade os.
Thank you very much!
Only thing is, the convertible I'm planning on buying only has a pen guess I'll just have to try if I get it working.
This is no working on my HP 2760p.
jarek3460 said:
This is no working on my HP 2760p.
Click to expand...
Click to collapse
I also tested it on HP 2760p. And it was working fine. I no longer use Remix OS so I can't confirm if this works on recent rom versions.
Remember that after copying file you have to set correct file permissions using any root capable file browser. (Try setting it to: rwxrwxrwx to be sure it works )
jarek3460 said:
This is no working on my HP 2760p.
Click to expand...
Click to collapse
were you able to ever get this working? I have a 2740p as well with only pen support
Rafostar said:
My laptop (Fujitsu T730) has Wacom digitizer with both touch input and pen. Using my method only touchscreen works (pen doesn't but I don't care )
You need to create live usb pendrive from official Android-X86 4.4 r4, run it live (without install) and copy from it inputattach file inside system/bin folder to Remix OS system/bin folder (you need rooted Remix OS for this) and set correct permissions.
Download from Play Store Terminal Emulator for Android and run:
su
inputattach --w8001 /dev/ttyS0 &
And touchscreen works
I have no idea why this file is missing in Remix OS while it is present in Android-X86 (Remix is based on Android-X86 after all)
It would be great if Remix developers could include it in next releases because as it is now you have to copy it every time you upgrade os.
Click to expand...
Click to collapse
I tried X86 Marshmellow and the Nought Beta versions, but touch is not working on them.
It is still working on Ubuntu Live and Debian. I ran lsusb and lsmod on them and got this result.
Code:
[email protected]:/home/ubuntu# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 009: ID 0bda:5830 Realtek Semiconductor Corp.
Bus 001 Device 007: ID 0bda:b720 Realtek Semiconductor Corp.
Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 003: ID 0bda:5830 Realtek Semiconductor Corp.
Bus 001 Device 008: ID 05e3:0718 Genesys Logic, Inc. IDE/SATA Adapter
Bus 001 Device 006: ID 04d9:e200 Holtek Semiconductor, Inc.
Bus 001 Device 004: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Code:
[email protected]:/home/ubuntu# lsmod
Module Size Used by
rfcomm 69632 2
bnep 20480 2
joydev 20480 0
rtsx_usb_ms 20480 0
memstick 20480 1 rtsx_usb_ms
intel_rapl 20480 0
x86_pkg_temp_thermal 16384 0
intel_powerclamp 16384 0
coretemp 16384 0
hid_multitouch 20480 0
kvm_intel 172032 0
kvm 536576 1 kvm_intel
irqbypass 16384 1 kvm
crct10dif_pclmul 16384 0
crc32_pclmul 16384 0
aesni_intel 167936 0
aes_x86_64 20480 1 aesni_intel
lrw 16384 1 aesni_intel
gf128mul 16384 1 lrw
btusb 45056 0
uvcvideo 90112 0
videobuf2_vmalloc 16384 1 uvcvideo
videobuf2_memops 16384 1 videobuf2_vmalloc
videobuf2_v4l2 28672 1 uvcvideo
glue_helper 16384 1 aesni_intel
btrtl 16384 1 btusb
ablk_helper 16384 1 aesni_intel
btbcm 16384 1 btusb
btintel 16384 1 btusb
cryptd 20480 2 aesni_intel,ablk_helper
bluetooth 520192 29 bnep,btbcm,btrtl,btusb,rfcomm,btintel
videobuf2_core 36864 2 uvcvideo,videobuf2_v4l2
v4l2_common 16384 1 videobuf2_v4l2
serio_raw 16384 0
videodev 176128 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2
input_leds 16384 0
media 24576 2 uvcvideo,videodev
intel_pch_thermal 16384 0
snd_hda_codec_realtek 86016 1
snd_hda_codec_hdmi 53248 1
snd_hda_codec_generic 77824 1 snd_hda_codec_realtek
snd_soc_rt5640 114688 0
snd_hda_intel 36864 5
snd_soc_ssm4567 16384 0
snd_soc_rl6231 16384 1 snd_soc_rt5640
snd_hda_codec 135168 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel
snd_soc_core 212992 2 snd_soc_rt5640,snd_soc_ssm4567
snd_hda_core 73728 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel
snd_hwdep 16384 1 snd_hda_codec
snd_seq_midi 16384 0
snd_seq_midi_event 16384 1 snd_seq_midi
snd_compress 20480 1 snd_soc_core
ac97_bus 16384 1 snd_soc_core
snd_rawmidi 32768 1 snd_seq_midi
snd_pcm_dmaengine 16384 1 snd_soc_core
snd_seq 69632 2 snd_seq_midi_event,snd_seq_midi
snd_pcm 106496 7 snd_soc_rt5640,snd_soc_core,snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_pcm_dmaengine,snd_hda_core
int3403_thermal 16384 0
mei_me 36864 0
snd_seq_device 16384 3 snd_seq,snd_rawmidi,snd_seq_midi
mei 98304 1 mei_me
kxcjk_1013 20480 0
elan_i2c 36864 0
snd_timer 32768 2 snd_pcm,snd_seq
industrialio_triggered_buffer 16384 1 kxcjk_1013
dw_dmac 16384 0
lpc_ich 24576 0
8250_dw 16384 0
snd 81920 23 snd_hda_codec_realtek,snd_soc_core,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_seq,snd_rawmidi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel,snd_seq_device,snd_compress
dw_dmac_core 24576 1 dw_dmac
int3400_thermal 16384 0
int3402_thermal 16384 0
processor_thermal_device 16384 0
acpi_als 16384 0
intel_soc_dts_iosf 16384 1 processor_thermal_device
acpi_thermal_rel 16384 1 int3400_thermal
int340x_thermal_zone 16384 3 int3402_thermal,processor_thermal_device,int3403_thermal
kfifo_buf 16384 2 industrialio_triggered_buffer,acpi_als
snd_soc_sst_acpi 16384 0
soundcore 16384 1 snd
i2c_designware_platform 16384 0
i2c_designware_core 20480 1 i2c_designware_platform
spi_pxa2xx_platform 24576 0
industrialio 57344 4 industrialio_triggered_buffer,acpi_als,kxcjk_1013,kfifo_buf
mac_hid 16384 0
acpi_pad 20480 0
parport_pc 32768 0
ppdev 20480 0
lp 20480 0
parport 49152 3 lp,ppdev,parport_pc
autofs4 40960 2
overlay 49152 1
nls_iso8859_1 16384 3
dm_mirror 24576 0
dm_region_hash 24576 1 dm_mirror
dm_log 20480 2 dm_region_hash,dm_mirror
mmc_block 36864 2
hid_generic 16384 0
usbhid 49152 0
rtsx_usb_sdmmc 28672 0
rtsx_usb 24576 2 rtsx_usb_sdmmc,rtsx_usb_ms
uas 24576 0
usb_storage 69632 4 uas
i915 1208320 5
i2c_algo_bit 16384 1 i915
drm_kms_helper 147456 1 i915
syscopyarea 16384 1 drm_kms_helper
sysfillrect 16384 1 drm_kms_helper
ahci 36864 0
sysimgblt 16384 1 drm_kms_helper
libahci 32768 1 ahci
fb_sys_fops 16384 1 drm_kms_helper
drm 360448 6 i915,drm_kms_helper
video 40960 1 i915
i2c_hid 20480 0
hid 118784 4 i2c_hid,hid_multitouch,hid_generic,usbhid
sdhci_acpi 16384 0
sdhci 45056 1 sdhci_acpi
fjes 28672 0
Rafostar said:
I also tested it on HP 2760p. And it was working fine. I no longer use Remix OS so I can't confirm if this works on recent rom versions.
Remember that after copying file you have to set correct file permissions using any root capable file browser. (Try setting it to: rwxrwxrwx to be sure it works )
Click to expand...
Click to collapse
Thank you so much Rafostar this helped getting my touch screen working on my hp 2740p
although it worked after the command was inputted. it failed to work after reboot
to fix this I needed to edit system/etc/init.sh
edit init.sh function init_misc
add command to line 18
inputattach --w8001 /dev/ttyS0 &
Redesterdragon said:
Thank you so much Rafostar this helped getting my touch screen working on my hp 2740p
although it worked after the command was inputted. it failed to work after reboot
to fix this I needed to edit system/etc/init.sh
edit init.sh function init_misc
add command to line 18
inputattach --w8001 /dev/ttyS0 &
Click to expand...
Click to collapse
I forgot to mention that you have to do this every time after reboot or create/add it to a startup script like you did
Rafostar said:
I forgot to mention that you have to do this every time after reboot or create/add it to a startup script like you did
Click to expand...
Click to collapse
I noticed that after falling asleep the touchscreen stops working again till reboot or manually entering the command within the command line
Rafostar said:
I forgot to mention that you have to do this every time after reboot or create/add it to a startup script like you did
Click to expand...
Click to collapse
what would I do to activate inputattach during wake?
Redesterdragon said:
what would I do to activate inputattach during wake?
Click to expand...
Click to collapse
I found one method of disabling sleep using a wake_lock command by placing it within the init.sh file under the function_misc section line 19
echo lock_me > /sys/power/wake_lock
this will dim the screen but not turn off the CPU so the digitizer will remain active now.
Please let me know if this might cause any other unfavorable issues.
Related
I'm looking for some experienced eyes to scan through the partition info of a CyberNav tablet that I've mucked up by being very stupid. The CyberNav is a cheap Chinese GPS/Android tablet. It works great, or rather worked great until I very stupidly left it attached to my computer after downloading a track of my latest dirtbiking exploits. Later that evening I decided to make another Ubuntu USB startup disk... well, you can guess the rest.
At this point, the tablet will not mount the internal "sdcard" memory. It still boots, everything works, not bricked yet. When connected to USB, it will share out this external storage just fine. It just won't mount it within Android. It reports "Preparing memory device, checking for errors." Never gets past that point. I do have a backup of the original internal sdcard contents (made that when I first got the device) and anything that was important to me. Yes, I make backups, been burned too many times. I've also managed to find a factory ROM for it and I've successfully flashed that to the device. It made no difference with the problem. I've also got a root prompt via ADB shell using psneuter.
I have a copy of parted and gdisk, though I've not tried to run them yet. In other words, it's time to start figuring out what to fix in the partition tables.
I think the problem is here:
# busybox fdisk -l /dev/block/mmcblk2p6
... Device Boot Start End Blocks Id System
/dev/block/mmcblk2p6p1 1 1017 3436381 5 Extended <<<<< HERE
/dev/block/mmcblk2p6p5 1 1017 3436379 b Win95 FAT32
Does that seem right? Am I in any danger of bricking this device if I blow away the mmcblk2p6p1 partition and/or the entire mmcblk2p6? How bad do things generally have to get in these partitions before the device bricks?
What is the best/safest way to remove this partition and if I have to blow the whole mmcblk2p6 partition away will I have to manually recreate it before rebooting?
Any advice appreciated,
David...
P.S. Here is all the hopefully relevant information I've so far managed to locate:
Cybernav Mini: CPU: IMAPX200 ARM11 800MHz, also known as YFPi08, now flashed to Android 2.2-104.
# cat /proc/partitions
Code:
major minor #blocks name
179 16 3878912 mmcblk2
179 17 4096 mmcblk2p1
179 18 8192 mmcblk2p2
179 19 153600 mmcblk2p3
179 20 1 mmcblk2p4
179 21 277760 mmcblk2p5
179 22 3435072 mmcblk2p6
# busybox fdisk -l /dev/block/mmcblk2
Code:
Disk /dev/block/mmcblk2: 3972 MB, 3972005888 bytes
1 heads, 16 sectors/track, 484864 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk2p1 9 520 4096 30 Unknown
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk2p2 521 1544 8192 31 Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk2p3 1545 20744 153600 83 Linux
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk2p4 20745 484864 3712960 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk2p5 20753 55472 277760 83 Linux
/dev/block/mmcblk2p6 55481 484864 3435072 b Win95 FAT32
# busybox fdisk -l /dev/block/mmcblk2p6
Code:
Disk /dev/block/mmcblk2p6: 3517 MB, 3517513728 bytes
109 heads, 62 sectors/track, 1016 cylinders
Units = cylinders of 6758 * 512 = 3460096 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk2p6p1 1 1017 3436381 5 Extended
/dev/block/mmcblk2p6p5 1 1017 3436379 b Win95 FAT32
# cat /proc/kmsg
Code:
...
<3>[ 2.295000] imapx200_iic imapx200_iic.0: iic thread TX_ABORT occur
<3>[ 2.295000] imapx200_iic imapx200_iic.0: source is 1
<3>[ 2.295000] imapx200_iic imapx200_iic.0: slave address is 1a
<4>[ 2.300000] mmc_request bus 2 cmd 5 error -110
<4>[ 2.300000] mmc_request bus 2 cmd 5 error -110
<4>[ 2.300000] set info,open device error -939392608
<4>[ 2.305000] mmc_request bus 2 cmd 5 error -110
<3>[ 2.305000] imapx200_iic imapx200_iic.0: iic thread TX_ABORT occur
<3>[ 2.305000] imapx200_iic imapx200_iic.0: source is 1
<3>[ 2.305000] imapx200_iic imapx200_iic.0: slave address is 1a
<4>[ 2.305000] mmc_request bus 2 cmd 5 error -110
<6>[ 2.330000] mmc2: new high speed SDHC card at address 0002
<6>[ 2.330000] mmcblk2: mmc2:0002 3.69 GiB
<6>[ 2.335000] mmcblk2: p1 p2 p3 p4 < p5 p6 >
<4>[ 2.400000] custom info start sector 8182
<4>[ 2.430000] i2c-imapx200 transfer timeout
...
<6>[ 4.095000] EXT4-fs (mmcblk2p3): mounted filesystem with ordered data mode
<6>[ 4.635000] EXT4-fs (mmcblk2p5): recovery complete
<6>[ 4.645000] EXT4-fs (mmcblk2p5): mounted filesystem with ordered data mode
...
<3>[ 26.285000] FAT: invalid media value (0xa5)
<6>[ 26.285000] VFS: Can't find a valid FAT filesystem on dev mmcblk2p6.
... x3 above spaced to end of log.
dmesg:
Code:
...
<6>[ 0.295000] Imap Framebuffer Driver Initialization OK!
<4>[ 0.340000] set info,open device error -939392608
<4>[ 0.440000] set info,open device error -939392608
<4>[ 0.540000] set info,open device error -939392608
<4>[ 0.640000] set info,open device error -939392608
<4>[ 0.740000] set info,open device error -939392608
<4>[ 0.845000] set info,open device error -939392608
<6>[ 0.925000] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
...
<3>[ 96.180000] FAT: invalid media value (0xa5)
<6>[ 96.180000] VFS: Can't find a valid FAT filesystem on dev mmcblk2p6.
... x2 above
adding a little info
# /data/local/tmp/parted /dev/block/mmcblk2
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk2
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Model: SD (sd/mmc)
Disk /dev/block/mmcblk2: 3972MB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Number Start End Size Type File system Flags
1 65.5kB 4260kB 4194kB primary
2 4260kB 12.6MB 8389kB primary
3 12.6MB 170MB 157MB primary ext4
4 170MB 3972MB 3802MB extended
5 170MB 454MB 284MB logical ext4
6 454MB 3972MB 3518MB logical
But,
# /data/local/tmp/parted /dev/block/mmcblk2p6
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk2p6
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Error: Can't have a partition outside the disk!
(parted)
Every command I try just reports: "Error: Can't have a partition outside the disk!"
Okay, Okay, I get it. No how do I get rid of said partition?
Back at: # /data/local/tmp/parted /dev/block/mmcblk2
(parted) check 6
check 6
Error: Could not detect file system.
(parted)
dare I go: rm 6
If I just reboot at that point, what are the odds of the bootloader just recreating this partition for me? Should I recreate the partition via parted first? Something like: mkpart logical fat32 454 3972 and then format it by Windows Computer via USB mode, or (man for parted says this is discouraged) mkpartfs logical fat32 454 3972 to let it format right away?
I guess what I'm really asking is: what are the odds of bricking it if I blow this partition away? Seem low, what with it not working properly now, but I figure I should at least make an attempt at asking before I suck it up and hit the button.
Anyone?
David...
fixed:
rm 6 and mkpartfs logical fat32 454 3972 then a reboot did the trick. I've copied all the data back and set the tablet back to where it was. All done
Only took 2 weeks of head-banging, trying to figure out the Android way. Not an easy thing, what with all the fragmentation, and it pushed my Linux skills to their limit as well. By the hour, this $100 tablet is now worth an order of magnitude more but those skills should be worth it, even if the tablet isn't.
David...
Sent from my GT-I8190 using xda app-developers app
AW: [REQ] Complete phone partition backup
Hello,
I start to collect all partitions from our Galaxy mini.
This will be usefull to overwrite custom binary count to original.
So if anyone things this could be successfull, becuause that were easy to manage write it here.
We need partitions from phones where binary count is original at zero.
I don t know all partitions and the command for dd, so if somebody helps, they help us all.
Hope for answers if it might be usefull.
Sent from my GT-I8190 using xda app-developers app
You can look them up using root explorer, just navigate to dev/block they're all there.
I have just entered the time dd if = / dev/block/mmcblk0 of = / sdcard / backup XXXX.tar not I know what that is but the file was afterwards so great that I had no more space on the internal sd card. gone were the yes on ext sd is just my take yesterday broke
sorry my english is not so good
Yes it's 1.27GB.
AW: [REQ] Complete phone partition backup
was this the right mmcblk0 been block?
Gesendet von meinem GT-I8190 mit Tapatalk 2
I don't know, you have to ask somebody else.
AW: [REQ] Complete phone partition backup
Well, i ve backuped mmcblk0, and terminal says: at around 3 GB not enough space.
But i ve a plan...
This file seems to be the whole phone memory.
So if we have that, i could search for "binary download" in bytes.
Maybe i find the position out ..
Then we could patch the file with zero count through a hex editor.
Sound easy, basic hacking!
Look at this: http://forum.xda-developers.com/showthread.php?t=2140514
Sent from my GT-I8190 using xda app-developers app
There's a Hex Editor on Google Play, just seen it. Just search Hex.
Sent from my GT-I8190 using xda premium
AW: [REQ] Complete phone partition backup
I backuped mmcblk0.
Theres a problem, dd means "file to large"
Can i override the file size in dd?
Sent from my GT-I8190 using xda app-developers app
try bs=4096 at the end.
my phone is unbricked just received today and all are ok
custombinary = no
from 120 to 0 now just expplain how i can make this partition and i try to make it
AW: [REQ] Complete phone partition backup
So it was repaired even with the custom binary?
Warranty isn t lost with custom binary?
Sent from my GT-I8190 using xda premium
Trykall8 said:
So it was repaired even with the custom binary?
Warranty isn t lost with custom binary?
Sent from my GT-I8190 using xda premium
Click to expand...
Click to collapse
yes given to him with 130 binary counter today when receive it from repear stor i have booted in download mode for see if changed or not and TADA restored to original with NO custum binary
===== partition information =====
Pulled this tabel from UART
ID: MBR,GPT ( 1) DEVICE: MMC FIRST UNIT: 0 NO. UNITS: 256 USED UNITS: 0
ID: MasterTOC ( 2) DEVICE: MMC FIRST UNIT: 256 NO. UNITS: 768 USED UNITS: 0
ID: PIT (70) DEVICE: MMC FIRST UNIT: 1024 NO. UNITS: 2048 USED UNITS: 0
ID: MD5HDR (71) DEVICE: MMC FIRST UNIT: 6144 NO. UNITS: 2048 USED UNITS: 0
ID: STEboot1 ( 3) DEVICE: MMC FIRST UNIT: 8192 NO. UNITS: 1024 USED UNITS: 0
ID: STEboot2 ( 4) DEVICE: MMC FIRST UNIT: 9216 NO. UNITS: 1024 USED UNITS: 0
ID: Dnt ( 5) DEVICE: MMC FIRST UNIT: 10240 NO. UNITS: 1024 USED UNITS: 0
ID: reserved ( 6) DEVICE: MMC FIRST UNIT: 11264 NO. UNITS: 1024 USED UNITS: 0
ID: CSPSAFS ( 7) DEVICE: MMC FIRST UNIT: 16384 NO. UNITS: 2048 USED UNITS: 0
ID: CSPSAFS2 ( 8) DEVICE: MMC FIRST UNIT: 18432 NO. UNITS: 2048 USED UNITS: 0
ID: EFS ( 9) DEVICE: MMC FIRST UNIT: 20480 NO. UNITS: 32768 USED UNITS: 0
ID: ModemFS (10) DEVICE: MMC FIRST UNIT: 53248 NO. UNITS: 32768 USED UNITS: 0
ID: ModemFS2 (11) DEVICE: MMC FIRST UNIT: 86016 NO. UNITS: 32768 USED UNITS: 0
ID: Fota (12) DEVICE: MMC FIRST UNIT: 118784 NO. UNITS: 102400 USED UNITS: 0
ID: IPL Modem (13) DEVICE: MMC FIRST UNIT: 380928 NO. UNITS: 128 USED UNITS: 0
ID: Modem (14) DEVICE: MMC FIRST UNIT: 385024 NO. UNITS: 28672 USED UNITS: 0
ID: Loke4 (15) DEVICE: MMC FIRST UNIT: 417792 NO. UNITS: 4096 USED UNITS: 0
ID: 2ndLoke4 (16) DEVICE: MMC FIRST UNIT: 421888 NO. UNITS: 4096 USED UNITS: 0
ID: PARAM (17) DEVICE: MMC FIRST UNIT: 425984 NO. UNITS: 32768 USED UNITS: 0
ID: Kernel (18) DEVICE: MMC FIRST UNIT: 458752 NO. UNITS: 32768 USED UNITS: 0
ID: Kernel2 (19) DEVICE: MMC FIRST UNIT: 491520 NO. UNITS: 32768 USED UNITS: 0
ID: SYSTEM (20) DEVICE: MMC FIRST UNIT: 524288 NO. UNITS: 2457600 USED UNITS: 0
ID: CACHEFS (21) DEVICE: MMC FIRST UNIT: 2981888 NO. UNITS: 1720320 USED UNITS: 0
ID: HIDDEN (22) DEVICE: MMC FIRST UNIT: 4702208 NO. UNITS: 655360 USED UNITS: 0
ID: DATAFS (23) DEVICE: MMC FIRST UNIT: 5357568 NO. UNITS: 9891840 USED UNITS: 0
&
[FONT=Verdana, Arial, Helvetica, sans-serif][SIZE=-1]$ dd --help dont need know more ac[SIZE=-1]tually[/SIZE][/SIZE][/FONT]
[FONT=Verdana, Arial, Helvetica, sans-serif][SIZE=-1][SIZE=-1]
[/SIZE][/SIZE][/FONT]
[FONT=Verdana, Arial, Helvetica, sans-serif][SIZE=-1][SIZE=-1][SIZE=-1]ex. [/SIZE][/SIZE][/SIZE][/FONT][FONT=Verdana, Arial, Helvetica, sans-serif][SIZE=-1][SIZE=-1][SIZE=-1]dd if=/dev/block/mmcblk0p20 of=/storage/extSdCard/boot.img bs=4096[/SIZE][/SIZE][/SIZE][/FONT]
Can someone install voodoo report from the market, run it and email the output zip file to [email protected] or attach it here.
I am thinking about making a toolkit for the S3 mini but just need some more information.
Also you cannot dump the data partition as it includes the Internal Storage (which is where you are trying to dump it to) so effectively yo uwould be trying to dump a 16/32GB partition and save it to itself which just isnt possible. Instead you have to tar the data folder and exclude the /data/media folder as follows:
adb shell su tar -pcvf /data/media/data.ext4.tar /data --exclude='data/media'
The toolkit will include a full NAND backup procedure in both CWM and TWRP formats.
Mark.
gummygum said:
Pulled this tabel from UART
Click to expand...
Click to collapse
Very nice. Did you use a specific Xloader command to obtain this information?
Check this out: http://docs.kali.org/armel-armhf/kali-linux-on-galaxy-note
I looked over the recovery and thought it looked ok (though thats an area i usually leave to pros), and attempted to make a x86 image so altering
Code:
dd if=/dev/block/mmcblk0p6 of=recovery.img_orig
and
dd if=recovery.img of=/dev/block/mmcblk0p6
and inputting this
Code:
dd if=/dev/block/mmcblk0p11 of=recovery.img_orig
and
dd if=recovery.img of=/dev/block/mmcblk0p11
then I rebooted and it hung up at the samsung galaxy tab 3 screen
How hard would it be to rewrite the recovery image linked to there to work on our device. Or if its in good shape I guess i screwed up making my x86 image of Kali any input of on either subject would be appreciated.
Had an idea as soon as I reflash and reroot and download a couple more files and reboot and finish updating this laptop I'm working on, ill try to break my gtab again
You can't. Those versions of Kali is for ARM (armel = ARM soft-float / armhf = ARM hard-float), while the GTab3 10.1. is x86.
But you should be able to modify any x86 (tablet-)linux for use with GTab3 10.1
Setialpha said:
You can't. Those versions of Kali is for ARM (armel = ARM soft-float / armhf = ARM hard-float), while the GTab3 10.1. is x86.
But you should be able to modify any x86 (tablet-)linux for use with GTab3 10.1
Click to expand...
Click to collapse
So you obviously didn't read the whole post.
I know the note 10.1 is arm and the gtab 10.1 is x86 I attempted to make a .img from the x86 live disc which obviously failed
I really just wanted someone to glance over the recovery.img and say with better authority than me if Offensive Security's recovery img needed anything.
However i will take your advise and toy around with some other distros that are x86 tablet ready in conjunction with that recovery. It only takes 5 min to reflash anyway.
hey
xkwr27 said:
So you obviously didn't read the whole post.
I know the note 10.1 is arm and the gtab 10.1 is x86 I attempted to make a .img from the x86 live disc which obviously failed
I really just wanted someone to glance over the recovery.img and say with better authority than me if Offensive Security's recovery img needed anything.
However i will take your advise and toy around with some other distros that are x86 tablet ready in conjunction with that recovery. It only takes 5 min to reflash anyway.
Click to expand...
Click to collapse
are you still up for this ?
i tried the same thing, i also tried swapping out the zimage from the kali recovery with p5210 stock
then changed any mmcblk refs i found in the init and instead of screen hang got it reboot, [over and over]
but didn't catch. this is totally doable and i wish i'd found this thread before starting another on the same subject.
but anyway i could go on forever.....we need to recruit people somehow... i would like a setup on this
tab so i could distro hop like i used to on pc :good:
Yes I'm still down for this, I've been so busy with work, and keeping my car running(done with the car now, motor/Trans rebuild) since my last post. Now I have my days off if not totally free free enough to put a few hours into this on my days off. I also know 2 people who could help if I can convince them one a relative with a name in the security industry and the other a relatively new guy to all things computer but with a knack for finding fixes that will be a help but for tonight I'm going to compare the two recoveries side by side during break and take notes. Then tomorrow I am going to see if I can put those notes to good use after I get back from taking my daughter and wife blackberry picking on my father's land.i figure I'll start on it noonish us central time and keep you updated...
xkwr27 said:
Yes I'm still down for this, I've been so busy with work, and keeping my car running(done with the car now, motor/Trans rebuild) since my last post. Now I have my days off if not totally free free enough to put a few hours into this on my days off. I also know 2 people who could help if I can convince them one a relative with a name in the security industry and the other a relatively new guy to all things computer but with a knack for finding fixes that will be a help but for tonight I'm going to compare the two recoveries side by side during break and take notes. Then tomorrow I am going to see if I can put those notes to good use after I get back from taking my daughter and wife blackberry picking on my father's land.i figure I'll start on it noonish us central time and keep you updated...
Click to expand...
Click to collapse
good deal, okay noob warning, but gleefully brick happy tester here.
right now i on the samsung open source site looking p5210 but not sure which
git-hub isn't an option for me as my surviving pc is a bit screwy but i still want to see the source
and try to get what the devs are saying, anyway i'm glad to hear from you
just thought i'd let you in on what i'm up to. hope to get something working.
:good:
do i need to get ubuntu 64bit for kernel stuff?
If you plan to tear into the recovery.img you'll need linux I use debian or debian based distro's, but ubuntu will work just fine.
https://01.org/android-ia
Not sure if this site will help but i'll post it anyways
I'll keep trying to post useful stuff
http://forum.xda-developers.com/showthread.php?t=1916936
Hope this helps somehow
Can we not change the partitions to whatever sizes we want using ODIN and .pit files ? if yes then we can do ANYTHING
Excercise caution. This MAY have the pit file for our device
http://forum.xda-developers.com/showthread.php?t=2526119
hey
Nitro_123 said:
https://01.org/android-ia
Not sure if this site will help but i'll post it anyways
I'll keep trying to post useful stuff
http://forum.xda-developers.com/showthread.php?t=1916936
Hope this helps somehow
Can we not change the partitions to whatever sizes we want using ODIN and .pit files ? if yes then we can do ANYTHING
Excercise caution. This MAY have the pit file for our device
http://forum.xda-developers.com/showthread.php?t=2526119
Click to expand...
Click to collapse
cool :good: reading:good:
as for repartitiong hold off for now but, read this anyway,
copy every command you see and keep in organized file for reference
http://forum.xda-developers.com/showthread.php?t=1388996
this command in term should pull pit file [get it right,check,double,check,triple check] must su first i believe
dd if=/dev/block/mmcblk0 of=/sdcard/out.pit bs=8 count=481 skip=2176
to xkwr27 hi, you're comparing with stock recovery right?
In terms of custom bootloaders we could install grub onto the device. but first we need to figure out the boot order.
http://forum.xda-developers.com/showthread.php?t=1018862 This thread is an amazing thread for samsung related stuff but kind of off topic for us.
Is there any way of figuring out the way the device boots ?
Sorry for stressing boot order and stuff so much but I really think it's the key to everything.
If we install GRUB after that everything else will be a piece of cake.
http://www.gnu.org/software/grub/
hey
Nitro_123 said:
In terms of custom bootloaders we could install grub onto the device. but first we need to figure out the boot order.
http://forum.xda-developers.com/showthread.php?t=1018862 This thread is an amazing thread for samsung related stuff but kind of off topic for us.
Is there any way of figuring out the way the device boots ?
Sorry for stressing boot order and stuff so much but I really think it's the key to everything.
If we install GRUB after that everything else will be a piece of cake.
http://www.gnu.org/software/grub/
Click to expand...
Click to collapse
the boot sequence is more where my thinking is going to.
my understanding is there are three stages , power on the boot loader does it's work, the kernel get's up and lays out the ramdrive and hardware
and get's the usual/basic/expected linux stuff going [yes, linux is already present,a form of it anyway] and finally, the android user space stuff.
altering something in the process to halt/bypass that last stage and get to , for now at least, a command prompt is the thought.
the hardware hacking looks really neat and is a good find as far as gaining insight on the basic boot process so thank you for
pointing me to it. having no up to speed modern pc i'm left to do what i can on my tab and can't risk it. but i DID find a
a kernel/boot img pack/repack/editing setup that i'm already using on my tab!!!
the link is http://forum.xda-developers.com/showthread.php?t=2073775
read the op then go to my post on the last page.
grub would be sweet though, wouldn't it ?
round one
okay this is what i did today
swapped busybox [arm] for [x86]
added parted in bin
replaced symlink named mtab==>/proc/self/mounts with actual file
corrected [?] mmcblk,loop references in hooks/looproot
changed this in init to experiment [attempt to return to android if fail,] marked edit and commented
if [ "$(stat -c %D /)" = "$(stat -c %D /new_root)" ]; then
#if [ "$(stat -c %D /)" = "$(stat -c %D /new_root)" ]; then
# Nothing got mounted on /new_root. This is the end, we don't know what to do anymore
# We fall back into a shell, but the shell has now PID 1
# This way, manual recovery is still possible.
init=/init
# err "Failed to mount the real root device." [edit]
# echo "Bailing out, you are on your own. Good luck." [edit]
# echo [edit]
# launch_interactive_shell --exec [edit]
elif [ ! -x "/new_root${init}" ]; then
# Successfully mounted /new_root, but ${init} is missing
# The same logic as above applies
err "Root device mounted successfully, but ${init} does not exist."
echo "Bailing out, you are on your own. Good luck."
echo
launch_interactive_shell --exec
fi
swapped zimage [from stock reco]
added modules [from stock reco]
result=fail, continuous reboot, re-odin recovery
try again tomorrow [yawn] uploaded experiment, contains .img ramdisk.gz and zimage
okay upload fail, i'll try again tomorrow grrrr.
moonbutt74 said:
okay this is what i did today
swapped busybox [arm] for [x86]
added parted in bin
replaced symlink named mtab==>/proc/self/mounts with actual file
corrected [?] mmcblk,loop references in hooks/looproot
changed this in init to experiment [attempt to return to android if fail,] marked edit and commented
if [ "$(stat -c %D /)" = "$(stat -c %D /new_root)" ]; then
#if [ "$(stat -c %D /)" = "$(stat -c %D /new_root)" ]; then
# Nothing got mounted on /new_root. This is the end, we don't know what to do anymore
# We fall back into a shell, but the shell has now PID 1
# This way, manual recovery is still possible.
init=/init
# err "Failed to mount the real root device." [edit]
# echo "Bailing out, you are on your own. Good luck." [edit]
# echo [edit]
# launch_interactive_shell --exec [edit]
elif [ ! -x "/new_root${init}" ]; then
# Successfully mounted /new_root, but ${init} is missing
# The same logic as above applies
err "Root device mounted successfully, but ${init} does not exist."
echo "Bailing out, you are on your own. Good luck."
echo
launch_interactive_shell --exec
fi
swapped zimage [from stock reco]
added modules [from stock reco]
result=fail, continuous reboot, re-odin recovery
try again tomorrow [yawn] uploaded experiment, contains .img ramdisk.gz and zimage
okay upload fail, i'll try again tomorrow grrrr.
Click to expand...
Click to collapse
hahaha i wish you good luck
thanks
FurFur_ said:
hahaha i wish you good luck
Click to expand...
Click to collapse
i've been through roughly 17 different experiments by now
but i'm too stupid to quit so we'll see :laugh:
---------- Post added at 10:46 PM ---------- Previous post was at 10:38 PM ----------
xkwr27 said:
So you obviously didn't read the whole post.
I know the note 10.1 is arm and the gtab 10.1 is x86 I attempted to make a .img from the x86 live disc which obviously failed
I really just wanted someone to glance over the recovery.img and say with better authority than me if Offensive Security's recovery img needed anything.
However i will take your advise and toy around with some other distros that are x86 tablet ready in conjunction with that recovery. It only takes 5 min to reflash anyway.
Click to expand...
Click to collapse
so if i'm understanding this right the samsung bootloader [which we don't mess with....snicker]
is initiating the command which grabs the kernel and get's things rolling..?
even if i'm not right in the init.rc scripting language is there a means to repeat that process ===> initramfs,bzimage ?
Ok the 3 key combos tell the tablet what to do 1 is power only boots normal 2 is power + volume up boots recovery 3 is power + volume down boots to download mode (odin)... what offensive security did was rewrite the recovery.img so that instead of launching you to the normal recovery all it does is tells the tab to boot the kali img in /SdCard/ so if you just power up with combo 1 it should still boot normal and 3 should still put you in odin mode but 2 will tell the tab to boot kali instead so all we should need is busybox maybe , a x86 kali img and a recovery img similar to the offensive security one. That is why I'm working to pick this recovery.img apart.
hey
i flashed the image as is first ; mmcblk's dont matchup in hook/looproot ; corrected[?] them no dice
aside from zimage&module&busybox mixing and matching
i think something with the hooks is the stumper
this is the ramdisk, i wasn't sure if you were asking or me to crack the image open or not,
i was hoping you might have a handle on kernel command lines.
if it comes to kernel building/compiling i'm boned:crying:
if there's something you want me to try or test let me know. :good:
kernel command
no_console_suspend=1 console=null
xkwr27 said:
Ok the 3 key combos tell the tablet what to do 1 is power only boots normal 2 is power + volume up boots recovery 3 is power + volume down boots to download mode (odin)... what offensive security did was rewrite the recovery.img so that instead of launching you to the normal recovery all it does is tells the tab to boot the kali img in /SdCard/ so if you just power up with combo 1 it should still boot normal and 3 should still put you in odin mode but 2 will tell the tab to boot kali instead so all we should need is busybox maybe , a x86 kali img and a recovery img similar to the offensive security one. That is why I'm working to pick this recovery.img apart.
Click to expand...
Click to collapse
Mate that sounds very good I'm so busy with life nowadays Final year of school I don't know too much and I can't learn anything cause I have literally no time
I won't be posting too often Good luck with your project. Eager to see some success :fingers-crossed::good:
Santos10 Bootloader trace:
Code:
IA32 CPU Firmware
Copyright (C) 1999-2013, Intel Corporation. All rights reserved.
7[0;23r[24;75H[1K[24;1H[1mIntel(R) Atom(TM) Z2560 CPU FW 00.73 (INTELFDK)[0m8------------------------------>FOR Teewinot ONLY<-----------------------------
******************************************************************************
************** Customer release based on Rel 00.49 + TWN changes**************
**************** BZ=115220 Bypass time/date check for product ****************
****************** BZ=118523 Cold Reset on ExecuteOS failure *****************
****** BZ=124478[TW 346-500-676] Request for logging enhancement in IAFW *****
************* BZ=127192 Disable Active Refresh during JEDEC Init *************
******************* BZ=none include ucode patch M013065110E ******************
**************************** New in this code drop ***************************
***** BZ=none Changed trace to match TWN RAMDUMP application requirement *****
*************** BZ=none Removed UART and PTI HW output methods ***************
******** Short circuiting the emInit when a fixed battery is detected. *******
********************* Customization done 201308261512 MST ********************
******************************************************************************
[37;41m******************************INTEL CONFIDENTIAL******************************
[0m
0x1E, 0x20, 0x21,
ERROR:::::SPID Not Programmed, Fake data being used based on IFWI version
ERROR:::::SPID FRU Not Programmed, Fake data being used based on IFWI version
OSC_CLK3 defaults only
0x22,
OEM board; Skip spidBasedPanelNdxUpdate
0x23,
Forced Battery via SMIP FPO Bit 2
0x28, 0x2A, 0x2B, in csSFIDevsEntries, HW Id 0x0019
SFI Dev...PR3
in csSFIGpioEntries, HW Id 0x0019
SFIOEMBInit:tbl->spidTbl update
0x2C, 0x2D, 0x2F PostCodes Done
IA32 FW: CPU v000.073/00.49; SUPP v000.073/00.49; VH: 000.081/00.51
IA Timestamp: 2013.08.26:18.00 (INTELFDK)
SCU FW: ROM 177.000/B1.00; RT 033.046/21.2E
PUNIT FW: v160.064/A0.40
IFWI: v249.086/F9.56
PL: 0000010E
Config & PCB: OEM Platform, C, CLV+ B1, Samsung (01,00) SR 4Gb 1067 1GB
FHOB DW0/DW1: 00000104:00010140
I2C Expander: FFFFFFFC:0000000F
IA Options: 024020A1:00000000:03E00000:80005C00:00000101;1264
[OS HASH VERIFY] [EIST] [eMMC] [VALID BATT][WDT]
Loading OS...
pOsip = 1000000
-->OSIP verified
00000000 E0000000
[COLOR="Red"]Android COS path taken
E0000000 D303000A[/COLOR]
[COLOR="red"]Boot path override selected OS image 0[/COLOR] (OS Attribute 0x00, Reboot Reason 0x0A)
D303000A D303000A
Splash disabled in GCT
Splash display time: 2 ms
[COLOR="red"]-->Bootable OS image 0 found for requested type 2 [/COLOR](OSII attribute 0x00)
-->[COLOR="red"]Loading OS image 0 from eMMC block 0x00000032 to DRAM address 0x010FFE20[/COLOR]
-->Starting transfer of 0xA11 512-byte blocks to DRAM
-->Done loading OS Image to DRAM
-->platformConfigBuffer_pt.scuFhobDw0.osven != 0
-->osIndex: 0, Signed Image
OS image 0 PASSED verify
Booting COS
*********************************
Starting command line:
-init=/init pci=noearly console=ttyMFD2 console=ttyS0 console=logk0 earlyprintk=nologger loglevel=8 hsu_dma=7 kmemleak=off ptrace.ptrace_can_access=1 androidboot.bootmedia=sdcard androidboot.hardware=ctp_pr1 emmc_ipanic.ipanic_part_number=1 ip=50.0.0.2:50.0.0.1::255.255.255.0::usb0:on hsu_rx_wa g_android.fastboot=1 droidboot.scratch=100
-
OSNIB.wakesrc = 0x3
OSNIB.RR = 0xA
Battery is high enough for normal boot
4166mV > 0mV
Ending command line:
-init=/init pci=noearly console=ttyMFD2 console=ttyS0 console=logk0 earlyprintk=nologger loglevel=8 hsu_dma=7 kmemleak=off ptrace.ptrace_can_access=1 androidboot.bootmedia=sdcard androidboot.hardware=ctp_pr1 emmc_ipanic.ipanic_part_number=1 ip=50.0.0.2:50.0.0.1::255.255.255.0::usb0:on hsu_rx_wa g_android.fastboot=1 droidboot.scratch=100 androidboot.wakesrc=03 androidboot.mode=charger-
*********************************
WDT aka Timer7 setup
Warn Duration for Timer7: 00 seconds
Start Timer7 bit 0 -> 1: 00000000000000000000000000000000
[0;24r[24;1H[2KM
Calling OS entry point --> 0x01101000 ...
Using NEW OSHOB structure size = 176 bytes
OSNIB size = 32 bytes OEMNIB size = 64 bytes
0xFF00_0510 FullChipRegister: Status flag = 0x0
0xFF10_0510 SCFabricRegister: Status flag = 0x0
Watchdog Disabled!
usb is connected, skip to set uart path
__stmpe811_write : fail
MUIC: CONTROL1:0x00
MUIC: CONTROL1:0x00
MUIC: CONTROL2:0x3b
MUIC: CONTROL2:0x3b
[SCU_IPC_DEBUG] board ID: NOT_IDENTIFIED(8)
VERSION : 0xa501
mmc_read_ext_csd : ext_csd_rev = 0x7
cardtype: 0x00000007
SB_MMC_HS_52MHZ_1_8V_3V_IO
mmc->card_caps: 0x00000311
mmc->host_caps: 0x00000311
!!!Enter 8 Bit mode.!!!
clt_mmc_init: mmc->capacity = 0x1d56000
[BOOT] RESETIRQ1=0x00 RESETIRQ2=0x00 (interrupt tree)
[BOOT] SCU_TR=0x00020013 IA_TR=0xffffffff (oshob)
[BOOT] RR=0x00 WD=0x00 ALARM=0x00 (osnib)
[BOOT] WAKESRC=0x03 RESETIRQ1=0x20 RESETIRQ2=0x00 (osnib)
Samsung S-Boot 4.0-1816966 for GT-P5200 (Nov 26 2013 - 01:43:08)
CLT(EVT 0.0) / 1024MB / 15020MB / Rev 8 / P5200XXUAMK8
pit_check_signature (PIT) valid.
initialize_ddi_data: usable! (159:0xc)
PARAM ENV VERSION: v1.0..
pressed_key = 0x1
clt_charger_init : [battery] using external charger init(3)
STATUS1:0x3f, 2:0x43
vbvolt=0x1, chgtyp=0x3, adc=0x1f, ret=0x1031f
[check_cable_type] : Output of USB Charger Detection 3
[max77693_init_charger] : attached device(0x02) : TA
clt_max77693_set_charger_state: chg_cnfg_02 (0x1f) -> (0x1f) -> (0x1f)
clt_max77693_set_charger_state: chg_cnfg_03 (0x00) -> (0x00) -> (0x00)
clt_max77693_set_charger_state: chg_cnfg_04 (0xdd) -> (0xdd) -> (0xdd)
clt_max77693_set_charger_state: chg_cnfg_09 (0x64) -> (0x64) -> (0x64)
set_charger_state : buck(1), chg(0), reg(0x04)
init_fuel_gauge: Start!!
[0] get_adc_battid() = 92
[1] get_adc_battid() = 92
[2] get_adc_battid() = 92
get_adc_battid() = 92
init_fuel_gauge: Battery type : SDI
init_fuel_gauge: Already initialized (0x32cd, SDI type)
STATUS1:0x3f, 2:0x43
vbvolt=0x1, chgtyp=0x3, adc=0x1f, ret=0x1031f
fuel_gauge_compensate_soc: Start!!
fuel_gauge_read_soc: SOC(73), data(0x491b)
fuel_gauge_read_vcell: VCELL(4071), data(0xcb92)
calculate_table_soc: Get table SOC in case of charging!!
calculate_table_soc: i(1), vcell(4071), table_soc(88)
differ(15), table_soc(88), RepSOC(73)
clt_charger_init : cable_type(0x02)
set_charger_state : buck(1), chg(1), reg(0x05)
intel_scu_ipc_cmd_oemnib : done => 0x0
check_reboot_cmd: nCmd = 0 ... skip check_reboot_cmd
debug level = 0x4f4c
disable max77693 manual reset
clt_max77693_disable_manual_reset: set max77693 MANCTRL1 val = 0x4
clt_max77693_disable_manual_reset: read max77693 MANCTRL1 val = 0x4
disable PMIC cod off triggered by PWRBTN#: 6
do_keypad: 0x1
intel_scu_ipc_cmd_oemnib : done => 0x0
check_download: 0
Is_lpm_boot : boot-mode saved in param = 0
Is_lpm_boot : jig-on level = 0, ignore...
STATUS1:0x3f, 2:0x43
vbvolt=0x1, chgtyp=0x3, adc=0x1f, ret=0x1031f
stat=0x1031f, adc=0x1f, chg=0x3, vbvolt=1, pinLevel=1
fuel_gauge_read_vcell: VCELL(4071), data(0xcb92)
fuel_gauge_read_soc: SOC(73), data(0x491b)
check_low_battery : rb=0 jig=0
check_low_battery : v=4071 soc=73
skip check low battery
scr_draw_image: draw 'logo.jpg'...
read 'logo.jpg'(105420) completed.
<start_checksum:355>CHECKSUM_HEADER_SECTOR :4096
<start_checksum:357>offset:6144, size:6296
<start_checksum:361>CHECKSUM_HEADER_INFO : NeedChecksum:0 PartNo:27
Not Need Movinand Checksum
Movinand Checksum Confirmation Pass
load_kernel: loading boot image from 106496..
total size : 8495104
pit_check_signature (BOOT) valid.
Set valid sign flag
if_ddi_data: succeeded. (159:0xc)
BOOT_MAGIC == ANDROID!
CMDLINE LENGTH = 538
CMDLINE = init=/init console=sec_log_buf kmemleak=off ptrace.ptrace_can_access=1 androidboot.bootmedia=sdcard androidboot.hardware=santos103g sec_debug.level=0 loglevel=0 androidboot.debug_level=0x4f4c vmalloc=256m [email protected] sec_bootfb=0x3f000000 lcd_panel_id=0 androidboot.revision=8 switch_sel=3 cordon=615d013e557994c8ad53b3325c31b124 connie=GT-P5200_OPEN_EUR_cf878c59e3c2eeb1cdb40863938b834d androidboot.emmc_checksum=3 androidboot.bootloader=P5200XXUAMK8 androidboot.serialno=4300b61fdc125000 snd_soc_core.pmdown_time=1000 jig=0
Bootstub: map SFI MMAP to e820 table
add mmap: 0x00000000 0x00098000 1
add mmap: 0x00100000 0x00580000 2
add mmap: 0x00680000 0x00680000 1
add mmap: 0x00d00000 0x00300000 2
add mmap: 0x01000000 0x35ff0000 1
add mmap: 0x36ff0000 0x0090d000 2
add mmap: 0x378fd400 0x00100000 2
add mmap: 0x379fd400 0x02602000 1
add mmap: 0x3a000000 0x02200000 2
add mmap: 0x3c200000 0x02d00000 1
add mmap: 0x3ef00000 0x00100000 2
add mmap: 0x3f000000 0x01000000 2
add mmap: 0xfec00000 0x00001000 2
add mmap: 0xfee00000 0x00001000 2
add mmap: 0xff000000 0x01000000 2
IMR6 start=0x3a000000 end=0x3c1fffff
new mmap: 0x3a000000 0x02200000 2
IMR7 start=0x00100000 end=0x0067ffff
new mmap: 0x00100000 0x00580000 2
Final E820 table:
e820: 0x00000000 0x00098000 1
e820: 0x00100000 0x00580000 2
e820: 0x00680000 0x00680000 1
e820: 0x00d00000 0x00300000 2
e820: 0x01000000 0x35ff0000 1
e820: 0x36ff0000 0x0090d000 2
e820: 0x378fd400 0x00100000 2
e820: 0x379fd400 0x02602000 1
e820: 0x3a000000 0x02200000 2
e820: 0x3c200000 0x02d00000 1
e820: 0x3ef00000 0x00100000 2
e820: 0x3f000000 0x01000000 2
e820: 0xfec00000 0x00001000 2
e820: 0xfee00000 0x00001000 2
e820: 0xff000000 0x01000000 2
Final mb_mmap table:
mb_mmap: 0x00000000 0x00098000 1
mb_mmap: 0x00100000 0x00580000 0
mb_mmap: 0x00680000 0x00680000 1
mb_mmap: 0x00d00000 0x00300000 0
mb_mmap: 0x01000000 0x35ff0000 1
mb_mmap: 0x36ff0000 0x0090d000 0
mb_mmap: 0x378fd400 0x00100000 0
mb_mmap: 0x379fd400 0x02602000 1
mb_mmap: 0x3a000000 0x02200000 0
mb_mmap: 0x3c200000 0x02d00000 1
mb_mmap: 0x3ef00000 0x00100000 0
mb_mmap: 0x3f000000 0x01000000 0
mb_mmap: 0xfec00000 0x00001000 0
mb_mmap: 0xfee00000 0x00001000 0
mb_mmap: 0xff000000 0x01000000 0
Using bzImage to boot
Relocating initramfs to high memory ...
usb is connected, skip to set uart path
0xFF00_0510 FullChipRegister: Status flag = 0x0
0xFF10_0510 SCFabricRegister: Status flag = 0x0
Jump to kernel 32bit entry ...0x05003c00
I check interesting rows by red color. But there is easy way: need to compile x86 binaries and inject some code to twrp recovery. After that Linux OS must load from any img or partition on internal or external SD. Manual for coding this: link. This method accept to boot any second linux-based OS from any defined partition. It's on Russian - use translator to read.
Santos10 partiton table:
Code:
major minor #blocks name
7 0 61362 loop0
7 1 7308 loop1
179 0 15380480 mmcblk0
179 1 3072 mmcblk0p1
179 2 20480 mmcblk0p2
179 3 16384 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 358400 mmcblk0p6
179 7 4096 mmcblk0p7
179 8 2416640 mmcblk0p8
179 9 12337152 mmcblk0p9
259 0 20480 mmcblk0p10
259 1 20480 mmcblk0p11
259 2 20480 mmcblk0p12
259 3 102400 mmcblk0p13
259 4 4096 mmcblk0p14
259 5 4096 mmcblk0p15
259 6 4096 mmcblk0p16
259 7 12288 mmcblk0p17
259 8 2048 mmcblk0p18
259 9 2048 mmcblk0p19
259 10 1024 mmcblk0p20
259 11 8192 mmcblk0p21
179 40 8192 mmcblk0gp0
179 30 1 mmcblk0rpmb
[COLOR="Red"]179 20 4096 mmcblk0boot1[/COLOR]
[COLOR="red"]179 10 4096 mmcblk0boot0[/COLOR]
252 0 307200 zram0
179 50 1955840 mmcblk1
179 51 1954816 mmcblk1p1
253 0 61362 dm-0
253 1 7308 dm-1]
Look at the red text i marked. I think we already have dual boot bootloader by Samsung.
Angel_666 said:
Santos10 Bootloader trace:
Code:
IA32 CPU Firmware
Copyright (C) 1999-2013, Intel Corporation. All rights reserved.
7[0;23r[24;75H[1K[24;1H[1mIntel(R) Atom(TM) Z2560 CPU FW 00.73 (INTELFDK)[0m8------------------------------>FOR Teewinot ONLY<-----------------------------
******************************************************************************
************** Customer release based on Rel 00.49 + TWN changes**************
**************** BZ=115220 Bypass time/date check for product ****************
****************** BZ=118523 Cold Reset on ExecuteOS failure *****************
****** BZ=124478[TW 346-500-676] Request for logging enhancement in IAFW *****
************* BZ=127192 Disable Active Refresh during JEDEC Init *************
******************* BZ=none include ucode patch M013065110E ******************
**************************** New in this code drop ***************************
***** BZ=none Changed trace to match TWN RAMDUMP application requirement *****
*************** BZ=none Removed UART and PTI HW output methods ***************
******** Short circuiting the emInit when a fixed battery is detected. *******
********************* Customization done 201308261512 MST ********************
******************************************************************************
[37;41m******************************INTEL CONFIDENTIAL******************************
[0m
0x1E, 0x20, 0x21,
ERROR:::::SPID Not Programmed, Fake data being used based on IFWI version
ERROR:::::SPID FRU Not Programmed, Fake data being used based on IFWI version
OSC_CLK3 defaults only
0x22,
OEM board; Skip spidBasedPanelNdxUpdate
0x23,
Forced Battery via SMIP FPO Bit 2
0x28, 0x2A, 0x2B, in csSFIDevsEntries, HW Id 0x0019
SFI Dev...PR3
in csSFIGpioEntries, HW Id 0x0019
SFIOEMBInit:tbl->spidTbl update
0x2C, 0x2D, 0x2F PostCodes Done
IA32 FW: CPU v000.073/00.49; SUPP v000.073/00.49; VH: 000.081/00.51
IA Timestamp: 2013.08.26:18.00 (INTELFDK)
SCU FW: ROM 177.000/B1.00; RT 033.046/21.2E
PUNIT FW: v160.064/A0.40
IFWI: v249.086/F9.56
PL: 0000010E
Config & PCB: OEM Platform, C, CLV+ B1, Samsung (01,00) SR 4Gb 1067 1GB
FHOB DW0/DW1: 00000104:00010140
I2C Expander: FFFFFFFC:0000000F
IA Options: 024020A1:00000000:03E00000:80005C00:00000101;1264
[OS HASH VERIFY] [EIST] [eMMC] [VALID BATT][WDT]
Loading OS...
pOsip = 1000000
-->OSIP verified
00000000 E0000000
[COLOR="Red"]Android COS path taken
E0000000 D303000A[/COLOR]
[COLOR="red"]Boot path override selected OS image 0[/COLOR] (OS Attribute 0x00, Reboot Reason 0x0A)
D303000A D303000A
Splash disabled in GCT
Splash display time: 2 ms
[COLOR="red"]-->Bootable OS image 0 found for requested type 2 [/COLOR](OSII attribute 0x00)
-->[COLOR="red"]Loading OS image 0 from eMMC block 0x00000032 to DRAM address 0x010FFE20[/COLOR]
-->Starting transfer of 0xA11 512-byte blocks to DRAM
-->Done loading OS Image to DRAM
-->platformConfigBuffer_pt.scuFhobDw0.osven != 0
-->osIndex: 0, Signed Image
OS image 0 PASSED verify
Booting COS
*********************************
Starting command line:
-init=/init pci=noearly console=ttyMFD2 console=ttyS0 console=logk0 earlyprintk=nologger loglevel=8 hsu_dma=7 kmemleak=off ptrace.ptrace_can_access=1 androidboot.bootmedia=sdcard androidboot.hardware=ctp_pr1 emmc_ipanic.ipanic_part_number=1 ip=50.0.0.2:50.0.0.1::255.255.255.0::usb0:on hsu_rx_wa g_android.fastboot=1 droidboot.scratch=100
-
OSNIB.wakesrc = 0x3
OSNIB.RR = 0xA
Battery is high enough for normal boot
4166mV > 0mV
Ending command line:
-init=/init pci=noearly console=ttyMFD2 console=ttyS0 console=logk0 earlyprintk=nologger loglevel=8 hsu_dma=7 kmemleak=off ptrace.ptrace_can_access=1 androidboot.bootmedia=sdcard androidboot.hardware=ctp_pr1 emmc_ipanic.ipanic_part_number=1 ip=50.0.0.2:50.0.0.1::255.255.255.0::usb0:on hsu_rx_wa g_android.fastboot=1 droidboot.scratch=100 androidboot.wakesrc=03 androidboot.mode=charger-
*********************************
WDT aka Timer7 setup
Warn Duration for Timer7: 00 seconds
Start Timer7 bit 0 -> 1: 00000000000000000000000000000000
[0;24r[24;1H[2KM
Calling OS entry point --> 0x01101000 ...
Using NEW OSHOB structure size = 176 bytes
OSNIB size = 32 bytes OEMNIB size = 64 bytes
0xFF00_0510 FullChipRegister: Status flag = 0x0
0xFF10_0510 SCFabricRegister: Status flag = 0x0
Watchdog Disabled!
usb is connected, skip to set uart path
__stmpe811_write : fail
MUIC: CONTROL1:0x00
MUIC: CONTROL1:0x00
MUIC: CONTROL2:0x3b
MUIC: CONTROL2:0x3b
[SCU_IPC_DEBUG] board ID: NOT_IDENTIFIED(8)
VERSION : 0xa501
mmc_read_ext_csd : ext_csd_rev = 0x7
cardtype: 0x00000007
SB_MMC_HS_52MHZ_1_8V_3V_IO
mmc->card_caps: 0x00000311
mmc->host_caps: 0x00000311
!!!Enter 8 Bit mode.!!!
clt_mmc_init: mmc->capacity = 0x1d56000
[BOOT] RESETIRQ1=0x00 RESETIRQ2=0x00 (interrupt tree)
[BOOT] SCU_TR=0x00020013 IA_TR=0xffffffff (oshob)
[BOOT] RR=0x00 WD=0x00 ALARM=0x00 (osnib)
[BOOT] WAKESRC=0x03 RESETIRQ1=0x20 RESETIRQ2=0x00 (osnib)
Samsung S-Boot 4.0-1816966 for GT-P5200 (Nov 26 2013 - 01:43:08)
CLT(EVT 0.0) / 1024MB / 15020MB / Rev 8 / P5200XXUAMK8
pit_check_signature (PIT) valid.
initialize_ddi_data: usable! (159:0xc)
PARAM ENV VERSION: v1.0..
pressed_key = 0x1
clt_charger_init : [battery] using external charger init(3)
STATUS1:0x3f, 2:0x43
vbvolt=0x1, chgtyp=0x3, adc=0x1f, ret=0x1031f
[check_cable_type] : Output of USB Charger Detection 3
[max77693_init_charger] : attached device(0x02) : TA
clt_max77693_set_charger_state: chg_cnfg_02 (0x1f) -> (0x1f) -> (0x1f)
clt_max77693_set_charger_state: chg_cnfg_03 (0x00) -> (0x00) -> (0x00)
clt_max77693_set_charger_state: chg_cnfg_04 (0xdd) -> (0xdd) -> (0xdd)
clt_max77693_set_charger_state: chg_cnfg_09 (0x64) -> (0x64) -> (0x64)
set_charger_state : buck(1), chg(0), reg(0x04)
init_fuel_gauge: Start!!
[0] get_adc_battid() = 92
[1] get_adc_battid() = 92
[2] get_adc_battid() = 92
get_adc_battid() = 92
init_fuel_gauge: Battery type : SDI
init_fuel_gauge: Already initialized (0x32cd, SDI type)
STATUS1:0x3f, 2:0x43
vbvolt=0x1, chgtyp=0x3, adc=0x1f, ret=0x1031f
fuel_gauge_compensate_soc: Start!!
fuel_gauge_read_soc: SOC(73), data(0x491b)
fuel_gauge_read_vcell: VCELL(4071), data(0xcb92)
calculate_table_soc: Get table SOC in case of charging!!
calculate_table_soc: i(1), vcell(4071), table_soc(88)
differ(15), table_soc(88), RepSOC(73)
clt_charger_init : cable_type(0x02)
set_charger_state : buck(1), chg(1), reg(0x05)
intel_scu_ipc_cmd_oemnib : done => 0x0
check_reboot_cmd: nCmd = 0 ... skip check_reboot_cmd
debug level = 0x4f4c
disable max77693 manual reset
clt_max77693_disable_manual_reset: set max77693 MANCTRL1 val = 0x4
clt_max77693_disable_manual_reset: read max77693 MANCTRL1 val = 0x4
disable PMIC cod off triggered by PWRBTN#: 6
do_keypad: 0x1
intel_scu_ipc_cmd_oemnib : done => 0x0
check_download: 0
Is_lpm_boot : boot-mode saved in param = 0
Is_lpm_boot : jig-on level = 0, ignore...
STATUS1:0x3f, 2:0x43
vbvolt=0x1, chgtyp=0x3, adc=0x1f, ret=0x1031f
stat=0x1031f, adc=0x1f, chg=0x3, vbvolt=1, pinLevel=1
fuel_gauge_read_vcell: VCELL(4071), data(0xcb92)
fuel_gauge_read_soc: SOC(73), data(0x491b)
check_low_battery : rb=0 jig=0
check_low_battery : v=4071 soc=73
skip check low battery
scr_draw_image: draw 'logo.jpg'...
read 'logo.jpg'(105420) completed.
<start_checksum:355>CHECKSUM_HEADER_SECTOR :4096
<start_checksum:357>offset:6144, size:6296
<start_checksum:361>CHECKSUM_HEADER_INFO : NeedChecksum:0 PartNo:27
Not Need Movinand Checksum
Movinand Checksum Confirmation Pass
load_kernel: loading boot image from 106496..
total size : 8495104
pit_check_signature (BOOT) valid.
Set valid sign flag
if_ddi_data: succeeded. (159:0xc)
BOOT_MAGIC == ANDROID!
CMDLINE LENGTH = 538
CMDLINE = init=/init console=sec_log_buf kmemleak=off ptrace.ptrace_can_access=1 androidboot.bootmedia=sdcard androidboot.hardware=santos103g sec_debug.level=0 loglevel=0 androidboot.debug_level=0x4f4c vmalloc=256m [email protected] sec_bootfb=0x3f000000 lcd_panel_id=0 androidboot.revision=8 switch_sel=3 cordon=615d013e557994c8ad53b3325c31b124 connie=GT-P5200_OPEN_EUR_cf878c59e3c2eeb1cdb40863938b834d androidboot.emmc_checksum=3 androidboot.bootloader=P5200XXUAMK8 androidboot.serialno=4300b61fdc125000 snd_soc_core.pmdown_time=1000 jig=0
Bootstub: map SFI MMAP to e820 table
add mmap: 0x00000000 0x00098000 1
add mmap: 0x00100000 0x00580000 2
add mmap: 0x00680000 0x00680000 1
add mmap: 0x00d00000 0x00300000 2
add mmap: 0x01000000 0x35ff0000 1
add mmap: 0x36ff0000 0x0090d000 2
add mmap: 0x378fd400 0x00100000 2
add mmap: 0x379fd400 0x02602000 1
add mmap: 0x3a000000 0x02200000 2
add mmap: 0x3c200000 0x02d00000 1
add mmap: 0x3ef00000 0x00100000 2
add mmap: 0x3f000000 0x01000000 2
add mmap: 0xfec00000 0x00001000 2
add mmap: 0xfee00000 0x00001000 2
add mmap: 0xff000000 0x01000000 2
IMR6 start=0x3a000000 end=0x3c1fffff
new mmap: 0x3a000000 0x02200000 2
IMR7 start=0x00100000 end=0x0067ffff
new mmap: 0x00100000 0x00580000 2
Final E820 table:
e820: 0x00000000 0x00098000 1
e820: 0x00100000 0x00580000 2
e820: 0x00680000 0x00680000 1
e820: 0x00d00000 0x00300000 2
e820: 0x01000000 0x35ff0000 1
e820: 0x36ff0000 0x0090d000 2
e820: 0x378fd400 0x00100000 2
e820: 0x379fd400 0x02602000 1
e820: 0x3a000000 0x02200000 2
e820: 0x3c200000 0x02d00000 1
e820: 0x3ef00000 0x00100000 2
e820: 0x3f000000 0x01000000 2
e820: 0xfec00000 0x00001000 2
e820: 0xfee00000 0x00001000 2
e820: 0xff000000 0x01000000 2
Final mb_mmap table:
mb_mmap: 0x00000000 0x00098000 1
mb_mmap: 0x00100000 0x00580000 0
mb_mmap: 0x00680000 0x00680000 1
mb_mmap: 0x00d00000 0x00300000 0
mb_mmap: 0x01000000 0x35ff0000 1
mb_mmap: 0x36ff0000 0x0090d000 0
mb_mmap: 0x378fd400 0x00100000 0
mb_mmap: 0x379fd400 0x02602000 1
mb_mmap: 0x3a000000 0x02200000 0
mb_mmap: 0x3c200000 0x02d00000 1
mb_mmap: 0x3ef00000 0x00100000 0
mb_mmap: 0x3f000000 0x01000000 0
mb_mmap: 0xfec00000 0x00001000 0
mb_mmap: 0xfee00000 0x00001000 0
mb_mmap: 0xff000000 0x01000000 0
Using bzImage to boot
Relocating initramfs to high memory ...
usb is connected, skip to set uart path
0xFF00_0510 FullChipRegister: Status flag = 0x0
0xFF10_0510 SCFabricRegister: Status flag = 0x0
Jump to kernel 32bit entry ...0x05003c00
I check interesting rows by red color. But there is easy way: need to compile x86 binaries an inject some code to twrp recovery. After that Linux OS must load from any img or partition on internal or external SD. Manual for coding this: link. It's on Russian - use translator to read.
Click to expand...
Click to collapse
Awesome work on that manual dude, now I have something to do while I'm at work bored... and we'll know what we can and can't remove/put in...
xkwr27 said:
Awesome work on that manual dude
Click to expand...
Click to collapse
If you mean manual on that site - it's not mine.
Post updated. Take a look at device partitions.
This is my partition table as generated by gdisk
Logical sector size: 512 bytes
Disk identifier (GUID): 98101B32-BBE2-4BF2-A06E-2BB33D000C20
Partition table holds up to 32 entries
First usable sector is 34, last usable sector is 15269854
Partitions will be aligned on 2-sector boundaries
Total free space is 313196 sectors (152.9 MiB)
Code:
# Name Start (sector) End (sector) Size Size (Sectors) Partition GUID Code
1 modem 131072 262143 64 MB 131072 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
2 sbl1 262144 263167 512KiB 1024 DEA0BA2C-CBDD-4805-B4F9-F428251C3E98
3 sbl1bak 263168 264191 512KiB 1024 DEA0BA2C-CBDD-4805-B4F9-F428251C3E98
4 aboot 264192 266239 1024KiB 2048 400FFDCD-22E0-47E7-9A23-F16ED9382388
5 abootbak 266240 268287 1024KiB 2048 400FFDCD-22E0-47E7-9A23-F16ED9382388
6 rpm 268288 269311 512KiB 1024 098DF793-D712-413D-9D4E-89D711772228
7 rpmbak 269312 270335 512KiB 1024 098DF793-D712-413D-9D4E-89D711772228
8 tz 270336 271871 768KiB 1536 A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4
9 tzbak 271872 273407 768KiB 1536 A053AA7F-40B8-4B1C-BA08-2F68AC71A4F4
10 pad 273408 275455 1024KiB 2048 EBD0A0A2-B9E5-4433-87C0-68B6B72699C7
11 modemst1 275456 278527 1.5MiB 3072 EBBEADAF-22C9-E33B-8F5D-0E81686A68CB
12 modemst2 278528 281599 1.5MiB 3072 0A288B1F-22C9-E33B-8F5D-0E81686A68CB
13 misc 281600 283647 1024KiB 2048 82ACC91F-357C-4A68-9C8F-689E1B1A23A1
14 fsc 283648 283649 1024Bytes 2 57B90A16-22C9-E33B-8F5D-0E81686A68CB
15 ssd 283650 283665 8KiB 16 2C86E742-745E-4FDD-BFD8-B6A7AC638772
16 splash 283666 304145 10MiB 20480 20117F86-E985-4357-B9EE-374BC1D8487D
17 DDR 393216 393279 32KiB 64 20A0C19C-286A-42FA-9CE7-F64C3226A794
18 fsg 393280 396351 1.5MiB 3072 638FF8E2-22C9-E33B-8F5D-0E81686A68CB
19 sec 396352 396383 16KiB 32 303E6AC3-AF15-4C54-9E9B-D9A8FBECF401
20 boot 396384 461919 32MiB 65536 20117F86-E985-4357-B9EE-374BC1D8487D
21 system 461920 4557919 2GB 4096000 97D7B011-54DA-4835-B3C4-917AD6E73D74
22 persist 4557920 4623455 32MiB 65536 6C95E238-E343-4BA8-B489-8681ED22AD0B
23 apedata 4623456 4688991 32MiB 65536 6C95E238-E343-4BA8-B489-8681ED22AD0B
24 cache 4688992 5213279 256MiB 524288 5594C694-C871-4B5F-90B1-690A6F68E0F7
25 recovery 5213280 5278815 32MiB 65536 9D72D4E4-9958-42DA-AC26-BEA7A90B0434
26 devinfo 5278816 5280863 1024KiB 2048 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
27 keystore 5373952 5374975 512KiB 1024 DE7D4029-0F5B-41C8-AE7E-F6C023A02B33
28 oem 5374976 5506047 64MiB 131072 7DB6AC55-ECB5-4E02-80DA-4D335B973332
29 config 5506048 5507071 512KiB 1024 91B72D4D-71E0-4CBF-9B8E-236381CFF17A
30 userdata 5507072 15269854 4.7GiB 9762783 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
My version of the tool is this
Code:
!/usr/bin/python
#===========================================================================
# This script parses "partition.xml" and creates numerous output files
# specifically, partition.bin, rawprogram.xml
# REFERENCES
# $Header: //source/qcom/qct/core/pkg/bootloaders/rel/1.2/boot_images/core/storage/tools/jsdcc/partition_load_pt/PartitioningTool.py#2 $
# $DateTime: 2012/01/12 16:00:13 $
# $Author: coresvc $
# when who what, where, why
# -------- --- -------------------------------------------------------
# 2011-03-22 ah rawprogram for GPT for 'grow' partition, since mjsdload.cmm couldn't handle big number
# 2011-03-22 ah Corrected final disk size patch (off by 1 sector), corrected GPT labels (uni-code)
# 2011-03-18 ah Fixed default bug for DISK_SIGNATURE, align_wpb -> align
# 2011-03-16 ah New DISK_SIGNATURE tag added for MBR partitions, Split partition0.bin into
# MBR0.bin and EBR0.bin, Corrected bug in backup GPT DISK patching
# 2011-03-10 ah Removes loadpt.cmm, splits partition0.bin to MBR0.bin, EBR0.bin
# 2011-03-09 ah Much more error checking, cleaner, adds "align_wpb" tag
# 2011-02-14 ah Added patching of DISK for GPT
# 2011-02-02 ah Allow MBR Type to be specified as "4C" or "0x4C"
# 2011-25-01 ah Outputs "patch.xml" as well, allows more optimal partition alignment
# 2010-12-01 ah Matching QPST, all EXT partitions 64MB aligned (configurable actually)
# More error checking, Removed CHS option, GPT output is 2 files (primary and backup)
# 2010-10-26 ah better error checking, corrected typo on physical_partition for > 0
# 2010-10-25 ah adds GPT, CFILE output, various other features
# 2010-10-08 ah released to remove compile errors of missing PERL script modules
I am purposely trying to keep my fsc partition to 1kb. I can make the change in my xml file to 2kb and the tool will continue. If I leave it at 1kb it will error out. Anyone else have this issue?
Should have held off asking. Once I found a newer version of the tool that issue is solved. Case closed.
follows the link of Stock Moto X4 ROM with Android 7.1.1 and September patch.
Model: X4 (Payton)
Version: NPW26.83-34-0-1
https://rsdsecure-cloud.motorola.co...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
The linked page shows a error, will be better if you can upload the file.
Yeah, link is borked. But I may pull it anyway... will post here if I do.
Had my XT1900-1 (Project Fi) for about an hour before I got bored and the bootloader was unlocked.
Thinking of rooting just to debloat (don't get me started on how bloated the Android One build is)... seems like root will be pretty straightforward given that unlock is painless and partition access seems unrestricted. Haven't tried yet, but thinking that just perms and pushing su might do the trick. Would like to have the device for a couple days before I go that far. [edit: Actually, Magisk looks like a pretty good bet w/o custom recovery... may try that]
Then maybe, if I have time start gathering vendor stuff/blobs/etc and build... something.
Anyone else out there tinkering yet?
mightysween said:
Yeah, link is borked. But I may pull it anyway... will post here if I do.
Had my XT1900-1 (Project Fi) for about an hour before I got bored and the bootloader was unlocked.
Thinking of rooting just to debloat (don't get me started on how bloated the Android One build is)... seems like root will be pretty straightforward given that unlock is painless and partition access seems unrestricted. Haven't tried yet, but thinking that just perms and pushing su might do the trick. Would like to have the device for a couple days before I go that far. [edit: Actually, Magisk looks like a pretty good bet w/o custom recovery... may try that]
Then maybe, if I have time start gathering vendor stuff/blobs/etc and build... something.
Anyone else out there tinkering yet?
Click to expand...
Click to collapse
I heard that the reason for the bloat is due to a huge number of partitions that consume space. As such, debloating may not be as easy as you hoped...
ebrandsberg said:
I heard that the reason for the bloat is due to a huge number of partitions that consume space. As such, debloating may not be as easy as you hoped...
Click to expand...
Click to collapse
Just ran cat /proc/partitions.... dang, you are right
|payton_sprout:/ $ cat /proc/partitions
major minor #blocks name
1 0 8192 ram0
1 1 8192 ram1
1 2 8192 ram2
1 3 8192 ram3
1 4 8192 ram4
1 5 8192 ram5
1 6 8192 ram6
1 7 8192 ram7
1 8 8192 ram8
1 9 8192 ram9
1 10 8192 ram10
1 11 8192 ram11
1 12 8192 ram12
1 13 8192 ram13
1 14 8192 ram14
1 15 8192 ram15
253 0 1048576 zram0
179 0 30535680 mmcblk0
179 1 3584 mmcblk0p1
179 2 3584 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 2048 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 512 mmcblk0p8
179 9 128 mmcblk0p9
179 10 128 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 1024 mmcblk0p13
179 14 1024 mmcblk0p14
179 15 512 mmcblk0p15
179 16 512 mmcblk0p16
179 17 512 mmcblk0p17
179 18 512 mmcblk0p18
179 19 512 mmcblk0p19
179 20 512 mmcblk0p20
179 21 128 mmcblk0p21
179 22 128 mmcblk0p22
179 23 256 mmcblk0p23
179 24 256 mmcblk0p24
179 25 112640 mmcblk0p25
179 26 112640 mmcblk0p26
179 27 1 mmcblk0p27
179 28 8 mmcblk0p28
179 29 16384 mmcblk0p29
179 30 16384 mmcblk0p30
179 31 1024 mmcblk0p31
259 0 512 mmcblk0p32
259 1 512 mmcblk0p33
259 2 2048 mmcblk0p34
259 3 2048 mmcblk0p35
259 4 6144 mmcblk0p36
259 5 6144 mmcblk0p37
259 6 32768 mmcblk0p38
259 7 512 mmcblk0p39
259 8 128 mmcblk0p40
259 9 16384 mmcblk0p41
259 10 512 mmcblk0p42
259 11 8192 mmcblk0p43
259 12 65536 mmcblk0p44
259 13 65536 mmcblk0p45
259 14 16384 mmcblk0p46
259 15 16384 mmcblk0p47
259 16 1024 mmcblk0p48
259 17 8192 mmcblk0p49
259 18 256 mmcblk0p50
259 19 256 mmcblk0p51
259 20 1 mmcblk0p52
259 21 1 mmcblk0p53
259 22 4608 mmcblk0p54
259 23 4608 mmcblk0p55
259 24 33424 mmcblk0p56
259 25 33424 mmcblk0p57
259 26 64 mmcblk0p58
259 27 64 mmcblk0p59
259 28 8192 mmcblk0p61
259 29 8192 mmcblk0p62
259 30 589824 mmcblk0p63
259 31 589824 mmcblk0p64
259 32 4227072 mmcblk0p65
259 33 4227072 mmcblk0p66
259 34 20262895 mmcblk0p67
179 32 4096 mmcblk0rpmb
252 0 4161104 dm-0
252 1 580580 dm-1
Click to expand...
Click to collapse
---------- Post added at 02:09 PM ---------- Previous post was at 01:56 PM ----------
Looks like the OP file was a leaked Brazilian version of the firmware... wonder if the boot.img is the same as US ?
And also looks like Motorola may be giving each variant of the device its own device name... not sure if this will be good down the line, development-wise, or not:
ro.product.name=payton_fi
ro.product.device=payton_sprout
Click to expand...
Click to collapse
So is it because of project Treble that we have such large system partition. Using 13 GB is too much.
saketkutta said:
So is it because of project Treble that we have such large system partition. Using 13 GB is too much.
Click to expand...
Click to collapse
Is this the partition scheme for Treble? If so, I'm fine with this personally, as it means they have thought ahead to help future-proof the phone (if there is such a thing).
I was seeing users in other threads saying it takes 16-18GB. That's just ridiculous. It should be half that, at most. My brand new install of OS X 10.13 High Sierra doesn't even take up that much space.
crazyates said:
I was seeing users in other threads saying it takes 16-18GB. That's just ridiculous. It should be half that, at most. My brand new install of OS X 10.13 High Sierra doesn't even take up that much space.
Click to expand...
Click to collapse
My custom OS on Nexus 5X took little more than 4 GB. Even if it was project treble (which is not confirmed yet BTW) it should not take more than 9 GB or 10 GB max. Mine out of the box it was 13 GB and something which is ridiculous)
Where did you get the ROM from? Link above is dead?
Iansip said:
Where did you get the ROM from? Link above is dead?
Click to expand...
Click to collapse
I don't think anyone got it here... I saw it bouncing around a couple Brazilian servers, but not open to download. Now that I look, it is the same Build # as the Project Fi version. So, hopefully it will turn up somewhere.
Seems the link in the OP is not dead, just goes to a secure server. It was originally posted on some G+ feeds, but no one has mirrored it yet, apparently
Actually, looks like that whole server is down right now. Every URL returns the same XML error. So maybe it will come back to life soon...
Oh, look at that... Moto has either geo or ISP restrictions on their download! VPN Proxy through server in Los Angeles, and download is running (sloooooowwwly).
Will update tomorrow morning.
UPDATE: Download died at 1.1 GB and the VPN workaround is no longer working. Grrrrr. Could probably extract boot.img anyway, but with no way to check the hash and no images to fall back on, too risky to actually patch/flash it
Got it... well, I have a completed download -- Obviously there is no way to verify the file since I have no MD5/SHA to check against. That said, the archive opens without errors, so I have boot.img now, just not enough stupidity to modify it and flash an unverified firmware back onto a brand new device.
Have a mirror uploading, will share when complete and maybe can get added to the OP.
WARNING: This is unverified fimware for testing/research only. Please don't flash it and then complain when you paperweight your new X4.
UPDATED 10-27-2017: This ZIP has several corrupt files... verify anything against the MD5 in the "flashfile.xml" file before using!
FILE: PAYTON_NPW26.83-34-0-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
SIZE: 2702597112 bytes
SHA256 (unverified on the Motorola end!!!): 124f53fef572850532d029d00166829e200b777491502504c9de215fe7dd1046
DOWNLOAD: https://drive.google.com/open?id=0ByZWXbOZqmVqQ09FUXliN3hYMGs
@Anderson_ARS , can you add this to the OP to save people asking the same question over and over and over? Thanks
mightysween said:
Yeah, link is borked. But I may pull it anyway... will post here if I do.
Had my XT1900-1 (Project Fi) for about an hour before I got bored and the bootloader was unlocked.
Thinking of rooting just to debloat (don't get me started on how bloated the Android One build is)... seems like root will be pretty straightforward given that unlock is painless and partition access seems unrestricted. Haven't tried yet, but thinking that just perms and pushing su might do the trick. Would like to have the device for a couple days before I go that far. [edit: Actually, Magisk looks like a pretty good bet w/o custom recovery... may try that]
Then maybe, if I have time start gathering vendor stuff/blobs/etc and build... something.
Anyone else out there tinkering yet?
Click to expand...
Click to collapse
I'd love to see a unlock/root method. Hope to see TWRP asap!
Slickademo said:
How do you unlock and root? I just got mine today
Click to expand...
Click to collapse
Unlock is just a regular Motorola unlock... lot of threads on how that is done.
Root is a little more risky and complicated to explain here. The first thing we all need is a trusted factory image -- hopefully the one above is just that. I would suspect that once we confirm a factory image, root methods will be plentiful.
mightysween said:
Got it... well, I have a completed download -- Obviously there is no way to verify the file since I have no MD5/SHA to check against. That said, the archive opens without errors, so I have boot.img now, just not enough stupidity to modify it and flash an unverified firmware back onto a brand new device.
Have a mirror uploading, will share when complete and maybe can get added to the OP.
Click to expand...
Click to collapse
I have tried downloading the file several times and always get to the very end and then it fails. I'm using idm and multiple threads and maybe I should try just a single thread..
once I get it downloaded I will validate the checksum with yours.
edit: I should add that I am in Vegas and have been able to access the link directly from the day it was posted.
Jayman007 said:
I have tried downloading the file several times and always get to the very end and then it fails. I'm using idm and multiple threads and maybe I should try just a single thread..
once I get it downloaded I will validate the checksum with yours.
edit: I should add that I am in Vegas and have been able to access the link directly from the day it was posted.
Click to expand...
Click to collapse
Oh, neat...definitely IP restricted then as I tried a VPN in LV and was still blocked. Wonder what the story is there!
Yes, if you end up with the same SHA256 let me know, we can at least be sure the file is intact.
---------- Post added at 10:37 PM ---------- Previous post was at 10:35 PM ----------
Jayman007 said:
I have tried downloading the file several times and always get to the very end and then it fails. I'm using idm and multiple threads and maybe I should try just a single thread..
once I get it downloaded I will validate the checksum with yours.
edit: I should add that I am in Vegas and have been able to access the link directly from the day it was posted.
Click to expand...
Click to collapse
Also FWIW, using that proxy link I posted gave me dl speeds of 2.5-3 Mbps, and plowed straight through to 100%.
mightysween said:
FILE: PAYTON_NPW26.83-34-0-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
SIZE: ~2.0 GB
CHECKSUM: UNVERIFIED! (my local SHA256: f8efa78d21f0fd4b968e860ec06b85442caaf7a93c325fbe7c5c0913306af86e)
DOWNLOAD: https://mega.nz/#!RkM2nSpL!4kHuZQfyHoSfeD-bfCcRxOi3A3rO7hz37RGcxRCglic
@Anderson_ARS , can you add this to the OP to save people asking the same question over and over and over? Thanks
Also, if you wish to try a direct download from Motorola, this link may work... it is a proxy download through NordVPN. Again, no guarantees and no way to verify (though if you end up with the same SHA256 as above, there is good chance the file is intact).
DIRECT DOWNLOAD (via anon proxy): http://proxy-it.nordvpn.com/browse....cbNvGOLw5iqOebtX0lAb+hCJw==&b=1&f=norefer&pr=
Click to expand...
Click to collapse
I downloaded it via the proxy and have the same checksum as you, so at least this means that your download is *probably* not corrupt. I don't have the device, so I'm certainly not going to flash it.
Code:
f8efa78d21f0fd4b968e860ec06b85442caaf7a93c325fbe7c5c0913306af86e PAYTON_NPW26.83-34-0-1_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
gee one said:
I downloaded it via the proxy and have the same checksum as you, so at least this means that your download is *probably* not corrupt. I don't have the device, so I'm certainly not going to flash it.
Click to expand...
Click to collapse
Thank you kindly! I downloaded again as well with same checksum, so I think we can assume the file is intact.