Hi I hope someone can help with this issue - I've been doing my own research and so far I've found no solution. Funny enough I thought this was a pretty unique issue but like with most things when you google them you start realising there have been several posts relating to the same issue. Unfortunately they've either been abandoned or unsolved.
Here's the issue and I'll try and provide as much information here as I can. Hopefully if we can work it out not only will it help me but all the other posters who've had this issue.
Like with other postsers I havent had this issue on a previous handset. I had to send my G1 in for repair due to it rebooting randomly and the usb port not working and it locking up - test came back saying hardware failure. (but my GPS worked at least) - The company Tmobile use for repair is called SBE ltd (im in the uk) - They replaced the mainboard (and yes its PVT not DVT).
When I got it back I was anxious to just get it back to how it was when I had it last. They'd given me a replacement cruddy phone which was driving me mad so I got straight on the case and rooted it - heres exactly what I did. I know theres other methods like the terminal trick but I'd done this one before and had the guide handy so just did it again -
1) I first downgraded to RC7 (uk)
2) Then upgraded to cupcake (1.5)
3) Turned on phone went to marked downloaded Linda File manager
4) I put FlashRec.apk and amon ra recovery1.2.3.img on the root of my SD card (which was just named recovery.img)
5) I ran the flashrec program and ran the command - /sdcard/recovery.img to install my custom recovery
After this I rebooted and went into recovery
In recovery I clicked on Partition SD Card > Partition SD
then selected 96mbs for Swap, 512mbs for ext2 and fat32 for the remainder. Finally clicked on Partition SD Card > SD: ext2 to ext3
Once That bit was done I Simply put the radio I was using along with SPL and rom on the root and updated.
The files I used were
radio - ota-radio-2_22_19_26I
SPL - Danger SPL
ROM - update-cm-5.0.8-DS-signed
I flashed the Radio first then wiped
Then I flashed the SPL then wiped
Then I flashed the rom and Gapps
Everything looked great - I got excited started playing around with it and putting my music and apps on it and I smiled sat back and breathed a sigh of releif.....until I tried using my GPS
....GPS wasnt working...could get a rough locoation with Cell towers but no GPS signal as such. Then it'd randomly work sometimes with google maps but not google navigator or any other navigation apps like Co Pilot.
So I did what anyone would.. spoke to a few people did a small bit of research and was advised by some it might be my radio was out of date so I loaded the trust DREAMIMG file on and did the whole thing again
Same process but this time I used Amon Ra 1.7 (thought I may as well update this as well)
Radio - G1-radio-2_22_23_02
SPL - Danger
ROM - update-cm-5.0.8-DS-signed
Still no luck got a nicer looking recovery image and everythign seems to run like a dream but no GPS signal tried turning it off and on and off an on at diff points.
I'm up for trying anything (read into that as you will) - but guys I'm desperate. I even ran FireRat's patch to increase my internal memory from 42mb to 78mb. Sorry if this post is long winded and boring but I wanted to explain it properly to finally get to the bottom of it.
So to put it bluntly - Rooted the phone - loaded CM5.0.8 no GPS
In my phone info it says -
Firmware 2.1-update 1
Baseband version 62.50SC.20.17H_2.22.23.02
Kernel - 2.6.34-cyanogenmodshade (at) toxygen #1
Build number - EPE54B
In fastboot info is -
DREAM PVT 32B ENG S-OFF
HBOOT- 1.33.2005 (DREA11000)
CPLD-4
RADIO-2.22.23.02
Apr 20 2009, 15:30:43
--------------
So far all I can find is that others have had similar issues - I did notice a few CM5 early builds gave people GPS issues but it seemed sorted in the final build and this is the same rom I used before my replacement G1 (or mainboard at least) and the GPS worked fine.
I've also noticed some are saying about codes to put in on dialers that may help. Some say its the radio which is why i updated it. some say it could be using the right class of radio EBI0: 1.x and 2.x - but i dont really understand that. And others suggest doing things like disabling the location settings for wireless networks and only having GPS ticked. I've tried most of this and still nothing.
Thanks in advance you guys deserve a medal for just reading this - I hope someone can help!! Imagine having a phone that messed up due to hardware issues and waiting 3 weeks with a bad loan phone - finally getting ur android back and then this happens!! - words cannot describe the anger ! - thanks again
vinemo said:
Hi I hope someone can help with this issue - I've been doing my own research and so far I've found no solution. Funny enough I thought this was a pretty unique issue but like with most things when you google them you start realising there have been several posts relating to the same issue. Unfortunately they've either been abandoned or unsolved.
Here's the issue and I'll try and provide as much information here as I can. Hopefully if we can work it out not only will it help me but all the other posters who've had this issue.
Like with other postsers I havent had this issue on a previous handset. I had to send my G1 in for repair due to it rebooting randomly and the usb port not working and it locking up - test came back saying hardware failure. (but my GPS worked at least) - The company Tmobile use for repair is called SBE ltd (im in the uk) - They replaced the mainboard (and yes its PVT not DVT).
When I got it back I was anxious to just get it back to how it was when I had it last. They'd given me a replacement cruddy phone which was driving me mad so I got straight on the case and rooted it - heres exactly what I did. I know theres other methods like the terminal trick but I'd done this one before and had the guide handy so just did it again -
1) I first downgraded to RC7 (uk)
2) Then upgraded to cupcake (1.5)
3) Turned on phone went to marked downloaded Linda File manager
4) I put FlashRec.apk and amon ra recovery1.2.3.img on the root of my SD card (which was just named recovery.img)
5) I ran the flashrec program and ran the command - /sdcard/recovery.img to install my custom recovery
After this I rebooted and went into recovery
In recovery I clicked on Partition SD Card > Partition SD
then selected 96mbs for Swap, 512mbs for ext2 and fat32 for the remainder. Finally clicked on Partition SD Card > SD: ext2 to ext3
Once That bit was done I Simply put the radio I was using along with SPL and rom on the root and updated.
The files I used were
radio - ota-radio-2_22_19_26I
SPL - Danger SPL
ROM - update-cm-5.0.8-DS-signed
I flashed the Radio first then wiped
Then I flashed the SPL then wiped
Then I flashed the rom and Gapps
Everything looked great - I got excited started playing around with it and putting my music and apps on it and I smiled sat back and breathed a sigh of releif.....until I tried using my GPS
....GPS wasnt working...could get a rough locoation with Cell towers but no GPS signal as such. Then it'd randomly work sometimes with google maps but not google navigator or any other navigation apps like Co Pilot.
So I did what anyone would.. spoke to a few people did a small bit of research and was advised by some it might be my radio was out of date so I loaded the trust DREAMIMG file on and did the whole thing again
Same process but this time I used Amon Ra 1.7 (thought I may as well update this as well)
Radio - G1-radio-2_22_23_02
SPL - Danger
ROM - update-cm-5.0.8-DS-signed
Still no luck got a nicer looking recovery image and everythign seems to run like a dream but no GPS signal tried turning it off and on and off an on at diff points.
I'm up for trying anything (read into that as you will) - but guys I'm desperate. I even ran FireRat's patch to increase my internal memory from 42mb to 78mb. Sorry if this post is long winded and boring but I wanted to explain it properly to finally get to the bottom of it.
So to put it bluntly - Rooted the phone - loaded CM5.0.8 no GPS
In my phone info it says -
Firmware 2.1-update 1
Baseband version 62.50SC.20.17H_2.22.23.02
Kernel - 2.6.34-cyanogenmodshade (at) toxygen #1
Build number - EPE54B
In fastboot info is -
DREAM PVT 32B ENG S-OFF
HBOOT- 1.33.2005 (DREA11000)
CPLD-4
RADIO-2.22.23.02
Apr 20 2009, 15:30:43
--------------
So far all I can find is that others have had similar issues - I did notice a few CM5 early builds gave people GPS issues but it seemed sorted in the final build and this is the same rom I used before my replacement G1 (or mainboard at least) and the GPS worked fine.
I've also noticed some are saying about codes to put in on dialers that may help. Some say its the radio which is why i updated it. some say it could be using the right class of radio EBI0: 1.x and 2.x - but i dont really understand that. And others suggest doing things like disabling the location settings for wireless networks and only having GPS ticked. I've tried most of this and still nothing.
Thanks in advance you guys deserve a medal for just reading this - I hope someone can help!! Imagine having a phone that messed up due to hardware issues and waiting 3 weeks with a bad loan phone - finally getting ur android back and then this happens!! - words cannot describe the anger ! - thanks again
Click to expand...
Click to collapse
only thing i reccomend is upgrading to the latest cm nightly or redownloading the 508 zip from wiki.cyanogenmod.com but some good steps to follow are found here
do you think it could be my version of cm5.0.8 isnt uptodate? I'll re download do you suggest going to CM6? I didnt think that was stable - but this version worked before which is why im stumped I dont mind trying this tho....just wanted to clarify what you meant.
in your guide that other guy says about certain steps being wrong I dont understand what he's talkin about it all makes sense to me when he said steps 2-6 should never be done what did he mean? lol
As a test try another ROM e.g. SpeedTeam
Just for ****s and giggles, have you opened up your phone to make sure all the cables, and attachments are in place? You said they replaced the mobo. Repairmen have frequently been known to screw other things up when they fix another problem. I would check this first. I've ran every flavor of cyan, and bought copilot before google gave us navigator. I've never had a problem with my gps. I modded my g1 bronze over a year ago to replace the silver keys with black. When I did, I ran a screw through the long coax cable. I got one off ebay from a guy in the uk for about 10-12€. While I was waiting on it, I still used my phone as a comp by using wifi. It works on a separate smaller coax cable. I have no idea if the gps reciever is part of one of those smaller boards or not. It's worth looking into never the less. If you are interested, I will save the phone's pdf manual that covers disassembly on my server and you can give it a look. I've taken mine down several times for other mods since then. Just let me know and I'll upload it.
Sent from my HTC Dream using XDA App
Ok thanks Id like to see the disassembly guide but as my phone is still under warantee i dont know if its a good idea as Ive never taken it apart surely they tested the phone before it was sent back??
I do know what you mean tho they could have easily put it back together and missed something is there no other reason apart from hardware?
these other suggestion such as radios spls roms etc - are they worth looking into or not?
You said your gps works...just not accurately...I don't see how it could be a disconnected cable.
The gps is flaky on anything but the stock Donut rom IMO.
I have had three g1's personally.
I have rooted two for friends.
I have played with unrooted and rooted G1's and found this too be an issue with all of them not on the actual stock rom.
For those that have a working GPS on all Eclair/Froyo roms, good for you, but I can tell you that there DEFINITELY is an issue with the GPS on Eclair/Froyo for some people
well....i understand what you mean G1forFun - but Ive had GPS working on custom roms before i had my mainboard replaced on my G1 - and i didnt say it sorta works - what happened was the other day it sorta picked up a gps signal on google maps but never worked on navigator or Copilot etc - and it only ever sometimes got a signal on google maps like once or twice and now i cant seem to get it to again at all - this is driving me nuts when it used to 'sort of work' it was using wireless data to triangulate my rough location but it didnt pinpoint me exactly apart from the two times it luckily worked. however ive been trying it without the wireless data location and i get - your location is temporarily unavailable and in GPS test apps nothing apart from my compass
ok...
anyone have any other ideas? Ive done a BART backup to the rom i had (chromatic) which had GPS working on my old mainboard before the repair still everything working perfectly without any issues EXCEPT GPS
this is so strange...
Ive tried a BART restore to another rom GPS was working and I reflashed CM5 when I updated the radio and recovery image incase it was the radio. Ive just gone back to stock too and still not working with GPS - i just loaded the dreamimg.nbh and flashed that.
ok gone to stock now....and still no GPS im guessing when they repaird it they messed up the GPs or didnt plug it in.... or it became faulty and they didnt check it for some reason.
Anyway back to repair factory for another long wait....grr
Related
Hi everybody,
I was trying to load the cyanogen mod to my G1
Had Android 1.6 and Radio 2.22.23.02
I downgraded to RC29 successfully
Rooted my phone
Loaded recovery-RA-dream-v1.7.0.img. Flashed successfully
Then started following instructions below:
wiki . cyanogenmod / index.php / DangerSPL_and_CM_5_for_Dream
I got stuck in step 6
It is probably because downgrading to RC29 also downgraded my radio version. I did not check the radio version again after I downgraded
Using danger.spl bricked the phone
I searched online and found some solutions with JTAG, but I am in Turkey and do not have access to purchasing these from ebay or the know-how to apply them (as you can tell from my mistake above!)
1) I found the below solution, but not sure if it will work:
code . google / p / android-roms / wiki / Unbrick
They say it will only work if you have soft-bricked your G1. I'm not sure
2) Others say I need to call T-mobile Customer care (where I purchased the phne from), but that was about a year and a half ago. How long is the warranty on the G1? 1 year or 2 years?
3) And yet others say use it paper-weight
Should I go for option 3?
What do you think?
Wiki Instructions
What is DangerSPL?
This SPL is actually a port of the Magic/MT3G (Sapphire)'s SPL to the Dream/G1. Called danger because not only does it wipe your data in the repartition process (data can be restored with Nandroid restore after flashing DangerSPL), it has a chance of bricking your phone if you would ever choose to downgrade the radio after flashing it (see below for compatible radios). Never flash a 1.x, 4.x, or 6.x radio with DangerSpl
It is not required for CyanogenMod versions 4.X (CM4) and below, but required for the CM5 series on the G1/Dream.
Why is it required for the CM5 series on G1/Dream?
The G1/Dream's /system partition was originally created to take ROMs up to 64MB. The CM5 series for the G1 & Magic/MT3G is currently too big to fit on this partition.
Why don't Magic/MT3G users have to apply it?
The Magic/MT3G (Sapphire)'s /system is set to take ROMs up to 96MB by default, so no SPL change is needed.
Is it dangerous?
While the method of applying it has been perfected over the course of its use, any modification of SPL/Radio/ROM carries with it an inherent risk. That being said, if you pay attention, follow instructions, and plan your approach, it is actually an easy process.
How do I check if I already have DangerSPL?
Boot into fastboot mode by turning the phone on while holding the camera button and pushing the power button. The second line contains your SPL version. If it ends in 2005 (eg 1.33.2005) then you have DangerSPL installed already. The line with RADIO tells the radio version, which is important if you don't have DangerSPL. To leave fastboot mode, press MENU+SEND+END at the same time.
Installation
Warnings
Make sure that you have a full battery during the steps below and at no point remove power from the device (i.e. no battery pulls!). See the first two bullets in troubleshooting regarding battery use after flashing CM5 and fixes for higher-than-expected battery drain.
There has been some development/debate over DVT/PVT and bricks. Optional reading (but still recommended): XDA forum
Prerequisites
A rooted G1/Dream
A compatible radio (IMPORTANT: If you just rooted, the RC29/RC7 install includes a 1.x radio and you MUST install one of the 2.x radios below before DangerSPL)
2.22.23.02 seems to get more bars for T-Mobile US customers, though non-US users might have better luck with 2.22.19.26i.
(HardSPL/Engineering Spl Users) Radio installations can be had by fastboot flash radio radio.img after extracting radio.img from the .zip
Either of the following radio versions is acceptable.
Radio 2.22.19.26I
Radio 2.22.23.02 (G1)
Rogers Dream users: A 3.X radio is Danger compatible (eg 3.22.26.17)
Failure to meet the Prerequisites WILL result in a BRICK!
Files required
Danger Spl
gapps-ds-ERE36B-signed.zip, Mirror1
Latest CM5 for Dream/Sapphire
ONLY Roger's Dream users: EBI1 kernel for 5.0.x
Steps
It has been brought up that Clockwork Recovery struggles with this guide, so Amon_ra is v1.7.0 recommended. If you have CM or older recovery, upgrade to Amon_Ra first.
Please if you need to diverge from these steps for any reason start over from step 1 when you return.
Boot into Fastboot (Power on the phone holding the camera button) This will either show a screen with dancing androids or a "rainbow" splash. Here you will find the hboot/radio version:
radio 1.x: You will need to upgrade this to a 2.x radio before running this process.. please upgrade and re-do this step (Ie. verify you see the updated radio in fastboot before continuing)
radio 2.x: You may press MENU+SEND+END at the same time and proceed (unless hboot-1.33.2005 is installed; indicating you already have dangerSPL)
radio 3.x: You may press MENU+SEND+END at the same time and proceed (unless hboot-1.33.2005 is installed; indicating you already have dangerSPL)
Copy DangerSPL (spl-signed.zip), CM 5.0.x, and gapps-ds-ERE36B (& Ebi1 port if required) to the root of your sdcard.
Reboot/Boot into your custom recovery by holding down the 'home' key before the G1 splash appears.
Make a Nandroid Backup (ext not required) (recommended for upgrading users, not required for freshly-rooted users)
Flash DangerSPL (spl-signed.zip). It will install and then ask you to reboot to finish the installation
Reboot as prompted at the bottom of the screen. This will finish installing DangerSPL and reboot back into recovery so you can flash your ROM.
Once back into recovery Wipe Data/Factory Reset
Flash CM 5.0.x THEN gapps-ds-ERE36B (& Ebi1 port if required); then reboot (Boot may take longer than normal)
Login to Android/Google as per usual
If you want to restore the nandroid backup (to attempt an unrecommended no-wipe upgrade between CM4.2 and CM5)
[Optional] Reboot to recovery, and issue a Nandroid Restore, then follow the regular instructions .
This command will attempt to restore user data.
Restoring will also restore your previous Firmware, so you have to follow the instructions to get 5.0.x again
Note: If this causes undesired consequences (ie bootloops, FC's, etc) then run Fix Permissions/'Fix UID Mismatches'.
***************************************
Instructions for the 'soft-brick' (I think)
How to Un-Brick Your Phone
(Method 1)
Ok so you're trying to put this really cool new custom ROM on your phone and then suddenly, your phone won't start up…well my friends, you have got yourself a bricked phone. The thing you worry about the entire time you're rooting, and flashing your phone, has now become reality. Well, fear no more, for I, CTDroidBeast have found a way to unbrick your device!
It's really easy. It's actually easier then rooting your phone, believe it or not.
Ok, you will need a new SD card, because I bet if you use the one out of your device your computer will not be able to read it. But if it does then HEY, you're in luck. You don't have to spend your money on a new SD card.
So let's get started.
Step 1: Turning Off Your Phone
Because you have a bricked phone, you can't just hold the power button. So if your phone is not already off then you're going to want to take out the battery.
Step 2: Preparing Our SD card
Take out your SD card and put it into an SD card reader or some type of other adapter so that we can view it from our computer. If you cannot view the SD card on your computer then you're going to need a new SD card.
Download DREAIMG-RC29.zip and unzip the file.
Reformat the SD card to FAT32 and copy the DREAIMG.nbh onto it.
Safely eject the SD card.
Put the SD card into your device.
Step 3: Wipe The Phone
Hold home and press the power button.
When you see the image of an ! mark, open your keyboard and press Alt + L if you cannot see any command options.
Do a factory reset by pressing Alt + W or just using the trackball.
When the reset is done, go ahead and hold the camera button and select the reboot system now option with your trackball.
Step 4: Flashing The Phone
Once the grey screen pops up (or the white screen if your phone was rooted with JesusFreke) it will ask you to hit a button to start installing the image…press that button. DO NOT DO ANYTHING TO STOP THIS PROCCESS. It will take about 8-12 minutes.
When the image has completed the installation (it will say completed), go ahead and press the green, red, and menu buttons at the same time. The phone will reboot.
And your done! Your phone is now unbricked!.
Please help!
YOU FAILED.
If you don't take the time to read and learn what you are doing, why should anyone take the time to help you?
WHY would you EVER install RC29? IDIOTIC MOVE!
WHY would you EVER install deathSPL? IDIOTIC MOVE!
I say you deserve what you got.
lbcoder said:
YOU FAILED.
If you don't take the time to read and learn what you are doing, why should anyone take the time to help you?
WHY would you EVER install RC29? IDIOTIC MOVE!
WHY would you EVER install deathSPL? IDIOTIC MOVE!
I say you deserve what you got.
Click to expand...
Click to collapse
I was just following the Wiki instructions ( Full Update Guide - G1/Dream Firmware to CyanogenMod ) here:
My radio before downgrading was 2.x, so I assumed it would still be the same after the RC29 downgrade, but it turns out the downgrade also dongrades the radio to 1.x
therefore death spl bricked the phone
I should have checked the radio version for a 2nd time before flashing death spl
Is there any way to fix this now??
HEARTBREAKER123 said:
I was just following the Wiki instructions ( Full Update Guide - G1/Dream Firmware to CyanogenMod )
Click to expand...
Click to collapse
You did not follow the instructions.
You deliberately skipped step one on the danger spl instructions. Put there so that those who didn't realize the radio had become downgraded didn't do what you just did. You also ignored the warnings on that page that rc29 installs the 1.x radio.
HEARTBREAKER123 said:
Is there any way to fix this now??
Click to expand...
Click to collapse
What part of not having the right radio will brick your device wasn't understood..
by all means hope your recovery is messed up and that you have access to fastboot when you attatch a USB wire.
Otherwise there is jtag. .. bit more complex than flash spl-signed.zip after being 100% sure a 2.x radio is installed however..
Another option is replace it.. some have found replacing the main board + daughter board of a working phone in bad cosmetic shape (screen cracked) a cheap alternative here than a brand new dream. Still requires reading the service manual to properly disassemble what you need without having a bit of a mess.. particularly if you skip a step.
My recommended solution is to find a phone you can deal with stock firmware buy it and sell the rest of your dream as is.. you want root you need to understand the instructions not just follow them.
Alright, well I think he got the point - he should have followed instruction better
I'll keep it as straight forward as possible, no there is not a way you can unbrick your phone without the JTAG tools. T-Mobile's warranty is only one year, afterwards they will not replace your device for any reason.
The soft brick solution you posted will not work, because you have a hard brick.
I believe you only have a couple of solutions.
a) Get a new G1
b) Buy an old G1, preferably one with a broken screen so its cheaper, and place the motherboard of that G1 into your current one
c) Work with some members of XDA and see if you can work out an arrangement to get you the JTAG tools, though this is unlikely to work and difficult to do.
I'm sorry that you have broken your G1, it's a terrible feeling to break your phone in this way where everything is physically still perfect. I believe your best bets are probably solution "a" or "b", you can shop around locally and see if you can find anything
Best of luck.
Thanks for the help.
I think I will try and get another G1 to see if I can replace the motherboards
HEARTBREAKER123 said:
Thanks for the help.
I think I will try and get another G1 to see if I can replace the motherboards
Click to expand...
Click to collapse
You know, if you're going to all the trouble of taking it apart and planning on essentially throwing the mainboard in the trash anyways, what do you really have to lose in attempting to jtag the thing? $2 worth of components and a couple hours of your time? Worst that happens is you fry it, in which case you were planning on trashing it anyway.
lbcoder said:
You know, if you're going to all the trouble of taking it apart and planning on essentially throwing the mainboard in the trash anyways, what do you really have to lose in attempting to jtag the thing? $2 worth of components and a couple hours of your time? Worst that happens is you fry it, in which case you were planning on trashing it anyway.
Click to expand...
Click to collapse
Like the OP said, he lives in Turkey and is unable to purchase these items on eBay.
SolemnWishing said:
Like the OP said, he lives in Turkey and is unable to purchase these items on eBay.
Click to expand...
Click to collapse
Turkey is NOT a back-woods country and there ARE LOTS of sources besides ebay. In fact, ebay is the LAST place you should look for electronic components.
I GUARANTEE that the required components can be purchased in STORES all over the place in Turkey.
lbcoder said:
You know, if you're going to all the trouble of taking it apart and planning on essentially throwing the mainboard in the trash anyways, what do you really have to lose in attempting to jtag the thing? $2 worth of components and a couple hours of your time? Worst that happens is you fry it, in which case you were planning on trashing it anyway.
Click to expand...
Click to collapse
$2? I thought Jtag cost like 70 bucks
racerxgt said:
$2? I thought Jtag cost like 70 bucks
Click to expand...
Click to collapse
Okay, I have good news and bad news
THe good news is that I was able to find someone with a jtag adapter and he fixed the phone for me for $50
Being more careful this time, I went through the wiki steps and installed CM 5.0.8 and gapps-ds-ERE36B-signed
Yaay!
But then I noticed that CM6 was out, and that it had flash, so why wait, right?
I flashed CM6 with no problems, rebooted the phone, logged in, everything seemed OK, except that I didn't have google apps
So I flashed gapps-mdpi-FRF91-signed.zip and... I wasn't able to log on to google!
You know the menu that asks you to sign in to your google account at the beginning
It says "touch the android to begin"... And when I touched the android, it wouldn't ask for my username and password.. Right click would go into 'Wireless Settings', and I was able to successfully define an APN and get a 3G connection, however, even after all that, and when the phone had reception,
touching the android would make the android change color, but it wouldn't let me go to the next step!
So I decided to flash the previous google apps
Now the phone does not boot in normal mode
I can access the bootloader and the fastboot menu (both Camera+Power and Home+Power work fine), but I am not sure how to fix the problem I have
I tried downgrading to Android 1.5 and starting over, but when I go into the bootloader menu, I see 3 androids with skateboards and the following options:
CAMERA_STEP2 : Hboot mode
SEND: Reset device (Doesn't reset, it just reboots when you try)
ACTION: Restart to hboot
MENU: Power down
And when you are in hboot mode, you can't click anything
How can I revert to CM 5.0.8??
Also, is it normal for the new gapps to cause this type of an error?
HEARTBREAKER123 said:
Okay, I have good news and bad news
THe good news is that I was able to find someone with a jtag adapter and he fixed the phone for me for $50
Being more careful this time, I went through the wiki steps and installed CM 5.0.8 and gapps-ds-ERE36B-signed
Yaay!
But then I noticed that CM6 was out, and that it had flash, so why wait, right?
I flashed CM6 with no problems, rebooted the phone, logged in, everything seemed OK, except that I didn't have google apps
So I flashed gapps-mdpi-FRF91-signed.zip and... I wasn't able to log on to google!
You know the menu that asks you to sign in to your google account at the beginning
It says "touch the android to begin"... And when I touched the android, it wouldn't ask for my username and password.. Right click would go into 'Wireless Settings', and I was able to successfully define an APN and get a 3G connection, however, even after all that, and when the phone had reception,
touching the android would make the android change color, but it wouldn't let me go to the next step!
So I decided to flash the previous google apps
Now the phone does not boot in normal mode
I can access the bootloader and the fastboot menu (both Camera+Power and Home+Power work fine), but I am not sure how to fix the problem I have
I tried downgrading to Android 1.5 and starting over, but when I go into the bootloader menu, I see 3 androids with skateboards and the following options:
CAMERA_STEP2 : Hboot mode
SEND: Reset device (Doesn't reset, it just reboots when you try)
ACTION: Restart to hboot
MENU: Power down
And when you are in hboot mode, you can't click anything
How can I revert to CM 5.0.8??
Also, is it normal for the new gapps to cause this type of an error?
Click to expand...
Click to collapse
*FACEPALM*
goldenarmZ said:
*FACEPALM*
Click to expand...
Click to collapse
Don't facepalm just yet
I managed to go back to 5.0.8 after doing everything from scratch
I guess I will use it like that for a while until CM6 / google apps stabilizes
HEARTBREAKER123 said:
Okay, I have good news and bad news
THe good news is that I was able to find someone with a jtag adapter and he fixed the phone for me for $50
Click to expand...
Click to collapse
I bricked my G1 as well, but I'm not in the US
Do you have an idea what the JTAG adapter looked like ?
wow you guys sound mean to the poor guy when he was just making a newbie mistake. i remember when i was making all of those mistakes...hell im still making those mistakes and even thou i have gotten my fone to freeze on the g1 logo or even just go into a constant reboot im glad iv been able to fix the problem everytime and still dont know what im doing im just learning. but hey isnt that procedure that you have up there an unrooting procedure???? and for those getting the wrong gappss try downloading the tiny mdpi on the dream that one worked for me, the mdpi didnt work at all till i tried that one got it from the cyanogenmod site. by the way i gotta say thanks to all the devs, which i had a brain like yals id love to join in on developing but im kinda an idiot here lol
spike210 said:
wow you guys sound mean to the poor guy when he was just making a newbie mistake. i remember when i was making all of those mistakes...hell im still making those mistakes and even thou i have gotten my fone to freeze on the g1 logo or even just go into a constant reboot im glad iv been able to fix the problem everytime and still dont know what im doing im just learning. but hey isnt that procedure that you have up there an unrooting procedure???? and for those getting the wrong gappss try downloading the tiny mdpi on the dream that one worked for me, the mdpi didnt work at all till i tried that one got it from the cyanogenmod site. by the way i gotta say thanks to all the devs, which i had a brain like yals id love to join in on developing but im kinda an idiot here lol
Click to expand...
Click to collapse
bigest mistake evar was probably buyng tha damn mobo ...you see i have 3 HTC's 1 HTC Dream that work's just fine , 2 T Mobile G1 that it's a piece of **** ( it got's nothing in comon with HTC dream it's just a cheap crap copy of the original ) and 3 it's a HTC with Win Mobile wich i think it's by far the most stable mobile operating sistem for now , all of you will say that it does not work like that , but think about this .... how manny win mobo's hawe ever been bricked?! and how manny android mobos are there bricking every day ? your android will brick eventualy ... oh yeah and i am selling 2 HTC dream Black and white
Thumb's upp if you are born in the rong generation )
can anyone advise if there is a stable froyo rom on here in 'zip' format
that does not need any radio/hardspl/ or recovery tweaks beforehand ? (hopefully with GPS, BT, Wifi, Camera etc working)
I genuinely have sweated blood over the last 3 days trying my best.
I have read all the guides, tried using ADB, Fastboot, Terminal Emulators etc
and for various reasons have always managed to crash and burn.
I really was after Lazlo's Froyo, but could not even get the Radio and Hardspl he advised on to the phone !
in desperation. I tried it anyway, and was very close to bricking the phone.
(thankfully though the help on here got me out of being stuck in fastboot)
I failed, even with the guide below ... as it said no room on device !
http://www.webnetta.com/2009/01/02/t-mobile-g1-rc30-to-jfv13/
I plead for a simple zip that I can apply via clockwork as I can manage that method ok.
I have found loads of zip files here:
http://www.filecrop.com/android-2.2-froyo-G1.html
would any of these be of help
anyone ?
thanks in advance
First of all what is your current state on the G1? (IE: SPL, radio, etc...)
And do you really want the froyo ROM to be loaded on your G1 only, or any would do to get your G1 up and running?
thanks for the response ...
the phone is currently running ok on the original 1.6 rom, but I had managed an spl update on it.
fastboot shows:
Dream 110 PVT 32B
HSPL.95.3000 (was hboot 0.95.000)
CPLD -4
Radio 2.22.19.261
Oct 20 (28?) 2008
in settings:
Firmware version 1.6
Baseband version 62.505.20.17U_2.22.19.261
Kernal version
2.6.29-00479-g3c7df37
[email protected] #19
Build number
DRC92
I don't know if all this is original as the Lazlo rom seemed to go on via clockwork,
but then hung, and somehow I got back booting to 1.6
ideally I would like to get Froyo on it
Have you look at [ROM] Froyo 2.2.1 for T-Mobile G1 " Froyo for Trout! " F4T1.8.2 (01/19/2011). You will have to load the SPL and radio that is related to the ROM. And it's Froyo.
sadly that was the one I previously went for.
I did the sdcard ok, but could not get the radio & spl images flashed to phone with either adb or emulator whatever I tried.
usb drivers are on ok, I have the sdk, and despite showing up in windows device manager, and connecting fine when mounted,
adb will not connect to device.
if this Radio and the SPL were available in zip, rather than .img format I could succeed.
I have really browsed all the roms in the Rom Bible link, but cannot find one that does not require these type of fixes.
I was having the same problem with mine the other week. I could not use the img file so I had to mannually search for those zip files.
Afterward this is what I found. See if that helps.
HERE ARE THE DOWNLOADS FOR NEW SPL/RADIO RAM HACK!!!!!
http://cdn.movilzona.es/repos/superatmel/ROMS/superblerv1/15M/hboot0013d-signed.zip
http://cdn.movilzona.es/repos/superatmel/ROMS/superblerv1/15M/radio-2_22_27_08-signed.zip
Click to expand...
Click to collapse
the links unfortunately give me a 404 !
John Denver once sang
'Some days are Diamonds,some days are Stone'
with my luck lately I suspect I was born in a quarry !
@beandroidized
maybe it was a diamond quarry after all !
I got the filenames (radio-2_22_27_08-signed.zip & hboot0013d-signed.zip)
from those dead links, put them into google and got them both via Mediafire !
so thanks a lot there my friend,
I'll have a go at flashing both, and the Laslo rom, tomorrow afternoon and will let you know how I get on.
regards,
Kevin
Good for you. And you are welcome. Good luck.
@beenandroidized ....
everthing did go well and I have now got Froyo !
sorry for late reply as I have been a bit under the weather last few days
carkev said:
@beenandroidized ....
everthing did go well and I have now got Froyo !
sorry for late reply as I have been a bit under the weather last few days
Click to expand...
Click to collapse
No worry, I figured you had a good turnout after the last post. Thanks for the updates. Enjoy!!!!
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!
Hi guys and girls,
First of all here's a little bit background:
I always liked Nokia (GSM's!). My first mobile was Alcatel OT Easy db if i'm not mistaken. After that i had several Nokia's. And then for many years i have used Sharp GX25. While i was using it, GSM world has quite changed. The only GSM i saw like perfect (because of the small size) was Modu mobile at the time. But i couldn't get it anywhere. And the iPhone is like cool. But to bulky for a GSM and to expensive for a thing to call with. When the battery of the GS25 died completely i was thinking how am i going to choose now? ^^ The only thing that i liked was Modu mobile but i couldn't get it anywhere. I don't really cared a lot about some features and so on. Because to get into choosing a phone now, to choose wisely, best for the money, is like spending so much time..
I'm often sending sms to a group of like 20 people. So i bought LG Neon. First cheapest full keyboard gsm i came across. I was thinking you know, Nokia is like the best ever, or has been for me, but i have to give something else a chance. Although i liked the full keyboard it was a really bad experience. But i learned something. So after that i remembered, that i was thinking sometimes, if iPhone was a little bit smaller and cheaper i would buy it. But then i accidentally realized. There are so many ideas you can google. Lets try, cheaper iPhone alternative. So i found Nokia Tube (5800, second hand). I pretty liked it - cheap, compact, a lot of features. I discovered mobile email/gps/sip telephony!/calendar/touchscreen and other nice features of a smartphone. Symbian (Nokia) was still good for me. So now i became kind of accustomed to this nice features. But Tubes touchscreen wasn't really great ether. So i was looking out for some other, more advanced, full keyboard/touchscreen smartphone. Not necessary touch screen, but anyway, it would be nice. So for some time i have been looking on a second hand sites to get a second hand blackberry. Because after researching the question of mobile Emailing i came to a conclusion that Blackberry is the best in it. And even that Blackberry is maybe like the best smartphone of all because of user friendliness, design maybe, and a technological advancement. Like the Mac in a PC world. As i see on the video reviews Blackberry's interface looks more text based would i say. What in my eyes is perfect for a smartphone. I don't see a lot of sense in bells and whistles, or how is it said then in actual information. But!
About not mobile experiences:
It's already for a view years that i am using Linux on my desktop. Since the time when i have got the GX25 i guess. Because i have been quite interested in IT from when i was younger. And now later i already became IT professional and run some Linux servers to. And even my Mac Mini at home runs Linux. I find Mac OS X amusingly technologically advanced, easy to use, user friendly and all that. But i cant install it on my workstation and a laptop at work. So that's the practical reason i choose Fedora over any other OS. No fanaticism here. Because i'm Christian and i believe in Jesus Christ. Because from His words in Bible i learned, or got at least some kind of understanding of what is love actually. So i don't have to be religious about Mac or Linux.
The funny thing actually is, i have used Gnome 3 now for a view month already on Fedora. And a view days ago installed Lion on a Mac. Wow, they already put all the Gnome 3's features in Lion, like first Spaces and now Mission control and Launchpad. ^^
Now, closer to the business - CM6? Dream:
So finally i was thinking, what else can i get, then android. I actually nearly bought Blackberry 8520 pretty cheap. But G1 compared to it has GPS and AutoFocus. And it runs Linux *thumbs up* \o/
Now, when i got the package from Netherlands view days ago. The guy have put CyanogenMod 6 on it for me. But after a day of use i discovered that when you call to me you go straight to voice mail. And i pretty liked CyangenMod's interface although i had an idea, from youtube videos that Hero rom would be nicer(visually). Google apps were not installed ether. So i googled a little bit. And At some places they said that you have to install google apps. But it didn't work. I tried installing it, but always got message about making recovery backup. And then after reboot still no Gapps installed. The phone came with a sd card with cyanogenmod rom on it and two hero roms. Off course before buying it, i already searched for some info. And went to CM wiki. And first questions that arised for me were: how do i determine which radio does the phone has? When i emailed this question to a guy from who i bought the phone he said that someone else has put Hero on it for him. So before he sent it to me he had put CM6 on it. This is i think where the trouble with calling is from. So i played a day with CM6. And using the ROM manager have put Hero on it back. Because seeing video reviews i thought it looked cooler. But now i have an impression, while using Hero rom, like CM6 was better. Like more tweaks and so on. So another question: What are actually benefits of CM6 compared to Hero rom, and vice versa? And the other question is: How do i put CM6 back? Because i don't find ROM manager in the menu anymore. Do i have to install it again? And by the way. I have made a recovery backup when rom manager asked me to do it while trying to install gapps. But doesn't matter a lot i guess. Because people couldn't call me there anyway. And here on Hero it works. I ask myself does the firmware for radio sit in the rom or not? (Ohh, and i actually just realised something, rereading the post here, and checking for errors. Would the radio rom be something like phones bios? And ROM like phones os?)
And also i'm confused a little bit about the process of flashing now. On the wiki i read bout installing DangerSPL and so on. But i have put Hero now just using ROM manager. Has it become easier or how does it work today? Also i ask myself which CM version is like optimal for Dream? To get some nice features but not getting to slow? I guess it would be 6 right?
Okay, hopefully someone can share some knowledge with me about all that rom flashing thing. Or point me to the right direction. Where to start reading.
Thanks in advance,
Sincerely yours,
Nikolai
versions info
Ok, i figured something.
Im reading the "HTC Dream: Installing CyanogenMod 5+" wiki page and heres the info i found so far:
DREAM PVT 32B ENG S-OFF
HBOOT-1.22.2005 (DREA11000)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009,15:30:43
HBOOT
Parsing...[DREAIMG.nbh]
[1] RADIO_V2
[2] BOOTLOADER
[3] RECOVERY
[4] BOOT
[5] SPLASH1
[6] SYSTEM
[7] USERDATA
Do you want to start update?
<ACTION> Yes
<POWER> No
============================
ClockworkMod Recovery v2.5.0.7 (the version)
============================
ROM's on the SDcard:
update-cm-6.1.0-DS-signed.zip
gapps-mdpi-tiny-20101020-signed.zip
---
zx2.1hero.v1.5.1.zip
update.ZX1.5Hero.v2.0.1.zip
dream_magic.2.22.19.26i.zip
Now i expect that offcourse DangerSPL is already installed so i skip this part. Only the version numbers are different. Wiki says 33 and my phone says 22. Then i see there the line tat says: "Select USB_MS toggle" - what does this suppose to mean?
ok
Ok i figured it. Rebooted into the recovery mode. Flashed CM6.1. Ended up in reboot loop. Googled. Wiped. Reflashed. And now it works. Working CM6.1 with working recieving calls.
THanks you guys.
DangerSPL
Hi agane,
The guy from who i bought the phone told me that i have to flash in this order:
-Wipe cache/data
-Install zip: de gewenste ROM
-Install zip: Google apps tiny
-Install zip: DangerSPL
But i havent done DangerSPL. Does it matter?
given that u already are running danger spl,u neednt flash it again, unless u upgrade ur radio and have to flash the corresponding spl....
ok thanks
Ok thanks, that's what i was thinkig.
Froyo by Lazslo
Hi guys,
im back to hacking ^^
well since i work and do alot other things i just bought a Blackberry 9780 and hapily used it all the time since i last posted here. And device is great. I like it alot. There was just a little issue i tought would be nice if it could be fixed. So i asked the retailer i bought it from to send it to BB. The stuttering keyboard is it. Google if u wanna know.
So now. Since i had blackberry i havent used Dream anymore. But back in the time i last posted here the sales guy who sold me the BB had a Dream to. And he advised me to use the Froyo by Lazslo. So now after a view month im back at Dream. I actually pretty havent used it alot.
So now i took my Dream and flashed the froyo by lazslo on it. The slp and radio numbers u can see in my previous post. So not i got the G1 logo at boot and the phone isnt booting. I suppose i did not good just flashing it. Because spl and radio numbers mentioned in the froyo by lazslo thread are not the same as mine. But i thought ok lets try. Wiped and installed the froyo by lazslo rom. And now have G1 logo. Well if i push camera button when booting i get into fast boot.
But can i push some combination to get into recovery to flash for example atleast cgm that atleast worked for me? TO get back to working state? Or what can i do now further to get froyo by lazslo running on it? Does the G1 logo means its bricked or not? Because dont know really? Have googled and found that theres posibility to do something via cmd. Any more info on this?
I google further, but dont have alot of time,
Thanks in advance,
Nikolai
good found something
i see that i had to have the ecsactly spl and radio mentioned in froyobylazslo thread
now gonna search how i install them,
because i got the phone with them already installed
not brickked - fixed
oh, good, got it fixed,
have pushed power and home button not long enough before,
so now after getting into the recovery flashed cgm 6 back on it. and its working
but i still think and will search more the other day to put froyobylazslo on it
just need to find instructions to get to newer spl and radio on it.
would anyone help thanks,
now gtg to Church,
see yaa
un root?
Hi all again,
So,
Is it so that i have to unroot and reflash all from the beginning now to jusmp from
HBOOT-1.22.2005 (DREA11000)
RADIO-2.22.19.26I
to
SPL: 1.33.0013d (hboot)
RADIO: 2.22.27.08 / 28.25
let me know please. ty.
edit,
ahh yes,
or can i still do something to flash froyobylazslo with my radio and spl and tont end up with g1 boot screen?
Nikolai_D said:
Hi all again,
So,
Is it so that i have to unroot and reflash all from the beginning now to jusmp from
HBOOT-1.22.2005 (DREA11000)
RADIO-2.22.19.26I
to
SPL: 1.33.0013d (hboot)
RADIO: 2.22.27.08 / 28.25
let me know please. ty.
edit,
ahh yes,
or can i still do something to flash froyobylazslo with my radio and spl and tont end up with g1 boot screen?
Click to expand...
Click to collapse
There is no need to unroot and start from the beginning. I suggest you to learn how to use fastboot and then read in Terry's 2708 thread how to do the update.
Another hint: After you are on the "new" SPL/radio combo you should check twice whether the ROM you want to install supports this combo, otherwise you will stuck on the G1 screen ...
this
Hi,
the guy here explains some things,
http://www.youtube.com/watch?v=sYg3UmQd5y4
what if i download the radio and spl that i need for froyobylazslo and update them the same way thee guy in the video did. Is it gonna work?
p.s. it looks the link u gave is definitive place aboout that but its difficult to follow
On the first look it probably looks difficult, but if you want to root your phone, install unsupported radio and SPL on it, then it's worth to invest some time to learn a bit more of this topic. Otherwise, if you do something wrong or you follow a guide which doesn't comply to your current "configuration" of the phone , risks are high, that it will get bricked. Just my 0.02 cents.
Sent from my Gingerbread on Dream using XDA App
back
hi all,
im back to mess with it a littlebit,
I installed Anroid SDK, and now i want to start flashig via fastboot as described in the link posted above.
But i dont get how do i start a CMD. Just starting CMD and writing for example fastboot devices in CMD doesnt do anything.
Any suggestions please?
And yes im googling to.
Thanks,
Nikolai
First you need to connect your phone to your PC by USB and get it recognized. You can check that by opening a command line window on your pc and typing
adb devices
if your phone is in "normal" or in recovery mode. You should also check whether you enabled "USB Debugging" in Menu -> Settings -> Development.
You should get a list with your device.
To check fastboot, your phone needs to be in fastboot mode. Switch off and reboot by back-Button pressed. In this case the phone gets into the hboot screen.
Now you can type
fastboot devices
on the command line and if your phone gets recognized, you will see it in the list printed on the screen. If it is not recognized directly and serial0 is printed on the phone's screen, try to press the back button. Then "fastboot" should be written on the screen and you can re-try whether your phone will be recognized.
figured
ok i figured that i had to download the fastboot file mentioned here
http://wiki.cyanogenmod.com/wiki/Fastboot
And the system variable path needed to be configured right.
now i dont have dll error but fastboot devices doesnt show anything,
adb devices does
AndDiSa said:
First you need to connect your phone to your PC by USB and get it recognized. You can check that by opening a command line window on your pc and typing
adb devices
if your phone is in "normal" or in recovery mode. You should also check whether you enabled "USB Debugging" in Menu -> Settings -> Development.
You should get a list with your device.
To check fastboot, your phone needs to be in fastboot mode. Switch off and reboot by back-Button pressed. In this case the phone gets into the hboot screen.
Now you can type
fastboot devices
on the command line and if your phone gets recognized, you will see it in the list printed on the screen. If it is not recognized directly and serial0 is printed on the phone's screen, try to press the back button. Then "fastboot" should be written on the screen and you can re-try whether your phone will be recognized.
Click to expand...
Click to collapse
thanks
trying further
duplicate post
spoofspl?
Do i have also to do this?
> A Rom (note: many cm6 based roms block install because of the '1.33.0013d' bootloader Please use firerat's SpoofSPL)
http://forum.xda-developers.com/showpost.php?p=9068311&postcount=84
Depends, what you want to do. Normally this spoofing is needed only when you want to install a ROM which officially isn't supported, but you know that it is runnig with your SPL. Especially when using cMTD you change the partition layout and some ROMs check with the SPL whether the ROM fits into the system partition or not.
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.