Database Develop

Just a quick question

Hiya,
Just about to upgrade my SPL so I can use JAChero rom. Before I do upgrade I just wanted to makesure I have the correct radio. When I go to the system info page this is what it says:
62.50S.20.17U_2.22.19.26I
When I press camera+power at boot this is the info it shows:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Should it be okay for me fo flash the SPL?
Thanks

A quick yes thats gd or no thats wrong would be really helpfull.
Thanks

Yeah, that's the latest, you should be good to go.
If you're using Cyanogens recovery, make sure you physically press alt-s to flash then home + back to reboot. This means you have to name it update.zip Don't touch the trackball at all, otherwise it wont flash properly.

AdrianK said:
Yeah, that's the latest, you should be good to go.
If you're using Cyanogens recovery, make sure you physically press alt-s to flash then home + back to reboot. This means you have to name it update.zip Don't touch the trackball at all, otherwise it wont flash properly.
Click to expand...
Click to collapse
THANKS! I wouldn't have known that. I'll go ahead and do it now.

Just a heads up go ahead and load your rom on your card cause you will have to flash it right after you flash the spl cause the new spl will overwrite your existing rom and your phone will be stuck at the g1 screen.

graphics-guru said:
THANKS! I wouldn't have known that. I'll go ahead and do it now.
Click to expand...
Click to collapse
Yeah, I'm not sure if it's to stop n00bs from flashing the SPL without the radio (ie if they don't read that they need the new radio, they wont have read you need to press the buttons) or a bug. I saw a guy yesterday that thought he had the new SPL but actually didn't because of it :-S

Can't Flash Any Hero Rom

So I've been running Cyanogen's latest for quite a while now, with no problems that aren't systematic to whatever version he's just come out with. I decided to try something else just for fun, so I tried flashing JAC's and Drizzy's Hero ROMs. And yes, I flashed the correct radio and spl prior to the ROM flash.
For some reason, neither will work. They both come up with some kind of error at a certain line, either 80 or 59, I believe. So, I restore my backup to Cyanogen, and I'm back in business no problem.
Anyone care to hazard a guess as to what's going on? Thanks.
nspbass

I had that issue before. Here is what I did:
Wipe + repartition(dont forget you need 3)
reupdate SPL -> used the OTA, the the hardSPL
that worked for me, give it a try and good luck

Yeah I would just say wipe everything, make sure you use parted to split your sdcard which should be class6 into fat32/ext2or3/linux-swap.

You need Haykuro's special SPL. If you don't have it you will get that error every time.

shaolinx said:
I had that issue before. Here is what I did:
Wipe + repartition(dont forget you need 3)
reupdate SPL -> used the OTA, the the hardSPL
that worked for me, give it a try and good luck
Click to expand...
Click to collapse
Diceman4 said:
You need Haykuro's special SPL. If you don't have it you will get that error every time.
Click to expand...
Click to collapse
Exactly, so how the hell did Shaolinx flash it with HardSPL?

AdrianK said:
Exactly, so how the hell did Shaolinx flash it with HardSPL?
Click to expand...
Click to collapse
I'm sure he's mistaken.
And to the OP can you tell us what spl you have (cam + power).

Here's what it says:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
I assumed the HBOOT to refer to the SPL, which obviously isn't correct. So, I reflashed the SPL.
I think I did a bad thing. Phone won't boot to anything past the initial G1 screen. I thought this was only an issue if I had the incorrect radio. Thoughts?
nspbass

nspbass said:
Here's what it says:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
I assumed the HBOOT to refer to the SPL, which obviously isn't correct. So, I reflashed the SPL.
I think I did a bad thing. Phone won't boot to anything past the initial G1 screen. I thought this was only an issue if I had the incorrect radio. Thoughts?
nspbass
Click to expand...
Click to collapse
I hate to break the news to you but that is not the correct radio...the newest radio is 2.22.19.26I
Looks like its time to call TMO and put on your lying cap...
Also just because it says HBOOT does not mean that it is Haykuros SPL. THe special SPL is 1.33.2005

nspbass said:
Here's what it says:
DREA100 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-1.22.12.29
Sep 2 2008
I assumed the HBOOT to refer to the SPL, which obviously isn't correct. So, I reflashed the SPL.
I think I did a bad thing. Phone won't boot to anything past the initial G1 screen. I thought this was only an issue if I had the incorrect radio. Thoughts?
nspbass
Click to expand...
Click to collapse
and you have the wrong radio since the new one is 2.22.19.26I

Diceman4 with your slightly faster connection
but basically tell them your got an update or something, and that when the phone rebooted that it would not pass the g1 screen. also make sure you sound as clueless as to what root or flashing or anything technical is.

Ok, before this was a problem, I downloaded and flashed the radio, then the SPL. Clearly, they didn't take for some reason.
Now, my question is this: what do I do now? I'm looking in the bricked phone threads, but I haven't found an answer yet. Any help? Thanks.
nspbass

david1171 said:
Diceman4 with your slightly faster connection
but basically tell them your got an update or something, and that when the phone rebooted that it would not pass the g1 screen. also make sure you sound as clueless as to what root or flashing or anything technical is.
Click to expand...
Click to collapse
I wouldnt even say you got an update, I would just say that the phone restarted on its own one day and then just froze at the G1 screen. Be sure to not use any terms like "flash" "bricked" "boot loop" or anything that makes it look like you know anything at all about phone hacking. David is right just make yourself sound as clueless as possible.

nspbass said:
Ok, before this was a problem, I downloaded and flashed the radio, then the SPL. Clearly, they didn't take for some reason.
Now, my question is this: what do I do now? I'm looking in the bricked phone threads, but I haven't found an answer yet. Any help? Thanks.
nspbass
Click to expand...
Click to collapse
There is no way to fix it, the board needs to be replaced. You need to call t-mobile, follow mine and David's instructions and try to get a new one under warrantee

nspbass said:
Ok, before this was a problem, I downloaded and flashed the radio, then the SPL. Clearly, they didn't take for some reason.
Now, my question is this: what do I do now? I'm looking in the bricked phone threads, but I haven't found an answer yet. Any help? Thanks.
nspbass
Click to expand...
Click to collapse
i assume you have a cyanogen recovery image with the trackball feature? if so, for the radio and spl flashes you have to do the keyboard commands to make it work, you can't use the trackball or recovery console to reboot. so you can't boot into recovery or bootloader? if you can't, you have a brick

Diceman4 said:
I wouldnt even say you got an update, I would just say that the phone restarted on its own one day and then just froze at the G1 screen. Be sure to not use any terms like "flash" "bricked" "boot loop" or anything that makes it look like you know anything at all about phone hacking. David is right just make yourself sound as clueless as possible.
Click to expand...
Click to collapse
Done! Should have the replacement by Tuesday. I'm a tard.
nspbass

shaolinx said:
I had that issue before. Here is what I did:
Wipe + repartition(dont forget you need 3)
reupdate SPL -> used the OTA, the the hardSPL
that worked for me, give it a try and good luck
Click to expand...
Click to collapse
You know that you can't install hero with hard spl right? For someone who has a site dedicated to Android you don't seem to have your **** straight - no offense. And he could have bricked his phone if he tried to do H's danger spl without having the correct radio. Be careful when you give advice, we don't need to HELP people brick there G1's.

Haha, that's what I get for assuming he had the right spl and radio when he said he did. But if you are getting G1 screen you aren't bricked, if you can get into bootloader(camera+power) you should be able to flash your way back in time then forward again. I guess it doesn't matter if you're already getting it replaced but I got my friends back when his was only loading to G1, a true brick wont turn on at all no matter what you press.

JoshHart said:
But if you are getting G1 screen you aren't bricked..
Click to expand...
Click to collapse
If you do brick you will get the G1 splash screen, just nothing else..

Huh, well I guess my friend got lucky that wasn't his problem. Learn something new every day.

JoshHart said:
Haha, that's what I get for assuming he had the right spl and radio when he said he did. But if you are getting G1 screen you aren't bricked, if you can get into bootloader(camera+power) you should be able to flash your way back in time then forward again. I guess it doesn't matter if you're already getting it replaced but I got my friends back when his was only loading to G1, a true brick wont turn on at all no matter what you press.
Click to expand...
Click to collapse
Check the brick threads and you will see that just cause you have the G1 screen doesn't mean you don't have a brick. Flashing the SPL before the Radio will brick your G1 and you will be stuck at the loading screen. That is really the only true bricks we are aware of yet, maybe your friend found another way to brick but if you do some studying you will see what I'm talking about.

radio 2.22.23.02 DREAIMG.NBH problem

My English is bad. I'm sorry.
these problems.
radio Image 2.22.23.02 devices will not open. fastfoot mode does not boot. cablo computer with usb device does not see.
DREAIMG.NBH rc7 rc8 loading screen I press the button action. but the process does not happen. device, a way to save here?
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.23.02
Is anybody able to send to Turkey or the motherboard? please hep me...

Just some advice, you will want to ask your question in the Q&A section. This is not Android development related and this topic will most likely get locked.

theartar said:
Just some advice, you will want to ask your question in the Q&A section. This is not Android development related and this topic will most likely get locked.
Click to expand...
Click to collapse
your post is pointless, just because you are not capable of answering doesn't mean others can't
go and play a computer game on your windows pc..

bluecolor said:
My English is bad. I'm sorry.
these problems.
radio Image 2.22.23.02 devices will not open. fastfoot mode does not boot. cablo computer with usb device does not see.
DREAIMG.NBH rc7 rc8 loading screen I press the button action. but the process does not happen. device, a way to save here?
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.23.02
Is anybody able to send to Turkey or the motherboard? please hep me...
Click to expand...
Click to collapse
ok im not really understanding what happened but this method will layit out to you pretty simple. although it was written for cm 4.2.15.2 but all u gotta do is after flashing the dander ( death)spl wipe and then flash the new cm 508ds version which can be found HERE and feel free to hit me up on the gtalk b6gsix

bluecolor said:
My English is bad. I'm sorry.
these problems.
radio Image 2.22.23.02 devices will not open. fastfoot mode does not boot. cablo computer with usb device does not see.
DREAIMG.NBH rc7 rc8 loading screen I press the button action. but the process does not happen. device, a way to save here?
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.23.02
Is anybody able to send to Turkey or the motherboard? please hep me...
Click to expand...
Click to collapse
you can not use fastboot with HBOOT-0.95.0000
can you get to bootloader ( power + camera )
or recovery ( power + home )
and type in any language, I can use translator

Hello. logo stays on the display device. rum with just the camera + power button and the screen can scroll. Press the action button to start uploading DREAIMG.NBH said. but does not progress. : (

Firerat said:
you can not use fastboot with HBOOT-0.95.0000
can you get to bootloader ( power + camera )
or recovery ( power + home )
and type in any language, I can use translator
Click to expand...
Click to collapse
correction good sir,
you can enter recovery with just the home button.. i do it all the time

Firerat said:
your post is pointless, just because you are not capable of answering doesn't mean others can't
go and play a computer game on your windows pc..
Click to expand...
Click to collapse
Your post is pointless, just because you didn't put a answer. I know you are capable of putting an answer but you didn't so your post is pointless.
Go and play games on your gameboy color emulator on your linux pc.
So is he trying to say that he is bricked?

Moved as not development.

Here's a few pointers;
1) There is no fastboot with 0.95.0000. You need at least 0.95.3000 for fastboot.
2) If home+power gets you an EXCLAMATION POINT SYMBOL ("!"), then you are able to get into recovery and it is the FACTORY recovery. The next step is learning how to use it. I believe that pressing ALT-L should get you the recovery menu....
3) From recovery, I think there should be a wipe option.
4) Failing to progress in the install of an NBH file may suggest that your SDCARD is DEFECTIVE. Try another one!
These are NOT a set of steps -- they are a set of IDEAS that you should think about in looking at this phone.

I doubt its bricked, just to a region not support by rc27.. (ie not a mobile from T-Mobile in the US) If that is the case a goldcard is your friend.

Hello. While doing the installation to work with the same DREAIMG.nbh 2.22.19.26I installed. 2.22.23.02 but does not work with the same file.
recovery mode, do not open.

Firerat said:
your post is pointless, just because you are not capable of answering doesn't mean others can't
go and play a computer game on your windows pc..
Click to expand...
Click to collapse
It was worthless, but wasn't pointless. Just trying to help the guy not get mocked like I, ironically, was. You're right, I wasn't capable of answering.
Now back to my computer game.....

R3N0V4D0 said:
correction good sir,
you can enter recovery with just the home button.. i do it all the time
Click to expand...
Click to collapse
then there is something wrong with your g1
one mine I have to use the power button to turn it on, pressing home at the same time gets me into recovery

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?

PLEASE HELP :) home home screen, can get into recovery but can't flash

Hello,
I hope that title helped a little OK, so I have a a big problem. My phone turns on, boots up, and has some functionality like calling but I can not get tot he home screen and has tons of FC's. So I decided to try and reinstall a new ROM. I'm using RA-dream-v.1.6.2 for my recovery which it will boot to. Once inside there I can not boot the zip files on the SD card "E:No Zip files found" and the USB toggle does not work. Before I was also getting some type of Dev/block issue which does not seem to be showing up now, and I have no idea why. Its says the device is connected but it will never show up on my computer. I don't care about losing all my stuff because there was nothing on there anyway. I just want the phone to get back to normal so I don't have to buy a Nexus Sh*#. Any help or suggestions would be great. One other side not is that I'm running the danger SPL. Please help me out guys. Thanks
Other info:
Dream PVT 32B eng s-off
hboot-1.33.2005 (drea10000)
CPLD-4
Radio 2.22.19.261
CA

Update: Now it willnot get past the ROM "sparksco" flash screen! Any thoughts guys? Should I install a new recovery? What about just resetting the phone back to stock and starting over? Any thoughts guys?