Related
Has anyone figured out a way to unlock this device without having it do a factory reset?
What's the reason for the wipe anyways? I don't understand why this has to happen.
I guess it's impossible, but you can try Carbon Backup to backup your apps+data, it works without root
Sent from my Nexus 7 running Android 4.2.2
I actually have root and titanium backup but it's a pain to backup and restore. Would be nice if the device simply didn't rest itself when unlocked.
Maybe one day the app "Boot Unlocker for Nexus Devices" will support the Nexus 7
Sent from my SK17i running Android 4.1.2
Yeah, something like that is what I'm looking for.
I wonder what method the app uses to unlock other devices.
xxbeanxx said:
I actually have root and titanium backup but it's a pain to backup and restore. Would be nice if the device simply didn't rest itself when unlocked.
Click to expand...
Click to collapse
Weird question how did you root without unlocking bootloader? and why do you need to unlock the bootloader, if you're already rooted?
clockcycle said:
Weird question how did you root without unlocking bootloader? and why do you need to unlock the bootloader, if you're already rooted?
Click to expand...
Click to collapse
I relocked after flashing su (for security reasons). I don't have a need to unlock again right now but wanted to know if it was possible just in case I wanted to flash a zip in the future.
xxbeanxx said:
I relocked after flashing su (for security reasons). I don't have a need to unlock again right now but wanted to know if it was possible just in case I wanted to flash a zip in the future.
Click to expand...
Click to collapse
Ok, makes sense. I did the same thing and couldn't find a way either, and just went at it the same way as initially, wiping.
I've heard that the rationale for forcing a memory wipe when unlocking the bootloader was to protect your data in case your device fell into the wrong hands. If someone steals it and can't get past your lockscreen, they won't be able to get to your device's memory via usb. They can try unlocking the bootloader, but that will wipe the device's memory clean. The thief will be able to use your device but the data is safe. If the bootloader is unlocked, the thief can plug in the phone or tablet, go mucking around in your files, and steal your identity as well as your device.
This is why using a device with an unlocked bootloader is not as safe as using one that is locked. It is also why a new security feature was added to 4.2.2 and adb, although I haven't plugged in my Nexus 7 to find out how it works.
getoffmylawn said:
I've heard that the rationale for forcing a memory wipe when unlocking the bootloader was to protect your data in case your device fell into the wrong hands. If someone steals it and can't get past your lockscreen, they won't be able to get to your device's memory via usb. They can try unlocking the bootloader, but that will wipe the device's memory clean. The thief will be able to use your device but the data is safe. If the bootloader is unlocked, the thief can plug in the phone or tablet, go mucking around in your files, and steal your identity as well as your device.
This is why using a device with an unlocked bootloader is not as safe as using one that is locked. It is also why a new security feature was added to 4.2.2 and adb, although I haven't plugged in my Nexus 7 to find out how it works.
Click to expand...
Click to collapse
Thats a good reason.
4.2.2 on my nexus 4, when I plugged it into the pc, a box poped up on the n4 asking perrmission showing the pc's key..
FWIW, I found this.. http://forum.xda-developers.com/showthread.php?t=2068207
Hi,
Running an unlocked bootloader is quite risky assuming someone has physical access to your phone.
It's extremely easy simply to put it into fastboot mode, flash a recovery (cwm/twrp) and then adb will provide root access to all data.
This is mitigated by encrypting the device, however, I haven't been successful in doing this (http://forum.xda-developers.com/showthread.php?p=48848592) on this particular phone although it works without any issues on nexus phones.
For the people with unlocked bootloaders, do you simply don't care about someone getting physical access or is there anything that can be done?
Also, did someone manage to successfully encrypt the phone (using the standard settings -> security -> encrypt phone) or is everyone running unencrypted?
Having a remote wipe capability is next to useless assuming the thief will power off the phone immediately (before you have a chance to issue the remote wipe).
An unlocked bootloader is mandatory for running Cyanogenmod so that's that.
Thank you.
A thief (if he had the knowledge or the inclination), could steal a locked bootloader phone (without encryption) and simply flash an ftf and untick "wipe data". He would then have full access to the data on the phone by rooting and flashing a recovery for LB. So locked bootloader is cold comfort really
Sent from my C6603 using xda app-developers app
i think the best to happen is to have passwords , when entering fastboot or flashtool , a password should pop up to access the fastboot or flash tool connection , and when entering recovery , a password should also pop up , it is so much secure to get these , but i think it is so hard to make it work or even impossible
You're right, a locked bootloader is indeed a false security.
At the end, encryption is needed but on this phone, it doesn't seem to work and no one tried using it apart from me...
I have my BL locked and I ensure that USB debugging is off, seeing as most rooting solutions required USB debugging I should be good for the average criminal. So the only way to have access to my data...(obviously SD card is immediately compromised with physical access) would be to guess my unlock code. Otherwise, a full wipe of the phone would be required for it to be usable but that should delete all my accounts off the device.
(At least this is what I tell myself to sleep better at night lol)
SmallsXD said:
I have my BL locked and I ensure that USB debugging is off, seeing as most rooting solutions required USB debugging I should be good for the average criminal. So the only way to have access to my data...(obviously SD card is immediately compromised with physical access) would be to guess my unlock code. Otherwise, a full wipe of the phone would be required for it to be usable but that should delete all my accounts off the device.
(At least this is what I tell myself to sleep better at night lol)
Click to expand...
Click to collapse
Getting all your data is as trivial as flashing a custom recovery for locked bootloaders which will provide direct root access.
It probably takes less than a few minutes.
Like they say, there's nothing more dangerous than the sense of false security.
Its not just having a Locked bootloader but also having USB Debugging off, 3rd Party App installs off as that alone would dramatically reduce the number of compatible tools to achieve root access to your device. As far as I know you have to be rooted in most cases to install custom recoveries or at least that is what most instructions say. Remember security is hardly ever a complete solution, its about making it not worth the effort.
For the average person/criminal it is not worth their time to access my data as it is actually worthless to them, As I said the SD card is already taken as soon.
My antitheft software will be lingering with a Data Wipe command, I would have changed the account information stored, I never stored Billing information. So my risk level is very low and not worth any more effort on my end.
As stated, Im speaking from a personal perspective and not a "best practice" one.
The real problem is we like to unlock everything and tick every security risk option and then complain when things get patched that make our device more secure, like all the root exploits.
BL unlocked - Any compilable kernel can now run
USB Debugging - Access from PC's to send commands to your device
Installs from unknown sources - Allows installations of root apps and other apps
All things we need set to do some great things with our devices but how many of us actually look back at these setting once we enable them. It is the equivalent to taking off a door to get the fancy new furniture inside but never putting it back on when we are done.
elias234 said:
i think the best to happen is to have passwords , when entering fastboot or flashtool , a password should pop up to access the fastboot or flash tool connection , and when entering recovery , a password should also pop up , it is so much secure to get these , but i think it is so hard to make it work or even impossible
Click to expand...
Click to collapse
Suppose i have encrypted my device, i.e., it asks for password before booting up...
Q1 So, is it still possible to access the fastboot or recovery mode? Will entering the recovery or fastboot mode would require the password?
Q2 If no, how can i prevent access to fastboot and recovery mode with an unlocked bootloader?
Hello all,
Here is my situation:
- I have my brother's Nexus 4.
- The screen no longer responds to touch, though it still displays correctly when it is turned on.
- It has PIN security
- It is running stock KitKat 4.4.4.
- It is not rooted.
- USB Debugging (ADB) is not enabled.
- Stock recovery is installed.
- The bootloader is locked.
I would like to be able to back up the contents of the phone, but the state it is in renders that difficult. Here are the different options I've considered and discarded:
- Connect the phone via USB to copy the contents of the SD Card
# Impossible since the phone will not mount USB storage (might be a security feature since it has PIN enabled?)
- USB OTG mouse to bypass using the touchscreen
# OTG support is not available on stock kernels for the N4
- Bluetooth mouse
# No way to enable Bluetooth
- Use Android Control to control the phone via my PC
# No ADB; no way to enable ADB; unlocking bootloader to install a recovery with ADB enabled would wipe the phone.
The only option that might work that I have yet to attempt is to replace the screen. However, based on research I did while trying to troubleshoot my own Nexus 4, this could be a costly waste of time. The Nexus 4 has a history of having faulty touchscreens. Case in point, both my phone and my brother's phone suffered from this same flaw. This might be because the touchscreen controller is bad on the N4's motherboard. I junked my N4 specifically for this reason.
I'm beginning to think that there is no way for me to recover the data on this phone. Does anyone know of a way I could get the data off of it? Any way to enable ADB via Fastboot or Recovery? Any way to flash an ADB-enabled kernel via ADB sideload? Any way to unlock the bootloader without wiping all the data? Any way to run a backup of the whole phone?
Please help! Thank you in advance!
You might try towelroot to root. Then bootunlocker from the play store to unlock but you'd have to be able to use the touch screen. Long and short, you're kind of screwed
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You might try towelroot to root. Then bootunlocker from the play store to unlock but you'd have to be able to use the touch screen. Long and short, you're kind of screwed
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yup, that's pretty much what I thought. I was hoping someone here could think of something I hadn't thought of yet. Basically, I think the only two avenues I have to send anything to the phone are via the Bootloader (Fastboot) or via ADB sideload in Recovery. I was hoping I could find something to save me there, but it is looking unlikely.
Hi, I've got 2 phones I want to get the photos off.
An S7 Edge with a broken LCD (can't see anything)
An S6 with a forgotten passcode.
What would you guys suggest? I toyed around with a trial of dr.phone and was able to preview photos on the S6, but I would prefer to find a free way. And dr.phone & fonepaw do not support the s7 edge.
Would a custom recovery like TWRP work? or does that require full access to the phone? (ie turn on debug mode etc)
Thanks in advance?
Abut the S6EDGE I can give you a suggest
Unlock your bootloader first(Require remove the Google/Samsung account,if you login these account your phone before,this way is didnt work)
secound flash the twrp,then you mount your phone and copy photos out to your pc.
Another way:You can contact with some Shenzhen(China) company,they have a lots of way to unlock your phone.hahahahaha
Mazl427 said:
Unlock your bootloader first(Require remove the Google/Samsung account,if you login these account your phone before,this way is didnt work)
secound flash the twrp,then you mount your phone and copy photos out to your pc.
Another way:You can contact with some Shenzhen(China) company,they have a lots of way to unlock your phone.hahahahaha
Click to expand...
Click to collapse
Thanks for the reply. So to flash TWRP I need to unlock the bootloader first? Is this something I can do without the passcode? I did a quick google, and it said the option is under the developer options menu.
northwestmicro said:
Thanks for the reply. So to flash TWRP I need to unlock the bootloader first? Is this something I can do without the passcode? I did a quick google, and it said the option is under the developer options menu.
Click to expand...
Click to collapse
Use fastboot order to unlock it
fastboot oem unlock
and then download the TWRP Image,and flash it by fastboot.
enter the twrp and mount it,done!
Got a question that I am not sure has a proper answer (and yes I know this is a sus question to begin with).
I have an old s7 and I forgot the pattern to unlock it. Developer mode is enabled but since I can't get through the lock screen I can't whitelist my PC on the phone when I connect it. I need to access my google authenticator app because I want to export it to my new phone (use to have it on my new phone but for other reasons it got wiped). I've tried using the samsung service mode code to put it into service mode from the emergency call dialer but that doesn't work. Is there anything else I might be able to try?
use droidkit or drfone screen unlock? I think dr.fone has a free trial, maybe you can screen unlock with it. Or just look for any other 3rd party free screen unlocker. They usually don't need root, nor adb.
Ive tried both but both don't support the s7. At this point I would pay for one of these apps to get into this damned thing.
Is it's bootloader unlocked?
Yes you may try with - UFED4PC_7.49.0.2.tar
This is supported to remove or read screenshot without lock data For Android & specially working on many SAMSUNG devices
AzimBahar said:
Yes you may try with - UFED4PC_7.49.0.2.tar
This is supported to remove or read screenshot without lock data For Android & specially working on many SAMSUNG devices
Click to expand...
Click to collapse
Is that something you can flash via odin or?
Did some research, looks like a full mobile forensic device suite. I don't have 2000 dollars to drop on trying to open a phone.
NO.
This is a tool which can read your phone lock
I wonder if there is a way to use Odin to flash TWRP for a single boot. It might be enough to push the ADB keyfile to the directory or to delete the sqlite keys for the pattern.
AzimBahar said:
NO.
This is a tool which can cellebrite your phone lock
Click to expand...
Click to collapse
That doesn't mean anything Cellebrite is the name of the company that produces UFED.
metalblaster said:
I wonder if there is a way to use Odin to flash TWRP for a single boot. It might be enough to push the ADB keyfile to the directory or to delete the sqlite keys for the pattern.
Click to expand...
Click to collapse
you use fastboot to boot a twrp image on a device, without actually flashing it, but im not entirely sure if you can do it with a locked bootloader. Google it i guess?
PhotonIce said:
you use fastboot to boot a twrp image on a device, without actually flashing it, but im not entirely sure if you can do it with a locked bootloader. Google it i guess?
Click to expand...
Click to collapse
I wonder if I could mount the system partition that way or not bootloader aside. Unlocking the bootloader would kill all the data too which is a no-no.
It does seem possible to flash TWRP on some devices without unlocking the bootloader. How would I go about booting from it with fastboot without flashing it if I tried it? edit: nevermind I know how to do it.
I assume I would have to use the herolte img to try to get it to work since there isn't one specifically for the sprint variant.
Well I tried but I can't seem to read the phone with fastboot. I tried Odin and it predictably threw out the flash because it wasn't properly authenticated either.
Did you install the correct drivers? You need the samsung usb drivers for odin, and some adb and fastboot drivers for adb.
PhotonIce said:
Did you install the correct drivers? You need the samsung usb drivers for odin, and some adb and fastboot drivers for adb.
Click to expand...
Click to collapse
Yeah, of course. I have the Samsung drivers and I tried working with linux and had the same issue. Feels like my only recourse at this point is to setup a kali nethunter.
You also need to manually install adb and fastboot drivers for your device, which for me is pain, but maybe it'll be easy for you.
PhotonIce said:
You also need to manually install adb and fastboot drivers for your device, which for me is pain, but maybe it'll be easy for you.
Click to expand...
Click to collapse
Yeah I have them both. For some reason though Fastboot just doesn't see the device. I tried pinging it with the linux version and its vendor id but it didn't do any good. Kind of a real pain this is becoming. I may just convert my old nexus 11 into a kali nethunter and try to brute force it.
Still haven't found a solution and now I am feeling the consequences. My Nintendo 2FA is on this damned phone. Going to try to call support and get it removed tomorrow but its a real big pain.
Metablaster,
Is there an update to this?
My wife's S8 is pattern locked, she didn't set up a Samsung account prior, and the Google Find my Phone web tool PIN option has been changed/ deleted. Maybe there's an older html version of this somewhere?
ADB keeps coming back that the device access is "unauthorized" even after reboot, so although I thought I enabled USB Debugging before giving her the phone (it used to be mine), she may have restored to factory without enabling it again.
Kali will delete all of the data like a factory reset so that defeats the purpose except to just get use of the phone at all again.
Is there anyone on here that knows of a professional grade service that can do this?
So frustrating...! Why , upon proof of ownership, can't something be done?
Please pm me, I'd want to try the MD-Next option first.
If I run the risk of losing her data than anything more intrusive probably isn't worth it.
mat68046 said:
Please pm me, I'd want to try the MD-Next option first.
If I run the risk of losing her data than anything more intrusive probably isn't worth it.
Click to expand...
Click to collapse
MetalBlaster,
I did manage to get the S8 to boot into Recovery Mode, please PM me about trying the MD-Next step via USB bridge.
mat68046 said:
MetalBlaster,
I did manage to get the S8 to boot into Recovery Mode, please PM me about trying the MD-Next step via USB bridge.
Click to expand...
Click to collapse
Have you already tried to unlock the device with a locked SIM?