Hi guys and girls,
First of all here's a little bit background:
I always liked Nokia (GSM's!). My first mobile was Alcatel OT Easy db if i'm not mistaken. After that i had several Nokia's. And then for many years i have used Sharp GX25. While i was using it, GSM world has quite changed. The only GSM i saw like perfect (because of the small size) was Modu mobile at the time. But i couldn't get it anywhere. And the iPhone is like cool. But to bulky for a GSM and to expensive for a thing to call with. When the battery of the GS25 died completely i was thinking how am i going to choose now? ^^ The only thing that i liked was Modu mobile but i couldn't get it anywhere. I don't really cared a lot about some features and so on. Because to get into choosing a phone now, to choose wisely, best for the money, is like spending so much time..
I'm often sending sms to a group of like 20 people. So i bought LG Neon. First cheapest full keyboard gsm i came across. I was thinking you know, Nokia is like the best ever, or has been for me, but i have to give something else a chance. Although i liked the full keyboard it was a really bad experience. But i learned something. So after that i remembered, that i was thinking sometimes, if iPhone was a little bit smaller and cheaper i would buy it. But then i accidentally realized. There are so many ideas you can google. Lets try, cheaper iPhone alternative. So i found Nokia Tube (5800, second hand). I pretty liked it - cheap, compact, a lot of features. I discovered mobile email/gps/sip telephony!/calendar/touchscreen and other nice features of a smartphone. Symbian (Nokia) was still good for me. So now i became kind of accustomed to this nice features. But Tubes touchscreen wasn't really great ether. So i was looking out for some other, more advanced, full keyboard/touchscreen smartphone. Not necessary touch screen, but anyway, it would be nice. So for some time i have been looking on a second hand sites to get a second hand blackberry. Because after researching the question of mobile Emailing i came to a conclusion that Blackberry is the best in it. And even that Blackberry is maybe like the best smartphone of all because of user friendliness, design maybe, and a technological advancement. Like the Mac in a PC world. As i see on the video reviews Blackberry's interface looks more text based would i say. What in my eyes is perfect for a smartphone. I don't see a lot of sense in bells and whistles, or how is it said then in actual information. But!
About not mobile experiences:
It's already for a view years that i am using Linux on my desktop. Since the time when i have got the GX25 i guess. Because i have been quite interested in IT from when i was younger. And now later i already became IT professional and run some Linux servers to. And even my Mac Mini at home runs Linux. I find Mac OS X amusingly technologically advanced, easy to use, user friendly and all that. But i cant install it on my workstation and a laptop at work. So that's the practical reason i choose Fedora over any other OS. No fanaticism here. Because i'm Christian and i believe in Jesus Christ. Because from His words in Bible i learned, or got at least some kind of understanding of what is love actually. So i don't have to be religious about Mac or Linux.
The funny thing actually is, i have used Gnome 3 now for a view month already on Fedora. And a view days ago installed Lion on a Mac. Wow, they already put all the Gnome 3's features in Lion, like first Spaces and now Mission control and Launchpad. ^^
Now, closer to the business - CM6? Dream:
So finally i was thinking, what else can i get, then android. I actually nearly bought Blackberry 8520 pretty cheap. But G1 compared to it has GPS and AutoFocus. And it runs Linux *thumbs up* \o/
Now, when i got the package from Netherlands view days ago. The guy have put CyanogenMod 6 on it for me. But after a day of use i discovered that when you call to me you go straight to voice mail. And i pretty liked CyangenMod's interface although i had an idea, from youtube videos that Hero rom would be nicer(visually). Google apps were not installed ether. So i googled a little bit. And At some places they said that you have to install google apps. But it didn't work. I tried installing it, but always got message about making recovery backup. And then after reboot still no Gapps installed. The phone came with a sd card with cyanogenmod rom on it and two hero roms. Off course before buying it, i already searched for some info. And went to CM wiki. And first questions that arised for me were: how do i determine which radio does the phone has? When i emailed this question to a guy from who i bought the phone he said that someone else has put Hero on it for him. So before he sent it to me he had put CM6 on it. This is i think where the trouble with calling is from. So i played a day with CM6. And using the ROM manager have put Hero on it back. Because seeing video reviews i thought it looked cooler. But now i have an impression, while using Hero rom, like CM6 was better. Like more tweaks and so on. So another question: What are actually benefits of CM6 compared to Hero rom, and vice versa? And the other question is: How do i put CM6 back? Because i don't find ROM manager in the menu anymore. Do i have to install it again? And by the way. I have made a recovery backup when rom manager asked me to do it while trying to install gapps. But doesn't matter a lot i guess. Because people couldn't call me there anyway. And here on Hero it works. I ask myself does the firmware for radio sit in the rom or not? (Ohh, and i actually just realised something, rereading the post here, and checking for errors. Would the radio rom be something like phones bios? And ROM like phones os?)
And also i'm confused a little bit about the process of flashing now. On the wiki i read bout installing DangerSPL and so on. But i have put Hero now just using ROM manager. Has it become easier or how does it work today? Also i ask myself which CM version is like optimal for Dream? To get some nice features but not getting to slow? I guess it would be 6 right?
Okay, hopefully someone can share some knowledge with me about all that rom flashing thing. Or point me to the right direction. Where to start reading.
Thanks in advance,
Sincerely yours,
Nikolai
versions info
Ok, i figured something.
Im reading the "HTC Dream: Installing CyanogenMod 5+" wiki page and heres the info i found so far:
DREAM PVT 32B ENG S-OFF
HBOOT-1.22.2005 (DREA11000)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009,15:30:43
HBOOT
Parsing...[DREAIMG.nbh]
[1] RADIO_V2
[2] BOOTLOADER
[3] RECOVERY
[4] BOOT
[5] SPLASH1
[6] SYSTEM
[7] USERDATA
Do you want to start update?
<ACTION> Yes
<POWER> No
============================
ClockworkMod Recovery v2.5.0.7 (the version)
============================
ROM's on the SDcard:
update-cm-6.1.0-DS-signed.zip
gapps-mdpi-tiny-20101020-signed.zip
---
zx2.1hero.v1.5.1.zip
update.ZX1.5Hero.v2.0.1.zip
dream_magic.2.22.19.26i.zip
Now i expect that offcourse DangerSPL is already installed so i skip this part. Only the version numbers are different. Wiki says 33 and my phone says 22. Then i see there the line tat says: "Select USB_MS toggle" - what does this suppose to mean?
ok
Ok i figured it. Rebooted into the recovery mode. Flashed CM6.1. Ended up in reboot loop. Googled. Wiped. Reflashed. And now it works. Working CM6.1 with working recieving calls.
THanks you guys.
DangerSPL
Hi agane,
The guy from who i bought the phone told me that i have to flash in this order:
-Wipe cache/data
-Install zip: de gewenste ROM
-Install zip: Google apps tiny
-Install zip: DangerSPL
But i havent done DangerSPL. Does it matter?
given that u already are running danger spl,u neednt flash it again, unless u upgrade ur radio and have to flash the corresponding spl....
ok thanks
Ok thanks, that's what i was thinkig.
Froyo by Lazslo
Hi guys,
im back to hacking ^^
well since i work and do alot other things i just bought a Blackberry 9780 and hapily used it all the time since i last posted here. And device is great. I like it alot. There was just a little issue i tought would be nice if it could be fixed. So i asked the retailer i bought it from to send it to BB. The stuttering keyboard is it. Google if u wanna know.
So now. Since i had blackberry i havent used Dream anymore. But back in the time i last posted here the sales guy who sold me the BB had a Dream to. And he advised me to use the Froyo by Lazslo. So now after a view month im back at Dream. I actually pretty havent used it alot.
So now i took my Dream and flashed the froyo by lazslo on it. The slp and radio numbers u can see in my previous post. So not i got the G1 logo at boot and the phone isnt booting. I suppose i did not good just flashing it. Because spl and radio numbers mentioned in the froyo by lazslo thread are not the same as mine. But i thought ok lets try. Wiped and installed the froyo by lazslo rom. And now have G1 logo. Well if i push camera button when booting i get into fast boot.
But can i push some combination to get into recovery to flash for example atleast cgm that atleast worked for me? TO get back to working state? Or what can i do now further to get froyo by lazslo running on it? Does the G1 logo means its bricked or not? Because dont know really? Have googled and found that theres posibility to do something via cmd. Any more info on this?
I google further, but dont have alot of time,
Thanks in advance,
Nikolai
good found something
i see that i had to have the ecsactly spl and radio mentioned in froyobylazslo thread
now gonna search how i install them,
because i got the phone with them already installed
not brickked - fixed
oh, good, got it fixed,
have pushed power and home button not long enough before,
so now after getting into the recovery flashed cgm 6 back on it. and its working
but i still think and will search more the other day to put froyobylazslo on it
just need to find instructions to get to newer spl and radio on it.
would anyone help thanks,
now gtg to Church,
see yaa
un root?
Hi all again,
So,
Is it so that i have to unroot and reflash all from the beginning now to jusmp from
HBOOT-1.22.2005 (DREA11000)
RADIO-2.22.19.26I
to
SPL: 1.33.0013d (hboot)
RADIO: 2.22.27.08 / 28.25
let me know please. ty.
edit,
ahh yes,
or can i still do something to flash froyobylazslo with my radio and spl and tont end up with g1 boot screen?
Nikolai_D said:
Hi all again,
So,
Is it so that i have to unroot and reflash all from the beginning now to jusmp from
HBOOT-1.22.2005 (DREA11000)
RADIO-2.22.19.26I
to
SPL: 1.33.0013d (hboot)
RADIO: 2.22.27.08 / 28.25
let me know please. ty.
edit,
ahh yes,
or can i still do something to flash froyobylazslo with my radio and spl and tont end up with g1 boot screen?
Click to expand...
Click to collapse
There is no need to unroot and start from the beginning. I suggest you to learn how to use fastboot and then read in Terry's 2708 thread how to do the update.
Another hint: After you are on the "new" SPL/radio combo you should check twice whether the ROM you want to install supports this combo, otherwise you will stuck on the G1 screen ...
this
Hi,
the guy here explains some things,
http://www.youtube.com/watch?v=sYg3UmQd5y4
what if i download the radio and spl that i need for froyobylazslo and update them the same way thee guy in the video did. Is it gonna work?
p.s. it looks the link u gave is definitive place aboout that but its difficult to follow
On the first look it probably looks difficult, but if you want to root your phone, install unsupported radio and SPL on it, then it's worth to invest some time to learn a bit more of this topic. Otherwise, if you do something wrong or you follow a guide which doesn't comply to your current "configuration" of the phone , risks are high, that it will get bricked. Just my 0.02 cents.
Sent from my Gingerbread on Dream using XDA App
back
hi all,
im back to mess with it a littlebit,
I installed Anroid SDK, and now i want to start flashig via fastboot as described in the link posted above.
But i dont get how do i start a CMD. Just starting CMD and writing for example fastboot devices in CMD doesnt do anything.
Any suggestions please?
And yes im googling to.
Thanks,
Nikolai
First you need to connect your phone to your PC by USB and get it recognized. You can check that by opening a command line window on your pc and typing
adb devices
if your phone is in "normal" or in recovery mode. You should also check whether you enabled "USB Debugging" in Menu -> Settings -> Development.
You should get a list with your device.
To check fastboot, your phone needs to be in fastboot mode. Switch off and reboot by back-Button pressed. In this case the phone gets into the hboot screen.
Now you can type
fastboot devices
on the command line and if your phone gets recognized, you will see it in the list printed on the screen. If it is not recognized directly and serial0 is printed on the phone's screen, try to press the back button. Then "fastboot" should be written on the screen and you can re-try whether your phone will be recognized.
figured
ok i figured that i had to download the fastboot file mentioned here
http://wiki.cyanogenmod.com/wiki/Fastboot
And the system variable path needed to be configured right.
now i dont have dll error but fastboot devices doesnt show anything,
adb devices does
AndDiSa said:
First you need to connect your phone to your PC by USB and get it recognized. You can check that by opening a command line window on your pc and typing
adb devices
if your phone is in "normal" or in recovery mode. You should also check whether you enabled "USB Debugging" in Menu -> Settings -> Development.
You should get a list with your device.
To check fastboot, your phone needs to be in fastboot mode. Switch off and reboot by back-Button pressed. In this case the phone gets into the hboot screen.
Now you can type
fastboot devices
on the command line and if your phone gets recognized, you will see it in the list printed on the screen. If it is not recognized directly and serial0 is printed on the phone's screen, try to press the back button. Then "fastboot" should be written on the screen and you can re-try whether your phone will be recognized.
Click to expand...
Click to collapse
thanks
trying further
duplicate post
spoofspl?
Do i have also to do this?
> A Rom (note: many cm6 based roms block install because of the '1.33.0013d' bootloader Please use firerat's SpoofSPL)
http://forum.xda-developers.com/showpost.php?p=9068311&postcount=84
Depends, what you want to do. Normally this spoofing is needed only when you want to install a ROM which officially isn't supported, but you know that it is runnig with your SPL. Especially when using cMTD you change the partition layout and some ROMs check with the SPL whether the ROM fits into the system partition or not.
Related
Hi guys,
I've been searching and searching, but a lot of the posts are dated June or July and I'm basically hoping to get the latest information.
I'll start with the details:
Rogers Branded HTC Dream
Recovery: CyanogenMod v1.2 + JF
Dream PVT 32B ENG S-OFF
HBoot: 1.33.2005 (DREA21000)
CPLD-4
Radio: 3.22.20.17
Apr 20 2009, 15:30:43
FW Version: 1.5
Baseband Version: 62.52S.20.18U_3.22.20.17
Kernel Version: 2.6.27-9af60ed4
[email protected]
Build No.: 1.85.631.5 146733 CL#33863 release-keys
Rooted (I think/hope!)
My Questions:
1- What is the best OS out there right now? (I know this depends on the user, but there must be ones that are more popular than others and ones that should be avoided). I'm mainly looking for something that would address the following:
* a proper voice dial ... the one that came with the phone is half assed ... recognition is great, but it's not exactly hands-free!!
* multi-touch ... I hate the iPhone, but you gotta agree that's one kickass feature
* SMS time stamp issue ... after 2 weeks it still confuses the hell outa me for the first few seconds
* My inner geek would like a good linux/unix shell too ... don't ask why
2- I can't get anything later than CyanogenMod 1.2, it won't get past the boot splash ... re-flashing to the 1.2 works ... any ideas?
3- All the links to the 'latest radio' point to a 2.x version, but I have 3.x ... doesn't that mean I have a newer version?
4- I flashed Splash1 and Splash2 to 2 different PNG images, but on boot I get what seems to be the default splash screen, 3 androids on skateboards (It used to be the Rogers logo). What are the specs on the splash image? and where do each of these splash screens come up?
5- How do I know if my phone is actually rooted? I type 'adb root' and I get 'adb is already running as root' ... is that enough?
6- if I type 'adb shell' and then 'su' the command is not found ... are these *nix commands only available in custom roms?
If you're about to start flaming, please take it elsewhere. I'm frustrated, overwhelmed, and not exactly satisfied with my search results because many posts are old and in some cases conflicting. Forums are where (the more experienced) people help other people.
If I've missed out any details/questions, I'll update my post. I will also update the first post with the answers immediately after the questions, is possible in a different color (it's easier for new people to follow up and get answers).
Thanks a lot for your time (I'm sure you've had stupid n00bish questions too, before you became 1337 ).
Next time search more to post the thread in the good place
ANDROID is the BEST OS for ROGERS HTC DREAM. actually its the only one. an OS is sumthign like android,windows mobile,webOS,symbian,etc.
just letting u know what the definition of OS is. or more like examples
My Questions:
1- What is the best OS out there right now? (I know this depends on the user, but there must be ones that are more popular than others and ones that should be avoided). I'm mainly looking for something that would address the following:
* a proper voice dial ... the one that came with the phone is half assed ... recognition is great, but it's not exactly hands-free!!
* multi-touch ... I hate the iPhone, but you gotta agree that's one kickass feature
* SMS time stamp issue ... after 2 weeks it still confuses the hell outa me for the first few seconds
* My inner geek would like a good linux/unix shell too ... don't ask why
2- I can't get anything later than CyanogenMod 1.2, it won't get past the boot splash ... re-flashing to the 1.2 works ... any ideas?
3- All the links to the 'latest radio' point to a 2.x version, but I have 3.x ... doesn't that mean I have a newer version?
4- I flashed Splash1 and Splash2 to 2 different PNG images, but on boot I get what seems to be the default splash screen, 3 androids on skateboards (It used to be the Rogers logo). What are the specs on the splash image? and where do each of these splash screens come up?
5- How do I know if my phone is actually rooted? I type 'adb root' and I get 'adb is already running as root' ... is that enough?
6- if I type 'adb shell' and then 'su' the command is not found ... are these *nix commands only available in custom roms?
Click to expand...
Click to collapse
1- You can't run any OS other than android. We have different builds/ROMs, some based on the google source code, others are HTC builds.
Voice dial is an app issue, maybe there's one on the market
Some ROMs have multi-touch in the browser, HTC Hero builds also have it in the gallery app.
No idea about the time stamp issue :-S
There's several terminal emulators in the market.
3- I believe Rogers Dreams use a different radio image, don't flash anything without some confirmation that it's for the rogers dream.
4- Splash images (you're flashing via fastboot, right?) need to be converted to a raw format, not .png's
5- Grab a terminal emulator from the market, type 'su' and if it works the $ will turn to a #
Thanks Adrian.
@imfloflo: Next time, if you have nothing useful to say, don't say anything at all.
@brian: I meant what is the best ROM out there. I'm quite familiar with the definition of OS and am a software engineer, I thought it would be clear enough that I'm not trying to Install Windows XP on my device.
Thank you Adrian for actually ANSWERING questions.
I've looked at the source for the voice dial app and it doesn't seem to be too much work to fix it (in fact the code to just execute the action if only one match is found is already there, but commented out!!), but I haven't been able to flash my build onto the device ... I can't get past the boot splash.
About the radio, yes I've heard that too and that's why I've been so reluctant to flash anything out in the forums on the device ... they all seem to stress that you need the specific radio image.
So the splash images have to be raw, I can do that, what about bit depth? 8 bit per color? is that RGB or RGBA?
su says permission denied ... so I've probably missed some of steps in the rooting instructions
Thanks again for the answers
brian_v3ntura said:
ANDROID is the BEST OS for ROGERS HTC DREAM. actually its the only one. an OS is sumthign like android,windows mobile,webOS,symbian,etc.
just letting u know what the definition of OS is. or more like examples
Click to expand...
Click to collapse
You beat me to the punchline.
copolii said:
@imfloflo: Next time, if you have nothing useful to say, don't say anything at all.
@brian: I meant what is the best ROM out there. I'm quite familiar with the definition of OS and am a software engineer, I thought it would be clear enough that I'm not trying to Install Windows XP on my device.
Thank you Adrian for actually ANSWERING questions.
I've looked at the source for the voice dial app and it doesn't seem to be too much work to fix it (in fact the code to just execute the action if only one match is found is already there, but commented out!!), but I haven't been able to flash my build onto the device ... I can't get past the boot splash.
About the radio, yes I've heard that too and that's why I've been so reluctant to flash anything out in the forums on the device ... they all seem to stress that you need the specific radio image.
So the splash images have to be raw, I can do that, what about bit depth? 8 bit per color? is that RGB or RGBA?
su says permission denied ... so I've probably missed some of steps in the rooting instructions
Thanks again for the answers
Click to expand...
Click to collapse
Damn, I guess you don't have root, not really sure what to suggest as I'm not familiar with the rogers rooting process. Just start again I guess?
Here's a how-to for the splash images. I've never done it, for the simple reason that if ever I brick my phone I can send it back to HTC and claim an OTA update bricked it. They're hardly going to believe me if my splash image says "I CAN HAZ ROOT, LOLZ" ;-)
I just realized I forgot something pretty important regarding rogers dream, I don't think you can flash ROMs at the moment. You can get root, and there are themes floating about, but I don't think anyone's managed to successfully flash a new ROM. Sorry if I got your hopes up back there.
AdrianK said:
Just start again I guess?
...
Sorry if I got your hopes up back there.
Click to expand...
Click to collapse
Yeah, I'll give the rooting another shot.
I almost knew it may be impossible (or simply too much of a hassle to do), but I'll call them and ask how to install my own custom flashes on it ... it's open source after all ... They should either not carry an open source product or if they do, do it the 'open source' way
Cheers
you can flash ROM's very easily...im not a technical expert so i cant really help you that much...but check dream android development...it has all the android ROM's...you have to reroot and theres stickys that should help a lot with some of your questions atleast...
Noobyflasher said:
you can flash ROM's very easily...im not a technical expert so i cant really help you that much...but check dream android development...it has all the android ROM's...you have to reroot and theres stickys that should help a lot with some of your questions atleast...
Click to expand...
Click to collapse
It's not the actual flashing ... I've read (as Adrian also confirmed above) that you can only root a Roger's Android for now.
I've already built the source and even flashed it to the device, but it just sat on the boot splash screen
Copolii, when you say, "call them", are you talking about Rogers? There's no way they're going to help you. Rooting voids the warranty. Currently there are a couple of threads floating about where people are trying to talk to Rogers and I believe get the source for for the Rogers branded Android OS, or something else which Rogers states is open source but has never actually released the code. They haven't succeeded yet due to Rogers claiming it's HTC's problem and what-not. If you phone them, they'll only tell you that you should have bought an Android Dev Phone 1 (ADP1).
It works
for those who care, I was able to put a few roms on the device and they all seemed to work. In fact as soon as I rebooted I had an incoming call
The ROM that I ended up keeping (at least for now) was Soulife's Rogers Remix v2.9.2 (Aug 5, 2009).
It has only been a few hours, but so far so good
Thanks to those who helped
I called rogers about getting access to their Android source (lol ... I wasn't gonna ask them for rooting help, that'd be too n00bish ... even for moi) ... they've been rather useless.
I noticed HTC had a support number too, they were a lot helpful and the guy even put my name down as a possible beta tester and said he'd get back to me on the Android source request. There's another thread here about it ... it has been going on since July I think and no progress.
copolii said:
@imfloflo: Next time, if you have nothing useful to say, don't say anything at all.
Click to expand...
Click to collapse
dude thats one of the site mods. u better apologize or they might boot ur asss!
help
because as I say my dream will not start I have installed the rc29 and if I am not confusing the phone stays on the screen "t Movile g1" I go to so fastboot or camera and pressing home and hang or crash or someone you know has gone how can I fix this
rafarico77 said:
because as I say my dream will not start I have installed the rc29 and if I am not confusing the phone stays on the screen "t Movile g1" I go to so fastboot or camera and pressing home and hang or crash or someone you know has gone how can I fix this
Click to expand...
Click to collapse
not the way your talking. I can't understand what the heck your trying to say
make it readable if you want help
Sorry I'm not Spanish and English
my problem is that my phone does not turn into the screen cellphone and t does not start and does not in any way at all fastboot
Why hello there.
Thought I'd start with a nice little greeting, if you're reading this hopefully you're looking forward to a nice little task. My G1 is entered paper-weight mode rather than my fast boot setting and it's starting to get rather redundant so this is my last resort. There's the premises of my problem here's a little more detailed one for ya.
So I have a launch G1 with Cyanogen's latest 4.2.4 rom installed with the latest radio & any of the other necessary things flashes, etc. I'm honestly pretty good with these kinds of things through actual knowledge from here for just trial and error but this is something I haven't had to deal with for a LONG time. The infernal pause screen of G1 death. It won't leave the "T-Mobile G1" boot image after being flashed / wiped / all around cleaned up. I'm curious if it may just be the G1 or maybe something else caused a corrupted image for some odd reason.
Prior to getting this to happen, my keyboard wouldn't type correctly. The space bar would result in some random key being pressed and in essence, my phone typing by itself. So either my phone's possessed or.... something far worse. If you happen to know what exactly that is, please help me out! I'm open to suggestions, I've tried other builds and I'm about to just grab some old roms and see if maybe this works. If you have tips or need to know any more information please, just ask.
Thanks! Adderall will make this much easier I just need some ideas
-chatty chatt mic-chat chat.
Boom.
The fact that your keyboard was messing up is ominous. Are fastboot and recovery working ok? Can you post a startup log?
I would flash the HardSPL
the spl monitor the control input (afaik because people w/ qwertz keyboards said flashing special spl's converted them to qwerty)
before you mess with that though, make sure you followed the install directions for 4.2.4
you dont just flash it as an update.zip if your switching to cyan for the first time.
you need to flash the HTC recovery image first, then flash cyan on top of that
no see i've been around here since the beginning of the G1 mods and such I know what to do with everything it just started going wild. I'll try flashing the hardSPL and see what happens but this is just odd. I'm trying one more time to flash a new rom on my phone with a freshly formatted sd card then we'll see what happens
Hi everyone really sorry for opening a new thread for a G1 brick.
My G1 has stuck at the T-Mobile screen and on pressing Camera+Power i cant get into fastboot to restore using the .nbh file.
I am not able to get into recovery using power+home key also.
There has to be a way to get my dream back....
please please please help
JTAG or go for a replacement. I'm guessing it's a DangerSPL brick, right?
Danger SPL
Yes dude....
i have done this so many time.....
this time i forgot to update the radio first and this is stuck....
Someone should have a solution for this....
I read many thread which say use it as a paperweight...
I am not loosing hope....
XDA Member will have some solution.....
Maybe you should try to keep current on developments.
There is NOT A SINGLE REASON to use the deathspl.
As for your "poll"... what do you expect to learn from something like this? Do you realize that any numbers you get will be completely MEANINGLESS?
lbcoder said:
Maybe you should try to keep current on developments.
There is NOT A SINGLE REASON to use the deathspl.
As for your "poll"... what do you expect to learn from something like this? Do you realize that any numbers you get will be completely MEANINGLESS?
Click to expand...
Click to collapse
By adding the poll I am just trying to avoid post which says hey even i have the same problem.
I was upgrading to cm 5 which needs deathspl.
chinmayfun said:
I was upgrading to cm 5 which needs deathspl.
Click to expand...
Click to collapse
Aaaaannnnnd.... it doesn't need it
http://forum.xda-developers.com/showthread.php?t=704560
lbcoder said:
There is NOT A SINGLE REASON to use the deathspl.
Click to expand...
Click to collapse
Sure there is as its one if the few full engineering spls. And I don't think your latest development will ever be quite as user friendly (however some more configuration it will be very close)
The real user friendly fix/patch for 1.33.2005 (those that know what they are doing can decide if any benifit of the spl exists) is an assertion statement in the recovery script to check the radio version is not one of the two common 1.x ones.
(the evil patch is to make the assertion somehow also autoinstall the lattest Rogers e911 patched rom if the user has the 1.x radio. Because atm the rogers rom appears to be very safe from the user messing up the boot chain.. actually we may need to "perfect" the spl a bit more I think it will let us erase hboot)
I am still a newb to the android scene - and do believe I as well made the same mistake - and have bricked my G1.
If eveything I've read is accurate, I can purchase a donor phone - broken screen, or other issues - so long as the mother board is still good.
Swap out the new mother board for the bricked one, and have a working phone again - right ?
Have an opportunity on a donor phone - have no issues pulling phones apart, and putting them back together
But just want to make sure I understand the basics
Thanks in advance for any replies
Motherboard only option ?
Is replacing the motherboard the only option left ?
I am not sure i would be able to do that
Worst day of my life i screwed up big time
Any help is appreciated.
Some tool to recover back to original.
I can understand there is no way to repair as I am not able to get into recovery nor fastboot so cant adb also...
youtube
i checked the below video bt this is kinda a complicated and nt a solution for me
chinmayfun said:
i checked the below video bt this is kinda a complicated and nt a solution for me
Click to expand...
Click to collapse
There is no tool to get it back except by the options listed above. If you are not going to switch the mobos in the G1 then you won't be able to do the other option either. There is no software that can bring your G1 back after a deathspl.
protomanez said:
There is no tool to get it back except by the options listed above. If you are not going to switch the mobos in the G1 then you won't be able to do the other option either. There is no software that can bring your G1 back after a deathspl.
Click to expand...
Click to collapse
Thanks....
i will have to plan out on buying a new android....
had waited for a long time to get tht android phone from a friend in usa....
now there are many android phones available in india.... will have to start saving some money.... cant live without an android....
hey,
i had the same prob.
only thing,
mine bricke in cause of a radio update,
i tried all which was in my head,
and all i can do
but after some nights spending to my phone i found this:
i copied my nand backup to root of sd,
and connected it to pc
first he told me, device not known
so i tried to boot the modified recovery,
and *tada* i was in recovery mode,
plz try and tell me if it fix your problem,
for mine it did
best regards,
psycho
Mine is also due to radio update dude, before flashing spl the radio has to be flashed i and forgot to do that.
Will try out your suggestion, just hoping that it work and my g1 is back to life.
Ne ways appreciate your suggestion.
Please let me know if you were able to get into recovery mode prior to putting the files on the sd card.
And if you could tell me the list of files (if u had nething other then the nand update) which you put on the sd card, i can replicate the exact process.
Thanks,
Chinmay
Hope
Is there any hope to get the G1 back to life from the Death SPL Brick ?
You should read instructions carefully man. Its not that hard. You should always verify that you have a compatible radio before flashing DangerSPL.
There is a method to recover your device and it involves a lot of time and patience. Google "JTAG".
Sent from my HTC Dream using XDA App
"JTAG".
me too, my G1 Bricked (Not able to fastboot). but i wanna know if the JTAG method work 100%.please.
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 )
After looking through the varying questions concerning the same topic and, subsequently, not seeing the right answers - within the right timeframe (e.g. within the past month or so), I decided that a new thread was needed. So here's it is:
A branded G1 (mine, T-mobile, Germany) is what I want to downgrade so that it may be rooted and upgraded with a custom ROM. The problem, I am finding, is not that the instructions aren't correct. Rather, it's that a piece of the instruction set doesn't exist. Namely, the revskills.de website. I mention this because I have tried, repeatedly, to boot with the DREAIMG.nbh in order to downgrade and have consisitently (after numerous downloads from different sites) received the same error - 00028002 (or something like that) while trying to load it. I eventually learned that some phones needed a "goldcard" so I set about trying to do that. Got the CID, reversed it, etc. but the part about going to psas.revskills.de is the killer. The site is down and apparently, no other method of changing the carrier ID exists (or, if it does, the method is too ugly to mention, let alone comprehensible by someone like me, a not-so-good-programmer). Worse yet, all the instructions involving the generation of a goldcard also involve this website and consequently, because of the aforementioned down-status of the site, renders all instructions moot (Grade: D for relying on unreliable sources). So, back to the question: does a method exist outside of what I have mentioned? Where can I find it? Does it have a cost attached to it?
If you've read this far it means that full words and sentences don't confuse you (in light of so-called "l337sp33k") and I applaud you. I will applaud you even more when a well thought out and not-so-glib answer unriddled with blog cliches and platitudes can be found as a reply to this post...
Seriously, if you don't know an answer, a link to check out or someone I can refer to, don't waste your time (or mine) with a the standard "you need to read this and that rules before asking a question" reply. I have trolled through this forum and a few others for the past 2 days looking for the answers to the question of downgrading and finding not the right answers that are specific to this problem (yes, I've read thropugh cyanogenmod wiki, read through the wiki here for dream/g1 phones, gsm programmer's sites, android dedicated sites, etc...ALL of them point to revskills for the goldcard gen (except for one which allows dowloading a perl prog to compile yourself to make the goldcard - I'm not so good with perl yet)
If you need to check the website go here:
psas.revskills.de/?q=goldcard
it's not working for me, whether through proxies in the US, netherlands, britain, frnace, or germany. My only conclusion is that it has been shut down.
Thanks for you attention and I really appreciate some advice from one of you that may be able to shed more light on this.
Incidentally:
SD Card: Hama 2GB Micro SD(formatted fat32)
Droid/HTC G1 phone has been factory reset to:
Firmware: 1.6
Kernel: 2.6.29-00479-g3c7df37 [email protected] #19
Baseband ver.: 62.50S.20.17U_2.22.19.26I
Build No.: DRC 92
are you going on that non exiatent site to download the qmat thing? maybe try looking for it as a torrent file... use bittorrent or something and see if it's out there... i wish i knew how to help more, but i never needed to do anything like that...
stupid question but did you try both dreaimg files? rc29 and rc7?
both img files
Yes, I tried both. The US version gave me the same response as the European one. Tried qmat 5.0.2 and got nowhere with it (i ran out of time before I could figure out everything it could do - apart from simply reversing the cid). The only way to create a gold card seems to be through revskills...kind of a raw deal for the rest of us, if you ask me.
yeahh haha this sucks im not sure what you can do... hopefully someone sees this who can help you. sorry
I am currently trying out the alternate root method from your guide. Something's working...the build version is now CRB43 and I have cupcake (1.5) installed - I think. I shoudl be able to go through the guide in order now, right?
yeah if you have 1.5 than all you need is a custom recovery installed and you have root access... i prefer amonra recovery.. than you can flash radio and spl and go even further by flashing the newer 2825 radio and 0013d hboot
I just have to update my phone account with a data plan (forgot I didnt have one and cant sign in to google without it). Fortunately, it's cheap and takes only a day to update.
OK, so i worked the alt recovery method, but I can't sign in to google. (I used the AMON_RA recovery img.) I can't do anything now. The phone is (for all intents and purposes, bricked. I then tried to do the work around to get the wireless turned on at the touch me screen. It doesn't work. Still no root access. trying to go back to stock rom, no go. Still get the "Not Allow" 00028002 error. Haven't seen the fast boot screen lately. I try the back arrow from the boot loader screen...nothing. Even went so far as to try the HTC site boot unlocker method. HTC Sync installed, android sdk installed, etc. got the drivers in win7 x64 to acknowledge the phone being plugged in...it even recognozed (once) as the HTC Dream/G1, after that never again. This is nuts! It's funny as well as highly annoying. I'm running out of ideas and could use some suggestions...
Thanks
incidentally, the link to "DREAIMG.nbh" in the unrooting section connects to a download of the update.zip file. So, the link is misplaced or something...
good news, the gold card gen sit is back up, however, I can't connect to the phone with adb...I have tried the workaround but I guess the image on this thing is still not rooted. I'm out of ideas what to do, I cannot sign in to google (registration work around) and I can't connect with adb to all the other work to change things. This phone is hosed (and I will absolutely not go to T-mobile (in germany) they're even worse here than in the US...
Here is the link that I found for dreaming.nbh file.
http://www.megaupload.com/?d=NAAS5VBS
See if that works.
So, I am resigning myself to never getting this fixed. I have a rom I cannot access because the data plan on my sim card is for Maxxim, while the rom sets everything up as T-Mobile. Maxxim support will not give out the APN info and, to top it off, the wireless work around does not work because the cupcake dreaimg.nbh and amon_ra recovery image still do not allow root access. I'm lost, got a "working brick" phone, and I'll be damned if I go crawling back to t-mobile whether here in Europe or the US! Thanks for the help anyway...
yeah sorry bout that will fix the link, but its the same one you use to 'downgrade' on the Root method.. just brings you to 1.0, then flash the update.zip to 1.5 or 1.6...
so you cant flash the DREAIMG.nbh file? and you cant do anything via recovery?
but your device works if you had a data plan.. lol wow all i can think of is trying to flash the orange.nbh or get the DREAIMG.nbh to work..
Yeah, tried the orange.nbh as well and I get the same error for every nbh I try:
"00028002 Not Allow". It's really weird that all the nbh do not work...it's almost deliberate. The only root that worked was the alternate root, but wouldn't that have let me flash other roms? Interesting that it didn't.
Good that this G1 is a spare, but I would still like to get it working. I've found a use for it at work but it needs to be rooted. Will post back shortly with results from the DREAIMG.nbh and orange.nbh (if need be).
Incidentally:
Bootloader screen:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
SEP 2 2008
Does this give you any ideas? I can get to the recovery console but it does not necessarily mean I have root (as far as I've seen to this point). I mean, if I were able to register the phone without a data plan (using the wireless connection) I think I would be ok. I did have a point when I was able to connect to the phone via adb (but the phone was registered).
I know I don't have root because I am unable to do the <enter>reboot<enter> thing in the reg bypass method. How did that happen? -I've got no idea...
Another thought, Is there another way to install drivers on my windows machine so that the phone is recognised by adb (even though it's not regitered and I have no way of turning on debugging)? Is there a way to alter the build manifest so that USB debugging is on by default thereby allowing me to connect via windows?
Its painful to read threads like this..
Do you still have your sdcards CID from the OP?
If so using the sdcard you have the CID to make the goldcard on your computer, tben takethe orange nbh rename it to DREAIMG.nbh and place it onthe root of the sdcard.
Then flash the orage nbh and use fastboot to install the 2708+ radio/spl/custom recovery (ra or clockwork)
If you dont have the CID find a device (likely a friends phone) that can read the CID and pick up from there. (notice no adb, and only fastboot after flashing an nbh with an engenering spl)
(I didn'tsay it earlier as the goldcard site was down...)
How to I go about reading the CID on another phone? I am not too familiar with the process. I have a nokia X2. Will that work through a bluetooth connection? (it's my wife's phone and I don't want to try anything with that one until I am absolutely sure.
If you could point me at something I could read on how to do this, I would be exteremely grateful...
Thanks
the site http://psas.revskills.de/?q=goldcard is odwn for me, so I can´t create my gold card.
Any other way to access the site?
I'm following the CM guide for my inspore 4g, but when I searched this forum, this thread came up
So here's my final result:
* Followed steps in the guide for alt root method (nothing else worked but that) - gained root.
* Restarted in order to follow thorugh with the radio upgrade
* No root
* Reflash the ROM
* still no root
* Cannot connect adb to device
* Windows sees it only as USB (even after uninstalling and pointing the hardware to the Android SDK USB Drivers
So I've come into an infinite loop:
* Can't gain root without a goldcard (or some ability to take the NBH apart and modify the kernel - DEFINITELY not my strongest skill...
* Can't get a goldcard without being able to read the CID
* Can't read the CID without connecting with adb
* Can't connect with adb without USB Debugging on
* Can't turn on usb debugging without a) registering phone (no data plan) or b) having root access to type in the commands at reg screen (with SIM Card in) or initial screen (without SIM card)
I've tried every ROM I could find, used the Android Kitchen tool (to modify the ROMs I've found, adding root access), I've read every guide I could get my hands on, as well as trying to extract the nb files from the NBH (in hopes of spotting what I needed to change in order to enable the phone to come on with wireless ON). I have been unsucessful. Is the phone now a paperweight?
I appreciate and respect any suggestions (I've already thought of buying a new phone - so that suggestion is out ;-) ).
Thanks