Jump to content


Photo

2 streaks, very similar problems


  • Please log in to reply
7 replies to this topic

#1
scoop_987

scoop_987

    Newbie

  • Members
  • Pip
  • 9 posts
  • Devices:Dell Streak
I bought 2 streaks off ebay. One had software issues and the other has software issues and a cracked LCD.

After azurren points me in the direction of the 360 update, I got the first streak to work and had an uptime of 100 hrs (Never used it though). I turn the phone off and back on and enters a bootloop (no logcat) and wont boot into android.

The 2nd streak crashes and reboots when Im in fastboot. I have no idea whats wrong with it, I done the sim and SD card test and returned ok. I also flashed the 360 recovery, I attempted to boot into recovery (The actual recovery, not just the menu) and crashed just after the first set of flashing lights.

Anyone have any idea?

Oh, and they dont have a warranty.

  • 0

#2
(InsertNameHere)

(InsertNameHere)

    Newbie

  • Members
  • Pip
  • 39 posts
Right, the first streak that seems to be ok, start again, flash recover.img using fastboot and then flash 360 using the recovery option, upon reboot hold down volume up and down, and choose to do a factory reset, once in android, set it up and reboot, see if it works.

Second one, i would start by testing and replacing the internal sd card, not the external. You will need to do a bit of research, look on youtube, you can find a video of a guy cutting the shield above where the internal sd card is, then you can replace the internal sd card and see if that fixes your problem, it is possible there is some other problem that is hardware related with both devices and beyond basic fixes.

Edited by (InsertNameHere), 04 November 2011 - 12:50 AM.

  • 0

#3
Azurren

Azurren

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,964 posts
  • Gender:Male
  • Location:Cornwall
  • Devices:Dell Streak
  • Twitter:@Azurren

Right, the first streak that seems to be ok, start again, flash recover.img using fastboot and then flash 360 using the recovery option, upon reboot hold down volume up and down, and choose to do a factory reset, once in android, set it up and reboot, see if it works.

Second one, i would start by testing and replacing the internal sd card, not the external. You will need to do a bit of research, look on youtube, you can find a video of a guy cutting the shield above where the internal sd card is, then you can replace the internal sd card and see if that fixes your problem, it is possible there is some other problem that is hardware related with both devices and beyond basic fixes.

I second this. Although I would try removing the external SD card from the second one first
Its a longshot but sometimes dodgy SD cards can cause strange effects
And it only takes 5 seconds to remove it anyway

  • 1

#4
scoop_987

scoop_987

    Newbie

  • Members
  • Pip
  • 9 posts
  • Devices:Dell Streak
The 1st streak is working fully now. so no need to worry about that one. It boots and reboots fine now. No idea what went wrong but its working so I wont be touching it again.




The 2nd streak is where my bother is, I replaced the screen and have the 360 recovery image on it with the 360 build. The problem is, when it does decide to boot, it crashes with the flashing lights. It would then crash when loading android, then boot into android and crash again and thats as far as it goes, obviously I have access to recovery and fastboot with no problems. I tested the internal SD card via fastboot and have no errors (What test does it do anyway?).


  • 0

#5
(InsertNameHere)

(InsertNameHere)

    Newbie

  • Members
  • Pip
  • 39 posts

The 1st streak is working fully now. so no need to worry about that one. It boots and reboots fine now. No idea what went wrong but its working so I wont be touching it again.




The 2nd streak is where my bother is, I replaced the screen and have the 360 recovery image on it with the 360 build. The problem is, when it does decide to boot, it crashes with the flashing lights. It would then crash when loading android, then boot into android and crash again and thats as far as it goes, obviously I have access to recovery and fastboot with no problems. I tested the internal SD card via fastboot and have no errors (What test does it do anyway?).



Test the internal SD outside of the streak.

To replace the internal SD is gonna be cheap. a 4GB one will do, however, thats not to say the device doesn't have some other problem, The internal SD is one of the easier things to replace, after that its some other hardware problem.

Edited by (InsertNameHere), 06 November 2011 - 10:55 AM.

  • 0

#6
scoop_987

scoop_987

    Newbie

  • Members
  • Pip
  • 9 posts
  • Devices:Dell Streak
Tried an update this morning and looked good, but then wouldnt boot. I done a factory reset (I thought it done that automatically?) and its working perfectly now, just waiting to see what the uptime will be like before (if) it crashes.

  • 0

#7
scoop_987

scoop_987

    Newbie

  • Members
  • Pip
  • 9 posts
  • Devices:Dell Streak
Ok it crashed, and the logcat states this:


W/PrintK  (   19): MODM:    1153528 	ERROR: ERR_ERROR_FATAL_TASK: 00000000 00000000 00000000 00527ef7 00000000 01490448
W/PrintK  (   19): MODM:    1153528 	ERROR: ERR_ERROR_FATAL: 4d444357 6146583a 20746c75 00527e00 00000000 00


Anyone know the problem? Chances of being a bad modem?
EDIT: 2nd attempt come back with this:

W/PrintK  (   19): MODM:    1091886     ERROR: ERR_ERROR_FATAL_TASK: 00000000 00000000 00000000 00527ef7 00000000 01490448
W/PrintK  (   19): MODM:    1091887     ERROR: ERR_ERROR_FATAL: 4d444357 6146583a 20746c75 00527e00 00000000 00000000
W/PrintK  (   19): MODM:    1162592     ERROR: ERR_ERROR_FATAL_TASK: 30545349 00000000 00000000 00000000 0139aa9a 01c0fe60
W/PrintK  (   19): MODM:    1162592     ERROR: ERR_ERROR_FATAL: 6d316c77 0000632e 00000000 00000000 0139aa9a 000013d6
V/PrintK  (  166): ARM9 has CRASHED
W/PrintK  (  166): smd_diag, smem: DIAG ''
W/PrintK  (  166): ARM9 has CRASHED
W/PrintK  (  166): smd_diag, smem: DIAG ''
W/PrintK  (  166): ARM9 has CRASHED
W/PrintK  (  166): smd_diag, smem: DIAG ''
W/PrintK  (  166): ARM9 has CRASHED
W/PrintK  (  166): smd_diag, smem: DIAG ''
W/PrintK  (   20): smd_restart_modem...
W/PrintK  (   95): ARM9 has CRASHED
W/PrintK  (   95): smd_diag, smem: DIAG ''
W/PrintK  (   95): ARM9 has CRASHED
W/PrintK  (   95): smd_diag, smem: DIAG ''
W/PrintK  (   95): <4>------------[ cut here ]------------
W/PrintK  (   95): <4>WARNING: at arch/arm/mach-msm/clock-pcom.c:78 pc_clk_disable+0x58/0xb0()
W/PrintK  (   95): <d>Modules linked in:
V/PrintK  (   95): 
W/PrintK  (   95): [<c0037204>] (unwind_backtrace+0x0/0x164) from [<c007a3b0>] (warn_slowpath_common+0x4c/0x64)
W/PrintK  (   95): [<c007a3b0>] (warn_slowpath_common+0x4c/0x64) from [<c007a3e0>] (warn_slowpath_null+0x18/0x1c)
W/PrintK  (   95): [<c007a3e0>] (warn_slowpath_null+0x18/0x1c) from [<c004068c>] (pc_clk_disable+0x58/0xb0)
W/PrintK  (   95): [<c004068c>] (pc_clk_disable+0x58/0xb0) from [<c003f0a8>] (clk_disable+0x18/0x1c)
W/PrintK  (   95): [<c003f0a8>] (clk_disable+0x18/0x1c) from [<c02d812c>] (kgsl_pwrctrl_clk+0x50/0x100)
W/PrintK  (   95): [<c02d812c>] (kgsl_pwrctrl_clk+0x50/0x100) from [<c02d836c>] (kgsl_pwrctrl_sleep+0x108/0x160)
W/PrintK  (   95): [<c02d836c>] (kgsl_pwrctrl_sleep+0x108/0x160) from [<c02d8400>] (kgsl_idle_check+0x3c/0x6c)
W/PrintK  (   95): [<c02d8400>] (kgsl_idle_check+0x3c/0x6c) from [<c008d328>] (worker_thread+0x180/0x22c)
W/PrintK  (   95): [<c008d328>] (worker_thread+0x180/0x22c) from [<c00908b4>] (kthread+0x78/0x80)
W/PrintK  (   95): [<c00908b4>] (kthread+0x78/0x80) from [<c0031fe4>] (kernel_thread_exit+0x0/0x8)
W/PrintK  (   95): <4>---[ end trace cf8eb052de567981 ]---




Edited by scoop_987, 06 November 2011 - 03:34 PM.

  • 0

#8
scoop_987

scoop_987

    Newbie

  • Members
  • Pip
  • 9 posts
  • Devices:Dell Streak
Ok, tried the 360 rom and whilst it booted it gave me the above error log. So i stripped both streaks down and swapped the SD cards over (both have the 360 rom on them), and its still doing the same so I think its either a dud mainboard OR its just a simple stupid thing that I've missed.

Since changing the SD cards hasnt sorted it, anyone else with any other ideas?
Thanks, Lewis



  • 0




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users