Database Users

What the hell...?!?!?

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

[ROM] Bonsai User Discussion

This post is only for discussing all issues regarding the use of the Bonsai roms. We can talk here about any version from 1.0.0 to x.x.x
Due to some political issues please do not post any links to the Bonsai website! This thread is just for us users and don't expect the developers of Bonsai to ever visit here.
One last thing >
nor

Yes this try to keep this thread open.
Sent From My Evo Killer!

So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Sent from my SPH-D700 using XDA App

I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force

forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Were you using CWM 3.0.0.6 or 3.0.0.5 ?
Sent from my SPH-D700 using Tapatalk

Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?

abrcrmdl23 said:
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Click to expand...
Click to collapse
I can't remember what stepping is on the kernel as we have been beta testing 4.0.1 and have been mainly dealing with a new setCPU governor called interactive. Were also still working on the other governor called smartass as well. I think that the stepping goes directly from 400 to 800, but we are always looking to go faster and with better battery life. I'll bug Randy and Mammon about it.
The sound will be Voodoo version 7, but I don't think the Voodoo color fix is going to make it into 4.0.1. Sorry, but we can't do everything...at least not all at the same time.

forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Did I see a similar post on the Bonsai website earlier today? I just want to verify that you were using CWM 3.0.0.6 as anything else will cause problems like that. Also when you get to these kinds of problems you should attempt a second flash of Bonsai before going to the trouble of a ODIN job. A second flash seems to fix a whole variety of odd kind of problems.
As you can imagine with all the beta testing I do I'm always finding ways to corrupt my phone. Some days I have managed to bork it 3-5 times.
I decided to test out today a 4.0.1 install directly from DI18 > CWM 3.0.0.6 > Bonsai 4.0.1 full rom. It went great with no problems at all and running just fine, so far

I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0

bluetooth
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?

forcelite said:
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
Click to expand...
Click to collapse
Do not use Rom Manager to be installing the beta CWM files. The correct way is with one of the 1 step CWM tools in the development forum. 3.0.2.4 is half-finished and is very difficult even to navigate through the various menu's. I know this because I tried out that CWM version for some grins one day. It will majorly screw your Epic if your not extremely careful. When DI18 was prevalent Rom Manager worked great to root your phone. When we started the move into the Froyo roms Rom Manager quit working and that is why the 1 click then became more prevalent.
Just follow the directions posted all over the place and Bonsai will install just fine and you will be a happy camper.

I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Thx All,
Force

forcelite said:
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
Click to expand...
Click to collapse
The linked one is the correct one for Bonsai version 4.x.x.

olddocwhite said:
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
Click to expand...
Click to collapse
Some people do and some don't I do know that Randy has instituted quite a few bluetooth linux upgrades into 4.0.1 rom. Some people are able to clear the data, but the problem usually reappears. Mattalica76 has the link to a more permanent fix to this problem, give him a PM.

Duplicate... Sorry

forcelite said:
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Click to expand...
Click to collapse
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.

Actually it didnt boot this time either, it installed the firs ttime fine, then kept booting after samsung in a loop,
So I went into CW3 and tried to flash bonsai 4.0.01 again and it gave me this error. It is long, however I shortened it, I have the whole error photo copied)
Finding package
Opening package
Install update
Assert failed getprop (“ro.product.device)”)
Sph-700
E:error in /SDcard/bonsai……….
(status 7)
Installation aborted

Top Nurse said:
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Click to expand...
Click to collapse
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.

forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
CWM3 will convert your filesystem to ext4 the first time you boot into it. It won't touch the sdcard so that won't be converted. After CWM is finished with the conversion, do not reboot the phone, you will then flash Bonsai.

forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
After flashing the boot script of cwm 3.0.0.6 you then have to power off. Then hold down the camera button, vol down, and power keys at the same time and the EXT4 script will automatically start to format your system. Please keep in mind that it is not formatting the SD card, but only the read only memory of the phone.
After you finished a few beers it will be done and will drop you back to cwm. Do not reboot, but flash bonsai. After bonsai is finished then reboot.
Sent from Bonsai 7.0.3

[Q] 2.3.3 OTA Rooted problem...

Hey I would have posted this on a different thread but i cant because i just made this account they want atleast 10 posts...
heres the deal... i have a rooted evo and running cm7 which i like, but i was dropping calls and where i live i should have good service. so i got the updated radio/wifi/ ect package and flashed it... it installed but did not help with the call issue... i heard many other having the same problem.
so i flashed the ota root update... which seemed like it did it really fast (wasnt watching the whole time) and the phone rebooted but gets stuck at the white htc evo screen, i let it sit there for 20 mins nothing, so right now i am recovering my old cm7... just wondering if anyone has that same problem or can help with getting better voice reception on cm7.. like i said i have tried the package for radio ect... and my prl was updated before i flashed to stable of cm7 so that should be in good standing i would imagine... thanks..

The obvious first question is, did you do a full and complete wipe of everything before you flashed the ROM?
As far as your signal, it may have been just in my area, but I know a few people that had problems texting and making calls, getting a "Network Is busy" error.

yea i did the wipe data/cache i wasnt dropping calls before the cm7 so im not sure right now im shootin to myns seeing how that is... cm7 was first flash i did
well as im trying to flash to the myns its looking like the samething... ill go through the steps...
have zip file in root of sd card
open up rom manager, have the newest clockwork thing installed
i goto flash from sd wipe data and cache are checked... i already have a backup so i skip that part
it installs.... says install is done and reboots itself... but seems to stay on that white bootscreen
if i take the battery out then i can reboot with recovery from the save file i have

blah i dont know... i got the ota installed... looked like it got a bit better reception.. i updated prl and came back to cm7 same probs... i dunno maybe ill just have to let go of cm7... really dont want to though its so sexy lol

I had the same weak signal issue with cm7 and had dropped calls and data dropping to 1x. I am on stock rooted 2.3.3 and reception is good again. Liked cm7 but need a phone I can use in the boonies.
Sent from my PC36100 using XDA Premium App

Dude, please, don't use ROM Manger.
Just boot to recovery, hopefully, you have Amon Ra, if not, search how to get it on your phone, it's not hard, do a FULL WIPE, full, wipe everything in recovery, then flash the ROM in recovery.
No offense to the Dev, I know he's a great guy, a smart guy, hard worker that makes a contribution, but Rom Manager is not the best way to do this.

Yea had to do it manually but nymph works now liking it so far

ok now i have different problem.... got the myn working liking it, but my market is completely different, not just the theme, but the apps i usually download... so tried to flash new market but it just open/closes quickly... any ideas for that?

Not sure by what you mean by the apps you usually d/l.
One thing about the Market in these newer ROMS is that sometimes, you just need to give it some time to fully sync before all your apps so up...
You should pull the market out of the zip file for the ROM and re-install that one, but you'll have to delete the one you have installed now, first.

umm usually download ninjump cant find that just some games that are usually on my phone the market on cm7 had them... ill give it a try though

look on the android market website

[Q] [CM7] Diagnosing constant freezes...

All...
Looking for some guidance before I go complete wipe/reinstall.
After months of rock solid performance, I'm getting constant total freezes with CM7. I don't have a whole lot of apps, maybe 30, and don't use Beautiful Widgets (I believe I've seen that mentioned as a possible culprit.) It seemed to be somewhere around when I flashed the newest version of Gapps (0828,) but I can't confirm.
Just to try, I flashed the newest nightly of CM7 and reflashed the older (06xx) version of Gapps. Same problem. Thought it might be a bad SDcard, but removing the card still gets freezes.
Nothing consistent - sometime it'll go for hours with no problem. Sometimes it's 2 minutes after I reboot.
So I'm looking to clear and restart. Any suggestions? Should I backup and restore the apps from Titanium Backup, or is it safer just to reflash and reinstall everything fresh from the market.
Any other recommendations?
Many thanks!
Adam

Have you tried fixing permissions?
Sent from my LG Optimus V using Tapatalk

koopakid08 said:
Have you tried fixing permissions?
Click to expand...
Click to collapse
Yes, and should have mentioned that. Have also taken overclocking from 1200 On Demand down to 1100 Conservative, though 1200 was completely stable for quite a while. No dice.
Thanks.
Adam

Thought it might be a bad SDcard, but removing the card still gets freezes.
Click to expand...
Click to collapse
I assume that means you are running CM7 off the eMMC, correct?
How are you flashing? ROM Manager? Download the .zip to the SD card and boot into CWR? When you flash a ROM do you wipe Davlik? What version of CWR is on your device?

patruns said:
I assume that means you are running CM7 off the eMMC, correct?
How are you flashing? ROM Manager? Download the .zip to the SD card and boot into CWR? When you flash a ROM do you wipe Davlik? What version of CWR is on your device?
Click to expand...
Click to collapse
Yes, running of emmc.
Originally flashed a nightly (current as of, maybe, 2-3 months ago) using bootable SD card into CWM. I updated early last week using a flashed CWM but with CM7 image on a card. Also updated to the latest nightly yesterday using ROM Manager.
Current Version: 0930 (207, I believe)
Yes, wiped Davlik each time.
Thanks.
Adam

Actually, after many months of rock solid Nook performance using CM7 and Phiremod and MIUI I've experienced a lot of random freezes the past couple of weeks no matter what ROM I'm using. I wonder if my hardware is becoming unreliable. I've scrubbed and wiped every element of the device before doing new ROM installs, changed SD cards, re-downloaded ROMs. Installed CM7.03, CM7RC1, CM7 nightlies, various MIUI iterations, all to internal memory. My Nook will run anything smoothly for a few days and then start freezing no matter what I do. I do use Beautiful Widgets so I'm not running that right now, just in case. In fact at the moment I have NO widgets, shortcuts or anything else on my homescreens, just to see if that helps. Yes, I've tried fixing permissions too. A head scratcher.

lesdense said:
Actually, after many months of rock solid Nook performance using CM7 and Phiremod and MIUI I've experienced a lot of random freezes the past couple of weeks no matter what ROM I'm using.
Click to expand...
Click to collapse
Well that's not promising. Hopefully I don't have whatever syndrome you do.
I'm going to do the full wipe this afternoon and see what happens with a fresh install.
Adam

I have come to believe that my problem was NOT with whichever ROM I was using but with Beautiful Widget. Using the usual trial and error method I found that, if I did not install Beautiful Widget I didn't have a freeze problem either with MIUI 1.8.5 or CM7.1RC1. Its a shame because I like that widget but I switched to Fancy Widget (a lot less flexible but gets the job done) and I'm fine now.

For some reason certain apps just don't play well with the Nook. They will freeze it regardless whether they are running or not. Simply having them installed will cause frequent freezes from my experience. Everytime I encounter more than two freezes I will delete the last 5 or so most recently installed apps.

@stir fry alot,
Is there an app that keeps track of installs?

I had a similar freezing issue..I had to reformat my SD card and reload my apps...took care of it.

Thanks guys!
I'm running 7.1 stable that i installed from scratch on SD and kept getting freeze ups too and stumbled across this thread and wanted to say THANK YOU! I uninstalled beautiful widgets and no more freezing! Whoohoo!

v7 bootloader effecting performance?

hi again guys as you have prob' seen in my last post i recently updated to the v7 bootloader and 1.7thor recovery.
since i updated the bootloader, ive had a few probs like the unreadable files showing up in my internal memory, my sd card deleting most of it contents, google play showing tracks i no longer have on the tablet.
i have also noticed that google music has begun to flash/glitch and last night g-music totally blacked out my screen after a load of flickering i was worried but the tab seemed to work fine just the app went crazy.
another issue is i tried to install a game (nova 3) and when i clicked install it said i did not have enough memory,,....but i have 22gb free?
so i tried another .apk and installed fine,.. could it be the .apk thats the problem? its just weird because you would think the game just wouldn't play, not give insufficient memory warning before installing?
another question i have is, if i made a nandroid backup using the teamwin recovery 2.x can i restore the nandroid that ive flashed the thor 1.7 recovery?
flexreaper R12.5
v7 bootloader skrillax
1.7 thor recovery

version?
I am not sure if the version of flexreaper you have installed supports the ICS bootliader...? Are you?
m.

You need to update your rom, you are about 20 revisions old and I don't think you have the right boot.img installed to make your bootloader compatible with the FR 12.5 rom you are running. You should have stuck with the HC bootloader if you are using such an old rom.

cruise350 said:
You need to update your rom, you are about 20 revisions old and I don't think you have the right boot.img installed to make your bootloader compatible with the FR 12.5 rom you are running. You should have stuck with the HC bootloader if you are using such an old rom.
Click to expand...
Click to collapse
i was on v2 ics bootloader before? and civato recommends using a ics bootloader for flexreaper? also the boot.img was replaced by civato .....sooooooooo i dunno?
note/update:
i found the files in the internal it was in a download folder from torrentz4android, i deleted them and got all space back and play music now displays all the correct information had to delete a lot individually . the nova 3 install problem was found to be a glitch with ICS actually , i cleared dalvik-cache and the apk install no problem
update
ok i seem to still be experiencing problems from the touchscreen once becoming unresponsive to apps freezing and my back/home buttons disappearing?
can using a new bootloader produce these problems or could it be a bad titanium backup?
hope this information helps others who come by this problem.