Database Develop

[SOLVED] Reading for hours, can't find solution - can't install HardSPL

I'm trying to root my G1, and despite the fact that every guide in existence gives different steps, I've managed to confirm I HAVE root now but I need to load the HardSPL so I can load roms to the phone... right.
Except when I do HOME+POWER I get the red/green/blue/white boot loader screen and it says Serial0. I don't get the recovery image. Camera button is not stuck, it works fine.
Anybody know why it won't let me to the recovery screen?
EDIT:
Solution: Turns out recovery image itself was corrupt. Downloaded cyanogen's recovery 1.4 and all was well again.

I'm surprised that after reading for hours you didn't post this in Q&A...
Plug in phone.
Do the power home thing.
Press the back key.
Smack forehead with phone repeatedly.

TheDudeOfLife said:
I'm surprised that after reading for hours you didn't post this in Q&A...
Plug in phone.
Do the power home thing.
Press the back key.
Smack forehead with phone repeatedly.
Click to expand...
Click to collapse
Lol after reading this I couldn't stop laughing

Oh COME ON!!!
Talk about rude - you take the time to reply but you don't contribute... wtf.
I have been at this for FOUR HOURS!!!!!!!!!! I have searched every thread I can find for a solution, I haven't been spending hours looking at exactly how I should avoid offending someone! I gotta say, I never got this kind of rudeness in the Vogue forum, maybe switching to an android device has put me in with a new 'class' of users?
Now as far as the problem - the problem is that HOME+POWER does NOT bring up the recovery screen - THAT is the problem! It brings up the boot loader screen instead.

what step r u on ur using this right http://forum.xda-developers.com/showthread.php?t=442480

Sounds to me like the recovery image was not installed in telnet, without it you would not be able to get into recovery cause there is not one to get into, read your steps on rooting and if if you have to redownload a recovery image, that is what happened to me on my second phone that I rooted

gridlock32404 said:
Sounds to me like the recovery image was not installed in telnet, without it you would not be able to get into recovery cause there is not one to get into, read your steps on rooting and if if you have to redownload a recovery image, that is what happened to me on my second phone that I rooted
Click to expand...
Click to collapse
This is what I'm beginng to think, that the downloaded recovery image has errors or something. I think I'll try redownloading it.

Most likely is, it happens every once in awhile and yes you will get some people on this forum that are quite rude and make fun of you without helping, a lot will also sit there and play mod, but you have to just bare with it. There are a lot of great people that will help you out and all the devs do a really great job so the android platform was a great choice in my opinion

well unfortunately, I downloaded the recovery image again, put the sdcard back in the PC, copied it over again, ran through the root process on the device again.... and still can't get the recovery ROM...
did not expect this much of a problem, I had no issues unlocking my Touch VOGUE (similar process) and I run through going to recovery ROM all day long with people at my job, when all the n00bs forget their gmail passwords.

Solved!
After downloading recovery.img 3 times from the thread here: http://forum.xda-developers.com/showthread.php?t=442480, I finally gave up and downloaded cm-recovery-1.4.img instead, renamed it recovery.img, and now I can access the recovery rom.
yay!
kudos to those that helped out! If you ever get me on the line at t-mobile pda tech support just say "xda developers" and I'll make sure to do my best to help out a bud!

That's great to hear buddy, seems like just a bad image, you will really like the g1 a lot now that it is rooted

lotherius said:
Oh COME ON!!!
Talk about rude - you take the time to reply but you don't contribute... wtf.
I have been at this for FOUR HOURS!!!!!!!!!! I have searched every thread I can find for a solution, I haven't been spending hours looking at exactly how I should avoid offending someone! I gotta say, I never got this kind of rudeness in the Vogue forum, maybe switching to an android device has put me in with a new 'class' of users?
Now as far as the problem - the problem is that HOME+POWER does NOT bring up the recovery screen - THAT is the problem! It brings up the boot loader screen instead.
Click to expand...
Click to collapse
TheDudeOfLife has contributed more to this forum and to making your device run like it does more than you ever will. He is one of the main developers here and has a large following using his ROM, it would be hard for him to contribute more than he already has.
Also, he did give you advice, he advised you to try hitting the back button to see if it would do anything, and if as suspected that it did help, he was only pointing out how dumb you would feel if that was all it took.
Just saying... anyways, congrats on fixing your phone. Next time post in the correct forum (I think its been moved anyways), and could you add [SOLVED] to the title of your thread so other might find it easier if they have the same problem.

Well it was resolved which is the main thing, was just a bad image before flashing which can happen.
TheDudeOfLife has contributed a fair bit to Android as well which his ROMs and whatnot and pressing Back does enable FASTBOOT at that stage.
No main harm done eh? ^_^ As h.nocturna suggested, if you could add a "[SOLVED]" tag to the thread title that would be great.

And you should feel privilaged that the dude came here and tried to help.

supremeteam256 said:
And you should feel privilaged that the dude came here and tried to help.
Click to expand...
Click to collapse
Are you serious? He got mocked by the guy and he should feel privileged because the guy is a ROM developer?!
h.nocturna said:
TheDudeOfLife has contributed more to this forum and to making your device run like it does more than you ever will. He is one of the main developers here and has a large following using his ROM, it would be hard for him to contribute more than he already has.
Click to expand...
Click to collapse
Again, the original poster wasn't bashing 'the dude', just stating the obvious fact that mocking people and not contributing makes him look like an ass.
I know this post was very off topic, I was just so shocked that people bow down to ROM developers like they can do no wrong.

AdrianK said:
Are you serious? He got mocked by the guy and he should feel privileged because the guy is a ROM developer?!
Again, the original poster wasn't bashing 'the dude', just stating the obvious fact that mocking people and not contributing makes him look like an ass.
I know this post was very off topic, I was just so shocked that people bow down to ROM developers like they can do no wrong.
Click to expand...
Click to collapse
I was pointing out that he said that the Dude didn't contribute when indeed he gave him instructions on how to solve his problem (contribution #1) and he also contributes by developing ROMs that help everyone (contribution #2). So next time, read what I said and why I said it instead of just taking the quote out of context. And I don't think he was mocking, again, read why I don't think he was.

Wow, when did everyone become such sensitive nannies?
To be honest I thought I was answering his question with a joke and the answer. I didn't read (reading is fundemental) it and realize his recovery was bad. Glad you guys were able to work this out.

TheDudeOfLife said:
Wow, when did everyone become such sensitive nannies?
To be honest I thought I was answering his question with a joke and the answer. I didn't read (reading is fundemental) it and realize his recovery was bad. Glad you guys were able to work this out.
Click to expand...
Click to collapse
I do appreciate any and all help. I apologize for my own rash reactions. hours of fighting with something that should have been straightforward can do that to you! No idea why the image was bad twice, but once I switched to the other recovery image it was all good. I will add [SOLVED] to the title as suggested.

TheDudeOfLife said:
Wow, when did everyone become such sensitive nannies?
To be honest I thought I was answering his question with a joke and the answer. I didn't read (reading is fundemental) it and realize his recovery was bad. Glad you guys were able to work this out.
Click to expand...
Click to collapse
Thank God. I was beginning to think that I misjudged what you wrote and you didn't mean it as a joke. ~sigh~ reading comprehension ftw!

Sorry but I dont know what else to do

If this is a noob question I'm sorry I've been around these parts for a little while and even though i know how to root the G1 im having a hard time un-rooting it.
OK I just recently traded a buddy of mine's white G1 for my Bronze G1. Its a little ruff around the edges and its a little messed up so i was going to do a warranty claim.
I'm having an issue with trying to get the splash image to reset it self better yet I cant get it to work whatsoever. every time i go and do the whole
run
cmd
cd desktop
cd fastboot
then type "fastboot erase splash2"
It hangs there and just says <waiting for device>
I have done this and have changed my splash image on my bronze g1 a million times with no issues but for some odd reason its like it doesn't recognize this damn phone?
while I'm here I've also had issues after flashing the original spl and placing the DREAIMG.nbh file on the root of my sd card going into the bootloader and it not giving me an option to do the update. it just goes from the "rainbow" screen right back to the "rainbow" screen am i doing something wrong?
I would love to resolve this before my replacement comes in the mail just in case T-mobile feels like giving me $hit about the phone being rooted.
Once again I'm sorry if this maybe a misplaced post or if its a noob question but from what I've seen I'm the only person having these issues

Answers for unrooting are all over, a quick search would've yielded plenty of answers. Questions go in the Q&A section, this section is for devs and testers.
1. replace whatever recovery image you're using with the stock recovery image.
2. use the RC29 DREAIMG.nbh to downgrade the phone and "unroot"
3. pack it up and ship it.
This takes less than 5 minutes to do and T-Mobile gives you plenty of time to ship the broken phone, so need to do it before the new phone arrives.
As an aside, I know four people who've shipped rooted phones back to T-Mobile and never heard a peep.
EDIT: if your phone isn't seeing the .nbh file its probably because your SD card is FAT16, it needs to be FAT32.

I guess you must have only read part of what i wrote.
i know what I'm "supposed" to do I'm writing what my phone is doing while in the process. yes i know its only supposed to take 5 minutes and I have googled and have searched. I'm not being lazy if that's what you implying
you find somone or somewhere where someone has had the same issues and i will apologize. re-read my post then answer again thanx
p.s. and yes my sdcard is and has been formatted to Fat32

LatinSilEighty said:
i know what I'm "supposed" to do
Click to expand...
Click to collapse
Then why did you post this in the development section?

I wanna be I wanna be a moderator
God forbid I placed this in the wrong section.
I figured, maybe a DEVELOPER might know the answer there for I posted it in the DEVELOPMENT section but forgive me father for I have sinned.
Please move my post so the people that obviously don't know the answer can stop coming in here.

Keep insulting people. That will get someone to help you really fast.

Try reinstalling your fastboot drivers. Its probably not recognizing it as its a different phone and has a different ID or something like that

if your not in here to help then why are you in here? people like you are the reason this forum is slowly going down. I'm just asking for a little help.

jsunkist146 said:
Try reinstalling your fastboot drivers. Its probably not recognizing it as its a different phone and has a different ID or something like that
Click to expand...
Click to collapse
thank you very very much i will try that

I wasn't going to help you, but I decided I will since I am not a doosh. I had a very similar problem. I agree that reloading the driver is a good idea. But that wasn't all I had to do. I had to reload the driver with the latest driver from HTC. You can find it here. http://www.htc.com/www/support/android/adp.html

Thank you very much i appreciate the help and yes updating the driver worked perfectly thank you.

LatinSilEighty said:
people like you are the reason this forum is slowly going down.
Click to expand...
Click to collapse
Pot, meet kettle.

Mods feel free to lock this post I found my answers thanks for those of you that helped

Some people are just incredibly ridicoulsy on this thread (sorry bout the spelling but I am a little drunk) people are getting out of hand, in all the reality the search bar rarely helps, you don't ever find **** that you are looking for, so stop being a ass and help out a fellow modder, you never know who is gonna be the best and greartest modder in a few months and you are turning them off, instead of acting like a ass or mod, why don't people starting answering ?s and helping out the noobs before flaming and being rude, people, android has a linux backbone and the support and help is what makes linux the best and most complete os that is out there, welcome everybody that is new because they need to learn and need the help to grow just like everybody else

gridlock32404 said:
Some people are just incredibly ridicoulsy on this thread (sorry bout the spelling but I am a little drunk) people are getting out of hand, in all the reality the search bar rarely helps, you don't ever find **** that you are looking for, so stop being a ass and help out a fellow modder, you never know who is gonna be the best and greartest modder in a few months and you are turning them off, instead of acting like a ass or mod, why don't people starting answering ?s and helping out the noobs before flaming and being rude, people, android has a linux backbone and the support and help is what makes linux the best and most complete os that is out there, welcome everybody that is new because they need to learn and need the help to grow just like everybody else
Click to expand...
Click to collapse
They're not helping because it only encourages others to also post in the development, questions that have nothing to do with developing something. Not because we're assholes. Post in the right section, and people will help.

Solution found to query. Thread closed

Are you a victim of trying new things?

I have had a htc g1 t mobile in 100% working condition for a long period of time. a month ago i rooted the phone ( and i was successful), downgraded the phone to rc29 and tried to put the hero firm ware into my phone. in the process of trying to put the new firm ware i came across some difficulties and now, as what they say "bricked" my phone. immediately as this happened i was able to reach such screens as holding the end key and the camera key landing upon a white page with some options. not having much knowledge i played around with it and now my phone is completely unresponsive. all it will do is start up and stay on the g1 spalsh home screen and only when i take out the battery will it shut of. holding down any certain keys together does not seem to help. i have also given my phone to such companies as SN traders who were unsuccessful in repairing it as they said " they could not identify the problem". perhaps they never really tried. but the point is, i want my phone to work again. do you have any suggestions as to what i may do to bring my phone back to life or perhaps suggest a place to go to that will repair it for a fee. Please help . thanks in advance

arbab01 said:
I have had a htc g1 t mobile in 100% working condition for a long period of time. a month ago i rooted the phone ( and i was successful), downgraded the phone to rc29 and tried to put the hero firm ware into my phone. in the process of trying to put the new firm ware i came across some difficulties and now, as what they say "bricked" my phone. immediately as this happened i was able to reach such screens as holding the end key and the camera key landing upon a white page with some options. not having much knowledge i played around with it and now my phone is completely unresponsive. all it will do is start up and stay on the g1 spalsh home screen and only when i take out the battery will it shut of. holding down any certain keys together does not seem to help. i have also given my phone to such companies as SN traders who were unsuccessful in repairing it as they said " they could not identify the problem". perhaps they never really tried. but the point is, i want my phone to work again. do you have any suggestions as to what i may do to bring my phone back to life or perhaps suggest a place to go to that will repair it for a fee. Please help . thanks in advance
Click to expand...
Click to collapse
wronggggg forum, http://forum.xda-developers.com/forumdisplay.php?f=507 go there

Victim is definitely the wrong term to use in your case. This is exactly why the Devs put a disclaimer up reccomending you don't try this unless you are confident in what you are attempting to do.
At the end of the day, it's your hardware and your choice whether or not you choose to tinker with such things. As a side note, if you were able to get a screen with some options on it, you were probably able to reflash at that point but decided to "mess around" with it instead of coming here for solid info.
Sorry for your loss.

move/lock/delete!!!!
(if you start a new thread in the Q & A section, i'll be glad to assist

hey thanks for the criticism. if you dont know a way to help dont bother posting. and as for the title, its mainly just a tool for attracting people to this thread

wow... because this has to do with development.... LOCK and Block~~~

arbab01, perhaps you misunderstood.
this part of the forum is for development. There is a wonderful Q & A section that experienced g1 users such as myself tend to frequent (yes it is nice to help people out every once and a while).
Also, its part of the rules.

arbab01 said:
hey thanks for the criticism. if you dont know a way to help dont bother posting. and as for the title, its mainly just a tool for attracting people to this thread
Click to expand...
Click to collapse
You're a moron. If you try to "attract" people to this thread with a misleading title, people will simply use their back button when they realize they've been duped. No one in their right mind is going to help you if you try to trick them into it. How stupid are you?
POST IN THE RIGHT SECTION, SERIOUSLY.

Mods: Ban the Noobs who cant use search or google.
To noob: buy a 20 dollar phone or go back to stock cause you are not tech savy enough to own/mess around with a g1. Also look for local colleges that teach a course on "googling"
now for the advice: you bricked your phone. its useless now. you are screwed. see above message.

jirafa said:
wronggggg forum, http://forum.xda-developers.com/forumdisplay.php?f=507 go there
Click to expand...
Click to collapse
google xda wrong forum haha
Results 1 - 9 of about 70,300 for xda wrong forum. (0.32 seconds)
damn noobs

In before lock-down!

no but ya i know ya moms is hahA

Holy crap guys. How rude can you be. Just help the guy out or kindly press the back button. Maybe the topic will die on page 2 but you guys keep bumping it with your mighty "NOOB LOCK BAN" replies. Does it make you feel superior? I bet this guy never posts here again.

i'll guess you have held camera and pressed home to go into the bootloader again?
if you have try and put the DREAIMG.img file on another sdcard and try again. if not, go for the deductible, it's cheaper than a new phone right now

Pinesal said:
Holy crap guys. How rude can you be. Just help the guy out or kindly press the back button. Maybe the topic will die on page 2 but you guys keep bumping it with your mighty "NOOB LOCK BAN" replies. Does it make you feel superior? I bet this guy never posts here again.
Click to expand...
Click to collapse
I actually used to do one or the other -- helping out or pressing back -- but it's getting ridiculous. If some guy is strolling along the grass with a "DO NOT WALK" sign in plain sight, is it really necessary to carry him off or ignore it? No. You yell at him so he gets the hell off himself and doesn't make that mistake again. And hopefully, spectators will see that such behavior will not be tolerated of them, either.
This is supposed to be a development section. Besides, XDA has too many users dragging it down as is. If this guy never posts here again, great, one less problem.

I cant believe this thread is still open..
and i hope he never posts again

If you can't boot in to the bootloader (camera + power) or the recovery menu (home + power) then it's dead. The only way to fix it is to replace the motherboard, but I doubt you'll be able to get a third party to do that for you. If you have a contract with tmo, go in to the store and act dumb, just say that that's what the phone does after you updated it. They should give you a replacement. If not, enjoy your paper weight.
Seriously guys, even if someone posts in the wrong section you might aswell help. But I'm sure it's much more satisfying to throw a hissy-fit >.>

AdrianK said:
If you can't boot in to the bootloader (camera + power) or the recovery menu (home + power) then it's dead. The only way to fix it is to replace the motherboard, but I doubt you'll be able to get a third party to do that for you. If you have a contract with tmo, go in to the store and act dumb, just say that that's what the phone does after you updated it. They should give you a replacement. If not, enjoy your paper weight.
Seriously guys, even if someone posts in the wrong section you might aswell help. But I'm sure it's much more satisfying to throw a hissy-fit >.>
Click to expand...
Click to collapse
thanks for ur sincere reponse. unfortuantly i got this phone from a local person here in ontario who i suppose brought it down from states. Would u know how to replace a mother board or any one who does and how much would it cost?

waaahhhhh...
FOLLOW FORUM RULES AND YOU WONT GET FLAMED. Its easy. All you do when you press the back button, or "just answer their question" is enable people to not do **** on their own and reinstate the fact they dont have to follow the rules. I'm sure we all haven't spent all of our time following the rules to watch someone else get away with completely disregarding them, right?
Besides, if this guy was REALLY trying to fix his phone it wouldnt have taken him a day to get back to anyone...and now its a "mother board" issue? He's wasting our time...

there's a post for a how-to for replacing a motherboard in this forum already....does this guy know where the search button is? He even includes how much you should expect to pay/best way to find one!
i feel bad when people brick their device, but you are a victim of yourself

Help!! Bricked tab !! Worst case yet!!

Here the what i think happened.
I tried to flash a some firmware onto sprint tab that I got working for a day. i then wanted to try a different rom. something went wrong and my tab didnt boot correctly. i couldnt get it into download mode, although ive done it about 100 times prior. Nothing worked but the flash was on. i couldnt turn it off. it would come on when i pluged the device to the comp or the charger.
i figured ill let the battery drain and try again to recover with the no_modem.tar everyone has used before. no luck .
a week past and now ive tried hiem and this time i was able to get a read. i must have tried the same files and same order 20 times out of desperation. to tell you the truth i didnt even notice when it made the connection. i just saw the process complete.
i thought like many other times before im back. however i cant get a sign of life from this device. i tried everything. if i had to put it into words this thread will be 3 pages before anyone can attempt to give me some input.
i want to give up. if it wasnt for this forum and all i have learned here before with my ppc8700 years ago , i would have mailed it in. so please. give me some advice. im too tired to continue. just spent 5 hours and missed dinner holding the 3 buttons and well getting no response from the tab.
please help..excuse my grammar . i didnt even proof read....

And this is relevant to the development section????

Dude how is this a dev project? Use some common sense, go to the question forum.
Sent from my GT-P1000 using XDA App

if it doesn't go into download mode your done. You're going to have to send it in unless youre good with a soldering iron and have some serious JTAG skillz.

kenside34 said:
this thread will be 3 pages before anyone can attempt to give me some input
Click to expand...
Click to collapse
akmzero said:
if it doesn't go into download mode your done. You're going to have to send it in unless youre good with a soldering iron and have some serious JTAG skillz.
Click to expand...
Click to collapse
Thread finished without 3 pages of replies

Sorry guys.took everything I had that night to put my problem in words.appreciate the move...

[Q] Help Please......

I have a NEW direct from Dell, Streak 7. This is my first tablet. This item was a gift from a family member out of state so getting a return is really not an option.
I have set the tablet up with T-Mobile, and everything seemed to go ok. Got gingerbreak and rooted tab. Waiting on Dell to send me unlock code so that I can get the firmware upgraded to latest Honeycomb. However....
This tablet will have forcecloses 10% of the time, on any given program, will shut down for no reason...sometimes reboot, sometimes not. Will freeze after restart. Will freeze and only hard reset will get it back. Will shut off and not be able to turn back on unless you hard reset button and then try to turn it on right.
I have tried to research the issue, but I really can't afford to pay someone for answers. Just trying to see what the deal may be. The item was new, I had to break the seal to get it out of the box and all original items were sealed.
THanks to anyone who can help......or at least direct me on the right path to fixing it......: )

You should've rooted using the Superuser7.zip posted by TheManii

I'm sorry, in my research, I only saw the gingerbreak boasted about. Plus the issue was ongoing before I rooted the tablet
Sorry again...I am still kinda new.....thanks for the reply however

HMMM, well I would suggest you decide what version you want to run (Froyo or Honeycomb) and then I would search the forum for how to restore the 7 back to factory state. It's hard to believe you were having FCs out of the box, sounds more like you are leaving out some details, but no matter, I would suggest restoring back to stock with a clean install... believe me, there are PLENTY of threads. Might I suggest you restore back to stock Froyo, play with that a while and do lots of reading before trying to root or change ROMs. If you don't follow my suggestions you will just be back here with a device you can't use and getting flamed for getting in above your head before you were ready

I have been waiting to answer this post.....Sir or whoever you are....
I do not appreciate you assuming I was not totally honest about the situation I am in with my product. I have no reason to not give all the information so that I can have the best chance of finding a solution to my problem.
Prior to my Dell tablet I have rooted my HD2 and also my MyTouch, so I do kinda know my way around, however when the issues happened right out of the box, it was a total shock. So I figured .... I would go to my friends at XDA....However, I don't feel too good about these posts you have left....or again the assumptions you have made....

jinx0117 said:
I have been waiting to answer this post.....Sir or whoever you are....
I do not appreciate you assuming I was not totally honest about the situation I am in with my product. I have no reason to not give all the information so that I can have the best chance of finding a solution to my problem.
Prior to my Dell tablet I have rooted my HD2 and also my MyTouch, so I do kinda know my way around, however when the issues happened right out of the box, it was a total shock. So I figured .... I would go to my friends at XDA....However, I don't feel too good about these posts you have left....or again the assumptions you have made....
Click to expand...
Click to collapse
Well you don't leave me much to assume sir, anyone that has a brand new product and immediately has issues with it would logically return it immediately, BUT in my experience when someone is in your situation it means they did something to their device and can't get it back to factory conditions to be able to get warranty work done on it....

Again,
First....I am a Mam.....not a SIR. Second. It was a gift.....I have managed to get help for my issues and they have been solved.....I have no control over someone whom assumes. You know what they say about that......Good Day.

get off your high horse

Not on a high horse.....I do not have to put up with rudeness. It is uncouth and uncalled for. I have every right to defend myself. I am sorry if you don't like that.......sorry