Hey Guys,
I've updated to Cognition and it worked fine; i had to do a hard reset on the phone becuase my time stamp was wrong so i thought it would of fixed it. Now i lost my Andorid Market and Rom Manager :S
Does anybody know how i can get this back.
Thanks.
This happened to me when I tried switching my wife's and my SIM cards so she could use my Captivate while I worked on hers. Both phones lost the Android Market app which of course makes it difficult to do anything else.
I ended up flashing mine back to stock which solved the issue as expected.
I have no idea why Market disappeared. I wouldn't think it had anything to do with the SIM cards.
How would you flash to stock? I lost Rom Manager as well when i did factory defaults
Use the Odin one click at http://forum.xda-developers.com/showthread.php?t=731989
That will put your phone back to stock. Read that thread to get a good idea of what's going on, but here's the simple part that you will end up doing.
To use it:
1. Make sure phone is not plugged into computer.
2. Open the Odin one click program.
3. Make sure phone is turned off.
4. Hold the volume down and volume up keys.
5. While the volume keys are being held, plug in your USB cord.
That should bring you to the Download screen with the robot digging and stuff. You can then click the start button in the Odin program.
If after step 5 you don't get into the Download screen then you need to do some more research in that thread, or read the steps and try again to follow them exactly as stated.
edit: I see you're on Rogers. I don't know, but I've seen separate threads pop up for people using Rogers so possibly things are different for you so make sure you research!
Thanks for your help; once i got to recovery mode i spent some time going through the menu and found out i could load my OS from there because i left the zip file on it.
I got a little nervous since i thought i screwed up a 2 day old phone lol....but all is well. Now i need to find another Rom to put on it
I remember reading about an app that let you read your market ID # and restore the ID# after you flash. Doesn't Cog give everyone the same market ID# when you flash it?
baseballfanz said:
I remember reading about an app that let you read your market ID # and restore the ID# after you flash. Doesn't Cog give everyone the same market ID# when you flash it?
Click to expand...
Click to collapse
App to read Device ID, is called Android Device ID.
App to change Device ID is called Android ID Changer.
Cognition before 2.3b4 (including 2.4.x) changed everyone to the same Device ID.
To get your real Device ID flash back to stock and use Device ID. Save that somewhere.
Then you can change it if you are not running Cognition 2.3b4, using Android ID Changer.
Cognition 2.3b4 has a script to make a random device ID if you don't have one.
If you do have your device ID, you need to insert it in a file called "udpate.id" in the Internal SD cards root directory. Then a reboot should put that Device ID back on your phone via the script.
Once you have a good device ID, clearing the Market cache and restarting should get things going again.
Well that's interesting ... I wish somebody told me to save my Android ID before i Flashed it. At least i know what that Android ID is for now lol
I did make a backup of my original; i'll try to pull it out of my phone and store it on my PC just in case i do something stupid and delete it lol.
Thanks guys for the info.
This is what I read, finally found it again.
http://adaptiveeng.blogspot.com/
Related
Ok, first of all I know it's been said not to mess with Framework. I read that too late =/
I was trying to install a status bar replacement, which overrides framework-res.apk. It sent it into reboot loop. I can get to recovery screen, but factory reset doesn't do anything of course.
I also can get to bootloader. It gives me the following:
===
Bootloader
29.01
Battery OK
OK to program
Transfer mode:
USB
===
It's connected through USB and bootloader recognizes that. My question - is there a way to push original framework-res.apk back to the phone or is it completely bricked?
I posted in an existing thread about this already, but figured I might have more luck with a new thread.
If you
Code:
adb devices
does it show up? I'm unfamiliar with this type of situation. =p
Oh sorry, forgot to mention that. adb devices doesn't show anything in either recovery nor bootloader.
When connecting through USB and starting bootloader, I can hear the sound of device found on my PC, but it doesn't get found and is listed as "S Flash OMAP3630 MI" with a ? mark in device manager.
Yikes, can't help you with the obvious then (just pushing framework-res.apk again).
Yeah, I was really hoping to somehow get in there with adb
As suggested in another thread, I tried applying .604 update, but it aborts when verifying current system with CityID.apk as a reason. I removed it along with other bloat from the phone.
Also when trying to remove app files I don't have on the phone from update.zip, it fails when verifying the update file.
hey its me again, take a look at this!
http://www.droidxforums.com/forum/d...your-x-stuck-bootloop-you-want-look-here.html
Thanks for the link!
That guy got lucky cause it bricked after he put all the bloatware back on the phone lol. So he had all the default apps. Mine gets stuck when verifying my system and complains about CityID.apk missing. And as we figured out, your previous suggestion with removing files from the zip messes up its integrity.
So I went to a Verizon store and got a replacement ordered. I was afraid they'd start asking if I'd rooted it, but apparently the guy helping me didn't even know what that is He tried a factory reset and then just ordered a new phone.
Thanks for your suggestions, guys!
He may not of known that the x has been rooted yet lol. Or you can just find something small and miniscule to complain about on you phone to get a new one. When the dare first came out I had a new one at the end of every month just for the fun of it. And they where always replaced with a brand new phone. Did that for atleast 5 months before getting a cheap wm phone because they felt bad about all the hassles I had.
Sent from my DROIDX using XDA App
Did the same thing with mine, except my framework file is there, just renamed. I tried last night to figure out how to change the name back with adb but never could.
to the OP, how did you get to that Bootloader? The only thing I have been able to do is get into "Android System Recovery (2e)", which is done by holding Home while powering up the phone. If you hold Home, you'll get a screen with Android next to an exclamation point sign. At that screen you can press Search to open up the menu system, and then you have the ability to reboot, apply update.zip from microSD, wipe data/factory reset, and wipe cache partition.
I am trying to get into ADB so I can potentially work on this phone and fix it. At the moment I am boot looping like nobody's business
-EDIT-
Found the answer myself on this forum: "Hold down the power+vol down+camera button."
This works, but from what I can tell, it puts the phone into a basic USB flashing mode that is useful if you wanna reflash the ROM. At the moment there isn't anything available which could be flashed onto the phone (need to wait for an SFP file?), so I'm stuck waiting.
If/ when the 2.2 update leaks, I believe I can at least try to install that via MicroSD while in System Recovery Mode. I already unbricked my phone once by doing that, but then removed exactly the wrong APKs so now I cannot use that trick a second time
Yep, that was exactly my experience. If I didn't remove bloat apk's, I'd be able to apply .604 update, but...
And yeah, bootloader doesn't do much at this point since we have no way/no ROM's to load.
As far as I remember, Verizon have one month return policy, so I'd suggest just taking it to them. I had my replacement ordered with no questions asked. I just said I was installing an app and it rebooted and went into a loop.
Please don't say Odin 1 click as it does not go 100% back to stock.
The nv_data.bin and bml3 device are not as stock. I have FFFFFFF where my unlock code used to be and my unlock code no longer works.
Master Clear and then JF6 restore doesn't change these either. I find it hard to believe there is no way to get 100% back to new.
Any ideas?
alphadog00 said:
Please don't say Odin 1 click as it does not go 100% back to stock.
The nv_data.bin and bml3 device are not as stock. I have FFFFFFF where my unlock code used to be and my unlock code no longer works.
Master Clear and then JF6 restore doesn't change these either. I find it hard to believe there is no way to get 100% back to new.
Any ideas?
Click to expand...
Click to collapse
Nandroid backup of rooted stock then unroot is probably the most effective.
gunnyman said:
Nandroid backup of rooted stock then unroot is probably the most effective.
Click to expand...
Click to collapse
I don't have a nandroid backup or I would do that
alphadog00 said:
I don't have a nandroid backup or I would do that
Click to expand...
Click to collapse
Well it seems like this Phone is a bit like windows 95 when it comes to wiping and reloading it. Bits and pieces of other installs are left over? Wish I knew how to help you. Perhaps someone out there has a completely stock nandroid they could send you. I know there's one for the Vibrant.
gunnyman said:
Well it seems like this Phone is a bit like windows 95 when it comes to wiping and reloading it. Bits and pieces of other installs are left over? Wish I knew how to help you. Perhaps someone out there has a completely stock nandroid they could send you. I know there's one for the Vibrant.
Click to expand...
Click to collapse
Yeah, but with any flavor of windows i can do an Fdisk and repartition.
I wonder if i can use standard odin and repartition? Anyone know?
gunnyman said:
Well it seems like this Phone is a bit like windows 95 when it comes to wiping and reloading it. Bits and pieces of other installs are left over? Wish I knew how to help you. Perhaps someone out there has a completely stock nandroid they could send you. I know there's one for the Vibrant.
Click to expand...
Click to collapse
I sent mine back to Samsung and they reset it -- when I get it back I can see if mine is able to be Nandroid'd if that'd help...
The Bishop said:
I sent mine back to Samsung and they reset it -- when I get it back I can see if mine is able to be Nandroid'd if that'd help...
Click to expand...
Click to collapse
Why did you send it back? I am curious how the /EFS directory gets built - it stores the IMEI related stuff and lock code data, but it doesn't get wiped with a Odin full restore.
I would think that if you put your phone in recovery mode, there should be an option to format the internal sd card. After you do that, just do a factory reset, and then run Odin One-Click back to JF6
Edit: There's not even a need for recovery mode. Go to Settings > SD card and phone storage > and then under Internal SD card you'll see "Format SD card".
miztaken1312 said:
I would think that if you put your phone in recovery mode, there should be an option to format the internal sd card. After you do that, just do a factory reset, and then run Odin One-Click back to JF6
Edit: There's not even a need for recovery mode. Go to Settings > SD card and phone storage > and then under Internal SD card you'll see "Format SD card".
Click to expand...
Click to collapse
Format SD card only formats the ~14GB that acts as an SD card that the user has access to. The 2GB that makes up all the system partitions is not touched. Some of it is rewritten when you do 1 click install - but not all.
With JF6 your NV_data.bin is not created like the original and the IMEI and BT files are dated from June - so the EFS partition is never rewritten. Maybe if you delete it is recreated, but i doubt it.
alphadog00 said:
Why did you send it back? I am curious how the /EFS directory gets built - it stores the IMEI related stuff and lock code data, but it doesn't get wiped with a Odin full restore.
Click to expand...
Click to collapse
I bricked mine trying to go to Froyo. They sent it back to me with JH7 so no go :/ Sorry.
did anybody try calling att if you are a att cust they will give you the code for free.
over on the i9000 forum they say when froyo first came out if you left your sim in the phone when you flashed it would relock your phone.
can anybody verify that if they goto froyo with a unlocked captivate without the sim do they still get locked.
if so it might be a measure to prevent people from messing with the beta to much
tjsooley said:
did anybody try calling att if you are a att cust they will give you the code for free.
over on the i9000 forum they say when froyo first came out if you left your sim in the phone when you flashed it would relock your phone.
can anybody verify that if they goto froyo with a unlocked captivate without the sim do they still get locked.
if so it might be a measure to prevent people from messing with the beta to much
Click to expand...
Click to collapse
Actually I did try it. In July, they said wait 60 days. Yesterday they input my IMEI and their system told them that the phone can't be unlocked - due to AT&T exlusivity. i am in the process of escalating, but it is hard to say what will happen.
It certainly appears that it is not as simple as waiting 60 days.
alphadog00 said:
Actually I did try it. In July, they said wait 60 days. Yesterday they input my IMEI and their system told them that the phone can't be unlocked - due to AT&T exlusivity. i am in the process of escalating, but it is hard to say what will happen.
It certainly appears that it is not as simple as waiting 60 days.
Click to expand...
Click to collapse
funny att rep when i got the phone told me that there was no exclusive deal and unlocking was no problem he was a general manager of a att corporate store in wayne nj
if that is the case i will never go to froyo till a unlock soluition is found.
The Bishop said:
I bricked mine trying to go to Froyo. They sent it back to me with JH7 so no go :/ Sorry.
Click to expand...
Click to collapse
Just out of curiosity, was there a charge for this or did you "forget" to mention that you bricked it while flashing Froyo?
tjsooley said:
funny att rep when i got the phone told me that there was no exclusive deal and unlocking was no problem he was a general manager of a att corporate store in wayne nj
if that is the case i will never go to froyo till a unlock soluition is found.
Click to expand...
Click to collapse
Those guys say what they think, but they make you call central to do certain functions - at least in the past. I guess I could go into a store and check, but I doubt I will do any better.
alphadog00 said:
Those guys say what they think, but they make you call central to do certain functions - at least in the past. I guess I could go into a store and check, but I doubt I will do any better.
Click to expand...
Click to collapse
he called the att corp support center
we had alot of issues and he spent like 1 h with us.
What role does SIM play in restore to 100% stock?
alphadog00 said:
Please don't say Odin 1 click as it does not go 100% back to stock.
The nv_data.bin and bml3 device are not as stock. I have FFFFFFF where my unlock code used to be and my unlock code no longer works.
Master Clear and then JF6 restore doesn't change these either. I find it hard to believe there is no way to get 100% back to new.
Any ideas?
Click to expand...
Click to collapse
I'm curious about this too...it seems that once you mod the phone in any way it's never 100% stock again. I wonder if having the SIM in when a mod is done has anything to do with it - does anyone know if the SIM can be written to and, if so, if anything is written to it during a mod?
I've tried everything possible to get this phone 100% stock again in an effort to get Kies Mini to STOP giving me the "unrecognized" error, including cleaning Windows registry and trying on my Windows XP Pro partition - no go. Something, somewhere, is providing information to Kies Mini.
---Edit---
Dumb question about writing to SIM; but question about something being written to it during a mod - if left in - still stands. Anyone?
boomerod said:
I'm curious about this too...it seems that once you mod the phone in any way it's never 100% stock again. I wonder if having the SIM in when a mod is done has anything to do with it - does anyone know if the SIM can be written to and, if so, if anything is written to it during a mod?
I've tried everything possible to get this phone 100% stock again in an effort to get Kies Mini to STOP giving me the "unrecognized" error, including cleaning Windows registry and trying on my Windows XP Pro partition - no go. Something, somewhere, is providing information to Kies Mini.
---Edit---
Dumb question about writing to SIM; but question about something being written to it during a mod - if left in - still stands. Anyone?
Click to expand...
Click to collapse
The SIM can only hold contact data - and very limited amount. I can almost guarantee that nothing is written to the SIM card.
Is Kies not recognizing the phone is plugged in , or refusing to upgrade because it is the wrong type? Unrecognized device by keys is usually due to Samsung drivers and reinstalling them has helped me.
But it seems that the only way to revert to 100% stock is via Samsung repair service.
alphadog00 said:
The SIM can only hold contact data - and very limited amount. I can almost guarantee that nothing is written to the SIM card.
Is Kies not recognizing the phone is plugged in , or refusing to upgrade because it is the wrong type? Unrecognized device by keys is usually due to Samsung drivers and reinstalling them has helped me.
But it seems that the only way to revert to 100% stock is via Samsung repair service.
Click to expand...
Click to collapse
I tried the drivers, but that didn't fix the issue either.
So i decided to go on a Flashing spree today for no reason, i just felt like it..
I started out by flashing 2.2 on my 2.1 phone, that all worked out quite well, but for some reason i could not root it. ( I used http://forum.xda-developers.com/showthread.php?t=845558) It all worked out nicelly but since i could not root it, i just game up on it.
After searching i found http://forum.xda-developers.com/showthread.php?t=734475 to revert my phone back to its original firmware. I have a Galaxy s Vibrant, so i thought it was the correct thing. But since i installed it i have alot of problems.
First of all, when i plug it into my USB the phone auto turns off. And it will not charge when the usb is in.
I have rom manager installed, but when i try to run a rom, i keep getting the error (status = bad ).
Also the phone wont recognise my SimCard so i cant stay with this firmweare anyways.
flash back to a stock Froyo
then boot into the Recovery Mode
then wipe data, and wipe cache
see if that helps
Do you know the best place where i can get a stock froyo rom ?
amnoric said:
So i decided to go on a Flashing spree today for no reason, i just felt like it..
I started out by flashing 2.2 on my 2.1 phone, that all worked out quite well, but for some reason i could not root it. ( I used http://forum.xda-developers.com/showthread.php?t=845558) It all worked out nicelly but since i could not root it, i just game up on it.
After searching i found http://forum.xda-developers.com/showthread.php?t=734475 to revert my phone back to its original firmware. I have a Galaxy s Vibrant, so i thought it was the correct thing. But since i installed it i have alot of problems.
First of all, when i plug it into my USB the phone auto turns off. And it will not charge when the usb is in.
I have rom manager installed, but when i try to run a rom, i keep getting the error (status = bad ).
Also the phone wont recognise my SimCard so i cant stay with this firmweare anyways.
Click to expand...
Click to collapse
It looks like you flashed the actual "Vibrant" (T-Mobile US) type firmware onto your Bell i9000M phone... I dont know if you can flash back as the Download and Recovery modes for the actual Vibrant are different than the i-9000 model phones...
@Allgamer, can you be of any further help?
btw i really hate Samsung right now, why would you release a phone called a i-9000m Vibrant, then release a phone under the brand name vibrant
amnoric said:
btw i really hate Samsung right now, why would you release a phone called a i-9000m Vibrant, then release a phone under the brand name vibrant
Click to expand...
Click to collapse
I agree with you on this man. How confusing could they make it? I guess they did it to sort of distinguish our model of i9000M from the International version but couldnt they at least give a different name from the U.S. model?
They even look identical except for the fact that the U.S. Vibrant has 4 soft keys at the bottom where we have the 2 soft and 1 hard key...
Well now that my panic attack is over and my phone is back to normal after Flashing 2.2 on it ( FOR I-9000m even ).
I have another random question..... what is the best way to root 2.2.. since the whole point of the **** up was because i would not root it
amnoric said:
Well now that my panic attack is over and my phone is back to normal after Flashing 2.2 on it ( FOR I-9000m even ).
I have another random question..... what is the best way to root 2.2.. since the whole point of the **** up was because i would not root it
Click to expand...
Click to collapse
I recommend the app called z4root by RyanZA. You can find it on the Market. It is a one click root that requires no flashing of any kind.
You may have to start the app and if it seems to hang for a while just perform a reboot and run the app again and it will root within 30 seconds. Also be weary in the Market as someone has stolen the icon and everything from RyanZA and the "rip off" app is NOT complete. Make sure the one you download states it is from RyanZA...
So, I'm getting really frustrated and reading isn't helping at all. I know there is plenty out there, but I can't seem to find a solution after spending probably 5 hours today on my phone trying to restore the correct product code on my phone so I can use kies mini to put it back to stock 2.2 android. I followed the directions exactly in this thread:http://forum.xda-developers.com/showthread.php?t=880223 , all to no avail. I am able to pull my efs file from my phone and edit it just fine, but when I try to push the new edited file back to my phone, something doesnt work in the command prompt, and the window disappears before I can read what's going on.
I really don't know where to go from here. I feel stupid, as if I'm not saving the edited file to the correct place or something. anybody have a similar issue?
The reason I NEED to get this figured out is that I got this phone as a replacement and it came stock with 2.2 on it, so I need to get it back to that in order return it again, and it worries me that I can't get the product code switched back. Am I just SOL?
Have you tried super manger in market. Just make shore you mount data read / rewrite (r/rw). Or use root explorer if willing to buy it
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
welchertc said:
So, I'm getting really frustrated and reading isn't helping at all. I know there is plenty out there, but I can't seem to find a solution after spending probably 5 hours today on my phone trying to restore the correct product code on my phone so I can use kies mini to put it back to stock 2.2 android. I followed the directions exactly in this thread:http://forum.xda-developers.com/showthread.php?t=880223 , all to no avail. I am able to pull my efs file from my phone and edit it just fine, but when I try to push the new edited file back to my phone, something doesnt work in the command prompt, and the window disappears before I can read what's going on.
I really don't know where to go from here. I feel stupid, as if I'm not saving the edited file to the correct place or something. anybody have a similar issue?
The reason I NEED to get this figured out is that I got this phone as a replacement and it came stock with 2.2 on it, so I need to get it back to that in order return it again, and it worries me that I can't get the product code switched back. Am I just SOL?
Click to expand...
Click to collapse
give my repair thread/process a go:
http://forum.xda-developers.com/showthread.php?t=881162
The only two things that I have ever needed to do this is Root Explorer and hex editor in the market. Success every time. Let me know if you need assistance.
bames said:
give my repair thread/process a go:
http://forum.xda-developers.com/showthread.php?t=881162
Click to expand...
Click to collapse
Worked wonders, thank you so much!
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"