I've following the step using RSDLite and flash the GOT 2.2 to my MS. Later on when I want to flash my stock FW by RSD but I CANNOT! Why?
wich version of the fw you want to flash.
Check this link.
http://and-developers.com/sbf:milestone
Flashing the nonservice sbf will clear all data.
Sent from my Milestone using Tapatalk
I was able to do it Quite Easily...What exactly happens when you try to flash the Stock Sbf?Any error or what?And which SBF are you trying to Flash?2.0 and 2.0.1 will make the Boot loader hang.
Hong Kong 2.0.1 or 2.0
I am following those steps...I am ok when I flash the GOT 2.2, but I can't when I want 2.1 back
interesting enough...I can now successfully flash UK 2.1 and when I help my friend to flash GOT 2.2, it fail again. the RSD said flash error...
the error code is 0x7100, i've search for it and some people said moving the file to other location will help. I did it but seems the error is still here, or the RSD skip all process and said finished, nothing changed! Do any one know how to solve?
Sent from my Milestone using XDA App
I recently tried to use MetaMorph on my phone it went through then it rebooted and now its stuck at the motorola logo I want to reflash back to stock but I dont know what Sbf file to use please help me im in trouble right now.
did you not create a nandroid backup prior to applying a metamorph theme?
should always do that.
as for what .sbf, just flash a new rom, i doubt you need to flash a .sbf
but even if you do have to, just flash any .sbf, then root, recovery, flash rom, just make sure you got the right baseband
Ok, So I have successfully rooted my D3 and all went fine. I installed the installed the Steel Droid Rom but later found out that I can no longer access my home email account using this ROM for some reason and stupid me didnt create a nandroid backup before installing the Steel Droid. I know, stupid. So now I want to SBF my phone and start over. However, I can find a working copy of RSD Lite. Can someone point me to a website that would have it or provide a working link for it? Also, I am trying to use the following threat:
[Recovery] RSD v5.5.0 and 5.5.184 (aka 5.6.890) fastboot partitions/flashable zip: http://forum.xda-developers.com/show....php?t=1255198
There are 3 separate sections in the OP:
Flashable File, Moto-Fast Boot and RSD Lite
In addition to needing a working copy of RSD Lite 5.5 I also dont really understand the difference in the Flashable File and Moto-Fast Boot? Will I need to do both of these steps in order to SBF my phone back to stock? Or is the Moto-Fast an alternative option to using the flashable SBF file in RSD Lite?
I hate to be demanding, and would appreciate any help I could get, but if someone could please provide a step-by-step guide of the correct SBF process that would be absolutely amazing.
Thanks.
EDIT.....I FOUND A LINK TO RSD LITE 5.5....
hey all - I got a new D3 replacement today after the touch screen stopped working on the old one. it came with 5.7.906 installed. i am confused as to weather there is a way to unbrick it if i manage to muss it up when i go back to cm9. i love cm9 and hate the stock rom but considering this is my 5th D3 i am not willing to flash roms if i have no way to return to stock in case of hardware malfunction so i can get a new one under waranty
i appreciate any information on the topic
As long as you can get to the Moto Bootloader, then it is 90% likely that you can unbrick it. The tools can be found here:
http://forum.xda-developers.com/showthread.php?t=1255198&page=23
If you try to sbf with the 5.6.890 it will fail and you will probably break your bootloader as the files have changed with the update and there is no "real" way back as of yet...BUT...
Q9Nap has helped out
" if you've actually flashed the 5.7.906 leak and need to fxz your device, the stock 5.6.890 fxz will fail becuase there are some components that cannot be reverted. here's a package of 5.7.906 fxz components you can drop in to your 5.6.890 fxz folder or zip so you can flash with rsdlite:
http://www.mediafire.com/download.php?r3i3ohwqirtk3b5
Hope it helps
ovelayer said:
If you try to sbf with the 5.6.890 it will fail and you will probably break your bootloader as the files have changed with the update and there is no "real" way back as of yet...BUT...
Q9Nap has helped out
" if you've actually flashed the 5.7.906 leak and need to fxz your device, the stock 5.6.890 fxz will fail becuase there are some components that cannot be reverted. here's a package of 5.7.906 fxz components you can drop in to your 5.6.890 fxz folder or zip so you can flash with rsdlite:
http://www.mediafire.com/download.php?r3i3ohwqirtk3b5
Hope it helps
Click to expand...
Click to collapse
So, flashing this .xml through RSD will push 5.7.906 to the phone? Because my phone refuses to accept any leak though stock recovery, but I can still flash it with AP Fastboot.
redsox985 said:
So, flashing this .xml through RSD will push 5.7.906 to the phone? Because my phone refuses to accept any leak though stock recovery, but I can still flash it with AP Fastboot.
Click to expand...
Click to collapse
No theese are the files you need to add to your 5.6.890 sbf files so you can successfully flash back to 5.6.890 then you will need to install the 5.7.906 update again
ovelayer said:
No theese are the files you need to add to your 5.6.890 sbf files so you can successfully flash back to 5.6.890 then you will need to install the 5.7.906 update again
Click to expand...
Click to collapse
Oh, ok, so these are just the 5.6.890 FXZ files?
redsox985 said:
Oh, ok, so these are just the 5.6.890 FXZ files?
Click to expand...
Click to collapse
These are the 5.7.906 files that can't be reverted along with a modified xml file that has the proper md5 values for the new files.
Sent from my DROID3 using Tapatalk 2
Q9Nap said:
These are the 5.7.906 files that can't be reverted along with a modified xml file that has the proper md5 values for the new files.
Sent from my DROID3 using Tapatalk 2
Click to expand...
Click to collapse
Hold on... Will flashing these through AP Fastboot put me on 5.7.906? I'm unable to flash a .zip leak though stock recovery. It fails when "flashing BP", bricks me, and I must FXZ to 5.6.890 to get it up and running again.
Here's a video showing what happens when I try to flash 5.7.894 (have only tried this since it can be 5.6.890 FXZ'd over).
http://www.youtube.com/watch?v=1taHiSTzd7A
redsox985 said:
Hold on... Will flashing these through AP Fastboot put me on 5.7.906? I'm unable to flash a .zip leak though stock recovery. It fails when "flashing BP", bricks me, and I must FXZ to 5.6.890 to get it up and running again.
Here's a video showing what happens when I try to flash 5.7.894 (have only tried this since it can be 5.6.890 FXZ'd over).
http://www.youtube.com/watch?v=1taHiSTzd7A
Click to expand...
Click to collapse
You should only flash the package i made if you're trying to get back to 5.6.890 from 5.7.906. If you're on 5.7.894, you should still be able to flash the stock 5.6.890 fxz without any issues. Not sure why you're getting the error on bp; as long as you're using an unmodified 5.7.894 leak and stock recovery it should work fine. I'd try flashing 5.6.890 with rsdlite as it flashes all possible partitions; pete's moto-fastboot method doesn't flash everything.
Q9Nap said:
You should only flash the package i made if you're trying to get back to 5.6.890 from 5.7.906. If you're on 5.7.894, you should still be able to flash the stock 5.6.890 fxz without any issues. Not sure why you're getting the error on bp; as long as you're using an unmodified 5.7.894 leak and stock recovery it should work fine. I'd try flashing 5.6.890 with rsdlite as it flashes all possible partitions; pete's moto-fastboot method doesn't flash everything.
Click to expand...
Click to collapse
I'm currently on 5.6.890 running various safestrapped ICS builds, but would like the updated radio from the newer leaks. I'm afraid to try anything higher than 5.7.894 because I know I can't go back...until now maybe with these files. My fear was I would flash 5.7.906 with stock recovery, get bricked, and be stuck there because it failed while flashing like 5.7.894 does to the phone.
redsox985 said:
I'm currently on 5.6.890 running various safestrapped ICS builds, but would like the updated radio from the newer leaks. I'm afraid to try anything higher than 5.7.894 because I know I can't go back...until now maybe with these files. My fear was I would flash 5.7.906 with stock recovery, get bricked, and be stuck there because it failed while flashing like 5.7.894 does to the phone.
Click to expand...
Click to collapse
The 906 update only asserts ro.product.device, while the 894 update asserts ro.build.fingerprint; in other words, 906 just checks to make sure the device is a cdma solana, 894 checks to make sure it's a cdma solana running 890. So 906 is designed to be able to flash over anything essentially, kind of like a fxz in update format.
If for whatever reason it does brick your phone, you *should* be able to restore to a mostly 890 state (boot.img, cdt.bin, mbm.bin, mbmloader_hs.bin, and recovery.img are stuck on the latest versions once 906 is flashed.)
But it is strange that 894 is failing on bp; that's the radio image. as mentioned, 894 asserts 890, so if you're on stock 890 there's no reason it should be failing. I actually tried flashing from 890 to 894 after being on 906 in an attempt to get back to full stock 890; the flash succeeded, but on reboot i was stuck in fastboot mode until i flashed the newer boot, cdt, and recovery. i have no idea why bp is failing for you
Q9Nap said:
The 906 update only asserts ro.product.device, while the 894 update asserts ro.build.fingerprint; in other words, 906 just checks to make sure the device is a cdma solana, 894 checks to make sure it's a cdma solana running 890. So 906 is designed to be able to flash over anything essentially, kind of like a fxz in update format.
If for whatever reason it does brick your phone, you *should* be able to restore to a mostly 890 state (boot.img, cdt.bin, mbm.bin, mbmloader_hs.bin, and recovery.img are stuck on the latest versions once 906 is flashed.)
But it is strange that 894 is failing on bp; that's the radio image. as mentioned, 894 asserts 890, so if you're on stock 890 there's no reason it should be failing. I actually tried flashing from 890 to 894 after being on 906 in an attempt to get back to full stock 890; the flash succeeded, but on reboot i was stuck in fastboot mode until i flashed the newer boot, cdt, and recovery. i have no idea why bp is failing for you
Click to expand...
Click to collapse
I wonder if it's because I have done the radio hack? I should RSD Lite to 5.6.890 since that should reflash the radio then try to immediately apply 5.7.894, then 5.7.906 on top of that. Could you add me on GTalk in case I get seriously bricked so we can work that out?
redsox985 said:
I wonder if it's because I have done the radio hack? I should RSD Lite to 5.6.890 since that should reflash the radio then try to immediately apply 5.7.894, then 5.7.906 on top of that. Could you add me on GTalk in case I get seriously bricked so we can work that out?
Click to expand...
Click to collapse
What radio hack are you referring to? are you using the xt883 radio? if so, that could definitely be why it's failing. sure hit me up at mhous33...
Q9Nap said:
What radio hack are you referring to? are you using the xt883 radio? if so, that could definitely be why it's failing. sure hit me up at mhous33...
Click to expand...
Click to collapse
Nope, XT862 with WiFi tether hacked radio. Request sent.
redsox985 said:
Nope, XT862 with WiFi tether hacked radio. Request sent.
Click to expand...
Click to collapse
yeah, i'd make sure your'e on fully stock 890 with no modifications before flashing 894; it should work. request accepted.
redsox985 said:
I wonder if it's because I have done the radio hack? I should RSD Lite to 5.6.890 since that should reflash the radio then try to immediately apply 5.7.894, then 5.7.906 on top of that. Could you add me on GTalk in case I get seriously bricked so we can work that out?
Click to expand...
Click to collapse
You can use RSD Lite to go back, and then flash .906. I use the script to do it via moto-fastboot, but whatever works for you. Radio should not be affecting it at all.
nemiroG1 said:
You can use RSD Lite to go back, and then flash .906. I use the script to do it via moto-fastboot, but whatever works for you. Radio should not be affecting it at all.
Click to expand...
Click to collapse
Q9Nap and I just spent a bunch of time on GTalk. I'm unable to accept any signed radio image. We're stumped as to why, but we want to figure it out.
redsox985 said:
Q9Nap and I just spent a bunch of time on GTalk. I'm unable to accept any signed radio image. We're stumped as to why, but we want to figure it out.
Click to expand...
Click to collapse
Flashing radio.img with rsdlite and fastboot is successful, but flashing any update in stock recovery fails on bp. only thing that makes sense that i can think of is that either the sdcard or update file is corrupt.
Q9Nap said:
Flashing radio.img with rsdlite and fastboot is successful, but flashing any update in stock recovery fails on bp. only thing that makes sense that i can think of is that either the sdcard or update file is corrupt.
Click to expand...
Click to collapse
I never did get around to formatting my SD card. Stock recovery only sees the EXT SD correct?
I'm currently chatting with Moto... This is odd. I'm going to start my own thread for it to leave this one be.
Flashed at&t firmware with odin but can't update software past July 1st sec uodate.
Hey guys. I picked a note 9 Verizon unlocked version and was having issues using it on at&t, volte obv not working hd voice calls not working and various other signal issues. I decided to flash to the at&t firmware with odin to fix it. First thing I did was flash the unlocked firmware, factory reset, then flashed at&t firmware. Everything is working just like I bought the at&t note 9 but I'm stuck on July security patch and the update is not recognized. Is there anyway to fix this ? Thanks in advance!
What happens when you try to update; it downloads the update but failing to install due to an error (what's the error) or not finding the updates at all? If latter try with Samsung smart switch install both on the phone and computer
It doesn't find any update ota or on smartswitch. Not sure maybe just need to wait longer, unless someone else has some bright ideas lol
Clo292311 said:
It doesn't find any update ota or on smartswitch. Not sure maybe just need to wait longer, unless someone else has some bright ideas lol
Click to expand...
Click to collapse
What build number are you running? If you managed to get yourself stranded on a build not officially pushed by ATT, then you're stuck until you Odin to something else. Current ATT is ARI5.
I am on ARG6 build. Is there something you know of I can flash that would be better?
@CrazyApe18
Clo292311 said:
I am on ARG6 build. Is there something you know of I can flash that would be better?
Click to expand...
Click to collapse
I'm not sure there is a path using update zips to get you current. I just looked and I can't see a way to get current from there. Somewhere on here an ARI5 Odin image (with no HOME_CSC) has been posted. That would get you to current ATT software. Once there, you would get OTA updates. I'm not sure how you got off the update track.
Edit: Here's the link to the Odin image you'd want: https://drive.google.com/file/d/1bKlJ-2ikGRsOd3JkDIFvjHGJX6XnrtEH/view?usp=sharing - courtesy of @Venom0642
@CrazyApe18 thank you for that link. Do I need to find a HOME_CSC file to add into that to flash it correctly?
Clo292311 said:
@CrazyApe18 thank you for that link. Do I need to find a HOME_CSC file to add into that to flash it correctly?
Click to expand...
Click to collapse
No, you don't need one. However, without HOME_CSC (and there isn't one that I'm aware of), your device will factory reset when you Odin this build. So make a full Smart Switch backup before doing it.
Oh that's fine I full wipe after odin anyways usually. Thanks so much !!
If you don't have an ATnT sim installed, it wont give you updates.
CrazyApe18 said:
I'm not sure there is a path using update zips to get you current. I just looked and I can't see a way to get current from there. Somewhere on here an ARI5 Odin image (with no HOME_CSC) has been posted. That would get you to current ATT software. Once there, you would get OTA updates. I'm not sure how you got off the update track.
Edit: Here's the link to the Odin image you'd want: https://drive.google.com/file/d/1bKlJ-2ikGRsOd3JkDIFvjHGJX6XnrtEH/view?usp=sharing - courtesy of @Venom0642
Click to expand...
Click to collapse
hey @CrazyApe18, i have a note 9 att locked on build number N960USQS2CSGB. I'm having an issue finding a current pie version to flash with odin. Basically I removed a bunch of things with adb a while back and wanted to restore back to factory. I pushed adb uninstall to things like the att update software, if I'm not mistaken a factory reset wouldn't restore this. I'm wanting to flash and then update to the new android version. I was wondering if you could point me in the right direction. I downloaded your link just in case it could help me. I'm familiar with odin, just having a hard time finding the firmware and SAMMOBILE is very slow for non paying users. I appreciate any help you can give me.
just realized that the version in your link is pre Pie. any idea where i can get a fairly recent pie firmware?