Good evening,
So I wasn't aware of this DPI bootlooping issue until it happened to me today. I tried changing my DPI to 1000, since it worked to me before (not yet MIUI 11)
Here are some points to consider:
> USB debugging OFF
> bootloader LOCKED
>basically just stock pocophone f1 without any trace of modding.
>Mi Flash Unlock might unlock my bootloader, but I dont want to lose personal data. I tried logging in and my account has permissions to unlock. I only consider this as a last resort. (Is this feasible by the way?)
Here are some things I discovered
1. Using command prompt:
> fastboot devices - detects my phone
> adb devices - detects my phone if I select "Connect with MIAssistant" on stock recovery
> adb shell wm density -doesn't work (I think because bootloader is locked)
> fastboot flash recovery - doesn't work either(bootloader locked)
"adb devices" did not work at first. I tried doing it on fastboot to no avail.
But after some time exploring, "adb devices" worked when selecting "Connect to MIAssistant" on stock recovery
2. It actually is not "not booting", because I tried connecting a mouse using OTG when the loading circle appeared, then a very small mouse cursor appeared.
Here is a picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. What I can tell is, it actually boots but encounters a problem when trying to display with that DPI setting. Correct me if I am wrong with #2 and #3.
Is there any solution to this without wiping my personal data?
Edit1: My solution here: https://forum.xda-developers.com/poco-f1/how-to/pocophone-f1-flash-stock-rom-locked-t4084979
Issue Solved with flashing stock rom. I will edit the post with a link on a new thread on how I did it even with a locked bootrom and USB debugging OFF. I hope that new thread will help others in this same problem.
hii please help fast
i have same problem i also have bootloader unlocked
i tried command in adb "adb shell density reset"
but it shows error closed
please replay soon
Kunalkp123 said:
hii please help fast
i have same problem i also have bootloader unlocked
i tried command in adb "adb shell density reset"
but it shows error closed
please replay soon
Click to expand...
Click to collapse
you need to time it correctly, or use adb's wait for device command
Can I copy somehow the files from my dead phone to PC, using fastboot command? Maybe by EDL mode
Related
Hello everybody,
want to ask your advice in re: following issue
I am going to use nextbook NX868QW8G tablet as an embedded advertisement solution ie it should start when external power gets plugged in. I can find a normal tech desc of this model in the internet even on the official site.
It have almost the same look&hardware as NX785QC8G availabe at wallmart but have slightly another cpu mtk8382 and embedded 3g modem which was the decisive factor since we need tablets to be updated remotely.
Here are system settings:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have done the following:
1) rooted device via cydia impactor - root check apps from gplay are saying its rooted now + it has auto instaled chainfire SU to the tablet. For some reasons cydia impactor thinks its HTC ONE X. I have installed a PdaNetA4150 and it also considers it as HTC phone. I have tried to install drivers for nextbook8 I have found in internet but window doesnt recognize them as appropriate. At the moment device is recognized as unknown MT65XX Android phone
2) run adb reboot-bootloader
3) run fastboot oem unlock
4) run fastboot oem off-mode-charge 0
I have tried doing it manually and through cydia impactor but in both cases the command thread for #3 and #4 seems to be in an infinite sleep - just displays "..." in command line shell and cydia impactor simply gets frozen for a couple of minutes then throws timeout exception.
I think its waiting my input after #3 however the screen remains black and it does nothing when I press on vol up/down/power buttons. Fastboot prints "OK [X sec]" when I call fastboot reboot from another shell window.
In regards to the adb drivers and etc - device is visible through both 'adb devices' and 'fastboot devices' commands. For some reasons
Please advice in which direction to seach and digg.
Any help will be highly appreciated,
Max
Hello there,
my issue is that when i go in bootloader mode, i have a blackscreen, then my phone switch off. The system ui (custom rom Crdroid) and the recovery (orange fox) are working well.
I recognize also that when i reboot, i don't have anymore the MI logo where you have the status of your bootloader when it's unlocked.
More of it, when i plug it on windows , i cannot access to its usb storage (i tried also in mounting it through twrp, but same issue), nothing appears. For example, with an "adb devices" cmd command, no device can be found.
When i check the Windows devices manager, i can see an "unknown usb device" (i tried to force to reinstall drivers on it like the latest google usb driver, but windows refuse it, saying that it has the best and latest one for it).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Debugging mode is well enabled
Drivers have been reinstalled (the latest miflashtool install all what is needed)
Nothing appears on my smartphone when i plug it to windows (before i had a notification ot choose in charge mode, usb mode, etc...)
Plug to different usb port has been done without succeess
The phone doesn't appear in miflashtool obv
Restoring a previous backup didn't change the issue (i'm using the custom rom crdroid).
I guess all the things are linked but how i can fix it if i don't have access anymore to my bootloader mode to be able to flash some *.img via fastboot or if i cannot transfer files to my phone to operate in recovery, and more WHAT to do?
I hope you guys, will be able to help. The issue can be really annoying, and stuck me in "no rom update and no transfers of anything possible" situation.
Thank you beforehand
@bonbonboy
Try flashing the firmware through recovery from here https://androidfilehost.com/?fid=11410963190603850663 then reboot device and send it to bootloader via command adb reboot bootloader
It works like a charm!
Mi logo back, adb commands run, usb transfers work and no more error in the device manager.
You saved my day :good::good::good: Thanks a lot !
Hi,
my Pixel 4 got stuck booting on the G logo. I tried rebooting from recovery, but no luck.
I sidloaded Android 11 hoping that would fix it, but no luck.
So my option I guess it's to factory reset. But in order to avoid losing data, can anyone give me pointers to backup the phone?
The bootloader is unlocked, but not rooted. Developer settings were enabled and usb debugging should on by default.
From recovery adb devices sees an unknown device I cannot successful run backup commands on as the device is unauthorized.
Any help is appreciated
andreadoli96 said:
The bootloader is unlocked, but not rooted. Developer settings were enabled and usb debugging should on by default.
From recovery adb devices sees an unknown device I cannot successful run backup commands on as the device is unauthorized.
Click to expand...
Click to collapse
You can't establish a valid ADB connection because on phone the ADB RSA keys didn't get confirmed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's what the "unauthorized" ADB-message means.
FYI: When you click to always allow, Android appends the public key from ADB on the computer into a specific file ( /data/misc/adb/adb_keys ) on the phone.
jwoegerbauer said:
You can't establish a valid ADB connection because on phone the ADB RSA keys didn't get confirmed
That's what the "unauthorized" ADB-message means.
FYI: When you click to always allow, Android appends the public key from ADB on the computer into a specific file ( /data/misc/adb/adb_keys ) on the phone.
Click to expand...
Click to collapse
So considering that I can't turn the phone on to confirm that is there a workaround?
@andreadoli96
Don't know whether this will work or not
Code:
adb devices
adb push %USERPROFILE%\.android\adbkey.pub /data/misc/adb/adb_keys
adb reboot
adb devices
Good luck.
BTW:
Take note that if your Android version has encryption enabled out of the box ( there’s no way to remove encryption !!! ) then trying to backup the user-data ( will say pulling them out by means of ADB ) may work, but is senseless because you can't decrypt them.
Rase to wake not working.
Phone waking up even Rase to wake in off position
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It may be a bug. You can try to upgrade the system
红豆生南瓜 said:
It may be a bug. You can try to upgrade the system
Click to expand...
Click to collapse
Hi
It is up to date
Fixed.
Follow these steps:
1- Activate developers options on your phone.
For this you have to open Settings>About phone and tap on MIUI Version for about 7-10 time.
Now you go back to settings>adittional settings > Developer Options. Make sure you have USB Debugging and
USB Debugging(Security settings) are activated. For this last one i think you have to be logged in your MI account.
2- Install ADB(Android Debug Bridge) on your computer.
If you are on Windows, install ADB Universal drivers first.
Then download the ADB files.
3- Excecute commands.
Open a Command prompt (or shell) on the directory where you have the adb files.
Connect your phone with a USB cable. Change the USB mode to “file transfer".
In the Command Prompt window, enter the following command to launch the ADB daemon: adb devices.
You should get a prompt on your phone to allow (or deny) USB Debugging. Allow it and re enter on command prompt the "adb devices" command.
Now you should see your phone serial number. And you just have to enter the mentioned commands.
adb shell
settings put secure wake_gesture_enabled 0
exit (to exit adb shell)
And that`s all.
Screen turning on by itself.
When moving the redmi Note 9 the screen turns on by itself. I have disabled the "lift to activate" option, but the screen keeps turning on when moving. Someone can help me please? When the winds of change blow, some build walls, others build...
forum.xda-developers.com
Hello everyone!
This is my first post here so I hope everything I try to explain is according to the rules as far as I read it.
I need to root my Doogee S88 pro mobile since I need test and develop some AR stuff. The standard apps are not accesible by the playstore so I need to bypass that. For doing that I need to root my phone (this is what I read at least).
So... I installed the doggee usb drivers from their website for my phone, usb debugging is activated and OEM is activated as well. I downloaded the most recen platform tools and the usb-cable should be fine since I find the phone with
Code:
adb devices
I execute the following commands:
Code:
adb devices
adb reboot bootloader
fastboot devices
I get the small Fastboot text in the lower left corner. Then if I try to execute
Code:
fastboot flashing unlock
or
fastboot flashing unlock-critical
I only get back <waiting for device>
As said I installed the usb drivers provided by doogee. But: In the device manager I can see the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also I periodically (every 10 seconds) hear the sound as if a usb-device is disconnected. Afterwards the device manager refreshes the list.
So... it is a driver issue? I tried updating the drivers but picking manually the folder where driver files are located leads to no result. Automatic search as well. If it is a driver issue - where can I get the appropriate driver files? Thank you for any hint.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Unfortunately that didnt help either. Dunno... What I did was: I switched to my Lnux OS and over there it worked out of the box (only needed to install adb and fastboot from repositories).