Tutorial: Install Froyo on N1 - READ TO INSTALL FROYO - Nexus One Q&A, Help & Troubleshooting

Here's a basic tutorial I wrote up to install Froyo on the N1. Seems like most are having trouble with it. All Files Included. Follow the steps as listed. Report any problems but I have yet to hear from anyone about any issues... Enjoy!
My Way also updates to the newest radio. New radio includes new Video Encoders so you'll want to try the new radio first.
Tutorial Here
Please Post your Results - Feedback. Thank You.
If you try any optional kernels, try .34 kernels, not 33.4. There is positive feedback w/ .34kernels + new radio. If you're using the Old Radio and a 2.1 Build then stay on the 33.4 kernels.
I know it's redundant to install CM first as it mostly gets overwritten. Again, these are the steps I took and it's what's worked for me and others. Don't skip steps, if you have any issues let me know. I also just updated the CM 5.0.7 to Final, it's not test-3 anymore.
Like I always say... ENJOY!

+1 - Worked like a charm

The N1 can't boot up and hang on the 4color logo after flash the CM 5.0.7, what can I do now ?

adamxadam said:
The N1 can't boot up and hang on the 4color logo after flash the CM 5.0.7, what can I do now ?
Click to expand...
Click to collapse
Did you wait for the radio update to finish (the picture of the box with the arrow coming out of it pointing to the android) and have it go back to the recovery screen again?
The instructions don't appear to make any mention of the radio flash & reboot. I also don't see the point of installing the Cyanogen ROM first, what's the benefit of doing this considering the majority of it gets overwritten by the FroYo /system flash anyway, and the gapps all get replaced as well. (Cyan installs nothing to the /data partition).

adamxadam said:
The N1 can't boot up and hang on the 4color logo after flash the CM 5.0.7, what can I do now ?
Click to expand...
Click to collapse
Try the tutorial again, the radio part wasn't the issue as you haven't even gotten to that step yet. I re-uploaded CM 5.0.7 to final, it's not test 3 anymore... Try again and post results please... and follow steps exactly. As far as doing CM first, it's not necessary, I just include that step because it's how I did it and it works great for me and everyone who's tried it this way.
Also, make sure you do the prerequisites first like installing the recovery

Why not just load up FRF50 straight up, why the need for the EPE54B, and CM 5.0.7?

DXL007 said:
Why not just load up FRF50 straight up, why the need for the EPE54B, and CM 5.0.7?
Click to expand...
Click to collapse
Again, this is the way I used and it worked... Also, there are 2 update.zip's floating around. 1 Is an update from 2.1 to 2.2 and one is the full update.
Better safe than sorry

Related

Unable to flash Anything else

i have done quite a few searches on this and yet have found nothing so i hope i dont get reamed for posting this.
if someone has a link for this answer id be very thankful.
if not then PLEASE SOMEONE EXPLAIN!!!!!!!
at the moment i am running drizzy hero rom. to do the update i did use the one touch root. on a second phone i did it manually. on both i added the hard spl and am running the RA v 1.2.1 recovery. I liked this ROM and wanted to see what bugs it had. after a few days i wanted to switch and try a different ROM I have dl most of the ROMs available and already have them on my sdcard once i did this no ROM would load except for Drizzy(new Vision v2.8). after trying a few things and accomplishing nothing i decided to redo EVERYTHING. unrooted my phone rooted again applied recovery made sure radio was to date and spl. and still nothing i cant even run the original jf1.5 that i was using before deciding to port. this issue is occuring on both phones. 1st phone was again done with one step root and the 2nd phone was done completly manually. I REALLY REALLY REALLY want to try these other roms SO PLEASE SOMEONE HELP. if you need more information on what i did with these phones ill gladly tell you step by step on what i did.
sorry for that.
I was using my G1 and also had a friends. On my g1 i used the one step root. I used the Instructions from The Unlocker.com. It uses flashrec.apk and also Amon Ra's recovery image. After that i went over to the How to Load a Custom ROM. same site. It asks you to check the Radio and the Spl. The radio is 2.22.19.26I and the spl used was the HARDSPL 1.33.2005.
Once i finished that i went and formated the sdcard to Fat32+Ext2+LinuxSwap also converted Ext2 to Ext3.Then I did-Move Dalvik Cache to SD. last 3 steps to speed up hero. after all of that I loaded 4 ROMS CyanogenMod ROM, jACXHeroSkiv Hero ROM v1.8, Drizzy’s NewVision TouchFlo ROM, and JF v1.5 Cupcake ROM. I have only flashed Drizzy's until last night.
I was unable to flash any other one and when i flashed back to drizzy I had problems loading it back but eventually loaded fully the issue was running the startup wizard it kept crashing. after a reboot it was ok.
Give us step by step on what you did and USE PARAGRAPHS
that whole thing looked like mumbo jumbo to me
put new lines where they belong to help separate out the steps you took
FIXED! thanks!
hobbitton said:
FIXED! thanks!
Click to expand...
Click to collapse
did you do a data wipe? you need to wipe going from hero to cupcake/donut
When I first did all of that I did. Am I supposed to data wipe everytime I switch the Rom?
hobbitton said:
When I first did all of that I did. Am I supposed to data wipe everytime I switch the Rom?
Click to expand...
Click to collapse
when your using hero rom's, yes.
if your upgrading cupcake roms (ie cyan 4.0.4 to 4.1.9.2 ), no
If its not working, WIPE
you cant go from hero to cupcake without wiping and not expect a lot of problems. they cause too many issues.
hero roms use the data partition differently
also remember to wipe /system/sd/ to clear all of that out. pull your /system/sd/ to your computer first though
thanks you guys it helped alot

simplest way to switch from JF 1.5 to current Cyan?

I bought a g1 off of craigslist and it already had root. JF 1.4 ....
Around the time cupcake was released I updated it to jf 1.51
Now since there will be no more JF updates I wish to switch to Cyan builds.
I'm unsure of the proper way of doing this?
Should I go back stock .. unroot and then go thru the steps to load cyan?
Or is there a better way? A wipe?
I'm asking to be clear because internet access is strictly from my g1.
Although I can download all the files I need, I do not have constant access.
I'd appreciate any tips or pointing me to the proper thread.
Check the threads in Dream >Dream Android Development look for Cyanogen's thread on his release of 4.1.999, follow the instructions and you will be fine. I'd also suggest at least flashing Cyanogen's v1.4 Recovery Image over JF's, easier to flash any .zip on sdcard. So, new recovery image (use search option in forums, or look in the same thread i mentioned for cyanogen recovery image 1.4) then update to cyanogen's latest rom build
So simply flash a new recovery, then follow the cyan steps?
Cool, easy as pie.
I certainly appreciate it.
Thank you
Yup. just be careful that you dont boot off the htc recovery rom, or the steps to get to cyans rom become much, much harder
B-man007 said:
Yup. just be careful that you dont boot off the htc recovery rom, or the steps to get to cyans rom become much, much harder
Click to expand...
Click to collapse
that is why there is a full update made for it.
haha o right i forgot about that one... no one asked questions about a bad all-in-one flash, only those who messed up while flashing the htc rom
i need sleep lol
B-man007 said:
haha o right i forgot about that one... no one asked questions about a bad all-in-one flash, only those who messed up while flashing the htc rom
i need sleep lol
Click to expand...
Click to collapse
sleep is for the weak. also it is really hard to flash two things while in recovery it causes hemorrhoids and anal fissures.
haha trust me...someone somewhere will make something incredibly easy look like rocketscience
B-man007 said:
haha trust me...someone somewhere will make something incredibly easy look like rocketscience
Click to expand...
Click to collapse
you mean rocketsurgery
david1171 said:
you mean rocketsurgery
Click to expand...
Click to collapse
*sigh*
yes its true.
B-man007 said:
*sigh*
yes its true.
Click to expand...
Click to collapse
lmao me went to smart person learning place
I'd like to chime in here as well since I'm having such a hard time searching for info on the conversion from jf1.51 to the latest build of CM. The amount of posts are staggering!
So, I vaguely remember setting up apps2sd following the guide at the bottom of this page - http://yokohead.com/2009/06/how-to-root-android-g1-with-cupcake-and-appstosd/
Will CM automatically detect this partition?
Also, will I lose the google experience? I'm still confused as to where we are on that.
Thanks for your time! If anyone knows an updated post on this process, please point me to it.
TJ
Well the sticky by fingerlickin at the top of this section is a good place to start....
all you have to do is find the singleflash update in the dev section, backup and clear everything off your ext3, and wipe+flash the single update. you can restore the ext backup then.
also you should upgrade to cyan 1.4 recovery
to do so
su
cd /sdcard
wget http://n0rp.chemlab.org/android/cm-recovery-1.4.img
flash_image recovery /sdcard/cm-recovery-1.4.img
Click to expand...
Click to collapse
you wont lose the google experience
Thanks B-Man007,
After a couple attempts, all is working well. I'm thoroughly impressed with the snappiness of this build. Although it's only my second time updating a ROM, I'm going to blame the amount of posts for my hesitation and confusion. It was easy to just go in and do it.
I actually updated to the latest Amon-Ra(sp?) recovery. At first my Rom was running real slow and the recovery allowed me to update my ext2 to ext3. Loving it now!
The amount of posts does make it quite confusing i agree, especially with the high amount of conflicting posts
Ya ext3 is a must, but you could have upgraded from cyans too haha
cyan usually has the fastest builds out there though at times it can get very slow.
Another noob here. A few months ago I rooted and flashed to xrom 1.5. When I do a reboot, my recovery screen tells me its "CyanogenMod v1.4 + JF".
Since xRom is experiencing some problems w/ updates, I figured I might try the latest build of Cyanogen. I re-booted, went to recovery mode. Wiped. Then flashed the latest Cyan and even found the 1.6 ota on another site. Flashed both zips, then did a re-boot and it hangs now.
I tried it over and over a few times, wiping then flashing again. Wiping, then re-booting, then flashing the rom, etc. Over and over with the same results.
Then as a test, I tried flashing back to xRom... perfectly fine.
As another test, I tried wiping and flashing to another rom, the rooted stock option (the HTC rom version)... and got the same results as when I tried Cyan... just hangs.
Wiped and flashed again back to xRom... works fine.
So at this point, I'm thinking I need a more updated recovery rom? Any other possible problems? Yes, I did a search all over and this was the best thread that matched my problem.
If it helps... I have a T-mo G1, firmware 1.5, JACxROMv1.5, kernel version 2.6.29.6-jac-ski root. And I know many will slap their foreheads when I say this: But the SD is NOT partioned at all (kept trying and trying with zero success, so I eventually gave up).

Need help.

Okay for those of you who don't know, I totally bricked my phone based on a dumb decision last time and not knowing what I was doing.
I am thinking off trying to root my phone again, any advice on what rom I should root to and which is the best and most stable for the G1.
Kaos Chase said:
Okay for those of you who don't know, I totally bricked my phone based on a dumb decision last time and not knowing what I was doing.
I am thinking off trying to root my phone again, any advice on what rom I should root to and which is the best and most stable for the G1.
Click to expand...
Click to collapse
u should really go with cyanogens roms
Cyanogen's latest is pretty sweet. As long as you follow the steps correctly to root your phone, you shouldn't have any problems flashing any of the roms available. Then you can test them out, and see what you like.
does anyone know any good tuts to use to do so?
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
melterx12 said:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
Click to expand...
Click to collapse
Thank you so much everyone! You all were a huge help. I have rooted my phone successfully this time and I love it!
I followed the instructions from the link on this thread to put cyanogen on my g1 but after the skateboarding android logo faded all I got was a illuminated phone I let it sit that way for 25 minutes hoping something would happen but nada so I restored a backup. Can anyone tell me what went wrong and how I can get cyanogen working?
Nobody can tell you what went wrong since we don't know what step you skipped/didn't do right based off that statement. All we can say is follow the guide to a T. The guides are the best the communitty has to offer/has produced on how to do what you want to do. If you can't follow the guide, sadly there is nothing we can do to help beyond repeating what the guide already says.
I've got cm recovery 1.4 so that step and the ones leading to it are done right, right? Then I ran the recovery, made a back up, wiped data, applied zip drc83 defanged, applied
Cm update 4.2.13 (I think 13, whatever stable version the "latest version" link give you), applied ota radio, and rebooted (automatically took me back to recovery) rebooted again, got g1 logo followed by the cyanogen android logo once that faded all the lights on my phone came on and stayed on and I had no display (apart from the backlight).
I tried multiple times with no luck. I downloaded the cm update from my phone could that of caused a problem? Everything else was dl'ed from a pc.
What's the differance between drc83 and signed dream devphone should I try that instead?
http://forum.xda-developers.com/showthread.php?t=563679
Follow the guide to a T, since you are partialy there I will tell you what you have left:
1. Download the developer recovery ROM (This is different than drc83 by a lot)
2. Download the latest CM
3. Put both on the root of your SD card
4. Boot into recovery mode, flash the developer ROM, then flash the latest CM
5. Use the "Home" and "Back" buttons to reboot the phone
6. Tada! Success!
7. Never, ever, do anything the guide doesn't tell you to do. If it says flash file X don't flash file Y because you think it is close enough. Never do extra stuff, ie if it doesn't say flash a radio by itself, don't flash a radio by itself because it seems like a good idea.

Stuck, don't know where to start now...

I have a tmob G1 and I've been running cyanogen for months with no problem. When I updated to 4.2.12 I noticed performance issues that I'd never seen before. This is commented on a lot at the cyanogenmod site and thats where I did most of my research. I read a post where someone factory defaulted, and then re-installed 4.2.12 and said it was flying again. They use DRC83 defanged? I know where to find that but I'm not sure what it is or if I need that. Many ppl made like comments. I read that I should get the radio and recovery imgs at the htc site so I did and flashed both. This is where (I think) I made my first mistake as I have a G1 and not an ADP1. My phone is now running fine with stock 1.6 and the above radio but instead of G1 it says my phone is a ADP1 (obviously). I've tried to install cyanogen 4.2.13 but I'm guessing that I am not rooted anymore because I can't? I've tried the rooting ADP instructions from cyanogen wiki and that doesn't work. Looking at the same instructions for the G1 it says I need to downgrade to RC29 but that seems like a big step backwards. Is that what I need to do? Do I have to start all over again? I don't know what my next move should be? Thanks!
Gonna have to Use the DreaIMG and go back down(make sure dont have danger SPL,but you went back down so dont think you do) then get the "signed-dream_devphone_userdebug-ota-14721" and a recovery (i like amon ra 1.5.2) and get your fav rom( i would give superD 1.2 a try[1.6 requires danger SPL] and 1.2 seems the most stable) but if your goin to use cyan rom get the latest cyan rom, from there after flashed recovery go into recovery do a wipe then flash the dev ota, dont reboot, then flash cyans rom after do a reboot and should be back on cyan's rom
Brilliant! I'm back up and running latest cyanogen. I completely missed the part about dreaimg in the wiki instructions. Thanks for the help.
Also, out of curiosity, why do you like super d? Whats the difference between it and cyanogenmod? Thanks again.
Super D is, in a way, one step faster then the current CM build. It comes with a 10mb ram hack pre-installed as well which is always nice. Don't get me wrong, CM has a dedicated thread on 10mb ram hacks.
Ultimately, it comes down to user experience. And it's always nice to try something new.
jkapernicus said:
Brilliant! I'm back up and running latest cyanogen. I completely missed the part about dreaimg in the wiki instructions. Thanks for the help.
Also, out of curiosity, why do you like super d? Whats the difference between it and cyanogenmod? Thanks again.
Click to expand...
Click to collapse
I like Cyan roms just as much as anybody, to a personal pref. i had lot of problems, gapps went missing after updated, FC's and what not, and i did everything from going back down(dreamimg) to update from latest, still had problems, then i wen to superD and i notice a great increase of speed and all around well stabled rom

[Q] Is cyanogenmod 6 rc2 radio upgrade important to flash

Hi all.
I had recently flashed cm6 rc2 without the radio via rom manager comming straight from froyo. While using the ROM today, I noticed a lot of processes crashed all at once including acore.
When I rebooted, I was stuck in a boot loop. I wiped stuff and did a nandroid restore to get back to my stock froyo, just fine.
Was it the radio that caused it (edit: seems like rom manager may have snuck it in). Since I flashed cm6 from ROM manager, I thought it would prompt me if I needed the radio. What went wrong?
The radio on the first post of the CM6 RC2 thread is the required radio and must be flashed separately if you are not already using that radio. If you are on stock froyo you most likely are.
Radio Firmware: 4.0.6.00.12_7 (FROYO RADIO, REQUIRED!)
Check this by going to: Settings - About Phone - Baseband version
If you are not on the correct radio you can flash by downloading the zip on the first page of the CM thread.
http://forum.xda-developers.com/showthread.php?t=722798
If you update again try wiping and a reboot into the mod before your nand restore. Some common issues/fixes are in the link below.
http://forum.xda-developers.com/showpost.php?p=7418214&postcount=2055
Good luck to you.
Please read the instructions next time instead of posting a new topic.
Edit: Actually, after reading your other post, I'd say, stop what you're doing, reflash to stock, and please don't do anything more. I can see you'll be a headache for all the other users in the future as you refuse to read first then ask questions. Everything you need to know is in the first post of the CM6 RC2 thread and the wiki that is linked within that post. If you can't handle that much, please do us all a favor and don't flash custom roms.
I'm waiting for the "My phone iz bricked now" thread to arise...In the right forum next time I hope!
It's lame topics like this that get budding roms pushed to the back of the list.
chesh is right though, you need to learn by reading first. The search button is your friend.
chesh420 said:
Please read the instructions next time instead of posting a new topic.
Edit: Actually, after reading your other post, I'd say, stop what you're doing, reflash to stock, and please don't do anything more. I can see you'll be a headache for all the other users in the future as you refuse to read first then ask questions. Everything you need to know is in the first post of the CM6 RC2 thread and the wiki that is linked within that post. If you can't handle that much, please do us all a favor and don't flash custom roms.
Click to expand...
Click to collapse
Mind you. I read those instructions 1 million times. I chose not to flash it because a website said you only need it if you are comming from froyo. I had also seen a video of someone running cm6 without the radio. So I thought I was fine
jrmurph said:
The radio on the first post of the CM6 RC2 thread is the required radio and must be flashed separately if you are not already using that radio. If you are on stock froyo you most likely are.
Radio Firmware: 4.0.6.00.12_7 (FROYO RADIO, REQUIRED!)
Check this by going to: Settings - About Phone - Baseband version
If you are not on the correct radio you can flash by downloading the zip on the first page of the
If you update again try wiping and a reboot into the mod before your nand restore. Some common issues/fixes are in the link below.
Good luck to you.
Click to expand...
Click to collapse
So are you saying that the 4.0.6.00.12_7 is the radio needed to use cm6 or does it mean I need to flash the radio
GlobaL_TroTTer said:
So are you saying that the 4.0.6.00.12_7 is the radio needed to use cm6 or does it mean I need to flash the radio
Click to expand...
Click to collapse
4.0.6.00.12_7 is the Froyo radio that is required for using CM6 or Froyo roms. Froyo will work with the earlier radio, but you'll have issues with camera, video camera, MMS, SMS, and a whole slew of other things. There is another radio floating about that's from the Korean version of the Nexus Ones, and has a higher version then the initial Froyo radio, but at this time, doesn't seem to change anything. So, the way you check which radio you already have (as most Froyo roms don't come with the radio, you're required to flash it on your own) is to go into Settings -> About Phone and check what version of the radio you have listed in there. If it is anything other then the above version, then flash the above version.
Follow this guide to the "T" and you won't have any issues. And, BTW: this guide is linked in Cyanogen's original post in the CM6 RC2 thread. (Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.) http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Nexus_One
Strangely enough, i have that radio even though i didn't flash it. is it possible it came from rom manager when i installed cm6 or could it have been there when i got froyo
chesh420 said:
4.0.6.00.12_7 is the Froyo radio that is required for using CM6 or Froyo roms. Froyo will work with the earlier radio, but you'll have issues with camera, video camera, MMS, SMS, and a whole slew of other things. There is another radio floating about that's from the Korean version of the Nexus Ones, and has a higher version then the initial Froyo radio, but at this time, doesn't seem to change anything. So, the way you check which radio you already have (as most Froyo roms don't come with the radio, you're required to flash it on your own) is to go into Settings -> About Phone and check what version of the radio you have listed in there. If it is anything other then the above version, then flash the above version.
Follow this guide to the "T" and you won't have any issues. And, BTW: this guide is linked in Cyanogen's original post in the CM6 RC2 thread. (Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.) http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Nexus_One
Click to expand...
Click to collapse
turns out i have the radio, even though i didnt flash it (unless its not the baseband you mean) i think rom manager snuck it in- could this be possible
if you flashed froyo previously then the radio got updated with that full ROM.
one more thing, for some reason the clockwork recovery keeps dissapearing. it changes to an exclamation mark in a white triangle with a mini green android. it just dosent like me!
Once again, see my previous post where I linked you to the Cyanogen Wiki with complete, step-by-step instructions of how to install all of this manually. I would suggest the manual route, as it seems you need the practice with the commands.
chesh420 said:
Once again, see my previous post where I linked you to the Cyanogen Wiki with complete, step-by-step instructions of how to install all of this manually. I would suggest the manual route, as it seems you need the practice with the commands.
Click to expand...
Click to collapse
what im saying is that every recovery image i use disappears after i have been in the recovery image more than once Even Amon ra's recovery!
Which means you haven't done some part of the process right. I remember hearing about this once before. Just start from the very beginning of those instructions (including unlocking bootloader). Not going to harm anything if it's already been done.
chesh420 said:
Which means you haven't done some part of the process right. I remember hearing about this once before. Just start from the very beginning of those instructions (including unlocking bootloader). Not going to harm anything if it's already been done.
Click to expand...
Click to collapse
Are you sure. I searched slot and I didn't find anything about recovery images reseting. I am in need of help.
One thing about the rooting process, all I did was unlock the bootloader and install su permissions. It's hard to find detailed and I mean detailed instructions on rooting a nexus one and installing a recovery image.
do a wipe
i did everything again except unlock the bootloader again because i am not sure of the result of that if you have already done it. do you think a factory restore would do the trick in setting or do i need to http://forums.t-mobile.com/t5/Opera...-Nexus-One-to-shipping-Rom/m-p/292051#U292051
Did you do all the steps in the Cyanogen wiki that I linked you, exactly as they were? Because, if you did, you wouldn't still be having a problem. See, this is what I'm saying, you keep on posting, but you don't want to follow any instructions. Why don't you follow that t-mobile guide, and give up on installing custom roms.
And, are you saying this isn't detailed enough?? http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Nexus_One
Or how about some video's in the sticky at the top of this forum? http://forum.xda-developers.com/showthread.php?t=705460
Or, how about these: http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials
I mean, I found all of those in the last 45 seconds. Come on man. You obviously just can't follow instructions. What you need is the 5yr old from down the block that keeps beating your a$$ at MW2 to do it for you.
why dont you post a video showing exactly what happens. show it booting into recovery, then trying again and recovery disappearing.
Would just let everyone know I fixed it. I've been reading alot and now allmost fully understand the rooting and flashing side of android. Sorry for this noobish post. Will never happen again
Sent from my Nexus One using XDA App
chesh420 said:
Did you do all the steps in the Cyanogen wiki that I linked you, exactly as they were? Because, if you did, you wouldn't still be having a problem. See, this is what I'm saying, you keep on posting, but you don't want to follow any instructions. Why don't you follow that t-mobile guide, and give up on installing custom roms.
And, are you saying this isn't detailed enough?? http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Nexus_One
Or how about some video's in the sticky at the top of this forum? http://forum.xda-developers.com/showthread.php?t=705460
Or, how about these: http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials
I mean, I found all of those in the last 45 seconds. Come on man. You obviously just can't follow instructions. What you need is the 5yr old from down the block that keeps beating your a$$ at MW2 to do it for you.
Click to expand...
Click to collapse
I fixed it differently from how you said I should do it even though I tried to do what you said.
Also. I OWN at WW2... you have no idea. Being cocky doesn't fix anything.
Also I know how it feels when there is a new generation of android hackers joining the community. I was with the iphone hacking community from the start. I miss the days when hacking was harder. Don't start saying I can't follow instructions on the rooting process because it was a nandroid restore that stuffed everything up. I rerooted twice just to make sure.
I hate being taken as a noob. Everyone starts somewhere.
Sent from my Nexus One using XDA App

Categories

Resources