Database Users

did i kill my epic?

i was running odin and download mode closed my phone now wont boot up or anything......
Euhmmmmm.... *poo*
just loaded and it has a pic of a cell a caution sign then a pc
*end heart-attack it decided it would work* i love the epic even more now....
PyRo
*please lock*

Take off the back, pull out the battery, pop battery back in and boot as normal into Download mode (holding down 1 as it powers up). Should work just fine.

bullet2300 said:
Take off the back, pull out the battery, pop battery back in and boot as normal into Download mode (holding down 1 as it powers up). Should work just fine.
Click to expand...
Click to collapse
I sort of had the same issue, but nothing I do will get the unit to power on. Plugging it in to the charger does not turn the charging light on. And no three button method is working. The screen stays black, no charging light. Suggestions?

Never mind, it did come back.

same problem
epic wont boot, charge, etc
please help

You're going to have to give us info if you want any help.
ROM, What you did right before it happened, etc.

RANT- Is it me or is it ever thread now somebody bricking their epic? Not trying to be a **** but it like people dont research at all. Me coming from an evo i will admit the epic is a whole other beast. But i atleast took the time to research everything before i rooted.
mmhertz26= Try getting the phone in download mode( hold power button with #1 key) at the same time. If that works use odin to flash back to stock with right files. Also check your download files size before you try to flash it.

903tex said:
RANT- Is it me or is it ever thread now somebody bricking their epic? Not trying to be a **** but it like people dont research at all. Me coming from an evo i will admit the epic is a whole other beast. But i atleast took the time to research everything before i rooted.
mmhertz26= Try getting the phone in download mode( hold power button with #1 key) at the same time. If that works use odin to flash back to stock with right files. Also check your download files size before you try to flash it.
Click to expand...
Click to collapse
The word brick is used too losely around here. Unless you've messed with the boot loader, and can no longer get into download mode your phone is NOT bricked.
Bricked means your phones is just a hunk of metal/plastic that's good for nothing but a paper weight.
Sent from my SPH-D700 using XDA Premium App

XtaC318 said:
The word brick is used too losely around here. Unless you've messed with the boot loader, and can no longer get into download mode your phone is NOT bricked.
Bricked means your phones is just a hunk of metal/plastic that's good for nothing but a paper weight.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Yeah we need a new word for soft bricking. Softing? Broft? Oops?

heathmcabee said:
Yeah we need a new word for soft bricking. Softing? Broft? Oops?
Click to expand...
Click to collapse
Nerf Brick? TV Brick? Sponged?
Do you BONSAI?

How about forget the term, and have people who are new to this actually research before jumping in.. but that's impossible because there's a lot of ignorant and stubborn people out there ^-^
Sent from my SPH-D700 using XDA Premium App

XtaC318 said:
How about forget the term, and have people who are new to this actually research before jumping in.. but that's impossible because there's a lot of ignorant and stubborn people out there ^-^
Click to expand...
Click to collapse
you think with all the disclaimers on each and every rom,root,theme,ect that people would understand the risks involved in modding whether its a ps3 xbox360 phone router anything but all logic seems to disappear.

kennyglass123 said:
Nerf Brick? TV Brick? Sponged?
Do you BONSAI?
Click to expand...
Click to collapse
lol
BTW its is thrown around how about saying in your thread title like stuck on a screen, errors in clockwork or other nice terms to help u more,
It is really hard to brick this thing believe me ive done it all, FCs, errors in clockwork, stuck on samsung screens boot loops and yesterday officially bricked!!!
The only reason it bricked is some charge card in a beta bonsai rom, but thats what tep is for.
And remeber if you can see something on your screen of your phone use odin or heimdell to go back to stock if you phone wont charge,gointo download mode or go on or go into recovery then its time to take it in and replace it.

Mnhertz26. Did you fix your epic too or is it another real brick?¿

I know what a brick phone is. Im just tired of people not knowing what to do asking questions that are already explanied and sticky on top of the page. Not researching will cause this problem until people realize that if you dont understand this then you need to read, read, read. I had a wm phone and if you flashed the wrong file...DONE. Atleast with the epic as long as it can get in download mode you should be fine.

brendan802 said:
Mnhertz26. Did you fix your epic too or is it another real brick?¿
Click to expand...
Click to collapse
Another real brick? So far there haven't been any Epic's that weren't recoverable.

Ouch I am so glad I did not run Bonsai on my phone yet I was waiting for i dunno what but dodged that issue.
For those who jacked thier phones but didnt brick persay make sure you have a charged battery before starting and if unabl to charge after the incident you can charge in an external charger to get back into dload mode to odin back to stock or CW flash a back-up
Peace

Stuck at "DUAL CORE TECHNOLOGY"

I unlocked, flashed rootboot, followed root procedure. All good, root working..
Come back 30 minutes later, hit power button and Xoom powers on and gets stuck at boot screen..
It appears to have crashed when I was away...
I have tried flashing stock boot img and unlocking again..
I can't get past the boot screen..
Someone please help.. I would appreciate it very much..
It's my brothers Xoom and I broke it, eek!

Can you boot up into bootloader (hold vol up and power during power up).

Also, try holding vol up + vol down + power until it turns off. then turn back on.

I'm having the same problem. I can get into the bootloader but where do I go from there?

You could try this:
http://forum.xda-developers.com/showthread.php?t=980803
Click to expand...
Click to collapse

Elementix said:
You could try this:
Click to expand...
Click to collapse
I'm downloading that as we speak. Thanks for the reply! I'll report back with my results

Did you just get the WiFi Model from Staples? I did myself. Things appears to be just a tad different. Stuck at the same screen.

Xaositek said:
Did you just get the WiFi Model from Staples? I did myself. Things appears to be just a tad different. Stuck at the same screen.
Click to expand...
Click to collapse
Yeah I did. I think you're right. There's probably stuff for radios that we don't have in the the Wifi only versions. Did you try flashing that Stock SBF?

n64kps said:
Yeah I did. I think you're right. There's probably stuff for radios that we don't have in the the Wifi only versions. Did you try flashing that Stock SBF?
Click to expand...
Click to collapse
Yeah you're the one that made the video of unboxing
I made a thread here - http://forum.xda-developers.com/showthread.php?t=1008780
Doesn't appear to be floating around yet. Gonna exchange mine tomorrow and then grab the boot.img BEFORE I screw it up.

Xaositek said:
Yeah you're the one that made the video of unboxing
I made a thread here - http://forum.xda-developers.com/showthread.php?t=1008780
Doesn't appear to be floating around yet. Gonna exchange mine tomorrow and then grab the boot.img BEFORE I screw it up.
Click to expand...
Click to collapse
Haha yeah that's me. Cool, I'll follow that thread too. Thanks for your help

Sounds like we're in the same boat. Can't get past the dual core screen now. Computer won't even recognize it anymore. looks like mine might be going back tomorrow too.

Just wait. There will probably be a working boot.img up shortly.
ke5hde said:
Sounds like we're in the same boat. Can't get past the dual core screen now. Computer won't even recognize it anymore. looks like mine might be going back tomorrow too.
Click to expand...
Click to collapse
Sent from my MB860 using XDA App

So I tried this
http://forum.xda-developers.com/showthread.php?t=980803
which is pretty clear it's for the Verizon Xoom since it has VZW in the file name but I thought something would be better than nothing.
Using RSD Lite v4.9, I still can't get anything. It's stuck at the boot screen (M logo and Dual Core Technology). I think I screwed the pooch on this one. I hope Staples still has some left when I go back tomorrow to exchange it :O

At this point I don't think a stock image is going to help. No way to push it back onto the xoom. It doesn't boot far enough for the computer to even recognize it.
Chris

Sure it does - you can boot into FastBoot by holding the Vol-Down button at boot.
Then you can do the fastboot flash boot boot.img with the stock boot.img file and you're golden.
Now if you ran the HRI39 restore (like n64kps) you will need the system.img and everything else.

I did already try to reboot into fastboot but the computer doesn't even know the xoom is plugged in.

Then you have other issues - I had no issues there. (I am on a Mac running ./fastboot-mac

Well Staples opens at 9 so I'm on my way to HOPEFULLY do an exchange.
Sent from my liberated DROIDX using XDA App

Yep!! I have an hour and a half before I can exchange mine.
After that we need to learn a few things - like pulling the system, boot, etc files BEFORE screwing them up LOL!

Ok. Returned it and they wouldn't let me have the replacement till tomorrow. Said she got yelled at for selling it last night. So 11am tomorrow I can pick it back up.
Sent from my liberated Droid X

Download mode?

Anyone else notice you can access download mode with power volume up or down . I forget. I got there a couple times. I never had a lg phone since the ally years ago and only kept that a week since it sucked. But otherwise I have only used download mode for Samsung to use Odin. Does lg have an Odin like application for there mobile devices. Thanks in advance.
Sent from my Nexus 4 using xda premium

I noticed that too but really don't see the point since we have factory images and a virtually unbrickable bootloader unless I'm wrong here.

Yeah but if it is like Samsung it would be cool to have an app like mobile Odin to flash with. Just never saw that option on any other phone than a samsung
Sent from my Nexus 4 using xda premium

Bit of a bump but I got into this mode, but for the life of me I can't work out how to get out of it.
Okay, wasn't holding the button down for long enough.

Hope this helps
Hold volume - (volume down) while pressing and holding power. Holding both of these gets you to the boot loader (or fast boot as some call it). This is the Nexus version of ODIN. From this menu you can use volume up or down to toggle different options (check the mode at the top of screen). The power button works like an ENTER button. If you have permanently flashed a custom recovery, this is how you access recovery during a boot loop or other catastrophe.
In this mode you can use ADB (Google it if you don't know what this is) to send files, flash files, boot a .img file or recovery, or even reset it to stock. This is by far way better than any other 3rd party method that I have encountered. It's what makes a nexus a nexus. However it is a little bit of a pain to get the Android SDK set up and running for some people.
I recommend every body that has this device to familiarize your self with what I am talking about.
If any of you need my help feel free to drop me a PM. Stay frosty!

parker09 said:
Bit of a bump but I got into this mode, but for the life of me I can't work out how to get out of it.
Okay, wasn't holding the button down for long enough.
Click to expand...
Click to collapse
How did you get into it? Or did you just get into the bootloader?

jasonpantuliano said:
Yeah but if it is like Samsung it would be cool to have an app like mobile Odin to flash with. Just never saw that option on any other phone than a samsung
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
odin was hellish. thank goodness its gone. fastboot is so, so much better and safer. fully documented aswell. in the s2 forum, that was my first cellphone, odin smashed countless of devices, and i mean smashed em dead. rooting my s2 after having paid such a sum of money made my heart beat like crazy. unlocking nexus via fastboot/adb, pfff, dont even care, i just know it'll work.

molesarecoming said:
odin was hellish. thank goodness its gone. fastboot is so, so much better and safer. fully documented aswell. in the s2 forum, that was my first cellphone, odin smashed countless of devices, and i mean smashed em dead. rooting my s2 after having paid such a sum of money made my heart beat like crazy. unlocking nexus via fastboot/adb, pfff, dont even care, i just know it'll work.
Click to expand...
Click to collapse
Seriously, and the number of bricks I saw from people hitting the wrong stuff in Odin was nothing short of amazing.
Sent from my Nexus 4 using Tapatalk 2

[Q] Huawei AT&T impuls 4G (U8800-51) - Flashed CM 7.2 0228 build but -

After what appears to be a successful flash of the CM 7.2 build from 02282013 all my phone will do is go to the at&t logo and sit there. Never completes the boot. I wiped data, factory reset and cache to no avail. I was on Froyo before flashing. I used CWM to flash. Never completes the bootup. I have to pull the battery to get it to shut down. I tried flashing twice with no luck.
I then tried to restore my CWM backup but it boots back into the recovery screen with the following errors:
Can't open /cache/recovery/log
Can't open /cache/recovery/log/last_log
Any ideas anybody?

pastorbob62 said:
After what appears to be a successful flash of the CM 7.2 build from 02282013 all my phone will do is go to the at&t logo and sit there. Never completes the boot. I wiped data, factory reset and cache to no avail. I was on Froyo before flashing. I used CWM to flash. Never completes the bootup. I have to pull the battery to get it to shut down. I tried flashing twice with no luck.
I then tried to restore my CWM backup but it boots back into the recovery screen with the following errors:
Can't open /cache/recovery/log
Can't open /cache/recovery/log/last_log
Any ideas anybody?
Click to expand...
Click to collapse
Are you on 2.2?
Sent from my SGH-T769 using Tapatalk 4 Beta

Somcom3X said:
Are you on 2.2?
Sent from my SGH-T769 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, I was on 2.2. I'm on nothing now. My last attempt totally bricked my phone and it won't even turn on.

pastorbob62 said:
Yes, I was on 2.2. I'm on nothing now. My last attempt totally bricked my phone and it won't even turn on.
Click to expand...
Click to collapse
1. Remove battery, plug in usb power cable. (means no battery in the phone)
2. Press power button, volume up, and volume down button. All three at the same time, and hold.
Did it turn on?

badiyee said:
1. Remove battery, plug in usb power cable. (means no battery in the phone)
2. Press power button, volume up, and volume down button. All three at the same time, and hold.
Did it turn on?
Click to expand...
Click to collapse
No. It does the same as when the battery is in. It vibrates as if it is going to turn on but the screen stays black and nothing else happens.

pastorbob62 said:
No. It does the same as when the battery is in. It vibrates as if it is going to turn on but the screen stays black and nothing else happens.
Click to expand...
Click to collapse
if what i read from other forums is correct, it sounds like you need a motherboard replacement.

badiyee said:
if what i read from other forums is correct, it sounds like you need a motherboard replacement.
Click to expand...
Click to collapse
That is what I figured to be the case as well. Unfortunately I am not able to locate one. Not sure if I would do that anyhow since it only cost me $140.00.

pastorbob62 said:
That is what I figured to be the case as well. Unfortunately I am not able to locate one. Not sure if I would do that anyhow since it only cost me $140.00.
Click to expand...
Click to collapse
Look on ebay. Buy one with a broken screen and replace it yourself.
Sent from my SAMSUNG-SGH-T769 using Tapatalk 4 Beta

Good suggestion
Somcom3X said:
Look on ebay. Buy one with a broken screen and replace it yourself.
Sent from my SAMSUNG-SGH-T769 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I've already tried that. Several times. Lots of new screens but no used phones that I can pick up for parts. I am leaning toward buying a new phone from my provider. Different model, Samsung Galaxy Exhilarate, better phone all around for only $150.00.
I'm done tweaking and modding my phones. It's okay for PC's and tablets but I think I'll stick to stock phones from now on. Lesson learned the hard way.

pastorbob62 said:
I've already tried that. Several times. Lots of new screens but no used phones that I can pick up for parts. I am leaning toward buying a new phone from my provider. Different model, Samsung Galaxy Exhilarate, better phone all around for only $150.00.
I'm done tweaking and modding my phones. It's okay for PC's and tablets but I think I'll stick to stock phones from now on. Lesson learned the hard way.
Click to expand...
Click to collapse
The exhilarate is a beautiful phone with good dev support. My blaze is compatible with the exhilarate.
Sent from my SGH-T769 using Tapatalk 4 Beta

Did I just Hard Brick my phone?

I've had my HTC 10 about a month. I was running NuSense Marshmallow by Santod040 and I had run the "NoRedText_aboot_firmware zip" to get rid ot the red text. Still, things were running well.
I then updated to the Nougat version of NuSense and the firmware and again things were running well. But the red text was back so I decided to get rid of the red text again. That is where things went wrong.
I didn't realize that there was a "new version" of the "NoRedText_aboot_firmware zip" and I tried to flash the same one.
I got an error message about it being the version prior to the update then the phone shut down. Now it wont power up.
Am I totally screwed? Is there a way to fix this? HELP... :crying:

Are you S-Off? Does your computer see it?
@dottat

acbrocksit said:
I've had my HTC 10 about a month. I was running NuSense Marshmallow by Santod040 and I had run the "NoRedText_aboot_firmware zip" to get rid ot the red text. Still, things were running well.
I then updated to the Nougat version of NuSense and the firmware and again things were running well. But the red text was back so I decided to get rid of the red text again. That is where things went wrong.
I didn't realize that there was a "new version" of the "NoRedText_aboot_firmware zip" and I tried to flash the same one.
I got an error message about it being the version prior to the update then the phone shut down. Now it wont power up.
Am I totally screwed? Is there a way to fix this? HELP... :crying:
Click to expand...
Click to collapse
Try charging with oem stock charger and cable overnight.
If it starts to take a charge, prepare a blank SDcard with
2PS6IMG_PERFUME_WL_M60_SENSE80GP_VZW_VERIZON_WWE_1.85.605.8_Radio_1.0.C010141xxxx.zip or similar. Rename it 2PS6IMG.zip with only one .zip at end. Try and boot with volume down and power.
With any luck, you'll get enough charge on it to allow you to do this software install.

Hard Brick
I did ask Santod and he said it is hard bricked. I flashed the wrong aboot image and now the phone does nothing, no power, no response from any combination of button presses, the computer does not see it. I don't know of anything else that might work.
I'm going to try to see if HTC can fix it, if not then I may use it for parts because the phone looks great. So I may try to get a beat up phone with a busted screen and swap out the guts.

Pretty sure this is what I've been talking about folks.
Stop messing with custom aboots.
Sent from my HTC6545LVW using Tapatalk

Bricked / aboot
dottat said:
Pretty sure this is what I've been talking about folks.
Stop messing with custom aboots.
Sent from my HTC6545LVW using Tapatalk
Click to expand...
Click to collapse
Yeah, I read your info and warning about it after the fact.

acbrocksit said:
Yeah, I read your info and warning about it after the fact.
Click to expand...
Click to collapse
Yep...Moreso posting for anyone who sees this as further warning.
Sent from my HTC6545LVW using Tapatalk

I did the same thing trying to downgrade my firmware. Same exact thing happened. So I got it replaced by Verizon with the warranty, and they accepted it, I just said that I was trying to update it and that it won't turn on now. They haven't noticed that I did it, and I doubt they'll be able to get it to boot without flashing complete stock.

Spinkness said:
I did the same thing trying to downgrade my firmware. Same exact thing happened. So I got it replaced by Verizon with the warranty, and they accepted it, I just said that I was trying to update it and that it won't turn on now. They haven't noticed that I did it, and I doubt they'll be able to get it to boot without flashing complete stock.
Click to expand...
Click to collapse
So Verizon accepted your bricked phone? No issues?
Sent from my HTC6525LVW using Tapatalk

I sent mine to HTC to see what they would charge me (repair center in USA). I didn't say what happened, just that it wouldn't turn on. I don't think that they looked very close at it. They just sent me a refurbished phone, no charge.
But I won't mess with the red text again. It's really not worth the risk.

acbrocksit said:
I sent mine to HTC to see what they would charge me (repair center in USA). I didn't say what happened, just that it wouldn't turn on. I don't think that they looked very close at it. They just sent me a refurbished phone, no charge.
But I won't mess with the red text again. It's really not worth the risk.
Click to expand...
Click to collapse
They didn't even ask why Verizon wouldn't warranty it?
Sent from my m8wl using Tapatalk

Evocm7 said:
So Verizon accepted your bricked phone? No issues?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
Sorry about the delayed response!!!
Yes they accepted it with no issues. Been a few months now and still nothing bad from them. The people at Verizon don't even have the knowledge to revive a hard bricked phone. At least not the people I've ever been able to speak to. But either way, it's not worth the hassle for them. They'll just part it, toss it, or send it back to HTC, where they will either part it or toss it. So yeah, no worries about sending Verizon a rooted/s-offed/bootloader unlocked phone. I've done it more times than I can count, and they've never found out.

Spinkness said:
Sorry about the delayed response!!!
Yes they accepted it with no issues. Been a few months now and still nothing bad from them. The people at Verizon don't even have the knowledge to revive a hard bricked phone. At least not the people I've ever been able to speak to. But either way, it's not worth the hassle for them. They'll just part it, toss it, or send it back to HTC, where they will either part it or toss it. So yeah, no worries about sending Verizon a rooted/s-offed/bootloader unlocked phone. I've done it more times than I can count, and they've never found out.
Click to expand...
Click to collapse
No problem. I called Verizon and even though it was dead, they were still able to communicate with the phone while I was talking to them on another phone. The power led was flashing red and then she said the phone wasn't under warranty because there was custom software. I ended up sending it to HTC where they sent me a refurb with a bad mic then the second one I have now is fine. So after a month and $40 worth of shipping charges, I have a working 10 again. I honestly don't think HTC cares about rooted phones and the time it would take to diagnose what actually happened in our down grade brick wouldn't be worth it for them.
Sent from my HTC6545LVW using Tapatalk

If it's under warranty, make a claim. Verizon will tell you to ship it back to another location where all they do is refurbish the phones for subsequent resale. You will likely get a replacement refurb. The refurbisher has absolutely no clue what you have done; they handle these things in bulk and I have not once ever heard of a phone under warranty being "refused" because an end user did something stupid. Which, as @dottat says, is what flashing an edited aboot to get rid of the red text is, by the way. Stupid.
I *like* the red-text, frankly. It reminds me whether I'm running pure stock boot and recovery or not while I'm flashing updates, etc.