[ROM] Passion_Google_WWE_2.16.1700.1_FRG33_MFG_Shipment_ ROM

Search This thread

LlabTooFeR

Inactive Recognized Contributor
May 26, 2007
3,433
12,675
llabtoofer.com
This ROM was released today, I'm not android guru, but I think this is quite interesting thing for users and cookers:D
 

Christopher3712

Senior Member
Oct 2, 2007
931
156
Google Pixel 6 Pro
Interesting...

***SPECULATION***

I wonder what the classification in the letters mean? It seems Eclair ROMs had E's in them, Froyos had F's in them. This latest has gone from FRF to FRG? That would be a nice, EARLY leak if it were an initial Gingerbread ROM.
 
Last edited:

ciwrl

Senior Member
Sep 1, 2006
70
55
Burtonsville
Radio is still 5.08, system.img is being unyaffs and compared to Stock FRF91/93, I'm sure you'll get a proper breakdown soon enough.

Spl is still the .35.0017 so no change there either.

Its not Gingerbread, or anything close; if anything its just a couple of bugfixes and a new base froyo code, still useful, but not that exciting.

http://teamdouche.pastebin.com/rg34zfW8 courtesy of persianown(kmobs)
 
Last edited:

wdfowty

Retired Recognized Developer
Jun 18, 2010
1,653
520
S.F. Bay Area, California
Last edited:

crazyknallchopf

Senior Member
Can u tell me how flash this rom?

sry my bad english

shutdown your nexus

press trackball und power (fastboot modus will be started)

unzip the file you downloadet

unzip the content again

copy the files to c:

-----

open command prompt

type: fastboot flash system system.img (press enter)

wait 1 minute

type: fastboot flash boot boot.img (press enter)

reboot

;-)
 

crazyknallchopf

Senior Member
None that I can find just browsing around. It feels smoother (?), but that could just be me wishing for a difference. Wifi is stabler, and faster to obtain IP addresses (for me at least)

Kernel version: 2.6.32.9-27237-gbe746fba [email protected] #1



You need to fastboot flash the system and boot imgs

yes.. wifi runns faster..(find my router) and all runns smoother... cool :)
 

wdfowty

Retired Recognized Developer
Jun 18, 2010
1,653
520
S.F. Bay Area, California
Second round of testing (fresh boot):

1375 on quadrant and a 35.116 on linpack.

The bottom of the screen seems to be cut off slightly when using quadrant...anyone else see that?
 

renegadEEE

Senior Member
Jan 24, 2009
120
0
Could anyone do a test and put all the homescreens full of widgets (certainly the heavy ones lik Market widget, youtube,...), put a livewallpaper on (water for example) and see if this works smooth? If it does then google might have fixed the homescreen lag finally :)
 

imfloflo

Senior Member
Apr 20, 2007
3,058
814
Clermont-Ferrand, France
Google Pixel 5
Guys i was joking, cause the new rom was release today just few hours, how would you know if the battery life is good or not for the moment we need to wait few days more.


BTW : Zapote21 : "The new FRG33 system folder in zip format for easy manipulating... N1 newest dump... http://bit.ly/aCOTHR #android"

Amon_RA : "The FRG33 N1 leak contains the same radio as the previous Korean leak."
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    My friend's new nexus one is already FRG33 as it arrived, there is no way to use 1-click root.
    I've tried to use new exploit from C skills and it did show "#". So I think it should do the trick.
    I doesn't flash anything yet, therefore, this is for your reference.

    C skills: h ttp://c-skills.blogspot.com/2010/08/please-hold-line.html

    1. Get the exploit (executable file)
    exploit: h ttp://stealth.openwall.net/xSports/RageAgainstTheCage.tgz

    2. Extract the .tgz file to get the "rageagainstthecage-arm5.bin"
    I put the file in d:\RageAgainstTheCage

    3. Put exploit file to your N1
    adb push d:\RageAgainstTheCage\rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
    adb shell chmod 700 /data/local/tmp/rageagainstthecage

    4. Enter adb shell
    adb shell

    5. Execute exploit (It will automatically close adb shell)
    $cd /data/local/tmp
    $./rageagainstthecage

    6. Restart adb
    adb kill-server
    adb start-server

    7. Enter adb shell again
    # (Yes, my lord.)

    I've found it may not success every time, if it doesn't, please go through steps 4~7 again.
    If it still doesn't work, we need to wait a new way to root. Good luck.