yashsingh1/xdaforums huggingface dataset:
[Nexus One General] Vaniuk:
Problem with update

Hi All,

I have some problem with OTA update from 2.2 to 2.2.1

I rooted my Nexus One with Universal Androot. When I got OTA Update for 2.2.1, then I made unRoot operation and I made System Update operation. But after Automatic Reboot, when system update files was copied, process was aborted and picked up Android Icon with "!".

Then I puuled up battery and powered on phone. Everything was good, but System version was 2.2 again. After 5 minutes I've got OTA update again and process was repeated.

So, I made Recover operation, but process was aborted and picked up Android Icon with "!" again.

Please help
[Nexus One General] BlindWolf8:
Hi all,

I got Part 1 of the FRG83D update, (still listed as FRG83 afterwards in About Phone) but Part 2 never came. I then updated to FRG83D from here: h ttp://android.clients.google.com/packages/ota/passion/ecb21b752065.signed-passion-FRG83D-from-FRG83.ecb21b75.zip (new user so I can't post a real link yet)

I then updated hboot from the attachment in this thread. According to some people, Part 1 was supposed to contain the hboot update, but after updating to Part 1 and then FRG83D, I still had version 0.33 of hboot. I have no idea what's going on or if I even needed hboot, but I'm on 0.35 now.

My wifi seems decent.

I got my Nexus One near the release date so I have an AMOLED screen. I'm not sure if this matters or not about not getting hboot 0.35 as other people have mentioned it includes updates for the LCD version of the Nexus One.

For people wondering, your hboot version is at the top of the screen that comes up when you boot your Nexus One by holding down the trackball and Power buttons.

Oh, and Swype must be reinstalled after upgrading.
[Nexus One General] nexus-six:
Anybody else tested this?

I downloaded the update.zip from earlier in the thread and successfully upgraded to FRG83D but my HBOOT is still 0.33
[Nexus One General] kikikaka:
So after this round of OTA to frg83d, all N1 will be assumed having hboot 0.35?

I just concern next time OTA may fail again bcoz the version unsync if gingerbread comes later...
[Nexus One General] Scarygore:
I have downloaded, renamed and installed this after manually upgrading to 83d. My h-boot went from 33 to 35. My thanks to efrant for posting.

Next on the blasphemy channel, celebrity gonad waggling, live from Canterbury Cathedral.
[Nexus One General] Pyrazol:
Just prior to the FRG83D update, I flashed FRG83 from developer.htc.com, then installed the FRG83D update, which went through fine - but I'm also still on Hboot 0.33.0012.

Is the 0.35 Hboot actually needed?
[Nexus One General] efrant:
It's not needed for the time being, but the speculation is that the newer HBOOT was rolled out to all Nexus One's as it is likely a requirement for Gingerbread.
[Nexus One General] danger-rat:
All the 35 hboot seems to do at the moment is prevent using the passimg method to restore images (meaning you have to unlock the bootloader and use fastboot, or root and use a custom recovery.

Edit:

I've also seen problems installing Amon Ra via fastboot with hboot 35. Not sure if it's indicative yet...
[Nexus One General] zer0day:
Is it possible to apply this via fastboot. I fubar'ed my sd card and haven't got a spare.

I tried fastboot flash hboot hboot-new.zip

I get:

Sending 'hboot' (380 KB)... OKAY

Writing 'hboot'... INFOsignature checking...

FAILED (remote: signature verify fail)

Edit:

I extracted the img file and tried again, I get "remote not allowed" error
[Nexus One General] Vaniuk:
Error with Update

Hi All,

I have some problems with Update and System Recovery. I received OTA update, I press to Install this update and after Reboot process of the coping files was stopped with "!". Then I pressed on Volume up and Power button and there was some text like this:

Finding update package...

Opening update package...

Verifying update package...

Installing update...

Verifying current system...

assert failed: apply_patch_check ("/system/framework/javax.obex.jar" . "2eba57207c48e714d2642237a4649502b521be69" . "a14691ea37cc164fdef6914bbe23cb826ddaf82b")

E:Error in /cache/7957af1a7018.signed-passion-FRG83D-from-FRF91.7957af1a.zip

(Status 7)

Installation aborted.

After that I can't recovery System too. Please help...
[Nexus One General] efrant:
If you are using fastboot, you can only flash images. Just extract the image from the zip file and flash it.

As well, I believe the command is fastboot flash misc hboot.img if I'm not mistaken, but you should verify the name of the partition.
[Nexus One General] danger-rat:
I thought you had to flash via adb.

Fastboot requires you to be booted into the bootloader, I can't see you being able to overwrite the bootloader while you are using it?

Rename the file to mtd0.img

Place in tools folder with flash_image file

adb push flash_image /data/flash_image adb push mtd0.img /data/mtd0.img

adb shell

chmod 755 /data/flash_image /data/flash_image misc /data/mtd0.img
[Nexus One General] efrant:
You're confusing things. If his bootloader is unlocked, he should follow my directions.
[Nexus One General] danger-rat:
Sorry...
[Nexus One General] mrbkkt1:
I was thinking it was a special update.... but my friends mytouch 3g has the exact sane update. Lol.
[Nexus One General] crabnebula:
Exact same problem here. I was running stock rooted FRG83 (with stock recovery) and received the OTA which failed with this error. I tried reverting to fully unrooted FRG83 (still no luck) and also tried flashing the manually downloaded update.zip with ClockworkMod recovery. I always get the same error.

Anyone have any ideas ?
[Nexus One General] nexus-six:
So no benefits to HBOOT 0.35?
[Nexus One General] efrant:
For the time being, it doesn't seem that there is any benefit to installing HBOOT 0.35. However, having HBOOT 0.35 installed on your device is likely a prerequisite to Gingerbread installing on your device.
[Nexus One General] GldRush98:
Doubt that.
[Nexus One General] efrant:
You could very well be correct. I was just going by what the OTA notification on my device said. Something about it being required to receive future updates or something like that.
[Nexus One General] bighulk666:
For the ones getting Status 7 errors try this zip out. I flashed it and now i'm on FRG83D. I did lose root, but i used suberboot's bat file to regain root, with NO issues.

http://xdaforums.com/showpost.php?p=9414781&postcount=70
[Nexus One General] efrant:
See the screen shots here. Specifically says that that the new HBOOT is required to receive new Android system software:

http://xdaforums.com/showpost.php?p=9429091&postcount=73
[Nexus One General] nexus-six:
Where does it say that?

Since most people flashed Part 2 without Part 1, I doubt you need it.
[Nexus One General] efrant:
See the second screen shot. I wasn't implying that Part 1 was needed before Part 2, I was suggesting that Part 1 will likely (but not certainly) be needed for Gingerbread...
[Nexus One General] ralphdavidvdb:
it gives "verification failed" on my nexus.

Got frf91 and stock recovery, unlocked and rooted.
[Nexus One General] avgjoemomma:
Anyone figure the problems with installing Part 2 yet? I'm stock with 2.2.1. The first part of the update worked for me as the bootloader version is .35 but I cannot for the life of me get the second update to work. I've tried using the links here but after I boot into recovery I just get the Android and exclamation point:confused:
[Nexus One General] efrant:
Try this:

1) Download this to the root of your sdcard: http://android.clients.google.com/p...signed-passion-FRG83D-from-FRG83.ecb21b75.zip

2) Rename the file to update.zip

3) Boot into recovery: you should see the Android and the exclamation point.

4) Push the volume up and power buttons simultaneously. (You may have to do it a few times before it actually works.)

5) Select the option to flash the update.

6) Reboot and let us know if that worked for you.

7) You will lose root, so use either SuperOneClick or root it manually using rageagainstthecage (see my signature).

8) Add a signature to your XDA profile so that we all know what you have, and it makes it easier to trouble-shoot. :)
[Nexus One General] kishandr:
Thx efrant. Your post helped me update.

If i may ask did your update to hboot .35??

I initially update my nexus one to frg83d manually and then after reading this thread i updated hboot to version of .35.

Did i do something wrong?

Thx for you advice.
[Nexus One General] efrant:
No, I did not update my HBOOT to 0.35. I'm still on 0.33 (see my signature - I keep that up to date). I don't really know what the 0.35 is for, other than possibly being a requirement for Gingerbread. If needed, I will update when Gingerbread comes out. Otherwise, I see no reason to flash it. Unless you can tell me otherwise.
[Nexus One General] Rusty!:
Removed any system apps?
[Nexus One General] avgjoemomma:
Thanks, efrant! That did the trick :D
[Nexus One General] gotunandan:
I applied the above update.zip as well but I have run into a problem. The phone is stuck at the Nexus "X" sign at boot and will not go further.

The phone is running rooted FRG83 with ClockworkMod recovery and a locked bootloader which was hboot 33.

I ended up using the above update.zip since the original update.zip (from FRG83 to FRG83D) gave me verification errors at a file named "/system/framework/am.jar" ( I think that was the name of the file !)

I really hope my phone isnt bricked.... :confused: :(
[Nexus One General] efrant:
I doubt your phone is bricked. You can still boot into recovery, correct? If so, then no worries.

Maybe download a full image from here: http://developer.htc.com/ (like this one: http://dl4.htc.com/RomCode/Source_and_Binaries/signed-passion-img-FRG83_0923.zip and rename it to PASSIMG.zip and place it in the root of your sdcard. Boot into into recovery and flash that, then try updating to FRG83D.
[Nexus One General] gotunandan:
Ermm... booting into recovery by pressing the "power button" and "volume up" button just after the phone starts ?

I am not sure whether or not that occurs either :(

When the phone starts, it vibrates (for half a second I guess ?) and the Nexus X shows up and nothing else seems to happen.

I guess I should try the recovery procedure again ? What about going into the bootloader ?
[Nexus One General] efrant:
That is NOT how you boot into recovery.

Turn the phone off. Hold the trackball down and push the power button. The bootloader will appear. Then, make sure bootloader is highlighted (in blue) and press the powert button. Then use the volume up/down keys to select "Recovery" and press the power button again. Now you are in recovery.
[Nexus One General] gotunandan:
Oh !

Thanks for that bit of info :)

Now I am downloading that system image you mentioned from the HTC dev site.

So I should rename it to PASSIMG.zip and place it in the root of the sdcard.

I read somewhere that naming it to PASSIMG.zip allows the bootloader (which is HBOOT 0.33) to apply the update itself ?

Or should I rename it to update.zip (or keep it as PASSIMG.zip) and use ClockworkMod recovery to apply it ?

Sorry, kinda confused.

I had no trouble getting CM6 onto this back in September and now I am getting my head in a mess trying to apply a stock update :(

Thanks a lot for all your help :)
[Nexus One General] efrant:
Try both ways: Rename it to PASSIMG.zip and see if the bootloader will pick it up. If that doesn't work, rename it to update.zip and flash via recovery.

P.S. When you tried updating initially, I hope you weren't trying to apply the stock update to CM6. It doesn't work. Stock updates are for stock ROMs... ONLY. Even stock that are deodexed will not work. Neither will ASOP ROMs (like CM6).
[Nexus One General] gotunandan:
No I did not apply it over CM6.

I had CM6 (Kang-o-rama) initially but I had FRG33 as a nandroid backup. I backed up Kang-o-rama 2 days ago and flashed back FRG33 to go to FRG83 and FRG83D eventually.

I think its best if I mention the progression of this "stock" version.

Sorry, it might sound like a bit of a drag, but hopefully that will make things clearer !!!

Until FRF91 I was running everything as Stock. When the Universal Androot (1-click) came about, I used it to root FRF91. Then I installed ROM Manager and ClockworkMod recovery.

When the FRG33 ROM was leaked I actually decided to upgrade to it using the Modaco repack from here:

android DOT modaco DOT com/content/google-nexus-one-nexusone-modaco-com/317147/03-sep-frg33-build-info-and-repacks-stock-rooted-deodexed/

and I used the repack mentioned on there in bold (Rooted / deodexed / busybox / trackball alert / FRF91 fingerprint with radio update zip download)

This gave me the new radio (5.08.00.04) as well as a deodexed ROM (according to the description of the repack).

After this I made a Nandroid backup of this and started using CM6 via the Kang-o-Rama Rom until two days ago, when I backed up Kang-o-Rama and flashed back FRG33.

Then to update to FRG83, I again used Modaco's repacks from here:

android DOT modaco DOT com/content/google-nexus-one-nexusone-modaco-com/319064/05-oct-frg83-build-info-and-repacks-stock-rooted-deodexed/

But this time, I did not need the radio so I chose the other one: Rooted without radio update zip download:

This does _not_ mention "deodexed" FRG83 ROM but I was able to flash it over my earlier "deodexed FRG33".

After this I chose the vanilla update (FRG83 to FRG83D) from google. On applying this update the verification failed.

So I tried the modified version mentioned a few posts back.

That lead me to being stuck at the booting at the Nexus "X" . Not the animated "X" just the plain "X" that shows up as you power up.

So I guess, its best that I do not flash this update. But I am now wondering whether I should flash the FRG83 build I downloaded from HTC dev either ?

Since there could be a chance that the incompatibility could again be caused by the Deodexed ROM issue !

Thanks for your help ( and even for reading this sad story above ! )
[Nexus One General] efrant:
I would flash the file form the htc site mentioned above by renaming it to PASSIMG.zip and letting the bootloader flash it if it can. That should clear up everything for you. Then apply the FRG83D from FRG83 update via the stock recovery.

In the process, you will lose root, but you can re-root and re-flash a different recovery once you are comfortably on FRG83D.
[Nexus One General] gotunandan:
Hmm... I did just that, downloaded the "signed-passion-img-FRG83_0923.zip" from the HTC dev site copied it over to the root of the sdcard and renamed it to PASSIMG.zip

The bootloader recognized it and applied it.

But, it did not reboot on its own or do anything else after finishing. So I chose recovery where, I still had ClockworkMod. So I rebooted from there and I am back again to the immovable "X"

Should I reboot from the bootloader itself then ? I think I missed that :|

P.S. As I was typing this post, the phone restarted on its own, I had just kept it aside. And now its back at the immovable "X" and not doing anything
[Nexus One General] efrant:
Hmm. Not sure. Reboot into ClockworkMod, clear all your caches, then go back to the bootloader and flash the PASSIMG.zip again. Let it complete the process. If it says complete, but it does not reboot, then just reboot normally into the ROM (not the bootloader, not recovery). Then wait at least 15 mins before doing anything. (It may take a long time for the first boot.)
[Nexus One General] gotunandan:
Nah, That does not seem to help. It stays on the immovable "X" for about 10 mins (I checked the time) and then reboots itself and after that comes back to the same position. It is continuously does this in loops I guess !

I cleared the cache through ClockworkMod and applied the PASSIMG.zip via the bootloader but the above continues.
[Nexus One General] efrant:
Well dude, I'm sorry, but I'm all out of ideas. Maybe someone else more knowledgeable can chime in. The only other thing that I can think of is to unlock your bootloader and flash using fastboot while plugged into your computer
[Nexus One General] gotunandan:
Well actually since I had the Kang-o-rama Nandroid backup from a couple of days ago, I just restored that back on.

I think from now on, I'd best give stock OTAs a skip and just take the repacked ones from all the fine folks here and at Modaco !

Unfortunately I did not make a Nandroid backup of FRG83 which was running fine after upgrading from FRG33 using Modaco's repacks. I do have a Nandroid backup of FRG33, so maybe I can start from there again and at least goto FRG83 which worked.

Sorry about all time spent, since we could not come to a working solution afterall :(

I guess the whole messy soup of rooted deodexed Roms with a custom recovery against a stock update just wasnt right :p

My initial scare (about getting the phone bricked) was because, I thought, I had lost ClockworkMod recovery as well and therefore I would not be able to restore earlier Nandroid backups either. Thankfully that was not the case. :o

Thanks a lot for sticking up with me and helping :)

P.S. Time to change my sig I guess ;)
[Nexus One General] danger-rat:
You're on the right track.

Try the FRG33 stock instead of FRG83 (83 doesn't like the PASSIMG method, for some reason)

http://www.mediafire.com/?dxwh5l4b5ygh6nf
[Nexus One General] gotunandan:
Actually, after yesterday incident I am a little hesitant about flashing stock images. Dont want to lose root access (along with custom recovery) and be unable to get it back.

And as all of you have mentioned, I know that it is possible with rageagainstthecage but I prefer to wait, especially now that I am doing ok with kang-o-rama (based on CM6) on the phone !
[Nexus One General] kkiran:
I just got my Nexus replaced. It had stock 2.2 and then FRG83D came along. All I want to do is get my nandroid image back on (Cyanogen 6.1). So I have to root my Nexus One.

I am looking for an all online solution - just feeling adventurous, not that I don't have microsd card reader or ADB setup!

I tried your FRG33 passimg.zip but it says Main version is older! Update Fail! Any other leads?

Once I am on a lower firmware, I can then use VISIONary for rooting on the phone. Sounds good?
[Nexus One General] SoberGuy:
You can root 83D pretty easily with the SuperOneClick, if you don't want to manually do all the ADB stuff yourself.
[Nexus One General] kkiran:
I have a Mac and I and I am at work. I thought an 'all online' version exists already! VISIONary seems to be a good solution for < FRG83D but not 83D. Any other ideas?
[Nexus One General] SoberGuy:
Doesn't SuperOneClick work on a Mac? I don't think there is an "all online" method for 83D. Suck it up for the day, find out if SuperOneClick works on a Mac (and I really want to say it does!) or do some research on the manual method via ADB and rage. Couple hours ain't gonna killa ya.
[Nexus One General] kkiran:
Mac ain't on the list cos' that solution is married to .Net! I feel so powerful with my Nexus One that I try my best to do everything from/within/on the phone without swapping batteries/memory cards and all that stuff!

If nothing else works, then yeah ADB it is! I wanted to downgrade to lower FR* version adn then use VISIONary but seems like its a no go right now.
[Nexus One General] SoberGuy:
I forgot about .net, you're right. You can't downgrade without rooting, that I'm aware of. Enjoy adb!

Sent from my Sexy Nexy, courtesy of the fine developers of Tapatalk
[Nexus One General] kkiran:
Awesome, thanks for clarifying! I hope I can do it on my work computer which is a Linux machine. Installing mono just for this sucks though! Cheers!
[Nexus One General] efrant:
Why not just follow this (it won't take you more than 20 mins...): http://xdaforums.com/showpost.php?p=8315805&postcount=2
[Nexus One General] kkiran:
That is what I may eventually follow. Just looking for a quicker, efficient way which doesn't involve a Mac/PC! Thanks for the link!
[Nexus One General] realme_RMX3231:
I've unzipped to this file myself, nothing here
[Streak 5 General] jay slasher:
So it appears I may have botched a step. I think I went straight from 2.1 to 2.2 v1.3 rather than updating to 1.1.1

As it stands the Streak turns on and gets stuck on the Dell Logo.

Anyone know how I can fix this. is it as simple as installing installing the 1.1.1 package in recovery mode. Or have I completely screwed something up.

Any help would be really appreciated... :(
[Streak 5 General] lufc:
Hi could you please ask in Steve's 2.2 thread about this problem rather than starting threads otherwise the board will be full of questions that can be answered just as well in the right thread thanks
[XPERIA X10 General] nexo08:
Hi Guys

i have a question it is possiple to port wm7 to x10?

or givs there any roms??

PS: sorry for my bad english =(
[XPERIA X10 General] Straf:
We can't either upgrade android version (maybe we can but not in 'full mode') and web should be able to port Wm7 (that couldn't either be ported yet to HD2) to our X10's?

Obviously no, we cant, and moreover, i think we will never can
[XPERIA X10 General] losty-1H:
x10i is a bad phone
[XPERIA X10 General] Kondzioz:
Do you think so? ok your opinion. Im proud as a hell of my x10.

Regarding the question:

Maybe one day it might be possible, but i wouldnt be sure. eg. iphone is in progress of transcription to android, so maybe android will be transcripted to wm7, why not?
[XPERIA X10 General] nexo08:
I trink olso the x10 is an amazing phone :)

and Android 2.1 olso amazing but i think wm7 is from the designe better

and i would buy no wm7 Mobile because they look all agly

I hob that there were any devoper That make that possiple :)
[XPERIA X10 General] Tjotte:
The only thing tempting with wp7 for me is the xbox integration, would love to have that!
[XPERIA X10 General] kindred7:
prolly the closest your gonna get

http://xdaforums.com/showthread.php?t=781455
[XPERIA X10 General] chaurjyh:
i would think we might have a chance at porting wm7 to x10 when x7 is released and we have the rom for the x7... that would be ur best bet...
[XPERIA X10 General] alankstiyo:
that'd be great but wonder if its possible
[XPERIA X10 General] saltorio:
Until the bootloader is cracked (allowing us to install whatever ROMs we wish), it's pretty-much impossible we'd ever see any way of installing an alternate OS. Once the bootloader is cracked, if someone were to put forth the effort to port the OS and get things working, technically it should be possible.

My question though is: why?

I'm personally not convinced WP7 is worth anyone's time, especially since it's as closed as iOS. Mind as well get an iPhone.
[XPERIA X10 General] NightSidew1nd3r:
Wp7 has minimum specs that x10 does not meet. It requires 512 MB ram
[XPERIA X10 General] hemo1001:
i will never ever back to windows even if i had a chance to.

i used almost all of windows versions and they all sucks and lags alot and have many bugs ... unlike android.

that my opinuin
[Epic 4G General] dfe002:
I was wondering if it was possible to use the epic to view pictures from an external usb drive. I know id need to make an adapter to make it work, but after that could I use astro to view the files? I'm running froyo if that makes a difference
[HD2 Windows Mobile 6.5 Q&A, Help & Troubleshooting] XDAGH0ST:
First Sry for my bad English i have one problem since i installed Core Cell v7.

I have the Core Cell Bootlogo in every Rom i flashed! I flash artemis,Dutty and much more, i still have the Core Boot Screen Splash! I install cab`S with new boot screens but i dont work i do a task 28 format, Hard Resets noting works =( any Ideas?

Mfg and thanks
[Hero CDMA Q&A, Help & Troubleshooting] Bierce22:
Hey I was wandering I decided to flash ras recovery 1.62 instead of clockworkmods and I must say ras layout is much better however when I went to choose zip from SD none of my roms were there it was just the rootme.zip file I used to root and the original 2.1 Sprint ruu do I have to download everything again to this recovery or what
[Hero CDMA Q&A, Help & Troubleshooting] churchwin88:
Do you have them saved in a folder on your SD card?

Amon Ra will only see the root of your SD card. If they are in a folder just move them to the root of your SD card where the rootme.zip and 2.1 RUU are.