Re: [android-building] 'Erase successful, but not automatically formatting. Can't determine partition type' - Nexus S
2,013 views
Skip to first unread message
Jean-Baptiste Queru
Jan 8, 2013, 10:44:32 AM1/8/13
to android-...@googlegroups.com
This is a warning, not an error, and you can safely ignore it on Nexus S.
When possible, fastboot -w internally uses fastboot format instead of
fastboot erase. The goal is to generate a filesystem on the host and
send it to the bootloader, instead of trusting the device to do so
(which causes trouble). In order to do that, the bootloader needs to
return the size and filesystem type of the partitions, and the Nexus S
bootloader doesn't do that (it's too old). The first device that does
that is Galaxy Nexus.
JBQ
On Mon, Jan 7, 2013 at 7:24 PM, Eishita Farjana <eze...@gmail.com> wrote:
> I'm having the following error -
>
> Bootloader Version...: I9020XXLC2
> Baseband Version.....: I9020XXKI1
> Serial Number........: 3334E1630CFF00EC
> --------------------------------------------
> checking product...
> OKAY [ 0.001s]
> sending 'boot' (3964 KB)...
> OKAY [ 0.693s]
> writing 'boot'...
> OKAY [ 0.603s]
> sending 'recovery' (4308 KB)...
> OKAY [ 0.541s]
> writing 'recovery'...
> OKAY [ 0.652s]
> sending 'system' (173123 KB)...
> OKAY [ 22.336s]
> writing 'system'...
> OKAY [ 24.196s]
> erasing 'userdata'...
> OKAY [ 0.243s]
> formatting 'userdata' partition...
> Erase successful, but not automatically formatting.
> Can't determine partition type.
> OKAY [ 0.001s]
> erasing 'cache'...
> OKAY [ 1.684s]
> formatting 'cache' partition...
> Erase successful, but not automatically formatting.
> Can't determine partition type.
> OKAY [ 0.001s]
> rebooting...
>
> finished. total time: 50.956s
>
> after I executed command - fastboot flashall -w while bulding jelly bean
> 4.1.2 in Galaxy Nexus. I had a look in the thread
> https://groups.google.com/forum/?fromgroups=#!topic/android-platform/h8Ewsl7ilZA,
> but could not really understand how to solve the issue. Can anyone help
> please?
>
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
When possible, fastboot -w internally uses fastboot format instead of
fastboot erase. The goal is to generate a filesystem on the host and
send it to the bootloader, instead of trusting the device to do so
(which causes trouble). In order to do that, the bootloader needs to
return the size and filesystem type of the partitions, and the Nexus S
bootloader doesn't do that (it's too old). The first device that does
that is Galaxy Nexus.
JBQ
On Mon, Jan 7, 2013 at 7:24 PM, Eishita Farjana <eze...@gmail.com> wrote:
> I'm having the following error -
>
> Bootloader Version...: I9020XXLC2
> Baseband Version.....: I9020XXKI1
> Serial Number........: 3334E1630CFF00EC
> --------------------------------------------
> checking product...
> OKAY [ 0.001s]
> sending 'boot' (3964 KB)...
> OKAY [ 0.693s]
> writing 'boot'...
> OKAY [ 0.603s]
> sending 'recovery' (4308 KB)...
> OKAY [ 0.541s]
> writing 'recovery'...
> OKAY [ 0.652s]
> sending 'system' (173123 KB)...
> OKAY [ 22.336s]
> writing 'system'...
> OKAY [ 24.196s]
> erasing 'userdata'...
> OKAY [ 0.243s]
> formatting 'userdata' partition...
> Erase successful, but not automatically formatting.
> Can't determine partition type.
> OKAY [ 0.001s]
> erasing 'cache'...
> OKAY [ 1.684s]
> formatting 'cache' partition...
> Erase successful, but not automatically formatting.
> Can't determine partition type.
> OKAY [ 0.001s]
> rebooting...
>
> finished. total time: 50.956s
>
> after I executed command - fastboot flashall -w while bulding jelly bean
> 4.1.2 in Galaxy Nexus. I had a look in the thread
> https://groups.google.com/forum/?fromgroups=#!topic/android-platform/h8Ewsl7ilZA,
> but could not really understand how to solve the issue. Can anyone help
> please?
>
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to android-...@googlegroups.com
> To unsubscribe from this group, send email to
> android-buildi...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en
--
Jean-Baptiste M. "JBQ" Queru
Technical Lead, Android Open Source Project, Google.
Questions sent directly to me that have no reason for being private
will likely get ignored or forwarded to a public forum with no further
warning.
Jean-Baptiste Queru
Jan 8, 2013, 12:53:09 PM1/8/13
to android-...@googlegroups.com
Those might be related.
How long have you waited for the system to load? At first boot,
Android noticed that the /userdata partition isn't formatted, and has
to format it in the background, which takes quite some time (it can
take several minutes). During that time, there's no UI, and eventually
the system reboots once it's done.
This might be what you're seeing.
JBQ
On Tue, Jan 8, 2013 at 9:06 AM, Eishita Farjana <eze...@gmail.com> wrote:
> Hi JBQ,
>
> Thanks very much for your response.
>
> But Later, it never loads the system. So that is the issue I'm having. Not
> sure what is going on.
>
> Thanks,
> Eishita
How long have you waited for the system to load? At first boot,
Android noticed that the /userdata partition isn't formatted, and has
to format it in the background, which takes quite some time (it can
take several minutes). During that time, there's no UI, and eventually
the system reboots once it's done.
This might be what you're seeing.
JBQ
On Tue, Jan 8, 2013 at 9:06 AM, Eishita Farjana <eze...@gmail.com> wrote:
> Hi JBQ,
>
> Thanks very much for your response.
>
> But Later, it never loads the system. So that is the issue I'm having. Not
> sure what is going on.
>
> Thanks,
> Eishita
Jean-Baptiste Queru
Jan 8, 2013, 2:18:48 PM1/8/13
to android-...@googlegroups.com
One hour is definitely too long.
Is there anything interesting in logcat?
JBQ
On Tue, Jan 8, 2013 at 9:56 AM, Eishita Farjana <eze...@gmail.com> wrote:
> Well, I waited for more than an hour. I'm still trying but no luck.
>
> I was following the instruction from here -
> http://source.android.com/source/building.html and
> http://source.android.com/source/building-devices.html.
>
> Thanks,
> Eishita
Is there anything interesting in logcat?
JBQ
On Tue, Jan 8, 2013 at 9:56 AM, Eishita Farjana <eze...@gmail.com> wrote:
> Well, I waited for more than an hour. I'm still trying but no luck.
>
> I was following the instruction from here -
> http://source.android.com/source/building.html and
> http://source.android.com/source/building-devices.html.
>
> Thanks,
> Eishita
Jean-Baptiste Queru
Jan 8, 2013, 3:32:22 PM1/8/13
to android-...@googlegroups.com
At a glance, I'd say you don't have the GPU libraries.
https://developers.google.com/android/nexus/drivers
JBQ
On Tue, Jan 8, 2013 at 11:35 AM, Eishita Farjana <eze...@gmail.com> wrote:
> I have attached the log file. You can have a look.
https://developers.google.com/android/nexus/drivers
JBQ
On Tue, Jan 8, 2013 at 11:35 AM, Eishita Farjana <eze...@gmail.com> wrote:
> I have attached the log file. You can have a look.
Jean-Baptiste Queru
Jan 8, 2013, 4:41:50 PM1/8/13
to android-...@googlegroups.com
Each tgz contains an "extract-<company>-crespo.sh" script, which you
need to execute at the root of the source tree.
JBQ
On Tue, Jan 8, 2013 at 12:54 PM, Eishita Farjana <eze...@gmail.com> wrote:
> Well, I have downloaded it, extracted but not sure where should I keep the
> folder. I'm sorry if I'm asking naive questions but I have never handled
> android OS this before. I appreciate your help.
>
> Thanks
need to execute at the root of the source tree.
JBQ
On Tue, Jan 8, 2013 at 12:54 PM, Eishita Farjana <eze...@gmail.com> wrote:
> Well, I have downloaded it, extracted but not sure where should I keep the
> folder. I'm sorry if I'm asking naive questions but I have never handled
> android OS this before. I appreciate your help.
>
> Thanks
Jean-Baptiste Queru
Jan 8, 2013, 5:16:51 PM1/8/13
to android-...@googlegroups.com
You might have forgotten to run "make" before re-flashing.
JBQ
On Tue, Jan 8, 2013 at 2:04 PM, Eishita Farjana <eze...@gmail.com> wrote:
> Ok So I kept extract-samsung-crespo.sh in the root directory and then ran it
> with the command
>
> sh extract-samsung-crespo.sh
>
> It extracted a directory named Vendor.
>
> Later I executed the commands -
>
> adb reboot bootloader
> and then
> fastboot flashall -w
>
> Still it's all the same. I have no clue.
JBQ
On Tue, Jan 8, 2013 at 2:04 PM, Eishita Farjana <eze...@gmail.com> wrote:
> Ok So I kept extract-samsung-crespo.sh in the root directory and then ran it
> with the command
>
> sh extract-samsung-crespo.sh
>
> It extracted a directory named Vendor.
>
> Later I executed the commands -
>
> adb reboot bootloader
> and then
> fastboot flashall -w
>
> Still it's all the same. I have no clue.
Antonio Marin Cerezuela
Jan 10, 2013, 3:37:14 AM1/10/13
to android-...@googlegroups.com
Hi Eishita,
Try extracting all the proprietary files, not just the graphic controller. I'm not sure which ones are required for the system to boot, but all are necessary if you want a fully functional system. I compiled recently the same tag for the Galaxy S and flashed without problem.
Also, try formatting the data and cache partitions from the recovery menu before normally booting the system.
BR,
Tony
El 09/01/13 00:12, Eishita Farjana escribió:
Try extracting all the proprietary files, not just the graphic controller. I'm not sure which ones are required for the system to boot, but all are necessary if you want a fully functional system. I compiled recently the same tag for the Galaxy S and flashed without problem.
Also, try formatting the data and cache partitions from the recovery menu before normally booting the system.
BR,
Tony
El 09/01/13 00:12, Eishita Farjana escribió:
Ok now my sequence of commands were -
make -j4
adb reboot bootloader
fastboot -w flashall
As I said I already ran the .sh file and extracted the directory vendor in the OS root file.
Still same issue. :(
-- Antonio Marin Research Dept Swiss Mobility Solutions Av. Jaime I El Conquistador 1, Local 2 03560 El Campello Spain www.swissmobilitysolutions.com Este mensaje contiene informacion reservada y confidencial destinada exclusivamente al destinatario. Si usted no es el destinatario no esta autorizado a copiar, reproducir o distribuir este mensaje ni su contenido. Si ha recibido este mensaje por error, le rogamos que nos lo notifique inmediatamente. The information in this e-mail is confidential and may be legally privileged. It is intended solely for the addressee(s). It may contain privileged and confidential information. If you are not the intended recipient, please destroy this message and notify us immediately. Any disclosure, copying or distribution of this message is prohibited and may be unlawful.
Reply all
Reply to author
Forward
0 new messages