this is just a copy paste from original thread located http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269 by @olokos
olokos said:
You do everything here at your own risk. I take no responsibility for any broken devices/sdcards/your house going down on fire and everything else.
PLEASE DO NOT MIRROR THESE FILES!
Requirements:
root
ability to use mouse and keyboard
terminal emulator on your phone
What do you get for doing this?
Propably you'll be able to use a lot more bands than before. Most likely your phone will work on every place in the world now.
Check the third post for a link to OPO guide
C6903
before
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after
1. Download this zip http://d-h.st/0Me
2. Extract it and install QPST from that zip
3. Open the caller app and type in *#*#8778#*#* (it should go off the screen after you type in the last symbol "*"
3.5 Those on custom roms (tested on cyanogen 11 with s4 mini) can use the efs professional toolkit to change the mode to enable the diag port.(Thanks @blackburn !)
4. Connect your phone to your PC
5. Open ADB console
6. Type in these commands:
Code:
adb shell
su
setprop persist.usb.eng 1
7. Turn off USB Debugging, Disconnect your phone from the PC
8. Wait about 10 seconds (don't have to be exact, just let it all disconnect in the PC) and turn USB Debugging back on
10. Connect it back to the PC. It should try to install drivers. Wait until it fails to install all of them.
11. Open device manager - you will see your device model a few times. Go to details tab. Scroll down a single time on that tab. You will see MI_0x there.
12. Go through those devices until you find MI_04 under the second drop down position.
13. Select "update driver" for this device and install the htc driver from the zip.
14. Press start button and navigate to QPST -> QPST Configuration
15. Go back to device manager -> modems -> HTC
16. Find "COM*" in my case it was "COM3". It might be different for you.
17. In QPST Configuration click on "Add new port" and in "Port" type in your "COM*". In my case It's "COM3" in there. In Port label it could be anyting u want. In my case I used a Z1 so I typed IN "Z1".
18. It should look like this now.
19. Navigate to QPST/bin and open RV_NV_Manager.exe
20. press on settings -> Comport and choose your COM port.
21. Press on file -> read from phone
22. Wait patiently until it is finished. Now pay attention!
23. Go to line 1877, click it and copy the decimal number on the right side of a programme. right click - copy
24. Go to the place where you extracted the zip from the first step and start mzTool
25. On the left side you will see "Input radix" - press decimal there.
26. On the right side you will see "RF BC CONFIG" paste your previously copied number from the RV_NV_Manager.exe there.
27. You will see now what bands are you able to use on the bottom of the app in "Bit information"
28. Switch tab to "Band Preference (NV Value)"
29. In there select all GSM bands and WCDMA bands. This place is really a field of testing. In my case (C6903 LTE) I selected all of GSM and WCDMA. I wouldn't suggest you to do anyting else in here unless you know what your'e doing. Let me know if you got something interesting in there.
30. After you're done choosing what bands do you want - copy decimal number from the bottom right
31. Remove all commas from that number ( "," ) so it would be just a bunch of numbers without anything else.
32. Open RV_NV_Manager.exe from the point you left it (step 23) and paste your new number without commas "," there.
33. Press on write NV and then press on file ->write changed NV to the phone.
34. Open up the terminal emulator on your phone and write there this:
Code:
su
setprop persist.usb.eng 0
35. Reboot the device and hope you'll have the reception. If you do, hooray!
36. Type in *#*#SERVICE#*#* (*#*#7378423#*#*) to see your new bands that your phone can use!
If your phone can't boot then flash stock FTF to your device and you should have your reception back!
Enjoy!
I wanted to mention that I'm just the guy that was interested in this and the person that actually made it possible is @BlackSoulxxx all thanks go to him! He's the guy that did it! Please thank him in the second post!
If you have any problems or issues here's some help from other users http://forum.xda-developers.com/showpost.php?p=55321344&postcount=3
Tested on: ZU, Z1,SP,Xperia TL,Sharp-DOCOMO Aquos Zeta SH-04F
Click to expand...
Click to collapse
more info
olokos said:
Nexus connection
1. Remove all installed drivers.
2. Install LG United Mobile Driver
3. Enable debugging and install adb driver if it's not automatically installed.
4. Using adb issue the following commands on a separate line
Code:
adb shell
su
setprop sys.usb.config diag, adb
5. Your phone should start installing drivers, once installed under Ports in device manager there should be (* indicates a number):
LGE AndroidNet for Diagnostics Port (COM*)
LGE AndroidNet USB Serial Port (COM*)
Thanks for that @CHAMAVELI !
One Plus One guide
Click to expand...
Click to collapse
Ok for some reason this
Code:
setprop persist.usb.eng 1
was not working with my M8, i tried it with the stock rooted ROM and ARHD 11.1 .
What did work for me was -
Code:
On:
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
Off:
su
echo 0 > /sys/devices/virtual/android_usb/android0/f_diag/on
Also, the *#*#SERVICE#*#* does nothing for me.
Any other way to check the available bands?
My device is an US unlocked BS_US001 device.
And even after changing the writing the settings, the changed decimal value isnt written.
bloodhawk said:
Ok for some reason this
Code:
setprop persist.usb.eng 1
was not working with my M8, i tried it with the stock rooted ROM and ARHD 11.1 .
What did work for me was -
Code:
On:
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
Off:
su
echo 0 > /sys/devices/virtual/android_usb/android0/f_diag/on
Also, the *#*#SERVICE#*#* does nothing for me.
Any other way to check the available bands?
My device is an US unlocked BS_US001 device.
And even after changing the writing the settings, the changed decimal value isnt written.
Click to expand...
Click to collapse
Try *#*#4636#*#*
JEANRIVERA said:
Try *#*#4636#*#*
Click to expand...
Click to collapse
Tried that, the bands are still the same.
Man, wish we had this back on the M7 Unlocked/Dev
Any updates on this ?
Anyone been successful with this yet?
Nope
I know myself as far as I can get is to the writing the NV value, there has been a user with a HTC M8 on verizon that has had success... Hopefully that means we can do it too. T-Mobile just activated LTE on Band 2 in my area and hoping I can activate it.
But that was only one, and all others who tried couldnt get it to work. Including me.
I Couldn't get it either. Pc just saw it as the m8 mtp nothing less nothing more.
Tachi91 said:
I Couldn't get it either. Pc just saw it as the m8 mtp nothing less nothing more.
Click to expand...
Click to collapse
I've been able to get it to see the Diag port jsut can't get the NV value to write. If you install the htc drivers and enter this in cmd prmpt should help ya:
Code:
adb sideload
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/on
I cannot see MI_04, I'm getting HTC DIAG at MI_03.
Thanks
The app mentioned in this thread has had its link removed and is banned from XDA. In care you didn't notice.
Dangerous thread it seems. ?
Has anyone been able to unlock bands 3 or 4?
As far as I've seen only one person has been successful at all with the M8 and it was a Verizon variant.
sapplegater said:
As far as I've seen only one person has been successful at all with the M8 and it was a Verizon variant.
Click to expand...
Click to collapse
I've tried as well on a Dev edition m8, same situation....nothing will write to the phone. Maybe I need to roll an xp box to do this....
compuguy1088 said:
I've tried as well on a Dev edition m8, same situation....nothing will write to the phone. Maybe I need to roll an xp box to do this....
Click to expand...
Click to collapse
You should look in the original thread,
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
Add me to that list...can only get MI_03 not 04
sadly...
Related
!!!THIS IS NOT A ROOTING GUIDE!!!
This pack contains everything you need to connect and use your nexus s on your pc
Will work on XP, Vista, 7
!!!HOWEVER 7 HAS THE BEST SUCCESS!!!
included:
* Fastboot
* ADB
* USB Drivers (32bit and 64bit)
Links:
SDK:
http://www.fileserve.com/file/RZqMfeC (sdk, fastboot, adb)
Mirror:
http://hotfile.com/dl/92897052/df7338b/SDK.rar.html
Direct Link - No wait, ads, popups:
http://mazodude.comze.com/ -down atm (have to reup)
DRIVERS:
http://www.fileserve.com/file/5bgRBX5 (PDAnet x86 and x64 which are the fastboot drivers plus android sdk drivers)
Mirror:
http://hotfile.com/dl/92897696/7ae5290/drivers.rar.html
Direct Link - No wait, ads, popups:
http://mazodude.comze.com/ -down atm (have to reup)
To be able to install drivers you have to have your phone booted into fastboot and connected via usb (Thanks to mmas0n)
How to force drivers to install:
Thanks to gravis86
WARNING: SELECTING THE WRONG DRIVER TO A DEVICE MAY BREAK THINGS...
1. Control Panel > Administrative Tools > Computer Management >Device Manager
2a. NS Right-Click "Android 1.0", and click "Update Driver Software..."
2b. NS4G Right-Click "Nexus s", and click "Update Driver Software..."
3. Click "Browse my computer for driver software"
4. Click "Let me pick from a list of device drivers on my computer"
5. Click "Have Disk..."
6. Browse to folder containing the driver, then click OK
7. It will show a list of drivers contained in that folder, select the appropriate one, and click next.
8. It might tell you the driver is unsigned / not verified to work / for the wrong device, etc. As long as you are sure it is the correct driver, then install it. Remember, you are smarter than Windows.
How to install ADB and Fastboot:
1. download and place in the root of your C:\ drive
2. extract here (not into a sub folder)
3. now open up control panel
4. find system
5. goto advanced settings
6. goto environmental variables
7. in the box that says "system variables" scroll down to find a variable "Path"
8. highlight it
9. click edit
10. add this to the end
;C:\android\tools
Click to expand...
Click to collapse
yes the ; is needed
11. click ok
Now when you open cmd (command prompt) you can use "adb" or "fastboot" anywhere with out locating the folder first
You should be able to do this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I have helped you please hit the thanks button
I have followed the directions to the letter and when I type fastboot devices it just goes back to command prompt. I tried typing fastboot oem unlock and it just said waiting on device. Adb devices typed produces "list of devices attached" I boot the phone into fastboot mode and and the usb is plugged in but I keep getting the same results. Am I preparing the phone incorrectly?The adb worked with my Vibrant but the fastboot failed there as well. I would greatly appreciate any and all help you may offer. As I am sure you can tell I am another one of those ignorant nubies.LOL
have you installed the usb drivers?
you will have to force them to install
mazodude said:
have you installed the usb drivers?
you will have to force them to install
Click to expand...
Click to collapse
Yes I have. adb works with my Vibrant but fastboot does not and neither one works with the Nexus s. I have read and reread and followed directions but nothing seems to work. Should I be looking to do something on the phone other than booting into fastboot mode? The Nexus S shows fastboot mode at the top of the screen and I have assumed that I just use the computer from there. On my Vibrant booting into recovery does not show anything about fastboot. I really do appreciate your help I am trying very hard to learn quickly so I can be of some help instead of a burden
I don't know how to force them to install. I went in an opened the folder and I assume they were installed. I do have usb debugging enabled
Edit Just copied usb drivers to C:\android and c:\android/tools and still the same results. I have done everything I can think of but i guess I am not getting the drivers installed properly.
to force them, go into control panel-> administrator tools->computer management
then goto device manager in the sidebar.
I cant remember what the device is called but you should know when you find it.
right click and hit update drivers.
hit browse for drivers and find the drivers in C:\android\google-usb_driver
Note: phone has to be in fastboot to be able to install the drivers
edit: I forgot the drivers opps
link:
http://www.fileserve.com/file/ZM9hbvH
edit: this video might help
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
I just downloaded the drivers and placed them in C:\android and then went into device manager and hit update drivers and then browse for drivers and it said no drivers found. I was in C:\android/google-usb drivers.
have a look in the post above i just posted a link to a vid
edit: are you using 64-bit?
no 32 bit I will look for the video. Thanks so much for your kind and patient help!!!
I think there is a trick in the video to get it to see the device in fastboot
edit: there are some drivers here
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
there is no video but I did read the directions and I believe I have done all that they state. Should my PC say installing drivers when I plug my phone in? It did and said one driver failed to install.
yea.
If you don't see a video (at the top) disable ad blocking
also the driver that failed try to force it (using previous method)
If anybody could help that would be great, then I will add it to the first post
Followed this guide and unlocked and rooted my friends Nexus S.
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
@shaolinmastr well that's good to hear
I still have no success installing the drivers. Are you sure that the drivers were in the last zip file? I have gone over and over it for the last 6 hours and am at the same place I started. NO adb and no fastboot on the Nexus S and adb working on Vibrant.but no fastboot . I guess it is time to take the Nexus S back and get a refund. It is not worth the lack of results with so much effort. Thanks for you help.
Save yourselfs the hassle and just install PDAnet and you should get the drivers to work.
I was having this same problem and used pdanet to get the correct nexus s drivers. You can dload pdanet to your PC and just plug your phone in via USB andfollow the directions.
So tmello56, pdanet worked for you?
If so I will extract the drivers and add them to the first post
WARNING: SELECTING THE WRONG DRIVER TO A DEVICE MAY BREAK THINGS...
Sometimes Windows needs to be forced to use a driver that we know works, but Windows thinks doesn't. This is similar to what mazodude posted, but is just a few steps further. To do this:
1. Control Panel > Administrative Tools > Computer Management >Device Manager
2. Right-Click "Unknown Device" or whatever it's called, and click "Update Driver Software..."
3. Click "Browse my computer for driver software"
4. Click "Let me pick from a list of device drivers on my computer"
5. Click "Have Disk..."
6. Browse to folder containing the driver, then click OK
7. It will show a list of drivers contained in that folder, select the appropriate one, and click next.
8. It might tell you the driver is unsigned / not verified to work / for the wrong device, etc. As long as you are sure it is the correct driver, then install it. Remember, you are smarter than Windows.
9. WIN!!!
@gravis86, very good explination will post in 1st post
Just wanted to post my results...
I was using the correct drivers, but was installing them while the phone was booted and connected. I could use ADB and mount the file system, but could not use fastboot. I then discovered that if I installed the drivers while the phone was booted into the bootloader and connected, it detected the device differently and fastboot worked.
Now rooted + custom recovery. Awesome.
I have seen many questions asking how to install universal naked drivers. Last week I received (loan) a windows computer and had the same issues. I decided to provide the info to help others.
Note: These drivers do work properly for the TF300T even though they may not state that exactly. Also if your tablet identifies as a TF201 it will still work properly.
Note: If you are on windows 8 and having problems please see the bottom of this post #1 for help! This info was provided by prototype7 please give him a thanks.
First some info. Windows thinks it should make the choices about drivers and is designed to keep us from choosing something that might cause problems. We need to maintain control through the process if we are to succeed.
Here are the choices I had to use to change my drivers and a link to the drivers.
windows-start - in search type device manager and return
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
right click on the entry you wish to change the driver for
Update Driver Software
Browse my computer for driver software
Let me pick from a list of device drivers on my computer
Have Disk
Browse
choose the universal naked drivers directory
click on the proper inf file
windows says drivers not signed; install anyway
Windows 8
Note: The following info was kindly provided by prototype7. Please give him a thanks.
Originally Posted by prototype7
I was trying to install these using this guide on Windows 8, but was running into a problem with the drivers not being signed, so here's the solution:
Hit Start+X, select Command Prompt (Admin)
Type "shutdown -o -r -t 0" (without quotes) and hit enter
You'll get a screen with some options on it after a few seconds
Click Troubleshoot
Advanced Options
Windows Startup Settings
Restart
You'll get a menu of options to choose from
Press the number on your keyboard for "Disable driver signature enforcement"
Now you can follow the guide without any issues, reboot again after the drivers are installed and you'll be good to go.
Click to expand...
Click to collapse
using this method you don't have to uninstall your current driver
if you deviate at any step windows will refuse to allow this change
Good Luck!
Re: How to install Universal Naked Drivers
Thanks for this thread which is really good and useful :good:
Good stuff
Sent from my N7 3G with DroiDevs premium between sky and earth.
And this thread is now stickied
MD
philos64 said:
Thanks for this thread which is really good and useful :good:
Good stuff
Sent from my N7 3G with DroiDevs premium between sky and earth.
Click to expand...
Click to collapse
Thanks for the kind words. I have wanted to post this for sometime but didn't have windows to prove the method.
Moscow Desire said:
And this thread is now stickied
MD
Click to expand...
Click to collapse
Thank you!
I just hope it can help some others getting their drivers installed and working.
Hi,
first thanks for the thread (i believe it will help a lot of people)
I followed all the steps, but it still doesn't work...
I did a lot of research but i have not found the solution... When i use fastboot, it still "<waiting for device>".
Anyone have the same probleme ?
Thanks for the help.
EDIT: Fine it's my fault, the cmd line have to be with -i 0x0B05 option, without it, it doesn't work.
Manox7 said:
Hi,
first thanks for the thread (i believe it will help a lot of people)
I followed all the steps, but it still doesn't work...
I did a lot of research but i have not found the solution... When i use fastboot, it still "<waiting for device>".
Anyone have the same probleme ?
Thanks for the help.
EDIT: Fine it's my fault, the cmd line have to be with -i 0x0B05 option, without it, it doesn't work.
Click to expand...
Click to collapse
Thanks!
I don't know why some tablets require the tablet designation and others don't. For that reason we suggest everyone use them. It is a code assigned by google that designates the manufacture of the unit. On linux we have to declare them to avoid a permissions error but we don't have to add drivers.
I'm glad you got everything sorted.
I was trying to install these using this guide on Windows 8, but was running into a problem with the drivers not being signed, so here's the solution:
Hit Start+X, select Command Prompt (Admin)
Type "shutdown -o -r -t 0" (without quotes) and hit enter
You'll get a screen with some options on it after a few seconds
Click Troubleshoot
Advanced Options
Windows Startup Settings
Restart
You'll get a menu of options to choose from
Press the number on your keyboard for "Disable driver signature enforcement"
Now you can follow the guide without any issues, reboot again after the drivers are installed and you'll be good to go.
prototype7 said:
I was trying to install these using this guide on Windows 8, but was running into a problem with the drivers not being signed, so here's the solution:
Hit Start+X, select Command Prompt (Admin)
Type "shutdown -o -r -t 0" (without quotes) and hit enter
You'll get a screen with some options on it after a few seconds
Click Troubleshoot
Advanced Options
Windows Startup Settings
Restart
You'll get a menu of options to choose from
Press the number on your keyboard for "Disable driver signature enforcement"
Now you can follow the guide without any issues, reboot again after the drivers are installed and you'll be good to go.
Click to expand...
Click to collapse
Thanks for the update info. If it is ok I'd like to quote your information in the first post for others who are on windows 8.
tobdaryl said:
Thanks for the update info. If it is ok I'd like to quote your information in the first post for others who are on windows 8.
Click to expand...
Click to collapse
Go ahead, it would make it easier to see. Glad I could help.
prototype7 said:
Go ahead, it would make it easier to see. Glad I could help.
Click to expand...
Click to collapse
Thanks again, I'll put in the first post for others.
Windows for x64
tobdaryl said:
Thanks again, I'll put in the first post for others.
Click to expand...
Click to collapse
Hello. I am having problems getting ADB to open. I did everything you mentioned hoping that these new drivers would work, but at the end I got a message window with "Select Device" saying;
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
I am using a Droid Razr Maxx with CM 10 installed on Android version 4.2.2. I have tried everything to get ADB to open and nothing seems to work.
Thank you in advance for your time
nathanielhall929 said:
Hello. I am having problems getting ADB to open. I did everything you mentioned hoping that these new drivers would work, but at the end I got a message window with "Select Device" saying;
"The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
I am using a Droid Razr Maxx with CM 10 installed on Android version 4.2.2. I have tried everything to get ADB to open and nothing seems to work.
Thank you in advance for your time
Click to expand...
Click to collapse
You have to actually select the file not just the directory. By only selecting the directory you give windows a choice. If windows has a choice it will always refuse to install.
Point windows to the android_winusb.inf file and it should install properly.
file selected still not working
tobdaryl said:
You have to actually select the file not just the directory. By only selecting the directory you give windows a choice. If windows has a choice it will always refuse to install.
Point windows to the android_winusb.inf file and it should install properly.
Click to expand...
Click to collapse
I have tried multiple times to select the file android_winusb file there is no .inf next to it but the file type is setup information
nathanielhall929 said:
I have tried multiple times to select the file android_winusb file there is no .inf next to it but the file type is setup information
Click to expand...
Click to collapse
That should be the proper file. In folder options there is probably a check in "Hide Known File Types". This will keep you from seeing certain extensions. Windows uses the inf extension for setup information.
Try the other inf file android_apxusb.inf and see if that will install. If you have already then I am lost.
Are you on windows 8? If so please see the topic Windows 8 at the bottom of the first post.
Still nothing
tobdaryl said:
That should be the proper file. In folder options there is probably a check in "Hide Known File Types". This will keep you from seeing certain extensions. Windows uses the inf extension for setup information.
Try the other inf file android_apxusb.inf and see if that will install. If you have already then I am lost.
Are you on windows 8? If so please see the topic Windows 8 at the bottom of the first post.
Click to expand...
Click to collapse
I have tried to select the android_apxusb file and I get the same message.
I am on Windows 7 x64
Also can you help me get a reply to this post: http://forum.xda-developers.com/showthread.php?t=2257005
I posted it a while ago and no one has answered me. Maybe you can help me with this post.
nathanielhall929 said:
I have tried to select the android_apxusb file and I get the same message.
I am on Windows 7 x64
Also can you help me get a reply to this post: http://forum.xda-developers.com/showthread.php?t=2257005
I posted it a while ago and no one has answered me. Maybe you can help me with this post.
Click to expand...
Click to collapse
I'll do some research and reply on the other thread. Adb is working if you get your serial number with adb devices, adb kill-server, etc.
In windows drivers have to be installed to get anything from your tablet with adb. Drivers are not needed for Linux and Mac but are required for windows.
Before I forget to mention later you need to run cmd as administrator in windows to use adb but since you fail with a terminal on the unit it may be a structure issue with the command.
how do I start ADB?
tobdaryl said:
I'll do some research and reply on the other thread. Adb is working if you get your serial number with adb devices, adb kill-server, etc.
In windows drivers have to be installed to get anything from your tablet with adb. Drivers are not needed for Linux and Mac but are required for windows.
Before I forget to mention later you need to run cmd as administrator in windows to use adb but since you fail with a terminal on the unit it may be a structure issue with the command.
Click to expand...
Click to collapse
I changed the path to C: Android-SDK platform tools and when I ran cmd as an administrator all I typed was adb. Am I missing something here? I also tried adb.exe
nathanielhall929 said:
I changed the path to C: Android-SDK platform tools and when I ran cmd as an administrator all I typed was adb. Am I missing something here? I also tried adb.exe
Click to expand...
Click to collapse
Check the thread you wished me to help with as I think I have already posted the resolution there.
tobdaryl said:
I'll do some research and reply on the other thread. Adb is working if you get your serial number with adb devices, adb kill-server, etc.
In windows drivers have to be installed to get anything from your tablet with adb. Drivers are not needed for Linux and Mac but are required for windows.
Before I forget to mention later you need to run cmd as administrator in windows to use adb but since you fail with a terminal on the unit it may be a structure issue with the command.
Click to expand...
Click to collapse
Thanks for ur great job
I have tf300t with replaced logicboard. -it was bricked
My os win8 64bit
I tried universal naked driver ..but no way
is their any reasons with the last bricked in this case...??
Sorry for the poor english
THIS WORKS WITH THE LATEST UPDATE!!!! THANK YOU dreamliner2012 FOR RUNNING IT THROUGH AND CLARIFYING!
THE ORIGINAL METHODS STILL WORK FOR ANYONE WHO WANTS TO USE RADIOCOMM AND DFS INSTEAD!
ALL CREDITS TO CELLZEALOT'S THREAD AND ARNOLD SNARB'S POST
GIVE THEM YOUR PROPER THANKS!!!
this was done with stock bootloader, rom, no root, official EVERYTHING
video tutorial HERE
heres the quick rundown -
1: get the Motorola QC Diagnostics driver to install. hard with Win7 x64, but be diligent it does work.
2: boot your XT907/XT926 into BP Tools mode (Vol Up and Down + Power, scroll down to BP Tools hit Vol Up)
3: connect to your computer *duh*
4: open CDMA WS 2.7 or higher (google)
5: connect to your COM Port and press CONNECT
6: click the SECURITY tab and enter 000000 as SPC and click SEND
7: click the MAIN tab and click READ *dunno if you need to but I did for safe measure*
8: click the MEMORY tab and select READ under NV ITEMS. dismiss the SPC prompt
9: First Item to read is 8322. Last Item to read is 8323. click SAVE and name the .txt file whatever you want, just remember where you put it
10: open the .txt file you just saved and under 8322 you will see 01 00 00 00 00 etc. change 01 to 00 and save the .txt file. DONT CHANGE 8323!!!
11: back in CDMA WS click WRITE under NV ITEMS. dismiss the SPC prompt again
12: find the .txt file you just edited and click OK
13: reboot the phone and put in your preferred Sim
14: in Settings go to More... under Wireless Networks and change your Network Mode to GSM/UMTS
15: SUCK IT VERIZON
happy days ahead for all!
don't forget that THANKS button :victory:
***DISCLAIMER***
NOT RESPONSIBLE FOR YOUR LACK OF ABILITY TO FOLLOW SIMPLE DIRECTIONS RESULTING IN A BRICKED DEVICE!
---from cellzealot on how to load Win7 x64 drivers---
cellzealot said:
Here is a screenshot of Device Manager on my PC on WIN7 64 bit with the latest 6.2 Motorola USB drivers and my XT907 connected in BP Tools mode with all of the interfaces highlighted.
There are 3 modems, 1 network device and 1 COM port that should be present and installed.
The 6.2 driver set has signed versions for these device interfaces so no force loading should be required and they should install automatically when the phone is connected in BP Tools mode with USB debugging enabled.
Make note of the port number assigned to the COM Port as that is the port you will use for CDMA WS or DFS or any other QC based NV access tool.
The QC Interface is the Motorola QC Diag Port.
Right click and choose Update Drivers then choose Do not load drivers automatically. Allow me to choose from a list of available devices.
Scroll down to Ports: COM/LPT and then Motorola and then Motorola QC Diag Port.
It will warn about unsigned drivers, just click Install anyway and it will load the driver and show up with a COM port number assigned.
Use that COM port for CDMA WS to edit the NV.
If you continue to have problems, I suggest reflashing the firmware or just the modem and fsg.mbn in fastboot, and starting over.
Click to expand...
Click to collapse
Thanks for some clarification on a confusing subject. Might want to move it to the General section or get it stickied.
Sent from my XT907 using xda premium
Leraeniesh said:
Thanks for some clarification on a confusing subject. Might want to move it to the General section or get it stickied.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
how would i go about making a request for such thing or would i have to do it myself?
dragonhart6505 said:
how would i go about making a request for such thing or would i have to do it myself?
Click to expand...
Click to collapse
Just contact a moderator and I'm sure they'd be able to help.
Sent from my XT907 using xda premium
Leraeniesh said:
Just contact a moderator and I'm sure they'd be able to help.
Sent from my XT907 using xda premium
Click to expand...
Click to collapse
gratzi ^_^
6: click the SECURITY tab and enter 000000 as SPC and click SEND
I got to this step, however I did not get a popup and at the bottom of the CDMA Workshop window reads the following error:
"Failed.. Phone does not answer"
Any suggestions?
lallafa said:
6: click the SECURITY tab and enter 000000 as SPC and click SEND
I got to this step, however I did not get a popup and at the bottom of the CDMA Workshop window reads the following error:
"Failed.. Phone does not answer"
Any suggestions?
Click to expand...
Click to collapse
you have the proper drivers installed i am assuming? check your device manager. your looking for Motorola QC Diagnostics Port. find the COM Port your phone is connected to then select it in CDMA WS.
dragonhart6505 said:
you have the proper drivers installed i am assuming? check your device manager. your looking for Motorola QC Diagnostics Port. find the COM Port your phone is connected to then select it in CDMA WS.
Click to expand...
Click to collapse
Okay, I have followed all of the instructions, went along with the video, everything seemed to work okay... I haven't gotten the Network Error popup message yet... However, I still do not have service.. I'm hoping it's just because I'm in a rural area. I'm going to drive around a bit and see if it changes.
My network mode is still under Global for preferred, should I change this?
lallafa said:
Okay, I have followed all of the instructions, went along with the video, everything seemed to work okay... I haven't gotten the Network Error popup message yet... However, I still do not have service.. I'm hoping it's just because I'm in a rural area. I'm going to drive around a bit and see if it changes.
My network mode is still under Global for preferred, should I change this?
Click to expand...
Click to collapse
yes to GSM/UMTS. probably why your not getting service. shoulda mentioned that
dragonhart6505 said:
yes to GSM/UMTS. probably why your not getting service. shoulda mentioned that
Click to expand...
Click to collapse
Okay, I changed the settings, and have turned my phone off and back on, hopefully this works, fingers crossed
lallafa said:
Okay, I changed the settings, and have turned my phone off and back on, hopefully this works, fingers crossed
Click to expand...
Click to collapse
and the verdict?
dragonhart6505 said:
and the verdict?
Click to expand...
Click to collapse
Well, after driving for about 15 minutes, still with the "Emergency Calls Only" symbol, I was about to turn around and give up...
and I got one bar, then two bars... then full service!! Everything works great, I am now running (what once was) a Verizon-locked Motorola Razr XT907 with the JellyBean 4.1.2 update, on Straight Talk's monthly service (with an activated Straight Talk card).
I kind of want to have your babies, but I hope a thanks and a subscription to your YouTube will do Thanks again SO much!
dragonhart6505 said:
ALL CREDITS TO CELLZEALOT'S THREAD AND ARNOLD SNARB'S POST
GIVE THEM YOUR PROPER THANKS!!!
video tutorial HERE
heres the quick rundown -
1: get the Motorola QC Diagnostics driver to install. hard with Win7 x64, but be diligent it does work.
2: boot your XT907/XT926 into BP Tools mode (Vol Up and Down + Power, scroll down to BP Tools hit Vol Up)
3: connect to your computer *duh*
4: open CDMA WS 2.7 or higher (google)
5: connect to your COM Port and press CONNECT
6: click the SECURITY tab and enter 000000 as SPC and click SEND
7: click the MAIN tab and click READ *dunno if you need to but I did for safe measure*
8: click the MEMORY tab and select READ under NV ITEMS. dismiss the SPC prompt
9: First Item to read is 8322. Last Item to read is 8323. click SAVE and name the .txt file whatever you want, just remember where you put it
10: open the .txt file you just saved and under 8322 you will see 01 00 00 00 00 etc. change 01 to 00 and save the .txt file. DONT CHANGE 8323!!!
11: back in CDMA WS click WRITE under NV ITEMS. dismiss the SPC prompt again
12: find the .txt file you just edited and click OK
13: reboot the phone and put in your preferred Sim
14: in Settings go to More... under Wireless Networks and change your Network Mode to GSM/UMTS
15: SUCK IT VERIZON
happy days ahead for all!
***DISCLAIMER***
NOT RESPONSIBLE FOR YOUR LACK OF ABILITY TO FOLLOW SIMPLE DIRECTIONS RESULTING IN A BRICKED DEVICE!
Click to expand...
Click to collapse
please set up how to instal the drivers manually
gagnier27 said:
please set up how to instal the drivers manually
Click to expand...
Click to collapse
Here is a screenshot of Device Manager on my PC on WIN7 64 bit with the latest 6.2 Motorola USB drivers and my XT907 connected in BP Tools mode with all of the interfaces highlighted.
There are 3 modems, 1 network device and 1 COM port that should be present and installed.
The 6.2 driver set has signed versions for these device interfaces so no force loading should be required and they should install automatically when the phone is connected in BP Tools mode with USB debugging enabled.
Make note of the port number assigned to the COM Port as that is the port you will use for CDMA WS or DFS or any other QC based NV access tool.
cellzealot said:
Here is a screenshot of Device Manager on my PC on WIN7 64 bit with the latest 6.2 Motorola USB drivers and my XT907 connected in BP Tools mode with all of the interfaces highlighted.
There are 3 modems, 1 network device and 1 COM port that should be present and installed.
The 6.2 driver set has signed versions for these device interfaces so no force loading should be required and they should install automatically when the phone is connected in BP Tools mode with USB debugging enabled.
Make note of the port number assigned to the COM Port as that is the port you will use for CDMA WS or DFS or any other QC based NV access tool.
Click to expand...
Click to collapse
In my particular case, the drivers does not loading here is a picture, how can i do that manually?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
gagnier27 said:
In my particular case, the drivers does not loading here is a picture, how can i do that manually?
Click to expand...
Click to collapse
The QC Interface is the Motorola QC Diag Port.
Right click and choose Update Drivers then choose Do not load drivers automatically. Allow me to choose from a list of available devices.
Scroll down to Ports: COM/LPT and then Motorola and then Motorola QC Diag Port.
It will warn about unsigned drivers, just click Install anyway and it will load the driver and show up with a COM port number assigned.
Use that COM port for CDMA WS to edit the NV.
If you continue to have problems, I suggest reflashing the firmware or just the modem and fsg.mbn in fastboot, and starting over.
cellzealot said:
The QC Interface is the Motorola QC Diag Port.
Right click and choose Update Drivers then choose Do not load drivers automatically. Allow me to choose from a list of available devices.
Scroll down to Ports: COM/LPT and then Motorola and then Motorola QC Diag Port.
It will warn about unsigned drivers, just click Install anyway and it will load the driver and show up with a COM port number assigned.
Use that COM port for CDMA WS to edit the NV.
If you continue to have problems, I suggest reflashing the firmware or just the modem and fsg.mbn in fastboot, and starting over.
Click to expand...
Click to collapse
Thanks for this cellzealot! I'll quote this in the OP so it'll be easier to find soon as I get to my office in the morning
lallafa said:
Well, after driving for about 15 minutes, still with the "Emergency Calls Only" symbol, I was about to turn around and give up...
and I got one bar, then two bars... then full service!! Everything works great, I am now running (what once was) a Verizon-locked Motorola Razr XT907 with the JellyBean 4.1.2 update, on Straight Talk's monthly service (with an activated Straight Talk card).
I kind of want to have your babies, but I hope a thanks and a subscription to your YouTube will do Thanks again SO much!
Click to expand...
Click to collapse
Will do just nicely and your quite welcome!
dragonhart6505 said:
Will do just nicely and your quite welcome!
Click to expand...
Click to collapse
done!!!!
thanks to you and cellzealot..
gagnier27 said:
done!!!!
thanks to you and cellzealot..
Click to expand...
Click to collapse
Anytime
This guid shows two things:
1. How to enable QPST and USB diag mode.
2. How to enable rSAP.
Please notice, I'm not responsible for any damage in hard- and software of your devices, if you are following this guid. You do all on your own risk.
Click to expand...
Click to collapse
For this guid your device have to be rooted.
In the newer versions of OnePlus' CyanogenMod diag mode is disabled in kernal. Therefore you have to flash an earlier ROM. In this step download Calkulin's Stock Rooted XNPH44S ROM and store zip to your device.
Go to recovery and make a full backup. This is really necessary to preserve the state of your phone.
Wipe Dalvik Cache, System, Data and Cache. ATTENSION: This will delete all your settings, apps and app data!
Install XNPH44S ROM
After rebooting system go to Settings -> About Device -> tab ten times on Build-Number to unlock developer settings. Than go to Developer settings and make sure USB debugging is enabled.
Download the package, containing driver and QPST
Connect your device to USB, go to Settings -> Storage -> USB computer connection and deselect both MTP and PTP.
For Win8 and Win10: restart with deactivated driver signature check.
Open ADB (Android SDK) and type following commands:
Code:
adb shell
Code:
su
Code:
setprop sys.usb.config diag,adb
Go to Windows Device Manager and open Other Devices node. There are two entries of our device "A0001". Klick right on the first one and choose Update driver software -> Browse my computer... -> Let me pick from a list... -> Show all devices -> Have disk -> Browse...
Browse to folder Driver in downloaded package, than open Win x64 or Win x86 corresponding to your system, select *.inf file and apply.
After seccessful installation there is a Modems node in Device Manager, containing node HTC USB Modem. Right click and go to Properties. In top of the Modem tab page is the information about used COM-port. Remember that COM<number>.
Go to QPST folder in downloaded package and execute setup.exe to install QPST.
Open QPST Configuration from windows Start menu, go to Ports tab page and click on Add New Port.... Type (the remembered) COM<number> to the "Port:" text box and OPO to the "Port Label:" text box. Than click on OK.
Active Phones tab page should now look like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you can use QPST.
Open EFS Explorer from windows Start menu. It may take a moment to read data from your device.
On left side you can see a folder tree like in file explorer. Navigate to /nv/item_files/modem/qmi/uim
Click right on right side and than Copy Item File from PC. Browse to EFS Entry folder of downloaded package and choose file sap_security_restrictions.
Close all windows and reboot your device. If you want, you can repeat the steps 10, 16 and 17 to verify success.
Boot to recovery and restore your backup.
Now go to Google Play and download app Bluetooth SIM Access Install and app Bluetooth SIM Access (Trial)
Open Install app and click on Install system files. The phone have to reboot after installation. If you want to verify successful installation, open app again, the desintall button have to be enabled now.
Enable your Bluetooth
Open Bluetooth SIM Access (Trial) app go to Settings -> Check SIM Access. If there no errors and several entries with green check marks, than rSAP is working now.
Files:
Package (On Mega click on 'download in browser')
ROM (On Mega click on 'download in browser')
Acknowledgement:
Thank you devilsshadow, for your tutorial, which showed me how to setup QPST.
Thank you Calkulin, for your ROM, which makes it possible to use QPST.
Special thanks goes to Martin , for developing his great apps and making our phones better.
Great! Thanks a lot!
Finally got my OPO working with my VW premium bluetooth car system
EFS Explorer crashes with a Runtime error upon opening sap_security _restrictions file.
Win 10 64Bit.
Edit:
Got it to work with the Frankenstein modem from here:http://forum.xda-developers.com/oneplus-one/general/firmware-modem-oneplus-one-lollipop-t3300907
Looks like it does not work with the newer modems, i was using bacon_firmware_update_2016_1-25_.4.0.1.c7-00011.zip
Hi, do you have further informatiom about the crash? Exact error message?
Did you try windows compatibility mode?
I used win 8.1 x64. Sorry I don't have win 10 to test it.
I used Win 10 Pro 64bit, and had no problems using the software.
Thank you very much for the precise description! I linked it from android-rsap
With my newly acquired OPO I first could not install the diag drivers. The USB id seems to have changed from VID_05C6&PID_6765&MI_00 to PID_676C. After changing that in the inf file the installation worked and I could run QPST.
Great. Thanks a lot.
Can i flash after enabling rSAP CM13, or will it disable rSAP again?
Thank you.
I'm wondering about this myself.
I was running jgcaap CM13 before I did enable RSAP. Took a backup of everything in TWRP first. And restored everything except EFS after (thought that if I flashed EFS I would loose rsap again, but I'm not sure). Everything is working fine btw
fitzpete said:
EFS Explorer crashes with a Runtime error upon opening sap_security _restrictions file.
Win 10 64Bit.
Click to expand...
Click to collapse
This seems to happen with more recent baseband versions. They require the "Factory Test Mode" (ftm_mode) to be set to allow changes. ftm_mode is NV item 453. It can be modified with the QXDM tool.
Now the value of ftm_mode is cached inside the baseband software. Currently I don't know a better solution than to reboot the phone. Sadly in some phones (OnePlus 2) the value doesn't survive the reboot.
Mugen_Civic said:
Great. Thanks a lot.
Can i flash after enabling rSAP CM13, or will it disable rSAP again?
Thank you.
Click to expand...
Click to collapse
Yesterday I do enable RSAP, wow I am really happy about that.
What happens when do a full wipe for flash and install an clean ROM? Is RSAP deactivated again?
Gesendet von meinem A0001 mit Tapatalk
hums87 said:
What happens when do a full wipe for flash and install an clean ROM? Is RSAP deactivated again?
Click to expand...
Click to collapse
No. RSAP will stay enabled.
Hi many thanks for this guide but all link are dead ! can you reupload them ?
thanks
Thanks for the hint. I will reupload it soon and give an announcement.
mamath53 said:
Hi many thanks for this guide but all link are dead ! can you reupload them ?
thanks
Click to expand...
Click to collapse
I reuploaded the files to other hoster.
Could someone tell me what this is good for?
Flatric said:
Could someone tell me what this is good for?
Click to expand...
Click to collapse
RSAP (remote SIM access protocol) is a communication standard for free speeking systems. Eg. Volkswagen concern uses it in its cars. The SIM of your phone is cloned per bluetooth to your cars build in mobile phone module. The radio functions (calling/SMS) are disabled on your phone while connection and executed by your car. That is good for battery, electro smog in your car and connectivity.
But it have drawbacks too. No internet connection on phone while connection. This problem is solved in newer cars by providing a wifi hotspot, which uses the internet contract of your SIM.
Hi
If I open Bluetooth SIM Access (Trial) app, there is no "Check SIM access" option.
Did I do something wrong?
r0tati0n said:
Hi
If I open Bluetooth SIM Access (Trial) app, there is no "Check SIM access" option.
Did I do something wrong?
Click to expand...
Click to collapse
Hi, I think the check has moved to the installer app. See section 3.
Thanks
Altough I couldnt find anything in there too...
In the installer app I get 3 check marks:
System Files installed, Connect to Socket, Connect to SIM, all green.
Does that mean I have RSAP?
Do I need anything else?
Can I uninstall the app and keep RSAP?
r0tati0n said:
Thanks
Altough I couldnt find anything in there too...
In the installer app I get 3 check marks:
System Files installed, Connect to Socket, Connect to SIM, all green.
Does that mean I have RSAP?
Do I need anything else?
Can I uninstall the app and keep RSAP?
Click to expand...
Click to collapse
I think so. Test it with your car. Thats the reason why the trial app exists. But you have to know that the trial app swaps numbers in contact, therefore it is not good for all day use.
I haven't uninstalled the installer app. In this app you can see updates for the system files. But the updates are seldom and if the installed version works for you, I think it's no problem to uninstall it.
Hello people ...
Here it's official ... since two days ago the official update for our LG MAGNA for version 6.0 of Android.
We had to wait a long time .. but ... essentially it's there.
Contrary to what I expected ... it is very well done ... I mean the LG interface with this version of MM. The least I can say is that it is purified ... LG overlay is married to that of pure Android ... finished the coarseness of the characters and the colors too dull (for my taste) of LG interface .
Frankly I like it a lot.
It remains to wait for an opportunity to ... ROOT and a custom recovery (why not ... I'm always up for a custom ROM).
To come to this update ... it is only available for the CIS countries yet .. but .KDZ is available for download .. and it is this version that I installed CIS.
So for those who have received the update OTA .. it can install ... for those in a hurry (like me) .. or have ROOT their phone and install TWRP .. they can install this update via OTA ... so must follow this method.
I want to thank my friend Berong the XDA forum which was the precursor to try it and I was a big help to do it.
I put the method to the next post.
So ... to install this version of Marshmallow ... we will need the following.
Euuuh .. you are solely responsible for anything that may happen to your phone by following this method ... neither me nor xda forums are responsible .. blah .. you are warned .
So .. we will need:
- The .KDZ (V20A for CIS) of course available here : http://lg-phone-firmware.com/index.php?id_mod=237
- The LG Flashtool 1.8.6.527 utility from here : https://www.sendspace.com/file/df0h5a
- The extraction utility KDZ from here : https://www.sendspace.com/file/cqq0kk
- The LG drivers here : https://www.sendspace.com/file/6jtwob
First stage :
1- Download and install the drivers for LG
2. Extract the .KDZ
The purpose of this operation is to extract the .KDZ to use it in the flash utility.
To do this ..
- Download and Install KDZ Extractor ..
- Launch the application and select the file .KDZ
- Check all files (3) ... and click Extract KDZ
- When finished, we will have 3 new files (.DLL + .DZ + LIB).
Of these three the only files .DZ and .DLL will be used later.
3- INSTALL LG Flashtool:
- Download LG FLASTOOL RAR
- Unzip the archive
- Install it.
- Copy and paste the MegaLock.dll file in the installation folder (default c:\LG ).
4- Change Port communication :
- Connect the phone to the USB
- Go to Device Manager
- Find "Ports (COM & LPT)", click on the tab on the left to expand it. You should see "LGE Mobile USB Serial Port (COM)".
- Double click on "LGE Mobile USB Serial Port (COM)"> Port Settings> Advanced> next to "COM Port Number" choose "COM41".
- Click on "OK" and then "OK" again.
Here .. now everything is ready .. move to flash the firmware.
Second step :
- Switch off the phone.
- Go DOWNLOAD mode : off phone ... press and hold volume UP plug the usb cable (you are in Download mode).
- Launch LG Flashtool
- Select the manual mode
- Click on "..." and choose the .DLL file (the one extracted earlier from the KDZ).
- Click on "Add" and the choose .DZ file (the one extracted earlier from the KDZ).
- Uncheck upgrade dl and check board dl (very important).
- OK
- In the new window .. just click on yellow arrow (Top left)
- The flash process starts and takes about 4-5 minutes.
- Once finished .. it should display PASS
- The phone will restart
That's it ... you just have to configure your phone and enjoy.
PS: it may be that first start you come across a kind thing: FACTORY RESET STATUS .. then just do (thanks for BERONG) :
1. Remove Battery
2. Power on
3. Do not touch the screen when you see MINI OS
4. Hold power button while MINI OS visible in screen
5. A menu will pop out... Find NORMAL BOOT (+POWER) .
6. Tap that while holding the power button (by clicking simultaneously on several occasions on NORMAL BOOT and the POWER).
Enjoy.
I forgot what site I read about MINI OS workaround anyways credit to them It was not me who originally got that idea... anyways ...
I will just provide some screenies ...
1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.
3.
4.
Thank you BERONG ... good job
I added step 4 on the port change.
I'll be flashing back to 5.0.1 again, I can't live without root
I'll be checking this thread from time to time... Hoping for some development like
1. ROOT
2. BOOTLOADER unlock
3. RECOVERY TWRP
I will try it tonight, thanks for the guide! I'm sure our russian friends will get us root and twrp, they are very enthusiastic
Works on H500f.
Tnks
Works fine for me, tanks
Root and install TWRP on LG MAGNA with MARSHMALLOW .... from here : http://forum.xda-developers.com/andr...magna-t3396704
Thanks
Sent from my LG-H502 using XDA-Developers mobile app
I have just recently installed it. Had no problems whatsoever
Why do my phone wont display its data indicator... It is connected though, I just wonder why help meeeee... Is it connected with my region...? Im flasing/using/ same file with same method.
Sent from my LG-H502 using XDA-Developers mobile app
Hello people.
For those who have updated their MAGNA to android 6.0 official ... and want to use the SD card as internal storage .. and do not find this option when formatting the SD card here .. taking method LG forum in SPIRIT on XDA. This method has been tested by me and successfully.
- Backup your data on SD because all data will be lost after formatting and encryption SD card (you can copy the latest since the backup on PC.
- Enable USB debugging mode in developer settings.
- Open ADB SHELL command (from the ADB folder .. shift + right mouse button ... OPEN A WINDOW COMMAND)
- List avaliable disks to get disk ID. It can be done with following command:
sm list-disks
You will get your SD Card ID (ex.: disk:179,64, which will be used in next step.
In our example the id is 179.64 for you ... you-remember number that is yours.
After that .. we have the choice of using any SD card or internal memory or half If you want to use only part of SD as Internal Storage and rest as standard Removable Disk, for example 50:50, ...
So it recapitulates the command line:
For all of the SD card :
adb shell
sm list-disks
sm partition disk:179,64 private
For 50/50 of the SD card:
adb shell
sm list-disks
sm partition disk:179,64 mixed 50
Remember that 179.64 is an example .. ID with you to put yours
Here is a screenshot of the command 50/50
Good luck.
Failed PreviousLoad()
After selected the yellow arrow into LG flash tool a receive the error message that says "Failed PreviousLoad()"
ikki82 said:
After selected the yellow arrow into LG flash tool a receive the error message that says "Failed PreviousLoad()"
Click to expand...
Click to collapse
have you installed all necessary driver?
Sent from my LG-H502 using XDA-Developers mobile app
yes I have installed the correct driver
yes I have installed the correct driver (LGMobileDriver_WHQL_Ver_4.0.4), tested with 2 different laptops and different operative system, and I receive the same error. also using different usb ports and different usb cables.
can you provide some screenshots?
Sent from my LG-H502 using XDA-Developers mobile app
I dont have the option to upload screenshots
I dont have the option to upload screenshots
@ikki82.. I think you selected the wrong dll...
There is a v20a for kazakh...
Sent from my LG-H502 using XDA-Developers mobile app