Introduction
Why is UART useful? It's a debugging tool. During the boot sequence on most computers, you see a splash screen. On most computers, you can hit 'ESC' to see the diagnostics in the background and then press a key like 'F2' to jump into the BIOS and make changes. On our devices we don't have that option.
On the Nook we have U-Boot which functions as a BIOS. We press 'Space Bar' to get into the U-Boot options. UART allows you to get into the U-Boot and make changes, as well as view the logs as they are generated. See the following code block for an example output
Code:
Texas Instruments X-Loader 1.41 (Oct 21 2011 - 14:00:05)
Start not on PWRON, skipping power button check.
Starting OS Bootloader from EMMC ...
U-Boot 1.1.4-acclaim1.4_1.4.0.1029^{} (Nov 11 2011 - 12:34:20)
Load address: 0x80e80000
DRAM: 1024 MB
Using default environment
In: serial
Out: serial
Err: serial
hw_status 0x23 vbus_status 0x80
mmc read: Invalid size
mmc read: Invalid size
2 bytes read
MAX17042+UBOOT: battery type=LG
MAX17042+UBOOT: gas gauge detected (0x0000)
MAX17042_STATUS (00h) is 0x0000
MAX17042+UBOOT: BATTERY Detected!
MAX17042+UBOOT:WARM BOOT
mmc read: Invalid size
mmc read: Invalid size
40 bytes read
Valid max17042 init data is loaded into memory
0x1234
0x215b
0x00d6
0x2037
0x0000
0x0100
0x007e
0x3670
0x078f
0x0000
0x0000
0x6435
0x2f2c
0x0140
0x7d5a
0x87a4
0x1400
0x205c
0x205c
0x6046
verify if mem loaded: FullcapNom was saved as 2037
uboot verify: 1d CONFIG is 2210 ; should be 2210 & 0xFDFB
uboot verify: 2a RELAXCFG is 083b ; should be 083b
uboot verify: 29 FILTERCFG is 87a4 ; should be 87a4
uboot verify: 28 LEARNCFG is 2466 ; should be 2406 & 0xFF0F
uboot verify: 18 DesignCap is 205c ; should be 205c
uboot verify: 12 Vempty is 7d5a ; should be 7d5a
uboot verify: 25 TEMPLIM is 2305 ; should be 2305
uboot verify: 2b MiscCFG is 0810 ; should be 0810 & cc1f
uboot verify: 2c TGAIN is e3e1 ; should be e3e1
uboot verify: 2d TOFF is 290e ; should be 290e
uboot verify: 2e CGAIN is 4000 ; should be 4000
uboot verify: 2f COFF is 0000 ; should be 0000
uboot verify: 37 FCTC is 05e0 ; should be 05e0
MAX17042+UBOOT: warm config is okay
SOC 90%, booting.
Board revision PVT
mmc read: Invalid size
mmc read: Invalid size
16 bytes read
ptn 0 name='xloader' start=256 len=131072
ptn 1 name='bootloader' start=512 len=262144
ptn 2 name='recovery' start=1024 len=15728640
ptn 3 name='boot' start=32768 len=16777216
ptn 4 name='rom' start=65536 len=50331648
ptn 5 name='bootdata' start=163840 len=50331648
ptn 6 name='factory' start=262144 len=387973120
ptn 7 name='system' start=1019904 len=641728512
ptn 8 name='cache' start=2273280 len=446693376
ptn 9 name='media' start=3145728 len=1073741824
ptn 10 name='userdata' start=5242880 len=64991232
mmc read: Invalid size
1088 bytes read
BCB found, checking...
** Unable to use mmc 0:1 for fatload **
** Unable to use mmc 0:1 for fatload **
** Unable to use mmc 0:1 for fatload **
Booting into Android
mmc read: Invalid size
mmc read: Invalid size
4 bytes read
BootCnt 2
1 bytes written
Autobooting in 0 seconds, press <SPACE> to stop...
kernel @ 80088120 (2682952)
ramdisk @ 81080000 (157153)
Initrd start : 81080000 , Initrd end : 810a64c1Acclaim Board.
Starting kernel ...
Linux version 2.6.35.7 ([email protected]) (gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202) ) #1 SMP PREEMPT Fri Nov 11 12:35:42 PST 2011
CPU: ARMv7 Processor [411fc093] revision 3 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
Machine: OMAP4430 ACCLAIM
Memory policy: ECC disabled, Data cache writealloc
On node 0 totalpages: 245760
free_area_init_node: node 0, pgdat c0587e00, node_mem_map c062a000
Normal zone: 1536 pages used for memmap
Normal zone: 0 pages reserved
Normal zone: 178688 pages, LIFO batch:31
HighMem zone: 512 pages used for memmap
HighMem zone: 65024 pages, LIFO batch:15
***********************
OMAP4430 ES2.3 type(HS)
id-code (6b95c02f)
Die-id (5C360006-00000001-09111715-1601D00D)
Prod-id (000DB95C-000600CC)
***********************
SRAM: Mapped pa 0x40300000 to va 0xfe400000 size: 0x100000
FIXME: omap44xx_sram_init not implemented
Reserving 33554432 bytes SDRAM for VRAM
SMC: Allocated workspace of 3M at (0x9c900000)
PERCPU: Embedded 7 pages/cpu @c0e37000 s5632 r8192 d14848 u65536
pcpu-alloc: s5632 r8192 d14848 u65536 alloc=16*4096
pcpu-alloc: [0] 0 [0] 1
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 243712
Kernel command line: androidboot.console=ttyO0 console=ttyO0,115200n8 [email protected] [email protected] init=/init rootwait vram=32M,82000000 omapfb.vram=0:[email protected]
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 448MB 256MB 256MB = 960MB total
Memory: 935252k/935252k available, 47788k reserved, 262144K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xf0800000 - 0xf8000000 ( 120 MB)
lowmem : 0xc0000000 - 0xf0000000 ( 768 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.init : 0xc0008000 - 0xc003d000 ( 212 kB)
.text : 0xc003d000 - 0xc053f000 (5128 kB)
.data : 0xc0540000 - 0xc05888c0 ( 291 kB)
SLUB: Genslabs=11, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
Hierarchical RCU implementation.
RCU-based detection of stalled CPUs is disabled.
Verbose stalled-CPUs detection is disabled.
You will need
In order to get started you will need some things. Here's what you will need.
Torx T5 screw driver (the star kind)
Soldering iron ( any soldering iron)
Case opener tool ( or guitar pick or something small and plastic)
30-40 AWG wire (small wires)
1.8V UART to USB converter (Like The Bus Priate)
Tweezers (Makes it easier to handle small things)
Most of the tools and parts used can be obtained at Lowes or Radio Shack
For a UART device, I recommend The Bus Pirate. The Bus Pirate is known as "The Hacker's Multi-tool" and it is useful for alot more than just UART. It is an Open-Source, Open-Hardware, community supported tool. You can get it from SeeedStudios.com for $27.15.
Instructions
There are several ways to set up UART. Here is how I set up mine.
Image 1:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disassembly
If you have an SDCard inserted, remove it.
Remove two(2) T5 Torx screws securing the back cover to the unit
Using the Case Opener tool, pry the rear cover off the unit. It is held on by small plastic hooks. They are fairly durable and I have not broken any in several removal and installations.
Remove ten(10) T5 torx screws from the metal case which secure the front cover
Image 2:
disconnect the battery and the volume control swich connections which are accessible through holes in the metal case.
Remove the front cover using a case opener tool or your bare hands, whichever is more comfortable for you
Remove the board and LCD from the metal case
Modification
Image 3:
Locate the UART RX and TX lines on the board shown in Image2.
You can hook your UART device to this directly, RX to TX and TX to RX, or keep reading and I'll show you how I set mine up. so..
Stop here and use UART or continue on for a cleaner method
run 40 awg wire to a piece of perf-board, about 8 holes wide.
Using 20 awg wire, make a loop on the perf-board which joins two holes in two spots on the small piece of perf-board
attach the UART RX
Image 4:
Route the wires along the board and tape them down
Use epoxy to mount the perfboard. It should be mounted at a very slight downward angle. Set something under the board while it dries. This gives room for the case to close.
Reassemble the unit, Assembly is reverse of Disassembly.
Image 5:
Hook up RX, TX to your perf-board hooks and connect ground to the metal case.
Image 6:
You will now be able to talk to your UART device using
Baud: 115200
Bits: 8
Parity: None
Stop Bits: 1
Voltage: 1.8 (open drain)
For the Bus Pirate, get it working in a termianal and use the following settings:
Code:
HiZ>m
1. HiZ
2. 1-WIRE
3. UART
4. I2C
5. SPI
6. 2WIRE
7. 3WIRE
8. LCD
9. DIO
x. exit(without change)
(1)>3
Set serial port speed: (bps)
1. 300
2. 1200
3. 2400
4. 4800
5. 9600
6. 19200
7. 38400
8. 57600
9. 115200
10. BRG raw value
(1)>9
Data bits and parity:
1. 8, NONE *default
2. 8, EVEN
3. 8, ODD
4. 9, NONE
(1)>1
Stop bits:
1. 1 *default
2. 2
(1)>1
Receive polarity:
1. Idle 1 *default
2. Idle 0
(1)>1
Select output type:
1. Open drain (H=Hi-Z, L=GND)
2. Normal (H=3.3V, L=GND)
(1)>1
Ready
UART>(3)
Conclusion
For those of you helping with security bypass methods, this will surely be useful as it will tell you when a secure failure is encountered. For those of you who want to experiment with U-Boot or a cool electronics project, I'd encourage you to try this. There's not alot that can go wrong because the board is well built and fairly heat resistant and the tools/parts used in this mod are available from several sources.
I hope this was informative and/or interesting for you to read.
Thanks to pokey9000 for pointing me to the right area.
A few lines before the kernal starts loading, it has bootcnt 2. What does this mean and what happens if it is modified? Or is any modification break the secure CHAIN?
Also, what would happen if it didn't autoboot in 0 seconds and you could hit the spacebar?
Sent from my BNTV250 using Tapatalk
HMG10 said:
A few lines before the kernal starts loading, it has bootcnt 2. What does this mean and what happens if it is modified? Or is any modification break the secure CHAIN?
Sent from my BNTV250 using Tapatalk
Click to expand...
Click to collapse
That's the number of boots since the counter was reset. After 8 failed boots, the device will go into recovery and restore all firmware.
this is great! I have been looking at my arduino and my pandaII (.netMF) dev boards and my tablet for a few days now.
Glad I dont have to pull out the logic analyser and find those pins..
servergod said:
this is great! I have been looking at my arduino and my pandaII (.netMF) dev boards and my tablet for a few days now.
Glad I dont have to pull out the logic analyser and find those pins..
Click to expand...
Click to collapse
that's exactly what I did...
Adafruit's FTDI Friend should also do the trick, $10 less.
I changed up my UART connection. I feel this is much cleaner and runs less wire through the nook. This makes it into a really good development device.
This new setup is made with a piece of perf-board from Radio Shack and it's held onto the nook using double-sided tape. Here are some pictures:
The wires are routed through the crack in the back cover and run to the same points mentioned in the Original Post. The 3rd connection (middle) here is Ground. Ground is the point on the board closest to the edge and furthest from UART TX in the staggered group of pins..
I thought I'd update this... I though I'd update this after a few weeks of working with it. The external connection works very well. It is easy to remove and replace if required with just 3 solder joints if required. The external perf-board is very unobtrusive, and does not interfere with operation.
I also found a case that works well with this modification. it's called "Mini Suit" for Nook Tablet.
If you go with this method and need a case, Mini Suit will suit you.
Adam,
In picture 3 you have a diagram that shows the pinout for uart tx and rx on the nook tablet (appears to be the left two pins of the 4 in the diagram), but if you look closely at picture 4, the top wire appears to be soldered to the top right pin rather than the top left pin as show on the diagram in picture 3. Is this just an optical illusion?
Thanks Again for all you do on these forums.!
acruxksa said:
Adam,
In picture 3 you have a diagram that shows the pinout for uart tx and rx on the nook tablet (appears to be the left two pins of the 4 in the diagram), but if you look closely at picture 4, the top wire appears to be soldered to the top right pin rather than the top left pin as show on the diagram in picture 3. Is this just an optical illusion?
Thanks Again for all you do on these forums.!
Click to expand...
Click to collapse
disregard picture 4. I took alot of pictures while setting things up and I chose the ones that gave the best idea of what was going on. Thanks.
Replacement for Bus Pirate
Hi Adam
Good day to you.
I would like to setup my own Uart devices for Samsung Phone, however, not able to locate the Bus Pirate devices as mention in your thread.
but i found a USB to RS232 converter as per attach PDF file.
would you please help to check on it? is it possible to setup the UART setup use on Samsung phone?
if can kindly help to give a detail guide connection setup from PC USB to Phone.
appreciate you help.
thanks
chongns said:
Hi Adam
Good day to you.
I would like to setup my own Uart devices for Samsung Phone, however, not able to locate the Bus Pirate devices as mention in your thread.
but i found a USB to RS232 converter as per attach PDF file.
would you please help to check on it? is it possible to setup the UART setup use on Samsung phone?
if can kindly help to give a detail guide connection setup from PC USB to Phone.
appreciate you help.
thanks
Click to expand...
Click to collapse
This should really go into the Samsung forum for the phone you're trying to get to, however here is where you can buy a bus pirate.
Hi all. I have compiled 0xdroid Gingerbread for beagleboard-xm following the official wiki.
the system stops during kernel boot
Here is my output:
Code:
reading boot.scr
462 bytes read
Running bootscript from mmc ...
## Executing script at 82000000
reading uImage
3502776 bytes read
reading uInitrd
173707 bytes read
## Booting kernel from Legacy Image at 80200000 ...
Image Name: Linux-2.6.38.6-g3298421-dirty
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3502712 Bytes = 3.3 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 81600000 ...
Image Name: Android Ramdisk Image
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 173643 Bytes = 169.6 KiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
<5>Linux version 2.6.38.6-g3298421-dirty (sarasini-64bit)
(gcc version 4.5.4 20110505 (prerelease) (Linaro GCC 4.5-2011.05-0) )
#6 Mon Jan 2 21:02:10 CET 2012
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: OMAP3 Beagle Board
<6>Reserving 33554432 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
<5>Truncating RAM at a0000000-bfffffff to -afffffff (vmalloc region
overlap).
<6>OMAP3630 ES1.2 (l2cache iva sgx neon isp 192mhz_clk )
<6>SRAM: Mapped pa 0x40200000 to va 0xfe400000 size: 0x10000
No more output. all leds on the board are turned on. Any help?
thanks
Francesco
Repo Sync , Sync'd all projects for over 8 hrs on my 2mbps plan
This is the guide i took for reference and changed the repositories address to the one for beagleboard , using this command
Code:
repo init -u https://bitbucket.org/sola/android_manifest
Yet all 239 odd projects got downloaded , how to only download the beagleboard source files and not all aosp project on the main android source code git
Please clarify this (i know how to use -b option in repo sync to take only branches of a project from the manifest i point it to)
repo should only download files from bitbucket.org and not all android sources files correct?
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...
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.
Hi, I downloaded the img file from the provided link(https://images.snappautomotive.com/rpi/snapp_automotive_rpi4_32gb_20211119.img.zip), but after successfully flashing the image file to an SD card, the raspberry pi4 model b didn't boot up. It shows (attached are the images of shown error) :
Raspberry Pi 4 Model B - 8GB bootloader: 6efe41bd 2022/01/25
board: 003115 6485fcf2 e4:5f:01:ad:58:05 boot: mode SD 1 order f41 retry 0/1 restart 18/-1
SD: card detected 00035344534431323885fa236632a165 part: mbr [0x0c:00000800 0x83:00040800 0x83:00440800 0x83:00480800]
fw: start4.elf fixup4.dat
net: down ip: 0.0.0.0 sn: 0.0.0.0 gw: 0.0.0.0
tftp: 0.0.0.0 00:00:00:00:00:00
Trying partition: 6
type: 16 lba: 2048 oem: 'mkfs. fat' volume:
rsc 4 fat-sectors 256 c-count 65399 c-size 4
root dir cluster 1 sectors 32 entries 512 Read config.txt bytes 206 hnd 0x00000000
Read start4.elf bytes 2214880 hnd 0x00000000 Read fixup4.dat bytes 5433 hnd 0x00000000
Firmware: 4b4aff21f72c5b9ba39d83c7b0f8fa910a6ef99b Dec 15 2020 14:48:29
0x00d03115 0x00000000 0x0000003f
start4.elf: is not compatible This board requires newer software
Get the latest software from https://www.raspberrypi.com/software/
Help me solve the issue. What should I follow?
just add the polestar and volvo images for emulator in android auto