32b Bricked? - G1 Q&A, Help & Troubleshooting

Hey guys,
i have a big problem,
my htc magic 32b was jerking me,
it lost the signal to network,
so i decided to make a radio update,
i used this:
http://forum.xda-developers.com/showthread.php?t=640535
now, i can't enter fastboot and it doesn't boot (only vodafone screen)
What can i do now??
plz help me

This is the HTC Dream aka G1 forum. You're looking for the HTC Magic forum.
Nonetheless, if you can't boot the phone into recovery or fastboot, then you're pretty much hosed. I'm actually trying to unbrick a G1 right now, I can't even get into fastboot/bootloader to try and reflash the phone. Really sucks for me because I had just flashed a G1 the night before and it was flawless. Same directions, different results

freakingwilly said:
This is the HTC Dream aka G1 forum. You're looking for the HTC Magic forum.
Nonetheless, if you can't boot the phone into recovery or fastboot, then you're pretty much hosed. I'm actually trying to unbrick a G1 right now, I can't even get into fastboot/bootloader to try and reflash the phone. Really sucks for me because I had just flashed a G1 the night before and it was flawless. Same directions, different results
Click to expand...
Click to collapse
Many myTouch users actually live here. 99% of users in the Sapphire section are 32A so any 32B problems will be better answered here.
However, yes you are bricked as freakingwilly said. Just off of a radio is quite funny, though. My only thought is that you got hold of a bad one and flashed it.

r3s-rt said:
Many myTouch users actually live here. 99% of users in the Sapphire section are 32A so any 32B problems will be better answered here.
However, yes you are bricked as freakingwilly said. Just off of a radio is quite funny, though. My only thought is that you got hold of a bad one and flashed it.
Click to expand...
Click to collapse
I didn't know that the Dream forum was home to the Sapphire users.
If I recall correctly, the boot order is RADIO > FASTBOOT > SPL. So if the radio is hosed, there won't be any real way to flash anything else (unless you use a JTAG, but that's a little more advanced than what the OP is looking for).

thx for the quick answers,
is there any possibility to debrick my phone?
i can't realise a brick in case of a radio update!!!
best regards,
depressed psycho

psycho_nr_1 said:
thx for the quick answers,
is there any possibility to debrick my phone?
i can't realise a brick in case of a radio update!!!
best regards,
depressed psycho
Click to expand...
Click to collapse
Well, like I said, it was only if memory is serving me correctly that the boot order is indeed RADIO > FASTBOOT > SPL. The only way you'd be able to fix a SOFT brick is if you were able to boot into fastboot/bootloader (Camera + End Call) or recovery mode (Home + End Call). From recovery, you could just reflash the radio or roll back to a radio that works. If that didn't work, you'd boot into bootloader, reflash the OEM NBH file, and start fresh. You lose all your data, but you don't lose a phone.
Unfortunately, you
There might be one option left... turn on your phone and connect it to your computer. If your computer recognizes the device, then you can use ADB to push a working radio to the phone.

freakingwilly said:
Well, like I said, it was only if memory is serving me correctly that the boot order is indeed RADIO > FASTBOOT > SPL. The only way you'd be able to fix a SOFT brick is if you were able to boot into fastboot/bootloader (Camera + End Call) or recovery mode (Home + End Call). From recovery, you could just reflash the radio or roll back to a radio that works. If that didn't work, you'd boot into bootloader, reflash the OEM NBH file, and start fresh. You lose all your data, but you don't lose a phone.
Unfortunately, you
There might be one option left... turn on your phone and connect it to your computer. If your computer recognizes the device, then you can use ADB to push a working radio to the phone.
Click to expand...
Click to collapse
As for your other comment, Sapphires come in 32b and 32a. Most 32b users dwell here.
As for bolded, some people have had luck issuing a fastboot command and leaving it sitting all night only to find it to be successful in the morning. You'll get a "Waiting for device...." for a loooong time and there's no assurance this will work at all and chances are slim to none.
Of course, you can send it in for warranty or buy another G1 with like a cracked screen or in real rough condition and replace what ever's broke from your old G1.

sounds like i'm realy ****ed up with my phone =(
hmm... i try something, if doesn't work the only way will be a new one i think...
i'm realy pissed off about this radio update, but it is how it is..
Thx for your answers and tips.
best regards
psycho

hey guys something new...
try to boot....
nothing... connect it to the computer...
klicked on "boot modified recovery" and *tada* its in recovery... and this w/o fastboot..
i try to wipe, old radio, wipe, new rom, we'll se if it's fixed afterwards

psycho_nr_1 said:
hey guys something new...
try to boot....
nothing... connect it to the computer...
klicked on "boot modified recovery" and *tada* its in recovery... and this w/o fastboot..
i try to wipe, old radio, wipe, new rom, we'll se if it's fixed afterwards
Click to expand...
Click to collapse
Hi, glad to hear you had success!
Exactly what did you do to achieve this, step-by-step?

startup and boot modified recovery
first computer found not device,
but i saved the nand back up files on root of sd,
booted device, also only vodafone screen,
but now i came in recovery, w/o fastboot.
My only prob. is now,
my sim don't connect to network -.-
this phone is jerking me....
and idk what to do =(
someone know how to fix?!
best regards,
psycho

This actually great news for you. The reason your SIM won't connect to the network is because the radio you flashed to the phone is not designed for your phone, which resulted in the "soft brick" you were experiencing before.
All you have to do is flash the correct radio for your phone through the recovery mode and you should be back in running condition.
Would you mind sharing how you got to the "boot modified recovery?" I am sure this will help people unbrick their devices as well.

i can't find an old radio =( can someone give me a link?
i've posted the way in another thread about a bricked g1
but i tell you again
i've tried all, i found...
but aber a few nights spending to my phone,
i found this:
1. copy your nand backup to root of your SD
2. Start you phone (should only boot, till vodafone screen)
3. Connect phone to computer (message: device not known)
4. Boot modified recovery with Z3kos recovery helper.batch
5. Wipe
6. Flash old Radio (DO NOT WIPE AFTER THIS)
7. Flash Rom

STOP FLASHING RADIOS. You need to FASTBOOT them. Please, if you're going to root, indulge yourself in the knowledge.
http://fwd4.me/Ur5
There is the newest radio. Now fastboot it.

i'm not a rooting noob!
and this is first time, something like this happen to me^^

psycho_nr_1 said:
i'm not a rooting noob!
and this is first time, something like this happen to me^^
Click to expand...
Click to collapse
obviously you are considering it even happened.

r3s-rt said:
STOP FLASHING RADIOS. You need to FASTBOOT them. Please, if you're going to root, indulge yourself in the knowledge.
http://fwd4.me/Ur5
There is the newest radio. Now fastboot it.
Click to expand...
Click to collapse
And if you are going to help, indulge yourself in the OP's post.
psycho_nr_1 said:
*OP shortened*... now, i can't enter fastboot and it doesn't boot (only vodafone screen)...
Click to expand...
Click to collapse
If you read the OP's post, you would have known that the OP cannot get into fastboot. So telling the OP to do something that they cannot do doesn't help.
r3s-rt said:
obviously you are considering it even happened.
Click to expand...
Click to collapse
If you don't have anything nice to say, don't say anything at all.

freakingwilly said:
And if you are going to help, indulge yourself in the OP's post.
If you read the OP's post, you would have known that the OP cannot get into fastboot. So telling the OP to do something that they cannot do doesn't help.
If you don't have anything nice to say, don't say anything at all.
Click to expand...
Click to collapse
and you should RTFT, OP now has a working phone but with no data connectivity. so he can now access fastboot. r3s-rt was telling OP to not flash the radio next time, fastboot it.

jamesd86 said:
and you should RTFT, OP now has a working phone but with no data connectivity. so he can now access fastboot. r3s-rt was telling OP to not flash the radio next time, fastboot it.
Click to expand...
Click to collapse
Wow, I suck. And I REPLIED to OP having a working phone.
*hangs head in shame* Excuse me while I walk in the other direction.

jamesd86 said:
and you should RTFT, OP now has a working phone but with no data connectivity. so he can now access fastboot. r3s-rt was telling OP to not flash the radio next time, fastboot it.
Click to expand...
Click to collapse
...10 char.

Related

Help me unbrick my phone

So i just updated to an SPL for a Hero ROM, and now i'm stuck on the t-mobile G1 screen, i can get to the console, but if someone can walk me through how to mount the SD card using ADB (from the very begining) it would be a great help. This way i can try to update the firmware, or resort back to the original radio/spl/firmware. I need a very easy to understand set of instructions, because every time i have tried to do something with ADB it never goes well.
all you need to do is re-flash your current rom your using no wipe needed.
Whats the command to do that, i've been trying to load the new ROM onto the SD card through the command prompt. and it doesn't seem to want to work.
Bassicly i use the adb push command to try and shove a ROM on to the SD card like this
adb push JAChero2.0r6.zip /sdcard/JACHero2.0r6.zip
and then i change the name to update.zip and it still applies the OLD SPL update.zip file i have in there.
Try removing the old update file first through the adb shell. I have run into a couple instances where it is doing what you are describing. I always found that removing the current file first will resolve it.
adb shell
# rm /sdcard/update.zip
# exit
adb push JAChero2.0r6.zip /sdcard/update.zip
Then try to flash the update through recovery.
Got it fixed, THANKS!
im stuck at g1 screen as well....what did you do to fix this?
Im stuck on G1 boot screen, cannot get into FBOOT or anything!
What can I do??
if none of the button combos work like home+power or camera+power or any others then you can either call tmobile and play dumb or have the sweetest paperweight at the office.
crpercodani said:
if none of the button combos work like home+power or camera+power or any others then you can either call tmobile and play dumb or have the sweetest paperweight at the office.
Click to expand...
Click to collapse
Will it cost me if I contact tmo?
I'll play it dumb, but when the phone ends up at some engineer, and they see what I've flashed on, will they just fix it, or report it to tmo? (as i've broken the t&c's!)
As much as having a paperweight sounds cool, I could really do with a phone!
BTW, thanks for your help!
IanVaughan said:
Will it cost me if I contact tmo?
I'll play it dumb, but when the phone ends up at some engineer, and they see what I've flashed on, will they just fix it, or report it to tmo? (as i've broken the t&c's!)
As much as having a paperweight sounds cool, I could really do with a phone!
BTW, thanks for your help!
Click to expand...
Click to collapse
If the phone won't boot using home + camera then they can't prove it's been rooted (unless they somehow read the nand...) so they should replace it for you without charge.. Same thing could happen if the battery was pulled during an over-the-air update.
they wont bother checking anything, just be sure it is bricked and your good. Most likely they just take it apart and jtag it or something like that. And if you got the phone from tmo and are with them then no its free.
AdrianK said:
If the phone won't boot using home + camera then they can't prove it's been rooted (unless they somehow read the nand...) so they should replace it for you without charge.. Same thing could happen if the battery was pulled during an over-the-air update.
Click to expand...
Click to collapse
crpercodani said:
they wont bother checking anything, just be sure it is bricked and your good. Most likely they just take it apart and jtag it or something like that. And if you got the phone from tmo and are with them then no its free.
Click to expand...
Click to collapse
Yep, it wont boot using any key-combo.
Its reading the NAND/using JTAG which is what I'd do (i work with embedded devices!).
I might say the battery died while the update was happening, gotta act dumb! (which I must be for managing to brick it in anycase, after all, Im a softy-eng!)
And I'll get a new phone! Or reconditioned?
Many thanks ppl!
Well.
If you manage to help this guy (http://twitter.com/r3nrutSite/) and the ppl on this thread (http://forum.xda-developers.com/showthread.php?t=309291) to JTAG the G1, please tell me.
I'm stuck with a bricked G1 here in Brazil.
Currently there is no way of bringin a g1 back to life short of giving it a heart transplant<new board>
see Brick Thread
Tp2 brick eny help??????
plis help
i was unlocking my phone (the HTC Touch Pro 2 <sprint>) and I was using a Diamond unlocker , but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. there's eny way to save it???
SHADE86 said:
plis help
i was unlocking my phone (the HTC Touch Pro 2 <sprint>) and I was using a Diamond unlocker , but during the process there was a connection error and now my phone seems to be bricked. I can't get it to even turn on, get to a bootloader screen, or anything even remotely close.
The one odd thing that it does though, is when I connect it to my computer, it pops up and my computer recognizes there is a device there. In my Device Manager there is an unknown device called: Qualcomm CDMA Technologies MSM. I have tried every combination of two buttons, including holding down the reset button with all of them, but nothing gets me anywhere.
If anyone could help, I would really appreciate it. there's eny way to save it???
Click to expand...
Click to collapse
Theres a app for that!
an app for recovery a htc tp2 brick
Ace42 said:
Theres a app for that!
Click to expand...
Click to collapse
really an app??
please tell me where i can find it
and what steps i must follow,
am desperatedm thank`s
SHADE86 said:
really an app??
please tell me where i can find it
and what steps i must follow,
am desperatedm thank`s
Click to expand...
Click to collapse
http://tinyurl.com/yayoq48
App used: Firefox

After manual update: stuck on G1 screen after update file – help!

Hi guys
So after unsuccessfully trying to root my G1, I changed my mind on the mastter and decided to keep it stock OS. I managed to get back to Android 1.0.
I’ve put a formatted and FAT32 SD card in the phone, with RC8 (UK phone) on it named update.zip (file ext hidden in windows).
I boot up the phone holding home key, ALT L then ALT S. It boots successfully saying things like ‘package verified’ etc until it says ‘install complete’. Then it says ‘press home+back to reboot your phone. When I do that it says ‘writing radio image’ then reboots. When it turns back on it has a picture of a sim card and an arrow or a phone and a box then reboots again. And here lies the problem: it never leaves the G1 screen (the first screen displayed when powering on the device. I’m able to power into recovery mode and fastboot mode, and from fastboot mode I can recover the phone by flashing to 1.0 via DREAIMG.NBH, but I really want to be running 1.6.
Can anyone help?
Many thanks
What phone are you using...a UK G1 or a US G1, as your trying to flash a UK rom...(rc8) have you tried flashing RC29? After flashing to android 1.0 it will prompt you to update your phone to 1.6 after that.
Tranquility__89 said:
Hi guys
So after unsuccessfully trying to root my G1, I changed my mind on the mastter and decided to keep it stock OS. I managed to get back to Android 1.0.
I’ve put a formatted and FAT32 SD card in the phone, with RC8 (UK phone) on it named update.zip (file ext hidden in windows).
I boot up the phone holding home key, ALT L then ALT S. It boots successfully saying things like ‘package verified’ etc until it says ‘install complete’. Then it says ‘press home+back to reboot your phone. When I do that it says ‘writing radio image’ then reboots. When it turns back on it has a picture of a sim card and an arrow or a phone and a box then reboots again. And here lies the problem: it never leaves the G1 screen (the first screen displayed when powering on the device. I’m able to power into recovery mode and fastboot mode, and from fastboot mode I can recover the phone by flashing to 1.0 via DREAIMG.NBH, but I really want to be running 1.6.
Can anyone help?
Many thanks
Click to expand...
Click to collapse
That's because you didn't flash your SPL yet.. I'll edit this post with the link to it. Oh and before I do, which rom are you trying to flash?
protomanez said:
What phone are you using...a UK G1 or a US G1, as your trying to flash a UK rom...(rc8) have you tried flashing RC29? After flashing to android 1.0 it will prompt you to update your phone to 1.6 after that.
Click to expand...
Click to collapse
Thanks for the suggestion protomanez - it's a UK G1.
xAbstract said:
That's because you didn't flash your SPL yet.. I'll edit this post with the link to it. Oh and before I do, which rom are you trying to flash?
Click to expand...
Click to collapse
That sounds promising I'm trying to flash UK 1.5 RC8. So I have to install this SPL first and then install the software? I'm correct in jumping straight from 1.0 to 1.5 right?
Tranquility__89 said:
That sounds promising I'm trying to flash UK 1.5 RC8. So I have to install this SPL first and then install the software? I'm correct in jumping straight from 1.0 to 1.5 right?
Click to expand...
Click to collapse
Do I need to flash this SPL? The bottom one on this page http://code.google.com/p/android-roms/downloads/list?q=label:SPL
it's called G1originalBootloadernocheck.zip or something similar
I wouldn't trust that, but I don't know just hold on. Wait a minute, so you flashed the RC8 rom? Are you sure, how long did you wait at the T-mobile G1 screen for? Try flashing RC8 again and let the phone do it's thing. Wait a max of 10 minutes for the phone to load.
Tranquility__89 said:
That sounds promising I'm trying to flash UK 1.5 RC8. So I have to install this SPL first and then install the software? I'm correct in jumping straight from 1.0 to 1.5 right?
Click to expand...
Click to collapse
I'm hoping that you're rooted at 1.0.. And nono, you flash radio first, then SPL THEN the rom.
xAbstract said:
I'm hoping that you're rooted at 1.0.. And nono, you flash radio first, then SPL THEN the rom.
Click to expand...
Click to collapse
He's trying to go back to stock, not flash a rom :U.
Tranquility__89 said:
That sounds promising I'm trying to flash UK 1.5 RC8. So I have to install this SPL first and then install the software? I'm correct in jumping straight from 1.0 to 1.5 right?
Click to expand...
Click to collapse
... sounds like he wants to flash.
-EDIT-
Why would he want to go back to stock if he flashed 1.0? Isn't that the first thing you do when you root?
After you flash DREAIMG.nbh, give the phone a few days and it will update over the air.
xAbstract said:
... sounds like he wants to flash.
-EDIT-
Why would he want to go back to stock if he flashed 1.0? Isn't that the first thing you do when you root?
Click to expand...
Click to collapse
He said he changed his mind because he tried to root but he failed so he's trying to go back to stock OS.
protomanez said:
He said he changed his mind because he tried to root but he failed so he's trying to go back to stock OS.
Click to expand...
Click to collapse
Oh my bad. My lack of attention span prevented me from reading that but to go back to the stock, do what cloverdale said. Reflash your G1 with the RC8 and WAIT for the update. There's no need to do it manually.
Thanks guys! Yes the root looked like it was about to brick my phone so I abandoned it and was feeling overwhelming relieved to even get normal OS back on my phone. So I should just wait for the over the air update (in the UK) and it will automatically bring it up to 1.6 again? Sorry for the late reply, my internet has only just started working, and itll be off again soon!
Why not do it manually btw guys?
Yeah you can just do what cloverdale said, or you can go to the settings(pick it by pressing menu on the phone) and scoll all the way to the bottom to "about phone" I believe there will be an "upgrade" option but I'm not quite sure . You can do it manually by dling the upgrade off the internet somewhere but it's probably better(on the safe side) to just download it from your phone.
Tranquility__89 said:
Thanks guys! Yes the root looked like it was about to brick my phone so I abandoned it and was feeling overwhelming relieved to even get normal OS back on my phone. So I should just wait for the over the air update (in the UK) and it will automatically bring it up to 1.6 again? Sorry for the late reply, my internet has only just started working, and itll be off again soon!
Why not do it manually btw guys?
Click to expand...
Click to collapse
Yes, just give it some time and it will update to 1.6 (or maybe 2.0/2.1). I would suggest waiting of the OTA update and not doing it manually simply because I what I read about your reactions to rooting. I am not trying to be mean when I say this, but the stress it seemed to cause from starting the rooting process may be recreated through a manual flash. Take life easy, relax, and it will update very soon.
OK, no offence taken. I didnt know 2.0 was out for the G1 yet..
I think my rooting went wrong because I didnt flash a radio image or SPL prior to the software - I tried to complete it with limited net access and therefore information, and a non working phone and non working internet is too much of a hinderance as i need these things every day.
I mainly wanted to root it to make the higher end 3d games run smoother via overclocking and use it as a wifi point so i could access the net properly again whilst BT stop ****ing around.

Serious problem. Need help urgently!

My friend flash his rogers g1 to android 1.0 with 1.22 radio and spl .95 something or the other thinking it would give him access to paid apps. in trying to get back to donut 1.5, he flashed cm 1.4 recovery then flashed update zip via recovery console using cyan wiki info:
http://wiki.cyanogenmod.com/index.p...ogers_Dream_EBI1_to_CyanogenMod#Prerequisites.
Now phone only boots to t-mobile image. no recovery or fastboot. Can somebody please help or is phone bricked?
If no recovery or fastboot... Most Likely it's bricked
not only is it probably bricked, you posted in the wrong section
jad011 said:
not only is it probably bricked, you posted in the wrong section
Click to expand...
Click to collapse
Well he said it was urgent.
Wrong Section BTW
you have a new paperweight....im so not jealous ha
Ace42 said:
Well he said it was urgent.
Click to expand...
Click to collapse
Lol sucks for you man, gotta read the instructions!
If it's booting to the tmobile screen it sounds like it might be soft bricked, there's a thread here somewhere which might help.
vegaman said:
If it's booting to the tmobile screen it sounds like it might be soft bricked, there's a thread here somewhere which might help.
Click to expand...
Click to collapse
the rogers dream does not have a g1 screen dude... it has a rogers screen.. and there's no such thing as a "rogers g1"
when you turn on the phone, it stays at t-mobile boot screen. and its not my phone. i had a magic, sold it, waiting for nexy . I was trying to help my friend. is it possible threw adb on comp to flash recovery image?
jfive74 said:
when you turn on the phone, it stays at t-mobile boot screen. and its not my phone. i had a magic, sold it, waiting for nexy . I was trying to help my friend. is it possible threw adb on comp to flash recovery image?
Click to expand...
Click to collapse
Won't be able to use adb because you can't get to recovery won't do adb otherwise :/
PS: You can always throw it at the person who's phone it is and run like hell lol

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

need confirmation of bricked g1 or not

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!

Categories

Resources