Ok, I havent seen this problem reported and it has really got me lost. I previously had the new SPL, at one point over a month ago my phone had problems and I couldn't get into recovery or anything. At that point I flashed back to RC29 and the HardSPL and then upgraded back to cupcake and updated the SPL. I just realized today that I was still on the HardSPL. Here is the fun part, twice I have flashed the new SPL successfully but when I go into fastboot it still shows the old SPL. Any Ideas? I am on Cyan's 3.9.7 with his 1.4 recovery.
jairomeo said:
Ok, I havent seen this problem reported and it has really got me lost. I previously had the new SPL, at one point over a month ago my phone had problems and I couldn't get into recovery or anything. At that point I flashed back to RC29 and the HardSPL and then upgraded back to cupcake and updated the SPL. I just realized today that I was still on the HardSPL. Here is the fun part, twice I have flashed the new SPL successfully but when I go into fastboot it still shows the old SPL. Any Ideas? I am on Cyan's 3.9.7 with his 1.4 recovery.
Click to expand...
Click to collapse
Reflash the SPL but instead of using the trackball button to reboot, hit Home+Power or whatever it is to reboot using the combo. Don't use the trackball.
jairomeo said:
Ok, I havent seen this problem reported and it has really got me lost. I previously had the new SPL, at one point over a month ago my phone had problems and I couldn't get into recovery or anything. At that point I flashed back to RC29 and the HardSPL and then upgraded back to cupcake and updated the SPL. I just realized today that I was still on the HardSPL. Here is the fun part, twice I have flashed the new SPL successfully but when I go into fastboot it still shows the old SPL. Any Ideas? I am on Cyan's 3.9.7 with his 1.4 recovery.
Click to expand...
Click to collapse
i too noticed this problem when i was trying to flash the new spl. i was typing reboot recovery from the console, but when i held home and power it worked.
Thanks to both of you, Im gonna try he Home+Back reboot. I didn't use the trackball to reboot i used the console. when it wasn't working.
Update: Home and Back worked. Thanks!
Related
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.
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.
I posted this in the "Brick" thread but I have not garnered any attention and IRC has moved too fast to get any reliable help.
Hello,
I've done some searching and I cannot find any definitive answers to my problem.
I was on CM 4.2.9.1 and tried to upgrade to 4.2.10.1 and had a bad flash (stuck at android boot). I noticed there was a new update, 4.2.11.1 the next morning and thought I would wipe completely and update from RC29. I downloaded all the files necessary and used spl to downgrade to RC29 which booted fine. From there I got root and started the upgrade part. I installed the RArecovery 1.5.2 which went fine. I then installed the defanged HTC recovery image and CM 4.2.11.1 then the newest radio and rebooted. That went directly back to the RA recovery after installing the radio. From there I installed the Hard SPL. After that finished and rebooted the phone booted to the Hard SPL or the recovery image.
Thinking I had messed something up I though I could start over and try again. I then booted to the SPL bootloader and flashed the RC29 DREAIMG.NBH to start over.
After that completed the phone will only boot to the SPL bootloader, which is now the original SPL. I have tried to flash the DREAIMG.NBH multiple times with the same result. When holding down Home and Power I get the ! screen.
Is my phone bricked? Or is there an image that I can flash to save it?
Thanks for any help.
David Perlik
[email protected]
Does it boot up into RA recovery? from there you can flash any zip... If you got root and the right radio and SPL. Put the latest Cyan on your SD and boot into recovery and flash away... If you can get it to recovery you are not bricked...
Okay... i reread... may be beyond my limited knowledge...
3rd time... I would pop out your SD and put recovery.img fromhttp://forum.xda-developers.com/showthread.php?t=442480... and make sure HardSPL is on there... when you boot into recovery and get the "!" hit ALT-L to get the menu... then ALT-S to apply the update.zip(HardSPL)... heck just follow the steps from the link above...
GOOD LUCK
No recovery at all. I'm assuming it was flashed back to RC29 specs.
You're not bricked because you can boot into SPL. You still have a recovery image on there, not that it's a good one, it's just a basic HTC recovery. What you do have is a hardware problem with you camera button most likely. See if you can blow some compressed air in there, try tapping it a little bit, it may fix it.
Good luck
I got stuck in a bad situation like this a bit ago...
If nothing else, you should still be able to get the dreaming.nbh on there, upgrade to donut and then reroot.
It's not a problem with the camera button as I can still get to the SPL and flash the DREAIMG.nbh.
The DREAIMG.nbh flashes fine, everything gets an ok, but when I restart the phone it boots directly to the SPL.
Just a quick update:
I've gotten a hold of a different micro sdcard than the one that I was using in hopes that some weird formatting error was happening with my old card. Alas, even with this new and freshly formatted card the DREAIMG.nbh will still not take correctly. All parts report ok while flashing, but my phone still boots directly to the SPL on startup.
Can anyone help?
Im having the same problem, but I can get into recovery, sd only has an fat partition, I made a thread here, can the Mods delete it
http://forum.xda-developers.com/showthread.php?t=619180
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*
I'm helping a friend with a hand-me-down G1 upgrade from 1.6 to CyanogenMod 6.1 using the wiki cyanogen links, which basically told me to downgrade to RC29 / RC7 DREAIMG.nbh file after reformatting the sdcard, then root the phone using telnet, flash Amon_Ra's Recovery using telnet, flash 2.22.23.02 radio using recovery, then install dangerspl, cyanogenmod 6.1 and tiny google apps.
As far as I know, I followed every step. I did get stuck a couple of times while installing DangerSPL. I'd fastboot and hit call+menu+end and instead of rebooting, it would install dreaimg.nbh again (since I used fastboot to flash dreaimg.nbh earlier and still had it on the root of the sdcard) and I would have to start over again and re-root, re-flash Amon_Ra's Recovery and the 2.22.23.02 radio. That happened twice before I decided to take dreaimg.nbh off of the sdcard, since I realized that it had already been flashed onto the phone and would probably work. Once I did that, the call+menu+end during fastboot worked and it restarted, which is what it was supposed to do. Kept trying and trying to hit the home button as quickly as possible to get to recovery, like the instructions said, but it wouldn't work. So I took a chance and booted into recovery using home+power and flashed Danger SPL, which seemed to install well, and Cyanogenmod 6.1 and tiny google apps. All seemed to be going well until rebooting the system. The cyanogenmod splash screen popped up after the g1 screen and just sits there, stuck in a boot loop. I waited a good 10 minutes before I pulled the battery and tried again...same thing. Also wiped the dalvik cache and cache, which i saw on the first page of this thread, to no avail. Can anyone tell me where I went wrong and what I can do to pull out of it and successfully install this rom? Really want to get this back to my friend. Also hoping his contacts are still on his sim card after all this... I flashed dreaimg.nbh, per the first step, and noticed that the contacts didn't come up after this. The data on the phone works and the phone number shows up under about phone but since I haven't gotten any further than that OS I can't tell. No where have I seen in the instructions that I had to pull my sim card before flashing... hope it's all good. Any help with any of this would be greatly appreciated.
As you can tell, I'm new to all this. I own a Samsung Moment and flash ROM's on it all the time but that process is much simpler than this one. Have never dealt with a boot loop so I'm a little unsure of what to do.
ejatx said:
I'm helping a friend with a hand-me-down G1 upgrade from 1.6 to CyanogenMod 6.1 using the wiki cyanogen links, which basically told me to downgrade to RC29 / RC7 DREAIMG.nbh file after reformatting the sdcard, then root the phone using telnet, flash Amon_Ra's Recovery using telnet, flash 2.22.23.02 radio using recovery, then install dangerspl, cyanogenmod 6.1 and tiny google apps.
As far as I know, I followed every step. I did get stuck a couple of times while installing DangerSPL. I'd fastboot and hit call+menu+end and instead of rebooting, it would install dreaimg.nbh again (since I used fastboot to flash dreaimg.nbh earlier and still had it on the root of the sdcard) and I would have to start over again and re-root, re-flash Amon_Ra's Recovery and the 2.22.23.02 radio. That happened twice before I decided to take dreaimg.nbh off of the sdcard, since I realized that it had already been flashed onto the phone and would probably work. Once I did that, the call+menu+end during fastboot worked and it restarted, which is what it was supposed to do. Kept trying and trying to hit the home button as quickly as possible to get to recovery, like the instructions said, but it wouldn't work. So I took a chance and booted into recovery using home+power and flashed Danger SPL, which seemed to install well, and Cyanogenmod 6.1 and tiny google apps. All seemed to be going well until rebooting the system. The cyanogenmod splash screen popped up after the g1 screen and just sits there, stuck in a boot loop. I waited a good 10 minutes before I pulled the battery and tried again...same thing. Also wiped the dalvik cache and cache, which i saw on the first page of this thread, to no avail. Can anyone tell me where I went wrong and what I can do to pull out of it and successfully install this rom? Really want to get this back to my friend. Also hoping his contacts are still on his sim card after all this... I flashed dreaimg.nbh, per the first step, and noticed that the contacts didn't come up after this. The data on the phone works and the phone number shows up under about phone but since I haven't gotten any further than that OS I can't tell. No where have I seen in the instructions that I had to pull my sim card before flashing... hope it's all good. Any help with any of this would be greatly appreciated.
As you can tell, I'm new to all this. I own a Samsung Moment and flash ROM's on it all the time but that process is much simpler than this one. Have never dealt with a boot loop so I'm a little unsure of what to do.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=566669 also I just got off that build it's really really slow, try yoshi's gingerbread build.