i want to update to the .901 as i don't believe i am on it already(i just swapped someone for this phone yesterday & all i know is, before i rooted, i attempted to do an update and it said i'm up to date).
i got that 'bionic path saver'(which i'm also unsure on how to actual use properly) and see there's a command to apply an update for either the 893 or the 901 and i'm not sure what exactly i am on right now.
i don't want to just proceed with something and screw anything up as i have no warrenty.
thanks
Settings > about phone > baseband version.
Sent from my DROID BIONIC using Tapatalk
i thought it was system infomation cause that is the only thing that ends in .893 ??? now i am truly confused cause basesband ends in 05.15.01 that doesn't quite add up unless i am retarted..
System version should contain information about the software version you're running; XT875, etc.
Baseband relates to the radio: CDMA_N_.03....
Most OTA's update the radio/baseband as well so once one changes as does the other.
Related
[Q]FRG83G update for [KERNEL]2.6.32.9-g6624e39 [email protected] #1 && 3G DNS issues
Hi xda community
This is my first post in this forum. I am the new user of google nexus one phone. I bought it outright in Australia and it was delivered from a warehouse in Hongkong.
I am pretty sure that phone is not rooted as I can't run rooted apps. Thats alright I don't want to root my phone.
Only thing which I am curious about is how come I have this kernel instead of the default google nexus one kernel (which gets updates from Google server straight away). Is it normal ?
I've searched through different forums and xda as well and found out that probably this kernel is tweeked by vodafone and all the nexus one from vodafone has this kernel. Is this correct ?
As you may have gathered, I have opened up this thread because I haven't received android 2.2.2 update released by google. Currently I have FRG83D and I got this update as soon as I turned my phone ON for the very first time few weeks ago.
When I tried manually updating it using the method prescribed by techs, I get signature verification failed error always. I've tried downloading file numerous times from google server and its definitely not the file. Probably its related to this kernel.
Can one of you please guide that why am I unable to get the FRG83F update ?
2nd issue is, which is a major one. On 3g, I always get browsing issues because of DNS failure. yahoo messenger remains connected, which is good. Its just browsing which fails using domain name.
I've done ping tests. Ping to IP pass, but Ping to domain fail. Only work around is that I have to restart 3g by either going into airplane mode or by selecting 2g and then unticking it, or by resetting the APN. This is really annoying cuz if my screen goes off after few minutes on idle time, DNS starts failing again and I have to keep on going through the same cycle of resetting 3g connection.
I am not using any 3rd party app to manage 3g or wifi. SMODA widget works fine to enable, disable 3g but after few minutes of idle time, DNS starts failing again.
I've tried using gscript lite, but it doesn't work on an unrooted phone. I cannot use setprop method as well cuz phone is not rooted. Is there any other method using which I can harcode the dns for 3g connection ?
WIFI works fine.
Can you please guide me a way to fix this issue ?
Kind Regards
Looks like you have one of the network supplied N1's, which have slightly different software.
Rusty! said:
Looks like you have one of the network supplied N1's, which have slightly different software.
Click to expand...
Click to collapse
Thanks for replying Rusty.
Does this mean that I will get OTA eventually ? or My only option is to flash the Rom with the Google Stock ROM ?
Should get it eventually yes, what you do depends on your level of patience
haha. Thanks Rusty I'll wait for few days and will contact u if needed any help.
lmk0 said:
This thread is growing way too fast to see if someone already figured out a possible solution, but this is for everyone getting the Status 7 errors...
I kept getting the Status 7 error too. My Nexus One was CM6.1, rooted and unlocked, etc
I followed instructions from this post by guitar east... http://forum.xda-developers.com/showpost.php?p=11618802&postcount=972
But I still ended up with Status 7...
Long story short, I did some troubleshooting and eventually figured it out. When running the update.zip from Recovery, it looks for the previous version. They all have dependencies on the previous version.
Think of it as a chain.
It had nothing to do with what ROM I had or if it was rooted. It simply needs to be done in order, i.e. FRG33 > FRG83D > FRG83G > GRI40
So download the following (sorry I don't have the links - mods feel free to udpate). Follow the instructions in the post mentioned above from guitar east. That includes the PASSIMG.zip steps, copy signed update zips to SD, rename to update.zip, reboot, recovery, etc, etc a few times BUT DO ALL OF THEM AND DO THEM IN ORDER. You'll be running Gingerbread in no time.
I used:
Passion-FRG33.zip
ecb21b752065.signed-passion-FRG83D-from-FRG83.ecb21b75.zip
2854b06b22b9.signed-passion-FRG83G-from-FRG83D.2854b06b.zip
81304b2de707.signed-passion-GRI40-from-FRG83G.81304b2d.zip
Try it out, worth a shot, and it may fix your Status 7 errors too!
And since I actually posted, might as well give everyone here at XDA all my thanks they have deserved over the years. A googol thank yous!
Click to expand...
Click to collapse
XDA - FORUM rocks. I had an unlocked Nexus one with the kernel version [KERNEL]2.6.32.9-g6624e39 [email protected] #1 and I bought it outright from HONGKONG. I didn't want to root the phone and didn't want to risk bricking my phone either. My phone had FRG83D and upgrade to FRG83G was failing with the error "signature verification failed"
I read this champion's post and used XDA-Forum Nexus wiki @ http://forum.xda-developers.com/wik...us_One/Guides_&_Tutorials#Flashing_custom_ROM and downgraded from FRG83D to FRG33 stock ROM using PASSIMG.ZIP method and then upgraded to FRG83, FRG83D, FRG83G and finally to GINGERBREAD
I could not have done it with out this forum. You guys rock. Keep up the good work.
Thanks for all your efforts guys.
neXus-sniper said:
XDA - FORUM rocks. I had an unlocked Nexus one with the kernel version [KERNEL]2.6.32.9-g6624e39 [email protected] #1 and I bought it outright from HONGKONG. I didn't want to root the phone and didn't want to risk bricking my phone either. My phone had FRG83D and upgrade to FRG83G was failing with the error "signature verification failed"
I read this champion's post and used XDA-Forum Nexus wiki @ http://forum.xda-developers.com/wik...us_One/Guides_&_Tutorials#Flashing_custom_ROM and downgraded from FRG83D to FRG33 stock ROM using PASSIMG.ZIP method and then upgraded to FRG83, FRG83D, FRG83G and finally to GINGERBREAD
I could not have done it with out this forum. You guys rock. Keep up the good work.
Thanks for all your efforts guys.
Click to expand...
Click to collapse
Thank you so much for that post
(in case it's not obvious, I had the same problem you had, and I did exactly what you did, and now I have Gingerbread on my Nexus One )
Awesome .. To be honest credit goes to the lmk0
Can I please ask what version of baseband/radio did you have when you were on the htc-kernel and what version is it running now after the gingerbread update?
I forgot to note down the previous version of baseband/radio but it was different to what I have now. Now it is :
Baseband : 32.21.00.32U_5.08.00.04
Kernel: 2.6.35.7-59423-g08607d4 [email protected] #1
Also I have SLCD verion of nexus one.
neXus-sniper said:
I forgot to note down the previous version of baseband/radio but it was different to what I have now. Now it is :
Baseband : 32.21.00.32U_5.08.00.04
Kernel: 2.6.35.7-59423-g08607d4 [email protected] #1
Also I have SLCD verion of nexus one.
Click to expand...
Click to collapse
Thanks for the quick reply. That's great as I have a SLCD one too with the same htc-kernel and am looking to upgrade it to gingerbread as well.
Just one more thing, did you use this file "766a101ae02c.signed-passion-ota-60505.766a101a.zip" to upgrade from FRG33 to FRG83 as I have read on other threads that FRG33 file actually has the newer radio (v5.08) whereas this FRG83 has the older one (v4.06) so your baseband actually gets downgraded in the process. Did you anywhere had to manually update the radio as v5.08 is the minimum requirement for gingerbread.
My current radio/baseband is "32.50.00.32U_5.12.00.08" which is what I think you would have had originally on the htc-kernel as well.
As far as I remember, mine was similar to ur one as well. Yes I used "766a101ae02c.signed-passion-ota-60505.766a101a.zip to upgrade from FRG33 to FRG 83 and then I upgraded to FRG83D and then FRG83G and then gingerbread.
Basically vodafone tweaked the radio to use on their network. I don't know why. But as soon as you will update to gingerbread radio will be : 5.08.00.04
I dont think radio matters. As I said, I didn't care about the radio and just followed the procedure. But I can't gaurantee anything as I don't know much difference in radios. When you will downgrade to FRG33, radio version will change and it will be 4.* something but it didn't halt or cause issues with upgrades.
I hope I've answered ur question. BTW U can get sotck roms from the following link:
http://shipped-roms.com/index.php?category=android&model=Passion (Nexus One)
If you'll do it, Just do it in sequence. Downgrade method is PASSIMG.ZIP one. For upgrades U'll use update.zip
neXus-sniper said:
XDA - FORUM rocks. I had an unlocked Nexus one with the kernel version [KERNEL]2.6.32.9-g6624e39 [email protected] #1 and I bought it outright from HONGKONG. I didn't want to root the phone and didn't want to risk bricking my phone either. My phone had FRG83D and upgrade to FRG83G was failing with the error "signature verification failed"
I read this champion's post and used XDA-Forum Nexus wiki @ http://forum.xda-developers.com/wik...us_One/Guides_&_Tutorials#Flashing_custom_ROM and downgraded from FRG83D to FRG33 stock ROM using PASSIMG.ZIP method and then upgraded to FRG83, FRG83D, FRG83G and finally to GINGERBREAD
I could not have done it with out this forum. You guys rock. Keep up the good work.
Thanks for all your efforts guys.
Click to expand...
Click to collapse
Hi,
I got the same problem as you! Can you please teach me how to do it step by step? I am not good at computer stuff....
Many thanks!!
konisan
Hoping to upgrade from 2.2.1 to stock 2.3.3 on SLCD Nexus One
Hey guys!
I am new to world of root to pure android and custom roms so I have bought a Nexus One (updated OTA from Vodafone AU to 2.2.1) quite recently in the last few weeks so I could play around with it, knowing that factory installed roms were available in case I screw up something. To begin with, I know that this thread is very relevant to my case and I was hoping to update the phone to stock 2.3.3 before I could go back and start installing custom roms later. Sure, I could have bought the Nexus S and just started from there but I wanted to own a phone that I could update myself (plus Nexus One looks better imo )
My N1 specs:
Nexus One PUT ship S-ON
HBOOT- 0.35.0017
MICROP - 0c15
Touch Panel - SYNT0103
Radio-5.12.00.08
Baseband version: 32.50.00.32U_5.12.00.08
Kernel version: [email protected]#1
Build number: FRG83D
I have done quite a bit of research and I thought I could just manually update it but I have read from this thread that each revision of android was dependent on the previous version. So I normally would get the same error message as most people with (E:signature verification failed. Installation aborted)
I am aware that Vodafone AU may have installed their version of 2.2.1 onto my N1 via OTA so I was also contemplating to revert from FRG83D down to stock FRG33 and work my way back up again. But reading the XDA wikis and more forum threads, I have found out that my N1 is a SLCD version and I would risk bricking the phone and end up with the red trackball of death.
So I am asking all you pros out that, what is the best method I could safely update my 2.2.1 N1 to stock 2.3.3 not custom roms? I have gone through many forum threads and they are usually specific to their AMOLED brothers and custom roms too.
Please spare some time and advice to help a newbie!
Thanks
It's pretty easy, but you're going to have to root.
Use SuperOneClick to root the phone, then install ROM Manager from the Market. Use ROM Manager to flash Clockwork recovery, and install this zip: http://www.multiupload.com/7PFE6QVIEO
You're now on stock GRI40 and so will be able to update to 2.3.4 using the stock Google update.
Thanks Rusty!
I'll give it a go! I thought no one else was going to read this thread again! I'll ask again if I stumble but thank you for responding.
Cheers!
There is an even easier way actually. Will still wipe the phone though.
Here is a link to an FRG83G passimg: http://tinyurl.com/6bym3vg
Rename it to passimg.zip, stick it on the root of your SD card and power the phone off. Hold Vol- and power on, the phone will find the file and ask to install. Say yes and shortly you will be on Google's FRG83G build, which will OTA itself to GRJ22 at some point.
Oh I thought the PASSIMG method only worked with AMOLED screen N1s.
Wouldn't I brick my phone this way if I downgraded the HBOOT on my SCLD N1?
It wont downgrade the HBOOT, FRG83G was the update that pushed the .35 HBOOT out to phones that didn't have it, and SLCD support was included in the FRG33 passimg.
Wow! That's awesome and really good news to hear!
I will definitely give a shot with that PASSIMG method now! I believe that this method would bring me to the google stock rom level of 2.2.2?
Will the stock roms available on the wiki would work from this FRG83G build > GRI40?
I'm currently running 2.2.2 OS Build FRG83G. The phone has downloaded the system update but refuses to install it. I keep getting "zip verification failed". I've even tried a manual update with the same results. The phone is rooted and unlocked if that helps. How do I get this phone to update to Android 2.3.3 Gingerbread ?
You have to be stock to apply official updates. Sense you are rooted, why not just flash one of the stock rooted builds in the dev section?
Hmm ok, I will go do that then and see if that works.
<snip><snip><snip>
I am having a similar problem. I have a brand new N1 with 2.2 build 2.16.405.1 CL223106, do you know if I can jump right to 2.3.4 without first going to 2.2.3? Whats with my build number? Why doesn't it show FR....? I tried the #*#checkin*#* and am getting nothing OTA. Thanks.
You may have carrier specific build. Are you with Vodafone, or Videotron, etc?
Shouldn't be with Vodafone or Videotron. Its a PB99100 and should be for Tmobile. I bought this new from a 'questionable' site on the internet and now I'm freaking out. I do get 3G with my tmobile sim card.
Just because it works on T-Mo, doesn't mean it doesn't have a ROM from another carrier. It's possible you got some back stock from a carrier that tweaks their ROM...
I don't recognize the build number, so I couldn't say for certain, but it doesn't sound like a Google build...
You can switch to a stock ROM very easily by following the unroot/restore guide in the wiki. It will wipe your phone, so you may wasn't to backup what you can first (MyBackup is about the best non-root option).
Since you bought a version from a questionable source, does it happen to have a lock symbol at the bottom of the 'X' when you boot up? If so, it will make it sooo much easier to get your phone to a modern version. You could still stick with Google's Stock Android, or you could go with a better (in my opinion) 3rd party ROM like CyanogenMod.
Please move this to Development if you see fit (I can't post there yet.)
If we have moved to 5.7.893 with a modified kernel and radio, are we off the upgrade path? Are we in danger of getting stuck?
I understand using leaks carries risks I just want to understand what we are looking at. I know people are trying very hard to unlock the bootloader with the help of Cheesecake, and I thank everyone for that.
from what i have read and understand, yes you are off the upgrade path because of the kernel. you can get system and radio back to stock but not kernel yet.
Once the update "drops" it will be out there for people to flash themselves though just like the ones so far.
Mer2112 said:
Once the update "drops" it will be out there for people to flash themselves though just like the ones so far.
Click to expand...
Click to collapse
I was just worried because the updates are a from and to style system.
Version you have -> Version you are updating too.
I was worried we wouldn't have one to go "from" 5.7.893
I have both upgrades on my sd card currently i'm on 901. The question is can I just flash the first upgrade and go back from current 901 to the 893 or whatever factory upgrade was. I know I can go to base and go forward but I want to sewer if I can flash backwards if I have original update from Verizon.
The downside to bootloader encryption is that once a new radio baseband and kernel have been flashed, you're stuck until they release a signed update designed to upgrade from the version you're running. In short: you're stuck.
Currently there is a signed radio for 886 and 893. Take your pick. With the stock886 boot hack; you may also flash kernel. You can backtrack to either of those, then go back up the chain to whatever you have updates to.
BBB
Energy = Area.
And since daywalker04 released the 5.7.893 FXZ, there is also a signed radio update.zip for the MR-11 radios. So the choice is yet greater.
I actually ran the 5.7.893 for a long time, from it's initial leak till the leak of 5.9.901 about 10 days ago, and I think the MR-11 radios perform as well or better than the .901 radios. I am in a 3G only area though and widely variable network conditions due the the rollout of LTE and issues with the eHRPD system make any anecdotal reports virtually meaningless, unfortunately.
Great to have more options though!
Edit: I also think its a shame that someone as prolific and helpful as realbbb has been lately with Bionic dev should have only one or two thanks on his meter.
Thank the guy fercrissakes! He is doing really good work to make the new recovery files and techniques as useful and well refined as possible.
Confused..
Now I am a bit confused. I'm on the 5.8.894 leak from a few weeks back and was under the impression that the recent developments could still get back to 883 and the upgrade path. But it looks like your are saying that it's only for 893??
Beef
The full 5.5.893 FXZ file will return you to stock from 5.8.894 without any issues.
From there you can root and 4everoot using realbbb's ROTA893.bat file.
cellzealot said:
The full 5.5.893 FXZ file will return you to stock from 5.8.894 without any issues.
From there you can root and 4everoot using realbbb's ROTA893.bat file.
Click to expand...
Click to collapse
I haven't seen a full FXZ for 893, only the 886 with steps to then pull the OTA update. I'll search more.
+1 thanks.
Beef
Bionic
Verizon network
System Info: 6.7.2231.xt875
Android version: 4.0.4
Build Number: 6.7.2_223
So I got fed up with the phone as it was and updated it to the info above. I have never done this before and just did it following the info instructions on droidhive. Didnt do anything more than back up contacts and downloaded the ICS leak and installed it with out bootstrap this or bootloader that or anything. Probably did more than I should have as I dont undertand anything about rooting or ROMS or anything else.
Now my understanding from reading here is when and if Verizon does a OTA upgrade I will not either 1) recieve notification nor 2) be able to download it is that correct? I also cannot go back to my old build since I didnt , insert magic special thing I should have downloaded or installed prior to me updating, is that correct also? Can I do further upgrades that I have been reading about on this forum as written and in theory if I follow the instructions should be ok? or do I need to go back to the old build (if possible) then work my way back up?
I probably should have left well enough alone but I was getting so pissed with my phone and I tell you since I upgraded to that leak it runs very nice with a few hiccups when I try and run different apps. Figure if I screw it up too bad I can always get the Samsung Siii...and not mess with it...thanks for entertaining this newb!!
Take a look at this thread. It shows how to get back to .905, or to go to newer versions without losing your data. As of right now, I suggest going with the .232 leak, which is the latest you can go to while still being able to return your phone to gingerbread.
http://www.droidforums.net/forum/droid-bionic-hacks/214902-downgrade-902-no-app-data-loss.html
Android_Troop said:
Bionic
Verizon network
System Info: 6.7.2231.xt875
Android version: 4.0.4
Build Number: 6.7.2_223
So I got fed up with the phone as it was and updated it to the info above. I have never done this before and just did it following the info instructions on droidhive. Didnt do anything more than back up contacts and downloaded the ICS leak and installed it with out bootstrap this or bootloader that or anything. Probably did more than I should have as I dont undertand anything about rooting or ROMS or anything else.
Now my understanding from reading here is when and if Verizon does a OTA upgrade I will not either 1) recieve notification nor 2) be able to download it is that correct? I also cannot go back to my old build since I didnt , insert magic special thing I should have downloaded or installed prior to me updating, is that correct also? Can I do further upgrades that I have been reading about on this forum as written and in theory if I follow the instructions should be ok? or do I need to go back to the old build (if possible) then work my way back up?
I probably should have left well enough alone but I was getting so pissed with my phone and I tell you since I upgraded to that leak it runs very nice with a few hiccups when I try and run different apps. Figure if I screw it up too bad I can always get the Samsung Siii...and not mess with it...thanks for entertaining this newb!!
Click to expand...
Click to collapse
I agree.. if you are running 223 right now.. i would stick with it till the ota. You might not recieve notification but either way, you will be able to dl the image and load it the same was as you did with 223. seeing as how it will be signed it shouldn't be a problem. I have been running 223 for a few days now and overall i'm very happy with it. i just wish that i could turn the 4g off sometimes because it's a beast on the battery in my area..
I'm Loving the .223 update. It has made my Bionic into the phone Verizon should have provided me from day one!!! It isn't perfect, but it is darn good, miles, yards, acres, even years ahead of Gingerbread.
Phiber187 said:
I agree.. if you are running 223 right now.. i would stick with it till the ota. You might not recieve notification but either way, you will be able to dl the image and load it the same was as you did with 223. seeing as how it will be signed it shouldn't be a problem. I have been running 223 for a few days now and overall i'm very happy with it. i just wish that i could turn the 4g off sometimes because it's a beast on the battery in my area..
Click to expand...
Click to collapse
Phiber187.. Get "Phone info" app from the Android market (Sorry Google Play) It will allow you to turn 4g on and off.
Bionic
Verizon network
System Info: 6.7.2231.xt875
Android version: 4.0.4
Build Number: 6.7.2_223
Guys still running above on the phone but have read of some upgrade/ROMs that I'd like to do, but it says I need to be rooted and I never rooted even when I did the upgrade shown above. Everything Im reading on how to root is assuming Im on the stock GB does it matter that Im not on GB and I still can do it on ICS the same way? Please advise on steps to root it now so I can continue upgrading and installing ROMS...thanks!