Related
If you aren't holding a bricked bell canada droid 3 in your hand don't flash this
Neither myself or anyone that I've mentioned will accept any responsibility or liability for anything you do to your phone.
All this info is just consolidate from 2-3 different threads but buried among a few different posts. This is just a quick and dirty for unbricking our bell models, trying to avoid a step by step on how to use rsd etc since all that information is available in posts/threads that I've linked below.
If you aren't holding a bricked bell canada droid 3 in your hand don't flash this
I know there's no sbf out but I've seen a few bell users say they've flashed the chinese rom(<-- link to thread, read pages 3-5 imo, link to post wih --> rom download or this multiupload mirror ) with rsd lite and then changed the language to english and install market to get their phone working again. Of course at that point they're on unrooted 2.3.5 and no one has found a root method for it yet so you can't install recovery and downgrade or anything but you'd have a working phone again at least.
Thanks to
the2dcour for the rsd links etc
Cuqui/Endoroid for the market/gapps links and additional info
mvp3 for finding and linking the chinese rom
LaZiODROID for the detailed explanation on how to switch to english language/which symbols to hit, I know I don't speak or read even han chinese
Again, If you aren't holding a bricked bell canada droid 3 in your hand don't flash this. Neither myself or anyone that I've mentioned will accept any responsibility or liability for anything you do to your phone, it's your phone and you do what you want with it.
The XT860 lives! Thanks Willis.
LaZiODROID said:
The XT860 lives! Thanks Willis.
Click to expand...
Click to collapse
No man, thank everyone! There's a list of names there and yours is on it too, I just grouped up some of the information to make it easier to find for us. Group effort.
Willis111 said:
If you aren't holding a bricked bell canada droid 3 in your hand don't flash this
Neither myself or anyone that I've mentioned will accept any responsibility or liability for anything you do to your phone.
All this info is just consolidate from 2-3 different threads but buried among a few different posts. This is just a quick and dirty for unbricking our bell models, trying to avoid a step by step on how to use rsd etc since all that information is available in posts/threads that I've linked below.
If you aren't holding a bricked bell canada droid 3 in your hand don't flash this
I know there's no sbf out but I've seen a few bell users say they've flashed the chinese rom(<-- link to thread, read pages 3-5 imo, link to post wih --> rom download or this multiupload mirror ) with rsd lite and then changed the language to english and install market to get their phone working again. Of course at that point they're on unrooted 2.3.5 and no one has found a root method for it yet so you can't install recovery and downgrade or anything but you'd have a working phone again at least.
Thanks to
the2dcour for the rsd links etc
Endoroid for the market/gapps links and additional info
mvp3 for finding and linking the chinese rom
LaZiODROID for the detailed explanation on how to switch to english language/which symbols to hit, I know I don't speak or read even han chinese
Again, If you aren't holding a bricked bell canada droid 3 in your hand don't flash this. Neither myself or anyone that I've mentioned will accept any responsibility or liability for anything you do to your phone, it's your phone and you do what you want with it.
Click to expand...
Click to collapse
As much as I like seeing my name up there, I did not provide market/gaaps. I'm helping cuqui try to build some sort of recovery we can flash by providing a /system dump. Just wanna make sure the credit goes where it should
Sent from my rooted xt860
Endoroid said:
As much as I like seeing my name up there, I did not provide market/gaaps. I'm helping cuqui try to build some sort of recovery we can flash by providing a /system dump. Just wanna make sure the credit goes where it should
Sent from my rooted xt860
Click to expand...
Click to collapse
Edited the post, yours was the post I was directed to where I found the correct files on a decent mirror
For sure. Go Team!
Sent from my ME863 using XDA App
Hey, are there any updates to this process? I've bricked my xt860 and tried to flash it with RSD light, and it just seems to fail on lbl.
I can edit the XML file to not include lbl, but then it will fail on boot.img too.
Not sure.. Hopefully someone can find the sbf for bell otherwise i might have to return it.
coniferous said:
Hey, are there any updates to this process? I've bricked my xt860 and tried to flash it with RSD light, and it just seems to fail on lbl.
I can edit the XML file to not include lbl, but then it will fail on boot.img too.
Not sure.. Hopefully someone can find the sbf for bell otherwise i might have to return it.
Click to expand...
Click to collapse
You can use one of the Latin America SBFs or return it... there are no Bell SBFs kicking around anywhere.
Sent from my XT860 running ICS
Thats a bummer. Thanks for the help though!
coniferous said:
Hey, are there any updates to this process? I've bricked my xt860 and tried to flash it with RSD light, and it just seems to fail on lbl.
I can edit the XML file to not include lbl, but then it will fail on boot.img too.
Not sure.. Hopefully someone can find the sbf for bell otherwise i might have to return it.
Click to expand...
Click to collapse
rsdlite will accept dd backups of the partitions that are failing (other than system.img, preinstall.img, and radio.img) as long as the md5s in the xml are correct. here's a post of the bell 2.3.6 partitions:
http://forum.xda-developers.com/showthread.php?t=1459648
unfortunately the link to the partitions you need is no longer valid; might try contacting the uploader or have someone with functioning bell 2.3.6 do dd backups of the partitions you need.
Q9Nap said:
rsdlite will accept dd backups of the partitions that are failing (other than system.img, preinstall.img, and radio.img) as long as the md5s in the xml are correct. here's a post of the bell 2.3.6 partitions:
http://forum.xda-developers.com/showthread.php?t=1459648
unfortunately the link to the partitions you need is no longer valid; might try contacting the uploader or have someone with functioning bell 2.3.6 do dd backups of the partitions you need.
Click to expand...
Click to collapse
Hehehe, that was all me, I am the original uploader. I tried using RSDLite and changing MD5s and everything, but I was never able to create my own SBF, even after I took dd images of each of the partitions. There was no way to grab the radio.img, and the DD images of a few of the other partitions sort of corrupted my phone so I ended up just sending it in to warranty for an "OS reload".
Now the RSDLite has been started, I'm pretty sure that all of the partitions have been wiped...
danifunker said:
Hehehe, that was all me, I am the original uploader. I tried using RSDLite and changing MD5s and everything, but I was never able to create my own SBF, even after I took dd images of each of the partitions. There was no way to grab the radio.img, and the DD images of a few of the other partitions sort of corrupted my phone so I ended up just sending it in to warranty for an "OS reload".
Now the RSDLite has been started, I'm pretty sure that all of the partitions have been wiped...
Click to expand...
Click to collapse
oh lol, didn't notice that before; oh well, good thing you can use the latam sbf
greetings,
I had the brilliant idea of flashing my droid 3, but now I'm stuck on a black screen:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.40
Battery OK
OK to Program
Connect USB
Data Cable
I used RSD Lite to flash, but it just shows
Failed flashing process. 1/18 (...) result FAIL
I'm trying to update with CW, but it stuck after the 'press menu' page
someone knows how to unbrick my phone?
http://forum.xda-developers.com/showthread.php?t=1336980
if youre trying to update through CW, you shouldnt need to use RSD. Since you have used RSD, you need to make sure you have the correct SBF. Im not sure if the Milestone 3/??Model# has an SBF! You will need to sbf (with RSD) and (probably) clear cache (through recovery m+power)
thank U vry much!
giving a try
as soon I get some results, I'll post here
and again: thank you
well... my droid is a
motorola Milestone 3 x850
Godmik said:
well... my droid is a
motorola Milestone 3 x850
Click to expand...
Click to collapse
oh..you have the XT860? In this topic http://forum.xda-developers.com/showthread.php?p=19784171 they're saying you can make nandroid backups now...I guess you didn't?
I'm not really up to date with XT860 news (there's still no subforum) but you could try flash the http://forum.xda-developers.com/showthread.php?t=1288823.
I don't know if there's an official SBF for XT860 yet
when i saw the flag in your profile, i figured you werent using our XT862. I did a couple searches but didnt come up with anything but a system dump
I did...
bot even the backup stuck....
when I boot with + and - volume buttons pressed, I can navigate to 'Normal Powerup'
then appears the CW window, where I made the backup, but when I try to restore and reboot, it keeps stucking....
http://forum.xda-developers.com/showpost.php?p=17419746&postcount=81
check out this thread, not just post 81. this guy said he tried flashing the xt862 rom to his xt860 and bricked like you. ive never had to fastboot the /preinstall partition (??), but you may find more information if you dig a little deeper. hope that helps
guys,
my greatest THANKS!
after this little time and this little help I can yell:
IT'S ALIVE!! \o/
I almost lost (another) mobile on flash (frist a Motorola v360, then a Palm Treo Pro 850)
on other hand.... it's on CHINESE!!!
but I think I can handle that..... or at least try to....
awesome. i was worried because motorola marketed two phones as the XT860, which is Bell Canada, and Vivo Brazil. everything ive checked out was for the Bell version (even though they could be the exact same base)
now, I'll try to root again, install CW and restore my backup...
wish me luck =P
thinking better....
this whole confusion started because my droid was too slow.... (I guess it's because motoblur) and restore the backup will only help to mess up with my head again
If you're on the me863 rom now thenone click root won't work, there is a link to a working root method in the me863 thread in the Droid 3 android dev forum
Rooted xt860, debloated and overclocked to 1.1
DoubleYouPee said:
oh..you have the XT860? In this topic http://forum.xda-developers.com/showthread.php?p=19784171 they're saying you can make nandroid backups now...I guess you didn't?
I'm not really up to date with XT860 news (there's still no subforum) but you could try flash the http://forum.xda-developers.com/showthread.php?t=1288823.
I don't know if there's an official SBF for XT860 yet
Click to expand...
Click to collapse
I've been making nanxroids through CWR since the d3 bootstrap first came out. Never had a problem. Its safestrap that doesn't work in xt860
Rooted xt860, debloated and overclocked to 1.1
there's only one problem: I can't instal gapps...
there's a method or a order?
Godmik said:
there's only one problem: I can't instal gapps...
there's a method or a order?
Click to expand...
Click to collapse
Yes flash with stock recovery http://www.gokuai.com/f/S2rh89s025kihzf6
Also install morelocale 2 to change language
now I got gapps working too
ty guys!
Details:
Version: Android 3.2
Build Date: Dec 19, 2011
Baseband Versions:
EU 3g: 11.810.09.13.00 (same as 507)
US 4g: 11.810.09.06.00 (same as 506)
US 4g: LG7_514_21700_30.pkg & recovery.img
US Wifi: LG7-WiFi_514_21700_30.pkg & recovery.img
EU 3g: LG7-820W_514_21700_00.pkg & recovery.img
EU Wifi: LG7-Wifi_514_21700_00.pkg & recovery.img
Prelim changelog:
Next to nothing over 506/7
Tablet market removed
Standard market added
Minimal driver changes(?)
Not included:
Latest standard market
Stage 1.7 update on market
Waiting for US 4g thanks ThaManii
I dont know if/when i'll be able to fish up the us4g or eu wifi ones as the 506/507 ones were named very stupidly. I didnt find the original 514 us wifi one but i did find the eu 3g one.
Keep in mind that this version may be techincally a leak, it was built on dec 19th and shouldnt be released till next week or so under their normal schedule (this is also completely ignoring the fact that the past few weeks have been holiday weeks).
If 514 really hits OTA it may not be till the end of the month
Found all four of them
Thanks Again that was Fast!!!
update zip
i was wondering if anyone can make the pkg into zip files to flash in cwm
Hi, Problem with Recovery.img of 514 EU Wifi in Wiki Recovery Error 404.
Greettings
calico12 said:
Hi, Problem with Recovery.img of 514 EU Wifi in Wiki Recovery Error 404.
Greettings
Click to expand...
Click to collapse
Yeah I can confirm there is a download error for the US 4G recovery... if TheManii took it down then it was probably for a reason and he will get back to us. I'm gonna try and flash using the 506 recovery and see what happens.. report back in a little bit
UPDATE: I flashed the 506 recovery that I used to flash the US 4G update package and it worked just fine for installing this update
Here's a post with a link to the download from Dell: http://www.androidcentral.com/dell-streak-7-getting-bugfix-update
wptski said:
Here's a post with a link to the download from Dell: http://www.androidcentral.com/dell-streak-7-getting-bugfix-update
Click to expand...
Click to collapse
Thanks for the link but there's nothing wrong with the .pkg files links, only the recoveries as far as I can tell
cdzo72 said:
Thanks for the link but there's nothing wrong with the .pkg files links, only the recoveries as far as I can tell
Click to expand...
Click to collapse
It was mentioned above that it would be released by Dell soon and I ran across it. Funny, checking for updates, still shows no updates!
Just a confused newbie! Since I'm still stock, I can go this route.
The 514 recs havnt been prepared yet, I'm gonna do them soon.
If you already have 506/7 installed you can simply use the equivilent 506/7 rec
Edit: recs have been uploaded for 514 now
Who has had success rooting the new build with superoneclick? I tried twice and it hung on step 7 both times. I then proceeded to install superuser via cwm and now have root.
Because I am still somewhat of a noob regarding Android I am not sure if superoneclick did a partial root or what.
One the plus side for some reason the update seems faster. My titanium backups are installing noticeably quicker.
Wetzel402 said:
Who has had success rooting the new build with superoneclick? I tried twice and it hung on step 7 both times. I then proceeded to install superuser via cwm and now have root.
Because I am still somewhat of a noob regarding Android I am not sure if superoneclick did a partial root or what.
One the plus side for some reason the update seems faster. My titanium backups are installing noticeably quicker.
Click to expand...
Click to collapse
I tried updating to the 514 today and wasn't able to root unless I flashed HoneyStreak R8, which I don't want to really do because for some reason Netflix will not run on R8 here in Costa Rica, but when I was in the USA last month I had no problems. Well then I tried to go back by flashing the 506 ROm for my US 4G Streak 7 and couldn't root that either, once again the only way to root was by flashing HoneyStreak R8...
If anyone has any ideas I'm open. If not, about the only thing I know to do is NVFlash HoneyStreak R2 and start from there
Wanted to report a positive bug fixed with 514 vs 512 that came with my device. When docked in my video dock, the streak will ask to disable the speakers ok or cancel. with 512 no matter what was said it disabled. With 514 it works
Now I can dock at my desk and watch Netflix
Have not found any bugs yet....
I believe 514 was a specific hotfix related to the dock, at least that's what I hear
I'm damn happy they fixed it. After seeing Dell stopped selling the streaks and the Video Docks I honestly thought I was screwed. Surprised they even continued to bring out software updates.
Bad enough I couldn't even get a Streak 7 dock. Morons sent me a streak 5 dock. And then told me after I attempted to return that they do not have one for the streak 7 in stock nor are they replenishing.
A pair of Dikes and a bit of patience fixed that problem
Does anyone know if this update will work on T-Mobile branded Streak 7?
icepop said:
Does anyone know if this update will work on T-Mobile branded Streak 7?
Click to expand...
Click to collapse
I had no problems... I flashed the 506 recovery image and it read the update.pkg for this ROM just fine and flashed without a hiccup... but I'm having trouble rooting it
cdzo72 said:
I had no problems... I flashed the 506 recovery image and it read the update.pkg for this ROM just fine and flashed without a hiccup... but I'm having trouble rooting it
Click to expand...
Click to collapse
Awesome, thanks. I'll give mine a shot today.
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