Related
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
atquick said:
I'm not sure whats going on with my D3. However, I have RSD and I have .890 and .959 downloaded as well as Fastboot.
What I want to do is just wipe the phone completely and just flash it like its a brand new phone.
Anyone know how to do so? Please post a link or instructions, I would greatly appreciate it.
Click to expand...
Click to collapse
http://goo.gl/7NoAv
Androidsims said:
http://goo.gl/7NoAv
Click to expand...
Click to collapse
Tried that. It keeps failing saying something about size was not as expected or something like that.
Redownload?
Avelnan said:
Redownload?
Click to expand...
Click to collapse
I have. MD5 sums match up each time. Should I try removing the ext sd card?
I would redownload everything and try agian
littleneutrino said:
I would redownload everything and try agian
Click to expand...
Click to collapse
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
atquick said:
Alright, attempt will be made again. Should I redownload RSD again or just the sbf's?
Click to expand...
Click to collapse
Downloading the sbf's again. Went over to check and see if the phone was still on, The charging led is on, however the screen is off..
Held power, nothing. Held M + Power. Still nothing... Any thoughts on whats going on now?
I didn't see if you have pulled the SD card but yeah it can't hurt.
Sent from my DROID3 using XDA App
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
wattnxt said:
http://forum.xda-developers.com/showthread.php?t=1278056
Follow the first portion of the instructions on how to flash back to original 5.6.890. Note the making of a folder and it's name for the 890 flash.
Ignore the part about flashing the new ROM. These are the best instructions I've found so far for flashing back to stock via RSD lite.
Good luck, keep us posted.
Download and follow exactly and you'll be good to go.
Hope that helps.
Sent from my DROID3 using xda premium
Click to expand...
Click to collapse
It keeps failing.
Step 3 mbmloader.bin
Step 4 mbm.bin
Step 8 logo.bin
Step 9 'lbl'
I'm stuck.
Let me do some looking when I get home tonight. I remember there being a file for certain versions of XP that helped some people and they couldn't flash without it.
I never had it happen personally, but I know those that did were terribly frustrated.
I also hear the 959 version is easier to flash for some reason. Never flashed that version, so this is only hear-say. But I know it did flash easier according to posts.
I will try to dig up a link for you.
i am getting the same thing also getting the bad CG boot.. now this may be a fix but idk how this guy got it it.. i have been asking eveywhere maybe you guys could help me... here is the thread http://forum.xda-developers.com/showthread.php?t=1248721
I found this by Psouza. He is likely the foremost expert on making things easy as far as unbricking your D3. Rumor has it he has a set of unbrick tools floating around this forum somewhere, though I haven't found it yet. Try in the Development thread, for sure it has to be there somewhere.
Post number 84
psouza4 said:
For those of you having problems flashing this and/or are suspicious of flashing ebr, mbr, and parts of the bootloader, you can selectively just flash the rest of it.
See attachment.
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=715510&d=1315657647
Hope this helps.
I also saw that flashing the pre-installs file alone first helped someone. That file borked on me once, but I was able to adb it over and then execute it via adb to get my phone unbricked.
Please let us know what works for you, as all of this is a work in progress right now.
Good luck!
i don't know to much about adb and are looking for help on pre-installed files. I don't understand what that means or how to go about it? i also cant get past the bootloader screen, "invalid CG version". i can not boot up at all.
How bricked are you? can you boot into CWM? Are you able to boot into tools, or how far can you get?
What version were you running? 5.959 (stock) or 6.890 OTA or Leaked OTA or Soak test (all the same as far as 6.890 goes).
i can get into boot tools and just tryed another flash got to step 6 till it failed instead of 3.. I'm running stock. Cannot get passed boot tools... scratch all that just tried to flash again just on the off chance it mnight work and i got it. Going to try and re-root and CWN recovery with sdteel froids rom... will keep you in the loop
Awesome!!
Here is the link about the adb commands for preinstall.sh
http://forum.xda-developers.com/showpost.php?p=17196391&postcount=88
It helped me when I borked my leaked update. I ran into the same problem as limaxray did with too many files in /system. So make sure you clean out any apps you made into system apps before trying the update via the standard update route, and that all stock system apps are in place and properly named.
I had to remove some that updated partially with the leaked update when mine borked. I used the posted system dump to push them to the phone and then the update ran properly and updated them anyhow.
If for some reason re-rooting doesn't work for you. Go to /system/bin and remove su, busybox. Do the same in /system/xbin. For some reason if you already have them in there when you run the process, it will say success but no root after reboot. My 2c as it happened to me. You do not need to remove superuser.apk, but you will have to update it in the market after you re-root.
Congrats!!
I see now too there is a fastboot and moto-fastboot. moto-fastboot has worked for some who had issues from what I've found.
Keep us posted, and smile knowing you've recovered from a bork; none of us got where we are without doing it at least once, so you're in good company.
re-rooted and installed bootstrap, just got steel droid all loaded up and all is good.... thanks for your speedy responses and detailed instructions and links. I realy think all that happened was i took everything aet it sone last time tried to flash and it went threw. All i used was RSD lite and flashed the 8.6.590 fast boot file and after a several retries it went threw. If anyone needs help on this i will post the file links if you need the ones i used
I would have posted this question in response to these instructions, however I'm still a noob on these forums, and haven't met my 10 post quota yet.
http://forum.xda-developers.com/showthread.php?t=1255198
My question is will this recovery method work for Bell Canada users, or will it only function for Verizon users?
I've installed AOKP a few months back, and while I enjoy it, I've lost support for some key features; namely HDMI, which is disappointing. When I tried recovering to the stock rom to hold me over until some new features and revisions show up on the mod scene, I found out my system backup was corrupt.
I have found a few downloads to system images, however every one I have found link to files that are now taken down. Can someone upload a current system dump?
I can set you up when I get home later
Sent from my XT860 using xda premium
try here http://sbf.droid-developers.org/umts_solana/list.php
What would happen if I flashed the Bell firmware to a Verizon Droid3?
Will it change the radio.img
Will I have to unlock it again?
Will everything still work?
I am using 5.7.906.xt852
jazz53 said:
What would happen if I flashed the Bell firmware to a Verizon Droid3?
Will it change the radio.img
Will I have to unlock it again?
Will everything still work?
I am using 5.7.906.xt852
Click to expand...
Click to collapse
Quite honestly no one knows. Wanna be the first?
Sent from my XT860 using xda premium
I'm really eager to find out. Worst case, you could always just flash the bell XT860 radio afterwards and see what happens!
I am way too new at this to try experimenting with untried solutions
I just barely figured out how to root my ph. Still working on how to flash.
Is it the same as installing a ROM?
jazz53 said:
I am way too new at this to try experimenting with untried solutions
I just barely figured out how to root my ph. Still working on how to flash.
Is it the same as installing a ROM?
Click to expand...
Click to collapse
No, you have to completely reflash your device and will have to re-root it. I think you should give it a go though
You'll need to download RSD Lite and download the XT860 Bell SBF files (they are about 500mb to download). Also make sure you FULLY CHARGE your phone, just in case you run into any issues. I think you can find an SBF how-to doc in the development forums. Please keep us posted.
Are you on Verizon? Because if you and this works, you probably won't be able to use it with them anymore.
Nope, I am on PCMobile without a data plan, use wifi.
I think maybe I'll try a Rom first.
So I'm posting here because I'm mostly a lurker and have found almost every answer I need by searching and using google.
[My post count is < 10]
Is there a .906 FXZ available for the Droid 3, if so, where may I find it?
I followed the guide almost 100% [no beer]: http://forum.xda-developers.com/showthread.php?t=1686911
It did allow me to unbrick the device. But the .906 update.zip file fails at flashing BP, I reboot and the phone shows system version .906 but I don't think the update finished 100%
I can still charge the phone, but I can't seem to get the .906 update to install properly, and the VRZ_XT862_5.5.1_84_D3G-55_1FF_01.xml fails flashing at cdt.bin [RSD, have not tried moto-fastboot CLI, though it has worked for me in the past with bionic and DX2 when RSD just wouldn't]
I know very little about the Droid 3, i got this off CL last night for 20 bucks, I have had the OG Droid A855, D2G A956, DX MB810, DX2 & Bionic and have successfully flashed, reflashed, rooted, unrooted, safestrapped and everything else under the sun with these devices - but these devices have SBF/FXZ files available for the latest system version and all I can find for the D3-XT862 is what seems like user created files.
So..a lil help please, first, does anyone have an MD5 for the 906 update.zip? I think this is my first step since the 906_1_click.exe works fine and brings me back to 890 system. {EDIT: found the MD5 8dcb7b93e2b4e4f3f44e99b24faab1ae and it matches the file on my SDCard}
Hopefully someone can make sense of this post and point me in the right direction. Thanks in advance.
EDIT: If anyone has a stock D3 I would love to know if there are any settings that may have been changed in QXDM/QPST or DFS CDMA Tool that I need to restore back to stock that could possibly be stopping the PRL/ERI from loading and being restored after factory data reset {RUIM should be set to ?}
moto-fastboot didn't work:
Code:
C:\_DATA\_phones\_motorola\XT862\VRZ_XT862_5.5.1_84_D3G-55_1FF_01.xml\VRZ_XT862_
5.5.1_84_D3G-55_1FF_01.xml>moto-fastboot flash cdt.bin cdt.bin
sending 'cdt.bin' (16 KB)... OKAY [ 0.008s]
writing 'cdt.bin'... INFOPreflash validation failure
FAILED (remote: )
906 update.zip error log
Code:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
updating HS mbmloader...
updating mbm ...
updating lbl ...
updating devtree ...
updating cdrom ...
updating logo.bin ...
updating BP ...
assert failed: motorola.motoflash("/tmp/bp.img")
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted.
final EDIT while awaiting response from anyone: If i root the phone, is there an app available that will allow me to write a new PRL/ERI? I thought I ran across something for PRL for Samsung Sprint phones, but Ive never seen anyone mention ERI. Also, I think this phone may have port damage or possibly a corrupted file system or maybe even bad flash memory [or possibly had 2nd init installed before the seller bricked it] and I'll tell ya why. When i plug the phone in to my pc, I cannot do anything with it in DFS CDMATool or QXDM while in BP Tools mode [4 drivers loaded, even the famous mysterious LTE BP driver]. While in a normal bootup I cannot keep the storage mode set to anything other than PC mode, the phone loses connection and resets to PC mode after 1-5 seconds from selecting Mass storage mode.
real final edit (until i think of another useful piece of information that i can post before someone asks me):
Code:
System version (all versions listed are after failed .906 update.zip)
5.7.906.XT862.Verizon.en.US
Kernal version
2.6.35.7-g5fa4155
[email protected] #1
Build number
5.5.1_84_D3G-66_M2-10
Baseband version (unknown)
ERI version (unknown)
PRL version (unknown)
last edit before i give up for the night: i used moto-fastboot to flash radio.img from the 906 sbf.7z but that did not restore my baseband, prl or eri.
well you probably know this
The Preferred Roaming List (PRL) is a database that assists the mobile in the acquisition and selection of a serving CDMA network.
ERI version: (Enhanced Roaming Indicator)extends the usage of the roaming indicator
Click to expand...
Click to collapse
PLR should get updated, with *228 option 2
I'm guessing you were just trying to get it up and running to resell
but haven't tried to activate
but don't know about ERI or baseband fix
you verified model number XT862 and not XT860 Milestone 3 GMS only
sd_shadow said:
well you probably know this
PLR should get updated, with *228 option 2
I'm guessing you were just trying to get it up and running to resell
but haven't tried to activate
but don't know about ERI or baseband fix
you verified model number XT862 and not XT860 Milestone 3 GMS only
Click to expand...
Click to collapse
The plan was to ship it to a family member who lives in NY after I activate it on Page Plus, but sadly I think I'm stuck with it as they need service Tuesday.
The weird part is that the SBF restore mentioned in the other thread does not restore my baseband, prl or eri. Nor does fastboot flash radio. I've never had a problem restoring a flashed phone using SBF/FXZ but this one won't take which makes me think something has been changed in RUIM but I can't read the phone while in BP Tools from DFS or QXDM, I'll try QPST after I read up on root & safe strap.
Yes, verified to be a Verizon Droid 3 XT862 with clean ESN.
I'm going to root this thing today and install 2nd init/safestrap [not sure which as of right now, i need to do more reading] and maybe then I can force the update.zip to be applied? I'm not really sure what the error message means.
edit: looks like installing an update.zip from a custom recovery is not recomended so i won't even try that.
i have a feeling that this phone was on the original .959 firmware before it was bricked as the seller told me that even if i can fix it, it had a blue camera....sigh. i should have sbf'd the original firmware and then the legit .890 sbf, but i went straight to the .890/906 sbf and now i have no baseband, prl or eri. so hopefully a .906 fxz gets leaked before cheesecake gets shut down permanently.
another edit: logic is telling me that i get an error while flashing the .906 OTA update zip because i don't have a baseband after SBFing .890, so the update installer gets error 7. amiright?
yet another edit: i see people have flashed the xt883 baseband to unlock GSM, can i do the same to get service with verizon? radio.img from the .890/.906 SBF does not work as i still have "unknown" as showing for my baseband version (also, why does everyone call it an sbf, when it is an FXZ?)
final edit: so i guess i'm waiting on redsox or someone from TBH to come to my rescue, i've searched the forums and anyone with a similar issue seems to have never resolved it. if the issue does get resolved i promise to post step-by-step instructions. [to reiterate, i can flash the radio.img from moto-fastboot, but that does not restore my baseband, prl or eri, which is probobly why i have issues getting this phone to connect while in diag mode]
SOLUTION:
VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml.zip fixed the problem.
I'm so glad a proper sbf/fxz was released/leaked some time this year.
afextwin said:
SOLUTION:
VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml.zip fixed the problem.
I'm so glad a proper sbf/fxz was released/leaked some time this year.
Click to expand...
Click to collapse
Hey, so was the original problem that all the phones system information was "unknown"? such as the IMEI and the Baseband version etc under "About Phone" in settings?
dinosaur swagg said:
Hey, so was the original problem that all the phones system information was "unknown"? such as the IMEI and the Baseband version etc under "About Phone" in settings?
Click to expand...
Click to collapse
yes, that was the problem.
the baseband was broken and could not properly be written to the phone using moto-fastboot or any baseband i could find.
I did not try to flash just the baseband from this particular fxz/sbf but i'm sure that would work too.
in the past, the .906 sbf was not official and was a mashup of previous version + new.
afextwin said:
yes, that was the problem.
the baseband was broken and could not properly be written to the phone using moto-fastboot or any baseband i could find.
I did not try to flash just the baseband from this particular fxz/sbf but i'm sure that would work too.
in the past, the .906 sbf was not official and was a mashup of previous version + new.
Click to expand...
Click to collapse
My Droid 3 currently has that problem and I thought I tried everything so I just wrote it off as a hardware issue. So is the problem causing all of the system information to be 'unknown' due to a broken baseband? I hate to be a pain but would you be able to provide us with the link you used. I did sbf the phone back to stock but perhaps used the wrong one.
Edit
I just used VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml.zip through RSDlite but still have the ERI, PRL, IMEI, Baseband, MIN, MEID and everything else as 'unknown'. This must be a hardware issue if the above sbf didn't work right? Did you flash the full xml through RSD? Grrrrrr wish this had worked
dinosaur swagg said:
My Droid 3 currently has that problem and I thought I tried everything so I just wrote it off as a hardware issue. So is the problem causing all of the system information to be 'unknown' due to a broken baseband? I hate to be a pain but would you be able to provide us with the link you used. I did sbf the phone back to stock but perhaps used the wrong one.
Edit
I just used VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml.zip through RSDlite but still have the ERI, PRL, IMEI, Baseband, MIN, MEID and everything else as 'unknown'. This must be a hardware issue if the above sbf didn't work right? Did you flash the full xml through RSD? Grrrrrr wish this had worked
Click to expand...
Click to collapse
Try http://sbf.droid-developers.org/cdma_solana/list.php for the file download. You can try to flash using motofastboot-adb, but I just used RSD Lite 6.1.4 for this sbf. I believe NONHLOS.bin is your baseband from this package. If nothing works...brick it by flashing a bad firmware and then restore it with the proper sbf as linked above. this should force an efs clear. i know, i know, it sounds like very very bad advice. but what do you have to lose at this point? i've never hard bricked a moto by flashing the wrong firmware on a (VZW) motorola or samsung and i flash about 30 vzw moto droid phones a day. and believe me i have accidentally chosen the wrong file many many times.
afextwin said:
Try http://sbf.droid-developers.org/cdma_solana/list.php for the file download. You can try to flash using motofastboot-adb, but I just used RSD Lite 6.1.4 for this sbf. I believe NONHLOS.bin is your baseband from this package. If nothing works...brick it by flashing a bad firmware and then restore it with the proper sbf as linked above. this should force an efs clear. i know, i know, it sounds like very very bad advice. but what do you have to lose at this point? i've never hard bricked a moto by flashing the wrong firmware on a (VZW) motorola or samsung and i flash about 30 vzw moto droid phones a day. and believe me i have accidentally chosen the wrong file many many times.
Click to expand...
Click to collapse
Yo, I think I'll stick with RSD as I'm not very familiar with adb. Okay so what you're recommending is to flash any old rom, lets say miui for my HTC DZ to brick the droid before sbf'ing it? I'll give it a shot but I can't understand why the efs wouldn't have been cleared during the sbf whereas if the droid were bricked, then it would clear the efs. Anyway I'll give that a shot. Cheers for the help by the way
could try one or both of these, they use an automated moto-fastboot.exe with batch.exe
sometimes moto-fastboot works when rsd lite fails, and this is just one click
Official .906 1_click sbf .exe [03-28-2013] (uses extracted 906 .xml)
or
.906 1-click-sbf.exe + tools [06-01-2012] (uses 906 update files and parts from 890 xml)
dinosaur swagg said:
...I can't understand why the efs wouldn't have been cleared during the sbf whereas if the droid were bricked, then it would clear the efs
Click to expand...
Click to collapse
Honestly I don't know why either, but I do know that every time I misflash and reflash the phone efs clears, but for some reason rsd does not always clear /data /cache efs etc when successfully flashing an sbf/fxz/xml. odd, i know.
But I would also try what the poster above me suggests, use a few different fxz's, like the 906 mashup that was released before the official one. i highly doubt the radio went bad.
afextwin said:
Honestly I don't know why either, but I do know that every time I misflash and reflash the phone efs clears, but for some reason rsd does not always clear /data /cache efs etc when successfully flashing an sbf/fxz/xml. odd, i know.
But I would also try what the poster above me suggests, use a few different fxz's, like the 906 mashup that was released before the official one. i highly doubt the radio went bad.
Click to expand...
Click to collapse
I don't even think I have an efs folder. I checked using a root explorer. Isn't it supposed to just be located at the very root of the phone (/). Could this mean its been deleted or what? And if it has is this phone a lost cause i.e there's no fix for that if there's no backup of it?
dinosaur swagg said:
I don't even think I have an efs folder. I checked using a root explorer. Isn't it supposed to just be located at the very root of the phone (/). Could this mean its been deleted or what? And if it has is this phone a lost cause i.e there's no fix for that if there's no backup of it?
Click to expand...
Click to collapse
I will root a droid 3 and let you know if i see a folder, i'll reply/update this post by tomorrow.
can't remember where the efs folder is, but I could not find it on mine
Sent from my XT862 using Tapatalk 2
Maybe he meant emstorage (which includes, I believe, the internal "sd card").
I don't think so, I believe I have found it on other motorola devices, but didn't plan on messing with it.
What is the /efs folder?
This is a very sensitive system folder that contains Phone-specific information such as the IMEI (encrypted in the nv_data.bin), wireless devices MAC addresses, product code (also in the nv_data.bin), and much more. Often users trying to change product codes or trying to unlock the mobile will end up corrupting data in this location.
Click to expand...
Click to collapse
---------- Post added at 07:12 PM ---------- Previous post was at 06:45 PM ----------
the efs folder may only be accessible radiocomm or cdma workshop, but I don't know
sd_shadow said:
I don't think so, I believe I have found it on other motorola devices, but didn't plan on messing with it.
---------- Post added at 07:12 PM ---------- Previous post was at 06:45 PM ----------
the efs folder may only be accessible radiocomm or cdma workshop, but I don't know
Click to expand...
Click to collapse
You are correct.
Very rarely does the physical hardware modem/radio go bad in this phone.
@dinosaur swagg, have you tried flashing old xt862 firmware and then flashing the latest?
It should softbrick if you try to downgrade, and hopefully reflashing the correct .xml will kick it into gear.
Also, have you tried moto-fastboot and just flashing the radio partition?
afextwin said:
You are correct.
Very rarely does the physical hardware modem/radio go bad in this phone.
@dinosaur swagg, have you tried flashing old xt862 firmware and then flashing the latest?
It should softbrick if you try to downgrade, and hopefully reflashing the correct .xml will kick it into gear.
Also, have you tried moto-fastboot and just flashing the radio partition?
Click to expand...
Click to collapse
Cheers for the help guys. I have successfully softbricked it but it has been bricked for ages as the battery is low and unable to be sbf'ed because of this. I'm currently waiting on a replacement battery. I have tried on more than one occasion to flash just the radio but has been unsuccessful, I also tried flashing the XT883 radio and pushing the appropriate build.prop but still no fix. By "old firmware" do you mean the .890 firmware? Thanks
dinosaur swagg said:
Cheers for the help guys. I have successfully softbricked it but it has been bricked for ages as the battery is low and unable to be sbf'ed because of this. I'm currently waiting on a replacement battery. I have tried on more than one occasion to flash just the radio but has been unsuccessful, I also tried flashing the XT883 radio and pushing the appropriate build.prop but still no fix. By "old firmware" do you mean the .890 firmware? Thanks
Click to expand...
Click to collapse
yessir i do. i had flashed every firmware i could think of before the official FXZ was released, i could never actually brick the device - the .890/906 mashup worked for unbricking but would not fix the radio issue. so that mashup was the last thing i flashed before flashing the official FXZ.
i'm sorry to hear about the dead battery. i recommend you order a universal chinese battery charger - the only issue is you may have to use additional copper wire since the droid 3 has that goofy slotted style for battery contacts.
something like this: http://www.amazon.com/HDE-Universal-Mobile-Battery-Charger/dp/B001AHU6QU/
just be careful not to leave it on too long.
dinosaur swagg said:
Cheers for the help guys. I have successfully softbricked it but it has been bricked for ages as the battery is low and unable to be sbf'ed because of this. I'm currently waiting on a replacement battery.
Click to expand...
Click to collapse
the charger afextwin linked is probably fine, especially if you have multiple devices, but this charger works good and is made for Droid 3 batteries, ,if you have other motorola devices or amazon Kindle the Motorola Factory Cable Adaptor by Team Black Hat is also good to have.
I have tried on more than one occasion to flash just the radio but has been unsuccessful, I also tried flashing the XT883 radio and pushing the appropriate build.prop but still no fix. By "old firmware" do you mean the .890 firmware? Thanks
Click to expand...
Click to collapse
if you are not sure which software version is on phone check the ap fastboot version.
0A.33 version is 5.5.959
0A.53 is 2.3.4/5.6.890.
0A.64 is 5.7.906
so if you have ap fastboot 0A.53, use 5.5.959 xml then use 890 or 906
or ap fastboot 0A.64 use 890 then 906
but I would try
.906 1-click-sbf.exe + tools [06-01-2012]
first if you haven't yet
Bought my bionic a while back and rooted it and used safestrap to use a JB rom.
Now that JB is out for the bionic ive been trying everything i can think of to update it. I've tried unrooting, uninstalling safestrap via the app itself and multiple factory resets. I try to update and it will get to about 25% after rebooting then of course the lil droid will die and i get a software update failed message.
Is there something i missed?
Gabraham said:
Bought my bionic a while back and rooted it and used safestrap to use a JB rom.
Now that JB is out for the bionic ive been trying everything i can think of to update it. I've tried unrooting, uninstalling safestrap via the app itself and multiple factory resets. I try to update and it will get to about 25% after rebooting then of course the lil droid will die and i get a software update failed message.
Is there something i missed?
Click to expand...
Click to collapse
Follow this thread: "http://forum.xda-developers.com/showthread.php?t=2242075"
"mc_akiong" has the solution in the third post. Go and thank him for it.
pmrmx774 said:
Follow this thread: "http://forum.xda-developers.com/showthread.php?t=2242075"
"mc_akiong" has the solution in the third post. Go and thank him for it.
Click to expand...
Click to collapse
i cant seem to locate the file he is referring to. What general area of the phones files should it be in?
Gabraham said:
i cant seem to locate the file he is referring to. What general area of the phones files should it be in?
Click to expand...
Click to collapse
You need the FXZ file from Verizon. You unzip it and open the file suggested. edit out the two entries in notepad and save. Then, run RSD to apply to your phone. this hould be a US based phone.
You can get the file cdma_targa_9.8.2O-72_VZW-22_cfc.xml.zip at "http://forum.xda-developers.com/showthread.php?t=2240725"
Been having trouble getting rsd lite to recognize my phone . could these issues be related ?
Sent from my ME172V using xda app-developers app
downloaded the cdma, properly booted my phone into fastboot with RSD lite, flashed the modified cdma zip ( sans step operation lines) worked like a charm, if not a bit overly complex. thanks much
I'm probably not going to get an answer, but I'm going to ask anyway. My wife's phone was running an old version of CM, I can't remember which one it was though. But anyway, it was running like crap. She would tap an icon and it would take forever to load the app or it would just freeze totally.
So I thought about it and installed safestrap on it and flashed CM12 to slot 1. I guess I flashed the other older rom to the stock slot. I don't know how I did that, I thought only stock goes there. It's been a long long time since I messed with her phone.
So now she has the first crap rom on the stock slot and CM12 on slot 1. The problem now, is that CM12 runs like crap on her phone too. It's like old people screwing in molasses.
My question now, is do I just find the original stock rom and flash it to the stock slot? It won't let me wipe the data from the stock slot, so I guess I have to dirty flash the stock rom over top of it. Is that a good idea? And also, where do I find the correct stock rom to install? It's pretty old and I don't know what the last known stock rom for it is called or where to find it.
She's stuck to this phone for sentimental reasons, she won't give it up. I'd at least like to make it run smooth again. If anyone helps me with getting her phone back to normal, I would truly appreciate it.
Thank you.
You could find an fxz file for jellybean it's like 98.2 or something boot into fastboot and use red lite to flash the fxz, that would put you back to stock, then if you look in the razor droid section they have one click root that works for our phone too I believe, then you can reinstall safestrap and have it back to normal,
Also speeds can decrease with your older sdcard if the ROM slot is on SD are, I am not sure if its on emmc or sdcard but if it is on sdcard it could slow down as the card has aged, better cards faster read
I
thanks for the response. I just found Blur_Version.5.9.905.XT875.Verizon.en.US(67246). move this zip over to my external card and then boot into recovery. I was then going to delete slot 1 and flash this rom into the stock slot. Would this work?
It all depends what boot loader your on, if you are on the new safestrap 3.7 no it won't work, if your on old like 2 something or gingerbread still it will, but if you flash a ROM from before jellybean and updated to jellybean you will have to use fastboot to flash no !after what, most people would call it a BRI l cause they can't figure out how to use rsdlite and fast lot, and it probably won't work because you need to flash that using rd
Sdlite
1. Google rsdlite fastboot flash tool
2. Google droid bionic jellybean fxz file
3. Download both files and programs
4 place a working folder on your desktop
5. Turn droid bionic on if fuilly charged into fastboot mode with power + down I believe, might be power plus + volume up and down, might be power plus volu!e+ up you can google that to how to boot into bionic fastboot
6. Once bionic is booted into fastboot and you have the fxz file and rsdlite open rsdlite
Make sure your bionic is connected to your computer rsdlite will see its in fastboot mode, then you can flash the fxz
I would do so!e research how to do it before I did, I ha e flashed a lot of fxz but if your new you can mess up, with a bionic its almost impossible to brick it because it has fast lot and can flash an fxz, but still if you don't know what your doing you might give up trying to fix it.
There are some fxz out there made to not flash data, or have a fix for a cpommom error, when trying to flash fxz sometimes you get an error because of fb_mode_set and fb_mode_clear you have to google how to remove those lines if you get an error there is an fxz out there with those lines already removed you just gotta find it
Sent from my Z970
[email protected]:/ # id
uid=0(root) gid=0(root) context=u:r:init:s0
simple root guide
http://forum.xda-developers.com/showthread.php?t=3110178
OK, I will try what you said tomorrow. But for now though, do I just boot into safestrap and delete rom slot 1 and then shut the phone off? Then boot to fastboot like you said and flash Blur_Version.5.9.905.XT875.Verizon.en.US(67246) with rsdlite? It's been a while since I've done this, it's really hazy, but familiar. I appreciate you taking the time to help me out with this. Thank you very much.
DroidisLINUX said:
You could find an fxz file for jellybean it's like 98.2 or something boot into fastboot and use red lite to flash the fxz, that would put you back to stock, then if you look in the razor droid section they have one click root that works for our phone too I believe, then you can reinstall safestrap and have it back to normal,
Also speeds can decrease with your older sdcard if the ROM slot is on SD are, I am not sure if its on emmc or sdcard but if it is on sdcard it could slow down as the card has aged, better cards faster read
I
Click to expand...
Click to collapse
I got around to reflashing it to day, worked great, just had to edit 2 lines in the .xml of my rom, but it worked great. would you mind pointing me in the direction of the razr one click root? all I'm seeing is install a virtual machine on my pc, I did that before I remember, but if there's an app I can install to the phone and it would do everything, that would be great. thanks for all the help.
Its in the razor forum moto razor one click root Google should find it, or look threw xda razor forum for it, it should work on bionic if not then use the virtual box tiny Linux install methld
Sent from my DROID BIONIC using XDA Free mobile app
DroidisLINUX said:
Its in the razor forum moto razor one click root Google should find it, or look threw xda razor forum for it, it should work on bionic if not then use the virtual box tiny Linux install methld
Sent from my DROID BIONIC using XDA Free mobile app
Click to expand...
Click to collapse
I don't think that first one you mentioned works for the bionic. However, the virtual machine does work and saferoot also works.