Database Users

[GUIDE] Noob's Guide to setting up ADB

How to get working ADB-- The Expedient method
Since the release of the mtd ROMS the importance of being able to use ADB has greatly increased. This guide is designed to produce a working adb evironment in windows. It is designed be as simple as possible and to avoid command line as much as possible. This guide is not targeted towards advanced users who can set up a working adb environment on their own. If you can setup adb from Google's packages, please avert your eyes and read no further -- this guide will only bring out the elitist snob in you.
If you are still with me you have likely tried to set up adb and failed. Perhaps you have a bootloop in an mtd (cm7, miui, OMFGB) ROM and are trying to avoid losing everything with an Odin flash. Perhaps you are trying to troubleshoot in another way. Regardless, this guide will get you going.
Step 1: Install USB drivers.
A) If you are using a Touchwiz based ROM (COMROM, Evil Fascinate) you will need the Samsung Fascinate driver.
B) If you are using a MTD based ROM (ICS, CM7, MIUI, OMFGB) you will need to use the Nexus S drivers.
Step 2: After you install the appropriate driver, put your Fascinate into Debugging Mode by:
Gingerbread: Settings->Applications->Development then checking Debugging Mode.
ICS: debugging mode is found System Setting>Developer Options>USB Debugging.
Step 3: Connect your phone to your computer and open up Device Manager.
Step 4: DON'T SKIP THIS STEP. You will see Fascinate/Nexus S with possibly an exclamation mark, just double-click on it, Update Driver->Browse my computer for driver software->ADB Interface then choose Samsung Electronics Co., Ltd, then choose Samsung Android ADB Device.
Step 5: Download and install Droid Explorer. Please select the appropriate build for your PC architecture. Be sure to select "Set up the Android SDK For Me" during the setup.
Step 6: Launch Droid Explorer and select your phone.
To send ADB commands click the button in the red box in the image below.
To view logcats click the button in the blue box below.
Step 7: How to use Droid Explorer
{
"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"
}
Troubleshooting example:
You are on AOKP and set a bad overclock as boot settings. 3-fingering is a no-no and you get frozen during boot or a bootloop before entering the OS and therefore can't reach recovery. To get into recovery click the button in the red rectangle. Then type "reboot recovery" at any time during the phone boot process and press enter. Your phone should reboot and you should end up in recovery. Success!

I have a fully Functional adb, android skd, java, eclipse, all the stuff needed for a proper build environment, and I still use Droid explorer and Android Commander, for some things. Once you get used to these programs they are very useful especially for a simple app swap or adding an app to your system file. Good of you to share the process with others.

Nice guide, would have been easier than setting up a full adb environment on my work pc in addition to my home pc. Where was this 6 months ago?

Dude thank you so much for that nexus driver. I have not been able to get my ADB to work until now with that driver. Every other one I got wouldn't work and no one really could help me. Just kept saying install driver. Now ADB finally works. The Droid Explorer program is pretty cool too. Thanks very much!!

I've edited the guide a bit to make it easier to follow. This should be the final version of it unless someone has an issue or suggestion. I'm glad this has helped some folks and I hope it will continue to do so.

ok somethings wrong because i have followed every freaking guide there is including the wiki for cyanogenmod and this one and adb is still "not a valid command" or whatever in the command prompt......freaking hell
**now all of a sudden it's kinda working, if i choose reboot into recovery from the application it just reboots the phone, not into recovery.....and if i choose the log icon it says it cant connect to device even though the device is clearly shown as connected in the main screen......sheesh
THANK YOU MAKE THIS STICKY NOW OR I WILL PUNCH BABIES

Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked

Just passing along a thanks for this guide in a world where OC/UV is so easy to screw up.

sfobrien said:
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Click to expand...
Click to collapse
During the DroidExplorer setup process did you tell it to "setup adroid sdk environment for me"? It should have been a blue link.

bobloblaw1 said:
During the DroidExplorer setup process did you tell it to "setup adroid sdk environment for me"? It should have been a blue link.
Click to expand...
Click to collapse
Yes and it appeared to install correctly.

+1 for sticky

sfobrien said:
Have went through the process three times all with the same result. Explorer doesn't see my phone. Any ideas?
Using the Nexus drivers (running CM7)
Drivers installed properly.
Using the 64 bit explorer (running Windows 7)
debugging checked
Click to expand...
Click to collapse
I have a different but similar issue. It sees my device when connected and disconnected but I can't do anything. If I choose reboot it rebooted. If I choose reboot recovery it just rebooted, no recovery. I can see the devices tree directory but if I try to access any of them I get an error. Also if I click the logcat button it opens the terminal window but has an error, says it can't connect or something. If I click on the terminal button it opens the terminal but no commands are recognized. But when I connect and disconnect my device it shows up and in device manager there are no errors.

Hmm are you sure that the USB cable you are using is still good? will it mount for data transfer?
Also, this generally shouldn't be necessary but it is possible that something is messed up in your PC USB install. At one point I had to clear off and reinstall all of my USB drivers. Everything worked fine after the drivers reinstalled.
There's a lot of places where errors come in. I'd like to try and figure out your guys' problem(s) so that I can update the guide and potentially save other people some time.

I just set up adb on my arch linux box, I think it was easier to set up this vs windows.
Sent from my I500 using XDA Premium App

allcity187 said:
I just set up adb on my arch linux box, I think it was easier to set up this vs windows.
Sent from my I500 using XDA Premium App
Click to expand...
Click to collapse
Probably. But that requires you to have a linux box setup and handy; which many people do not have.

Well you can always dual boot your computer. I have windows 7 and arch linux set up. I'm usually on linux but I still have software that I use on windows, so that's why I kept it.
Sent from my I500 using XDA Premium App

bobloblaw1 said:
Hmm are you sure that the USB cable you are using is still good? will it mount for data transfer?
Also, this generally shouldn't be necessary but it is possible that something is messed up in your PC USB install. At one point I had to clear off and reinstall all of my USB drivers. Everything worked fine after the drivers reinstalled.
There's a lot of places where errors come in. I'd like to try and figure out your guys' problem(s) so that I can update the guide and potentially save other people some time.
Click to expand...
Click to collapse
My USB cable is fine. Went back uninstalled the drivers and explorer. Downloaded fresh copies of both and same thing????
Giving up for now. In the event of a crash I can Odin back,rebuild,restore apps, etc. in about an hour. Less time than I have spent trying to get this to work! LOL. For now I'm back on the stock CM7 kernel and not doing any tweaking that might cause a crash. All is good thanks guys.

sfobrien: Sorry I couldn't get thisto work for you.
jamesandmandy: Did you ever flash anything in red recovery? Are you able to get into blue recovery by the normal method? Your issue sounds like something on the phone recovery end if You are able to send commands to it successfully over adb.

bobloblaw1 said:
sfobrien: Sorry I couldn't get thisto work for you. /QUOTE]
Hey no problem. I think it is some kind of glitch between Windows 7 and the explorer program. CM7 is an awesome upgrade so no complaints here.
Click to expand...
Click to collapse

Thanks for this. I've always avoided adb because it seemed to complicated to setup/learn. I'm up and running.
Sent from my GT-P7510 using XDA Premium App

[FIX][WIP] Blank Screen Boot (hardbrick-no bootloader)

Hello guys!
since we all do mistakes, i alongside alot of people have formatted /sys_boot partition on our dear RM-980.
that partition is actually the bootloader and without it the phone bricks.
the signs of that brick is black and no screen lights but a vibration that indecates "PLEASE HELP ME!!"
connecting it to windows will cause seeing a drive that windows can't detect and it will ask to format it which is the worst IDEA EVER!! and fastboot will never detect the phone.
if plugged in to Linux you'll get full control over all phone partitions including internal SD, system, boot, bootloader etc.
its easy to flash images from linux side using gparted or "disks in ubuntu which i use" but also fastboot can't be used.
all we need is an mmcblk0p3 dump to save all dead NOKIA X2 lives!!
it can be easily done on ADB on any computer if you are willing to help follow the following easy steps:
start up your nokia x RM-980, enable debugging, connect to USB and find an ADB then give it next comand:
Code:
adb shell
you should be in your phone shell. then:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3.img
that will backup your bootloader as mmcblk0p3.img in root of your sdcard
now compress that in a zip and donate it here with your phone CODE (you can find it in the back of your phone)
I will collect the bootloaders for all the CODEs you people will send.
Thank you very much in advance
UPDATE!
IT WORKED ON MY NOKIA X phone and it should work on X2 too!! but i have not tested it (i do not own the device and there is no1 here willing to help)
but in case someone wanted to help here's how you do it.
Please DO NOT DO IT unless you REALLY KNOW what you are doing!!
When you find a working X2 (or maybe someone from this forum can upload it and post it) do the following on the working X2:
First - Backing Up a Working Bootloader from a Working NOKIA X2: (you can do on Windows or Linux)
1- access it with adb from PC while its ON (connect to USB, enable dev debugging..etc) you should know these stuff if you are willing to fix your phone, if you don't you should take it to NOKIA CARE Centers to fix it for you.
2- type the following in ADB:
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3.img
then check your phone internal storage you will find an image called (mmcblk0p3.img) copy it to your PC
Second - Flashing the Working Bootloader on the Not Working X2: (requires Linux get an Ubuntu)
1- Boot up in a Working Ubuntu (or Ubuntu Live CD)
2- Download and extract the attachment in Home Folder
3- Open up Ubuntu Menu and look up (Disks)
4- Remove your NOKIA X Battery and Unplug it from any USB or charger, re-insert battery, then hold Power button untill phone Vibrates then release power button. after you do all that plug it in USB to your computer
** if you have done those steps perfectly you should see a new device in (Disks) application will say(something-qualcomm-something) depends on the type of your phone. you will see a table on the right when you click it that has 3 partitions and then many other partitions grouped up don't touch these at all**
5- click on the third partition from left it should be in size of 52MB.
6- right click it and choose (Restore Disk from an Image).
7- Browse to your Home folder then in (NOKIA X RM980 BOOTLOADER) and choose mmcblk0p3.img
8- it will ask you if you are sure click Restore.
9-Wait for it to finish. when it does close Disks then unplug phone, remove battery, re-insert it, power up your phone.

I don't understand why can you use mmcblk0p3 of Nokia X (RM-980) to save Nokia X2 (RM-1013).

nvuphi said:
I don't understand why can you use mmcblk0p3 of Nokia X (RM-980) to save Nokia X2 (RM-1013).
Click to expand...
Click to collapse
we cant use bootloader of NOKIA X for NOKIA X2 "at least i never tried" however the issue still happens for both phones and its caused by same "mistake" and so i wunna start trying to save these phones and not force people to just go to NOKIA Care "since we don't even have one here"
the only way to do so is for a single donator to upload his bootloader image and the community will thank him forever!
but it seems like no1 is willing to help until now..

I try to make a Unbricker Tool. But I need proper preload, boot and system partitions. (bootloader is about.img and I have it already)
When I have all product codes image files, I will create a tutorial for unbricking via Linux.
After that try to build a cygwin based Microsoft app of it.

symbuzzer said:
I try to make a Unbricker Tool. But I need proper preload, boot and system partitions. (bootloader is about.img and I have it already)
When I have all product codes image files, I will create a tutorial for unbricking via Linux.
After that try to build a cygwin based Microsoft app of it.
Click to expand...
Click to collapse
this is exactly what i said ... however thank you for effort and if u already have a NOKIA X2 thats working please upload ur 1st 3 partitions independently

xWaLeEdOoOx said:
this is exactly what i said ... however thank you for effort and if u already have a NOKIA X2 thats working please upload ur 1st 3 partitions independently
Click to expand...
Click to collapse
Which partitions do you want?

Will this software help if the device is unbootable? like if i cant even boot it up (No vibrate...no recovery..) but i still can flash software even after faslhing the software..my phone isn't turning on..would this help?
---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------
I have the Nokia Care Suite and i downloaded the Firmware for my phone...now Which .IMG file do i need to upload?
is it the BOOT.IMG?

symbuzzer said:
Which partitions do you want?
Click to expand...
Click to collapse
mmcblk0p1 , mmcblk0p2 and mmcblk0p3. u can follow the steps i stated in first post

DinethIrusha said:
Will this software help if the device is unbootable? like if i cant even boot it up (No vibrate...no recovery..) but i still can flash software even after faslhing the software..my phone isn't turning on..would this help?
---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------
I have the Nokia Care Suite and i downloaded the Firmware for my phone...now Which .IMG file do i need to upload?
is it the BOOT.IMG?
Click to expand...
Click to collapse
my friend, if NOKIA CARE can flash "do Recovery" for your phone then this post is not the right one for you. our issue that NOKIA CARE does not detect the phone anymore because of damaged bootloader.
about your phone, do you really think its a software issue?! "maybe the screen isnt working or broken!!"

xWaLeEdOoOx said:
my friend, if NOKIA CARE can flash "do Recovery" for your phone then this post is not the right one for you. our issue that NOKIA CARE does not detect the phone anymore because of damaged bootloader.
about your phone, do you really think its a software issue?! "maybe the screen isnt working or broken!!"
Click to expand...
Click to collapse
i don't think so... cuz i used my phone,Patched / Installed Google Play Store and after reboot it doesn't turn on..nor vibrate..
so its hard bricked...

xWaLeEdOoOx said:
Hello guys!
since we all do mistakes, i alongside alot of people have formatted /sys_boot partition on our dear RM-980.
that partition is actually the bootloader and without it the phone bricks.
the signs of that brick is black and no screen lights but a vibration that indecates "PLEASE HELP ME!!"
connecting it to windows will cause seeing a drive that windows can't detect and it will ask to format it which is the worst IDEA EVER!! and fastboot will never detect the phone.
if plugged in to Linux you'll get full control over all phone partitions including internal SD, system, boot, bootloader etc.
its easy to flash images from linux side using gparted or "disks in ubuntu which i use" but also fastboot can't be used.
all we need is an mmcblk0p3 dump to save all dead NOKIA X2 lives!!
it can be easily done on ADB on any computer if you are willing to help follow the following easy steps:
are you successful in unbricking your nokia x2 i am also facing same issue like you unable to unbrick with nokia care suite mine is nokia x2ds
start up your nokia x RM-980, enable debugging, connect to USB and find an ADB then give it next comand:
Code:
adb shell
you should be in your phone shell. then:
Code:
dd if=/dev/block/mmcblk0p3 of=/sdcard/mmcblk0p3.img
that will backup your bootloader as mmcblk0p3.img in root of your sdcard
now compress that in a zip and donate it here with your phone CODE (you can find it in the back of your phone)
I will collect the bootloaders for all the CODEs you people will send.
Thank you very much in advance
Click to expand...
Click to collapse
are you successful in unbricking your device,my nokia x2 ds also hard bricked unable to unbrick my x2 using nokia care suite it is giving sahara error,i even tried with qfil,emmc download tools but unsuccessful to unbrick my x2 ,please tell me your procedure i will try to unbrick my x2 using your tutorial,my x2 detected as qualcomm hsusb qdloader 9008 in my pc,please help me to unbrick my device
---------- Post added at 08:30 PM ---------- Previous post was at 08:27 PM ----------
[/COLOR]
symbuzzer said:
I try to make a Unbricker Tool. But I need proper preload, boot and system partitions. (bootloader is about.img and I have it already)
When I have all product codes image files, I will create a tutorial for unbricking via Linux.
After that try to build a cygwin based Microsoft app of it.
Click to expand...
Click to collapse
please give me boot image file and tell me linux procedure to unbrick nokia x2

harish120 said:
are you successful in unbricking your device,my nokia x2 ds also hard bricked unable to unbrick my x2 using nokia care suite it is giving sahara error,i even tried with qfil,emmc download tools but unsuccessful to unbrick my x2 ,please tell me your procedure i will try to unbrick my x2 using your tutorial,my x2 detected as qualcomm hsusb qdloader 9008 in my pc,please help me to unbrick my device
---------- Post added at 08:30 PM ---------- Previous post was at 08:27 PM ----------
[/COLOR]
please give me boot image file and tell me linux procedure to unbrick nokia x2
Click to expand...
Click to collapse
you can extract it from Advanced Nokia X2 Tool

harish120 said:
please give me boot image file and tell me linux procedure to unbrick nokia x2
Click to expand...
Click to collapse
my friend, you need a working X2 to take the bootloader image from.
since i have NOKIA X i cant help you however the procedure is the same.
i updated my post please read it carefully. however i can not guarantee that your issue can be fixed with this procedure so please DO NOT DO IT unless you REALLY KNOW what you are doing!!

xWaLeEdOoOx said:
my friend, you need a working X2 to take the bootloader image from.
since i have NOKIA X i cant help you however the procedure is the same.
i updated my post please read it carefully. however i can not guarantee that your issue can be fixed with this procedure so please DO NOT DO IT unless you REALLY KNOW what you are doing!!
Click to expand...
Click to collapse
can i use bootloader image file which is extracted from symbuzzers advance nokia x2 tool (see post #12) to flash my nokia x2 boot partition using your method,my nokia x2 is hard bricked,unable to unbrick it using nokia care suite,i even tried with qfil but not successful i am getting sahara error,my x2 completely hard bricked even no vibration buy my x2 is detected as qualcomm usb when connected to windows pc,i tried every thing but not successful to unbrick my nokia x2 ,i want to try your method to unbrick my nokia x2,please help me,anyone who has x2 bootloader image file (backup) please upload..

harish120 said:
can i use bootloader image file which is extracted from symbuzzers advance nokia x2 tool (see post #12) to flash my nokia x2 boot partition using your method,my nokia x2 is hard bricked,unable to unbrick it using nokia care suite,i even tried with qfil but not successful i am getting sahara error,my x2 completely hard bricked even no vibration buy my x2 is detected as qualcomm usb when connected to windows pc,i tried every thing but not successful to unbrick my nokia x2 ,i want to try your method to unbrick my nokia x2,please help me,anyone who has x2 bootloader image file (backup) please upload..
Click to expand...
Click to collapse
my friend i am not sure what method did symbuzzers use to back up the partition, if his code used
dd if=/dev/block/mmcblk0p3 of=/sdcard/(WHATEVER).img
from ADB to back it up,
then it should theoretically work.
also when u plug your phone to Windows it should show you a Flash drive that need to be formatted, if you formatted it then this method will not work for you anymore.
and i've checked his post it has nothing stating a backup.
can you please boot up an Ubuntu Live CD , connect your phone powering it on, open up Disks aplication and send me a screenshot of Qualcom device?

OHH
Thanks..

device not found
guys, do we need drivers for ubuntu? I followed the steps in first page and I have my Nokia X2 usb debugging on but adb wont detect my device.. my X2 is running CM11..
{
"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"
}
Edit***
I thought backup only works on linux so I installed ubuntu (which I have zero knowledge using it) but failed.. after searching google I saw someone did it on windows so I'm back to windows and tried I did get into the shell but I can't access the backup /dev/block/mmcblk0p3 showing "Permission denied"..
Edit***
I did it using adb root.. sorry about that.. my problem now is that ubuntu didn't see my other device (Nokia XL) in disks.. what's weird is, when I insert this device in windows.. it shows that the device is connected and driver is present in my device drivers even though this phone is completely dead (no vibrate, no fastboot, no lights)..

nokia xl black screen dead
my nokia xl connect to pc (win 7 ) detect qulicomm but not disply mmc strge ..
when connect to Ubuntu phone not detect,,, plzz help sry for bad english

my nokia xl connect to pc (win 7 ) detect qulicomm but not disply mmc strge ..
when connect to Ubuntu phone not detect,,, plzz help sry for bad english

[GUID] Enable Remote SIM Access Protocol (rSAP) on the OnePlus One, using QPST

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.

[HOW TO]Guideline / Install MTK drivers / How to Root / Flash a Rom / IMEI Restore

In this Thread i will explain how to set up MTK drivers and Flashtools.
Guideline:
Post #1 : Set up MTK drivers in Windows 8 / 8.1 / 10
Post #2 : Use Flashtools for MTK Devices
Post #3 : How to Root Stock Rom
Post #4 : Windows 10 MTK Drivers installation ( just in case post #1 dont work )
Post #5 : Lost IMEI Backup​
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
How to Install MTK drivers in Windows 8 / 8.1 / 10
what we need:
MTK Vcom Preloader Driver 2.0
Download : https://www.androidfilehost.com/?fid=24438995911977169
First thing we need is to Disable the Signed Driver verification on Windows :
To disable driver signature verification, we’re going to need to get into the Troubleshooting options from the boot manager.
The easiest way to bring this screen up is using this secret trick.
Hold down the SHIFT key while you click Restart.
{
"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"
}
Once your computer has rebooted you will be able to choose the Troubleshoot option.
Then head into Advanced options.
Then Startup Settings.
Since we are modifying boot time configuration settings, you will need to restart your Computer one last time.
After restarting your computer a second time,
choose Disable driver signature enforcement from the list by typing the number 7 on your keyboard.
That’s all there is to it. Your PC will then reboot and you will be able to install unsigned drivers.
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Now its Time to open SP_Driver_v2.0.zip and start the DriverInstall.exe
it will open the install prompt . Press okay and dont change the installation path
Code:
C: // program files / Mediatek / Driver Package
during the installation it will start the verification window security.
Click on Install this driver software anyway
There will be an Error Message . - We Ignore it !
-Now Open your Device Manager and leave it open.
-Power Off your Phone and connect it with your Pc.
-you will see Under ports ( COM & LPT ) a Preloader unknown device
right click on there and click on Driver update/installation.
-Choose manually search for drivers
-Browse to C:// program files / Mediatek / Driver Package and apply.
-If all went good you have successfully installed the MTK Vcom Drivers. :good:
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>​

How to Use Flashtools
i use SP_Flash_Tool_Windows_v5.1520.00.000 and never had a problem with it.
Its for most all MTK Phones and for all Elephone Devices
Download Link: https://www.androidfilehost.com/?fid=24438995911977217
- Extract the Flashtool zip folder to your Desktop
- Click flash_tool.exe to open the Tool
- You will see two "folder buttons" Download agent and Scatter-loading
- Into Download agent place the MTK_AllInOne_DA.bin file .
its in your Flashtools folder
- Into Scatter-loading place the Scatter.txt
All Stock Roms / Custom Recoverys have one Scatter.txt in their Zip files.
- Make sure that every partition is checked
-IMPORTANT NOW, Flashing Part-
-Power Off your Device!
-Press on the Download Button!
-Connect your Device with PC and wait until all is flashed
-you will see a Green Mark when all is done
-Disconnect your Device and press Power button to Reboot.
:fingers-crossed::good::fingers-crossed:
------------------------------------------------------------------------------------------------------------------------------------------------​

How to Root Stock Rom
-If you want to Root your prefered Stock Rom
-Place SuperSU into your Sdcard
-Flash a Custom Recovery with Flashtools and its Scatter.txt
-Hold Vol+ and Power to get into Bootloader Menu
-Navigate with Vol+ and apply Recovery with Vol-
-Flash Supersu.zip
-Reboot
Stock Roms:
Stock ROM Elephone P9000_Android 6.0_20160315 Link: http://bbs.elephone.hk/thread-9967-1-1.html#[email protected]
CWM Recovery:
Link : https://www.androidfilehost.com/?fid=24459283995304518
100% bug free Supersu v.2.46.zip
https://download.chainfire.eu/696/SuperSU/​

Windows 10 MTK VCOM USB Drivers for 32 & 64 bit + Driver install tutorial
To determine the version of Windows 10 that you have (32 bit or 64 bit):
- Right-click on Start then click on System
- In the System window that opens, in System section, you will find your version of Windows next to System type
To disable Windows 10 64 bit driver signature enforcement:
- On your 64 bit Windows 10 desktop click on Start then on Settings
- Click on Update & security then in the left pane click on Recovery
- Under Advanced startup click on Restart now button
- Click on Troubleshoot then on Advanced options
- Click on Startup Settings then on Restart button
- The computer will restart with the Startup Settings screen
- To disable the driver signature enforcement until next restart press on number key 7 or F7 on your keyboard.
- After restart you can proceed with the unsigned MTK drivers installation for your 64 bit Windows
- After you install the unsigned drivers, to use them again in the future, you have to repeat this procedure
To install the MTK VCOM USB Drivers on 32 & 64 bit Windows 10:
- Download the drivers *.zip archive and extract the folder from inside on to the desktop:
https://www.androidfilehost.com/?fid=24269982087012126
Right-click on Start then click on Device Manager
In the Device Manager Window click on the first item – your computer name
Click on Action then Add legacy hardware
On the Welcome to the Add hardware Wizard window click on Next button
Select Install the hardware that I manually select from a list (Advanced) and then click on Next button
Click on Show All Devices then on Next button
In the Add Hardware window click on Have Disk… button
In the Install From Disk windows click on Browse… button
In the next window – Locate file – browse for the folder that you have extracted on the desktop at the beginning
Select the version of the driver according to your Windows 10 version – x64 for 64 bit and x86 for 32 bit and click Open button
Click the OK button to load the driver
From the list of drivers select MTK USB Port and click on Next button
If a red warning window will open, click on Install this driver software anyway
This action will add the following drivers in to the operating system:
- MediaTek DA USB VCOM Port
- MediaTek PreLoader USB VCOM Port – for transferring the firmware to your device
- MTK USB DEBUG Port
- MTK USB Modem Port
- MTK USB port – for transfering PreLoader to your device (and recovery in case of bad or corrupt firmware)
Now we need to remove the device that we have installed but leave the drivers in the operating system.
To do that, in the Device Manager window we expand Ports (COM & LPT) section
Right-click and click Uninstall on the MTK USB Port
- In the Confirm Device Uninstall window make sure that the box Delete the driver software for this device is empty
- You need to leave the drivers in the operating system and only remove the device that you added
- Click on the OK button to finalise
Now, when you will connect your turned off MTK device to the Windows 10 computer by USB, the device will be recognized either trough a MediaTek Preloader USB VCOM Port interface or as a MTK USB port if it is bricked or it has bad/corrupt firmware. The SP Flash Tool will be able to transfer the firmware to your device trough this interfaces. Make sure you connect the device after you press the Download button in SP Flash Tool, as the communication interface will only be alive for 2 seconds if no data is being sent.
Download SP Flash Tool v3 & v5 – Latest versions:
http://laurentiumihet.ro/technology/download-sp-flash-tool-v3-v5-latest-versions/
TUT found here : http://laurentiumihet.ro/technology...-for-32-64-bit-drivers-installation-tutorial/
cheers​

Lost IMEI Restore
A common problem many face in their phone is loss of IMEI no. This is results in no network detection by your phone. U can come to know you have lost your IMEI by checking Settings->About phone->Phone information. There under IMEI section you won’t be finding your mobile IMEI numbers displayed.
Don’t worry you can restore your IMEI’s. Just follow this guide and you will be able to restore your IMEI. I will split the tutorial into two parts.
BACKING IMEI :
-First step before performing all these things is that your phone should be rooted.
When your phone is in normal state with everything functioning install Root explorer and navigate to the below location
Code:
>ROOT>DATA>NVRAM>MD>NVRAM>NVD_IMEI>MP0B_001
-Now copy this MP0b_001 file to your SD card or PC whichever place you feel the file we be safer.
-Now download MTK Droid tools .
-Now extract the zip file and open the MTK droid tools exe file.
-Now in your phone turn on USB Debugging by going to Settings->About phone-> Developer options and there turn on USB debugging.
-Now connect your phone and MTK droid tools should be able to detect your phone. U should see a window like this appearing after your
phone has been detected.
-Now press the ROOT button present in lower right corner. When it asks Supersu grant in your mobile click allow. After MTK droid gets
access u should see a green colour box appearing in the lower left corner which means u have correctly granted access to MTK droid.
-Now click on the IMEI/Nvram tab. A window should open and click backup NVRAM and MTK droid tools would take a backup of NVram in
its folder.
RESTORING IMEI :
-Now when you lose IMEI first try this method. Now take the MPDB_001 file which you took backup at the first step and navigate through
Root explorer to this location ->ROOT->DATA->NVRAM->MD->NVRAM->NVD_IMEI.
-Now paste that file and replace the one present there. Set the permissions for that file as RWER-ER-E. Now reboot your phone and you
should be able to get your IMEI back.
If you still haven’t got IMEI open MTK droid tools and connect your phone and press ROOT again and give MTK droid tools root access.
-Now click on IMEI/Nvram tab and select Restore option and restore the NVram backup which you took earlier. Now reboot your phone and
you should be able to get your IMEI.
Extreme method :
-After performing all the above if you haven’t still got IMEI. Now switch off your phone and open SP Tools and connect your phone.
Click on format and format your whole phone. ( This wipes whole of the phone including NVram region ).
-Now flash stock ROM through SP Tools and after it completes start up your phone. ( Don’t be surprised. Your IMEI will still be in lost state
only ). Now root your phone.
-After successful rooting now connect your phone to MTK Droid tools and again press ROOT button and grant root access to MTK Droid
tools. Now click on IMEI/NVram tab.
-Now as you see in the image above you can see two boxes IMEI1 and IMEI 2. Now enter your device IMEI numbers manually in those two
boxes.( You can get your IMEI no’s from your phone box ). Now click replace IMEI. Now reboot your phone and you should be definitely able
to get your IMEI restored.
MTK DROID TOOLS LINK : https://www.androidfilehost.com/?fid=24438995911972546
found: http://www.androiddevs.net/restoring-lost-imei-mtk-phone/​

MTK droid tool doesn't recognize my device. I turned on USB debugging and drivers are installed. Can somebody help ?

I'm having same issue here on Win10 installed the drivers etc... using latest SP Tools plug phone in and try and put recovery as a download nothing happens.
EDIT: Nvm got it working realised I was downloading and plugging in the phone in the wrong order.

Windows defender says MTK Vcom Preloader Driver 2.0 has got a trojan: Win32/Spursint.A!cl but i downloaded drivers from http://spflashtool.com/ instead.
False warning?
/#LOUDmouth#

#LOUDmouth# said:
Windows defender says MTK Vcom Preloader Driver 2.0 has got a trojan: Win32/Spursint.A!cl but i downloaded drivers from http://spflashtool.com/ instead.
False warning?
/#LOUDmouth#
Click to expand...
Click to collapse
False positive

kopasz93 said:
MTK droid tool doesn't recognize my device. I turned on USB debugging and drivers are installed. Can somebody help ?
Click to expand...
Click to collapse
I have a solution for restoring IMEI:
In the dialer: *#*#3646633#*#*
OR
download "MTK engineering mode" app and start it
it will open engineering mode:
1/ go to "Connectivity" tab
2/ go to "CDS information"
3/ go to "Radio information"
4/ then select "Phone 1"
5/ At the top there is a command line "AT+" in it
6/ type AT+EGMR=1,7,"your imei number" (for example: AT+EGMR=1,7,"012345678901234")
7/ then hit "Send at command" (if you got error try to put space between "AT" and "+")
8/ go to "Phone 2" and type in the command line: AT+EGMR=1,10,"your imei"
9/ hit "send at command"
10/ restart your phone and it should work
You can check if it changed at Settings -> About Phone -> Status -> IMEI information
If your forgot your original IMEI numbers you can find them on the box of the phone

MTK droid tool recognizes my phone, but do not get the green button so root error. Granted permission in supersu.

If anyone is still struggling (like me) with the error: Initializing scatter file failed. Please check the name of the scatter which you load is legal
i solved by using SP Flash Tool 5.1552.00.000 downloaded from
https://mega.nz/#!ixdnhDLK!oOaAsJrcvJI0vH3fTsUOYjtDxQ_HT61E-_iuo6fTuKk
as specified in elephone forum flashing guide
http://bbs.elephone.hk/thread-1037-1-1.html#.VWgkX_RAU-0

Use latest v5.162 version
Gesendet von meinem P9000 mit Tapatalk

Linux way?
Is there a way to root my brand new P9000 in Linux?

I flashed the linked SuperSU 2.46 with TWRP but when i start the SuperSU App it says that there is no su-file installed - any ideas?

sundawn said:
I flashed the linked SuperSU 2.46 with TWRP but when i start the SuperSU App it says that there is no su-file installed - any ideas?
Click to expand...
Click to collapse
Why on earth are you using such an old version of SuperSU?
You are probably using TWRP 3.0.0 which does not work on newer ROM versions. Try flashing TWRP 3.0.2-1.

Well i used it because it is said to work in this tutorial
The newer one didnt work either, as you said i think its the TWRP 3.0.0
I would like to download this http://www.needrom.com/download/twrp-3-0-2-1-4/
but i dont get any registration mails, tried to register with 2 different emails half an hour ago...
The version here on XDA is said to be only for P9000 Lite.
Edit: Ok got my login by using the forgot password function - the linked TWRP 3.0.2 and installing SuperSU 2.65 works.
Thanks!

also would like to know, can we fastboot the recovery as per all the other android phones i've used? And then custom ROM to our hearts content?

n1ck75 said:
also would like to know, can we fastboot the recovery as per all the other android phones i've used? And then custom ROM to our hearts content?
Click to expand...
Click to collapse
Yes. In Settings / developersettings enable oem. unlock Bootloader.
Then reboot to Recovery and go to power/ reboot to fastboot.
Then Unlock your Bootloader with the fastboot oem Unlock command.
After that you can use fastboot.
P.s: i didnt did that. But it should work
Gesendet von meinem P9000 mit Tapatalk

skeleton1911 said:
Yes. In Settings / developersettings enable oem. unlock Bootloader.
Then reboot to Recovery and go to power/ reboot to fastboot.
Then Unlock your Bootloader with the fastboot oem Unlock command.
After that you can use fastboot.
P.s: i didnt did that. But it should work
Gesendet von meinem P9000 mit Tapatalk
Click to expand...
Click to collapse
Thanks for the prompt reply;
Have got to the fastboot oem unlock part, gives option for
Vol Up - Unlock
Vol Down - Cancel
Vol Up doesn't work? Can only Vol Down

official update to MARSHMALLOW 6.0 for LG MAGNA

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