Related
So, first hello and thanks ahead of time for answering a noobs' problem.
I wanted to search before posting but don't know really where to start.
I followed the Tutorial Ninja guide to rooting found here:
http://tutorialninjas.net/2009/06/27/root-jailbreak-an-android-g1/
(so you can see which ROM, img, etc I used)
Everything went according to plan, except that the second command listed gave an error, that "-f no such file or folder could be found." But commands 1 & 3 worked, so I proceeded.
The problem I ran into was that when I upgraded the ROM at the very end, it would not boot up, it got stuck at the metallic "android" screen and was just stuck in a loop.
So, not having a microSD card reader, I just restored to factory settings. However this time, the beginning screen called my phone a Developer Phone, which it isn't. So it must not have restored everything to factory.
It appears the phone has a lot of the cupcake features, like auto-rotate screen, soft keyboard, but how could it be cupcake if I did a factory restore?
Here's the details listed under About Phone:
Model number: Android Dev Phone 1
Firmware version: 1.5
Baseband version: 62.33.20.08H_1.22.12.29
Kernel version: 2.6.27.25-cm [email protected] )
Build number: dream_devphone-userdebug 1.5 CRB43 148830 test-keys
I'm used to looking for an RC#, like RC33, but since I used a diff ROM, I have no clue what I'm running and if I indeed have root access.
Anyway, the point of rooting the phone was to have tethering capability, so I downloaded the Tether App and when I attempt to tether it asks me if I want to "allow" access for root:root (I'm paraphrasing) so it seems it is rooted. Can someone help me figure this one out?
Also, since I'll have to manual updates, where should I go for them?
This is such an awesome forum, and look forward to being part of the community. Thanks
meanderingthemaze said:
So, first hello and thanks ahead of time for answering a noobs' problem.
I wanted to search before posting but don't know really where to start.
I followed the Tutorial Ninja guide to rooting found here:
http://tutorialninjas.net/2009/06/27/root-jailbreak-an-android-g1/
(so you can see which ROM, img, etc I used)
Everything went according to plan, except that the second command listed gave an error, that "-f no such file or folder could be found." But commands 1 & 3 worked, so I proceeded.
The problem I ran into was that when I upgraded the ROM at the very end, it would not boot up, it got stuck at the metallic "android" screen and was just stuck in a loop.
So, not having a microSD card reader, I just restored to factory settings. However this time, the beginning screen called my phone a Developer Phone, which it isn't. So it must not have restored everything to factory.
It appears the phone has a lot of the cupcake features, like auto-rotate screen, soft keyboard, but how could it be cupcake if I did a factory restore?
Here's the details listed under About Phone:
Model number: Android Dev Phone 1
Firmware version: 1.5
Baseband version: 62.33.20.08H_1.22.12.29
Kernel version: 2.6.27.25-cm [email protected] )
Build number: dream_devphone-userdebug 1.5 CRB43 148830 test-keys
I'm used to looking for an RC#, like RC33, but since I used a diff ROM, I have no clue what I'm running and if I indeed have root access.
Anyway, the point of rooting the phone was to have tethering capability, so I downloaded the Tether App and when I attempt to tether it asks me if I want to "allow" access for root:root (I'm paraphrasing) so it seems it is rooted. Can someone help me figure this one out?
Also, since I'll have to manual updates, where should I go for them?
This is such an awesome forum, and look forward to being part of the community. Thanks
Click to expand...
Click to collapse
Doing a factory restore merely does a wipe of the data folder. You will still keep your ROM, SPL, radio, etc things that you've flashed. Those things stick with you. If its asking you for root, press always allow. You have root.
Firmware Version: 1.5 = cupcake. 1.1 = noncupcake. So you succeeded.
If you want to double check, go into terminal emulator (just download from market if you don't already have it)
When you open it, you should see:
$
from there, type su
$su
if you get:
# <- this means you have root permissions.
You can download custom ROMs from the developers forum. Just find one that you like and try it out, most of them only require you to wipe/flash the ROM from recovery (Home+Power). Cyanogen's are always a nice choice, or you can try Haykuro's or JesusFreke's (JF). But always check to make sure you have to the requirements to flash the ROM before doing so. They're usually located on the first post of the first page, so don't ask if you need this or that.
H
Hi, you do indeed have rooted cupcake my friend when you do a wipe, it's like a factory restore, it doesnt reflash the firmware the phone came with, it just re sets everything so the phone is "as new". This fixed the bootloop you had for some odd reason so your phone now boots up. It shows as an Android Dev Phone because you flashed the dev phone firmware.
That's it really, everything appears to be fine
I was beaten to it by the poster above because I was typing on my G1 Oh well, the 'su' in the terminal is a good point though.
Off the top of my head I'm not sure what version you're running, but yes - it is rooted. Does tethering work? If so, you're all set.
Well, mostly. Your radio is out of date. Use the link in my sig to snag the latest, apply it in recovery like the update.zip you did to flash your ROM.
What to do for updates is up to you.. There are many different ROMs out there, just need to pick which one works best for you. Personally, I suggest Cyanogen. But a new user shouldn't use the link in my sig.. Go over to the Development section of the forum and find the CyanogenMod 3.6.8.1 version - it's currently the stable version. If you want regular updates (new patches from Google, community developed features, etc) CM is the way to go.
SOLVED
h.nocturna - I did get #, I have root! everybody dance. Good to know about the factory restore
AdrianK - thank you. i guess i got kinda lucky fixing it myself, mostly due to lack of options. hehehe
Saiboogu - I have yet to get the tethering working. I tried today at work with a Mac Pro via Bluetooth, was able to pair, but could not establish a connection. I'm going to try later with my Ubuntu laptop which is what I will be tethering to in most cases anyway. I heard Bluetooth is the best way to go, but not sure why. Definitely convenient if you forgot your cord.
I'll check the dev forum to see about upgrading to the latest ROM, but I'm nervous, as I don't want to screw up my phone again. I was out-of-commission for half a day with this trial. But updating ROM should be easier that gaining root right? You don't need any special commands, just reboot and flash?
Again, thanks!!!
meanderingthemaze said:
h.nocturna - I did get #, I have root! everybody dance. Good to know about the factory restore
AdrianK - thank you. i guess i got kinda lucky fixing it myself, mostly due to lack of options. hehehe
Saiboogu - I have yet to get the tethering working. I tried today at work with a Mac Pro via Bluetooth, was able to pair, but could not establish a connection. I'm going to try later with my Ubuntu laptop which is what I will be tethering to in most cases anyway. I heard Bluetooth is the best way to go, but not sure why. Definitely convenient if you forgot your cord.
I'll check the dev forum to see about upgrading to the latest ROM, but I'm nervous, as I don't want to screw up my phone again. I was out-of-commission for half a day with this trial. But updating ROM should be easier that gaining root right? You don't need any special commands, just reboot and flash?
Again, thanks!!!
Click to expand...
Click to collapse
I'm pretty sure the bluetooth stack doesn't have transferring enabled at this point. You can only connect to headsets and whatnot, you can't transfer data. Try Wireless Tether (app from Market) to do your tethering.
Solved Again
Right again h.nocturna.
I am using the WiFi to type this post!
Thanks
meanderingthemaze said:
I'll check the dev forum to see about upgrading to the latest ROM, but I'm nervous, as I don't want to screw up my phone again. I was out-of-commission for half a day with this trial. But updating ROM should be easier that gaining root right? You don't need any special commands, just reboot and flash?
Again, thanks!!!
Click to expand...
Click to collapse
Don't be worried about flashing ROM's, the recovery console (power+home) is always available when you soft-brick, so you can always recover. My advice before you go any further is a) flash your radio if you haven't done so already, if you don't you may notice problems with calls, texts. data ect. b) grab cyanogen's recovery image and flash that. It will let you make an image of the phones memory (a nandroid backup) and then restore it if you soft-brick and are in a hurry to get your phone working again.
So today i finally get the gusto mod my phone Android Dev 1. After downloading all the files and following the instructions here i can't get past the black g1 screen (#8). note i can also get the the rgb screen. thats it, but with so many different posts with similar issues, my brain is pounding. At this point if i can get beack to factory, ill live. what i'll hate is the fact that bricked my phone. i'll most likely get screamed on for not searching, but i think i may be searched out. any help would be appreciated.
thanks.
docfu.
first of all dont freak out lol. Download the dreaming.nbh or w/e file from the rooting instructions and place it at the root of the sdcard. Then get into the rgb screen (Camera + Power) and flash it. That should get you back to factory settings. If not, download the update.zip for w/e region you are in place it on your sd card. Enter recovery (Home + Power) and flash the update.
ok...so i tried the DREAMING file and it kept turning up no image found, alternatively i'm not sure what you mean by w/e region update. i ihavent come across that in my searches.
ok dreaming file did infact work. i feel better knowing that the phone isnt bricked. however after running the update when it prompts for action, i hit the trackball and i'm right back at the rgb screen..AGGGHHHH! sorry. i've been at this since 3pm this afternoon.
Chill. Don't freak. You can't just jump in and do something as soon as your read it. Read the whole thing and if you don't have the patients for this work on that before you work on this. bbreath.
I must say start by saying thanks guys. i stepped back, and actually took my [email protected]@ to bed. Rest does wonders. That said. I've accomplished the factory reset. so i back to a stock g1, and boy does it suck. As stated my phone WAS a dev 1. i've already started the upgrade process, my question at this point is where do you recommend i go from here. back to dev 1 or try one of the other roms. i've already installed the spl, and right now im stuck at the telnetd part of the root process. and this too may have me screaming by the end of the day...
any thoughts would be appreciated.
After the recovery image is installed you need to update the radio if you want to install a cupcake 1.5 ROM. You can get it here, rename 'update.zip', place on the SD card and boot in to recovery and flash. Then flash a ROM of your choice. You should be able to do that on RC 30, but I'm not sure if you need to install a rooted image first, so I'd wait for someone else's input before trying that.
I played it extra safe and used the rc29. as far as i know the proper radio is installed. i'll wait around before i do something stupid. thanks for the input tho. i'm trying to learn everything.
ok...so i went back to the original method for obtaining root. i was so frustrated last nite that i ended up trying to combine 2 slightly diff methods. at this point i call them the telnetd method and root.apk method. correct me if im wrong but niether one mentions the other. so i make it to the bootloader running the root.apk it runs thru the list and the fails at radio_v2. now im on the white screen wuth the skateboarders, the radio #says 1.22.12.29. so i run it again i
now im on the rgb screen at proceeds to attept the update again. this time the dreaimg.nbh fails. i'm not freaking out. im good. because i know im almost there. feedback appreciated. thanks in advance.
y'know i never thought about this..but if i reverted a dev phone to factory settings...did i relock everything? and for the record, i only have a mac. if that matters at all.
Future reference ^-^
In case you encounter this problem in the future, cause it can happen with flashing new roms if you skip a step:
You're only bricked if you are stuck at the G1 boot screen but can't get into recovery or fastboot, adb or anything. In cases where you can still get to other phone options to start over, rest assured your phone does still work, just need to step back and figure it out, which you did in this case with a little help ^-^ First few times doing anything to my phone, I went into panic mode a couple of times thinking I bricked until I read around and found out otherwise.
Just in case you didn't know these things, if you did, well, hope it was a nice read? ^-^
doctorfugazi said:
ok...so i went back to the original method for obtaining root. i was so frustrated last nite that i ended up trying to combine 2 slightly diff methods. at this point i call them the telnetd method and root.apk method. correct me if im wrong but niether one mentions the other. so i make it to the bootloader running the root.apk it runs thru the list and the fails at radio_v2. now im on the white screen wuth the skateboarders, the radio #says 1.22.12.29. so i run it again i
now im on the rgb screen at proceeds to attept the update again. this time the dreaimg.nbh fails. i'm not freaking out. im good. because i know im almost there. feedback appreciated. thanks in advance.
y'know i never thought about this..but if i reverted a dev phone to factory settings...did i relock everything? and for the record, i only have a mac. if that matters at all.
Click to expand...
Click to collapse
Well... if you actually purchased a dev phone it should not be sim locked.
Technically... after the rooting process, we all have dev phones with the exception of the sim lock.
So... what SPL are you using?
What ROM are you trying to install? Some roms you should consider partitioning your sdcard.
What radio do you have?
First thing is first.
Get the 1.4 recovery if you haven't done so already. 1.4 Recovery
Because this allows you to select any .zip file without having to rename it to update.zip. This saves on confusion so you don't try flashing a spl (like danger spl )before a radio (could brick your phone).
Second
You need the 1.5 radio to use cupcake. 2.22.19.26I
Third
Consider an spl. You have 4 choices. HARDSPL (Recommended), Eng SPL (what the dev phone defaults with.. skateboarding androids), the standard spl (nondev) and Danger SPL (risk bricking but worth it because you have more memory for your ROMs and can try HERO builds).
Fouth
Find your rom. NOTE: Read each post carefully! If it says you need a specific spl then get it! Otherwise it won't work. Some require the Danger SPL. If you chose a JF rom then you should be alright and don't even need to partition your card and it will work just like the OTA release. Some (such as Cyanogens 3.9.7) are experiemental and are not recommended for noobs.
Fifth (and probably the most important)
ALWAYS BACKUP WITH NANDROID!!!
In the event that you think that you've bricked your phone. I would say that there is a 90% chance that you didn't. As long as you have a nandroid backup and can get to the bootloader then you still have a phone. Just make sure the fastboot.exe file is in your sytem32 directory of your computer. Open CMD and cd to your fastboot backups saved on your computer. Simply
fastboot flash boot boot.img <enter>,
fastboot flash system system.img <enter>,
fastboot flash userdata data.img <enter>
fastboot reboot <enter>
and you should be back to where you were immediately after the point you backed up. Think of it as a system restore for Windows. It couldn't hurt to have a few backups stored.
If you have any questions or problems include information for us to read in a single post and edit as necessary.
Example:
AT&T
Cyanogen 3.9.7 Rom
Recovery 1.4
HARD SPL
Radio 2.22.19.26l
8GB class 4 sd card (7gb fat32/900mb ext3/100mb swap)
Theme version if any.
That way we know what we are working with.
Happy flashing.
rest assured i was in panic mode yesterday. but honestly the only thing i could really do was just step back for a while, meaning get some rest tackle it with a clean head. its frustrating for sure. this one guy tho who posted in the brick think tank thread...just cuz he couldnt figure things out in an hour he got pissed and started screaming waste of time this that and the other. total BI$CH! I was like whoa. I was at that point too. but Im not tryna be that guy.
Now, if could just figure out if i have to start from scratch, i just might be able to get my phone working again in time fro me to go to work tmrw morning.
So... what SPL are you using?
the hard SPL found here
What ROM are you trying to install?
Well i was trying to follow suggestion on something simple, like one of the early jesusfreke's. if i can step it up sure why not. but i'll pass on the partitioned sdcard setup for now.
actually I'll run with JesusFreke JFv1.51 US CRB43
What radio do you have?
radio number listed in my previous post.
Hey thanks by the way for taking the time out of your day to respond to this. i know u guys get your fair share of spazmiesters, so i appreciate it totally.
after doing research it seems that all the current roms require partitioning. or is that optional just for running apps to sd?
partitioning is optional of apps2sd for preformance. some like myself have three partitions, the third being for a linux swap
Ok ive final decided on the dudes cupcake 101. the ? i have now is do i start from scratch. im kind of in limbo as i'm stuck on the bootloader. if remember correctly i got half way thru the root process and it went down hill from there.
TMobile
RC29 / previously Dev 1
Recovery 1.4
HARD SPL
Radio currently 1.22.12.29 / trying to get to 2.22.19.26l
4gb card
(hope i did that right)
doctorfugazi said:
Ok ive final decided on the dudes cupcake 101. the ? i have now is do i start from scratch. im kind of in limbo as i'm stuck on the bootloader. if remember correctly i got half way thru the root process and it went down hill from there.
TMobile
RC29 / previously Dev 1
Recovery 1.4
HARD SPL
Radio currently 1.22.12.29 / trying to get to 2.22.19.26l
4gb card
(hope i did that right)
Click to expand...
Click to collapse
Okay... you have the recommended recovery and spl.
So all you need to do is get your rom and radio and store the zip files to the root of your sdcard. You don't need to rename them.
Just boot in recovery (power+home) and scroll down to:
[Alt+A] apply any zip from sd
And then you should see the zip files.
Upgrade your radio first.
Then your rom.
Another note... make sure you have a data plan once you've installed your rom. Depending on your rom version, you may not be able to sign in without one. If you can't sign in, you can't use your phone which is why most would recommend a custom rom or an adp rom.
Now... if I'm not mistaken... you do NOT have to partition your sdcard to install a rom (unless it's a HERO rom).
You may want to consider doing so however.
The advantages are that you can have virtually unlimited storage for apps and it's much easier to restore them after a wipe because they are still on your sdcard. Some apps will recognize the partitioned sdcard and automatically do all the apps2sd work for you by default. It is also recommended that you use at least a 2gb class4 card at MINIMUM. Any slower then a class 4 may result in system crashes and errors. Any less then a 2gb card is almost not worth all the effort since you'll likely be using at least a quarter of it for the apps2sd. I would suggest buying at least a 8gb class 6 card for less then $50 online. It's both fast and plenty of storage. With apps to sd, if you do need to wipe you still have all of your apps installed. A great advantage of having apps2sd.
Also... try different roms! There are DOZENS out there! Some have the htc music installed, some have myfaves, some have special cameras, etc. Don't be afraid to experiment. As long as you have a backup and can get to the bootloader (skateboarding androids) and a pc, you can't go wrong! If fact... with the 1.4 recovery you can store several different roms on your sdcard, backup your current rom, wipe, flash a new rom to try it, wipe, flash a different rom to try that one, etc. If you decide that you didn't like any of those... just restore back to your previous backup. Simple as that. No pc needed. However having a pc is handy to get logcat information if it's not booting for some reason.
Speaking of roms not booting... while your experimenting with various roms... you MUST have patience. Sometimes (based on my personal experience with about 10+ different roms) they can take up to 15 minutes to boot up. You can literally be staring at the ANDROID or HTC logo this entire time. Unless you are using ddms.bat or adb shell logcat, you will be clueless of whats going on. DO NOT do anything unless you get the infamous "boot loop". This will be obvious. It will stick at the ANDROID or HTC screen for a while and then blink and go back to the logo. If you see it blink and go back to the logo then try pressing power + talk + menu to restart it and then immediately press the home button to bo back to recovery. Wipe... try again. This time it should work. If it doesn't then restore your backup while you research on that partitcular rom. You may have skipped a step or not have the proper requirements (partitioned card, spl, etc).
With all of that said... good luck and you'll be posting help to other users like yourself before you know it.
Hey Doc, if I'm not mistaken (other guys correct me if I'm wrong), if all, and I mean ALL you have is a boot loader (AKA SPL. ie// skating androids or colored bars) you need to reflash dreaimg.nbh to get a system back.
This ALSO flashes your SPL and RADIO back to default so reflash your radio and SPL afterward. (IN THAT ORDER I HOPE)
Binary100100 is a gentleman and a scholar
nicely written response binary.
I can't stress enough how helpful it is to have the sdk working on a computer when flashing new roms. Get ADB working, it'll save you a ton of headaches.
innerspace said:
nicely written response binary.
I can't stress enough how helpful it is to have the sdk working on a computer when flashing new roms. Get ADB working, it'll save you a ton of headaches.
Click to expand...
Click to collapse
Thank you! I do what I can.
Ok, i have a need for a bit of help. I rooted and flashed to Jesusfreaks adp. I tried to get it to RC33. LONG story short, JF is installed. My kernel is 2.6.27-00392-g8312baf
NO clue what that means but im at fireware 1.5 and Build number CRB43
I want to get to Cyanogen. It looks a little smoother then JF and more frequently update. BTWi have a G1
I followed this guide TO THE T!
simplehelp.net/2009/10/04/how-to-install-cyanogenmod-4-1-99-on-your-g1-android-phone/
and after i rebooted, it took forever to boot (which is usual)
All my apps crashed. My desktop didnt even load. It had force closes like *android.phone and *android.mail
I figured it was because i was trying to mod off of the Jesus freak setup. Can anyone help me out and tell me how to either COMPLETELY wipe my phone and restore it to its origional G1 official build and then i can re-root to Cyanogen OR a way to mod from Jesusfreak to Cyanogen
copy and paste this into your browser... follow the directions...
wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod[/url]
Just read that guide over and thats all exactly what i already did. I have tried to signed-dream flash and then after taht the cyan mod. It installed the OS no problem. It just didnt have any programs working. IT is as if the phone had the OS but no program files. It wouldnt even load the phone at all. it was a black screen with a status bar and infinate force close screens. Any idea what that is a result of? I had to flash recover back to my JF os
Try this:
1. Flash recovery Amon_Ra (Great improvment on JF and Cyans recovery)
Code:
Copy recovery-RA-dream-v1.5.2.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
select console from the menu
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-dream-v1.5.2.img
2. Boot into recovery (Home+Power)
3. Wipe Data/Factory Reset
4. Wipe EXT
5. Repair EXT
6. Flash Super D (I suggest Super D only because there is less flashing involved and it's a great improvement on the Cyan roms.. super quick too)
From here you should be set.
so if i already have root and all that, do i still need to follow step 1? Like flash with Amon_Ra? or can i just wipe, and reload the D rom? also your rom says its myHero2.2? is that a good rom? Im just trying to find the best rom to use on a g1. I have read up on Jesusfreak, its very stable, but it is pretty much just a open version of the regular tmobile os. THe only difference is the apps store is an older version. In your opinion, what is the best G1 rom and what are its percs?
thanks for all your help. This has been a working progress haha, finding a good rom and sticking with it. and can you give me a list of all the files needed for the best rom? if they have a step by step guide to it, thatd be great! i would look myself, but im still new at all this and there are like a bajillion different roms/ ways to load the rom. Im a PSP hacker, not an experienced phone guru
Tigger166 said:
so if i already have root and all that, do i still need to follow step 1? Like flash with Amon_Ra?
Click to expand...
Click to collapse
I would just so you're current on your recovery. The updated recovery has added features compared to JF's recovery
Tigger166 said:
or can i just wipe, and reload the D rom? also your rom says its myHero2.2? is that a good rom?
Click to expand...
Click to collapse
I would load the new recovery and then flash Super D. Again it's the most stable and is wicked fast. Yeah used to use myHero2.2 but i haven't updated my sig in a while. It's getting mundane at this point.
Tigger166 said:
Im just trying to find the best rom to use on a g1. I have read up on Jesusfreak, its very stable, but it is pretty much just a open version of the regular tmobile os. THe only difference is the apps store is an older version. In your opinion, what is the best G1 rom and what are its percs?
Click to expand...
Click to collapse
This is going to be more of a difficult question to answer. It just depends on what you're after. I really prefer Super D because of it's speed. Again its built from the Cyan roms so you get Cyan + extras. That's what I would go with. Simple, easy, and fast.
thanks for all your help. This has been a working progress haha, finding a good rom and sticking with it. and can you give me a list of all the files needed for the best rom? if they have a step by step guide to it, thatd be great! i would look myself, but im still new at all this and there are like a bajillion different roms/ ways to load the rom. Im a PSP hacker, not an experienced phone guru
Click to expand...
Click to collapse
Well that's the cool part about the community here at XDA. All the files are set up for you. To flash a rom:
Code:
Download the .zip file and place it on the root of your sd card
Reboot into recovery
Make a backup (i prefer switchrom)
Wipe Data/Factory Reset
Wipe EXT
Repair EXT
Flash rom from .zip
Reboot.
It's that easy.
I've been on XDA today for atleast 3 hours and havent gotten anywhere, I have owned my G1 since dec. 08, rooted it, and kept the firmware at 1.1. I have jesus freak recovery 1.41.
Like I said, I've been on XDA forums for 3 hours already and haven't had any clarity what so ever and am just frustrated right now. Without being 100% I managed to upgrade to 1.6 withy cyanogen 4.2.15.1 I lost everything that was on my phone, it hurts but I'm just frustrated to the point right now that the phone is functioning slower than before and theres lag between the screens and functions. With the upgrade, all of the phones original fucntions "contacts, alarm clock, calculator, etc." force closed and nothing worked, i tried to factory reset and because of the stupid sync issue from the begining skrewed me and about half of my info saved to my google account. I'm so frustrated right now.
I need to know how to install the newest recovery to hopefully work with Nand because I had to Manually rename the DRC83_base_defanged to update.zip and then had to manually rename update-cm-4.2.15.1-signed to update.zip to install each one at a time without having the ability to freely choose what zip i wanted to install.
I haven't been able to find what issues there are with using another phones firmware on the G1, i've seen the Hero firmware, the home screen looks gorgeous and runs like a dream, but I haven't been able to find anything saying that it is okay or a BAD idea to attempt to install it, also I havent been able to find any info on finding the newest g1 firmware or any mods to be able to make the g1 firmware look like the hero, or any other android platforms. I have just found constant cooked firmware after firmware with a hard time decyphering why one may be better than the other. If someone could help me, I would GREATLY appreciate it.
I continute to run into threads "how to root" or "down load this, and download this, and assuming you have something with options you dont have, make it work like this"
Please someone help.
First you need to upgrade your recovery b/c the one you have is very very Ancient with a capital A....You have to wipe before you flash the defanged then flash cyan w/o rebooting.
I want to upgrade my recovery, but I haven't found anything that can help me upgrade the thing. any links to tell me how to do it? and is there no order that I have to install the firmware? instead of having to go from 1.1 to 1.5 to 1.6, can i just go from 1.1 to 1.6 in one hit?
step 1: search the development forum for amon ra's recovery. read the instructions to flash it.
step 2: go to cyanogenmod.com and read the instructions for upgrading from scratch.
once you've done those two things, you'll be much happier.
maniacallyhappy said:
I want to upgrade my recovery, but I haven't found anything that can help me upgrade the thing. any links to tell me how to do it? and is there no order that I have to install the firmware? instead of having to go from 1.1 to 1.5 to 1.6, can i just go from 1.1 to 1.6 in one hit?
Click to expand...
Click to collapse
You don't re-root when you need to change roms you just wipe in recovery mode
You need amon_ra
http://forum.xda-developers.com/showthread.php?p=4647751#post4647751
Like the other guys have said, upgrade to Amon_RA recovery. This allows you to flash updates from any filename, not just update.zip. The link is in my signature, or it's on the G1 Dev Forum in the sticky threads.
After that, boot into recovery and go to the Wipe section. Wipe all the things there, not just data. I never used to wipe everything either and I found that was the source of alot of my problems when changing ROMs. Obviously if you have your SD card partitioned and you choose to wipe your ext then you will lose what is on there.
Cyanogen has good instructions on his Wiki, but basically you want to flash DRC83_base_defanged, DO NOT reboot, and flash CM over the top straight away, then reboot your phone and you'll have a nice clean CM install.
This flashes the HTC Developer image which includes legal Google apps (Gmail, Maps, etc) and then flashes CM over the top which includes all his cool changes but does not delete the Google apps which we aren't supposed to distribute because it's illegal. Perhaps you are not aware, but Cyanogen got a Cease & Desist letter from Google, which is why we now do the defanged base method. More ROMs are moving to this method as time goes on, Pay's ROM and Super D are two which do this.
As an aside, I have found CM is not the fastest ROM. Some people have had better success with a ROM called Super D which is quite popular and includes many of the Eclair bits and pieces which CM does anyway. I personally use Dwang's ROM which is a much more plain Donut image however it absolutely flies. Both of these are linked in my sig, and are usually within the first few pages of the G1 Dev Forum anyway.
Thank you guys so much! I really appreciate how helpful the community has been. I've been having some issues with the the upgrading and maintaining because of my memory card slot dying out. A lot of the times the system will not register that I have my micro sd card in it or it'll say the sd card is blank. I just hope the phone lasts the extra 6 months till the end of my contract
Sent from my T-Mobile G1 using XDA App
maniacallyhappy said:
I've been having some issues with the the upgrading and maintaining because of my memory card slot dying out. A lot of the times the system will not register that I have my micro sd card in it or it'll say the sd card is blank.
Click to expand...
Click to collapse
I used to have this problem too, but it went away when I moved to 1.6 (coincidentally the same time I replaced the SD Card that came with my phone with a new Class 6 card). So either the upgrade of the OS or the SD Card fixed it.
In going to have to try the new men card cause the system is already at 1.6 but the phone is still trying to kill itself.
Sent from my T-Mobile G1 using XDA App
Hi guys,
The power button on my nexus one died, and I tried to get the phone replaced by htc singapore.. but all efforts were futile. So they replaced the "Rigid FLex" jacket for free and gave me back the phone..
I dont really have any complaints, other than the power button still feels flimsy and I dont trust it, since it causes a lot of inconvenience.
NOW, can I use the volume key or trackball to wake the phone up ?
Would any of these buttons Die like the power button (are they equally flimsy ? )
Ive been reading on custom-roms which will add trackball-wake-up option..
-Could you point me to the most stable rom? (Im running froyo frf91)
-If rooting is required, could you point me to a newbies guide to rooting..
Thank you
abstrucity said:
Hi guys,
The power button on my nexus one died, and I tried to get the phone replaced by htc singapore.. but all efforts were futile. So they replaced the "Rigid FLex" jacket for free and gave me back the phone..
I dont really have any complaints, other than the power button still feels flimsy and I dont trust it, since it causes a lot of inconvenience.
NOW, can I use the volume key or trackball to wake the phone up ?
Would any of these buttons Die like the power button (are they equally flimsy ? )
Ive been reading on custom-roms which will add trackball-wake-up option..
-Could you point me to the most stable rom? (Im running froyo frf91)
-If rooting is required, could you point me to a newbies guide to rooting..
Thank you
Click to expand...
Click to collapse
cyanogen rom can do trackball wake up...trackball unlock...and pressing menu will lock your phone..
i suggest you to download rom manager from market...
and dont forget to learn about how to unlock and rooting your phone..
or you also can root your phone without unlock your phone...
use search function..you can find a lot resource to root your phone
http://forum.xda-developers.com/forumdisplay.php?f=559
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One
harunjo said:
cyanogen rom can do trackball wake up...trackball unlock...and pressing menu will lock your phone..
i suggest you to download rom manager from market...
and dont forget to learn about how to unlock and rooting your phone..
or you also can root your phone without unlock your phone...
use search function..you can find a lot resource to root your phone
http://forum.xda-developers.com/forumdisplay.php?f=559
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One
Click to expand...
Click to collapse
Thanx..
I did use the search button, but it gave me tonns of threads, with a 100 pages in each..
So I had to start this thread.
My phone is unlocked.. (sim-free)..
There is no SIM-locked Nexus in existence, as mentioned multiple times. "Unlocked" stands for "Unlocked bootloader", doesn't have anything to do with SIM. Yours is locked, since you just got it and never unlocked it.
I suggest you read the Wiki instead of continuing this thread, read all the guides, use 1-click root application and DO NOT use ROM Manager. Learn to install the custom recovery yourself, and to install ROMs using the recovery. Everything is written in the Wiki.
The most stable yet heavily customized Froyo ROM would probably be Enomther's, which I personally use.
Jack_R1 said:
There is no SIM-locked Nexus in existence, as mentioned multiple times. "Unlocked" stands for "Unlocked bootloader", doesn't have anything to do with SIM. Yours is locked, since you just got it and never unlocked it.
I suggest you read the Wiki instead of continuing this thread, read all the guides, use 1-click root application and DO NOT use ROM Manager. Learn to install the custom recovery yourself, and to install ROMs using the recovery. Everything is written in the Wiki.
The most stable yet heavily customized Froyo ROM would probably be Enomther's, which I personally use.
Click to expand...
Click to collapse
Thanks for the clarification.
Hi, i was reading and stumbled on Softroot.
I cannot find more info on it..
Its apparently, temporary rooting.. like jailbreaking..
Can I do a softroot to achieve the track-ball wakeup ?
Use Universal Androot.
There is no "temporary rooting", and rooting isn't equal to jailbreaking, it's a different thing, done for different purposes. Rooting is permanent, otherwise it's worthless. Having 1 session of root access (until reboot) doesn't accomplish anything, unless all you want to do is delete some system application or something of the sort.
@jack_R1
Hi, I used the 1Click Androot app to Root my device. Im backing up apps and settings using titanium backup.
My next step is to flash the custom rom.
Im deciding between Enomthers 2.11.3 NOT Pre_Themed ROM, and Nightly's CM6 for Nexus one..
So to clarify things, I need to
1 rename the Custom rom to Update.zip and paste it to the Root of SD card.
2 Rename the Amon recovery image to recomevry.img and paste to root of SD.
3 Turn on the phone while holding Volume Down
4 Select "BOOTLOADER" from the menu
5 Select "RECOVERY" from the menu
6 Select "Flash update.zip" or "Flash ZIP file"
7 Turn off verification, if such option is presented
8 Select your downloaded ROM image
9 Wait for the flash to finish successfully, if it didn't - do not continue!
10 Return to main recovery menu
11 Select "Wipe"
12 Select "Wipe data / factory reset"
13 Select "Wipe Dalvik cache"
14 Return to main recovery menu
--> Reboot the phone
?
Is there anything missing? please lemme know. I wanna do this asap.
Also, Im already updated to Froyo Radio (v4.06...) so I do no figit with radio .. correct?
-Also, when do I configure SpareParts? (before or after flashing) ?
-What is the difference between pre-themed black text and pre-themed white text? (black notification bar with white text on top)?
Thanks!
You got some things confused.
1. No need to rename it. Using custom recovery lets you flash anything with any name.
2. Since you rooted using 1-click root, you don't have a recovery yet. You need to flash it before you reboot to it. Read and execute: Nexus One Wiki / Recovery Images / Amon_Ra's Recovery / using flash_image method. Link for your convenience. You could also go to Developer section and download the latest 1.8.0.1 Amon_Ra's recovery instead of 1.7.0.1 in the Wiki. I'll update the Wiki to give a choice between the two.
3. Continue your list till the end.
Nothing needed for the radio, if you're already on 4.06.
Spare Parts will appear only after flashing the ROM.
Pre-Themed black text is regular, white text is for black notification bar - just as you wrote.
Personally, I run Enomther's since Froyo is out. Before that I was using CM. You might try them both and see which you like more.
Well, thanks for the reply.. Ill look into it after the ADB hurdle.
Presently, Im stuck at the ADB step..
I got the android sdk package, got nexus one drivers.. but for whatever reason, it wont show my device in cmd prompt..
I have pretty much memorised the adb for beginers guide.. but no luck..
(Im on Win Xp)
This is turning out to be a pain in the rear end..
You don't need ADB to flash recovery.
Follow the guide I've pointed you to.
Return to ADB once you're already on the custom ROM, it won't run away.
Flashing the recovery image was quite a task!
Luckily I googled and stumbled on a thread where YOU mentioned to download and install BusyBox.
So yes, Ive flashed it finally..
Im downloading the Enomthers ROM now.. slow net connection.. will load it in a while if it allows.
Thanx a bunch!
hi..
Done installing custom rom.. it was pretty staright forward once recovery img was flashed.
I would like to add some info, for someone who stumbles on this.
In recovery options,
For backup/Restore.. when you select Nand+Ext, and end up getting 'Error...Run nandroid-mobile.sh', press back to goto the main menu, toggle USB MS (mass storage) on, plug it to the computer, delete the nandroid folder, and try again.
If you still get the error, delete nandroid folder, and this time select 'Nand backup only'. if succesful, proceed to copy the nandroid folder to your computer.
So far Ive installed themed enothmer rom.. and its decent.
Will customize it tomo..
For the time-being, ive noticed one issue/bug .. the LED light blink interval is too quick even on selecting 'Slow'.
Thanx Jack!
You're welcome.
Thanks for reminding about the need for busybox to execute chmod and such. Added to Wiki instructions.
Hi,
Now that Ive successfully flashed a custom rom, and its working fine..
I noticed an update to enomthers rom. (v2.12.2)
I want to flash this rom, so do I have to re-flash recovery? and then flash this new rom?
Or just flash the new rom? but then do I wipe/factory reset and wipe Dalvik cache of the device?
Actually restoring the data (especially mesages and apps) is quite an issue, it takes a while (considering im on EDGE)..
also, is it recommended to make an apps2sd partition on SD card? I did get low memory warning on internal memory.
and last, I just want the black status bar and 'some' custom icons (not all), so is there a way to install these on otherwise stock looking enomther rom?
I know they are some noobish questions but I need answers..
Thanx
You don't touch the recovery once it's flashed, as long as it's working. You just flash the ROM using the recovery that you already installed. And don't do any wipes - so you won't have to restore the data.
Apps2EXT (EXT2 partition for apps on SD card) is great and highly recommended.
You can apply themes, simple as complex, using morphs.
Hi Guys,
Need your opinions again.
I was extremely satisfied with Enomthers 2.14.4 rom, till the update notifiation appeared.
Ive waited long enough for an update from Enom, but he has his reasons, and I dont see an update in the pipeline.
So I need to get a new rom & it should have have trackball wake up/vol keys wakeup (cant afford to break the power key).
Also Gingerbread, and Apps2SD (+).
Now Ive come across two roms,
a) Nightly's CM rom
b) GRI40, system dump + unmodified stock n rooted rom.
So which one should I get?
Also whats the difference between nightlys CM rom and CM rom ?
Also, I see I need to update the radio, so this has to be done before flashing rom or after?
I have flashed AMON RA's recovery 2.0, do I need to flash anything else?
Remove the update notification and return to being happy.
Sent from my Nexus One using XDA App
Stock GRI40 doesn't have any mod for trackball/volume wake. So for now you're out of options - you have to use a custom compiled AOSP Gingerbread, which point you towards CM7/SuperGinger/Leo's Ginger/etc. Currently none of those are as stable as Enom's (I've tried 2 of them).
I can also suggest flashing FOTAKill (use Google to find, learn and download) and keeping with Enom's. That's what I'm doing now. And after a brief experience with MyTouch 4G, I'm seriously considering flashing Froyo Desire port.
Thanks for the prompt replies. Really appreciate it.
For now I can live with enomthers rom. Its not giving any issues. Its got everything I need, other than gingerbread.
the Gingerbread update is glued to the taskbar, and doesnt pop-up at all (doesnt intervene/hinder ) in regular operations.
So ill patiently wait as well
thanks again guys!