Looking for anyone who can help progress things further for this phone. No, I'm not a developer, but I'm learning what I can. Your advice and suggestions are most welcome.
Here's a quick run-down of the phone (as of 10/20/2011) :
Full Spec Sheet
Model No. - IS03
Android Version - 2.2.1 (Froyo)
Baseband/Build Number - 01.01.05 (.06 is available but it breaks the temp root)
Bootloader/Fastboot/Recovery modes are all inaccessible
Short history of root attempts by Build Number (click here)
Open Source files from the Sharp Developer website - (click here)
Checklist GREEN : DONE | RED : NOT DONE
Root - Temporary ONLY (click here or scroll below)
Unlock nand
Dumps - system / recovery
What am I missing from this checklist?
Temporary Rooting Guide (ISuhax306)
Thanks to cielavenir, goroh_kun, and love_marijuana for the work they've been putting in. This method works if your IS03 is on 2.2.1, with Baseband/Build at 01.01.05. If your Baseband/Build is at 01.01.06 or higher, THIS WILL NOT WORK.
You will need ISuhax306.7z, which is attached in this post.
Do this at your own risk. We are not responsible for any adverse effects that you may cause by attempting these methods.
### This is based on the idea that SuperOneClick is useful to make is03break stable. Thank you reporters. ###
1. prepare (on PC)
adb push data_local /data/local/
adb shell chmod 755 /data/local/is03break
adb shell chmod 755 /data/local/psneuter
adb shell chmod 755 /data/local/busybox
adb shell chmod 755 /data/local/lcd_density
adb shell chmod 755 /data/local/market.sh
adb shell chmod 755 /data/local/autoexec.sh
adb shell chmod 755 /data/local/exploit.sh
adb shell chmod 755 /data/local/finalize.sh
adb shell chmod 755 /data/local/pu
adb shell chmod 755 /data/local/pu.sh
adb shell chmod 755 /data/local/prepare_busybox.sh
adb shell chmod 755 /data/local/reboot
adb shell /data/local/prepare_busybox.sh
adb shell rm /data/local/prepare_busybox.sh
adb shell mkdir /data/local/tmp
adb shell chmod 777 /data/local/tmp
2. prepare su (on PC)
[3.0]
adb push su/30efgh/su /data/local
adb install ISuhax306.apk
[2.3.6.3]
adb push su/23efgh/su /data/local
adb install ISuhax2363.apk
3. exploit (on IS03)
$ /data/local/exploit.sh
---alternatively, on PC---
adb shell rm /data/local/tmp/sh
adb shell rm /data/local/tmp/boomsh
adb shell /data/local/psneuter
adb shell /data/local/psneuter
adb shell /data/local/is03break
---
4. finalize (on IS03)
$ /data/local/tmp/sh
# /data/local/finalize.sh
---alternatively, on PC---
adb shell
$ /data/local/tmp/sh
# cat /data/local/local.prop > /data/local.prop
---
5. reboot
6. utilize root
adb shell rm /data/local/psneuter
adb shell rm /data/local/is03break
adb shell rm /data/local/exploit.sh
adb shell rm /data/local/finalize.sh
adb shell
$ au
# cd /data
# ln -s local root
# chmod 777 local #sed requires directory write permission to change lcd_density.
* ISTweak - toggle /sbin/su http://marijuana.ddo.jp/is01/index.php?moddir=downloads&action=single&lid=19&cid=3
* jackpal.androidterm - Terminal
* revised busybox with wget: http://www.mediafire.com/?495qvu33lj6l8 see busybox.7z (use /data/local/prepare_busyboxciel.sh)
You are not alone!
I got my IS03 the first day it was out. Only got it, because it was the best Android phone on au so far. Even though the IS06 will be better. But I needed a contract as soon as possible. Kind of nice phone, but lots of things i don't like. Like the launcher (try ADW.Launcher - can be found in the android market - for home, is a lot faster and looking nicer).
I would love to root this IS03 device to get wifi tether so I can use my Nexus One with Gingerbread soon .
I have been in Android for a long time. Started with the ADP1, Nexus One and now IS03. As well I am working as an Android App Developer for tonchidot (creators of SekaiCamera). So I know my way around Android. But I am not sure how to root the IS03 or even how to try. And a little afraid of ruining my phone . Nexus One is a little different. because i don't depend on it. But I need the IS03 for calling. And can not use my Nexus One on au . If I could I would. That is why i need wifi tether as soon as possible .
Any recommendations on Rooting? Let me know and I will try!
Have you tried the regular rooting tools, just for kicks?
such as z4root and try both perm and temp root...
If you don't mind me borrowing some of your time to work out things, I could try out a few things with rooting, pm me your information(skype/gtalk/msn/aim/etc )
pboos said:
You are not alone!
I got my IS03 the first day it was out. Only got it, because it was the best Android phone on au so far. Even though the IS06 will be better. But I needed a contract as soon as possible. Kind of nice phone, but lots of things i don't like. Like the launcher (try ADW.Launcher - can be found in the android market - for home, is a lot faster and looking nicer).
I would love to root this IS03 device to get wifi tether so I can use my Nexus One with Gingerbread soon .
I have been in Android for a long time. Started with the ADP1, Nexus One and now IS03. As well I am working as an Android App Developer for tonchidot (creators of SekaiCamera). So I know my way around Android. But I am not sure how to root the IS03 or even how to try. And a little afraid of ruining my phone . Nexus One is a little different. because i don't depend on it. But I need the IS03 for calling. And can not use my Nexus One on au . If I could I would. That is why i need wifi tether as soon as possible .
Any recommendations on Rooting? Let me know and I will try!
Click to expand...
Click to collapse
Thank you for your response! I recognize you from twitter when I tried to google up information regarding the IS03. I'm trying ADW right now after you suggested it. I was using Launcher Pro, it was all right; however, ADW seems to be a little smoother.
I'm really scared to try to attempt any rooting procedure with my phone too. I do have a backup phone but I'd hate to brick my new purchase so I definitely need to do my research.
That's cool that you work with tonchidot, I've used Sekai Camera a couple times to test it out, but there really isn't too much activity around me other than a lot of landmarks.
Anyways, if I come up with any information I'll let you know on this thread.
razor950 said:
Have you tried the regular rooting tools, just for kicks?
such as z4root and try both perm and temp root...
If you don't mind me borrowing some of your time to work out things, I could try out a few things with rooting, pm me your information(skype/gtalk/msn/aim/etc )
Click to expand...
Click to collapse
I haven't tried any regular rooting tools just yet. I'm still just getting used to using it. As I find out more, especially in terms of bricking, booting into recovery, etc, I'll probably try some rooting tools.
Thanks for your response too, I will PM you with my information shortly.
just trying to boot into recovery mode...
I was trying to see if I could boot the phone into recovery mode in the first place, all my attempts have failed so far.
There's the power button, volume up and volume down buttons, and the camera button. Hidden from view (need to take off the back cover) is the reset button.
On a sidenote, I timed the startup process just for kicks:
~2 seconds - "Android au with Google" logo appears
~30 s - IS03 animation appears
~40 s - screen brightens slightly
~43 s - Monochromatic menu lights up, IS03 animation is still playing
~50 s - "Reading au card..." message replaces IS03 animation
~53 s - Home screen with Unlock pattern appears
Anyways, back to this recovery mode business: I tried a method that a couple of other websites suggested which was a combination of Vup and CAM being pressed while being powered on. That didn't work, so I tried all sorts of combinations:
Hold POWER throughout startup
Hold Vup only X
Hold Vdown only X
Hold CAM only X
Hold Vup and CAM X
Hold Vdown and CAM X
Hold ALL X
Power on and release power button but
Hold Vup only X
Hold Vdown only X
Hold CAM only X
Hold Vup and CAM X
Hold Vdown and CAM X
Hold ALL X
During Startup
Hold CAM, press HOME X
Hold Vup and CAM, press HOME X
At this point, I tried messing around with the reset button. All the reset button does is restart the phone while powered on. Nothing happens if the reset button is pressed while the phone is off. I still tried various combinations anyways but nothing worked.
After perusing some of the other threads, perhaps my phone has this recovery option disabled (likely), doesn't have such a mode (erm, unlikely?), or I just haven't found the right combination yet (also likely).
It's too bad this phone is only in Japan in the moment. I better brush up on my Japanese...
Tested some Android codes via this page
The only code that seems to work is *#*#4636#*#* which brings up general information that is otherwise easily accessible in the normal menus in this phone.
Hmmm.
z4root attempt
I've just successfully used z4root's temporary root feature to root the phone. <---- I jumped the gun when I ran z4root for the first time and it said it was successful, oops.
Now what? I don't want to try the permanent root solution yet, especially if I don't know how to get my phone into recovery mode yet.
At the moment:
1. z4root temporary root 'works' (USB debugging needs to be checked)
2. Superuser icon is in the drawer
3. BusyBox is not installed as z4root says it will do
4. Downloaded Titanium Backup, program doesn't work (asks to verify rom root and installation of BusyBox)
5. Installing BusyBox from Titanium Backup doesn't seem to work
6. Installed BusyBox installer from the Market, that works
7. Running the newly installed BusyBox installer, it tells me that I don't have root
Regarding step 7: I'm guessing that BusyBox failed to install during the z4root process even though z4root 'worked', plus trying to install via Titanium Backup didn't work as well. At this point, looks like the temporary root solution is a false positive pending further testing.
Universal Androot time.
That was quick. Attempting to install Superuser for Android 2.0-2.2 (or even 1.5-1.6) didn't work. Here's what I get:
*Rooting your device, please wait...
Generating exploit .. [OK]
Generating su .. [OK]
Generating Superuser.apk .. [OK]
Generating root script .. [OK]
*after about 10 seconds, changes to Installing toolkit ..
After roughly 20 seconds, I get this message:
Failed ! No ~~~ Fu goo ~~~
It looks like the process fails somewhere during the toolkit installation.
Boo.
ADB issues
Did it really take this long just to resolve all the ADB issues? All I wanted to do was take a simple screenshot of my phone
When I plugged my phone into my computer, all of the drivers EXCEPT the ADB installed just fine.
1. Install Android SDK and JRE SDK, Eclipse is optional since I'm not really a developer (link)
2. Install PDAnet for Android (link)
3. Ensure that your ADB files are in the correct folder (at least for the ddms.bat stuff...) (link)
So...I can take some screenshots now...yippee.
Trying SuperOneClick
Decided to give this program a chance too since I tried the other ones, and I was finally able to get the ADB driver to work.
First Method
1. Restarted the phone
2. USB Debugging is CHECKED
3. Plugged phone into the netbook
4. Started SuperOneClick, clicked Root
5. SuperOneClick will start looping after running RATC and trying to restart the ADB server. Left it like this for 5 minutes.
6a. IF I uncheck USB debugging while it says "Waiting for device" with the USB connection sound indicating a detected device, USB disconnection sound will play and program will wait. If I check USB DEBUGGING again then the program will resume looping
6b. IF I uncheck USB debugging at any time during the loop when the USB disconnection sound has already played (so before the starting up sound can play), the program will be unable to resume looping and just freeze despite shutting off any processes related to this procedure. At this point I need to restart both my netbook and my phone
7. Letting SOC loop for about 10 minutes will result in the program saying NOT RESPONDING and would then need a fresh restart
Code:
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Pushing rageagainstthecage...
21 KB/s (5392 bytes in 0.249s)
OK
chmod rageagainstthecage...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
OK
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Second Method
1. Leave USB DEBUGGING unchecked
2. Plug phone in, start SOC, click Root
3. When SOC says "Waiting for device", check USB DEBUGGING
4. RATC should start
5. When SOC says "Starting ADB server", uncheck USB DEB, check USB DEB, uncheck USB DEB again before the "Waiting for device" message appears again
I usually can't get this timing right due to some lag on my phone. I got it right a couple of times and after about a minute, SOC will have the NOT RESPONDING indicator on again. At this point, I can check USB DEB and the program might start on a loop again, or I need to restart...again.
With either of the two methods, if I go into my Task Manager on my netbook and kill one of the two ADB.exe (usually the one with the lower memory value) processes, then the program will say FAILED, like so:
Code:
***IF IT KEEPS LOOPING, TRY DISABLING USB DEBUGGING NOW***
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Running rageagainstthecage...
FAILED
Third Method
1. Power off phone, restart netbook
2. Start SOC, click Root
3. When "Waiting for device" message appears, connect phone to netbook
4a. If USB DEB was checked before turning off the phone, SOC will do the looping thing again when the phone is finished turning on
4b. If USB DEB was unchecked before turning off the phone, nothing happens when the phone comes back online
== tl;dr ==
It looks like it's getting stuck at the RATC process and loops from there until it freezes. Range of problems may include: bad USB cables, bad USB ports, and/or this IS03 is one tough SOB.
z4root permanent root option
Just tried the permanent option with z4root.
Similar process that the temporary process did except the phone rebooted. After the reboot, everything seemed to be working as normal.
BusyBox, Titanium Backup, and Wireless Tether all say I am not rooted, though.
So much for that.
Safe Mode
My efforts to boot the phone into recovery mode have led me into Safe Mode instead.
No big deal.
I still haven't found a surefire way to get into Safe Mode except to keep mashing the Volume Up and Camera buttons while pressing the monochromatic buttons when they finally light up just before the home screen appears.
Universal Androot 1.6.2 beta 5, Recovery Mode
Interesting thing about this version is that it adds a Soft Root as well as logging to the SDCARD.
1. Uninstalled Universal Androot 1.6.1 (stable)
2. Installed Universal Androot 1.6.2 beta 5 from the SDCARD using App Install
3. Tried all options, including the option not to install Superuser
RESULT: Failed! No ~~~ Fu Goo ~~~
Would you look at that? I can put my phone into recovery mode through adb commands...huh.
I have a IS03 from au as well, so I appreciate your efforts in this. So far the phone will do, but I do find it strange that I can't use Skype over wifi, instead of 3g...
lundman said:
I have a IS03 from au as well, so I appreciate your efforts in this. So far the phone will do, but I do find it strange that I can't use Skype over wifi, instead of 3g...
Click to expand...
Click to collapse
Thanks for your comments. I feel I'm not really doing much except for poking around to see what kind of reaction I get from the IS03.
If I stumble on something worthwhile, it'll be posted here.
As far as your Skype problem is concerned, when you use Skype, it switches from your WiFi connection to 3g? I believe I can use Skype with my WiFi, but I'll have to pay closer attention to that.
Bootloader and Recovery reboot via ADB
Let's see what happens if I try to reboot my phone via ADB in either recovery or bootloader mode.
According to this site, if I'm not mistaken, I anticipate seeing some menu options pop up when I get into either recovery or bootloader mode.
Rebooting into Recovery Mode
1. Unmount SDCARD
2. USB DEBUG is checked
3. Plug the phone into the netbook
4. Windows+R 'cmd' to bring up the prompt
5. get to android-sdk-windows/tools directory
6. adb devices to ensure that the device is listed
7. adb reboot recovery to restart the phone into recovery
Phone reboots and shows a white triangle with a yellow exclamation mark with the green droid icon in front of it. What happens when I do some button combinations? Let's see...
VolUP + CAM = FAIL
VolDN + CAM = FAIL
POW + CAM = FAIL
POW + VolUP = FAIL
POW + VolDN = FAIL
POW + VolUP + CAM = FAIL
POW + VolDN + CAM = FAIL
VolDN + VolUP + CAM = FAIL
Randomly pressing all buttons = FAIL
I can't access any menu here...
Rebooting into Bootloader Mode
Same steps as before, except
7. adb reboot-bootloader to restart the phone into bootloader
The phone restarts and the Android AU with Google logo appears...and it seems to be stuck at this part. Button presses do nothing, no menu or text.
With either method, I have to take out the battery.
Mistaken, I am.
ADB Driver
Greetings!
It seems this is the only place I've seen for english speaking IS03 help. I saw that you were able to install the ADB drivers. Are you using a Japanese version of windows?
I was able to get the USB drivers from Sharp's site, but no luck in getting them to work...
I'm using Win 7 64bit, but it seems I can't get the ADB interface to be recognized.
Anyhow, any help would greatly appreciated.
adb reboot recovery
starts recovery.. but do not get the menu (no matter which buttons i press)
adb reboot bootloader => hangs in booting? or is that the bootloader?
fastboot devices => no devices.. well. it was worth a try
IS03 ADB Drivers
Well, strangely enough, the IS03 drivers wouldn't install for me, but these would:
sh-dev.sharp.co.jp/android/modules/driver/index.php?/003sh/download
(forum wouldn't let me post the link...)
When I have my phone plugged in and I have an emulator running, I get this:
List of devices attached
SSHEV080667 device
emulator-5554 device
I'm assuming the SSHEV device is my IS03, and the other is obvious...
I haven't gotten to much farther than this, but I thought I'd share...The drivers specific for the IS03 Win 7 64bit at this address:
k-tai.sharp.co.jp/support/a/is03/download/usb/index.html
...they didn't work for me. When trying to install the drivers, they weren't recognized.
I'll post more when I get a bit farther...
Hi,
I am looking for some help as I did something stupid...
I came across some posting that explained that the moto has an unused partition under /cache that could be used for the dalvik-cache.
So I tried to move the dalvik-cache there and link /data/dalvik-cache to this new location.
Now the problem is that I get an "unfortunately the location-service has stopped" message all the time that makes the device unusuable (as soon as I press ok the same warning appears again).
When I try to boot into recovery I get a "dead android robot".
I can however access the device via adb, unfortunately I am not able to get a root shell. My device is rooted, but su in an adb-shell just hangs.
If I could only get a root-shell I could undo my changes and hopefully my device will work again, but I have to idea on what to try...
Can anone help me here?
morgonhed said:
Hi,
I am looking for some help as I did something stupid...
I came across some posting that explained that the moto has an unused partition under /cache that could be used for the dalvik-cache.
So I tried to move the dalvik-cache there and link /data/dalvik-cache to this new location.
Now the problem is that I get an "unfortunately the location-service has stopped" message all the time that makes the device unusuable (as soon as I press ok the same warning appears again).
When I try to boot into recovery I get a "dead android robot".
I can however access the device via adb, unfortunately I am not able to get a root shell. My device is rooted, but su in an adb-shell just hangs.
If I could only get a root-shell I could undo my changes and hopefully my device will work again, but I have to idea on what to try...
Can anone help me here?
Click to expand...
Click to collapse
The dead android bot is normal for stock recovery, if you didn't install a custom one. You can always flash a custom recovery using fastboot, and wipe the dalvik-cache and regular caches. Or, in the "dead android bot" screen, you can press the Vol+ key for about 15 secs, then tap the Power button, then scroll using the Vol buttons to something that says wipe cache. You might have to wipe dalvik-cache as well, if you can. I forget where the options are, since I haven't used the stock recovery in so long, sorry!
Ok, I managed to get beyond the "dead android" and from the menu I did a "wipe cache parition". That ran for some minutes, then it rebooted.
But after that I still have the same problem. The continuous "unfortunately the location-service has stopped" messages still persist.
Any other ideas?
Do you have an unlocked bootloader? If you do, the simplest solution may be to flash back to a stock ROM.
audit13 said:
Do you have an unlocked bootloader? If you do, the simplest solution may be to flash back to a stock ROM.
Click to expand...
Click to collapse
Yes my bootloader is unlocked. But I don't want to loose too much...
I believe the problem is only a permission-problem in my new /cache/dalvik-cache directory (/data/dalvik-cache now links there).
So all I would need is a way to get a root-shell (the device is rooted).
I can do a "adb shell" as normal user but that does not have the permissions to even look into /cache and for whatever reason when I type "su" I don't get an error nor do I become root but the command simply hangs...
The system as such still seems to work, e.g. my Moto still connects to my hotspot and I can ping it from there.
The even seems to be an "adb root" command, but that does not work on my adb. Is there a version of adb somewhere that would honor adb root?
Anyone with another idea on how to get a root-shell in my situation
Sorry, I don't know enough about adb commands to change the directory back to the default.
I assume you have usb debugging enabled and your computer is a trusted machine?
USB debugging is definitely enabled, whether or not I've set up my PC as trusted I don't remember.
If I didn't could that explain why I can get a shell but not as root or would you without a trusted computer not even get a shell?
Ok, issue resolved.
I've flashed clockworkmod recovery and cleared the dalvik-cache with that. That did the trick.
And moving my 300MB dalivk-cache to /cache seems to have worked and frees up memory for me, even better.
Finally the reason I could not get root in the adb shell was that when I type su in the adb-shell a superuser-request pops up on the phone that you have to acknowlege. But with constant warnings poping up I did not even see that...
Thanks for all support.
For the Developer options, look under Root access. Did you grant root access to ADB and apps?
When you type su, look at the phone's screen. Are you prompted to grant root access to ADB?
Hello,
I have Oneplus One 64 gb variant, yesterday my nephew somehow changed my phone's lock pattern and now my phone is locked. USB debugging was disabled at that time. I am not able to get into my phone through any means. I have lot of important data in my phone and don't want to hard reset my device. I found a solution online to get usb debugging on through adb , but I am a ultra noob and don't understand how that has to be done. please dumb it down so that I can save my precious data and unlock my phone when debugging gets enabled. Also I don't have any custom recovery installed on my phone.
This is what is mentioned in the solution.
"Instructions
1. You should try your pattern-cracking software (or whatsoever the genre it has) from inside the Stock Recovery to see whether it works with the former's environment (ADB shell available there or not).
2.Since I would never try step 1., I would do the following:
-For Jellybean 4.2.1:
1. Boot into Recovery and mount Data partition.
2. Open a shell on PC and type:
adb pull /data/property/persist.sys.usb.config ~/
Repace ~/ with home directory of your OS.
3. Open that file in a text editor and you would possibly see mtp written there. Change it to mtp,adb.
Note that sometimes Android doesn't understand the text file changes if the line terminator is "DOS Terminators" which Notepad would probably do on Windows (mine is Linux so no issue here).
In that case, I would suggest not using adb pull but doing:
adb shell
echo 'mtp,adb' > /data/property/persist.sys.usb.config
You may verify that the echo command overwrote the file by using:
adb pull /data/property/persist.sys.usb.config ~/
and seeing the file's content in some text editor.
4. Unmount Data and reboot into Android OS. USB Debugging would probably be enabled.
-For Lollipop 5.0:
JB 4.2.1 users can also follow this method if the previous one didn't work for them.
1. Boot into Recovery and mount Data partition.
2. Repeat step 2 and 3 used in JB 4.2.1 method.
3. We need to tweak some parameters in settings.db. Type:
adb pull /data/data/com.android.providers.settings/databases/settings.db ~/
4. Back it up at some other location too, and open the file in an SQLITE editor. I'm running Linux and DB Browser for SQLite works well. It's also available for Windows OS/OSX.
5. In the global table, change the value for:
adb_enabled to 1
development_settings_enabled to 1
6. Check that verifier_verify_adb_installs is set to 1 in the global table.
7. Check that as default, in the secure table:
adb_notify is 1
adb_port is -1
These checks in step 6 and 7 are not necessary but should be done so that troubleshooting becomes rather easy if the solution doesn't work for you.
8. Save the changes in settings.db and copy it back into Android by typing:
adb shell
rm /data/data/com.android.providers.settings/databases/settings.db
exit
adb push ~/settings.db /data/data/com.android.providers.settings/databases/
That delete (rm) command is not necessary since adb push should overwrite the file, but I executed it for my peace of mind.
8. Unmount Data and reboot into Android OS. ADB probably would be enabled.
source:- https://android.stackexchange.com/questions/112040/how-to-enable-usb-debugging-in-android-if-forgotten-pattern-for-screen-unlock"
Please help me understand this code and be a life saver.
Thanks in advance..
You are stuck, I'm afraid. You won't be able to run any script on stock recovery, but you can't flash a custom recovery without unlocking the bootloader which will wipe your data.
What's more, your phone should be encrypted (if it's running 6.0 or higher), which means you'll need to know the pattern to decrypt after a reboot.
If you can't figure out the pattern, there's nothing you can really do.
jisoo said:
You are stuck, I'm afraid. You won't be able to run any script on stock recovery, but you can't flash a custom recovery without unlocking the bootloader which will wipe your data.
What's more, your phone should be encrypted (if it's running 6.0 or higher), which means you'll need to know the pattern to decrypt after a reboot.
If you can't figure out the pattern, there's nothing you can really do.
Click to expand...
Click to collapse
Is there any way I can create backup of the data in these conditions?
Dush123 said:
Is there any way I can create backup of the data in these conditions?
Click to expand...
Click to collapse
Unfortunately for you in this case, there isn't.
From a general security perspective, if there was it would mean the pattern lock and encryption can be bypassed, which would be very bad.
jisoo said:
Unfortunately for you in this case, there isn't.
From a general security perspective, if there was it would mean the pattern lock and encryption can be bypassed, which would be very bad.
Click to expand...
Click to collapse
Ohk. Then it seems I don't have any option but to hard reset my device.
Thanks anyways
HI! Is there anything I can do for my pattern locked Moto E4 Plus? Details I've posted in this thread.
https://forum.xda-developers.com/showthread.php?t=2620456&page=13