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 :-(
Related
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.
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!!
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
Hi,
Already posted part of the situation in Amon_RA's recovery thread but neither of the answers there seem to solve my problems. Decided to post it here since the problem seems to involve aspects other than the recovery itself.
Here's the complete situation:
Had problems with RA recovery freezes since the start and with different versions. I could (and can) enter recovery mode (v1.6.2), scroll down the options but after 15 seconds the recovery just freezes and reboots every single time. Checked the version (H) and the MD5, they where all correct. Tried cm-recovery-1.4-32A and it seems to work fine but when I flash a ROM (1.6) I have similar problems with the ROM (freeze+reboot in "touch droid setup"). Curiously I flashed my hero 2.0.5 (1.5) and had no problems...
Tried booting the latest RA recovery trough fast-boot and it worked fine the first two times I did it (scrolled down the options for like 10 minutes and it didn't freeze). After that it did not work and got the freezes+rebooting problem back again. Tried ADB, Flash-rec and flashed the recovery but got the freeze+reboot problem once again. Re-checked the version and MD5 and they where all correct.
Why does this happen? Any clues?
Thanks for your help!
I'm kind of lost here...Could it be a radio or SPL problem? Should I re-flash/update it? I never had problems with the stock ROM so this situation is really odd...
Can anyone help?
Thanks in advance!
strange... try some random methods here lol (I don't know if they'll work though but it can't hurt)
First, try flashing an ENG SPL, see if that makes a diff
If that fails, try flashing a whole new ROM/RADIO/SPL
for example: Since you're a 32A user, I believe you can flash the 6.35.x radio and the 1.76.2007 SPL and then use the hero recovery. Test out a rom on the new radio for like a day and try out the recovery. See if that freezes! (This doesn't really accomplish much though because even if it doesn't freeze, i think you'll wanna go back to the old radio to try out other roms lol. You risk bricking your phone if you don't understand this stuff so don't do it if that's the case)
But anyways, I'm a bit confused. What rom are u using?
noroses said:
Hi,
Tried cm-recovery-1.4-32A and it seems to work fine but when I flash a ROM (1.6) I have similar problems with the ROM (freeze+reboot in "touch droid setup"). Curiously I flashed my hero 2.0.5 (1.5) and had no problems...
Click to expand...
Click to collapse
So you can use the recovery fine, until you flash a rom? So when you flash a rom, your recovery beings to freeze. But when you flash a different rom, your recovery works fine? Weird. Sounds like a problem when you're flashing a rom...
I have no idea dude but what I would do if I was in your situation:
1) Flash ENG SPL, something like 1.33.0010 (double check everything, i dont like advising people to play with their spl/radio so dont just take my word)
2) load up recovery and give it a try! if all that fails...
3) I'd backup your phone via nandroid in recovery (i pray that it doesn't freeze lol)
4) Wipe wipe wipe
5) Go into fastboot, fastboot erase system -w and then try another rom! And if the rom is good, then go back to your old one. Try to find out what the prob is.
It appears that you're able to flash roms still even with your recovery freezing (so weird) so I dunno. Just give it a try I guess lol
very weird indeed.... question.. does this do this when plugged in as well as on battery? ive heard of some really weird issues with bad batteries....
i would try what kawata recommended as well.. kind of just a process of elimination...
hopefully you dont have a hardware issue..
Hi,
strange... try some random methods here lol (I don't know if they'll work though but it can't hurt)
First, try flashing an ENG SPL, see if that makes a diff
Click to expand...
Click to collapse
Will try this. Can I flash the SPL trough the recovery?
If that fails, try flashing a whole new ROM/RADIO/SPL
for example: Since you're a 32A user, I believe you can flash the 6.35.x radio and the 1.76.2007 SPL and then use the hero recovery. Test out a rom on the new radio for like a day and try out the recovery. See if that freezes! (This doesn't really accomplish much though because even if it doesn't freeze, i think you'll wanna go back to the old radio to try out other roms lol. You risk bricking your phone if you don't understand this stuff so don't do it if that's the case)
Click to expand...
Click to collapse
Will have to check and recheck this complex process.
But anyways, I'm a bit confused. What rom are u using?
Click to expand...
Click to collapse
Now I'm using stock 1.5. I tried cyanogen, superD and other 1.6 Roms and they all freezed at the android setup process. Used myhero for a week with no problems whatsoever. Since I have a nandroid backup done with CM's recovery I restore everything back as it was.
So you can use the recovery fine, until you flash a rom? So when you flash a rom, your recovery beings to freeze. But when you flash a different rom, your recovery works fine? Weird. Sounds like a problem when you're flashing a rom...
Click to expand...
Click to collapse
The Amon_Ra recovery freezes every time. It doesn't give me enough time to do anything...Now I'm using CM's recovery and I have no freezing problems while in recovery mode. The problem is after I flash a Rom and reboot. The ROM experiences freezing problems (just like the Amon_Ra's recovery).
Thank you for your answer and suggestions!
digitaljeff said:
very weird indeed.... question.. does this do this when plugged in as well as on battery? ive heard of some really weird issues with bad batteries....
i would try what kawata recommended as well.. kind of just a process of elimination...
hopefully you dont have a hardware issue..
Click to expand...
Click to collapse
Hi,
Thanks for your answer.
I have never tried with the phone plugged into a socket but did it with the phone running on battery and connected via usb to the computer. Should it make a difference?
Could it be a hardware problem? I never had problems with the stock ROM or with the myhero ROM...
it could be hardware...
if you want to flash to new radio and spl please follow this guide to the T or else you will get a brick, you cannot flash radio and spl via recovery.
so...
follow this guide and all will be good... must have adb ....
http://forum.xda-developers.com/showthread.php?t=605239
digitaljeff said:
it could be hardware...
if you want to flash to new radio and spl please follow this guide to the T or else you will get a brick, you cannot flash radio and spl via recovery.
so...
follow this guide and all will be good... must have adb ....
http://forum.xda-developers.com/showthread.php?t=605239
Click to expand...
Click to collapse
Checked that guide but I'm unsure about this part:
If you do not have an Engineering SPL, download 1.33.2010 and flash through recovery before starting this procedure. Flash the SPL update.zip like any other update.zip file.
Click to expand...
Click to collapse
This part I can do within the recovery to enable flashing via fast-boot right?
yup you can flash the eng spl via recovery ... i should have been more specific and said you cant flash new radio and spl via recovery
for the new radio,spl and recovery you do through fastboot
good luck
digitaljeff said:
yup you can flash the eng spl via recovery ... i should have been more specific and said you cant flash new radio and spl via recovery
for the new radio,spl and recovery you do through fastboot
good luck
Click to expand...
Click to collapse
Will try that tomorrow.
Thanks for your help!
digitaljeff said:
very weird indeed.... question.. does this do this when plugged in as well as on battery? ive heard of some really weird issues with bad batteries....
i would try what kawata recommended as well.. kind of just a process of elimination...
hopefully you dont have a hardware issue..
Click to expand...
Click to collapse
Hi again,
Still didn't mess with SPL and Radio. I'm still afraid I'll brick the phone..However yesterday tried a few simple things like using another sd card or entering recovery while plugged in. These two things seem to influence the behavior of the latest Amon_RA recovery but don't solve my problem completely. Example: When I enter recovery using the original SD card (2gb) the recovery would freeze within 20 secs max. Using another SD card (128mb) most of the times it would take longer to freeze (4 or 5 minutes). Sometimes it would not freeze at all. Although this seemed to influence what happened it wasn't constant and could not find a pattern. The same with the phone plugged into computer. Sometimes it helped. One thing is certain: with the original SD card and unplugged from the computer the recovery freezes within 20 secs every single time.
With the CM 1.4 recovery never had any freeze problems. It seems to work great while in recovery mode. The problem is after a flash a ROM I have freeze problems with the ROM itself (tried different ROM's, CM, SuperD, etc and got the same freeze problem). The only Rom that worked fine was myhero 2.0.5.
This is a very strange situation and I'm starting to think that this could be hardware..
Would that be a SD card problem?
try using another SD card and see if the problem still occurs
I am having exactly the same problem, did you ever find a solution?
Went from a fully updated magic 32A (1.76.0009H) now i'm at 1.76.0008
UPDATE: I just found that the hero recovery works (I would post link but xda doesn't allow new users to do that) however it may still be necessary to downgrade radio and spl
I had also same problem. My device is Magic 32A radio 6.35. Solution was to reflash recovery-RA-hero-v1.6.2.img.
I fubared my royalgingerless glacier this afternoon, it stuck on the mytouch boot screen for over 30 minutes after attempting to flash the new sense 3.0 3d rom. (I know I'm sure I did something dumb)
Before that flash I did a wipe all and flash, it flashed, I rebooted and then it hung on the mytough screen for over 10 minutes. I pulled the batt, and had no boot, went to cwm and tried to restore my cwm backup and it said something like e: cache not found etc..
Well I tried to wipe the cache, same deal, tried a bunch of other stuff, no avail, put the pd15img.zip on my sd card, it ran
Parsing ...[SD.Zip]
Recovery -Fail-PU
Boot -Fail PU
Radio_V2 -Updating
it hangs here, so I pulled batt,
At this time I have lost recovery, still have fastboot and hboot so I am not a brick as far as I know.
fastboot devices returns SH12JRM00507 so somethings happening...
I have showing
GLACIER PVT SHIP S-OFF
HBOOT-0.86.000
RADIO-26.0.3.02.26_M
eMMC-boot
Sept 27 2010,11:12:59
Ive been at this for a while, slipped my tmo chip back ino my hyperdroid hd2 and am awaiting some good thoughts on what to do next.
Please search the numerous threads about "Fail-PU", including recent "Rooting dangers" thread in Development section. To say it shortly - your phone is dead.
Cool thanks
I got it completely kia now I'll call htc fore repairs.
another one bites the dust...... this is getting serious
happened to me a couple of days ago and suddenly its spreading like wildfire. I got rid of the mytouch because of it but i really hope it gets resolved soon
side thought: i dunno about anyone else, but isnt the Sense 3.0 rom being mentioned a lot when this happens? Coincidence? Hope so
Same Here
Almost exact same scenario happened to me, except I wasn't trying to flash anything. I was running CM7...whatever the latest nightly was about a week ago. I started getting random reboots, then it just finally stuck on the MyTouch boot screen. I am able to get into HBOOT, FASTBOOT, and CWM Recovery no problem. Attempting to flash ANYTHING just locks up and/or fails.
Time to move to Verizon anyway....boo!
"Almost exact same scenario happened to me, except I wasn't trying to flash anything."
It's crazy that you're able to access the phone thru hboot yet for naught. I've read all the threads like a detective, and it still puzzles, that with the access you still have to CWM and fastboot, that you're not able to repair the situation.
What could these guys have done differently to avoid this?
tankmorph has access to cwm and fastboot - isn't that supposed to allow him to apply some herioc measures to get out of this? At least, that's why I flashed my 085 hboot, to be available in situations like this...
Stinks.
If you just get partition mount failure - ENG HBOOT will help you out of it.
If you have Fail-PU - you need to replace the eMMC on the board (which I'm not sure is possible). Access to bootloader won't help.