FORUMS

[Q] Bricked. Samsung Logo/Broken recovery

12 posts
Thanks Meter: 1
 
By ChrisMcIntosh, Junior Member on 8th June 2014, 02:58 PM
Post Reply Subscribe to Thread Email Thread
I need some assistance please. My phone is stuck on the Samsung Logo. When booting into recovery it just shows the Teamwin logo then reboots.

I didn't seem to modify anything. The phone just crashed one day.

I believe the android version it's on is 4.1.2, rooted, teamwin, flash counter (can't kies)

It hadn't been updated in a long time because my USB flex cable was faulty. I repaired this after the phone bricked and it seems to be functioning properly to charge and send data via odin.

I tried several fixes by flashing alleged stock roms with Odin. This didn't fix the issue or I did something wrong. I searched around a bit on the forums but it is difficult because there is so much information and many broken links. If anyone can help I would really appreciate it.

The ironic part is that my contract just ran out 2 days after it bricked. Sprint's trying to covertly get me to renew

(p.s. I'm currently on a Samsung Epic 4G, gingerbread!! It's quite a downgrade!!)

Also, ideally if the phone can be fixed I would like to have a rooted KitKat, so if the solution involves that no worries. I just want the phone to work really.
Last edited by ChrisMcIntosh; 8th June 2014 at 03:04 PM.
 
 
9th June 2014, 01:15 AM |#2  
Account currently disabled
Flag houston, tx
Thanks Meter: 5,837
 
Donate to Me
More
Quote:
Originally Posted by ChrisMcIntosh

I need some assistance please. My phone is stuck on the Samsung Logo. When booting into recovery it just shows the Teamwin logo then reboots.

I didn't seem to modify anything. The phone just crashed one day.

I believe the android version it's on is 4.1.2, rooted, teamwin, flash counter (can't kies)

It hadn't been updated in a long time because my USB flex cable was faulty. I repaired this after the phone bricked and it seems to be functioning properly to charge and send data via odin.

I tried several fixes by flashing alleged stock roms with Odin. This didn't fix the issue or I did something wrong. I searched around a bit on the forums but it is difficult because there is so much information and many broken links. If anyone can help I would really appreciate it.

The ironic part is that my contract just ran out 2 days after it bricked. Sprint's trying to covertly get me to renew

(p.s. I'm currently on a Samsung Epic 4G, gingerbread!! It's quite a downgrade!!)

Also, ideally if the phone can be fixed I would like to have a rooted KitKat, so if the solution involves that no worries. I just want the phone to work really.

Sounds like a corrupt recovery. Use odin to flash another recovery (suggest philz 6.07.9).

Sent from my SPH-L900 using XDA Premium 4 mobile app
9th June 2014, 02:03 AM |#3  
OP Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by jlmancuso

Sounds like a corrupt recovery. Use odin to flash another recovery (suggest philz 6.07.9).

Sent from my SPH-L900 using XDA Premium 4 mobile app

Booting to recovery after flashing still gets me to the Teamwin logo then a reboot. Did I do something wrong?

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> philz_touch_6.07.9-l900.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
9th June 2014, 03:12 AM |#4  
Account currently disabled
Flag houston, tx
Thanks Meter: 5,837
 
Donate to Me
More
Try cwm then. I have had this issue before once with philz and once with twrp.

Sent from my SPH-L900 using XDA Premium 4 mobile app
9th June 2014, 04:42 PM |#5  
OP Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by jlmancuso

Try cwm then. I have had this issue before once with philz and once with twrp.

Sent from my SPH-L900 using XDA Premium 4 mobile app

<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> recovery.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/004> Added!!
<ID:0/003> Completed..
<ID:0/004> Added!!
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!

I tried cwm and same result of Teamwin logo and will not boot.
I had to convert the original cwm .img with a tool found in these forums to .md5.tar

Is it important to note that I currently dont have the SD card in the phone?
Also Odin is v3.04, Auto-reset and f. reset time are checked
13th June 2014, 12:16 AM |#6  
OP Junior Member
Thanks Meter: 1
 
More
Just for kicks I tried flashing the various recoveries with the reboot off. Tried various versions of Odin.
Still all result in a failure.

Please help.
13th June 2014, 02:49 AM |#7  
g_money's Avatar
Senior Member
Thanks Meter: 338
 
More
You *might* try this

http://forum.xda-developers.com/show....php?t=2780984

Stock 4.4.2. It would install stock recovery (I believe). If it works, you could then flash custom recovery and root.

I currently use odin v3.07 (I believe)

Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Last edited by g_money; 13th June 2014 at 02:52 AM.
13th June 2014, 04:22 AM |#8  
OP Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by g_money

You *might* try this

http://forum.xda-developers.com/show....php?t=2780984

Stock 4.4.2. It would install stock recovery (I believe). If it works, you could then flash custom recovery and root.

I currently use odin v3.07 (I believe)

Sent from my SPH-L710 using Xparent Cyan Tapatalk 2

Unfortunately this did not fix the problem.

Odin (I used 1.85 this particular time)
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_SPT_L900VPUCNE2_L900SPTCNE2_1561791_REV04_user _low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> param.bin
<ID:0/003> tz.img
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img
<ID:0/003> tombstones.img
<ID:0/003> modem.bin
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/003> Removed!!
<ID:0/004> Added!!
13th June 2014, 06:45 AM |#9  
g_money's Avatar
Senior Member
Thanks Meter: 338
 
More
The only thing that i could think of would be to pull the battery for about 10 minutes. Sounds dumb, but it got me out of a boot loop once...

Just used the same file to update my wife's phone (but she wasn't soft-bricked either.

When i come up with something more I'll be back....

Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
13th June 2014, 06:15 PM |#10  
g_money's Avatar
Senior Member
Thanks Meter: 338
 
More
Here's another thread that might help

http://forum.xda-developers.com/show....php?t=2781785

Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
13th June 2014, 07:16 PM |#11  
OP Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by g_money

Here's another thread that might help

http://forum.xda-developers.com/show....php?t=2781785

Sent from my SPH-L710 using Xparent Cyan Tapatalk 2

The link for the fix is either not present or it is in the other thread and the link doesn't work. I will try that when it's available.
As for the battery pull, I leave it out of the phone between trials of getting this device to work, however the status of the brick(?) has since changed since flashing your last suggestion and leaving the battery out overnight.

Now it hangs at the Galaxy Note II logo on normal power on. (This is the change, all else is the same)
If I boot by going in to download mode then hitting cancel it will loop on the Samsung Logo
Recovery will display Teamwin logo then boot loop on Samsung Logo

Read More
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