As the title says.. is it within the scope of any dev to have some kind of lock or password protection on accessing recovery? This would obviously have to be optional.
Wavesecure is kinda rendered useless if someone could easily flash another rom on the phone before the user can get to wiping all data.
I'm not so concerned about getting a phone back after it's stolen... but i'm much more worried about the information i may have stored on it.
Is this even possible?
Thanks in advance
Alex
a) If you flash another ROM to remove wavesecure, you would have to wipe first and therefore your personal data would be gone anyway.
b) You can install a recovery via adb as far as I know so if the user knew enough to boot into recovery mode, they could flash another recovery and circumvent the password anyway
Hmm, you'd need to password protect fastboot too wouldnt ya?
+1
I was gonna post this. I mean if phone was stolen, and wavesecure did prevent them using it, a wipe will remove it.
Well, ask ninpo maybe over at villainrom site.
Dunno if he would do it, but he modified recovery for villainrom 12 so it could wipe dalvik2cache properly iirc
I would also like it. And flashing over adb is for a newcomer harder then pressing the home button at booting
Seelbreaker said:
I would also like it. And flashing over adb is for a newcomer harder then pressing the home button at booting
Click to expand...
Click to collapse
True.
You could always install the 007 spl if you were that bothered. But I don't recommend that.
I will look into wave secure, as I have a few ideas about things to do.
But remember most thieves would not manage to flash a rom, but a wipe using power + call (I think) is easy.
Also remember that wave secure is a great program, and it has improved loads since I first contacted them to show a way to add your own un approved sim to the allowed list. But I can still bypass it in about 30 seconds, just like any other security measure your phone may use (eg pattern lock or third party app locker).
So whilst a thief in theory could do this, it's unlikely in my opinion. They would need a fair bit of android knowledge, and anyone who knows the inner workings can get rid of any user security measure in seconds.
And btw, when in say I can bypass ws in 30 secs, that don't involve removing the app. I mean bypass that lock screen completely with the app installed
just curious: this possibility doesn't involve activated USB debugging in the device? So you do some trick during boot... or something else I just can't think of?
xdafalter said:
just curious: this possibility doesn't involve activated USB debugging in the device? So you do some trick during boot... or something else I just can't think of?
Click to expand...
Click to collapse
I have more than one method. But I used methods that are unlikely to be found. One certainly can't be fixed, as it is inherently a flaw on linux, though by design. For this reason I won't be disclosing it, and I'm sure people understand.
But yes, usb debugging is useful for bypassing it, though I can still get round it even if you have disabled it
anon2122 said:
But yes, usb debugging is useful for bypassing it, though I can still get round it even if you have disabled it
Click to expand...
Click to collapse
Interesting... I will give it some thought as I like to know stuff
Knowledge brings fear (from Futurama) but don't be evil (Google)
thanks for the replies.
In the end any security can be broken and circumvented.. i just like the idea of layering as much as possible... again i don't expect to be able to get my phone back or stop someone from selling it (given how common imei spoofing seems to be)..
i just want to have time to run a remote wipe from another location.
I do turn off usb debugging whenever i'm not likely to be at a PC.
I know i'm being paranoid... but with good reason
Bantu85 said:
thanks for the replies.
In the end any security can be broken and circumvented.. i just like the idea of layering as much as possible... again i don't expect to be able to get my phone back or stop someone from selling it (given how common imei spoofing seems to be)..
i just want to have time to run a remote wipe from another location.
I do turn off usb debugging whenever i'm not likely to be at a PC.
I know i'm being paranoid... but with good reason
Click to expand...
Click to collapse
Wanna try something? Turn off USB debugging, then try and connect via adb.
Try "adb shell" and see what happens.
I'm not sure what you are up to, but it cannot connect (no device connected or similar output)... and this is the expected result.
Did you want to prove something else?
Yeh adb shell with usb-debugging off just gives "error no device found".
xdafalter said:
I'm not sure what you are up to, but it cannot connect (no device connected or similar output)... and this is the expected result.
Did you want to prove something else?
Click to expand...
Click to collapse
Nah, just wondered. Some phones used to have persisting ADB, which meant that you could get a connection even when that was disabled IIRC.
But remember that you can get adb on boot regardless of setting AFAIK, as well as in recovery
so, if we would have a pw protected recovery/spl and use a kernel with no adb compiled in, where would then be your basis to break in?
xdafalter said:
so, if we would have a pw protected recovery/spl and use a kernel with no adb compiled in, where would then be your basis to break in?
Click to expand...
Click to collapse
Or perhaps limit the use of ADB so that it can only be used while booted into the recovery and after the pw-protection of it has been passed.
Related
hey there everyone,
I will make this as short as I can so you guys can read it. There is a company that fixes my screen, but they (for some reason!) cant promise my data is safe.
Researched myself, I know some suggestions are technically exploits and silly, but I still would like to ask at least, no matter how unlikely.
So.. lockscreen prevents acess to my photos. I disabled G+, which I regret now. Phone is in plane mode. Touchscreen doesnt response. ADB developer option is not activated.
Can I ..
- use "Find my phone" to deactivate the plane mode (could download an app like airdroid maybe)
- Email Google, send them proof and ask them to remotely unlock my phone? Serial Number, billing details etc.
- Activate bluetooth somehow to connect a bluetooth mouse
- Force my phone to reset its options?
- wipe my phone safely and recover the data over an 3rd party app (recovery tool).. maybe over find my phone?
- Somehow circumvent the lockscreen (yes, silly .. I know)
I know about this
HTML:
http://forum.xda-developers.com/nexus-4/help/nexus-4-to-copy-data-broken-touch-input-t2415195
. If really necessary I will fight myself through it.
Thanks everyone who helps!!
nexkon said:
hey there everyone,
I will make this as short as I can so you guys can read it. There is a company that fixes my screen, but they (for some reason!) cant promise my data is safe.
Researched myself, I know some suggestions are technically exploits and silly, but I still would like to ask at least, no matter how unlikely.
So.. lockscreen prevents acess to my photos. I disabled G+, which I regret now. Phone is in plane mode. Touchscreen doesnt response. ADB developer option is not activated.
Can I ..
- use "Find my phone" to deactivate the plane mode (could download an app like airdroid maybe)
- Email Google, send them proof and ask them to remotely unlock my phone? Serial Number, billing details etc.
- Activate bluetooth somehow to connect a bluetooth mouse
- Force my phone to reset its options?
- wipe my phone safely and recover the data over an 3rd party app (recovery tool).. maybe over find my phone?
- Somehow circumvent the lockscreen (yes, silly .. I know)
I know about this
HTML:
http://forum.xda-developers.com/nexus-4/help/nexus-4-to-copy-data-broken-touch-input-t2415195
. If really necessary I will fight myself through it.
Thanks everyone who helps!!
Click to expand...
Click to collapse
Do you have a custom recovery? ADB should work if you boot in recovery and connect your phone.
abaaaabbbb63 said:
Do you have a custom recovery? ADB should work if you boot in recovery and connect your phone.
Click to expand...
Click to collapse
thanks, everything is stock. usb debugging deactivated. plane mode. lock screen.
I'll give up and just let it repair. if they lose my data.. let's not think that far.
nexkon said:
thanks, everything is stock. usb debugging deactivated. plane mode. lock screen.
I'll give up and just let it repair. if they lose my data.. let's not think that far.
Click to expand...
Click to collapse
Wait wait.
Do you have an unlocked bootloader? If not.. then yeah.. no other way.
Replace the screen yourself. Buy a screen assembly off eBay ($45USD for just the screen/digitizer, $60 for one installed in a new bezel - far easier). It's not that hard to do, honestly. Watch some videos on youtube and study the device tear-down on ifixit.com.
Hello people,
so a few days ago I dropped my Galaxy S5 and the screen is now black, I can't use it. I want to try to save the data, but it's not as easy as plug in and transfer, since I have a password that I can't unlock. Using a screen mirroring program is also out of question, because I had USB Debugging disabled before I dropped it.
My next thought was to enable USB debugging with the help of adb, but that didn't work, since adb sees my device as "unauthorized". It still shows up as "Samsung Android ADB Interface" up in the Windows Device Manager.
So my next thought was to flash a custom recovery such as CWM via Odin (my phone doesn't have to be rooted for that, right?). That way I could use the volume keys to navigate through recovery mode once I enter it. All I would have to do is look at screenshots online and count how many times I press the volume buttons to know when to hit enter since the sceen doesn't work.
Would that even be helpful? I really hope that someone can help me or at least tell me there is no possible way to recover the files so I can sleep in peace. I've been trying so much, but all I find is more problems. I even had to use the Samsung 300K tool to enter Download mode, since that didn't work at one point. And I did that to use Dr. Fone's Android Lock Screen Remover which didn't remove my password. So that was 50 dollars well spent.
Looking forward to any kind of help, really desperate right now!
i dont think you can enable usb debugging from outside of the GUI. Can you use one of those MHL devices to get the display output to something? Perhaps the digitizer will still recognize touch input and let you turn it on from there.
youdoofus said:
i dont think you can enable usb debugging from outside of the GUI. Can you use one of those MHL devices to get the display output to something? Perhaps the digitizer will still recognize touch input and let you turn it on from there.
Click to expand...
Click to collapse
That's a pretty good idea! Looks like I haven't tried everything after all. I'll take a look if I the local electric market has some sort of adapter or is there anything I have to take into consideration? I am not familiar with the term MHL...
zakuani said:
That's a pretty good idea! Looks like I haven't tried everything after all. I'll take a look if I the local electric market has some sort of adapter or is there anything I have to take into consideration? I am not familiar with the term MHL...
Click to expand...
Click to collapse
nothing else really to take into consideration, just hope it works for ya
https://images-na.ssl-images-amazon.com/images/I/413PWcLXQHL._SY300_.jpg
Phone fell out of my pocket and got run over. Screen is completely black and the digitizer is done as well. If I connect it to my PC, it comes right up, but I have no way to enable USB file transfer mode so I can't "see" the SD card or internal memory. I tried to use [email protected] with Android Control, but it appears USB Debugging is turned off on the phone as ADB tells me the device is "unauthorized" and [email protected] gives me a "Rejected" status when it connects with the phone. (Yes, I did remove the ADB keys from my PC's ./user/.android folder and tried again)
Recovery is stock so no ADB access to open a shell and tweak anything. I haven't run across an ADB enabled recovery that I can install on this unlocked bootloader. (I can get into download mode and Odin recognizes the phone.) so I thought I'd try the "simple" route.
I bought an MHL adapter and an OTG cable thinking I could use a spare monitor and a mouse to turn on USB debugging or, at a minimum, turn on USB file transfer so I can get my data off the phone. I connected everything up and I can see the display, but mouse movement isn't being passed through the MHL cable assembly. If I plug the OTG cable directly into the phone, the phone does react to mouse movement and clicks and I can get lucky and launch apps, but I can't see WTH I'm doing. The odds of me turning on USB debugging like this are slim.
Anyone know of an MHL adapter that will allow "piggybacking" a USB mouse or an ADB enabled recovery I can flash to the phone? Maybe some uber-secret method to turn on USB debugging without access via ADB?
(Skiddz) said:
Phone fell out of my pocket and got run over. Screen is completely black and the digitizer is done as well...
Click to expand...
Click to collapse
I don't have this device but, I believe that one or both of the following threads may be helpful for what you need and don't be afraid to ask for some member guidance within one of them.
https://forum.xda-developers.com/showthread.php?t=2786395
https://forum.xda-developers.com/showthread.php?t=3607259
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Ibuprophen said:
I don't have this device but, I believe that one or both of the following threads may be helpful for what you need and don't be afraid to ask for some member guidance within one of them.
https://forum.xda-developers.com/showthread.php?t=2786395
Click to expand...
Click to collapse
Yep, have all this working. Replacement phone works so my config is correct. The issue is USB debugging got turned off somehow. If I can get in via ADB, I can tweak the files I need to turn it back on. Or, I can find a MHL/OTG combo that works and just turn it on via the screen. Hell, if I could view the ADB key on the phone, I'd modify that file on my PC and it'd probably work.
https://forum.xda-developers.com/showthread.php?t=3607259
Click to expand...
Click to collapse
Read this one as well. I'm not sure what all gets nuked in the process nor have I researched ADB enabled ROMs. I have 2 files I *need* to get off the phone before I send it back. If I had local copies, I wouldn't sweat it and I'd boot into recovery and since I'm familiar with the order of the menus in there, I can probably do a factory restore. Unfortunately, the 2 files I need were updated/created while I was doing the errands that resulted in the broken screen.
(Skiddz) said:
Yep, have all this working...
Click to expand...
Click to collapse
If you are unable to obtain any member guidance, within any of those threads, the only other thread, that I can point you to, is the following Q&A thread that's specific for all S5 Variants.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.
Looks like it should be a cable with 11-pin connector.
Something like this: https://www.ebay.com/itm/252931732046
bbsc said:
Looks like it should be a cable with 11-pin connector.
Something like this: https://www.ebay.com/itm/252931732046
Click to expand...
Click to collapse
Yeah, I've seen a bunch of those, but have read several reviews that state it does not work with the S5. I wish I could find one locally just to try it out and if it doesn't work, I can return it without too much hassle.
Just spent almost an hour on the phone with Verizon and Samsung. The 2nd tier person at Verizon said that if the phone was still activated, they *might* be able to get in remotely and tweak the USB Debugging setting for me. I would have to acknowledge the request on the screen, but that may have been doable via blind mouse clicks after seeing where the dialogue was located on the display. Unfortunately, the phone was already deactivated and without a working digitizer, I would not have been able to temporarily reactivate it.
Samsung was slightly better than useless. I had to explain several times, to two different people, the specifics of my situation and they couldn't seem to grasp the idea that both the display and the digitizer were dead and all I was looking for was a way to get MHL and OTG working at the same time. That concept seemed completely foreign to them and they couldn't tell me if the dock they manufactured for the S5 would do what I wanted. The capper was the last person I spoke to all of a sudden said, "Thank you. Have a nice day." and hung up while I was asking a question.
I called Asurion again to see if I could send the replacement phone back (Because the sound quality is so bad it's almost useless. Even the Samsung Advanced Support guy said the quality on his end was crappy.) and just get this screen replaced. They told me "That service is not available in your area (I'm in a city of approximately 1.3 million - surely they'd have a vendor here?) and "we don't replace the digitizer, only the glass." When I asked, "How is that possible when the glass, the LCD and the digitizer are all one unit (At least I've not seen the separate components in my searches) that you can replace the glass?" The response was a seemingly scripted, "We don't replace the digitizer." When I asked if I could just send this replacement back and replace the screen myself, they said the phone would no longer be insured. Same as if I had a "professional" swap it out.
At this point, it appears I'm dead in the water. I'm still going to research the feasibility of cobbling my own cable(s) together before I have to return this phone. This seems so simple to solve, but it's proving to be an exercise in frustration.
Having a little success in "driving" the phone now with the use of an MHL adapter and some swapping of MHL and OTG cables and a keyboard. I've verified USB debugging *IS* enabled, turned it off, revoked previous privs, turned developer options off, rebooted the phone, turned developer options and USB debugging back on.
I installed the Samsung USB drivers on my notebook and installed Android Control and [email protected] and tried again. Still getting an unauthorized response from ADB with a request to check the screen for messages. Unfortunately, as soon as I unplug the USB cable from the phone to plug in the MHL adapter, any message that may have been there disappears. I did this same thing on my replacement phone and after a couple tries, I got the Authorization message and was able to get that one "talking" again.
At some point I had installed a screen mirroring app on the old phone and managed to get WiFi working with some blind mouse clicks and got the mirroring working with a keyboard plugged in. It's VERY slow, but I was able to turn on BlueTooth as well. I ran out of time for the trial version of the mirroring app and can't seem to make it work again so....
I'm off to buy a BT keyboard and mouse. The plan is to try and sideload Samsung Smart Switch, use the BT KB/Mouse to "drive" and the MHL adapter to "see" and transfer data that way. Alternately, if I can get the screen mirroring working with BT KB for control, I could, in theory, reauthorize the USB stuff.
Alternately, what's the trick to making ADB work via TCPIP? I've been reading a few threads about it and actually got a brief response (Still unauthorized) early this morning (0230-ish) but have been unable to repeat that. Trying with my new phone ADB tells me it can't "see" any devices and "unable to connect to :5555"
Found a thread on Stack Overflow that mentions adbd insecure needing to be disabled, but I have no idea where that might be done.
Continuing from other thread...
(Skiddz) said:
If I could get an ADB shell up, I can turn on USB debugging *and* copy my key to the phone, but I've got no ADB ability in recovery mode..
Click to expand...
Click to collapse
And here is a chicken and egg. For you need USB debugging activated in order to provide you with an ADB shell. At least as I understand it.
Smart Switch is already installed, but I can't access the confirmation dialogue(s). If I can get the thing talking to the PC, I'm golden. I can pull my data and then do a factory reset.
Click to expand...
Click to collapse
That's strange. I managed to get it working on my Core Prime with a dead screen. Well broken enough. With no OTG support. And I wasn't aware of any dialogue on screen. I loaded up Switch in Windows and it communicated with Switch on the mobile fine AFAICT.
I can the phone recognized by ODIN and wouldn't mind attempting to flash something if it'll help. At this point, I'm considering this pretty much a lost cause so if something gets jacked, I don't care.
Click to expand...
Click to collapse
If your phone has a supported custom recovery then you have a chance.
Was able to recover an ADB key file pair from Saturday afternoon's initial attempt to get in to the phone. Still no joy. However! I *was* able to drive through the settings menus with a keyboard. USB debugging IS on and I was able to revoke USB debugging Authorizations
Click to expand...
Click to collapse
This started off well but if your phone had a list of keys already, even if you didn't know it is, then revoking the keys pulls rug from under your feet. So to speak. However, if you can satisfy the dialogue to authorise a new computer, then that's no problem and your in!
Am I on the right track with revoking authorizations? Any way to make the phone think I've never "touched" it with ADB? Again, the new phone connected right up with no input required from me.
Click to expand...
Click to collapse
I wouldn't have done that given it freshens the slate. But if you wanted to clear it to a near untouched state that is the way to do it. Strange the new phone was easy that way. In that case it would be a good idea to clear it if the old one acts the same.
Here is my story about trying to get USB debugging working:
https://forum.xda-developers.com/ga...how-recover-data-core-prime-sm-g360g-t3681433
Here is a guide I wrote from my story detailing how I hacked my adb key in to authorise my computer for USB debugging:
https://forum.xda-developers.com/android/help/guide-modfying-cf-autoroot-kit-to-t3725596
Now this details what's involved but my phone was fully unsupported by everything but the CFAR kit. Which I needed to hack. You shouldn't need to go to such measures. Just need a recovery with ADB enabled.
Hypexed said:
Continuing from other thread...
And here is a chicken and egg. For you need USB debugging activated in order to provide you with an ADB shell. At least as I understand it.
Click to expand...
Click to collapse
USB debugging *is* on. I was able to verify that once I figured out how to drive "blind" with a keyboard. I was able to turn it off, turn off debugging options, reboot, turn debugging options back on, then turn on USB debugging.
That's strange. I managed to get it working on my Core Prime with a dead screen. Well broken enough. With no OTG support. And I wasn't aware of any dialogue on screen. I loaded up Switch in Windows and it communicated with Switch on the mobile fine AFAICT.
Click to expand...
Click to collapse
I'll have to try again but when I used Switch to move my wife's data from her Droid Mini to an S5, there was a confirmation dialogue on the Mini.
If your phone has a supported custom recovery then you have a chance.
Click to expand...
Click to collapse
G900V. Locked bootloader (Thanks Verizon) and I haven't found a custom recovery I can install without rooting.
This started off well but if your phone had a list of keys already, even if you didn't know it is, then revoking the keys pulls rug from under your feet. So to speak. However, if you can satisfy the dialogue to authorise a new computer, then that's no problem and your in!
Click to expand...
Click to collapse
I was getting the "unauthorized" status of the device via ADB and had no way to compare keys. I revoked keys so I had a known starting point. Yes, if I can get to the dialogue to confirm the access, I'm golden. Going to try the BT keyboard/Mouse and screen mirroring this evening when I'm done for the day. Even if I get Switch to start talking and get my data moved over, I'm going to figure out the ADB thing - it's become personal.
(Skiddz) said:
USB debugging *is* on. I was able to verify that once I figured out how to drive "blind" with a keyboard. I was able to turn it off, turn off debugging options, reboot, turn debugging options back on, then turn on USB debugging.
Click to expand...
Click to collapse
Then you're half way there. Almost living on a prayer. And if you can do the above it should be a cinch to get over the line and get that computer authorised.
I'll have to try again but when I used Switch to move my wife's data from her Droid Mini to an S5, there was a confirmation dialogue on the Mini.
Click to expand...
Click to collapse
It may work different from a non-Samsung phone. I used Switch on Windows to back up data from my Samsung phone. It was able to do so without intervention on the phone. Well I didn't see any prompt on the phone. Since my screen was blank.
G900V. Locked bootloader (Thanks Verizon) and I haven't found a custom recovery I can install without rooting.
Click to expand...
Click to collapse
Aha. Well hopefully you can get it going without need of that. In my case my under supported phone wasn't locked.
I was getting the "unauthorized" status of the device via ADB and had no way to compare keys. I revoked keys so I had a known starting point. Yes, if I can get to the dialogue to confirm the access, I'm golden. Going to try the BT keyboard/Mouse and screen mirroring this evening when I'm done for the day. Even if I get Switch to start talking and get my data moved over, I'm going to figure out the ADB thing - it's become personal.
Click to expand...
Click to collapse
Haha. Yes I know what you mean. You can see by the links I posted how personal I got.
I managed to CF-AutoRoot my phone before I got USB debugging even close to on. Of course I still couldn't do much with a broken rooted phone since all actions needed acknowledgement on screen. Later when I finally broke in and got the authorisation I still didn't have root access from an adb shell since that needed the screen working.
I had AirDroid installed. So once USB debugging was working I could do screen mirroring right away. That was a reward in itself. But it was the darnedest thing. The time I got it up and working suddenly the screen started responding to touch which didn't work before. I could brush my finger across the screen and hear the waters. So I quickly backed up my data. The next day, the screen stopped detecting my touch again. As well as AirDroid being unable control input. It's stuck in the corner and I can't use the mirroring to echo any touch to the phone. Most bizarre! I backuped my data just in time.
I used Helium to do a non root backup even though it was rooted. Worked well. Needed the mirror to see on screen.
I'm in! I was able to use my MHL adapter and a mouse via OTG to get the trial version of Stream Screen Mirror going. Once I got that going, I was able to pair a BT mouse/keyboard and use an MHL adapter to "see". Out of "spite", I fired up Android Control and authorized ADB access and voila! Remote screen and control. Pretty slow, but it works.
Sideloaded Switch via SMB and got it transferring data. It's grinding along now but will likely be another hour or so.
Thanks to everyone for the help.
That's good you got it going. Well done, I knew you would get there. Now if only there was a better solution than all this fiddling around.
Hypexed said:
That's good you got it going. Well done, I knew you would get there. Now if only there was a better solution than all this fiddling around.
Click to expand...
Click to collapse
No kidding... I can't imagine someone without any technical knowledge being able to move their data over in this type of situation. Oh well, it was a nice learning experience. I got a BT keyboard and Mouse for use with my Rapsberry Pi and now have a solution for the next time.
Actually, I think I'm going to root this thing and avoid all the hassle in case this happens again.
I agree with you there!
Hi,
So today I changed the pin for my mom's phone and the completely forgot it.
She has a lot of Photos on the phone that she wants to keep, but she has not turned on the backup to google photos option
Is there a way to unlock the phone or recover the photos ?
I have entered the wrong pin multiple times and I still cant see the forgot password option.
Pls help or else mom will kill me.
I hope there is no solution because it would be big security problem.
Your mother maybe using google photos cloud so dont be worry
This poses a security risk for those who lost their phones, so I hope there's no easy way around it.
RIP OP
I also hope there isn't a remedy. I don't mean to sound negative and not help but look at it from our side.
I once had a phone that needed a pin to unlock after being fully booted. Was able to go into recovery without it though.
But on 6t I think the pin encrypts the partition, so no way of bypassing it.
[irony] Maybe tell some intelligence agency that there is terrorist evidence on the phone, see if they have a "special key". [/irony]
elchmartin said:
I once had a phone that needed a pin to unlock after being fully booted. Was able to go into recovery without it though.
But on 6t I think the pin encrypts the partition, so no way of bypassing it.
[irony] Maybe tell some intelligence agency that there is terrorist evidence on the phone, see if they have a "special key". [/irony]
Click to expand...
Click to collapse
I agree.
Can you not plug in your USB cable and copy the contents off the phone onto your laptop?
KashMiester said:
Can you not plug in your USB cable and copy the contents off the phone onto your laptop?
Click to expand...
Click to collapse
Not without unlocking and enabling USB transfer
Just to be sure, it is the pin for the phone and not the simcard right?
superiscch said:
Just to be sure, it is the pin for the phone and not the simcard right?
Click to expand...
Click to collapse
Good point
Is it not possible to boot to recovery then factory reset it.........
xobtik said:
Hi,
So today I changed the pin for my mom's phone and the completely forgot it.
She has a lot of Photos on the phone that she wants to keep, but she has not turned on the backup to google photos option
Is there a way to unlock the phone or recover the photos ?
I have entered the wrong pin multiple times and I still cant see the forgot password option.
Pls help or else mom will kill me.
Click to expand...
Click to collapse
Get your plot ready then.
You have to format data.
Hopefully you can remember the password or pin.
There is far to many security measures in place
you could by having USB debugging on don't know if it's against rules to tell you or just have them email you don't they still email the password to email reg. on phone
There is simply NO way to access the contents without the encryption key. No app from google that claims it can, not google, not even the NSA or anyone but the key holder can. Trust me, you messed up and there is no other way but to remember what it was or completedly reset the phone. After you reset you will be asked password for the account that was last used there. not worth even trying mate.
I wouldnt normally try to help in a situation regarding security but check out this link: Bypass lock screen PIN all One Plus Devices! Might help!
Good luck and let us know how it turns out :highfive:
That worked for me! Thanks so much!
Scott said:
I wouldnt normally try to help in a situation regarding security but check out this link: Bypass lock screen PIN all One Plus Devices! Might help!
Good luck and let us know how it turns out :highfive:
Click to expand...
Click to collapse
+1 this worked for me too
elchmartin said:
[irony] Maybe tell some intelligence agency that there is terrorist evidence on the phone, see if they have a "special key". [/irony]
Click to expand...
Click to collapse
Not really for 6T. File Based Encryption that's used by OnePlus doesn't help here either. There may be a way for OnePlus 6 tho since it uses a different key to sign its boot image.
It may be possible to change current password by using Google Find My Device (https://www.google.com/android/find), but i haven't used it for a long time so i'm not sure at this point.
I bought this 6t refurbished and I suspect is a t-mobile converted to global. I've tried resetting the phone and deleting all kinds of apps cache/data to no avail. in addition I tried to get the
Google Services Framework Android ID but my phone is not rooted. i would like to keep the phone as stock as possible.
chrisrf said:
I bought this 6t refurbished and I suspect is a t-mobile converted to global. I've tried resetting the phone and deleting all kinds of apps cache/data to no avail. in addition I tried to get the
Google Services Framework Android ID but my phone is not rooted. i would like to keep the phone as stock as possible.
Click to expand...
Click to collapse
Did you convert your tmobile to international ? I guess you did. So either root it and install magisk or livr without Google pay.
Sent from my [device_name] using XDA-Developers Legacy app
chrisrf said:
I bought this 6t refurbished and I suspect is a t-mobile converted to global. I've tried resetting the phone and deleting all kinds of apps cache/data to no avail. in addition I tried to get the
Google Services Framework Android ID but my phone is not rooted. i would like to keep the phone as stock as possible.
Click to expand...
Click to collapse
When you go to About phone the build number will tell you if it is T-Mobile converted phone. If the build number starts with ONEPLUS A6013_34_ then it is converted, if it starts with ONEPLUS A6013_41_ or ONEPLUS A6010_41_ then it is a global version.
Krzysiek_CK said:
When you go to About phone the build number will tell you if it is T-Mobile converted phone. If the build number starts with ONEPLUS A6013_34_ then it is converted, if it starts with ONEPLUS A6013_41_ or ONEPLUS A6010_41_ then it is a global version.
Click to expand...
Click to collapse
yes the build number is ONEPLUS A6013_34_2000222 what should I do ?
chrisrf said:
yes the build number is ONEPLUS A6013_34_2000222 what should I do ?
Click to expand...
Click to collapse
Well you can't do really anything but if you have not had it too long you could return it.
chrisrf said:
yes the build number is ONEPLUS A6013_34_2000222 what should I do ?
Click to expand...
Click to collapse
You have 3 options:
1. DO nothing and hope OnePlus will fix it down the road. I actually lost hope with this one.
2. Load T-Mobile version, and loose dual sim capability. Google Play will pass certification and Google Pay will work.
3. Use Magisk, at your own risk, to trick SafetyNet check.
I have one of those scammy "no warranty" T-mo -> Intl. OnePlus 6T and, with enough work, it is possible to convert to the most recent Intl. android 10, and get root and Google pay working. I don't think at this time it's possible to watch Netflix in HD while having your cake and eating it too, sadly. The A/B situation on this phone is painfully confusing and leads to brick after brick as you learn the ropes of this phone. Not sure that's TMo's fault. Thankfully the bricks are fixable. You need the modded flasher for 9.0.11. From usb serial mode, the flasher gives some gibberish "Sahara" error. There is whole infuriating thread consisting of nothing but post after post of newbs being shamed for asking how to fix this problem (because it's already been asked a million times) but no clear concise solution ever provided (just a bunch of conflicting half-answers i.e., "I finally figured it out after mashing buttons for a long time..." -- What worked for me was holding down all the physical buttons, vol+, vol- and power, with the red "Saharah, please fix..." (something like that) red error message blinking away at me on the computer screen, and the phone plugged in to computer USB, the whole time. Only when its air composition sampling system detects your fingers bleeding profusely, will it kick in and fix your bricked device
So that gets you to an equivalent to a locked Global 9.0.11 rom with no OTA updates. From there you can do developer mode -> unlock bootloader instantly from fastboot -> (loose all your data) -> TWRP; now the a/b stuff gets really confusing AF but if you do TWRP from fastboot->flash 10.3.2 -> TWRP from fastboot again (it's like ms windows!) -> flash TWRP .zip installer -> TWRP from fastboot yet again -> Magisk, you can finally boot system.
To pass CTS profile you'll need to use the command-line signature changer Magisk module and Magisk Hide. Once the play store says it's "Certified" (certifiable more like...) and Magisk is giving you two green checkboxes, you are ready for more suffering. Now you need to freeze the Google Pay/Play apps and Google Play services and blow away all their data. At least that's what I did. Then make sure Magisk hide has all the Google play/GMS/AR/pay stuff hidden in Magisk, one more reboot for good measure, and you're off to the races. This gets Google Pay working and even lets you watch DRM at Widevine L3 level... it's still not all your cake and all your eating I suppose... hopefully you're not a big Netflix guy. Otherwise you kinda bought the wrong phone.
GL! Oh btw I have not found any way to restore an encrypted TWRP backup on this device. Starting to suspect it's literally impossible at this time -- but, if I'm honest, probably I just haven't gone through enough suffering, yet, to figure it out.
anonywimp said:
There is whole infuriating thread consisting of nothing but post after post of newbs being shamed for asking how to fix this problem (because it's already been asked a million times) but no clear concise solution ever provided (just a bunch of conflicting half-answers i.e., "I finally figured it out after mashing buttons for a long time..." -- What worked for me was holding down all the physical buttons, vol+, vol- and power, with the red "Saharah, please fix..." (something like that) red error message blinking away at me on the computer screen, and the phone plugged in to computer USB, the whole time. Only when its air composition sampling system detects your fingers bleeding profusely, will it kick in and fix your bricked device
Click to expand...
Click to collapse
Nope. Just completely dis-confirmed the above recipe. I am clearly still well in the cargo-cult phase of my OP qdl client tools education
All I can say for sure is randomly frobbing with the buttons and the phone-side usb-c cable for long periods of time will usually eventually start the process. And one sure-that-I'm-not-sure---but-still-fairly-confident correction: It probably helps to /un-/plug the phone from the PC, once it starts giving the meaningless red "Sahara quintessence frobnitz poop" error message (or whatever equally meaningful thing it actually says). If you find yourself in TWRP, you can use the "Reboot edl" button. Likewise, I believe the stock recovery has an interface to jump to qdl mode... could be making that up though Anyhow I think from there you want to turn the phone entirely off, which I believe can only at this point be achieved through continuous, uninterrupted mashing of the power button. So just after your get the error and disconnect, is your opportunity to impress the phone by bleeding all over it.
anonywimp said:
You need the modded flasher for 9.0.11. From usb serial mode, the flasher gives some gibberish "Sahara" error. There is whole infuriating thread consisting of nothing but post after post of newbs being shamed for asking how to fix this problem (because it's already been asked a million times) but no clear concise solution ever provided (just a bunch of conflicting half-answers i.e., "I finally figured it out after mashing buttons for a long time..."
Click to expand...
Click to collapse
OK, I think I figured out an actual recipe now, or the beginnings of one. It is still a bit fuzzy in places. It goes like this:
If you're not in qdl mode, or you are there but it won't talk to the proprietary flasher software, get the phone completely turned off. Often this is the hardest part. I have sometimes managed to brick my phone where it will Boot and insta-freeze at the infuriating-yellow-triangle screen¹. Then it will just sit there, indefinitely, and never bring up any sort of USB or wifi connectivity (nor does it show any sign of boot-looping, judging by dmesg output on my computer. It's just cold, and dead. Probably a bootloader bug/secure boot fail). In every semi-brick-like circumstance like this, I've found the following enables me to get the phone to turn itself off reasonably quickly, in fact, in just a couple of seconds, usually: unplug any USB-C cable (so I'm running on batteries), hold down all the buttons* until fingers bleeding or something happens -- if nothing happens, release all the buttons briefly and try again; once off, release all the buttons immediately.
Now get the phone back on, and in qdl mode. Somehow. Usually, if the phone is unplugged and off, I can get it there by holding all the buttons and plugging it into usb. If I'm soft-bricked, I'm already there, so nothing to do. From TWRP I can easily "reboot edl" to get there. Maybe there's ways to do it from fastboot, stock recovery, and system as well, via adb/fastboot commands.... My preferred way is holding "all the buttons" for about 1 second, and plugging in the usb cable, which will cause it to enter qdl mode "just one time" without actually bricking anything.
Now, finally, we run the proprietary flasher tool. Press start and it will go until it gets to the "sahara bingo yip-a-dee-ha" error (or whatever it really says... definitely not exactly what I wrote ).
Now turn the phone off again. Same recipe, but this time it seems to almost-always suffice to keep the phone connected to USB, while holding all-the-buttons. If that isn't working, then I go ahead and unplug, power cycle, and get into qdl mode like above. During this, the computer software is maybe completely disconnected from your phone, *****ing and moaning the whole time about Sahara or whatever. Ignore that, it's fine.
If the phone was fully powered off (rather than power-cycled in place), be sure to next release all the buttons, so that the phone has no usb or button-press input of any kind for at least a fraction of a second. Then press "all the buttons" again (nb: I suspect just vol+ and vol- suffice here, and the power button is superfluous? Maybe even detrimental depending on ordering? If I screw this up (sometimes it winds up booting into recovery or bootloader), then I find a way to ask it to reboot from there into qdl mode, if I can, or else power off from there and try again to use the three buttons.
pro tip said:
It is possible to hold all the buttons for too long. In which case, you may find yourself booting system. From there you may need to start this guide over from the beginning, sorry. The correct period of time to hold all the buttons down is about a second. Two seconds is probably too long.
Click to expand...
Click to collapse
Using your fourth hand, Plug in a USB-C cable, what leads from your computer, to the phone, while continuing to hold down all the buttons with your other three hands (or, if you entered qdl via software, just plug it in, now).
That's it, done. Kick back and enjoy as the tool's progress bars go wild and unbrick your phone tut suite. The qdl process should be able to go all the way to the end where it says "100%" (although when you close the program it will still treat this like you are interrupting it in the middle; I think that's because it does multiple phones at once, and you only ever fed it the one phone, so it is alerting you that, hey, phone #2 never got processed).
I am doing the above in a non-FOSS emulator under desktop linux, using the patched client referenced from xda threads.
I imagine qemu would work, as well. Obviously native Windows is going to be your best bet. I def. wouldn't trust Oracle (VirtualBox) USB emulation with my qdl flashing needs, if I were me -- which I am. Phones tend to look like huge USB hubs, full of an ever-changing kaleidoscope of peripherals. Which I don't think the VirtualBox USB stack is really ready to cope with right now. (Not even with the proprietary USB add-on pack or whatever that is -- I simply don't trust Oracle not to hard-brick my phone; VirtualBox has seemingly perma-bricked one device for me, already. That was some time ago but I'm not going to feed it any more devices and I doubt the USB was fixed in vbox. It think it's paravirtualized, or something, so as to be super-fast, but unreliable when the bus topology changes in meatspace.
-- rants / footnotes ---
¹ You know, that warning screen for "security." Which, currently, happens to be punishing me for trying to put the newest stock security updates onto my phone that I just purchased a month ago¹*².
* Not an "All the things" meme -- by "all the buttons" I literally mean all the hardware buttons: [vol+], [vol-], and [power].
¹*² I imagine the person who made the decision to require this in Android would explain it something like this:
straw man said:
(California accent) "Um, like, why? Are you a criminal or something? You know, you could just buy a new phone for like $899 US. Oh, you're, like, poor, or something? Well, OK, I guess there's no way for us to stop you from doing that. But we, like, won't be able to support you in any way. Also, sorry, but we're just going to need to put a brief warning screen on your phone, as a safety measure? No, it's not really a warning for you. More, like, in case other people might be around you for some reason? It just says, 'Hey, no judgement, but it seems like maybe a poor person owns this phone? And they're definitely doing some really weird stuff with it. So just be careful. Like maybe tell a friend where you're going, if you're going to spend time with them.' What? No, I'm sorry, there's no way to remove it. We paid millions to have it fused into the microchips or something? If you could just remove the warning, that would defeat the purpose. So, I'm sure you'd want the people around you to be safe, right? And, like, so do we! So we, like, locked that down pretty tight, yehh-...!'
Click to expand...
Click to collapse