Develop Bugs

[Q] Soft Briked by Odin (HELP)

Hello,
I seem to have bricked one of my Epics. I can get it to boot to the Download screen, but I can't seem to get anything downloaded to it.
It previously had the CleanGB ROM (1.05?) with the EL30 modem, I think. I tried to use Odin to upgrade the modem to FB15, when 25% of the way through the phone screen changed to all one color. I unplugged and retried, but every time I get the same result (though the color is always different).
I've also tried flashing SPH-D700-EC05-8gb-REL.tar, and flashing that and the modem together. The process always dies (colored screen) or hangs (10 minutes and the modem still isn't flashed).
This USB cable and computer have been working as recently as a few days ago, so I have no particular reason to suspect them.
Any advice? Obviously the phone won't do anything other than Download right now.

You have a bad cord go get a new one... your screen changing color is the biggest tell tell sign of a bad connection. Get a good thick usb cord and you should be good to go
Sent from my SPH-D700 using xda premium

Might wanna try leaving the battery out for 15 minutes then go back to stock again with odin
Sent from my SPH-D700 using XDA App

Thanks guys, I'll try both suggestions.

Worked
Alright, the new cable and/or waiting 30 minutes worked. I flashed the ancient official ROM and modem, flashed CWM into recovery, booted into recovery and am now installing Sleeper ROM.

Netop said:
Alright, the new cable and/or waiting 30 minutes worked. I flashed the ancient official ROM and modem, flashed CWM into recovery, booted into recovery and am now installing Sleeper ROM.
Click to expand...
Click to collapse
It was the cable.. leaving the battery had Nothing to do with it... that's only useful when it won't go into download mode nonetheless glad you got it working.
Sent from my SPH-D700 using xda premium

Big Goron said:
You have a bad cord go get a new one... your screen changing color is the biggest tell tell sign of a bad connection. Get a good thick usb cord and you should be good to go
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I bricked one of my epics because of this back when I posted the eg22 leak. Same colored screens every time. Got a blackberry cord and it never happened again, plus Odin seems to upload images faster now.
Sent from my cm_tenderloin using Tapatalk 2 Beta-5

Screen is black but phone works?

i was out getting some pretty damn good ice cream tonight phone was working fine.. go to check time and black screen... lights for back and menu came up but screen is black... also after batt pull found that its still black but phone boots up and you can unlock it.. i think its just a bad phone but could anyone help me find out whats going on?
[ROM][UCALH1]Triune II[AllianceRom][81512]
is what i'm using... but yeah kinda sucks. the only thing great about working for AT&t is i can get a new one fast but was hoping it was a rom problem.. any idea what i can do?

Could be some loose connection with your digitizer call phone support or repair place.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

tacotino said:
[ROM][UCALH1]Triune II[AllianceRom][81512]
is what i'm using... but yeah kinda sucks. the only thing great about working for AT&t is i can get a new one fast but was hoping it was a rom problem.. any idea what i can do?
Click to expand...
Click to collapse
I didn't have this problem after I installed Triune II, but if you suspect the ROM is related, do a backup and install a different ROM to see if that resolves the problem..... just a thought and takes less than 5-10 min.

What does the screen look like in download mode or in CWM?
Sent from my SGH-I747 using xda premium

OK Found out that the screen is defective, no problem! Ferrying new phone Tuesday
Sent from my MB886 using xda premium

RiPpeR_dUdE said:
I didn't have this problem after I installed Triune II, but if you suspect the ROM is related, do a backup and install a different ROM to see if that resolves the problem..... just a thought and takes less than 5-10 min.
Click to expand...
Click to collapse
How can he back up what he cant see?
Sent from my SAMSUNG-SGH-I747 using xda premium

So i need help, I'm sending in my phone for warranty.. Do you think they'll fix the screen then see i have a custom ROM or wipe it the fix the screen... Or how do i put it to stock and reset the counter?
Sent from my MB886 using xda premium

Help... Bootloop? But not a bootloop? Confusion.

Rooted my i317 2 days ago with the "no triangle counter" method. All was good, got TWRP installed, nandroided stock and did my thing. Been rooting phones for many years and have yet to brick anything *knocks on virtual wood*. Installed paranoid android, and all was awesome. Decided to give another rom a try... Cant remember which, but im not thinking thats the issue.
Wiped, flashed, no errors, rom booted normally, but as i unlock the device i get three force close errors. Then reboot. Over and over. Restored three different backups and all three do the same thing. Never run into this one before. Admittedly i am worried. Not a rich man and bought this phone outright...
I am hoping flashing in odin the original root tar file will correct the issue. But honestly wanted to do some reading and post this first. Any help would be greatly appreciated.
Sent from my SAMSUNG-SGH-I957 using Tapatalk

Did you try flashing a touch wiz kernel before going back to a nandroid? If not try that and if so try a factory reset and then a good old reboot!
I assume you tried a cm10.1 rom?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Same thing happened to me and I did just use odin to push that tar file through, rerooted, and flashed in my rom. That to me seems to be the fix for the bootloop imo. But someone with more knowledge could correct me if im wrong. Probably didnt help you any but just thought I would share my experience and fix when I was in the same position.
Sent from my SGH-I317 using xda premium

Both of you are good people. Alleviated is a drastic understatement. Was afraid it was a bad internal storage (bad hard drive) and was an issue limitec to my device. Others have done it, it can be fixed.
Cheers, gonna odin reflash now. If not will figure it out.
Sent from my SAMSUNG-SGH-I957 using Tapatalk 2

Let me know im always ready to help and trouble shoot had lots of devices and theyve all lived through my tests and bad flashes :thumbup:
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2

Keep us posted.
Sent from my SGH-I317 using xda premium

jdc5 said:
Keep us posted.
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Help full group over here, Appreciated greatly. Ive messed up a couple devices pretty good in my day, but never beyond repair. Always credited to people round these forums.
The factory reset didnt seem to help. But if system apps are missing... Reflashed the original tar file, and am just sitting here with a lump in my throat watching the Samsung logo hang...
Anyone got a link for the original rogers firmware?
Sent from my SAMSUNG-SGH-I957 using Tapatalk 2

*edit* back to stock. Dont wanna speak too soon, kinda superstitious with phones. But i think im good. Took two trys to flash original firmware.
Thanks guys, **** not so bad when ya got communication in a forum.
Cheers
Sent from my SAMSUNG-SGH-I957 using Tapatalk 2

What I did when it was stuck at the Samsung logo was I took out the battery> held down volume up, center home, and power to go into the system and did a factory wipe> then it pulled through nack to stock. Give it a try and keep me posted.
Sent from my SGH-I317 using xda premium

I tried the factory wipe through the cwm recovery included, didnt work. Was still stuck on samsung logo. Reflashed with odin a second time which allowed a successful boot and recovery of my paranoid android backup. Im good to go... Gonna do some more reading though. Im missing something important with this phone. Moving from 4.1 to 4.2 roms or vice versa seems to be... Weird.
Anyways all good. Thanks.
Sent from my SGH-I317 using Tapatalk 2

Note 2 black screen ...

This is my first thread if i have something wrong then sorry guys.
I have a AT&T Note 2 phone for 1 month and suddenly the screen went black. I tried to pull out battery and restart but the screen is still black ( the phone still power up, i can touch it and hear it's sound as well ) my friends still can call me i dont know what to do please help me . I can farely see a black light in the screen when its starting up.
Sorry for my bad English. Have a good day guys.

can you get it into recovery or download mode?

SeraldoBabalu said:
can you get it into recovery or download mode?
Click to expand...
Click to collapse
Yes i can i did restore the stock firmware for it but no luck.

drop the phone ? maybe a hardware issue with the screen
Sent from my SAMSUNG-SGH-I317 using xda app-developers app

x2daz1102 said:
Yes i can i did restore the stock firmware for it but no luck.
Click to expand...
Click to collapse
What did you do b4 this happened to you? Like the above poster said, did you drop the phone? Did you previously have a custom Rom? What recovery your running? CWM or TWRP?? There are a lot of possibilities that could have caused that. :what:
The reason I asked all that because I had a similar issue happen to me messing around with a bootanimation. After putting it on my phone my screen would just stay black with all sounds working?
If you have a back (nandroid) up of the previous Rom, stock Rom you had on your phone b4 this issue I would put that back on there. Should fix your problem. Because after I restored my back up. Everything was back to normal..
Just my 2¢®
Sent from my SAMSUNG-SGH-I317 using Xparent SkyBlue Tapatalk 2

Bajanman said:
What did you do b4 this happened to you? Like the above poster said, did you drop the phone? Did you previously have a custom Rom? What recovery your running? CWM or TWRP?? There are a lot of possibilities that could have caused that. :what:
The reason I asked all that because I had a similar issue happen to me messing around with a bootanimation. After putting it on my phone my screen would just stay black with all sounds working?
If you have a back (nandroid) up of the previous Rom, stock Rom you had on your phone b4 this issue I would put that back on there. Should fix your problem. Because after I restored my back up. Everything was back to normal..
Just my 2¢®
Sent from my SAMSUNG-SGH-I317 using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
yea i dont think i droped my phone for once thank you for your advice i will try to restock firmware

4th time I had to factory restore. This is unbelievable.

Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium

If its boot looping that's not normal obviously you know that so I would exchange it. Keep swapping until you get a good one.
Sent from my Nexus 7 using Tapatalk 4

Rican Bx Bomba said:
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
wha?? I would return immediately.

Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium

player911 said:
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Will try that. Thanks!
Sent from my SPH-L710 using xda premium

player911 said:
Yea I don't know why its boot looping either. Maybe your factory images are corrupt and thus you keep restoring a bad image. Perhaps you have a bad sector in your memory.
You could test it by flashing a non-stock rom, such as CM10.2 which also uses a CM kernel.
Use it for a few days and See if the problem goes away or stays.
Either way, reflash stock using the Google Nexus 7 images. If the problem stays, then take it back. If it fixes it, then keep it.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thought I'll give you an update.. Installed CM10.2 for a few days, as you said.. No issues what so ever. Decided to try my luck with CoolRom and it bootlooped the moment I rebooted.
Decided on doing a complete wipe of the device and flashing a factory rom ( http://forum.xda-developers.com/showthread.php?t=2381582 ).
Don't want to give up hope yet.

Rican Bx Bomba said:
Had my N72013 for 2 weeks now, and it boot loop'd four times on me twice in one day.
This can't be only happening to me.
I ordered from Google (big mistake), their rep said they can send me a new model but I would have to pay for it (dock the amount) first then once I receive it, send in my current model then wait to get my $$$ back.
Is this an issue with 4.3 or the device. I really don't want to return it if this problem could be patched away with an update...
Forgot to mention, I'm unlocked and rooted. 32gigs. No dead pixels, minor light bleed that doesn't bother me at all.
What would you do?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app

smurphdogg said:
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Rooted it for some apps that required root access.

smurphdogg said:
Not sure why you would need to root this device. Its straight android and runs great without root or custom ROM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
There are tons of apps that require root access and are mandatory for many people including me.

I wouldn't bother to unlock and root. The N7 is flawless and fast out of the box.
Sent from my Nexus 7 using xda app-developers app

Again, root access is required for most decent backup programs and cloud data syncing apps. The issue doesn't require a debate about whether you need root or not. Yes the N7 is wicked fast and if you only use it as a bathroom reader for Facebook and light use, then that's cool. I like OTG support for my thumb drives when I'm in the field working.
Glad CM is working for you. That at least shows it isn't a hardware problem. I'd reflash stock images and see where that leaves you. Worse case you use CM (oh my!) until we see a patch.
It sounds like it just has a corrupted stock image. Kernels typically cause the reboots but a bad app or system file can too.
If you flash stock back and you still have issues, try just flashing a modified stock kernel (stock rom/custom stock kernel). CM has its own kernel which might be why it was working better.
You also should do a complete wipe between stock and CM and AOSP and vice versa. It typically bootloops if you dirty flash one type of rom over another. Stock and AOSP are pretty much the same thing but some custom ROMs like CM have different structures that hose you.
Sent from my Nexus 7 using XDA Premium 4 mobile app

player911 said:
It sounds like it just has a corrupted stock image. Kernels typically cause the reboots but a bad app or system file can too.
If you flash stock back and you still have issues, try just flashing a modified stock kernel (stock rom/custom stock kernel). CM has its own kernel which might be why it was working better.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium

Rican Bx Bomba said:
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
I do not understand the hassle with Google.
I told them yesterday to get a new device, as wireless charging does not work. I talked max 10 minutes on the phone and I received an email 2 minutes after saying that I'll get a new device.
Yes, they will charge you "temporarily" for this, but you do not have to pay anything.
Anyway, it's me, I found it easy with Google.

Mine bootlooped today. Stock. No root or anything. I was forced to do a factory reset from recovery. Very troubling that this seems to be happening to a few people. There's a couple of threads over on android central of people having the same problem.
Sent from my Nexus 4 using XDA Premium 4 mobile app

I will admit this device is great without root but I prefer custom ROMs and titanium backup
Sent from my HTC One using XDA Premium 4 mobile app

Just sat here rebooting the n7 a few time and it happened. Held power and got it to re start the boot process and it loaded. As soon as I unlocked it I got an android process media force close
Sent from my Nexus 4 using XDA Premium 4 mobile app

Andro_pty said:
I do not understand the hassle with Google.
I told them yesterday to get a new device, as wireless charging does not work. I talked max 10 minutes on the phone and I received an email 2 minutes after saying that I'll get a new device.
Yes, they will charge you "temporarily" for this, but you do not have to pay anything.
Anyway, it's me, I found it easy with Google.
Click to expand...
Click to collapse
I rather not do the whole process of sending, receiving, ect. Call me lazy or whatever. Either way, it seems like my problem is solved, I'm once again happy.
Sent from my SPH-L710 using xda premium

Rican Bx Bomba said:
I flashed a stock image unroot, relocked. The process went without a hitch. Then I unlocked and rooted, flashed clean ROM, tried to see if I would get it to bootloop and it hasn't! Must've been a corrupt image.
I just want to thank you again, your advice saved me a lot of time and hassle with Google.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Super glad its worked. It worked for me. It worked for another guy. And worked for you. I think there is a bad rom image flashed on all of these that are causing lots of problems. The only fix is to clean slate and reflash the stock image, or move to custom ROMs.
Probably need to get someone to write a little app that just automates flashing the stock image again just for simplicity.
I'll probably create a new thread covering this.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

The stock images and the install script .bat file is simple enough.
Especially if you're rooted already. Since you already have the drivers installed on your computer.
Toolkits need to die a slow painful death.

You need root access a pen drive using an OTG cable, install app like titanium backup etc. Rooting doesn't mean custom rom or kernel
Sent from my Nexus 7 using xda app-developers app