Yup, another NEWB having trouble looking for help. Have a rooted ATRIX 4g, (ADB/Fastroot method), but am away from home, so do not have access to the PC with drivers, ADB, etc. on it. I am running stock ROM, took the last OTA update and retained Root using Rootkeeper. I did not unlock the bootloader. Today phone started soft-boot like symptoms after I downloaded an app (Mayo Clinic PAtient App) partially installed it - app installed, but was waiting on info to login, when phone locked and I pulled battery. At this point, phone will not boot. It goes through Motorola Dual Core to Rethink possible, but then times out and reboots before loading OS. I have downloaded Motorola Drivers, I can bring up RSD, I can get to Fastboot menus. Any and all help appreciated!
Tried Fastboot Andriod Recovery, got white Triangle with yellow exclamation point. Somebody please tell me I wont have to do a factory reset. :crying: At least I have my usb battery charger with me, charging up a battery just in case.
Worst timing ever - all the relatives have my cell phone number for updates on my Wife, we are at Mayo Rochester all week.
Another odd thing - can't get the phone into safe mode.
Damn I am stubborn. After repeated efforts - and we're talking about 90 minutes here, I found by holding down the up/down vol buttons at the same time and holding them all the way through the painfully slow Rethink possible, past the long vibrate, all the way to home screen, I could get into safe mode. First time the phone still rebooted. Second time could not get past lock screens, third time I got in and uninstalled last couple programs I installed and the phone boots normally again. Hope this helps others.
Related
Hello, any advice/suggestions would be appreciated!
After doing the update process (Root v2) I went back into TiBu and started freezing the bloat, and I kinda got carried away (I didn't even know what everything I froze was... stupid! To any other dummies out there: just because it has motorola in the name, don't assume it's bloat, apparently).
Then I left TiBu and turned off my phone. Upon reboot, it brought up the red moto dual core thing, and then it did the first 2-3 seconds of the red moto dual core with red wavy animations around the circle, but then suddenly stopped and the red light began flashing.
Holding volume up and volume down on subsequent reboots brought up different messages about starting some kind of protocol and fast boot, respectively, but after five minutes I figured that they were just frozen too.
So I f'ed it up. Right now I'm just charging my phone to do the "[Guide] Flash SBF to Atrix" directions. But INSTEAD, is there any way I can just defrost what was frozen in tibu without going through all that? Not a huge deal, but I'd rather not do the SBF Flash (looked lengthy to a noob like me) AND the update process again.
Thanks!
Ah, found this link that explains how to use super one click to "recover from a soft brick caused by freezing needed apps or services."
I need to "run shell root from superoneclick in Early USB Enumeration." I have a mac, so I downloaded the drivers and super one click onto a ****ty, borrowed netbook. The problem is I don't know how to run it in early usb enumeration, and even running s.o.c. seems problematic because my atrix starts booting up when connecting to the ****ty netbook, and gets itself nice and soft bricked/frozen/stuck.
I really don't want to keep guessing and doing battery pulls - I fear eventually my Atrix will get tired of this mistreatment and REALLY brick itself for good... if anyone has any info, please help!
So yesterday I was in a call with low battery when it shut off. Normally not a problem, just plug it into the wall for a while. Well when I tried to turn it on, it wouldn't even boot up. It was stuck at the red M logo. The LED showed amber colored as well. I left it plugged in and the light remained amber until 90% battery, where it turned green.
I tried to turn it on and its been stuck on the red M logo. Its been stuck for more than 12 hours now.
I CAN access fastboot, android recovery, etc. I already tried wiping the cache and even did a factory reset. Still wont work.
What can I possibly do? I luckily have a backup phone, but I've had my photon for less than a month, no warranty, and I'm a novice Android user. Any help would be greatly appreciated.
MooseV2 said:
So yesterday I was in a call with low battery when it shut off. Normally not a problem, just plug it into the wall for a while. Well when I tried to turn it on, it wouldn't even boot up. It was stuck at the red M logo. The LED showed amber colored as well. I left it plugged in and the light remained amber until 90% battery, where it turned green.
I tried to turn it on and its been stuck on the red M logo. Its been stuck for more than 12 hours now.
I CAN access fastboot, android recovery, etc. I already tried wiping the cache and even did a factory reset. Still wont work.
What can I possibly do? I luckily have a backup phone, but I've had my photon for less than a month, no warranty, and I'm a novice Android user. Any help would be greatly appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1393519
Click on the software and tools link and use rsd lite to reflash the stock os onto the phone. If that doesn't work I would take it to the sprint store.
I assume you tried pulling the battery?
I'm downloading SBF now. Hopefully it works, because I live in Canada and we don't have Sprint stores.
And YES, I tried pulling the battery. Multiple times. With every combination (eg, plug in, turn on, then insert battery; put in battery, turn on, then plug in, etc)
the sbf should work but may i ask how you managed to brick your photon? when i just got mine i did everything wrong and i never got even a soft brick so i'm interested what i didn't mess up haha
Quick question: I should be downloading the most recent? Will it make a difference?
And damn, did I actually brick it?? I'm pretty new to this thing, this is my first Android and I've had it for less than a month...
And nothing should have triggered it. I added another line in build (ro.media.setting.1080p or something) and I added another setting in /system/etc/mediaprofiles.xml. I was trying to add 1080p to the camera (unsuccessfully). I didn't remove anything, and even after a reboot it was fine.
It wasn't until the battery died, where it stopped booting up. Just my luck :/
You should probably choose one of the newer ones, just becasue of bug fixes, etc. If you happen to know what version you were running before then I'd choose that. I cant stress enough, make sure the one you download is for the Photon and NOT Electrify! And technically yeah that is a brick lol but its extremely hard to legit brick beyond repair a photon due to the fact that we have RSD Lite and SBF files to bring it back.
Strangely, I found a thread depicting the same problem that I had, although with the electrify. http://forum.xda-developers.com/showthread.php?t=14813
Anyways, the problem is fixed, by reflashing the SBF using RSD Lite, everything is back to normal! Well, almost, just have to restore my backup
Thanks so much for your help guys, I wouldn't have been able to fix it without you all!
can you fix a bricked phone??
My Photon has done the same thing! I rooted her and did the Bootstrap Recovery thing. Everything was kosher until I tried to load that stupid Beats Audio. Something happened between me flashing it and the reboot where it locks the phone. I tried to do the Android recovery screen, I wiped, I did about everything I could find. No bueno.
I followed this forum and clicked the software and tools link as instructed. I tried with RSD 5.6, and tried several iterations of SBF's located here and here. I was using SBF - 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-154_MR-3-CM.
It lets me go into boot mode, and when I try to flash the SBF it appears to go through, but it always fails at the end. Which, the posts state it will do, but my phone will not reboot afterwords. After trying everything I could for a couple days, I decided to just take it to a Sprint store. Mind you I've had this under 30 days, but longer than 14 so they stated it would have to be replaced. They tried to flash, but said they were getting stuck too.
I know that a replacement is pretty much the answer, but just wanted to check one more time to see if anyone had any other ideas, or could point me to other forums maybe? Appears I've done what few have been able to accomplish...brick this joker.
All,
I've been following posts on XDA since my original droid incredible days. I've rooted and maintained two phones, never have any issues.
Recently I purchased a T-Mobile Springboard (got a crazy promotion price through my company) which ran stock TMo Honeycomb. Eager to get ICS and eager to get rid of the power-on tmobile jingle, I installed the latest S7-302u firmware update from Huawei's website. I am aware that my device is technically S7-303u, but the update worked fine and I had little-to-no bugs. I am very pleased with this tablet.
Now here where I get stupid.
A coworker of mine then tells me that he has a S7-303u update.zip file that he can give me, which I don't object to. I give him my micro SD, he places the file in the 'dload' folder with 'unlmt.cfg'. I then reconsider my predicament, and decide that I'm happy with my current firmware, even if it's not made specifically for my tablet hardware version. If it ain't broke, don't fix it.
By the evening, I forget that the update file is on my SD card.
Before going to bed, I extinguish the battery and let it power down. I then plug it in the the wall and fall asleep.
Around 3 am (3 hours later) I was woken up to my springboard rebooting. Confused, I pick it up and see that it's in some kind of boot-loop. The screen turns on, but stays black, and then immediately powers down, and restarts. This process repeats indefinitely. I hold the power button down, trying to do a hard-reboot, but it doesn't seem t work. Then, after about 5 "holding the power button down for 10 seconds", the device reboots and I am graced with the gracious Huawei MediaPad logo.
The device automatically goes into recovery mode and installs the forgotten update.zip....
Now I'm pissed, specifically because I've lost my high scores in Trainyard Express and just because I now how to re-install all my apps. It's annoying, but it's not the end of the world. Or so I thought.
I use my tablet 75% of the time for reading through the kindle app, and on this version of ICS the kindle app doesn't work! So immediately I decide to revert back to the old S7-302u update that I originally had installed, following the same steps I did to manually update the device previously.
I now cannot, for the life of me, get this thing to boot into recovery mode. The only thing I can get this device to do is get to the "Enter into fastboot mode" screen by holding the power button and the volume+ key (the one closest to the power button).
A few other symptoms:
1. The device is set to quickstart mode by default and I don't see any option to deactivate it. The only way to get the device to actually "turn off" is to choose restart to hold the power button down for a hard reboot.
2. If I hold down the power button for ten seconds, I expect the device to power down and stay down. This is not the case. It always reboots immediately. I have no way of actually fully powering this device down (not counting the quick-start power-down).
3. No charging indication. I'm not sure if this is a hardware or software issue. My device will charge, but it does not give any indication on the screen or the battery icon.
Now I'm stuck wondering what to do. Did I ruin this device? I wanted to avoid rooting it because of the loss of 4G data, but now I'm afraid that I might need root-permissions to fix whatever I messed up.
Thanks in advance for your help.
Daniel
PS. Just so you all know my experience, I've rooted and maintained a droid incredible and currently, my galaxy nexus. I however, have no programming experience what-so-ever. I'm just good at following directions (usually).
What happens if you pull the micro sd card out? It should stop the boot loop (in theory). If the install didn't go through it should boot up normally to the previous version. In settings you can turn off FastBoot.
You might have to look at the sd card on a computer and either get rid of the unlmt.cfg from the dload folder and it shouldn't try to boot to the dload folder.
eurobass said:
All,
I've been following posts on XDA since my original droid incredible days. I've rooted and maintained two phones, never have any issues.
Recently I purchased a T-Mobile Springboard (got a crazy promotion price through my company) which ran stock TMo Honeycomb. Eager to get ICS and eager to get rid of the power-on tmobile jingle, I installed the latest S7-302u firmware update from Huawei's website. I am aware that my device is technically S7-303u, but the update worked fine and I had little-to-no bugs. I am very pleased with this tablet.
Now here where I get stupid.
A coworker of mine then tells me that he has a S7-303u update.zip file that he can give me, which I don't object to. I give him my micro SD, he places the file in the 'dload' folder with 'unlmt.cfg'. I then reconsider my predicament, and decide that I'm happy with my current firmware, even if it's not made specifically for my tablet hardware version. If it ain't broke, don't fix it.
By the evening, I forget that the update file is on my SD card.
Before going to bed, I extinguish the battery and let it power down. I then plug it in the the wall and fall asleep.
Around 3 am (3 hours later) I was woken up to my springboard rebooting. Confused, I pick it up and see that it's in some kind of boot-loop. The screen turns on, but stays black, and then immediately powers down, and restarts. This process repeats indefinitely. I hold the power button down, trying to do a hard-reboot, but it doesn't seem t work. Then, after about 5 "holding the power button down for 10 seconds", the device reboots and I am graced with the gracious Huawei MediaPad logo.
The device automatically goes into recovery mode and installs the forgotten update.zip....
Now I'm pissed, specifically because I've lost my high scores in Trainyard Express and just because I now how to re-install all my apps. It's annoying, but it's not the end of the world. Or so I thought.
I use my tablet 75% of the time for reading through the kindle app, and on this version of ICS the kindle app doesn't work! So immediately I decide to revert back to the old S7-302u update that I originally had installed, following the same steps I did to manually update the device previously.
I now cannot, for the life of me, get this thing to boot into recovery mode. The only thing I can get this device to do is get to the "Enter into fastboot mode" screen by holding the power button and the volume+ key (the one closest to the power button).
A few other symptoms:
1. The device is set to quickstart mode by default and I don't see any option to deactivate it. The only way to get the device to actually "turn off" is to choose restart to hold the power button down for a hard reboot.
2. If I hold down the power button for ten seconds, I expect the device to power down and stay down. This is not the case. It always reboots immediately. I have no way of actually fully powering this device down (not counting the quick-start power-down).
3. No charging indication. I'm not sure if this is a hardware or software issue. My device will charge, but it does not give any indication on the screen or the battery icon.
Now I'm stuck wondering what to do. Did I ruin this device? I wanted to avoid rooting it because of the loss of 4G data, but now I'm afraid that I might need root-permissions to fix whatever I messed up.
Thanks in advance for your help.
Daniel
PS. Just so you all know my experience, I've rooted and maintained a droid incredible and currently, my galaxy nexus. I however, have no programming experience what-so-ever. I'm just good at following directions (usually).
Click to expand...
Click to collapse
Thanks
What is the firmware version of S7-302u are you installed in your S7-303u?
Hey, I have the springboard and did the exact thing you did, somehow the stock recovery was all messed up, best bet is to install twrp using fastbood and cm10. just follow after_silences instructions here,
http://forum.xda-developers.com/showthread.php?t=2045808
[Edit]once you change tmo stock firmware you'll lose your 4g option(there my be a fix for this now)but you will be able to text and make calls over 2g, edge2 and 3g"no need for WiFi or side app"[Edit]
I bought an LG Mach LS860 (4.0.4 Ice Cream Sandwich) about a week ago, and I just found out about rooting. (This is my first Android.) I had no luck last night, but I tried today and I got it rooted.
Anyway... here's the problem: I was altering some settings with an app (I believe it was called Pimp My ROM.) and everything was fine. When I restarted, the battery was lower by about 7%. I figured the changes I made were the reason for this, so I went back and reverted them. However, when I restarted the phone this time, it wouldn't get past the boot screen. It would flash the Boost logo, go dark, then flash it again with an animation and a short vibrate. That's all. So I tried restoring the factory settings. (Volume down + power button, then power button and power button.) The phone went through and reverted settings, then rebooted. But THIS time, I got messages popping up like "Unfortunately, System UI has stopped." I believe there was something along the lines of "Unfortunately, Home has stopped." as well. On a layer below that at the bottom of the screen, there was another type of error. I think it had to do with voicemail. After the phone sat there for a bit as I looked online for a solution, the phone restarted again. Now it just goes to the problem from the beginning with the boot screen. My computer makes a noise indicating the USB is connected, but all my phone does is charge off it.
Any help would be much appreciated.
It's not necessarily that I'm inexperienced. I've done all sorts of flashing and things on PSP. Obviously Android is much more complex. But I know that it's not bricked unless it won't turn on at all. Because that's not a brick.
There's also very little (if any) development for this specific model. No one cares about the LG Mach because there are much more well-known phones. But I digress.
Please help. I'm extremely desperate to get this working again.
EDIT: I recently thought of another question. Would the hard reset erase all evidence of the root access? Considering I just bought the phone, I might be able to send it back. But obviously if they know I accessed the root, the warranty is void.
I have the D-800 AT&T LG G2, It was rooted with KitKat 4.4.2. After I rooted my phone, I tried several different ways to install TWRP onto it. I tried FreeGee, adb shell, and straight from TWRP App, nothing worked, because when I tried to boot into TWRP it would just come up with the LG Logo and "Secure Boot Error" and "Certification Error" or something like that, then be a blank screen. I then just held the power button to turn it off, and it would turn back on and run fine, no problem. I figured it never installed right, and so I left TWRP alone. I know you are not supposed to take an OTA after install TWRP, but thinking TWRP never installed on the phone, I took the OTA, and now it will do the "Error" messages and blank screen, but my power off, power on trick doesn't work anymore. I can boot into Recovery Mode, but when I do a Factory Reset, the screen just goes blank. I have tried to put it into Download Mode by pressing Volume Up + Power when hooked up to a PC, but nothing happens. I feel as though its a tough brick. Please Help!
Dirk1616 said:
I have the D-800 AT&T LG G2, It was rooted with KitKat 4.4.2. After I rooted my phone, I tried several different ways to install TWRP onto it. I tried FreeGee, adb shell, and straight from TWRP App, nothing worked, because when I tried to boot into TWRP it would just come up with the LG Logo and "Secure Boot Error" and "Certification Error" or something like that, then be a blank screen. I then just held the power button to turn it off, and it would turn back on and run fine, no problem. I figured it never installed right, and so I left TWRP alone. I know you are not supposed to take an OTA after install TWRP, but thinking TWRP never installed on the phone, I took the OTA, and now it will do the "Error" messages and blank screen, but my power off, power on trick doesn't work anymore. I can boot into Recovery Mode, but when I do a Factory Reset, the screen just goes blank. I have tried to put it into Download Mode by pressing Volume Up + Power when hooked up to a PC, but nothing happens. I feel as though its a tough brick. Please Help!
Click to expand...
Click to collapse
Bump Please. Same Exact Problem With Me, Rooted, Couldnt Get A Recovery Installed (Even Though I've Literally Been Doing Custom ROMs Since The G1 Released) And As Of The Other Day, AT&T Kept Bugging Me To Update To 4.4.2, Even Though I Was Already At 4.4.2. I Kept Declining, But Today My Battery Died, And When It Turned On, It Automatically Installed It, And I'm Getting The Same Errors And Everything.
Send It In
dotjsx said:
Bump Please. Same Exact Problem With Me, Rooted, Couldnt Get A Recovery Installed (Even Though I've Literally Been Doing Custom ROMs Since The G1 Released) And As Of The Other Day, AT&T Kept Bugging Me To Update To 4.4.2, Even Though I Was Already At 4.4.2. I Kept Declining, But Today My Battery Died, And When It Turned On, It Automatically Installed It, And I'm Getting The Same Errors And Everything.
Click to expand...
Click to collapse
I could not find a fix for this problem. Instead, I sent it back saying that it updated automatically and then it didn't work. They can not tell that you have rooted it, because it is so messed up, SO DONT TELL THEM THAT YOU DID! It'll take about 2-3 weeks foe it to be sent back. It'll be free as long as you are under warranty. Just talk to a customer service person on LGs Online Customer Service people. I hope this helps you out!
Dirk1616 said:
I could not find a fix for this problem. Instead, I sent it back saying that it updated automatically and then it didn't work. They can not tell that you have rooted it, because it is so messed up, SO DONT TELL THEM THAT YOU DID! It'll take about 2-3 weeks foe it to be sent back. It'll be free as long as you are under warranty. Just talk to a customer service person on LGs Online Customer Service people. I hope this helps you out!
Click to expand...
Click to collapse
Thanks For The Suggestion. Ironically, I Was Just At The AT&T Store Because They Were Selling Otterbox Defenders For 25 Bucks, And I Told The Guy That My Phone Was Rooted. I'll Have To Go To Another Store. I'm Working On The Linux Fix As We Speak, So Hopefully I Wont Have To Send It In.
dotjsx said:
Thanks For The Suggestion. Ironically, I Was Just At The AT&T Store Because They Were Selling Otterbox Defenders For 25 Bucks, And I Told The Guy That My Phone Was Rooted. I'll Have To Go To Another Store. I'm Working On The Linux Fix As We Speak, So Hopefully I Wont Have To Send It In.
Click to expand...
Click to collapse
I have tried the Linux fix, that didn't work for me, hope it works out for you. Talk to LG, they are the ones who will fix it. You will have to send it to them. I used United States Postal Service, it costed me like 9 dollars, which isn't bad. Good Luck!