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 )
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?
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!
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' !!!