Database Develop

Buying possibly locked phone running Android 5 or 6

When buying from ebay dead phone it might be either password, fingerprint or even Google locked (not sure what the last one means).
Would I be able to use it after fixing the screen and hard reset?
Older Androids at least up to 4.4.2 upon the hard reset simply eraze all data and let you use the phone.
What is the situation with Android 5, 6 and 7?

toshik1 said:
When buying from ebay dead phone it might be either password, fingerprint or even Google locked (not sure what the last one means).
Would I be able to use it after fixing the screen and hard reset?
Older Androids at least up to 4.4.2 upon the hard reset simply eraze all data and let you use the phone.
What is the situation with Android 5, 6 and 7?
Click to expand...
Click to collapse
Be careful if the reactivation lock is on from settings you won't be able to use or flash anything no matter if it's on android 4,5, or 6.
Even if you do hard reset when setup the device it will ask for samsung account password.
You must have device owner password to unlock the reactivation lock.

Thanks!

toshik1 said:
Thanks!
Click to expand...
Click to collapse
i would sugest you to install twrp format and reinstall with samsung kies if phone google locked

viewsfromthepi said:
i would sugest you to install twrp format and reinstall with samsung kies if phone google locked
Click to expand...
Click to collapse
Doesn't work....at least on the 100+ phones iv Google unlocked..I for got the name...but it's in a hidden partition in no way associated with the operating system or recovery etc etc

trinilu27 said:
Doesn't work....at least on the 100+ phones iv Google unlocked..I for got the name...but it's in a hidden partition in no way associated with the operating system or recovery etc etc
Click to expand...
Click to collapse
oh.

Yes FRP does not seem to be an easy one, so all ebay phones are potentially bricks. BTW FRP was first introduced in 5.1

toshik1 said:
Yes FRP does not seem to be an easy one, so all ebay phones are potentially bricks. BTW FRP was first introduced in 5.1
Click to expand...
Click to collapse
Also no two same phones unlock the same way that iv found anyway....and with new security updates every few months,right when someone finds a back door its patched...the result is the internet is full of different videos for the same phone and none of them work....its frustrating. ..for every 25 videos i watch maybe one will work to unlock the phone im working on....

VIE-L09 seems to be totally screwed!

Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help

I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
tolerant said:
Hey,
So i used the SRK tool to try and root my VIE-L09C40 (P9 Plus)
Something seemed to happended during the rooting procedure and when i entered e-recovery it said it had to Download a new version, but couldnt connect to internet via wifi.
Any ways it seemed to work after a while but now i have no keyboard at all, so i cant literally start my phone.
it starts, boots the EMUI 5.0 logo and goes through the information a terms, i click the ok button and thats fine.
Next it tells me to sign in to my wifi, i select my wifi and when i go to type the password all i have is google voice as a keyboard, ive searched and searched but cannot find a way around it, also the frp has tripped on phone so i cannot log in to my google account without a keyboard.
How can i get around this?
do i have to flash parts of firmware?
any help would be great, i sent it away to hauwei and they say warranty void due to software!, can only assume something wrong was flashed?
Waiting for phone to be returned now, please help
Click to expand...
Click to collapse

dmccort said:
I had the exact same issue last night as well. No keyboard and only an option to enter details with voice.
Ended up with an essentially bricked phone. Couldn't find any info on the problem online, so I have to improvise.
I'm starting from scratch after formatting etc. using stock oeminfo, recovery and rolling back to Marshmallow. (fingers crossed ADB will let me, because it was giving me errors before)
Will let you know if I'm successful and the steps I took.
=====================
Click to expand...
Click to collapse
Good luck, i did read that it might be possible to install the base firmware back to it and then update again.
Im sure we are not the only people this has happened to and if you succesfully do this, maybe consider making a full step by step guide so to help others.
Fingers crossed
:good:

Will do my best.. So far it's been a major. I've managed to flash a working stock ROM and boot up. But there are a few things to smooth out. Such as, I have no IMEI number now and the build is C900, also the bootloader is modified.
To get it to boot I had to use DC- Phoenix to flash a factory firmware(Chinese) which I had to pay for. Then I flashed a stock vie-l09c432b181 ROM over the top.
To repair the IMEI I'll have to use HCU, which I'll have to pay for as well. But that's ok. If I can get my original IMEI back, I can use the original unlock code I got earlier this year, otherwise I'll have to get a new one based on a new IMEI.
I can repair the bootloader and region code using twrp etc. so that's not a problem.
I'm actually using the phone to write his reply, so I can at least use it.
Once I have it all 100% working I'll try to put together a full step by step.
Cheers.

Well, I have a working phone. But, it'snot stable. Having trouble with mobile connection, sms, mms, 4g etc not staying connected. So wont be doing any write-ups just yet.
Not until it's stable.
I'm wanting to return it to complete stock now. And that requires trying to find an oeminfo file for C706 (New Zealand).
Will add more as I get there. Sorry.

I had the same problems. All I did is updated the phone with the firmware you want via Twrp . Be warned that it will replace the recovery back to stock. Also clear the cache and etc.

I had a similar issue with SRK tool, bootlooping, won't flash new firmwares, lost all the stock apps and diagnostic tools.
I'm now stuck on a TEST-KEYS build with no NFC or Bluetooth.
My solution was to throw the piece of junk in a drawer, forget about it and I went and bought a Pixel XL instead - a phone that is properly supported and gets updates quickly.

After much messing and a headache I finally got to c432b370
And everything back to normal

tolerant said:
After much messing and a headache I finally got to c432b370
And everything back to normal
Click to expand...
Click to collapse
How did you succeed?
I am stuck on TEST-KEYS but I am not able to flash other roms on it. When I go to recovery, the update process stops after a while
Sent from my VIE-L09 using Tapatalk

[P BETA] Last OTA update broke the phone

Hey,
I was running Android P Beta, and had an OTA update today.
As it's been said on the beta topic, it apparently put me back on Oreo (the pattern lock is different on P).
But now I can't unlock the phone with the pattern at boot. When I put it the right pattern, it gives me a black screen, and ask me to unlock again.
So nothing's coming up, no wifi, no backup etc.
Does anyone have an idea on how to solve this **** ?
Thanks guys.

Deeptwix said:
Hey,
I was running Android P Beta, and had an OTA update today.
As it's been said on the beta topic, it apparently put me back on Oreo (the pattern lock is different on P).
But now I can't unlock the phone with the pattern at boot. When I put it the right pattern, it gives me a black screen, and ask me to unlock again.
So nothing's coming up, no wifi, no backup etc.
Does anyone have an idea on how to solve this **** ?
Thanks guys.
Click to expand...
Click to collapse
Boot to Recovery mode. Wipe/factory reset and reboot system.

koschey_immortal said:
Boot to Recovery mode. Wipe/factory reset and reboot system.
Click to expand...
Click to collapse
Thanks for your answer.
I know I could do that, but I'd like to be able to get some data back first (like whatsapp messages).
Whichi is why I'm trying to find a workaround, but so far it's not really a success.

have you tried android unlock my phone method?
Go to google and sign in. Then go to find/locate my device and then check the option unlock my phone. It will help surely.

Styleshman said:
have you tried android unlock my phone method?
Go to google and sign in. Then go to find/locate my device and then check the option unlock my phone. It will help surely.
Click to expand...
Click to collapse
i think that OTA update on Android P is in real "Android 0 8.1 June Update", as mentioned here, if this true that's the reason why you have problems

Bought phone from ebay, now registration wizard won't let me pass

So I bought this phone from eBay, like many before it. But this time it came with a twist: when I booted the phone, initial setup ran and all wend fine until I got to the register Google account screen.
There, the phone says: "This phone was reset. To continue, sign in with a Google Account that was previously synced on this device".
No matter what account I use, I always get a Toast message saying "Unable to sign in to device due to a unknown error. Please try another account or try to sign in again after 24 hours.".
I'm guessing this is some kind of theft protection where entering a previously synced account "proves" that you're the legit owner. The authorised service here told me that I need some kind of proof that I'm the legit owner and surely enough the eBay seller has issued no invoice containing the phone's IMEI (or any similar document).
Anyway, here I am with this gorgeous phone on my hands which is little more than a brick due to this.
Is there any way I could get it to work again? Returning it will just generate more costs for me and I'd like to avoid that.
I've seen guides on youtube where they managed to bypass this security measure, but both methods I've seen failed for me. I guess the version running on my phone is just too recent and plugged all the holes.
Do I have any way of downgrading the software at least? Note that this is a fully locked phone and I can't even start TWRP from fastboot.
Anything else?
Edit: Now that I'm re-reading this post, it occurred to me that there's very little chance that this phone wouldn't be a stolen one. Had it not been, the seller would easily issue me an invoice.
Leaving this post only because my searching hasn't turned up anything on XDA. Probably also reporting the guy on eBay.

velis74 said:
So I bought this phone from eBay, like many before it. But this time it came with a twist: when I booted the phone, initial setup ran and all wend fine until I got to the register Google account screen.
There, the phone says: "This phone was reset. To continue, sign in with a Google Account that was previously synced on this device".
No matter what account I use, I always get a Toast message saying "Unable to sign in to device due to a unknown error. Please try another account or try to sign in again after 24 hours.".
I'm guessing this is some kind of theft protection where entering a previously synced account "proves" that you're the legit owner. The authorised service here told me that I need some kind of proof that I'm the legit owner and surely enough the eBay seller has issued no invoice containing the phone's IMEI (or any similar document).
Anyway, here I am with this gorgeous phone on my hands which is little more than a brick due to this.
Is there any way I could get it to work again? Returning it will just generate more costs for me and I'd like to avoid that.
I've seen guides on youtube where they managed to bypass this security measure, but both methods I've seen failed for me. I guess the version running on my phone is just too recent and plugged all the holes.
Do I have any way of downgrading the software at least? Note that this is a fully locked phone and I can't even start TWRP from fastboot.
Anything else?
Edit: Now that I'm re-reading this post, it occurred to me that there's very little chance that this phone wouldn't be a stolen one. Had it not been, the seller would easily issue me an invoice.
Leaving this post only because my searching hasn't turned up anything on XDA. Probably also reporting the guy on eBay.
Click to expand...
Click to collapse
From the Settings / About, what is exact (full) build name/number?
Generally, if you are on Nougat then IMO, rolling back to MM should completely reset your phone.
You cannot flash TWRP without unlocking Bootloader. But that will not help much for resetting Google protection.
Btw, enable Developer's menu, does it allow you to unlock FRP/OEM Unlocking - in that case you will be able to reset all from EMUI recovery.

zgfg said:
From the Settings / About, what is exact (full) build name/number?
Generally, if you are on Nougat then IMO, rolling back to MM should completely reset your phone.
You cannot flash TWRP without unlocking Bootloader. But that will not help much for resetting Google protection.
Btw, enable Developer's menu, does it allow you to unlock FRP/OEM Unlocking - in that case you will be able to reset all from EMUI recovery.
Click to expand...
Click to collapse
He can't get passed the setup screen

Twisted Prime said:
He can't get passed the setup screen
Click to expand...
Click to collapse
- Boot to Recovery (switch off, press and keep pressing Vol+ and Pow). Does it boot to stock Recovery and does it allow there to Factory reset (it should but if FRP was unlocked)
- Boot to Fastboot (switch off, connect by USB to PC, press Vol- and Pow), do you see Phone (Bootloader) and FRP locked or unlocked?

zgfg said:
- Boot to Recovery (switch off, press and keep pressing Vol+ and Pow). Does it boot to stock Recovery and does it allow there to Factory reset (it should but if FRP was unlocked)
- Boot to Fastboot (switch off, connect by USB to PC, press Vol- and Pow), do you see Phone (Bootloader) and FRP locked or unlocked?
Click to expand...
Click to collapse
It is stock recovery. I don't recall the option for factory reset. In fact there's no options at all, save for reboots.
Fastboot says everything is locked as it should be.
Don't know how to downgrade to MM.

velis74 said:
It is stock recovery. I don't recall the option for factory reset. In fact there's no options at all, save for reboots.
Fastboot says everything is locked as it should be.
Don't know how to downgrade to MM.
Click to expand...
Click to collapse
Rollback instructions are here
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
But not sure would it allow you to setup.
That is Factory Reset Protection (FRP/OEM Unlocking) - if it was unlocked you would be allowed to reset from recovery.
You can ask seller - maybe he can login to his Google account and remotely remove Google account from the sold phone.
Or you can try DC Unlocker, not sure would it work
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial

Well, DC unlocker ultimately worked, but not before buying a wrong package, having to ask tech support, etc, etc. Not to mention the guy really has no patience for people who don't have his level of understanding of the subject. Why does he do it then if he hates the whole thing so much?

velis74 said:
Well, DC unlocker ultimately worked, but not before buying a wrong package, having to ask tech support, etc, etc. Not to mention the guy really has no patience for people who don't have his level of understanding of the subject. Why does he do it then if he hates the whole thing so much?
Click to expand...
Click to collapse
So did you use DC Unlocker to unlock Bootloader or DC Phoenix to reinstall the phone?

zgfg said:
So did you use DC Unlocker to unlock Bootloader or DC Phoenix to reinstall the phone?
Click to expand...
Click to collapse
DC unlocker. I wanted minimal impact on the OS as the phone is for my daughter and she doesn't do custom ROMs et al

velis74 said:
DC unlocker. I wanted minimal impact on the OS as the phone is for my daughter and she doesn't do custom ROMs et al
Click to expand...
Click to collapse
Sorry for bothering but I'm interested now - when Bootloader was unlocked (and FRP too), were you just able to pass setup or you needed to do Factory reset from Recovery or how did you get the stock ROM working for you

Final resolution: the seller sent me an invoice. I guess that means that the phone wasn't stolen after all since they can only expect that this will be entered into Huawei databases.
zgfg said:
Sorry for bothering but I'm interested now - when Bootloader was unlocked (and FRP too), were you just able to pass setup or you needed to do Factory reset from Recovery or how did you get the stock ROM working for you
Click to expand...
Click to collapse
The procedure was thus:
1. unlocker unlocked the FRP
2. phone rebooted into a factory reset (low level) mode - it specifically said "low level"
3. phone booted into normal Android where the FRP protection was no longer active. On screen where it previously demanded a previous Google account it now only demanded A (any) Google account as I'm used to from all the other phones I ever bought.

Sorry old post

Unlock carrier locked bootloader Pixel [BETA]

UPDATE AS OF 16 OF MAY 2023
This project isn't working right now, but I am still working on it.
However due the complicated nature of the projects and the fact that I have little free time means this project will probably still take time to get to functional state.
If anyone has any idea please contact me, any hell is welcome!
______________________________________________________
Hi!
So I decided I wanted to flash custom software into my phone, but it's bootloader was locked so I figure a way to unlock it!
I am going to leave 2 methods:
1. It's the most risky but has more chance of working. The idea is to flash the whole firmware again to the phone, but from an unlocked model.
This is posible using the EDL mode and Sahara protocol.
The EDL mode is an emergency mode which allows user to flash firmware in case fastboot and ADB fails. It's also available in all Qualcomm devices.
It is also completly independent from the rest of the phone, and it's the first bootloader we have. If everything is ok it triggers the second bootloader(fastboot) which then boots the system(See the diagram if you want).
As we want to reflash the firmware keep in mind this could brick your phone and I won't take any resposability if it happen
Materials:
-QPST
-Qualcomm Driver
-Working USB Cable
-Fastboot and ADB set up and working
-knoledge on using ADB
Procedure:
1. Download and install Qualcomm drivers
2. Download and install QPST
4.Downlaod the MBN file
3. Reboot
4. Connect the phone to the PC, then open cmd and run "adb reboot edl".
If you are on fastboot mode, then try "fastboot oem edl", "fastboot reboot-edl", "fastboot reboot edl". One of this should work
5. Go to C:\Program Files\Qualcomm\QPST\bin\
6.Open QPST Config(it's a blue phone, see picture)
7. Click on "Start clients" and then "Software download". A new window should open
8. Now we need to select the phone image using the browser button
9. Click on start to flash ⚡️
Please be aware the method wasn't tested, so this could brick your phone.
If you decide to try it, and have questions or ru into problems during the process, please let me know.
Also remember to take a backup of your data, as it is goig to be lost. ℹ
____________________________________________________________________________
As for the second method, I tried it and it didn't work for me, but is completly safe so you may want to give it a try.
1. Enrrol on the android 12 beta program, AND MAKE A BACKUP OF YOUR DATA
2. Install the update
3. Now exit from the beta program
4. Now you should have an update, it's a rollback to the stable version of android 12. After you installed the update the phone will restart and factory reset.
5. Do the setup as normal
In the end you may have unlocked the bootloader, to check just go to developer options and check if it is enabled or not.

Can we get a video of how to do this?

trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
So you attempted one of these methods and did it work or not work.What device did you use?

trzpro said:
View attachment 5491701
Click to expand...
Click to collapse
That seems to be a probelm with the drivers. Did you install everything properly?
You may want to uninstall them and reinstall again to see if we solve the problem. Also try to run the app with admin privileges
Let me know how if you have more issues or if this doesn;t solve the problem at all.

AtrixHDMan said:
Can we get a video of how to do this?
Click to expand...
Click to collapse
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.

#mcl said:
I can make a video, but I can only publish it on January. Untill then I think the guide is easy to understand so if you want to try the method you shouldn't have problems.
Click to expand...
Click to collapse
I understand thanks

#mcl said:
这似乎是驱动程序的问题。您是否正确安装了所有内容？
您可能需要卸载它们并重新安装，看看我们是否能解决问题。还尝试以管理员权限运行该应用程序
如果您有更多问题，或者这根本无法解决问题，请告诉我
MOD EDIT: You may need to uninstall them and reinstall to see if we can fix the problem. Also tried running the app with admin rights
Let me know if you have more questions, or if this doesn't solve the problem at all.
Click to expand...
Click to collapse
同样的问题，无法解决。
MOD Edit: Same problem, can't solve it.

Looks like this is a common issue, I will look the documentation of QPST and see if I see the cause of the problem. Thank you guys for helping up this project

So I found that that version of QPST is outdated(it's the 2.7 build 140 and the latest version is 2.7 build 460). I am leaving a zip with it here.
Try and see if this time around we manage to unlock the bootloader

MOD EDIT:
This is the latest version
这是最新版本

#mcl, I have the same problem as you have, I live in Portugal and bought a used Pixel 4 but apparently it's origin is the US, Verizon. From your original post I take it that you didn't try this method yourself and hope others will try? Or were you successful?

for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"

gentle_giant said:
for anyone in the same situation, read this thread: https://android.stackexchange.com/q...ed-against-physical-tampering-in-google-pixel
My guess is: if your pixel's " OEM unlocking " is greyed out it will not be possible to unlock. Although I didn't try the EDL route I'm quit sure that at some point you will get a message "bootloader is locked"
Click to expand...
Click to collapse
Hey I am quite busy recently so I haven't really had time to look more on the thread, though I believe there will always be a way, it may be hard to find but no OS is perfect, and Android is no exception. As it turns out, even if this method worked, when it connect to the internet there will be a high chance that using the IMEI of the phone it will "remember" it's a locked model and won't allow you to flash new firmware.
However I am working on a new method, which is also safer, though I have still work to do, so when It is ready I am going to publish another guide.
Good luck all untill them

Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.

gentle_giant said:
Hi mcl, my problem is: I do like to change OS and I did so on my previous HTC M7 and M10. And these 2 phones still function with PixelExperience 10 or 11.
But at best I'm a simple layman with a lot of enthusiasm.
Anyway, I will keep an eye on this thread and hopefully you will find time to make this new method work!
By the way, I see that we are "neighbors", I live in Portugal.
Click to expand...
Click to collapse
Hahah yeah we are definitely neighbors.
Well I do want to become a software engineer though right now I am just a busy enthusiastic.
I also really enjoy custom OS, when I had my Galaxy S9 I used to have custom ROMs.
Hope I manage to find a new solution as soon as posible for all if you guys!!!

How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com

any luck with that? can I backup my firmware before doing it?

darknmy said:
How is bootloader state protected against physical tampering in Google Pixel
A week ago my professor's Pixel 4 XL was stolen from his desk when he left it there for charging. The phone has been shut down. It had few minutes of battery left when it was plugged in charging. T...
android.stackexchange.com
Click to expand...
Click to collapse
We are not doing physical atack, so that is not a problem for us.
Also, I don't believe the pixel 4 XL is perfect, for sure there are errors and security vulnerabilities. We just need to find them.