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?
I just purchased a Vibrant from a co-worker yesterday for forty bucks and immediately started working on getting CyanogenMod running on it. I have some experience with CyanogenMod, and currently have it running on my Samsung Galaxy Tab 2 10.1 (Wifi only, US).
Getting this Vibrant free of the original operating system was easy enough. I also was able to flash ClockworkMod Recovery onto it via Heimdall at the command line.
What I cannot do is boot the device into Recovery Mode. The vol up + vol down + power button combination does not work. I've also tried connecting the device to my laptop (Windows 8) with Kies, but it cannot connect, even after re-installing the Samsung USB drivers through Kies. Equally unsuccessful is attempting to interact with the device in any manner whatsoever through the adb.
Also, after interfacing the device with Kies, it seems I may not be able to boot into Download mode (USB + vol up). I only get an error (on the phone) stating "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Can anybody help me out?
actuallybambi said:
I just purchased a Vibrant from a co-worker yesterday for forty bucks and immediately started working on getting CyanogenMod running on it. I have some experience with CyanogenMod, and currently have it running on my Samsung Galaxy Tab 2 10.1 (Wifi only, US).
Getting this Vibrant free of the original operating system was easy enough. I also was able to flash ClockworkMod Recovery onto it via Heimdall at the command line.
What I cannot do is boot the device into Recovery Mode. The vol up + vol down + power button combination does not work. I've also tried connecting the device to my laptop (Windows 8) with Kies, but it cannot connect, even after re-installing the Samsung USB drivers through Kies. Equally unsuccessful is attempting to interact with the device in any manner whatsoever through the adb.
Also, after interfacing the device with Kies, it seems I may not be able to boot into Download mode (USB + vol up). I only get an error (on the phone) stating "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Can anybody help me out?
Click to expand...
Click to collapse
First of all, never use Kies with a rooted phone, it could hard brick it!
Do some more reading, you can access your cwm recovery in several ways. It depends also on the type of bootloader you have.
ioancr said:
First of all, never use Kies with a rooted phone, it could hard brick it!
Do some more reading, you can access your cwm recovery in several ways. It depends also on the type of bootloader you have.
Click to expand...
Click to collapse
The thing that concerns me is that I don't know of any other means by which to access recovery mode beyond the three button combination. I'm concerned something may be up on the hardware end. The only files I modified on my phone via Odin where the PIT to redo the partitioning, and the PDA image of CyanogenMod. As far as I know I did not alter the bootloader in any manner, nor did I replace it with an alternative one.
And please, please do not patronize me by telling me I should "read some more". I racked my brain for almost four days looking for methods by which I could get this phone usable again. I came to xda in hopes that someone could assist me with what I'm certain is becoming a unique and mind-numbingly stupid problem. Being thrown back out into the wild binary yonder is not how I had anticipated someone trying to help me.
Thank you for replying to my post, but is there any helpful resources you could link me to involving complete and utter necessary recovery of my Vibrant?
Try to use Odin back to stock 2.1,had the same issue a while back.Odin worked for me.then flashed a 2.2 ROM. Then went from there
Sent from my SGH-T959 using xda app-developers app
actuallybambi said:
I just purchased a Vibrant from a co-worker yesterday for forty bucks and immediately started working on getting CyanogenMod running on it. I have some experience with CyanogenMod, and currently have it running on my Samsung Galaxy Tab 2 10.1 (Wifi only, US).
Getting this Vibrant free of the original operating system was easy enough. I also was able to flash ClockworkMod Recovery onto it via Heimdall at the command line.
What I cannot do is boot the device into Recovery Mode. The vol up + vol down + power button combination does not work. I've also tried connecting the device to my laptop (Windows 8) with Kies, but it cannot connect, even after re-installing the Samsung USB drivers through Kies. Equally unsuccessful is attempting to interact with the device in any manner whatsoever through the adb.
Also, after interfacing the device with Kies, it seems I may not be able to boot into Download mode (USB + vol up). I only get an error (on the phone) stating "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Can anybody help me out?
Click to expand...
Click to collapse
The vibrant all in one by Bay wolf. It has all the tools you need to get the phone working again.
Good luck.
actuallybambi said:
I just purchased a Vibrant from a co-worker yesterday for forty bucks and immediately started working on getting CyanogenMod running on it. I have some experience with CyanogenMod, and currently have it running on my Samsung Galaxy Tab 2 10.1 (Wifi only, US).
Getting this Vibrant free of the original operating system was easy enough. I also was able to flash ClockworkMod Recovery onto it via Heimdall at the command line.
What I cannot do is boot the device into Recovery Mode. The vol up + vol down + power button combination does not work. I've also tried connecting the device to my laptop (Windows 8) with Kies, but it cannot connect, even after re-installing the Samsung USB drivers through Kies. Equally unsuccessful is attempting to interact with the device in any manner whatsoever through the adb.
Also, after interfacing the device with Kies, it seems I may not be able to boot into Download mode (USB + vol up). I only get an error (on the phone) stating "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again.
Can anybody help me out?
Click to expand...
Click to collapse
So does your phone boot up or are you soft bricked, I'm confused? If it boots up then download "quick boot" from the playstore and it will boot you into recovery but you must be rooted. If its bricked just get back to that kies error screen/download mode and see if a yellow com box comes up in Odin when connected to your pc, if so just flash back to stock.
Sent from my GT-I9000 using Tapatalk 2
iTz KeeFy said:
So does your phone boot up or are you soft bricked, I'm confused? If it boots up then download "quick boot" from the playstore and it will boot you into recovery but you must be rooted. If its bricked just get back to that kies error screen/download mode and see if a yellow com box comes up in Odin when connected to your pc, if so just flash back to stock.
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
The only thing the phone currently does it turn on and show a screen stating "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
actuallybambi said:
The only thing the phone currently does it turn on and show a screen stating "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again."
Click to expand...
Click to collapse
I would NEVER recommend using kies, it messes up more phones than it helps. If Odin doesn't recognize the phone you can try kies as a last resort. If that doesn't work either you should call Samsung and tell them Kies has bricked your phone, they should fix it for free or send you a new replacement. I have heard many stories of people getting a replacement for free so give that a shot. You could also try a usb jig and try to get into download mode if you have one but that is no guarantee.
Sent from my GT-I9000 using Tapatalk 2
iTz KeeFy said:
I would NEVER recommend using kies, it messes up more phones than it helps. If Odin doesn't recognize the phone you can try kies as a last resort. If that doesn't work either you should call Samsung and tell them Kies has bricked your phone, they should fix it for free or send you a new replacement. I have heard many stories of people getting a replacement for free so give that a shot. You could also try a usb jig and try to get into download mode if you have one but that is no guarantee.
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
Apologies for the lateness of this reply, but I do think that I have made some progress. Or at least, there is hope for me yet.
The machine I'm doing all this work on is now running Arch Linux, and Heimdall is detecting the phone when it's plugged in; despite it being stuck at the "firmware encountered an error" screen. I'll be doing the rest of the work on the phone through Heimdall from this point on, and won't ever be letting this phone touch Kies again.
actuallybambi said:
Apologies for the lateness of this reply, but I do think that I have made some progress. Or at least, there is hope for me yet.
The machine I'm doing all this work on is now running Arch Linux, and Heimdall is detecting the phone when it's plugged in; despite it being stuck at the "firmware encountered an error" screen. I'll be doing the rest of the work on the phone through Heimdall from this point on, and won't ever be letting this phone touch Kies again.
Click to expand...
Click to collapse
Yea don't mess with kies ha, its really a terrible program. I hope you get heimball to successfully flash it. O yea, im pretty sure there is a heimball one click unbrick around here somewhere. I own a windows pc so can't really attest to its usefulness but I have heard success stories, good luck.
Sent from my SGH-T959 using Tapatalk 2
Okay, I feel like an update on my progress is appropriate now.
The phone can get to download mode via my jig, the current issue is getting it to boot into CWR. The three-button press method does not work, as I stated earlier. I'm currently building the Android platform utilities on my Linux machine to access the adb so I can pass whatever command it is to the phone to reboot into recovery mode.
One last update before bed.
the adb is working, but will not recognize my phone while it's in download mode.
I'm afraid I'm SOL since I didn't enable USB debugging before I nearly bricked this thing.
I don't think adb is supposed to recognize it while in dl mode, that's meant only for Odin or Heimball. Did you ever flash your phone back to stock?
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
I don't think adb is supposed to recognize it while in dl mode, that's meant only for Odin or Heimball. Did you ever flash your phone back to stock?
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
I've been scratching my head over this for a few days now; how exactly would I go about to flashing it to stock?
Would you happen to know where I can find the necessary firmware package/files I need to do that through Heimdall?
Okay, I've downloaded a firmware package and PIT file from here.
However, when I try to open the firmware package in Heimdall (through heimdall-frontend), it throws up an error stating that "firmware.xml is missing from this package". I can load the PIT file up in Heimdall, but am confused as what to do next.
I've managed to get the device's PIT table from Heimdall:
Downloading device's PIT file...
PIT file download successful.
Entry Count: 13
Unknown 1: 0
Unknown 2: 0
Unknown 3: 0
Unknown 4: 0
Unknown 5: 0
Unknown 6: 0
Unknown 7: 0
Unknown 8: 0
--- Entry #0 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 0
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 1
File Offset (Obsolete): 6684783
File Size (Obsolete): 2097268
Partition Name: IBL+PBL
Flash Filename: boot.bin
FOTA Filename:
--- Entry #1 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 1
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 1
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PIT
Flash Filename:
FOTA Filename:
--- Entry #2 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 20
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 40
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: EFS
Flash Filename: efs.rfs
FOTA Filename:
--- Entry #3 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 3
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 5
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL
Flash Filename: sbl.bin
FOTA Filename:
--- Entry #4 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 4
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 5
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: SBL2
Flash Filename: sbl.bin
FOTA Filename:
--- Entry #5 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 21
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 20
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: PARAM
Flash Filename: param.lfs
FOTA Filename:
--- Entry #6 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 6
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 30
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: KERNEL
Flash Filename: zImage
FOTA Filename:
--- Entry #7 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 7
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 30
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: RECOVERY
Flash Filename: zImage
FOTA Filename:
--- Entry #8 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 22
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 1540
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: FACTORYFS
Flash Filename: factoryfs.rfs
FOTA Filename:
--- Entry #9 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 23
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 2120
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: DATAFS
Flash Filename: data.rfs
FOTA Filename:
--- Entry #10 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 24
Attributes: 2 (STL Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 160
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CACHE
Flash Filename: cache.rfs
FOTA Filename:
--- Entry #11 ---
Binary Type: 0 (AP)
Device Type: 0 (OneNAND)
Identifier: 11
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 256
Partition Block Count: 60
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: MODEM
Flash Filename: modem.bin
FOTA Filename:
--- Entry #12 ---
Binary Type: 1 (CP)
Device Type: 1 (File/FAT)
Identifier: 11
Attributes: 0 (Read-Only)
Update Attributes: 0
Partition Block Size/Offset: 0
Partition Block Count: 0
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name:
Flash Filename:
FOTA Filename:
Okay, I've made serious progress but I am still severely lacking in luck at the moment.
I'm attempting to re-partition the device, and I have all the necessary files loaded up in heimdall-frontend (minus EFS and SBL2, are these totally necessary?).
However, heimdall is being a pain in the butt now. While heimdall detects the phone no problem, every time I attempt to re-partition, I get this error:
"ERROR: Protocol initialisation failed!"
Again, this is where I think I'm SOL because I believe this protocol is failing to initialize because I did not enable USB debugging prior to making a huge mess of this phone.
Hi to everyone.
I make some changes in vold partiitons encryption, but I can't test it on emulator with android 5 because it every time make images again after encryption:
emulator: WARNING: system partition size adjusted to match image file (550 MB > 200 MB)
emulator: WARNING: data partition size adjusted to match image file (550 MB > 200 MB)
Creating filesystem with parameters:
Size: 576716800
Block size: 4096
Blocks per group: 32768
Inodes per group: 7040
Inode size: 256
Journal blocks: 2200
Label:
Blocks: 140800
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35200 inodes and 4536/140800 blocks
With andtoid 4.4 I had no this issue. How can I disable this?
It happend because last android 5 latest kernel broke fs during encryption.
I download android 5 stable repo and it works
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