yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] Iggy82:
Yup, my mistake, multi-colour trackball is working. I got confused because old version of Blink! would show trackball colour with screen on, in current version, you have to set the test up then turn off screen to see it working.

All working fine now, just used the black bar patch. The page said I should install stockbar first but this was an entire ROM! Working fine by simply installed with AmonRA recovery.

I'm so pleased, I now have my phone exactly as I wanted it!
[Nexus One Android Development] RunTimeWorld:
Best ROM ever

Been on 50% battery status after 3 days intensive usage. Never had such a solid ROM.

Thank you for the work of rooting etc.
[Nexus One Android Development] ultra99:
any patch for arabic support?
[Nexus One Android Development] supercopter:
Damn ! I shouldn't have updated to the latest ClockworkMod before flashing this ROM !

ClockworkMod v.3.0.0.5 says it can't install this ROM because of some update script that has been removed for Honeycomb compatibility issues...

:mad:

Edit: How can I be so unlucky with this ROM ?

After going back to ClockworkMod v.2.5.1.4 the flash seems to start OK but after a few minutes...

:mad: again !

Any clues on why this is happening ? I'm trying to flash the "Stock, with no modifications but root" one.

Can someone with a working ROM post the MD5 cheksum... Maybe my downloaded ROM is corrupted...

Thanks in advance for any help on this !
[Nexus One Android Development] ZetaTre:
I've tried to flash the stock (first link) using Clockwork and I get this meassage:

"Amend scripting (update-script) is no longer supported. Amend scripting was deprecated by Google in Android 1.5. It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread based recovery., Please switch to Edify scripting (update-script and update-binary) to create working update zip packages"

Then the flash is aborted... Any way you could fix it?

EDIT: solved that problem by switching to ClockworkMod 2.5.1.4. Now other problem: when I flash it aborts abain while copying files in the System partition. The error is: "E:Board does not support mtd utils.E:Failere at line 76: write_raw_image PACKAGE:boot.img BOOT:"
[Nexus One Android Development] dsixda:
To solve these issues you'll need to convert the update-script (Amend) to an updater-script (Edify). Sorry guys, didn't realize the technology would be progressing this fast ;-)

This conversion can be done automatically with my kitchen:

Just add this ROM to the kitchen and then build it. While building it will ask you if you want to convert the script to updater-script format. That's it.

EDIT: Another method is to use an older ClockworkMod recovery image or switch to an Amon_RA recovery.
[Nexus One Android Development] ultra99:
hey dsixda great rom! any news on Arabic support (for connecting letters)?
[Nexus One Android Development] dsixda:
Thanks. Keep in mind, however, this is not a real 'custom ROM' ;) All i wanted was to give users a stock 2.2.2 which will hopefully allow them to have the capability to eventually upgrade to the next OTA update. I never claim to be a ROM cooker, nor am I doing any real updates to this ROM, nor do I know how to do the stuff you asked for. :-)

Leave it to the REAL developers in this forum ;-)
[Nexus One Android Development] RunTimeWorld:
Respect to such a statement. I couldn't agree more with you.
[Nexus One Android Development] supercopter:
Reverting back to ClockworkMod 2.5.1.1 also solves the problem and allows flashing your ROM. Thanks for it !
[Nexus One Android Development] RunTimeWorld:
Why don't u use Amon_RA custom recovery? It has more features, is user friendly and never gave any problem whatsoever, while CWM always has some issues.
[Nexus One Android Development] supercopter:
Simply because ROM Manager is the perfect tool for newbies and it seemed logical to install the Recovery made by the same dev...

Anyway, regarding those annoying issues with CWM, I may give RA_Recovery a try quite soon ;-)
[Nexus One Android Development] Silverexp:
FYI... Issue was new defective SD card. Reverted back to old ADATA 16GB class 6 and all is fine now. Just had to slim down my music & movie collection... :(
[Nexus One Android Development] ZetaTre:
I figured it, so I rolled back to an earlier version of ClockworkMod and solved that specific issue. I still get the other error: when I flash it aborts abain while copying files in the System partition. The error is: "E:Board does not support mtd utils.E:Failere at line 76: write_raw_image PACKAGE:boot.img BOOT:"
[Nexus One Android Development] dsixda:
You'll need to convert it to an updater-script then, with my kitchen. That recovery image of yours does not recognize the boot partition without mounting it to a folder.

OR simply use Amon_RA recovery image with the existing update-script.
[Nexus One Android Development] ZetaTre:
Thanks so much for your help!!! I've installed Amon_RA and it worked perfectly!!!! Now I'm back to complete stock
[Nexus One Android Development] machina77:
Thank you very much, used the first link - stock rooted, fantastic :-)
[Nexus One Android Development] Turbocom:
I've noticed with this ROM the haptic feedback will suddenly stop working and will ocassionaly start again.
[Nexus One Android Development] y2jamit:
Fabulous stock rom with some nice additions :) Can anyone confirm if Trackball Alert Pro works or not? When I try to patch from TBA it tells me that the rom is not recognised. I have set up alerts for various things. Somehow my alerts for SMS using Handcent are working fine but not sure about others. Gmail alert doesn't work and I am getting a white color instead of the green one which I had set.
[Nexus One Android Development] RunTimeWorld:
it works with the smali patch for 2.2 devices
[Nexus One Android Development] dsixda:
I have updated Post #1 with a download link for the stock ROM with updater-script (compatible with latest Clockwork Recovery which only supports 'Edify' scripts).
[Nexus One Android Development] GldRush98:
Are you planning on putting out a 100% stock but rooted Gingerbread when we get ahold of that soon?
[Nexus One Android Development] dsixda:
If you guys feel these stock updates help you, then, sure. I will try when I have time.
[Nexus One Android Development] efrant:
Just a clarification to the first post: you do not NEED a stock recovery to receive/install OTA updates.

Amon_RA v1.9 and higher WILL work with no issues whatsoever (Amon_RA 1.9 has signature verification set to OFF by default, and in the later versions, you can switch it to off).

I believe that the latest CWM has the ability to turn off signature verification, but I have never used it.

As well, just to clear up some confusion I've seen in other threads: as long as you are using a stock ROM (like dsixda's), whether you have root or not makes NO difference - you can still receive/install OTA updates...
[Nexus One Android Development] Budius:
Efrant ....

Is that verification on amon_RA should be on or off to work? Or it doesn't matter?
[Nexus One Android Development] efrant:
It should be OFF...
[Nexus One Android Development] Budius:
.... thanks!!

I'm downloading this now.
[Nexus One Android Development] GldRush98:
The only snag is when you delete or change files in the rom (like removing Amazon MP3). This will cause OTA's to fail in splendid glory.
[Nexus One Android Development] efrant:
Yeah, if you starting deleting files from the /system partition, or make other modifications like, de-odexing the ROM, updates will not work, regardless of the recovery you have. You need a stock ROM, with all the stock files in /system partition, and odexed. Root is irrelevant.
[Nexus One Android Development] dsixda:
Thanks, yes I was aware of this but for some reason I could never get this to work, probably because it was always defaulted to signature verification ON, even if I changed it to OFF in a previous session. Maybe I need to update my recovery.

And yes, like I said in the original post, you can flash the first two 'stock + rooted' ROMs but the rest cannot be used for OTA, because the original files in the system partition have been modified (deodexed, etc.).
[Nexus One Android Development] Budius:
installed fine, totally stock + SU

but even thou SU toast clearly states that Permission was granted Titanium insist telling me that he doesn't have permissions... I just want to reinstall my backedup apps....

any ideas why this would be happening ??
[Nexus One Android Development] efrant:
Maybe something is wrong with your busybox installation.
[Nexus One Android Development] dsixda:
That's correct, it's only rooted and doesn't have busybox.

Press the Problems button to get busybox, as they said in the app..
[Nexus One Android Development] Budius:
I though TB would say it does have SU permission but doesn't have busybox in case that was the problem....

that's it... thanks!
[Nexus One Android Development] y2jamit:
Thanks for replying mate. I tried this option and got a message " An error occured - File failed md5 check after copy". I guess I need to take this matter to the official TBA thread.
[Nexus One Android Development] lockab:
Can someone verify this, during froyo OTA update a security patch was sent out which unrooted phones. I used one click root successfully, now wonder if 2.3.3 update which do the same and unroot my phone if I install this rom. Can someone please advise me on this matter before I accept the OTA update when it arrives.

Thanks in advance
[Nexus One Android Development] rich1984:
does the hboot version matter??
[Nexus One Android Development] Dirk:
The OTA will most likely unroot your phone. Whether or not SOC or any other method will work on the updated ROM is yet to be seen.
[Nexus One Android Development] siddharthsai:
I still don't understand how *#*#CHECKIN#*#* works. When I do that, it just shows checkin succeeded and an exclamation! Is this how its supposed to work?
[Nexus One Android Development] Dirk:
Yes. If there were an update available it would start downloading, although you wouldn't necessarily notice until going into Settings/About Phone/System Updates.
[Nexus One Android Development] siddharthsai:
Great, thanks
[Nexus One Android Development] sirgoob:
Once the OTA is sent out, if your phone is rooted, it will download and a notification will let you know its ready to install. The update won't work, you'll have to manually update it.

Sent from my Nexus One
[Nexus One Android Development] siddharthsai:
Damn bad luck then.. im on edge.. no affordable 3G in India yet.

looks like this-

Any thoughts?
[Nexus One Android Development] efrant:
Not true. Works just fine.

The ragaeagainstthecage exploit that (the earlier versions of) SOC uses should certainly work, as it is an exploit in how ADB connects to your device. Don't think they can patch that easily at all...
[Nexus One Android Development] siddharthsai:
Okay
[Nexus One Android Development] Geo411m:
can you post the stock/unrooted frg83g file? I need the file to apply the new gingerbread update. Thanks in advance.
[Nexus One Android Development] dsixda:
My 'rooting' modified the default.prop in the boot.img. If I change them back, and then flash it, and then apply the Gingerbread update, I still get errors for the BOOT partition. Probably because it's not exactly the original boot.img, as it's been modified over and over.

I'll get this resolved ASAP.
[Nexus One Android Development] dsixda:
OK, I've used an unmodified boot.img and I was able to update to Gingerbread successfully! Updated first post.
[Nexus One Android Development] arkavat:
thanks!

but were you able to get root after gingerbread? if yes, how?

thanks in advance
[Nexus One Android Development] gcng:
flashing this su.zip which i got from another post by netzpirat gave me root after the update

flash from recovery
[Nexus One Android Development] awicks:
I have just used this ROM (Stock, unrooted, no modifications version) to upgrade from FRG83D to FRG83G. I then applied the GB update and tried to reboot but got stuck in a bootloop at the moving X. I then reflashed just the FRG83G update and have tried rebooting this but got the same bootloop.

My HBoot is already 0.35.0017 so I did not update this - is this where I am going wrong? Radio is 5.08.00.04

I am using Amon_RA recovery and both the FRG83G rom and GB update installed without errors.

Any other suggestions?

Thanks.
[Nexus One Android Development] awicks:
Discovered that I was being a complete n00b by forgetting to wipe anything before I flashed the new ROM. Following a wipe and a reinstall I am now up and running with Gingerbread :-)

Thanks for the FRG83G ROM!!!

Andy
[Nexus One Android Development] GldRush98:
Thanks for the OTA compatible flash dsixda. It got me to GB :)
[Nexus One Android Development] dsixda:
Likely the HBOOT

You can now skip all that and flashed the full stock 2.3.3 dude.. (needs hboot)

http://xdaforums.com/showthread.php?t=968396
[Nexus One Android Development] gotunandan:
I used the Stock unmodified FRG83G and then downloaded the official Gingerbread OTA and got to GRI40. It went smoothly and everything seems fine as of now.

But I do have a query.

A little bit of history first:

I was running Kang-o-Rama (CyanogenMod 6.1.1) and thought, I'll go back to stock.

And I even decided to

That was successful but after that for some reason I was not able to flash the newer 0.35.0017 hboot using fastboot.

gave the following error:

Did not understand how to solve this, so I just decided to flash the hboot image via recovery using the d6096cac5e9f.signed-hboot-0.35.0017.zip file from the GOOG servers. This went fine and then I flashed the stock FRG83G image and beyond.

Dunno why it would not work with fastboot though, anybody with an answer ?

P.S. Also as I understand, now that I have an unlocked bootloader, I should be able to flash a custom recovery, boot.img images, etc via fastboot as well right ?
[Nexus One Android Development] colognerunner:
How did you do this. I can enter the Recovery, but it's the stock recovery now (Android System recovery (e3)) and when I try to install su.zip it says

Finding update package...

Opening update package...

Verifying update package...

E:signature verification failed

Installation aborted

Did you get this managed with the Stock recovery ???
[Nexus One Android Development] gcng:
no, I used Amon_Ra's 2.2.1
[Nexus One Android Development] robotnoize:
so I have stock recovery back on my phone and I also have stock with no root 2.3.3 on my phone. it seems after I installed the GB ota it cleared my amon Ra. trying to flash su.zip but I can't with stock....can I fastboot flash amon ra again without doing any damage??
[Nexus One Android Development] dscott23:
I just went through the same procedure, and I flashed RA recovery without any issue.
[Nexus One Android Development] rajazeeshan:
Originally Posted by robotnoize

so I have stock recovery back on my phone and I also have stock with no root 2.3.3 on my phone. it seems after I installed the GB ota it cleared my amon Ra. trying to flash su.zip but I can't with stock....can I fastboot flash amon ra again without doing any damage??

===================

I am in same boat as you ... any solution ?
[Nexus One Android Development] gcng:
worked for me
[Nexus One Android Development] hhg2190:
Thanks pal. I received GB OTA, now I am on GB. Awesome!
[Nexus One Android Development] rajazeeshan:
I had unlocked bootloader and I was in same situation as you with stock bootloader. Just did fastboot flash amon recovery without any issue and now I have amon's recovery back. Give it a shot it worked for me.

I am back to CyanogenMod 6.1.1 Gingerbread is all cool but without track ball wake, FM Radio , no 720 recording hmmm not my taste .. I will wait until some one atleast puts trackball wake ... Good luck !
[Nexus One Android Development] rajazeeshan:
Have anybody noticed that new radio came with Gingerbread has very bad wifi connectivity ?
[Nexus One Android Development] hhg2190:
I know but that is not a new GB radio, I think.

Radio version is still 5.08.00.04 and its connectivity is worse than Korean radio 5.12.00.08.
[Nexus One Android Development] rajazeeshan:
Here in US Tmobile I have reverted back to Radio 4.06.00.12_7 that I was using since stock and got back things to normal.
[Nexus S Q&A, Help & Troubleshooting] theinternot:
Hi all,

I am on my 4th Nexus S in three weeks.

The current one seems perfect, but just noticed today that when I have the headphones plugged in and am receiving a call... the speaker on the phone rings and not the headphones.

I can't remember if this has always been the behavior on the previous ones, but I am pretty sure I would have noticed that before.

Anyone else experiencing this? Any fix?

I am about ready to call it quits on the NS and look at a different manufacturer if this is a defect. Love the phone, but if I can't find a solid one in 4 tries, I am not gonna waste anymore time with it.
[Nexus S Q&A, Help & Troubleshooting] zorak950:
I don't know what it's supposed to do; mine rings in both the headphones and the external speaker. Also, bear in mind that defects often come in batches, and they don't shuffle the boxes before sending them to retail, so if you've gotten several bad ones in a row, it's not a bad idea to try a different store.
[Nexus S Q&A, Help & Troubleshooting] theinternot:
Thanks for the response. I hear you on the batches... I purchased them all at different locations specifically for that reason.
[Hero CDMA Q&A, Help & Troubleshooting] AspenTree:
please help

i tried using root explorer and titanium back up and many other apps that require root access but the superuser prompt for granting access isn't appearing :( someone please help me get it working asap
[Hero CDMA Q&A, Help & Troubleshooting] FdxRider:
Try settings applications superuser clear data abd reboot and try to gain access again

Sent From My Pedal-to-the Metal Hero
[Hero CDMA Q&A, Help & Troubleshooting] laie1472:
Go into settings/applications / manage applications. Then scroll down to the superuser app and force close then clear data. Then go to the app in your app drawer and restart the app. Then go into the settings of the superuser app and scroll down to notification type and choose regular / normal notification instead of toast notification. Then try your apps that require su you should be good to go. Let me know if this works.

Root-Hack-Mod-Always™
[Hero CDMA Q&A, Help & Troubleshooting] AspenTree:
neither worked :( i'm just going to reinstall my entire rom........sigh
[Hero CDMA Q&A, Help & Troubleshooting] laie1472:
After you do either one try a reboot

Root-Hack-Mod-Always™
[Hero CDMA Q&A, Help & Troubleshooting] AspenTree:
titanium backup says i am rooted but i don't have busybox so i need busybox but i can't get it to install that either...i even tried to use the busybox installer fromt the market but superuser won't grant it access...... :(

this is holding me back big time on my phone lots of apps require superuser to grant them access :(
[Hero CDMA Q&A, Help & Troubleshooting] FdxRider:
Kifno did you try reflashing your rom again you shouldn't loose any settings or apps.Also you could try uninstalling superuser and reinstalling it,or don't know which recovery you are using but you could try fix permissions.
[Hero CDMA Q&A, Help & Troubleshooting] Bierce22:
Also don't update the binarys a couple roms have that problem when u flash a new rom go to the market first thing and make sure su isn't automatically updated if so stop it I had to do that coming from cm6.1 to asop9.9.2
[Hero CDMA Q&A, Help & Troubleshooting] AspenTree:
I did a complete wipe of every thing and re flashed my rom and this time I used the apps2sd that was built into the rom instead of flashing the new one on that one thread lol.....flashing newer apps 2 sd was the problem lol
[Droid Eris Q&A, Help & Troubleshooting] Ddukes76:
How hard is it to change out cracked screen on eris?

anyone have an extra screen lying round possibly from a bricked phone?

Please help
[Droid Eris Q&A, Help & Troubleshooting] EhudBenjamin:
There have been a couple post like this and the general consensus is its a lot cheaper and easier to have the insurance handle it.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
I could swear I have seen a post - including pictures - of the entire dissassembly process; of course, I can't remember where, but it is probably worth your time to do a little Googling.

A few months ago, "for parts" Eris phones with intact screens on eBay were selling for north of $60-70; I suspect that price is due to the fact that a new replacement touch-screen assembly will cost a bit more than that.

So, the prior poster's remarks make sense if you have phone insurance, since the costs involved are comparable - especially if you consider that there is a chance you will spend the money on self-repair.. and not succeed at it.

If you thought you were going to spend $70 and a bunch of your time to end up with a used phone, maybe you could sell it ("for parts") on eBay, and then you would have $140 to spend on a different used phone... with the same out-of-pocket expense.
[Droid Eris Q&A, Help & Troubleshooting] Ddukes76:
Ui

Digitizers are currently going for 40-50 bucks with tools, insurance is 80 bux. Just weighing my options, im confident I can change digitizer screen. As of now, all still works... :|crosses fingers|:
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
$40-50 new?
[Droid Eris Q&A, Help & Troubleshooting] Ddukes76:
Yep- new. Out of cali
[Droid Eris Q&A, Help & Troubleshooting] frostbyte32:
I tried doing the repair on my old Eris and ended up screwing up and bricking my phone. I have an extra digitizer that I never even was able to use. I ended up getting an Eris off someone who got an upgrade. It was my only option since I didn't have insurance on the phone.
[Droid Eris Q&A, Help & Troubleshooting] amfetamine:
Not hard at all. Look it up on youtube. Watch video till you're comfortable, go slow and be gentle. Get the right screwdriver. Torx set.
[Droid Eris Q&A, Help & Troubleshooting] eriscat:
Try at your own risk

If you don't have insurance, you can pick the digitizer up for $40 or so (I think I got the first one for around $30.) I actually got the last one on Amazon, there are several there now.

YouTube videos help a lot even at helping you see the parts and knowing what comes next. We paused the video as we went so we could match up parts and it helped when putting it back together again. Go slow and keep track of pieces parts (like any other repair work you have likely done.)

One thing that was an after the fact duh - was that any dust you get under the new screen is very visible. You will keep trying to clean off your screen. Then you have to take it apart again to get it really clean.

If you don't think you can do it and if you don't have insurance, there are places that repair phones. Talk to your Verizon store, they might know of one. The one around my house wanted $100 to replace the digitizer.

Good luck!
[Droid Eris Q&A, Help & Troubleshooting] frostbyte32:
The whole process is pretty easy, but the only problem I ran into was that the parts that had adhesive on them were OVERLY sticky. Like it was next to impossible to pry off some of the parts that needed to be replaced. There's an attachment to the back of the LCD screen that I worked on for 45 minutes and just when I was about to get it a small ribbon got cut by the prying tool rendering the phone completely useless.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
FWIW

http://www.youtube.com/watch?v=ltg18zSau9M

also the most recent posts in this AF thread

http://androidforums.com/htc-droid-eris/31566-screen-replacement.html

The link to the digitizer re-seller (repairsuniverse.com) in the above thread still has a $69 price - anybody have a link to a supplier (not eBay/Craigslist) that is cheaper?

[ Edit ] Never mind - Amazon.com - 39 bux. doh!
[Droid Eris Q&A, Help & Troubleshooting] Ddukes76:
Vid walkthru really helped..

Go slow, take ur time...

It will work great,

Back in bizness....

Thanks bftb0