Very unique problem regarding HTC Dream - G1 Q&A, Help & Troubleshooting

So I purchased an HTC Dream from a friend and learned all about the wonders of rooting, and found what i thought was going to be a simple step by step guide to upgrade my phone to android 2.1, and was encouraged to use it after reading all the positive comments. I can't post the link to it as I'm a new user, but you can find it by entering "guide on how to root your htc dream to 2.1" into google, the article is on adroidheadlines.com...
I followed it step by step until I got to step 20. After entering:
adb reboot bootloader
i got "error: closed." Being stupid, I looked around on the internet and came across a page that said putting a file called "DREAIMG.nbh" onto the root of my sd card would fix all my problems. Unfortunately for me I did, and then used fastboot which i (think) flashed that rom (i think that's the right lingo, anyway) To my surprise, I turned on my phone to see "T-Mobile G1" on my screen as opposed to the regular "ROGERS" logo. My phone won't move past that screen and won't even boot into recovery or fastboot. I have this gut feeling i've bricked the damn thing and am looking for someone to tell me it isn't so.
Any help at all would be appreciated, and i can't seem to find anyone else on the internet stupid enough to have made the same mistake, which is never, ever a good sign.

Related

Rogers Dream: Bad radio flashed, bricked?

Bought a new in box white Rogers HTC Dream, from someone who had an extra. Having owned a Dash, TyTN and Diamond before, I knew I wanted to flash a custom ROM, but was not familiar with Android.
I searched Google and came across this: http://www.maximumpc.com/article/howtos/howto_hack_your_android_g1_phone?page=0,0
This turned out to be a really bad guide for me. I found out Rogers phones require special attention AFTER I bricked my phone, and now I'm stuck on the Rogers logo with no access to Fastboot or Recovery Mode. In the linked guide, I flashed the recovery image and booted into Recovery Mode. I then selected the update.zip radio file I downloaded and flashed it, finishing the process with Home+Back to reboot my device, winding up where I am now. Is there any hope for me, since it's just a radio and not an SPL? If not, do you think rogers might do something? I still have the retail box and everything, it just wasn't purchased on my account.
Thanks in advance for any help!
eeesh...Flashing the wrong radio is NEVER good...There might...might be a chance to fix. I'd search the forums for the word "Brick" and see what you can find there is a lot of threads on the subject. I recall reading something about a warranty of sorts offered by HTC, you could look into that as well.
you can TRY this, but im not sure if it will work (like 1% chance maybe, but this guy also had rogers)
http://forum.xda-developers.com/showthread.php?t=568938
if that doesnt work, then idk how to help you.... rogers have a different radio than the regular g1..i think if you flashed 26I, you maybe ok.. but then again idk
please post your results here back
PS: thats the same article that pissed cyanogen off lol
Thanks for the link, I'd actually already found and tried that myself. I guess you can put that thread to rest now, as I am in the exact same situation. His described steps, including any and all variations I could think of, did nothing for my poor Dream. I'd have to say the OP in that thread did indeed have only a semi-brick with some other extenuating circumstances.
Anyways, I got in contact with the one who sold me the phone and we successfully switched the ownership and IMEI over to my Rogers account, so now the phone is registered to me and I have full warranty. As the phone is older than 30 days old a factory refurbished Dream is in the mail and should arrive sometime next week with a return package for the recently deceased.
This time I'm going to make sure to root/flash the phone properly, with this guide: http://forum.xda-developers.com/showthread.php?p=4280573#post4280573 (or the linked guide depending on SPL version...)
Once that's done, do I need a specific ROM too? I've read about 3G problems on the Rogers network with some ROM's...
Thanks for your help!

Stuck on G1 Logo.

Alright here's what happened. I went to root my new G1, I started to follow the steps from the Unlockr but stopped halfway through cause i thought i was going in circles I had finished at "rooted" my phone when i looked in the "about phone" i thought for sure that i hadn't. So i went and did Androids world but when i did the first step my phone got stuck. I thought it was bricked but doing some reading think its soft bricked. But i don't know what to do, i cant get to the rainbow screen or the Home+Power screen only the G1 logo. What do i do?
did you flash the the spl and radio, and flash the right one first ?
jad011 said:
did you flash the the spl and radio, and flash the right one first ?
Click to expand...
Click to collapse
I actually never got to that I don't think i ever officially rooted my phone.
Place your phone on a stack of papers and get a new one
Mjolnir106 said:
Alright here's what happened. I went to root my new G1, I started to follow the steps from the Unlockr but stopped halfway through cause i thought i was going in circles I had finished at "rooted" my phone when i looked in the "about phone" i thought for sure that i hadn't. So i went and did Androids world but when i did the first step my phone got stuck. I thought it was bricked but doing some reading think its soft bricked. But i don't know what to do, i cant get to the rainbow screen or the Home+Power screen only the G1 logo. What do i do?
Click to expand...
Click to collapse
I'm going to be real lazy and ask you to post links to the guides you used
I would google them myself , but busy and seeing as you have them in your internet history...
when is an url not an url?
when http is hteeteep
I will then have a look and see just what damage you may have done and if it can be undone

[Q] N1 recovery problem

Hello folks
I'm kinda new in this forum, but i'm always told that i have a great potential
I want to be one of the most important android developpers (apps and ROMs, etc)
enough with the introduction
I have a Nexus One, and I've rooted it following the unlockr site
but after the last step (which i think is the devil here) i started to get a pink unlock icon (not a blue one), and after that, whenever i try to access recovery (after holding the power and volume down buttons) i get the nexus x logo with the unlock icon at the bottom for a few seconds, then I get our little green guy (android) with an exclamation mark, and that's it. Nothing happens next, i have to pull out the battery to restart. it only works when i plug my N1 to the computer an run the fastboot-windows.exe boot recovery-RA-nexus-v1.7.0.1.img (i got this from other site)
so what's the problem?
i really want it to act normally!
oh! one other thing
there's an app called universal androot from here Android Applications | TheUnlockr
but it won't work
when i root it says failed!
when i unroot it says that i have to root my phone first (my phone is already rooted!!!!)
any idea what is happening in my N1's mind?
There is no "blue unlock icon". The text on bootloader screen is always pink.
You didn't flash your recovery correctly.
It might be also that you didn't root your phone correctly - you just unlocked the bootloader.
If you want to be a developer, you need to learn to read a lot, so here's a good exercise for starters - there's a Wiki on this site, for Nexus. Find it, find the relevant guides and procedures, do whatever you need to get your phone running a custom ROM of your choice. Also, try to read some more to understand, why does Universal Androot fail, the reason is (most probably) found in the Wiki also.
hmmmmmm..... OK
no problem
i'll go to this wiki and hit the rod
If I had some any problems i'll let u know OK

Bricked? Im not sure of this situation...

So here's the deal.
it's a long story, but i happened in a short time.
I was unlocking my bootloader and stuff on my nexus one on my mac. using the boot loader.
I used the superboot to unlock it.
and so i succeed in that.
i didn't bother with the install-superboot-mac.sh thing.
i didn't know that by then.
so i went on to search about the cyanogenmod 7, and i can't get the radio refreshed. i read the article in the cm forum.
so, i saw this post somewhere,(...read hundreds of posts now)
that tells me to use the rom manager thing.
so i downloaded it, and i tells me that my phone is not rooted!
so i was wondering how this happened.
i searched online, and i found this post telling me to use that install.bat(which is for windows, mac is the one i mentioned above) thing after i unlock the bootloader.
i was a bit scared.
but i went on to the fast boot manu and i connect my computer,
i put the directory in, and then i threw the install-superboot-mac.sh thing in my phone, successful, so i rebooted my phone.
And after the first not-ANIMATED start up screen, which is the staying-X and the unlocked symbol at the bottom, the screen goes black.
i was not sure what happened. so i pullout the battery and booted it again.
same thing.
it was not until the third time i opened it and waited for it, i realized that it was my screen that's not working!
After the stable X, the system goes to the animated one, but my screen is blacked out, so i can't see.
The bottoms on the phone are still working , yet i can't see a thing!
I can still open the fastboot/bootloader screen, but after that, nothing!
the recovery don't work, it's just an android with the sign.
I'm very worried about this situation.
please reply to me!!
i really need help, since i know nothing about this.
I just thought that 2.3's cool and now i got this....
here's some info that might help,
i have the korean version of the phone, it was cheaper and stuff.
didn't notice a different except that there's no 3g?
i don't really know what's the deal with it.
but it seems to be special or something.
The phone is unlocked, but my computer fails to find it using the adb devices.
im not sure if my phone is usb debbuging.
probably yes.
Everytime i try to load the recovery, it tells me to wait for device.
I really need help!!
OK... so you might have messed up your firmware... no worries... get a custom recovery (like AmonRA recovery)... flash it using fastboot... pop in a custom ROM like CM... flash and reboot...
the thing is i can't load the recovery or the mods. so here's the problem
Do as Craig said.
Put phone into the bootloader screen. White screen with skateboarding androids.
Do your thing with fastboot.
Reboot directly into the freshly flashed recovery and install a ROM.
Read the wiki.
Sent from my Nexus One using XDA App
Read my signature, find a proper guide in Wiki ("Unroot / restore"), execute.
Next time, before you're trying anything, either find a good guide on the internet or try understanding what things actually do before you attempt them.
I've read the wiki, but is my phone compatible with the rom?
my phone's korean version..
im not sure if i can.
and i certainly can't afford another adversity.
reclusivenigma said:
I've read the wiki, but is my phone compatible with the rom?
my phone's korean version..
im not sure if i can.
and i certainly can't afford another adversity.
Click to expand...
Click to collapse
It will work just fine, your phone isn't bricked and will be working fine in no time if you follow the advice in the posts above.
Edit: Am I the only one who wants the word 'Bricked' explicitly defined for the xda forums?
and also, since my screen is out, im not sure of weather my back up data thing is on or not, and usb debugging also
i've tried the ROMs, but the three i tried don't work.
downloading more, but i doubt if there's difference.
the device doesn't tell me to install the update, instead it just goes back to the bootloader screen
i've tried the ROMs, but the three i tried don't work.
downloading more, but i doubt if there's difference.
the device doesn't tell me to install the update, instead it just goes back to the bootloader
...
K, they don't really work, after checking the rom, my phone just goes back to the screen that showed up when i pressed power and volumn down
Why do people insist on receiving their instructions on a golden spoon?
Do you think you're the first one ever that got his phone corrupted? Maybe the second?
Go to Wiki, download FRG33, proceed with instructions for PASSIMG method. PUT ATTENTION THAT YOU'RE NAMING THE FILE RIGHT!
These instructions have been given in 800000000 threads by now. Look for the thread about moving from Vodafone OS version to stock Google OS. Search the forum with the words "restore stock".
What exactly are you doing?
You have a few pieces of advice that will work, but you're not really giving any details about what you are actually trying...?
Here's the link to follow Jack's advice:
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_%26_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my NookColor using Tapatalk
just if you want to know,
i've downloaded the frg33
and i HAVE NAMED it CORRECTLY!
YET, IT doesn'T WORK
im not a retard!
after the 2 min period of searching, which is step 7, my phone goes back to the same screen
CID incorrect!
Update Fail!
Do you want to reboot device?
<VOL UP> Yes
<VOL DOWN> No
this shows up a couple of times also
Why ask for help if you're not going to do what people tell you?
With a unlocked bootloadet flash a custom recovery.
Reboot DIRECTLY into that.
Wipe and flash any rom you want.
If you don't know how to do any of the above search or read the wiki.
Sent from my Nexus One using XDA App
As albundy2010 suggested - if you have the bootloader unlocked (I didn't notice that part in the OP), just follow the guide for unlocked bootloader - fastboot flash all the partitions on the device manually. The guide is in the same place, but a different one - this time use "for unlocked bootloader".
tHANKS man!
I was such a f-in idiot...
now i can finally boot into the recovery..
I got it.. thanks guys
It's a tough flashing world out there, hey rec
I am glad you got it working

Noob here - screwed up my T-Mobile One M9?

Hi XDA community,
I'm scared out of my mind. Tried rooting for the first time ever, but don't actually know what I'm doing. Using various guides I found in these forums, I:
1. Used HTCdev to unlock the bootloader
2. Used ADB to install TWRP 3.0.2-0
3. Used TWRP to install UPDATE-SuperSU-v2.76.zip
Once that finished, my phone tried booting up (the white HTC logo) but now it has the red development build text at the bottom.... and then it gets into an infinite boot loop.
I don't know how to fix my phone. Please someone here with guidance, please help.
I've got the same identical issue.
I was able to get out of the boot loop by holding volume up and power, and I got back to download mode. From there, since the SU update I tried to install boot looped me (I was following this tutorial), I jumped ahead and just installed cm13 as I was planning to.
This install went fine, but then I ran into the issue of the rom not recognizing my sim card. I've been researching this problem and I guess I need to update my baseband? I tried for hours but I do not know how to accomplish this, and couldn't figure it out for the life of me. This thread on the cyanongenmod forum seemed to be the closest thing to help I could find, but still it didn't help very much.
So at this point now I'm trying to back out and unroot my phone and get everything back to factory settings; it doesn't feel worth it anymore to me since I've just had trouble every step of the way. I've been trying to follow this post to get back to at least a usable factory rom. But I can't even get this one to install because I cannot access my phone through adb while it's in download mode. Furthermore the instructions are just confusing me because I'm not so versed in the nomenclature of these procedures.
Is there anyone that can help me get back to complete stock t-mobile sense? Or if not, help me get my cm13 rom to recognize my sim card so I can at least have my phone working in some capacity? I'd be tremendously grateful of either. I'm really in over my head here and quite scared I won't be able to figure this out.

Categories

Resources