Page 4 of 4 FirstFirst ... 234
Results 31 to 37 of 37

Thread: Understanding the Spica

777
  1. [translate]    #31
    Junior Member
    Join Date
    Mar 2011
    Location
    Netherlands
    Posts
    13

    Default

    I was wondering which partitions and what parts of odin can brick the phone.
    I guess if I can get into download mode I can always recover the phone.
    So my question, what parts are needed to boot into download mode.
    boot(SBL) and PBL seem to be needed, but also modem and efs?
    Kernel, boot image and boot parameters don't seem to be necessary.
    So in odin it should be safe to flash 'pda' and 'csc', but 'phone' and 'modem' can irrevocably brick the phone.
    Can somebody confirm this?

    At the moment I guess I have stock boot, sbl, modem and efs. Are there significant advantages to flash these components to newer versions which are spread across the net? With boot/sbl I would think, never flash if it isn't broken but what about the modem/efs for gsm fixes?
    Last edited by barrybul; 03-13-2011 at 01:58 AM.

  2. [translate]    #32
    Senior Member
    Join Date
    Aug 2010
    Location
    Poland
    Posts
    2,826

    Default

    Quote Originally Posted by barrybul View Post
    I guess if I can get into download mode I can always recover the phone.
    Yes, you can.

    Quote Originally Posted by barrybul View Post
    So my question, what parts are needed to boot into download mode.
    Bootloader (PBL and SBL) and apparently data stored on bml3 partition after bootlogo (starting at offset 0x30000 of bml3)

    Quote Originally Posted by barrybul View Post
    boot(SBL) and PBL seem to be needed, but also modem and efs?
    PBL and SBL are our bootloaders.
    Modem (aka Phone) is baseband firmware. It is not needed for download mode, cpu loads it from internal flash to baseband cpu during each boot-up process.
    Efs stores IMEI and (AFAIR) Wifi MAC plus some other stuff. Don't touch this at any circumstance.

    Quote Originally Posted by barrybul View Post
    Kernel, boot image and boot parameters don't seem to be necessary.
    We don't have bootimage- this is needed for qualcomm based hardware.

    Quote Originally Posted by barrybul View Post
    So in odin it should be safe to flash 'pda' and 'csc', but 'phone' and 'modem' can irrevocably brick the phone.
    No, it won't.

    Quote Originally Posted by barrybul View Post
    but what about the modem/efs for gsm fixes?
    Phone.bin can be flashed, some firmwares contain it.
    You will never get a copy of Efs (except for backups from your phone)
    Code:
    setprop persist.world.domination 1

  3. [translate]    #33
    Junior Member
    Join Date
    Mar 2011
    Location
    Netherlands
    Posts
    13

    Default

    Thanx darth_llamah

    Quote Originally Posted by darth_llamah View Post
    No, it won't.
    Can I conclude that only flashing 'boot' in odin can irrevocably brick your phone?

    Quote Originally Posted by darth_llamah View Post
    You will never get a copy of Efs (except for backups from your phone)
    Already made a tar.gz and dd backup of efs so should be safe here.

  4. [translate]    #34
    Senior Member
    Join Date
    Aug 2010
    Location
    Poland
    Posts
    2,826

    Default

    Quote Originally Posted by barrybul View Post
    Can I conclude that only flashing 'boot' in odin can irrevocably brick your phone?
    If something goes wrong- yes. But Odin will not flash bootloaders with standard parameters (start Odin, check Debug ONLY and look which options become aviable)
    Code:
    setprop persist.world.domination 1

  5. [translate]    #35
    Junior Member
    Join Date
    Apr 2011
    Location
    Poland
    Posts
    7

    Default

    Quote Originally Posted by Phlexonance
    For example in the Kitchen you do replace the Kernel and the rest of the system, yet there already needs to be LK2.02 on it, why?
    Doesn't the recovery mode use a different kernel than the running system?
    It's interesting for me too. Can someone explain me it in few words please?
    Last edited by goofy; 04-14-2011 at 07:03 PM.

  6. [translate]    #36
    Junior Member
    Join Date
    Sep 2010
    Location
    Moscow, Russia
    Posts
    23

    Default

    It is written by LeshaK here that it is necessary to flash the bootloader files during an update from Android 1.5 to Android 2.1. I updated Android on my Spica to 2.1 using the JH1 version. I have noticed recently it doesn't contain the bootloader files (it has 5 files instead of 8 and the 3 missing files are the bootloader ones: logo.png, Sbl.bin and boot.bin). But my phone booted and worked properly. I don't understand why it is necessary to flash them during an update from 1.5 to 2.1.

  7. [translate]    #37
    Junior Member
    Join Date
    May 2011
    Location
    Europe
    Posts
    2

    Default

    How can I determine the mapping from /dev files to partitions?

    I activated USB-debugging and logged in with adb shell. and ls into /dev and found all eleven bml* files from bml0 to bml10. I executed a mount, but it only lists /dev/bml8 mounted on /xbin. But what about the other partitions, how can I determine where they are mounted?

    To clarify again: I am interested in the how, not in the what. I don't want to know what partitions exist and how they are mounted, but I want to know how I can determine which partitions are present and how they are mounted.
    Last edited by sysrq11; 05-14-2012 at 06:02 PM.

Page 4 of 4 FirstFirst ... 234

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •