Related
So I've got my phone rooted with Cyanogen 5.0.8 DS loaded up and running fine. I wanted to mess with OC'ing so I followed these directions but started only getting a black screen after the splash instead of the animation. After already having Cyanogen installed I tried flashing the boot-cm_2634_ds_32a-oc-uv-fp-061710.zip kernel and couldn't get the phone to reboot with the previously mentioned problem. So I did a complete wipe, reflashed Cyanogen, reflashed the Google Apps, and then flashed the OC kernel with the same indications. I'm pretty sure I'm suppose to be using the 32A kernel, am I wrong? Also, will just running SetCPU work or do you have to load the kernel as well?
DonJuan692006 said:
So I've got my phone rooted with Cyanogen 5.0.8 DS loaded up and running fine. I wanted to mess with OC'ing so I followed these directions but started only getting a black screen after the splash instead of the animation. After already having Cyanogen installed I tried flashing the boot-cm_2634_ds_32a-oc-uv-fp-061710.zip kernel and couldn't get the phone to reboot with the previously mentioned problem. So I did a complete wipe, reflashed Cyanogen, reflashed the Google Apps, and then flashed the OC kernel with the same indications. I'm pretty sure I'm suppose to be using the 32A kernel, am I wrong? Also, will just running SetCPU work or do you have to load the kernel as well?
Click to expand...
Click to collapse
You don't use 32A because the Fender/1.2 is a 32A/B hybrid.
Use 32B.
Hey All,
First I want to apologize if this isn't the place for this thread or if this has been brought up before.
Now onto what I came here for. I have a myTouch 3G phone (the one without the jack) and I have rooted my phone a couple of months ago. The rooting process went fine and currently I'm running the CyanongenMod 4.2.15.1 rom on my phone. It's running fine as it should be. Now my dilemma is when I tried to update to CM 5.0.7 or 5.0.8. At first when I flashed the rom, I thought everything was fine during the setup process but then when it came to using any Google apps, none of them seem to work with the exception of GTalk and Google Maps. I've tried the troubleshooting guide where it says to do the fix_permissions but that didn't work at all. After about 3 days of trial and error, I finally admitted defeat and flashed back to CM 4.2.15.1. I also came to the conclusion that my phone will only take 1.5 & 1.6 roms whereas any roms 2.0 and above will not work correctly. I even tried to flash CM 6.0 RC1 and it got stuck at the green boot screen.
My question is there something wrong with my phone or am I doing something wrong? Has anyone else ran into this problem? Please let me know because I would love to have the 2.0 and above roms on my phone.
Thanks in advance
Did you do a full wipe and then upgrade?
Yes I did a complete wipe, even did the command that you do in fastboot
u gotta install the google pack i think....for that u will find it in cyanogen forums
If you mean by installing the gapps after flashing the rom, I've done that already. Also I've even reflashed the gapps again just to make sure and I also tried the fix_permissions and that didn't work either.
I also saw that the browser was acting funny too (not sure if that's part of gapps)
Sent from my T-Mobile myTouch 3G using XDA App
Hello,
In your sign, you're using an old rom with the old method of app2sd (on /system/sdcard/), newer rom uses /sd-ext/ but 1.6.2 recovery is not compatible with the new method.
Not sure but try to update your recovery with 1.7.0.
Good luck, Scargoll.
scargoll, i failed to mention that I'm already using Amon Ra's 1.7G recovery image. I need to update my sig (my bad). also as i stated before, i tried upgrading to CM 5.0.8 and running into issues, that's why i'm still running CM 4.2.15.1
Yup. Wrong section. I'll move to General when I get back home.
Google Addon: FRF91-MDPI-2
Mirror: http://kanged.net/mi...91-3-signed.zip
EBI1 Port:
Download: http://briancrook.ca...ebi1-signed.zip
MD5Sum: 30f00833c6b9e15027603be4cbe415cc
Are those what you tried?
jeff, if i'm correct the FRF91 Google Addon is for the CM 6.0 RC1 rom and i don't have a MyTouch 3G 1.2 32A phone to be using the EBI1 port.
Well, since you say so, your phone is just jacked.
Have you tried reflashing the whole ROM and GAPPS again? See if a different version of cyanogenmod works for you.
jeffakajeff said:
Well, since you say so, your phone is just jacked.
Click to expand...
Click to collapse
LOL...jacked how?
appledroid said:
Have you tried reflashing the whole ROM and GAPPS again? See if a different version of cyanogenmod works for you.
Click to expand...
Click to collapse
appledroid, i've tried relashing both CM 5.0.7 and CM 5.0.8 roms gapps. the roms flashes fine but when it comes to using the gapps (with the exception of GTalk & Maps), they either close without a warning or i get a app loop (GMail does that most before it finally closes without warning)
sounds to like your running out of space on a partition while flashing. try fireat's mtd partition hack and see if it works for u.
flash the 1.1 zip
flash cm6
flash gapps
flash 1.2 zip
and then reboot
chrisgto4 said:
sounds to like your running out of space on a partition while flashing. try fireat's mtd partition hack and see if it works for u.
flash the 1.1 zip
flash cm6
flash gapps
flash 1.2 zip
and then reboot
Click to expand...
Click to collapse
hey chris,
running out of space on a partition - are you talking about the space on the phone or on the SD Card? if it's the SD Card, not sure how that's possible when I have 4GB card (also it's not partitioned as of now but before I did have it partitioned)
if i follow this route, do i need to flash CM 6 or can I flash CM 5.0.8?
also where can i find the 1.1 and 1.2 zip files?
in any case, i'll try both to see what's up
um does anyone know what chris is talking about?
c'mon....anyone?
hey im not to sure why u cant switch to the latest cm roms. cause mine is doing fine on every updates.
i use clockworkmod recovery
try redownloading the rom. while downloading, watch ur downloading progress bar, makesure u have good internet connection. do not let the data connection change speed( switching from 3g to e or g) do not let phone switch from portrait to landscape.
if any of the above does happen you will have to cancel current download then redownload.
try to download cm6 rc3 - its 2.2 and it have lots of goodies. gapps are also preinstall
well i had this problem too... i was stuck on green screen... setup abort... gapps was acting up... so i did the above and everything is fine...
i hope this works for
rooted mt3g 32b cm6-rc3 htcClay 1.3
forgot to mention... since u have this problem, i recommend a full wipe... i dont kno if it is ok to flash without wipe from cm4 to cm5 or 6... flashing rom over another rom is wat i normally do... cause i hate reinstalling apps
rooted mt3g cm6-rc3 htcClay 1.3
Hello, I have had my evo for about a month and over the last week or two my phone constantly reboots and crashes. It sometimes gets stuck in boot loops and i haveto yank the battery. it seems to happen most frequently during the browser or market apps. I cannot figure why it is doing this!!!!
my phone is rooted and this has been happening on multiple ROMS including CM6, AVA froyo, baked snack, and fresh EVO.
I have wiped:
cashe
DATA
full factory reset
Dalvik Cache
battery stats adn rotate settings
I have triedmultiple batteries and SDcardsi have tried an 8GB and 16GB and reformatted both
any other ideas?
Which ROM and kernel are you using? Your description sounds like an overclock or under voltage issue. Do you get the same behaviour with the stock ROM & kernel?
Right now I am Ava froyo v7 I have used cyanogenmod Ava froyo v6 as well as baked snack 1.5-7 and fresh 3.0.1 and 3.2 same with all
I have use the stock kernel and still get rebooting with stock speeds and 400mhz
I had VERY similar problems to you (rooted, no matter what ROM I would use (even rooted stock) I would get reboots). Usually after yanking the battery I'd get a good 2 or 3 minutes, and then, particularly when using the browser, I would get a reboot. Then reboots would repeat in perpetuity. I even tried unrooting and going back to complete stock, no luck.
Note there is a thread about a code to fix some problems with GPS -- this didn't fix my problem, but it might fix yours.
So just today I took my Evo back to a Sprint store, convinced them it was a problem, they tried doing the complete RUU flash, and the reboots happened again (yay!)...and they gave me a "new refurb".
So I'm currently rooting the new refurb.
- Eckless
Could it possibly be that I am not reapplying the stock kernel before flashing a new rom how log did it take you to get a new phone?
First of all what root method did you use and did you root 2.2 or root 2.1 then upgrade to a prerooted 2.2 rom.
And if you are not following the rom install instructions to a T and are wondering why you are getting reboots then frankly wtf do you expect.
I said that because you said you were not flashing the stock **** before flashing the rom.
Typically this is not needed unless the rom creator SPECIFICALLY states it is needed.
First of all you are using some very nonstandard Rom's. Start by completely wiping and removing any custom sdcard formatting and reformat your sdcard on your pc.
It has been said and proven many times that a bad sdard can screw with your phone and make some crazy **** happen.
Then go back to the STOCK 2.2 ODEXED, not deodex, the point is to get as close to retail as possible without losing root.
Then see what happens.
Sent from my PC36100 using XDA App
Started with 2.1 1.47 OTA update and Jane followed all instructions to the dot and I have re reformated my sdcard several times with windows for both the 8 gb and the 16 gb which both work great on my droid ( which I did reformat between moving them to a new phone) I also tried using no sdcard and no difference ill try going back to stock rom but I have always been using ava froyo and baked snack but now I'm getting problems with any romI use
I am using swype so sorry for any wrong words. Any way I was also using clockwork recovery for a while and it was apparently not wiping dalvik etc. Correctly so I thought that was why it was crashing so I switched to amon Ra recovery and its still crashing so could it have caused permanent damage that can't be fixed by just wiping everything with amon Ra
Clockwork didn't cause damage...flash stock 2.2...flash stock kernel...do a factory reset...and report back...
The What: phone wont boot past the boot animation
The How: I started from kaoscinate, did a Odin restore to dj05, flashed the dj05/dl09 cwm (for both cwm & root), downloaded the rom & addons & flashed it, received no errors during install but phone wouldnt boot, went back to cwm & installed dl30 rom & tried flashing blackhole 4.0.1 again and got the same results
Current Setup: Sammy fascinate running dj05 radio & dl30 rom as released by punk.kaos, I access cwm by holding down vol. buttons while turning phone on & applying update.zip
The Rub: normally I'm able to search for my answers or just plain "dumb luck" it, but to no avail, is there something I'm doing wrong or a step I'm missing somewhere, I really want to get this up & running, thank you in advance for your time & patience
ive had this problem one time on an old rom, can't remember what one though.... anyways maybe the zip file has a corrupted file in it. Try redownloading the blackhole zip or you could always try installing from rom manager since you have dl30 installed. I beleive that rom is on rom manager...
capital advice my dear zparlet, you are both a gentleman & a scholar.
Sent from my SCH-I500 using XDA App
Does Kaos use Voodoo? If so i didnt see you say anything about disabling Voodoo before installing Blackhole. Other than that...i have no idea : )
I actually like my Fascinate
I'm currently using the wildfire. I rooted it and installed rom manager.
I did backup my rom (CWRv3.2.0) and installed the wildpuzzle rom (Newest one).
But i think forgot to wipe off the data. After installing the rom, it booted fine but it says that my phone memory was low.
I waited for a very long time but it does not respond. Hence, i thought something was wrong and tried to go to cwr and did a factory reset.
But now it gives me a black screen after the htc logo.
And after 10 to20 minutes and it still does not respond. I went back and did a restore(before the wildpuzzle rom I've installed)and it came out that my phone cannot boot and stucked in a loop. (after 2 turns it went back to cwr)
I'm scared that i might bricked my phone.
Help please! Much appreciated!
When you do a Factory Reset in Clockworkmod, you need to flash a ROM again. Also, if you read the thread completely, WildPuzzle 2.3.2 does NOT work. It was released untested by danne (as he stated), and, various tests by users show it didnt boot.
EDIT: And if you are talking about Android 2.2 Sense ROM's, you will need to flash it using Clockworkmod 2.x. They are not supported on 3.x
So do i have to flash a new rom like CyanogenMod ? Sorry, I'm a complete noob at these. Edit: Its the Wildpuzzle 2.2 froyo v0.8 rom.
Clubbysupercharged said:
So do i have to flash a new rom like CyanogenMod ? Sorry, I'm a complete noob at these. Edit: Its the Wildpuzzle 2.2 froyo v0.8 rom.
Click to expand...
Click to collapse
Yeah flash the CyanogenMod 7 ROM. But before you install this ROM please make sure to Wipe the data, Clear cache partition and also to clear dalvik cache and then proceed to install the CM7 ROM
Yes! Thanks a lot! Flashed Cm7 Nightly Builds 2.3.4. Running perfectly
EDIT: Wifi does not connect lol, stucked on locating ip address.