Database Develop

my brick ?

no adb and no fastboot on pc
i can go into recovery but when phone boots it goes straight to tri color screen a.k.a bootloader with serial0
i tried downgrading it shows down grade on bootloader but not booting to rom what am i not doing

any suggestions

mods close thread solved by reflashing org.spl

ok it happen again and this time flashing stock spl is not working any help any one

Well it's very probable that by flashing your stock spl that youre now running a perfected spl which won't let you get any further, If you do manage to get back into the rom adb erase and flash a new recovery and spl because it sounds as if your recovery is fried. If you want help from others it would be a good idea to include rom, spl, radio, recovery that you're running so we can better assist you. every combination is different and often it's something as simple as a radio/rom mismatch or an overclocking issue

ok im at complete stock everything

rooted or unrooted?
one second thought.. try downgrading and re-rooting your phone via old school rc29 rom versions..
something has obviously gone awry. lets see if flashing an older rom will get you into the phone and then you can flash a new recovery, spl and radio from there.
http://forum.xda-developers.com/showthread.php?t=442480&page=35
Sometimes you just gotta redo everything because of software mismatches and extra crap in your phone that isn't supposed to be there.

i had bought the phone like that stuck on bootloader i fixed it after i tried to flash the org. spl it didnt flash but after reset it booted fine after rooting and using the danger spl and cannon complete eclair my carmera went bugging so i decide to downgrade and reroot i flashed the rc29 but it went back to the first problem again

all eclair roms have problems with cameras.. but this sounds more like there's just something not right.. could be anything from your radio to your recovery.. Full wipe and restart the process I no longer have a g1 but im pretty sure if i downgraded from 2.1 to rc29 my phone would act screwy too.

i did the full wipe formated sd cards i am at a brick wall with out a brick

thatruth132 said:
i did the full wipe formated sd cards i am at a brick wall with out a brick
Click to expand...
Click to collapse
set up sdk/adb and see if your phone is being found or not with the command
Code:
/cd
cd AndroidSDK/tools/
adb devices

i have adb installed correct its not picking up in adb at all no fastboot of course

I don't know i maybe wrong but think you should start all over again
downgrading to v1.0
although i am not that experience
please wait for someone how know

nothing i try is catching

still needing help

And we still don't know what you have installed..
1) make sure your phone is off: boot into the spl by turning on the phone while holding down camera.. tell us all the text on that screen
2) power off your phone again and enter recovery (power on holding home) if it loads do you see any version info? Or just an icon in the center of the screen.. if it dosent load tell us that
3) can you boot into a system (in your case I assume not but if others are reading) tell us the build number and rom if possible in about phone. If it wont boot tell us that.
4) Last what carrier and country is the phone originally from. (This changes what "stock" is)
With all of this information we can find the correct path to solve any issues.. usually without resorting to jtag.

DREA 100 PVT 32B
HBOOT 0.95.0000
CPLD 4
Rado 2.22.19.26I
Sep 2 2008
At this point, I searched around again for 30 minutes or so, and saw the stuck camera button problem and took off the back battery case and performed a restart and still went straight to the SPL with almost no delay. The camera button depresses properly and doesnt seem to be stuck.
After all this, I figured I should just start off fresh, so I flashed the DREAM.nbh for RC29 that is listed everywhere in order to get root. On restart, I held down the camera button, and the white screen comes up to ask if I want to boot image.
I do, and everything goes off without a hitch, I press action key to restart and end up at the SPL screen again, this time, my radio is down to v1.2 instead of v2.2 so I know I changed something. I have done this update twice just to make sure everything is going right but I am still stuck at SPL.
Sorry for the extensive post, but as you can see, I did a bit of trouble shooting before I posted this.
1 did that
2 did that regular recovery
3 can not boot into system on 1.5 cupcake signed-kila-ota-148830.de6a94ca.zip
4 tmobile usa

anything i know its not bricked

OK you have rc29 installed. That is the original android with 1x radio. So software wise you are fine. (Ie not bricked)
The problem is you need to enter normal boot and are always entering the spl instead?
My guess is the camera button is stuck..
The real button is surface mounted on the main board what you press is a user friendly piece of plastic on top of that, attatched to the phone's cover.
If you have any warranty get T-Mobile to take a look.. Otherwise you can try opening it and cleaning it out.

i tired that and i actually switched the mother boards and check the buttons and nothing is stuck when i update to rc29 it lets me when i update to cupcake it lets me the text even changes on bootloader but not actual boot

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?

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

Okay, so a few years ago I successfully rooted my boyfriend's G1 and swore never again to go anywhere near the process.
However, said phone has now been given to my boyfriend's dad, and he's managed to install a couple of custom roms. In the last week though, he's totally screwed it up. Didn't seem to follow any sort of backing up process, or can even tell me what tutorial he was following to get it in this state.
The phone hangs at the splash screen. I can get into fastboot/hboot but there are only a few options available.
SPL is 1.33.0006 which I can gather is bad from my reading.
Hboot info is:
Dream PVT 32B Ship S-on
Hboot - 1.33.0006 (Dream11000)
CPLD-4
Radio-2.22.19.261
I have tried:
Initially I just tried going into recovery mode (I think that's what it's called - home & power) and wiping the data to see if that stopped the screen hanging. It didn't.
Putting rc7 dreamimg.nbh on the phone and loading via hboot/fastboot. When I do this it fails saying 'Main version is older.'
After doing some searching, I see someone mentioned this would mean you need to use the goldcard method. I vaguely remember having to do this a few years back on the phone when I rooted it the first time.
I go through the process, following an unlockr tutorial (can't post the link - sorry).
However, I get the same response through fastboot - 'main version is older'.
At this point I decided to try flashing a recovery image via the adb. Go through the process of installing everything etc. but when it came to installing the usb drivers for the phone, it failed although it did install the htc bootloader. I checked using adb devices command to see if it was picking anything up and it was however, when I go into the command prompt and try to do anything I just get a <remote: not allow> message.
It's only after I look for <remote: not allow> message error that I understand that 1.33.0006 is a 'perfect' SPL, and explains why I can't really do anything.
I really didn't want to resort to forum posting (one of the reasons I swore never to go near the G1 again after rooting was because I *know* I'm not tech savvy enough to be messing around with this stuff), but after spending around 6 hours over two days on this I'm absolutely stumped. The problem is, I'm stubborn so I hate to give up after spending so much time on the stupid thing (bye bye flexi day), so if anyone has any suggestions, or if they could just tell me it's a lost cause then it might help.
Thanks for your time...

do you have the UK version of phone or the US version?
can you get into recovery?

Sorry, it's the UK version - I can get into recovery (if that's home and power ?) I think. Thanks.

What nbh file was flashed prior to this? (almost sounds like the states someone was in after flashing the sappimg on a dream with 1.33.0013d..
Well first thing is to make a gold card if you don't already have one.. Then we can try one of two things. (you can make it on another phone, its a property of the sd card not the phone)
1) (may have the same main version is older problem but easy if it works) place the Orange nbh:
orange-1.58.73.2.nbh (MD5: aca4dee0c1ece7e9773f2ecbdfbba7c0)
onto the root of the goldcard named DREAIMG.nbh
If this works (or at least flashes the s=off SPL) you are in the clear simply use fastboot to re-install the 2708+ recovery/radio/spl then install a rom as per here
2) If option 1 failed... well this is an annoying process.. and risky if you take shortcuts so don't ..
A -- This time put the rogers e911 patched nbh rogers_1.89.631.1.nbh MD5:25bfcc329679e4869b3d65f673e463ac
onto the root of the goldcard named DREAIMG.nbh
This is the larges "main version number" in an official nbh for the Dream we have.
If that fails to flash (try again) if it still fails.. well I'm not sure what to do if both boot/recovery are failing (short of jtag anyway)
B -- If it succeeded you now (despite any labels on your phone) have a rogers dream.. (I mention this because working with an ebi1 radio is a bit different than the ebi0 and you don't want to brick your phone)
Ok next step is re-root: http://forum.xda-developers.com/wiki/index.php?title=Rooting_HTC_Branded_EBI1_Dreams
(Sections A-D inclusive)
C -- Before installing a rom.. now that an eng SPL is installed you can use fastboot (and only fastboot with the 3.22 radio) to install the 2708 radio and thus have a more commonly supported system:
per Follow this 2708+ install
remember do not install a 2.22 radio via recovery while a 3.22 radio is installed you will brick your phone
--
Best of luck.. really sounds like something happened that ought not have.

Thank you!
Option 1 didn't work - I still got the 'main title is older' message.
However, option 2 (after a small wobble) worked! First time I tried it, it failed stating 'partition update fail!' but after a reboot (which showed the rogers logo - a change from before) and a retry, it worked! I followed the rest of the provided instructions and installed the BIFFMOD V2.1-EZTerry 2708 port and all is well!
Thank you so much again for your help, it really is appreciated. I would not have been able to do this without your help - I've sent a small donation through as a token of thanks.
I've learnt more about G1s than I ever wanted to know, but thanks to you (and the information provided by the XDA community) it wasn't all wasted time!

[Q] Wow I feel lost...

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

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

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