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
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!
These files and steps will get your Bionic on ICS with root. Follow directions carefully and enjoy.
To make it simple and help I have made a 1 file tar to download. Contents include FXZ to 902 then supplied 902_905 and .230 files with RSD and new Moto Drivers. Also includes Rooting script.
http://android.mattsimoni.com/Bionic.tar
Code:
// Use at your own risk, I'm not responsible for anything that happens to your phone. This is the method I choose to do this and it worked without fail.
// You have been warned, now have fun and jump on the band wagon!!
** 902_905.zip treat like a normal update.zip and flash through stock recovery
** 6.7.230 ICS Bionic.zip you will need to unzip before flashing
**Install Flashing Process**
First back up both SDCARDS and format each
then RSD back to .902
When it boots up for the first time, bypass activation and stuff by touching the 4 corners of the screen
Top Left - Top Right - Bottom Right - Bottom Left
Add 902_905 zip to SDCARD
Reboot into recovery flash ZIP
When it boots up for the first time, bypass activation and stuff by touching the 4 corners
Top Left - Top Right - Bottom Right - Bottom Left
Add 6.7.230 ICS Bionic.zip and crc file to SDCARD
Reboot into recovery flash ZIP
When its boots up it will be ICS, dont panic wait a few minutes and your set.
**Rooting Process**
Install New MOTO Drivers
Put phone into USB Debugging Mode
Confirm you put your phone into USB Debugging Mode
Click run.bat from the Root Folder.
You are now rooted.
Super..
You are amazing, ty...
Ok I have been trying to post this for a bit now, I am running rooted Bionic .2233 very smooth and easy process. However, when I installed Avast anti virus Avast came back and told me that a program called Verizon Remote Diagnostic too is using a high SMS priority and Avast will not work properly with it installed. Avast at this point offered to uninstall and, of course, this tool will not uninstall. I googled this tool and I saw a Verizon rep saying something like this is a tool for customer service and sits in the background and does not mine data. Anyone else hear of this tool? Is there a way to freeze or due bloat? I don't like the idea that Verizon did this, the rep also said this tool was for the LG Optimus?? Is this leak originally for the Optimus?
Sqwaller said:
Ok I have been trying to post this for a bit now, I am running rooted Bionic .2233 very smooth and easy process. However, when I installed Avast anti virus Avast came back and told me that a program called Verizon Remote Diagnostic too is using a high SMS priority and Avast will not work properly with it installed. Avast at this point offered to uninstall and, of course, this tool will not uninstall. I googled this tool and I saw a Verizon rep saying something like this is a tool for customer service and sits in the background and does not mine data. Anyone else hear of this tool? Is there a way to freeze or due bloat? I don't like the idea that Verizon did this, the rep also said this tool was for the LG Optimus?? Is this leak originally for the Optimus?
Click to expand...
Click to collapse
Try disabling it from applications menu
Sent from my GT-P7510 using Tapatalk 2
Well done Matt, ty
matt1313 said:
Try disabling it from applications menu
Sent from my GT-P7510 using Tapatalk 2
Click to expand...
Click to collapse
Can not disable so tried force stop and that did not work, I did not see this app in titanium backup will look again and see if I can freeze it.
Thanks though for the quick response.
Can someone rehost. Data quota is exceeded.
arizona55 said:
Can someone rehost. Data quota is exceeded.
Click to expand...
Click to collapse
Give me a few and Ill upload to a server
That was really easy - now one question: Is there are restore process torestore the internal and External SD cards that we backed-up?
OR should I just drag/drop what I need?
Thanks again -
Ok I have a silly question.
I followed the instructions and RSD back to 902. The problem is when I boot into recovery I get the Android guy with the !
I am able to take the 905 update and that worked just fine.
I was unable to apply 905 or ICS from this thread or any others.
I have tried to search various places but can't find the same problem.
help?
arizona55 said:
Can someone rehost. Data quota is exceeded.
Click to expand...
Click to collapse
New link added
Lemmy Caution said:
That was really easy - now one question: Is there are restore process torestore the internal and External SD cards that we backed-up?
OR should I just drag/drop what I need?
Thanks again -
Click to expand...
Click to collapse
Drag and drop
powrful1 said:
Ok I have a silly question.
I followed the instructions and RSD back to 902. The problem is when I boot into recovery I get the Android guy with the !
I am able to take the 905 update and that worked just fine.
I was unable to apply 905 or ICS from this thread or any others.
I have tried to search various places but can't find the same problem.
help?
Click to expand...
Click to collapse
Try it all over again, sound like something went wrong
powrful1 said:
Ok I have a silly question.
I followed the instructions and RSD back to 902. The problem is when I boot into recovery I get the Android guy with the !
I am able to take the 905 update and that worked just fine.
I was unable to apply 905 or ICS from this thread or any others.
I have tried to search various places but can't find the same problem.
help?
Click to expand...
Click to collapse
did you unroot before you did all of this? try that and see if it works.
AWSOME ...!!!
This worked GREAT ... I followed the instructions as listed and am now running ICS - BTW make sure that your battery has a good charge on it BEFORE attempting ANY flashing ...!
My battery went too low while flashing - I thought I bricked it (would not charge after) I had to borrow a battery from a buddy.
Rookie mistake I know ...
Thanks again I will update if I find any bugs.
Bricked?
I downloaded to my unrooted stock 905 bionic last night and ran the update. All went successful until I rebooted. I received a great error message..
Code:
Invalid CG OTV (CG: webtop): Invalid SP Data
Invalid CG HAB (CG: webtop, status: 0x004E)
Invalid CG OTV (CG: webtop)
I tried going back to 902 using the FXB and RSDLite, but it fails. It worked the first time and failed at 19/20.. now it fails at 1/20 (aka immediately). I tried using laptop, desktop, two USB cords, etc. Any ideas on how to unbrick? I'll update this thread if I figure out how to fix it.
powrful1 said:
Ok I have a silly question.
I followed the instructions and RSD back to 902. The problem is when I boot into recovery I get the Android guy with the !
I am able to take the 905 update and that worked just fine.
Click to expand...
Click to collapse
PremierGT said:
did you unroot before you did all of this? try that and see if it works.
Click to expand...
Click to collapse
same thing happened to me and my phone is unrooted. I even re-ran RSD. Please help.
crobs808 said:
(turn off phone, hold down both vol buttons + power, press vol down then up to go into recovery, press both vol buttons at android exclamation icon to see menu options)
Click to expand...
Click to collapse
<was not doing the highlighted part
Can't Download files..
this ICS leak unlock Global GSM, Right?
what is the reason for formatting the sd cards?
my phone hasn't been rooted and i'm on 905 already. i'm just in it for the ics, i haven't had a need for root, as of yet.
Just install the 233 leak works great and i didnt format the sd cards, so i dont see the need of that.
I was using the gsm hack but after the install i cant get signal and i cant change the network type in settings, ICS for the bionic will open the global feature? If not can i re apply the gsm patch? or maybe use radiocomm
Thanks
Okay quick question I downloaded the .tar file, this makes the second time. Seems the root file is empty. After both downloads it still seems to be this way. Can I just use voodoo or is there another way? Thanks
Thanks for posting this. Also, i don't remember if I was on .893 or what I was on for stock. What if I never went past .893? thanks.
Can you just use cheesecake.apk to get the 905 and leaked ICS updates? thanks.
Ok I've become highly frustrated can anyone help me on this one? Droid 3 stock was working fine and all of a sudden no service what so ever. Can only connect via wifi. I've done: *228 (doesn't work no service), ## program (didn't work somehow my spc password has changed tried all vzw told me to try), tried factory reset (still didn't work), tried rooting phone cwm boot strapper etc (still no radio) even tried the stock flash from other threads where these phones have had this issue. (Still not working) I even tried cdma workdhop to read the memory to find the spc pw and the file said that the txt file did not exist. What's left to do? Pull the trigger? Really could use some help.... thanks!
By stock flash do you mean sbf via rsdlite or motofastboot. If you've flashed stock firmware and still have issues I would suspect it's a hardware issue
Sent from my XT860 using xda premium
Its the one named D3.906.SBF by overlayer I used ill try to find the post that has the file. Moto-fastboot I think where would I find the other (it'll be a pain if its hardware....)
liquidoutl4w said:
Its the one named D3.906.SBF by overlayer I used ill try to find the post that has the file. Moto-fastboot I think where would I find the other (it'll be a pain if its hardware....)
Click to expand...
Click to collapse
Try toggling through Global/CDMA/GSM modes and end on CDMA (if you use Verizon). I sometimes have this issue, though usually after flashing a radio. Also if you SBF, remember to wipe data/cache. If you want it, I can upload the stock 890 radio and you can flash with moto-fastboot. The 890 radio DOES work with 906 system, I switch between the 890 and XT883 radio for CDMA/GSM.
Motofastboot and rsdlite are just 2 different ways of flashing firmware. Rsdlite is more user friendly and automated whereas motofastboot is a command line utility that allows you to flash single partitions instead of the whole device. Ovelayers tool uses motofastboot and a script I believe
Sent from my XT860 using xda premium
Ohhh ok got it yes if you could please upload the file I'd appreciate it i'll I've that a try then pull the trigger if that doesn't work. Shame too really liked the phone lol. Ill just have to get another one and root it next time right away to really enjoy it haha (I miss my droid 1 with bugless )
liquidoutl4w said:
Ohhh ok got it yes if you could please upload the file I'd appreciate it i'll I've that a try then pull the trigger if that doesn't work. Shame too really liked the phone lol. Ill just have to get another one and root it next time right away to really enjoy it haha (I miss my droid 1 with bugless )
Click to expand...
Click to collapse
http://www4.zippyshare.com/v/77282840/file.html here you are, one stock radio image.
Hello! I have a moto x4 bought on CLARO (brazilian) carrier that comes with their official ROM (with non uninstallable apps, etc). It's the XT1900-6 model, with Android 8.0 Oreo installed. Thing is, the moto x4 was updated to Android 9 Pie, the retail devices have started receiving through OTA over a year ago. But as mine is carrier branded, it depends on them to release the updates (motorola gives to them and they do whatever they want, modify and release or do nothing) and they haven't lanuched the update. So I am tired of waiting and want to know if I can just "unbrand" my phone by installing an official retail firmware to receive the update (or just install the Android 9 firmware directly). Can I just get the retail firmware from lolinet and flash it following a guide? Or this is not possible at all?
I think the problem would be in getting the non-Brazilian ROM to access Claro, or whatever carrier you are using down there. But I don't know.
KrisM22 said:
I think the problem would be in getting the non-Brazilian ROM to access Claro, or whatever carrier you are using down there. But I don't know.
Click to expand...
Click to collapse
But the ROM would still be brazilian. Check out this firmware on lolinet.com on /firmware/moto/payton/official/RETBR/XT1900-6_PAYTON_RETBR_9.0_PPWS29.69-26-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip (As a new user, I cannot post links yet)
Ah, okay, I understand your question. But of course not having tried it I don't know the answer. Have you tried lmsa (see my sig) to see what if anything it offers you?
KrisM22 said:
Ah, okay, I understand your question. But of course not having tried it I don't know the answer. Have you tried lmsa (see my sig) to see what if anything it offers you?
Click to expand...
Click to collapse
I have not, but I tried to check it out right now, your link is giving 404 not found error.
LOL yes, I screwed up. Thanks. Try it now.
---------- Post added at 10:22 PM ---------- Previous post was at 09:51 PM ----------
I realized another possible prob - the ROM you have on there now is a (maybe) custom ROM made by Claro. Therefore some other ROM like the one you suggested, might not connect to Claro. Dunno...
KrisM22 said:
LOL yes, I screwed up. Thanks. Try it now.
---------- Post added at 10:22 PM ---------- Previous post was at 09:51 PM ----------
I realized another possible prob - the ROM you have on there now is a (maybe) custom ROM made by Claro. Therefore some other ROM like the one you suggested, might not connect to Claro. Dunno...
Click to expand...
Click to collapse
Yes, I think that is the case. But the model is exactly the same as retail, I can't think of why a retail ROM wouldn't work. I think it would be like I had bought the phone in some random store and put a Claro sim card on it, it would work.
Okay, I tried LMSA, it says my ROM version is up to date. But this is expected, as it would check for updates in the Claro channel, which has none. I want to change to retail ROM so it would check for updates in retail channel.
Back in the day, even before Android, I did something like this with an old Nokia phone. Phones used to differ the model number not only by region, but also by carrier. I don't remember the procedure exactly, but I flashed a retail number over the carrier number and used a Nokia support software like the LMSA and it recognised the phone as retail. It had an update to be installed, so I did and the phone "turned" into retail version. Of course none of this applies for modern smartphones, but I think it may be possible to do something similar.
I hear you. Not having the Claro ROM to flash back if it doesn't work, you would be simply taking a chance. And if the new ROM won't connect to Claro, you're stuck. I realize the big reason I am being so cautious here is that in my reading I had recently encountered a Claro phone that now wouldn't work, but of course I forget where I read that and what was done to the phone - maybe a custom ROM? I'll do a search and see if I find it again. Nope, nothing in X4, so I don't know where I saw it.
EDIT: no, I find nothing. it was something about (I think) they were on a custom ROM and it would connect to Claro only and very slowly, or something like that.
EDIT2: I'm advising you not to flash unless you have a clear way back.
You're right, you're being cautious. This is exactly why I registered in the forum in the first place, so I could discuss the matter with people more experienced before I do anything stupid, maybe even found someone who had already done what I'm trying to do. I appreciate your help.
ivooc28 said:
You're right, you're being cautious. This is exactly why I registered in the forum in the first place, so I could discuss the matter with people more experienced before I do anything stupid, maybe even found someone who had already done what I'm trying to do. I appreciate your help.
Click to expand...
Click to collapse
You're welcome! Yeah, caution is something too many folks don't have enough of and wind up with bricked phones. And even used, they're not cheap. Keep searching!!!
I will keep searching! Isn't there a way to just extract the current firmware I'm running to use as a backup?
Theoretically, maybe, but I wouldn't want to trust it(see modems comment below). You could
fastboot boot twrp.img
to temporarily get twrp and then boot to it, and then use it to do a backup, but you must make sure that you back it up to your SDcard since internal storage is often wiped during a flash. Then, theoretically if your new ROM doesn't work you could
fastboot boot twrp.img
back into twrp and restore that backup, but, again, I wouldn't want to trust it. I have used that to back up stock when flashing custom ROMs in the past, but I always had, and often used, RSDlite to flash a stock ROM to get me out of trouble. I believe RSDlite will work on an 8.x ROM on the X4 (I haven't tried it) but I know it will not recognize my phone at all now that it is at 9.0 RSDlite needs to be updated and I have no idea who is running that these days. One question I would have over the above is the particular modems being flashed - are they different in your Claro ROM, and if so, i do not believe they are backed up/replaced if you do a TWRP backup or restore.
"Okay, I tried LMSA, it says my ROM version is up to date."
Does it offer to download that ROM? If so, click the little down arrow and download it and see if you can access that and see if it looks like something that could be saved and flashed later. When I tried it a few days ago it looked like it was offering to download the same thing I had on. If so, that might give you a copy of the ROM you're on that you could flash to get back if need be - IF YOU CAN TRUST IT.
Nite. I'll check in tomorrow PM.
EDIT: of course I don't know if you can go from a partial Treble 9.0 back to a regular 8.x ... even if you have the stock ROM.
KrisM22 said:
Theoretically, maybe, but I wouldn't want to trust it(see modems comment below). You could
fastboot boot twrp.img
to temporarily get twrp and then boot to it, and then use it to do a backup, but you must make sure that you back it up to your SDcard since internal storage is often wiped during a flash. Then, theoretically if your new ROM doesn't work you could
fastboot boot twrp.img
back into twrp and restore that backup, but, again, I wouldn't want to trust it. I have used that to back up stock when flashing custom ROMs in the past, but I always had, and often used, RSDlite to flash a stock ROM to get me out of trouble. I believe RSDlite will work on an 8.x ROM on the X4 (I haven't tried it) but I know it will not recognize my phone at all now that it is at 9.0 RSDlite needs to be updated and I have no idea who is running that these days. One question I would have over the above is the particular modems being flashed - are they different in your Claro ROM, and if so, i do not believe they are backed up/replaced if you do a TWRP backup or restore.
Click to expand...
Click to collapse
You're saying that if the upgrade fails, then I would need to downgrade back to 8.x and that could be a problem, I see.
About the modems being flashed, I don't know if I understand it right. I believe the modems are the same here, regardless if I bought in Claro or retail. What I'm saying is, usually here in Brazil, if you buy a retail or carrier phone, either way you can put any (Brazil) sim card and the carrier would work. Of course that if a phone doesn't support specific LTE frequency bands by hardware, then it wouldn't work, but then it wouldn't matter if it is retail or carrier.
lmsa apparently doesn't give me option to download firmware, or maybe I didn't check it out properly.
ivooc28 said:
You're saying that if the upgrade fails, then I would need to downgrade back to 8.x and that could be a problem, I see.
About the modems being flashed, I don't know if I understand it right. I believe the modems are the same here, regardless if I bought in Claro or retail. What I'm saying is, usually here in Brazil, if you buy a retail or carrier phone, either way you can put any (Brazil) sim card and the carrier would work. Of course that if a phone doesn't support specific LTE frequency bands by hardware, then it wouldn't work, but then it wouldn't matter if it is retail or carrier.
lmsa apparently doesn't give me option to download firmware, or maybe I didn't check it out properly.
Click to expand...
Click to collapse
a) yes, might be a prob. Don't know.
b) if you know that then you can flash any Br ROM you want and connect to any carrier with it.
c) in lmsa, click flash (top tabs), then "go rescue". A box with fill-in-the-blanks pops up: fill in:
moto phone, moto X 4th gen, XT1900-6 (I believe it was in your case)
Hopefully some lines will appear and there will be a little down arrow thing on the right side saying download.
Click that and download the ROM. Once it is downloaded (DO NOT click rescue as that will wipe your phone), but go looking on your PC and see if you can find where it stored that download and grab/save it for yourself for possible future . I suspect it will be in c/users/<name>/local/motorola/"rom name" or something like that, not necessarily in local. It gives you part of the name so you could search your c:/ for some of that name to try to find it.
I wish I could be more specific as to its location but when I tried it with my phone this morning it said "This device is not supported" - I suspect that is because I just took the Nov 1 sec patch and there is no ROM out yet for it (lolinet doesn't have it yet - probably take another 2 or 3 weeks)(pretty lame imho, but it is what it is.
As to b) above if there are really that many folks using different carriers down there it seems that someone should know the answer to your question. Different website maybe, or post blatant "any one from Brazil here?" subject line in x4 , or search xda for Brazil. someone's gotta know! I don't believe LenAsh will swat you for a post like that if you link to this post and make clear your problem. A piece of the problem may be that the xda x4 forum seems very quiet . There may be 80 folks looking in but few are talking. Or, simply no experience in the matter and not wanting to encourage you to do something that will render your phone useless...