Ok, So right now im running snap 7.6 bfs without turbo enabled. earlier today i tried to enable turbo, and it worked, phone rebooted, booted back up and it was all good. I turned off my phone again and hooked it up to my wall to charge it..hours later i turned it back on and it got stuck on the white evo screen.
Last week i did the same thing i mentioned above, only difference was that when i enabled turbo, i enabled it the moment after flashing the rom with the failsafe install method. I ended up with the same result stated earlier too, after turning the phone off and back on it would get stuck on the white evo screen.
why is that happening? I was running a CM nightly last week and im running CM nightly 116 now, i know some people have turbo running on that nightly...i just cant seem to get it working on my phone now. I need help.
Ok, first plug your phone into your computer and run adb logcat to see where it's getting stuck. Also try to boot into recovery to reflash the kernel. Let us know what errors it's getting and looping at in logcat.
--Swyped from my Snappified EVO!
Related
Ive been trying to flash MAG and what not so i could flash droid. Aanyways the first time i tried to flash mag and hspl it would get stuck at the tmobile screen, then i reflashed stock and tried it again, same thing happened. so i reflashed back to stock again. Now i installed hspl again, and this morning when i tried to flash mag, it didn't fully responde.
I connected via activesync, ran the ruu. it recognized the phone, rebooted it to the tri color screen, then the program shows status bar for flash, my HD2 shows the status bar, but Neither of them move from 0%.
the phone powers on and im able to use it, but it wont communicate with my computer once it hits that status bar.
Any idea?
hopefully it can be fixed
No one wants to chime in?
Nevermind, don't know what happened over night, but just got android nand done...
hehe, see? no need for any responses! and doesnt it feel better to fix it yourself?? evening flashing is dangerous, ive pulled the usb, pulled the battery, flashed the wrong roms, allsorts, late at night.
oh no, it'd be great if infact i did fix it myself... but it fixed itself over night, so im out ruled on that one.... it hates me.
okay i almost just bricked my hero i was playing around with different prl/radio combos again and when i flashed the 2.2.27 radio using cm witch i do all the time. first it updated the radio image succes reboot now and i did. then it went to the usual black screen with the android guy but it turned of and didnt reboot so i turned it back on and got to the splash screen then it immediately powered of again. so i tried to reboot to recovery and same thing. then i went to hboot and pressed home to get to recovery. so at this point im starting to panic a little because wouldnt have internet access on my computer without my phone,but i remembered i still had the 2.2.27 ruu on my computer and i went to fast boot usb but nothing poped up on my computer i heard the notification noise though so i tried the ruu anyway and luckily it worked! so from there my phone was able to restart normally after the ruu finished and i was able to z4 it and use rom manager to install recovery. so all is well now im just wondering if this has happened to anyone else doing a normal radio update because nothing like this has ever happened to me before and im definitely going to be more careful for now on lol.
dude you crack me up.. at least you have a computer to do all of this stuff at.. thats why i dont flash radios, i do most of what i do on phone, so near bricks put me without a phone for a while.. and i cant have that.. thankfully i havent near bricked my phone in like 6 months (knock on wood)..
yea that was a close call for sure lol.
I unsuccessfully tried to fix my friends moto Droid x after he ran out of battery while flashing a rom. What a retard.
Sent from my HERO200 using XDA App
All this just to get a better signal lmao wow real close call
®patience is a virtue©
This is wife's phone. I was doing regular App Market updates for her installed apps. After they were complete got an error message, don't remember exactly what, but rebooted... Phone then went into a boot loop... It would boot all the way up to the lock screen then reboot again. I went in and wiped both cache's with no success. Went back into recovery and did a set factory defaults and now I am dead in the water...
I get to the Bootloader screen and it tells me Err:A5,69,35,00,27 and I have done everything but stand on my head to fix. I have re-SBF'd from multiple computers, using different SBF versions, driver versions, and RSD Lite versions including multiple bootable Linux CD's with embedded SBF. All resulted in getting the darn ERR:A5,69,35,00,27.
The only way I ever got anything different was to flash 1.13.604 and then I got an error message Err:A5,70,70,00,1F.
After that, if I SBF the newer version, I go right back to original error.
I tried a suggestion from another thread to download the system and full sbf files for 340. I flashed the full, got error... Then flashed system, still get error.
I am using RSD Lite 5.4 on Vista 32 with UAC disabled (full admin mode), latest Moto drivers as of this post. Again, I have tried all of the versions of bootable linux SBF's as well. All yield the same result.
Wife's phone, she is very unhappy with me, and if I don't get her back up and running, I guess I will be dropping $500 on a new phone, as she is still under contract. If Mama ain't happy, I sure ain't getting any! LOL!
It seems to me that you've tried everything possible.
Your best bet now would be to take it to Verizon, if it's still under warranty.
Sent from my DROIDX using XDA App
Out of warranty by 2 months.
I actually have two of these phones, and I was able to figure some information out here. I wanted to see if I could get my working Droid X into Stock Recovery, and low and behold it wouldn't go in either. I did some searching around and found that some ROM's were wiping out the stock recovery. I found this file dxgb_recovery_patch.zip and downloaded it and flashed it in Clockwork Recovery and that fixed the Stock Recovery on my working phone.
However, since my wife's Droid X is bootlooping, I can't access Stock Recovery or Clockwork Recovery. I feel like I am chasing my tail here. I need to wipe the data/factory reset, but I can't get there because I don't have Stock Recovery. I can reinstall Stock Recovery if I have Clockwork Recovery, but I don't have Stock Recovery to install Clockwork Recovery... Round and round I go...
There absolutely must be a way to get the Stock Recovery reinstalled from the state I am in.
what rom was the phone running when you had the original issue?
Apex 2.0 RC4
Good ROM, but it appears to torch stock recovery. I ended up having wife call and plead stupidity with Motorola. They are exchanging phone.
Still don't feel bad. Would have been able to fixed If they would unlock the damn billiard.
I have the same Problem with my Defy+ what can i do?
I have the exact same issue. Have tried all the sbf methods, still getting the error :A5,69,---, I was on MIUI prior to this. When I boot the phone back up I get the motorola M but then it brings me right back to bootloader and the error. I'm guessing stock recovery is gone.
Anybody find a fix to this yet. I am about to go back to Verizon, but wanted to fix it myself if at all possible, cause I have had my phone for a year and a half so I doubt they will help me out and don't have the money for a new phone right now.
Are you holding down Home and both volume buttons with power at boot to get to stock recovery?
*I have had several phones and don't remember exactly so you may have to hold Home and vol- only.
Jiggity Janx said:
Are you holding down Home and both volume buttons with power at boot to get to stock recovery?
*I have had several phones and don't remember exactly so you may have to hold Home and vol- only.
Click to expand...
Click to collapse
Yes, on the droid x its just home and the power button release the power button when you see the m and then you hit search once the droid pops up. Instead of seeing the droid it takes me to the bootloader screen with the above error message. The way to bootloader is volume button camera button and power. Which that still works and I have tried several sbf methods with none working. I didn't know if it was an issue that may have been mentioned above about the stock recovery being missing now since I was on MIUI 2.1 wizards verison. I didn't know if there was a way to get stock recovery back on the phone cause sbf doesn't seem to work. I really have no clue at this point. But full disclosure I have done quite a few sbf's and this is the first time I've ran into such an issue. Thanks again for any help.
Apologize ahead this is so long. I just wanted to update anyone just in case they ran into the same error that I did earlier. The Err:A5,69,35,00,27 on the bootloader 30.04 screen. I finally got an sbf to stick. About 30 sbf's later (no exaggeration) and 3 different nights of working on it. Honestly persistence just ended up paying off. Anyone else can chime in here if they know why it worked so its not so grueling for the next guy/gal and major props to 1kds who gave me a couple different suggestions and for making this awesome way to sbf. The linux disc didn't end up working for me in the end but it may have if I kept at it, because that is the way to go if you can (way easy to run), Also may have worked if I did the linux disc on a different computer. I started on MIUI 2.1 (Wizards vers) but previous to that the latest android vers I was on was 602, friday night my phone died and for some reason wouldn't charge in the morning or boot up. I had a spare battery with about 50% charge on it, so I used that to try and turn on the phone and I got the red M then the error message on the bootloader screen mentioned above. I ran the linux disc on my windows 7 (64bit) machine for all the currently downloadable files (froyo, 596, 602, 602root). Kept getting the err:a5,69...
Ran RSDLite on the Windows 7 machine (my current vers was 4.8, but then upgraded to 4.9) then 5.4.4 and also 5.6.4 (latest on the rsdlite motosbf site). I tried both froyo .340 and gingerbread 602 files on all these versions and even the .596 gingerbread which I had never been on. Nothing worked and I had gone through my second battery at this point. Then I figured I would try my Windows Vista 32 bit Laptop that never had rsd lite on it or the drivers. So Downloaded 5.4.4 (found this to be the one favorable for the 602 flash per the forums) and the motorola driver and sbf'd again both the froyo .340 and the gingerbread 602 file. Still getting the same error. Every third sbf or so I would even start getting a code corrupt error. The flashes actually failed every now and then and then sometimes they would show finished and the phone would still show the s/w update screen (I just did a battery pull and would sbf again at this point). After each sbf tried getting into stock recovery Volume down, home, and power button and each time I would get an error and/or go back to the bootloader screen. I also tried just home and the power button.
What worked!!! - Not sure why but my last sbf I did was the 602 still on the laptop running Windows Vista 32 bit since I thought that would work on the rsd lite 5.4.4 (credit here to droidmodderx and 1kds). It still showed the Err:A5,69,35,00,27 after the sbf finished and it tried to boot (i did get the red m, but then went to that error page again). Battery pull, turned back on and then error page on bootloader 30.04 again. I held the home, volume down, and power button for about 1-2 minutes = same result. Held Home and Power button = same result with error. Tried the home, volume down, and power one more time (still same result). Battery pull again, waited a few minutes and just tried to turn on and it got past the red m to the droid eye!!!! It did bootloop, but I battery pulled and tried to reboot since stock recovery hadn't been working. Same thing, bootloop, so I tried the stock recovery again (home, volume down, and the power button) and stock recovery came up. Hit the search button then did the factory reset. I couldn't believe it and like I said not sure why/how it worked (maybe the multiple attempts to get into stock recovery). All I know is 4 days later it works now and I thought all was lost!!! Of course again wouldn't have been able to do this without 1kds or these awesome forums! Thanks again and sorry so long, but hopefully this helps someone else!
Back on the X!
I apologize already if this has already been posted before, I couldn't see one that had my issues so I'm making this thread.
OK, so here is my problem and everything that I can think of that I've done to my phone.
Today I tried to restart my phone as it was getting a bit sluggish. When I did it started booting fine then the animation sound stopped while the droid eye was being put together. Now my phone will not pass the droid eye during the boot phase. I press the power and both volume buttons and after a few seconds it starts itself back up again. I do the power button and down volume buttons and it still does the same thing. I've even performed the factory reset twice and it still won't help.... And no matter what I do it keeps booting itself back up on its own.
What I've done to my phone:
I am rooted but never got the boot loader unlocked since i waited too long and the last update wouldn't allow the boot loader unlock methods anymore. I have used titanium backup app to delete some system apps for example the Verizon football one, slacker radio, and any of those useless apps that I never use. I haven't deleted anything lately and have restarted my phone many times since. I have been delaying the recent update hitting no or not now, whatever it says. I thought that I said no today on the system update as well. Even then my phone was working before I restarted it.
PLEASE I hope that there is something that I can do to fix my phone because I'm forced to use my LG Vortex again and my upgrade isn't for another year..... I don't want to buy a new one since this phone has been great and I'm almost certain that if there was a way to reinstal or flash the droid razr m OS that that would fix my issues.
Thanks in advance for your input and please know that I'm a novice with this kind of thing so you will have to explain the process to me. If i have instructions I can definitely follow them.
THANKS!
You Factory Reset a couple of times, so that tells me you know how to get into recovery. See if you can get back into recovery and try clearing cache/dalvik too. I think you can still do that from stock recovery.
If that doesn't work and your battery is good, you can fastboot to recover it. If your battery was low when you started this, charge it prior to fastbooting. Just hold down the power button until the phone shuts off and plug into a WALL charger until it's charged. If the battery is good, you can grab the firmware from here http://sbf.droid-developers.org/phone.php?device=8 (use the second one from the bottom, .3, if you flash the last one you will not be able to gain root) and flash in RSD. Another choice is to use House of Moto to recover: http://www.droidrzr.com/index.php/topic/28162-house-of-moto-20/ .
OK, so I deleted the cashe and still a no go. For the second step of getting the .3 to regain root. would it be possible to get an even earlier version so I can unlock the boot loader? Also when you say flash in RSD, what is that? I know of the AP flash from the first menu, is that something inside of Recovery menu options?
Thanks for your help!
**UPDATE**
THANKS! I was able to eventually figure it out and used the last option that you said and my phone works! Now working on getting root back. Thanks again!! But I really would like to know if I could do the same thing but with an earlier version to unlock the bootloader.
Droid Razr starting up issue
Hi guys, I am facing a weird issue with my Droid Razr and hoping pros to help me sort this out and get my phone running.
I am using Droid Razr but since last one week it is not starting up. Let me elaborate, currently it is switched off and not getting up. While starting it pass through M logo but can't go ahead for startup animation (droid eye animation). Even after leaving on that animation for entire day, it is not going ahead of that.
However, if I connect it to a wall charger (while it is off) it shows battery getting charged. It is taking a usual timing of 90 minutes for full charge.
I have important pictures and data into phone memory is there any way to recover it.
I would appreciate if you can guide me to get my phone up and running as usual.
RikRong said:
You Factory Reset a couple of times, so that tells me you know how to get into recovery. See if you can get back into recovery and try clearing cache/dalvik too. I think you can still do that from stock recovery.
If that doesn't work and your battery is good, you can fastboot to recover it. If your battery was low when you started this, charge it prior to fastbooting. Just hold down the power button until the phone shuts off and plug into a WALL charger until it's charged. If the battery is good, you can grab the firmware from here (use the second one from the bottom, .3, if you flash the last one you will not be able to gain root) and flash in RSD. Another choice is to use House of Moto to recover: .
Click to expand...
Click to collapse
I've been messing around with my phone, trying to flash CWM and CyanogenMod (to no avail), and yesterday something happened. I woke up, my phone was dead so I started charging it. It booted into the Stock OS (the one that ships with the G2--build D20010o I think). Shortly after, a message appeared on the screen about an update the phone was going to install (I'm assuming one that AT&T was pushing to my phone), and shortly after it powered down on its own. I have not been able to get it to boot into the OS since.
Before all of this happened, I rooted the phone with IORoot, tried to flash CWM (I think successfully), but was not able to install CyanogenMod, so I flashed an earlier build of the stock OS (D20010o), rooted it again (I'm not sure that I had to--I think it stated that my phone was already rooted), tried to flash CWM again (unsuccessfully this time), and I gave up. Then this problem occurred.
Every time I try to power on the phone, the LG logo flashes, and the screen stays on, but it's black. If I try to do a factory reset via the hardware buttons, I am able to see that screen, but as soon as I follow the instructions of pressing the power button twice, it says that it's initializing the reset, but then the phone's screen goes black again--not sure if the screen is on or off, though. The LED light is also not on during any of this.
I'm unsure what to do. I've had the phone for about 6 months, but I had not owned an Android before that--iPhone user for 3 years. I obviously did not do enough research or ask enough questions, but I would like my phone to be in a usable state. I would greatly appreciate any help that anyone can give me!
NEVER take an OTA with a recovery.
Use the lg flash tool to go back to stock
http://forum.xda-developers.com/showthread.php?t=2432476
Sorry, should have also mentioned that I can't boot into Download Mode. I'm assuming there's no .kdz file for AT&T, and the other method in that link requires Download Mode. :/