Database Develop

Going back to stock need help!

I need to get my Droid Bionic back to factory stock. I tried flashing the fxd file using rsd lite. For some reason it fails on step 1 everytime. I was on the liberty 2.0 rom but I went back to stock motorola rooted rom using cwm. The thing now is everytime I turn my phone off or restart it, it goes to the fastboot screen and shows some error about the failed flashing process. I can press the power button to turn the screen off then hold the volume keys while pressing the power button to get into the stock recovery. From there I can reboot normally and everything works fine. I am supposed to be selling this thing and I am going to be meeting at verizon so obviously I need to get back to factory. This is very confusing and any help would be greatly appreciated thanks
EDIT: Im on 5.5.886 as well..

Can anyone help with this..?

Did you get anywhere with this? I'm very interested in trying the 901 update and am also on Liberty 2.0 (5.5.886). The data drops have been brutal, and knowing that there seems to be a solution out there for me if I had not rooted just makes it worse. I'll go back to stock unrooted for the solution

Have yall tried the 43v3r root, I think option one to set your phone back to stock? Did you do the 893 update? If so that's why you cannot RSD the phone regarless if it says 886 on liberty ROM. Use 43v3r root and do the option that will put your phone back to stock/43v3r rooted.
---------- Post added at 10:09 AM ---------- Previous post was at 10:02 AM ----------
SamuriHL said:
No don't do that. For sure don't do that as it will not work. You didn't make a backup of the stock rom when you did the 5.5.893 update before putting a custom rom on?? UGH. If that's the case and you don't have a nandroid backup of 5.5.893 then this is going to be a pain. Not impossible but will cause you some headaches. First thing's first. Go make a nandroid backup of your existing rom install. I'll see if I can put some steps together that'll get you upgraded.
---------- Post added at 03:38 PM ---------- Previous post was at 03:37 PM ----------
But not with RSD using the FXZ now that he's on 5.5.893, yea? That'd be...bad.
---------- Post added at 03:45 PM ---------- Previous post was at 03:38 PM ----------
1) http://rootzwiki.com/topic/5484-r3l...he-bionic-v21/page__view__findpost__p__127684
Get that, unzip it, run it, and choose option 1. That will put you back on 5.5.886 stock *system* but will not touch anything else. And will of course, will install permanent root.
2) http://www.multiupload.com/0ZEN69NGO2
Get that, throw it on the SD card, and boot to stock recovery. Flash it.
3) Now you are ready to try flashing 5.9.901 again
Click to expand...
Click to collapse
Thx to SamuriHL for helping me!!
This should do it for ya...

I flashed the RSD lite files in this link.
Restores you to complete stock.
It works
http://rootzwiki.com/topic/13105-a-easier-way-back-to-the-update-path/
Sent from my DROID BIONIC using xda premium

-----Duplicate post-----

[Q] And why did I leave my X2 again?...

Hey guys,
Ok, so here's the deal: I ruined my X2, completely unrelated to MODing, and opted for a 4G Bionic. Cool phone, but a totally different world from the X2. I can't even gain Root status. From what I gather this is mainly because I am on the new 5.9.902 build, which requires me to revert to an older version, gain root, flash forever root, THEN update? This is probably totally off base but any info is appreciated...Thx

Rooting 902 is easy:
Get the latest 5.5 moto-drivers here... USB and PC Charging Drivers -Motorola Mobility,Inc. USA
Make sure your device is in USB debugging mode,attach it to your PC.
Then use this to root.. http://dl.dropbox.com/u/63864500/motofail_windows.zip (for windows pc only)
Extract the entire zip file,and execute “run.bat”.

eye__dea said:
Rooting 902 is easy:
Get the latest 5.5 moto-drivers here... USB and PC Charging Drivers -Motorola Mobility,Inc. USA
Make sure your device is in USB debugging mode,attach it to your PC.
Then use this to root.. http://dl.dropbox.com/u/63864500/motofail_windows.zip (for windows pc only)
Extract the entire zip file,and execute “run.bat”.
Click to expand...
Click to collapse
Thanks bro, I'm on it now....
Alright, the problem is that when I open Motofail #1 my phone isn't recognized in "Charge Only" mode and #2 if I switch to "USB Mass" it roots but gives an error of not being able to push SU...

Any time man.
Use this guide for custom ROMs: http://www.droidhive.com/forums/ind...omrestore-instructions-for-droid-bionic-41412
---------- Post added at 10:49 PM ---------- Previous post was at 10:45 PM ----------
You in usb debugging mode and also turn on apps from unknown sources.

Still nothing. In Motofail, while it's doing it's thing it says things like "more than one device emulator" and a bunch of errors. IDK. What about if I Flashed to an earlier version? I read somewhere that you must have been rooted in a previous build to gain root in 902. True?

No. Motofail works flawlessly.
You have your phone booted normally?
---------- Post added at 11:11 PM ---------- Previous post was at 11:08 PM ----------
Make sure usb debugging and appa from uknown sources are checked in setting>>>apps>>>development
Try using rear usb port too.

Yeah dude, just brought it home from Verizon. I haven't done anything...

You downloaded all the files to your pc, right?

MathiasKnight said:
Yeah dude, just brought it home from Verizon. I haven't done anything...
Click to expand...
Click to collapse
To be on the safe side, reinstall the drivers.
Here's Moto's page where the most updated drivers are kept: http://developer.motorola.com/tools/usb_drivers/handset_usb_driver/
After you've reinstalled, reboot your PC.
While your PC is rebooting, ensure that USB Debugging is enabled, as well as enabling "Unknown sources".
Once your PC is all the way back up, plug in your Bionic, set it to Charge Only, then run Motofail on it. Motofail absolutely works on 5.9.902

I've gone through every method I can find short of flashing back, which now that I think about would have been a bad idea I think. I've even tried to manually achieve root by Command Prompt (MS, which is the same thing as Terminal Emulator...right?) And PowerShell, also Microsoft, but i'm not familiar enough with the line commands or what they're supposed to look like...but i'm studying. This will not get me down!! Are there even any decent stable ROM's for the Bionic?
****ty Bionic stock...I CAN'T ROOT!!!

Sorry, didn't mean to quote myself...
****ty Bionic stock...I CAN'T EVEN ROOT!!!

I've used Motofail several times since I got my Biionic earlier this year and it has worked flawlessly each time. Just incase you havent seen this link, this may help point you in the right direction and give you links to the correct drivers and the latest version of Motofail:
http://forum.xda-developers.com/showthread.php?t=1455888
And Eclipse 2.2 of Eclipse .904 work great, you can find them at:
http://eclipserom.com

I've had no problem rooting my Bionic (also a defector from X2). I've tried Eclipse 2.2 and Axiom ICS on my Bionic. I haven't tried Gummy or other ICS builds.
Not sure why I had a problem switching from Unsafe to Safe in Safestrap but I lost the ability to toggle (into safe) multiple times. What I saw of Eclipse it looked to be a very good gingerbread based rom. Too bad I couldn't keep it running. Axiom ICS seemed quite nice, too, but I've been afraid to toggle back into safe mode to continue using it.
Right now I'm running stock rooted .902.

Actually I was able to toggle back to safe mode this time. Back into Axiom...
Sent from my DROID BIONIC using XDA

Drunkula said:
Actually I was able to toggle back to safe mode this time. Back into Axiom...
Sent from my DROID BIONIC using XDA
Click to expand...
Click to collapse
If you have any issues, hit me up on gtalk.

Thx. Hopefully not needed!

I'm finally rooted on my Bionic, but only after I update to 905 and install the correlating 5.7 divers!! I can finally change this signature!!
****ty Bionic stock...I CAN'T EVEN ROOT!!!

Froyo 2.2 NVFlash Files

Anyone know where I can track down the 2.2 NVFlash files? Everything everywhere seems to be for honeycomb or pointing to dead spam links. I'm trying to downgrade from honeycomb (so obviously cwm images won't work) to diagnose whether a compatibility issue is related to honeycomb or the device.

Try here: http://d-h.st/users/TheManii/?fld_id=1682#files

looking for same thing.. I might be stupid but didn't find in link provided

PM "TheManii" and ask him to add the file(s) you require.

Thanks, yeah, the tools link didn't have anything. The streak 7 folder on the same site had a few files, but not full flash (just the bootloader and recovery, but without repartitioning and having the system.img it's a no-go). I'll try PMing. Thanks.

I have it, but I'm not going to share....
just kidding, I"ll get it up on my Google Drive, this weekend, and I'll have TheManii host it on his place as well.
---------- Post added at 01:58 PM ---------- Previous post was at 12:58 PM ----------
https://docs.google.com/open?id=0B0ozkQsJWIScSFVkOUdXcFFZWUE

I'm gonna build a proper set of NVflash payloads soon (though I did promise to do that months ago)
I've nearly cleared my to-do list though, so giveen's version should suffice for now

giveen said:
I have it, but I'm not going to share....
just kidding, I"ll get it up on my Google Drive, this weekend, and I'll have TheManii host it on his place as well.
---------- Post added at 01:58 PM ---------- Previous post was at 12:58 PM ----------
https://docs.google.com/open?id=0B0ozkQsJWIScSFVkOUdXcFFZWUE
Click to expand...
Click to collapse
Thanks, I've downloaded it and I'll try it when I get home. I found some of those nvflash images finally last night on some slow antiquated file sharing site, but I figured I'd have to try to put everything together (and probably screw up on that a few times in the process). After doing a bunch of things last night I got to the point where it wouldn't boot past the dell logo, so I reverted everything back and can now try it clean again. I'll post again if its successful (or not) in reverting from honeycomb to froyo -- hopefully not doing this until 3am again.

I've uploaded it here for the time being.
If/when I get proper payloads made I'll remove it.

Thanks Guys. I tried this last night and it worked great. I did end up putting on the stock t-mobile 2.2 package afterwards since the nvflash image had some things removed and I wanted to do stock testing, but it did work. Of course, after all that it didn't solve my Bluetooth compatibility issue with my stereo, but at least I know it's a hardware compatibility issue and not an OS one (though I was hoping for it to be the OS).
Thanks again!

dell streak 7, boot loop.. want to restore back to 2.2 (t-mobile)
giveen said:
I have it, but I'm not going to share....
just kidding, I"ll get it up on my Google Drive, this weekend, and I'll have TheManii host it on his place as well.
---------- Post added at 01:58 PM ---------- Previous post was at 12:58 PM ----------
https://docs.google.com/open?id=0B0ozkQsJWIScSFVkOUdXcFFZWUE
Click to expand...
Click to collapse
I don't know if it is me or what. I flashed all those files with NVflash, (to get back to froyo) and the darn thing doesn't load up. I can get into NVflash mode and fastboot, so I know it isn't bricked... It has to be something I am doing wrong. Also i don't know if it is worth noting, I have windows 7 (64 bit)

norcalnub said:
I don't know if it is me or what. I flashed all those files with NVflash, (to get back to froyo) and the darn thing doesn't load up. I can get into NVflash mode and fastboot, so I know it isn't bricked... It has to be something I am doing wrong. Also i don't know if it is worth noting, I have windows 7 (64 bit)
Click to expand...
Click to collapse
I'm on W7 x64 and have NVflashed back to 2.2 several times with no problem. It does take a bit of time to complete, does it take some time?

Fingerprint scanner not working

I've tried 3 different Roms and get this error..an error has occurred. ..try restarting etc etc.

Searching will give you full answer. Basically you have to go back to stock and start over.

here is the answer to you ur problem i had the same issue
http://forum.xda-developers.com/showthread.php?t=2919478

I tried that and still can not get it to work

jjr3211 said:
I tried that and still can not get it to work
Click to expand...
Click to collapse
Did you flash the latest modem NJ7?

As far as I know I did I flashed the the whole firmware package for nj7 still no luck
---------- Post added at 10:08 PM ---------- Previous post was at 10:05 PM ----------
Is there a place to check just to make sure

jjr3211 said:
As far as I know I did I flashed the the whole firmware package for nj7 still no luck
---------- Post added at 10:08 PM ---------- Previous post was at 10:05 PM ----------
Is there a place to check just to make sure
Click to expand...
Click to collapse
Get the phone info app from the market

jjr3211 said:
As far as I know I did I flashed the the whole firmware package for nj7 still no luck
---------- Post added at 10:08 PM ---------- Previous post was at 10:05 PM ----------
Is there a place to check just to make sure
Click to expand...
Click to collapse
settings about device baseband version

Well it is nj7 I have factory reset it a couple of times Odin back to stock a couple of times as well and still can not get it to work

[/COLOR]
jjr3211 said:
Well it is nj7 I have factory reset it a couple of times Odin back to stock a couple of times as well and still can not get it to work
Click to expand...
Click to collapse
I bought my white note 4 on Oct 30 or 31, can't remember, I read all the problems with this fingerprint scanner stuff, but I did not root for 2 days. and the past 2 days I did everything I was on NIH, and when testing my stock odexed roms, I had the fingerprints saved, but when I flashed, I couldn't log in, so when I deleted the saved fingerprints is when this happened, the error messages,
I did the firmwares so many times for the NIH, did not work... :crying: I then upgraded the firmware to NJ7 same thing, could not get it working...
I went to another tmobile store, and the guy went into downloader mode.. shocked me,, but he said I need to goto where I bought the phone to change it out, he didn't have any note 4... but he went and reset the phone and didn't work...
when I got home, I called tmobile 611... and went through the process and they said, they don't have any replacements, since I didn't buy the phone from them, they can't send a new phone, for me to goto the tmobile store I bought the phone, but no one has the note 4.. call back next week and we can send a replacement.
I called the corporate store today, they had 2 in black, I really wanted the white, but I took the black anyway.. lucky they were so busy, they didn't check the phone and swapped everything out.
I guess im gonna wait a bit before rooting and flashing the phone, to see what everyone finds out.

I have the same problem with my note 4. tried everything already so it may be hardware related. will buy a home button replacement from ebay hopefully that helps will update if successful

Stock rom without root or unlock only can enter bootloader

My nexus 6 using stock rom and update to the latest version thru OTA, without root or unlock bootloader. Yesterday it suddenly reboot and only allow to boot into bootloader. Cannot select recovery or factory mode, check the bootloader log show failed to validate the boot image or recovery image.
I've read many threads and try many methods to unloock the bootloader and flash the factory image but failed.
Anyone can help to get the nexus 6 back, thanks so much.

Probably going to have to do an RMA, you can't use any of the recovery options (fastboot, custom recoveries) with a locked bootloader, that is the whole point of it being locked.

Since we're now suggesting RMA, I have to ask...
Have you tried in the bootloader screen "fastboot oem unlock"?
Maybe you have, but your problem description is really pretty vague.
scryan, not trying to tread on your toes, and I may be completely wrong (about to fall asleep) but isn't the whole point of "fastboot oem unlock" that it runs in bootloader specifically to unlock it?

dahawthorne said:
Since we're now suggesting RMA, I have to ask...
Have you tried in the bootloader screen "fastboot oem unlock"?
justMaybe you have, but your problem description is really pretty vague.
scryan, not trying to tread on your toes, and I may be completely wrong (about to fall asleep) but isn't the whole point of "fastboot oem unlock" that it runs in bootloader specifically to unlock it?
Click to expand...
Click to collapse
I am sorry as this is my 1st post here. My Nexus 6 was not rooted and even not enable "usb debug" or "oem unlock" setting.
I've already tried "fastboot oem unlock" and failed. I've also tried "fastboot flashing unloock", it said ok but restart the bootloader and it still show locked.
I've also tried the Nexus Root Tools too to unlock or flash the factory image, recovery image or boot to twrp but all failed too.

Then you have no choice but to request a RMA. To be able to unlock the bootloader so you can then flash a stock ROM, you have to enable Developer Options, then in Developer Options enable both USB Debugging and OEM Unlock.

Have you tried the hardbrick tread? Not sure if this will work with locked bootloaders. http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:06 PM ---------- Previous post was at 08:50 PM ----------
Have you tried fastboot reboot-recovery to enter recovery? With or without the "-", I forget the proper form. With locked bootloaders I don't think u can flash anything from recovery. Plus it may be a hardware issue not necessarily software related.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
But if you can enter recovery maybe you can factory reset and at least get it to boot!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:03 PM ---------- Previous post was at 09:07 PM ----------
What version of fastboot are you using, old fastboot may not work properly.
Sent from my Nexus 6 using Tapatalk

Jnewell05 said:
Have you tried the hardbrick tread? Not sure if this will work with locked bootloaders. http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:06 PM ---------- Previous post was at 08:50 PM ----------
Have you tried fastboot reboot-recovery to enter recovery? With or without the "-", I forget the proper form. With locked bootloaders I don't think u can flash anything from recovery. Plus it may be a hardware issue not necessarily software related.
Sent from my Nexus 6 using Tapatalk
---------- Post added at 09:07 PM ---------- Previous post was at 09:06 PM ----------
But if you can enter recovery maybe you can factory reset and at least get it to boot!
Sent from my Nexus 6 using Tapatalk
---------- Post added at 10:03 PM ---------- Previous post was at 09:07 PM ----------
What version of fastboot are you using, old fastboot may not work properly.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Thx so much for your reply, I've tried the hard-brick thread but can't install the qualcomm driver.
I plan to contact the Google see whether it can help me since I am in HK and my Nexus 6 is not directly bought from HK Google.
It really quite depress me since I do nothing with the phone, I do not flash any custom rom, do not root or unlock bootloader, just normal use it then suddenly crashed .... >_<

this exact same thing happened to my wife's phone just a month ago... and the sad thing is the phone was just bought new for only 2 months or so. never installed any custom roms, never rooted, etc. and now i wish that i did so that i could have at least turned ON that option in Developers Option to "allow OEM Unlock" and if i did, it should've been an easy fix.
i never had this kind of issue before thats why i thought there is nothing important to turn on in the Developers Option. they should've made that information more available and even point it out on the Update but they didn't which sucks.
i also tried to contact Motorola US but since im not in the US, even though the phone is bought in the US via Ebay, they weren't able to help and sent me to another Motorola site for my region. i'm trying it now and i still cant go through the site...
it's really depressing when this kind of things happen... i hope in the future there would be some kind of fix for this. i heard if we can get a signed System that we could flash into the phone then there's a chance it could work but as of now, i keep checking for information about this and hoping someone came up with something...
hope this thing won't happen to anyone else and if you got a Nexus 6, make sure to turn On "Allow OEM Unlock" on your phone.

quinceyr said:
this exact same thing happened to my wife's phone just a month ago... and the sad thing is the phone was just bought new for only 2 months or so. never installed any custom roms, never rooted, etc. and now i wish that i did so that i could have at least turned ON that option in Developers Option to "allow OEM Unlock" and if i did, it should've been an easy fix.
i never had this kind of issue before thats why i thought there is nothing important to turn on in the Developers Option. they should've made that information more available and even point it out on the Update but they didn't which sucks.
i also tried to contact Motorola US but since im not in the US, even though the phone is bought in the US via Ebay, they weren't able to help and sent me to another Motorola site for my region. i'm trying it now and i still cant go through the site...
it's really depressing when this kind of things happen... i hope in the future there would be some kind of fix for this. i heard if we can get a signed System that we could flash into the phone then there's a chance it could work but as of now, i keep checking for information about this and hoping someone came up with something...
hope this thing won't happen to anyone else and if you got a Nexus 6, make sure to turn On "Allow OEM Unlock" on your phone.
Click to expand...
Click to collapse
Hi, quinceyr, I've just tried the below thread and restore my Nexus 6 back and only draw back is updated to Android N preview version. I've tested for a while seems work fine and will keep monitor for a period.
http://forum.xda-developers.com/nexus-6/help/command-device-corrupt-update-t3362317/page2
Hope your Nexus 6 will recover back.