Related
Found on a few occasions I put the device into Airplane mode to conserve battery life but when I went to exit Airplane Mode, the device stays stuck in Airplane Mode.
Turning off the device and rebooting the device works ok.
Has anybody noticed this behavior?
Should I try something else to toggle Airplane mode ON/OFF?
I've been battling with my HOX losing signal completely (0 bars, just the small "x") and not able to reacquire the signal until I either toggle airplane mode or reboot it. Seems to be entirely random. Going to try and hard reset once and if that doesn't resolve it I'll swap it out for another one.
Dose it randomly happen anywhere or only in certain places?
Sent from my HTC One X using xda premium
Tankmetal said:
Dose it randomly happen anywhere or only in certain places?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Seems to happen randomly everywhere I am. While researching this issue, I came across this post over on androidcentral: http://forums.androidcentral.com/htc-one-x/171872-htc-one-x-att-version-bugs-thread.html#post1762071
It describes my issues almost exactly. Seems like AT&T didn't do enough QA with some of these. If there isn't a patch/update soon, I'll most likely go swap it out for another one and hope it performs better.
agentdr8 said:
Seems to happen randomly everywhere I am. While researching this issue, I came across this post over on androidcentral: http://forums.androidcentral.com/htc-one-x/171872-htc-one-x-att-version-bugs-thread.html#post1762071
It describes my issues almost exactly. Seems like AT&T didn't do enough QA with some of these. If there isn't a patch/update soon, I'll most likely go swap it out for another one and hope it performs better.
Click to expand...
Click to collapse
dont swap since your possibly returning your htc one x cause of the locked boot loader. Let someone else enjoy a brand new hox.
same thing is happening to my Verizon Droid 3
So I have no clue what is happening.... Last 2 days now random airplane mode and have to reboot...tried my backups... I don't want to do hard reset cause it does not seem to help others..
Rooted Droid 3
Eclipse 3 ROM
Here are 3 screenshots that might help one of you xda geniuses.. You guys are the best.. even Leo Laport talks about you!
so these are from Motomizer;
I hope the attachments are okay...this is my first time attaching here...
*I always get "com.androidphone" force close before I lose radio.
I have spent many hours trying to find a solution
Thank you in advance
Rich
@richsapf unless I'm missing something you have a droid 3..... This is the one x forum you should try the forum for your device you will probably get a better answer to your problem
http://forum.xda-developers.com/forumdisplay.php?f=1193
Sent from my Nocturnalized Beast
Hi E. Cadro,
I know. I'm sorry if i broke a rule. I looked everywhere Google..etc..and found nothing. so this seemed to be most possible place to get help. XDA is the best... I did post in Droid 3 and 0 replies. I am trying to figure out if I did something wrong or if just nobody has an answer yet?
Rich
I have put a request in to see if a fellow rc that may have more knowledge about your phone than me can help out
Sent from my Nocturnalized Beast
Have you tried to flash a new radio image ?
"Friends forever." - Ventus
CallMeVentus said:
Have you tried to flash a new radio image ?
"Friends forever." - Ventus
Click to expand...
Click to collapse
i dont think radio is the issue...
also in the log don't see anything related to phone...
Sent from my MB526 using xda premium
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
com.android.phone?
fc is random or at boot?
is this rom stock based? if so is it debloated?
Sent from my MB526 using xda premium
Thank you so much for replying!!..
I just reflashed Eclipse 3 and it has been fine.. I personally feel it was something i dl'ed..one of the GPS fixer apps..OR..call blocking app is my prime suspect.. I tried about 5 uninstalled all but mr(something)..i forgot name..
It would happen random.. i thought it was when i used bluetooth and google maps at same time..but it would do it just at random...
I am going slow and doing backups as I install my many fun apps..
So did anything look suspicius in the logs I posted?... I really should go line by line and learn all that stuff...
Many thanks again!!... How do i offically thank you guys...just click a thanks button?
Rich
Glad you got it sorted out
Sent from my Nocturnalized Beast
nogoodusername said:
i dont think radio is the issue...
also in the log don't see anything related to phone...
Sent from my MB526 using xda premium
---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------
com.android.phone?
fc is random or at boot?
is this rom stock based? if so is it debloated?
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
That's why I'm confused.....his log shows nothing
"Friends forever." - Ventus
Is there a tutorial on how to flash just the radio?
HTC One X stuck on Airplane Mode
Hey guys..
ok.. this is my first time posting on here, so i'm not sure exactly how this works..
2 days ago.. my HOX suddenly lost it's signal, (small x next to the bars), and hasn't regained it yet. Attached is a screen shot of the settings screen, showing that the airplane mode is 'turning off', but the thing is, that's all I get.. it won't turn off.. it's as if it's on, and the device can't turn it off.. I tried everything from resetting to doing a restore factory settings.. nothing.. it's stuck like this.
The thing is, I live in Egypt, and I bought this mobile online from the UK.. if I were to take it to the shop here, I would lose my warranty. I need to be sure exactly what I'm dealing with, so if I need to, I send it back to the UK and incurr the shipment fees. If it's a minor hardware problem, I'll just void the warranty and fix it here.
The device is running the original Sense 4.1.. I did not flash any ROM's.
Appreciate your response!
akram.k.nassar said:
Hey guys..
ok.. this is my first time posting on here, so i'm not sure exactly how this works..
2 days ago.. my HOX suddenly lost it's signal, (small x next to the bars), and hasn't regained it yet. Attached is a screen shot of the settings screen, showing that the airplane mode is 'turning off', but the thing is, that's all I get.. it won't turn off.. it's as if it's on, and the device can't turn it off.. I tried everything from resetting to doing a restore factory settings.. nothing.. it's stuck like this.
The thing is, I live in Egypt, and I bought this mobile online from the UK.. if I were to take it to the shop here, I would lose my warranty. I need to be sure exactly what I'm dealing with, so if I need to, I send it back to the UK and incurr the shipment fees. If it's a minor hardware problem, I'll just void the warranty and fix it here.
The device is running the original Sense 4.1.. I did not flash any ROM's.
Appreciate your response!
Click to expand...
Click to collapse
Why are you posting it here ? You have a One X....
Sent from Ursa's claws.
I had this problem with my first one xl. Saw a bunch of threads with people having the same problem. Warrentied the phone and haven't had it again yet
Sent from my HTC One X using xda app-developers app
E.Cadro said:
I have put a request in to see if a fellow rc that may have more knowledge about your phone than me can help out
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
Ok I do have a Htc one x. It was working fine i friend updated to jelly beam and now have the same problem stuck at "Airplane Mode on, if i try turn off stuck at Turning off" i cant find a solution and cant sent to htc suport center cuz i am living on south america :s plz if someone know a solution about this i need your help.
mats1980 said:
Ok I do have a Htc one x. It was working fine i friend updated to jelly beam and now have the same problem stuck at "Airplane Mode on, if i try turn off stuck at Turning off" i cant find a solution and cant sent to htc suport center cuz i am living on south america :s plz if someone know a solution about this i need your help.
Click to expand...
Click to collapse
Firstly we need to make sure we're talking about the right device. Go to the bootloader and tell us what it says.
To get to the bootloader do this: hold power button and volume down button together, the button lights will start blinking, when the lights stop blinking and the screen turns off, let go of power but keep holding volume down until it reaches bootloader. Now tell us what it says.
Also, have you modified the phone in any way? Is your bootloader locked or unlocked? Are you rooted? Do you have s-off or s-on?
Sent from my Evita
Ok, so I had recently flashed MIUI sense based, I realized it wasn't for me so I restored my backup of TrickDroid 6.1. After doing this I went through and decided to delete some some stuff because my space was getting low (not 5mb low, more like maybe 1/2gb), I went to delete the MIUI v4 2.7.6 file and the phone appeared to go into standby... I tried to wake it up again with no luck. Plugging it into a charger does nothing, no red light; no green light. I'm unable to get into bootloader mode, no matter how long I hold down the "down volume + power" combo or any variation of it.
I need one of the gurus to help please !!!!
maybe post this in general or q&a?
any adb connection? if it's in standby then you may be able to move along to the next step
could just be a SOD (sleep of death)
Sent from my HTC One S using xda premium
calming said:
Ok, so I had recently flashed MIUI sense based, I realized it wasn't for me so I restored my backup of TrickDroid 6.1. After doing this I went through and decided to delete some some stuff because my space was getting low (not 5mb low, more like maybe 1/2gb), I went to delete the MIUI v4 2.7.6 file and the phone appeared to go into standby... I tried to wake it up again with no luck. Plugging it into a charger does nothing, no red light; no green light. I'm unable to get into bootloader mode, no matter how long I hold down the "down volume + power" combo or any variation of it.
I need one of the gurus to help please !!!!
Click to expand...
Click to collapse
Did u try hold the power? It'll reboot?then hold volume down about 10s.it should go to bootloader
2nd Option: use all-in-one tool kit.it has a command to reboot.
And don't post question or help here.read the rule.
Sent from my HTC One S using xda premium
Sorry about posting in this section, I assumed I'd get a quicker response.
I tried the All-In-One Kit thing... doesn't work "error: device not found"
I cannot get the phone to power on at all, no bootloader, no splash screen, nothing recognized by my pc. I get a "QHUSB_DLOAD NO DRIVER FOUND"
Thoughts?
calming said:
Sorry about posting in this section, I assumed I'd get a quicker response.
I tried the All-In-One Kit thing... doesn't work "error: device not found"
I cannot get the phone to power on at all, no bootloader, no splash screen, nothing recognized by my pc. I get a "QHUSB_DLOAD NO DRIVER FOUND"
Thoughts?
Click to expand...
Click to collapse
If it can't boot or use adb command.i think u should contact with HTC for helps,or at least where u buy the mobile. And of couse u still have Warranty.
It may be a hardware problem.We here can only try if it is a software problem.at ur position,the device can't be recognized by Computer/Laptop (before this,it worked well right?),then i think bad luck.
Don't be despair, it'll have some way to solve.
Sent from my HTC One S using xda premium
Sorry to tell you man the same thing just happened to me. I just got a replacement from T-Mobile. You will not get that thing back on. Just call T-Mobile and tell them it won't power on nor will it charge. It's funny because I was adding music to mine when it happened. If it happened the same way mine did then you will notice it was really hot when it shut off. The MDJ kernel overheated the Processor and killed it. Once that happens the device is a useless brick. I'm trading my replacement for another phone because this phone happens to overheat a lot.
Azuske said:
Sorry to tell you man the same thing just happened to me. I just got a replacement from T-Mobile. You will not get that thing back on. Just call T-Mobile and tell them it won't power on nor will it charge. It's funny because I was adding music to mine when it happened. If it happened the same way mine did then you will notice it was really hot when it shut off. The MDJ kernel overheated the Processor and killed it. Once that happens the device is a useless brick. I'm trading my replacement for another phone because this phone happens to overheat a lot.
Click to expand...
Click to collapse
Yup, same here, overheated while using fpse, died suddenly and wouldn't even charge. Tmo overnighted a replacement.
Sent from my HTC VLE_U using Tapatalk 2
Thanks everyone for the help... At least I know what I have going on... Already started re-downloading a buttload of stuff to get back on track. I don't normally backup my Nandroids or my TB files to my PC, maybe I should start.
Going tomorrow to the Tmo store to get the replacement sent overnight.
Thanks again.
Moved To Q&A
Please post in the correct section.
this exact thing happened to me twice. i dont get it. is it overheating or whats going on? it happened twice both times i was deleting a very large file 100 mb plus i have to call tmobile in the morning =/
---------- Post added at 08:29 AM ---------- Previous post was at 08:29 AM ----------
no one else knows of anything that might be able to revive my phone?
just read that it is most likely the processor a couple post up. =/ damn. im going to look into trading this phone for another
this has just happenmed to me to. was fully charged thought battery was low after it switched off managed to reboot see battery was full before crapping out completely. wont charge wont recognize in adb. Really dissappointed in my loss of data. i also imported this phone and had it running on att anyone know how good htc warranty service is bc tmobile is a no go for me
phone was all working fine until i guess attempted to install wrong version of CM10 said installed thru CWM did i said reboot then phone screen went black and now wont power on no Samsung logo or nothing just black but when i plug in to pc i hear the sound like looking for drivers for a device plugged in. anyone have them happen and if so any fix? before i do a insurance claim...
Jacob2kD said:
phone was all working fine until i guess attempted to install wrong version of CM10 said installed thru CWM did i said reboot then phone screen went black and now wont power on no Samsung logo or nothing just black but when i plug in to pc i hear the sound like looking for drivers for a device plugged in. anyone have them happen and if so any fix? before i do a insurance claim...
Click to expand...
Click to collapse
Guessing it's more of a soft brick and recoverable. Where did you get CM10 and what version of cwm? Unlocked bootloader?
Jacob2kD said:
phone was all working fine until i guess attempted to install wrong version of CM10 said installed thru CWM did i said reboot then phone screen went black and now wont power on no Samsung logo or nothing just black but when i plug in to pc i hear the sound like looking for drivers for a device plugged in. anyone have them happen and if so any fix? before i do a insurance claim...
Click to expand...
Click to collapse
You'll probably have to go into download mode, and odin back to stock.
Yeah it's probably a soft brick, if you can get into odin (power + home + vol UP) you should be good to flash back a stock w/root and be back up and running.
I just did this when I had to flash back from a bad download of the synergy nightly....or possibly it's a problem with the nightly, a good lesson to actually check the md5 on a download...
how will i know when in download mode if screen is black..it was CM10 that showed up on rom manager at one point CM10 konstakang JELLYO
If you pit it no dl mode while Odin is open and phone plugged in ...it should show up in the "com port area of Odin. I think even if you can't see it on the screen. It worked with my Charge. Give it a shot
Sent from my SCH-I535 using Tapatalk 2
Mike you have any ideas for me to try?
I've had similar issue in the past if you have sound when plugged in its probably just a display issue you will have to try to put it into download mode blind and flash stock unfortunately will have to set up from scratch but should do the trick
Sent from my SCH-I535 using Tapatalk 2
Power + home + volume up to get into download mode. It should show something on the screen if not try what was said above and put it in d/l mode with Odin opened and the phone plugged in.
I don't want to start some heated debated but I don't see the difference in "self bricked" and "self dropped into a toilet" when it comes to insurance. Now warranty that's a different story.
I have to disagree and agree with the guy who says these people are xxxxbags. I wouldn't go so far as to call people who want a working phone as a "xxxxbag" a bit irresponsible yes, but to go so far as calling them xxxxbags I think is a bit harsh.
On the other side of the argument are the people who act as if Verizon or Samsung are obligated to replace a bricked phone. You don't throw your phone around like a football then expect it to be replaced for free. People who flash custom roms, etc (including myself) are fully aware of the risks they are taking by doing so and should take the responsibility to try and fix it themselves. If they can't figure out how to fix it with the help of all the brilliant minds on XDA, Verizon won't have too much luck either.
mikeew83 said:
I've had similar issue in the past if you have sound when plugged in its probably just a display issue you will have to try to put it into download mode blind and flash stock unfortunately will have to set up from scratch but should do the trick
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
thats kinda weird if its just the display when all was working just fine then went blank after CWM said install successful until i did a reboot :X.. i don't expect a "free" replacement" insurance isn't free anyways $99 deductible
mikeew83 said:
**** you god tell some one there scum bag for wanting a working device get your holier than thou **** ass self out of here people like you are why xda loses member base
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
You're an idiot. You break your phone YOU take the responsibility for fixing it.
---------- Post added at 07:26 PM ---------- Previous post was at 07:22 PM ----------
UOTE=JBO1018;30370951]Power + home + volume up to get into download mode. It should show something on the screen if not try what was said above and put it in d/l mode with Odin opened and the phone plugged in.
I don't want to start some heated debated but I don't see the difference in "self bricked" and "self dropped into a toilet" when it comes to insurance. Now warranty that's a different story.[/QUOTE]
.
It's home+voldwn+power then vol up to continue.
And one is and accident and one is self inflicted. If you don't see the difference I can't help you:victory:
Nothing but a flame war here
It is against XDA rules to discuss ways to fraud the carrier into warranty replacement
You brick it, you bought it. That is what insurance is for.
Admit you messed up your phone and pay the deductible
Thread closed
Thank you for your cooperation
NFNM
So, while I'm no expert I'm not new to rooting and flashing. Did it quite a bit on my older Droid Inc 1, and have performed a few on my new SG3.
I have 3 backed up ROMs on my SD, Synergy, Beans and CM10. I was running Synergy and decided to give CM10 another shot to see if I could figure out what was killing NFC. So, flashed it up with ROM Manager (Used Odin previously) and everything went swimmingly. ROM was running, NFC was working, all my apps were reinstalled, no problems.....
Decided to see if I could get Wallet working on this install, so flashed it in, made the changes to build.prop and rebooted.
Heeerreeee's where the trouble started. Part way through the reboot the phone just shut down. Completely. 100%. Dead.
I had 87% battery when I started so it 'shouldn't be a battery problem. No power, no LED when I plug in the charger, no vol-up, home, power to get into recovery.
One interesting thing did happen while I was trying to get the phone up, I removed the battery for a bit, and plugged the USB cable in and got a red charging light. Put the battery back in, light still there. 1 minute later, light goes off and still nothing happening with the phone at all.
Anyone have any ideas beyond all the stuff I've given a shot to?
Will it show up when plugged in on your CPU?
Sent from my Nexus S 4G using xda app-developers app
nexus995743 said:
Will it show up when plugged in on your CPU?
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Unfortunately not. Only thing that seems to show up is in the device manager, a QHSUSB_DLOAD device that's banged.
Hmmmm
Sent from my Nexus S 4G using xda app-developers app
nexus995743 said:
Hmmmm
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
Well, I called Verizon and they've shipped me a replacement. I guess throwing all my bit and pieces into a new main body should work fine...
Oh no. Another one sending a phone back because of rooting. That's why they lock bootloaders.
Sent from my Galaxy Nexus using xda app-developers app
+1
Have you tried borrowing someone's battery to see if you can also least boot? I have four samsung batteries for the S3 and would consider sending it to you before getting a replacement. I think the cost of a battery is $3 on Amazon.
Sent from my SCH-I535 using xda premium
The reasons were different but i had the same thing happen to me, my phone wouldn't boot, wouldn't show up in the computer. Nothing, i tried my wife's battery, no change there either. I left it on the charger overnight and tried turning it on in the morning and after messing with it it came back on. Haven't had an issue since. Don't know what caused it, the phone just freaked out, turned off and wouldn't turn back on.
You can also try the resistor trick to see if that will bring your phone back. Here is a cheap way to do it.
http://hackaday.com/2012/09/03/saving-a-bricked-phone-with-a-pencil-lead/ Otherwise you can go to radio shack and pick up a resistor.
If Verizon sends you your phone back cause you messed with it, there is a brick repair service for like $60 bucks PM for the link if it comes to that.
Congrats on the new phone
Sent from my Nexus S 4G using xda app-developers app
nexus995743 said:
Congrats on the new phone
Sent from my Nexus S 4G using xda app-developers app
Click to expand...
Click to collapse
hehe.. I can't say I was pleased with having to go that route, (can't stand being defeated by electronics) but all in all I can't imagine a simple software change causing the entire unit to just go dead. Not booting properly, or locking up and such, sure... but not just dead.
By this morning I had tried another battery (a friend has an SG3 also) to no effect, but I didn't try leaving it plugged in overnight. I did check the battery with an external charger I have and it was showing fully charged....
So, I'll get a replacement and stay away from CM10 at the very least.
**ihavenewnike - Not sure why you're on an android developers forum really...
Ok, so the new phone got here at about 12:30. Plugged all my stuff into it and it fired right up.
Rooted and unlocked it, put my latest Synergy backup (1 day old) on the SD card and restored it.
Ahhhh... It's just like it never left. :victory:
keno1964 said:
Ok, so the new phone got here at about 12:30. Plugged all my stuff into it and it fired right up.
Rooted and unlocked it, put my latest Synergy backup (1 day old) on the SD card and restored it. . .
Click to expand...
Click to collapse
. . . and then the display went black and it wouldn't power on! What the heck?!
. . .
Oh, sorry: I was just imagining a funny ending to this topic.
- ooofest
ooofest said:
. . . and then the display went black and it wouldn't power on! What the heck?!
. . .
Oh, sorry: I was just imagining a funny ending to this topic.
- ooofest
Click to expand...
Click to collapse
Don't like you.......
Same thing happened to me when I tried to mess with the NFC hack on my SGS III.
What saved me was a USB Jig I happened to have handy when I...accidentally... soft bricked a friend's Samsung Captivate a few months back. The USB Jig is used to put the SGS III into download mode when all else fails that tiny little gadget saves the day.
tekrhino said:
Same thing happened to me when I tried to mess with the NFC hack on my SGS III.
What saved me was a USB Jig I happened to have handy when I...accidentally... soft bricked a friend's Samsung Captivate a few months back. The USB Jig is used to put the SGS III into download mode when all else fails that tiny little gadget saves the day.
Click to expand...
Click to collapse
I have looked into those and will most likely make one very soon. (I think I have everything I'd need, just may need to cobble some resistors together).
Couple of things I noticed throughout this 'process', regarding the CM10 (9-15 nightly) ROM, NFC and google wallet....
At first install of CM10 I noticed that NFC was active and working normally. It could read my tags without issue. After Wallet was installed though, NFC disappeared. It wasn't just disabled, it simply wasn't there any more. It was after noticing this that I decided to reboot, at which point my original problem started.
The reboot never came close to completing though, it shut down before it actually made it to the 'boot' phase, as in, while it was shutting down.
The actual cause of the power off is still a mystery to me, as I can't see a simple app change causing hardware failure.
So you bricked your phone, just like a few of us did yesterday.
What did you call Verizon saying in order for them to send you a new phone?
AB_ said:
So you bricked your phone, just like a few of us did yesterday.
What did you call Verizon saying in order for them to send you a new phone?
Click to expand...
Click to collapse
I told them what happened, just left out a few bits of info.
"I rebooted it, and it never came back on." and that was that.
Nice.
I should have gone that method, but ended up paying for the repair service from MobileTechVideos
A friend has the qhsusb-dload showing up as well.. phone won't turn on.. flashed a bad kernel or rom I forget which.. red light comes on.. that's it.. its a Verizon i535 .. tried the resistor jig and nothing happens.. any ideas to fix?
---------- Post added at 12:03 PM ---------- Previous post was at 11:59 AM ----------
Guess he had aokp rom then flashed neak kernel and that's when it died..
I was surfing the forums here and seen this and thought I would post it as it might help with some soft bricks, when fastboot is not wanting to work.
http://forum.xda-developers.com/showthread.php?t=2198223
I take no responsibility if you try that and it damages your device.
alldoom65 said:
I was surfing the forums here and seen this and thought I would post it as it might help with some hard bricks
http://forum.xda-developers.com/showthread.php?t=2198223
I take no responsibility if you try that and it damages your device, but if it is hard bricked it is not like you have much to lose.
Click to expand...
Click to collapse
That's a solution for a soft brick, not a hard brick.There's a reason why it's called hard brick dude, you can't recover from it unless you're tony stark and are able to patch the blown e-fuses
Sent from my MB865 using xda premium
Yeah after taking a closer look that does look more like a softbrick fix not a hardbrick fix.
Sorry everyone that was my bad, I asked alldoom65 to post this thinking it would help someone out of a hard brick, but I did not read close enough to see that the guy was stuck on M logo.... so everyone can slap me, not alldoom65.
Hey alldoom65, maybe change the title to indicate that this post is an alternate way out of a softbrick, when rsd does not see the phone, and you do not have the scripts. Not a hardbrick fix. you can edit the title in the go advanced button in the edit screen, I think.
Again sorry everyone, especially to you alldoom65.
jimbridgman said:
Yeah after taking a closer look that does look more like a softbrick fix not a hardbrick fix.
Sorry everyone that was my bad, I asked alldoom65 to post this thinking it would help someone out of a hard brick, but I did not read close enough to see that the guy was stuck on M logo.... so everyone can slap me, not alldoom65.
Hey alldoom65, maybe change the title to indicate that this post is an alternate way out of a softbrick, when rsd does not see the phone, and you do not have the scripts. Not a hardbrick fix. you can edit the title in the go advanced button in the edit screen, I think.
Again sorry everyone, especially to you alldoom65.
Click to expand...
Click to collapse
Jim!!!So it's true then.You never left the A2 forum.You're just taking a vacation and when that ends you're planning on making an epic comeback right???
Please say yes
And rest assured you're the last person anyone on this forum would wanna slap.
May the -Mass times Acceleration- be with you...
deveshmanish said:
Jim!!!So it's true then.You never left the A2 forum.You're just taking a vacation and when that ends you're planning on making an epic comeback right???
Please say yes
And rest assured you're the last person anyone on this forum would wanna slap.
May the -Mass times Acceleration- be with you...
Click to expand...
Click to collapse
I never fully left, just been taking a back seat.
I am working on buying an engineering version of the atrix2 with an unlocked bootloader, so... We'll see.. I might be back with a vengeance, soon.
P.S. I love your signature
jimbridgman said:
I never fully left, just been taking a back seat.
I am working on buying an engineering version of the atrix2 with an unlocked bootloader, so... We'll see.. I might be back with a vengeance, soon.
P.S. I love your signature
Click to expand...
Click to collapse
Lol thanks and here I thought no one would understand.
May the -Mass times Acceleration- be with you.
So my A2 seems really dead for some reason. I had system 1 in BMM as Stock ICS rooted. System 2 blank and 3 PAC milestone RC1. Flashed a 4.3 font on system 1 accidentally and lost BMM. Had a day to get to a computer and try the windows.batch cuz not enough time for FXZ. No avail. Rebooted a couple times and now its a blank. Won't get into fast boot barely unless I have it plugged in while volume up n down while stuck on M. Plugged into PC I get the white led. But wall AC only brings me to M. Not battery charging. I don't get it. It can't be bricked. Can battery be done for? Wtf happened? I'm currently trying to get a Motorola branded USB wall AC charger to see if I can get it to at least charge to 5% and give the windows.batch a go again...
Sent from my ADR6350 using xda app-developers app
A2Trip said:
So my A2 seems really dead for some reason. I had system 1 in BMM as Stock ICS rooted. System 2 blank and 3 PAC milestone RC1. Flashed a 4.3 font on system 1 accidentally and lost BMM. Had a day to get to a computer and try the windows.batch cuz not enough time for FXZ. No avail. Rebooted a couple times and now its a blank. Won't get into fast boot barely unless I have it plugged in while volume up n down while stuck on M. Plugged into PC I get the white led. But wall AC only brings me to M. Not battery charging. I don't get it. It can't be bricked. Can battery be done for? Wtf happened? I'm currently trying to get a Motorola branded USB wall AC charger to see if I can get it to at least charge to 5% and give the windows.batch a go again...
Sent from my ADR6350 using xda app-developers app
Click to expand...
Click to collapse
Yup has happened to me before(I think).It's a soft brick.Get more juice in your battery and then fxz back or use the windows patch.You should be just fine..
Good luck..
deveshmanish said:
Yup has happened to me before(I think).It's a soft brick.Get more juice in your battery and then fxz back or use the windows patch.You should be just fine..
Good luck..
Click to expand...
Click to collapse
That's happened to me too. Had to use the macguyver battery charge method to get it back going again.
Brought to you by time and relative dimensions in space.
1BadWolf said:
That's happened to me too. Had to use the macguyver battery charge method to get it back going again.
Brought to you by time and relative dimensions in space.
Click to expand...
Click to collapse
LIKE A BOSS! It's up and running! Thanks for the info dude...I did sum crazy surgery and took a huge gamble doing this but it worked like a lucky charm! AWESOME! Letting it charge cuz after the FXZ It's at 0%! Crazy! Letting it get to 100 before I even try rooting it. So glad I got my laptop back today too!!!
This is what the cord looked like after cutting and seperating/taping. I'm keeping this thing just in case I ever need it again! lol!
Sent from my MB865 using xda premium