Database Develop

xperia Z1 crashed screen,forgotten pattern, and USB debugging OFF !!, HELP please!!

hello,
It's worst scenario I could imagine, My sisters Xperia Z1 dropped on street floor and crashed almost 70% of the screen,
touch is working on the remain area, she left the device for a while, and now she need some contacts, sms, pics from it, she forgot the pattern, and forgot the google mail associated !!.
I tried many ways described in many sites to remove the pattern without removing stored data, but the way ends at USB debugging OFF on the device,
please any one can lead my to how to unlock it ?
and in worst case if we can reset the device totally , how to do that? and can we use some app to recover data?
any help would be so appreciated.
thanks
A.H.A

engali555 said:
hello,
It's worst scenario I could imagine, My sisters Xperia Z1 dropped on street floor and crashed almost 70% of the screen,
touch is working on the remain area, she left the device for a while, and now she need some contacts, sms, pics from it, she forgot the pattern, and forgot the google mail associated !!.
I tried many ways described in many sites to remove the pattern without removing stored data, but the way ends at USB debugging OFF on the device,
please any one can lead my to how to unlock it ?
and in worst case if we can reset the device totally , how to do that? and can we use some app to recover data?
any help would be so appreciated.
thanks
A.H.A
Click to expand...
Click to collapse
If she has recovery, you should be able to start recovery and from there you can connect the phone to computer and have access to internal card. If there is no recovery and bootloader is unlocked, fastboot TWRP and do the same. If bootloader is locked, and there is a google account prompt, I doubt you'd be able to get to data. But google the options...

Hello,
I'm Afraid there is no recovery available ,
as I check about fastboot TWRP recovery, it needs first the device to be rooted and "Enabled USB debugging " ; means need the device to be opened and rooted and Enabled USB debugging !.
any idea please ?

unlock bootloader using fastboot mode via flashtool, then fastboot flash twrp.
then boot into recovery and attach your device to pc.
links that might help are below
twrp recovery
how to unlock bootloader
how to flash with adb fastboot

If you don't have anything particulary worth saving on it, then just flash a fresh rom with flashtool.

team_div said:
unlock bootloader using fastboot mode via flashtool, then fastboot flash twrp.
then boot into recovery and attach your device to pc.
links that might help are below
twrp recovery
how to unlock bootloader
how to flash with adb fastboot
Click to expand...
Click to collapse
IGnoTon said:
If you don't have anything particulary worth saving on it, then just flash a fresh rom with flashtool.
Click to expand...
Click to collapse
thanks for replies,
my first problem is FLASHTOOL which is "EMMA" , it dosn't work at all, it always says: "unable to connect to the network" , ... while I really have a network connection working fine !!.
what to do please?

engali555 said:
thanks for replies,
my first problem is FLASHTOOL which is "EMMA" , it dosn't work at all, it always says: "unable to connect to the network" , ... while I really have a network connection working fine !!.
what to do please?
Click to expand...
Click to collapse
ok, get this one:
http://www.flashtool.net/index.php
it works like a charm. And it has firmware downloader built in.

after unlocking the bootloader and installing TWRP, you want to delete the file password.key in /data/system/ using this:
forum.xda-developers.com/showthread.php?t=1646108
then it should be unlocked. good luck.

NEM-L21: Stucked with wrong version of boot.img, no more possibility of flashing

Hello everyone, it's my first time writing here, but I’ve tried everything, searched everywhere, and am desperate for help.
I screwed up big time while trying to flash a custom rom on my nem-l21, as I successfully did before with my xiaomi... So what I did:
I managed to unlock bootloader with dc unlocker. Then I got stucked flashing twrp with adb tools. Everything was looking to be fine, no error messages, “flashing successful”… But, I was never able to boot into flashed twrp. Always got stuck on “your phone has been unlocked blah blah. Your device is booting.” It never booted, not in twrp, nor in stock recovery. I tried different versions of twrp from different sources, always same result (flashing successful, booting into recovery not). Booting into the system was fine. And then I made that horrible mistake. Oh, how I wish I didn’t!!
I read on some website, that you are supposed to flash the twrp as boot.img, not as recovery.img. Seemed illogical and stupid to me, but in the end I tried it. Of course, this just bricked my phone, with no possibility to boot. After hours of googling, installing, trying and crying, I managed in the end to flash back stock boot.img. But at that time, I didn’t know my build number (b359), and I flashed boot.img b351. So now I have a phone which boots into the system b359 with boot.img b351, but with lot of errors.
- developer options, security options, display and factory reset option doesn’t work and just crashes. Therefore I am not able to flash the correct boot.img b359 or anything else at all from pc, no way to enable usb debugging and oem unlocking. Adb devices → nothing. I am able to use fastboot (fastboot devices sees the phone), but when try to flash something, I get error “command not allowed”. Also I can’t enable unknown sources installation, which bothers me a lot. And I can’t make factory reset to restore the crashing settings. Also I can’t change display timeout, and original 30 secs is super annoying.
- I am not able to uninstall even apps installed by me, always just restarts system UI and app stays.
What I tried so far:
- flashing correct boot.img from pc, not working because of dev options crashing
- go into recovery, but stock one is overwritten with unfunctioning twrp, always just get stuck on “your phone was unlocked blah blah… your device is booting now”, but it never does, have to hard reboot
- go into huawei erecovery, which is working, but when I try to resolve problem from there, always ends up with errors and crashes
- connect to pc and use HiSuite, system recovery tool here always says “no problem detected”
- updating to b361 through system update settings, always crashes on 5% and sends phone into “your phone was unlocked blah blah… your device is booting now” error
- downloading the proper b359 as and update.app file, put it in dload internal storage → same error during update, put it in dload sdcard → same error, no matter which way I use to start the update
- boot into twrp or stock recovery.img through fastboot without actually flashing it, anyway error “command not allowed”
- do factory reset or update through dial codes (i.e. *#*#123456#*#* …), nothing worked
My pc is windows 10, all drivers up to date. Using powershell as an admin. Am an idiot for not making backup of the phone before I started...
So, now I have more or less functioning phone, but I can’t uninstall any apps at all, can’t install from unknown sources, can’t do nothing from pc, can’t make any update, and lot of important settings keep crashing.
I can use the phone like this, but if somebody could think about some solution for this ****ed up situation I got myself into, I would be grateful to him/her for the rest of my life.
Sorry for a long post.
Thank you in advance and have a nice day

I think using Hisuit will help. Enter Fastboot and connect ur phone to ur computer and use system recovery toll

Xiao Mi A2 "Can't load Android system"

Hi Guys,
My phone suddenly stuck at this screen since may :
Android Recovery
Xiaomi/jasmine/jasmine_sprout
9/PKQ1.180904.001/V10.0.9.0.PDIMIXM
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data store on this device.
- Try again
- Factory data reset
If i press try again, sometime it will go to fastboot screen.
I can go into recovery mode here but i not sure which step i should do next.
Reboot system nowreboot to bootloader
apply update from ADB
apply update from sd CARD
wipe data/factory reset
Mount/sstem
view recovery logs
run graphics test
run locale test
power off
I'm not a very tech savvy person, i would really appreciate some help as i have data inside my phone which i need. So if possible i would like to retain the data.
I tried like EDL,fastboot,and flashing none seem to work. Of course I may be doing it wrong.
Can anyone guide me step by step I be happy to give an reward via paypal.

I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?

blazessdd said:
I'm so sorry bro.... 80% of times this means you lost your data.
Is the bootloader unlocked?
Click to expand...
Click to collapse
Thank you so much for replying.
Nope, but I can do EDL to unlock bootloader, I already disassemble the device a few times.
Just that every time I try to flash it , it give me some error. like Bluetooth error or the version error .
Which I watch thousand of video to work but it's doesn't help. Or maybe I just watched the wrong video

Ok tell me exactly what are you doing and where you have downloaded the rom.
If it's corrupted and you try to flash it you will lose the data... Was debug USB activated on developer settings?

My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:

epilifio said:
My device died too. After the October update, he never came back. It is looped on the home screen written "Android One".
I've tried several tutorials, it accesses the FastBoot screen, but when trying to use MI Flash appears a Bluetooth error and does not proceed.
I've tried using the adb flashing unlock_critical command, but it fails too.
He didn't have the bootloader unlocked, I now have a large paperweight.:crying:
Click to expand...
Click to collapse
You can try to short the edl points so you can flash the ROM again

blazessdd said:
You can try to short the edl points so you can flash the ROM again
Click to expand...
Click to collapse
I already made this attempt, "adb reboot edl" reports the message "error: '(null)' not found
Xiaomi never again

Xiaomi MI A2, is stuck in bootloop

Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.

Is it a Guide?
Oh, now, its a Great News!
Please delete this post from this forum.
As I have already wrote to you, questions should go to "Questions and Answers" forum.
And as I have already wrote to you, Search works here, and if you've used it, you'd get answers (in mentioned above forum):
1. MiA2 having A/B slots architecture, - is supposed to recover to the other slot X when OTA corrupts ROM is slot Y, - after numerous boot attempts.
2. In case you have tampered phone with try-and-see operations without knowing what you were doing - the only way to recover phone is: TEST Point / EDL. Search these keywords in this forum for appropriate Guide.

try the "fastboot continue" command

dillu12 said:
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Click to expand...
Click to collapse
you need to flash the phone in edl mode
**just be careful there is a timeout ..when you put it into edl you need miflash and rom.loaded
*** download a stock fastboot stable pie for jasmine
**** unzip amd select revelant xml from within miflash
*****on phone manually boot to fastboot mode with buttons
****** run command "fastboot oem.edl"
*******device will boot to black screen ... immediately go to miflash and press the button to start flashing
___BE CAREFUL__ select clear all tick box at bottom of miflash screen
this should be enough to rescue your device regardless of what you've done or whether you unlocked bootloader or not

Pixel 5 mdm lock

Hi, my friends pixel 5 is MDM locked and automatically resets every 2 hours. I already have unlocked bootloader and I'm trying to flash official factory image
( developers.google.com/android/images ) but fail (i have latest version of platform tools installed).
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
I'll attach image of that.
Tried flashing manually .\flash-all an using .bat file. Have done tons of research today but nothing.
Any ideas what can i do?

update
I flashed factory image successfully but it didn't help with mdm.

Is this a second hand phone or a company issued phone?
If it's second hand, probably best to ask the seller for refund or replacement.
If it's a company issued phone, may have to take it back to the company to unlock it.
I haven't dealt with MDM before so I'm not entirely sure. There may be tools to force disable MDM but not sure.

First, it sounds like you have a stolen phone.
You managed to flash without errors?
The phone is registered at the mdm server and the 2 hours is how long it is taking to reregister the device and then wipe it because it was flagged.
I am not sure how it was registered at the server. You could try installing lineage and see if still resets after a couple hours.
If so, since you have root. That means you have two hours after a reflash to find the mdm process and disable it.
Good luck, let us know if you find it.
*also found this to try after you reflash.
Go to Settings > Security > Device Admin Apps, and disable whatever is in there. I would do this after a clean flash, without enabling any sort of data connection.
You can also try to freeze or remove com.google.android.apps.work.oobconfig

HT123 said:
First, it sounds like you have a stolen phone.
You managed to flash without errors?
The phone is registered at the mdm server and the 2 hours is how long it is taking to reregister the device and then wipe it because it was flagged.
I am not sure how it was registered at the server. You could try installing lineage and see if still resets after a couple hours.
If so, since you have root. That means you have two hours after a reflash to find the mdm process and disable it.
Good luck, let us know if you find it.
*also found this to try after you reflash.
Go to Settings > Security > Device Admin Apps, and disable whatever is in there. I would do this after a clean flash, without enabling any sort of data connection.
You can also try to freeze or remove com.google.android.apps.work.oobconfig
Click to expand...
Click to collapse
It's second hand device which previously was purchased from eBay.
What i did is, i flashed android 11 and after activating without internet rebooted into bootloader & used this adb commands: adb shell; pm uninstall -k --user 0 com.google.android.apps.work.oobconfig .
It temporarily removes mdm, after reseting device problem still persists, but otherwise all good. Haven't tried rooting it and searching for mdm.

P.S.
11 seems like only android version on which it works

Normally, a MDM locked device is not bootloader unlockable; if the bootloader is indeed unlocked, performing a clean flash of Android with a full wipe should eliminate MDM entirely.
Just to be sure, boot into bootloader mode and post the output of fastboot flashing get_unlock_ability
Try using the Android Flash Tool. Make sure you check the Wipe device and Force flash all partitions boxes.

V0latyle said:
Normally, a MDM locked device is not bootloader unlockable; if the bootloader is indeed unlocked, performing a clean flash of Android with a full wipe should eliminate MDM entirely.
Just to be sure, boot into bootloader mode and post the output of fastboot flashing get_unlock_ability
Try using the Android Flash Tool. Make sure you check the Wipe device and Force flash all partitions boxes.
Click to expand...
Click to collapse
I've unlocked bootloader and flashed official factory image from there. I couldn't make Android flash tool work though, it begins downloading and at certain point stops it & starts again.

Absolutely nothing said:
I've unlocked bootloader and flashed official factory image from there. I couldn't make Android flash tool work though, it begins downloading and at certain point stops it & starts again.
Click to expand...
Click to collapse
USB debugging has to be enabled, and you have to have the ADB driver installed on your computer.

V0latyle said:
USB debugging has to be enabled, and you have to have the ADB driver installed on your computer.
Click to expand...
Click to collapse
Of course I had them, otherwise how could i unlocked bootloader and completely rewrite factory image. Haven't tried installing custom ROMs, my friend prefered not to play with it too much and just stick with android 11 solution.

Absolutely nothing said:
Of course I had them, otherwise how could i unlocked bootloader and completely rewrite factory image. Haven't tried installing custom ROMs, my friend prefered not to play with it too much and just stick with android 11 solution.
Click to expand...
Click to collapse
OEM Unlocking and USB debugging are separate. Both are enabled through Developer Options. USB Debugging is disabled after a data wipe.
If you're able to flash the factory image via ADB, try wiping both /system and /data using fastboot erase system (replace system with data for the data partition)
Using the Android Flash Tool is the most ideal option. I'm not sure where a MDM app/lock is installed on the device but I would think that completely reformatting it would be sufficient.
Does the MDM lock appear even if the device isn't connected to the Internet?

>Using the Android Flash Tool is the most ideal option.
What does the flash tool do that you can’t do from the command line?

HT123 said:
>Using the Android Flash Tool is the most ideal option.
What does the flash tool do that you can’t do from the command line?
Click to expand...
Click to collapse
As far as I know, nothing. The trick is knowing which commands, so if you have some way to look at the commands coming from the WebADB interface, that would help. I know some of the commands, but I don't know what is used for "force flash all partitions"
Edit: I missed a rather critical detail:
I forgot that only one process can use ADB at a time, so if you've used ADB from command line, you have to use adb kill-server for the Flash Tool to work.

>As far as I know, nothing. The trick is knowing which commands,
the commands for installing a stock image are in the extracted ROM zip in my experience. Usually in the flashfile.xml