Can't use G. Maps Navigation after Cyanogen upgrade! - myTouch 3G, Magic General

ll, I am still running 4.2.5 on rooted Magic. I tried upgrading a while back but found that I had to re-flash the Navigation piece i downloaded here. For some reason it is still failing to show up, even after clearing cache and rebooting.
Am I missing something. The instability of 4.2.5 is starting to get to me...
Thanks

re wipe and re flash.

oshizzle1991 said:
re wipe and re flash.
Click to expand...
Click to collapse
Im aware that I have to re-flash everytime I get a Cyano update, but are you telling me I have WIPE as well?? May not be worth the trouble....

Related

Strange problem with my wife's G1...any ideas folks?

Hey guys,
My wife is having a very strange problem with her G1 - I haven't seen anything like it before.
Basically, everything is working fine except for the actual Dialer. When she goes to make a call, it just sends her back to the home screen, and her signal disappears.
Any idea what could be causing this or have any of you experienced anything similar?
She's running Cyan 4.0.4 with the latest radio, if that's any help.
no theme correct?
reflash the rom then the radio.
this is to start as fresh as possible without wiping.
Yeah, no theme...
So you're saying re-flash the ROM and the radio, without wiping?
I would wipe just to make sure everything is correct and fresh.
supremeteam likes to wipe (especially other people's wives)
You will most likely end up wiping anyways but there is a chance that reflashing the rom then radio will fix the problem without loosing any information. If you're not worries about loosing the information then go ahead and wipe, flash rom, then flash radio.
Fingerlickin said:
supremeteam likes to wipe (especially other people's wives)
Click to expand...
Click to collapse
Ssshhhhhh...Don't let the cat out the bag.
Factory reset from within the OS itself (not the recovery menu) appears to have sorted it.....! Thanks guys.
f-me
supremeteam wins
Fingerlickin said:
f-me
supremeteam wins
Click to expand...
Click to collapse
LOL.....................
Yeah just reflash. I had a lot of problems with cyanogens new rom. My phone kept rebooting, signal would go out, ect.

Fix the superuser for the Taboonay rom(Also I also fail, with suddenly lost root))

Sorry to start this thread, I find I also lost root suddenly. No clear reason, thought I power down and start many times and didn't lose. Now I have no root.
So adminstrator please close this thread
gave me an error
Tried it again, flashed rom followed by this zip, no go.
Says there was an error in /sdcard/su_mod.zip followed by an installation aborted message....
jamesnmandy said:
gave me an error
Tried it again, flashed rom followed by this zip, no go.
Says there was an error in /sdcard/su_mod.zip followed by an installation aborted message....
Click to expand...
Click to collapse
You wipe or not?
liu2002 said:
You wipe or not?
Click to expand...
Click to collapse
I didnt wipe anything. I can try wiping cache and Dalvik cache but i would rather wait until a fix comes that doesn't require a data wipe as i have things all set up the way i like.
jamesnmandy said:
I didnt wipe anything. I can try wiping cache and Dalvik cache but i would rather wait until a fix comes that doesn't require a data wipe as i have things all set up the way i like.
Click to expand...
Click to collapse
OK, I think the HoneyVillain's files are right. The best way is to replce the both su and superuser.apk directly in the taboonay rom not use the fix package.
liu2002 said:
OK, I think the HoneyVillain's files are right. The best way is to replce the both su and superuser.apk directly in the taboonay rom not use the fix package.
Click to expand...
Click to collapse
Sorry but i ran into the same problem, had root and suddenly no root annymore ive flashed as usual factory reset, format system and after this installed 2.1 so i think someone has to do his homework once again.
henk_j said:
Sorry but i ran into the same problem, had root and suddenly no root annymore ive flashed as usual factory reset, format system and after this installed 2.1 so i think someone has to do his homework once again.
Click to expand...
Click to collapse
The reson is setcpu as they said. Maybe it is.
Fix the superuser for the Taboonay rom
It would appear that the problems can be caused by the installaton of SetCPU

atrix non responsive after cm7

I was running cm7 since it was first released. I got a new phone so i decided to give my atrix to my younger brother. The problem is after i went through the process of putting the phone back to stock, there now seems to be dead zones on the phone. For example i cannot press the w,e,s, keys. Can anyone help me or tell me if i've done something wrong?
I'm not sure you did anything wrong specifically. Did you make sure the clear all the cache? How did you put stock back on it (IE. flashed stock via CWM, moto fastboot, etc)?.
Boot into recovery, wipe dalvik cache, system cache, reflash your firmware of choice, reboot.
Sent from my MB860 using Tapatalk
Ive had numerous problems with cm7 for atrix but ive found that backup everything you need with titanium backup and then just reflash the rom and wipe the data and davlik cache and it should. But yh there are lots of issues with the cm7 rom for atrix but its still in beta so dont worry too much it will be ok when there are more updates
Sam
samdrake112 said:
But yh there are lots of issues with the cm7 rom for atrix but its still in beta so dont worry too much it will be ok when there are more updates
Click to expand...
Click to collapse
The CM7 beta does not have the issues that the OP described so please don't let him think that's the reason.
OP, re-flash your phone with a different ROM or with CM7 again and see if it still persists.

[Q] Installing Stock Update with Acer Recovery Installer?

So, I'm new to the world of tablets - the only interaction with them being some light use on my mom's tablet (including rooting it via Iconia Root and installing Acer Recovery Installer v2.54) I was curious about updating via ARI (since she's rooted and being plagued by OTA popups). Back when she first got the tablet, she tried to update and it would stop mid-download, giving no error, and just sit there until she cancelled it (this was before the root). So, basically, my question is: Is it possible to run a stock update (Ie "Stock 3.1 4.010.42_EMEA_GEN3") without having to wipe during install? I have a backup via ARI and also Titanium backup installed but I'd really like to not have to re-install all the apps/set up the homescreen (she's on stock) and stuff. I know on my OG droid that when I installed CM7 I had to do a wipe for it to even get past the boot screen but I figure with this being a stock update maybe it's different...
If not is there some way that I can install an update while keeping the root/system data?
AliceInUnderland said:
So, I'm new to the world of tablets - the only interaction with them being some light use on my mom's tablet (including rooting it via Iconia Root and installing Acer Recovery Installer v2.54) I was curious about updating via ARI (since she's rooted and being plagued by OTA popups). Back when she first got the tablet, she tried to update and it would stop mid-download, giving no error, and just sit there until she cancelled it (this was before the root). So, basically, my question is: Is it possible to run a stock update (Ie "Stock 3.1 4.010.42_EMEA_GEN3") without having to wipe during install? I have a backup via ARI and also Titanium backup installed but I'd really like to not have to re-install all the apps/set up the homescreen (she's on stock) and stuff. I know on my OG droid that when I installed CM7 I had to do a wipe for it to even get past the boot screen but I figure with this being a stock update maybe it's different...
If not is there some way that I can install an update while keeping the root/system data?
Click to expand...
Click to collapse
No. If you run the OTA, you WILL lose root. Not to mention I don't have a lot of faith in any device OTA updates. Prior experience, and hanging around various forums, well, you can read the horror stories.
I would advise, if you want to upgrade her OS and get rid of the "pesky" update notifications, is to flash one of the Stock rooted roms available. Or maybe a stripped down version of a Stock rom.
Search the developer section for a rooted version of the stock OTA, there are several in there. Install it via recovery, you only need to wipe dalvik and cache before the install. All of her data and programs will still be there. It will upgrade just fine. Remember wipe Dalvik and cache but do not wipe data and everything will be fine.
get and flash one of the honeylicious rom from the dev area .. good rom very basic apps.. but has a update to get the acer apps back.. and bunch of other cool mods.. the dev is also . kinda trustworthy..
Giggles.. ok he is kewl for a guy yukeeee guys smell..
good luck .. read read read read before you flash anything and of course back up and back up your backups .. then back them up again
cruise350 said:
Search the developer section for a rooted version of the stock OTA, there are several in there. Install it via recovery, you only need to wipe dalvik and cache before the install. All of her data and programs will still be there. It will upgrade just fine. Remember wipe Dalvik and cache but do not wipe data and everything will be fine.
Click to expand...
Click to collapse
Well... if the person was going to do an update to the exact same rom (different version) I would say ok.
But... if you are going to go to a totally different Rom, you NEED to wipe User Data.
Or, does anybody want to tell me you never have to?
3 Wipes. Mandatory when switching between roms, unless you are a dev and know exactly what you are doing.
Or.... you can forget about the safe side of things, and just flash away, and hope luck is with you.
The Market, SHOULD, allow you to re-download apps based on the market version you previously used. If not, it's a good time to clean house of the useless apps.
Moscow Desire said:
No. If you run the OTA, you WILL lose root. Not to mention I don't have a lot of faith in any device OTA updates. Prior experience, and hanging around various forums, well, you can read the horror stories.
I would advise, if you want to upgrade her OS and get rid of the "pesky" update notifications, is to flash one of the Stock rooted roms available. Or maybe a stripped down version of a Stock rom.
Click to expand...
Click to collapse
I wasn't talking about an OTA, I was talking about the stock 'rom' updates via recovery. I've had experiences with phones that have been rooted and accidentally updated via OTA, it's not fun. My phone was actually put into something I like to refer to as the Root limbo lol, bricked it for a small period of time - that was fun fixing it. I didn't have a nandroid at the time so I had to start from scratch...
cruise350 said:
Search the developer section for a rooted version of the stock OTA, there are several in there. Install it via recovery, you only need to wipe dalvik and cache before the install. All of her data and programs will still be there. It will upgrade just fine. Remember wipe Dalvik and cache but do not wipe data and everything will be fine.
Click to expand...
Click to collapse
So if I find a rooted version of stock OTA I can install it and only wipe Dalvik? I won't get stuck in a bootloop if I don't wipe data?
AliceInUnderland said:
So if I find a rooted version of stock OTA I can install it and only wipe Dalvik? I won't get stuck in a bootloop if I don't wipe data?
Click to expand...
Click to collapse
If you stick with a stock pre-rooted ROM, you won't get stuck in a bootloop like you do some phones. You're just doing an upgrade.
But like doing an upgrade to any other OS without formatting first, you're writing good data over bad, so your mileage may vary.
---------- Post added at 06:38 PM ---------- Previous post was at 06:34 PM ----------
erica_renee said:
get and flash one of the honeylicious rom from the dev area .. good rom very basic apps.. but has a update to get the acer apps back.. and bunch of other cool mods.. the dev is also . kinda trustworthy..
Giggles.. ok he is kewl for a guy yukeeee guys smell..
good luck .. read read read read before you flash anything and of course back up and back up your backups .. then back them up again
Click to expand...
Click to collapse
Hey I resemble....or is it resent that remark! lol
kjy2010 said:
If you stick with a stock pre-rooted ROM, you won't get stuck in a bootloop like you do some phones. You're just doing an upgrade.
But like doing an upgrade to any other OS without formatting first, you're writing good data over bad, so your mileage may vary.
I can't seem to find any pre-rooted stock Roms on the Developers forum. Links? I know I'm probably being a pain in the ass but I really don't want to get something by mistake and start with scratch on my mom's tablet - if it were mine I wouldn't care. lol
Click to expand...
Click to collapse
The link in the post above yours in this thread. Is a link to the rom scroll up one post
Giggles
AliceInUnderland said:
kjy2010 said:
If you stick with a stock pre-rooted ROM, you won't get stuck in a bootloop like you do some phones. You're just doing an upgrade.
But like doing an upgrade to any other OS without formatting first, you're writing good data over bad, so your mileage may vary.
I can't seem to find any pre-rooted stock Roms on the Developers forum. Links? I know I'm probably being a pain in the ass but I really don't want to get something by mistake and start with scratch on my mom's tablet - if it were mine I wouldn't care. lol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1290318
Click to expand...
Click to collapse
kjy2010 said:
AliceInUnderland said:
http://forum.xda-developers.com/showthread.php?t=1290318
Click to expand...
Click to collapse
Oh my god you rock, thanks so much!
Click to expand...
Click to collapse
AliceInUnderland said:
kjy2010 said:
Oh my god you rock, thanks so much!
Click to expand...
Click to collapse
Yw
Click to expand...
Click to collapse
kjy2010 said:
AliceInUnderland said:
http://forum.xda-developers.com/showthread.php?t=1290318
Click to expand...
Click to collapse
Okay, this sent her into a bootloop so I had to nandroid. I wiped dalvik cache before installing this. Put it in the root of my SD card and installed via CWM in recovery. what am I doing wrong?
Click to expand...
Click to collapse
AliceInUnderland said:
kjy2010 said:
Okay, this sent her into a bootloop so I had to nandroid. I wiped dalvik cache before installing this. Put it in the root of my SD card and installed via CWM in recovery. what am I doing wrong?
Click to expand...
Click to collapse
I've never heard of the A500 going into a bootloop simply from flashing one rooted stock ROM to another, but then again most people do all the necessary wipes when they do. Did you wipe dalvik and battery stats? That's about as minimal as you're going to get. If that doesn't work, you'll just have to flash the proper way. Instructions here complete with a video tutorial on how to flash by yours truly:
http://forum.xda-developers.com/showthread.php?t=1390860
Click to expand...
Click to collapse
kjy2010 said:
AliceInUnderland said:
I've never heard of the A500 going into a bootloop simply from flashing one rooted stock ROM to another, but then again most people do all the necessary wipes when they do. Did you wipe dalvik and battery stats? That's about as minimal as you're going to get. If that doesn't work, you'll just have to flash the proper way. Instructions here complete with a video tutorial on how to flash by yours truly:
http://forum.xda-developers.com/showthread.php?t=1390860
Click to expand...
Click to collapse
Nevermind, I fixed it XD I wiped dalvik and battery/partition and it worked fine lol.
Click to expand...
Click to collapse
AliceInUnderland said:
kjy2010 said:
Nevermind, I fixed it XD I wiped dalvik and battery/partition and it worked fine lol.
Click to expand...
Click to collapse
Uh huh....you're welcome!
Click to expand...
Click to collapse

Got rooted, installed custom recovery, lost root, now i'm confused...

So I used the Auto CF root and all went well. Next, I went back into recovery and installed the TWRP Recovery though odin. It installed fine. After that I noticed I no longer had root and I can't figure out how to get it back. Supersu was still installed, it just wouldn't work.
At this point, i've tried redoing the root process a couple of times and it says that it worked fine, but doesn't do the job. Anyone got any ideas on what to do?
If anyone's curious, I started on totally stock OTA MF9.
Thanks
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
ifly4vamerica said:
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the tip. Downloading the odexed version of this. Slow download so almost 2 hrs left.
[ROM][ZIP]Stock Rooted Deodexed/Odexed MF9 with SuperSU/Busybox 1.20.2
Hopefully it works. I tried wiping cache and dlvik cache and now when i turn the phone on it just keeps giving errors that this and that app can't open so the phone is essentially unusable. Didn't think wiping cache would do that.
Yeah sometimes things just go screwy. Have you tried fixing permissions? While you wait for a download you can wipe cache davlik and fix permissions its in the advanced menu of twrp. The odexed with no data wipe should fix you up I would recommend wiping cache davlik and system before you flash it. If it still gives errors you may have to wipe the data also and start fresh. You can also try TWRP version 5.0.2 if you aren't on it there is a flashable in the dev forum also. Some people have reported issues with the newer version. I think you will be fine flashing that stock odexed ROM though.
SGS4 Sent
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
iivisionii said:
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
Click to expand...
Click to collapse
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preload before flashing to avoid issues. All the custom ROMs have root built into them so you should be good to go.
SGS4 Sent
ifly4vamerica said:
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preloaded.
SGS4 Sent
Click to expand...
Click to collapse
Thanks. I'll have an update soon. Either that or a panic attack and a question in roughly 30-45 minutes.
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
daniel4653 said:
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
iivisionii said:
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
Click to expand...
Click to collapse
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
iivisionii said:
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
Click to expand...
Click to collapse
Have you tried the battery pull trick once frozen?
ObrienDave said:
Have you tried the battery pull trick once frozen?
Click to expand...
Click to collapse
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
iivisionii said:
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
Click to expand...
Click to collapse
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
ObrienDave said:
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
Click to expand...
Click to collapse
Ah ok. Good tip to know. I had tried that and it didn't work. Seems to be working ok now. I'm gonna be careful not to screw it up cuz its already 1 am, hehe. Thanks for everyone's tips.

Categories

Resources