Rogers to Cyanogen 4.2.5 Rom Help - G1 Q&A, Help & Troubleshooting

Ok I bricked two phones so far I need help. So this is the process that I took I rooted my rogers dream using the one click method. So this would allow me to get a new recovery menu and hboot would say 1.33.2005. So I now I can root my device cause I have done it multiple times. I install the recovery image from here http://developer.htc.com/adp.html#s3 that goes fine I reboot and then I install cyanogen 4.2.5 and then when I reboot it seems to get stuck on rogers splash. I don't know it seems to take to long and then when I take the battery out to try to boot to recovery it does not work. Could give me some guidance as to how to install the cyanogen rom after following the instructions of rooting from this page http://forum.xda-developers.com/showthread.php?t=558301. Thanks in advance.

Related

Easy Question About Cyanogen ROM

Hi, I have installed RA-dream-v1.2.3 img and I want to install Cyanogen ROM but I need change the recovery image to Cyanogen 1.4 or can I do with the RA-dream-v1.2.3 ?? It's necessary have installed cyanogen recovery image to install a cyanogen rom or can I do with my favorite recovery image (AMONRA)
jonzina said:
Hi, I have installed RA-dream-v1.2.3 img and I want to install Cyanogen ROM but I need change the recovery image to Cyanogen 1.4 or can I do with the RA-dream-v1.2.3 ?? It's necessary have installed cyanogen recovery image to install a cyanogen rom or can I do with my favorite recovery image (AMONRA)
Click to expand...
Click to collapse
You can run RAs recovery, it'll work just fine i use RA 1.2.2 just for the 96 size linux swap part but it'll work just fine.
any modded recovery will work. so you can continue using Amon RA. i am using that myself.
No disrespect to Cyanogen, but I perfer the Amon_RA recovery because there are more options available.
G1 stuck at Tmobile screen
I have installed cyanogen recovery and rom and i am stuck at tomobile logo screen for hours. I tried to do alt w and than update from any zip and select the last Cyanogen rom and it still stuck at tombile screen after install and reboot. Can anyone help please
syedfaz26 said:
I have installed cyanogen recovery and rom and i am stuck at tomobile logo screen for hours. I tried to do alt w and than update from any zip and select the last Cyanogen rom and it still stuck at tombile screen after install and reboot. Can anyone help please
Click to expand...
Click to collapse
Did you follow the instructions properly? Did you flash the HTC image first then Cyanogen's rom? If it was your first time using it?
first i ran the DREAMING.nbh file, than install the recovery image, than install the updated radio, than install the latest spl and than the update ROM from Cyanogen website. i was reading through other post for the same error where the sreen is stuck on tmobile sign , it was instructed to run n droid back and than wipe and install the ROM from sd again which i did , and as soon as i click on home + power it took me to White box and arrow coming out and cell phone sign and it is stuck on this window for the past 20 min.
Any Clue
Below is the link i used for instruction,
http://androidandme.com/2009/08/news/how-to-root-a-t-mobile-g1-and-mytouch-3g-android-phone/
All the steps i followed and have done it twice. Is there anything missing in these steps? can anyone help, I am trying to install Cyanogen update-cm-4.2.3-signed.zip and no luck .
You need to flash the HTC 1.6 recovery image first. Go to cyanogen's ROM's op and click the link to his wiki to give you detailed instructions

Can't install Cyanogen 4.2.6 nor Dwang 1.13

I am completely stuck as of now, tried everything! No idea what else I could try. I basically can install any rom just fine, Dwang 1.12 works fine, Cyanogen Mod 4.2.5 works fine too. I am not able to install the latest ones by either though, what could be the issue?
I have rooted MyTouch 3g.
What do you have on your phone right now, and what methods have you tried? What have your steps been?
I have 2 MyTouch 3g phones actually, one is my roomie's and I can install dwang's 1.13 just fine on it, weird .
For dwangs:
Backup
Wipe
Install
Reboot and get stuck on the MT3G boot screen
For Cyanogens:
Backup
Wipe
Install rooted Base
Install Cyanogens
Reboot and get stuck at MT3G boot screen.
It is my understanding that Dwang's latest is based off Cyanogen's 4.2.6, thus I can see why both of them won't work. But why?
I am on Cyanogen's 1.4 recovery tools, I've had Amon RA 1.3.2, as well as RA 1.4.
HBOOT: 1.33.0006 (SAPP30000)
Radio: 2.22.19.26I
anybody?
afive720 said:
anybody?
Click to expand...
Click to collapse
Sorry i can't help, but just to add on... I'm having almost the same issue, but with a G1. Although i can install any of Dwang's versions, including 1.13, but as far as cyanogen goes, 4.2.5 works great, but 4.2.6 and 4.2.7.1 i get stuck at the g1 logo when trying to flash. If anyone can help my set up is
SPL 1.33.0006
Radio 2.22.19.26I
Amon_RA recovery-RA-dream-v1.2.3.img
have you both done thorough wipes through the console?
Are you flashing the signed developer zip file before trying to flash the rom itself?
The process should be...
Wipe
flash signed dream developer zip
NO REBOOT
flash the rom zip on top of the previous zip
Reboot
you can find links to the signed dream dev zip here
http://forum.xda-developers.com/showthread.php?t=593626
Since the first guy has a mt3g, you'll need to find that primary file. The dream one wont do it for you.
check cyanogen's wiki over at cyanogenmod.com
I've had a similar problem. I follow all the instructions correctly, but Dwang's 1.13 works and CM doesn't. For CM I did everything, wiped, flashed 1.6, flashed CM, rebooted, and then it would go back into Recovery for some reason. I'd reboot again and it'd hang on the Rogers screen for me. I couldn't fix it so I wiped, flashed Dwang's, and his worked fine. No clue why CM wouldn't work for me since that's the ROM I actually wanted.
DiSTroy3d said:
For CM I did everything, wiped, flashed 1.6, flashed CM, rebooted, and then it would go back into Recovery for some reason. I'd reboot again and it'd hang on the Rogers screen for me.
Click to expand...
Click to collapse
Yes the first reboot writes the radio files. The second boot writes the cache.
You will have to hit reboot when the cache writing stops. (reboot will become an option in the recovery)
This is the first boot of a brand new OS as far as your phone is concerned and it will take a few minutes. The boot process will take a while. The phone is writing and moving the entire android OS.
I have had mine hang for about 10 minutes before. Sometimes it is 5 minutes.
Mine normally hangs for about 2-5 in the G1 boot screen and another 3-5 in the cyanogen logo.

Flashed myself into a corner...

So I was running OpenEclair v1.1.1, and since putting eclair on it, I've been unable to flash to any other rom. It goes through the wipe/install process, but when the device reboots I just get the rogers screen forever. I can then go back into recovery and re-flash OpenEclair to get it working again. I just got through all that hassle with rogers and made it out with my data and my root, so I was now attempting to fix this issue, and figured it couldn't hurt to upgrade my radio and try out amon ra's 1.5.2R image.
Unfortunately, I downgraded the SPL to 1.33.0009 right after trying to flash another ROM which didn't work, and performed the downgrade before I put a working ROM back on it (to use flashrec to get to amenra's), so at present I can only get into the SPL. My cyanogen1.4 recovery seems to be gone as I just get the original triangle ! logo (no menu or anything) when trying to start up in recovery mode.
Now what did I do, and how far back do I need to dig through tutorials to get back to a working rooted ROM? I'm not really sure what point I'm actually at, whether I still have root or not, or where to start.
Ninzoku said:
So I was running OpenEclair v1.1.1, and since putting eclair on it, I've been unable to flash to any other rom. It goes through the wipe/install process, but when the device reboots I just get the rogers screen forever. I can then go back into recovery and re-flash OpenEclair to get it working again. I just got through all that hassle with rogers and made it out with my data and my root, so I was now attempting to fix this issue, and figured it couldn't hurt to upgrade my radio and try out amon ra's 1.5.2R image.
Unfortunately, I downgraded the SPL to 1.33.0009 right after trying to flash another ROM which didn't work, and performed the downgrade before I put a working ROM back on it (to use flashrec to get to amenra's), so at present I can only get into the SPL. My cyanogen1.4 recovery seems to be gone as I just get the original triangle ! logo (no menu or anything) when trying to start up in recovery mode.
Now what did I do, and how far back do I need to dig through tutorials to get back to a working rooted ROM? I'm not really sure what point I'm actually at, whether I still have root or not, or where to start.
Click to expand...
Click to collapse
Have you got a fastboot mode you can boot into? At least then you could fastboot boot a (non-peristent) recovery image to let you then restore from a nandroid backup...assuming you have some good backups either on the phone or on a PC that can be copied to the phone.
I should note you haven't said what kind of phone you have (G1 or Magic) or really provided anything resembling a complete set of relevant information about your phone and its current state. So it's hard to help.....even if this was the right forum...and it isn't.
Try formatting or using a new memory card.
I'm using a rogers Dream, I have a 2gb SD card with 32MB linux swap and 500MB ext3
HAD 1.33.2005 SPL, 1.4 cyanogen recovery image.
Now I have 1.33.0090, can't get into recovery.
Trying to boot normally brings me to a rogers screen.
I CAN get into fastboot, can I put cyanogen's recovery back on?
Sorry if this is the wrong forum, where should I have posted?
Also, I don't know what information IS relevant to this, so please bear with my noobness.
Is there a recovery that will let me flash a ROM without changing the SPL back to 2005? Apparently if I can get the phone to boot up I should be able to use flashrec to upgrade the radio and SPL from the point I'm currently at.
Moved as not Android Development.
So I'm not sure what I did but the phone boots now...
Holy sh** it wasn't just me. I have this SAME problem. After flashing eclair and wiping and flashing another ROM it just stays at my splashscreen FOREVER. Even broke my nandroid, so I can't restore. How I fix mine everytime: Flash a rom OVER open eclair boot up... you'll probably get a sht load of force closes and all that but once you ge tto login screen just reboot into recovery and wipe and flash or nandroid restore then it should work.
If you guys are rogers, then you will most likely be ebi1, in which case, dont forget that you must also flash an ebi1 kernal to get past the boot screen.
So the phone booted into the original 1.5, I didnt realize the downgrade of my SPL flashed the ROM too. I put flashrec on and flashed Amen Ra's new recovery image and the rogers radio update, this is what I'm at now.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA21000)
CPLD-4
Radio-3.22.26.17
Trying to flash to a custom rom again still fails. I've tried cyanogenmod, super D, and openEclair, it doesn't seem to matter. Where can I get an ebi1 kernel to flash?
E: looking at your signature, it seems I've got the right radio, I'll try using that port tool.
That did the trick! I followed the steps in your signature, flashed a rom, then flashed the ebi1 kernel and my phone booted like a dream. Pun intended.
Edit: So I'm back to only being able to run openeclair. Flashing cyanogen and then briancrook's ebi1 kernel still only gives me the rogers screen. I am however able to flash back to openEclair to get access to a working device again.
Edit: openEclair is running like garbage, it keeps completely locking up the device, I haven't even been able to log into my gmail account to get my contacts back.
Okay, I've managed to get the rom running smoothly by wiping everything, flashing the non-ramhack version of openEclair 1.2.2, then flashing the 1.2.2 ebi1 kernel. Unfortunately for some reason when I do get into eclair, I have no phone app, no settings, and no contacts app, even tho the contacts still work if i try to message someone. This is infuriating.

Help Flashing Custom Recovery on G1

Hi am a newbie here.i have read many guides here and form cyanogen and addictivetips on flashing custom recovery image on T-Mobile G1,DMD64,Donut..i have tried ROM Manager,Fastboot and ADB but still i get errors.what can i do ?
is your phone rooted? what errors?
Well first you need root. I was lazy and used this (http://forum.xda-developers.com/showthread.php?t=747598) app to get root. Then I followed the CyanogenMod wiki (http://wiki.cyanogenmod.com/) to get the Recovery, Radio, SPL, then ROM flashed and now I'm running CM 6.1.
yo9gnc said:
is your phone rooted? what errors?
Click to expand...
Click to collapse
My phone is rooted...but now i finnaly got clockworkmod recovery working and i tried flash alternate recovery which is Ra 1.7.0..but now wen i reboot the first time, i get into the recovery well,and wen i try to reboot again, i can't get into recovery.just seeing a triangle and a dead phone..wat am i doing wrong
Did you remember to flash the defanged base on the cyanogenmod wiki? I forgot to do that the first time I rooted and my recovery got reverted back to stock.
raydar670 said:
Did you remember to flash the defanged base on the cyanogenmod wiki? I forgot to do that the first time I rooted and my recovery got reverted back to stock.
Click to expand...
Click to collapse
Thanx Brother..i followed everything and am now running chromatic 4.4..very sweet

Got stuck on X - Detailed information

Firstly, it is a well known issue and I've searched a lot and do everything I can. This is my current status :
1. it could not boot into anything, stuck on X all the time.
2. After reflash all ( boot, recovery, radio, system respectively ). I got my n1 passed the X and boot into OS. But it's screen is black, completely ( I can still see the X so I do not sure it is the hardware problem or not ). I still interact with all the button and when I call it with another phone, busy signal received, I guess it is still in configuration mode.
3. I try to flash custom recovery (CWM) but it is stuck again on X.
Detail information:
Code:
Korean Nexus
HBOOT ...0017
S-ON
PASSIMG does not work due to CID incorrect !
Thanks for reading my issue and I am looking for your help. I really love my N1 and I just bought it 2 months ago This happened when I plug the charge and it rebooted, then stuck on X.
Erm... why don't you try installing the Blackrose HBOOT and then fastboot flash a new ROM? This might not even be a logical solution but it looks like you've tried most of the other stuff. Just out of interest, what radio are you on?
You flashed old Froyo OS, I believe, and have SLCD screen variant - which makes Froyo older than FRG83 incompatible with your phone. This is why you don't see a screen output when booted into OS. If you install a fresh Gingerbread or latest Froyo ROM - everything will be fine. If your bootloader is unlocked (you see padlock on the "X" screen) - you can flash custom recovery directly from fastboot.
If you can't PASSIMG because of having Korean Nexus variant - you can try to install Blackrose, as suggested, which will allow you to PASSIMG whatever you want.
Thanks for your help. I will try to see how it is going
Steps that I will take :
1- Flash Custom BlackRose HBOOT
2- what is the best ROM that I can flash ( pass as PASSIMG ) to have a chance to boot my phone again
Any latest Gingerbread PASSIMG that you find, or any PASSIMG starting with FRG83 and beyond. Any of those will work.
Thanks you all for great help. I finally get my Droid running by reflash to amon ra recovery and flash cm7
nXqd said:
Thanks you all for great help. I finally get my Droid running by reflash to amon ra recovery and flash cm7
Click to expand...
Click to collapse
I'm stuck on the same X logo. The phone is an SLCD variant with stock GB and no root.
please guide me through the steps you followed.
thanks
abhilash_ksh said:
I'm stuck on the same X logo. The phone is an SLCD variant with stock GB and no root.
please guide me through the steps you followed.
thanks
Click to expand...
Click to collapse
Firstly, can you tell me the reason why this happened ?
I don't know well about the root and the difference between the KOR and GB version. I still hold the guide, and I will post here if you need

Categories

Resources