I just received my phone and noticed an odd screen issue after updating the firmware:
Notice the slight line around the screen. The odd part is that I do not see the line when I have a white screen, I also do not see it when I am in clockworkmod nor do I see the lines when the boot screen is loading.
Is my screen going out or what?
I had this problem with my first Atrix and I searched high and low with no workable solution. Some say it is a firmware issue. Honestly, there's no fix to my knowledge, without forking over some cash for a new digitizer. Only option is to get another one or another phone Lord willing. Apologies. Well, unless you can bear with it. It doesn't effect performance from what I saw, but it's annoying and no matter what I couldn't ignore it as if it wasn't there.lol
#Sent from my God given Atrix 4G
phreshy said:
I had this problem with my first Atrix and I searched high and low with no workable solution. Some say it is a firmware issue. Honestly, there's no fix to my knowledge, without forking over some cash for a new digitizer. Only option is to get another one or another phone Lord willing. Apologies. Well, unless you can bear with it. It doesn't effect performance from what I saw, but it's annoying and no matter what I couldn't ignore it as if it wasn't there.lol
#Sent from my God given Atrix 4G
Click to expand...
Click to collapse
Well I can deal with it as I got a pretty good deal on the phone (off contract via ebay) but it is still very annoying. If I can deal with it till November, I am eligible for an upgrade from ATT (with some money of course).
I would definitely blame it on the firmware. If you are getting crazy lines all the way through you could probably blame it on the video. I see this all the time at my work. Try a hard reset, back up your data.
Cheers
Burrito
Burrito Bandit said:
I would definitely blame it on the firmware. If you are getting crazy lines all the way through you could probably blame it on the video. I see this all the time at my work. Try a hard reset, back up your data.
Cheers
Burrito
Click to expand...
Click to collapse
Thanks!! I will try to fully upgrade the firmware to 4.5.141 instead of stopping at 4.5.91.
How would you go about upgrading the firmware if you already unlocked the bootloader and rooted the device? If this is indeed a firmware issue, how would I go about this. I searched the forum and found a lot of conflicting answers. If you could provide me with a good link, I would appreciate it.
Thanks
I am thinking about following this in the morning when I have my phone fully charged and I was wondering if you see any issue with running this?
http://www.android-advice.com/2012/fix-bricked-motorola-atrix-after-ota-update/
My phone is not bricked but I want to revert to stock (locked bootloader, remove root, etc) to see if the issue is indeed a firmware issue. Then I can re-unlock the bootloader, enable root again and restore or reinstall CM9.
Thanks
comhack said:
I am thinking about following this in the morning when I have my phone fully charged and I was wondering if you see any issue with running this?
http://www.android-advice.com/2012/fix-bricked-motorola-atrix-after-ota-update/
My phone is not bricked but I want to revert to stock (locked bootloader, remove root, etc) to see if the issue is indeed a firmware issue. Then I can re-unlock the bootloader, enable root again and restore or reinstall CM9.
Thanks
Click to expand...
Click to collapse
You will not ever lock the bootloader once unlocked. All you can do is hide the unlocked text. It is a fuse that gets burned when unlocking the bootloader.
pre4speed said:
You will not ever lock the bootloader once unlocked. All you can do is hide the unlocked text. It is a fuse that gets burned when unlocking the bootloader.
Click to expand...
Click to collapse
Ok, I am not worried about the unlocked text, all I want to do is update to the official firmware.
comhack said:
Ok, I am not worried about the unlocked text, all I want to do is update to the official firmware.
Click to expand...
Click to collapse
Can't help there. I'm done with crapblur. Staying on cm roms now. You could go with nottachrix, his rom is based off 2.3.6 and you can choose full blur or blur removed when installing.
Well I think I hardbricked my phone anyway --
Failed to boot 1
PwrReason: PWR_KEY_PRESS
Starting Fastboot protocol support
Battery is too low to flash
Click to expand...
Click to collapse
Granted the battery did run out of juice but not until I finished upgrading the firmware:
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf
Click to expand...
Click to collapse
I made sure not to flash lower than the original 4.5.91
Pretty much before I got a chance to install clockworkmod again, the battery died. When I went to restart the phone to go into SBF, I got the above message. I tried booting the phone without the battery in it and it says the "Failed to boot 1" (since I do not have a rom installed yet) but if I try to run fastboot, I get the battery is too low to flash.
I am not for sure if this is a hardbrick or if my battery is just dead but I have charged it for about an hour so far with the same message.
I ordered another battery before this incident so I should get another next week but I am so worried that I hardbricked my device and I will not be able to recover.
Frick!!!
I am so screwed...... I cannot get it turn on with just the battery in but I can disconnect the power cable and the screen stays at Failed to boot 1.
I am at a loss as I have read a ton of threads here on the "battery too low to flash" but none of them are same as my issue. I really do not know what I can do as I bought the phone on ebay for $200 and just received it yesterday.
Well now I have it plugged into my computer and the screen is off but now the green charging light is on again. The computer recognized it as a usb device called MOBOOT and the Motorola USB Networking driver miniport is showing up in Device Manager.
Any ideas?
I am using this method (post 2) DIY active micro-usb cable to battery posts (post #2 method) to charge the battery for a few hours:
http://forum.xda-developers.com/showthread.php?t=1528729
Then I will will try to continue the OP's method to recover my device.
I cannot believe it, this method fixed my issue with "Battery is too low to flash"!!!
I am now in the process of flashing the firmware via RSD Lite.
I had an issue with the Bluetooth and wifi radios on my original atrix so I bought a used one. the used one had an issue similar to yours though not as severe.
I finally got around to replacing the actual LCD with the good one and problem is gone... I don't think it's firmware related, more than likely, hardware is the culprit.
xandr115 said:
I had an issue with the Bluetooth and wifi radios on my original atrix so I bought a used one. the used one had an issue similar to yours though not as severe.
I finally got around to replacing the actual LCD with the good one and problem is gone... I don't think it's firmware related, more than likely, hardware is the culprit.
Click to expand...
Click to collapse
Actually the screen is really not that bad as the camera I used shows the lines much more than they appear.
BTW how much did the lcd cost and where did you buy it from?
Related
Hi,
I tried flashing the phone with Clockwork. Part of the way through the flash it started writing in large letters going off the screen (weird text) then screen turned off, and back on to the installation progress, and then it shut off. No response from anything.
I did a battery pull after 10 mins to try to get the phone into recovery, but the phone does not respond to any combination of keys, battery pulls, and connecting the phone to the PC does nothing. The computer does not see the phone, the USB controller in hardware management does not refresh and show anything when connecting while holding both volume keys, and I have tried everything I could google.
There are no lights on the phone when pressing power, or any combination of recovery keys. Screen is permanently off.
Is there a way to force the phone to boot into any mode to get any recovery?
Thanks for the info.
The T-Mobile Vibrant and the Bell Vibrant are not the same and are quite incompatible actually. Did you flash something for the T-Mobile Vibrant instead? That could be your problem. If so, you'll need to be more careful in making sure it works on the "Bell Vibrant" since most of the stuff here is only tested on the US TMO Vibrant. The big letters are pretty common / normal when flashing a ROM kernel, modem, etc. It would help to know what OS version, ROM name / version you were running before and what filesystem (RFS, EXT2, EXT4). You might also mention what you tried flashing and the version of the Clockwork you were using if you can remember.
Even though you say it doesn't respond to charging, does that mean when you plug it into the "Wall Outlet" as well as the "Computer"? They have been known to produce different results. If you can get it to show the Green battery charge screen, there's a good chance you'll be fine.
Have you seen / read this thread before? - http://forum.xda-developers.com/showthread.php?t=848737
Failing that, you might wish to try the USB JIG method to try to see if that will get you into "Download Mode".
I was trying to flash from Stock 2.1 to Axura2259VE. Not sure what File System.
Only tried charging on computer with no response. will try a dedicated usb charger.
I was using the latest version of Clockwork as of today (Updated from app store, Jan 5).
I will put the jig together tonight if possible.
The phone is a GT-I9000M if that helps.
"If your phone screen is always black, that is it does not display the white Galaxy S/Samsung/AT&T logo when you switch it on, then sorry, this jig will not help you."
http://forum.xda-developers.com/showthread.php?t=819551
So, the Jig will not work for my situation. Anything else I can do? The phone was bought on classifieds and only bricked when updating.
Yes, that's the proper model # for the Canadian Vibrant. The US Vibrant is T959. I'm not sure Axura2259VE for T959 is compatible with the Bell Vibrant as the developer (Master) only owns a US model AFAIK. Try the dedicated charger that came with the phone plugged into a wall outlet with no extensions in between. Mind you, I've not troubleshooted a Bell Vibrant before so I don't know how it differs.
The Filesystem is RFS when stock, EXT2 if you applied the OCLF lagfix from RyanZA (not recommended) and EXT4 if you're running VooDoo. By asking about the filesystem, I was just wondering whether you had a lag fix installed / in-use before flashing. Does any of this apply to you?
I have installed lag fix following the tutorial from the app store, but it was for the intent of rooting the phone, which was already rooted. nothing else was run in the application unless it runs the lag fix by default. doubtful. I do not think it was applied.
Phone not under warranty because i bought it from classifieds. Hoping to get it fixed myself so will try to assemble the 301k resistance between pins 4 and 5 and try it tonight.
Any other ideas?
I really don't know what else to suggest to you. However, installation of the lagfix was unnecessary to have obtained root access on the phone. Rooting and Lagfixing are separate processes. If it was both rooted and lag fixed then which app from the Market did you use to apply the lagfix? Did you disable the lagfix before flashing?
RyanZA's OCLF 2.0.
I had it installed, never ran the lag fix, so I do not think this is the case here.
Thanks alot for the replies. I will post results tonight.
eugenek5 said:
I was trying to flash from Stock 2.1 to Axura2259VE. Not sure what File System.
Only tried charging on computer with no response. will try a dedicated usb charger.
I was using the latest version of Clockwork as of today (Updated from app store, Jan 5).
I will put the jig together tonight if possible.
The phone is a GT-I9000M if that helps.
Click to expand...
Click to collapse
The latest Axura flashes the bootloader to your phone. I suspect this is what the problem is and why you are unable to recover from it. I know absolutely nothing about the Bell Vibrant, but flashing a bootloader will affect how you get into recovery/download mode [I THINK]. You could try entering download mode the way U.S. Vibrant owners do, but I'm not sure if it will help. Sorry I don't have any helpful information, just thought I'd note the possible cause for your grief.
Interesting. I hadn't realized that or looked to see if that was the case. That definitely makes sense. Bootloader bricks are the hardest to recover from IMO (if you can at all). At least, in the future the OP should be able to tell if any rom if going to update the bootloader if it contains an "SBL.bin" in the package.
What?!? I'm suprised a ROM was packaged with the bootloader. To me flashing the bootloader is risky business. I'm not sure there's a way a consumer can recover from a failed bootloader
silow said:
What?!? I'm suprised a ROM was packaged with the bootloader. To me flashing the bootloader is risky business. I'm not sure there's a way a consumer can recover from a failed bootloader
Click to expand...
Click to collapse
I haven't flashed the new Axura because of the inclusion of the bootloader [SBL.bin] and truth be told I was shocked when I saw it in there.
So you guys are saying that the Jtag way does not work? I am sitting here trying to connect 2x150K resistors to pin 4-5 and it is not doing anything.
eugenek5 said:
So you guys are saying that the Jtag way does not work? I am sitting here trying to connect 2x150K resistors to pin 4-5 and it is not doing anything.
Click to expand...
Click to collapse
This method is to help you get into download mode if you are "hardware locked". In your case you have the wrong bootloader on your phone. At this point there is not much you can do yourself. The bootloader will need to be reflashed and as far as I know that's only possible with external equipment rigged into your phone.
I think other people were able to recover from the same incident. they just went to a phone technician(i don't know what do call that) and they just flashed a bootloader to your phone and it wil be flashed back to stock.
hey i'm not sure about this because i have only read about it and i really can't remember where because a lot of bricks already happened here.
Sent from my SGH-T959 using XDA App
Hard brick and fix not working
SO...
My vibrant is bricked, and I have my brother's vibrant to reference. (GT-I9000M)
This is a hard brick, with nothing showing up on the screen.
I have ordered the JIG thinking this would solve the boot issue, but with no luck.
I have tried the following:
- Up/Down - USB - Battery - Release keys
- Up/Down/Power - USB - Battery - Release keys
- JIG - Battery
- Battery - JIG
- USB - Up/Power/Menu - Battery
- USB - Down/Power/Menu - Battery
I have confirmed that the second vibrant that is working fine boots from the JIG successfully. I have also confirmed that the battery is working fine and tested on the other phone.
Cause: Battery pull on unsuccessful flash.
Please help! This phone has been bricked for 2 weeks and I want it back to working. I am out of ideas!
I had my phone hard bricked literally 4 days ago. I called T-Mobile and now I'm typing to you from the new phone. Call and see if the phone is still under warranty. If not then you'll have to pay Samsung themselves to fix the issue for you. I don't know what they'll charge, but I'll assume no more than $60 since its a software issue.
Sent from my SGH-T959 using XDA App
OuncE718 said:
I had my phone hard bricked literally 4 days ago. I called T-Mobile and now I'm typing to you from the new phone. Call and see if the phone is still under warranty. If not then you'll have to pay Samsung themselves to fix the issue for you. I don't know what they'll charge, but I'll assume no more than $60 since its a software issue.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Bought from Classifieds so not sure if it is covered. I have contacted repair places around Toronto.
Any advice would be awesome.
Not sure if there are differences for Download mode but the I9000 forum might be better than the US Vibrant forum.
eugenek5 said:
Bought from Classifieds so not sure if it is covered. I have contacted repair places around Toronto.
Any advice would be awesome.
Click to expand...
Click to collapse
I bought mine off craigslist from a private seller. Its worth a try. The most they'll say is no. Just don't say you rooted your phone.
Sent from my SGH-T959 using XDA App
Can somebody tell me what happened to my motorola atrix?It just suddenly turned white screen...i only got it for at least 2 weeks...it's like the lcd has been damaged but i haven't dropped it not even once...
have u rebooted it?
Can you post a pic of what it looks like?
I already have rebooted it...I did the restore factory setting and even did the hard reset..nothing works...
That looks software based since it seems to follow whatever is on the screen, rather than physical damage which would stay in one place. Have you considered flashing the phone back to stock?
http://forum.xda-developers.com/showthread.php?t=991072&highlight=sbf+flash
which one do i download?the 1.2.6 or 1.5.2? or is it both?
By the way my phone was pre-rooted when i bought it..may i ask how would i know what drivers should i use?32bit or 64 bit?thanks
Use 32 bit if you have a 32 bit computer, or 64 for 64. And flash 1.2.6 with rsd life, ota to 1.5.7, then ota to 1.8.3
Sent from my GingerBlur'd, de-odex'd, modded Motorola Atrix 4G (ish.)
Im sorry but im new to this...what is ota?what do you mean ota to 1.5.7 to ota 1.8.3
zmokez008 said:
Im sorry but im new to this...what is ota?what do you mean ota to 1.5.7 to ota 1.8.3
Click to expand...
Click to collapse
OTA is over-the-air (no computer required). What I suggest is a fresh data factory wipe along with flashing of 1.8.3 SBF (or if you want 1.5.7 to OTA). Whatever suits your fancy.
zmokez008 said:
Im sorry but im new to this...what is ota?what do you mean ota to 1.5.7 to ota 1.8.3
Click to expand...
Click to collapse
Follow the directions in my previous post to flash your phone back to completely stock software. Once that is done, go to Settings -> About Phone (bottom of the list) -> System Updates. You must be on wifi to download the updates. First, it will download an update to 1.57 (I don't think it goes straight to 1.83). Download and install that update following the prompts. Once that is done, do it again to get the 1.83 update. Now you have a fully up-to-date, and hopefully functioning screen, Motorola Atrix.
Since you are flashing back to stock, I recommend using gladroot to obtain root on the phone. This will avoid the formatting of your internal and external storage that gingerbreak rooting method would require. Gladroot files and instructions here: http://forum.xda-developers.com/showthread.php?t=1016060
Basically these are your steps:
Flash 1.26 SBF
Run gladroot.bat
OTA update to 1.57
run afterupdate.bat
OTA update to 1.83
run afterupdate.bat again
The batch files I referenced are in the gladroot download.
jimbush3 said:
That looks software based since it seems to follow whatever is on the screen, rather than physical damage which would stay in one place.
Click to expand...
Click to collapse
Physical damage would not necessarily appear in the same place all the time. It looks to me like the problem appears when a sufficient number of pixels in one column/row are white, and the white is then streaking into other pixels that shouldn't be white. Could indicate a problem with the display circuitry properly handling the voltages. I'd be surprised if this is not a hardware problem. I guess we'll find out after the OP reflashes the ROM.
GoodFoot said:
Physical damage would not necessarily appear in the same place all the time. It looks to me like the problem appears when a sufficient number of pixels in one column/row are white, and the white is then streaking into other pixels that shouldn't be white. Could indicate a problem with the display circuitry properly handling the voltages. I'd be surprised if this is not a hardware problem. I guess we'll find out after the OP reflashes the ROM.
Click to expand...
Click to collapse
Quite true. I was thinking of an impacted screen and not so much of design/production issues. I'm curious to see the outcome now too.
It didn't work...is there any other way?by the way my phone became unrooted after the process
by the way not all of it is white...during the opening of the phone where the logo of motorola comes up the line is colored purple and the icon of contacts when somebody is calling the line is also purple..
It sounds defective. Did you say you bought it rooted? Somebody might have dumped off a bum phone on you.
Sent from my MB860 using XDA App
I dont think there's something wrong when i bought it...It's still fine for 2 weeks..is there any other way?can overcharging did it?there's time that i charge it overnight..
Two things:
I have replaced 4 screens on my girlfriend's Motorola a1200 and 3 years later is still working. Screens go bad AND the internal cable can loosen over time and cause your problem. eBay usually has new screens for under $20.00 and you can Google for instructions on how to do it. It's actually fairly simple and you probably just need to re-seat your current screen cable. I seriously doubt it's anything other than a loose cable or worn out screen.
Sent from my SAMSUNG-SGH-I897 using XDA App
Can't be worn out screen...i just got it for at least 2 weeks..by the way whenever i browse my phone not all have this white screen like when i access the messaging page
I guess i'll just have to stick with it for a while...btw i found a useful apps that help me on my phone..it's called screen filter..while its activated the white screen can't be seen that clear and i read that it help conserve battery so it's like hitting 2 birds with one stone..anyway thanks for the help guys.
Hello All,
I am getting the above error message after a power cycle on my Atrix. It is on the 2.2.2 Android with the latest updated without any special MOD's other than the fact that it was rooted and had a custom APN ...
So after a battery pull (I had to check the back of the phone) then I get modem did not power up (0) message and the phone waits for RSD ...
I downloaded the OLYFR_U4_1.5.2_SIGNED and tried to flash the sbf using the RSDLite it processed without any error, but after the reboot I still get the same message.
Any thoughts or words of advise?!
HoSsEiN
hgn842001 said:
Hello All,
I am getting the above error message after a power cycle on my Atrix. It is on the 2.2.2 Android with the latest updated without any special MOD's other than the fact that it was rooted and had a custom APN ...
So after a battery pull (I had to check the back of the phone) then I get modem did not power up (0) message and the phone waits for RSD ...
I downloaded the OLYFR_U4_1.5.2_SIGNED and tried to flash the sbf using the RSDLite it processed without any error, but after the reboot I still get the same message.
Any thoughts or words of advise?!
HoSsEiN
Click to expand...
Click to collapse
I bought an Atrix off of Craigslist that said it had water damage and it's doing the Same thing.. I've managed to Unlock the bootloader and install CWM, going to see if i can flash a rom to it... I'm new to Moto's so i'm struggling a bit
I'll let you know if i figure anything out..
Suggestions are welcome from all
Edit*
So i've tried flashing a ROM
I've flashed the gingerbread via this method and I got zero errors, but when the phone boots up it still says
Modem did not power up (0)
Starting RSD protocol support
I have no idea what to try next..
Anyone?
well, i've got it to boot up by holding down the volume when powering on and going to the:
BP HW Diag & Boot AP
Baseband is blank so it definitely needs a radio flashed to it.. Which i tried and it didn't work since it won't boot up correctly.. I've got a SDcard ordered going to wait till then to try some more..
I'm guessing the radio is actually damaged and nothing you can flash will fix it because it is a physical problem. I'd say you turn it in for warranty.
BravoMotorola said:
I'm guessing the radio is actually damaged and nothing you can flash will fix it because it is a physical problem. I'd say you turn it in for warranty.
Click to expand...
Click to collapse
hmm.. wish i would have thought about that before unlocking the bootloader.. Also i bought mine off of craigslist and it was water damaged..
So if i can't fix it i guess i'll just have to sell it to someone else that wants to do something with it...
I actually bought 2 off craigslist yesterday, luckily the other one is in perfect condition, just did the OTA to gingerbread
Looking forward to seeing cm7 available for the Atrix
I can't say i've had the water damage problem, however my phone used to do this all the time. My issue was i was using a micro sim card (i cut it myself), and if the sim card slid it would give me that error message.
elijahblake said:
hmm.. wish i would have thought about that before unlocking the bootloader.. Also i bought mine off of craigslist and it was water damaged..
So if i can't fix it i guess i'll just have to sell it to someone else that wants to do something with it...
I actually bought 2 off craigslist yesterday, luckily the other one is in perfect condition, just did the OTA to gingerbread
Looking forward to seeing cm7 available for the Atrix
Click to expand...
Click to collapse
Hmm, isn't there something like to where Motorola will repair outside of warranty but it just costs money?
BravoMotorola said:
Hmm, isn't there something like to where Motorola will repair outside of warranty but it just costs money?
Click to expand...
Click to collapse
that would be VERY nice to know... i could deal with that.. should be able to still recoup what i have in it and "maybe" make a few $'s..
as far as the SIM.. i pulled mine out of my inspire 4G and it's the same error. So it's definitely not that in this case.. wish it was that easy though
I also started having this problem and I'm getting very worried.
EDIT: Now it says 'battery is too low to flash' and it is plugged into mains! I can't even charge my phone anymore!?
PLEASE HELP!!
Have you flashed anything prior to this? What I mean is what did you flash before you got this error? And did you flash on a low battery?
Sent from my MB860 using xda premium
903tex said:
Have you flashed anything prior to this? What I mean is what did you flash before you got this error? And did you flash on a low battery?
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
I never used to get this before but after I flashed CM7, I started getting this error.
Last time I got this error, I simple plugged my phone into mains and it started charging. After that, it booted.
But now, nothing works. My phone doesn't even charge if its plugged in and I even tried using my dads battery but I still get the error.
Shall I flash a different radio? Or shall I go back to Blur-based Roms?
I was just wondering if anybody has fixed the "modem did not power up (0)" problem?
Thanks!
*Bump*
I have a Photon, but I'm getting the same error, right after I flashed the SBF for my phone. Removing the SIM card got it to boot, but I haven't tried putting it back in yet. I know the Atrix actually requires the SIM card, unlike the Photon (Sprint CDMA phone but global capable) but I would try booting without it, and then sticking it back in and booting again.
mikerotchitches said:
I was just wondering if anybody has fixed the "modem did not power up (0)" problem?
Thanks!
Click to expand...
Click to collapse
I'm wondering as well.. Plagued with this problem and 250 for warranty.
If u go in Q&A section, there's already an answer.
And The answer is to get it in warranty :v
There isn't a fix, that's a hardware issue
I have found if you hold volume down when booting and change to "Boot (No BP)", no SIM is required to utilize the operating system. (obviously you cant make calls though)
Modem sometimes powers up.
My phone is finicky with it. Sometimes it says modem did not power up, and then other times it doesn't. This might seem weird but when I squeeze the bottom of my phone it will start working and does NOT give me the message. But it freezes from the problem it has been having.
I have unlocked and rooted my phone, it has been a long time before the message showed up. Does Motorola know about this happening to their phones? And does anyone know if people would want to but the phone on craigslist or ebay or something?
I just get this problem too.. any fix for this at the moment?
raunamaxtor said:
I just get this problem too.. any fix for this at the moment?
Click to expand...
Click to collapse
Hardware issue. There is no fix , only if u know how to replace parts in the phone or want to send it to warranty.
now it can be fixed.. here is the solutions
put your battery in your phone, and plug it into the charger.
When the Motorola logo appears, hold the Volume Down button and boot options will appear.
Hit the volume down button until you see "Boot Android (No BP)". Press the Volume Up button. It will say "Cold Booting Linux..."
Screen will reset, and you'll see your battery begin to charge.
Ok guys, yes...I'm a noob...
I did a master reset on the phone and now I get nothing...
It won't turn on unless I plug it in to the charger.
When it does turn on, all I get is a few vibrations, and
the icons at the bottom light up.
I can get windows to see the two "drives" of the phone,
but they are empty (have 0 bytes if you right click and check properties. If you left click, it says please insert disc).
I've tried a new battery and my battery turns another phone on...
I've also tried two cables and two PCs.
It hasn't been rooted or messed with, the battery died and I went to charge
it and nothing...I left it on charge overnight and at least see a bit life.
Any ideas, or should I just send it on to HTC??
So that others have a better idea... can you get into hboot or fastboot?
try a nwe battery
xboarder56 said:
try a nwe battery
Click to expand...
Click to collapse
he said he already tried a new charged battery, so it can't be that. I'm thinking his phone's OS might be gone so he should probably installed a RUU or something.
In the dark...
Can't see anything come up on screen...
no idea what mode it's in, hboot, fastboot or anything ??!?!!
Think it might be possible to install just a stock (Tmobile) RUU?? If so, how ?????
karaokekarnival said:
Can't see anything come up on screen...
no idea what mode it's in, hboot, fastboot or anything ??!?!!
Think it might be possible to install just a stock (Tmobile) RUU?? If so, how ?????
Click to expand...
Click to collapse
if you can't get into hboot/fastboot (totally forgot which, basically same thing) then you can't do the RUU
Hmmm, OK
Do you think there is anything that I can do to get it running ??
And where do I find the thanks button ???
karaokekarnival said:
Do you think there is anything that I can do to get it running ??
And where do If ind the thanks button ???
Click to expand...
Click to collapse
if you rooted and custom recovery you could but right now you out of luck you gonna have to return
Duh, I found the thanks button !!!
I was afraid of that...guess I'll ship it off Monday. If anyone knows a way before then, let me know...can't hurt to try, eh ??
karaokekarnival said:
Duh, I found the thanks button !!!
I was afraid of that...guess I'll ship it off Monday. If anyone knows a way before then, let me know...can't hurt to try, eh ??
Click to expand...
Click to collapse
There isn't a way if your phone isn't detected or you can't get into hboot. Meaning you have no control over your phone to do anything.
Anyways, for htc warranty exchanges that is done with tmobile... they usually send you the phone first and then you send one back in return. Unless your policy is different. So i suggest you calling them immediately.
Update
I can go into control panel and "see" the phone listed in device manager under portable devices as "F" and "G". Click properties and they are found as HTC devices. Does this mean I can do anything to it? I just want my phone back working as fast as I can. Sending it in will take a while. I bought this phone for the camera. We have a 1 yr old and don't wanna miss the Christmas pics...
karaokekarnival said:
I can go into control panel and "see" the phone listed in device manager under portable devices as "F" and "G". Click properties and they are found as HTC devices. Does this mean I can do anything to it? I just want my phone back working as fast as I can. Sending it in will take a while. I bought this phone for the camera. We have a 1 yr old and don't wanna miss the Christmas pics...
Click to expand...
Click to collapse
are you on tmobile? they usually send within 2 days, their distribution center is in texas or something. I usually get it next day.
You said your screen doesn't turn on or doesn't show anything. It's gonna be hard to determine what you're doing even if you can run ADB to put it in oem fastboot and to flash a RUU that way. But it sounds like your display might be a problem too then. It'll be quicker to do an exchange. If you call in today, they'll probably ship it on monday and you'll get it wednesday latest. unless you have tmobile insurance plan. it should be next day and you'll get it tuesday.
Thanks
Well that might work for me then...can't hurt to give it a try.
Thanks a bunch for letting me know !!!
No problem, I had my fair share dealing with tmobile exchanges lol.
If you purchased directly from tmobile it should be very easy to do an exchange because your warranty is verified.
If you bought it off craigslist/ebay. sometimes the previous users used a different carriers that makes the warranty no longer verified. HOWEVER many customer reps will still try to process the exchange (you can determine by their upbeat personalities lol).
If you run into someone who won't do it, just call again and talk to another rep. Most of the time they will push it through because it's still a newly released phone.
Have you already contacted T-Mobile support? You'll have to talk to them anyway before they agree to replace your phone.
The reason I am asking this is because there might be an unpublished backdoor way to restore your device if your device is not completely (hardware-wise) dead. For example, Dell Streak has a complete firmware image on its internal SD card and you needed to somehow trigger an IPL routine to restore the device to its original condition.
I haven't heard of anything similar on HTC devices yet, but hey, it's just a thought. And if there actually is a way, and you are the first one to post it here, you'll be a hero!
ringochan said:
Have you already contacted T-Mobile support? You'll have to talk to them anyway before they agree to replace your phone.
The reason I am asking this is because there might be an unpublished backdoor way to restore your device if your device is not completely (hardware-wise) dead. For example, Dell Streak has a complete firmware image on its internal SD card and you needed to somehow trigger an IPL routine to restore the device to its original condition.
I haven't heard of anything similar on HTC devices yet, but hey, it's just a thought. And if there actually is a way, and you are the first one to post it here, you'll be a hero!
Click to expand...
Click to collapse
yeah we normally just flash a RUU, but you can't even see the screen, so we can't even be certain that we're in the correct modes to be flashing and stuff. because we require to ADB it to restart in fastboot, but we can't even see if its going to fastboot. or if it already is in fastboot to begin with, so we're not certain which commands to run with the screen being off. Well you can always try commands and it should only work in certain modes, but do you really want to do it blindly? I would rather just exchange the thing.
Not afraid to try....
Well, I can't use it as it is...exchange is a hassle even in 2-3 days. Can't do anything until tomorrow anyway. I was thinking today, I've heard they can port Android to iPhone...there's no fastboot there, is there ??? Soooooo, if it's turning on, I should be able to do something...I want my phone back !!!
Edit: I misunderstood the issue
Sent from my HTC Ruby using xda premium
Please share....
Snargaflab, please share, it might help me or others to think !!
Flashing green light ???
It is now turning on and has a flashing green light, does that mean anything??
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.