Related
Hi guys,
Need URGENT help. I have a Nexus 5 running android 5.0.1. Today morning it was working fine. After that I changed the pin lock and it has stopped working since then. Every time I enter the new password it says wrong password.
1. I tried using Android device manager but it says 'No active devices' linked to my account.
2. I tried using cerberus but it is also of no use as it says 'you are not connected to google servers'.
Can anyone help me unlock the phone or bypass the lock screen.
Much needed help
Did you already tried a factory reset? Boot into recovery mode and make a factory reset. That should help you. You a have a lot of guides showing how to do this .
nunojsa said:
Did you already tried a factory reset? Boot into recovery mode and make a factory reset. That should help you. You a have a lot of guides showing how to do this .
Click to expand...
Click to collapse
Is there a way by which I'll be able to save my data. I guess factory reset will wipe out all the data.
Contact the support of Google. They may be able to fix your account and link it to the device .
gauravshaan said:
Is there a way by which I'll be able to save my data. I guess factory reset will wipe out all the data.
Click to expand...
Click to collapse
You only have screen lock and you haven't encrypted the phone, right? If that is true I can flash a custom recovery to your phone even if the bootloader is locked. Maybe from the custom recovery I could remove the screen lock (never done that before). If I fail to do that then atleast we could save files from the internal storage.
bitdomo said:
You only have screen lock and you haven't encrypted the phone, right? If that is true I can flash a custom recovery to your phone even if the bootloader is locked. Maybe from the custom recovery I could remove the screen lock (never done that before). If I fail to do that then atleast we could save files from the internal storage.
Click to expand...
Click to collapse
I have not encrypted the phone. Can you please let me know how can I install custom recovery without unlocking the bootloader. Sorry for the trouble but I'm a noob at this.
gauravshaan said:
I have not encrypted the phone. Can you please let me know how can I install custom recovery without unlocking the bootloader. Sorry for the trouble but I'm a noob at this.
Click to expand...
Click to collapse
Well you have to download this
Extract it.
Run it.
Select Nexus5 in AP Chipset
Select the img folder as Target Dir
Check AP check
Check RESTORE BOOT IMG and select recovery
Make sure your phone is turned on
Connect USB cable
Open device manager
Start pressing volume_up+volume_down+power keys until a new device appears
Wait for windows to install drivers
Expand Ports (COM & LPT) in device manager
Check the COM number after Qualcomm QHS-USB QDLoader 9008 device
In boarddiag tool set the same com port what you saw in device manager.
Click on start.
After the process finishes the phone restarts and you have to avoid to get the phone booting to android because it will replace TWRP recovery with the stock one. So when you click on start keep pressing the volume_down key for the whole time until you are in fastboot mode. Then select recovery mode. Then follow the instructions here http://forum.xda-developers.com/showthread.php?t=1409304 I have no idea will it work on lollipop, but it worth a try.
bitdomo said:
Well you have to download this
Extract it.
Run it.
Select Nexus5 in AP Chipset
Select the img folder as Target Dir
Check AP check
Check RESTORE BOOT IMG and select recovery
Make sure your phone is turned on
Connect USB cable
Open device manager
Start pressing volume_up+volume_down+power keys until a new device appears
Wait for windows to install drivers
Expand Ports (COM & LPT) in device manager
Check the COM number after Qualcomm QHS-USB QDLoader 9008 device
In boarddiag tool set the same com port what you saw in device manager.
Click on start.
After the process finishes the phone restarts and you have to avoid to get the phone booting to android because it will replace TWRP recovery with the stock one. So when you click on start keep pressing the volume_down key for the whole time until you are in fastboot mode. Then select recovery mode. Then follow the instructions here http://forum.xda-developers.com/showthread.php?t=1409304 I have no idea will it work on lollipop, but it worth a try.
Click to expand...
Click to collapse
Can this method be used to access data when GUI is unaccessible?
Description of the problem is in "[Q] "Unfortunately, System UI has stopped." after OTA to LRY47I" thread.
hello guys previous night my opo is automatically restart and hang on logo i try to restart several times and leave mobile upto 1 hour but cant succeded.... the condition is set is going to fastboot and recovery and charging also i try wipe cache but still same.... i have very important data inside my opo.... please guide me how i recover my opo or inside data....
oneplus one
variant 64gb
os cyanogen 12
Is it a stock COS ROM?
I suggest you to dirty flash the rom without overwriting /data
So if you flash the zip it's OK but if you flash from fastboot be aware of not flashing userdata_64.img
yes my ROM is stock rom .... what is dirty flash please guide me....
imran72199 said:
yes my ROM is stock rom .... what is dirty flash please guide me....
Click to expand...
Click to collapse
-Is your bootloader unlocked?
-What recovery do you have?
Available signed flashable ROMs: https://forums.oneplus.net/threads/mirrors-for-official-cyanogen-roms-ota-updates.141825/
Find yours or just chose one, and download the signed flashable zip, then copy it to the phone (while in recovery the phone has MTP enabled on the PC) then just flash that ROM from the recovery, this will overwrite system but won't touch data and most likely fix the bootloop.
Before rebooting after flash wipe cache and dalvik just in case.
Next time do a nandroid backup if you have sensible data. I usually don't keep anything important on the phone, everything on google drive.
I don't know my bootloader is locked or unlocked.... when I try to connect phone in recovery and connect USB nothing happen but when I restart phone and set is on onelus logo and attch usb PC recognized as mtp USB device but driver failed....
I don't know my bootloader is locked or unlocked.... when I try to connect phone in recovery and connect USB nothing happen but when I restart phone and set is on onelus logo and attch usb PC recognized as mtp USB device but driver failed....
imran72199 said:
I don't know my bootloader is locked or unlocked.... when I try to connect phone in recovery and connect USB nothing happen but when I restart phone and set is on onelus logo and attch usb PC recognized as mtp USB device but driver failed....
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Do this.
Mr.Ak said:
https://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
Do this.
Click to expand...
Click to collapse
He wants to keep data... So he at least should try my method first.
seanwlk said:
He wants to keep data... So he at least should try my method first.
Click to expand...
Click to collapse
Then reply him about his latest query.
imran72199 said:
I don't know my bootloader is locked or unlocked.... when I try to connect phone in recovery and connect USB nothing happen but when I restart phone and set is on onelus logo and attch usb PC recognized as mtp USB device but driver failed....
Click to expand...
Click to collapse
Which recovery? Stock or twrp? I'm not sure that when you have stock recovery on the phone gets recognized as mtp on the PC.
I can think of adb to push the ROM zip on the PC but if you claim it doesn't get recognized I have no clue. Are you sire you have the google USB drivers installed?
seanwlk said:
Which recovery? Stock or twrp? I'm not sure that when you have stock recovery on the phone gets recognized as mtp on the PC.
I can think of adb to push the ROM zip on the PC but if you claim it doesn't get recognized I have no clue. Are you sire you have the google USB drivers installed?
Click to expand...
Click to collapse
i have cyanogen recovery.... my set is previously rooted with kingoroot..... i dont know what to do which driver should install or which rom should be good for me..... please give me simple method to recover my data from opo..... i dont have twrp recovery installed.... only cyanogen recovery after pressing vol+ vol- and power this are the options under cyanogen recovery.....
reboot system now
apply update
wipe data/factory reset
wipe cache partition
wipe media
reboot to bootloader
power down
view recovery logs
inside apply update
apply from adb
choose from internal storage
imran72199 said:
i have cyanogen recovery.... my set is previously rooted with kingoroot..... i dont know what to do which driver should install or which rom should be good for me..... please give me simple method to recover my data from opo..... i dont have twrp recovery installed.... only cyanogen recovery after pressing vol+ vol- and power this are the options under cyanogen recovery.....
reboot system now
apply update
wipe data/factory reset
wipe cache partition
wipe media
reboot to bootloader
power down
view recovery logs
inside apply update
apply from adb
choose from internal storage
Click to expand...
Click to collapse
Install fastboot,adb and google USB drivers : https://drive.google.com/file/d/0B9fZIF6vzIBzT2ZtZkNSVFI5ZHc/view?usp=drivesdk
Reboot the pc
Download twrp: https://dl.twrp.me/bacon/twrp-3.1.0-0-bacon.img.html
Reboot in fastboot mode.
Open a command prompt on the PC inside the folder where the downloaded recovery is.
-Find the folder (maybe user/Downloads)
-while holding shift mouse right click inside the folder
-select "open command prompt here"
Connect your phone and type in cmd
Code:
fastboot devices
If you're lucky and did everything correctly then your phone should appear and you can continue, if not uninstall the drivers you previously had and kingroot and whatever minitool you used and try again.
Now that the device is visible
Code:
fastboot flash recovery twrp twrp-3.1.0-0-bacon.img
Phone should reboot. Just turn off and boot into recovery and hopefully you'll see twrp.
Now connect the phone to the PC an you should see the mass storage and you'll be able to copy the ROM zip there.
Now just flash the zip of the rom and you're done.
U cannot assure you that it will fix the bootloop but it's your best choice.
In the future:
-Never use kingroot or other ****ty mini tools. CMD and manual flash are always the best choice.
-Do a backup if you are not confident with this kind of stuff.
-Don't keep too much stuff on the phone. Use google drive. And services to save contacts, notes images videos.
seanwlk said:
Install fastboot,adb and google USB drivers : https://drive.google.com/file/d/0B9fZIF6vzIBzT2ZtZkNSVFI5ZHc/view?usp=drivesdk
Reboot the pc
Download twrp: https://dl.twrp.me/bacon/twrp-3.1.0-0-bacon.img.html
Reboot in fastboot mode.
Open a command prompt on the PC inside the folder where the downloaded recovery is.
-Find the folder (maybe user/Downloads)
-while holding shift mouse right click inside the folder
-select "open command prompt here"
Connect your phone and type in cmd
Code:
fastboot devices
If you're lucky and did everything correctly then your phone should appear and you can continue, if not uninstall the drivers you previously had and kingroot and whatever minitool you used and try again.
Now that the device is visible
Code:
fastboot flash recovery twrp twrp-3.1.0-0-bacon.img
Phone should reboot. Just turn off and boot into recovery and hopefully you'll see twrp.
Now connect the phone to the PC an you should see the mass storage and you'll be able to copy the ROM zip there.
Now just flash the zip of the rom and you're done.
U cannot assure you that it will fix the bootloop but it's your best choice.
In the future:
-Never use kingroot or other ****ty mini tools. CMD and manual flash are always the best choice.
-Do a backup if you are not confident with this kind of stuff.
-Don't keep too much stuff on the phone. Use google drive. And services to save contacts, notes images videos.
Click to expand...
Click to collapse
writing recovery failed remote: device not unlocked cannot flash or erase
imran72199 said:
writing recovery failed remote: device not unlocked cannot flash or erase
Click to expand...
Click to collapse
This means your bootloader is still locked so you basically can't do anything. To unlock it you would need to factory reset. So your only option is to try installing the ROM via adb on the cyanogen recovery.
PS
Please don't spam my PM I can read you here I get notifications instantly. Thanks. I want to keep the post public in order to help future users in similar conditions so I'm not going to help you in private if it's not strictly necessary.
oneplus one data recovery
seanwlk said:
This means your bootloader is still locked so you basically can't do anything. To unlock it you would need to factory reset. So your only option is to try installing the ROM via adb on the cyanogen recovery.
PS
Please don't spam my PM I can read you here I get notifications instantly. Thanks. I want to keep the post public in order to help future users in similar conditions so I'm not going to help you in private if it's not strictly necessary.
Click to expand...
Click to collapse
if i try to install rom from adb it will kill my data??
imran72199 said:
if i try to install rom from adb it will kill my data??
Click to expand...
Click to collapse
Try to push the zip from adb to /sdcard and then flash the zip through the recovery (which technically should do it since it's a stock ROM)
This will result in a "dirty flash" which will not delete data.
This is your only option in the current state of your phone, if you had rooted your phone properly without kingroot you would have booloader unlocked an you would've had more options. If this doesn't work you are forced to factory reset. And use this opportunity to unlock bootloader with
Code:
fastboot oem unlock
Which due to security measurements will delete all the data.
Before you going to flash anything using adb or something, do this.....
1. Turn off your phone completely.....
2. Connect the charger and let it charger for 10 minutes
3. While the charger is still connected, press the power button (turn it on)
4. Wait....
If the phone boot normally while the charger is still connected, unplug the charger and waits....if the phone goes back bootloop after a few minutes and hours without charger connected then your problem is a dying battery not software....buy a new battery and once your replace it, it will solved your problem without having to flash anything via adb or recovery...it also can save all your data....
iPusak Gaoq™ said:
Before you going to flash anything using adb or something, do this.....
1. Turn off your phone completely.....
2. Connect the charger and let it charger for 10 minutes
3. While the charger is still connected, press the power button (turn it on)
4. Wait....
If the phone boot normally while the charger is still connected, unplug the charger and waits....if the phone goes back bootloop after a few minutes and hours without charger connected then your problem is a dying battery not software....buy a new battery and once your replace it, it will solved your problem without having to flash anything via adb or recovery...it also can save all your data....
Click to expand...
Click to collapse
battery is ok i try your method but not worked
seanwlk said:
Try to push the zip from adb to /sdcard and then flash the zip through the recovery (which technically should do it since it's a stock ROM)
This will result in a "dirty flash" which will not delete data.
This is your only option in the current state of your phone, if you had rooted your phone properly without kingroot you would have booloader unlocked an you would've had more options. If this doesn't work you are forced to factory reset. And use this opportunity to unlock bootloader with
Code:
fastboot oem unlock
Which due to security measurements will delete all the data.
Click to expand...
Click to collapse
what if i flash ota update file through adb sideload of oxygen os
iPusak Gaoq™ said:
Before you going to flash anything using adb or something, do this.....
1. Turn off your phone completely.....
2. Connect the charger and let it charger for 10 minutes
3. While the charger is still connected, press the power button (turn it on)
4. Wait....
If the phone boot normally while the charger is still connected, unplug the charger and waits....if the phone goes back bootloop after a few minutes and hours without charger connected then your problem is a dying battery not software....buy a new battery and once your replace it, it will solved your problem without having to flash anything via adb or recovery...it also can save all your data....
Click to expand...
Click to collapse
Lolwat?? What kind of sorcery are you talking about.... ? if it was the battery it wouldn't have happend right after he messed with that stuff. Improve your troubleshot skills ? this kind of stuff happened to me insane amount of times and always were able to fix it, in this case the guy is limited by the fact he doesn't have the bootloader unlocked.
imran72199 said:
what if i flash ota update file through adb sideload of oxygen os
Click to expand...
Click to collapse
That depends if you are running oxygen os, you can't flash an OTA of OS that you are currently not running. To dirty flash you have to use the same version or distribution of the OS you are currently running.
Xiaomi Pocophone F1 [Beryllium]
WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are NOT risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Unlocking the bootloader
You will have to apply for unlocking bootloader for that make sure you do have MI Account if not then create now, Once you are done with then visit here and make sure you use same mi account you have in your phone then wait for 2-3 days. After that download, the latest MI Unlock tool(Shared in download section) Run mi*.exe as admin and simply sign in there as well. Now move to your phone --> Settings app --> About phone --> Tap on MIUI for 6-7 times and you will see "you are a developer now", go back to main settings additional options --> Developer options --> Turn on OEM Unlocking and USB Debugging. Also allow USB Debugging from this PC If you still didn't get simply revoke all and connect usb then in adb type "adb devices", you will see a prompt on your mobile just tick and allow. You will also see an option called as "Mi Unlock status" click on it and click on "Add account and device" Now turn off your phone and go to fastboot mode for that press and hold volume down + power key. You will see "FASTBOOT MODE" on your phone now move to your PC and connect USB. Now once your phone appears in Mi Unlock Tool just click on "Unlock" "It will pop up some prompts" agree with them by clicking "Unlock anyway", It simply means your data will be wiped and warranty will be void! Once that's done it will reach till 99%(In most cases) and will show wait for some hours like for me it said to wait for 72hrs. This may vary user to user. Now once your waiting time is over try again. If it shows press any key to poweroff on your phone when you connect in fastboot then try changing the port or simply reset your device and redo changes that we did (Follow above process again as USB debugging will be off by default, reset ) Now you are done with unlocking the bootloader let's move to TWRP
Flashing TWRPThis is one of easiest step, just open cmd in adb folder and type following codes :
Code:
adb reboot bootloader
Code:
fastboot flash recovery *your recovery name.img
Code:
fastboot boot recovery.img
We are done with flashing TWRP now let's move to encryption issues!
DFE
Now this is most critical. If you skip you will have to flash stock ROM again so don't mess here!
Download vendor image, dfe, your favorite custom ROM, Gapps, Magisk(Everything mentioned in the download section
Boot into TWRP --> Wipe --> Format data! Reboot to recovery from TWRP menu and flash DFE. Now, go to system and setup MIUI and then come back to TWRP for flashing your favorite custom ROM. Now in TWRP --> Wipe --> Advance wipe choose system, data, dalvik & cache --> Swipe to wipe. Now copy those files to your Sdcard. Then go back to main TWRP page and choose --> Install, Now follow the order of flashing these files(most important)
* Flash vendor image i.e beryllium-9.4.8-9.0-vendor-firmware.zip(This is optional if you had latest MIUI ROM then you can skip this)
* Flash ROM & Gapps
* Flash DFE i.e DisableForceEncryption.zip
* Flash Magisk(up to you, only if you want root)
* Reboot
Enjoy! You are done with it. Yea.. ik Download section is mentioned below!
Here's a quick tip always flash DFE whenever you update ROM as the vendor might be changed, This will ensure the safe running of the device!
Download section :
* Mi Unlock Tool
* TWRP(official)
* Vendor image
* DFE
Enjoy!
Which vendor image to use
dlas.dl said:
Which vendor image to use
Click to expand...
Click to collapse
I have mentioned that in OP i.e "beryllium-9.4.8-9.0-vendor-firmware.zip"
Hi if I want only root
What is the process to root with stock ROM
Thanks in advance
Rameshhreddy98 said:
Hi if I want only root
What is the process to root with stock ROM
Thanks in advance
Click to expand...
Click to collapse
Same, all i want is Magisk and twrp with global (or beta) miui ota and I am not sure what to do
Dearminder said:
Same, all i want is Magisk and twrp with global (or beta) miui ota and I am not sure what to do
Click to expand...
Click to collapse
You can't have the cake and eat it too!
By flashing Magisk, you modify /system and you lose the ability to receive and flash OTA.
AFAIK, there is no official TWRP version which can handle OTAs. The unofficial ones were created for specific purposes and so they fail in some other respect.
tnsmani said:
You can't have the cake and eat it too!
By flashing Magisk, you modify /system and you lose the ability to receive and flash OTA.
AFAIK, there is no official TWRP version which can handle OTAs. The unofficial ones were created for specific purposes and so they fail in some other respect.
Click to expand...
Click to collapse
How about the Orange fox recovery? Doesn't it support OTA?
Dearminder said:
How about the Orange fox recovery? Doesn't it support OTA?
Click to expand...
Click to collapse
It is supposed to support OTA but it may have other issues as I said above. Read its thread.
Hello,
Could you repost the DFE tool? The link is broken.
Thanks in advance
vinimdi said:
Hello,
Could you repost the DFE tool? The link is broken.
Thanks in advance
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=1395089523397944356
Thanks. But I was looking for the DFE without magisk that was available on the OP.
vinimdi said:
Thanks. But I was looking for the DFE without magisk that was available on the OP.
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=1395089523397897352
There you go mate!
Tribes11 said:
https://androidfilehost.com/?fid=1395089523397897352
There you go mate!
Click to expand...
Click to collapse
Thank you very much bro
Why its so complicated on poco ? my last phone was mi a1 it was super easy to unlock bl , twrp and root
now i have poco and came here to check rooting and other stuff then shocked by these complications ?
I'm in MIUI stable now and whenever I try to connect my phone in fastboot mode to the mi unlock tool, it automatically exists fastboot mode and I get a black screen with a message, "press any key to shutdown".
Is that normal?
MI unlock has also not been able to detect my phone. I wonder what's wrong.
thapaavijeet said:
I'm in MIUI stable now and whenever I try to connect my phone in fastboot mode to the mi unlock tool, it automatically exists fastboot mode and I get a black screen with a message, "press any key to shutdown".
Is that normal?
MI unlock has also not been able to detect my phone. I wonder what's wrong.
Click to expand...
Click to collapse
Re-install the drivers available in the Unlock tool.
Help me
Bro I requested for bootloader unlock, they gave me 72 hours time, then by mistakenly in middle time I sign out my mi acc from my device and again sign in, then again 72 hours later I try to unlock but now it is showing couldn’t unlock, error -1, I tried with different computer, what to do now ?, how can I unlock bootloader now? With new Mi account? Or with this one? Please help , and sorry for my bad English
Its mentioned here as .... Once that's done it will reach till 99%(In most cases) and will show wait for some hours like for me it said to wait for 72hrs. This may vary user to user. Now once your waiting time is over try again.Once that's done it will reach till 99%(In most cases) and will show wait for some hours like for me it said to wait for 72hrs. This may vary user to user. Now once your waiting time is over try again. ...
DO i have to wait 72 hours to unlock ?? or its just a message and unlock done within secs/ mints
My way of installing TWRP and ROOT on A20e (only tested on a202f).
Everything is working both on TWRP and MAGISK.
Versions:
-Magisk (v26.1)
-MagiskManager (v26.1)
-TWRP (3.6.1_9.0)
_________________________________________________
Download attached files:
-TWRP and ROOT(magisk) Odin is included!
_________________________________________________
#Factory reset is recommended!
#Make sure BOOTLOADER is unlocked!
#If you don't need MAGISK stop at step 6 and reboot to system
[TWRP Installation]
1. Extract required files, open ODIN (as Administrator) click on the "AP" button and choose TWRP-3.6.1_9.0.tar file.
2. In the "Options" menu untick "Auto-Reboot" .
3. On your phone boot into the "Download Mode" then in ODIN you can press the START button. (make sure you are connected to PC)
4. If everything is fine there should be green "PASS!" text in ODIN.
[ If your flashing failed make sure the bootloader is unlocked and check if cable is properly connected ]
[Don't let the phone boot into system because it will replace TWRP with stock recovery.img]
6. Boot into TWRP and FORMAT DATA (Wipe/Format Data) to remove encryption.
# If you don't need MAGISK you can reboot to system. Otherwise continue reading the guide.
[MAGISK Installation]
7. From TWRP reboot into RECOVERY again.
8. Connect your phone to PC or if you moved Magisk-v26.1.zip and Magisk-v26.1.apk to SD card then use SD card.
9. Flash the Magisk-v26.1.zip file and reboot to system.
10. When you boot into system install the Magisk apk.
11. Open it and finish the installation process.
12. Reboot
ENJOY!
[UPDATE]
-Updated versions of both TWRP and MAGISK
# TWRP 3.5.2_9-0 --> TWRP 3.6.1_9-0
# Magisk v23 --> Magisk v24.3
-Remodifed VBMETA
For ANY help contact me on Telegram: https://t.me/SerbianGeek
does encryp work on this ? dont need to backup just hide data part if fone is stole
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
No problems on my end, pal.
SerbianGeekster said:
No problems on my end, pal.
Click to expand...
Click to collapse
this phone is really a PITA. every time i try to do something it's 1 step forward and 2 steps back. never suffered so much. i flashed it like 20 times. all i want is a working twrp on stock rom and pass safetynet
/dev/null/ said:
This one flashes and boots the first time, but after a reboot there is the infamous error "only official released binaries are allowed to be flashed"
Click to expand...
Click to collapse
to bypass this error:
1. connect to wifi
2. change the date to 2 august 2019
3. boot into download mode
4. flash twrp
Thank you! It worked! No problems got me.
I kinda feel like idiot that I couldn't install it with that ease before
OH **** IT WORKED !!!
I've been at this for hours, thank you so much !!!
Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version). I would like to install twrp and then to root it. I tried several tutorials (Odin, OEM unblocked, USB debugging, time change) but twrp installation fails with message 'custom recovery blocked by frp'.
Can anyone help me?
I duckduckgoed, and found this XDA thread, where the second post says the following :
Nemirtingas said:
FRP: https://www.samsung.com/us/support/frp/
FRP Just locks your phone if you alter the boot or recovery image and you had a google account registered. To unlock it you have to wipe data (factory reset) and reflash stock boot.img and recovery.img before using it again. If your cousin wants to flash my ROM (lineageos-13.0) he'd better not, its not stable and he will encouter random reboots and codecs bugs. The best thing to do is to remove FRP from his phone and flash Magisk (a root manager like SuperSU) and debloat it.
For more information, find the Grandprimevelte group on Telegram.
Click to expand...
Click to collapse
The rest of the posts mention the need for a modified boot.img, else your phone would brick after adding a Google account, but I don't know about that... I have MicroG on mine with a Google account and no problems.
Anyway, frp seems to be a related to having a Google account on your phone.
fjunk said:
Hello,
I have a Samsung A20e running with the a202fxxu4cvk1 firmware (a11 version) /.../ Custom recovery blocked by frp'.
Can anyone help me?
Click to expand...
Click to collapse
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?
fjunk said:
Hello..I was wrong. My issue is not related to frp but OEM. OEM is unlocked according to developper menu but is not effective. Not able to upload any custom rom or bootloader.
I read that there was issue (use of a volume up button in download mode).
Any idea?
Click to expand...
Click to collapse
Indeed, my issue is that in download mode I can only do a volume down button and power button to reboot in system mode. No option to unlock bootloader.
I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, odin) ?
lPolarisl said:
I think you only need to do that once, afterwards, download mode doesn't warn you.
What error message do you get exactly when trying to flash TWRP, at what point, and what gives it (phone, od
Click to expand...
Click to collapse
Many thanks for your update. Attached are pictures of the mobile and the Odin result. The error is an OEM issue (red text on the top of the mobile screen). In other forums, I can see that the download mode has an option to unlock OEM bootloader. I can't see it on my phone.
Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?
lPolarisl said:
Putting the camera so that it covers the error message, what an amazing idea xD
I have never encountered this error, so let's start from the beginning.
Have you enabled the developer options, and activated "allow USB debugging" on the phone ? Also, if there is an option "allow OEM unlock", activate that as well (not all Samsung phones have it).
Have you installed the proper ADB and Samsung drivers ? Which version of Odin are you using ?
Click to expand...
Click to collapse
Thanks for your reply.
That's sure that it doesn't really help to hide the error message. Usb debugging is enabled (I am able to run adb commands) and OEM is unlocked on the preference setting. I did the test with Odin 3.13 but same results with newer version. I installed an A11 firmware (a202fxxu4cvk1).
Don't t know how to go ahead. It seems that I don't have the possibility to unlock OEM in the download mode interface....
Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)
lPolarisl said:
Wait, what is that about the firmware ? What did you flash, how and why ?
also, try a patched version of Odin from this post (I have 3.13.1_3B)
Click to expand...
Click to collapse
I bought a refurbished mobile phone (blackmarket). It came with a 9.0 version. I tried to update to a custom rom without success so I installed the latest 'official' version
Download Samsung Galaxy A20e SM-A202F XEF France A202FXXU4CVK1 firmware
Fast download latest Samsung Galaxy A20e firmware SM-A202F from France with A202FXXU4CVK1 and Android version 11
www.sammobile.com
I uploaded this version using Odin. I also tried the patched Odin version. I read that the patched version only works with a10 version.
Huh...
I have no idea how that behaves, but I hardly see why it would cause a problem.
What else could you try... Restore factory settings maybe ?
Pressing volume up when starting in download mode ? (Note, this supposedly relocks the bootloader if it has been unlocked, if that happens and your phone isn't 100% on stock, it will brick.)
Hello everyone,
I need some help with the following situation:
Using Odin I successfully flashed my Galaxy A32 5G with Android 13 (as indicated by the green PASS in Odin).
When the phone tries to reboot, I get the dreaded error message, "Can't load Android system. Your data may be corrupt....."
On my PC I issued the command, >adb devices, but no devices were found.
This is probably because I did not enable USB debugging, when the phone was still working.
I'm trying to avoid doing a factory reset, because I don't want all my data wiped.
According to the following article, you can flash an OTA file using "adb sideload" command, even without enabling USB debugging.
However, everything else I've read says that adb commands work only when USB debugging is enabled.
Fix “Can’t Load Android System Your Data May Be Corrupt” Without Resethttps://www.droidwin.com/fix-cant-load-android-system-your-data-may-be-corrupt-without-reset/
Can someone perhaps clarify whether or not USB debugging is required for using adb commands?
Thank you very much,
Peter
plee12 said:
Hello everyone,
I need some help with the following situation:
Using Odin I successfully flashed my Galaxy A32 5G with Android 13 (as indicated by the green PASS in Odin).
When the phone tries to reboot, I get the dreaded error message, "Can't load Android system. Your data may be corrupt....."
On my PC I issued the command, >adb devices, but no devices were found.
This is probably because I did not enable USB debugging, when the phone was still working.
I'm trying to avoid doing a factory reset, because I don't want all my data wiped.
According to the following article, you can flash an OTA file using "adb sideload" command, even without enabling USB debugging.
However, everything else I've read says that adb commands work only when USB debugging is enabled.
Fix “Can’t Load Android System Your Data May Be Corrupt” Without Resethttps://www.droidwin.com/fix-cant-load-android-system-your-data-may-be-corrupt-without-reset/
Can someone perhaps clarify whether or not USB debugging is required for using adb commands?
Thank you very much,
Peter
Click to expand...
Click to collapse
I think, In stock recovery only the adb sideload command works so it don't need USB Debugging to be turned ON.
aiSanaul said:
I think, In stock recovery only the adb sideload command works so it don't need USB Debugging to be turned ON.
Click to expand...
Click to collapse
Thanks for your input. Encouraged by your input, I read the article again and realized that I have to put the phone in sideload mode first.
So, I went back to the stock recovery mode and selected the menu item, "Apply update from ADB". Then I see the message on the phone, "Now send the package you want to apply....with adb sideload <filename>". Now that I thought the phone was in sideload mode, on the PC I entered ">adb devices". This time it recognized the device and displayed the device name. However, it also displayed the word, "unauthorized", after the device name. According to the article, if sideload is properly entered, it should display the word, "sideload".
Anyway I tried entering ">adb sideload update.zip", and I got the error message, "device unauthorized".
So, any idea how to get the phone to be authorized?
If this is not possible, I was thinking of replacing the stock recovery with a custom recovery like TWRP. This way I can at least back up all my data first before doing a factory reset. However, I believe installing TWRP requires the bootloader to be unlocked, which automatically wipes all data. So, this defeats the purpose of installing TWRP in the first place
Is there some trick to install TWRP without unlocking the bootloader?
Thank you
plee12 said:
Thanks for your input. Encouraged by your input, I read the article again and realized that I have to put the phone in sideload mode first.
So, I went back to the stock recovery mode and selected the menu item, "Apply update from ADB". Then I see the message on the phone, "Now send the package you want to apply....with adb sideload <filename>". Now that I thought the phone was in sideload mode, on the PC I entered ">adb devices". This time it recognized the device and displayed the device name. However, it also displayed the word, "unauthorized", after the device name. According to the article, if sideload is properly entered, it should display the word, "sideload".
Anyway I tried entering ">adb sideload update.zip", and I got the error message, "device unauthorized".
So, any idea how to get the phone to be authorized?
If this is not possible, I was thinking of replacing the stock recovery with a custom recovery like TWRP. This way I can at least back up all my data first before doing a factory reset. However, I believe installing TWRP requires the bootloader to be unlocked, which automatically wipes all data. So, this defeats the purpose of installing TWRP in the first place
Is there some trick to install TWRP without unlocking the bootloader?
Thank you
Click to expand...
Click to collapse
As you already know this is not possible without unlocking bootloader, I will explain further more to make it easy to understand.
If you don't unlock your bootloader and try flashing TWRP on your phone using ODIN Flash Tool then maybe your phone get into an veification error and your phone will end up in a softbrick. You can repair your phone by flashing your phone's stock firmware using ODIN Flash Tool, eventually you will wnd up loosing all your data.
Also unlocking bootloader in Samsung devices is so easy by turning OEM Unlocking in Developer options, but you don't seem to have access to your phone.
An Unlocked Bootloader is the PASS, which allows you to do custom thing to your phone. So without it, this won't work, maybe that is why you got that error “Can’t Load Android System Your Data May Be Corrupt”.
ALTERNATIVELY you can try flashing your phone's OLD original Stock Firmware using ODIN Flash Tool and see what happens. You can also try flashing TWRP through ODIN Flash Tool. Only flash OFFICIAL TWRP made for your device (if any), otherwise you don't have options I guess.
also Why didn't you Unlocked Bootloader before flashing a custom rom? because of warranty?
aiSanaul said:
As you already know this is not possible without unlocking bootloader, I will explain further more to make it easy to understand.
If you don't unlock your bootloader and try flashing TWRP on your phone using ODIN Flash Tool then maybe your phone get into an veification error and your phone will end up in a softbrick. You can repair your phone by flashing your phone's stock firmware using ODIN Flash Tool, eventually you will wnd up loosing all your data.
Also unlocking bootloader in Samsung devices is so easy by turning OEM Unlocking in Developer options, but you don't seem to have access to your phone.
An Unlocked Bootloader is the PASS, which allows you to do custom thing to your phone. So without it, this won't work, maybe that is why you got that error “Can’t Load Android System Your Data May Be Corrupt”.
ALTERNATIVELY you can try flashing your phone's OLD original Stock Firmware using ODIN Flash Tool and see what happens. You can also try flashing TWRP through ODIN Flash Tool. Only flash OFFICIAL TWRP made for your device (if any), otherwise you don't have options I guess.
also Why didn't you Unlocked Bootloader before flashing a custom rom? because of warranty?
Click to expand...
Click to collapse
Thanks very much for your detailed explanations and for your continued support.
Let me answer your question first about why I didn't unlock the bootloader before flashing a custom ROM. Let me backtrack and explain how this problem came about in the first place. My phone was doing an automatic system update two weeks ago (Android 13). After downloading and installing, it tried to boot up. That's when it got stuck in an infinite rebooting loop. At that point, I had no way to change any settings on the phone.
Also, to clear up any confusion, I was not trying to flash a custom ROM. I was simply trying to flash the stock ROM (Android 13), supposedly the same firmware version as the OTA that broke my phone after the automatic system update. I was thinking that perhaps there was an internet glitch during the automatic system update process, which corrupted the OS. So, I was just trying to re-install the same version as the OTA to see if that would solve the problem.
I had also thought about flashing the original version that came with the device (Android 11). But, I think I read somewhere that either Samsung phones do not allow the user to downgrade, or even if it does allow you do so, the downgrading process will wipe out the existing data on the phone. Perhaps you can confirm that or not?
In the meantime, as you suggested, I will look into how to flash TWRP.
Thank you