Database Develop

dev phone

been having some real trouble with my uk spec g1, ive experimented with it quite alot, ran jakrom, the dude, jesusfreke, and settled on cyanogen, i dont think ive ever gone about flashing it all properly, so my phone threw a fit and now after a hard reset it comes up with the google sign in droid and it says dev phone underneath?!?
i think i also lost root as i no longer have spare parts and no superuser permissions,
i tried to root again with a down grade to ukrc7, when i try to enter the bootloader it comes up with the skateboarding droids, says no images found and go's back to the droid skateboarding again, then i cant do anything with the device!!
help appreciated!!

tobirichmond said:
been having some real trouble with my uk spec g1, ive experimented with it quite alot, ran jakrom, the dude, jesusfreke, and settled on cyanogen, i dont think ive ever gone about flashing it all properly, so my phone threw a fit and now after a hard reset it comes up with the google sign in droid and it says dev phone underneath?!?
i think i also lost root as i no longer have spare parts and no superuser permissions,
i tried to root again with a down grade to ukrc7, when i try to enter the bootloader it comes up with the skateboarding droids, says no images found and go's back to the droid skateboarding again, then i cant do anything with the device!!
help appreciated!!
Click to expand...
Click to collapse
Could you explain a little better? So your phone is a UK G1, with 1.33.2005 SPL and you were running a Cyanogen Mod ROM, and then something weird happened?
If you're on 1.33.2005 SPL then it's a good thing your phone didn't take the NBH, your phone would have bricked. 1.33.2005 requires the 26i radio which gets downraded when reverting to RC7.

AdrianK said:
Could you explain a little better? So your phone is a UK G1, with 1.33.2005 SPL and you were running a Cyanogen Mod ROM, and then something weird happened?
If you're on 1.33.2005 SPL then it's a good thing your phone didn't take the NBH, your phone would have bricked. 1.33.2005 requires the 26i radio which gets downraded when reverting to RC7.
Click to expand...
Click to collapse
Its safe to Downgrade with the RC29 image as it replaces the radio AND the spl
Can you provide more details on the issue? How it happened/what you were doing?

one problem to another
Right, I've wiped my phone, formatted the sdcard so that all is on it is the files needed to update to cm!
The phone is running perfectly like a stock handset, but it won't let me root, when I type into telnet the code to apply the cm recovery image I get an mtd error, but it is still followed by the two ##

Have you tried using the root.apk app that helps to flash it? Search for it and maybe it can help you out

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] G1 freezing on BiffMod2.0

I recently flashed BiffMod2.0 to my rooted Rogers Dream using ezterry's EB1I port. I've got the DangerSPL, I've cleared the cache's and factory reset twice, but it keeps having this issue. When left for about 20 min to an hour, it'll lock up solid, whether I'm in the middle of something or its on standby -- and I can't shut it down until the battery is removed. If it freezes while locked, I can still hear the unlock screen working, and the buttons light up, but the screen stays blank. I thought it might have been an issue with the display, but it's also frozen solid with the screen on, while I was in the middle of using the phone.
Bad install or bad ROM?

Ya, 2.0 did that sometimes. it was so bad that I went back to 1.9.2. But then there was an update to 2.0.1 that fixed that, and now 2.1 is the latest. Try updating.

Several Zombies said:
I recently flashed BiffMod2.0 to my rooted Rogers Dream using ezterry's EB1I port. I've got the DangerSPL, I've cleared the cache's and factory reset twice, but it keeps having this issue. When left for about 20 min to an hour, it'll lock up solid, whether I'm in the middle of something or its on standby -- and I can't shut it down until the battery is removed. If it freezes while locked, I can still hear the unlock screen working, and the buttons light up, but the screen stays blank. I thought it might have been an issue with the display, but it's also frozen solid with the screen on, while I was in the middle of using the phone.
Bad install or bad ROM?
Click to expand...
Click to collapse
MAN, Biffmod needs Hard/Death/Haykuro's SPL not DANGER SPL (the one you got), it's not gonna work until you flash Death SPL in your phone
Before flashing, Turn off your phone & Press (Camera & Power), check which board you got (if it's PVT, then go for Death SPL (follow instructions, Stock > Root > Amon's Recovery > Radio Update > Death SPL > Biffmod) but if you got DVT board (as of me), never make a mistake of even downloading Hard/Death/Haykuro's SPL, they are not compatible with DVT phones, so avoid BRICKING your phone

rawfire said:
MAN, Biffmod needs Hard/Death/Haykuro's SPL not DANGER SPL (the one you got), it's not gonna work until you flash Death SPL in your phone
Before flashing, Turn off your phone & Press (Camera & Power), check which board you got (if it's PVT, then go for Death SPL (follow instructions, Stock > Root > Amon's Recovery > Radio Update > Death SPL > Biffmod) but if you got DVT board (as of me), never make a mistake of even downloading Hard/Death/Haykuro's SPL, they are not compatible with DVT phones, so avoid BRICKING your phone
Click to expand...
Click to collapse
Um, two problems. Death/danger spl are the same thing. It's the spl from the mt3g patched gor the g1. Also, the rom would be too big to install or wouldn't boot if there was a problem with the spl. There is a memory leak in biffmod 2.0, which causes the freeze. Update to 2.1.
Sent from my T-Mobile G1 using XDA App

Bigt2003 said:
Um, two problems. Death/danger spl are the same thing. It's the spl from the mt3g patched gor the g1. Also, the rom would be too big to install or wouldn't boot if there was a problem with the spl. There is a memory leak in biffmod 2.0, which causes the freeze. Update to 2.1.
Sent from my T-Mobile G1 using XDA App
Click to expand...
Click to collapse
They are same things mate but there's board difference (DVT/PVT) which actually matters in Danger & other SPLs

rawfire said:
They are same things mate but there's board difference (DVT/PVT) which actually matters in Danger & other SPLs
Click to expand...
Click to collapse
If they're *actually* the same they all work on the same type of board, wat you just said made no sense.
Also this is the second time I have accidentally given thanks because I'm used to having the quote button on the far right, ****ing hell.

atleast death SPL haven't worked for me on DVT board (it bricked my G1)
Cheers

rawfire said:
atleast death SPL haven't worked for me on DVT board (it bricked my G1)
Cheers
Click to expand...
Click to collapse
I think you'll find your inability to follow simple instructions bricked your phone, a phone can't brick itself it can only do what YOU tell it.

[Q] Cannot install 2.2 on my g1 help me please

Hello,
i had android 1.6 on my g1 i tried to upgrade to 2.2 and i bricked it then i went to fix it by JTAG. then i am trying different ways to install roms but it never does.
sometimes it makes loop of restart
sometimes i install the radio and spl exactly as a post here says but at the end it says that setup cannot verify the update package!!!!
now i have r7 on my phone so can any one please to give me exact steps to do with exact files to install at least android 2.2 ? because i tried so hard follow many posts but it never work.
thank you for your help guys

Are you sure you have a non stock spl and radio. Most roms won't install if the spl isn't changed. I think it has to do with the size of the roms. The stock spl will only load up to 44 mb. (Or something like that) the new spl changes the partition to 90 (or somethin....)
I am sure most froyo roms are larger than the stock spl will allow. I would start by checkin what it says in your bootloader screen. With phone off hold the power and camera button and it should take you to the bootloader screen. Get your hboot and spl number and see if it is the danger spl or stock.
Sent from my HTC Dream using XDA App

Did you root your G1 already?

go here http://forum.xda-developers.com/showthread.php?t=1098899 update your device to latest and greatest!! lol

[Q] Al little direction...

OK here it is. My G1 is currently on version. 1.0 (RC29) stock recovery as well. i have been scanning the forums here and keep finding info with broken links and pages that say they are out dated. Can someone here post me a few links to some current info on rooting and installing a froyo rom (gingerbread was too laggy) the part that seems to get me lost is all the radio, spl, and recovery menu options out there and after 3 attempts at rooting and installing a new rom last night all i could get the phone to do was hang at the g1 screen. so now im back to stock on the phone and will wait on some help before i attempt this again. I used this site to root and hack back when i used the phone for PSFreedom, but it wasnt as cluttered with info overload.
The phone is:
T-Mobile G1 US
Firmware 1.0
PS I already installed Telnet but thats as far as I have gone. And if you can point me to a Froyo rom that is stable and runs without lag I would really appreciate it. Thanks.

ok this guide is easy to follow... [Guide] (8-18-11) G1 How-to: Root, Un-Root & Everything in-between
just folow instructions and i will help you along the way if you need it

ok i did the wipes and everything in the first step but when i get to the google sign in screen the phone shows no signal (usually 4 bars where i am) so i cant get past the google screen to do the next step.

wait you said you were on 1.0 already? so which file did you flash the update.zip? and you cant sign on..?
thats just the update to 1.5 so im not sure why you would have no signal...

no idea either its rooted though i have tried a few roms so far.
GINGERBREAD-DS-Beta-20110716 (hangs at G1 Screen)
cos-ds =07182011 (makes it as far as the bluish android logo and then loops)
will the 1.5 update work with the hboot0013d and the 2708 radio?
when i flashed the 1.5 update (as in the guide) it made it to the google sign in screen and wouldnt let me by, so i reflashed the 1.0 file and got my service back restarted the guide and skipped the 1.5 update the second time.
my fast boot info:
Dream PVT 32b SHIP S-on
HBOOT 1.33.0013d (drea10000)
CPLD-4
RADIO 2.22.28.25
OCT 21,2009,22:33:27

wait no that dont make sense... lol are you trying to root your device?
if you have 28.28 and 0013d than you are rooted and should be good to flash roms.. all you need is to make sure your sdcard is properly formatted and partitioned lol

some roms require an ext4 partition... if you have amonra recovery than go to partition sd options.. choose partition sd and set swap to 96mb and ext to 512mb.. than upgrade ext2 to ext3 than upgrade ext3 to ext4.. than wipe all data, cache, system than flash a rom..

I did all the steps i managed to get it rooted but with the specs of hboot and radio i tried 5-6 roms and none booted up i even tried the SenseLX one with MTD and without, and never made it past the G1 screen i have even gone back to rc29 a few times and started over. this last attempt i decided to just got to 1.6 so i did the upgrades for that (unrooted) and when i hit 1.5 i lost all cell signal again, went to 1.6 and still didnt have it now im back to 1.0 again. im lost on what could be going on.

so your saying you had radio 28.25 and hboot 0013d and you couldn't get the roms to boot?
and that you cant get a cell signal?
-for the rom issue i think it may be your sd card...
-for the signal issue you might need a new sim card... you can get them replaced for free at a tmobile store..

New SD card and sim in phone and attempting this again... ill keep you posted on any progress if any.

This is a regular US T-mobile branded G1, not a unbranded or Asian, model?
If you are still having these issues, and starting from any Engineering SPL, you might try the orange-1.58.73.2.nbh file over here.
It updates radio/hboot/kernel/system all at once, in a known working set.
You can change the French over to English, but might need to know a bit of French to find the setting, and I even kept it on a phone for my kids to play with (no sim) just to run some apps via wifi.
Then if you get REALLY stuck again with updating, just flash back to the orange NBH, it is much easier then going all the way back to RC29 and rooting again.