Hello everyone!
So the last day I costumer gave me a Huawei Y5 that has a Factory reset protection, And I started thinking about how to bypass it, I tried a costume rom but it didn't do any help, also tried to remove the setup wizard .apk and same! no result.
so after seeing a couple of articles I managed to find a solution :
1- Reboot your phone to recovery mode and connect it to a computer with adb
2- Pull the build.prop file
3- Edit it with any software you want and add the following 3 lines :
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
4- Save the file and push it to the phone
5- Reboot and check if adb recognizes the phone then run an adb shell
6- execute the following commands :
am start -S com.android.settings -c android.intent.category.LAUNCHER 1
7- The settings app will pop up, simply enable oem unlock in developer settings then reset the phone through the settings app
8- Reboot and you're done !
---------------------------
PS: This is my first post here so sorry if it's the wrong section !
peace out
Related
STEP :
1. run 01-local-prop.cmd to create /data/local.prop (enable android emulator hack)
2. power off device and update your device WITHOUT FACTORY RESET
3. run 02-push-root-files.cmd to push su binary and superuser.apk
4. your device will automatically reboot
5. enjoy your new rooted firmware
Hi.. im stuck at step 1. When i started to run local prop cmd will open for about 1 sec only then closes.. my friend told me that it must not go that way. it should load and then when its done. proceed to step 2. but in my case running local-prop suddenly closes.. i needed to print screen just read whats the cause not loading the cmd .. and this is what it says "acess is denied file cannot find busybox is not recognized internal and external command" my phone is already ver.062 with root while doing the step 1. please help guys. i want my ics to be rooted
I recently tried to lower the resolution on my Samsung Galaxy Note II using NOMone to increase game performance. Unfortunately I ended up making my phone unusable (system.ui kept force closing, launcher wouldn't open, etc). After a few hours I found a way to fix my mistake without doing a factory reset. This is just a quick write up I felt I had to share. It may not help everyone but hopefully this will help someone avoid factory reset. This guide assumes your phone is rooted, has a removable sd card, and has a custom recovery.
If you had USB debugging enabled prior to changing your resolution, the process is much simpler:
1. Make sure your phone's usb drivers are installed on your computer (adb, etc...)
2. Open up a terminal or command prompt on your computer and type in:
(For android versions 4.3 and up)
Code:
adb shell wm size reset
adb shell wm density reset
(For android versions below 4.3)
Code:
adb shell am display-size reset
adb shell am display-density reset
3. Everything should be back to normal, although a reboot may be needed.
If you're a complete moron like me and did not have usb debugging enabled prior to changing your resolution, there is hope as long as you have a custom recovery.
1. Download Aroma File Manager and place on your sd card.
2. Copy your build.prop from the /system directory and place on your sd card.
3. Connect your sd card to your computer and open your build.prop using your favorite editor.
4. Add the following lines at the bottom of your build.prop
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
5. Save and overwrite your existing build.prop with the edited build.prop and reboot your phone.
6. You should now have adb debugging enabled and should be able to follow the first series of steps to restore your resolution.
Life saver!
hjjr15 said:
I recently tried to lower the resolution on my Samsung Galaxy Note II using NOMone to increase game performance. Unfortunately I ended up making my phone unusable (system.ui kept force closing, launcher wouldn't open, etc). After a few hours I found a way to fix my mistake without doing a factory reset. This is just a quick write up I felt I had to share. It may not help everyone but hopefully this will help someone avoid factory reset. This guide assumes your phone is rooted, has a removable sd card, and has a custom recovery.
If you had USB debugging enabled prior to changing your resolution, the process is much simpler:
1. Make sure your phone's usb drivers are installed on your computer (adb, etc...)
2. Open up a terminal or command prompt on your computer and type in:
(For android versions 4.3 and up)
Code:
adb shell wm size reset
adb shell wm density reset
(For android versions below 4.3)
Code:
adb shell am display-size reset
adb shell am display-density reset
3. Everything should be back to normal, although a reboot may be needed.
If you're a complete moron like me and did not have usb debugging enabled prior to changing your resolution, there is hope as long as you have a custom recovery.
1. Download Aroma File Manager and place on your sd card.
2. Copy your build.prop from the /system directory and place on your sd card.
3. Connect your sd card to your computer and open your build.prop using your favorite editor.
4. Add the following lines at the bottom of your build.prop
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
5. Save and overwrite your existing build.prop with the edited build.prop and reboot your phone.
6. You should now have adb debugging enabled and should be able to follow the first series of steps to restore your resolution.
Click to expand...
Click to collapse
Dude, i swear to GOD you are a life saver!! i don't use this site frequently. i had to reset my password just to be able to thank you. Can't thank you enough. You really saved my life.
Man, you saved my life after 4 years lol
ematc egq327
Nomone app crashed when I increased dpi to 600. Now tablet constantly reboots. I can not figure out how to enter recovery mode. If I can wipe data will this reset dpi? Anyone?
Bro pls help me I'm changed dpi-screen resolution and density
Now my device touch in not working pls guide me
Device-redmi note 7 pro
So my issue is actually diffrent, i DO have usb debugging, BUUUUUUUUUUT, it doesnt allow me to do any commands cuz i have my device with locked screen, and i am unable to do anything with adb, is there any last hope?
Lauris Roze said:
So my issue is actually diffrent, i DO have usb debugging, BUUUUUUUUUUT, it doesnt allow me to do any commands cuz i have my device with locked screen, and i am unable to do anything with adb, is there any last hope?
Click to expand...
Click to collapse
did you figure out what to do??
Hello,
I have Oneplus One 64 gb variant, yesterday my nephew somehow changed my phone's lock pattern and now my phone is locked. USB debugging was disabled at that time. I am not able to get into my phone through any means. I have lot of important data in my phone and don't want to hard reset my device. I found a solution online to get usb debugging on through adb , but I am a ultra noob and don't understand how that has to be done. please dumb it down so that I can save my precious data and unlock my phone when debugging gets enabled. Also I don't have any custom recovery installed on my phone.
This is what is mentioned in the solution.
"Instructions
1. You should try your pattern-cracking software (or whatsoever the genre it has) from inside the Stock Recovery to see whether it works with the former's environment (ADB shell available there or not).
2.Since I would never try step 1., I would do the following:
-For Jellybean 4.2.1:
1. Boot into Recovery and mount Data partition.
2. Open a shell on PC and type:
adb pull /data/property/persist.sys.usb.config ~/
Repace ~/ with home directory of your OS.
3. Open that file in a text editor and you would possibly see mtp written there. Change it to mtp,adb.
Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows (mine is Linux so no issue here).
In that case, I would suggest not using adb pull but doing:
adb shell
echo 'mtp,adb' > /data/property/persist.sys.usb.config
You may verify that the echo command overwrote the file by using:
adb pull /data/property/persist.sys.usb.config ~/
and seeing the file's content in some text editor.
4. Unmount Data and reboot into Android OS. USB Debugging would probably be enabled.
-For Lollipop 5.0:
JB 4.2.1 users can also follow this method if the previous one didn't work for them.
1. Boot into Recovery and mount Data partition.
2. Repeat step 2 and 3 used in JB 4.2.1 method.
3. We need to tweak some parameters in settings.db. Type:
adb pull /data/data/com.android.providers.settings/databases/settings.db ~/
4. Back it up at some other location too, and open the file in an SQLITE editor. I'm running Linux and DB Browser for SQLite works well. It's also available for Windows OS/OSX.
5. In the global table, change the value for:
adb_enabled to 1
development_settings_enabled to 1
6. Check that verifier_verify_adb_installs is set to 1 in the global table.
7. Check that as default, in the secure table:
adb_notify is 1
adb_port is -1
These checks in step 6 and 7 are not necessary but should be done so that troubleshooting becomes rather easy if the solution doesn't work for you.
8. Save the changes in settings.db and copy it back into Android by typing:
adb shell
rm /data/data/com.android.providers.settings/databases/settings.db
exit
adb push ~/settings.db /data/data/com.android.providers.settings/databases/
That delete (rm) command is not necessary since adb push should overwrite the file, but I executed it for my peace of mind.
8. Unmount Data and reboot into Android OS. ADB probably would be enabled.
source:- https://android.stackexchange.com/questions/112040/how-to-enable-usb-debugging-in-android-if-forgotten-pattern-for-screen-unlock"
Please help me understand this code and be a life saver.
Thanks in advance..
You are stuck, I'm afraid. You won't be able to run any script on stock recovery, but you can't flash a custom recovery without unlocking the bootloader which will wipe your data.
What's more, your phone should be encrypted (if it's running 6.0 or higher), which means you'll need to know the pattern to decrypt after a reboot.
If you can't figure out the pattern, there's nothing you can really do.
jisoo said:
You are stuck, I'm afraid. You won't be able to run any script on stock recovery, but you can't flash a custom recovery without unlocking the bootloader which will wipe your data.
What's more, your phone should be encrypted (if it's running 6.0 or higher), which means you'll need to know the pattern to decrypt after a reboot.
If you can't figure out the pattern, there's nothing you can really do.
Click to expand...
Click to collapse
Is there any way I can create backup of the data in these conditions?
Dush123 said:
Is there any way I can create backup of the data in these conditions?
Click to expand...
Click to collapse
Unfortunately for you in this case, there isn't.
From a general security perspective, if there was it would mean the pattern lock and encryption can be bypassed, which would be very bad.
jisoo said:
Unfortunately for you in this case, there isn't.
From a general security perspective, if there was it would mean the pattern lock and encryption can be bypassed, which would be very bad.
Click to expand...
Click to collapse
Ohk. Then it seems I don't have any option but to hard reset my device.
Thanks anyways
HI! Is there anything I can do for my pattern locked Moto E4 Plus? Details I've posted in this thread.
https://forum.xda-developers.com/showthread.php?t=2620456&page=13
Recently, I successfully ported TWRP from Coolpad Note 3 Lite to Modena 2. After testing, everything works fine, on both devices. Since this device has locked bootloader, we need to bypass this by enabling fastmmi mode and factory mode to enable temporary root access and make initial backup and flashing. So, let´s get started.
Remember to read this post carefully. I am not resposible for any damage to your device. If you brick your device while flashing the TWRP you can *almost* always recover it using SP Flash Tool and YGDP Tool
IF YOU ACCIDENTALY BRICK YOUR DEVICE AND YOU WANT TO FLASH IT VIA SPFT, DO NOT FORMAT THE DEVICE IN SPFT!!! If you´ll format partitions in TWRP, that´s fine, but don´t do FORMAT ALL + DOWNLOAD or FIRMWARE UPGRADE! This will brick your device, like mine This tutorial will not (hopefully) brick it, but just in case something goes wrong, now you know what not to do.
Preparing the environment on your computer
Windows
Download ADB and Fastboot from this link
Open it
Install it system-wide
Also, install the drivers
GNU/Linux (Ubuntu / Debian based distros)
Open terminal
Type "sudo apt install adb fastboot libusb-dev" without the quotes (")
Other things, that are required
Since the file size of the recovery exceeds the maximum 8MB of allowed upload size, you can download it from DataFileHost.
Preparing the device
First, you need to remeber that this could render your device unbootable and will void warranty.
Enable developer options
Go to Settings -> About phone
Tap the build number 7 times
Go back
Go to Developer options
Make sure OEM unlocking and USB Debugging is enabled
Enabling factory mode
Open dialer app
Dial *#9527*#
Click on "DM"
You will be prompted to insert RD personnel password. Enter: 54321
Click cancel button
DM button should change colour to RED
Exit the app by clicking home button
Installing and setting up openrp app
Open terminal / command prompt
Type:
Code:
adb start-server
Type:
Code:
adb devices
Now, click on your phone allow debugging and make sure to tick the radiobutton to remember / always trust this computer
Type:
Code:
adb install
Press spacebar after the install word and drag and drop the downloaded openrp.apk file to terminal
Hit enter
After it´s done, type:
Code:
adb shell monkey -p com.yulong.openrp -v 500
Now, the fun part. ROOTING the device
But before that, BACKUP
Now, keep your phone plugged in, and do a normal reboot by pressing and holding the power button and clicking reboot
When it vibrates, press and hold the Volume down key (Vol-)
You will see these lines on the screen:
Code:
=>[Factory mode]
Code:
=>VolumeDown key is pressed
Code:
=>[fastmmi mode]
After that, you´ll see the LED turns green and "Up Down" text on the screen
Now, back to your computer, type in the command prompt
Code:
adb devices
You should see XXXXXXXXXXXXXX device listed (where XXXX... is the serial number)
Type in the command prompt:
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery of=/storage/self/primary/stock_recovery.img
and
Code:
adb shell dd if=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/boot of=/storage/self/primary/stock_bootimg.img
Flashing the TWRP Image
Type in the command prompt:
Code:
adb push (drag and drop the recovery image file here, like you did with the openrp.apk file) /storage/self/primary/
Type:
Code:
adb reboot
Press and hold VolumeDown key (Vol-) to boot to fastmmi mode
Type:
Code:
adb shell dd if=/storage/self/primary/recovery_twrp_e502.img of=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/recovery
Type
Code:
adb reboot
Press and hold the VolumeUp key (Vol+) to boot into recovery. If you see white screen with "Recovery" text in it, congrats. Everything is working. If not, try again.
Flashing the SuperSU package
Download the zip from SuperSU website
Copy the zip over to the device, with TWRP running
In TWRP, click install, click the zip and confirm the installation.
Factory reset is not required, but you should at least wipe the cache
If this post was useful for you, hit the thanks button
RESERVED
Hi i have a problem here. at the part to drag and drop the openrp file. When i have downloaded the file a drag it and drop it after the install word. The problem is that if I want to drop it there it will do nothing, nothing there shows or anything. Please respond.
I guess you can type the path to the installation file instead of dragging.
Hello,
Very helpful thread, my coolpad Modena 2 (E502) is now rooted.
Don't forget to disable the factory mode once everything is done, or you won't be able to access the storage to usb anymore.
Thanks.
helo, can i get help, when i try to install openrp on abd and fastboot, it printed this message "Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]"
can anyone help me on that step, so i can root my e502
TCRakt said:
Hello,
Very helpful thread, my coolpad Modena 2 (E502) is now rooted.
Don't forget to disable the factory mode once everything is done, or you won't be able to access the storage to usb anymore.
Thanks.
Click to expand...
Click to collapse
how to disable the factory mode ?? :crying:
Firefa23 said:
how to disable the factory mode ?? :crying:
Click to expand...
Click to collapse
Hello,
If I recall correctly (I don't have the phone anymore, just touched it once to root it at the time), you basically undo the "Enabling factory mode" step.
I think if you dial the number, you'll be back in the menu where you have the option to disable the factory mode.
Factory mode should be disabled when 'DM' is green.
Good luck
very good
Need Custom rom please
nougat / pie
Hello, could you resend the twrp recovery file for this phone again?. old links not work!.
(sorry for my bad english)
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