My bionic is bricked. I tried to take the JB update and for some reason bricked my phone. i even tried that RSD Lite to fix it, but it didn't work. If I called Verizon and put in for a replacement, with the way my phone is, ONLY boots to AP Fastboot mode, if I sent it in to Verizon, would they be able to anyway retrieve the type of data I have on my phone? I know they're not allowed to go through personal data and whatnot but I have some very private things on there that I don't want getting into anyone's hands. So basically I'm just wondering if I send it in the way it is, will they be able to determine anything about its old condition, regarding data/applications etc?
When you tried to RSD Lite did you do the fix where you edit the XML file? That's been a common problem for people trying to FXZ direct to JB
projektorboy said:
When you tried to RSD Lite did you do the fix where you edit the XML file? That's been a common problem for people trying to FXZ direct to JB
Click to expand...
Click to collapse
no. i wish i did because i could easily fix that and reflash. but I think its more than that. .246 fxz and .22 fxz are both getting stuck at "install-mbmloader-flashing-mbm-bin" >> USB error during reading/writing. but I know its not USB because I was using a factory cable (TBH cable)
Try that fix where you copy the system.IMG and I think boot.IMG and push with moto. I know this sounds retarded I'll look for the link.
Sent from my DROID BIONIC using xda app-developers app
---------- Post added at 09:18 PM ---------- Previous post was at 09:13 PM ----------
http://forum.xda-developers.com/showthread.php?t=1427945
I think that's the post that fixed me. Can you even get to recovery with Power+volup+voldwn ?
Sent from my DROID BIONIC using xda app-developers app
lemonoid said:
no. i wish i did because i could easily fix that and reflash. but I think its more than that. .246 fxz and .22 fxz are both getting stuck at "install-mbmloader-flashing-mbm-bin" >> USB error during reading/writing. but I know its not USB because I was using a factory cable (TBH cable)
Click to expand...
Click to collapse
If the OTA started to install at all, as opposed to giving you an Error code 7 immediately after rebooting into recovery, then you cannot try flashing the .246 - your bootloader has already been updated.
If it boots to AP fastboot screen then if it says A.78 you know it is the new bootloader. If it says A.72 then it has not been updated yet.
Related
Hey guys,
unrooted the bionic, but Liberty rom is still very present. super user is gone, and it looks like it was unrooted successfully. Any ideas how to get rid of the boot loader and other Liberty artifacts?
thanks
yungwunn911 said:
Hey guys,
unrooted the bionic, but Liberty rom is still very present. super user is gone, and it looks like it was unrooted successfully. Any ideas how to get rid of the boot loader and other Liberty artifacts?
thanks
Click to expand...
Click to collapse
run the fxz file
ran it twice on RSD lite and keep getting a cycling boot screen...
hmm...any tips?
yungwunn911 said:
ran it twice on RSD lite and keep getting a cycling boot screen...
hmm...any tips?
Click to expand...
Click to collapse
Do you have usb debugging on? If not it needs to be on. Also are you in fastboot mode? Volume down then power at the same time
---------- Post added at 06:41 PM ---------- Previous post was at 06:30 PM ----------
If all else fails, hopefully you made a nandroid backup of your phone when it was stock right after you rooted it and you can always reboot and restore your nandroid then un root.
Use dhacker's one-click restore. It's stickied in development. I guarantee it'll fix you right up.
Sent from my DROID BIONIC using xda premium
Similar experience here...but i know why. I did the one click root using the smaller file that preserves data.
Sent from my DROID BIONIC using xda premium
Go here:
http://forum.xda-developers.com/showthread.php?t=1279825
Sent from my DROID BIONIC using xda premium
i dont know whats ahppening but after i download the ota and select install, it reboots with a lil droid guy next to a box with progress bar then it gets 1/4 down and then a a error sysmbol comes and it reboots then it tells update failed... im rooted and i have no roms just root stock. can anyone help me figure out what going on? and help me get this phone to update
Sent from my DROID BIONIC using Tapatalk
Are you moving it from /cache to your external SD Card then flashing it?
Sent from my DROID BIONIC using XDA App
no im letting my phone doing it. im downloading from verizon.
Sent from my DROID BIONIC using Tapatalk
i got on my sdcard now moved it from cache folder how do i flash to install it?
Sent from my DROID BIONIC using Tapatalk
Boot into stock recovery.
Having the same issue. Moved file to ext sdcard. Flashed from recovery and i get an error and aborts. Says status 7 error in system/apps/bookphone.apk
confuzzled1007 said:
Having the same issue. Moved file to ext sdcard. Flashed from recovery and i get an error and aborts. Says status 7 error in system/apps/bookphone.apk
Click to expand...
Click to collapse
I had a similar problem. I had to use r3l3ased and forever root, then path saver.
Sent from my DROID BIONIC using XDA App
Had the same problem. I have narrowed it down to either a bootstrap issue or one of the mods I used in the past. I used R3L3AS3DRoot and 43V3R Root before doing 2 separate OTA's, one to get back to 893 than the next to 902. It takes some time, sure, but it worked. I'm now waiting for my apps to reinstall.
I tried to go into stock recovery just a sec ago. and when i click vol up to select it . i get an exclamation point with the android guy below it? anyone know why this is happening or what i can do? thanks guys
---------- Post added at 08:11 PM ---------- Previous post was at 08:06 PM ----------
crking1980 said:
I tried to go into stock recovery just a sec ago. and when i click vol up to select it . i get an exclamation point with the android guy below it? anyone know why this is happening or what i can do? thanks guys
Click to expand...
Click to collapse
derp soory i figure it out. i forgot you are supposed to hit vol up and down at the same time
I had similar issues getting a corrupted file. So I ended up going back to stock 893 using the fxz and rsd lite. That put me back to true factory setup, and back on the OTA wagon. So I forever rooted and took the update direct from Verizon and let the phone update itself. Now "poof" running rooted 902.
Sent from my DROID BIONIC using Tapatalk
I had a similar issue, I did a hard reset of my phone, and updated fine afterwards.
Sent from my DROID BIONIC using xda premium
I have a bionic that i system updated to 5.9.902 a couple days after i got it. Then i made the mistake of coming here and messing up my phone because i have no idea what I'm doing
I installed safestrap and did the whole noob step by step guide. Installed eclipse and a couple other roms. For some reason i wiped my internal and external storage. I have no backups of anything.
I've tried releasedroot, petes, rds lite with the 902 xml. I got stuck all the time with what seemed to be a driver issue.
I just want to return this thing to stock and stop messing with it
As of now when I press power i go straight to ap fast boot flash failure screen. I press power to power off and hold vol up and down to boot into recovery but just pick the normal boot option. Phone then boots into what seems to be my stock 902. I dont know if im rooted anymore.
If i could rid my phone of this flash failure and safestrap, i would be stupid happy
Anyone out there willing to help a total noob? If any more info is needed I'd be happy to provide
Sent from my DROID BIONIC using XDA
What error did you receive using rsdlite?
When you go into your phone settings..can you verify your on 902?
I'm at work now but it was some sort of usb failure. It got stuck on 1/22 mbm something.
Yes as of right now im on 902.
Is there a tutorial on how to completely remove usb drivers? Even though rsdlite says I'm connected, I don't see my phone drivers in device manager. That's where I think I'm going wrong but not really sure.
Sent from my DROID BIONIC using XDA
Cool. I'm at work too. When would you be available?
About 5pm est ... thanks alot dude
Sent from my DROID BIONIC using XDA
Send me a PM when your available.
I tried to pm you but xda force closed. I replied to, i believe, your hotmail
Sent from my DROID BIONIC using XDA
has anyone found a way to root the latest offical ICS 4.0.4 build 6.7.246? i lost root after installing it. thanks.
Motofail for ICS
I was able 2 using razors edge jus make sure debuggin and custom apps are checked
Sent from my DROID BIONIC using xda app-developers app
it worked!
hey thanks, it worked!!!
Sir_Eagle said:
Motofail for ICS
Click to expand...
Click to collapse
Phone not showing ICS
I can't get my son's phone to show the update as available. Has anyone posted the zip file out there for other users to install the ICS update?
shduong said:
hey thanks, it worked!!!
Click to expand...
Click to collapse
Mind sharing where you found it? I'm finding links but not sure which is right. I'd rather just use whatever you used since I know it will work.
uggghhhh. I was just going to use OTA Rootkeeper but ever since I updated to .905 my adb does not work. My phone will not mount to the computer at all, it won't read my SD Card, only charge the phone. So I tried to fix it by flashing a FXZ through RSDLite, because that fixed it last time it happened 6 months ago, and it didn't work. So I'm just going to install the update, and hopefully it will fix my adb. If not, I have no clue how I'm going to root this ******* phone!!! its so frustrating! If anyone knows of a way that I could edit some rooting script to connect through adb wireless, please let me know. I would even be willing to pay someone like ten or fifteen bucks if they could give me a working script to root through adb wireless, or some other way, which I've never heard of.
shduong said:
hey thanks, it worked!!!
Click to expand...
Click to collapse
Please let us know where you found the motofail-ics download that you used. Also, did you just have usb debugging checked or did you need to check other options as well?
Motofail-ics is included in the thread at the top of the page titled 905 to ICS update... worked for me
Sent from my DROID BIONIC using xda app-developers app
---------- Post added at 09:03 PM ---------- Previous post was at 08:21 PM ----------
It is included in the guide in the sticky section..
Sent from my DROID BIONIC using xda app-developers app
bonzai276 said:
Motofail-ics is included in the thread at the top of the page titled 905 to ICS update... worked for me
Sent from my DROID BIONIC using xda app-developers app
---------- Post added at 09:03 PM ---------- Previous post was at 08:21 PM ----------
It is included in the guide in the sticky section..
Sent from my DROID BIONIC using xda app-developers app
Click to expand...
Click to collapse
I also used the motofail-ics posted in the guide and had no issues.
sytech55 said:
I can't get my son's phone to show the update as available. Has anyone posted the zip file out there for other users to install the ICS update?
Click to expand...
Click to collapse
https://docs.google.com/file/d/0B7z9xJrt55a6bFM0YUV1amhLZVU/edit?pli=1 enjoy
Instructions Links
Mobifail-ics
Source: http://forum.xda-developers.com/showthread.php?t=1771993&highlight=motofail - Original post
In addition to that post you will be able to get everything you need to download and install the latest ICS version and root your device.
- Cheers
motofail ics failed for me
Just hot a replacement bionic in the mail and am about to send back my rooted 2.3.4 running eclipse 3.0. I updated the replacement w 4.0.4 and tried the wonderfully simplified motofail ics, usb debugged (not in mtp mode) it recognized device, started daemon, then stalled out for 20 min....? I unplugged read up some more switched to mtp mode and now it claims its waiting for device to be ready..... i am a unlimited data grandfather who relies on my unlocked wifi tether.... any guidance?!
tonamaste said:
Just hot a replacement bionic in the mail and am about to send back my rooted 2.3.4 running eclipse 3.0. I updated the replacement w 4.0.4 and tried the wonderfully simplified motofail ics, usb debugged (not in mtp mode) it recognized device, started daemon, then stalled out for 20 min....? I unplugged read up some more switched to mtp mode and now it claims its waiting for device to be ready..... i am a unlimited data grandfather who relies on my unlocked wifi tether.... any guidance?!
Click to expand...
Click to collapse
How did you update to ICS? Over the air update? I ask because if you updated it via FXZ and Fastboot mode with RSD Lite, then what I'm about to suggest is moot. But if you took the OTA update, then it makes more sense.
I'm betting that either your computer doesn't have the right Moto drivers on them, or that you're plugging it into a bad port. They can be finicky.
Go here: http://forum.xda-developers.com/showthread.php?t=1771993
Grab the USB drivers mentioned in step (4).
Then make sure that you're plugging your phone into a USB port on the back of your computer, not an external USB hub. Also don't plug it into USB 3.0. This may not actually be the issue but I accidentally used my USB 3.0 port once to Motofail and it didn't work at all. If you already tried one of the back ports, or are on a laptop, just try another port.
MrChupon is spot on. I had the exact same problem until i went Motorola and grabbed the very latest drivers. Worked like a champ after that.
Sent from my DROID BIONIC using Tapatalk 2
It was over the air, from a fresh stock VZW replacement. For what ever unknown reason it stalled out once it started daemon..... I pre maturely ejected it, and I think it left the device in a partial state, and when reattempting in my 2.o port it was confused and left me hanging.... so in my sleep i decided to try a factory reset to flush the cache so to say and motofail proved to be a fantastic success! (Using my wifi right now thanks to some sqlite value adjustments! Thanks for the wisdom and words regardless!
tonamaste said:
It was over the air, from a fresh stock VZW replacement. For what ever unknown reason it stalled out once it started daemon..... I pre maturely ejected it, and I think it left the device in a partial state, and when reattempting in my 2.o port it was confused and left me hanging.... so in my sleep i decided to try a factory reset to flush the cache so to say and motofail proved to be a fantastic success! (Using my wifi right now thanks to some sqlite value adjustments! Thanks for the wisdom and words regardless!
Click to expand...
Click to collapse
Premature ejection will get you every time!
Sent from my DROID BIONIC using Tapatalk 2
I was running gingerbread 2.3.6 on my Droid 4 and decided I wanted access to Chrome and to update my baseband, so I used the Droid 4 Utility (Jellybean) to update to JB stock (wipe data). Upon reboot my display is all corrupted with a black and white checkerboard on the bottom. The CRT power-off animation is also really slow, and I noticed inside of moto recovery while wiping my user partitions I no longer have a progress bar, only a dashed line. The phone was working for a month on Gingerbread fine, so what could have caused this new issue? I have already reflashed again with droid4 utility and tried doing a factory reset. I am a noob and don't know how the "drivers" work for the display. Thanks.
Mods please leave this post in case someone else encounters this issue, but,
I solved it!
Apparently the Droid 4 Jellybean utility does not flash something correctly. It could be because I am using Windows 8.1 64 bit, or some other reason. I did verify the md5 of the zip and I verified the integrity of the unzipped files as well. It is a real noodle scratcher as to why it did not work. I did not notice it before but in addition to the graphical glitches my phone would also NOT TURN OFF. It was crazy.
Anyhow,
The solution to this issue (at least in my case) was to use RSDLite 5.7 and follow the tutorial here:
http://www.droidforums.net/threads/...a-droid-4-xt894-to-stock-windows-only.206972/
After going through that I am back up and running again. It is strange because my bootloader is 0A.77 just as before, and all the version information in Settings>About is the same. I hope I can help someone having the same issue. Good luck everyone.
Sometimes flashing fails, for no known reason.
Threads are not deleted unless they are reported.
Sent from my XT907 using Tapatalk
---------- Post added at 07:09 PM ---------- Previous post was at 06:56 PM ----------
Rsd lite flashes differently than the d4 utility.
RSD lite flashes more precisely but more likely to fail.
Sent from my XT907 using Tapatalk