Can't Factory Reset or Flash - Motorola Droid Bionic

To start this is not my phone but my girlfriend's brother's phone. I have a Samsung Galaxy SII on Sprint and am used to rooting and flashing with Samsung phones. It has never been rooted or anything and all these problems started after the ICS OTA.
The problems that are occurring are there constantly apps that give the message "Unfortunately [APP] has stopped." including ones that are not in use and gapps. So I figured I could fix this with a factory reset by going to settings and factory reset. That didn't work so I tried in recovery mode and that did not work either. I moved on to using RSD to flash an unrooted stock rom. I have tried 905, 902, and 246. 246 successfully flashed but actually did nothing and reboots in the exact same state as before the flash. 905 and 902 would get stuck on step 6 of 22 of the flashing process.
Please do not flame me if I missed something or I'm using the incorrect terms or whatever. I'm just trying to get this phone fixed and any help would be appreciated.

Related

[Q] Post SBF Questions

A few weeks ago I rooted my X and ran the manual deodex method posted on the site. Phone ran great, I installed clockwork recovery and made a few backups. after installing a rom and not being able to get back into the recovery, I had to flash the phone with the 2.2 full SBF. This leads to my questions
1. After I SBF'd I was able to recover my applications and my data was all on the SD card. however I have a few applications that when run will close and give me an error message stating that the "application unexpectedly quit" I can duplicate the issue most when attempting to search the a forum through the XDA application. I am sure I failed to wipe data and cache before I recovered the stock OS, could this be the cause, any ideas?
2. I have re-rooted my phone but I have a question about deodexing again. I understand that motorola is in the early stages of working on an update to fix reported issues with 2.2, I also believe that they will use this opportunity to update the bootloader version. is there a way to disable the OTA updates? I am concerned about bricking my phone if an update is release and I am deodexed, what is the worst that could happen?
Sorry for the post, I am technically inclined but am still learning the android OS, any help is very much appreciated.
If you run a rom either aosp or blur you can avoid the ota that's end only way I know to avoid it
Sent from my DROIDX using XDA App
thanks for the response, I read a few places that clockwork recovery blocks OTA updates from installing, but I am having a hard time nailing down a definitive answer.
From what I understand Droid X SBF files do not wipe data like other phones. I recently had to SBF but kept getting stuck looping at the droid eye. I booted into recovery and did a factory reset and all worked out just fine. I know it's not your exact problem but it still might be worth it to try.
As for not getting OTA updates other than doing a custom ROM I can't help you there, sorry.

[Q] Bricked my bionic, help

OK, so I'm not new to the custom firmware thing, I had a Droid, and kept flashing all kinds of stuff, never had a problem. So I got my bionic, rooted it, flashed a few custom firmwares, had no issues. I decided to upgrade to the Nexus, so I was gonna restore my bionic back to factory settings for when I gave it to a friend.
So I used the R3l3ase3droot method, I figured it'd be easiest. After it flashed it, it said flash failure. So I figured, no problem. I can flash it manually. I try that, and it says boot failure now. When I try to flash a boot image it goes back to flash failure. I can't seem to get out of this loop. I've tried different versions, different methods. All of that. Any tips?
nevermind, in my rush to try everything, I guess I forgot to use pathsaver, it worked perfectly.

[solved] lost access to google account after flash attempt

Hi Guys
bit of a newb her, I tried to flash a jellybean rom and after doing plenty of research followed the instructions to the letter. The result was that it didnt work and reverted back to honeycombe 3.2. The problem i have is that it no longer allows me access or set up my google account and some buttons such as the home button no longer seem to work. I have been unable to go back to stock and am lookign for a little guidance.
I did carry out a factory reset.
Kies is also not recognising my tablet.
I apologise for starting a new thread if this has been asked before. I have not seen an identical problem on this forum so far
Did you make a backup in cwm recovery for the stock honeycomb before flashing the jellybean? And what method did you use to revert back to stock?
For the factory reset, did you do it after reverting back to stock or before?
Sent from my GT-P7300
x24 said:
Did you make a backup in cwm recovery for the stock honeycomb before flashing the jellybean? And what method did you use to revert back to stock?
For the factory reset, did you do it after reverting back to stock or before?
Sent from my GT-P7300
Click to expand...
Click to collapse
I did do a backup in CMW recovery. The flash to jellybean didn't failed. It took a few minutes and then restarted and booted up as 3.2. The factory reset and wipe cache partition were carried out as per the instructions online prior to installing the zip file.
I'm just hoping it is possible to resolve this problem.
thanks for any help
Just to provide an update. I have now resolved the problem
After trying to factory reset my tab then became stuck was stuck on the galaxy tab screen. Using the stock rom for 3.2 found here http://forum.xda-developers.com/show....php?t=1483168 i was able to flash this using Odin and much to my relief it booted up again in 3.2.
Much to my amazement once it was flashed onto my device and booted up i was able to get an OTA update to ICS 4.0.4 which was a bit of a suprise. Not sure how or why this happened but i am very pleased with the result. ICS is a huge improvement from honeycombe and is like having a new tablet. It is so much smoother and more responsive.
I was using CWM 5.2.0.4
Since you have figured out how to resolve the problem please change the title from [Q] to [solved] this way if someone else has a similar problem they will know that they can find a answer here.
Sent from my Nocturnalized One XL using Forum Runner

[Q] Restore to 4.3 NB4

OK it's been a while and I have screwed up some stuff.
I have the att note 3 and I"m rooted running 4.3 build NB4. I had some stuff frozen and xposed things setup. Been running fine and really haven't messed with anything for 6-7 months. I'm selling the phone and told the person buying it I would leave it on 4.3 stock rooted.
So I just did a factory reset / wipe cache. Now when it boots up I get a samsung keyboard force close error and can't do anything until I change to something else. I figure there will be other issues also, I realize now I should have undone things, but it's to late.
So what do people recommend. My first thought was to somehow flash the NB4 files, but i don't have custom recovery.
So any suggestions, steps or files would be much appreciated.
Can you not just odin to reflash it back to stock 4.3?
Maybe but i cant locate the files to odin and im not that famaliar with how to use odin. Can some provide a liitle guidance.
cd23murray said:
OK it's been a while and I have screwed up some stuff.
I have the att note 3 and I"m rooted running 4.3 build NB4. I had some stuff frozen and xposed things setup. Been running fine and really haven't messed with anything for 6-7 months. I'm selling the phone and told the person buying it I would leave it on 4.3 stock rooted.
So I just did a factory reset / wipe cache. Now when it boots up I get a samsung keyboard force close error and can't do anything until I change to something else. I figure there will be other issues also, I realize now I should have undone things, but it's to late.
So what do people recommend. My first thought was to somehow flash the NB4 files, but i don't have custom recovery.
So any suggestions, steps or files would be much appreciated.
Click to expand...
Click to collapse
I don't think you will find it NB4 build for odin. I was looking for firmware for some time and had no success. You need to get back to NI9 than find update NI9 to MJ5 and then MJ5 to NB4. So i will suggest find this updates so you can sideload after you get stock NI9. and i think you have all files you need to do this here : http://forum.xda-developers.com/showpost.php?p=51468226&postcount=10

Note 3 4.4.2 ATT [ROOTED] Bootloop type glitch

hello,
ive been searching around for about an hour and i havent found a thing.
Let me describe my phone:
Safestrap
rooted
android 4.4.2
Scenario:
got a nasty ad virus yesterday, so i restarted my phone today and went into safestrap. Then i installed my previous back up from about a month ago. (not sure if i needed to delete anything left of the device) I restored data and system and it worked fine. I was in android for about 5 minutes then it restarted. so i assumed it was normal then it did it continuously.
First off im not sure what a bootloop is but i assume it doesnt post to the android system and continuously loops the boot logos.
Whats happening to me is that my phone will boot for a few seconds, sometimes minutes, and i can get on android for a few. Then the phone restarts. Ive been looking around for a few hours now and i cant find a fix or a way to restore my phone to the restore i made on 4/22/17.
ANY help would be greatly appreciated and please correct me if i did something i wasnt supposed to.
If you need more info i will gladly post more
-LL
I am no expert, but I think you would have to do a factory reset on your phone if you wanted to have a proper restore. When I did rooting on 4.4.4 and 5.0 I always flashed the phone with Odin.
Sicuro said:
I am no expert, but I think you would have to do a factory reset on your phone if you wanted to have a proper restore. When I did rooting on 4.4.4 and 5.0 I always flashed the phone with Odin.
Click to expand...
Click to collapse
I got it fixed i had to flash a new stock rom and root it again. up and running from a softbrick. Its also running Android 4.4.2

Categories

Resources