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.
Related
Ok, I'm guessing I misunderstood something. I'm a "noob" so bear with me...
here's what I did.
I was running cm v 4.2.9.1 and decided to try and upgrade to the latest version. I wiped and reflashed and got 4.2.14.1 running, but I felt it was slow (the reason I didnt use any other new version), so I came here looking to see any new roms.
I decided KiNgxKxlicK AOSP 2.1 rom looked cool, so I downloaded it and flashed it (yes I wiped first). I'm guessing this is where it went wrong. The rom took 30 mins to finally boot to home (longest ever) but the sweet nexus screen made it easier to bear. I DID NOT do anything with an spl or any radio (that part still kinda confuses me to be honest). I'm guessing this is why I am in the predicament that I am.
The KiNgxKxlicK AOSP 2.1 rom loads fine, but was VERY slow. I decided I'd just go back to cm v 4.2.9.1. I went to wipe and reflash, but the G1 screen never disappeared. I let it load for about 30 minutes and decided that was a bit ridiculous before removing the battery (mind you, it never got past the T Mobile G1 screen). I was, however, able to reflash KiNgxKxlicK AOSP 2.1 rom and run it. This is all I am able to do. When trying to reflash cyonagen it just hangs on the G1 screen.
I'm a noob so I don't know what went wrong or what I missed.
Can someone PLEASE help me out here and tell me what I need to do to fix this. Thanks
Additional Notes:
Can't get to settings running KiNgxKxlicK AOSP 2.1 AT ALL, and a lot of programs Force Close on the rom.
Thanks for any help/input you guys can provide.
Thanks
Do you have Amon Ra recovery?
No I do not believe so, as I am not exactly sure what that is?
UPDATE: I should also note I checked my SPL and Radio, both were very old (as I realized I followed an OLD guide when I rooted my phone)
I upgraded to the latest radio and SPL and still have the same problem...except King's rom doesn't force close when I go to "settings".....thats about the only difference (still slow/laggy, lots of programs still FC)
When you boot into recovery (holding home+power) it should tell you what recovery image you are using. (i.e. mine says v1.5.2 down at the bottom of the screen) I ran into a similar issue when I attempted to jump between roms without taking all the appropriate steps; all I did was reformat my sd card, wipe the phone, and reflashed my rom and it worked great after that.
I tried reformatting my sd card, even re-partitioned it and I'm still having the same problems:
CM wont get past g1 screen after flash, King's rom still pretty slow....
What do you gys recommend I do next? This is getting really frustrating
1st: Check if youre Formatting is correct
2nd: Wipe EVERYTHING
3rd: Re-Format
4th: Try downloading the ROM again. It could be an issue with the ROM's
5th: Check you have proper radio and SPL (1.33.2005 and 26I)
6th: Pray
Try them all hope one of them works for you dude.
why is it that that 99% of newbs are on cyanogen
@Macrophage001
1. how do I CHECK my formatting to see if its correct?
2. Doesn't formatting do this automatically? I also "wiped" in recovery...
4. Not the roms, I have multiple CM roms, one of which I've had for some time with no problems and have re-flashed over and over
5. As stated above, I did not have the latest at first, i did upgrade to the latest radio and hakyuro(sp) spl to no avail.
@zachattack052
We've all been told it's THE BEST, much before even making the decision to root. I honestly thought CM was the only rom available, that's how much he's praised around here and other forums.....it's just what everyone tells us.
Here's what i suggest you do:
1> Download Amon_RA's recovery from here
here is a link to his thread
2> Transfer the file you just downloaded to the root of your sd
use this code to mount your sdcard from recovery console itself if needed
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
3>Disconnect usb and reboot to recovery (keep home pressed while powering on) or just type
reboot recovery if you are already in recovery console
4> Flash Amon's recovery:
Code:
#mount -a
#flash_image recovery /sdcard/recovery-RA-dream-v1.5.2.img
when complete, reboot to recovery again
5>Partion your sd using amon's recovery (All data on SD will be lost so backup if needed)
[Alt+P] then [Alt+0] or scroll down using the trackball or the volume keys
follow the prompts, set your swap-size to 96 MB (use the vol keys) and 512 MB ext2. when done use the back button to go back and reboot
The above step will give you the partitions required to run any rom. Please make sure you meet the radio and SPL requirements before flashing a rom.
6>Transfer the latest CyanogenMod rom to your SD and flash it.
I would suggest that you try bbuchacher's SuperD rom (it requires Haykuro's Danger SPL)
make sure you flash the radio first and then the SPL if you dont already have it
P.S. When anyone says full wipe, they mean doing a factory reset, wiping your ext partition and wiping the dalvik-cache. These are the first 3 options in Amon_RA's recovery's wipe menu
what i would do....
make sure you flash the HTC recovery files first before you flash the CM rom
go for the defanged version of HTC
so...(once u have amon ra's latest recovery installed)
wipe everything
flash htc / defanged (DO NOT REBOOT!!!)
flash cm latest rom
ALLOW IT TO LOAD FULLY
reboot (personal preference)
create a nandroid backup for future **** ups
enjoy ur rom!!
j.
airmcnair06 said:
@Macrophage001
1. how do I CHECK my formatting to see if its correct?
2. Doesn't formatting do this automatically? I also "wiped" in recovery...
4. Not the roms, I have multiple CM roms, one of which I've had for some time with no problems and have re-flashed over and over
5. As stated above, I did not have the latest at first, i did upgrade to the latest radio and hakyuro(sp) spl to no avail.
@zachattack052
We've all been told it's THE BEST, much before even making the decision to root. I honestly thought CM was the only rom available, that's how much he's praised around here and other forums.....it's just what everyone tells us.
Click to expand...
Click to collapse
1: Go to recovery console and type parted. A list will show up with your fat32,ext2/3/4,linux-swap settings.
2: Yes it does but you can never be too sure.
4: ok
thanx guys I followed the instructions MrBurrito and cqms13 gave and am now running the Super D rom just fine.
Thanks again!
very quick question..
did you wipe dalvik-cache?
Firerat said:
very quick question..
did you wipe dalvik-cache?
Click to expand...
Click to collapse
After installing the RA recovery, yes. I was running CM Recovery though when I began this thread, which is why I was not able to wipe dalvik
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
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.
I have been running Cyanogen 4.2.15.1 for a few months now, I recently noticed that 5.0.7 (test5) for the G1 was released, and am trying to get it to install.
I follow the various steps to install, I have DangerSPL installed, then Cyanogen, then the Google Apps, and the install procedure seems to work correctly.
It hangs on the G1 screen for a long time. I read that 5-15 mins for a first boot is normal but I have had to on 30+ mins.
I can reboot into recovery and install 4.2.15.1 again, and it works like a charm, I wipe and try to install 5.0.7 (test5) from a fresh 4.2.x and no luck.
Has anyone had any similar problems or know of a way to solve them?
thedevilsjester said:
I have been running Cyanogen 4.2.15.1 for a few months now, I recently noticed that 5.0.7 (test5) for the G1 was released, and am trying to get it to install.
I follow the various steps to install, I have DangerSPL installed, then Cyanogen, then the Google Apps, and the install procedure seems to work correctly.
It hangs on the G1 screen for a long time. I read that 5-15 mins for a first boot is normal but I have had to on 30+ mins.
I can reboot into recovery and install 4.2.15.1 again, and it works like a charm, I wipe and try to install 5.0.7 (test5) from a fresh 4.2.x and no luck.
Has anyone had any similar problems or know of a way to solve them?
Click to expand...
Click to collapse
first off bro never flash it direct on top of a rom your not sure of. but all u gotta do is :
wipe all 5>flash danger spl>wipe data factory only>flash test5>flash google app add on>reboot.
if this fails then u jus need to start from rc29, re-root, flash test5.
i kno for a fact this works. if u still need assistance feel free to pm my profile here on xda and ill reply asap.
goodluck and enjoy
Ok here is what I did, I flashed Amon_RA's recovery image (I was using CM), wiped everything with Amon_RA and installed DangerSPL, CM 5.0.7, and the Google Apps, and this time I was greeted with the nice new boot logo!
I dont know if it was just bad luck on my part of if the CM Recovery Image is not a good choice for installing 5.0.7?
thedevilsjester said:
Ok here is what I did, I flashed Amon_RA's recovery image (I was using CM), wiped everything with Amon_RA and installed DangerSPL, CM 5.0.7, and the Google Apps, and this time I was greeted with the nice new boot logo!
I dont know if it was just bad luck on my part of if the CM Recovery Image is not a good choice for installing 5.0.7?
Click to expand...
Click to collapse
so it worked or no ???? lol hope it did and always wipe after installing danger spl jus heads up for next time
Yes it worked, I have 5.0.7 (test5) successfully installed, thank you.
Hello again. Like in subject.
Issue happened when i tried to flash Liberty 5.1 ROM. Well i did not read all requirements ;/ - but i do have a nandroid backup that works like a charm (and i don't know why?)
specially about Radio: 2708+ and SPL: 1.33.0013d.
So i flashed it on Radio 26.91i and Hayakuro's SPL.
Than i read other requirements
3) Flash recovery-patch.zip.
So Dream was stuck in G1 logo. After super wipe i deciced to make 3) Flash recovery-patch.zip.. So i did. Still stuck on G1 logo. So i used this CMTD removing zip and i deciced to flash Radio: 2708+ and SPL: 1.33.0013d.. SO i did. Still nothing. i cannot flash any rom. Even DRC83_base_defanged gives a G1 stuck. Even logcat is't ready at the moment, and i cannot reboot it via SEND+Menu+END... battery removing, restoring nandroid, and on the road again.
Well i am stuck right now in 1.6 SuperD with RamHack, Radio: 2708+ and SPL: 1.33.0013d., 128 SWAP, 512 EXT which is superior fast, but i'd like to test other roms from time to time, and i am wondering why the device is being blocked on other roms. MTD should be restored, and even if i flash other rom on my nandroid backup (i remamber it should normally give bootloop) i am stuck with G1 logo.
If anyone could help me with this issue it would be super. I flashed many things to my G1 over the years (and this is third G1 ) but i have never been is situation when logcat shows -waiting for device-...
PS: i never got LIBERTY rom working :/
I have installed BananaBread 4.0 by Banana4444 and i think it's working. Logcat talks to me like crazy, Bootanimation breaks the glass. I wonder why...
Well i can see desktop
After a while playing with dekstop i will try to install something else and check if it will work.
Sometimes the remove.zip doesn't seem to work, I noticed that sometimes it needs to be flashed twice to get it to stick. You can always flash amonra again just to make sure.
Does adb work when you are using super d right now? If not then you probably have a driver issue. If it does then make a nandroid (sounds like you did) wipe all, supperwipe, fastboot -w, grab a known stable Rom (maybe ezgingerbread or froyobylaszlo) and flash that in recovery along with any gapps/kernel/etc. (Froyobylaszlo has gapps and kernel packaged with the Rom so try this one as nothing else needs to be flashed)
Sent from my Desire Z using xda premium
Sometimes the remove.zip doesn't seem to work, I noticed that sometimes it needs to be flashed twice to get it to stick. You can always flash amonra again just to make sure.
-Well i tried to flash it once, and after i sent AmonRA via fastboot. just to be sure its clean. It gave me no effect.
Does adb work when you are using super d right now? If not then you probably have a driver issue. If it does then make a nandroid (sounds like you did) wipe all, supperwipe, fastboot -w, grab a known stable Rom (maybe ezgingerbread or froyobylaszlo) and flash that in recovery along with any gapps/kernel/etc. (Froyobylaszlo has gapps and kernel packaged with the Rom so try this one as nothing else needs to be flashed)
- i tried to flash Defanged, superD, super E, superF, CM5,6,7,9,10, FroyoByLaszlo, Liberty, CronMod, Superfast and chromatic - every gave same effect. I have nandroid via recobery, and logcat works every time. just new flashed roms are stuck before logcat can be run from /system.
In the evening i will try Laszlos rom and i will post results here.
Dude. Are we the last G1 forum readers?
_________________________________
EDIT:
Now everything works... so just need to be on newest updates.