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 )
So I purchased an HTC Dream from a friend and learned all about the wonders of rooting, and found what i thought was going to be a simple step by step guide to upgrade my phone to android 2.1, and was encouraged to use it after reading all the positive comments. I can't post the link to it as I'm a new user, but you can find it by entering "guide on how to root your htc dream to 2.1" into google, the article is on adroidheadlines.com...
I followed it step by step until I got to step 20. After entering:
adb reboot bootloader
i got "error: closed." Being stupid, I looked around on the internet and came across a page that said putting a file called "DREAIMG.nbh" onto the root of my sd card would fix all my problems. Unfortunately for me I did, and then used fastboot which i (think) flashed that rom (i think that's the right lingo, anyway) To my surprise, I turned on my phone to see "T-Mobile G1" on my screen as opposed to the regular "ROGERS" logo. My phone won't move past that screen and won't even boot into recovery or fastboot. I have this gut feeling i've bricked the damn thing and am looking for someone to tell me it isn't so. To clarify, I'm wondering if there is anyone to factory reset the phone or restore it to its original rom somehow while its in this state.
Any help at all would be appreciated, and i can't seem to find anyone else on the internet stupid enough to have made the same mistake, which is never, ever a good sign.
i think you grab the wrong Dreaimg, there is 2 different ones if im not mistaken.. have you tried turning off phone hold camera then power?
If you can get in there then you can use this guide
http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Rogers_Dream_EBI1
These are the instructions you should have followed for Rogers..
The op was actively rooting the dream (just using a clone of the instructions with a typo) 'adb reboot bootloader' instead of 'adb shell reboot bootloader'
The wiki page has this correct, the comment on the article the op read indicates the correct one and comments in the thread on XDA indicate if you are stuck all we where trying to do was enter fastboot..
Unable to find any of what I just mentioned op left the guides for rogers dreams and switched to T-Mobile Howtos and got a t-mobile nbh, having already installed danger SPL it could be flashed.
80% of the time this would have left the user with RC29, however 20% of the time system fails to flash correctly, and you need to flash it again. This is made harder since now you have the rainbow SPL (no fastboot and security locked) 1.x radio, and a Rogers CID. Thus need a gold card.
There are many nbh files however; one with the rogers CID can be flashed without a gold card.
http://www.rogers.com/dream-zip
has the current 911 patched nbh file (unzip it).. that will let you start again, but do note nothing went wrong the first time so don't enter and endless loop please.
(Note I recommend you apply it twice to ensure all partitions are flashed correctly, rogers has the partitions layout of dangerSPL, not t-mobile stock SPLs)
Okay, I understand what I did wrong, and I understand how I WOULD flash the file you provided using fastboot, except that my computer no longer recognises my phone when I connect it, and as a result I can't access the phone using adb... Not sure what to do next. Would placing that file on the sd card using an sd reader change anything? Or is that what you meant for me to do?
EDIT: Nevermind, I figured out what I was supposed to do with that file, though the problem remains that my computer no longer recognizes my phone when I connect it via USB. Is this hopeless?
EDIT (again) I tried holding camera while powering up, before it didn't do anything but now the phone has booted to a screen with 4 horizontal coloured bars. the screen reads
"DREA210 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO- 1.22.12.29
Sep2 2008
Serial0"
Not sure if that means anything but I figure it could. Please advise.
weezerx said:
I looked around on the internet and came across a page that said putting a file called "DREAIMG.nbh" onto the root of my sd card would fix all my problems.
Click to expand...
Click to collapse
That is also how you can flash the rogers 911 nbh from the 0.95.* spl that has no fastboot..
It may fail but it will likely then have 1.33.0010 and the 3.x radio that if you flash it a 2nd time will work.
Once done remove the file from the sdcard
ezterry said:
That is also how you can flash the rogers 911 nbh from the 0.95.* spl that has no fastboot..
It may fail but it will likely then have 1.33.0010 and the 3.x radio that if you flash it a 2nd time will work.
Once done remove the file from the sdcard
Click to expand...
Click to collapse
I really appreciate the help but I'm very new at this and I'm not entirely sure of what it is you're asking me to do
So does that mean all i need to do is remove the G1 image from the sd card and put the rogers one on via an sd reader and I'll be okay?
weezerx said:
So does that mean all i need to do is remove the G1 image from the sd card and put the rogers one on via an sd reader and I'll be okay?
Click to expand...
Click to collapse
And power on while holding camera it ought to ask you if you want to flash it..
Well I followed all of the instructions and removed the bad image from the sd card and put on the one you provided, turned on the phone, attempted to flash it, and got to a screen that says "Update terminate UPDATE FAIL" ... ideas?
Remove sdcard, boot holding camera, tell me all the text at the top of the screen
"DREA210 PVT 32B RUUNBH
HBOOT - 0.95.0000
CPLD - 4
RADIO - 1.22.12.29
Sep2 2008
Serial0"
Interestingly enough, when I boot to that screen now (despite having no sd card in the phone anymore) it still switches to the screen it tried to update with before (light blue background, darker blue text) for a split second before switching back... it never did that before, I'm not sure if that means anything.
Again, I really appreciate all the help though I'm starting to consider sending it to someone for JTAG if we can't find a solution
Hem I think rc29 on a gold card will make your phone into a T-Mobile dream that can be rooted with the telnet method.. remember you will have a 1.x radio so you will not want to directly install danger spl.
The big trick IS unless you have another HTC phone making the goldcard
I'm nt sure what you mean by all of that I tried backing up the fles on the sd card and only putting that nbh file on the card and that didnt work. I tried putting it on with all of the other files that were on it before in place of the other nbh that screwed up the phone in the first place... unsure what to do next. Was i supposed to put the "HTC update" file on the sd card without unzipping it? :S I'm so lost. ezterry, you're from toronto and do jtag service right? cause I'm not too far away...
Okay so scrap everything I said before. I decided to investigate the whole goldcard thing and to me it sounds like it's my best bet. I have a buddy who's willing to let me use his HTC Magic to complete the process. I found a guide online here
http://www.droid-den.com/android-guides/android-guide-how-to-create-a-gold-card
It sounds easy enough to follow, but I have a few questions. First, does the app "GoldCard Helper" still exist, because i know google has taken apps off the market before. Secondly, would you recommend this method/ have any advice or maybe a different way of doing things? and thirdly, just using my friends phone to get the CID for the sd card doesn't pose any threat to it at all, right?
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?
Hello,
I was running CyanogenMod 6.x for a while, but my Android Dev Phone 1 just wasn't keeping up (and stuff was randomly breaking such as all camera-related apps force-closing), so I wanted to go back to JesusFreke's 1.5 ROM, which is what I had been using before I started using CyanogenMod back in the day. Stupidly, I just restored a Nandroid backup, and now things are really pretty broken (sometimes even calling doesn't work properly, market doesn't download anything, etc.).
I'm thinking what I did wrong is that I didn't change back from DangerSPL to... whatever I had before that, when I restored the old Nandroid backup of JF1.5. So can someone tell me how to do this? There is a guide on the CyanogenMod Wiki but that seems to apply only to T-Mobile G1 phones, whereas mine is an ADP1.
Where can I get the correct SPL I should use for the ADP1 when I want to install JF1.5? (Or is there even a "correct" one?) Do I need to downgrade/upgrade my radio?
Incidentally, my fastboot screen looks like this:
Code:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.23.02
Apr 20 2009,15:30:43
Any advice or help would be greatly appreciated. Thanks!
i also have the adp1 but it doesnt matter because the only difference was the spl. as we have the same as others right now, our phone only differs with the backcover
i wouldnt go back to 1.5. just make a real clean wipe follow the instructions exactly and you are good to go.
if you are really sure that you want to go back, search for the downgrade (original rooting method) to rc7(UK)/rc30(us) i think and then head over to htc's website
there you find everything concerning adp updates and then tell you exactly how to proceed (although it's written in a weird way)
sorry but i'm too lazy to search the links atm...
EDIT:
Downgrade:
RC7 Firmware
1. Download and unzip the RC29 or RC7 image file. Copy the DREAIMG.nbh file to the SD card. (RC29 for US, RC7 is for UK)
2. Turn the device power off.
3. Hold Camera button, and press Power button to entry boot loader mode. You should see a gray/white screen with instructions to flash your phone with the update on your SD card. If you don't see that, make sure you followed the instructions properly.
As per the on-screen instructions, press the Power button to start upgrade procedure. DO NOT DO ANYTHING TO INTERRUPT THIS PROCESS. (when you interrupt or battery empty or sth similiar you will most likely end with a brick)
then you should be at android 1.0 or 1.1 not sure.
after that you head over to ADP1 Stuff like radio and system images
follow the instructions and everything should work out
Thanks. The reason I'm downgrading is because CM breaks my camera for some reason, and CM 6.x even caused my phone to fail to make calls about 75% of the time, which was not something I could accept for daily usage. My phone has actually had its screen smashed in in the past (I got it used) so I wouldn't be surprised if there's still some hardware damage somewhere, even though it was repaired by HTC (perhaps their testing isn't that thorough). 1.5 seems not to take my phone into territory where it starts getting ****ed up, so I think I'll stay away from CM until I get a new phone, maybe in another 6 months to a year
Anyway, I figured out what to do. I used fastboot to flash Engineering SPL, then flashed in the latest AmonRa recovery image and JF1.51 without any problem. The radio version was not an issue. Some guys in #cyanogenmod on freenode coaxed me into just doing it and not worrying about bricking... basically fastboot is magic and I don't see why you would ever use the recovery image to dao anything when you could do it with fastboot
lolmensch said:
1. Download and unzip the RC29 or RC7 image file. Copy the DREAIMG.nbh file to the SD card. (RC29 for US, RC7 is for UK)
2. Turn the device power off.
3. Hold Camera button, and press Power button to entry boot loader mode. You should see a gray/white screen with instructions to flash your phone with the update on your SD card. If you don't see that, make sure you followed the instructions properly.
As per the on-screen instructions, press the Power button to start upgrade procedure. DO NOT DO ANYTHING TO INTERRUPT THIS PROCESS. (when you interrupt or battery empty or sth similiar you will most likely end with a brick)
then you should be at android 1.0 or 1.1 not sure.
after that you head over to ADP1 Stuff like radio and system imagesfollow the instructions and everything should work out
Click to expand...
Click to collapse
(doubleposting because you edited your post)
Doesn't the NBH overwrite your SPL as well? If so, your method would remove my ability to use fastboot to install the images from the HTC site (or do anything else with fastboot until I had reinstalled a fastbootable SPL), right?
After looking through the varying questions concerning the same topic and, subsequently, not seeing the right answers - within the right timeframe (e.g. within the past month or so), I decided that a new thread was needed. So here's it is:
A branded G1 (mine, T-mobile, Germany) is what I want to downgrade so that it may be rooted and upgraded with a custom ROM. The problem, I am finding, is not that the instructions aren't correct. Rather, it's that a piece of the instruction set doesn't exist. Namely, the revskills.de website. I mention this because I have tried, repeatedly, to boot with the DREAIMG.nbh in order to downgrade and have consisitently (after numerous downloads from different sites) received the same error - 00028002 (or something like that) while trying to load it. I eventually learned that some phones needed a "goldcard" so I set about trying to do that. Got the CID, reversed it, etc. but the part about going to psas.revskills.de is the killer. The site is down and apparently, no other method of changing the carrier ID exists (or, if it does, the method is too ugly to mention, let alone comprehensible by someone like me, a not-so-good-programmer). Worse yet, all the instructions involving the generation of a goldcard also involve this website and consequently, because of the aforementioned down-status of the site, renders all instructions moot (Grade: D for relying on unreliable sources). So, back to the question: does a method exist outside of what I have mentioned? Where can I find it? Does it have a cost attached to it?
If you've read this far it means that full words and sentences don't confuse you (in light of so-called "l337sp33k") and I applaud you. I will applaud you even more when a well thought out and not-so-glib answer unriddled with blog cliches and platitudes can be found as a reply to this post...
Seriously, if you don't know an answer, a link to check out or someone I can refer to, don't waste your time (or mine) with a the standard "you need to read this and that rules before asking a question" reply. I have trolled through this forum and a few others for the past 2 days looking for the answers to the question of downgrading and finding not the right answers that are specific to this problem (yes, I've read thropugh cyanogenmod wiki, read through the wiki here for dream/g1 phones, gsm programmer's sites, android dedicated sites, etc...ALL of them point to revskills for the goldcard gen (except for one which allows dowloading a perl prog to compile yourself to make the goldcard - I'm not so good with perl yet)
If you need to check the website go here:
psas.revskills.de/?q=goldcard
it's not working for me, whether through proxies in the US, netherlands, britain, frnace, or germany. My only conclusion is that it has been shut down.
Thanks for you attention and I really appreciate some advice from one of you that may be able to shed more light on this.
Incidentally:
SD Card: Hama 2GB Micro SD(formatted fat32)
Droid/HTC G1 phone has been factory reset to:
Firmware: 1.6
Kernel: 2.6.29-00479-g3c7df37 [email protected] #19
Baseband ver.: 62.50S.20.17U_2.22.19.26I
Build No.: DRC 92
are you going on that non exiatent site to download the qmat thing? maybe try looking for it as a torrent file... use bittorrent or something and see if it's out there... i wish i knew how to help more, but i never needed to do anything like that...
stupid question but did you try both dreaimg files? rc29 and rc7?
both img files
Yes, I tried both. The US version gave me the same response as the European one. Tried qmat 5.0.2 and got nowhere with it (i ran out of time before I could figure out everything it could do - apart from simply reversing the cid). The only way to create a gold card seems to be through revskills...kind of a raw deal for the rest of us, if you ask me.
yeahh haha this sucks im not sure what you can do... hopefully someone sees this who can help you. sorry
I am currently trying out the alternate root method from your guide. Something's working...the build version is now CRB43 and I have cupcake (1.5) installed - I think. I shoudl be able to go through the guide in order now, right?
yeah if you have 1.5 than all you need is a custom recovery installed and you have root access... i prefer amonra recovery.. than you can flash radio and spl and go even further by flashing the newer 2825 radio and 0013d hboot
I just have to update my phone account with a data plan (forgot I didnt have one and cant sign in to google without it). Fortunately, it's cheap and takes only a day to update.
OK, so i worked the alt recovery method, but I can't sign in to google. (I used the AMON_RA recovery img.) I can't do anything now. The phone is (for all intents and purposes, bricked. I then tried to do the work around to get the wireless turned on at the touch me screen. It doesn't work. Still no root access. trying to go back to stock rom, no go. Still get the "Not Allow" 00028002 error. Haven't seen the fast boot screen lately. I try the back arrow from the boot loader screen...nothing. Even went so far as to try the HTC site boot unlocker method. HTC Sync installed, android sdk installed, etc. got the drivers in win7 x64 to acknowledge the phone being plugged in...it even recognozed (once) as the HTC Dream/G1, after that never again. This is nuts! It's funny as well as highly annoying. I'm running out of ideas and could use some suggestions...
Thanks
incidentally, the link to "DREAIMG.nbh" in the unrooting section connects to a download of the update.zip file. So, the link is misplaced or something...
good news, the gold card gen sit is back up, however, I can't connect to the phone with adb...I have tried the workaround but I guess the image on this thing is still not rooted. I'm out of ideas what to do, I cannot sign in to google (registration work around) and I can't connect with adb to all the other work to change things. This phone is hosed (and I will absolutely not go to T-mobile (in germany) they're even worse here than in the US...
Here is the link that I found for dreaming.nbh file.
http://www.megaupload.com/?d=NAAS5VBS
See if that works.
So, I am resigning myself to never getting this fixed. I have a rom I cannot access because the data plan on my sim card is for Maxxim, while the rom sets everything up as T-Mobile. Maxxim support will not give out the APN info and, to top it off, the wireless work around does not work because the cupcake dreaimg.nbh and amon_ra recovery image still do not allow root access. I'm lost, got a "working brick" phone, and I'll be damned if I go crawling back to t-mobile whether here in Europe or the US! Thanks for the help anyway...
yeah sorry bout that will fix the link, but its the same one you use to 'downgrade' on the Root method.. just brings you to 1.0, then flash the update.zip to 1.5 or 1.6...
so you cant flash the DREAIMG.nbh file? and you cant do anything via recovery?
but your device works if you had a data plan.. lol wow all i can think of is trying to flash the orange.nbh or get the DREAIMG.nbh to work..
Yeah, tried the orange.nbh as well and I get the same error for every nbh I try:
"00028002 Not Allow". It's really weird that all the nbh do not work...it's almost deliberate. The only root that worked was the alternate root, but wouldn't that have let me flash other roms? Interesting that it didn't.
Good that this G1 is a spare, but I would still like to get it working. I've found a use for it at work but it needs to be rooted. Will post back shortly with results from the DREAIMG.nbh and orange.nbh (if need be).
Incidentally:
Bootloader screen:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
SEP 2 2008
Does this give you any ideas? I can get to the recovery console but it does not necessarily mean I have root (as far as I've seen to this point). I mean, if I were able to register the phone without a data plan (using the wireless connection) I think I would be ok. I did have a point when I was able to connect to the phone via adb (but the phone was registered).
I know I don't have root because I am unable to do the <enter>reboot<enter> thing in the reg bypass method. How did that happen? -I've got no idea...
Another thought, Is there another way to install drivers on my windows machine so that the phone is recognised by adb (even though it's not regitered and I have no way of turning on debugging)? Is there a way to alter the build manifest so that USB debugging is on by default thereby allowing me to connect via windows?
Its painful to read threads like this..
Do you still have your sdcards CID from the OP?
If so using the sdcard you have the CID to make the goldcard on your computer, tben takethe orange nbh rename it to DREAIMG.nbh and place it onthe root of the sdcard.
Then flash the orage nbh and use fastboot to install the 2708+ radio/spl/custom recovery (ra or clockwork)
If you dont have the CID find a device (likely a friends phone) that can read the CID and pick up from there. (notice no adb, and only fastboot after flashing an nbh with an engenering spl)
(I didn'tsay it earlier as the goldcard site was down...)
How to I go about reading the CID on another phone? I am not too familiar with the process. I have a nokia X2. Will that work through a bluetooth connection? (it's my wife's phone and I don't want to try anything with that one until I am absolutely sure.
If you could point me at something I could read on how to do this, I would be exteremely grateful...
Thanks
the site http://psas.revskills.de/?q=goldcard is odwn for me, so I can´t create my gold card.
Any other way to access the site?
I'm following the CM guide for my inspore 4g, but when I searched this forum, this thread came up
So here's my final result:
* Followed steps in the guide for alt root method (nothing else worked but that) - gained root.
* Restarted in order to follow thorugh with the radio upgrade
* No root
* Reflash the ROM
* still no root
* Cannot connect adb to device
* Windows sees it only as USB (even after uninstalling and pointing the hardware to the Android SDK USB Drivers
So I've come into an infinite loop:
* Can't gain root without a goldcard (or some ability to take the NBH apart and modify the kernel - DEFINITELY not my strongest skill...
* Can't get a goldcard without being able to read the CID
* Can't read the CID without connecting with adb
* Can't connect with adb without USB Debugging on
* Can't turn on usb debugging without a) registering phone (no data plan) or b) having root access to type in the commands at reg screen (with SIM Card in) or initial screen (without SIM card)
I've tried every ROM I could find, used the Android Kitchen tool (to modify the ROMs I've found, adding root access), I've read every guide I could get my hands on, as well as trying to extract the nb files from the NBH (in hopes of spotting what I needed to change in order to enable the phone to come on with wireless ON). I have been unsucessful. Is the phone now a paperweight?
I appreciate and respect any suggestions (I've already thought of buying a new phone - so that suggestion is out ;-) ).
Thanks