I can't use my phone, it needs the older Google account in order to keep using it, but I don't remember the details. Is there a way to bypass this?! It's really stupid. iPhones has this sort of protection but Apple keeps track of its users so it makes sense... Now if you do a mistake here your phone is useless?! Or, there's a fix for it
Thanks
You can try to unlock bootloader and see if that works. Someone did data wipe on official firmware, with root and recovery if never asks
FreiKhost said:
I can't use my phone, it needs the older Google account in order to keep using it, but I don't remember the details. Is there a way to bypass this?! It's really stupid. iPhones has this sort of protection but Apple keeps track of its users so it makes sense... Now if you do a mistake here your phone is useless?! Or, there's a fix for it
Thanks
Click to expand...
Click to collapse
If you have twrp you can easily fix it. If not then there is a way to flash persist partition to fix it.
djhulk2 said:
You can try to unlock bootloader and see if that works. Someone did data wipe on official firmware, with root and recovery if never asks
Click to expand...
Click to collapse
But how? I can't enable developer options
superac11 said:
If you have twrp you can easily fix it. If not then there is a way to flash persist partition to fix it.
Click to expand...
Click to collapse
If I install TWRP, can I then install back original recovery? I want the phone to look as new after
EDIT: I just realised I can't install TWRP because I can't transfer files to my phone! because on FRP the computer does not recognise the device, and I also can't use ADB push because I can't turn on developer settings. Also, recovery mode does not work. but Fastboot does..
Through fastboot you can root, install twrp, wipe phone completely. You unlock boatloader in fastboot mode. May give you error saying locked...but you sure can still wipe the phone. There isn't a Samsung counter when you root, and you can lock back to official
djhulk2 said:
Through fastboot you can root, install twrp, wipe phone completely. You unlock boatloader in fastboot mode. May give you error saying locked...but you sure can still wipe the phone. There isn't a Samsung counter when you root, and you can lock back to official
Click to expand...
Click to collapse
I did it! In another way without fastboot. But just to know: How can I install TWRP via fastboot, if I can't transfer the zip file to the phone?
Tool all in one, once in fastboot mode it'll show you connected. Recovery and flasher option, you can install twrp and magisk. Works on official rom and custom
You have no chance to access the phone without the code. Its the google FRP lock.
Yess i have solution inbox me ..
This is Factory Reset Protection (FRP) which is a built-in security feature of Android 5.1 and later.
Related
Hello, I have a
Nexus 5, bootloader unlocked on kitkat 4.4
I somehow forgot my new 4 digit unlock PIN i put right before I went to sleep.
I can't connect to my phone with the USB, doesn't show any files. Neither it has usb debbuging on.
I've entered PIN over 500 times but i still dont have "Forgot PIN/Password/Pascode" button.
I CAN'T , in no possible way wipe my data because the items i have there are crucial for me.
If there is nothing I can do then ill go hang myself.
Thanks
If your bootloader is unlocked you can flash a custom recovery, then pull your data from there using adb.
If your data is so crucial, maybe next time the best thing to do is keep backups and/or don't solely keep it on a mobile device.
Elluel said:
If your bootloader is unlocked you can flash a custom recovery, then pull your data from there using adb.
If your data is so crucial, maybe next time the best thing to do is keep backups and/or don't solely keep it on a mobile device.
Click to expand...
Click to collapse
i don't have usb debbuging on.
Smexhy said:
i don't have usb debbuging on.
Click to expand...
Click to collapse
USB Debugging is completely irrelevant. It is ONLY used for adb while in Android. NOT fastboot while in the bootloader or adb while in recovery.
Elluel said:
USB Debugging is completely irrelevant. It is ONLY used for adb while in Android. NOT fastboot while in the bootloader or adb while in recovery.
Click to expand...
Click to collapse
can i pull using the method you suggested the GOOGLE KEEP with it's content?
If i flash a recovery, will i be able to flash back to stock with no recovery for warranty purposes?
Smexhy said:
can i pull using the method you suggested the GOOGLE KEEP with it's content?
Click to expand...
Click to collapse
In a custom recovery you have access to the entire /system and /data partitions once you simply mount them.
1. Boot into the bootloader
2. Flash a custom recovery using fastboot
3. Boot into recovery
From there on you can either use adb pull to retrieve files in your Internal Storage, pull app data if you know how, or remove the set lockscreen PIN/whatever itself.
---------- Post added at 20:50 ---------- Previous post was at 20:46 ----------
Smexhy said:
If i flash a recovery, will i be able to flash back to stock with no recovery for warranty purposes?
Click to expand...
Click to collapse
You won't flash to "no recovery". There is a stock recovery (you can only really wipe data/cache from it hence the need for a custom one).
Technically you voided warranty when you unlocked the bootloader and triggered it's tamper flag, but it is easy to reset and relock after you finish doing whatever you want to do and reflash factory images.
Elluel said:
In a custom recovery you have access to the entire /system and /data partitions once you simply mount them.
1. Boot into the bootloader
2. Flash a custom recovery using fastboot
3. Boot into recovery
From there on you can either use adb pull to retrieve files in your Internal Storage, pull app data if you know how, or remove the set lockscreen PIN/whatever itself.
---------- Post added at 20:50 ---------- Previous post was at 20:46 ----------
You won't flash to "no recovery". There is a stock recovery (you can only really wipe data/cache from it hence the need for a custom one).
Technically you voided warranty when you unlocked the bootloader and triggered it's tamper flag, but it is easy to reset and relock after you finish doing whatever you want to do and reflash factory images.
Click to expand...
Click to collapse
Ok, thanks for helping me. I feel much calmer now
Ok, i've got into the recovery. How do i erase the lock pin?
Nevermind, used this link to solve the problem
http://www.androidfanclub.net/2014/03/reset-android-pattern-lock-password-without-erasing-data.html
I'm not certain of any conditions that you need to have fulfilled in the past but try this. On any computer go to https://www.google.com/android/devicemanager login using the Google account that is used for the device and you should be able to see your device. Click on "Lock" and you get:
New lock screen
Your current lock screen will be replaced with a password lock. Don't use your Google account password.
New Password
Confirm password
Recovery message (optional)
That gets sent to the N5 as the new lock screen and hopefully problem solved.
Hi, I really need your assistance for my pixel. I locked my bootloader after unrooting my phone. This process totally bricked my phone(I can't even get to the booting process of the phone) (I get a message saying that my phone is corrupt). I am able to gain access to my fastboot. So I was wondering if there was a way for me to flash the factory image to my phone and get it to work again. Please of there is anything you can do, please help me.
Its_joey_k23 said:
Hi, I really need your assistance for my pixel. I locked my bootloader after unrooting my phone. This process totally bricked my phone(I can't even get to the booting process of the phone) (I get a message saying that my phone is corrupt). I am able to gain access to my fastboot. So I was wondering if there was a way for me to flash the factory image to my phone and get it to work again. Please of there is anything you can do, please help me.
Click to expand...
Click to collapse
I'm really afraid there's nothing you can do. Before relocking the bootloader, you must go back to an approved stock firmware. (See, when you rooted it, you changed it.)
quangtran1 said:
I'm really afraid there's nothing you can do. Before relocking the bootloader, you must go back to an approved stock firmware. (See, when you rooted it, you changed it.)
Click to expand...
Click to collapse
I unrooted my device, so then after I can lock my bootloader. I'm just wondering if that's how I was supposed to do it.
If you have downloaded the full image from Google servers, try if you can fastboot using the boot image from the full image. It that boots your phone, you could try enabling unlock, get into fastboot to unlock for flashing. You can then flash the full image from unlocked fastboot
hackworks said:
If you have downloaded the full image from Google servers, try if you can fastboot using the boot image from the full image. It that boots your phone, you could try enabling unlock, get into fastboot to unlock for flashing. You can then flash the full image from unlocked fastboot
Click to expand...
Click to collapse
Is there any way you could lead my step by step. I don't want to screw up my phone even more. + I'm new to the community and don't know much.
You can use the fastboot continue command.
This will boot up your phone normally and then you will be able to go to developer settings and enable oem unlocking again.
After this you will be able to unlock from fastboot again.
http://forum.xda-developers.com/pixel/help/accomplished-hardbricked-pixel-d-t3516717
Its_joey_k23 said:
Is there any way you could lead my step by step. I don't want to screw up my phone even more. + I'm new to the community and don't know much.
Click to expand...
Click to collapse
If you can put your phone in fastboot mode, you're not bricked yet.
hackworks said:
If you have downloaded the full image from Google servers, try if you can fastboot using the boot image from the full image. It that boots your phone, you could try enabling unlock, get into fastboot to unlock for flashing. You can then flash the full image from unlocked fastboot
Click to expand...
Click to collapse
You saved my life! Thank you.
I have
UNLOCKED BL
INSTALLED TWRP
FLASHED CUSTOM ROM
Is it possible to disable Factory Reset from TWRP. So that no body can reset my phone & flash ROM & use my phone.
How to track the phone if someone use the phone?
ANYWAY TO GET BACK?
itsmedRb said:
I have
UNLOCKED BL
INSTALLED TWRP
FLASHED CUSTOM ROM
Is it possible to disable Factory Reset from TWRP. So that no body can reset my phone & flash ROM & use my phone.
How to track the phone if someone use the phone?
ANYWAY TO GET BACK?
Click to expand...
Click to collapse
In TWRP you can set a password lock on the recovery screen. This should prevent anyone from accessing the factory reset option from the recovery menu.
As it relates to tracking, Google device manager can be used for that.
Freewander10 said:
In TWRP you can set a password lock on the recovery screen. This should prevent anyone from accessing the factory reset option from the recovery menu.
As it relates to tracking, Google device manager can be used for that.
Click to expand...
Click to collapse
How to set password lock in TWRP recovery.
itsmedRb said:
How to set password lock in TWRP recovery.
Click to expand...
Click to collapse
Follow the instructions given here
I've not gotten the chance to test it out yet. So be careful
Freewander10 said:
Follow the instructions given here
I've not gotten the chance to test it out yet. So be careful
Click to expand...
Click to collapse
what about fastboot. If someone tried in fastboot mode?
itsmedRb said:
what about fastboot. If someone tried in fastboot mode?
Click to expand...
Click to collapse
I really don't know much about fastboot.
But maybe you can add a password and try fastboot to unlock it.
itsmedRb said:
what about fastboot. If someone tried in fastboot mode?
Click to expand...
Click to collapse
You can turn usb debugging off then password protect your settings apk, that will prevent anyone from turning usb debugging back on, this will prevent them flashing it because fastboot won't recognize the device.
I will warn you though. If you go through all of this to prevent anyone from flashing your phone and then your phone randomly softbricks, you'll have to flash the device to fix it, with all the things you're doing to prevent flashing, you wouldn't be able to connect to PC to fix the device. You'll get your own foot caught in your own trap. Be warned.
Sent from my SM-S903VL using Tapatalk
I don't even know why I wanted to root my phone. I'm like 3/4 of the way through rooting it and after I flash the boot_stock.img and the twrp installer .zip, I get this message saying
"Unmodified System Patition
Keep System Read only?
..."
and I don't know what to do. I'm following the video tutorial titled "OnePlus 7 Pro - How to Unlock the Bootloader, Install TWRP, and Root with Magisk" by the XDA devs and I get right up before I need to install Magisk or whatever. I don't care anymore.
Have I bricked my phone? Is there any way for me to go back?
Thanks for the advice.
That's just TWRP telling you the system partition isn't rooted, you can say no to allow read/write, then flash the TWRP zip. It sounds like you didn't do the original setup correctly, in the TWRP it tells you to use :
fastboot boot TWRP.img (replace for the current version)
Then the phone would boot into TWRP but TWRP isn't actually installed, that's why you should then flash the TWRP.zip and then immediately flash the latest Magisk to allow root and allow TWRP to remain in place.
Or, as you say, you could just lock the bootloader back but that will wipe data just as unlocking it did. That's a security measure to stop a malicious attempt to access files.
You could also, most likely, just download the zip for your rom version, put it in the root folder and perform a local "upgrade" which should just put your phone back to default, although, if you unlocked the bootloader it will still be unlocked, you need to run the following command to lock it again :
fastboot oem lock
scp-507 said:
I don't know what to do. I'm following the video tutorial titled "OnePlus 7 Pro - How to Unlock the Bootloader, Install TWRP, and Root with Magisk" by the XDA devs and I get right up before I need to install Magisk or whatever. I don't care anymore.
Click to expand...
Click to collapse
You cared enough at one point to start the process. Whether to root or not is a personal decision, based on what types of added modifications of features you want out of root, and how important those are to you. Maybe you have changed your mind to that point. And I am biased to my own opinions. But that opinion would be to go ahead and finish the job, since you got this far. Nothing wrong is going on really, you just got stuck, not knowing what to do next. It does happen from time to time, when modding these devices. And nothing to get discouraged about. You did the right thing coming onto the forum and asking before doing something you were unsure about.
scp-507 said:
Have I bricked my phone? Is there any way for me to go back?
Click to expand...
Click to collapse
This is pretty hard to brick. Unlocking the bootloader, flashing TWRP, and root likely will not result in a real brick. Even if you brick the phone, there is an unbrick tool that will mostly likely get it up and running again.
scp-507 said:
I'm like 3/4 of the way through rooting it and after I flash the boot_stock.img
Click to expand...
Click to collapse
It's not necessary any longer to flash the patched boot.img in order to root. Follow the "Recommended" install method from the TWRP thread, which is simple and straightforward. It's pretty much what the previous response outlined above.
https://forum.xda-developers.com/on...nt/recovery-unofficial-twrp-recovery-t3931322
The method you are following (flashing a patched boot.img) does work. But it has more steps. And you have to be careful to flash the correct boot.img for your OOS version. Otherwise, you may have some issues. So going with the easier method is better, in my opinion.
djsubterrain said:
Or, as you say, you could just lock the bootloader back but that will wipe data just as unlocking it did. That's a security measure to stop a malicious attempt to access files.
Click to expand...
Click to collapse
Is that true for all phones?
If you have the Global OP7Pro and not the T-mobile variant you don't have to be afraid of bricking the phone. The MSM unbrick tool can bring your device back to stock if its bricked or even if its not. I am not sure if the MSM tool works on the T-mobile variants, but it might.
I've hard bricked this device and successfully used the tool to recover it.
djsubterrain said:
That's just TWRP telling you the system partition isn't rooted, you can say no to allow read/write, then flash the TWRP zip. It sounds like you didn't do the original setup correctly, in the TWRP it tells you to use :
fastboot boot TWRP.img (replace for the current version)
Then the phone would boot into TWRP but TWRP isn't actually installed, that's why you should then flash the TWRP.zip and then immediately flash the latest Magisk to allow root and allow TWRP to remain in place.
Or, as you say, you could just lock the bootloader back but that will wipe data just as unlocking it did. That's a security measure to stop a malicious attempt to access files.
You could also, most likely, just download the zip for your rom version, put it in the root folder and perform a local "upgrade" which should just put your phone back to default, although, if you unlocked the bootloader it will still be unlocked, you need to run the following command to lock it again :
fastboot oem lock
Click to expand...
Click to collapse
Thanks for the advice. However, once flash the TWRP .zip installer, immediately flash magisk, and then attempt to reboot back into the system it just throws me back into TWRP saying "Unmodified System Partition". Is there something I should be doing after I flash Magisk?
scp-507 said:
Thanks for the advice. However, once flash the TWRP .zip installer, immediately flash magisk, and then attempt to reboot back into the system it just throws me back into TWRP saying "Unmodified System Partition". Is there something I should be doing after I flash Magisk?
Click to expand...
Click to collapse
Ignore this entire reply, I got it rooted. After flashing the TWRP installer, I rebooted back into recovery and flashed Magisk. Then, it booted and all is well, except for the fact that my bootloader is still unlocked and I still get that annoying splash screen telling me my data is insecure. How/should I relock my bootloader?
Well if you relock your bootloader you won't be rooted or have TWRP... It will also wipe all of your data like starting over when you got the phone out of the box.... If you want to stay rooted and use twrp you will have to deal with the splash screen all of us see it on our phones also. Basically you need to have the bootloader unlocked to keep root and have TWRP
scp-507 said:
Ignore this entire reply, I got it rooted. After flashing the TWRP installer, I rebooted back into recovery and flashed Magisk. Then, it booted and all is well, except for the fact that my bootloader is still unlocked and I still get that annoying splash screen telling me my data is insecure. How/should I relock my bootloader?
Click to expand...
Click to collapse
You can't relock your bootloader, you currently do not have the default recovery partition, if you really want to relock your bootloader you would need to flash the stock rom back over itself so it replaces the recovery with the default one. Then you can run "fastboot oem lock" but be aware, as I said before, this will want to wipe your data so the rom will go back to default setup. Remember to disable bootloader unlocking from the developer settings if you do, then you will be back to the default stock rom state.
scp-507 said:
Ignore this entire reply, I got it rooted. After flashing the TWRP installer, I rebooted back into recovery and flashed Magisk. Then, it booted and all is well, except for the fact that my bootloader is still unlocked and I still get that annoying splash screen telling me my data is insecure. How/should I relock my bootloader?
Click to expand...
Click to collapse
If you want root, you need to leave the bootloader unlocked. That is normal, and just how it is. The warning screen is just something to live with.
You need to return to full stock (ROM, boot.img, recovery) in order to relock the bootloader (otherwise you will get a bootloop or no boot). Which of course defeats the purpose of rooting the phone. So again, having the bootloader unlocked is the normal and expected state, when you are rooted.
Hey Guys,
So my idiot brain decided to mess around with substatum themes after I updated and rerooted my OP7P. I rooted with magisk but forgot to put TWRP recovery on.
Anyways, got the phone semi bricked when applying one of the overlays. The phone boots and I can see my lock screen wallpaper but the screen is just flashing on/off.
I cant use the fingerprint or pin to get it. Is there a way for me to backup my pictures and data or somehow remove substratum?
Biggest problem is that for whatever reason, the update revoked my ADB authorization so it looks like I cant do anything with ADB.
If someone has any way to salvage my situation, please reply. Factory reset is my last resort due to no backup.
Thank You
Try booting into TWRP and using ADB there.
Well boot to fastboot. Flash twrp there and then reboot to twrp.
Flash rescue zip and you should be good to go
tech_head said:
Try booting into TWRP and using ADB there.
Click to expand...
Click to collapse
pranacrockz said:
Well boot to fastboot. Flash twrp there and then reboot to twrp.
Flash rescue zip and you should be good to go
Click to expand...
Click to collapse
Problem is, I dont have TWRP recovery flashed, looks like it reverted to stock recovery after I updated. I rooted with Magisk which does not put TWRP back. I forgot to flash it after.
I also probably wont be able to do anything in fastboot either because the update removed the ADB Authorization and I am unable to accept it since my screen doesnt respond to anything, I will attempt this route though.
Edit: No go. ADB vendor key not set and I dont think I will be able to accept it on my device due to unresponsive screen
morphius88 said:
Problem is, I dont have TWRP recovery flashed, looks like it reverted to stock recovery after I updated. I rooted with Magisk which does not put TWRP back. I forgot to flash it after.
I also probably wont be able to do anything in fastboot either because the update removed the ADB Authorization and I am unable to accept it since my screen doesnt respond to anything, I will attempt this route though.
Edit: No go. ADB vendor key not set and I dont think I will be able to accept it on my device due to unresponsive screen
Click to expand...
Click to collapse
Fastboot doesn't need adb.
Switch off the phone, reboot to fastboot.
Then type fastboot boot (filelocation of twrp.img)
Then your phone will boot to twrp.
Flash rescue.zip.
If it is still a no go. Then use msm tool
pranacrockz said:
Fastboot doesn't need adb.
Switch off the phone, reboot to fastboot.
Then type fastboot boot (filelocation of twrp.img)
Then your phone will boot to twrp.
Flash rescue.zip.
If it is still a no go. Then use msm tool
Click to expand...
Click to collapse
Rebooted to fastboot, entered the PIN but Fastboot is a no go. Just keeps saying <waiting for any device> and nothing happens. Would that be because the authorization keys were not accepted after the update?
I am downloading the MSM Tool and will try that if I cant get it to work with fastboot. Will update if it works.
Thanks for suggestions
Ended up using the MSM tool. Did not know it wipes data and also put me back to Android 9.
Oh well, lesson learned. Gotta make monthly backups, make sure twrp is installed and working before messing around with substatrum.
Thanks for the help.