Early debug output - OnePlus 3 Questions & Answers

Is it possible to get some kind of UART or Serial port over USB at the start of the phone?
I want to dig into a issue where a ROM - under a specific circumstances - hard bricks my device (that means, no system, no recovery). However, it happens during a early boot stage. I only have a chance of finding the culprit when I have access to the (kernel) log. If Qualcomm devices have even more detailed logs (before the kernel is started?) I would like to read those to.
Mind that saving the log and reading it out doesn't work here... at the point I need to access it my device is already hard-bricked.
I read somewhere that QCSC devices have a USB UART / Serial mode, but I can't find any concrete information about it.
Would love to hear your thoughts about this.

Related

[Q] i747m (Bell) - Requesting Assistance

Alright, Apologies if this thread has been started in the wrong area - Just to get that off my chest lol.
I've recently made a serious mistake - noob mistake -
I had flashed the (DMG2) (I747 (AT&T)) from http://forum.xda-developers.com/showthread.php?t=2321310
Now, my phone is dead as a doorknob - Almost.
I thank you in advance for reading through this and ANY help is greatly appreciated
I've recently discovered that the device is recognized as:
Qualcomm HS-USB QDLoader 9008 (COM2;Can be changed)
Model: QHSUSB_DLOAD
I've been lurking the threads and found a very promising lead into wat may be a solution to my issue without JTAG'ing the device - Since the JTAG RIFF box, after research, my not support my model, the only option would be to replace the Mobo, though I coul be wrong on that.
I'm opt'ing to not send the device off to get JTAG'ed since I'm determined to find a solution...for now
OS - Windows 8
Firmware (Prior to Brick) - I747MVLDMF1
ROM: SlimRom - build.1.8-WEEKLY-1260 (Ver. 4.3)
My work so far:
- Phone will not boot into DL Mode/Recovery mode, red light (consistant) when plugged in without the battery; drops connection (w/out battery) after minute or so - with battery, the device stays connected through COM2
- USB Jig found not to work with this particular brick
- Odin does not detect (though it's using COM2) the device - I suspect this to be something to do with the DLOAD device recognition.
- Heimdall does not detect the device
- EFS: Recognizes device, cannot connect to it...
- 2nas does not detect the device
- Unified Root Tools is unable to connect to the device
- ADB (SDK Manager) - Nothing found relevant, so far - ADB doesn't connect.
- Roadkil SD Image Creater (SD boot Option) - Ironically, no i747m (Bell) Dumps located in this fourm
- UART drivers installed
- USBXpress: Still searching for potential leads
- QPST: The only viable option would be "Use Emerg. Host D/L" option under Multi-Image section in the Software Download Client - And after reading this http://www.anyclub.org/2012/05/qpst-emergency-download-support.html it burst that little bubble of mine.
I'm still searching http://www.anyclub.org/ but I wanted to see if anyone else might have located a ix for the issue - I was thingink on doing the Unbrickable mod from http://forum.xda-developers.com/showthread.php?t=1206216 but I'm kinda leary as to if that's such a good idea with my phone being in the state it's in - My question is whether or not the mod will create the opposite effect, the "non-unbrickable device"
The other idea, which I'm not to keen on either, is the possibility of forcing the phone to boot by soldering the boot leads on the Mobo -Using the MSM8960 BGA pin map showing the BOOT_CONFIG_x pads.- Source: http://forum.xda-developers.com/showthread.php?p=30781353
Again, Thank you for reading through this - Any help is GREATLY appreciated I've been up all night the past few nights trying to implement a fix for it - at this point I'm game for any testing software that may be out there to resurrect this dead body.

n910v, unrooted, usb debugging disabled, black screen, recover sms log over ADB?

I have hit dead end after dead end, after many hours, just want to get copy of text messages off this phone somehow, and then erase all data. I have spent many hours on this, my level of experience with all this is beginner/intermediate, as I'm sure you will be able to tell by the ramble below. Skip to the last paragraph **** with the asterisks to get to the important part of my inquiry. if you don't want to read about what I have tried already.
Before you suggest the obvious, replace lcd, let me say that the motherboard lcd connector is damaged beyond repair. water damage, but the phone boots normally and seems to run fine. phone calls ring and other sounds indicate the phone is able to function but no display or touch function obviously. the usb port works. Also there is no samsung account on the phone so that option to bypass screen lock does not help. Kies, smart switch, etc don't help due to the "screen lock"
ie... There is a basic swipe to unlock "lock" on the phone, so otg cable options also hit a dead end. There are workarounds to bypass other lockscreens, but no way to do the swipe over otg that I can find. And even if/once I am able to swipe to unlock over otg, there are other obstacles to get around that may not be possible (click ok, navigate to enable usb debugging). If I am wrong here and there is an obvious solution I am missing, let me know (explain in detail if you can) and I will get the hub & cable back out and try again!
Dr.phone android recovery (data recovery/damaged device option) looks like the most promising, and here I have also run into trouble. Dr phone will put the phone into download mode but then always seems to fail "flash recovery package failed" at some percentage. dr.phone downloads the recovery package (I am selecting the correct model n910v) successfully, but the percentage before flash recovery package fails changes. It hasn't made it past 85%. the dr.phone log files don't reveal anything to my untrained eye.
Before running dr.phone, adb "permission denied"...after using dr phone, however, while the phone is still powered on and in download mode, once I close dr phone, I am able to start to get somewhere with adb! adb devices shows the phone as an emulated device, and (some) adb commands start to work! I think if I just am able to find the exact location of the stock messaging log, I will be very close.
If anyone can suggest some commands to try in adb to grab just the sms log I would be very grateful!
I can run "adb backup", and have tried a few other adb commands, but none of the standard backup commands actually contain a sms log.
***Anyway, I think the best option might be to flash a custom recovery after getting the phone in download mode & adb working successfully (showing as an emulated device) with dr.phone as described above... However I have no way to tell what firmware version the phone is running (don't want to brick it or loose data), and I am really looking for specific directions on which clockworkmod or twrp recovery file to try for n910v, that will allow me to get a sms backup, and/or a recovery that will have usb debugging enabled.
Thanks for the input! sorry for the rambling post, I hope it's possible to make sense of it.. ANY help greatly appreciated!
beefriendly said:
I have hit dead end after dead end, after many hours, just want to get copy of text messages off this phone somehow, and then erase all data. I have spent many hours on this, my level of experience with all this is beginner/intermediate, as I'm sure you will be able to tell by the ramble below. Skip to the last paragraph **** with the asterisks to get to the important part of my inquiry. if you don't want to read about what I have tried already.
Before you suggest the obvious, replace lcd, let me say that the motherboard lcd connector is damaged beyond repair. water damage, but the phone boots normally and seems to run fine. phone calls ring and other sounds indicate the phone is able to function but no display or touch function obviously. the usb port works. Also there is no samsung account on the phone so that option to bypass screen lock does not help. Kies, smart switch, etc don't help due to the "screen lock"
ie... There is a basic swipe to unlock "lock" on the phone, so otg cable options also hit a dead end. There are workarounds to bypass other lockscreens, but no way to do the swipe over otg that I can find. And even if/once I am able to swipe to unlock over otg, there are other obstacles to get around that may not be possible (click ok, navigate to enable usb debugging). If I am wrong here and there is an obvious solution I am missing, let me know (explain in detail if you can) and I will get the hub & cable back out and try again!
Dr.phone android recovery (data recovery/damaged device option) looks like the most promising, and here I have also run into trouble. Dr phone will put the phone into download mode but then always seems to fail "flash recovery package failed" at some percentage. dr.phone downloads the recovery package (I am selecting the correct model n910v) successfully, but the percentage before flash recovery package fails changes. It hasn't made it past 85%. the dr.phone log files don't reveal anything to my untrained eye.
Before running dr.phone, adb "permission denied"...after using dr phone, however, while the phone is still powered on and in download mode, once I close dr phone, I am able to start to get somewhere with adb! adb devices shows the phone as an emulated device, and (some) adb commands start to work! I think if I just am able to find the exact location of the stock messaging log, I will be very close.
If anyone can suggest some commands to try in adb to grab just the sms log I would be very grateful!
I can run "adb backup", and have tried a few other adb commands, but none of the standard backup commands actually contain a sms log.
***Anyway, I think the best option might be to flash a custom recovery after getting the phone in download mode & adb working successfully (showing as an emulated device) with dr.phone as described above... However I have no way to tell what firmware version the phone is running (don't want to brick it or loose data), and I am really looking for specific directions on which clockworkmod or twrp recovery file to try for n910v, that will allow me to get a sms backup, and/or a recovery that will have usb debugging enabled.
Thanks for the input! sorry for the rambling post, I hope it's possible to make sense of it.. ANY help greatly appreciated!
Click to expand...
Click to collapse
This tool might work for you. Ive never used it myself but it looks promising. It supposed to be able to control your phone on your pc.
For the custom recovery, it should tell you what model you have when you boot into download mode but the TWRP for the note 4 has been unified so it should work either way. This link is for the most recent version. Get the .tar file if you're looking to use ODIN to install it.
Thanks for the reply! The tool you inked to requires USB debugging switched on. I was looking at it previously but didn't consider it because of this. I have USB debugging off, and the process I described with the dr phone windows application /download mode, doesn't turn usb debugging on.
Is there a way that I can flash a recovery for the note 4 that has USB debugging enabled from the start? If anyone knows please describe the process or post the link.
I think I need step by step instructions or screen shots for what to do with the Note 4 twrp recovery. I am trying to acquire a second phone so I can view the screen and know what buttons to press, but so far it is not looking like I have enough information to do sms backup from the twrp menus..on the device when I can't see the screen.
I see reference to being able to use adb commands to control the twrp recovery / backup process, but so far I haven't found anything that will help for my particular situation. If anyone knows what adb commands to use to pull the note 4 sms files , or a backup that includes them, PLEASE let me know.
thanks again

Locked bootloader, cannot OEM Unlock or access USB Debugging

Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.
Calgary84 said:
Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.
Click to expand...
Click to collapse
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!
tnsmani said:
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!
Click to expand...
Click to collapse
I was afraid of that..... is there a way to test a given hardware component?
Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM
acetone802000 said:
Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM
Click to expand...
Click to collapse
Indeed I have, dozens of times between the full and mini versions. I've even gone as far as running the toolkits featuring MSMDownloadTool v4.0 to see if it achieved different results (it did not). The mini tool would finish doing its thing (turned the text green upon completion),but I would face varying partitions not being flashed correctly. The full version completes and does not have these varying partitions missing, but the device would then be either stuck in a bootloop where it will eventually reboot itself, or would hang indefinitely on the "swirling dots" loading screen. I tried the remedy of deleting cache in recovery, but this did not help.
deleted
***UPDATE*** - As I mentioned in this thread earlier, I noticed a discrepancy between the variant type listed on my actual device and the variant type returned when queried via fastboot. This got me thinking, and to make a long story somewhat shorter, I found that while most stock Oxygen images I attempt to sideload onto the device fail (at precisely 47%, oddly), I was able to sideload two different Hydrogen images without any resistance at all. I'm guessing something to do with the eMMC vs UFS file storage systems and how each OS uses them.
So I got Hydrogen flashed onto my my device. Smooth sailing, right? Afraid not. Despite fastboot's output clearly stating it was a successful transfer, and the stock recovery on the device echoing this, I still cannot get the OS to load. Now i' stuck with the loading screen hanging indefinitely prior to animation occurring, so basically the static ONEPLUS logo. Factory resets and cache wipes have done nothing to help the situation along. Conventional wisdom from the threads here seem to say using the MSMTool is the right answer..... and thus the circle of frustration is complete with me arriving back where I started. Does anybody have another suggestion I can try out? Still can't flash/boot to TWRP, unlock bootloader, or access Android to activate USB Debug/OEM Unlock either btw.
Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?
voodooline said:
Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?
Click to expand...
Click to collapse
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.
150208 said:
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.
Click to expand...
Click to collapse
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.
voodooline said:
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.
Click to expand...
Click to collapse
Magnificent, bro.
You're a truly genius.

Qualcomm Diagnostic Mode code

To enter Diagnostic Mode dial:
Code:
*#*#25327337#*#*
In QPST phone is identified as "KOMORTA_H (0)" (I don't know what that means).
But I was able to do *.qcn and *.xqcn backup with correct IMEI numbers inside those files.
According to https://github.com/MiCode/Xiaomi_Kernel_OpenSource, kernel source for Redmi Note 9 4G/POCO M3 has a base tag of LA.UM.8.15.r1-06600-KAMORTA.0. This info might be related to what you have found.
Does this mean that qualcomm EDL mode works freely and that possible hard bricks can be fixed by the user himself or as other Xiaomi devices there is a need for authorization (which is never granted to the user)?
KaMyKaSii said:
Does this mean that qualcomm EDL mode works freely and that possible hard bricks can be fixed by the user himself or as other Xiaomi devices there is a need for authorization (which is never granted to the user)?
Click to expand...
Click to collapse
I don't think so. I only tested making a backup. I didn't try to write anything on the phone and I STRONGLY advise against that.
Ps: I'm new to Qualcomm ecosystem so take what I write with caution.

Redmi Note 8 locked, need help with unlocking/backup

Hello!
I need help regarding a Redmi Note 8 that no longer accepts the correct pattern and is locked.
I'm looking for a solution that would allow me to either unlock my phone without data loss, or make a backup of the phone's internal storage on an sd card/pc before hard resetting.
The device is not rooted and I don't have custom recovery installed. USB Debugging is on, but my laptop is not authorized.
With Adb, the device is detected but unauthorized. It seems to be detected normally in fastboot mode. I was able to get my laptop to detect it in recovery mode by clicking on "Connect with MIAssistant" while it was plugged in, but only in sideload mode. I also somehow managed to get into safe mode, but I used the stock screen lock, so unless there's something else that can be done in that mode, it doesn't seem useful in this situation.
I tried the actual MIAssistant software but it tells me to update my device before connecting. From what I found, this is because it doesn't even work with phones running Android 6.0 Marshmallow or above, so that seems to be a dead-end, unfortunately. Downloaded from here, updated to version 3.2.1.3111. If there's a newer version that could support my device, even an untranslated one, I would love to know, but I couldn't find a working one.
I had some ideas that could potentially solve my problem, but couldn't find a way to actually execute them, so here they are in case someone out there who knows more than me could help me with one of them.
1, Is there any way I could authorize my laptop for USB Debugging without being able to accept the prompt on screen?
2, Is there a way to make a backup of the internal storage of my phone in fastboot/sideload mode?
3, Is there a way to get adb to detect this device normally in recovery mode, instead of in sideload mode?
4, Is there a way to get my device into mtp/ptp mode instead of charging mode when connected to a PC without USB Debugging so I can copy my files?
5, Here's a thread I found that seems promising, although it's old. Could I somehow use this, or a similar method on Redmi Note 8? The Recovery Mode is much more limiting on this device, unfortunately, so I can't exactly follow this tutorial. Are there alternatives that can be done in adb fastboot/sideload mode, perhaps?
6, If I am forced to hard reset, is there any software out there that could recover at least some of the deleted data afterwards, or is everything lost in case of a reset?
I am open to new ideas not listed above, as well. I am not a very advanced user so I probably missed some things.
Thank you so much for any answer in advance!
zoey_96 said:
Hello!
I need help regarding a Redmi Note 8 that no longer accepts the correct pattern and is locked.
Click to expand...
Click to collapse
do you have the default recovery ? or a custom one ?
zoey_96 said:
Is there any way I could authorize my laptop for USB Debugging without being able to accept the prompt on screen?
Click to expand...
Click to collapse
No
loopypalm said:
do you have the default recovery ? or a custom one ?
Click to expand...
Click to collapse
Default, which doesn't have many options on Xiaomi. :/
loopypalm said:
No
Click to expand...
Click to collapse
Sad to hear that. Are there any alternative options that could solve my problem? I'd really rather not factory reset.
zoey_96 said:
Default, which doesn't have many options on Xiaomi. :/
Click to expand...
Click to collapse
if you had twrp or similar your problem would be solved ...
zoey_96 said:
Are there any alternative options that could solve my problem?
Click to expand...
Click to collapse
not as far as i know, ask in ADB thread if you find any
Updated with extra info in case anyone else has any ideas.
Even if you can copy your files to PC, they are problably unusable because of encryption.
That is why you need that pattern
For security this is exactly what you want, if your phone is lost or stolen.
Elinx said:
Even if you can copy your files to PC, they are problably unusable because of encryption.
That is why you need that pattern
For security this is exactly what you want, if your phone is lost or stolen.
Click to expand...
Click to collapse
Do you mean that the reason it doesn't accept the correct pattern anymore is for security? I would have thought it would still accept the correct one, at least after several tries of the same thing. Being completely locked out even when you know the correct password is a little strange to me.
zoey_96 said:
Hello!
I need help regarding a Redmi Note 8 that no longer accepts the correct pattern and is locked.
I'm looking for a solution that would allow me to either unlock my phone without data loss, or make a backup of the phone's internal storage on an sd card/pc before hard resetting.
The device is not rooted and I don't have custom recovery installed. USB Debugging is on, but my laptop is not authorized.
With Adb, the device is detected but unauthorized. It seems to be detected normally in fastboot mode. I was able to get my laptop to detect it in recovery mode by clicking on "Connect with MIAssistant" while it was plugged in, but only in sideload mode. I also somehow managed to get into safe mode, but I used the stock screen lock, so unless there's something else that can be done in that mode, it doesn't seem useful in this situation.
I tried the actual MIAssistant software but it tells me to update my device before connecting. From what I found, this is because it doesn't even work with phones running Android 6.0 Marshmallow or above, so that seems to be a dead-end, unfortunately. Downloaded from here, updated to version 3.2.1.3111. If there's a newer version that could support my device, even an untranslated one, I would love to know, but I couldn't find a working one.
I had some ideas that could potentially solve my problem, but couldn't find a way to actually execute them, so here they are in case someone out there who knows more than me could help me with one of them.
1, Is there any way I could authorize my laptop for USB Debugging without being able to accept the prompt on screen?
2, Is there a way to make a backup of the internal storage of my phone in fastboot/sideload mode?
3, Is there a way to get adb to detect this device normally in recovery mode, instead of in sideload mode?
4, Is there a way to get my device into mtp/ptp mode instead of charging mode when connected to a PC without USB Debugging so I can copy my files?
5, Here's a thread I found that seems promising, although it's old. Could I somehow use this, or a similar method on Redmi Note 8? The Recovery Mode is much more limiting on this device, unfortunately, so I can't exactly follow this tutorial. Are there alternatives that can be done in adb fastboot/sideload mode, perhaps?
6, If I am forced to hard reset, is there any software out there that could recover at least some of the deleted data afterwards, or is everything lost in case of a reset?
I am open to new ideas not listed above, as well. I am not a very advanced user so I probably missed some things.
Thank you so much for any answer in advance!
Click to expand...
Click to collapse
Howdy bro (I also have a Xiaomi Redmi Note 8).
I've been almost two intense weeks reading and watching the XDA forum, trying somehow and I did not find the way to unlock it .... Besides that I have the Bootloader disabled it makes me more difficult, because for that I need to format my phone and is what I do not want .... Already today is my last day of searching and I think I will have to leave my memories behind and Format my cell phone.
I leave you a thread of a user that explains well the process of why you can not:
A Comprehensive Guide to getting Past the Android Pattern Lock Screen
So, here's the situation I’m in. Also I am 99% sure I got something wrong so please tell me. I’m past the pattern lock screen so ADB won’t directly work to unlock the lock screen. If I was at a pattern lock screen, I could use ADB to unlock the...
forum.xda-developers.com
and several more of the many threads that I searched, maybe it will help someone:
[Xiaomi] How to unlock phone after forgetting the password.
Hello, today it happened that I forgot a password to my phone. I've tried to restore it by logging in into my xiaomi account and my google account. Unfortunately it only offers to wipe my data, which I want to avoid at all costs. I have Poco F2...
forum.xda-developers.com
[Android][Guide]Hacking And Bypassing Android Password/Pattern/Face/PI
- DISCLAIMER - This Is For Educational Purposes Only You Shall Not Use This On Other People Phones Without Permission Under Any Circumstances I'm Not Responsible For Any Eventual Errors And Misbehaving Of Your Devices Files And Tutorials Are...
forum.xda-developers.com
[Android][Guide]Hacking And Bypassing Android Password/Pattern/Face/PI
- DISCLAIMER - This Is For Educational Purposes Only You Shall Not Use This On Other People Phones Without Permission Under Any Circumstances I'm Not Responsible For Any Eventual Errors And Misbehaving Of Your Devices Files And Tutorials Are...
forum.xda-developers.com
[GUIDE] Unlock bootloader without losing user data.
Hi, I am writing this guide because many people followed other guides in the forum and lost their data. This is the proper way of unlocking the bootloader without losing your data. 0 - Read the whole guide before proceeding and proceed at your...
forum.xda-developers.com
[GUIDE] Redmi K20 Pro - Unlock & Root Information, Links, Tools and Instructions
Like many, I was overwhelmed with information when trying to unlock, flash, and root my phone. After many failures, I decided to compile the good information all in one place. I hope this helps. If it does, please consider buying me a beer...
forum.xda-developers.com
Recovery without data loss
Hi Community, you are my last salvation. I am owner of Pixel 4a 5g since half a year and now it cannot boot anymore. I see only the google-"G" and the loading bar nothing else. I can start the Boatloader but before i do a factory reset i need to...
forum.xda-developers.com

Categories

Resources