Flashed myself into a corner... - G1 Q&A, Help & Troubleshooting

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.

Related

ooops Lost Root

I was running cy's 4.2.4, but I was having an issue with rotate.
I realized that the base Rom i was using was a sapphire rom (or at least that is what i was led to believe) I decided to go to cy's wiki and download the correct base image... signed-dream_devphone_userdebug-ota-14721.zip
I flashed this image and then when I tried to go back to recovery *poof* no recovery. (I was using the RA recovery) I downloaded telnet and tried it, no telnet.
I was going to reflash the RC29, but I was running the "Danger" SPL.
sooooooooo. Will I brick if I go back and install RC29?
Well. for anyone in the future, I can tell you that reflashing back to RC29 will NOT brick you when coming from Danger SPL.
If you have Danger SPL you could just flash back AMON Recovery from Fastboot, no need to root again.
the recovery gets replaced on reboot due the HTC image. You have to edit some scripts which a lot of people find harder than rerooting

STUCK!

Okay i am fully aware of how a forum works and how much i am going to get flamed for this. I really need to go to bed and it would be nice to not have to go find a new phone tomorrow.
I installed JFv1.41 perfectly fine, had the root running etc.
I went to install a Theme, i ran the update.zip...now my phone just gets stuck on the TMOBILE G1 screen...not the flashing droid.
I can boot into Home+Power and into Camera+Power
i have HARD SPL on my root, but it is named update_OG is there anyway i can execute that to fix my problem?
Thanks
d
please can anyone help. Do i need to get a SD card reader and put a recover.img on it...i deleted it on accident because i am anuberchaun.
was the theme made for JF 1.41?
If not, that's why you are hanging on the screen.
What recovery do you have? Can you enable UMS from your recovery? If so, you can just copy a new rom and flash it.
If not, you need a memory card reader and put a new rom on it, then flash.
You are going to need to wipe obviously. I hope that goes without saying.
You should also condsider updating to a newer rom. You are still on RC33 with that I believe. Find a donut rom, like Dwang's. I would recommend you get the new Cyanogen, but that involves flashing more than one thing at a time, and I don't know if you will be able to do that without messing it up... No offense.
Okay so in my HARD SPL on boot, it says no IMAGE file. I have manually uploaded a image file to my SD's root folder. Why wont it see it?
Okay, im in deep. Last resort. Trying to reflash to rc29...only problem is it says not signature on 3 files. I definitely lost root. I using the stock rc29 though why wont it work? Maybe i have the wrong rc29 can anyone help?
Why would you flash a rom in fastboot? You were supposed to do it in your recovery. That's where you went wrong. You say you have rc29 now? Just reroot the phone then.
i cannot re root the phone because it will not get past the flash screen.
i didn't re-flash from fastboot, i did it in recovery. Ive tried re flashing a few times now. I am running jf v1.4 i can not go to any original rom, i also cannot find a DL for a OEM rom. I am trying to reflash to rc29 using the link found in at (http://forum.xda-developers.com/showthread.php?t=442480) the DREAMIMG.nbh file. I was assuming that was a stock ROM, but when i try to reflash to that it says 3 files (no signature)....i was under the impression stock ROM's did not require ROOT access to flash.
i have also tried rc27
FIXED
everything i needed was right here.
http://forum.xda-developers.com/showthread.php?t=592662

Not sure what i have done

Was running lastest Cm Rom & RA recovery 1.5.2.
Loaded into bootloader to check what Radio & SPL i was running.
Then phone started to update.
Now i'm back to stock G1 running firmware 1.0.
Do i need to go though the whole thing again like the first time i flash the rom??
please help.
Looks like you had DREAIMG.nbh at the root of your sd card and then hit the button to update it. Yeah, you are now at RC29 and must re-root and re-install cm.
Could be worse though.

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

Big troubles after flashing CyanogenMod 5.0.7

Hi,
I tried flashing the brand new CyanogenMod 5 with Eclair for G1, and I seem to be in "serious" trouble now.
Before flashing:
I had already installed DangerSPL for a few months with no issue
Had the latest radio
Was happily running SuperD1.9.3 with WG Kernel and JIT enabled
Made a Nandroid backup just in case I wished to go back
Wiped Dalvik-cache and Data/Cache to avoid boot loops
All of this with Cyan's Recovery 1.4.
After flashing the ROM and the Gapps, my phone restarted and got stuck on the G1 screen (no boot screen) for, maybe 15 to 30 minutes, which seemed a bit long for me... I finally decided to remove the battery, went back to recovery and made a Nand restore.
But after the restore, rebooting had the same effect : stuck on G1 screen.
I tried flashing several custom roms with no luck (all stuck on G1 screen).
I finally decided to flash the official ADP1.6 ROM from HTC (signed-dream_devphone_userdebug-ota-14721.zip) which installed fine (and updated the radio by the way), and it finally booted on stock Donut.
I tried then to reinstall custom roms but get stuck on G1 screen everytime I try... and flashing Amon_RA's recovery won't work (i keep booting on the stock recovery). But as a workaround, I can use fastboot to boot into Amon_Ra's recovery.
The questions now are :
did I lose root access, thus preventing from installing custom ROMs ?
if so, is it possible to downgrade while being under DangerSPL ? Won't it brick the phone ?
Is there anybody else who had the same problem with upgrading to Cyan's 5 ?
I really need to get custom roms back, stock sucks on G1... but there is no way i can afford bricking my phone.
Thanks for help guys!!
As long you can get to your custom recovery menu, you still have root access.
Keep the Danger SPL, not worth changing it and the Danger SPL has fastboot also.
It takes a while to boot into a newly flashed ROM so just wait 5-15 min.
Do these steps:
1)Do a FULL WIPE of the phone (data, dalvik-cache, ext, battery stats, and rotation ****You won't have some of these options with Cyanogen's recovery. Just wipe what you can****)
2)Repair the ext partition
3)Flash CyanogenMod 5.0.7-DS-Test 1 (this is the g1/mt3g version)
4)Without wiping or rebooting, flash the gapps .zip file
5)Reboot and set up the ROM
6)Flash the latest Amon_RA recovery for your device. Cyanogen uses Amon-RA's recovery now.
1. Upgrade your recovery....cyanogen stopped working on his a while ago, upgrade to Amon_RA's recovery.
2. You only have to wipe data/dalvik, and maybe sd-ext. you do NOT have to wipe battery stats or rotation EVER.
3. Flash CM Rom
4. Flash gapps
Unfortunately, exact same thing.
Stuck on G1 screen.
Reverted back again to adp 1.6
Any other suggestions ?
alou2 said:
Unfortunately, exact same thing.
Stuck on G1 screen.
Reverted back again to adp 1.6
Any other suggestions ?
Click to expand...
Click to collapse
Give us your spl (hboot) and radio. Go into fastboot and type exactly what you see.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.26I
Good ?
alou2 said:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.26I
Good ?
Click to expand...
Click to collapse
Try upgrading your radio? You shouldn't HAVE to, but it might work.
Are you on Amon_RA's recovery now?
I'll try upgrading radio, but it's weird I can't switch back to other custom donut builds...
I've used Amon-RA's recovery to wipe and install the ROM this time.
For some odd reason though, it seems i can't "install" Amon_RA recovery (it seems to switch back to stock recovery), but just boot it through fastboot...
alou2 said:
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA20000)
CPLD-4
RADIO-2.22.19.26I
Good ?
Click to expand...
Click to collapse
make sure you're flashing the right recovery. dream still has two options. just like mytouch has H or G.
the one with "R" on the end of it is for rogers, one without it is for USA ones.
What files are you flashing? It sounds like you're flashing an old 1.6 base that has a recovery image included. Are you flashing the DRC83 Defanged as a base?
OK so I tried to take a fresh start on this.
I installed Amon_RA's 1.6.2 as recovery (not the Roger's one, I'm in France and the US tools always worked)
did a nandroid backup to stop reinstalling everything over again each time I want to make a phone call...
used it to repartition the SD (FAT / EXT2 / SWAP), thus formatting everything
wiped everything (except battery and orientation)
Flashed DRC83 Defranged
Without rebooting flashed CM5.0.7-t1
Without rebooting flashed Gapps
And it still gets stuck on the first boot screen (left it for about 20mn on it)...
Then I tried installing DRC83 defranged and it still gets stuck on the damned boot screen !!!
Through adb I can get to shell while on recovery, but the su command prints out :
/sbin/sh: su: not found
Is it normal ?
I can't find the /proc/last_kmsg file (just /proc/kmsg). Is there any log file that could help here ?
I'm going to nand back to stock 1.6, hoping it will start without having to flash the radio+recovery one again...
I noticed something weird when i nand back to my pre-CM5 WG-SuperD backup :
when it boots, it gets to the first boot screen and if USB is connected, i get a "fastboot usb" in a red box on top left of the screen.
To sum up :
phone's definitely not bricked, but won't run any custom rom anymore, but it still permits custom recovery installation/boot.
Something must have been broken/deleted somewhere.
Still asking the (dumb?) question : do I still have root, since su doesn't works (even using terminal server) ?
By the way, I really appreciate you guys taking time to read and answer my posts. Really
alou2 said:
OK so I tried to take a fresh start on this.
I installed Amon_RA's 1.6.2 as recovery (not the Roger's one, I'm in France and the US tools always worked)
did a nandroid backup to stop reinstalling everything over again each time I want to make a phone call...
used it to repartition the SD (FAT / EXT2 / SWAP), thus formatting everything
wiped everything (except battery and orientation)
Flashed DRC83 Defranged
Without rebooting flashed CM5.0.7-t1
Without rebooting flashed Gapps
And it still gets stuck on the first boot screen (left it for about 20mn on it)...
Then I tried installing DRC83 defranged and it still gets stuck on the damned boot screen !!!
Through adb I can get to shell while on recovery, but the su command prints out :
/sbin/sh: su: not found
Is it normal ?
I can't find the /proc/last_kmsg file (just /proc/kmsg). Is there any log file that could help here ?
I'm going to nand back to stock 1.6, hoping it will start without having to flash the radio+recovery one again...
I noticed something weird when i nand back to my pre-CM5 WG-SuperD backup :
when it boots, it gets to the first boot screen and if USB is connected, i get a "fastboot usb" in a red box on top left of the screen.
To sum up :
phone's definitely not bricked, but won't run any custom rom anymore, but it still permits custom recovery installation/boot.
Something must have been broken/deleted somewhere.
Still asking the (dumb?) question : do I still have root, since su doesn't works (even using terminal server) ?
By the way, I really appreciate you guys taking time to read and answer my posts. Really
Click to expand...
Click to collapse
I run into the same issue, I was upgrading from the latest cm 1.6 and after trying a few different things, after wiping with alt+w, I reinstalled danger-spl then installed the cm update, then the google apps; after doing this, it worked fine. BTW, it took about 15 mins to boot up though.
alou2 said:
OK so I tried to take a fresh start on this.
I installed Amon_RA's 1.6.2 as recovery (not the Roger's one, I'm in France and the US tools always worked)
did a nandroid backup to stop reinstalling everything over again each time I want to make a phone call...
used it to repartition the SD (FAT / EXT2 / SWAP), thus formatting everything
wiped everything (except battery and orientation)
Flashed DRC83 Defranged
Without rebooting flashed CM5.0.7-t1
Without rebooting flashed Gapps
Click to expand...
Click to collapse
There is your problem. DO NOT FLASH THE DRC83 BASE!!!
Just repartition your sdcard (if you want to), upgrade to ext3 or ext4, then follow the last 2 steps.
Hi UberMario,
I just reinstalled DangerSPL using Amon_ra's recovery, and then directly flashed CM5 + Gapps (no reboot inbetween).
It's been stuck on the 1st splash screen for 30 minutes now...
I'm letting it for another 30mn (although I think it's useless) and will eventually revert back to stock 1.6... again...
I just don't get what's wrong...
I'm going to try redownloading the archives in case they would've been corrupted, but being unable to install anything else than an official htc firmware seems like a symptom to me... isn't it ?
alou2 said:
Hi UberMario,
I just reinstalled DangerSPL using Amon_ra's recovery, and then directly flashed CM5 + Gapps (no reboot inbetween).
It's been stuck on the 1st splash screen for 30 minutes now...
I'm letting it for another 30mn (although I think it's useless) and will eventually revert back to stock 1.6... again...
I just don't get what's wrong...
I'm going to try redownloading the archives in case they would've been corrupted, but being unable to install anything else than an official htc firmware seems like a symptom to me... isn't it ?
Click to expand...
Click to collapse
I'm not sure if this will make a difference, but flash Gapps first then flash CM5 then reboot and everything should work...
or
You might want to check and make sure your MD5 is correct too..
why would you flash gapps first? you have to flash it on top of cm5.
Yeah... quite sure this won't help.
What could prevent the phone from booting custom firmwares but still allowing to install them ? (and finally I can still run the su command through adb, and get root access, but apps can't get root...)
tehseano said:
why would you flash gapps first? you have to flash it on top of cm5.
Click to expand...
Click to collapse
I rooted my G1 for the first time. I flashed CM 5.0.7 then GApps (no reboot in between). When the phone booted, none of the Google Apps were on the phone. Went back to recovery and did a wipe and flashed GApps then CM (no reboot) and everything installed correctly. Someone said to flash CM first then GApps, but that didn't work for me. Weird.

Categories

Resources