Related
Hi guys
So after unsuccessfully trying to root my G1, I changed my mind on the mastter and decided to keep it stock OS. I managed to get back to Android 1.0.
I’ve put a formatted and FAT32 SD card in the phone, with RC8 (UK phone) on it named update.zip (file ext hidden in windows).
I boot up the phone holding home key, ALT L then ALT S. It boots successfully saying things like ‘package verified’ etc until it says ‘install complete’. Then it says ‘press home+back to reboot your phone. When I do that it says ‘writing radio image’ then reboots. When it turns back on it has a picture of a sim card and an arrow or a phone and a box then reboots again. And here lies the problem: it never leaves the G1 screen (the first screen displayed when powering on the device. I’m able to power into recovery mode and fastboot mode, and from fastboot mode I can recover the phone by flashing to 1.0 via DREAIMG.NBH, but I really want to be running 1.6.
Can anyone help?
Many thanks
What phone are you using...a UK G1 or a US G1, as your trying to flash a UK rom...(rc8) have you tried flashing RC29? After flashing to android 1.0 it will prompt you to update your phone to 1.6 after that.
Tranquility__89 said:
Hi guys
So after unsuccessfully trying to root my G1, I changed my mind on the mastter and decided to keep it stock OS. I managed to get back to Android 1.0.
I’ve put a formatted and FAT32 SD card in the phone, with RC8 (UK phone) on it named update.zip (file ext hidden in windows).
I boot up the phone holding home key, ALT L then ALT S. It boots successfully saying things like ‘package verified’ etc until it says ‘install complete’. Then it says ‘press home+back to reboot your phone. When I do that it says ‘writing radio image’ then reboots. When it turns back on it has a picture of a sim card and an arrow or a phone and a box then reboots again. And here lies the problem: it never leaves the G1 screen (the first screen displayed when powering on the device. I’m able to power into recovery mode and fastboot mode, and from fastboot mode I can recover the phone by flashing to 1.0 via DREAIMG.NBH, but I really want to be running 1.6.
Can anyone help?
Many thanks
Click to expand...
Click to collapse
That's because you didn't flash your SPL yet.. I'll edit this post with the link to it. Oh and before I do, which rom are you trying to flash?
protomanez said:
What phone are you using...a UK G1 or a US G1, as your trying to flash a UK rom...(rc8) have you tried flashing RC29? After flashing to android 1.0 it will prompt you to update your phone to 1.6 after that.
Click to expand...
Click to collapse
Thanks for the suggestion protomanez - it's a UK G1.
xAbstract said:
That's because you didn't flash your SPL yet.. I'll edit this post with the link to it. Oh and before I do, which rom are you trying to flash?
Click to expand...
Click to collapse
That sounds promising I'm trying to flash UK 1.5 RC8. So I have to install this SPL first and then install the software? I'm correct in jumping straight from 1.0 to 1.5 right?
Tranquility__89 said:
That sounds promising I'm trying to flash UK 1.5 RC8. So I have to install this SPL first and then install the software? I'm correct in jumping straight from 1.0 to 1.5 right?
Click to expand...
Click to collapse
Do I need to flash this SPL? The bottom one on this page http://code.google.com/p/android-roms/downloads/list?q=label:SPL
it's called G1originalBootloadernocheck.zip or something similar
I wouldn't trust that, but I don't know just hold on. Wait a minute, so you flashed the RC8 rom? Are you sure, how long did you wait at the T-mobile G1 screen for? Try flashing RC8 again and let the phone do it's thing. Wait a max of 10 minutes for the phone to load.
Tranquility__89 said:
That sounds promising I'm trying to flash UK 1.5 RC8. So I have to install this SPL first and then install the software? I'm correct in jumping straight from 1.0 to 1.5 right?
Click to expand...
Click to collapse
I'm hoping that you're rooted at 1.0.. And nono, you flash radio first, then SPL THEN the rom.
xAbstract said:
I'm hoping that you're rooted at 1.0.. And nono, you flash radio first, then SPL THEN the rom.
Click to expand...
Click to collapse
He's trying to go back to stock, not flash a rom :U.
Tranquility__89 said:
That sounds promising I'm trying to flash UK 1.5 RC8. So I have to install this SPL first and then install the software? I'm correct in jumping straight from 1.0 to 1.5 right?
Click to expand...
Click to collapse
... sounds like he wants to flash.
-EDIT-
Why would he want to go back to stock if he flashed 1.0? Isn't that the first thing you do when you root?
After you flash DREAIMG.nbh, give the phone a few days and it will update over the air.
xAbstract said:
... sounds like he wants to flash.
-EDIT-
Why would he want to go back to stock if he flashed 1.0? Isn't that the first thing you do when you root?
Click to expand...
Click to collapse
He said he changed his mind because he tried to root but he failed so he's trying to go back to stock OS.
protomanez said:
He said he changed his mind because he tried to root but he failed so he's trying to go back to stock OS.
Click to expand...
Click to collapse
Oh my bad. My lack of attention span prevented me from reading that but to go back to the stock, do what cloverdale said. Reflash your G1 with the RC8 and WAIT for the update. There's no need to do it manually.
Thanks guys! Yes the root looked like it was about to brick my phone so I abandoned it and was feeling overwhelming relieved to even get normal OS back on my phone. So I should just wait for the over the air update (in the UK) and it will automatically bring it up to 1.6 again? Sorry for the late reply, my internet has only just started working, and itll be off again soon!
Why not do it manually btw guys?
Yeah you can just do what cloverdale said, or you can go to the settings(pick it by pressing menu on the phone) and scoll all the way to the bottom to "about phone" I believe there will be an "upgrade" option but I'm not quite sure . You can do it manually by dling the upgrade off the internet somewhere but it's probably better(on the safe side) to just download it from your phone.
Tranquility__89 said:
Thanks guys! Yes the root looked like it was about to brick my phone so I abandoned it and was feeling overwhelming relieved to even get normal OS back on my phone. So I should just wait for the over the air update (in the UK) and it will automatically bring it up to 1.6 again? Sorry for the late reply, my internet has only just started working, and itll be off again soon!
Why not do it manually btw guys?
Click to expand...
Click to collapse
Yes, just give it some time and it will update to 1.6 (or maybe 2.0/2.1). I would suggest waiting of the OTA update and not doing it manually simply because I what I read about your reactions to rooting. I am not trying to be mean when I say this, but the stress it seemed to cause from starting the rooting process may be recreated through a manual flash. Take life easy, relax, and it will update very soon.
OK, no offence taken. I didnt know 2.0 was out for the G1 yet..
I think my rooting went wrong because I didnt flash a radio image or SPL prior to the software - I tried to complete it with limited net access and therefore information, and a non working phone and non working internet is too much of a hinderance as i need these things every day.
I mainly wanted to root it to make the higher end 3d games run smoother via overclocking and use it as a wifi point so i could access the net properly again whilst BT stop ****ing around.
Hi all, I've searched for help on this and not found anything, please don't crucify me if the solution is extremely simple. I wanted to post my problem in the relevant thread but it wouldn't let me do that so I made a new one.
My girlfriend recently won an Incredible S in a competition here in Shanghai. Great phone but it seems that the Chinese ROM is crippled in some ways - most importantly no Google syncronisation. She can set up her Gmail account in the usual way but it doesn't sync her contacts/calendar/email etc. like her Desire does. It's also got a bunch of Chinese crap that she doesn't need (Weibo, RenRen, etc.).
All I want to do is put a non-Chinese stock Sense ROM on it. I don't really care about custom ROMs as she really likes the Sense UI. It's currently running Gingerbread 2.3.3.
So I downloaded the 2.3.3 Virgin Mobile Australia ROM from this thread (since it seemed to be the most popular and apparently is free from any Virgin Mobile branding or bloatware). I researched and realised that I need to make a gold card. I did this using Goldcard Tool 0.7, and I double-checked with a hex editor that it was correct according to the .IMG I got from the site where you input your CID and get the IMG. Everything seems to check out.
So now I have the gold card in the phone, I connect it with USB debugging on, and put it into mass storage mode (I've tried in charge only mode too, didn't work). I then run the Virgin Mobile RUU file on my Windows 7 PC (RUU_Vivo_Gingerbread_S_Virgin_Mobile_AU_2.12.981.2_R_Radio_20.2803.30.085AU_3805.04.03.12_M_release_185029_signed).
And every time I try, I get the same error: Error [131]: Customer ID error.
I researched this and it seems this is what happens if you try to flash another carrier's ROM to your phone without a gold card. The full error text is "The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
I also note that the Virgin Australia ROM has a lower version number (2.12.981.2) than the ROM that is currently on the phone (2.21.1400.8), could this be the reason why it won't update?
My main question is... what do I do from here to get the Virgin Mobile ROM running on the phone? Is it possible that they've made this phone so you can't flash any other ROM on it, even with a gold card?
Apologies for any noobishness. I have spent hours researching this, but to no avail. I previously rooted my girlfriend's HTC Desire and didn't have too many issues (and learned a lot about Android in the process), but this seems to be kicking my ass as I'm following instructions to the letter and it's still not working.
Any advice? I would really appreciate any help.
kinggimped said:
Hi all, I've searched for help on this and not found anything, please don't crucify me if the solution is extremely simple. I wanted to post my problem in the relevant thread but it wouldn't let me do that so I made a new one.
My girlfriend recently won an Incredible S in a competition here in Shanghai. Great phone but it seems that the Chinese ROM is crippled in some ways - most importantly no Google syncronisation. She can set up her Gmail account in the usual way but it doesn't sync her contacts/calendar/email etc. like her Desire does. It's also got a bunch of Chinese crap that she doesn't need (Weibo, RenRen, etc.).
All I want to do is put a non-Chinese stock Sense ROM on it. I don't really care about custom ROMs as she really likes the Sense UI. It's currently running Gingerbread 2.3.3.
So I downloaded the 2.3.3 Virgin Mobile Australia ROM from this thread (since it seemed to be the most popular and apparently is free from any Virgin Mobile branding or bloatware). I researched and realised that I need to make a gold card. I did this using Goldcard Tool 0.7, and I double-checked with a hex editor that it was correct according to the .IMG I got from the site where you input your CID and get the IMG. Everything seems to check out.
So now I have the gold card in the phone, I connect it with USB debugging on, and put it into mass storage mode (I've tried in charge only mode too, didn't work). I then run the Virgin Mobile RUU file on my Windows 7 PC (RUU_Vivo_Gingerbread_S_Virgin_Mobile_AU_2.12.981.2_R_Radio_20.2803.30.085AU_3805.04.03.12_M_release_185029_signed).
And every time I try, I get the same error: Error [131]: Customer ID error.
I researched this and it seems this is what happens if you try to flash another carrier's ROM to your phone without a gold card. The full error text is "The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
I also note that the Virgin Australia ROM has a lower version number (2.12.981.2) than the ROM that is currently on the phone (2.21.1400.8), could this be the reason why it won't update?
My main question is... what do I do from here to get the Virgin Mobile ROM running on the phone? Is it possible that they've made this phone so you can't flash any other ROM on it, even with a gold card?
Apologies for any noobishness. I have spent hours researching this, but to no avail. I previously rooted my girlfriend's HTC Desire and didn't have too many issues (and learned a lot about Android in the process), but this seems to be kicking my ass as I'm following instructions to the letter and it's still not working.
Any advice? I would really appreciate any help.
Click to expand...
Click to collapse
This usually indicates a bad goldcard. What size SD card did you make the goldcard with? Also, when you ran the GoldCard tool, did you use the MMC0 or MMC1 value? Either way that is the problem because the IncS actually uses MMC2, so you need to use SimpleGoldCard:
http://forum.xda-developers.com/showthread.php?t=970157
tpbklake said:
This usually indicates a bad goldcard. What size SD card did you make the goldcard with? Also, when you ran the GoldCard tool, did you use the MMC0 or MMC1 value? Either way that is the problem because the IncS actually uses MMC2, so you need to use SimpleGoldCard:
http://forum.xda-developers.com/showthread.php?t=970157
Click to expand...
Click to collapse
Thank you SO much for replying! I was using MMC1 (MMC0 didn't work). I will try SimpleGoldCard and report back.
I tried with a 2Gb and a 1Gb card (both Sandisk), neither worked.
Thanks again for your help! Hope it works this time.
Well... progress! I think the gold card is working now, because I'm now getting a different error - Error 140, wrong bootloader. Guess it's back to Googling solutions...
kinggimped said:
Well... progress! I think the gold card is working now, because I'm now getting a different error - Error 140, wrong bootloader. Guess it's back to Googling solutions...
Click to expand...
Click to collapse
That could indeed be due to the fact you are on a 2.21 ROM and you are trying to flash a 2.12 RUU. The HBOOT versions are probably different.
tpbklake said:
That could indeed be due to the fact you are on a 2.21 ROM and you are trying to flash a 2.12 RUU. The HBOOT versions are probably different.
Click to expand...
Click to collapse
Well, I ended up using revolutionary.io to S-OFF the phone and install ClockworkMod Recovery, then tried the RUU again for good measure... and guess what?
IT'S WORKING
It's currently 30% through the "Updating system" phase, which is further than it's got before. There's also a progress bar under the HTC logo on the phone's screen, which hasn't appeared before.
I'll check back once it's worked or bricked the phone. Thanks again for your help!
VICTORY!
Thanks again for your help, mate. Now got the Virgin Mobile ROM up and running, and all the Google stuff is there. She's really happy with it!
Feel free to close this thread now guys, nothing more to see here.
Thanks again tpbklake!
Hello,
I am a newcomer to the Forum and I would be grateful if I could benefit from the experience and the knowledge of the experts.
I have an unlocked HTC G1 phone. I use the ATT network.
I would like to install Gingerbread.
Could somebody give me the direction where I would find a step by step guide to replace my actual Donut version with Gingerbread.
Here are the specs of the phone:
Model number Android Dev Phone 1
Firmware version 1.6
Baseband version 62.50S.20.17H_2.22.19.261
Kernel version 2.6.29-00479-g3c7df37
[email protected]#19
Build number DRC83
well if its a dev phone it should already be rooted so ignore those steps, check and see your radio/spl (power on holding camera button)
your answer here will determine the next step
chances are you need to follow this link _ http://forum.xda-developers.com/showthread.php?t=831139
once this is complete follow the steps here _ http://forum.xda-developers.com/showthread.php?t=882356
if you need more help let me know!
Thank you very much for your reply.
Unfortunately my knowledge in this field is infinitesimal small.
That is why I am looking for a step by step guide.
Maybe I put myself in the wrong forum for my level and my needs. My apologies.
The only thing I know is that my phone does not need to be rooted.
Thank you again for your advice and your time.
Happy New Year to all of us
if your not finding what you are looking for ill see what i can do
first off i need to know your radio/spl - this will help me determine what you need to do next
just type in everything off the screen that will be rainbow colored or have three androids on skateboards
to check the screen, power off your phone, then hold down the power (red button) and the camera button at the same time. tell me what it says...
after you write all of that down press the green, red and menu buttons all at once and the phone will reboot normally.
gunner1937: There is a link I found in another thread for an older version of ROM Manager which will work on Android 1.6. Since you're rooted with a Google ADP phone this might be all you need. But I would go in the menu and do a factory reset.
I upgraded my T-Mobile G1 from stock Android 1.6 to CyanogenMod 6.1 (Android 2.2.1) three days ago following the instructions on http://wiki.cyanogenmod.com/wiki/HTC_Dream:_Rooting
I will stick with it for now. It came bundled with the ROM Manager app.
In the past week I've researched upgrading to Gingerbread and just recently there may be a bug uncovered where the phone no longer goes into Deep Sleep mode. This means the battery usage is not ideal compared to other earlier ROMs. It turns out virtually all Gingerbread Dream ROMs use some code by ezTerry, so they may all have this issue. So.. I think I will hold off on going to a flavor of Gingerbread until I get more info on this possible bug.
In your case I believe I'd do the factory reset, then load this ROM Manager onto it. You'd need to copy the ROM Manager.apk file to your phone's SD card. I would backup the contents of your SD card onto your PC just so you have any files/songs you want, and then format it with FAT32. You can format the SD card from a Settings menu on the phone if you like. I think there's another setting in the menu to allow installing a program from unknown sources. Find that and check it in order to be able to manually install an app like this. Or I dunno, that may not be in the ADP phone. Next you'd need to get on the Android market and get a file manager to be able to dig into the SD card's file directory and install the APK file. I used a text editor called TxtPad Lite which included a usable file manager. Another one is called Astro File Manager. With something like that you can browse the file system to be able to look at the files on your SD card and install ROM Manager. You'd just find the APK file and tap on it.
So then you're reset, got the ROM Manager app that will work on Android 1.6, then you can use it. You want to let it install the ClockworkMod Recovery first thing. It's required and what the app uses to manage installing your ROMs. I myself have never actually used ROM Manager to install a ROM (I did use it to install the ClockworkMod Recovery). I've gone in and out of the app. It asked me to update it, so I did. And I decided to stick with CyanogenMod 6.1 for now. It looks like it's gone through a ton of vetting to get it really honed.
I kind of wanted a more full introduction to flashing the ROMs and stuff and the CyanogenMod guide was great for me. This looks like a relatively painless and less complicated way to safely upgrade and switch out ROMs for you, and I might've done it more or less this way if I'd discovered it first.
Thank you.
HBOOT: 0.95.0000
Radio: 2.22.19.26I
CPLD4
Personally I would recommend you install froyobylaszlo
But anyways, first of all before you start installing the 2708+ kernel, you're gonna need fastboot and adb on your computer
What OS do you have on your computer?
one laptop is Vista and the other is Win7
JediDwight said:
In the past week I've researched upgrading to Gingerbread and just recently there may be a bug uncovered where the phone no longer goes into Deep Sleep mode. This means the battery usage is not ideal compared to other earlier ROMs. It turns out virtually all Gingerbread Dream ROMs use some code by ezTerry, so they may all have this issue. So.. I think I will hold off on going to a flavor of Gingerbread until I get more info on this possible bug.
Click to expand...
Click to collapse
If you are not testing it this is a bad conclusion:
*) Deep sleep may or may not be working.. this has mixed results but the device is mostly sleeping.. so yes if completely idle (ie no cell network no wifi, screen off, no services running..) you might go from 4days uptime that the system currently gets even with an sdcard to 5 days if the problem if it exists is solved
problem is deep sleep is when the ARM11 CPU is turned completely off (it is going into low speeds correctly, and disabling other hardware into low power modes) This means when you are using the phone this state will not be entered (and thus the phone uses the same power as it is now) when a service is actively running.
Thus most peoples battery enhancements in GB are from the new APIs to allow applications to stay in the background more in Gingerbread; and a much larger problem is many applications these days are running more services than the G1 can support thus the system is constantly swapping in and out applications from memory.
Thus those whose battery on gingerbread roms is draining fast will more likely benefit from checking what is running in the backgound than waiting on a deep sleep fix if its even a problem.. since the services will still run after any fix and the battery life won't improve.
What the op needs is the 2708+ radio/SPL (that others are helping with) than nandroid in recovery can be used to switch between roms; since it provides more ram to CM5/CM6 and gingerbread roms all work with the 2708+ combination then the op can pick what works best for them in a more overall evaluation... and not just what lasts the longest when not used as a phone.
To OP:
the best way to continue is to:
1) Install fastboot (and the sdk) on your computer. you will need to search for this since the since I don't know the details for windows
2) If you already have a custom recovery (clockwork or ra-recovery) continue; otherwise you will need to install one: http://forum.xda-developers.com/showpost.php?p=4647751&postcount=1
3) then since you have HBOOT: 0.95.0000 install 1.33.2003 from: http://forum.xda-developers.com/showpost.php?p=6510019&postcount=76 this will allow fastboot and let you continue with:
4) Then the installation section at: http://forum.xda-developers.com/showthread.php?t=831139 (The files section will have the various files required and older roms that have been ported to work on the new SPL/Radio.. newer roms mostly will work per instructions on the rom's thread) .. read the entire post before doing anything.. as this is a major change to the phone, and the actions to fix something if you run into a problem may be slightly different than they were with more stock roms..
Try to get a feeling for what is needed before you begin .. we know its a bit of an involved process.. but most users have auctioned this in smaller steps originally.
(Note the cmwiki will probably be the best way to install recovery)
forum.xda-developers.com/showthread.php?t=910008
Download the drivers only pack
I think it includes fastboot
I can't check, if not tell me and ill upload my files as soon as I can get to a computer
search in google (or probably even xda) for "easy fastboot" if your having issues using fastboot, its exactly that an easy way to use fastboot for noobs.
also you can flash your new radio/spl as well as your rom via recovery, it isnt recommended but it can be easier if you have issues. ill tell you i have done it this way many times and have yet to brick a phone but as always my experience dosent me you will have the same. so try to follow the suggested route of fastboot is best.
upgrading to Gingerbread
I should have taken a longer rest.
I am starting the New Year with the feeling that everybody gets the right to flame me: my G1 does not work after a very bad step.
I installed on the re-formatted SD card 2 files namely DREAIMG.nbh and cupcake.
In short, I got the message "E: cannot open /sd card /update.zip (no such a file or directory). Installation aborted".
The next step was to sign my google account. It failed.
At this stage I cannot format, read, transfer, and use the SD card because it is not recognized by the computer. And of course the phone is not working.
Right now the G1 shows in the colored bars:
DREA100 PVT 32B
HBOOT- 0.95.0000
CPLD-4
RADIO- 1.22.12.29 (before doing anything to the phone the radio was 2.22.19.26I)
This phone was unlocked and set on the AT&T network.
Thanks to my wife Nexus One I can use, format, transfer files (which I did, to no avail) by inserting my SD card in her phone.
The least to say is that I really need the help, knowledge, and assistance of the Forum members.
What you don't want to hear is we see no error in what you have described. > well apart from the nbh file used it may be the original way to root but its not the easiest.
The message you are seeing in recovery is not am indication of a problem.
Ok, 0.95.0000 has no fastboot and thus you really need a custom recovery, to do that you. Need to flash it from the rom after rooting it, this means you need to try and boot the phone normally and log into Google normally.. if this fails try the following:
A.) go into recovery (home+power) and press alt+L then the combo to wipe the phone
B.) If its still not working try re-flashing the nbh
Oncce logged into google the telnet trick can work..
C.) While it needs a bit more setup, this third option is easier to install the 3rd party roms without a Google login and manual flash of recovery from system: make a goldcard ( you can do this on the n1) then put the orange nbh from the 2708+ thread http://forum.xda-developers.com/showthread.php?t=831139 this can be renamed DREAIMG.nbh and then be flashed with the gold card you made. (There are many guides on making the goldcard for HTC phones) Once flashed you will have a fastboot enabled spl that will let you flash anything by fastboot.
Thank you for helping me to breathe a little bit deeper, better, and slower.
So far I am in the same situation.
Dropping by BestBuy I found an SD micro with an adapter. It makes life easier for everybody.
I did again what I started, trying 2 different downloads of the .nbh file. Still locked at signing my google account.
Following your advice I will try to create a goldcard and follow the procedure you mention this evening.
Wait...locked at signing in to google account?
What do you mean? It shows google sign in but you can't sign in?
Do you not have a data plan?
If so, just google "activate g1 wifi"
Sent from my Gingerbread on Dream using Tapatalk
gunner1937 said:
Thank you very much for your reply.
Unfortunately my knowledge in this field is infinitesimal small.
That is why I am looking for a step by step guide.
Maybe I put myself in the wrong forum for my level and my needs. My apologies.
The only thing I know is that my phone does not need to be rooted.
Thank you again for your advice and your time.
Happy New Year to all of us
Click to expand...
Click to collapse
I'm on my phone so idk what link he posted.. but if you got the G1 development section.. look for a thread titled G1 rooting,unrooting and more or something like that by ldrifta, then look around on that thread for a gingerbread ROM
Sent from my T-Mobile G1 using xda premium
ezterry said:
What you don't want to hear is we see no error in what you have described. > well apart from the nbh file used it may be the original way to root but its not the easiest.
The message you are seeing in recovery is not am indication of a problem.
Ok, 0.95.0000 has no fastboot and thus you really need a custom recovery, to do that you. Need to flash it from the rom after rooting it, this means you need to try and boot the phone normally and log into Google normally.. if this fails try the following:
A.) go into recovery (home+power) and press alt+L then the combo to wipe the phone
B.) If its still not working try re-flashing the nbh
Oncce logged into google the telnet trick can work..
C.) While it needs a bit more setup, this third option is easier to install the 3rd party roms without a Google login and manual flash of recovery from system: make a goldcard ( you can do this on the n1) then put the orange nbh from the 2708+ thread http://forum.xda-developers.com/showthread.php?t=831139 this can be renamed DREAIMG.nbh and then be flashed with the gold card you made. (There are many guides on making the goldcard for HTC phones) Once flashed you will have a fastboot enabled spl that will let you flash anything by fastboot.
Click to expand...
Click to collapse
I am still trying to create a goldcard with the nexus 1. I cannot install a driver for it, I cannot install a driver from HTC sync, I get a message that "the device is not connected" but I can see the microSD on the computer.
This is where I am. And I do not know anymore what I have to do next since I feel I am in front of a wall.
frankdrey said:
Wait...locked at signing in to google account?
What do you mean? It shows google sign in but you can't sign in?
Do you not have a data plan?
If so, just google "activate g1 wifi"
Sent from my Gingerbread on Dream using Tapatalk
Click to expand...
Click to collapse
I did not express myself correctly.
When one reaches the sequence to sign into a Google account one has to enter email address then password.
I did that and few minutes later I got the message it could not reach the google servers.
Also, I have -rather had - a wi-fi connection since I got the G1 in December 2008.
gunner1937 said:
I did not express myself correctly.
When one reaches the sequence to sign into a Google account one has to enter email address then password.
I did that and few minutes later I got the message it could not reach the google servers.
Also, I have -rather had - a wi-fi connection since I got the G1 in December 2008.
Click to expand...
Click to collapse
There's your problem...
Wifi is off when you first turn on the phone
wiki.cyanogenmod.com/wiki/Google_Login_via_a_WiFi_Connection
Use that guide to turn it on and sign in
And if you don't want to download the entire sdk just wait until I get on my computer and ill upload just the files you need
But tell me if you still need the files or not...I don't wanna upload for nothing
And if you can't get the steps right, I can try tell you more stepbystep instructions
Sent from my HTC Dream using Tapatalk
wiki.cyanogenmod.com/wiki/Google_Login_via_a_WiFi_Connection.
Thanks for the link.
I cannot take advantage of it: Device manager shows 7 Intel ICH* universal controller, 1 USB composite device and 7 USB root hub.
Nothing else.
No USB mass storage device.
Android SdK is installed on C: but I do not know if it is properly installed or activated because I could not check "adb devices"
OK folks, I know some of you are going to jump straight down my throat, but please, back off and stick to the friendly forums that this used to be where anyone would help anyone.
the story so far is that I once loved my Nexus One, I've had it since launch, I have ran Cynogen Mod 7 for a couple of years, I have had MUI roms running, I have played with various kernels, updated radio, upgraded hardware, all was going wonderfully.
the one thing I could never get was full SU!! Heck knows why!!
I then started getting random problems and downloaded the original google frf83 software and flashed the phone via update.zip using amon-ra recovery.
I thought all was well after this, as my phone received 3 OTA updates and now my phone is on...
Android 2.3.6
Baseband 32.41.00.32U_5.08.00.04
Kernel 2.6.35.7-59465-g42bad32 ([email protected] #1)
Build GRK394
I noticed that in the Status (settings) it was displaying my old sim card number, which is not the number for the sim in the phone now. his I thought was odd and that something had gone wrong.
So as most of us would do, I went to boot AmonRa recovery and it wasnt available, it had been overwritten with the default recovery; ok lets just ADB and reflash it, I hadnt used ADB for a couple of years because I did everything through AmonRa's awesome recovery!!
So off I go, install the SDK, all the appropriate packs including the USB driver, just like I did when I originally flashed the phone with the recovery image!
But an old problem came back that I hadnt even been bothered about because I always put stuff on SDcard via a card reader!!
I have had consistent problems with my nexus one for some time now in regards to the USB drivers, no matter what I do the phone will not install and I believe it could be some conflict in the device.
I am running Vista Ultimate (fully registered) and no matter what I do I cannot get the Nexus One to install. It will only display as unknown device, which is absolutely useless.
I have browsed every post and tried everything I have found, and yet nothing is working. I have used devmgmt, I have tried the roll backs, I have tried to install every driver available to get it working. I have uninstalled the device, updated drivers after fresh install attempts, I have even formatted my laptop thinking it may have had a corrupt OS and bought Vista Ultimate.
I am not a complete noob and I have been around these forums for some years, but I never thought I would have to cry out like a 4ucking Noob with such a seemingly simple problem, but it is not simple, I have done everything I can possibly find!!
I must get the USB working in order to get the recovery back, I can access my phones default recovery but it will not work when trying various roms as update.zip!!
I have tried the terminal commands on the phone to install the recovery.img but I do not have SU access and the phone point blank refuses.
I have attempted to change and remove the recovery files reffered that are causing the revert to default recovery, but shock.. I cannot delete because of insufficient permissions. I cannot ADB because the USB driver refuses to install.
So if I cannot change the files due to permissions, I cannot ADB because of USB, I cannot get to Ra's recovery because of bootfiles, I cannot use default recovery to update.zip... I am absolutely losing my mind and I'm going nuts browsing the forums for the second week running, yes I am now on day 12 of trying to fix this problem and at a complete loss...
Can someone please help??
I will even allow remote access to pc because I am that desperate to resurrect my beloved Nexus One.
I also have a Galaxy I9000 without 3 button download mode but that is an entirely different story!!
Please just someone, come to an oldskoolers rescue, and yes PAYMENT will be given to the knight in shiny armour!!
You could try on another computer which doesn't run Vista
tommert38 said:
You could try on another computer which doesn't run Vista
Click to expand...
Click to collapse
Or just use fastboot instead of adb...
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
tommert38 said:
His Nexus One isn't recognized by the computer, so that won't help unfortunately. Also, I've never heard of build GRK394..
Click to expand...
Click to collapse
Install the drivers for fastboot already Jeez and then read How to use android for dummies.
I believe I have correctly rooted the phone - I have a Super User icon and when I abd shell I get #
When I run the adb shell /data/local/flash_image recovery /data/local/yourrecoveryimage.img command I get "[1] Illegal instruction /data/local/flash_image recovery"
In several threads here I saw people saying to just use ROM Manager. I downloaded the APK, but when I tap on it I get a Parse Error.
More research... and I think the issue may be that my system version is blocking things. I found a site that had a Windows program that was supposed to push an older version to the phone (can't find the link right now) but it failed too. It ran, accessed the phone, then said it couldn't update my phone.
I'm not sure where to turn next. If there is a post or FAQ somewhere that addresses this please point me to it. If you have something for me to try, I'm ready and willing.
--edit - found the program I mentioned above. ROM Update Utility 1.0.2.10, trying to change from image version 2.3.651.2 to 2.27.651.6. I found the program here:
forums.androidcentral.com/htc-hero-rooting-roms-hacks/56118-how-root-your-sprint-hero-one-click (html)
What hboot do you have ? What radio? What software ver? Also what carrier are you with?
#Root-Hack_Mod*Always=SG3
laie1472 said:
What hboot do you have ? What radio? What software ver? Also what carrier are you with?
#Root-Hack_Mod*Always=SG3
Click to expand...
Click to collapse
The phone is Sprint, but I am not connected to any carrier. I'm only using it on WiFi.
Not sure what hboot is or how to tell what my radio is.
Software Number is 2.3.651.2 as mentioned in my first post, though I guess it was buried a bit.
minidrag said:
The phone is Sprint, but I am not connected to any carrier. I'm only using it on WiFi.
Not sure what hboot is or how to tell what my radio is.
Software Number is 2.3.651.2 as mentioned in my first post, though I guess it was buried a bit.
Click to expand...
Click to collapse
You need to install rom manager 2.5 when first rooting sprint. search for it on the web or here at xda.
jamstewonline said:
You need to install rom manager 2.5 when first rooting sprint. search for it on the web or here at xda.
Click to expand...
Click to collapse
Thanks! That version installed. Now I just need to get to where I have WiFi to see if the rest works, but I'm very hopeful.
Thanks again.
ROM Manager 2.5 installed just fine. It grabbed a Recovery (clockwork-2.5.0.7 I believe) and installed it for me. I booted to that and installed the ROM I had on the SD card - Cyanogen 7.2.0 which seemed to go fine.
Then I had a bit of a scare. The phone rebooted and I got a Cyanogen animated logo and nothing else. No buttons did anything - I couldn't even power off. Had to pull the battery for that. Put it back in, powered on, same thing.
Booted to Recovery and it was the built in one, not Clockwork, but based on some reading I did a Wipe and after that the phone booted to Cyanogen.
Thanks for the help!