Related
Hi,
I've been searching the forums for this, but haven't found any real answer, so I thought I'd open a new thread .
I've successfully rooted my stock N1. However I'm wondering, with my newly acquired root rights, would it be possible to flash a custom kernel on it without needing to use a custom ROM.
The reason I'm asking this is that I would like to use iptables for use with a transparant proxy. It seems that the stock kernel does not support this
Of course if anyone has a different approach for the proxy, feel free to let me know as well .
Thanks!
I was able to flash just the cyanogen kernel onto my FRF91.
Sent from my Nexus One using XDA App
instructions?
Ok that is great news... did you encounter problems afterwards with any of the core components? what about some instructions on how to do this (or a link )
Thanks!
I haven't seen any problems with the stock components on the phone.
I can't find the thread I got this from to save my life! I don't know where you are in the process so here's the entire list of what I did:
Unlocked the bootloader using the fastbooot oem unlock command.
Flash Amon-Ra recovery for N1.
Reboot straight into recovery, Back up Stock ROM.
Flash Modaco's superboot for FRF91 from recovery
Flash Cyanogen's N1 Addons (which contains the kernel).
If you google update-nexusone-FRF91-cm-addons-signed.zip you'll see a bunch of downloads for the kernel update. The MD5 sum on the file I have is: 7cf8074d3685681728043f367e6b35fd
It goes without saying, but backup your phone before flashing...
Thanks
I actually rooted without unlocking the bootloader, and would prefer to keep it that way since I get to keep my warranty
I'll try this today, thanks a lot!
Tried it, failed
No worries though, just 'upgraded' to CM6 RC2
Hi,
I've just bought a new nexus one mobile phone from Egypt. Since the mobile was not officially released here, the only shops that sell it are the ones that import it from Europe...so lucky me i got my self a Vodafone Nexus one Mobile running Android 2.1-update1
After a long search on the internet i was able to update it to Android 2.2 (build FRF91). After another very long time trying to find the 2.2.1 update (build FRG83) i discovered that it wasn't released yet for the Vodafone mobiles. but some claim that by installing the FRG33 build Rom your kernel will completely change and thus you become a "Normal" nexus one
My questions are:
-Is the above true?
-How do i install this Rom?
-Does the process of installing the Rom need rooting my device?
-is there a simple tutorial for a noob (running Linux ubuntu) for rooting?
-Is it possible to root the mobile "Temporary" until I get to Build FRG83?
-Is there a high chance of Bricking the device?
Thx in advance!!!
Since you have AMOLED Nexus (otherwise it wouldn't be able to run 2.1), there is no problem flashing stock FRF91 on it.
Of course it requires rooting.
Read my signature, I hope you'll find your way from there easily. If any step in the directions below isn't clear - go to Wiki and find what it means and what needs to be done.
If you want stock 2.2.1:
Use 1-click root, install custom recovery (any), download stock FRF91, use the recovery to flash it, then download FRG83_from_FRF91 upgrade, rename to update.zip and put on SD card, go to the stock recovery (your custom recovery would be overwritten by then), flash update.zip.
If you want custom ROM:
Use 1-click root, install custom recovery, download and install custom ROM of your choice.
I would like to say that Android 2.2.1 has no major changes compare to Android 2.2.
for your questions..
-Is the above true?
I'm not sure about kernel version because I keep using third-party ROMs, but it's possible for FRG83 to have a different kernel than FRG91
-How do i install this Rom?
Stock FRG83 rom should be available to download somewhere, once you have unlocked bootloader and have a recovery (Amon or Clockwerk) installed, you should be able to flash FRG83 rom in recovery.
-Does the process of installing the Rom need rooting my device?
sorry about this
-is there a simple tutorial for a noob (running Linux ubuntu) for rooting?
http://wiki.cyanogenmod.com/index.php?title=Nexus_One
-Is it possible to root the mobile "Temporary" until I get to Build FRG83?
It's not necessary to root device temporarily, because once you have acquired root privilege, you can play a lot more tricky things, so there's no reason to become unrooted again, but I've heard from people who would like to receive update OTA, they have to unroot in order to get OTA update properly.
-Is there a high chance of Bricking the device?
Nexus One is now developer phone, so it's unlikely to be broken only by flashing new ROM
Wrong info. That's exactly why people should read before asking questions - because the answers they get might be partially correct at best.
1. Kernel versions don't matter, the OP just doesn't know ROM from Kernel. He should read more. He wants stock Google ROM.
2. Stock FRG83 is available from the same Wiki I've mentioned above, and some reports say that it doesn't like to be flashed from custom recovery and doesn't proceed. So I didn't suggest it, and suggested FRF91 which 100% flashes.
3. CyanogenMod Wiki only has 1 root method - unlocking the bootloader. It's definitely not the easiest one, and some people might want to keep their bootloader locked. I don't believe OP is one of them, since he bought a phone for unsupported country and warranty won't mean anything to him, but at least he needs to be educated about the differences. In Wiki he does, in your post - he doesn't.
4. When you flash stock ROM, you lose root - as simple as that. If he wants stock FRG83 - he WILL lose root, and if he wants it rooted - he'll have to go to Wiki again and see, how to root. If he has unlocked bootloader - it'll be just a bit easier.
5. Since he already has Froyo, chances are his radio is updated. If they aren't - the stock ROM contains radio, and if it's not up to date on the system - it will be flashed. Flashing radio incorrectly (terminating it in the middle, power failure, etc) is the only way to brick the device. So if his radio is updated - there's no chance he'll brick it, if it's not - it depends on if he'll touch the phone during the radio flash or not.
And this has no place in Development section.
well I'm still kinda confused, so I'll try to explain a little better what I got in mind first.
I read this post (google.com/support/forum/p/android/thread?tid=5fe9454b7c7261e7&hl=en) in the nexus one forums that explains the difference between 2 kernels one exclusive to Vodafone (Europe?) and one to other Carriers in the USA.
The kernel version I have ([email protected] #1) get updates like a month after other one and I believe I have to insert a Vodafone sim for it to work. what I read online (can't remember where) is by installing the FRG33 leaked rom on the device it basically changes the Kernel version to the US version ([email protected]#1) so that I can easily update to FRG83, as till now the Vodafone kernel still didn't receive the FRG83 update OTA.
I tried downloading the file FRG83 from FRF91 and it simply gives me a failed to verify file whole-signature and never completes the update.
So reading online, I'm still confused on what exactly to do to install this leaked rom. Now correct me if I'm wrong but what I understand from this thread I have to gain root privileges to install custom recovery and then install roms and solve my problem. right?
I'll be following this thread (forum.xda-developers.com/showthread.php?t=747598) to root my device is it the correct one?
You need to flash full update of frg33,and after that you'll update OTA to FRG83.Here it is the full rom http://shipped-roms.com/shipped/Pas...le_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip
Cheers
This is the thread with FRG33->83 OTA, link in the last post:
http://www.google.com/support/forum/p/android/thread?tid=51704fcd145670fb&hl=en
razlken said:
well I'm still kinda confused, so I'll try to explain a little better what I got in mind first.
I read this post (google.com/support/forum/p/android/thread?tid=5fe9454b7c7261e7&hl=en) in the nexus one forums that explains the difference between 2 kernels one exclusive to Vodafone (Europe?) and one to other Carriers in the USA.
The kernel version I have ([email protected] #1) get updates like a month after other one and I believe I have to insert a Vodafone sim for it to work. what I read online (can't remember where) is by installing the FRG33 leaked rom on the device it basically changes the Kernel version to the US version ([email protected]#1) so that I can easily update to FRG83, as till now the Vodafone kernel still didn't receive the FRG83 update OTA.
I tried downloading the file FRG83 from FRF91 and it simply gives me a failed to verify file whole-signature and never completes the update.
So reading online, I'm still confused on what exactly to do to install this leaked rom. Now correct me if I'm wrong but what I understand from this thread I have to gain root privileges to install custom recovery and then install roms and solve my problem. right?
I'll be following this thread (forum.xda-developers.com/showthread.php?t=747598) to root my device is it the correct one?
Click to expand...
Click to collapse
The kernel versions are identifying ROM variants, other than that they're of no use.
You can't apply FRG83-from-FRF91 update to Vodafone ROM, you need to install stock Google ROM first.
Yes, this is the correct thread to root the device.
Or you could do another thing that you wanted, and it'll probably be simpler:
Go to Wiki, download stock FRG33 image, rename to PASSIMG.ZIP, put on SD card, reboot the phone into bootloader. It'll automatically apply.
Then either wait for the OTA to FRG83, or apply the update.zip as I suggested above - only use FRG83-from-FRG33, that you can find linked in the first link, or in Wiki between "All stock ROMs and OTAs".
I've downloaded the FRG33 Rom and installed it using the PASSIMG.zip method. now the last problem, hopefully, is that i can't find a FRG83 from FRG33 OTA and i don't get any automatic OTA on my nexus one phone.
i tried the link but it seems that the any file on the google server was removed or something as it says page cannot be found and i can't find the file on the wiki.
any help here? and way to force the OTA to start on my nexus one or does anyone have the file or a mirror to the download?
Copy-pasted from some Google search:
Open the phone dialer
dial this: *#*#2432546#*#*
you'll see a notification that checkin was successful
Then, hit menu>>about phone>>system updates to see if anything is there.
Still nothing I dial it and get the checkin succeeded notification but when i go to the system updates it just says my system is up to date.
P.S: sorry for not searching but it's like 3 in the morning and I've been dealing with this for like hours....my brain hurts.
edit: tried using the passimg.zip method with this file (dl3.htc.com/RomCode/Source_and_Binaries/signed-passion-img-FRG83_0923.zip) which i found on the rom section of the wiki but after checking the passimg.zip the bootloader just reboots itself and returns to the main menu without doing anything.
Yes, it's reported that FRG83 doesn't like to be installed by PASSIMG method.
You could try renaming to update.zip and flashing in recovery.
Tried that but still nothing gives me an error: E: signature verification failed.
Well, in that case, if you really want FRG83 - you have to root and apply this update through a custom recovery.
The root and the custom recovery will be gone once you apply it.
ok so i rooted my phone using the rageagainstthecage method since the 1 click root does seem work for FRGXX build. then i used Rom Manager to install this file (http://loadbalancing.modaco.com/dow.../update-nexusone-FRG83-stock-radio-signed.zip)
now the last problem, not really sure if it is anyway, after the rom was installed i lost root privileges as u said but the recovery remained custom (clockwork mod) now I don't really care if it's stock or not, but am i going to get OTA updates with no problem even with a custom recovery or do i have to put it back to stock?
EDIT: I've Extracted the recovery.img from a stock FRG83 Rom and installed using the Flash_image method now i've got the stock Recovery back, I believe that this way everything is ok to receive OTAs in the future..
THX a lot to everybody that helped me out Especially Jack_R1
[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?
Hello all,
After many months of excitement, Motorola Canada released Froyo(2.2.1) for the Telus Moto Milestone. Through all of this, it seems like I've gotten the DSI and kernel errors. The 4 capacitative keys take a while to respond (3 times before they work), and my keyboard and contacts/messaging are all screwed up, color-wise.
I was looking at rooting following this guide (http://forum.xda-developers.com/showthread.php?t=983516) but do not know if the vulnerable sbf's would be able to work now that I have 2.2.1.
Also, I have been told that FroyoMod is a very stable Froyo ROM, which I was looking to customize with a Gingerbread theme that he has released (http://forum.xda-developers.com/showthread.php?t=815595). Will I be able to follow the same tutorial to revert back to stock 2.1 then apply the official Moto update (in case I need to return it for servicing)?
I've heard rumors of people bricking their phones after applying faulty radios after flashing a custom ROM. Will I need to worry about applying the proper radio? Or is fairly painless to do?
What happens if I brick my phone if I apply a wrong radio?
Sorry for all these questions, I'd like to make this entire process as easy as possible and I've never rooted a phone before!
Thanks in advance!
skadude66 said:
Hello all,
After many months of excitement, Motorola Canada released Froyo(2.2.1) for the Telus Moto Milestone. Through all of this, it seems like I've gotten the DSI and kernel errors. The 4 capacitative keys take a while to respond (3 times before they work), and my keyboard and contacts/messaging are all screwed up, color-wise.
I was looking at rooting following this guide (http://forum.xda-developers.com/showthread.php?t=983516) but do not know if the vulnerable sbf's would be able to work now that I have 2.2.1.
Also, I have been told that FroyoMod is a very stable Froyo ROM, which I was looking to customize with a Gingerbread theme that he has released (http://forum.xda-developers.com/showthread.php?t=815595). Will I be able to follow the same tutorial to revert back to stock 2.1 then apply the official Moto update (in case I need to return it for servicing)?
I've heard rumors of people bricking their phones after applying faulty radios after flashing a custom ROM. Will I need to worry about applying the proper radio? Or is fairly painless to do?
What happens if I brick my phone if I apply a wrong radio?
Sorry for all these questions, I'd like to make this entire process as easy as possible and I've never rooted a phone before!
Thanks in advance!
Click to expand...
Click to collapse
1. The sbf will still work, sbfs replace everything...so version does not matter
2. Radios are not such a big deal on milestone, they an be easily swapped from AOR ( if you mean basebands, i dont know of any radio files other than this)
3. You can usually reflash older sbfs, unless bootloader changed
Sent from my Milstone running CM7
Caz666 said:
1. The sbf will still work, sbfs replace everything...so version does not matter
2. Radios are not such a big deal on milestone, they an be easily swapped from AOR ( if you mean basebands, i dont know of any radio files other than this)
3. You can usually reflash older sbfs, unless bootloader changed
Sent from my Milstone running CM7
Click to expand...
Click to collapse
So I will be able to use the 2.1 sbf for Canada over the 2.2.1 official Moto update that I have right now?
How would I swap the basebands and I'm guessing AOR is OpenRecovery? How would I do that.
Does anybody know if the bootloader for 2.2.1 changed?
Thanks!
skadude66 said:
So I will be able to use the 2.1 sbf for Canada over the 2.2.1 official Moto update that I have right now?
How would I swap the basebands and I'm guessing AOR is OpenRecovery? How would I do that.
Does anybody know if the bootloader for 2.2.1 changed?
Thanks!
Click to expand...
Click to collapse
1. I dont know if you can resinstall 2.1 on top of 2.2, you should...but i have never tried. At wore, you could use one of the 2.1 based roms in the dev section...i wont be the official version, but it will be eclair.
2. AOR is Androidiani open recovery...it is a different version or openrecovery with a bit more options. There is a change baseband submenu that lets you install the baseband files for each country.
Sent from my Milstone running CM7
People are saying that the bootloader is different between 2.1 and 2.2.1, so I think I might wait and see what others think before I try and root it. Thanks for your help!
any luck since then to root your Milestone from 2.2.1?
Just got a shiny new Nexus 1 today, which out of the box is running Android 2.2. I'm wanting to update to 2.3.4 or whatever the latest OTA version is, and I'm too impatient to wait for any automatic OTA updates. When talking to a friend who also has a Nexus 1, when he asked me for my build number, I realised it's nothing like what he was expecting, or the build numbers for OTA updates like I've been seeing on the forums.
With a build number that looks quite different to what most people are posting about on the forums, I don't really want to try any manual updates in case it gives me a one-way ticket to brickville. I've tried using *#*#CHECKIN#*#* from the phone dialer, get a notification saying "checkin succeeded", but no system updates.
My About Phone screen is:
Model Number: Nexus One
Android Version: 2.2
Baseband version: 32.41.00.32U_5.08.00.04
Kernel Version: 2.6.32.9-27227-g3c98b0d [email protected] #1
Build Number: 2.16.405.1 CL223106 release-keys
As long as you have Nexus One, any build for Nexus One will work.
Use PASSIMG method to move completely to a new system, use "root, install custom recovery, back up everything, install whatever you want" method if you want to keep a backup of your current system.
Jack_R1 said:
As long as you have Nexus One, any build for Nexus One will work.
Use PASSIMG method to move completely to a new system, use "root, install custom recovery, back up everything, install whatever you want" method if you want to keep a backup of your current system.
Click to expand...
Click to collapse
The phone is completely stock and unrooted, and I'm wanting to keep the stock ROM (for now), so I was going to manually flash the OTA updates. But without being able to figure out what version/build I'm running now, I'm not sure which update(s) I need to push.
i think you need to activate the phone with google servers first...
there is a code for that ... i forgot.. search here...
and then they will send you the ota update
Your issue is that you have a custom build from a carrier. I have no idea what is custom, but it isn't the factory shipped Android version that most of us have. So, you will need to do that passimg method that Jack_R1 mentioned, which will take you to a real stock state and then you will receive the OTA updates.
You can still keep everything stock and non-rooted (although, stock will now be subjective for your phone and the carrier might not be willing to honor the warranty).
bassmadrigal said:
Your issue is that you have a custom build from a carrier. I have no idea what is custom, but it isn't the factory shipped Android version that most of us have. So, you will need to do that passimg method that Jack_R1 mentioned, which will take you to a real stock state and then you will receive the OTA updates.
You can still keep everything stock and non-rooted (although, stock will now be subjective for your phone and the carrier might not be willing to honor the warranty).
Click to expand...
Click to collapse
The phone was bought out-right through mobicity.com.au, so carrier warranties isn't an issue. Because it was not a carrier-locked phone, that's why I'm a little surprised that it's a non-standard ROM. Is there any walk-throughs or guides as to how to flash a stock ROM using passimg? And links to a flashable stock ROM? I did a bit of a forum search and didn't come up with anything other than "use passimg to flash blahblahblah".
Read my signature, please. Everything's in the Wiki. Follow "Unroot/restore" guide, PASSIMG method.
Jack_R1 said:
Read my signature, please. Everything's in the Wiki. Follow "Unroot/restore" guide, PASSIMG method.
Click to expand...
Click to collapse
Awesome thanks, I must have missed that when I was looking through the wiki. This works on the stock recovery, yes?
This is on the bootloader level, so the recovery or any part of the current ROM doesn't matter at all. It replaces the recovery too (with stock one).
Great success! Flashed a stock ROM as per the Wiki and it's now downloading/installing the OTA update to 2.3.4 \o/
Thanks for the help