Database Develop

coolest bootloop ever

So i had a blast last night at the party till i spilled beer on my phone......pulled out the batt and all that, few hours later after it dried out i powered it back up no problems but home home and green button aint working along with w e r 6 7 0 buttons so this morning i decided to do a system rest to see what it would do. So it did it took me into recovery only 1 problem i cant do anything since my home button isn't working....so i restarted and now i get a bootloop on the hero screen....
So i was wondering what to do now? i got insurance on the phone and i didn't spill that much beer on so i didn't flood the back where the white sticker is that changes color so will i able to exchange it as hardware defect so i dont have to pay deductible?

you should be able to get into recovery by running
adb shell reboot recovery
while the device is plugged in on USB, and you're in the SDK folder...

how do i brick it so it doesnt go past G1 screen i dont want them see Hero boot screen =/

Install RA-recovery 1.2.1 it uses call instead of home. To brick it flash an old radio over 1.33.2005 spl and you are good to go.
If you plan to blame a HW defect flash it back to stock, otherwise brick it & blame an OTA update.

gurnted said:
Install RA-recovery 1.2.1 it uses call instead of home. To brick it flash an old radio over 1.33.2005 spl and you are good to go.
If you plan to blame a HW defect flash it back to stock, otherwise brick it & blame an OTA update.
Click to expand...
Click to collapse
sweet but can u give me step by step direction cuz i cant get past hero screen cuz that's where its loops and i cant get into recovery, cuz that's where its loops...do i need to do adb or w/e its called? cuz i have no clue how to do it....

One thing you could do, is grab the RC29 US or RC7 UK update and place that on your SD cards root as DREAIMG.nbh. Boot in to the SPL (home+camera) and flash it. That update contains the 1.1 radio, the one which isn't compatible with 1.33.2005 SPL. As soon as it flashes the radio it should brick it.
Download the NBH
Place it on the root of you SD card as DREAIMG.nbh
boot in the the SPL (Power+Camera)
Flash it!

Hard Bricked my G1. Any way to unbrick it?

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 )

Trying to Root HTC DREAM: nightmare

Hello all. This isn't your usual noob rooting thread. I'm having some serious problems trying to root my phone, I need some professional help here. I literally have scoured every tutorial trying to figure this out, my phone has been down for two weeks. PLEASE help me out, I looked everywhere trying to fix this thing.
Here is my problem: Downgraded from 1.5 to RC29, but when I try and update from RC29 A) Rainbow/Serial0 B) When I try to go into the OS it hangs at the T-Mobile G-1 Screen (I have a Rogers Dream).
Here is where my phone is at now:
DREAM210 PVT 32B
HBOOT 0.95.0000
CPLD-4
RADIO-2.22.23.02
Sept 2 2008
I can access the recovery options, but I can't update. When I tried to access sqlite_stmt_journals it told me it couldn't cd there even though when I ls'ed it told me the directory existed.
Even when I thought I used update.zip and flashed to the newest version it still had the old T-Mobile on there. Please help, I'm desperate guys! Anything!
You guys are great, thanks in advance. I'll check this thread constantly. Regards.

I'm not sure how you are where you are.. (you must have been rooted at some point to install RC29; rogers phones won't install it without doing so.. however for many it boots into android more successfully)
It also sounds like you have a custom recovery as stock dream recoveries don't have ADB or console applications. In addition having 2.22.23.02 indicates you changed the radio after flashing RC29 (that may be the issue with boot.. but as Android 1.0 isn't that interesting we can leave the radio in question)
So here is some questions
1) is it stock recovery (has a /!\ image and you must use ALT+L to see the options) or a custom recovery; if a custom recovery can you give more info like is it RA or clockwork recovery
2) Where are you seeing sqlite_stmt_journals in adb with recovery booted or while stuck on the G1 screen? If the G1 screen maybe a 'adb logcat > out.log' will help attach said out.log to your post.
With this info I can try to help you find a way out of this mess.

Thanks - I appreciate the reply. It's been a strange path for sure. But I managed to escape the one I was in and into another one.
I managed to put AMON RA's 1.7.0 recovery on my phone, and upgrade to Android 1.6 (Cyanogen 4.2.15.1). My radio at that point was 2.22.19.26i (obvious mistake). But regardless it worked for whatever reason. Regardless.
I pumped straight through that (as in the instructions after flashing DangerSPL) to putting Cyanogen 6.0.0DS on, then the EB11 kernal (even though I wasn't sure if I needed it, but it said it you had a Rogers phone you should) and the tiny GAPPS. It said welcome to Cyanogen 6.0.0 in the recovery screen, but when I rebooted it still went to the T-Mobile G1 screen.
So i sasw my error with the radio, and went to switch it from the one I had to the correct one: 3.22.26.17 (as per the site). So I thought I should reflash the Danger SPL just to make sure I was clean to reapply the Cyanogen update after.
However, when I applied the 3.22.26.17.zip, and rebooted and held camera it just held at the t-mobile G1 screen. I waited for 10 minutes then had to pull the battery.
Now I can't boot into the phone, into recovery, or fastboot. What. a. mess.
Thanks in advance for the help, this really is a nightmare for me.

nudasveritas said:
Thanks - I appreciate the reply. It's been a strange path for sure. But I managed to escape the one I was in and into another one.
I managed to put AMON RA's 1.7.0 recovery on my phone, and upgrade to Android 1.6 (Cyanogen 4.2.15.1). My radio at that point was 2.22.19.26i (obvious mistake).
Click to expand...
Click to collapse
NOT a mistake at all! There is NOTHING wrong with a 2.x radio!!!!
But regardless it worked for whatever reason. Regardless.
Click to expand...
Click to collapse
Probably worked because it was a perfectly valid thing to do!
I pumped straight through that (as in the instructions after flashing DangerSPL) to putting Cyanogen 6.0.0DS on, then the EB11 kernal (even though I wasn't sure if I needed it, but it said it you had a Rogers phone you should) and the tiny GAPPS.
Click to expand...
Click to collapse
Your mistake was the EBI1 kernel -- you had an EBI0 radio, that means that you needed to use the (default) EBI0 kernel.
It said welcome to Cyanogen 6.0.0 in the recovery screen, but when I rebooted it still went to the T-Mobile G1 screen.
Click to expand...
Click to collapse
This is because CM doesn't change that image. It came with the NBH file you installed. Nothing to worry about. The reason it didn't boot is because you had the wrong kernel installed.
So i sasw my error with the radio, and went to switch it from the one I had to the correct one: 3.22.26.17 (as per the site). So I thought I should reflash the Danger SPL just to make sure I was clean to reapply the Cyanogen update after.
Click to expand...
Click to collapse
I'm trying hard to understand what you did... at this point, you had... 1.33.2005 SPL and 3.22.26.17 radio?
This is a valid pair, BUT, you had an EBI0 recovery installed and just switched to an EBI1 radio... and have the thing set to boot-recovery. This is an awkward spot to be in..... basically, since you had a 1.33.2xxx SPL installed, you should NOT have tried flashing radio through recovery -- you had a perfectly good FASTBOOT, and should have used THAT.
However, when I applied the 3.22.26.17.zip, and rebooted and held camera it just held at the t-mobile G1 screen. I waited for 10 minutes then had to pull the battery.
Now I can't boot into the phone, into recovery, or fastboot. What. a. mess.
Thanks in advance for the help, this really is a nightmare for me.
Click to expand...
Click to collapse
This is an interesting spot you're in, I'm not sure how to resolve it. You appear to have an SPL and RADIO that are compatible, but are, nevertheless, bricked in a boot-recovery mode.
Following the update-radio cycle, the command field of the misc partition gets set to boot-recovery, with the parameter set to format the cache partition. Well, you have an EBI1 radio and an EBI0 recovery kernel, so recovery won't boot to finish its cleanup.

The reason I went from the 2.x radio to the 3.x radio is because on the walkthrough it said that the 2.x radio was for non-US whereas the 3.x radio was for Rogers dream customers. But something that might help:
If I plug in my phone via USB, it won't acknowledge it as either a Fastboot or Recovery/ADB device, but the computer does acknowedge it as an "Unknown USB device," while under Android Devices there is the Android Composite ADB Device... which says it cannot start because of Code 10. Windows 7 Pro, 64-Bit is my OS.
Would repartitioning or formatting the SD card do anything? Also, start+menu+end won't do anything either.
Thanks again folks for the help, I am in a situation here.

I'm stuck in 1.0 with some keys not responding like "s" and am stuck. Any chance this could be what I did?

[Q] How to downgrade from DangerSPL on ADP1?

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?

HELP!! May have Seriously Messed up phone...

(Rogers HTC Dream)
Ok, so, i know this sounds ridiculous, and you may find yourself asking "WTF Was He Thinking?!?!?" But, was a late night, and i was quite possibly half asleep lol...
Ok, so, long story short, i have tried possibly every rom for the Rogers Dream, and majority of them didn't work for me, or atleast, if they did, not that well.... Cyanogenmod 6 worked ok, although it started to get slow pretty fast :/ Anyways, i had previously rooted and flashed my dream with the steps provided on cyanogen's wiki, but i had never updated the kernel or anything, so, i came to the conclusion that it was possibly my kernel that was un-allowing me to run most roms, so i decided to update my kernel using the steps here
"http://forum.xda-developers.com/showthread.php?t=831139"
Everything went well, kernel updated, wiped everything, except i accidently deleted my recovery.....but thought, no problem, i'll just follow the instructions on the thread, no biggie.....it said to download the "orange-1.58.73.2.nbh" and flash that......BUT... I Should have known that the Orange one was the one for T-Mobile!! But out of stupidity i didn't realize it and flashed it!! Now my phone won't boot up or Anything :/ when i try to boot into recovery OR Hboot, it shows the t-mobile startup flash, then shows an error with a triangle and a yellow exclamation in the middle, with a phone on it's side beside it!! :S
Did i completely mess up my phone?.... Someone please help!! x.x

I got a Rogers dream and I just push amonRA with adb. As for the exclamation screen, I think there is a key combo to bypass it. Something like volume up and power at the same time. I can't remember now the exact combination. Took a lot of Googling to find it, and if I remember correctly the dream has a different combo than the tmo did. But with this nexus one my memory has faded.
Sent from my Nexus One using Tapatalk

The orange nbh is orange not t-mob..
But has a eng spl so recovery is easy.. head over to my 2708+ radio thread and flash that, a 2708+ rom (most new roms support it and older ones the kernel in that thread will fix it.
Rogers if they are your carrier may cut wireless data there is a e911 wavier form to get around this search for it or ask the support person if they cut your data for detasils.
The good thing about using the 2708+ radio/kernel is extra ram, and it works on the rogers dream the same way as the non rogers dream thus you can ask more people to help support you with 2708+

Thanks for the reply guys,
ezterry:
thanks for replying, would had posted in your thread but didn't want to jam it full of even more posts of someone needing help lol...
as for your reply, it was after i had flashed the orange nbh that i was getting the t-mobile splash :S thus i assumed it was t-mobile.... but, as for flashing anything, i can't....when i try to boot phone in hboot or recovery, i get the error i previously mentioned, and when i normal boot, i can only get to the screen that says to plz insert sim card, and it won't let me pass that screen :S....that's where im stuck.....i tried using the usb cord to access adb through it, but on the comp it says there are no adb devices, i'm assuming it's because i can't get past the "no sim card" screen to enable debugging ..... Any suggestions?
Thanks!!

I'm going to hope you are doing something silly since your description indicates no problem with the phone.
SpawnOfSatan said:
but, as for flashing anything, i can't....when i try to boot phone in hboot or recovery, i get the error i previously mentioned
Click to expand...
Click to collapse
That /!\ screen *is* recovery, alt+L will show you additional options.. but in its self its not that useful.
SpawnOfSatan said:
, and when i normal boot, i can only get to the screen that says to plz insert sim card, and it won't let me pass that screen :S....that's where im stuck..
Click to expand...
Click to collapse
I don't recall if adb is enabled by default on the orange rom; regardless this is the rom. (putting a sim card active or not in the phone may let you get further however ought not be necessary )
So either you got so anoyed at your phone you did phisical damage to it or you are attempting to enter HBOOT/Fastboot incorrectly.
Powering on when holding 'camera' is supposed to always bring you to the HBOOT screen; then pressing send or back as prompted will let you to the Fastboot screen (don't re-flash the orange NBH, say no if it asks)
Alternatively either booting with send or back will go directly to HBOOT.. (The rogers [2000 series] dream uses Send while the t-mobile (100 series) users Back but some SPL only provide the back options regardless of dream model.. I don't recall about 1.42.2000 so you will want to try both)
In theory Home is the only button to send you to recovery.
Once in fastboot it ought to be a full featured fastboot and the normal 2708+ install instructions will work using fastboot on your PC

That /!\ screen *is* recovery, alt+L will show you additional options.. but in its self its not that useful.
Click to expand...
Click to collapse
Ahh ok lol, i'd installed RA recovery when i first got the phone, so it was the only recovery screen i remembered ever seeing, thus why i was confused, but yah, hit alt+L and saw the options, but yah, not that many :/
So either you got so anoyed at your phone you did phisical damage to it or you are attempting to enter HBOOT/Fastboot incorrectly.
Click to expand...
Click to collapse
Apparently was entering it wrong, i was used to using Home+Cam+End to enter hboot.....so that's my fault....
Once in fastboot it ought to be a full featured fastboot and the normal 2708+ install instructions will work using fastboot on your PC
Click to expand...
Click to collapse
[/QUOTE]
When i enter hboot, it looks like a friggin rainbow now lol....red, green, blue, and white bars as the background :/ and once in hboot, it says "Serial0" in the middle of the screen :S and when i plug it into the computer, i tried hitting both back, and send, and it makes the "Serial0" dissapear, but seems no matter what i do, it won't show the phone as a connected device in fastboot :S
Thanks again for replying soo quickly and all the help u've been giving me, any advice on where to go from here or getting it to enter fastboot?

What you are describing is not 1.42.2000.. but 0.95.0000.. or that its likely the Dreaimg you flashed was the t-mobile rc29 and not the orange nbh..
Rc29 can be flaky.. but there are two options
1) go to recovery, alt+l and wipe, put a sim card into the phone and root via telnet.. assuming you have the 1.x radio of rc29 follow the link to my 1.33.2003 spl then with that install 2708+ normally
2) if you still can't boot you will need to use/make a goldcard (if you don't already have one this may require finding a friend's phone to help make one) and this time flash the orange nbh *not* rc29
0.95.0000 will not let you flash a rogers nbh so there is no way to re-flash with out a goldcard.. otherwise I'd just have you flash the roger 911 patch and re-root from there..

hey if you are still getting that screen with the yellow triangle and '!' that means you have stock tmobile recovery with no rom lol can you try to press (alt+L) hold alt and press L should make a list pop up.. if it does than maybe you can still re root it so than it will read your sim... but im not sure if the rogers G1 has and different software so it could possibly make it worse.. lol just a suggestion

ezterry said:
What you are describing is not 1.42.2000.. but 0.95.0000.. or that its likely the Dreaimg you flashed was the t-mobile rc29 and not the orange nbh..
Rc29 can be flaky.. but there are two options
1) go to recovery, alt+l and wipe, put a sim card into the phone and root via telnet.. assuming you have the 1.x radio of rc29 follow the link to my 1.33.2003 spl then with that install 2708+ normally
2) if you still can't boot you will need to use/make a goldcard (if you don't already have one this may require finding a friend's phone to help make one) and this time flash the orange nbh *not* rc29
0.95.0000 will not let you flash a rogers nbh so there is no way to re-flash with out a goldcard.. otherwise I'd just have you flash the roger 911 patch and re-root from there..
Click to expand...
Click to collapse
Hboot is 0.95.0000
Radio is 2.22.19.26I
So i'm guessing it is the rc29 And i'm not too sure what a gold card is? :S

SpawnOfSatan said:
Hboot is 0.95.0000
Radio is 2.22.19.26I
So i'm guessing it is the rc29 And i'm not too sure what a gold card is? :S
Click to expand...
Click to collapse
that sounds like stock 1.5 firmware to me

..Still have yet to find a solution....any help please?
info again is
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Background:
Accidently wiped rogers rom + flashed t-mobile rom, and since then,
Hboot says "Serial 0" and won't allow me to flash any images, phone doesnt have a recovery, will boot up now, but only to the android set-up process which i can't continue with because it won't accept my rogers sim card, despite the fact i unlocked the phone before all this happened :/ so i can't sign in to or create a google account. Have attempted every bypass to get past it with no success. Obviously since i can't get past it i have no access to adb...
Please help

Just out of my curiousity, got download the orange nbh file (make sure that it marked orange).
Format your SD card to FAT and put the nbh file in the root of your SD card.
put the SD card in your G1.
Boot up with camera+power and flash it.
See if that work.

BeenAndroidized said:
Just out of my curiousity, got download the orange nbh file (make sure that it marked orange).
Format your SD card to FAT and put the nbh file in the root of your SD card.
put the SD card in your G1.
Boot up with camera+power and flash it.
See if that work.
Click to expand...
Click to collapse
Thank you for your response, unfortunately i have tried that countless times with no luck it says it cannot read or flash or something, i forget what it says Exactly but it wouldn't allow it x.x any other suggestions?
I'm Really desperate x.x and i have been having the crappiest luck lately. I bought a phone off kijiji today, spent 3 hours trying to meet up with the guy to buy it, then when i did get it (after all the running around) i took it to "The Source" to get it activated in my name , and after 4 hours (5pm-9pm) they finally said they tried everything but couldn't do it because the phone is registered to someone with a contract that has a suspended account do to owing an outstanding amount of money!!

At this point, when you boot up the phone. What do you see?

BeenAndroidized said:
At this point, when you boot up the phone. What do you see?
Click to expand...
Click to collapse
It loads up to the setup screen, in which i cannot bypass...i have tried with another active (with data) rogers sim, telus sim, and virgin mobile sim card, but none of them will work....and like i previously mentioned, i unlocked the phone prior to all this happening :S

OK! I am not sure why it will not let you activate your phone. But don't worry about that ATM.
Let try activate your G1 over wifi. Follow the instruction from the link below.
http://theunlockr.com/2010/01/10/how-to-activate-the-g1-without-a-data-plan-or-sim-card/