FORUMS
Remove All Ads from XDA

Bootloop problems, flashing sbf doesn't work

657 posts
Thanks Meter: 277
 
By kv1dr, Senior Member on 21st March 2012, 09:50 PM
Post Reply Email Thread
Hi everybody. I was stupid and I installed Linux installer on my phone. I don't know why I did this, but I tried to install Linux Ubuntu on Milestone. Because milestone's kernel doesn't support loop mode, I tried to install with chroot method(I made a nandroid backup before I started installing Ubuntu). While the app was downloading things needed for Ubuntu to work, the internal memory became full and my phone started to act very wierd(A lot of FCs, one after another), so I restarted my phone. But after restart my milestone started to bootloop(The CM7's boot animation is still shown). I tried to restore my backup, but it didn't help. I tried to flash stock ROM(2.1 and also 2.2) with RSD Lite and also with sbf_flash, I also tried full wipe and I also tried to flash vulnerable recovery only but I am still getting the bootloops. With stock ROM the phone restarts on 'M' logo, with CM7 it restarts on boot animation and with CM9 it stucks on bootanimation. I can access bootloader, I can flash everything ok without any errors, I can access recovery mode, I can charge turned off phone, but can't secusseful boot my phone. How to fix that?

Any help would be appreciated.
 
 
21st March 2012, 11:23 PM |#2  
kabaldan's Avatar
Recognized Developer
Flag Prague
Thanks Meter: 3,925
 
Donate to Me
More
CM7:
boot to recovery and enable logger from OpenRecovery console or adb shell
Code:
echo 1 > /data/property/persist.service.aplogd.enable
let the phone boot and when it starts looping, reboot to recovery
fetch the logs to pc via usb
Code:
adb pull /cache/logger
post the logs for inspection
The Following User Says Thank You to kabaldan For This Useful Post: [ View ]
22nd March 2012, 08:01 AM |#3  
kv1dr's Avatar
OP Senior Member
Flag Gornji Grad
Thanks Meter: 277
 
Donate to Me
More
Wow..doesn't this looks like kernel panic?

AOL_kernel.ap.bin
Code:
03-22 07:46:36.426 D/kernel  (    0): [   16.526306] [<c0035b24>] (unwind_backtrace+0x0/0xd8) from [<c005d15c>] (warn_slowpath_common+0x48/0x60)
03-22 07:46:36.426 D/kernel  (    0): [   16.526336] [<c005d15c>] (warn_slowpath_common+0x48/0x60) from [<c005d1ac>] (warn_slowpath_fmt+0x24/0x30)
03-22 07:46:36.426 D/kernel  (    0): [   16.526367] [<c005d1ac>] (warn_slowpath_fmt+0x24/0x30) from [<c009137c>] (__free_irq+0x98/0x1dc)
03-22 07:46:36.426 D/kernel  (    0): [   16.526397] [<c009137c>] (__free_irq+0x98/0x1dc) from [<c00914fc>] (free_irq+0x3c/0x5c)
03-22 07:46:36.426 D/kernel  (    0): [   16.526458] [<c00914fc>] (free_irq+0x3c/0x5c) from [<c02a5948>] (sim_ioctl+0x3e8/0x138c)
03-22 07:46:36.426 D/kernel  (    0): [   16.526489] [<c02a5948>] (sim_ioctl+0x3e8/0x138c) from [<c00c8720>] (vfs_ioctl+0x70/0x8c)
03-22 07:46:36.426 D/kernel  (    0): [   16.526519] [<c00c8720>] (vfs_ioctl+0x70/0x8c) from [<c00c8d8c>] (do_vfs_ioctl+0x558/0x5c4)
03-22 07:46:36.426 D/kernel  (    0): [   16.526550] [<c00c8d8c>] (do_vfs_ioctl+0x558/0x5c4) from [<c00c8e2c>] (sys_ioctl+0x34/0x54)
03-22 07:46:36.426 D/kernel  (    0): [   16.526611] [<c00c8e2c>] (sys_ioctl+0x34/0x54) from [<c0030f40>] (ret_fast_syscall+0x0/0x2c)
03-22 07:46:36.426 D/kernel  (    0): [   16.526641] ---[ end trace 1b75b31a2719ed1e ]---
AOL_main.ap.bin
Code:
03-22 07:46:51.700 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:46:51.762 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:46:52.700 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:46:52.762 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:46:53.707 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:46:53.762 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:46:54.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:46:54.762 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:46:55.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:46:55.762 W/AudioSystem( 2120): AudioPolicyService not published, waiting...
03-22 07:46:56.262 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:46:56.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:46:57.270 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:46:57.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:46:58.270 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:46:58.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:46:59.270 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:46:59.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:47:00.270 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:47:00.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:47:01.270 W/AudioSystem( 2120): AudioPolicyService not published, waiting...
03-22 07:47:01.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:47:01.770 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:47:02.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:47:02.770 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:47:03.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:47:03.770 I/ServiceManager( 2120): Waiting for service media.audio_policy...
03-22 07:47:04.708 E/panic_daemon( 1515): Couldn't open ACM: /dev/ttyACM0 with error d, will reboot soon.
03-22 07:47:04.778 I/ServiceManager( 2120): Waiting for service media.audio_policy...
I hope this is not hardware failure.

P.S.: All logs are attached.
Attached Files
File Type: zip logs.zip - [Click for QR Code] (23.3 KB, 12 views)
22nd March 2012, 09:31 AM |#4  
kabaldan's Avatar
Recognized Developer
Flag Prague
Thanks Meter: 3,925
 
Donate to Me
More
I'm afraid that you erased your pds partition. Have you made a backup of it in the past by any chance?

To list content of your pds block, boot to OR and in console or adb shell do:
Code:
mkdir /pds
mount /dev/block/mtdblock5 /pds
ls -lR /pds
In the current state, you should be able to boot the system if you disable the panic daemon (comment out the lines 496-501 in /system/etc/rootfs/init.mapphone_umts.rc - https://github.com/nadlabak/android_...e_umts.rc#L496 ). But your radio won't work.
The Following User Says Thank You to kabaldan For This Useful Post: [ View ]
22nd March 2012, 09:51 AM |#5  
kv1dr's Avatar
OP Senior Member
Flag Gornji Grad
Thanks Meter: 277
 
Donate to Me
More
It looks like it's everything ok with pds partition. After mounting pds partition I got this:

Code:
# ls -lR /pds
/pds:
drwxrwx---    1 radio    radio         2048 Mar 22 07:22 bp_nvm
drwxrwx---    1 radio    radio         2048 Mar 21 09:15 comm_drv
drwxrwx---    1 root     root          2048 Jan  1  1970 lost+found
drwxrwx---    1 radio    shell         2048 Mar 21 09:15 opprof
drwxrwxr-x    1 9000     9000          2048 Mar 21 09:09 public
I now disabled panic deamon and now my phone stuck at boot animation.
22nd March 2012, 10:41 AM |#6  
kabaldan's Avatar
Recognized Developer
Flag Prague
Thanks Meter: 3,925
 
Donate to Me
More
If the listing above is complete, then the state of your pds partition is far from OK.
It has been obviously erased and now contains only empty folders created during boot.

Your boot is currently stalled at "Waiting for service media.audio_policy" - the successful audio driver initialization depends on some files in /pds...

The problem with pds content is that some files there are unique for each phone. Namely e.g. /pds/bp_nvm/File_PDS_IMEI (each phone has to have unique IMEI) and also e.g. /pds/wifi/nvs_map.bin (contains unique wifi MAC address). Wile the wifi MAC is not a big issue, I'm afraid that no one will be willing to give you his file with his encoded IMEI number. I'm also not sure if the IMEI files can be actually used on a different phone other than the one for which they've been generated.
The Following 2 Users Say Thank You to kabaldan For This Useful Post: [ View ]
22nd March 2012, 10:59 AM |#7  
kv1dr's Avatar
OP Senior Member
Flag Gornji Grad
Thanks Meter: 277
 
Donate to Me
More
Woops, this is the whole output of ls -lR /pds
Code:
# ls -lR
.:
drwxrwx---    1 radio    radio         2048 Mar 22 09:51 bp_nvm
drwxrwx---    1 radio    radio         2048 Mar 21 09:15 comm_drv
drwxrwx---    1 root     root          2048 Jan  1  1970 lost+found
drwxrwx---    1 radio    shell         2048 Mar 21 09:15 opprof
drwxrwxr-x    1 9000     9000          2048 Mar 21 09:09 public
drwxrwx---    1 system   system        2048 Mar 21 09:15 security
drwxrwx--x    1 wifi     wifi          2048 Mar 21 09:15 wifi

./bp_nvm:
-rw-rw-rw-    1 radio    radio         1517 Mar 22 06:37 NVM_Daemon_MD5

./comm_drv:
-rw-rw----    1 radio    radio         2964 Mar 21 09:15 mmins_settings.cfg

./lost+found:

./opprof:

./public:
drwxr-x---    1 9000     9000          2048 May 26  2011 battd

./public/battd:

./security:

./wifi:
A lot of folders are empty...and the only backup I have is nandroid backup. But nandroid doesn't backup pds partition.

So...that means I can't bring my phone back to life?
22nd March 2012, 01:20 PM |#8  
Junior Member
Thanks Meter: 0
 
More
I have the same problem:

Milestone-Recovery:/
# ls pds/ -R
pds/:
bp_nvm lost+found public wifi
comm_drv opprof security
pds/bp_nvm:
NVM_Daemon_MD5
pds/comm_drv:
mmins_settings.cfg
pds/lost+found:
pds/opprof:
pds/public:
battd
pds/public/battd:
pds/security:
pds/wifi:
Milestone-Recovery:/

I don't have the file: /system/etc/rootfs/init.mapphone_umts.rc
# ls /system/etc/
01_Vendor_ti_omx.cfg location.cfg
NOTICE.html.gz media_profiles.xml
apns-conf.xml motorola
bluetooth nuance
bluez permissions
cameraCalFileDef5M.bin photoworkshop
cameraCalFileDef8M.bin ppp
dbus.conf pvasflocal.cfg
dhcpcd pvplayer.cfg
event-log-tags pvplayer_mot.cfg
excluded-input-devices.xml security
firmware updatecmds
gpsconfig.xml vold.conf
hosts vold.fstab
init.d wifi
init.goldfish.sh
Milestone-Recovery:/


My phone is now garbage? can i utilize it for gps navigation?
can i clone pds directory from an low cost android phone?
Qwewq!
22nd March 2012, 09:16 PM |#9  
mrvek's Avatar
Senior Member
/home
Thanks Meter: 462
 
More
When checking for the sake of precaution I found that while the system is running my pds is mounted at mtdblock0, not mtdblock5. Latest unofficial/nightly cm7 rc1 posted on xgraphs a few days ago.
Just wondering if this is ok and if pds can be backed up by using
Code:
dd if='proper mtdblock' of=/sdcard/pds.img
while the system is running and restored by reversing input and output files. Because in OR pds can be mounted by mtdblock5 while mtdblock0 gives error (invalid argument). A bit odd.
22nd March 2012, 09:50 PM |#10  
kabaldan's Avatar
Recognized Developer
Flag Prague
Thanks Meter: 3,925
 
Donate to Me
More
Unlike the normal running system that shows only subset of mtd blocks, OpenRecovery makes all mtd blocks accessible, that's why the numbers are different.
Use
Code:
cat /proc/mtd
to see the list of available mtds.

In OR, mtdblock0 is mbmloader - that mtd block does not contain any filesystem, so it can't be mounted.

I simply use tar to backup already mounted pds
Code:
tar -cf /sdcard/pds.tar pds
dd should work as well.
The Following User Says Thank You to kabaldan For This Useful Post: [ View ]
8th April 2012, 03:47 AM |#11  
Member
Thanks Meter: 1
 
More
i also have this problem recently.. i just swipe data.. it fixed it.. every time that it bootloops.. i always swipe the data.. it it will boot up normally..

honestly i really new to this andriod thing and i dont understand that the codes are..

but it works..
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes