Force Closes? - myTouch 3G, Magic General

Hi, I have a MT3G and a G1 before that. I have experience flashing roms and other stuff. I have had the MT3G for sometime and noticed that I can't flash roms anymore since I get FC errors after the boot up. Even the latest CM mods don't let me sign in, and I have to skip the initial sign in to find the market FCing every time I open it. This is getting really annoying, and some roms won't even get past the boot screen without a fix uid mismatches which allows me to boot up, but still gives me some errors, like no android keyboard to sign in or FC on settings or other important things. Any help would be appreciated!

are you wiping the phone completely... list things in your signature like what recovery image what rom you are using at the time are you using a different SPL the community needs to know these kind of things to help you out...

I had this same problem when trying to flash Cyanogens latest.
Go ahead and find version 4.2.1.8 or 4.2.1.9
Wipe everything, then flash one of those.
Everything should work, I would advise not to upgrade to 4.2.12.2 or whatever because I experience home not responding upon reboot. Have to wait a couple times, then it's ok.

Well, I would put it in my sig, but for some reason, I can't edit it. Here's what I've got.
I had the SPL 1.33.2005 then recently 1.33.2009.
I've had problems like this on my G1 as well and never really understood the problem. I have the latest RA v1.5.2 recovery.
I do perform a full wipe and have tried to follow what someone else posted about installing a fresh rom and to fix the apk uid mismatches and a command in terminal, although neither seem to last long. Sometimes I can wipe and do an install of any rom 10 times and still get FC on startup. I fix the apk uid mismatches in recovery to be able to get further, but will usually start to have problems in other settings and apps.
I have a general idea on what to do, and usually wipe the data and everything else about 2 times. I just don't know if it's something I'm doing that's causing this.
I just searched around for the differences of SPL's and read from Amon_RA that they aren't really different besides being able to allow certain roms to run. I'm wondering if the reason I can't run certain roms is because I don't have Haykuro's Death SPL? Is the Death SPL only .2005?

Related

recently rooted phone, troubles installing roms

I've been reading these forums for quite some time folowing H's and JF's builds and just seeing what the devolping community has been up to.
I've been wanting to root my g1 for some time but didnt ever make the jump till now. I read through the Helpful Thread / Build Round up started with in the beginning there was root as well as the How-to- Root, Hack, and Flashing your G1/Dream and decided i could do it. i followed all of hte steps with ease. had my phone rooted within 20 minutes the first thing i wanted to do was to get a new rom with cupcake but i also wanted to be sure not to mess it up so i read through nandroid and was a bit confused as to what all was needed so i figured the recovery img that the tutorial gave was fine since everything i had done was no problem. i then went to H's ion thread and saw that i needed a differen spl so i went and read about those and decided with hardspl got that applied no problem. i downloaded the ion rom renamed it to update.zip put it on my card and loaded up recovery mode pressed alt+s to apply it and everything went fine till it hung at the 2nd boot screen. a little disheartened i went into the spl using camera+power and flashed the recovery img. i read around the forums seeing if i did anything wrong and couldnt figure it out so i tried a different rom this time one of Jf's early roms i think it was rc33 i tried to apply that but i got a no signature verication failed at the recovery screen so i tried some others. JF's 1.51 and same problem. i read around some more and thought maybe it was because i didnt do alt+W so i tried that with JF's roms and both of the leaked hero roms (i know hero is extremely unstable but i just wanted to see if something entirely differnt would work.) by this time i go into the spl again and saw that the hard spl wasnt loaded any more (i guess the recovery img changes that) i reloaded the recovery img once more and tried to install a the 2nd Ion rom with H's root apps and still the same problem.
i really try to read and search before posting but after 4 hours of nothing i really just want some help. if someone could help me get a working rom on my phone preferably H's new Ion rom and tell me what im doing wrong i'd be endlessly great full.
Im guessing what happend was you did the switch of releasekeys to testkeys and then later redid the DREAIMG.nbh. If so you need to redo the steps involving testkeys. This is why it gives the no signature verification error.
In fact id suggest redoing the whole root process again. starting with the DREAIMG.nbh.

Stuck after flashing

Hey guys, I usually try to avoid asking for help because I can usually find several topics to guide me on how to do thigns, but today I find myself completely stuck. So here's my story:
A couple of days ago I was running cyanogen's 4.2.4 rom. I had ended up with some bugs like not syncing with gmail and it was giving me 3-4 hours of battery life while idle and everything turned off. The previous rom had none of these problems. Anyway, I heard about Dwang's and decided to try out v1.11 of his rom and loved it. However last night when I tried to flash to version 1.13 it froze on my rogers screen. My last nandroid backup was the one made on the cyanogen rom. I spent all day fiddling around trying to do everything to get anything stable to run and now tonight I ended up overwriting the nandroid backup and now it can't boot anything up other than the fastboot and 1.4 loader. I've tried wipes loading older roms, newer one (both dwang and cyanogen)
I don't wanna touch anything else for tonight in fear of bricking my phone but I'm hoping someone can help. It's not bricked, but I feel at this rate and how frustrated I am I have a feeling that might happen and I want to avoid it.
I know there are some other topics that may be similar because I've done a search but I'm not exactly 100% that the solution given to them might be used for my problem as well.
DREAM PVT 32B ENG S-OFF
HBOOT-1.33.2005 (DREA210000)
CPLD-4
RADIO:2.22.19.261
Ok well, I seemed to have made things a bit worse somehow. Now when I hold camera+ home it brings up a triangle with an exclamation mark and a phone logo. BUT I'm still able to fastboot.
Did you boot on the ADP 1.6 ROM?
Yes I did as it was one of the steps on cyanogens wiki. I even tried to flash it without flashing cyanogen's rom and what it does is just show the android screen, then when it finishes loading it goes black for a split second and then goes back to the android screen. I managed to load older nandroid backups of cyanogen again but whenever I try to flash the 1.6 and then either dwangs or cyanogens it doesn't work. I also cannot do fix_permission at the recovery screen. it tells me something about e2fsck.
Here some of the things I've tried today on the phone without any success:
Another thread had a similar problem and one of the tips was to fastboot and do
fastboot flash radio radio.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-RAv1.3.2G.img
so I tried that and now I am equipped with the ra recovery and when I try to flash the rom it still doesn't work. I also let it hang for about 20 minutes before trying something else.
I've also flashed it to 1.6 htc stock and it works but it doesn't let me have the proper recovery screen and whne I try to update with a renamed rom file it says installation aborted.
So now I feel stuck :-(

g1 keeps restarting

starting a couple days ago, my g1 would restart on boot for no reason. It gets into the phone OS and says preparing SD card and then it vibrates and restarts. I've even unrooted my g1 and rerooted just to make sure everything is perfect and nothing is wrong using the cyanogenmod wiki. I have the latest radio/dangerSPL yet this keeps happening. my phone only boots when its not rooted in 1.5 or 1.6. I'd give more info, but I need some help doing that. I even made a useless video for you to watch my problems. http://www.youtube.com/watch?v=kyAOAPAhq2U
I'm assuming you're not overclocked since you haven't got into the os to set anything up. What rom are you trying to use? Prob. be a good idea to post your fastboot info. A useful thread that might help getting into fastboot and learning the commands to flash through fastboot.
http://forum.xda-developers.com/showthread.php?t=532719
Another question: What SPL do you have installed / what is you space on /system? You have to use DangerSPL, or better: 1.33.2003 in combination with the custom-MTD method to get cm6 running. (Links can be found in my signature)

[Q] Help from the Pros - man you guys (gals) are smart!

Have been trying my best to figure this out, but so many steps. Lame I know but...
I've got a Rogers 32A SPL 1.33.0010 SAPP50000 3.22.20.17. After buying it used with a Hero ROM almost a year ago, I managed to flash CM6-FroyoRedux-1.6-32a which worked (great!) for almost a year. Lately it has been getting really flakey with lots of FC and problems connecting to wifi.
So I thought a re-flash of ROM should fix things up. No luck, same problems. Super flakey, lots of FC (even with base install). Does that mean I have a hw problem?
So thought I would try another more up to date ROM. Tried CyanogenCARZ-7.1.0... and Ginger Yosi 1.2.1 and a few other but none would flash properly (Recovery on the phone is ClockworkMod Recovery v2.5.0.1 - is that the problem? If so can anyone direct me to easy steps to change this? Found some others but me to dumb, or they to hard to follow b/c no luck. I have done ROM messing about for years, more recently with Dell Streak, but it seemed to be much easier.)
Questions:
- If i can get this far, does it mean my phone is rooted?
- I hear I have a 'Perfect SPL', but if the Hero and the CM6 ROM could be flashed, does that matter?
Where should I go from here?
Thanks for your help, and sorry for being so dumb.
Don't worry, it's natural to have questions whwn confronted with such a confusing phone. I would recommend going to the RUU sticky in the development section, and flashing back to stock. If you still gets fcs and the like on stock, it is likely a hardware issue. Otherwise, we can just reroot and flash another custom rom. Let me know how it goes!
Sent from my Sapphire/dream using XDA App
What you need is a simple (full)wipe.
The problem when applying new roms or re-flashing the same rom is that the userdata and cache partitions are not cleaned.
Userdata = all the app and settings you have accumulated through the years.
Cache = as the name says.
When the partitions are not wiped, then complication can and most likely will occur when (re)flashing roms.
So, inside the recovery, chose to wipe all the partition you can find. Then you flash the rom you want. Wait 5-15 min for it to load and you should be good to go.
paulheth said:
Questions:
- If i can get this far, does it mean my phone is rooted?
- I hear I have a 'Perfect SPL', but if the Hero and the CM6 ROM could be flashed, does that matter?
Click to expand...
Click to collapse
Rooted = have SU binaries... my guess = YES you are rooted.
Perfect SPL does not influence rom flashing since you are working from recovery.
If you are flashing from fastboot, then SPL will have a dominant position.
Looking more like hardware.
Seems it may be a hardware issue? Even with the stock RUU rom from HTC there are still sim recognition and wifi flakiness issues.
Any chance a radio re-flash/update would help?

What am I doing wrong?

Got S-Off, Superuser is installed, and AmonRa is installed. When I try to load the Evo-Deck the ROM and Gapps load with no errors. When I try to start up my phone it does the white HTC screen then goes to a black screen that says ANDROID with flashing blue letters and just sits.
I've been searching around and can't find anything, but blackscreen and android aren't exactly narrow search words on here. Is that android screen Evo-Deck trying to load or is that some kind of generic android screen that pops up when there's not ROM loaded?
Think I got it figured out ... I wasn't wiping EVERYTHING. Apparently something I was missing was causing problems. I got EVO-Deck 1.0 to just boot. Hopefully I can get the newer version to work now.
For future reference, check my sig for VRsuperwipe. Flash that like you would an app, and it wipes everything.

Categories

Resources