Anyone know which app to freeze to prevent the Rezound from automatically triggering the prompt to load Verizon Media Manager on connect to PC?
There used to be a way to do it through a dial-in sequence on the Incredible; that doesn't work on the Rezound.
Doesn't pop up on mine. Are you talking about their website on your computer screen, or the app on your phone? In settings you can change how the phone reacts when connecting to your PC.
I know that. When I connect I get an immediate prompt to download Verizon's Media Manager software, and the web page pops up in a browser (or additional tab if the browser is already open). On the Incredible, there was an *.iso file in the system root that could be de-activated by dialing a sequence of numbers and getting a feature menu which would de-activate CD-ROM. That menu is missing from the Rezound, so something else is triggering the pop-up.
There might be an *.iso file somewhere in there, but I am hesitant to delete or write anything to the ROM. Last time I did that I had to do a factory reset. I'm hoping it's an apk that can be frozen by Titanium during temporary root.
you did check off to connect via "USB Debugging Mode" in settings right?...
i do it that way & when i connect to my PC the only thing it does will bring up the prompt on the phone itself asking if i want to do "charge only" or "hard drive".
voxigenboy said:
you did check off to connect via "USB Debugging Mode" in settings right?...
i do it that way & when i connect to my PC the only thing it does will bring up the prompt on the phone itself asking if i want to do "charge only" or "hard drive".
Click to expand...
Click to collapse
Usually keep USB debugging ON, not off, but even setting it to off produces the prompt when I connect. It appears to "see" CD-ROM which would suggest that there *is* an *.iso file somewhere. Guess I'll have to go back into temporary root and see what's in there.
hgoldner said:
Usually keep USB debugging ON, not off, but even setting it to off produces the prompt when I connect. It appears to "see" CD-ROM which would suggest that there *is* an *.iso file somewhere. Guess I'll have to go back into temporary root and see what's in there.
Click to expand...
Click to collapse
yeah when i go to 'windows explorer' after the phone's connected, it shows that 'CD-ROM', as well as both the drives from the phone itself & then the sd card.
oh wait... perhaps it's because i have "autorun" in windows disabled. anytime i pop in anything, nothing happens. i just go into explorer and manually open things. so my guess is that it's your PC's autorun feature.
i believe once you have the phone connected, go into windows explorer and right-click on the 'CD-ROM' listing, there should be an option somewhere to "autoplay/autorun" & you can disable it.
there's a way to disable autoplay/autorun completely in windows & there's more info on that here:
http://answers.microsoft.com/en-us/...indows-7/7ba51974-c009-44ad-9067-f3968744175b
or here:
http://support.microsoft.com/kb/967715
hgoldner said:
I know that. When I connect I get an immediate prompt to download Verizon's Media Manager software, and the web page pops up in a browser (or additional tab if the browser is already open). On the Incredible, there was an *.iso file in the system root that could be de-activated by dialing a sequence of numbers and getting a feature menu which would de-activate CD-ROM. That menu is missing from the Rezound, so something else is triggering the pop-up.
There might be an *.iso file somewhere in there, but I am hesitant to delete or write anything to the ROM. Last time I did that I had to do a factory reset. I'm hoping it's an apk that can be frozen by Titanium during temporary root.
Click to expand...
Click to collapse
It has never popped up for me. In any case, what if you just Freeze that app using TB? (I think I froze that one on my last trip into Temp Root.)
Related
Hey Guys,
I asked this in the actual rooting thread, but there doesn't seem to be much activity there. Was hoping for an answer by tonight when I attempt rooting.
Got my Thunderbolt yesterday. Didn't have time to root last night, but did go ahead and set up ADB Shell via the youtube tutorial (thanks man).
One issue I noticed was when I went to plug in my TB to a Win7 notebook, it did not give me the option of mounting it as disc drive like the Incredible does. I believe the option I chose was something like "connect apps to pc" or something to that effect and enabled USB debugging. I installed the drivers and added the variables for ADB, then checked to see if ADB was reading my TB via the cmd prompt, and it was. It displayed my serial number and device under list of devices attached.
Everything seemed to be fine, just like in the vid. But, with the mounting as disc drive option missing am I going run into any problems when I begin rooting?
So when you plug your TB into your computer you dont see a screen pop-up on your phone that has options like "Charge only" or "Mount drive"?
I replied in the root thread, but I can do it here too.
If I remember correctly when you first plug it in it doesn't show disk drive as an option. But once you've selected an option, pull the notification bar down and select it again the disk drive option should be there.
If not, you can always push the files to the sdcard with adb (adb push name_of_file.extension /sdcard/).
Hope this helps.
Well, the option is there now. I swear it was not at any point last night. Even after I put the drivers in.
But, both my notebook and TB have been restarted since then. Perhaps this was all it needed.
Thanks to you guys for responding. I'm about to attempt root. I'm just as nervous as I was when I rooted the Incredible for the first time.
Send some positive chi my way!
I can access all the files on the phone and memory car through the computer, I can delete files. However when attempting to transfer a file (music) it comes up with a black sort of 'no entry' sign and I am unable to copy anything.
Which way are you trying to copy phone -> Windows or Window -> Phone
I've experienced this too Win -> Phone
What I can't understand is why, even though I have full root, I can only see certain folders in Windows still...
I know its not ideal, but you can always try FTP'ing or SSH the files...or even adb. Any of those should sort out the permissions correctly and if not, they'll probably give you a more informative error.
IRPnet said:
Which way are you trying to copy phone -> Windows or Window -> Phone
I've experienced this too Win -> Phone
What I can't understand is why, even though I have full root, I can only see certain folders in Windows still...
I know its not ideal, but you can always try FTP'ing or SSH the files...or even adb. Any of those should sort out the permissions correctly and if not, they'll probably give you a more informative error.
Click to expand...
Click to collapse
It's a driver problem(in windows). You can try to go in your Windows Device manager and uninstall the driver. Disconnect your phone's USB and reconnect. You should then see windows re-installing the drivers. This method works 50% of the time.
If it still doing it you can download AIRDROID from the market. Pretty cool app, no need for USB or bluetooth. control your phone with WIFI.
On my previous Verizon Android phones (Droid X, Thunderbolt, Rezound), once I was rooted, I was able to remove the .iso file in \system\etc that caused the verizon bloatware autorun package to execute every time I plugged the phone into my computer.
On my S4, I have root access, and have granted root access to the file manager app I'm using, but it's still telling me I don't have permission to delete "Autorun.iso" in \system\etc
Anyone know how I can get rid of it?
Use rootexplorer
ajeteja said:
Use rootexplorer
Click to expand...
Click to collapse
Ah, I'm an idiot... I forgot to tell ES File Explorer to mount the system directory as writable.
Thanks.
I would like to kill that annoying feature as well. Did deleting that file work? I want my phone straight into mass storage when I connect it to a PC.
skiddingus said:
I would like to kill that annoying feature as well. Did deleting that file work? I want my phone straight into mass storage when I connect it to a PC.
Click to expand...
Click to collapse
Yes and no.
Deleting that file worked perfectly in that the Verizon autorun BS doesn't start every time I plug it in, which is all I was really going for.
Unfortunately, as I've discovered based on another thread in this forum, mass storage mode is pretty much done for. The best I can do is putting it into "MTP" (media device) mode. It seems like MOST of the time, it'll go into MTP mode when I plug it in, but not always - sometimes it'll say "connected as an installer", or switch to that mode after initially being in MTP.
I have yet to find a way to make it go into true mass storage mode (the MTP mode kinda sucks - the transfer rate is slow, getting to the SD directory takes several more clicks, and since Windows is treating it like a media device, file transfers are screwy at best), let alone "charge only" mode, which is all I really want ~95% of the time.
masicia find
beleynn said:
Ah, I'm an idiot... I forgot to tell ES File Explorer to mount the system directory as writable.
Thanks.
Click to expand...
Click to collapse
How did you mount it? It still saying i do not have permission
I've turned on the developer options and can enable the USB Debugging option to be able to use Titanium backup. However I notice when I reboot the device it gets disabled again. Does anyone know of something/somehow to ensure it's enabled on boot?
Thanks!
---Eric
Got it, need root shell of course:
- Remount /system in readwrite mode.
- Add this to /system/build.prop: persist.service.adb.enable=1
- Save, remount as read only.
- Reboot.
Well...didn't really work...though it did, any ideas? USB debugging for me has to be manually picked each time.
So what seems to work for me upon reboot is that I use SManager and have a script run as root at boot up:
#!/system/bin/sh
echo 1 > /data/property/persist.service.adb.enable
This seems to enable USB debugging upon each boot. The build.prop worked once, but did not seem to keep it enabled.
Any chance anyone else has come up wth a different way to retain USB debugging on reboot? I just had to rebuilt my phone from scratch by restoring from stock and executing a script at boot up could potentially be fatal. I'm a linux admin so I do know what I am doing but without a unlocked bootloader and the ability to recover from a CWM backup, I'd rather not mess with the OS too much if possible.
x86cpu said:
So what seems to work for me upon reboot is that I use SManager and have a script run as root at boot up:
#!/system/bin/sh
echo 1 > /data/property/persist.service.adb.enable
This seems to enable USB debugging upon each boot. The build.prop worked once, but did not seem to keep it enabled.
Click to expand...
Click to collapse
JCDinPGH said:
Any chance anyone else has come up wth a different way to retain USB debugging on reboot? I just had to rebuilt my phone from scratch by restoring from stock and executing a script at boot up could potentially be fatal. I'm a linux admin so I do know what I am doing but without a unlocked bootloader and the ability to recover from a CWM backup, I'd rather not mess with the OS too much if possible.
Click to expand...
Click to collapse
I use Tasker with the secure plugin.
It allows turning on USB Debugging. I use it to turn on USB Debugging as a condition after boot.
Also the worst case with a script, you re-install/flash the OS.
I've reinstalled my Verizon LG G3 from stock ROM twice now. The first time I rooted it with IOROOT and the USB debugging option stays enabled after reboot. The second time I rooted it with Stump root and the USB debugging option does not stay enabled after reboot. No idea what is different between them but maybe someone else can dig through and figure it out.
I have the same problem, when I reboot the phone and open titanium backup.
tech_head said:
I use Tasker with the secure plugin.
It allows turning on USB Debugging. I use it to turn on USB Debugging as a condition after boot.
Also the worst case with a script, you re-install/flash the OS.
Click to expand...
Click to collapse
Could you share how to set this up? Thanks
bamemanxxa3416 said:
Could you share how to set this up? Thanks
Click to expand...
Click to collapse
Set up a task with the "secure Settings" plug in.
You are going to go into the "System Actions" and select "USB Debugging" then select the radio button to "On" then save.
Now you are going to create a profile that uses an Event.
The even will be a "System" type of event and under system you will see "device boot".
Once you have created the event add the USB Enable task you created.
This all assumes you know how to use tasker.
problem fixed......
tech_head said:
Set up a task with the "secure Settings" plug in.
You are going to go into the "System Actions" and select "USB Debugging" then select the radio button to "On" then save.
Now you are going to create a profile that uses an Event.
The even will be a "System" type of event and under system you will see "device boot".
Once you have created the event add the USB Enable task you created.
This all assumes you know how to use tasker.
Click to expand...
Click to collapse
Very nice instructions and thanks for taking the time
because of stumproot, if using iosroot then problem will never appear.
ericsmart said:
because of stumproot, if using iosroot then problem will never appear.
Click to expand...
Click to collapse
Actually not true.
I used ioroot and I have the issue of USB Debug not sticking.
That's why I came up with the way to fix it in tasker.
tech_head said:
Actually not true.
I used ioroot and I have the issue of USB Debug not sticking.
That's why I came up with the way to fix it in tasker.
Click to expand...
Click to collapse
but, it's good to have other solution, it's all good that you guided them who have similar problem.
I have the same problem as you.
tech_head thanks for giving this tasker newb enough bread crumbs that I was able to figure it out and solve the problem (and learn something in the process).
Real easy check usb debug,then plug phone into computer go to your folder that you have adb shift right click mouse all at once open cmd window here check Ethernet mode on phone check rsa cert when prompted type adb devices press enter then adb reboot then enter when LG logo appears unplug phone now your usb debug will always stay checked
WHATSAMATTA U ALUMNI
the tasker approach is now disabled and deathsquad737`s approach has caused it to stay checked... Thanks!
Hi Guys
I found a easy way to fix it.
1) turn on USB debugging
2) Connect G3 to your PC
3) Reboot your G3 when keep connected to PC
4) Unplug
Now the debugging option will be kept.
Background:
I have a rooted SM-G900V (Verizon Galaxy S5) running Lollipop with a broken screen. I have Titanium Backup installed and it was supposed to be running weekly but wasn't. I have recovered my photos, contacts, etc. by connecting to my PC and copying the internal storage and from my gmail restore to a new GS5. I want to recover app data from a couple apps. The phone has USB debug turned on and I can connect with ADB.
I thought I could just run an ADB backup, but apparently in order for the backup to initiate I have to press a button on the lower right of the screen...which is broken. I suppose if I could connect via WiFi and then use a MHL cable I could use a keyboard/mouse to click the button on the phone but I don't have a MHL cable right now and I don't know if that would work anyway (WiFi ADB hasn't worked for me to this point).
THE QUESTION:
I've done a lot of reading and found a number of ADB options that sounded viable, but have not been successful. I have TitaniumBackup installed and thought that I could launch the "backup all" batch process but don't see how to make that happen. I have a new GS5 that is identical setup so I could record some actions on that one and play them on the broken one potentially.
I'm open to any suggestions.
bkenobi69 said:
......... THE QUESTION: I've done a lot of reading and found a number of ADB options that sounded viable, but have not been successful..........
Click to expand...
Click to collapse
The only thing I can think of is to guide you to the following thread that should, hopefully, be what you need.
https://forum.xda-developers.com/showthread.php?t=2786395
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
I really appreciate the suggestion. FWIW, I sort of came up with a similar approach myself that I almost have working. I turned on ADB WiFi on the device and then plugged in my wireless USB mouse/keyboard. I set up a script that performs a screen capture every 2 seconds and downloads it locally. With Windows7 image viewer, it automatically updates when the image changes so I get a slide show of what's happening on screen. The only issue I have is that the SD card isn't set up for TitaniumBackup apparently since I get an error when I select the backup action. If I can get TitaniumBackup set up correctly, I should be golden!
Thanks for posting that link. Ironically, the solution I developed was very similar in concept. I will give a short description for others who may need to recover data from a phone with a broken screen.
Prerequisites:
* TitaniumBackup - This can be installed from the Play store even if the phone is not functioning
* USB debug mode enabled - Without this, you are stuck. The only issue here is newer phones don't always enable MTP on connection. My old on did but the new one does not. If it doesn't connect via MTP, you will need to install MTPEnabler or similar.
* USB keyboard/mouse combination
* USB cable
* Charged fully functional phone sans screen
* ADB software - You must have the same version on the phone and PC. If not, it won't work reliably/at all. I went with fastboot_adb(1.0.32)_071114_r21 since I have 1.0.32 on my SM-G900V.
Basic steps:
1) Unpack the ADB software on your PC in a convenient location (C:\ADB)
2) Connect phone to PC via USB
3) Send command to enable WiFi ADB connection
4) Disconnect phone from USB
5) Connect ADB via WiFi
6) Run following batch script:
:loop
adb shell screencap /sdcard/screen.png
del screen.png
adb pull /sdcard/screen.png
echo captured
timeout /t 2
goto loop
Click to expand...
Click to collapse
This will dump a screen shot every 2 seconds
7) Open screen.png in Windows image viewer. It should automatically update when the image is refreshed.
8) Type "launch titaniumbackup" and press enter on wireless keyboard.
9) Using either tab or mouse, select the check box to launch TB.
10) Using either tab or mouse, select "menu" from upper right.
11) Using mouse, select "batch actions" from the list.
12) Using mouse, select "RUN" next to "Backup all user apps" from the list.
If all went well, you now have your phone backup up all application data to your SD card which can be easily used on a new phone to restore data.
NOTE:
It may be possible to also use the built-in ADB backup function. I attempted this at one point, but it requires selecting a button in the lower right on the phone. Since I was using ADB over USB at the time, I could not click the button on the phone since I only had one device connected (no hub). If you have a hub it may be possible to use that approach. Alternately, if you use ADB over WiFi, it should also work. However, be aware that there is no way to see where you are clicking or confirm that it worked other than looking at the files on the SD card as ADB backup doesn't appear to give any feedback. Also, this isn't as easy as TB when it comes to restoring as you either have to backup every app one at a time or all together. When restoring, it's also a one shot deal so you can't select specific apps to restore from a larger set.