My Nexus one coult not recieve over the air update.
So I loaded a passimg file on it but when it rebooted i noticed it was not a europe ROM.
This was the file I loaded on itPassion_Google_WWE_2.16.1700.1_FRG33_MFG_Shipment_ ROM.zip
The rom i need with dutch language is this i guess:
Cestina
Dansk
Deutsch
English (Australia)(New Zealand)(South Africa)(UK)(US)
Espanol
Francais
Italiano
Nederlands (DUTCH°
Polski
Portugues
Svenska
and Russian
Can someone give me a link to a recent file.
The files i already tried give me the following error: Main version is older, UPDATE fail.
I just want dutch language back on it, who can find a european passing.zip stock rom that works.
Currently this is on the device: android 2.3.4, build GRJ22
thx
This seams strange to me because the default android ROM has many languages, now I am running cm6.1.1 so it may be a little different but I have all the languages you mentioned above (except Russian but I figure that is because it is righten in a language I don't understand ) so I'm not sure but if you go to settings -> language & keyboard -> select language they should be there.
Dude Random21 said:
This seams strange to me because the default android ROM has many languages, now I am running cm6.1.1 so it may be a little different but I have all the languages you mentioned above (except Russian but I figure that is because it is righten in a language I don't understand ) so I'm not sure but if you go to settings -> language & keyboard -> select language they should be there.
Click to expand...
Click to collapse
thx for your reaction: It shows the following locale:
Deutch
English (UK)
English (US°
Espanol (espana)
espanol (estados unidos)
Francais
Italiano
Portugues
AND 4 chinese languages
So the nexus one sure has other language roms
How can i get the DUTCH one back??
I used this tut for putting the passimg file with the wrong language files on my phone.
this was the procedure I followed:
1.Download all the update files listed in the Links to Files section at the bottom of this post.
2.Unzip Passion_Google_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip. One unzipped you will find a zip file called PASSIMG_Passion_Google_WWE_2.16.1700.1_FRG33_release_signed.zip. Rename this file passimg.zip and copy to the root of your SD card.
3.Use the PASSIMG.ZIP method above to install the file. Once you are in the HBOOT menu, it will automatically start loading the passimg.zip file and then prompt you asking if you want to install the updates. Press Vol Up to install these updates. Once the process has completed, you will be asked to press VolumeUp to reboot the phone. it may prompt you to restart the phone or restart it automatically for you. (SOMEONE PLEASE CONFIRM WHAT IT ACTUALLY IS. It was 4am when I did it and I can’t remember anymore).
4.When the phone has finished rebooting, it will be as if you have a new phone and will prompt you for your google account. Don’t enter your Google account. You should only do this once you have finished installing the Gingerbread update.
5.Check your android version information matches the following:
It was the Passion_Google_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip. that contained the wrong language files for me
does anybody has such a file with dutch language?
There's no stock google ROM that supports Dutch on our Nexus One, you will have to use this Vodafone frf91 ROM (rename PASSIMG.ZIP).
There's no gingerbread update yet, but they are working on it..
@ Tommert38
I get the message, main version is older update failed
I have currently this is on the device: android 2.3.4, build GRJ22
what can i do ?
thx
Unlock your bootloader and flash a ROM that has support for Dutch (like the stock one in the link posted above, or send it in for warranty...
the strange thing is it had originaly the DUTCH europe rom on it en then i follewed this methode on this site ossadmin.wordpress.com/2011/02/26/goodbye-vodafone-uk-nexus-one-rom and it changed in a english rom.
for this procedure i diddend had to unlock bootloader on my unrooted machine
it seems that restoring my nexus to stock firm is a hard procedure to follow since I dont wont to lose my warranty
ydq473 said:
the strange thing is it had originaly the DUTCH europe rom on it en then i follewed this methode on this site ossadmin.wordpress.com/2011/02/26/goodbye-vodafone-uk-nexus-one-rom and it changed in a english rom.
for this procedure i diddend had to unlock bootloader on my unrooted machine
it seems that restoring my nexus to stock firm is a hard procedure to follow since I dont wont to lose my warranty
Click to expand...
Click to collapse
When you followed that procedure, you flashed a WWE (World Wide English) ROM to your device. A WWE ROM does not have Dutch. To get Dutch, you need to flash a VF ROM. However, you tried to do that, but you got the "main version is older" error. So, your only options are to unlock your bootloader, and then flash the images from the VF ROM, or, since you say it is still under warranty, send it in for repair.
I contacted HTC about the problem.
Theire response:
Thank you for contacting HTC regarding your Google Nexus One I understand that you are currently experiencing difficulties with getting the 2.3 update. I apologise but as this has not been updated by the official process we would not be able to provide support on this and the warranty would now be void.
What since when does using the passimg method void your warranty it's Google signed files, might as well say that using the update.zip with there file from there servers voids your warranty because you didn't do it via OTA.
Ok so the way I see it you have two options root with one of the many methods and flash a ROM that has the languages you want OR call the guys at htc back a few times cause maybe the guy you talked to the first time didn't know exactly what he was talking about and thought you flashed custom firmware not Google signed firmware if they don't take your case then you may just have to root.
Htc refered in their last mail with me to:
Dear X,
Thank you for your email and the information. I can only apologise however we would always advise to search for updates manually or wait until these are pushed to you over the air. I am only advising you of our terms and conditions of repair and warranty. I have enclosed these for you.
http://service.europe.htc.com/terms.aspx
Terms & condistions
1. Estimated turnover period
We estimate that we will normally be able to complete orders and return the units to most mainland addresses in the UK within 5 working days from receipt of the unit. Where the repair requires parts to be specially ordered or delivery to remote areas of the UK, or to other countries, this may take longer. HTC EU will endeavour to complete all orders within 5 working days from clearance of payment or warranty authorisation.
2.1 General
These terms and conditions do not affect your statutory rights.
2.2 In warranty Repair
In-Warranty repair means a repair carried out on a unit within 12 months of its purchase. This is not a Non-Warranty chargeable repair.
2.3 Non-Warranty chargeable repair
Repair of a unit that is In-Warranty but which needs to be repaired for one of the following or similar reasons will be classified as a Non-Warranty chargeable repair:
a) Accidental damage. Accidental damage to the unit, such as dropping it on the ground or in water, broken LCD, damaged Sync/Charger Connector, damage caused by liquid entering the unit, dog bites, or other misuse due to failure of the customer to follow the instructions properly or failure to upgrade the software as procedures outlined warranty terms or downloading illegal software onto the unit. Where the fault is caused by downloading illegal software into the unit or other accidental damage, the customer will be required to pay for spares, labour, diagnosis and software refurbishment along with shipping and handling charges plus VAT. These figures together with any other costs will be specified under the "quotation for chargeable repairs" procedure as set forth in this Agreement.
b) No Fault Found (NFF). Given below are some examples of NFF:
Failure of the unit to charge due to particles trapped inside the charging socket.
Failure to use the unit properly according to instructions in the manual and warranty terms.
If the unit is identified as NFF, the customer will be required to pay the cost of fault-diagonsis and shipping. These figures together with any other costs will be specified under the "quotation for chargeable repairs" procedure as set forth in this Agreement.
c) Liquid Damage. We recommend that the customer does not send us phones which have been damaged by liquid. Liquid damaged phones are expensive to repair as all the major components have to be replaced and for this reason we classify them as Beyond Economic Repair.
Dude Random21 said:
What since when does using the passimg method void your warranty it's Google signed files, might as well say that using the update.zip with there file from there servers voids your warranty because you didn't do it via OTA.
Ok so the way I see it you have two options root with one of the many methods and flash a ROM that has the languages you want OR call the guys at htc back a few times cause maybe the guy you talked to the first time didn't know exactly what he was talking about and thought you flashed custom firmware not Google signed firmware if they don't take your case then you may just have to root.
Click to expand...
Click to collapse
Two things:
The "passimg" method as you so call it, is using a shipped ROM that was leaked by someone. It was never "officially" released by Google. If you happen to flash the wrong leaked image onto your device (like what the OP did), you do not have official software on your device...
Second, how do you expect him to root 2.3.4 without unlocking his bootloader? Not possible at this point in time. He could try to reflash the same shipped ROM that he originally did, and if that works, he could root that build, flash a custom recovery, and then flash a Dutch-compatible ROM.
efrant said:
Two things:
The "passimg" method as you so call it, is using a shipped ROM that was leaked by someone. It was never "officially" released by Google. If you happen to flash the wrong leaked image onto your device (like what the OP did), you do not have official software on your device...
Second, how do you expect him to root 2.3.4 without unlocking his bootloader? Not possible at this point in time. He could try to reflash the same shipped ROM that he originally did, and if that works, he could root that build, flash a custom recovery, and then flash a Dutch-compatible ROM.
Click to expand...
Click to collapse
hello
i never ever rooted or unlocked my bootloader
i just had problems with over the air updates on my N1. I installed Passion_Google_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip and renamed passing.zip like described here, then I rebooted and dutch language was gone but OTA, update to ginngerbread.
now i just want to go back to dutch stockrom
http://ossadmin.wordpress.com/2011/02/26/goodbye-vodafone-uk-nexus-one-rom/
when I trie the same proces with a dutch rom i get the error: Main version is older update fail
efrant said:
Two things:
The "passimg" method as you so call it, is using a shipped ROM that was leaked by someone. It was never "officially" released by Google. If you happen to flash the wrong leaked image onto your device (like what the OP did), you do not have official software on your device...
Second, how do you expect him to root 2.3.4 without unlocking his bootloader? Not possible at this point in time. He could try to reflash the same shipped ROM that he originally did, and if that works, he could root that build, flash a custom recovery, and then flash a Dutch-compatible ROM.
Click to expand...
Click to collapse
For thing number one yes I know it was leaked but it's still google singed so how do you want them to know the difference between the two also if he just flashes the 2.3.3 passimg file that was released by htc on their developers page then it is not leaked or illegal software it was put there by the manufacturer of the phone so it should be good.
For thing number two that is exactly what I meant he did the passimg method once so he can do it again then from there just root it and flash a rooted version of 2.3.4 like the cm nightlys.
Dude Random21 said:
For thing number one yes I know it was leaked but it's still google singed so how do you want them to know the difference between the two also if he just flashes the 2.3.3 passimg file that was released by htc on their developers page then it is not leaked or illegal software it was put there by the manufacturer of the phone so it should be good.
Click to expand...
Click to collapse
They know, because he has a vodafone N1, which did not come with 2.3.3, and there is no way of getting 2.3.3 on a vodafone N1 (as there are no official updates yet) without either unlocking the bootloader, or flashing a leaked build (to go to unbranded). No other way...
ydq473 said:
hello
i never ever rooted or unlocked my bootloader
i just had problems with over the air updates on my N1. I installed Passion_Google_WWE_2.16.1700.1_FRG33_MFG_Shipment_ROM.zip and renamed passing.zip like described here, then I rebooted and dutch language was gone but OTA, update to ginngerbread.
now i just want to go back to dutch stockrom
http://ossadmin.wordpress.com/2011/02/26/goodbye-vodafone-uk-nexus-one-rom/
when I trie the same proces with a dutch rom i get the error: Main version is older update fail
Click to expand...
Click to collapse
I'm assuming that it is a translation issue, and not you not reading my posts.
YOU FLASHED AN STOCK, UNBRANDED, ENGLISH ROM. This was NOT an official ROM for your device. If you want to go back to a Dutch ROM, you have to either root your device, or unlock your bootloader, and flash back the Vodafone ROM. You cannot do it without root or an unlocked bootloader.
Is everything clear up to this point?
efrant said:
They know, because he has a vodafone N1, which did not come with 2.3.3, and there is no way of getting 2.3.3 on a vodafone N1 (as there are no official updates yet) without either unlocking the bootloader, or flashing a leaked build (to go to unbranded). No other way...
Click to expand...
Click to collapse
Ok for the frg33 your right it is leaked unofficial firmware but what about htc's 2.3.3 that it is not leaked it was purposely sent out and it has Google's signature on it so you can't say that that is leaked by htc cause or else Google would have forced them to take it down, then maybe it would be considered illegal but Google said nothing so it they can't say that that is illegal software cause or else they should sue htc for releasing something they had no permission to and that had Google's signature not say that people can't use it. Or am I missing something?
efrant said:
I'm assuming that it is a translation issue, and not you not reading my posts.
YOU FLASHED AN STOCK, UNBRANDED, ENGLISH ROM. This was NOT an official ROM for your device. If you want to go back to a Dutch ROM, you have to either root your device, or unlock your bootloader, and flash back the Vodafone ROM. You cannot do it without root or an unlocked bootloader.
Is everything clear up to this point?
Click to expand...
Click to collapse
cristal clear
i gonna try a life chat tomorow with htc but i guess they gonna follow your lead on this
if they cant help i gonna root or unlock because my warranty is already void said htc
Dude Random21 said:
Ok for the frg33 your right it is leaked unofficial firmware but what about htc's 2.3.3 that it is not leaked it was purposely sent out and it has Google's signature on it so you can't say that that is leaked by htc cause or else Google would have forced them to take it down, then maybe it would be considered illegal but Google said nothing so it they can't say that that is illegal software cause or else they should sue htc for releasing something they had no permission to and that had Google's signature not say that people can't use it. Or am I missing something?
Click to expand...
Click to collapse
I think you are missing something. Point me to an official link to a 2.3.3 shipped ROM (a I mean a shipped ROM, i.e., one with all the images in it, just like the FRG33 one that you can use via PASSIMG).
efrant said:
I think you are missing something. Point me to an official link to a 2.3.3 shipped ROM (a I mean a shipped ROM, i.e., one with all the images in it, just like the FRG33 one that you can use via PASSIMG).
Click to expand...
Click to collapse
Maybe your right and maybe I am but I could have sworn that i heard of people using it like that http://developer.htc.com/ scroll down and look for nexus one system image. Now if you don't believe me then I can always try it if you want, just ask if you want me to I'll nandroid then flash then we will see but if you know other wise then please elaborate to save me the trouble.
Related
Hello everyone, my HTC DREAM touch screen just died on me today meaning it doesn't detect me. I tried battery pull and soft/hard reset and even wipe. I plan on bringing it back to rogers for a replacement or repair but I gotta revert this back to stock. My Phone is rooted and is rogers its also running cyanogen. How I unroot and install the factory firmware, i have looked through google and here and i may missed some or didn't see any results that reflected what I was looking for.
You obviously did not search Google correctly.
Al you'll really need is to find the DREAIMG.nbh file for RC29, and use fastboot to flash it over. That should take you to 1.0, I believe. You may need to find an official OTA update for Cupcake to flash as well, you may not.
[email protected] said:
You obviously did not search Google correctly.
Al you'll really need is to find the DREAIMG.nbh file for RC29, and use fastboot to flash it over. That should take you to 1.0, I believe. You may need to find an official OTA update for Cupcake to flash as well, you may not.
Click to expand...
Click to collapse
Just getting it back to 1.0 is fine. All the OP would have to say is he never wanted to get the updates.
Here is the factory cupcake build you can use. http://androidoverdrive.com/viewtopic.php?f=11&t=85
So if I unrooted using the DREAIMG.nbh procedure 48 hours ago, how long do I have to wait for the OTA upgrade to bring me current? Is there anything I can do to hurry it along? For example, will it not come through if certain apps are being used, etc? Or do I just ... wait longer?
ummm, Rogers doesn't have OTA updates. Just get the e911 update thing from rogers and run that. It will unroot you and put you to the latest rom.
FYI you can now say good bye to root as the new phone that you get from rogers will not allow root.
I feel for you as I am in the same stupid F'N sinking boat. F Rogers.
ravencore17:
I will not scold you for not reading enough or reading correctly. I have been reading this site, others, and searching for 3 months to get to the point where I am now. There are thousands of posts and it is often difficult to piece it all together and sort the wheat from the chaff.
I can offer what I have found.
1.
http://forum.xda-developers.com/showthread.php?t=534464
I thought this post might be helpful since it offers a stock rogers rom, but it says 32A, so I don't konw if that will work with the Dream.
2.
http://forum.xda-developers.com/showthread.php?p=5486789
This thread has a link to:
"
http://haykuro.polygonize.com/ROGERSDREAM.nbh.zip
"
This seems cool, but i can't find an md5sum for it, so there seems to be no way to verify the download. It would be a shame to brick the phone with a bad download.
I wonder if anyone has used it successfully and has a checksum?
Maybe [email protected] could help us?
3.
http://forum.xda-developers.com/showthread.php?t=544654
has this:
"
Regardless, heres the original radio (3.22.20.17) and the original recovery (WARNING: UNROOTED) from rogers dream:
http://www.stevebirstok.com/android/losemyroot.zip
"
but again, I cannot find and md5sum for the file, so I am a bit hesitant to use it if a brick could result.
I think suggestion #2 would be great if there was a checksum for the file.
I would keep a copy of it handy as well if I could verify it.
David
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
I just ended up purchasing a Nexus One from someone on craigslist and it turns out this phone has never been rooted. Was running GingerBread 2.3.4 OTA, I checked the mainversion it was 1.01.1700.1 (or something to that extent).
I downloaded a PASSIMG that had this mainversion, flashed it and now Im set all the way back to ERD79 (the original Nexus one Eclair).
I want to root this without unlocking the booloader, and keeping the MAIN VERSION intact. I am aware of the "Rageagainstthecage" method but I need FROYO. Is there a Froyo update that I can flash to this device (using UPDATE.zip) that wont screw around with the MAIN VERSION.
I think FRF91 is my best bet? Am I correct? Where can I find a trustable source for the FRF91 (or any other Froyo update). Note I am coming from ERD79 so it has to be able to take the update.
Once I get to FROYO (without touching the main version), I can take it from there with respect to the rooting and loading custom roms.
My original Nexus one is at 2.16.1700.1 which doesn't allow me to go all the way back to ERD79. The reason why I want to keep the main version untouched is so that I can easily load any PASSIMG.zip file.
Thanks for all the help/
c
anything at all, come one someone's gotta know?
I think if you can get Gingerbread on it ( older than 2.3.4 ) you can user Gingerbreak to root it without unlocking the bootloader:
http://forum.xda-developers.com/showthread.php?t=1044765
For pre-Gingerbread version I think you can user SuperOneClick:
http://forum.xda-developers.com/showthread.php?t=803682
There is no reason to do it, that's why you are not getting many responses - there is a passimg file that works on any main ver, and that's all you need...
danger-rat said:
There is no reason to do it, that's why you are not getting many responses - there is a passimg file that works on any main ver, and that's all you need...
Click to expand...
Click to collapse
And if you bought the phone secondhand, the warranty is probably expired, and there is no reason to not unlock the bootloader.
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
Hello, first off, I'm new to the android OS, especially flashing ROMs. I did however have some prior experience in flashing other mobiles such as the Symbian platform on my previous Nokia phones.
I would like to try the new Firmware XXLA1 as of now Im using an OTA update kernel version of 2.6.35.7-N7000DXKL3[email protected]#2.
Btw, im from the Philippines and I bought this handset on this country.
So going back to my question, what are the repercussions and implications if I flash the LA1 official ROM from Samsung knowing that its a ROM for "Open Europe"?
if your phone is unlocked (No carrier restriction) you can flash any Stock ROM
Yes, i bought it unlocked. Will the app availability in the market change?
Also, since its an official ROM, would it break my warranty?
I Live in Indonesia, yes samsung Indonesia say it will break our warranty but you can flash it back to KL3 whenever you want to claim it..
Bump. I would also like to know of any important differences between stock roms if any. I live in the US and will be getting my Note in the next day or so and think I will root it but keep it stock and just uninstall any bloatware I deem unnecessary.
I recommend using it for a week before you try any (potentially) warranty breaking mods on it. Get used to it. learn how things work. Then when you start modding you will have a far better idea if the mod has broken something or not.
You can generally flash a ROM from any region, as long as you understand the language. You can flash RADIO seperately, and you would choose one that will work well with your local provider. Lastly, you can manually set the APN settings to lock onto your chosen provider.
Be aware that some new devices have a "binary counter" which will sometimes increase when you flash something. Your warranty may be affected. Spend time reading the forums learning about the issues before you flash.
Thanks! Sounds like a plan
leihuwan said:
Hello, first off, I'm new to the android OS, especially flashing ROMs. I did however have some prior experience in flashing other mobiles such as the Symbian platform on my previous Nokia phones.
I would like to try the new Firmware XXLA1 as of now Im using an OTA update kernel version of 2.6.35.7-N7000DXKL3[email protected]#2.
Btw, im from the Philippines and I bought this handset on this country.
So going back to my question, what are the repercussions and implications if I flash the LA1 official ROM from Samsung knowing that its a ROM for "Open Europe"?
Click to expand...
Click to collapse
Looking at the kernel version you have, it is safe to assume that we possess the same unit, and yes we have the same roots (oy, kapatid!) as well.
I started rooting my unit after a few weeks of getting familiar with it. Don't worry too much, since i was able to successfully flash root my unit and install CWM (clockworkmod), using the zergrush exploit.
Once CWM was installed, the 1st thing i did was a nandroid backup, just to keep a backup on my stock settings.
After that, i tried flashing custom ROMs, and it worked flawlessly, albeit with bugs. Just follow the steps outlined on each ROM thread and you should do fine.
Managed to encounter boot loops, phone not booting up, etc., but nothing too critical that made my unit useless.
As for your question, the obvious implication is that by flashing custom ROMs, you void your warranty. So, unless you have qualms in losing your warranty, then go ahead and flash a custom ROM.