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
Related
I have a G1 that was given to me stuck on the exclamation point screen.
I've tried various update.zip methods, When i try to update it says it can't read from the recovery. It'll install the update like normal it seems, but then when it reboots, go right back to the exclamation point screen.
It was never rooted. Not sure what version was on it when it bricked
I've searched the forum all day trying to find a thread like this.
Does anyone have any insight into how to fix this?
Thanks
PusherRobot said:
I have a G1 that was given to me stuck on the exclamation point screen.
I've tried various update.zip methods, When i try to update it says it can't read from the recovery. It'll install the update like normal it seems, but then when it reboots, go right back to the exclamation point screen.
It was never rooted. Not sure what version was on it when it bricked
I've searched the forum all day trying to find a thread like this.
Does anyone have any insight into how to fix this?
Thanks
Click to expand...
Click to collapse
Not sure what rom you tried to put on it but I would bet the camera button is stuck.
billquinn1 said:
Not sure what rom you tried to put on it but I would bet the camera button is stuck.
Click to expand...
Click to collapse
Should be the home button in this case. If it was the camera he'd see rainbows, with home it takes you to recovery (the ! screen)
exactly. thanks for the help.
I replaced the buttons and now everything works.
Hey guys its been a while since I've even tried to fix my phone cause everyone was saying its dead. But I've been reading stories of people coming back from the G1 logo. So i could really use your help.
Heres the problem, A while back I dropped my old G1 and had to get a new one. Upon looking for the video I used last time to root my phone, I couldn't find it. I searched high and low but to no avail. I figured any video would work as long as it rooted me. So I started up the video. however once i was "done" with it i noticed nothing had changed. So i figured the video was garbage and found another one and started it up. I know, STUPID. Well when i booted my phone after wiping and flashing. It stayed on the G1 logo. I knew the worst had happened. So now i don't know what to do. There have been one or two occasions that I've gotten it to boot loader. So i know i can get there. but what do i do when I get it?
Also, no, I never got to flashing raido's or anything like that. I thought I wasn't rooted so i didn't move on.
I know it was long but I'm getting all the info out there. Please help, I think its possible, and if it is I want my phone back!!!
What were you installing by the way?
EDIT: Made a mistake, thought you were able to boot into recovery.
He does not get to recovery, but into bootloader mode (cam + power on). This is good, as there is a good chance to recover from that.
Try the first section of this guide:
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
You have to flash the correct dreamimg.nbh via bootloader. You might need a Goldcard to do so, in certain countries, but lets just hope that is not the case (would be more work...)
€: Some more Info on Bricking your device with Radio/SPL updates, so take care: http://forum.xda-developers.com/showthread.php?t=655097
The guide on cyanogens wiki is considered dangerous at the optional update to HardSPL
Hi,
I have a G1 that I upgraded to CM6 half a year ago. I was excited in the beginning but the more it began to lack the more I was thinking of restoring to default Android 1.6.
Then one moment I decided to downgrade.
I followed the Downgrade Guide in CyanogenMod forum:
wiki.cyanogenmod.com/index.php?title=Full_Downgrade_Guide_-_HTC_Dream
But it failed. I followed every step carefully but now it got broken some way.
What it actually does:
When booting up it gives the T-Mobile G1 screen and after few seconds, like 20 or so, the screen goes black and reboots. And that in an infinite loop.
It had the rainbow image on it so I can boot fastboot. But has no recovery I think so can't flash zips the way I know to do so..
CAN ANYONE HELP WITH THIS?
I CAN'T LIVE WITHOUT THAT THING!!!
I hope for some response soon!
Greetings!
Steven
stevenroose said:
Hi,
I have a G1 that I upgraded to CM6 half a year ago. I was excited in the beginning but the more it began to lack the more I was thinking of restoring to default Android 1.6.
Then one moment I decided to downgrade.
I followed the Downgrade Guide in CyanogenMod forum:
wiki.cyanogenmod.com/index.php?title=Full_Downgrade_Guide_-_HTC_Dream
But it failed. I followed every step carefully but now it got broken some way.
What it actually does:
When booting up it gives the T-Mobile G1 screen and after few seconds, like 20 or so, the screen goes black and reboots. And that in an infinite loop.
It had the rainbow image on it so I can boot fastboot. But has no recovery I think so can't flash zips the way I know to do so..
CAN ANYONE HELP WITH THIS?
I CAN'T LIVE WITHOUT THAT THING!!!
I hope for some response soon!
Greetings!
Steven
Click to expand...
Click to collapse
Go here and search like you never searched before
http://theunlockr.com/how-tos/android-how-tos/
I'm not sure if this is right but I think you can try and flash a recovery image from your fastboot then from there maybe you could flash another ROM? I don't know if that is the case but I think it might work. Let us know if it does.
Yes, I heard that as well, but how??
...
I searched the Cyanogen Wiki, Forums but didn't find anything on flashing from fastboot...
Anyone has experience with that or knows where to find usefull information on it?
stevenroose said:
Yes, I heard that as well, but how??
...
I searched the Cyanogen Wiki, Forums but didn't find anything on flashing from fastboot...
Anyone has experience with that or knows where to find usefull information on it?
Click to expand...
Click to collapse
Put the phone into fast boot while you have the recovery image in your sd card. It will read it and should flash it.
This post was brought to you in part by my HD2 using XDApp.
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
ok so i got my hands on my sisters old G1 and it was unrooted and with rc30.
so i was able to downgrade it to rc29, flash it with RA recovery 1.7.0, and i was applying the the spl next. i booted into recovery and flashed the spl, and when i rebooted the g1 i just got suck at the tmobile g1 screen, i left it there for like 10 minutes thinking its gonna do its thing but it was still stuck there.
i pulled the battery out and pressed home and the power button, and it still didnt wanna go into recovery. so i pulled the battery again. so pressed and held the camera button and power button and it booted into the g1 screen instead!
so at this point i think i bricked it since im just stuck at the g1 screen and cant do nothing from there and i wanted a 2nd opinion to confirm it, or for a possible solution.
im thinking i messed up with the spl, but the one i have DL is the same one i used with my old G1 and its still kicking some (this one has a problem with the flex ribbon cable i believe, but completely usable.)
Im pretty sure when a phone is bricked, you cant even boot your phone, so im pretty sure ur phone is not bricked.
sorry, idk how to fix this, but im sure someone does.
You have to flash a rom, of coursebit would get stuck at g1 screen bcuz it had no direction(no rom)
Sent from my HTC HD2
the situation is you can get into hboot but not recovery nor system，right?
you could flash radio/spl via fastboot ,then flash recovery, rom at last.
read this thread:http://forum.xda-developers.com/showthread.php?t=532719,try to fix it
edward0119 said:
the situation is you can get into hboot but not recovery nor system，right?
you could flash radio/spl via fastboot ,then flash recovery, rom at last.
read this thread:http://forum.xda-developers.com/showthread.php?t=532719,try to fix it
Click to expand...
Click to collapse
no i cant access recovery, or hboot.
when i hooked it up to the computer hoping that it might recognize it, nothing happened either when i tried to boot into hboot, or recovery.
so ive been doin some more digging into the internet and yep i did end up bricking it.
looks like im gonna perform some phone operation between the two g1s to have a fully working one.
so pressed and held the camera button and power button and it booted into the g1 screen instead!
you said this last day,it doesn't work now?
edward0119 said:
you said this last day,it doesn't work now?
Click to expand...
Click to collapse
no it doesnt.
i have no access to hboot, or recovery. and it doesnt get recognized by my computer if i try to have it hooked up with the usb, so i cant even use adb or nothing.
so like i said, i could pretty much confirm myself that i bricked it. so right now im like phoneless because my original g1 has an issue with it not showing nothing if the keyboard is CLOSED (yes closed, not open! lol) and it ended up closing on me when i tossed it in my bed (doh!)
damm that sucks man.. sorry for your loss lol
ldrifta said:
damm that sucks man.. sorry for your loss lol
Click to expand...
Click to collapse
haha its alright, only option right now is phone operation with the two g1s i have, but i need to buy a torx screwdriver for it since the one i got is the wrong size.
but its not such a bad thing because ive been hearing that i might end up getting a new HTC phone as a graduation present. so heres to hoping thats true! lol
I guess it is bricked,maybe it can be fixed by a serviceman
Well seeing it's screwed lol try out JTAG used it before to unbrick a phone once ^^ that should be a solution for you
xillius200 said:
Well seeing it's screwed lol try out JTAG used it before to unbrick a phone once ^^ that should be a solution for you
Click to expand...
Click to collapse
yeah i was looking into that, but idk it seemed wierd for me.
but last night i opened up the g1s and replaced the motherboards from eachother. and now i got a working g1!