I tried to turn it on and all I get is a vertical line that fades from gray to blue to red. It buzzes like it's coming on and then... nothing. Anyone else had this problem?
edit: I also can't get into the recovery menu
First. What did you do or try to do to it?
Sent from my PG86100 using XDA Premium App
Sorry, I'm having a borderline panic attack...
I wasn't doing anything to it at the time - It had gone dead and I plugged it in to charge when I got home. After maybe 10 min I tried to power it up and I got the weird vertical line on the right side of the screen. I have tried battery pulls, I tried charging it fully then turning it on. I can't boot into the hboot menu. It is 100% stock, s-on. I haven't even tried temp-root on it. I'm trying to run an RUU but it keeps giving a usb error
don't try fixing this yourself! Take it back to an authorized Sprint repair store ASAP.
First of all relax, most bricks are reversible - but indeed some are not and hence you are panicking. Well if you followed the instructions as mentioned in the thread 99.9% things should have not gone wrong. But now that they have - you either need to figure out at what step did they go wrong - and what step before that step you did something wrong.
If nothing works - then run to your operator.
I took it in to Sprint. The rep was literally outraged that my phone was broke. Said it was ridiculous that I should have to come down there after only having my phone 2 weeks. Gave me a brand new one in the box, no questions asked. FYI - they said they hadn't had any other reports of similar issues and hadn't seen it before. It was just a white line down the right side of the screen and wouldn't do anything else.
Glad to hear Sprint is keeping the a good face...especially in this locked hboot era...just try not to break this one
Good to know that, and good on Sprint's part as well. Please read well before doing something tothis one.
Seriously. I didn't do anything to it. It is bone stock. I didn't accept a new OTA. I didn't drop it, get it wet, or try to run unrEVOked. I haven't even tried to run frEvo. It wasn't OC'd, UV'd, STFU'd or ROFLMAO'd. It seriously just borked itself. Or it was the pornography. I guess it could have been the porn...
austontatious said:
Seriously. I didn't do anything to it. It is bone stock. I didn't accept a new OTA. I didn't drop it, get it wet, or try to run unrEVOked. I haven't even tried to run frEvo. It wasn't OC'd, UV'd, STFU'd or ROFLMAO'd. It seriously just borked itself. Or it was the pornography. I guess it could have been the porn...
Click to expand...
Click to collapse
Anyways now that it's okay - cool down and read around before messing with your EVO
austontatious said:
Seriously. I didn't do anything to it. It is bone stock. I didn't accept a new OTA. I didn't drop it, get it wet, or try to run unrEVOked. I haven't even tried to run frEvo. It wasn't OC'd, UV'd, STFU'd or ROFLMAO'd. It seriously just borked itself. Or it was the pornography. I guess it could have been the porn...
Click to expand...
Click to collapse
Too much 3d porn is never good for any phone
You know, it is possible for the OP to be telling you guys the truth about not doing anything to his phone, and his phone just had some kinda software/hardware defect, from running the battery too low..
Sent from my PG86100 using XDA Premium App
Related
I need to get this phone in a bootloop.
How can I do it?
I need to return the phone to the Sprint store because of light leakage but they said 'that's not sufficient reason for a return' so I need to bootloop it. Help me out guys, please?
Lawl
shot from your moms V$GINA IN 3D
I like this thread already. Have you tried flashing a rom for another phone? Say the Evo 4G?
readingkeeper said:
I like this thread already. I have you tried flashing a rom for another phone? Say the Evo 4G?
Click to expand...
Click to collapse
^^^ That should do it.
Have fin finding one without it I would say over 90% have it
If you don't have an Evo3d well ...
just flash multiple roms without clearing caches and dalvik.... should bootloop for ya
That's bull. Tell them its a hardware defect and means the screen is improperly sealed.
That's a fine reason to take it back.
Sent from my Xoom using XDA Premium App
I also have this problem that when I go into teamwin recovery my search button has a dim light on it while all the other buttons are not lit on. I'm talking about the capacitive buttons at the bottom.
Do you think If I show a sprint employee that screen it will raise a flag or are they too stupid to know?
Also, I was thinking of just flashing a ROM and midway through the 1st boot I just battery pull. Does that sound like it would loop me?
iCaptivate said:
I also have this problem that when I go into teamwin recovery my search button has a dim light on it while all the other buttons are not lit on. I'm talking about the capacitive buttons at the bottom.
Do you think If I show a sprint employee that screen it will raise a flag or are they too stupid to know?
Also, I was thinking of just flashing a ROM and midway through the 1st boot I just battery pull. Does that sound like it would loop me?
Click to expand...
Click to collapse
Battery pull while flashing radios that should brick it
My rice krispies told me what to say
dased14 said:
Battery pull while flashing radios that should brick it
My rice krispies told me what to say
Click to expand...
Click to collapse
Bricking it as in it won't turn on?
That's a no no.
I just need it for where I can't get the use Sense 3.0 but I can still turn it on.
Look men just take ur micro SD card and **** up the SD slot wit a knife(the inside so they won't notice).
Sent from my PG86100 using XDA Premium App
Your just gonna get one with worse or real problems .
If you don't have an Evo3d well ...
This has to be the funniest thread so far for the day lmao
If you don't have an Evo3d well you don't have an Evo3d
jgalan14 said:
This has to be the funniest thread so far for the day lmao
If you don't have an Evo3d well you don't have an Evo3d
Click to expand...
Click to collapse
Thief ! I don't care if you told me , I ain't even mad though
If you don't have an Evo3d well ...
I have seen many threads asking how to get OUT of a bootloop, but NEVER have I seen one trying to get INTO a bootloop. lmao. So you're going to get yourself into a bootloop, and take it in rooted, with S-off and all? I wonder how well that will go over. They'll be like,"oh look, it has a software problem because it's bootlooping. Oh look at that, this thing has S-off and super user installed, guess no software warranty on this thing.". The reason I say you'd be taking it in with S-off and super user is because you'd need that to flash something to get you stuck in a bootloop....and if you unrooted it and turned it back to s on before you brought it in, that would mean you had to run an RUU, which would at the same time fix the bootloops! LOL Just demand they replace it for the light leakage, rather than intentionally trying to make it bootloop. That is the funniest **** I've seen all day!
mcmikecruz1 said:
Thief ! I don't care if you told me , I ain't even mad though
If you don't have an Evo3d well ...
Click to expand...
Click to collapse
Lmao makes it even better lol don't trip august is here time to changed my sig lol
If you don't have an Evo3d well you don't have an Evo3d
iCaptivate said:
I also have this problem that when I go into teamwin recovery my search button has a dim light on it while all the other buttons are not lit on. I'm talking about the capacitive buttons at the bottom.
Do you think If I show a sprint employee that screen it will raise a flag or are they too stupid to know?
Also, I was thinking of just flashing a ROM and midway through the 1st boot I just battery pull. Does that sound like it would loop me?
Click to expand...
Click to collapse
That light over your search button is light leakage. The other buttons are supposed to be off while you're in recovery. Just deal with it. I have that problem and many other people do as well.
I don't know why you're so worried about light leakage. It really isn't a big deal. There is no point in taking your phone back for this. You're just screwing the rest of us in the long run.
It's not just light leakage. Ever since I took the OTA I get random reboots, even tho I'm using SupraROM. I'm within my 30 days, they have to give me a new one.i just tell them that doing the OTA the battery died.
Take a leak on your phone. Lightly.
My wife's EVO 3D, completely stock, S-ON, never installed the OTA update.
The phone was on and she had it in her pocket and felt it vibrate, when she looked at the phone, it was booting up but it appeared to be stuck in a boot loop. She said she saw it rebooting itself (just the initial sprint splash screen) several times before she pulled the battery.
She re-installed the battery, but the phone wouldn't turn on. So she left it alone and brought it home.
The reboot loop was a bit concerning to me, but the phone not turning on sounds like a drained battery. So, I put it on the charger (AC power adapter) for about an hour (orange led is lit).
When I turn it on, I see the boot screen (HTC -> Sprint -> 3D -> Sprint) and then the screen goes black. The soft key LEDs are stuck on the entire time. but nothing happens. I let it sit like that for 10 minutes and it never boots. I've tried several times with the same result.
I can get into hboot (Volume-down + Power)... Almost feels like a corrupt stock ROM?? I can check the CRC, but I don't know the correct values... And no one has tried to root or flash it. I asked if she might have accidentally started the OTA update, but she says not likely...
I've searched the forums here and various others, and it seems all not-booting and endless-boot-loop issues are all due to people trying to root or flash an image.
So.... I don't have a whole lot of experience with Android... What's the next step before attempting a factory reset or bringing it back to Sprint?
Thanks!
EDIT: Typos
Wow, this is very weird. My advice is if you still have 30 day return use it or insurance, bring it to sprint. If not both call HTC and complain but I doubt they cover software issues, idk I might be wrong. Why fix it? Get a brand new one, you paid for it to be working, not broken.
Sent from my PG86100 using XDA App
You said you can do a factory reset? I'd say do that first before trying anything else. If it works, then the only thing she has to worry about is taking 30 minutes of her time to re-set up her phone.
Sent from my PG86100 using XDA App
^^^You can do that or you can take it back to sprint store or a repair spot and possibly get a new one. Custom firmware would knock those bugs right out, so maybe its a sign. Your wifes' phone is ready to be rooted. Hey, I'm just saying...
My "DU4L C0R3 SH00T3R" shot you down in 3D! Screw Tupac. "A,O,S,P BACK!" >_
Try removing the SD card and see if it will boot up properly. I had that happen to me once (boot loop and all). Phone would boot fine without the SD card.
I ended up having to format the SD card (connected to my PC with a card reader). That solved the problem.
This happened to my phone once. A factory reset from the bootloader fixes it good as new. It's been like a month and a half since then and I have had no problems since then.
boom!! from my shooter
Quick update -- phone finished charging... Green LED now... and still same behavior... Thanks for all the replies guys!
iModMM said:
Wow, this is very weird. My advice is if you still have 30 day return use it or insurance, bring it to sprint. If not both call HTC and complain but I doubt they cover software issues, idk I might be wrong. Why fix it? Get a brand new one, you paid for it to be working, not broken.
Click to expand...
Click to collapse
I want to see if I can get her a working phone tonight instead of sending her off to the Sprint store tomorrow, waste a bunch of time, and having them just do a factory reset anyhow.
DDiaz007 said:
You said you can do a factory reset? I'd say do that first before trying anything else. If it works, then the only thing she has to worry about is taking 30 minutes of her time to re-set up her phone.
Click to expand...
Click to collapse
Yeah... This was my first instinct, but just wanted a sanity check here on the forums first...
r0cky0790 said:
^^^You can do that or you can take it back to sprint store or a repair spot and possibly get a new one. Or maybe this is a sign. Custom firmware would knock those bugs right out, so maybe its a sign. Your wifes' phone is ready to be rooted. Hey, I'm just saying...
Click to expand...
Click to collapse
I know! I had her not install the OTA because I had intended to root the phone... I'm so tempted to just root the thing and flash something nice, but I don't want to risk it in case it is a more serious problem and we need Sprint to replace it... Maybe if the factory reset fixes it for a couple of weeks, then I'll consider again...
mvansomeren said:
Try removing the SD card and see if it will boot up properly. I had that happen to me once (boot loop and all). Phone would boot fine without the SD card.
I ended up having to format the SD card (connected to my PC with a card reader). That solved the problem.
Click to expand...
Click to collapse
Sorry I forgot to mention it in the original post, but did try re-seating the SD card and without the SD card... both exhibit the same behavior.
DJ1994 said:
This happened to my phone once. A factory reset from the bootloader fixes it good as new. It's been like a month and a half since then and I have had no problems since then.
Click to expand...
Click to collapse
This is what I wanted to hear.... Someone else with the exact same issue and a fix... I think I'll factory reset it now... I warned my wife that she will lose high scores and text messages. She didn't care about the texts, but was sad about losing her progress in Angry Birds! lol.
---------- Post added at 10:57 PM ---------- Previous post was at 10:34 PM ----------
Okay.. Factory reset went well... Restoring settings and apps now... Thanks for the help guys!
To get rod of those problems you should take the ota's if you haven't rooted it yer then no reason in leaving inferior firmware on the device
Sent from my PG86100 using Tapatalk
ktrotter11 said:
To get rod of those problems you should take the ota's if you haven't rooted it yer then no reason in leaving inferior firmware on the device
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Noooo, he can root and solve the problem that way. Just visit Haus's stock ROM thread, and he'll have everything there for you. A stock rooted ROM with all the OTA firmware fixes available for download. Just root first.
This is assuming you live in the U.S, and own the Sprint Evo 3D (CDMA).
ktrotter11 said:
To get rod of those problems you should take the ota's if you haven't rooted it yer then no reason in leaving inferior firmware on the device
Click to expand...
Click to collapse
Is this kind of failure a known issue with the original stock firmware? I'm not going to take the OTA to keep my options open for rooting in the near future.
DDiaz007 said:
Noooo, he can root and solve the problem that way. Just visit Haus's stock ROM thread, and he'll have everything there for you. A stock rooted ROM with all the OTA firmware fixes available for download. Just root first.
This is assuming you live in the U.S, and own the Sprint Evo 3D (CDMA).
Click to expand...
Click to collapse
Yeah.. I know not to take the OTA... I'm going to root it eventually.
I looked through the complete list of ROMs and didn't see Haus mentioned anywhere... Am I missing something?
Also, is there a common consensus on the top two or three Sense ROMs for the EVO 3D?
ken830 said:
Is this kind of failure a known issue with the original stock firmware? I'm not going to take the OTA to keep my options open for rooting in the near future.
Yeah.. I know not to take the OTA... I'm going to root it eventually.
I looked through the complete list of ROMs and didn't see Haus mentioned anywhere... Am I missing something?
Also, is there a common consensus on the top two or three Sense ROMs for the EVO 3D?
Click to expand...
Click to collapse
Here http://forum.xda-developers.com/showthread.php?t=1223979
Sent from my PG86100 using XDA App
iModMM said:
Wow, this is very weird. My advice is if you still have 30 day return use it or insurance, bring it to sprint. If not both call HTC and complain but I doubt they cover software issues, idk I might be wrong. Why fix it? Get a brand new one, you paid for it to be working, not broken.
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
*14 days if bought on the 16th.
Try these things:
- Take batter off and hold power button down for like 10 secs, put battery back in.
- Download the RUU from a thread in the development section and flash it (it will replace everything back to stock).
That SHOULD fix it, if its a software issue, if it doesn't, or it still continues to act funky, just take it back to Sprint and demand a new one since you're within your 14/30 days.
Make sprint replace it the phone will be doing the so thing after resting it or trying any other trick its a software issue belive me I had 5 replacements because of software issues
Sent from my PG86100 using xda premium
Guys my note seems to be in the most dreadful state possible. It wont turn on, I can't put it in recovery, when I connect it to the computer I can hear a sound signalling it does recognize something, but adb cant find the device (seems like it turns off).
This happened after trying to put the cwm beta4 recovery.img , nobody except me is responsible, I was trying to put flash the image, after running the command however it dint seem to me it made any difference after trying to boot to recovery so, I tried running the command again, except this time, it gave me an error which said it ran out of space or disk space, I tried restarting and it wont turn on.
Any and all help is appreciated.
Please move this to the correct forum.
This forum is for development
Sent from my SAMSUNG-SGH-I717 using XDA
Return it and they'll give you a new one. They cant tell you bricked if it won't turn on.
G~Note "nuff said"
alperin1 said:
Please move this to the correct forum.
Sent from my SAMSUNG-SGH-I717 using XDA
Click to expand...
Click to collapse
I'm sorry I wasn't aware that this wasnt the right place.
N3RD420 said:
Return it and they'll give you a new one. They cant tell you bricked if it won't turn on.
G~Note "nuff said"
Click to expand...
Click to collapse
Agreed, except I want to try and see if it can be recovered, else I'll get it switched.
Did u try to go to download mode by holding down. Then wait 15 sec press up even if it doesnt have anything on screen and see if odin sees it?
Sent from my SGH-I717R using XDA App
u921333 said:
Did u try to go to download mode by holding down. Then wait 15 sec press up even if it doesnt have anything on screen and see if odin sees it?
Sent from my SGH-I717R using XDA App
Click to expand...
Click to collapse
Okay just noticed this, in the device manager it now says QHUSB_DLOAD, I'm guessing this is some form of download state, I have odin open, how do I know if its recognizing it?
It would show a yellow square with a com port.... But i think that error is very bad one of our devs in skyrocket got it and it was return phone or jtag service online.
Sent from my SGH-I717R using XDA App
you might have had a typo in your last flash...
if you typed mmcblk0p2 instead of mmcblk0p22, then it would explain the out of space, and possibly also the boot error...
u921333 said:
It would show a yellow square with a com port.... But i think that error is very bad one of our devs in skyrocket got it and it was return phone or jtag service online.
Sent from my SGH-I717R using XDA App
Click to expand...
Click to collapse
Odin doesn't show anything, I mean I doesn't show the yellow exclamation mark.
braway said:
you might have had a typo in your last flash...
if you typed mmcblk0p2 instead of mmcblk0p22, then it would explain the out of space, and possibly also the boot error...
Click to expand...
Click to collapse
Very likely thats what I did, is there anyway out?
i_max2k2 said:
Very likely thats what I did, is there anyway out?
Click to expand...
Click to collapse
probably not, or only with lots of effort
returning it is probably the fastest
I do understand, but since I'm a total noob on android, .and that nothing else could possible go any wrong, I would sure like to try.
drop 5 bucks on a jig
http://www.amazon.com/gp/product/B005UUCT0Y/ref=oh_o00_s00_i00_details
or similar.
this wont reset the counter like on certain devices but it will put the sgh-i717 at&t note into download mode just by plugging it in
then flash back to stock with odin. all of the info to do that is located in this forum
edit.. alot of these guys are right though, if it doesnt react to being plugged in or turned on no matter what, nobody in the at&t store will figure it out, they will mark it defective and give you a new one
Honestly......best idea.... return it. I'd actually suggest leaving it alone, on the off chance you got Odin to recognize it, and maybe halfway fixed the Note, it might then look to whomever you return it to that you broke it somehow. Basically the fact it won't turn on at all is to your benefit at this point.
My phone will eat your Apple!
brittoking said:
Honestly......best idea.... return it. I'd actually suggest leaving it alone, on the off chance you got Odin to recognize it, and maybe halfway fixed the Note, it might then look to whomever you return it to that you broke it somehow. Basically the fact it won't turn on at all is to your benefit at this point.
My phone will eat your Apple!
Click to expand...
Click to collapse
I agree. Return. Been there twice with an infuse and skyrocket. No questions asked...swap out. I always say I'm never getting involved in Modding my phone after an incident like that. Am I the only who says that?
Sent from my SAMSUNG-SGH-I717 using xda premium
brittoking said:
Honestly......best idea.... return it. I'd actually suggest leaving it alone, on the off chance you got Odin to recognize it, and maybe halfway fixed the Note, it might then look to whomever you return it to that you broke it somehow. Basically the fact it won't turn on at all is to your benefit at this point.
My phone will eat your Apple!
Click to expand...
Click to collapse
I kind of just thought about that, I'll leave it as is, and get it swapped.
ryanbmw51 said:
I agree. Return. Been there twice with an infuse and skyrocket. No questions asked...swap out. I always say I'm never getting involved in Modding my phone after an incident like that. Am I the only who says that?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Yep will do this.
ryanbmw51 said:
I always say I'm never getting involved in Modding my phone after an incident like that. Am I the only who says that?
Click to expand...
Click to collapse
I, for one, couldn't wait to tear into my new $300 gem
As for the brick, i concur, returning it at this point would be best. I hate using dd to flash things, one typo can screw up the entire device.
if it turns on at all... you may risk getting it found to be modded. just sayin.
if i were you. Id find an old ac adapter cut the wires and seperate. then zap the prongs where the battery connects. in my experience, old laptop chargers work the best. be sure to cut the end off of the cord that plugs into the laptop. the brick will protect you from fatal or even harmful shock so dont worry.
just my .02
I agree. Mine was rooted the day I got it.
If you do decide to root the replacement, reading is your friend. Read, read again, and read it a third time. Then don't be afraid to read it more if necessary, and a you're doing the steps.
Well on the way to my fairytale!
braway said:
probably not, or only with lots of effort
returning it is probably the fastest
Click to expand...
Click to collapse
It happened as you had said missed a 2
ashies7 said:
I agree. Mine was rooted the day I got it.
If you do decide to root the replacement, reading is your friend. Read, read again, and read it a third time. Then don't be afraid to read it more if necessary, and a you're doing the steps.
Well on the way to my fairytale!
Click to expand...
Click to collapse
I had it rooted, it was while trying to install cwm, I did read it a few times, perhaps needs more reading, I had tinkered with iphones quite a bit, but I never had a bricked device ever in like 4 years, I never thought it could goto a state where the only real way to bring it back would it be to connect to a jtag device.
So, yesterday morning this all went down. My Rezound has been nothing but an expensive paperweight. I am not new to the rooting game so save the nonconstructive comments.
Early Monday morning I felt the need to change things up a bit so I wanted to flash the latest CleanRom 3.7 to check it out (coming from BAMF v.09). I backed up all my apps & data and continued to make a nandroid backup (with Amon_Ra 3.14). After that, I completed the necessary wipes (including boot because Scott packages his roms with the kernel) in recovery and then flashed CleanRom 3.7 (MD5 sum matched) then booted into bootloader to flash the kernel. Everything went perfect with that.
After the phone booted I realized how low on battery I was on but connected to Wi-Fi during the initial start-up on the new rom. I got all my accounts and data synced/restored and was getting ready to knock out. I set my alarm, placed the phone on the wall charger and confirmed it was charging by the orange light around 3am.
I woke up yesterday morning around 7:30am and realize I'm running late. I pick up my phone to see if the time is correct and I get nothing but a black screen. Pulled the battery...nothing...plugged in the phone without the battery..then plugged in the battery...nothing. On my 45 minute commute to work I removed the battery and let the phone sit (hoping some magic would happen lol) and nothing changed.
When I made it to my office, I plugged the phone in to see if it would accept a charge and 2 hours later nothing. I have the 3.7v battery and have had no indications of a bad battery (short life, warm, etc.). Due to the circumstances, I was left with no choice but to go to the local VZW and order a replacement.
The guy at the Verizon store plugged my phone in the wall charger and saw it was not accepting a charge. Swapped the battery with his own personal Rezound and mine worked in his, however, his fully-charged battery would not work in mine. Narrowed it down to the phone itself which blows. I thought at worst it would be the battery.
I am really curious how/why this all went down of all times when I wasn't doing anything to my phone. You guys/gals have any idea?
Marcismo55 said:
and continued to make a nandroid backup.
Click to expand...
Click to collapse
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
mike.s said:
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
Click to expand...
Click to collapse
My bad..I forgot to mention I have been running Amon_Ra from the start. I've never ran CWM on my Rezound and I did run across some threads regarding the charging issues associated with CWM.
Thanks though!
Did you check the pins on the inside of the phone for the battery? Any scratches or rust?
This is exactly why I stay on GB and GB Kernels.
I experienced non-charging on two different ICS ROMs at seemigly random times. Sometimes just on the 3.8v. Once on the 3.7v. Going back to GB, then back to ICS temporarily resolved the issue.
One of the 10 reasons I tell people not to go ICS with this phone yet.
Get back on GB and your phone may well be just fine.
That's where my money is.
Ineffabilis with the 2.011.xxx kernel and radio is winning still.
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
mpalatsi said:
Did you check the pins on the inside of the phone for the battery? Any scratches or rust?
Click to expand...
Click to collapse
Yes. All the contacts were intact and free of dirt/debris.
pkopalek said:
This is exactly why I stay on GB and GB Kernels.
I experienced non-charging on two different ICS ROMs at seemigly random times. Sometimes just on the 3.8v. Once on the 3.7v. Going back to GB, then back to ICS temporarily resolved the issue.
One of the 10 reasons I tell people not to go ICS with this phone yet.
Get back on GB and your phone may well be just fine.
That's where my money is.
Ineffabilis with the 2.011.xxx kernel and radio is winning still.
Click to expand...
Click to collapse
I would give GB a try, however, the phone does not do anything at all.
I also don't quite follow your reasoning behind not running ICS roms as this appears to be more of a hardware related issue itself. However, that is fine if it works for you.
Dstu03 said:
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
More than half of all the roms out there are from ports/leaks. Please explain.
You put the sim card in backwards? I fried one rezound doing this already.
Sent from my ADR6425LVW using XDA
Did you try to connect via USB to your computer and type in adb reboot? I have heard some success with that. But it was for the CWM problem. It might be worth a shot.
nosympathy said:
You put the sim card in backwards? I fried one rezound doing this already.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
Actually I didn't even take the SIM out. Maybe I should have given that a try.
EmerikL said:
Did you try to connect via USB to your computer and type in adb reboot? I have heard some success with that. But it was for the CWM problem. It might be worth a shot.
Click to expand...
Click to collapse
Thanks man...I tried that too and ADB was unable to see the device.
VZW told me my replacement won't be here until tomorrow...weak.
dude i started a topic on this months ago..i had a guy come in who had the SAME problem..except his somewhat powered on with another battery.
i put one in, went into bootloader, tried to boot to recovery, but it just came up as a black screen...so i reboot it, wiped it, but it wouldn't even wipe, it just went to that same black screen. his battery had died overnihgt, and he didn't charge it, and then this happened..it just wouldn't turn on, the orange light wouldn't come on showing it was charigng...
i couldn't fix it, so we had to get him a replacement that really sucks that i'm still hearing it out there...
sorry if i didn't read, but what rom/kernel were you running? this guy swears it was stock and he never heard of rooting, so who knows if he was lying or not
mike.s said:
Were you using CWM recovery? You don't say. There are reported battery charging issues with that on the Rezound. Search around. You should use Amon Ra.
Click to expand...
Click to collapse
That's only for charging when you're booted into recovery if I'm not mistaken...
---------- Post added at 07:10 PM ---------- Previous post was at 07:08 PM ----------
Dstu03 said:
If you flash leaks this is what happens. Live and learn this phone does not have soff so mistakes can cost you a phone
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
If flashing killed it, it would have never booted back up...
Marcismo55 said:
Actually I didn't even take the SIM out. Maybe I should have given that a try.
Thanks man...I tried that too and ADB was unable to see the device.
VZW told me my replacement won't be here until tomorrow...weak.
Click to expand...
Click to collapse
In my case when the Verizon rep gave me the phone he put the sim in and put it in backwards. To be fair, it does go in "backwards" to every other android phone I have owned haha.
Sent from my ADR6425LVW using XDA
mjones73 said:
That's only for charging when you're booted into recovery if I'm not mistaken...
Click to expand...
Click to collapse
It may depend on how you're charging. The charging process requires some intelligent oversight - if you power off the phone, and connect a charger, the process is controlled by code loaded from somewhere. I think that code is in, or loaded by, the recovery. That would tend to explain things like this, this, this, and this.
jayochs said:
dude i started a topic on this months ago..i had a guy come in who had the SAME problem..except his somewhat powered on with another battery.
i put one in, went into bootloader, tried to boot to recovery, but it just came up as a black screen...so i reboot it, wiped it, but it wouldn't even wipe, it just went to that same black screen. his battery had died overnihgt, and he didn't charge it, and then this happened..it just wouldn't turn on, the orange light wouldn't come on showing it was charigng...
i couldn't fix it, so we had to get him a replacement that really sucks that i'm still hearing it out there...
sorry if i didn't read, but what rom/kernel were you running? this guy swears it was stock and he never heard of rooting, so who knows if he was lying or not
Click to expand...
Click to collapse
Yeah dude I had just flashed CleanRom 3.7 and the stock kernel that came with it.
It was completely unresponsive to anything but I didn't think of booting into recovery. My battery had a 30% charge on it when the VZW rep put it in his Rezound and powered it on. It was just really weird.
Marcismo55 said:
Yeah dude I had just flashed CleanRom 3.7 and the stock kernel that came with it.
It was completely unresponsive to anything but I didn't think of booting into recovery. My battery had a 30% charge on it when the VZW rep put it in his Rezound and powered it on. It was just really weird.
Click to expand...
Click to collapse
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
scrosler said:
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
Click to expand...
Click to collapse
^This. Even if it is new hardware there can be defects. **** happens!
Marcismo55 said:
I would give GB a try, however, the phone does not do anything at all.
I also don't quite follow your reasoning behind not running ICS roms as this appears to be more of a hardware related issue itself. However, that is fine if it works for you.
Click to expand...
Click to collapse
I assessed your OP as related to a phone not charging.
I see what you mean, now. My points were in the case of non-charing, or failure to charge (and a phone going dead on the charger) which aren't things I've seen on any stock-based ROM, but very much so on ICS ROM's (and Kernels, as such).
I bid you good luck on your replacement hardware. Stuff happens!
scrosler said:
I see this happen a few times. I can assure any one reading this it was coincidental that it happened after the ROM was flashed. If not there would be about 5,000 bricks out there with my name on it.
I think you had some bad luck man. It happens. My boss at work just ordered a brand new 1TB HD. Hooked it all up in his new rig and it would be seen by BIOS. Had to RMA it back to new egg.
I just put together a killer i7 system. Insane specs, water cooler, the whole nine yards. It had a 2GB GeForce Ti GTX 560 OC in it... Died within 2 weeks. That was a $300 card. Within the first couple days it started hard locking my computer. This was all on a fresh build mind you. Then after a week and a half the screen would lock and turn pink... Thats when I was positive it was video.
Replaced it and all was well.
Im just trying to illustrate that hardware failure can happen at the least opportune times. In other words, **** happens.
Click to expand...
Click to collapse
I understand Scott. I am in now way shape or form saying flashing your ROM was the reasoning behind all this as I have flashed numerous times before this and had no issues. Also, considering I am one of the very few this has happened to, i think its pretty obvious this was a hardware failure. I
I'll be running your roms soon enough
Thanks to everyone providing insight on this situation. I'll be back at it again very soon!
So today as I was preparing to flash the latest AOKP rom at 90% battery, I accidentally hit reboot to bootloader instead of recovery. No problem, i hit reboot. The screen turned black and a minute later it was still black, so I removed the battery. Nothing turned it on, couldn't access the bootloader and the charging light wouldn't even go on.
That was odd, so i thought maybe it was just still in bootloader mode. I gained access to ADB and it doesn't see the device at all (yes i tried the method explained because of the CWM problem, I also do not have CWM and have had a battery die before and it was able to charge fine) I also tried fastboot and it just sits at "waiting for device"
I called up Verizon support figuring it was the battery and they said i could test it at a store. The rep didn't think it was the battery, but when he tested it said 3/3 times it was increment, so it was bad. Then when he tried a regular battery it didn't work either, so he said the phone was bad.
Now, i called support and they are sending me a new phone and i am going to exchange my extended battery for a good one tomorrow. The thing is the lady on the phone said that as long as there were no hardware defects or unauthorized software than there wouldn't be any charge but if there was then it would be a $200 charge added onto the bill. A $200 charge would be pretty bad.
I would never return my phone if i messed it up actually doing something to the phone but here it didn't... at least not in any way I can think of. I am worried about the charge though. I know they usually don't check them but I had the Juopunut bear h-boot and neo's ICS installed. I am not even sure if it's recoverable at all because from everything i tried it definitely wasn't.
Am i just being silly here?
If they can't even boot the phone, then there is no way that they can tell it was hacked.
Sounds like the only way they'll get the phone booting is to do the manufacturer RUU thing with their special tools, so I'd say you're in the clear.
I've sent a phone back that was S-OFF running CM9. If they check before they JTAG it, I've seen no evidence of it.
I had heard before many times that they never checked, but i was extremely surprised whenever she said that. I wanted to ask some of you guys your opinion as well. I doubt it's recoverable without a full sbf as well, so i should be fine. Thanks!
Reaper0294 said:
I had heard before many times that they never checked, but i was extremely surprised whenever she said that. I wanted to ask some of you guys your opinion as well. I doubt it's recoverable without a full sbf as well, so i should be fine. Thanks!
Click to expand...
Click to collapse
I had to send mine back for a screen hardware issue. I was still s- on with the bootloader saying relocked and I did not get hit with that charge. As stated before I have heard of people sending back their phones with different ROMs without issue. Good luck
Sent from my Rezound using xda app-developers app
I've returned multiple devices saying relocked in the bootloader. I think Verizon simply doesn't care to be honest.. Hell I've even gotten a replacement phone that was rooted and running custom software. Shows you how muc hattention they pay to the devices they recieve and send out. Hell I've gotten replacements with screen protectors still on them and big ass gashes/scratches on the screen. 100 point inspection my ass.
Same here; my first Rezound was S-OFF, bootloader unlocked when the USB port failed (the unit would charge but couldn't connect to PC). I just factory reset it and sent it back. The folks who refurbish the phones don't even turn 'em on, and if they did, they probably wouldn't know what they were looking at. The things are bulk reflashed, if the motherboards are even retained at all.