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
Hey all,
Just a couple days ago, my track ball stopped working when I use it to scroll down. In recovery, you need to be able to scroll down to do anything. Is there a way to flash things and do nands without the track ball? I know there is Clockwork, but I don't trust it with the stories of bricking. If anything, all I need to do is be able to flash the flashback ROM so I can send it in and get a new phone.
Any remedies?
Thanks
Have a read here.
chris22_2 said:
Hey all,
Just a couple days ago, my track ball stopped working when I use it to scroll down. In recovery, you need to be able to scroll down to do anything. Is there a way to flash things and do nands without the track ball? I know there is Clockwork, but I don't trust it with the stories of bricking. If anything, all I need to do is be able to flash the flashback ROM so I can send it in and get a new phone.
Any remedies?
Thanks
Click to expand...
Click to collapse
It happened to me. I was trying to flashback to send it back...no trackball. I found that pushing on the phone with my thumb above the trackball enabled the trackball enough to flash the zip. Keep in mind I was sending the phone back to Verizon for the broken trackball, though, so I wasn't worried about breaking it further.
Chevelle1768 said:
Have a read here.
Click to expand...
Click to collapse
DoubleByte said:
It happened to me. I was trying to flashback to send it back...no trackball. I found that pushing on the phone with my thumb above the trackball enabled the trackball enough to flash the zip. Keep in mind I was sending the phone back to Verizon for the broken trackball, though, so I wasn't worried about breaking it further.
Click to expand...
Click to collapse
Thank you and thank you!
By the way, you probably should grab the recovery-RA-eris-v1.6.2-trackball-optional.img 1.7.1 version (it has all of the functionality of the "original" 1.6.2 Amon_RA; the first "trackball-not-required" version I built was based on the 1.6.2 source that actually omitted some of the menu options).
Cheers!
i have the trackball not working during recovery issue as well
I have found, and I am almost certain this will work for you, plugging your phone into your charger will get your trackball to work
If I don't have my cord to plug into the usb, I've used a paper clip to press against the top of the usb port towards the trackball and have found this to work as well
if you have any questions on the process please don't hesitate to contact me
NPH- said:
i have the trackball not working during recovery issue as well
I have found, and I am almost certain this will work for you, plugging your phone into your charger will get your trackball to work
If I don't have my cord to plug into the usb, I've used a paper clip to press against the top of the usb port towards the trackball and have found this to work as well
if you have any questions on the process please don't hesitate to contact me
Click to expand...
Click to collapse
Actually, most people find out about the problem, or it's more severe when a cord/charger is plugged in.
roirraW "edor" ehT said:
Actually, most people find out about the problem, or it's more severe when a cord/charger is plugged in.
Click to expand...
Click to collapse
Does the problem worsen over time to the point at when it does it if it's not on the charger? Cuz mine's pretty bad on the charger.
I went through this as well. The various tricks to get it to work succeed on some phones and not others, but they're worth a try. In most cases the trackball will continue to deteriorate over time and mine got to the same point where I couldn't scroll down and therefore couldn't use RA to flash. But I needed to flash it back to stock so I could get a refurb from Verizon via my warranty. At that time, I don't think this RA that doesn't require a trackball was available. I asked about if there was and I couldn't find anything about it. Thought about trying to use the RA source and build a version myself but I just didn't have the time and lord knows, screwing that up might have really borked my phone for good, so I get it go. Now that RA without the trackball is out there, I'd use it if you can get that on your phone.
But there's another very easy solution. You can download ROM Manager from the market: ROM manager will let you flash ROMs without the trackball. It uses Clockwork Recovery for flashing and I was concerned at first about the stories of CR possibly bricking phones (in fact this not really a serious risk) or maybe making it harder to return the phone to unrooted stock or something else. But in fact, ROM manager uses Clockwork by only temporarily loading CR in memory, where you can use it to flash a ROM, and it does NOT replace RA! It leaves RA intact on your phone. If you reboot, RA is there. You can use ROM manager to flash any ROM and in my case I used it to flash the easy, return to stock zip that you can find here on the Eris forum. I brought it to the Verizon store and all I had to say was the trackball died and they traded me for a refurb.
BTW, this was a few months ago and there were several threads here with stories about people calling Verizon (not the stores) with tales of woe about their Eris and getting a free upgrade to Incredibles, Moto Droids, etc. if they were very nice about asking. This might have been a time when the inventory on the Eris was low. Anyway, I tried twice times and couldn't swing it - they only offered a refurb Eris. Found a local store with the Eris in stock and did it on the spot.
Now, if an Eris is out of warranty, then the best route is to replace the trackball. There are threads on XDA with all the step by step instructions you need. These are the same trackballs that are used in many of the Blackberrys and apparently those fail frequently and there are a LOT of options available on line for about $3-$5 via Amazon, etc. And hey, you can get them in kinds of whizzy colors ;-p
Hope this helps!
Good luck!
CPCookieMan said:
Does the problem worsen over time to the point at when it does it if it's not on the charger? Cuz mine's pretty bad on the charger.
Click to expand...
Click to collapse
That's my observation and experience.
Sent from my Eris using XDA App
Oh Man!
roirraW "edor" ehT said:
That's my observation and experience.
Sent from my Eris using XDA App
Click to expand...
Click to collapse
crap! that is what I thought and this just confirmed the fate and almost certain death
I think I'm being stalked but maybe I'm not the only one.
Hey guys... been checking around.. have a few quick questions. Just to give you an idea.. I've rooted and flashed my own Captivate, now my brother is looking for a new phone so we may get him an atrix.
1. How common is it to hardbrick the atrix? I know that on the captivate a hardbrick is an extremely rare happening, and you can almost always go back to stock via odin.
2. Is CM7 officially available? if so are the nightly releases fairly stable?
3. I know that flashing voids the warranty, and I wouldn't try to redeem a phone I ruined by overclocking or anything like that.. However, I prefer to have a way to completely remove anything I did to the phone. Is this possible?
1. Not very. Unless you try to downgrade from 4.5.91
2. I'm using cm7 now. No nightlies but 0 issues! VERY stable!
3. If you unlock bootloader its unlocked. No going back.
Sent from my MB860 using XDA App
Like joe said a hard brick is not very common, unless you don't follow directions. Cm7 is currently in beta for the atrix, but it is very very stable. No web top or finger scanner try though. Once you unlock the phone, during startup wroth the red M in thee upper left it will say unlocked. So nope, no way to undo it all.
Sent from my MB860 using XDA App
I'm going to agree with the the first two points earlier posters made, but as for relocking the bootloader, I think it can be done if you sbf(not recommended) back to the stock 3.4
Sent from my Unlocked Gingerblurred Atrix
Thanks guys, I know that on the Captivate if you go back to odin it returns it to stock.
I am hesitant to root something that can't be reverted.. not a good situation if something goes out.
I don't think he is too worried about the finger print scanner or webtop.
My friend wanted his Atrix rooted i took it home and did it under a hour, I had no experience with command prompts at the time
Sent from my VS910 4G using XDA App
There's an easy to follow guide if you only want root, not unlocked bootloader. Other than removing bloat its mildly pointless though
Sent from my MB860 using XDA App
krad54 said:
I'm going to agree with the the first two points earlier posters made, but as for relocking the bootloader, I think it can be done if you sbf(not recommended) back to the stock 3.4
Sent from my Unlocked Gingerblurred Atrix
Click to expand...
Click to collapse
I was under the impression that unlocking the bootloader cannot be undone, which is why the hardbrick occurs when flashing back to an earlier version after the GB OTA update.
I believe flashing a fruit cake should give you the stock Motorola bootlogo (no "Unlocked" at the top) image, but the bootloader will still be unlocked.
The biggest issue here is honestly this.
I don't want to get a phone with some sort of manufacturer defect, then not be able to claim the warranty because the phone was at some point in its life flashed. (Sometimes it takes a while for the defects to actually pop up..)
I don't believe in overclocking or anything like that.
If I softbrick a phone I can usually fix it on my own.
I just don't want say, the speaker to go out and it have nothing to do with what rom he is running..
And then for my brother to be out of a phone, just because the speaker went out.. despite it having nothing to do with the fact it was flashed..
As to the bootloader, yes you can flash earlier versions and the "unlocked" at the boot screen will disappear, however there will remain evidence that you had unlocked the bootloader before if they investigate it
That being said there's been quite a few people who have been able to get warrenty replacements and repairs sending back their phones after flashing back..I haven't heard of anyone who's phone has been investigated that deeply and rejected
That works.
I mean, I don't have any intention of overclocking or pushing the hardware out of spec or anything.
I figure as long as whatever goes wrong is reasonable and not related to doing something stupid with the device we will probably be ok.
You don't need to overclock that phone at all ... rooting it's simple as I posted before. There some bootloader blocking you from loading roms, can be taken off.
Sent from my VS910 4G using XDA App
While completely bricking the Atrix is hard to do, it's still possible if you don't carefully read all the instructions. I do miss the Captivate though, it's incredibly easy to flash and recover from any mistake. The CM7 beta build is very stable, I have been using it since the last update was release on the 13th of September and haven't experienced any big problems. If your brother is looking at the Atrix for the webtop or fingerprint scanning capabilities though, just know that the current CM7 build do not yet support them.
From what I've read so far, I haven't seen anyone trying to use their warranty have a problem with the unlocked bootloader. If you're going to buy it through AT&T, I'm pretty sure they're oblivious to it anyway. Last time I exchanged my phone at the repair center, they didn't even bother to see if it booted. They just took it and handed me another one on the spot.
Verizon is sending out replacement phone and need to restore this to stock.
This also started prior to flashing the new ICS leak and after dling ~600mb's via wireless tether.
Not sure if something burned up.
Phone is stuck on 1X only. Tried everything and can't get 3g or reliable 4g.
It get's 4G but only a minute at a time.
I tried doing the various "Fix network bootloop 1x issue threads" but still a no go.
Phone doesn't take the CDMA only option under Mobile networks, it resets back to to lte/cdma.
It never drops to 3g.
I dled the RUU but it does not update nor recover.
Any ideas?
Thanks!
Flash the stock Rom from scrosler's website.
www.scottsroms.com
Droidel said:
Verizon is sending out replacement phone and need to restore this to stock.
This also started prior to flashing the new ICS leak and after dling ~600mb's via wireless tether.
Not sure if something burned up.
Phone is stuck on 1X only. Tried everything and can't get 3g or reliable 4g.
It get's 4G but only a minute at a time.
I tried doing the various "Fix network bootloop 1x issue threads" but still a no go.
Phone doesn't take the CDMA only option under Mobile networks, it resets back to to lte/cdma.
It never drops to 3g.
I dled the RUU but it does not update nor recover.
Any ideas?
Thanks!
Click to expand...
Click to collapse
First thing I'm thinking is you can't RUU back in your situation because the version number is higher than the old RUU. My suggestion is to ROM it, and then flash back to stock RUU, because most ROMs set the version number to 1.0.0.0, therefore all RUU's are a higher version number. Then when you go to flash it, it will recognize, read and flash.
On a side note form this, you're pretty much screwed if you're trying to go to stock from something ripped, since your bootloader will show relocked or tampered, or something other than 'locked' as it shows when completely stock out of the box. This is of course unless you never unlocked it, which means you cant change version numbers, which means you're screwed either way.
Verizon will be able to look at your bootloader and know that it isnt factory stock, so chances are, they are going to charge you for your phone. I'm just trying to be honest and upfront, since I'm kind of a realist when it comes to getting screwed by big corporations like Verizon.
Good luck getting it back to an older version though.
p.s. on the note of your signal issue... the back is on the phone, right? Did you check the contacts inside the cover?
poppajules said:
First thing I'm thinking is you can't RUU back in your situation because the version number is higher than the old RUU. My suggestion is to ROM it, and then flash back to stock RUU, because most ROMs set the version number to 1.0.0.0, therefore all RUU's are a higher version number. Then when you go to flash it, it will recognize, read and flash.
On a side note form this, you're pretty much screwed if you're trying to go to stock from something ripped, since your bootloader will show relocked or tampered, or something other than 'locked' as it shows when completely stock out of the box. This is of course unless you never unlocked it, which means you cant change version numbers, which means you're screwed either way.
Verizon will be able to look at your bootloader and know that it isnt factory stock, so chances are, they are going to charge you for your phone. I'm just trying to be honest and upfront, since I'm kind of a realist when it comes to getting screwed by big corporations like Verizon.
Good luck getting it back to an older version though.
p.s. on the note of your signal issue... the back is on the phone, right? Did you check the contacts inside the cover?
Click to expand...
Click to collapse
The contacts are fine. what if the phone bricked during a software update in hboot? Can they still see relocked and tampered?
Some say that vz doesnt care as long as it has no physical damage.
I don't know about Verizon not caring, but I highly doubt they would take back all of our rooted phones..
I doubt the phone bricked if it booted up. I would flash the ICS RUU and see if the radios fix your signal issue.
Like I said before, I am running Scott's CleamROM and it sets the software versions to 1.0.0.0, so any RUU will flash over it. This is your best bet.
If VZW doesn't care about the bootloader, then you're golden, but don't count on that.
If I may pry, why are you sending it back for the replacement? If it's because of the radios, then I really doubt they are going to just take the phone back, since you could have messed up software to cause the issue.
Just try flashing some stuff before you call it busted. I would go with the ICS leak, Scott's CleanROM, and then back to your old RUU if you want. There's also a patch you have to install to downgrade from CleanROM and ICS leak back to GB, so you might want to do research, also. If you need help finding stuff, just send me a PM.
p.s. Anyone can boot your phone to bootloader (unless of course your phone is in little tiny pieces all over the street), and see that the bootloader is unlocked, possibly tampered for the custom recovery installed, and even if you lock it again, it will say relocked, indicating to everyone that it has been unlocked at one point. 'Unlocked', 'Relocked', 'Tampered', and 'Security Warning' void certain parts of your warranty (in the words of HTC dev.com). The only thing that doesn't void it is if it reads 'Locked'. Period.
Some say that vz doesnt care as long as it has no physical damage.[/QUOTE] Dude I sent two Dinc2 back completed rooted with no problems. Most times the tech at big V. couldn't care less. Most don't wouldn't know what rooting is and the ones that do, more than likely are rooted themselves. The question is if they send it to HTC? And will it meet their requirment now that they have a record that you are rooted as I'm sure if you're had to go thru HTC to unlock. However in reading alot of cases noone have posted a problem with returning a rooted or relocked phone at lease none I've read about. Good luck tho as there's always that first time.
ghostt021 said:
Dude I sent two Dinc2 back completed rooted with no problems. Most times the tech at big V. couldn't care less. Most don't wouldn't know what rooting is and the ones that do, more than likely are rooted themselves. The question is if they send it to HTC? And will it meet their requirment now that they have a record that you are rooted as I'm sure if you're had to go thru HTC to unlock. However in reading alot of cases noone have posted a problem with returning a rooted or relocked phone at lease none I've read about. Good luck tho as there's always that first time.
Click to expand...
Click to collapse
Yeah, I've never tried to send a rooted phone back, personally, but I've never asked anyone at VZW about it. (I'm paranoid that SWAT will descend from the roof and take me down if they knew my phone was rooted)
Good luck dude, just box it up and ship it off then. 'F' 'em.
No go, reflashed ICS leak, the tamper and security warning are gone.
I don't understand why it's not letting me switch to CDMA only. It goes back to CDMA/LTE. Could a bad SIM card cause 3g issues?
I doubt the SIM card would cause 3G issues, but hey, anything is possible I guess. I would say that you wouldn't get ANY signal if the SIM card were bad. Do you have another SIM card phone to test with, perhaps? Just an idea...
Did you go to a ROM instead of just the leak? Hell, you might just have signal issues where you are.. Maybe?
Maybe the antenna did burn up.. never heard of it, but that's not saying it can't happen.
I think tracing your steps back is going to be the best at figuring out the issue. When you flashed the ICS leak, you relocked and flashed, right? no errors? the install went straight down the list with no skipping around? After the install, you went through full HTC/Verizon setup? Have you tried the phone in other locations, i.e. work, groceiry store, gas station, interstate, etc.? Even outside the house will give a different strength... Forgive these sugestions as 'elementary' or 'duh' type suggestions, but something just doesn't sound right.
Also, go to your network settings and try changing the network type from automatic to home only. See what happens.
poppajules said:
I doubt the SIM card would cause 3G issues, but hey, anything is possible I guess. I would say that you wouldn't get ANY signal if the SIM card were bad. Do you have another SIM card phone to test with, perhaps? Just an idea...
Did you go to a ROM instead of just the leak? Hell, you might just have signal issues where you are.. Maybe?
Maybe the antenna did burn up.. never heard of it, but that's not saying it can't happen.
I think tracing your steps back is going to be the best at figuring out the issue. When you flashed the ICS leak, you relocked and flashed, right? no errors? the install went straight down the list with no skipping around? After the install, you went through full HTC/Verizon setup? Have you tried the phone in other locations, i.e. work, groceiry store, gas station, interstate, etc.? Even outside the house will give a different strength... Forgive these sugestions as 'elementary' or 'duh' type suggestions, but something just doesn't sound right.
Also, go to your network settings and try changing the network type from automatic to home only. See what happens.
Click to expand...
Click to collapse
I noticed this happeneng a day prior to flashing the ICS leak. I was using wifi tether do download about 600mb's and notice a couple of hours later that it dropped to 1x. Restarted phone and it went to 4g. I usually switch to 3g to save battery, that's when i notice the problem.
The ics leak flash didn't show any errors.
I am trying to flash GB to this new firmware but i'm having a hard time flashing the PH98IMG RUU from scott's site. It reads and checks it but doesnt flash it.
RUU.exe errored out with "Unknown Error"
Droidel said:
I am trying to flash GB to this new firmware but i'm having a hard time flashing the PH98IMG RUU from scott's site. It reads and checks it but doesnt flash it.
RUU.exe errored out with "Unknown Error"
Click to expand...
Click to collapse
Make SURE you are pulling the PH98IMG for the stock RUU from the android police website, NOT Scott. He didn't post up the new leak. The RUU that Scott has will NOT flash over the old ICS stuff he's put out before.
Go here to get the leaked RUU.
In this process, relock your bootloader, flash the file from A.P.(TWICE, this is important), unlock your bootloader with your unlock token from htcdev, and THEN flash what scott has. It's a time consuming process. It's up to you though. The directions are out there on A.P., Scott's website, all over Scott's thread around the 400-page range for the 4.0.1 release... and my abbreviated directions here.
Grab one of the top three selections, not the pre-rooted version.
also, try going back and re-downloading your ROM file, maybe you got a bad download.
If you upgraded to ics, you can't ruu to gingerbread at all because of the older hboot. But you can flash a gb kernel then a Rom or nandroid+ scrosler sdcard fix
Sent from my ADR6425LVW using xda premium
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?