Sorry! The device is an A854, not A855.
I should preface this by saying that I am sure my ineptitude has created these problems. I have been trying to figure out why my A854/CDMA phone was unable to send outgoing MMS messages, while still being able to receive them. I had been running Cyanogen6 without issue, but wanted to try the stock rom, just to make sure that wasn't the issue.
Through RomManager, I downloaded the Verizon Droid 2.2 FRG01B image and attempted loaded it. The install went through without a hitch, however I don't believe that I prepared my applications and settings properly. After loading the image, I am no longer able to use most of the items in my dock (phone, contacts, settings, etc).
Usually, I would just boot into recovery and load my backup...but that is not available now. When I attempt to boot into recovery (through RomManager), I get the message "An error occurred while attempting to run privileged commands!". Should I try loading a stock SBF file through RSDLite? If so, which SBF file would I need? My phone is on the ACS network in Alaska, which is CDMA.
Try this:
1. Turn off the phone
2. Hold "Camera" button and the "X" button (on the keyboard)
3. While holding those two buttons power on the phone
...that would get you to recovery mode, from there you can do factory reset. If you want another firmware, then flash it through RSD Lite. Hope it helps.
Related
So, I was running CM7 no problems. Then one day the ax just fell. I tried re-flashing the ROM and it hangs on the boot animation...so, I removed CWM, made a bootable CWM SD and flashed a few different "return to Stock.zips." One finally worked, but when I connect to Wifi, it says it can't connect and shows that my device doesn't have a serial number or a model number, so I can't get beyond that screen, and it is on version 1.0.1. So I tried using the CWM SD again to update the Firmware. When I did that as soon as I turned on the device, it locked up on a screen that says, "Install Failed, please power Off and the Back on again." So I tried completely wiping and re-installing CM7 to eMMc, and now, again it just hangs on the boot screen.
Oh, and 8 boot interruptions doesn't work for me and when I try holding the power +N keys I go directly into the "Install failed please press off and power back on to try again," screen.
My head is going to explode. Please help. I think my next attempt is going to be trying to flash an alternate kernel.
Use this .zip to get full stock 1.3: http://dl.dropbox.com/u/30572895/Nook_Color/update-nc-stock-1.3.zip
patruns said:
Use this .zip to get full stock 1.3: http://dl.dropbox.com/u/30572895/Nook_Color/update-nc-stock-1.3.zip
Click to expand...
Click to collapse
Hey I tried this, and when I flash the .zip, as soon as the device powers on it goes straight into the "install failed please turn off device and the turn back on to try again," dialog. On this screen it is black with a white stenciling of the NC. I have grown to despise this screen.
Also, anytime I have tried to factory reset, it goes directly into the install failed screen.
I have managed to get into the stock 1.0.1 homescreen by bypassing the Out of Box Experience, and even when I try to Erase/Deregister there, it stops and says device not registered, and therefore it cannot wipe. Also, when I check device info, every single one has red 000000000.
I suppose that since I'm at least to the homescreens I could try ADB, because it wasn't working either the last two nights.
Also is there anything in the LOST.DIR that could help? What the hell is a LOST.DIR?
So, another interesting thing here...whenever I go to install ADB the softkeys show up in the status bar, like its already rooted and running the stock 1.0.1 launcher bar, as soon as I unplug the USB, they disappear, so I can't even enable debugging.
Also, the NC isn't showing up on the ADB device list.
Dear Sir/Madam,
Before Spring Break, I rooted my droid bionic using motofail for windows. I do not know what the software version is, but I will include the software (motofail) in this email. On Thursday March 28, 2012 I decided to try installing ROMs to my Droid Bionic. I saw that Liberty Rom, Blurr3d Rom, and Eclipse Rom were cool roms. so first, I got Bootstrap (I will include it in this email) Bootstrap is a .apk file. I also got ROM manager, titanium backup, and one more, but i do not recall what it was. I made a backup of the stock ROM with ROM manager. and i installed bootstrap. little did i know that if something bad happens to the phone during a ROM install, you cannot restore a previous backup. So i cannot get my stock ROM back on. later on, before i had a problem with bootsrap i installed liberty ROM. then i got board with it then got blurr3d. then i got eclipse ROM. that's when i started to have problems. After i installed the eclipse ROM, noticed that i could not get any cell service or data service. I could get data from wifi though. So i freaked out and got liberty ROM. i read up on it and someone said i should get safestrap. Safestrap is like bootstrap but it is safer because you can access the recovery menu from boot and not have to access it through an application on the phone like with bootstrap. So after i got safestrap i installed it, rebooted it and made a back up. Before i made the backup i put plurr3d back on becasue i thought that the radio files from eclipse were not compatible with the radios on the bionic for some reason. This was all on Thursday. well, this time, it took 3-4 hours for blurr3d to get passed the welcome to andorid please touch the android to continue screen. on the screen it said, "please wait... this may take a few mins" after about 20 mins i got worried so I pulled the battery and rebooted the phone. and got back to the same screen. After i got back to the welcome to android screen, i had to go to football practice and dinner afterwards. when i got home, which was 3-4 hours later, I checked on the phone and it was past that screen and i was able to add my gmail account to it. For some reason or another, the cell and data services were not working. so i left it at that for a day or so and on Friday, I tried using what a lot of people are saying on the Internet which is, RSD lite. you can use RDS lite to flash a stock ROM onto the droid bionic. at that point, i thought that if i got the stock ROM back on, the radios would start working again. well, when I put the phone into fastboot mode it said,
AP Fastboot Flash Mode (S)
0A.61
Battery OK
OK to Program
Connect USB
DATA Cable
It also said the same thing when i connected the USB cable to the phone and the computer. RSD lite did not recognize the phone so i tried for a couple hours with the same result. Later on, I read that restarting the computer with the phone in AP Fastboot while the phone was plugged in would get the phone to say,
AP Fastboot Flash Mode (S)
0A.61
Battery OK
OK to Program
Transfer Mode:
USB Connected
This worked, but RSD lite still would not recognize the phone. So then i remembered that i had a stock ROM backup with bootstrap and i did. so i un-installed safestrap (one of the worst mistakes i made so far) and installed bootstrap. so i booted into recovery via bootstrap to restore to stock ROM. things did not go as planned... for some reason or another, it booted up normally. without going to recovery. then it wont to the dual core screen then the bionic eye screen with someone's ROM underneath it (it didn't say someones ROM but it said some one's name then the word ROM) then blurr3d ROM booted up and it kept crashing. so i ended up staying up to around 2-4 AM trying to fix that. i ended up saying forget this and going to sleep.
When i woke up in the morning, i looked at the phone and i had my data and my cell service back so i was confused so i started texting my friends and when i tried to go tot he home screen, nothing happens. but what i learned earlier is that when i reboot the phone, my data and cell service goes away for a couple of hours. So here i am now with my droid bionic, and cant do anything but text and call. i can only call when i get a text from someone, open up the text, and click on the phone number and click call when it brings me to the contact page for the number. I am also not able to access the home screen, the settings folder, or anything besides the notification bar. i really need my phone to use email, games, software (learning how to write java code), and for school in some instances. Any help would be greatly appreciated.
Thank you for your time,
NH85
Seems to me...you lost data along the way.
A possible reason rsdlite is not recognizing your phone might be because you dont have the proper moto drivers installed.
Try this rsdlite and install the correct drivers for your pc...http://dl.dropbox.com/u/63864500/rsd_drivers.zip
Make sure your battery does not die!
Boot into AP fasboot (power and down volume)
Use the cable that came with your phone.
See if rsdlite recognizes the phone.
If it does, you can flash the full 902 xml file (make sure your pc has 4g of RAM tho)
Do you have the full 902 xml file...if not, let me know.
Drivers
Dear Sir/Madam,
I have the correct drivers installed. When i connect the phone regulry once it is all booted up, i am able to access the sd card and the internal storage via windows explorer.The problem is that the phone refuses to connect to the computer in fastboot mode. i do not want to risk rebooting unless it is guaranteed to work 100% because I can still text and call on it for some reason. Every time the phone is restarted, the radios stop working for a while and i need to be able to text my parents where and when to pick me up from school.
Thank you for your time,
NH85
i notice that you didn't once mention a wipe data or otherwise cleaning of previous ROM before flashing another (correct me if im wrong). also DO NOT have bootstrap and safestrap installed at the same time, this could be what caused all your problems. in order to switch between the two (which i've had to do for webtop issue), you have to return to STOCK +root, uninstall the currently used strapper, reboot, then install the other. things start getting even hairier if you forget that safestrap has both a safe/non-safe system. you need to be doing the switch on the non-safe system if necessary.
the purpose of safe-strap isn't that it can boot to recovery, it's that it *creates a an isolated ROM installation while preserving your "safe" system in case things like everything your experiencing occur. from what i can tell, you did not change to safe system before flashing new ROMs, again correct me if im wrong. at any rate, a bit of advice for the future is follow directions to the dot, but before even attempting the install read through AT LEAST 3 or 4 pages of user feedback to see what the common issues or install goofs are!
that being said...
having your computer recognize the phone as storage device does not necessarily mean you have the right drivers installed, however it does mean that you probably have the right cable (this is important, bionic is finicky without the proper moto cable). you will know if you have the right drivers if you see in device manager Motorola ADB. when you plug your USB cable in, there should be an option for "PC Mode" which will force the computer to search for the drivers you claim to have installed correctly. if not found, here is your chance to install them properly and test RSD to make sure device is detected.
nh85 said:
Dear Sir/Madam,
I have the correct drivers installed. When i connect the phone regulry once it is all booted up, i am able to access the sd card and the internal storage via windows explorer.The problem is that the phone refuses to connect to the computer in fastboot mode. i do not want to risk rebooting unless it is guaranteed to work 100% because I can still text and call on it for some reason. Every time the phone is restarted, the radios stop working for a while and i need to be able to text my parents where and when to pick me up from school.
Thank you for your time,
NH85
Click to expand...
Click to collapse
Obviously you don't.
Mass storage and ADB are not the same drivers.
If you are in fastboot mode and your device doesn't connect, it's most likely your missing or don't have the fastboot drivers installed on your computer properly.
Once you get the ADB driver from motorola you can use fastboot start flashing.
The information you need is here
http://forum.xda-developers.com/showthread.php?p=22758211 .
I had trouble using RSD to flash the .902 FXZ.
What I had to do is extract the .img files from the ZIP, and use fastboot through CMD to get everything up and running.
Just open up the XML file inside the zip, it will show you the commands you need to type to flash each section and when to reboot the bootloader
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
whoisthisis said:
I rooted my droid 4 a few months ago when I first got it so I could tether. I removed a couple of programs using titanium backup (blockbuster app and some other bloat). Phone worked fine until monday when the touchscreen stopped working. I did a reboot (power + volume down) whereupon it just sat at the M "Dual Core" logo. I tried booting into the recovery menu but selecting "recovery" didn't do anything - it would just hang.
Last night I was able to get it working again by going into the recovery menu and selecting asp fastboot, then using RSDLite to push a stock Droid 4 ROM onto the phone. However, it didn't wipe my old system, and didnt install over it either because all my files were there, and the programs I removed were still gone. So the phone worked for a few hours then the touchscreen stopped working again.
I repeated the process with RSDLite and after a few failed attempts where the phone would hang while booting, I finally got it to boot into the OS again. And this is where I am at now.
I am pretty sure that the problem is related to the OS that is on the phone now and that I need to wipe the phone and start fresh with either a custom ROM or the stock D4 ROM. The problem is that I can't get recovery to do a factory reset. As I mentioned above, recovery just hangs and doesn't do anything. I am reasonably literate when it comes to this stuff but I get really confused because there are so many different ways that people seem to do this stuff (safestrap, bootstrap, CM( etc). I would love to try CM9 but my priority right now is just to have a phone that works. Any help would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
select recovery by holding the vol buttons and power on boot just like fastboot. press vol - for recovery. when u see dead droid hit both vol up and vol down and theres the recovery
Thanks, I was finally able to get into recovery. Wiped data and did a factory reset which again got stuck at the logo screen. Went back into fastboot and ran RSDlite again to flash the stock ROM which gets me to the "Welcome to Droid4" screen where it says "touch the android to start" but the touchscreen is unresponsive. Starting to think there is something physically wrong with the phone....
send it to motorola, I've heard their customer support is pretty good. but if you voided your warranty by rooting/flashing other roms, I've heard bricking the phone and sending it in works to get a new one too
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
whoisthisis said:
The only way I can send it back is through an insurance claim so I am trying to save myself $75j if this thing will just work. I just did a reboot and now the touchscreen seems to be working so I am going through the setup process....so weird.
Update: I was able to get the phone to load up and configured my google account etc. It appears that the phone is now running on completely stock installation of OS.....
Click to expand...
Click to collapse
So it has been a couple days now and the phone works totally fine. It looks like the problem was that by removing whatever bloatware that I did, the phone's OS got borked when VZW pushed an update of some kind. Flashing the stock ROM without doing a factory wipe would temporarily solve the problem but eventually the update would get pushed again and the whole thing would lock up again. The factory wipe + reinstall seems to have been the solution to the problem.
Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Titerepayaso said:
Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Click to expand...
Click to collapse
Sounds pretty accurate. You'll have to get a jig to get in download mode, flash stock Odin KK4 to fix w/e happened during your testing.
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Titerepayaso said:
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Click to expand...
Click to collapse
Make a backup with ADB.
Once that's done, push download mode with it and get Odin KK4 (without bootloaders). You'll have to start from there to fix w/e went wrong.
You don't have to wipe your sd doing so but you will lose your apps and such. If you backed up your phone with your Play Store account, it will re-download your apps as you're done booting up.
To get back up where you were, grab Corn Kernel, flash it with Odin 1.87 and then follow the full instructions of the ROM you wanna use.
Very noobish issue. Rooted, unlocked bootloader on Atrix HD. Set up SafeStrap as recovery. Everything checked and working. After letting SafeStrap install Cyan 10.3 and rebooting, phone entered CyanogenMod boot screen and become stuck for an hour. Realized that I forgot to reset and wipe all stock settings and cache (yes, I know that should have been obvious step). Figured I could just go into SafeStrap and make the quick fix.
Seems that I'm unable to enter my custom recovery, instead I'm lead to the familiar bricked android stock recovery. No options to access stock rom (assuming it was deleted during install or lost, etc). Tried installing a different recovery, but fastboot on PC is unable to find device. Help at this point is very much appreciated, either to do any of the following:
1. Somehow access SafeStrap again (assuming that it wasn't wiped aswell) so I can clear stock settings and cache, get Cyan 10.3 going properly.
2. Instructions/links to another method to otherwise forcibly delete stock settings and cache (please keep in mind, fastboot is currently unable to find device).
3. Otherwise completely clear phone of EVERYTHING, then reinstal stock recovery and or/stock ROM so I can give up on flashing custom and stick with stock.
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Update Motorola drivers on your computer and check threads for fastboot files from skeevydude.
Sent from my MB886 using XDA Premium 4 mobile app
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
http://forum.xda-developers.com/showthread.php?t=2226527
Sent from my MB886 using XDA Premium 4 mobile app
SkunkID said:
*Update:
Was finally able to get phone into AP Fastboot Flahsh Mode. My computer itself can't see the phone, but device manager shows it as "Fastboot QINARA S" and I'm able get a response through my PC's end of flashboot.
Tried using RSD lite to install a stock ROM, but no success since the phone isn't off and can't be turned off without trying to go into another Boot Loop. Also tried installing a new recovery through fastboot, but I keep getting the response, "(Bootloader) variable not supported."
At this point, I'd be really happy if I could get the proper commands to wipe and factory reset my phone while in fastboot. At least then I'd have Cyan. I could try installing stock if it continued to glitch.
Click to expand...
Click to collapse
The error is from using the wrong fastboot executable. Look at post 5. If you get a stickybit error, search our general forums for "stickybit" and you'll find that fix.
deeje00 said:
Well safestrap is for use with locked bootloaders so there lies your problem. Maybe you can make a factory cable or buy one to put your phone into fastboot so you can flash stock through rsd.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
With a bit of creativitity one could use SSR to dual boot Holo Blur and Batakang....or two custom 4.3's that use the same kernel....PAC + Carbon both with arrrghhh's kernel.....Only problem is ya can't be a noob at all if ya do it.
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
When you're at the "dead Android" screen pressing Vol Down + Power pushes it into recovery, iirc - might seem random but there's a purpose behind it.
SkunkID said:
Solved issue...somehow.
Used method shown in link below to install stock recovery image since Safety Strap was apparently deleted/wiped/banished?
(can't link, still noob poster. Just search, "[Guide] How to flash back to Stock Rom - chacha. Please Sticky This !", should be the first result.)
After installing stock recovery, was able to go to the standard dead android screen, but after punching the volume buttons randomly, the option menu for stock recovery opened. Was able to factory reset and wipe cache, then properly reboot. Cyanogenmod finally got out of it's BootLoop, and everything seems to be running fine. Flashed a non-official CWM (no offical CWM or Twrp avaliable for Atric HD) and got Gapps. Phone is finally running fine.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Lingering issues worth mentioning incase there are obvious fixes.
.Cyan likes to crash whenever running programs for the first time or doing do much activity in a short amount of time (I suspect the cache has something to do with the cleared cache since revisiting apps doesn't cause crashes as often). If it persists, I'll probably just back up and look for a more stable rom.
.All notification lights are white, except the battery notification lights, despite me changing the colors and/or allowing apps to use their own light settings.
Click to expand...
Click to collapse
Hi, I am having the same issue you had... how the heck were you able to get back into stock recovery? Every time I try my phone just reboots and gets stuck again. I cant even turn off my phone with out it rebooting. I have read your posts and followed that other forum you mentioned but if I cannot boot into recovery and if my computer cant see my phone it wont work. Please help when you get a chance.