G1 Wont boot after SPL Update - G1 General

So, I have just made a couple of changes to my phone. My mistake is that I did it all at the same time. So I dont know what fu***ed it up !
1. I formated the ext2 partition to ext3
2. I added a linux Swap partition (104Mb)
3. I loaded the CN 1.4 Recovery image
3. I installed the SPL 1.33.2005
I have been using JF 1.51 and I was having some issues after a recent corruption so I thought I will try JacHero 1.7 since I was planning on a clean install anyway. So the new SPL was for the Jachero rom.
Anyway, why i think the issue happened while flashing the SPL its because after I flashed the CN Recovery screen came up and it said "Formatting Cache" and it stayed on that screen for like 15 min. and I thought ok, it must be done and the Recovery menu was active so I just scrolled to reboot after which I was never able to boot past T-Mobile G1 screen.
I did eventually update to JacHero 1.7 after a wipe but still didnt seem to work. Still stuck at boot screen.
Any ideas ?
Any help is appreciated !!
Thanks.

If its the spl I know that one if I rem was the tricky one that couldnt be downgraded or so.
http://forum.xda-developers.com/showthread.php?t=517593 is the only thread on top of my head I can link you to. Hopefully it helps.

Sometimes the only way the danger spl will take is if you rename it to update.zip and click on apply sdcard update zip. Try doing that and see, also try a non hero rom and see if it boots, if it does and a hero won't chances are it was the spl

ITS WORKING !!
So I kept on messing around, I went into the SPL settings pressed lots of keys (not much clue wut i was doing) and I tried a couple of restarts and after messing around with everything.......somehow it booted into the new Hero rom (Dont ask me how !) but it was completely screwed up. Meaning, This HTC screen is the only thing I can see. If i turn off the screen and turn it back on, I will see the unlock screen of Hero (which looked really cool) but as soon as I unlock im back to this wierd HTC black screen where nothing happens!!.
Soooo I went back into the recovery mode and tried the nandroid restore option (AGAIN) only this time it went through and completed the recovery ! (It wouldnt do that the last 3 times i tried) and now I back to my JF 1.51
Not really sure if I still want to try Hero anymore

and thanks alot guys for your quick responses......I REALLY Appreciate it.
Thanks again for your help !

It's up to you, cyanogen just came out with donut in his expermental line of roms so now we are gonna be passed cupcake roms soon

Related

recently rooted phone, troubles installing roms

I've been reading these forums for quite some time folowing H's and JF's builds and just seeing what the devolping community has been up to.
I've been wanting to root my g1 for some time but didnt ever make the jump till now. I read through the Helpful Thread / Build Round up started with in the beginning there was root as well as the How-to- Root, Hack, and Flashing your G1/Dream and decided i could do it. i followed all of hte steps with ease. had my phone rooted within 20 minutes the first thing i wanted to do was to get a new rom with cupcake but i also wanted to be sure not to mess it up so i read through nandroid and was a bit confused as to what all was needed so i figured the recovery img that the tutorial gave was fine since everything i had done was no problem. i then went to H's ion thread and saw that i needed a differen spl so i went and read about those and decided with hardspl got that applied no problem. i downloaded the ion rom renamed it to update.zip put it on my card and loaded up recovery mode pressed alt+s to apply it and everything went fine till it hung at the 2nd boot screen. a little disheartened i went into the spl using camera+power and flashed the recovery img. i read around the forums seeing if i did anything wrong and couldnt figure it out so i tried a different rom this time one of Jf's early roms i think it was rc33 i tried to apply that but i got a no signature verication failed at the recovery screen so i tried some others. JF's 1.51 and same problem. i read around some more and thought maybe it was because i didnt do alt+W so i tried that with JF's roms and both of the leaked hero roms (i know hero is extremely unstable but i just wanted to see if something entirely differnt would work.) by this time i go into the spl again and saw that the hard spl wasnt loaded any more (i guess the recovery img changes that) i reloaded the recovery img once more and tried to install a the 2nd Ion rom with H's root apps and still the same problem.
i really try to read and search before posting but after 4 hours of nothing i really just want some help. if someone could help me get a working rom on my phone preferably H's new Ion rom and tell me what im doing wrong i'd be endlessly great full.
Im guessing what happend was you did the switch of releasekeys to testkeys and then later redid the DREAIMG.nbh. If so you need to redo the steps involving testkeys. This is why it gives the no signature verification error.
In fact id suggest redoing the whole root process again. starting with the DREAIMG.nbh.

Problems with builds! (Splash screen hangs)

Hey everyone,
I am writing this because a day of research and playing about with my phone has resulted in nothing.
I recently rooted my G1 european (UK) phone and ended up with the JesusFreke build absolutely no problems...
Today I updated to the latest radio and SPL (again, no problems) and went to put on the Virtudude Roger's mod first and it froze on the splash screen, so I reverted back to original Android, rooted again and went back to JesusFreke's build.
This time I tried Cyanogen mod, which also freezes on the splash screen.
I have tried going to both these builds straight from Android 1.0 or from the JesusFreke build with no success - it just freezes on the splash screen every time.
Anyone have any advice? Maybe theres something I'm doing wrong on the way?! I use recovery mode to format and load the flash images on
So much thanks in advance!
After rooting the phone and then putting it on JesusFreke's build, you were trying to update the radio and SPL with the 2.22.19.26I radio and the 1.33.2005 SPL (Haykuro's "special" SPL - http://forum.xda-developers.com/showthread.php?t=517593)?
You do risk bricking your G1 with this SPL, but if you follow the directions in the thread exactly, you should be fine (do this at your own risk).
Also, make sure to do a wipe (Alt+W) in recovery before you try to apply (Alt+S) the build update.zip.
Nickizzle said:
Hey everyone,
I am writing this because a day of research and playing about with my phone has resulted in nothing.
I recently rooted my G1 european (UK) phone and ended up with the JesusFreke build absolutely no problems...
Today I updated to the latest radio and SPL (again, no problems) and went to put on the Virtudude Roger's mod first and it froze on the splash screen, so I reverted back to original Android, rooted again and went back to JesusFreke's build.
This time I tried Cyanogen mod, which also freezes on the splash screen.
I have tried going to both these builds straight from Android 1.0 or from the JesusFreke build with no success - it just freezes on the splash screen every time.
Anyone have any advice? Maybe theres something I'm doing wrong on the way?! I use recovery mode to format and load the flash images on
So much thanks in advance!
Click to expand...
Click to collapse
What SPL do you have? Are you wiping before you update?
Thanks for the great advice, I was actually following the instructions you provided and have 1.33.2005 SPL.
I just had no idea why it wasn't working, but I have now sorted it...
I put on the recovery utility from JFv1.43, format/flashed the image for Virtudude, restarted and then just left the house for a couple of hours whilst it was on the splash screen....just came back and it had booted in fine.
Now it boots fine every time (does take a few minutes to boot but worth it!)
So, all sorted now - again, so much thanks for the help - I honestly thought it was because I had an EU model or something like that; unfortunately, searching the forums for "EU" or "UK" doesn't bring up much because of the minimum character limit!!

*SOLVED* Not sure if my g1 is bricked or not ???

Hello first of I sincerely apologize if I'm doing anything wrong which I probably am but I am desperate. I may have bricked my g1 my phone is rooted w/ the jf cupcake 1.51. I was attempting to update to the hero rom and I rooted the haykuro spl first I rooted it in sd card renamed update.zip wouldn't work then I remembered all updates I rooted were just renamed update. So I renamed it the ladder and it worked but when I rebooted it kept goin back to the bootloader screen so I went to fast boot and when it loads it says "SD checking...loading...(dreaming.zip) no image nxt line loading...(dreaming.nbh) no image or wrong image" then it repeats the 1st 2 lines and I hit back 2 go 2 fast boot i get <camera step2> HBoot Mode,<send> reset device, <action> restart to HBoot, <menu> Power Down. I read another post where it says it's maybe not booting cause it doesn't have an image to boot so if this is the case how can I put a image on the phone to boot it ? Also when I turn it on normally my pc recognizes it in device manager under computer ACPI Uniprocessor PC...Please help some one and again if I'm breaking any forum rules please forgive me
hmmmm, sorta new to all this but here an idea... load your orignal rom as in the jf 1.51 to your memory card and of course rename it to update. power on using the home and power button then perform a wipe "alt-w" then apply the update "alt-s". let me know if it works. also you will have to apply all this to your memory card from another source other then your g1... please let me know if this works
Um could you explain your problem more clearly and in a more organized fashion? Thanks
Hey guys thanks for the interest but I just fixed my own problem I pretty much have to do the jailbreaking process over but atleast my phone is opperational thanks for the input and I see where sum1 left solution to what I may have used but all is good and I don't have 2 go sumwhere and cry lol
Oh one more quick thing to anyone who has updated to the hero rosie ui...I already had the updated radio on my phone so I started at the hero spl but when I rooted and did the "alt+s" I ran into my problem. did I do sumthin wrong or is there a problem with the spl ?
Thanks
cool, glad your g1 isnt bricked. perhaps a clean wipe is needed first. alt-w??? maybe
yea perhaps not really sure what went wrong but I'll do more homework b4 I try again but it looks like you just have is downgrade again.

Video of me bricking my Magic, what went wrong?

Hey guys,
Few of you in the cyanogenmod irc room the other night might have recalled me totally bricking my t-mobile mytouch by pulling the battery after a reboot... dumbest thing I have ever done. I consider myself a fairly knowledgeable linux geek, but unfortunately I panicked and did the worst possible thing, pulling my batt and completely bricking my phone.
I was installing the 4.1.999 cyanogen mod. Phone was so toast it wouldn't charge. Status led's wouldn't work, it was 100% toast. Fortunately I was able to have it replaced and would like to try again in a day or so.
Here is a video showing exactly what I did, please excuse the length of the video it goes from start to finish, backing up and flashing everything, up until the point where I pulled the battery. I'd love to know what I did wrong, so I can try again!
View the video here on vimeo -> http://vimeo.com/7022688
Ok, here's what you did wrong:
The first steps are good... You've installed the 1.6 update, then applyed the cyanogen rom... After that I've seen that it was installed a new radio... That might have killed your phone...
At least that appears to be the problem... But why a new radio was installed, no idea... (I don't think you did it on purpose)...
the phone you have there is a magic not a dream.For a start that dosnt help!! Other than that i think yiou have put Dream radio on the device, It not being a dream is the problem as when it detects its the wrong radio the phone goes into a safe mode where it wont turn on to save breaking it.
HTC might fix it under warranty as they did me but it WILL come back with perfect spl on.I have flashed the wrong radio on 2 phones yes 2! now i learn from my mistakes Oh and when/if it gets fixed and you bypass perfect spl, You cant put any ROM Other than donut based ones so no hero takes the fun out of flashing
All bricks I've seen are because you guys install new( in most cases wrong radio- from different phone or MotherBoard version) or changing SPL (exception: people with perfect SPL). I'm asking WHY you do this , WHAT FOR ? Putting different rom /rooting etc does NOT require changing anything and is simple as bread and butter, and you CAN'T damage the phone !! Sorry to see this I'm not 100% sure but it looks like you have flashed with wrong radio. As my predecessor said I think only HTC can fix it... To all people DO NOT TOUCH SPL AND RADIO IF YOU JUST WANT TO PUT HERO ROM OR ROOT THE PHONE (exception ppl with perfect SPL)
i accidently flashed the radio for ION on my 32A last week. got my phone fixed under warranty thank god. but i got the perfected SPL.
if you do get the perfected SPL, you dont really need to change your SPL to flash stuff on your phone.
just replace your recovery using the recovery flasher apk a.k.a the one click root.
reboot to recovery, flash a new ROM that is rooted.
then using the adb shell method, flash a new recovery permanently to your phone.
i have had no issues using that method since i got my perfected SPL.
whalesalad said:
Hey guys,
Few of you in the cyanogenmod irc room the other night might have recalled me totally bricking my t-mobile mytouch by pulling the battery after a reboot... dumbest thing I have ever done. I consider myself a fairly knowledgeable linux geek, but unfortunately I panicked and did the worst possible thing, pulling my batt and completely bricking my phone.
I was installing the 4.1.999 cyanogen mod. Phone was so toast it wouldn't charge. Status led's wouldn't work, it was 100% toast. Fortunately I was able to have it replaced and would like to try again in a day or so.
Here is a video showing exactly what I did, please excuse the length of the video it goes from start to finish, backing up and flashing everything, up until the point where I pulled the battery. I'd love to know what I did wrong, so I can try again!
View the video here on vimeo -> http://vimeo.com/7022688
Click to expand...
Click to collapse
after applying the 4.1.999 update you pressed the trackball to reboot your suppose to hold the home key while its rebooting on that step till the mytouch screen shows up also you need to wipe the ext. redo the last step then the my3g should be fine in other words reflash the cyanogen
u install wrong recovery
Install instructions for an HTC Magic (32B ONLY!!!)/ION/MyTouch3G
Same as above if you are using CM-Recovery 1.4.
OR
Same as above EXCEPT step 2
Download HTC ADP 1.6 DRC83 http://www.androidspin.com/downloads...ooted_base.zip
*You have to manually reboot MT3G and hold home.
he can use the ra recovery image it works because i used it on mine
Turns out I used the wrong recovery image before doing the cyanogen flash.
I followed this guide on my second phone (swapped out my old white one for a black mytouch) and am running 4.1.999 right now - http://forum.xda-developers.com/showpost.php?p=4666075&postcount=282

Stuck after flashing

Hey guys, I usually try to avoid asking for help because I can usually find several topics to guide me on how to do thigns, but today I find myself completely stuck. So here's my story:
A couple of days ago I was running cyanogen's 4.2.4 rom. I had ended up with some bugs like not syncing with gmail and it was giving me 3-4 hours of battery life while idle and everything turned off. The previous rom had none of these problems. Anyway, I heard about Dwang's and decided to try out v1.11 of his rom and loved it. However last night when I tried to flash to version 1.13 it froze on my rogers screen. My last nandroid backup was the one made on the cyanogen rom. I spent all day fiddling around trying to do everything to get anything stable to run and now tonight I ended up overwriting the nandroid backup and now it can't boot anything up other than the fastboot and 1.4 loader. I've tried wipes loading older roms, newer one (both dwang and cyanogen)
I don't wanna touch anything else for tonight in fear of bricking my phone but I'm hoping someone can help. It's not bricked, but I feel at this rate and how frustrated I am I have a feeling that might happen and I want to avoid it.
I know there are some other topics that may be similar because I've done a search but I'm not exactly 100% that the solution given to them might be used for my problem as well.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA210000)
CPLD-4
RADIO:2.22.19.261
Ok well, I seemed to have made things a bit worse somehow. Now when I hold camera+ home it brings up a triangle with an exclamation mark and a phone logo. BUT I'm still able to fastboot.
Did you boot on the ADP 1.6 ROM?
Yes I did as it was one of the steps on cyanogens wiki. I even tried to flash it without flashing cyanogen's rom and what it does is just show the android screen, then when it finishes loading it goes black for a split second and then goes back to the android screen. I managed to load older nandroid backups of cyanogen again but whenever I try to flash the 1.6 and then either dwangs or cyanogens it doesn't work. I also cannot do fix_permission at the recovery screen. it tells me something about e2fsck.
Here some of the things I've tried today on the phone without any success:
Another thread had a similar problem and one of the tips was to fastboot and do
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-RAv1.3.2G.img
so I tried that and now I am equipped with the ra recovery and when I try to flash the rom it still doesn't work. I also let it hang for about 20 minutes before trying something else.
I've also flashed it to 1.6 htc stock and it works but it doesn't let me have the proper recovery screen and whne I try to update with a renamed rom file it says installation aborted.
So now I feel stuck :-(

Categories

Resources