Database Develop

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.

Phone stuck at G1 Screen

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

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.

[Q] G1 wont boot

Following this thread: http://forum.xda-developers.com/showthread.php?t=1098899
I was able to do everything except install the hboot0013d.zip; it kept on comping up saying to many firmware found & wasn't able to store hboot.
if I go to fast boot right now my phone says
dream pvt 32b eng s-off
hboot- 1.33.2005
radio 2.22.27.08
I tried installing cyanogenmagpie but that wont work; the phone is stuck in a loop where the t-mobile g1 logo comes up for about 2 minutes then it resets; Idk what to do
any help will be greatly appreciated...

did you wipe the device? try flashing ohsaka superwipe than flash the hboot file..

following ldrifta's advice, I was able flash the hboot file and flash the cm7 magpie rom. It took for a while but it booted. Now the problem is that the rom wont let the phone part of the phone work. I keep on getting a force close about the phone & messaging once i boot it. I'm sorry for all the problems guys, any help would be appreciated again

that sounds like its the rom... try another rom lol if you still have the same issue than your sim card may be messed up, happened to me before. just out of nowhere it stopped working..
ps. make sure you wipe system, data, cache and sd-ext each time before flashing roms...

lol what rom would you suggest?

uhhhmmmm depends what you like... froyo, sense, gingerbread.. lol list goes on and on... but uhh
1. froyo by lazslo
2. EzGingerbread
3. SenseLX
4. FroSense
5. Magic sense
6. COS GB
7. AOSP 2.2
i think froyobylazslo is the only rom you need to flash a 2708 kernel with... but it worth it

(Issue) G1 T-Mobile (ERA PL) Cannot be flashed with any ROM

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.