Related
Alright, so I updated my phone when the first OTA update was released, and it installed successfully no problems. After this I got into rooting my phone so that I could get rid of the AT&T crapware, use launcher pro, and enable sideloading for apps. I thought that I would check for another update since rumors were swirling about 2.2, and to my surprise it detected a package to download. I was able to download it, however it wouldn't finish installing on the phone and said that it could not be installed. Thinking that this was due to my root, I used Odin to flash back to stock and retry the install, and it still didn't work. So, after that I reverted back to the root, and decided to go and check the firmware and baseband version What is confusing to me is that for "firmware version" it says that I have "2.1-update1", but my baseband version still says "1897UCJF6" instead of "JH7". Now when I try to install whatever supposed update that is available, it downloads and then gets stuck at 50% in the progress bar when trying to install. So I guess my question is, should I be worried about this? Is this the current version, and does it just say "JF6" because of my root? Also, will I need to unroot if I want to install the 2.2 update whenever it comes out?
I apologize for the novel, I'm just trying to be as informative about my situation as possible. Any help with this would be greatly appreciated.
Thanks
JF6 is the stock firmware and JH7 was the ota update.
Sent from my Captivate
Alright thanks, but why is my phone still displaying "2.1-update1" if I still have the stock firmware? Is it because of the root that it is displaying JF6 instead of JH7?
goosefraba91 said:
Alright thanks, but why is my phone still displaying "2.1-update1" if I still have the stock firmware? Is it because of the root that it is displaying JF6 instead of JH7?
Click to expand...
Click to collapse
JH7 was also considered 2.1-update1
there is not an official 2.2 yet
Okay well thanks, I think I'm about to just flash to a 2.2 ROM, I'm tired of waiting on samsung for 2.2
i need help with the rooting of my phone
bosoxtm said:
i need help with the rooting of my phone
Click to expand...
Click to collapse
View this topic:
http://forum.xda-developers.com/showthread.php?t=739304
Hi, I've looked and can't find the answer. I am not rooted nor do I want to root. I would like to do the leaked 5.7.893, can I just download it and go into stock recovery? Is it possible to get the "official" update still if something changed or is there a way to go back to the original 5.5.886 like with the droid x being able to SBF back to froyo. Again I have no intention of rooting, any help would be greatly
appreciated . Many thanks to anyone who is willing to help.
yes you can install the leak but you will not be able to go all the way back. you can take the system back but you will still have the new kernal and radio. you cannot change those till the bootloader gets unlocked.
hello all I upgraded my phone to 5.7.893 and had to go back for various reasons but I lost my system and my radio and kernel are on that version and I have been unsuccessful at reinstalling the OTAs from Cheesecake. Does anyone have an update.zip of the system for 5.7.893 that I may be able to atleast get my system back to on the same level as my kernel and radio without the use of a custom rom?
Thanks in advance.
*****DO NOT DO THIS (See why here)*****
Hey guys,
I currently have a very messed up 5.7.893 (webtop missing, forever root, unable to get to 5.8.894 from cheesecake, etc...).
I'm looking to get back to completely factory stock image that accepts OTA's properly. Seems like there are a lot of mixed messages in the threads. Does anyone have a method that is confirmed working?
I was able to get to the OTA update using the following. Not sure if I got lucky or if it works for everyone.
I was able to get from the leaked 5.7 update to the official Verizon 893 Ota update.
1 – I used the R3L3AS3DRoot program and restored back to stock.
2 – Using the same program I 4RVRRooted the phone
3 – started up phone and did not sign into anything (google, etc). Did the bare minimum to get the phone up and running.
4 – Restarted in stock recovery and flashed radio.zip file that puts the radio back to stock. http://forum.xda-developers.com/showpost.php?p=19680673&postcount=40
5- Downloaded the OTA update and attempted to install. Phone rebooted and said that the update failed.
6- Copied the OTA update from http://www.multiupload.com/0ZEN69NGO2
7 – Installed the OTA update – SUCCESS!!
8 – Root is still there.
I am now at:
System version – 5.7.893.xt875.Verizon.en.US
Baseband Version – CDMA_n_03.1C.57r LTEDC_U_05.15.02
Webtop – WT-1.3.0-108_dbn-21
Kernel – 2.6.35.7-g68606e6 [email protected] #1
Build number – 5.5.1_84_dbn-62
Links for #4 and #6 are no good. You have dots in that link "..."
hopefully I fixed them. Sorry about that
rumpy said:
hopefully I fixed them. Sorry about that
Click to expand...
Click to collapse
Thank you very much. I will try it out tonight and let you know.
but system # 5.7.893 is a cheesecake leak, not the OTA. The OTA is 5.5.893
the only things that don't match the leak I am on are the Webtop version ( WT-1.3.0-105_DBN-1) and the build # on my phone has an added MR-11 to the end of it
dB Zac said:
but system # 5.7.893 is a cheesecake leak, not the OTA. The OTA is 5.5.893
Click to expand...
Click to collapse
This is correct. I won't need to do that part, just get to stock, flash stock radios, and then check for updates and install the OTA when it shows up.
what part? I am saying that the post above did not get him to the OTA according to his own final information.
dB Zac said:
what part? I am saying that the post above did not get him to the OTA according to his own final information.
Click to expand...
Click to collapse
That's right because he flashed 5.7.893 instead of the OTA. I'm just stating that I won't be flashing 5.7.893 and will just update the actual OTA (5.5.893). I'm aware he was mistaken.
If you applied the leaked 5.7.893 update there is no way at all to apply the official ota of 5.5.893. the leak updates your kernel and that makes the ota fail. at this time there is absolutely nothing you can do to work around the kernel mismatch.
Sent from my DROID BIONIC using XDA App
open1your1eyes0 said:
That's right because he flashed 5.7.893 instead of the OTA. I'm just stating that I won't be flashing 5.7.893 and will just update the actual OTA (5.5.893). I'm aware he was mistaken.
Click to expand...
Click to collapse
You can find your way back so that you can take the OTA. Follow the instructions that p3droid has posted here: http://www.mydroidworld.com/forums/droid-bionic-forum/9800-how-get-your-phone-back-upgrade-path.html
I can personally testify that this works, because that is what I did to my phone last night. You can also use the forever root method from here: http://droidmodderx.com/bionic/too-easy-unbrick-bionic-with-oneclick-fastboot-restore/
Sent from my DROID BIONIC using Tapatalk
Remember to hit the "Thanks" button when someone helps you!
Are there any advantages to "downgrading" to 5.5.893 OTA from leaked 5.7.893?
rumpy said:
I was able to get to the OTA update using the following. Not sure if I got lucky or if it works for everyone.
I was able to get from the leaked 5.7 update to the official Verizon 893 Ota update.
1 – I used the R3L3AS3DRoot program and restored back to stock.
2 – Using the same program I 4RVRRooted the phone
3 – started up phone and did not sign into anything (google, etc). Did the bare minimum to get the phone up and running.
4 – Restarted in stock recovery and flashed radio.zip file that puts the radio back to stock. http://forum.xda-developers.com/showpost.php?p=19680673&postcount=40
5- Downloaded the OTA update and attempted to install. Phone rebooted and said that the update failed.
6- Copied the OTA update from http://www.multiupload.com/0ZEN69NGO2
7 – Installed the OTA update – SUCCESS!!
8 – Root is still there.
I am now at:
System version – 5.7.893.xt875.Verizon.en.US
Baseband Version – CDMA_n_03.1C.57r LTEDC_U_05.15.02
Webtop – WT-1.3.0-108_dbn-21
Kernel – 2.6.35.7-g68606e6 [email protected] #1
Build number – 5.5.1_84_dbn-62
Click to expand...
Click to collapse
How did you get the OTA to install from multiupload? I tried via stock recovery and cwm. I got my radio back to stock, but cannot get the ota flashed.
dagostin said:
If you applied the leaked 5.7.893 update there is no way at all to apply the official ota of 5.5.893. the leak updates your kernel and that makes the ota fail. at this time there is absolutely nothing you can do to work around the kernel mismatch.
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
Can anyone else confirm if this is true?
If Rumpy will post how he was able to get the OTA to flash manually after rolling back the radio, then I should be able to do the same thing. I am back to stock from the leak, with the stock radio and leaked kernel. My OTA fails via the auto method, CWM method and stock recovery method. I am rooted and haven't messed with any .apks or my webtop.
skullvet said:
If Rumpy will post how he was able to get the OTA to flash manually after rolling back the radio, then I should be able to do the same thing. I am back to stock from the leak, with the stock radio and leaked kernel. My OTA fails via the auto method, CWM method and stock recovery method. I am rooted and haven't messed with any .apks or my webtop.
Click to expand...
Click to collapse
It seems like the kernel is the only thing that can't be returned to stock (which is why the OTA fails). I want to see if anyone else can confirm this first.
What I'd like to find is the radio from 5.5.893. I think if we had that, we could find a way to get back on the upgrade path going forward. But so far, I've not been able to find it.
Baseband 5.5.893: CDMA_n_03.1C.57r LTEDC_U_05.15.01
Baseband 5.7.893: CDMA_n_03.1C.57r LTEDC_U_05.15.02
The kernel and webtop appear to be the same. My theory is if we could downgrade the radio, we could then use one of the 5.5.893 CWR images floating around to get back on the upgrade path. There's a signed radio for 886 to get back to stock, but, that won't help us. We need the kernel and radio to match 5.5.893 to guarantee being able to upgrade in the future.
skullvet said:
If Rumpy will post how he was able to get the OTA to flash manually after rolling back the radio, then I should be able to do the same thing. I am back to stock from the leak, with the stock radio and leaked kernel. My OTA fails via the auto method, CWM method and stock recovery method. I am rooted and haven't messed with any .apks or my webtop.
Click to expand...
Click to collapse
Has anyone else been able to get the OTA to take after going back to stock with the leak?
I used R3L3AS3DRoot and was then able to download the ota.
Sent from my DROID BIONIC using XDA App
If you applied the 5.7.893 leak there is no way to apply the officially released update. the update fails on checking the kernel and there is no current way to revert the kernel. for now just have to wait it out.
Sent from my DROID BIONIC using XDA App
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.