Ok guys, I've rooted my phone, flashed the newest cognition, and installed ROM manager I have super user permission and am ready to move forward ( I think). What is ( in very simple terms for a newbie) my next step in making my phone a wifi hotspot and/or enable usb tethering. I have pretty much done all this straight to my phone, I have still not been able to get my windows pc ( running vista) to regognize my phone, or rather, I can see it in connected devices but no communication back and forth. Please help this newbie has been working on this for days and I know I'm close. Thanks to all members and threads so far. Also did clockwork mod recovery and backed up, but have nothing I can find anywhere that enables or allows wireless tether. Did I do something wrong, or skip a step somewhere? Should I go back into recovery, is there an option in this mode to enable wireless? Again I'm a newbie and when I started to go back into recovery, I got a prompt that asked if I was sure I wanted to go back in, and that worried me, but also read in a forum that now my phone is near unbrickable. Is that true? Am I over worrying? Just got the phone and don't wanna fry it, a non warranty replacement is over 500 bucks, so I'm a lil leary about what to do next.
Go to Settings> Wireless and networks> Mobile AP, change the settings and enable.
Sent from my Captivate
It only give one option do I simply hit the green dot and off I go? I'm not getting an actual mobile ap option in there I'm having to settings>wireless network>mobile networks> then I have 3 options
Data roaming
Access point names
Network operators
Which to I choose, and what are the info do I input?
Ok if I go into settings, choose wireless and networks I get
Flight mode
Wifi settings
bluetooth settings
vpn settings
Mobile networks
I then chose wireless networks and I get
Data roaming
Access point names
Network operators
Have I missed a step somewhere or done something wro g?
Sounds to me like your ROM doesn't have the Mobile AP software in it.
You can always try WIFI Tether for Root I guess. My stock Rogers ROM has Mobile AP and it works fine, I heard Cognition had it, maybe they've removed it?
I tried to download and I am still not allowed I still get "download not allowed from outside the market" which is leading me to believe that I've done something wrong in the process, or that I've simply skipped a step or didn't enable something somewhere. Should I try going back into recovery with clockwork mod and maybe go thru that again? Is there an enable setting in there?
p1p3l1n3r205 said:
I tried to download and I am still not allowed I still get "download not allowed from outside the market" which is leading me to believe that I've done something wrong in the process, or that I've simply skipped a step or didn't enable something somewhere. Should I try going back into recovery with clockwork mod and maybe go thru that again? Is there an enable setting in there?
Click to expand...
Click to collapse
wireless-tether must be sideloaded on the Captivate, you can't get it from the market.
You get it from here:
http://code.google.com/p/android-wifi-tether/
You can use adb or the Sideload Wonder Machine to install it on your phone.
Having said that, the Cognition ROM had Mobile AP in it the last time I used Cognition. Normally it would be between Wi-Fi Settings and Bluetooth Settings on the Wireless and Network menu.
Would suggest ODIN One-Clicking back to stock and re-flashing Cognition, or perhaps moving to another ROM that confirms it's got it (I am using DG's Perception ROM now, which does). While it does work, wireless-tether is really a poor substitute for the regular Mobile AP ap.
Ok, quick ( probably dumb) question. I didn't load rom from sd card. When I go into ROM manager and choose load from sd I have an update.zip, but it does not say cognition, is this the correct choice to download or am I missi g something? And if it is the correct one I simply choose wipe data correct? And at that point I should have my wireless ap option in my wireless and network folder? Think I may have done right but am lacking on follow thru.
p1p3l1n3r205 said:
Ok, quick ( probably dumb) question. I didn't load rom from sd card. When I go into ROM manager and choose load from sd I have an update.zip, but it does not say cognition, is this the correct choice to download or am I missi g something? And if it is the correct one I simply choose wipe data correct? And at that point I should have my wireless ap option in my wireless and network folder? Think I may have done right but am lacking on follow thru.
Click to expand...
Click to collapse
No, Cognition will not be named update.zip. If you downloaded the most recent version, the filename is:
Cognitionv2.3b6.zip
You have to download it and then move it to the root directory of the built-in storage of your phone of your phone (It goes in the same place that update.zip is at).
When you reboot into recovery, scroll down to 'install zip from sdcard, hit the power button, scroll down to 'choose zip from sdcard' and scroll down until you find the Cognition ROM, highlight it and press the power button once more.
Would suggest you spend a lot more time reading before you try to flash a ROM. All the instructions are out there and not that difficult to follow. If you are not careful in what you do, you can brick your phone. Fortunately it's really hard to permanently brick a Captivate, but read a lot before you start. It will save you a lot of headaches moving forward.
T, hank you for the advice, and the tongue lashing, and I understand your frustration with me, but first off, I have repeatedly admitted my lack of knowledge, second, I have done nothing but read and attempt to follow exact instruction to the letter but many terms I do not know and are hard to understand from my perspective, which is why I have repeatedly asked for very simple instruction, I do not presume to be any type of wizard, and I don't feel it just to come at me in such a way. I do however understand your frustration and appreciate any and all help I have been given or will be given in the future. I simply ask, how is someone like me who works hard everyday just not in the same field as you supposed to ever get to the point of understandi g terminology if I don't try. Please do not misunderstand, I'm simply saying that I did my readi g before beginning and obviously came to the right place for help, I'm just a lil slow on the uptake and for that, I appologize. Again, thank you all for your help.
It was not a tongue lashing ... or rather not intended to be ...
Just an honest (if frank) piece of advice. Many people can be harsh on these forums, especially when they see people not even bothering to look before they leap. You were at least trying, which is why I outlined a (possible) solution for you before telling you to do some more looking around.
Flashing ROMs can be tricky business, and a bit intimidating (if not scary) the first time you do it. Trust me, after the first successful flash you will be home free ...
Still, the forum is full of people who try to flash without really reading up on things before they do. And also full of people begging for help because they bricked their phones specifically because they either didn't study up first, or ignored the steps that they read.
I'm not all that tech savvy in the grand scheme of things either, but I read for days before I attempted to flash my first ROM. It's the same advice I would give to anyone looking to start flashing.
If nothing else, when things go wrong you will have that little voice in the back of your head that goes "hey, I remember reading someplace that this happened to someone" and then you can go searching for the solution more easily.
Related
First off I would like to say that this is one of the best forums I have ever seen as the amount of support and helpful users and creativity put into these phones are staggering. I was going to go to Windows mobile for my next phone but I now doub it with this site or at least maybe I will dual boot.
So I am sure I am asking questions that have already been answered but my problems with the phone (USA G1) are many and the answers to some of the problems are so fragmented that I had at one point 14 tabs open for reference to solve just a few issues. I am 70% noob with the G1. I have had the phone for a year with no major issues just the annoying Force Close that seemed unecessary for the commonality of the app that had problems. Texts were annoying because I could not tell if they had been sent the previous day or recently as service at my home is come and go and my older Verizon phone had envelope information and even said if the person had read it or not so no annoying duplication. However, otherwise it was stable and would last about a day and a half with the double size battery.
Recently, however I had rebooted from the power button prompt and it got stuck (I can't remember on what screen) and figured installing a different ROM and other files would fix the problem. By the way, I had bought the phone rooted and I believe it was using JF 1.42 and a Cyagen mod (forgive my spelling). So I followed step by step from this forum the wiki on the lastest stable Cy ROM. I followed the instructions to the T.
Being new to the software, it was a slow process with a lot of repeating of steps discovering little details that were not mentioned like naming something update instead of update.zip like instructed or adding the .img as an extension. So I had nearly made it and then I came to the DangerSPL and other files to be loaded on the phone in order via fastboot. Despite, several attempts I could not get the skateboarding droids or the rainbow screen to come up so I finally decided to just continue as I had been using Amon-RAs 1.7 update zip feature to follow the instrucions and install the software in order. All was well until I got to flashing the actual ROM which said something about how it said the E: [insert file name here] was not correct so it aborted everytime but it did show some progress on the yellow bar.
Next came the issue of the G1 screen hanging up after the above problem and for some reason I could get to the 1.7 screen but only by holding the button required to access Amon RA longer than usual other wise it would say the build of Amon RA at th ebottom with no commands and the reboot itself or hold it longer and finally get to the Amon RA but it would not load my recovery files as I had made many along the way.
I nearly gave up but then came across this solution which worked by using method 1 at well I am not allowed to pu the websit in here but I am not allowed by the mods. but it is the 4th one down if you google "how to fix a soft brick g1" and the link is titled Unbrick - android-roms - How To: Recover your G1 from a bring ...However, it did get stuck at the rainbow screen as it finally let me do the fastboot and I saw the Androids skateboardig but it hung at the rainbow screen. It was here I noticed that my 32A phone was now a 32B. I took the battery out and powered it up and lo and behold it was asking me to put in my google information and I finally made it to the home screen.
I thought "Yes!". Now, I can try again since it will fastboot now which was what was recommended at the final steps but I was mistaken. I could not searc the market for common apps like wave secure and it frequently said it does not exist. I saw that my terminal app was gone and when I was finally able to download it from the market and my superuser app was gone and the termina would not respond as before to the input of SU.
Then, I noticed my phone's screen would randomly come on and only sometimes go off. When I pressed menu it was as if it the call button was stuck and it would either repeatedly bring up voice dial or call someone. The buton does not appear to be stuck otherwise. When it would briefly stop, acting like the call button was in turbo mode it would give me the option to mount the SD card as I had lost my micro sd card reader but never give me a chance to mount it before the call button interrupted with google dial or calling some number.
I do not believe this to be a hardware issue because as far as I remember the call button worked normally during the steps as it was requently used. So my questions, at the moment, are these:
1. How do I tell if the call button problem is a hardware or software issue?
2. Once I find my card reader and will I be able to use the factory bootloader to go through the updates.
3. Obviously I have derooted my phone (or maybe I can delete the diag from sd card and it will operate as it is derooted), will I be able to reroot my phone by using my backups of nandroid basically leaving me at whatever step I was on to the road of recovery?
4. How do I use my nandroid backup to recover especially if I am stuck with the factory bootloader?
5. I copied my SD card before I did the wipe originally so will I be able to find a .xml from handcent with my texts? (I text myself my mileage for work as with my hours, it is easier than using an app plus it saves space for other apps)? Should I load that backup nandroid first and start over?
6. Is there a quicker way to root like...a program?
7. What is your advice for the future other tha obviously backing up my texts more?
8. When did wave secure start costing money? I think I might have backed up everything a few days before the crash but I have no access to it now.
9. What other key combinations can I later use for the fast boot?
10. When formating the card to fat32 what allocation do you use and do you use quick format?
11. What is lost dir. and why is it empty?
12. In Amon RA 1.7 there are several caches which I cleard all of them when asked to clear the the cache in the wiki directions? Should I clear all of them and what are the seperate caches, espicially the davik one?
I am sure I am missing some question but I will post more as I try to follow your directions or attempt other methods. I apologize for the long, long story but I wanted make sure I did not leave out any detail so this can be resolved ASAP because I am sure I am receiving texts and calls and people are probably thinking I am ignoring them (no one leaves voicemails anymore so how can I know if they called or texted during the phone's sickness). I also apologize if I have broken any forum rules or posted in the wrong section or violated some. Thanks guys in advance. I miss the fat little thing so much.
Oh My god! Sorry but that's too long for me to read, my attention span isn't all that great =p
I will try to help with your questions but I didn't read the whole intro so my answers might be a little redundant.
1.Run "adb logcat" from a cmd prompt on your computer and see if pushing the button registers on the computer
2. um ok??? not a question
3. you will have to re-root but your backups will still be usable after you gain back root
4. boot to recovery (home+power), scroll down to backup and restore, select restore, and select the file
5. I'm not familiar with handcaent so can't offer help there.
6. It's not hard. Downgrade with DREAIMG.nbh to RC29, use update.zip to upgrade to 1.5, install one click root, use it, flash a recovery, and flash a rom.
7. You should write shorter paragraphs =p
8. Again, not familiar with it.
9. HOME + POWER, and BACK + POWER
10. No clue....
11. It's a folder automatically created when you don't unmount your phone before disconectiong the usb. It's useless and you can delete it.
12. When installing a new rom, just wipe everything. It saves you trouble later on.
Hope I helped...
Thanks I will give it a try later today and probably come back with more questions and longer paragraphs
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/
I have been trying to get the clockworkmod on my galaxy tab so I can flash the EXT4 kernel and the overcome ROM but I cannot for the life of me figure out how to do the clockworkmod. I've tried searching everywhere for instructions, this site, google, youtube, and I've had no success in understanding how to do it for my tab, let alone finding where to download the clockworkmod file that I need. I have dialed *#1234# and *#7465625# to get the info of my tab, when I dial the one number it says for everything is off and when I dial the other number I get this info, PDA1000JPJJ1 Phone1000JXJJ1 CSC1000OJPJJ1. I have no carrier that I'm using just running it off of wifi, but if I ever decide to buy a data plan it will probably be with at&t. A friend of mine bought me the tab from afghanistan he told me it was unlocked. I know I have a slot for a SIM card. Just trying to give as much info about the tab as I can cause if what I'm reading is correct you have to install a certain clockworkmod depending on your tab. like I said I just am not understanding how to do this or where to get the files I need. I have rooted the tab and I have the ROM manager and ASTRO file manager apps downloaded and I've tried just tapping on the Flash ClockworkMod Recovery in ROM manager then tapping on Reboot into Recovery and when that happens it pops up in the reboot screen but the text is still green and I believe what it said was it was installing files for clockworkmod recovery but would never finish so I'm assuming I did that wrong. Could some one please help me with this I'm going crazy trying to figure out how to do it? that are too many different post about how to do it and one person saying do it this way while the other says do it this way and I'm not grasping how to do it properly without messing up my tab, it already keeps freezing up on me from time to time and i have to hold the power button in and restart it. Please any help I'd appreciate, Thank You.
Just follow the guide in the overcome thread. Its a pdf file you download and print, with very careful instructions.
I did things in a different order. I flashed the overcome kernal, which did the ext4 reformat, and it installed CWM.
Just in case you havnt found the thread, it's here --> http://forum.xda-developers.com/showthread.php?t=932082
I suggest you print the pdf file and follow it STEP BY STEP.. mark each step you've done if necessary..
Goodluck!
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"
Hi!
This is my first post an I hope I did put it on the right place and I havent found any other post that really matches my problem.
Anyway, I was so happy for being able to bring back stock rom on a rooted SGS2 I9100 who didnt worked proper with its root. In this case, no USB-debugging were necessary.
After this mission I felt ready to try to downgrade the SGS Advance I9070 from stock Jelly Bean to Stock Ginger Bread by mainly following one of all those tutorials about how to do it. And I know its said - enable USB-debugging.
But as I were interupted by my wife just before I were going to proceed, I totally forgot it when I finally went back to my work of downgrading. As I were a bit stressed, I just connected the phone to Odin and slammed the PDA-button like I did with the SGS2. It went smooth all the way through Odin and the green PASS showed up. But when the phone were about to boot up it stuck at the Samsung-logo. Its in a bootloop. After a short time of wondering about what went wrong, it struck my head I forgot to enable USB-debugging. Amen!
So, I forgot debugging while running JB-stock to downgrade to GB-stock. The only thing I can reach now is download-mode except the bootloop Samsung start interface. Its probably occured because I forgot enable debugging, right? And does it mean this device is bricked for real or is there anyway to bring back life?
Best regards // emsoh
emsoh said:
Hi!
This is my first post an I hope I did put it on the right place and I havent found any other post that really matches my problem.
Anyway, I was so happy for being able to bring back stock rom on a rooted SGS2 I9100 who didnt worked proper with its root. In this case, no USB-debugging were necessary.
After this mission I felt ready to try to downgrade the SGS Advance I9070 from stock Jelly Bean to Stock Ginger Bread by mainly following one of all those tutorials about how to do it. And I know its said - enable USB-debugging.
But as I were interupted by my wife just before I were going to proceed, I totally forgot it when I finally went back to my work of downgrading. As I were a bit stressed, I just connected the phone to Odin and slammed the PDA-button like I did with the SGS2. It went smooth all the way through Odin and the green PASS showed up. But when the phone were about to boot up it stuck at the Samsung-logo. Its in a bootloop. After a short time of wondering about what went wrong, it struck my head I forgot to enable USB-debugging. Amen!
So, I forgot debugging while running JB-stock to downgrade to GB-stock. The only thing I can reach now is download-mode except the bootloop Samsung start interface. Its probably occured because I forgot enable debugging, right? And does it mean this device is bricked for real or is there anyway to bring back life?
Best regards // emsoh
Click to expand...
Click to collapse
LOL...:laugh: Wives will remain Wives!
The device is Soft Bricked and can be resurrected..did you follow this procedure: http://forum.xda-developers.com/showthread.php?t=2195673 ?
arneldna said:
LOL...:laugh: Wives will remain Wives!
The device is Soft Bricked and can be resurrected..did you follow this procedure: http://forum.xda-developers.com/showthread.php?t=2195673 ?
Click to expand...
Click to collapse
Haha.. Well, I had to drive her to the shop and that was enough to make me lose my patience of remembering important rules just because I had to go with other important rules. Like the gentleman I am. :fingers-crossed:
Thanx for reply. It makes me glad you do believe its possible to fix this issue. The link you showed is on of those I been looking at before I got started. But after a lot of comparing between several links from i-net, I decided to go with the procedure that the majority declared. For example, in this link its said "re-partition" must be ticked in. The other guides said not. Only "reboot" and "time-reset" to be ticked in.
The stock firmwire I downloaded were from some address connected to Samsung. It means there were only one file with all included just to insert in the PDA. Now, afterwards..I do understand it isent that hard to fill in 3 lines myself instead of one. But it seemed simplier with only one at that time. As I am a newbie about changing software in phones, I were ready to make mistakes but not this mistake and I really dont know what guides who are the best to go with.
Do you think it will make any difference if I go with your link and try again?
Remember, the phone were not rooted. Im really not sure, but I think I read somewhere that if debugging are not enabled on official kernel, theres no way back because cant reach debugging in any way. But I hope its not true.
Now, as far as I understand in my case...what I did was to erase the operation system I had (stock 4.1.2) and filled it up with (stock 2.3.6) but it only reached the gates and not the internal of the phone. It means there are no operating system at all?
Then why Odin shows PASS? And if no communication files can reach the phone, how is it possible that the counter now shows the phone has been rooted? Yes, I tried to root it today and Odin showed PASS again. And as the counter counts, it must mean the phone is not 100% blocked from communication even without debugging enabled?
But still the phone act as described earlier. Only Samsung-logo, bootloop and I can only go forward to download-mode.
:crying:
emsoh said:
Haha.. Well, I had to drive her to the shop and that was enough to make me lose my patience of remembering important rules just because I had to go with other important rules. Like the gentleman I am. :fingers-crossed:
Thanx for reply. It makes me glad you do believe its possible to fix this issue. The link you showed is on of those I been looking at before I got started. But after a lot of comparing between several links from i-net, I decided to go with the procedure that the majority declared. For example, in this link its said "re-partition" must be ticked in. The other guides said not. Only "reboot" and "time-reset" to be ticked in.
The stock firmwire I downloaded were from some address connected to Samsung. It means there were only one file with all included just to insert in the PDA. Now, afterwards..I do understand it isent that hard to fill in 3 lines myself instead of one. But it seemed simplier with only one at that time. As I am a newbie about changing software in phones, I were ready to make mistakes but not this mistake and I really dont know what guides who are the best to go with.
Do you think it will make any difference if I go with your link and try again?
Remember, the phone were not rooted. Im really not sure, but I think I read somewhere that if debugging are not enabled on official kernel, theres no way back because cant reach debugging in any way. But I hope its not true.
Now, as far as I understand in my case...what I did was to erase the operation system I had (stock 4.1.2) and filled it up with (stock 2.3.6) but it only reached the gates and not the internal of the phone. It means there are no operating system at all?
Then why Odin shows PASS? And if no communication files can reach the phone, how is it possible that the counter now shows the phone has been rooted? Yes, I tried to root it today and Odin showed PASS again. And as the counter counts, it must mean the phone is not 100% blocked from communication even without debugging enabled?
But still the phone act as described earlier. Only Samsung-logo, bootloop and I can only go forward to download-mode.
:crying:
Click to expand...
Click to collapse
Don't worry - as long as you have access to download mode you are fine :good:
I am not sure as I never downgraded to GB myself, but from my understanding of posts in here it is partitioning issue.
JB got different sizes or mount points (forgot exactly) of key partitions and that is what is wrong here - it cannot find some components to finish booting.
re-partition is the main thing here.
Get file from this guide.
Key point is:
9)Hit on PIT button and select the PIT file extracted from the downloaded package in first step above (GT-I9070_EUR_XX_8G.pit).
You should be able to use your 1-file-ROM and get it working, as long as you use .pit and tick re-partition.
Worst case scenario - flash JB again (no re-partition needed) and it will be working as before ;]
th3cr0w said:
Don't worry - as long as you have access to download mode you are fine :good:
I am not sure as I never downgraded to GB myself, but from my understanding of posts in here it is partitioning issue.
JB got different sizes or mount points (forgot exactly) of key partitions and that is what is wrong here - it cannot find some components to finish booting.
re-partition is the main thing here.
Get file from this guide.
Key point is:
9)Hit on PIT button and select the PIT file extracted from the downloaded package in first step above (GT-I9070_EUR_XX_8G.pit).
You should be able to use your 1-file-ROM and get it working, as long as you use .pit and tick re-partition.
Worst case scenario - flash JB again (no re-partition needed) and it will be working as before ;]
Click to expand...
Click to collapse
Ok, it makes me a bit more calm and Im starting to believe a bit, theres a way back for the phone to rise again. So you mean it might not be the failure of missed debugging, instead the critical main thing can be re-partiton?! It sounds very possible based on what you said.
The thing now is, ofcourse I would be satisfied if my first plan come true. But right now I really dont care what version it´ll be running, rooted or not. I only want it to act like a smartphone again n matter what´s installed. So I will go with your advise and test it one by one.
Thanx so far! To be continued..
SOLVED Forgot USB-debugging downgrading
I must admit I didnt really believed it wud work even I hoped it wud do. Before I started the new operation I gave it the chances 75% negative and 25% positive. But I was so wrong.
It really passed!!
Im so thankful for the support. To arneldna who made me reconsider this current version and tutorial for firmware downgrade. And to th3cr0w who explained and really pointed out the missing spot in my failure of action during the installing process.
The solution - Just to be sure, I followed the tutorial exactly. When it rebooted it showed up not to be my country region so I did it again with my nordic region all-in-one tar-file. This time just to be safe, I enabled usb-debugging and also unknown sources. Idk if it had any use but just in case of. And Voila..back to my region and everything seems to be as it was the first time I started up the phone when it was new last summer. After that I did a factory reset which I learned is useful to do.
As this was only one of my childrens phones, I actually got 3 more of the same to downgrade to work smooth again. But now I learned another lesson. I hope!
THANX A LOT to both of you! :good:
emsoh said:
I must admit I didnt really believed it wud work even I hoped it wud do. Before I started the new operation I gave it the chances 75% negative and 25% positive. But I was so wrong.
It really passed!!
Im so thankful for the support. To arneldna who made me reconsider this current version and tutorial for firmware downgrade. And to th3cr0w who explained and really pointed out the missing spot in my failure of action during the installing process.
The solution - Just to be sure, I followed the tutorial exactly. When it rebooted it showed up not to be my country region so I did it again with my nordic region all-in-one tar-file. This time just to be safe, I enabled usb-debugging and also unknown sources. Idk if it had any use but just in case of. And Voila..back to my region and everything seems to be as it was the first time I started up the phone when it was new last summer. After that I did a factory reset which I learned is useful to do.
As this was only one of my childrens phones, I actually got 3 more of the same to downgrade to work smooth again. But now I learned another lesson. I hope!
THANX A LOT to both of you! :good:
Click to expand...
Click to collapse
Glad to know you fixed it.. Appreciate your patience and efforts... :thumbup:
You don't care where I sent it from....!