Hi all,
I've got a problem. I used tasker with secure settings to set my pin. Secure settings was enabled as device admin. Now tasker set a bogus pin. I can't get into my phone and I can't factory reset through stock recovery. This just does a soft reboot. What to do?
Presumably there is a safety in the fastboot menu. Try to do the factory reset by doing this:
Go into recovery while factory reset is selected. Press 10 - 15 s the volume up button and then the power button while holding the volume up button. Then release both keys.
Or you go to fastboot menu (Holding Vol- and Power when off) and open the fastboot/adb console on your PC and type the following:
Code:
fastboot -w
This will wipe your device to factory default without any question, so be careful!
difusio said:
Hi all,
I've got a problem. I used tasker with secure settings to set my pin. Secure settings was enabled as device admin. Now tasker set a bogus pin. I can't get into my phone and I can't factory reset through stock recovery. This just does a soft reboot. What to do?
Click to expand...
Click to collapse
Try flash a custom recovery and the factory reset it
Related
I want to erase the possibility to do a reset from the recovery mode. how do i change what will be written there (i locked the "settings" with app lock so reset from inside the device is blocked)
0527164842 said:
I want to erase the possibility to do a reset from the recovery mode. how do i change what will be written there (i locked the "settings" with app lock so reset from inside the device is blocked)
Click to expand...
Click to collapse
any answer ?
HI all
So I downloaded the OTA, flashed it with TWRP which was fine, then it rebooted.
Because it was encrypted it asked me to enter the password. Then it asked me again...
"Decryption unsuccessful - the password yo entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you setup your phone after the reset, you'll have an opportunity to restore and data that was backed up to your Google account"
One button - RESET PHONE
I press it and it tried to go into TWRP but appears to be in some kind of bootloop.
I can get into Fastboot but ADB DEVICES doesn't show a phone.
I can get into recovery (vol down + power) and the data appears to decrypt properly - all my files are there.
I'm trying a restore now. I'll update the thread when It's done.
Any suggestions on how to install the OTA? (assuming this works properly)
koocha said:
HI all
So I downloaded the OTA, flashed it with TWRP which was fine, then it rebooted.
Because it was encrypted it asked me to enter the password. Then it asked me again...
"Decryption unsuccessful - the password yo entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you setup your phone after the reset, you'll have an opportunity to restore and data that was backed up to your Google account"
One button - RESET PHONE
I press it and it tried to go into TWRP but appears to be in some kind of bootloop.
I can get into Fastboot but ADB DEVICES doesn't show a phone.
I can get into recovery (vol down + power) and the data appears to decrypt properly - all my files are there.
I'm trying a restore now. I'll update the thread when It's done.
Any suggestions on how to install the OTA? (assuming this works properly)
Click to expand...
Click to collapse
Adb devices will never return anything in fastboot because adb doesn't work in fastboot, only fastboot commands work in fastboot mode. Report back with any further information.
Transmitted via Bacon
timmaaa said:
Adb devices will never return anything in fastboot because adb doesn't work in fastboot, only fastboot commands work in fastboot mode. Report back with any further information.
Transmitted via Bacon
Click to expand...
Click to collapse
Ah right, that makes sense!
Backup restore failed. I can mount data via TWRP so I can pull the files off my phone to my computer, so I guess I'll do that then wipe it and flash it all again
koocha said:
Ah right, that makes sense!
Backup restore failed. I can mount data via TWRP so I can pull the files off my phone to my computer, so I guess I'll do that then wipe it and flash it all again
Click to expand...
Click to collapse
Sounds like a good idea to me.
Transmitted via Bacon
I am experiencing exactly the same thing. I can see the device in fastboot, but was unable to get the device into recovery until just now. It seems that holding Power+Volume Down during the TWRP bootloop will shut the phone off after several loops. Then I held Power+Volume Up to get into fastboot, but I can't seem to repeat it. After rebooting via fastboot command, I got back to the "Data corrupt" message. Holding the power button on that screen instead of touching Reset gave me a power menu. It properly shut down, and then I was able to Power+Volume Down into recovery.
Does anyone think I have a realistic chance of installing the previous CM11 over top of the botched CM12 to get back to a working phone without having to re-install all my apps? I don't know enough about Android upgrade processes to know if this is even a little bit feasable.
Hey guys, so I have this dilemma on my hands. One of my friends has a Nexus 5 that has a power button issue. It seemed like a stuck power button, because even cleaning it did not solve the issue. So I removed the power button, and it finally turned on. However, it's now stuck in a Google logo bootloop.
The Objective:
To recover all data on the device. This is a must.
The Obstacles:
- No physical power button, but I can place a pair of tweezers on the terminals on the board to simulate a power button press.
- Bootloader is locked (I can unlock it, but that erases all data on the phone).
- Cannot enter proper stock recovery (I get a "no command" error when I do; I've tried all button combinations afterwards, including the ones from HERE, but to no avail).
- USB debugging was not enabled on the phone when booting normally, so even though the phone is recognized by my PC, I cannot do anything using ADB.
- Fastboot mode is the only successful mode I can reach on the phone.
The Final Question:
Does anyone know how I can successfully recover all the data on the phone using ADB or any other method, having the above obstacles?
Thanks in advance.
If you can reach fastboot without any problem, you can try to boot a custom recovery image using the following command : fastboot boot recovery yourcustomrecovery.img
(if you dont have a custom recovery, you need to flash one with : fastboot flash recovery yourcustomrecovery.img)
It will boot in recovery mode and, I hope, allow you to have an adb access and recover your data.
edit : since your bootloader is locked, i guess this won't work.
MrKhozam said:
Hey guys, so I have this dilemma on my hands. One of my friends has a Nexus 5 that has a power button issue. It seemed like a stuck power button, because even cleaning it did not solve the issue. So I removed the power button, and it finally turned on. However, it's now stuck in a Google logo bootloop.
The Objective:
To recover all data on the device. This is a must.
The Obstacles:
- No physical power button, but I can place a pair of tweezers on the terminals on the board to simulate a power button press.
- Bootloader is locked (I can unlock it, but that erases all data on the phone).
- Cannot enter proper stock recovery (I get a "no command" error when I do; I've tried all button combinations afterwards, including the ones from HERE, but to no avail).
- USB debugging was not enabled on the phone when booting normally, so even though the phone is recognized by my PC, I cannot do anything using ADB.
- Fastboot mode is the only successful mode I can reach on the phone.
The Final Question:
Does anyone know how I can successfully recover all the data on the phone using ADB or any other method, having the above obstacles?
Thanks in advance.
Click to expand...
Click to collapse
I bit of a trick. Try 'fastboot flash boot recovery.img' but instead of kernel flash twrp. After flash do a 'fastboot reboot'. It will boot recovery. Via twrp the pc will recognize phone as a media storage. You will not erase any data
icrunchbanger said:
I bit of a trick. Try 'fastboot flash boot recovery.img' but instead of kernel flash twrp. After flash do a 'fastboot reboot'. It will boot recovery. Via twrp the pc will recognize phone as a media storage. You will not erase any data
Click to expand...
Click to collapse
Thanks for the response, but the bootloader has to be unlocked for that to work, and while I can do that, it will wipe the data I need.
First, you’ll need ADB and fastboot, which can be downloaded here. To set up ADB, go to Settings/About Phone/Software Info and tap on build number until you get a toast notification saying “You are now a developer!” You will now have a new category in Settings called Developer Options. Go into developer options and enable USB debugging and OEM Unlock. You won't be able to turn it on if your phone is plugged in to your PC. Once you've turned it on, go to your PC, open Terminal or Command Prompt and type “adb devices”. Then plug in your phone and hit enter. You'll get a prompt on your phone to “Allow connections to this PC?”. Check Always allow and Allow. Now run “adb devices” again. Your device should now appear in Terminal.
If you have a SD card, download the latest zips from here and here onto your SD card. It'll save you a step later on.
Then you'll need to reboot to fastboot by holding down VOL- and plugging in USB while power is off. Alternatively, you can type “adb reboot bootloader” in Terminal or Command Prompt.
Next, you'll need to unlock the bootloader. Bootloader unlocking will factory reset your phone! Once you're in fastboot, run “fastboot oem unlock” in Terminal or Command Prompt. Now the bootloader is unlocked.
Now it's time to flash TWRP, a custom recovery for Android. It's going to be the way you install custom ROMs and add-ons. Download Official TWRP here. Once you've extracted the recovery.zip, run this command: “fastboot flash recovery path/to/recovery.img”. Once the file has flashed, disconnect the USB cable and battery. The next step is important! You're going to need to boot into TWRP for the first time. With the phone off, hold down VOL- and press power until the phone vibrates and the LG logo appears. While still holding down VOL-, release and immediately press and hold power. You should now be at a white screen that says “Reset all data and restore to factory settings?” Use the volume and power keys to select yes and yes again. If you've installed TWRP successfully, it won't actually factory reset your phone. Now you should see the TWRP screen. If you don't see the TWRP screen and instead see a floating ring that says “Erasing”, don't worry. Let if complete and try flashing TWRP in fastboot again.
In TWRP, you'll be greeted by a screen that says “Swipe to allow modifications?” Swipe it, then go to the Wipe tab. Go to Wipe, then Format Data, then type yes, then go to the Reboot tab and select Recovery to reboot into TWRP again. If you're prompted to install the TWRP app, don't bother.
Once you've rebooted into TWRP again, it's time to disable encryption and root the phone. Download the latest zips here and here. Skip downloading them if you already put them on your SD card earlier. On your PC, push the files to your phone using the command “adb push path/to/file.zip /sdcard/”. You can drag and drop the file into Terminal or Command Prompt to copy file path. Then go to the Install tab in TWRP and select the no-verity-opt-encrypt.zip, tap Add more zips, then add the root zip, then swipe to flash. Let the zips flash, then tap the Reboot System button when it's done. Your phone will take a little longer to boot and might reboot a couple times.
Once you're back in the OS, go through the setup wizard. Set up Magisk. If you stay on stock, you should install an app like Quick Reboot Pro from the Play Store to make it easier to reboot into recovery. Now reboot back into TWRP and go to the Backup tab. If you have a SD card, set it as the backup location. You can enable compression if you want. This will make a full system backup that you can restore from as long as you have TWRP. If the backup takes up too much space, you can put it in Google Drive or your PC later on.
You are now ready to install ROMs!
Thanks to @messi2050
My device will not start boot loader with command "adb reboot bootloader" or with the method of holding volume down and pugging it into the PC, it just restarts and boots like normal. i cannot even get to the stage to use the command "fastboot oem unlock"
I cant get it too boot into TWRP
? Has anyone else have had issues geting into bootloader mode on lg stylo 2 boost mobile.
meg540 said:
? Has anyone else have had issues geting into bootloader mode on lg stylo 2 boost mobile.
Click to expand...
Click to collapse
Please explain more in detail so you can be helped better In what ways? What are you doing to get into bootloader mode? I've never had any issues on my T-Mobile Stylo 2 plus. Are you trying to get into bootloader using buttons manually or through twrp or adb?
SM210 said:
Please explain more in detail so you can be helped better In what ways? What are you doing to get into bootloader mode? I've never had any issues on my T-Mobile Stylo 2 plus. Are you trying to get into bootloader using buttons manually or through twrp or adb?
Click to expand...
Click to collapse
Im trying too put my phone into bootloader mode to unlock bootloader but it keeps restarting phone and wont go into it. Also i have tryed on my computer command promt but phone into bootloader mode it. Restarts phone but not into bootloader mode. Also i have tryed power down and holding power button that doesn't work.
meg540 said:
Im trying too put my phone into bootloader mode to unlock bootloader but it keeps restarting phone and wont go into it. Also i have tryed on my computer command promt but phone into bootloader mode it. Restarts phone but not into bootloader mode. Also i have tryed power down and holding power button that doesn't work.
Click to expand...
Click to collapse
You hold volume DOWN and power then soon as screen comes on and you see LG you let go of the power button and then immediately press power again and you never let off volume DOWN. That doesn't work?
Edit
SM210 said:
You hold volume DOWN and power then soon as screen comes on and you see LG you let go of the power button and then immediately press power again and you never let off volume DOWN. That doesn't work?
Edit
Click to expand...
Click to collapse
Ill try that i think i wasnt doing it correctly i was holding down power button then i let go an i was holding down the down button. Ty for u help ill try it later today.
Hey there, I've got the LG K530F, is there any chance of unlocking it? I looked up the LG developer website and it's not listed in there, filling that form will just lead to a popup regarding that. I thought about downgrading it back to MM (Android 6.0) using the K350F10d_00_02221.kdz firmware package aiming to be able to run fastboot oem unlock, but I'm afraid of getting it bricked. Anyone tried it? I recall doing something like that to unlock the LG Optimus L9, but that one was way older and had much weaker security measurements.
Can't get into Bootloader
Hi i have a LGL82VL and when trying to use adb reboot bootloader it just restarts, And when using Vol Down and Power it just comes to the factory reset page (Hard Reset)
Any ideas on how to get to the bootloader? i checked with fastboot devices while on the hard reset page and got nothing. Any Ideas?
Newbie here. Tried to download TWRP onto unrooted device (Galaxy Note10 Exynos d1) with Odin and now my phone is stuck on "downloading" screen. When I try to cancel (restart phone) it goes to the startup/booting screen for less than a second and then jumps back to "downloading". It says this at the top left corner of the screen:
recovery: Error validating footer (6) CUSTOM RECOVERY VBMETA N970F XXU1 ASG0. 24967245R
I am able to get into the custom OS installation screen (don't know what it's actually called but second picture) by letting the battery drain so that the phone turns off and then holding volume up + volume down key and plugging the phone into my laptop with USB.
The bootloader is unlocked. I went to https://twrp.me/samsung/samsunggalaxynote10.html and even there it says "Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot." Does anyone know how to fix this? Thanks in advance.
TheAckermans said:
Newbie here. Tried to download TWRP onto unrooted device (Galaxy Note10 Exynos d1) with Odin and now my phone is stuck on "downloading" screen. When I try to cancel (restart phone) it goes to the startup/booting screen for less than a second and then jumps back to "downloading". It says this at the top left corner of the screen:
recovery: Error validating footer (6) CUSTOM RECOVERY VBMETA N970F XXU1 ASG0. 24967245R
I am able to get into the custom OS installation screen (don't know what it's actually called but second picture) by letting the battery drain so that the phone turns off and then holding volume up + volume down key and plugging the phone into my laptop with USB.
The bootloader is unlocked. I went to https://twrp.me/samsung/samsunggalaxynote10.html and even there it says "Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot." Does anyone know how to fix this? Thanks in advance.
Click to expand...
Click to collapse
Go first to the unlocking menu to check if your device is really unlocked, long press volume up, and see which the menu says.
If it is unlocked, then flash the vbmeta file provided, then try to boot to recovery and perform a factory reset.
SubwayChamp said:
Go first to the unlocking menu to check if your device is really unlocked, long press volume up, and see which the menu says.
If it is unlocked, then flash the vbmeta file provided, then try to boot to recovery and perform a factory reset.
Click to expand...
Click to collapse
Bootloader is unlocked and I've flashed the vbmeta file but now my phone is stuck on the startup screen and I can't seem to boot into recovery. Why?
TheAckermans said:
Bootloader is unlocked and I've flashed the vbmeta file but now my phone is stuck on the startup screen and I can't seem to boot into recovery. Why?
Click to expand...
Click to collapse
Maybe you missed some essential part of the process, by unlocking your device through the Download menu option your data has to be erased, it's recommendable after to unlock the bootloader, to reboot again to system and check once the UBS debugging and OEM unlock options if they remain fine, from there you should reboot to download mode again, uncheck the Auto-reboot option within Odin, flash the vbmeta.tar and then flash the TWRP, if all till here goes well you should reboot manually to TWRP by powering off completely, pressing the three buttons, and just now, pressing the volume up + PWR key buttons till your device boots to TWRP.
SubwayChamp said:
Maybe you missed some essential part of the process, by unlocking your device through the Download menu option your data has to be erased, it's recommendable after to unlock the bootloader, to reboot again to system and check once the UBS debugging and OEM unlock options if they remain fine, from there you should reboot to download mode again, uncheck the Auto-reboot option within Odin, flash the vbmeta.tar and then flash the TWRP, if all till here goes well you should reboot manually to TWRP by powering off completely, pressing the three buttons, and just now, pressing the volume up + PWR key buttons till your device boots to TWRP.
Click to expand...
Click to collapse
Thanks for the help, tough i am struggling to get acces to the download menu option. Could you give me a example to acess the menu?
TheAckermans said:
Thanks for the help, tough i am struggling to get acces to the download menu option. Could you give me a example to acess the menu?
Click to expand...
Click to collapse
The screenshots you uploaded some months ago, are the download screen, you, successfully did boot to, download mode doesn't have a useful menu, it's just a mode, so you can flash some things, using Odin. To boot to, use the same way you did it previously, usually, doing it manually, or if you are rooted, you can use other ways too.