Hello, I am new to xda-developers and have just joined up.
I have gone to great lengths to find an answer to my problem with Google and have searched this forum.
Not having any luck I have decided to call out for help.
My situation
- Country: Australia
- Model: ZOPO ZP990 Android phone.
- Android 4.2, Jelly Bean
- Phone is "rooted".
- No recovery backup was ever made.
- My 3G wasn't working. The best I could achieve was "2G EDGE" data connections.
- I have a good HSDPA connectivity with my old LG Android P500 phone in my area.
- As I bought the Zopo phone in China I don't have the option of "after sales service".
- I am an Android newbie and I know very little about Android systems in general.
I was very happy with this phone, except that I was having issues connecting to 3G.
I had used Mobileuncle to configure for the specific 900/2100MHz 3G service in Australia.
Setting the 3G bands with Mobileuncle for my region did not correct my problem with no 3G access.
I then followed the advice to make changes to /system/build.prop
As there were no similar entries in my default build.prop I added the following lines to the very end.
# Start Support for Australian 3G
ro.ril.hsxpa=2
ro.ril.hsdpa.category=5
ro.ril.enable.3g.prefix=1
ro.ril.hsupa.category=5
ro.ril.enable.dtm=1
ro.ril.gprsclass=12
ro.ril.enable.a53=1
# End Support for Australian 3G
I made a copy of the original /system/build.prop to /system/build.prop.bak as a backup.
I made the changes using Notepad++ (on PC) and an Android File Manager (provided root access) app.
I then rebooted and my phone hangs after it presents a ZOPO musical/visual start-up advert presentation.
My phone wont boot !!!
--------------------------------------------
<by pressing buttons on power-up I get the following>
Android system recovery <3e>
Enter: OK Key, Select : Vol UP/ Vol down
Reboot system now
apply update from ADB
apply update from sdcard
wipe data/ factory reset
wipe cache partition
--------------------------------------------
Using ADB(Android Debugging Bridge) Version 1.0.31
(I am using Mini-SDK and not the full Android SDK)
I have "Java Runtime Engine" but not "Java SDK" installed.
I connect the phone to my PC via USB and enter the "Android system recovery <3e>" environment.
I select the "apply update from ADB" on my phone.
I then enter the following commands into my PC.
C:\mini-sdk>adb version
Android Debug Bridge version 1.0.31
C:\mini-sdk>adb devices
List of devices attached
0123456789ABCDEF sideload
C:\mini-sdk>adb usb
error: closed
C:\mini-sdk>adb shell
error: closed
Besides the above commands I cannot get ADB to do anything useful.
I have "USB Debugging" turned off at the phone so I suspect this is why ADB doesn't work.
I know very little about ADB only what I have recently learnt with Google.
--------------------------------------------
I then downloaded the latest ZP990 ROM and Flash Tool V4.2
While I found the instructions straightforward I cannot establish communication between PC and phone via USB.
(I have the correct Android drivers installed on my PC and had full USB functionality before this problem started.)
Once again I suspect the fact that my "USB Debugging" is turned off prevents Flash Tool to work.
--------------------------------------------
I've noticed there is an "apply update from sdcard" in the "Android system recovery <3e>" environment.
I wonder if I can exploit this?
Is there a recovery ROM on the internet that I could download from the net to use on my sdcard?
If I could get any ROM to load, I could later use Flash Tool to do the final ROM upgrade.
Does anyone know if I could use the "apply update from sdcard" from "Android system recovery <3e>" to install a new ROM.
--------------------------------------------
Can someone please help me?
I work in the electronics/IT field, but I know very little about Android systems.
So all I need is guidance on moving forward.
If I sound like I know more about Android that is because I have done a lot of research on the internet to try and fix my phone.
--------------------------------------------
Are you able to do an ADB PULL of the backup you took, rename it on your PC to build.prop, do an ADB REMOUNT then ADB PUSH it back?
I fixed it myself !!!
No need to help me.
I found what I was looking for on the various Android websites around.
I needed to first instal the Mediatek USB VCOM drivers.
Install the latest copy of SP Flash Tool on my PC.
Down load the latest ZP990 ROM from the ZOPO website and unpack it.
Remove battery from phone for a short period. Put the battery back, but don't power up.
Start SP Flash Tool
Select the scatter-loading file from the ROM I unpacked.
Press F9 (or hit Download button) and connect your phone into the computer via USB data cable.
Things went much easier than I expected.
Lost my data, but I got my phone back. :good:
Samsung Luna StraightTalk S120VL FRP Bypass
In Model Number usually..
BL = Tracfone
VL = Straight Talk
(Both the same company but there are differences in ways used to do FRP removal depending on certain devices so I always list accordingly)
Tested on U2 firmware APJ2 so not sure if this works on U1. If the U2 firmware is wanted I will host and post it here.. It can be found by searching google too.)
Security Patch: (October 1, 2016) and.. should work fine on any other.
I had a stack of these phones gave to me for FRP Removal and these days I usually use Uni Android Tools, OctoPlus, or Z3X boxes for SamSung work. I tried while knowing this would most likely not be possible with this handset model. Success = 0. Tried a multitude of other operations and still nothing. Upgraded Firmware to the latest U2 because i had it, couldn't find a (free) combo in the time i looked and thought maybe it would allow something different.. I might be right. This is the first one in the stack I have done this on. So I will edit / post about U1 (Binary 1) models once this one is finished off. I know the methods work below just getting this write up done first. Anywho..
Whats needed? (each will depend on method taken below)
1) Bluetooth EarPiece
2) Old sim card (Verizon best for this way)
3) ADB Installed (Install this anyway as it's handy to have!) - Here is a link to a super quick and easy installer that will do it and while making ADB systemwide. Thanks to XDA user @Snoop05
Link for basic info - https://www.xda-developers.com/15-s...ng-fast-adb-fastboot-and-driver-installation/
Link to Thread for dicussion - https://forum.xda-developers.com/showthread.php?t=2588979
DIRECT DOWNLOAD LINK - https://forum.xda-developers.com/attachment.php?attachmentid=4623157&d=1540039037
4) ADB FRP Removal Application
Lots of ways past this initial point.. Here are 3 i know of that will work for this $20 old pocket buddy.
1) Preperation - First start off by hard resetting your Samsung Luna S120VL
Next find a sim card. I used an older used Verizon sim card. No longer in service. Put it in.
Boot phone. Goto Emergency Dialer. Dial 112 and instead of taking you to 911 (good yeh?) you'll get a voice greeting by Verizon. While this happens pair your bluetooth. (best if you have it in pair mode before dialing)
2) Removal - Three ways to do this. 2 more possibilities to do at the bottom of this post.
a. Connect to WiFi with Bluetooth. -> [Will do this when i get time]
b. Stay offline and use Bluetooth to open Calculator. Type in Calculator (+30012012732+ Now DRParser will open. Type now.. *#0808#. USB Settings will open now select the last one that says DM + Modem + ADB. Select reboot and watch your phones screen when you reboot. Enable when you get the authentication popup. Stay on the very first page of the setup wizard.
-
Now open CMD prompt type
Code:
adb devices
and make sure your device shows something like this -
List of devices attached
8e60d4bf device
Yeah? Ok now copy the following code and paste it into the CMD window and press enter.
Code:
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
Follow through the Setup Wizard which will quickly drop you onto your home screen and now you are done!
If the above command does not work in your case you can try the following command below. This will take you to login screen and then you can enter you Google account.
Code:
adb shell am start -n com.google.android.gsf.login/
If both previous commands do not work then try this.
Code:
adb shell am start -n com.google.android.gsf.login.LoginActivity
c. Stay offline and use Bluetooth to open Calculator. Type in Calculator (+30012012732+. Now DRParser will open. Type now.. *#0808#. USB Settings will open now select the last one that says DM + Modem + ADB. Select reboot and watch your phones screen when you reboot. Enable when you get the authentication popup.
-
Now use one of the many apps out there to remove FRP now that ADB is enabled. I will ask the moderators about posting but not sure it is allowed. Also the one that is easiest to use and that I recommend will trigger a false positive on Anti Virus. IF ok to post I will update this thread with a download.
----
Other Methods?
Accessibility Mode Method - When i get time (if it's possible.. as a quick check on U2 APJ2 didn't allow much)
ADB enabled boot IMG - Found one and these can be made as well but the one i have found (free) is from the Factory Engineering Firmware I believe. I just don't have much more time to fool with these luna phones. You'd just need to flash this then no need for bluetooth.. Again when i get a minute and remember I will put it up here.
Enjoy!
-noidodroid
Thanks
I was able to use QPST and PDC on my OnePlus Nord (AC2003) when it was running Android 10 / Oxygen 10.5
After this weekends update to Android 11 / Oxygen 11 my phone is no longer recognised. I've tried all sorts of USB drivers I could find using some Google Fu, but none of them recognises it anymore.
Does anyone have USB drivers for the OnePlus Nord (AC2003) that works with Android 11?
Thank you
After some digging, it appears that there is something disabled in Android 11 that causes the USB connection not to be recognised (at least that's my understanding of what the below does).
To get PDC to work with OnePlus Nord on Android 11, we need to download and install Google Platform Tools so that we can use ADB to temporarily make some tweaks so that we can run PDC to change the profile.
These are the steps I took to get it working:
------------
1. Get and install the ADB tools:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
2. From the command line run the following:
• adb devices
Validate your device shows. If it does, but it's not authorised, check phone to authorise the PC on the phone.
• adb reboot ftm
Wait until asian / chinese characters are shown and then a black screen.
• adb shell
• setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
(this will trigger USB change and device driver will install)
Qualcomm HS-USB WWAN Adapter 90E5
3. Open PDC application
Enable "Telefonica_UK_Commercial" profile
4. Close PDC
5. adb reboot
After this, the phone is not recognised again. I force installed the "Qualcomm HS-USB Diagnostics 9091" driver and was able to connect to it using QPST tools to use EFS Explorer like before.
Jaansburger said:
After some digging, it appears that there is something disabled in Android 11 that causes the USB connection not to be recognised (at least that's my understanding of what the below does).
To get PDC to work with OnePlus Nord on Android 11, we need to download and install Google Platform Tools so that we can use ADB to temporarily make some tweaks so that we can run PDC to change the profile.
These are the steps I took to get it working:
------------
1. Get and install the ADB tools:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
2. From the command line run the following:
• adb devices
Validate your device shows. If it does, but it's not authorised, check phone to authorise the PC on the phone.
• adb reboot ftm
Wait until asian / chinese characters are shown and then a black screen.
• adb shell
• setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
(this will trigger USB change and device driver will install)
Qualcomm HS-USB WWAN Adapter 90E5
3. Open PDC application
Enable "Telefonica_UK_Commercial" profile
4. Close PDC
5. adb reboot
After this, the phone is not recognised again. I force installed the "Qualcomm HS-USB Diagnostics 9091" driver and was able to connect to it using QPST tools to use EFS Explorer like before.
Click to expand...
Click to collapse
Thank you for this. Managed to get mine working with VoLTE and VoWIFI.
I have added all the drivers needed and some instructions here : https://gitlab.com/sorinfatu/opnord-volte-vowifi
If anyone wants to contribute to the profiles list feel free.
Thank you again Jaansburger
Jaansburger said:
After some digging, it appears that there is something disabled in Android 11 that causes the USB connection not to be recognised (at least that's my understanding of what the below does).
To get PDC to work with OnePlus Nord on Android 11, we need to download and install Google Platform Tools so that we can use ADB to temporarily make some tweaks so that we can run PDC to change the profile.
These are the steps I took to get it working:
------------
1. Get and install the ADB tools:
How to install ADB on Windows, macOS, and Linux
A step-by-step guide to get you started with the Android Debug Bridge tool.
www.xda-developers.com
2. From the command line run the following:
• adb devices
Validate your device shows. If it does, but it's not authorised, check phone to authorise the PC on the phone.
• adb reboot ftm
Wait until asian / chinese characters are shown and then a black screen.
• adb shell
• setprop sys.usb.config diag,diag_mdm,qdss,qdss_mdm,serial_cdev,dpl,rmnet,adb
(this will trigger USB change and device driver will install)
Qualcomm HS-USB WWAN Adapter 90E5
3. Open PDC application
Enable "Telefonica_UK_Commercial" profile
4. Close PDC
5. adb reboot
After this, the phone is not recognised again. I force installed the "Qualcomm HS-USB Diagnostics 9091" driver and was able to connect to it using QPST tools to use EFS Explorer like before.
Click to expand...
Click to collapse
No need to root?
Thanks
ippo18 said:
No need to root?
Thanks
Click to expand...
Click to collapse
Nope, no need
Jaansburger said:
Nope, no need
Click to expand...
Click to collapse
Thanks, I got blocked at the PDC step: no options available in the devices list.
Do I need a special version of PDC?
Tks
Thanks, it worked in the end, good job!
sorfat said:
Thank you for this. Managed to get mine working with VoLTE and VoWIFI.
I have added all the drivers needed and some instructions here : https://gitlab.com/sorinfatu/opnord-volte-vowifi
If anyone wants to contribute to the profiles list feel free.
Thank you again Jaansburger
Click to expand...
Click to collapse
I have no gitlab account, you may add, on the profiles Markdown file:
WindTre Italy ---> Italy-Volte-Vodafone profile works properely!
ippo18 said:
I have no gitlab account, you may add, on the profiles Markdown file:
WindTre Italy ---> Italy-Volte-Vodafone profile works properely!
Click to expand...
Click to collapse
Done
hi, there is no option to deactivate wifi scan throttle huawei p30 lite in developer mode, nor can i get su in adb.... any help?
If phone's Android is version 10 or higher go to Settings > Developer options > Networking find “Wi-Fi scan throttling” and disable it.
tx @jwoegerbauer , but it has been removed from huawei's dev options in emui10, there is also no way i can get access through adb, it does not allow rooting with the su command and ignores the "adb shell settings put global wifi_scan_throttle_enabled 0" command...
If Android OS is properly rooted, means SU-binary's location got added to Android's global PATH variable ( it's the same mechanism as with Windows OS, too ) then you can try
Code:
adb devices
adb shell "su -c 'settings put global wifi_scan_throttle_enabled 0'"
If Android OS isn't already rooted then you may consider to make use of temporary root what you have to install at your own.
tx @jwoegerbauer , i'll try and let u know!
My screen broke and I can't access the regular menus to enable adb debug mode. I can get into TWRP recovery or fastboot/odin mode which does enable MTP, so I've been able to access files on the data partition. I want to be able to access my app data though. If I can use adb backup I can make a backup and mount it offline or restore to an identical model and get access to my app data that way, but adb seems to not be enabled in TWRP. TWRP has a pretty simple menu so I could maybe fudge my way through by blind clicking, but even looking at a working model I can't find any menu option to enable adb in TWRP 3.1.1-0. Do I need a different version? The closest I can find is to enable adb sideload, but that's limited to only sideload and it doesn't work anyway. The device always shows as "offline". Seems my PC needs to be included in a trusted devices file. I've seen some clever instructions on overwriting the file containing trusted devices, but it requires the system partition is mounted, which if I could do that I'd have access to the app data anyways.
Is there some way to get access to this data? I looked at apps like vysor which work as an external display for the device which could allow me to work around the broken screen, but that seems to require adb debug is enabled, which it isn't.
Only if ADB got successfully enabled on a phone you can run Android shell-commands via ADB when phone is booted into recovery mode.