Database Users

Volume Issues on rooted 4.5.602

Ok I'm not an idiot, but humor me. I did everything I need to to root my phone to 4.5.602. Im happy with it and actually have some positives (Swype doesnt crash anymore compared to 596)
The one big issue I do have is that whenever I am running a streaming app, i.e. Sirius Xm or Pandora, the volume from the headphone jack is super low. But here is the kicker, if I make a phone call using the speakerphone, after i finish with the phone call the volume is fine, until i get some sort of notification, i.e. a new email or the battery is full. Also to note the alert that makes the streaming headset volume low again is not audible.
In the past to fix this I have edited the build.prop file to have media.stagefright.enable-player=false
and I did this to the new build.prop file when I upgraded to 602. (the value wasnt there as a note) This did not work. This is getting really annoying and would appreciate any help.

I just updated to 4.5.602 all of my sounds are fine I was reading somewhere that if u were rooted .596 to rooted. 602 there are fine bugs it said to fix go stock gb.602 u will lose root google DROID x root 4.5.602 there should be a computer option for one click root its what I used
Sent from my DROIDX using XDA App

As far I have read there is no one click option fire gb on the droid x

hitnrun30 said:
As far I have read there is no one click option fire gb on the droid x
Click to expand...
Click to collapse
There is now.
http://rootzwiki.com/showthread.php?t=3714

So I can sbf back to froyo upgrade to 602, and use the one click option, that is fantastic.I'll have to try that and see if my problem fixes itself

Ok you guys are going to think I'm an idiot. I found the reason. When i Rooted to 602 i ran Titanium Backup which happened to install 2 volume boosters. They must have been competing and caused my issue.
On a side note, the One Click Root, how do you unroot it just in case I need to replace the ohone and I have a smart rep, (warranty and all)

hitnrun30 said:
Ok you guys are going to think I'm an idiot. I found the reason. When i Rooted to 602 i ran Titanium Backup which happened to install 2 volume boosters. They must have been competing and caused my issue.
On a side note, the One Click Root, how do you unroot it just in case I need to replace the ohone and I have a smart rep, (warranty and all)
Click to expand...
Click to collapse
I'm not sure what that one click program even looks like...
There may be an ability to unroot.
Read up on this as well...it probably works on the X.
http://www.droid-life.com/2011/09/09/droid-bionic-unroot-tool-also-available-now/
And if need be, a .602 sbf is available now as well.
http://www.mydroidworld.com/forums/droid-x-discussion/9127-official-4-5-602-sbf-droid-x.html

Thanks for the SBF link, but it sometimes wont load the sbf, i will test, but I had a lot of issues sbfing to 458 to install the rooted 602.

why not to rename system app .bak (how I bricked my phone) - Resolved

Resolved: see post below.
Hi there, I'm really writing this hoping that maybe someone knows a fix for my problem and as a warning for why renaming system/apps with .bak is a silly idea when you can just do it via titanium or something similar.
About the device
Phone is a bell model, rooted but running the stock rom. I froze a bunch of apps with titantium (the smart way) but also added the .bak extension to some apps in the system/app folder.. I can't remember which ones but evidently important ones.
Everything was fine until today when an app I sideloaded caused my phone to go into a boot loop. I've been fighting with wakelock issues lately so I figured it wasn't a big deal to pop into the android recovery and do a factory restart. Problem is, some of the apps I added the .bak extension to are needed via the setup.
Problem I'm having
I can boot the phone fine and get to the blur setup screen which I can bypass as well. Problem is, once I skip the screen I immediately get a force close, and instead of taking me to the home screen, it goes back to the blur setup screen. I tried the keyboard shortcut bypass method which also works fine, but renders the phone useless since I can't access any menus, etc. It's just a black screen with the notification bar at the top. Horrah!
Long story short:
I can't enable usb debugging unless there is a way to sneak into the settings menu from the emergency call screen
Bell doesn't have a stock rom available
I can't re-root and fix my problem via adb because I can't turn on debug mode.
GAH!
Anyways, I'm pretty screwed. What are my choices?
I can return it to bell and hope they don't notice my giant gaff, flash an aftermarket rom and lose any warrenty I might have (I'm pretty toast now anyways) or buy a replacement phone.
Any thoughts would be greatly appreciated
- Kate

OMG
my heart had literally stopped beating for the past hour until I remember reading somewhere that you could text message a link to a replacement launcher hosted on dropbox.
OMG
Problem solved, phone is working.. I think.
Lesson for today kids: Do not mess with things you're not totally 100% sure about. Also, don't screw around with work phones. You need them to stay employed. Bricks don't keep you employed.

Flashing after market software shouldn't void your warrenty. I've sent in a few self bricked phones to bell.
Try early USB enumeration mode for ADB access
sent from my Atrix via XDA premium

marko! said:
Flashing after market software shouldn't void your warrenty. I've sent in a few self bricked phones to bell.
Try early USB enumeration mode for ADB access
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
And I have sent 2 of my atrixs back to at&t both were unlocked and rooted
No questions asked not on extra doller spent I love insurance its worth 5 dollers a month to me + my phones were both bricked by apps in the android market
that's my story and I'm sticking to it!!!
Sent from my MB860 using xda premium

marko! said:
Flashing after market software shouldn't void your warrenty. I've sent in a few self bricked phones to bell.
Try early USB enumeration mode for ADB access
sent from my Atrix via XDA premium
Click to expand...
Click to collapse
Does that work even if usb debugging is off? If so, that's fantastic! I'll keep that in mind next time I'm in a horrible jam.
It wasn't market apps though that was my concern though... rather it was messing with system/apps and build.prop that had me concerned. Any wise tech would know that my problems weren't caused by some error on Motorola's part, but rather a silly girl who's breaking things from within.
Thanks though

I once told the **tech repairs specialist** that I bricked my phone installing a custom rom and got asked " what kind of customer was on the phone?"
Try and find NFHimselfs atrix mods apk it will help a lot
sent from my Atrix via XDA premium

[Q] I can't get my DX out of safe mode!

I browsed the 14 pages in the development thread and a few in the general. I googled for an answer to my problem, but haven't found anything that has worked.
problem: My Droid X (formerly with VZW) has constantly been loading in safe mode. It was intermittent the past couple weeks or so, but now it only loads in safe mode.
1.I tried: to power down/restart normally-ineffective;
2.power down/remove battery/restart-ineffective;
3.booted phone holding the power button and home screen until alternate screen loads/wiped cache/rebooted normally-ineffective;
4. repeated step 3 boot/performed factory reset/rebooted-rendered ineffective.
History: I cancelled my service prior to contract guidelines. Have been using my phone strictly for wifi the past couple months now. Very recently (past few days) has this safe mode issue been lingering.
Question: Has vzw installed some kind of script that basically disables all cellular usage (except preinstalled apps) if the phone isn't 'free and clear'?
Also, is there ANY possible way I can install a completely different rom so that vzw network can't affect my phone? I just want to keep it for wifi access for calling/net/gaming. Has anyone seen this issue before?
ps - The first person to help me fix this problem so I can use my phone 'free and clear' I will donate at least $25 ! Not sure if that is appropriate to include this here, but I haven't seen anyone actually saying they would pay to get their problem(s) fixed. I am MORE THAN HAPPY to pay someone for his/her time to help me.
I don't want to infringe upon forum rules so I won't include my email or cell#, so I guess the best way to reply for now is either here or pm?
Thank you for all your help! I hope we can rectify this problem.

What u mean safe mode? But try sbfing your phone, root it, and then install a rom. Liberty is a very good rom.
Sent from my DROIDX using XDA App

Safe mode. I can't install/run any apps other than preinstalled, which I rarely use.

weiky79 said:
Safe mode. I can't install/run any apps other than preinstalled, which I rarely use.
Click to expand...
Click to collapse
I would sbf the phone and root it. Then I would install a custom rom. You will be rooted and be able to use the phone a lot more freely.
Sent from my DROIDX using XDA App

I sent you a PM so call me and we can work on sbf'ing the phone back to health

I'll let barracudacm work on this with you but I just wanted to add that you should consider installing CM7 instead of a blur based rom to help you escape big red.

Thanks for all the help! Will post when I get it resolved!

Turning back on

Hi Everyone, I just got my Droid 2 back after loaning it to a friend. He did a factory reset to wipe his data off and now all I need to do is activate it by dialing the number I wish to use. My problem is that I have a new phone and and I just want to be able to have it for wifi and mostly just to root and play around with the different roms. I don't know what software version is on here because its been sever months since it was in my hands.
Am I going to have to turn off my current phone to activate the D2 and then turn off so that I can turn service back on my everyday phone?
Thanks in advance for any help
Sent from my MZ604
happy to be running
Team EOS Nightlies #103
with the great support from the XDA community...Thanks!!!

No. When you turn the D2 back on just skip the activation step that has you dial *228

MissionImprobable said:
No. When you turn the D2 back on just skip the activation step that has you dial *228
Click to expand...
Click to collapse
When I turn phone on the only 2 things it allows me to do is an emergency call or touch the green droid on the screen. When I touch the green Droid it automatically dials (doesn't even show me the number) and I have no opportunity to skip entering my number. Only problem is that my only number is on my everyday phone. I hope by the additional info added someone can help me to turn phone on.
Worse case scenario is that I can deactivate my good phone then run through the activation only to turn my good phone back on. Oh well I was hoping to play around with a new rom tonight.
Sent from my MZ604
happy to be running
Team EOS Nightlies #102
with the great support from the XDA community...Thanks!!!

bypass startup
Touch the four corners of the screen
Top left
then top right
then bottom right
them bottom left
Then touch the green droid
This will bypass the auto dial

glennsardone said:
Touch the four corners of the screen
Top left
then top right
then bottom right
them bottom left
Then touch the green droid
This will bypass the auto dial
Click to expand...
Click to collapse
Thank You that worked great! All I need to do now is read a bit to figure out which way for root and which rom is best for me.
Sent from my MZ604
happy to be running
Team EOS Nightlies #103
with the great support from the XDA community...Thanks!!!

Just don't upgrade to 2.3.4 whatever you do.

hondateg91 said:
Just don't upgrade to 2.3.4 whatever you do.
Click to expand...
Click to collapse
Ok thanks for the heads up! Can you recommend a rom and or which way to root. I have only been able to read through the development section for a limited amount of time.? I am currently on 2.3.3
Thanks again
Sent from my DROID BIONIC using xda premium

If you guys are looking for a newer rom where pretty much everything works without any issues. I would suggest Miui 2.2.10 cause i have been using it for months now and its leagues better than stock. Its prerooted so no need to worry about that. You do have to sbf to stock GB and root it so you can use bootstrap to flash a custom rom. Once its flashed though you're good to go, and i have not run into a single app this rom wont run just as well as stock. After using it for some time now there is no way i would go back to a stock rom. Its a GB rom but there is also a true ICS rom on this site.
http://rootzwiki.com/topic/17285-ne...tt-charge-while-off-updated-bootmenu-scripts/

I will second the above poster's praise for Galnet MIUI 2.2.10. It is super stable.
As for Rooting, just use Pete's One Click Tool:
http://dl.dropbox.com/u/6643359/Software/Android/PetesMotorolaRootTools_v1.06.zip
Here's the thread if you have any issues:
forum.xda-developers.com/showthread.php?t=1258599

Hello all, hopefully someone could help a guy out. So last night I rooted my DROID 2 using Petes one click tool and it was successful. I had installed Bootstrap for D2 and then wiped data, dalvik,and cache then flashed Miui 2.2.? From sd and all looked like it was going well until the phone rebooted. When the phone came back on it now just keeps cycling through the boot animation.
Could someone please help me out I am completely clueless as what to do next.
Thanks in Advance
Sent from my DROID BIONIC using xda premium

try wiping data again
when you wipe delvik, it can take a couple of mins to boot, the first time

Word. It can actually take up to 10 minutes for a first boot.

Thanks for the help.. It took me a few but remembered how to get back to bootloader. I pulled the battery then power and volume down to get back. I wiped data, cache, and dalvik reflashed the rom and now have Miui on my D2. It did take a few minutes for the initial boot up. Since this is an extra phone I plan to setup and use it mainly as a mp3 and streaming music player for in garage/outside.
Just wanted to say thanks again!!!
Sent from my MZ604
Team EOS Nightlies #107

Google Wallet on Rooted MF9 Phones

I had a working google wallet on my rooted phone prior to upgrading to MF9, however I just realized that wallet is broken again. I haven't been able to find a solution that works now with my rooted MF9. Anyone have a solution?

DarqAnshin said:
I had a working google wallet on my rooted phone prior to upgrading to MF9, however I just realized that wallet is broken again. I haven't been able to find a solution that works now with my rooted MF9. Anyone have a solution?
Click to expand...
Click to collapse
What happens when you try to use it? Did you try going online and deactivating the device then setting it back up on the phone?

DarqAnshin said:
I had a working google wallet on my rooted phone prior to upgrading to MF9, however I just realized that wallet is broken again. I haven't been able to find a solution that works now with my rooted MF9. Anyone have a solution?
Click to expand...
Click to collapse
I'm on MF9 and rooted, and I can use Google Wallet without issue. All it does is place a little nag bar about your device being unsupported because it's rooted. It still functions, but if you have a problem they technically won't "support" you. If you didn't do a clean install (update to MF9, factory reset), there may be a software issue. Try this if you haven't, in this order. App manager -> Clear cache, delete data, uninstall, go to Market, reinstall.

Darnell0216 said:
I'm on MF9 and rooted, and I can use Google Wallet without issue. All it does is place a little nag bar about your device being unsupported because it's rooted. It still functions, but if you have a problem they technically won't "support" you. If you didn't do a clean install (update to MF9, factory reset), there may be a software issue. Try this if you haven't, in this order. App manager -> Clear cache, delete data, uninstall, go to Market, reinstall.
Click to expand...
Click to collapse
I did do that. It keeps telling me the device is unsupported, but no matter how many times I try waving the over the NFC contact on the reader it does not detect a device transaction. I thought that it may be a a problem with the reader (7-11), so I brought a buddy and had him test it. The reader instantly picked up his unrooted MF9.
Now if I go home, do a factory reset; downgrade; unroot; do a factory reset; OTA MF9; and try it, the device instantly works. The moment I hit with root it states unsupported and then I spend 3 minutes waving my phone like a magic wand over the reader while the guy behind the counter looks at me as if I've lost my mind. Granted he has seen me buy items with the wallet before, but still I would rather figure out what I may be doing wrong that is causing the issue than to just not using it.

DarqAnshin said:
I did do that. It keeps telling me the device is unsupported, but no matter how many times I try waving the over the NFC contact on the reader it does not detect a device transaction. I thought that it may be a a problem with the reader (7-11), so I brought a buddy and had him test it. The reader instantly picked up his unrooted MF9.
Now if I go home, do a factory reset; downgrade; unroot; do a factory reset; OTA MF9; and try it, the device instantly works. The moment I hit with root it states unsupported and then I spend 3 minutes waving my phone like a magic wand over the reader while the guy behind the counter looks at me as if I've lost my mind. Granted he has seen me buy items with the wallet before, but still I would rather figure out what I may be doing wrong that is causing the issue than to just not using it.
Click to expand...
Click to collapse
You're not crazy. I knew I left this thread somewhere. Sometime after the 15th and before the 20th, Google changed rooted MF9 from a nag bar to a full block. I tried to launch Wallet later that evening after that post and was met with the full denial message. I contacted them on Twitter and during trouble shooting they eventually asked about being rooted and I admitted to it, while also noting it worked previously. I am waiting to see if this was an intentional server side change or they cut my support off right here, LoL

I'll have to try mine, I'm rooted stock mf9 and when I start wallet I don't get the unsupported message that I used to see. I'll have to try a purchase and see if I get denied.

cruise350 said:
I'll have to try mine, I'm rooted stock mf9 and when I start wallet I don't get the unsupported message that I used to see. I'll have to try a purchase and see if I get denied.
Click to expand...
Click to collapse
If you get it to launch, you're already one step ahead. This is what you'll see if the app has been fully blocked. I haven't gotten further contact from GoogleWallet. I'm guessing they've cut my support off for rooting, lol.

Darnell0216 said:
If you get it to launch, you're already one step ahead. This is what you'll see if the app has been fully blocked. I haven't gotten further contact from GoogleWallet. I'm guessing they've cut my support off for rooting, lol.
Click to expand...
Click to collapse
That message is because of root. You modded your build prop or something and now your phone is showing up as a phone that isn't supported. Are you running a mod to allow an app from another phone to run?
Sent from my SPH-L720 using Tapatalk 4

It lives!
cruise350 said:
That message is because of root. You modded your build prop or something and now your phone is showing up as a phone that isn't supported. Are you running a mod to allow an app from another phone to run?
Sent from my SPH-L720 using Tapatalk 4
Click to expand...
Click to collapse
It worked while rooted before. Just a small banner appeared above a "working" app. I did, however, edit my build.prop to change my 4G symbol to Verizon's 4GLTE because Sprint's is well, ugly. You mean to tell me that little thing pissed off Google Wallet? -_- Great.
...
.....
.......
And just like that Wallet is launching and functional again with the nag bar instead of a full blocking. Thanks for the tip, although I still want to kick Google in the shin for making that 3 letter edit disable the app.

Actually, I'm running that same mod for the Verizon symbols. I can't remember if one of the xposed modules gets rid of the unsupported nag or not since I'm not getting the nag.
Sent from my SPH-L720 using Tapatalk 4

Xposed? Seen the name thrown around but haven't looked into it. Guess now is as good a time as any. And yes, the "4G" irks me that much, lol. Hopefully an update will come along and change the symbol as more LTE locations come online.