Can Only Flash RC33, Need Help - G1 Q&A, Help & Troubleshooting

I was using a theme CM 3.6.8.1 ROM today with modified launcher_7, phone and MMS. I changed the Launcher from 7 to 8 and flashed the themed ROM again and I got stuck at the G1 screen.
I fastbooted (Dreaimg.nbh) to refresh, did the usual steps, flashed RC33, the radio, then I tried to flash the original 3.6.8.1 (no theme). After flash and reboot, it took me to fastboot. I flashed JFv1.5 -ADP1.5 and it did the same thing.
I then flashed the Special SPL and then tried each ROM again which left me on the T-Mobile G1 screen.
However, when I flash RC33, it loads just fine and works normally. I tried searching for a thread that'll help me flash back to the 3.6.8.1-level ROMs but nothing seemed to match my situation.
If anyone can help or send a link to a thread that can, it'll be greatly appreciated.

Related

Help with my phone need to resolve brick

OKAY soo...
I was trying to flash cyanogens new rom 4.2.1.1 or w/e... and i flashed the radio. didn't do home + back, then i flashed his rom.
It was stuck at g1 screen for a long while so i went to recovery then flashed the radio again.. but instead of back home i did menu+call+end [which restarst phone]
now, when I try togoto recovery it shows exclamation point with triangle
though, my phone will boot up to my recent dwang rom, but its stuck at android bootloop.
help appreciated!
You flashed the wrong recovery image. Meaning you need to re-root your phone. Thats the STOCK recovery image, not the update.zip style recovery from the website. Easy fix.
I wiped and yeah i had 4 columsn of icons =/. thanks

Rogers to Cyanogen 4.2.5 Rom Help

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.

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.

Possible G1 Brick with Cyanogen?

Okay, so I was feeling somewhat frisky, so I backed up my G1 with BART (first backup ever), and I installed AOSP Eclair.
It worked fine, I installed the SPL for it (I dont remember the exact title, but it's correct), and everything was smooth.
I didn't like the eclair, so I thought to switch back to cyanogen.
I flashed the Danger / Death SPL again.
I flashed the Cyanogen's latest rom, and it hung at the G1 screen.
Like, for 30 mins. I flashed the Other SPL + AOSP Eclair again, and it worked fine.
I can get into Recovery, as well as FastBoot (Camera+Power).
Why the extreme lag / brick with Cyanogen now?
Im going to try and re-BART again..
cyanogen brick
Go to cyanogen wiki site you need to flash a zip before flasing cyg because og the google thing I had to do it to not sure what its called but it ends with a 83 its not bricked if you can get into recovery screen
NoCyg brickk
Drc83 is what its called flash that first no wipe or reboot then flash cyg over that

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.

Categories

Resources