Originaly i was on kingclick 1.6.1 hard spl recovery 1.5.2 latest radio 26i, however, i rebooted holding the power button and all of the sudden i was stuck on the 3 skaters bootloader. After many attempts to flash various roms(wipe everything before doing so) i decided to flash an dreaimg.nbh and now im
stuck on
drea100 pvt32b
hboot-0.95.0000
cpld-4
readio-1.22.12.29
sep 2 2008
serial0
(rainbow screen)
recovery (home+power) works and it seems that when applied a rom-cr29 the flashed rom is applied but it returns to the rainbow boot loader where it proceeds to the .nbh file.
(in 1 occasion using cyanogen wiki i let the .nbh file run just like i was going to aquired root, the exact procedure.
furthermore, on top of the android recovery commands i get "E:cant open /cache/recovery/command and the options 3 minimal options of reboot, toggle log, apply update and wipe are available.
im fan of reading all threats. top to bottom but as a last resort ill just say "this time i dont understand and would like some guidance"
Is there a specific rom that Runs on that spl provided above?
Is the problem ever solved? I have exactly the same problem:
stuck at the rainbow screen
apply rc29, update successfully, but when i reboot, it goes back to where it proceeds to the .nbh file.
I once had to revert my phone back to stock and I could only boot to the SPL screen . Luckily I followed this (http://theunlockr.com/2010/09/23/how-to-unroot-the-htc-g1-dream/) guide and got back to stock, re-rooted, and now I'm running CM 6.1 . Good luck to you.
Related
For the last year I have been able to boot to recovery no problem. About a week ago it stopped booting to recovery. Holding home + power brings me to the g1 endless loop. The weird part is it will load any recovery right after I flash it via adb or terminal. I have tried out all the recovery images out there and they all are the same, I have to flash it before I can boot to it and it will only boot once, after reset I have to flash again to get back into it. The same goes for cm updater. I download the update, apply it, phone resets, g1 boot screen infinity... I am an advanced script kiddy and I can't find a solution anywhere any ideas on how to deal with this? Would a log help?
Thanks!
FiFTYSiX said:
For the last year I have been able to boot to recovery no problem. About a week ago it stopped booting to recovery. Holding home + power brings me to the g1 endless loop. The weird part is it will load any recovery right after I flash it via adb or terminal. I have tried out all the recovery images out there and they all are the same, I have to flash it before I can boot to it and it will only boot once, after reset I have to flash again to get back into it. The same goes for cm updater. I download the update, apply it, phone resets, g1 boot screen infinity... I am an advanced script kiddy and I can't find a solution anywhere any ideas on how to deal with this? Would a log help?
Thanks!
Click to expand...
Click to collapse
What's your SPL version?
Have u ever flashed SPL or Radio?
Dream PVT 32B ENG S-OFF
HBOOT 1.33.2005 (DREA10000)
CPLD 4
RADIO 2.22.19.26I
APRIL 20TH 2009
HBOOT
did you try to flash a new recovery.img?
^^
Every time I want to boot to recovery I have to flash. It does not matter what recovery.img I flash (RA, CM, etc..) I stil have to do it every time if I want to boot to recovery. If I reboot the phone or power off cycle more then once I lose the ability to boot to the recovery rom. Its as if it disapears after rebooting or shut down...
Solved...
I wiped and reinstalled cm's latest build. Works fine now. I'm guessing I have to wipe from now on I was really hoping I don't have to.
Thanks
hi,
I have a G1 that I got with unrooted 1.6
I followed instructions at http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod to get CM 4.2 on the phone, that worked without any problems
I then installed DangerSPL and followed instructions at http://forum.xda-developers.com/showthread.php?t=672992 to get CM 5.0.7 installed, and that also worked.
When I installed ROM Manager to partition SD card for apps2sd, the phone would not boot any more, it kept getting stuck at the G1 / T-mobile screen
I then entered fastboot and reinstalled RC7 (DREAIMG.nbh)... that booted without a problem... I then re-flashed cm-recovery-1.4, went into recovery and installed cm 5.0.7 and gapps... I'm not sure but I may have skipped radio and danger this time around
since then the phone won't boot or enter recovery or enter fastboot... any attempts to boot into any of those results in the phone getting permanently stuck on the G1 / T-mobile screen
I'm out of ideas here, so any help would be greately appreciated.
thanks,
allixsenos
allixsenos said:
hi,
I have a G1 that I got with unrooted 1.6
I followed instructions at http://wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_G1/Dream_Firmware_to_CyanogenMod to get CM 4.2 on the phone, that worked without any problems
I then installed DangerSPL and followed instructions at http://forum.xda-developers.com/showthread.php?t=672992 to get CM 5.0.7 installed, and that also worked.
When I installed ROM Manager to partition SD card for apps2sd, the phone would not boot any more, it kept getting stuck at the G1 / T-mobile screen
I then entered fastboot and reinstalled RC7 (DREAIMG.nbh)... that booted without a problem... I then re-flashed cm-recovery-1.4, went into recovery and installed cm 5.0.7 and gapps... I'm not sure but I may have skipped radio and danger this time around
since then the phone won't boot or enter recovery or enter fastboot... any attempts to boot into any of those results in the phone getting permanently stuck on the G1 / T-mobile screen
I'm out of ideas here, so any help would be greately appreciated.
thanks,
allixsenos
Click to expand...
Click to collapse
Why would you unroot just because a ROM wouldn't get past the G1 screen. Too bad you didn't post about that instead of completely unrooting and trying again.
Oh, you probably didn't miss danger spl the second time around and forgot to flash radio and now you're soft bricked. Sorry, there's nothing we can do.
Hi all, I would ask for your kind patience reading the lengthy story to understand how I came to the problem.
recently I got my AMOLED N1 stolen in the nightclub (very stupid of me), so the new N1 I can get is all SLCD version coming with HBOOT 0.35.0017, microp-0c15 and FRGxx
I managed to fastboot flash RA recovery 1.8.0.1-aw, but found HBOOT 0.35.0017 would automatically replace the custom recovery if the phone was turned off and boot up again, though you can use it via boot into recovery from the menu without a power off.
So i did managed to flash r21-modaco-N1-FRF91 (blank screen, guess it's not customised for SLCD), and fastboot flashed an official boot.img from a official unrooted korean FRF 91 ROM, and it worked, the screen lit up with r21 custom ROM and the system was already rooted. Splendid.
But I wasn't happy about the HBOOT 0.35.0017 resetting custom recovery all the time ( i don't know if it resets all other custom recovery), so I downloaded the EPF30 passimg ROM, cos it came with HBOOT 0.33.0012.
so I did managed to downgrade the HBOOT to 0.33.0012, but it BLANKed (haha, no worry, I still managed to fastboot flash RA recovery 1.8.0.1, but the recovery wouldn't lit the screen either), then I put the official passimg FRG33 rom (with HBOOT 0.35.0017) to the SD card, blind boot the phone into HBOOT again (cos it's still blank).....waited patiently until passimg been checked completely, press up to confirm applying the passimg, and ding ding, the screen lit up again with HBOOT 0.35.0017 microp-0b15. (cos EPF30 comes with microp-0b15, and FRG33 doesn't)
Now the problem came as I rebooted into system, and found the trackball LED stayed always in RED when the screen was lit. So I guess it's the microp that got me here.
So Question 1, if anyone knew how to update or fix the microp?
Question 2, while RA recovery 1.8.01 is for both AMOLED and SLCD version, does it always choose its display mode relating to the HBOOT?
If it is related, would RA recovery 1.8.00 (SLCD version only) work with HBOOT 0.33.0012? I guess SLCD only version doesn't neccessarily have to check up with HBOOT, and thus workable with HBOOT 0.33.0012, could somebody confirm my guess?
I guess a working RA recovery is worth putting up with a blank HBOOT as long as I know where to press to get into recovery.
First I downgraded to 1.0 then upgraded to 1.5. Then I used FlashRec and applied Amon Ra's Recovery Image, rebooted to the SPL, then applied cyanogen 6.1.0 then the gapps file. After rebooting I get to the "G1" splash screen, it... stops... It's been on this screen for 20 minutes. I tried the guide here verbatim first but, alas nothing. How did I screw up this time?
After installing the rom and following the steps for BlueGinger, I am now stuck in a boot loop. After the flashy and very vivid ICS boot animation run though,freezes before starting over. I waited for a good 10 mins for this to change. I have flash MANY roms on my G1. Thought something went wrong so I flashed Ohsaka-SuperWipe v2 to make sure my RA recovery didn't miss anything in the wipe. Went thought the steps in the thread. Why is this happening?
Well, do you have the given SPL and Radio? Just check it by pressing [POWER] + [CAMERA] Like it's mentioned in the thread, you have to have Radio 2.22.27.08 and SPL 1.33.0013d. Just look for a thread for doing this on the forum. If THAT doesn't work, you download file may be corrupted. Just downloaded the file again. And if this works, just press the thanks button will ya?????