My Xiaomi Mi 9T just fell and the screen now just flashes black and green. I'm sure that the phone is working but not so sure about the touch screen (can't see anything).
I wanted to access the screen from PC and recover my data but adb devices shows "unauthorized", and obviously I can't see the dialog box on the phone asking for adb authorization.
I already tried rebooting in recovery mode but trying to adb push the key to the device gives an error, and adb shell outputs "error: closed".
Installing a custom recovery afaik requires unlocked bootloader and unlocking it means losing all the data so that's not an option.
Am I 100% screwed or is there anything I didn't think of that could help?
e-ew--w said:
My Xiaomi Mi 9T just fell and the screen now just flashes black and green. I'm sure that the phone is working but not so sure about the touch screen (can't see anything).
I wanted to access the screen from PC and recover my data but adb devices shows "unauthorized", and obviously I can't see the dialog box on the phone asking for adb authorization.
I already tried rebooting in recovery mode but trying to adb push the key to the device gives an error, and adb shell outputs "error: closed".
Installing a custom recovery afaik requires unlocked bootloader and unlocking it means losing all the data so that's not an option.
Am I 100% screwed or is there anything I didn't think of that could help?
Click to expand...
Click to collapse
Unless you unauthorize adb from operating sytem you can't access it from recovery, unless you do adb sideload. One thing is that the screen doesn't display, an other that doesn't react to touches. Anyway adb backup will not backup everything. I recommend you to buy a counterfeit screen for $15 and replace it at least to power on and recover your data.
...
Related
Today i broke the screen of my moto g
I am with android 6.0, it has root, but I can not connect throught adb on my computer, it says this, when i do "adb shell":
error: device unauthorized. Please check the confirmation dialog on your device.
Click to expand...
Click to collapse
I would like to recovery my personal data, and to unlock my phone (to still continue to use with half of screen working)
pmj_pedro said:
Today i broke the screen of my moto g
I am with android 6.0, it has root, but I can not connect throught adb on my computer, it says this, when i do "adb shell":
I would like to recovery my personal data, and to unlock my phone (to still continue to use with half of screen working)
Click to expand...
Click to collapse
I was lucky and I entered on recovery mode and did:
adb pull -p /sdcard ./
Click to expand...
Click to collapse
and is now performing the backup
But how can I enter the pass of the sim card and deactivate the lock screen?
Solved
I deleted the keys through adb shell. This thread can be closed or delete
Hello,
My friend gave me his locked out phone AppTab Dual talk...( a company name unheard of) and asked me to unlock it for him. He doesn't know his account password. Now I tried booting into recovery or anything. I held power and vol down. Some stuff in Chinese came up. Image attached.
And language barrier apart, only vol down and up buttons work in that to scroll through the options . I've tried everything to try and select an option in that. But no luck!
If I hold down vol up and power buttons, something like a broken Android logo screen comes up which I believe is recovery mode for this device.
Then I plugged it on to my PC and installed the adb drivers for it.
adb devices --> I can see the device listed
Fastboot devices --> I can't see the device
adb reboot bootloader --> the stupid phone just reboots into actual rom instead of bootloader.
I tried to see if the bootloader is locked..now how do I unlock it? fastboot OEM unlock? Damn thing doesn't get recognised in fastboot.
I thought I'll enable USB debugging..which I believe isnt enabled.
So I searched online and came across this command.
adb pull /data/property/persist.sys.usb.config ~/
But the out put of this is either "error: no device" or "permission denied"
I don't know what to do. Here it doesn't go into bootloader. If I want to flash a custom recovery, fastboot commands ain't working, if fastboot shud work I shud enable USB debugging some how, and that too isn't working. If I hold down some random buttons also there is no bootloader mode or anything.
And the options which it gives and which I believe will have the factory reset option also doesn't work bcoz I can't select any option in that.
And yeah...I tried one more thing
adb shell recovery --wipe_data
Which also dint work
I tried
adb shell
Wipe /data
Wipe /system
Wipe /all
I also tried to side load one zip package which could disable the pattern lock
Bt that also dint work.
I tried adb USB and then adb side load <file>
Still no luck.
I might just recommend my friend to throw this phone into the water!
Thanks in advance
I've never heard of that device either and I couldn't find much information here. The adb commands that you tried won't work unless the phone's rooted. You can't access /system or /data or any other nested folders hence the "permission denied." It also looks like the bootloader isn't unlockable since adb reboot bootloader doesn't work. If you just need to unlock the phone you can check this thread but you need to have usb debugging enabled.
Art Vanderlay said:
I've never heard of that device either and I couldn't find much information here. The adb commands that you tried won't work unless the phone's rooted. You can't access /system or /data or any other nested folders hence the "permission denied." It also looks like the bootloader isn't unlockable since adb reboot bootloader doesn't work. If you just need to unlock the phone you can check this thread but you need to have usb debugging enabled.
Click to expand...
Click to collapse
Well, that still keeps me in the loop. I have to enable usb debugging & if i have to do that i have to root & so on.
Thanks for the reply. No luck with the thread you linked either.
I'm checking out my sister's phone that she dropped and broke the screen. Device boots up, since I can feel the vibration and hear alarms but the screen is dead. Debugging was not enabled, bone stock. I can see it in fastboot, but I'm not sure if there is a specific mode to be in to allow ADB for this device. I've read Downloader mode, which should be 3 spots below where Fastboot drops you, but I get no change. Anyone have a suggestion on how to pull the old data off?
Atemi1337 said:
I'm checking out my sister's phone that she dropped and broke the screen. Device boots up, since I can feel the vibration and hear alarms but the screen is dead. Debugging was not enabled, bone stock. I can see it in fastboot, but I'm not sure if there is a specific mode to be in to allow ADB for this device. I've read Downloader mode, which should be 3 spots below where Fastboot drops you, but I get no change. Anyone have a suggestion on how to pull the old data off?
Click to expand...
Click to collapse
You can only have adb connectivity when booted in the OS and usb debugging must be ON. You must also allow your computer RSA key from your phone at the first attempt to use adb.
adb can also be used form a custom recovery (even with debbug off) but if the phone was still stock it's bootloader is probably locked... Unlocking the bootloader will wipe data (and a working screen is also needed to unlock it).
At this point I think replacing the display would be the only option...
Sorry
alray said:
You can only have adb connectivity when booted in the OS and usb debugging must be ON. You must also allow your computer RSA key from your phone at the first attempt to use adb.
adb can also be used form a custom recovery (even with debbug off) but if the phone was still stock it's bootloader is probably locked... Unlocking the bootloader will wipe data (and a working screen is also needed to unlock it).
Sorry
Click to expand...
Click to collapse
Pretty much confirmed my thought. Thanks for the glance.
Hi, I have MI7 and after wiping data (noticed at show 2% complete and just returns, saying wipe was done, so maybe that is a sign of something) and rebooting it keeps saying that there was a factory reset and I need to enter password. I keep going into MI 3 Recovery and choosing MI Connect and trying ADB but `adb devices` simply lists a sideload entry and adb shell keeps returning error:closed. So `adb shell rm /data/system/gesture.key` doesn't work as it returns `error closed`. The MI PC Console tool doesn't detect the phone.
If I type `adb reboot-bootloader` my phone shows Fastboot but no menu. Just hangs at fastboot. `fastboot devices` returns a fastboot device.
So seems like there are some signs my phone is able to be communicated with, but none of the usual commands are helping me get anywhere...
Really not sure how to totally reset this device so I can start all over again. This factory reset loop just doesn't want to go away.
Any ideas how to get this phone to behave like it is brand new, regardless how technical?
thanks,
Brian
bhuether said:
Hi, I have MI7 and after wiping data (noticed at show 2% complete and just returns, saying wipe was done, so maybe that is a sign of something) and rebooting it keeps saying that there was a factory reset and I need to enter password. I keep going into MI 3 Recovery and choosing MI Connect and trying ADB but `adb devices` simply lists a sideload entry and adb shell keeps returning error:closed. So `adb shell rm /data/system/gesture.key` doesn't work as it returns `error closed`. The MI PC Console tool doesn't detect the phone.
If I type `adb reboot-bootloader` my phone shows Fastboot but no menu. Just hangs at fastboot. `fastboot devices` returns a fastboot device.
So seems like there are some signs my phone is able to be communicated with, but none of the usual commands are helping me get anywhere...
Really not sure how to totally reset this device so I can start all over again. This factory reset loop just doesn't want to go away.
Any ideas how to get this phone to behave like it is brand new, regardless how technical?
thanks,
Brian
Click to expand...
Click to collapse
Sounds like you are dealing with Factory Reset Protection(FRP). You need to look for methods to bypass FRP.
Sent from my SM-S767VL using Tapatalk
Hello. I wont lie.... im very frustrated. Its hard to find straight forward instructions.
I'm using linux ububtu. Ive also tried FWUL and mAid
Sdk tools installed, tried androud and google sdk
I have enabled oem unlock from the developer settings menu, along with usb debugging. file transfer mode is recognized as mtp.
I tried exalab's non-root busybox for some functions. Superuser x from k shark apps. I get bad system call.
I can only adb sideload and adb shell from pc. i cannot access anything else!
The most annoying part? When the sideload fails, it takes me into recovery mode, but adb doesnt work there!!! I have options like erase cache, reboot to bootloader, and mount /system (which mounts) but useless because i cant adb pull the build.prop file to change ro.secure 1 , ro.adb.secure 1, and ro.flash.locked 1.
Through getprop, i found the oem key but fastboot doesnt recognize anything at all.
I inspected the init.rc file Just to try and understand.
Adb setprop doesnt work.
How do i allow adb in recovery mode, or modify these syrstem properties? yes, manually and the ultra hard way. Even though im annoyed about it i want and love to learn.
edit: power, vol + and - at boot brings up a white screen saying 'device information' with the imei and s/n #'s with barcodes.
power with vol - to reboot, then at logo: release power and hold again : brings up factory reset screen with yes/no option (not recovery screen).
I cant figure anything else out
I opened up 2 androids now and i notice some pins, maybe for a debug mode? Forced bootloader ?
oliverbell760 said:
Hello. I wont lie.... im very frustrated. Its hard to find straight forward instructions.
I'm using linux ububtu. Ive also tried FWUL and mAid
Sdk tools installed, tried androud and google sdk
I have enabled oem unlock from the developer settings menu, along with usb debugging. file transfer mode is recognized as mtp.
I tried exalab's non-root busybox for some functions. Superuser x from k shark apps. I get bad system call.
I can only adb sideload and adb shell from pc. i cannot access anything else!
The most annoying part? When the sideload fails, it takes me into recovery mode, but adb doesnt work there!!! I have options like erase cache, reboot to bootloader, and mount /system (which mounts) but useless because i cant adb pull the build.prop file to change ro.secure 1 , ro.adb.secure 1, and ro.flash.locked 1.
Through getprop, i found the oem key but fastboot doesnt recognize anything at all.
I inspected the init.rc file Just to try and understand.
Adb setprop doesnt work.
How do i allow adb in recovery mode, or modify these syrstem properties? yes, manually and the ultra hard way. Even though im annoyed about it i want and love to learn.
edit: power, vol + and - at boot brings up a white screen saying 'device information' with the imei and s/n #'s with barcodes.
power with vol - to reboot, then at logo: release power and hold again : brings up factory reset screen with yes/no option (not recovery screen).
I cant figure anything else out
I opened up 2 androids now and i notice some pins, maybe for a debug mode? Forced bootloader ?
Click to expand...
Click to collapse
Can you help me root my lg journey the same way you did pls ?
You can't fix it the LG L322L CAN NOT be unbootlocked or rooted especially StraightTalk, tracphone or t-moble phones. ANYONE WHO CLAIMS THEY CAN OR HAVE IS A BOLD FACE LIAR!
IF YOU visit lg's website the K30 LG L322L is NOT on the list of devices that can be unlocked they have been houndreds of people tried in the last 4 years and not one has successfully done so
It's sounds like you soft bricked it and their is not a fix for it.. sorry but best of luck!
MountainMan42 said:
You can't fix it the LG L322L CAN NOT be unbootlocked or rooted especially StraightTalk, tracphone or t-moble phones. ANYONE WHO CLAIMS THEY CAN OR HAVE IS A BOLD FACE LIAR!
IF YOU visit lg's website the K30 LG L322L is NOT on the list of devices that can be unlocked they have been houndreds of people tried in the last 4 years and not one has successfully done so
It's sounds like you soft bricked it and their is not a fix for it.. sorry but best of luck!
Click to expand...
Click to collapse
Ah, I see.
I didnt mean the phone doesnt work, actually, it works just fine....my bad. just the adb/fastboot/root attempts didnt work.
if only i could modify those system service variables somehow. .. or even access the /system after mount?
getting access to adb via recovery? i had thoughts that if adb isnt shown via recovery, it isnt implemented there but can be done...
i havent tried since, been playing with my solder tools xd.
oliverbell760 said:
Ah, I see.
I didnt mean the phone doesnt work, actually, it works just fine....my bad. just the adb/fastboot/root attempts didnt work.
if only i could modify those system service variables somehow. .. or even access the /system after mount?
getting access to adb via recovery? i had thoughts that if adb isnt shown via recovery, it isnt implemented there but can be done...
i havent tried since, been playing with my solder tools xd.
Click to expand...
Click to collapse
oliverbell760: Do you STILL have the LG Journey phone??
I just came across your post here , while investigating this secon-hand phone ,the lgl322dl . I picked it up right after my LAST economy LG phone lgl355dl ,2022 model running Android 10 slipped into a bootloop.
I have found some very interesting "root-like" methods of running Linux distros "natively" along side of Android.
Please get in touch with me if you care to
expand on your 19-month old concern.
Also reach me at [email protected]