[Q] Wow I feel lost... - G1 Q&A, Help & Troubleshooting

I bought my G1 on the first day I could. I rooted it as soon as you could so I could get apps to SD and bump up the CPU a bit. I loved this phone. I eventually upgraded to an HD2 so I could run Android on it and stick with T-Mobile. I just booted my G1 back up so that I could install some apps to use it as a remote webcam. I did a factory reset and then got stuck during the activation screen. I know you can use ADB to bypass this but I figured I might as well just install a new rom on it that can activate the wifi during the startup process.
This is where I feel lost. I haven't booted up my G1 in ages and thus I haven't flashed it in ages. I would like to install this rom: The Official "KANGED" CM7 for DS ... but I don't have the correct SPL or Radio I am guessing. I currently have HBOOT-1.33.2005 and Radio 2.22.19.26I. I have a recovery image installed (RA-dream-v1.6.2) so I can flash roms and radios and such but I am having trouble finding threads that talk about the proper files to install. If somebody could just point me in the right direction I would appreciate it. Thanks!!

http://forum.xda-developers.com/showthread.php?t=831139
this will have all the needed info
so to clarify - via fastboot update recovery then radio then spl
when finished download rom and gapps
congrats your done!

Well, there's also a way to flash these RADIO and SPL, shown by YOU (demkantor) but as he said, fastboot is a little bit more complicated for me, but if you have it , just use fastboot. And remember, 'Fastboot is your Friend' !!!

Related

Trying to Root HTC DREAM: nightmare

Hello all. This isn't your usual noob rooting thread. I'm having some serious problems trying to root my phone, I need some professional help here. I literally have scoured every tutorial trying to figure this out, my phone has been down for two weeks. PLEASE help me out, I looked everywhere trying to fix this thing.
Here is my problem: Downgraded from 1.5 to RC29, but when I try and update from RC29 A) Rainbow/Serial0 B) When I try to go into the OS it hangs at the T-Mobile G-1 Screen (I have a Rogers Dream).
Here is where my phone is at now:
DREAM210 PVT 32B
HBOOT 0.95.0000
CPLD-4
RADIO-2.22.23.02
Sept 2 2008
I can access the recovery options, but I can't update. When I tried to access sqlite_stmt_journals it told me it couldn't cd there even though when I ls'ed it told me the directory existed.
Even when I thought I used update.zip and flashed to the newest version it still had the old T-Mobile on there. Please help, I'm desperate guys! Anything!
You guys are great, thanks in advance. I'll check this thread constantly. Regards.
I'm not sure how you are where you are.. (you must have been rooted at some point to install RC29; rogers phones won't install it without doing so.. however for many it boots into android more successfully)
It also sounds like you have a custom recovery as stock dream recoveries don't have ADB or console applications. In addition having 2.22.23.02 indicates you changed the radio after flashing RC29 (that may be the issue with boot.. but as Android 1.0 isn't that interesting we can leave the radio in question)
So here is some questions
1) is it stock recovery (has a /!\ image and you must use ALT+L to see the options) or a custom recovery; if a custom recovery can you give more info like is it RA or clockwork recovery
2) Where are you seeing sqlite_stmt_journals in adb with recovery booted or while stuck on the G1 screen? If the G1 screen maybe a 'adb logcat > out.log' will help attach said out.log to your post.
With this info I can try to help you find a way out of this mess.
Thanks - I appreciate the reply. It's been a strange path for sure. But I managed to escape the one I was in and into another one.
I managed to put AMON RA's 1.7.0 recovery on my phone, and upgrade to Android 1.6 (Cyanogen 4.2.15.1). My radio at that point was 2.22.19.26i (obvious mistake). But regardless it worked for whatever reason. Regardless.
I pumped straight through that (as in the instructions after flashing DangerSPL) to putting Cyanogen 6.0.0DS on, then the EB11 kernal (even though I wasn't sure if I needed it, but it said it you had a Rogers phone you should) and the tiny GAPPS. It said welcome to Cyanogen 6.0.0 in the recovery screen, but when I rebooted it still went to the T-Mobile G1 screen.
So i sasw my error with the radio, and went to switch it from the one I had to the correct one: 3.22.26.17 (as per the site). So I thought I should reflash the Danger SPL just to make sure I was clean to reapply the Cyanogen update after.
However, when I applied the 3.22.26.17.zip, and rebooted and held camera it just held at the t-mobile G1 screen. I waited for 10 minutes then had to pull the battery.
Now I can't boot into the phone, into recovery, or fastboot. What. a. mess.
Thanks in advance for the help, this really is a nightmare for me.
nudasveritas said:
Thanks - I appreciate the reply. It's been a strange path for sure. But I managed to escape the one I was in and into another one.
I managed to put AMON RA's 1.7.0 recovery on my phone, and upgrade to Android 1.6 (Cyanogen 4.2.15.1). My radio at that point was 2.22.19.26i (obvious mistake).
Click to expand...
Click to collapse
NOT a mistake at all! There is NOTHING wrong with a 2.x radio!!!!
But regardless it worked for whatever reason. Regardless.
Click to expand...
Click to collapse
Probably worked because it was a perfectly valid thing to do!
I pumped straight through that (as in the instructions after flashing DangerSPL) to putting Cyanogen 6.0.0DS on, then the EB11 kernal (even though I wasn't sure if I needed it, but it said it you had a Rogers phone you should) and the tiny GAPPS.
Click to expand...
Click to collapse
Your mistake was the EBI1 kernel -- you had an EBI0 radio, that means that you needed to use the (default) EBI0 kernel.
It said welcome to Cyanogen 6.0.0 in the recovery screen, but when I rebooted it still went to the T-Mobile G1 screen.
Click to expand...
Click to collapse
This is because CM doesn't change that image. It came with the NBH file you installed. Nothing to worry about. The reason it didn't boot is because you had the wrong kernel installed.
So i sasw my error with the radio, and went to switch it from the one I had to the correct one: 3.22.26.17 (as per the site). So I thought I should reflash the Danger SPL just to make sure I was clean to reapply the Cyanogen update after.
Click to expand...
Click to collapse
I'm trying hard to understand what you did... at this point, you had... 1.33.2005 SPL and 3.22.26.17 radio?
This is a valid pair, BUT, you had an EBI0 recovery installed and just switched to an EBI1 radio... and have the thing set to boot-recovery. This is an awkward spot to be in..... basically, since you had a 1.33.2xxx SPL installed, you should NOT have tried flashing radio through recovery -- you had a perfectly good FASTBOOT, and should have used THAT.
However, when I applied the 3.22.26.17.zip, and rebooted and held camera it just held at the t-mobile G1 screen. I waited for 10 minutes then had to pull the battery.
Now I can't boot into the phone, into recovery, or fastboot. What. a. mess.
Thanks in advance for the help, this really is a nightmare for me.
Click to expand...
Click to collapse
This is an interesting spot you're in, I'm not sure how to resolve it. You appear to have an SPL and RADIO that are compatible, but are, nevertheless, bricked in a boot-recovery mode.
Following the update-radio cycle, the command field of the misc partition gets set to boot-recovery, with the parameter set to format the cache partition. Well, you have an EBI1 radio and an EBI0 recovery kernel, so recovery won't boot to finish its cleanup.
The reason I went from the 2.x radio to the 3.x radio is because on the walkthrough it said that the 2.x radio was for non-US whereas the 3.x radio was for Rogers dream customers. But something that might help:
If I plug in my phone via USB, it won't acknowledge it as either a Fastboot or Recovery/ADB device, but the computer does acknowedge it as an "Unknown USB device," while under Android Devices there is the Android Composite ADB Device... which says it cannot start because of Code 10. Windows 7 Pro, 64-Bit is my OS.
Would repartitioning or formatting the SD card do anything? Also, start+menu+end won't do anything either.
Thanks again folks for the help, I am in a situation here.
I'm stuck in 1.0 with some keys not responding like "s" and am stuck. Any chance this could be what I did?

ROM help

Hello all. new user here. Where to start where to start.
I consider myself an intermediate PC user and a noob with cellphones. I am a novice at Command prompt and ROM's and such.
Here's my problem..
I recently purchased the HTC Dream (Google G1) GSM Unlocked from America.
It came loaded with Android 2.1 on it.
I am trying to bypass the activation screen and cannot find anyone with a data SIM to fix the issue. So I've attempted to mod. Had some help with an advance PC user and he is also stumped.
I currently have no OS on the phone.
I have successfully rooted the phone, updated Hard SPL, and I originally had Radio version 1.22.12.29 and successfully updated it to 2.22.23.02
I have followed instructions to best of my knowledge and tried older and newer versions of Cyanogen mod. I get the error E: Can't find update-script installation aborted.
I have also tried a couple of other totally different ROMS..same issue.
I currently am running Hboot 1.33.2005
It's hard to find clear instructions on what exactly works for the phone. I don't want to brick it lol, I paid good money.
Please help I am a total noob I'll admit. If you could break down the terminology lol. thanks a million!
If u can get into recovery flash from a sd card
1 put your rom on the root of your sd card
2 pit card Into Phone
3 boot into recovery
4 wipe then flash rom
Reset your phone and see if it boots up

[Q] Running out of options - soft brick on 1.33.0006 spl

Okay, so a few years ago I successfully rooted my boyfriend's G1 and swore never again to go anywhere near the process.
However, said phone has now been given to my boyfriend's dad, and he's managed to install a couple of custom roms. In the last week though, he's totally screwed it up. Didn't seem to follow any sort of backing up process, or can even tell me what tutorial he was following to get it in this state.
The phone hangs at the splash screen. I can get into fastboot/hboot but there are only a few options available.
SPL is 1.33.0006 which I can gather is bad from my reading.
Hboot info is:
Dream PVT 32B Ship S-on
Hboot - 1.33.0006 (Dream11000)
CPLD-4
Radio-2.22.19.261
I have tried:
Initially I just tried going into recovery mode (I think that's what it's called - home & power) and wiping the data to see if that stopped the screen hanging. It didn't.
Putting rc7 dreamimg.nbh on the phone and loading via hboot/fastboot. When I do this it fails saying 'Main version is older.'
After doing some searching, I see someone mentioned this would mean you need to use the goldcard method. I vaguely remember having to do this a few years back on the phone when I rooted it the first time.
I go through the process, following an unlockr tutorial (can't post the link - sorry).
However, I get the same response through fastboot - 'main version is older'.
At this point I decided to try flashing a recovery image via the adb. Go through the process of installing everything etc. but when it came to installing the usb drivers for the phone, it failed although it did install the htc bootloader. I checked using adb devices command to see if it was picking anything up and it was however, when I go into the command prompt and try to do anything I just get a <remote: not allow> message.
It's only after I look for <remote: not allow> message error that I understand that 1.33.0006 is a 'perfect' SPL, and explains why I can't really do anything.
I really didn't want to resort to forum posting (one of the reasons I swore never to go near the G1 again after rooting was because I *know* I'm not tech savvy enough to be messing around with this stuff), but after spending around 6 hours over two days on this I'm absolutely stumped. The problem is, I'm stubborn so I hate to give up after spending so much time on the stupid thing (bye bye flexi day), so if anyone has any suggestions, or if they could just tell me it's a lost cause then it might help.
Thanks for your time...
do you have the UK version of phone or the US version?
can you get into recovery?
Sorry, it's the UK version - I can get into recovery (if that's home and power ?) I think. Thanks.
What nbh file was flashed prior to this? (almost sounds like the states someone was in after flashing the sappimg on a dream with 1.33.0013d..
Well first thing is to make a gold card if you don't already have one.. Then we can try one of two things. (you can make it on another phone, its a property of the sd card not the phone)
1) (may have the same main version is older problem but easy if it works) place the Orange nbh:
orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0)
onto the root of the goldcard named DREAIMG.nbh
If this works (or at least flashes the s=off SPL) you are in the clear simply use fastboot to re-install the 2708+ recovery/radio/spl then install a rom as per here
2) If option 1 failed... well this is an annoying process.. and risky if you take shortcuts so don't ..
A -- This time put the rogers e911 patched nbh rogers_1.89.631.1.nbh MD5:25bfcc329679e4869b3d65f673e463ac
onto the root of the goldcard named DREAIMG.nbh
This is the larges "main version number" in an official nbh for the Dream we have.
If that fails to flash (try again) if it still fails.. well I'm not sure what to do if both boot/recovery are failing (short of jtag anyway)
B -- If it succeeded you now (despite any labels on your phone) have a rogers dream.. (I mention this because working with an ebi1 radio is a bit different than the ebi0 and you don't want to brick your phone)
Ok next step is re-root: http://forum.xda-developers.com/wiki/index.php?title=Rooting_HTC_Branded_EBI1_Dreams
(Sections A-D inclusive)
C -- Before installing a rom.. now that an eng SPL is installed you can use fastboot (and only fastboot with the 3.22 radio) to install the 2708 radio and thus have a more commonly supported system:
per Follow this 2708+ install
remember do not install a 2.22 radio via recovery while a 3.22 radio is installed you will brick your phone
--
Best of luck.. really sounds like something happened that ought not have.
Thank you!
Option 1 didn't work - I still got the 'main title is older' message.
However, option 2 (after a small wobble) worked! First time I tried it, it failed stating 'partition update fail!' but after a reboot (which showed the rogers logo - a change from before) and a retry, it worked! I followed the rest of the provided instructions and installed the BIFFMOD V2.1-EZTerry 2708 port and all is well!
Thank you so much again for your help, it really is appreciated. I would not have been able to do this without your help - I've sent a small donation through as a token of thanks.
I've learnt more about G1s than I ever wanted to know, but thanks to you (and the information provided by the XDA community) it wasn't all wasted time!

[Q] Al little direction...

OK here it is. My G1 is currently on version. 1.0 (RC29) stock recovery as well. i have been scanning the forums here and keep finding info with broken links and pages that say they are out dated. Can someone here post me a few links to some current info on rooting and installing a froyo rom (gingerbread was too laggy) the part that seems to get me lost is all the radio, spl, and recovery menu options out there and after 3 attempts at rooting and installing a new rom last night all i could get the phone to do was hang at the g1 screen. so now im back to stock on the phone and will wait on some help before i attempt this again. I used this site to root and hack back when i used the phone for PSFreedom, but it wasnt as cluttered with info overload.
The phone is:
T-Mobile G1 US
Firmware 1.0
PS I already installed Telnet but thats as far as I have gone. And if you can point me to a Froyo rom that is stable and runs without lag I would really appreciate it. Thanks.
ok this guide is easy to follow... [Guide] (8-18-11) G1 How-to: Root, Un-Root & Everything in-between
just folow instructions and i will help you along the way if you need it
ok i did the wipes and everything in the first step but when i get to the google sign in screen the phone shows no signal (usually 4 bars where i am) so i cant get past the google screen to do the next step.
wait you said you were on 1.0 already? so which file did you flash the update.zip? and you cant sign on..?
thats just the update to 1.5 so im not sure why you would have no signal...
no idea either its rooted though i have tried a few roms so far.
GINGERBREAD-DS-Beta-20110716 (hangs at G1 Screen)
cos-ds =07182011 (makes it as far as the bluish android logo and then loops)
will the 1.5 update work with the hboot0013d and the 2708 radio?
when i flashed the 1.5 update (as in the guide) it made it to the google sign in screen and wouldnt let me by, so i reflashed the 1.0 file and got my service back restarted the guide and skipped the 1.5 update the second time.
my fast boot info:
Dream PVT 32b SHIP S-on
HBOOT 1.33.0013d (drea10000)
CPLD-4
RADIO 2.22.28.25
OCT 21,2009,22:33:27
wait no that dont make sense... lol are you trying to root your device?
if you have 28.28 and 0013d than you are rooted and should be good to flash roms.. all you need is to make sure your sdcard is properly formatted and partitioned lol
some roms require an ext4 partition... if you have amonra recovery than go to partition sd options.. choose partition sd and set swap to 96mb and ext to 512mb.. than upgrade ext2 to ext3 than upgrade ext3 to ext4.. than wipe all data, cache, system than flash a rom..
I did all the steps i managed to get it rooted but with the specs of hboot and radio i tried 5-6 roms and none booted up i even tried the SenseLX one with MTD and without, and never made it past the G1 screen i have even gone back to rc29 a few times and started over. this last attempt i decided to just got to 1.6 so i did the upgrades for that (unrooted) and when i hit 1.5 i lost all cell signal again, went to 1.6 and still didnt have it now im back to 1.0 again. im lost on what could be going on.
so your saying you had radio 28.25 and hboot 0013d and you couldn't get the roms to boot?
and that you cant get a cell signal?
-for the rom issue i think it may be your sd card...
-for the signal issue you might need a new sim card... you can get them replaced for free at a tmobile store..
New SD card and sim in phone and attempting this again... ill keep you posted on any progress if any.
This is a regular US T-mobile branded G1, not a unbranded or Asian, model?
If you are still having these issues, and starting from any Engineering SPL, you might try the orange-1.58.73.2.nbh file over here.
It updates radio/hboot/kernel/system all at once, in a known working set.
You can change the French over to English, but might need to know a bit of French to find the setting, and I even kept it on a phone for my kids to play with (no sim) just to run some apps via wifi.
Then if you get REALLY stuck again with updating, just flash back to the orange NBH, it is much easier then going all the way back to RC29 and rooting again.

[Q] need some help

hello,
I hope someone could help me as i have no idea how to my G1 back to stock.
i tried to flash my g1 to an froyo build but i couldn't do anything anymore. now i try to get it back to stock rom.
the only thing i still can do on my phone is i can get into recovery mode...
i can't get to the rainbow screen.
i have an dutch G1 but i cant get any other of the specs anymore cause i dont know how to get them on this phone.
i hope someone could help me as i tried to search a lot on Google and XDA but i could not find anything related to this ****ty problem.
thanks in advance for the one who could help me.
greets Ollievssn
Power + Back takes you to recovery, too? Did you check whether your home button is stuck?
Power + Back also works.
but what can i do with this?
EDIT: i pluged in my USB cable and i saw it was Fastboot. But i still dont know what i can do with this
If you have a working fastboot mode, you can do almost everything, i.e.
- flashing a new recovery / rom
- flashing new radio / spl
- ...
A tutorial you can find here
Probably it's enough to flash a new rom to solve your problems. In that case, you should first select the rom you would like to run, then to flash the requirements (i.e. SPL, radio, etc.) and than the ROM.
What SPL / radio do you have installed? Can you post what's written on the fastboot screen?
The thing written (wrong spelling i guess) on my fastboot screen is:
DREA110 PVT 32b
HSPL10.95.3000
CPLD-4
RADIO-2.22.19.26 1 or I (i couldn't tell from the screen)
Oct 20 2008
Ok, you have installed the so called "HardSPL", which is a custom SPL which unfortunately doesn't allow you to flash recovery / radio / SPL using fastboot.
Now you have different possibilities:
1) keep your spl / radio and flash a rom which supports your SPL/radio. The old enomther roms, CM4/5 should work without problems
2) keep your spl / radio in combination with custom partition tables. In that case, you should be able to run CM6 or other Eclair/Froyo based roms, too.
3) Update your SPL and/or radio and you will be able to run all roms available for the G1
In your case, updating the SPL is to be done in recovery mode. This is a bit more risky that doing so in fastboot, because flashing is done while setting the "reboot into recovery" flag. If for some reason the recovery cannot be started correctly you will have a brick.
There are some tutorials here in the G1 area guiding you through these steps, unfortunately I don't have the links available at the moment, but if you search for it, you should find it easily.
Btw. if you really want to return to tock, you can also flash an original image ...
i really want to return to stock rom but i dont know how
There are some OTA images available which you can flash. The easiest way would be the "dreaimg.nbh", but this will give you only Android 1.1.
There are some other images available (at least one which give you Android 1.5), but at the moment I don't have the link. Additionally all the original roms do provide only a limited number of languages, so probably you need to check first, whether your language is supported by those ota-images ...
Probably tomorrow I will have a look whether I can provide you with a / some link(s).
That would be great.
but for now i will keep trying to find something, and thanks to your notes i probably will be able to find something

Categories

Resources