Hi Guys,
I've got a big problem with my G1 which I bought on ebay.
It has the original cupcake 1.5 on it, no modifications.
The last few days, I read diffent posts about rooting and custom ROM's and I decided to try it by myself.
So I rooted the phone successfully and wanted to flash the newest Sense ROM on my G1.
I updated the radio first and than the SPL. After flashing the SPL, the phone is now stuck into the T-Mobile screen and won't boot further.
I took this versions of radio an SPL:
http://code.google.com/p/sapphire-port-dream/
I tried a hard reset but it didn't work. My G1 doesn't boot into update mode. No success with home + power on button or camera + power on button.
Please help me, if you got any other ideas.
Thank you very much.
Regards
Ahh, the phone bricking spl...
http://forum.xda-developers.com/showthread.php?t=517593
Toi-Man said:
Hi Guys,
I've got a big problem with my G1 which I bought on ebay.
It has the original cupcake 1.5 on it, no modifications.
The last few days, I read diffent posts about rooting and custom ROM's and I decided to try it by myself.
So I rooted the phone successfully and wanted to flash the newest Sense ROM on my G1.
I updated the radio first and than the SPL. After flashing the SPL, the phone is now stuck into the T-Mobile screen and won't boot further.
I took this versions of radio an SPL:
http://code.google.com/p/sapphire-port-dream/
I tried a hard reset but it didn't work. My G1 doesn't boot into update mode. No success with home + power on button or camera + power on button.
Please help me, if you got any other ideas.
Thank you very much.
Regards
Click to expand...
Click to collapse
What is this Sense ROM? I searched in Android Development (the first 3 pages anyway) for the word Sense and didn't see anything. Can you provide a link to the ROM that you are trying to flash? Did you post your question on there?
Also... do you have a PVT board?
Can you try another ROM to see if that loads? You MUST reflash your ROM after the 1.33.2005 SPL. If the ROM requires you to put a app_s directory on your sdcard do this:
Boot in recovery (ALT-X)
#mount system/sd
#cd system/sd
#rm -r app_s
#reboot recovery
then wipe and reflash your ROM.
Binary100100 said:
What is this Sense ROM? I searched in Android Development (the first 3 pages anyway) for the word Sense and didn't see anything. Can you provide a link to the ROM that you are trying to flash? Did you post your question on there?
Also... do you have a PVT board?
Can you try another ROM to see if that loads? You MUST reflash your ROM after the 1.33.2005 SPL. If the ROM requires you to put a app_s directory on your sdcard do this:
Boot in recovery (ALT-X)
#mount system/sd
#cd system/sd
#rm -r app_s
#reboot recovery
then wipe and reflash your ROM.
Click to expand...
Click to collapse
Sense is referring to the Sense UI aka Rosie, which means basically any full hero build
I tried a hard reset but it didn't work. My G1 doesn't boot into update mode. No success with home + power on button or camera + power on button.
Click to expand...
Click to collapse
how did you try the hard reset? if you can't get into recovery or spl (home+power or cam+power) your phone is bricked and there is nothing you can do about it except call tmobile or htc
B-man007 said:
Sense is referring to the Sense UI aka Rosie, which means basically any full hero build
how did you try the hard reset? if you can't get into recovery or spl (home+power or cam+power) your phone is bricked and there is nothing you can do about it except call tmobile or htc
Click to expand...
Click to collapse
Power+Menu+Talk at the same time then immediately press and hold Home will get you into recovery.
OR
hook up to your pc and adb shell reboot recovery
No matter how many warnings, people just ignore them *sigh* Enjoy your brick.
hook up to your pc and adb shell reboot recovery
Click to expand...
Click to collapse
You can't access adb when the phone is bricked.
Almost every occasion that someone thinks that they've bricked their phones, they haven't. It's just user error.
Things to keep in mind:
If you use the Danger SPL, you NEED the updated drivers to fastboot.
If you can get into either the bootloader or recovery then you're not bricked.
If you can get ANYTHING on adp then you should still be able to save it.
If none of the above are successful then you're s.o.l.
The same thing happens to a lot of people that upgrade their spl. Including myself. If you have a backup from nandroid on your computer and can get into fastboot (with the required drivers) try to flash them back. Nandroid does not recover the spl BUT make sure your backup did not include the old radio because I'm not certain if Nandroid restores the radio. (I need clearification on that part.) If you have the Haykuro (aka danger) spl DO NOT flash any other radio to your phone in ANY circumstance. But if you can't access the bootloader or recovery or get anything with ddms then I guess it doesn't matter (since you would officially have a brick). If you followed the directions to the letter and have a PVT board, this shouldn't have happened though.
Whats interesting is.. my friend had a new G1 yesterday, later that night, Tmobile pushed its update out on it, next you know the G1 was locking up and then just now got stuck forever on the G1 screen, after 10 mins it will load up, but even recovery mode would not load up quick. Touch screen went out too. So not sure if he did something or if the update really is a issue.
Either way Tmobile is sending it back via warrenty. =)
Just kinda concerned tho that a auto push update would cause the phone to screw up. Was stock g1 at that.
Related
I think i bricked my phone by fallowing this tutorial.
http://forum.xda-developers.com/showpost.php?p=3874647&postcount=406
It happened after flashing the spl.
My phone will not go past the white "t-mobile g1" splash screen.
thank you for reading.
Damn, another brick? Did you make sure you had a PVT board and not the DVT-1, DVT-2 boards? It's a known problem with the Special SPL that it pretty much bricks DVT board phones...at least so far. (check by booting with camera+power if possible, board type is shown on the first line of text)
Can you boot using home+power? Are you just stuck at the Splash screen? If so, after about 10 mins the screen will change, giving you an triangle error symbol. At this point push Alt+L. This should give you the recovery utility, where you will have access to wipe (you should prob do one) and reflash a rom.
Of course this is all assuming you have root already.
i dont know if i actually got root i fallowed some tutorial on that too today i can do both of those boots but dont know how to flash anymore updates with my phone stuck like this
aronissleeping said:
i dont know if i actually got root i fallowed some tutorial on that too today i can do both of those boots but dont know how to flash anymore updates with my phone stuck like this
Click to expand...
Click to collapse
Ok, so what you need to do is this:
1. Wait for the error message //remember it sometimes takes 10 mins or so
2. open keyboard, hit Alt+L //this will toggle your phone to the recovery utility
3. If you have root, you may have a recovery utility that says "JF version 1.43", if not you have the stock recovery utility
4. If you have root, you could try to DL pretty much any rom although I might try the Ion rom for its stability and simplicity //there are tons of instructions for flashing a new rom
5. If no root, search in the Dev section of the Dream forum for an OTA ( Over The Air, ie. stock) rom. In particular, search for Dreaimg.nbh, and read the instructions for reflashing it. This will help you gain root.
6. reboot, and enjoy (hopefully)
If none of that works, you can find the "Bricked G1's" thread on the Dev section too. I think your prob out of luck, but it's possible someone has/or is coming close to a fix.
re flashing ill let you know the out come
lol you didnt brick it since u can access the recovery image.
anyways what happened to me yesterday, i flashed latest radio, the latest spl and it wouldnt boot. i flashed a new system image but still no boot (t-mobile screen). I wiped the system (data partition) from recovery boot, and reflashed with a new system image, worked ok... so from what i get, u need to wipe / reflash system, if you upgrade spl...
is by using a card reader on a pc the only way to flash a different img if this happens to you?
my phone is in root and i'm on the same g1 screen. if i take the battery out i can boot to recovery mode but my only options are alt-w and alt-s. i've tried wiping and reflashing with the same spl img and it's not resolving anything.
It's an old problem I never got solved, but simply been putting up with. Now that Cyanogen ROM's can be updated OTA, I'd really like to get my phone back to normal...
Problem started after flashing DangerSPL. I may have flashed old radio while having DangerSPL, however, my phone is not bricked.
Symptoms:
1. Everytime I flash a new ROM, wipe or no wipe, I come back stuck at the T-Mobile G1 boot screen. The only way I've found to get through is to take out battery and boot into ADB (the Camera + Power screen) and "fastboot flash boot boot.img". This almost always work.
2. Nandroid stopped working. Nandroid always errors during the process of backing up, and I'd only have splash1.img and splash2.img in the nandroid folder of my SD card.
3. "Insufficient storage available" with Dude's and Cyanogen's builds. I'm not sure if this one is related to recovery or SPL. This might be caused by past attempts at doing apps2sd (I've done both symlink and unionfs).
I've tried flashing the old HardSPL, but everytime I've done that, I either get stuck at the T-Mobile G1 boot screen, or the phone always boots straight to the SPL screen (3 Android skateboards) w/o me holding the Camera button.
Only way I've been able to make my phone usable is my going back to DangerSPL.
this may suck but have you tried downgrading to rc-29 and rooting again?
btw, this is newport country
david1171 said:
this may suck but have you tried downgrading to rc-29 and rooting again?
btw, this is newport country
Click to expand...
Click to collapse
What should the process order be? Flash rc-29 first then try and revert the SPL?
start at the beginning of this:
http://forum.xda-developers.com/showthread.php?t=442480
david1171 said:
btw, this is newport country
Click to expand...
Click to collapse
Yessir, I agree with you 100%.
Went back to start over the rooting process, and now I'm back at booting straight the SPL screen.
I think the problem starts after I upgrade the radio to the latest. I was booting fine into rc29, but I upgraded the radio and ROM (Cyanogen) at the same time, though I'm leaning towards radio starting the problem, not the ROM.
As a workaround, does anyone know how I can flash the boot.img file to the system w/o using ADB (through recovery console)? This would remove the dependence of a computer, making my problem more acceptable.
I tried to do a "flash_image boot boot.img" but it tells me file not found. I can't see files in my SD card while in recovery console.
Figured it out, but still issues:
after "mount /sdcard" and "flash_image boot /sdcard/boot.img", I get...
"header is the same, not flashing boot"
cigar3tte said:
Figured it out, but still issues:
after "mount /sdcard" and "flash_image boot /sdcard/boot.img", I get...
"header is the same, not flashing boot"
Click to expand...
Click to collapse
What if you renamed boot to something else and tried to flash it? Maybe it won't flash it cause it's the same file name and the system won't flash because of it. Just my .02.
But another thing I was thinking was not to update the radio if your on RC29 since the new radio version wasn't out at the time of RC29 so it may be buggy. Then upgrade to a new rom then flash the new radio. Again just a suggestion.
supremeteam256 said:
What if you renamed boot to something else and tried to flash it? Maybe it won't flash it cause it's the same file name and the system won't flash because of it. Just my .02.
But another thing I was thinking was not to update the radio if your on RC29 since the new radio version wasn't out at the time of RC29 so it may be buggy. Then upgrade to a new rom then flash the new radio. Again just a suggestion.
Click to expand...
Click to collapse
I had it named 4192-boot.img actually, just was lazy to type it out on this thread.
I left the phone at the boot-straight-to-bootloader state and called T-Mobile, a replacement is on the way.
cigar3tte said:
I had it named 4192-boot.img actually, just was lazy to type it out on this thread.
I left the phone at the boot-straight-to-bootloader state and called T-Mobile, a replacement is on the way.
Click to expand...
Click to collapse
awhh how sweet lol. thats one way to get it working.
Okay, so I know what everyone says, "make sure you know what you're doing before you update to Danger SPL." So I read and re-read all the forums and guides about various problems and how to avoid them and how to flash the radio and SPL, THEN after I was comfortable I decided to go for it.
So here is my issue:
I used the two sd card method. After wiping, I flashed the radio to 2.22.19.26I, then rebooted. I wiped again and flashed the SPL to 1.33.2005, took out the SD card and put the other one in. I rebooted from console (using command "reboot recovery"), wiped again, and flashed CM 4.2.10.1 and rebooted. After this final reboot it sticks at the G1 screen and doesn't do anything beyond here. I also tried reflashing everything and formatting the new SD card, then loaded the CM version with RA's USB-MS mode and flashed it. Same effect, stuck on G1 screen.
I still have access to the recovery image as well as fastboot and the screen with the androids on the scateboards (bootloader? I'm niot sure). WIth those things in mind, I don't think I have bricked anything, but of course that doesn't help the fact that I can't use the phone. Any help here would be AWESOME.
ROM: CM-4.2.10.1
recovery image: RA-dream-v1.5.0
Android screen reads:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009, 15:30:43
ALSO I hope a thread with an answer doesnt already exist, I did search for quite a while for a solution but couldn't find one. Thanks again to anyone who can help me out.
Just checking cause you didn't mention this step but before flashing Cyanogen 4.2.10.1 did you flash the HTC ADP image??
Have you tried flashing any other ROM's??
Since you still have recovery && bootloader you're not in a terrible position, you're not bricked, just gotta find out where you're going wrong
HamToast said:
Okay, so I know what everyone says, "make sure you know what you're doing before you update to Danger SPL." So I read and re-read all the forums and guides about various problems and how to avoid them and how to flash the radio and SPL, THEN after I was comfortable I decided to go for it.
So here is my issue:
I used the two sd card method. After wiping, I flashed the radio to 2.22.19.26I, then rebooted. I wiped again and flashed the SPL to 1.33.2005, took out the SD card and put the other one in. I rebooted from console (using command "reboot recovery"), wiped again, and flashed CM 4.2.10.1 and rebooted. After this final reboot it sticks at the G1 screen and doesn't do anything beyond here. I also tried reflashing everything and formatting the new SD card, then loaded the CM version with RA's USB-MS mode and flashed it. Same effect, stuck on G1 screen.
I still have access to the recovery image as well as fastboot and the screen with the androids on the scateboards (bootloader? I'm niot sure). WIth those things in mind, I don't think I have bricked anything, but of course that doesn't help the fact that I can't use the phone. Any help here would be AWESOME.
ROM: CM-4.2.10.1
recovery image: RA-dream-v1.5.0
Android screen reads:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA10000)
CPLD-4
RADIO-2.22.19.26I
Apr 20 2009, 15:30:43
ALSO I hope a thread with an answer doesnt already exist, I did search for quite a while for a solution but couldn't find one. Thanks again to anyone who can help me out.
Click to expand...
Click to collapse
Snab a copy of cyanogen's rom (update.zip) and recovery image (on the forums)
Boot the phone into fastboot (power off, hold camera button and power on)
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
this should insure that you have a proper recovery image.
boot into recovery mode now (you can press the menu button to power off the device from the SPL menu, then hold the HOME button and power on the device)
Code:
adb devices
you may need to do this a couple times until it shows up, once adb reports your device is available
Code:
adb shell mount /sdcard
adb push update.zip /sdcard
then press ALT+S (or select the option from the menu using your wheel)
let the rom flash.
when it's complete, reboot your device (HOME+BACK) or just use the menu again.
it should now boot.. if it takes a bit longer than usual, check if the device is active using:
Code:
adb devices
if your device is listed, see if it's actually doing something using
Code:
adb logcat
if you see a bunch of "E/" followed by text, your phone is erroring out and you may have to report back here for further assistance, if you see a bunch of "apks" and "jars" flying by, your phone is booting it's just checking signatures most likely.
jackslim said:
Just checking cause you didn't mention this step but before flashing Cyanogen 4.2.10.1 did you flash the HTC ADP image??
Have you tried flashing any other ROM's??
Since you still have recovery && bootloader you're not in a terrible position, you're not bricked, just gotta find out where you're going wrong
Click to expand...
Click to collapse
ADP image? I did the steps exactly as I described them. Should I have flashed HTCs ADP image? I guess so, if thats what I did to get CM in the first place. Is that the image that puts all the Google Apps on the phone? Also, if I'm getting CM v4.2.10.1 from the website, and I'm coming from a new radio and SPL, should I have to treat it as though I'm not updating and am coming from a freshly rooted phone?
and @haykuro, I'll try that as soon as I get the time.
Before you flash Cyanogen for the first time you need to flash HTC's ADP image
Check out the Cyanogen's Wiki for a full guide on installing his rom
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
Since you've already gotten as far as getting a custom recovery skip down to the section called "File Download" and continue on, that should get you on the right track
Yes that is the image that get's you all the Google Apps
Yes after installing the 1.33.2005 SPL you have to reinstall a fresh ROM
jackslim said:
Before you flash Cyanogen for the first time you need to flash HTC's ADP image
Check out the Cyanogen's Wiki for a full guide on installing his rom
http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod
Since you've already gotten as far as getting a custom recovery skip down to the section called "File Download" and continue on, that should get you on the right track
Yes that is the image that get's you all the Google Apps
Yes after installing the 1.33.2005 SPL you have to reinstall a fresh ROM
Click to expand...
Click to collapse
Worked like a charm! Kinda makes me feel like an idiot though for not thinking about needing to treat it like a fresh install instead of an update, but I'm glad it worked!
Also, thanks for how quick you helped me out! I was only without my G1 for maybe 5 hours!
I LOVE THIS COMMUNITY!!!!
HamToast said:
Worked like a charm! Kinda makes me feel like an idiot though for not thinking about needing to treat it like a fresh install instead of an update, but I'm glad it worked!
Also, thanks for how quick you helped me out! I was only without my G1 for maybe 5 hours!
I LOVE THIS COMMUNITY!!!!
Click to expand...
Click to collapse
Man! 5 hours is 5 hours too long!
I have a G1 with CyanogenMod 1.4 recovery and the original SPL. It boots into either of those just fine.
When I select to apply any zip, I get the list of possibilities. I have tried wiping many times.
Whenever I choose an option from the recovery or flash something, a message appears that says
Code:
E: Can't read MISC:
(No space left on device)
This occurs even after a wipe. Also, I know that the SD card is not full or corrupted (I generally use it in a different G1).
After I have flashed something and reboot, it simply hangs at the G1 boot screen. I left it for half an hour, and it stayed that way.
Any thoughts?
what are you trying to flash? rom might require danger spl. i don't have a g1, so i'm not positive, but i'm willing to bet on it.
I actually tried flashing the danger SPL. In spite of saying "reboot to complete installation," I know it does not work. if I hold Camera as I turn on, it is still the original SPL.
Next bet?
tal82k said:
I actually tried flashing the danger SPL. In spite of saying "reboot to complete installation," I know it does not work. if I hold Camera as I turn on, it is still the original SPL.
Next bet?
Click to expand...
Click to collapse
1.33.2005 is what the danger spl shows up as, which i believe is your "stock" spl. if you installed it and rebooted without any errors it works. simple and plain.
Does the danger SPL look like the original (RGB color testing)? That is what shows up when I boot with camera pressed.
I was trying to flash either Super D or CyanogenMod, when I follow the instructions for either of them and do the final reboot, it never leaves the G1 logo screen. Yes I know that it is a while for the dalvik-cache to be reworked.
I have flashed roms successfully many times on my other G1.
I am very curious what the error message that I posted earlier means. Thanks for your suggestions!
Sorry for the double post. I have an update. I am pretty sure there is a problem with the NAND chip or something similar. I flashed the Amon_RA recovery, and it worked. I used Amon_RA to wipe, and re-partition the SD card. I then tried flashing the HTC 1.6 image for ADP1. And it worked. It booted into 1.6 with no problem (except that I no longer had root). So I tried to get root again. First I tried the Recovery Flasher app. It said that it failed. So I downloaded the DREAIMG.nbh to get back to RC29. When I ran it, I got
Code:
DREAIMG.nbh - FAIL
Update Terminate
UPDATE FAIL
Any thoughts are appreciated. Thanks!
[RESOLVED]
UPDATE: Apparently that last bit ended with bricking the phone. I took out the SD, put DREAIMG.nbh back on it. Put it back in the phone. Re-flashed from the SPL (holding camera while pressing power). It worked. I then went through with regular rooting, putting Amon_RA on there, with Super D 1.8. Everything smooth. I have no idea what really fixed it, but everything works fine.
tal82k said:
UPDATE: Apparently that last bit ended with bricking the phone.
Click to expand...
Click to collapse
i still lol every time i hear that. phixed my brick.
Yeah.... I wish my brick would go into SPL.
*sorry double post, browser messed up*
New to G1 and have a problem. Bought a G1 and it came with elcaires rom I think it was.
So I downloaded UK RC7, renamed it to Update, and placed it on the root of my card.
Held the home and power button, and tried to install but I'm getting installation aborted each time. I've also tried to wipe, but that gets aborted too.
I rebooted and now its stuck on G1 screen
I hope somebody can help, had the phone an hour and I've mucked it up already.
Thanks in advance
Im also "bricked" at the loading screen, i turn it on and it gets frozen at the tmobile screen. Home+power, camera+power, Alt+L etc dont work.
Is this fixable?
sirlewis said:
Im also "bricked" at the loading screen, i turn it on and it gets frozen at the tmobile screen. Home+power, camera+power, Alt+L etc dont work.
Is this fixable?
Click to expand...
Click to collapse
No. It's Not.
if its not than what should he and i do?
Are you trying to boot into recovery while its in the G1 screen?
yo my name is sammy as well and i swear i just did the same thing with my g1 on eclair. hit me up dude on [email protected]. we can try and help each other out. plus i love the uk man. i never been, but plan too very soon. i love the music and the accents of the women, oh god. hit me up bro!
If you cannot access recovery or bootloader, you have a rather expensive paperweight. If you can, then you have hope.
AroundTheWorld said:
If you cannot access recovery or bootloader, you have a rather expensive paperweight. If you can, then you have hope.
Click to expand...
Click to collapse
It is not so expensive since it be can brought for less than 100>$$
You can fix it by replacing the board with one from a working phone which is not the easiest thing to do.
hey ill take one of those paper weights... I need a new screen...
in the same boat cant get into anything hung up on splash screen
maybe our only option is jtag, ive never bricked before i always put cm 4 then go and install cm5 above that and it worked but this time it told me to go kick rocks and and and it was a customers phone so i gave him mine which is running eclair.
you guys arn't bricked. If you can turn on the phone than your perfectly fine.
You just gotta learn how to use it
G1 hanged at white screen!
Hi all,
I really need a help here. I have a G1 rooted with CM rom ver5. it was working fine since 3 months but suddenly now the phone doesnt boots up, it goes to white screen with 3 droid skaters and highlight on Hboot. It is freezed then and nothing can be done. I removed battery and tried booting by home + power ; camera+power etc etc . nothing happens it goes to that screen only. i have amons recovery and also nand backups in sd card. but the system doesnt let me go any where!! Please help......
attached is the snapshot
Either your back-button hangs, or something messed up your phone completely.
But as long as you have the fastboot mode, it's not bricked. I would suggest you to clean everything, i.e.
Code:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
and then flash recovery again, i.e.
Code:
fastboot flash recovery <recover.img>
After that you can boot into recovery and restore your latest backup.
Please note: fastboot is a command you execute on your PC and you have to connect your phone with USB to your PC.
If after that procedure your phone boots again into hboot, most likely your back-button is defect.
I myself I think got a bricked G1...
I first installed many custom roms and thought that they were slowing my g1 so I wanted to get my g1 back to normal... For that I googled and was gone to the htc official website and ported the radio and rom from there but unfortunately I read it somewhere and it said that the rom is for only developers phone.
Everything first went very good... no error on clockwork recovery but when I reboot my phone, it got stuck on T-mobile G1 logo screen? I now can not even go to recovery mode or in fastboot mode? I need help...
Someone told me to use odin multi loader? but how do I use it or do it?? I need some instructions?
What should I do now? All I want to do right now is to get rid of my g1 by fixing it and selling it at once!!!
before flashing radio, spl, rom...anything...u need to check out the warnings and compatibility-MUST!!!!
there are 32B and 32A devices...both have different stuffs for themselves....which can be bricked if u dont follow the guidelines and try to act in sort of a haste to accomplish something new!!!
for those who can get to the camera+power (hboot) screen, but cant do anything else...u need to format ur sdcard...FAT32...then download dreaimg.nbh file...keep it in the root of ur sdcard...
then boot into the hboot menu, and ur phone should read the dreaimg.nbh file and prompt u to take an action(flash it)....do that and it'll get ur phone to the stock rom thingy....
then later u gotta root ur device again(telnet, great)....then install amon ra's recovery...change radio and what not and play again....
u gotta be patient...that's the only thing!!!
check this too
http://code.google.com/p/android-roms/wiki/Get_Root