Hi all,
my wifes phone was stuck in a bootloop at the MIUI logo (phone is full stock original, no changes at all).
All options with the buttons (rebbot,safe mode, wipe all data) did no work. Battery drain also not.
I tried to reboot via "Minimal ADB an Fastboot" and since then I get the message -> dm-verity curruption on the POCO Screen. If I press POWER within 5s, the message disappears and phone is stuck on the POCO screen forever, not even booting to the MIUI logo anymore.
I tried to flash the exact same version of the recovery ROM that is on the phone via MIFlashPro -> did not change anything.
Is there a solution to flash the original firmware to the phone? Like a "full reset"? I am able to enter the red FastBoot logo with the buttons.
Thanks for every help
Is the bootloader unlocked?
aricooperdavis said:
Is the bootloader unlocked?
Click to expand...
Click to collapse
They said “no changes at all”. Nobody unlocks bootloader for sh-ts and giggles.
rosicky88 said:
Hi all,
my wifes phone was stuck in a bootloop at the MIUI logo (phone is full stock original, no changes at all).
All options with the buttons (rebbot,safe mode, wipe all data) did no work. Battery drain also not.
I tried to reboot via "Minimal ADB an Fastboot" and since then I get the message -> dm-verity curruption on the POCO Screen. If I press POWER within 5s, the message disappears and phone is stuck on the POCO screen forever, not even booting to the MIUI logo anymore.
I tried to flash the exact same version of the recovery ROM that is on the phone via MIFlashPro -> did not change anything.
Is there a solution to flash the original firmware to the phone? Like a "full reset"? I am able to enter the red FastBoot logo with the buttons.
Thanks for every help
Click to expand...
Click to collapse
is usb debuging enabled?
Arealhooman said:
is usb debuging enabled?
Click to expand...
Click to collapse
They said “no changes at all”. Nobody enables usb debugging for sh-ts and giggles.
aricooperdavis said:
They said “no changes at all”. Nobody enables usb debugging for sh-ts and giggles.
Click to expand...
Click to collapse
Yes they do. I enable it as soon as I get any device. Multiple years before I rooted. Why wouldn’t I .
They're trying to flash stuff, so asking if the bootloader is unlocked is a reasonable question. But to answer your question, most users don't enable USB debugging. MIUI warns users that it's a bad idea, which is enough to put many people off, and this is sensible if you don't need to use it as it's a security risk (see this paper for some clear examples).
Fix for dm-verity error on Xiaomi devices · Issue #261 · bkerler/mtkclient
Hi, I've managed to fix the dm-verity error on the Redmi Note 10 Pro 5G/Poco X3 GT by simply rebooting into the bootloader and running fastboot oem cdms. After running this my device remains unlock...
github.com
Related
I know there is few hundered threads with "unbrick" in title but I read them all and nothing seems to work.
Friend brings me kenzo that he gets since his cousin brick it while trying OTA.
When I power phone its start to load system and it has 3 stages:
1. Show screen with "powered by Android" and 3 dots in the bottom, usualy about 4 min and restart
2. After restart just get black screen with Mi logo in the middle, for about 30 sec and restart
3. Instead of Android with dots bottom have white line progres bar, it takes 4 to 5 min and restart again.
After that stage 2 and 3 repeat for long as you have nervs to wait .
Phone can get in recovery and fastboot mode. And when I put him in test mode just show test screen and cant do anything.
In fastboot mode MiFlash recognize phone but report "device is locked" (try with 20160401 and 20160830).
After that i put him in EDL mode (fastboot reboot-edl) and MiFlash report successful flash. But nothing changes.
I try flashing global stable v8.0.5.0, china stable v8.0.4.0, global dev v6.10.13 and at the end global stable v7.2.5.0.
Any idea welcome. Thx
Have you tried to unlock bootloader? Perhaps install TWRP and do a system/dalvik/cache wipe and install MIUI through that?
banana_bender said:
Have you tried to unlock bootloader? Perhaps install TWRP and do a system/dalvik/cache wipe and install MIUI through that?
Click to expand...
Click to collapse
Cant do that. Even unofficial unlock need phone to be working to enable USB debbuging and accept RSA kay from PC.
Edit: Right now looking for ways to edit boot.img to unlock bootloader in attempt to get any useful recovery.
you can try this guide to flash twrp altogether with rom. after flashing, directly boot to twrp and move to custom rom
abihary said:
you can try this guide to flash twrp altogether with rom. after flashing, directly boot to twrp and move to custom rom
Click to expand...
Click to collapse
I will try... but dont think it will do the job. Will post result little later.
EDIT
It dose not work, just as I think.
All that kind of method/advice need 2 things:
1. Enabled USB debbuging - You cant do that on bricked phone even if you edit boot.img ( ro.debuggable=1 ) because fastboot will not execute command since you will not have option to accept RSA kay from PC on your phone and complete that action.
2. Dev ROM - since you have to enable OEM unlock and that option you have only in dev ROMs. Even Xiaomi official unlock requires that you must do it on dev ROM and that is a reason for "stuck on 50% in unlocking".
I try all that I can think: edit boot.img file, use patch emmc_appsboot.mbn, use edited flash_all.bat and rawprogram0.xml, insert sTWRP and ZCX TWRP in fastboot ROM... and all combination of that. Did it on 7.2.5.0 and 8.0.5.0 stable and 6.8.18 dev (since its last 5.1 ROM that I have).
Most of this attempts ends with "3 stages" explained in the first post. Some just show Mi logo for few sec and restart, once even power off phone. And once I even get phone to go directly to sideload/recovery state showing picture of the phone and usb cable.
Only thing left now is to find info is there difference in accessing to EDL mode between software (reboot-edl), deep flash cable and testpoint. IMHO there is none or little difference. Since software and deep flash can be troubled with bad USB cable or connector or USB board in phone.
Hello,
This morning I turned off and on my phone (RN5 Global).
Now, If I try to start it, phone goes directly to Mi-Recovery 3.0 and, no matter how hard you try to restart, it always ends there.
More info:
- The phone is completely from stock. No root, no bootloader unlock, nothing.
- Mi-Recovery only let me Wipe All Data, so this would be an unfeasible option without first having recovered the data.
- My PC Suite does not recognize the phone.
- If I connect the mobile to the pc, 'adb devices' command says "sideload".
- If I try to make a backup by 'adb shell' it says "error: closed".
- I do not know if 'debug usb' is activated. I remember i activated it in the past, but I think that MIUI10 update deactivated it again.
- I can enter fastboot mode.
- I tried to open the phone, disconnect and connect the battery, but nothing has been fixed.
What can I do? My priorities now are:
1.- Recover the data (at least photos).
2.- Revive my phone.
Thank you.
Found this on MIUI, what do you think?
http://en.miui.com/thread-2171064-1-1.html
CiDsTaR said:
Found this on MIUI, what do you think?
http://en.miui.com/thread-2171064-1-1.html
Click to expand...
Click to collapse
If your device is Redmi Note 5 from other country but India then it´s Whyred and this Forum is for Redmi 5 Plus/Redmi Note 5 (only India) that is Vince.
In the case I´m right and your device is Whyred (two rear cameras is a simple way to note it) then as far as I know you will need an EDL authorized account to flash a rom through MiFlash Tool.
Other tool that you can use is XiaomiFlash Tool by Francesco Tescari through Mi-Recovery but you will need too have enable USB debugging (maybe you have) but the same way you can flash a rom also you´ll lose all your data.
Adb shell works only in rooted devices, you can´t backup nothing in this state and fastboot mode is limited to just few commands like list device/reboot devices and nothing more in locked bootloaders.
In this scenario you have two things in order to solve this issue:
1- Highly probable loosing all your data.
- Doing format data through recovery and try to boot (data lost for sure)
- Flashing a rom through recovery with the mentioned tool (99% data lost probabilities)
- Flashing a rom through EDL; if you have Vince you can do it but if you have Whyred I don´t think so (if you choose second option "Flash without erase userdata" in MiFlash Tool I guess your data will be preserved)
2- If you enabled before USB debugging and binded your Mi account with device wait the time to unlock bootloader and maybe booting first of all in TWRP you can recover some data from your device, if you unlocked but first of all you boot on system for sure all your data will gone.
So what happened? Were you able to solve it? PLs share if you were...
I am also faced that situation.
When i tried to flash stock miui through fastboot it locked the bootloader and cant boot into rom then mi flash tool cant flash as boot loader is locked.
Worst part is in order flash another rom i need recovery, unable to reach developers option as rom not booting up.
Lost hope on the device
After all so many google searches and sleep less nights
I found application called mi pc suite china
Try to flash miui rom through mi pc suite mode
It says boot loader locked do you want to unlock
Finally it unlocked boot loader without booting into mobile.
In your case that will app will work. try it
gldvs007 said:
I am also faced that situation.
When i tried to flash stock miui through fastboot it locked the bootloader and cant boot into rom then mi flash tool cant flash as boot loader is locked.
Worst part is in order flash another rom i need recovery, unable to reach developers option as rom not booting up.
Lost hope on the device
After all so many google searches and sleep less nights
I found application called mi pc suite china
Try to flash miui rom through mi pc suite mode
It says boot loader locked do you want to unlock
Finally it unlocked boot loader without booting into mobile.
In your case that will app will work. try it
Click to expand...
Click to collapse
THANK YOU THIS HELPED ME OUT A LOT
I JUST INSTALLED THE APP THROUGH THIS LINK - https://miui.blog/any-devices/china-mi-pc-suite-english-translation/
AND THEN CONNECTED MY MI4i TO THE PC. IT AUTOMATICALLY ADDED THE STOCK REQUIRED FROM THE INTERNET AND I DIDNT CLICK ANYTHING IN THE APP.
RehanSiddiqui said:
THANK YOU THIS HELPED ME OUT A LOT
I JUST INSTALLED THE APP THROUGH THIS LINK - https://miui.blog/any-devices/china-mi-pc-suite-english-translation/
AND THEN CONNECTED MY MI4i TO THE PC. IT AUTOMATICALLY ADDED THE STOCK REQUIRED FROM THE INTERNET AND I DIDNT CLICK ANYTHING IN THE APP.
Click to expand...
Click to collapse
BIG THANKSS, THIS HELP ME TOO
In my case my Redmi Note 7 MIUI 11.xx and had a update notification
im accidenly hold my power button my, and ALWAYS go to MI-Recovery 3.0 after several reboot
Im downloading that app and updating that app,
And copy the translate file from China to English (my pc WINDOWS 10 64x)
i chose "Connect to Mi Assistant" in phone connect to my pc and open the app, that can see my current ROM (MIUI 11.xx) can be update to "MIUI 12.xx" ,im flashing(updating) with "LEFT" option
that say "CAN SAVE UR SEVERAL FILES" than option RIGHT(DELETE ALL FILES) i guess i dont much remember
Im flashing(updating) with hope my files still in there,
The app start downloading the ROM and instaling to my phone 0% to 100%
My phone reboot and had notify "The system has been destroy"
After restarting several time, Im lossing hope on my phone,
Im trying hold my -Volume button while rebooting, then my phone booting on MIUI 12 in several minute
And "EVERYTHING ITS FINE" i have my all files,app,photos, just like my regular phone but have new MIUI 12 update Introduce changelog
I just wanna share my experience
THANK YOU A LOT
Seeing this Stuck in Mi Recovery 3.0 with a stock device
Thanks Dude... It works for my MI Poco F1.
Steps
Download chinese version of mi app (version 3 beta) from below link
Replace English Translated mi_phone_assistant.res file in installation folder.
Connect Mobile with PC
Open the Mi App Then Click the update button which shows upon opening
Phone automatically came back to normal (No loss in Data) and Remove Cable. Don’t Flash Data.
China Mi PC Suite with English Translation | MIUI Blog
Mi app recovery will not work on older phones like vince i suggest flashing through test point by removing the back cover and reconnect both points
mccholai said:
Seeing this Stuck in Mi Recovery 3.0 with a stock device
Thanks Dude... It works for my MI Poco F1.
Steps
Download chinese version of mi app (version 3 beta) from below link
Replace English Translated mi_phone_assistant.res file in installation folder.
Connect Mobile with PC
Open the Mi App Then Click the update button which shows upon opening
Phone automatically came back to normal (No loss in Data) and Remove Cable. Don’t Flash Data.
China Mi PC Suite with English Translation | MIUI Blog
Click to expand...
Click to collapse
it stuck at 99%
CiDsTaR said:
Hello,
This morning I turned off and on my phone (RN5 Global).
Now, If I try to start it, phone goes directly to Mi-Recovery 3.0 and, no matter how hard you try to restart, it always ends there.
More info:
- The phone is completely from stock. No root, no bootloader unlock, nothing.
- Mi-Recovery only let me Wipe All Data, so this would be an unfeasible option without first having recovered the data.
- My PC Suite does not recognize the phone.
- If I connect the mobile to the pc, 'adb devices' command says "sideload".
- If I try to make a backup by 'adb shell' it says "error: closed".
- I do not know if 'debug usb' is activated. I remember i activated it in the past, but I think that MIUI10 update deactivated it again.
- I can enter fastboot mode.
- I tried to open the phone, disconnect and connect the battery, but nothing has been fixed.
What can I do? My priorities now are:
1.- Recover the data (at least photos).
2.- Revive my phone.
Thank you.
Click to expand...
Click to collapse
Just remove SD card & SIM tray from phone and restart. I work for me. try at our end. Don't flash or connect anything.
CiDsTaR said:
Hello,
This morning I turned off and on my phone (RN5 Global).
Now, If I try to start it, phone goes directly to Mi-Recovery 3.0 and, no matter how hard you try to restart, it always ends there.
More info:
- The phone is completely from stock. No root, no bootloader unlock, nothing.
- Mi-Recovery only let me Wipe All Data, so this would be an unfeasible option without first having recovered the data.
- My PC Suite does not recognize the phone.
- If I connect the mobile to the pc, 'adb devices' command says "sideload".
- If I try to make a backup by 'adb shell' it says "error: closed".
- I do not know if 'debug usb' is activated. I remember i activated it in the past, but I think that MIUI10 update deactivated it again.
- I can enter fastboot mode.
- I tried to open the phone, disconnect and connect the battery, but nothing has been fixed.
What can I do? My priorities now are:
1.- Recover the data (at least photos).
2.- Revive my phone.
Thank you.
Click to expand...
Click to collapse
how u solved your problem , i am stuck in same stage .. help please
I was stuck in Mi Recovery Mode 3.0 on my Mi Redmi Note 5.
Even after doing reboot to system, it wasn't going back to normal.
After scratching my head for a lot of time I decided to do the old school thing, i.e. REMOVING the SIM card and SD card and pressing the VOLUME DOWN + POWER KEY until the vibration occurred (NOTE: Mi logo will appear while you have pressed but keep the 2 buttons pressed until vibration occurred).
harsimran27 said:
I was stuck in Mi Recovery Mode 3.0 on my Mi Redmi Note 5.
Even after doing reboot to system, it wasn't going back to normal.
After scratching my head for a lot of time I decided to do the old school thing, i.e. REMOVING the SIM card and SD card and pressing the VOLUME DOWN + POWER KEY until the vibration occurred (NOTE: Mi logo will appear while you have pressed but keep the 2 buttons pressed until vibration occurred).
Click to expand...
Click to collapse
were any files deleted? and do you perhaps know if it would work on redmi note 7?
hello guys just look this video i solved it
Hi all,.
I also faced the same issue my redmi note 5 Pro which was on I believe MIUI 10 because it was never updated from the day it was purchased got stuck in bootloop and not getting ahead after recovery mode no matter how much time you reboot it was all working fine but some apps were updating such as youtube when this incident occurred I tried every solution like pressing keys pressing all three keys simultaneously or ADB method but none could work since the phone was locked also there was no USB debugging so adb method wouldn't work to also if an if ADB connected I couldn't flash because it will remove the data, in recovery mod you can see in option connect with MI Assistant but the Indian English version shown no connection so found one youtube video (channel name -" Ach Sharif ", video link-
which helped to install chinese version and and solved login issues I used Google translate translate to read the Chinese characters and understand what is going on I connected the device intending to take a backup backup but as no option was available I had to click on flash device so it downloaded upgraded recovery rom and automatically flash to MIUI 11 but still same problem then again I connected and upgraded to MIUI 12 and the phone was able to boot so the phone finally got fixed all data and all apps were intact and working as originally also all data of WhatsApp chats etc remained even the open apps at the time when problem happened were still present.
I believe guys this is the only solution to the problem because while flashing it replaces the recovery module of the rom which was corrupted earlier in my case when MIUi 12 installed not 11 I feel that it replaced recovery module due to update and it was able to work so please try once and I hope you get your files back, now lesson learned please do regular backups to live worry free life otherwise we will be spending time and energy here only.
I believe ADB methods or other methods won't work because they will flash and you won't be able to get data only flashing through recovery ROM not fastboot rom just like update package will be able to solve your problem if it is a software problem it will be can be fixed fixed this way only and saving data if it's a hardware problem such as power of all volume buttons are stucked you just get change and everything will be fine it happened in my other phone redmi Y2 so from speaking from experience thats all as I was going through trouble these things really help me so I thought to spend time in creating this guide please follow and I hope it will be solved.
You must open back cover( easily you can do it by hair dryer) and disconnect and connect again the battery, it will fix
Hi,
my Note 5 (which is standard with latest software updates) hangs on the Mi screen when starts up. I can get it into FASTBOOT mode.
And when I connect to PC/Windows 10 and go through adb and enter this:
fastboot devices
gives this result:
fcef713c0904
But I'm not sure what to do now? I guess I need to flash some sort of recovery but not being super tech savvy I'm a bit nervous.
thanks Phillip
@phil170258
Edit: fastboot is recognicing your device, as far I understood what you mean you tried to unroot it and gave you bootloop, flash the boot image that you are using lastly through fastboot and see what happens
SubwayChamp said:
@phil170258
Edit: fastboot is recognicing your device, as far I understood what you mean you tried to unroot it and gave you bootloop, flash the boot image that you are using lastly through fastboot and see what happens
Click to expand...
Click to collapse
Hi,
thanks for your reply.
I wasn't trying to do anything with my phone (root or unroot) when it started this behaviour so I don't have a boot image to flash? And my phone doesn't have 'usb debugging enabled' but because it won't turn on I can't enable it.
So i need to do 'fastboot flash recovery twrp.img' but when I do this it says cannot load twrp.img no such file or directory.
Aaaaaah!
thanks, Phil
phil170258 said:
Hi,
thanks for your reply.
I wasn't trying to do anything with my phone (root or unroot) when it started this behaviour so I don't have a boot image to flash? And my phone doesn't have 'usb debugging enabled' but because it won't turn on I can't enable it.
So i need to do 'fastboot flash recovery twrp.img' but when I do this it says cannot load twrp.img no such file or directory.
Aaaaaah!
thanks, Phil
Click to expand...
Click to collapse
Then try first going to recovery stock manually and wipe data and try to boot.
There are many users reporting this kind of issues along the time (updating firmware, charging all the night, etc) so the best is enabling USB debugging if something goes wrong you´ll have more options to save your device.
I guess you have your bootloader locked and also for this reason you can no longer use fastboot mode to flash some file.
If the first doesn´t result then your last resource would be to flash a rom through test point method (if you have Redmi 5 Plus-Vince)
SubwayChamp said:
Then try first going to recovery stock manually and wipe data and try to boot.
There are many users reporting this kind of issues along the time (updating firmware, charging all the night, etc) so the best is enabling USB debugging if something goes wrong you´ll have more options to save your device.
I guess you have your bootloader locked and also for this reason you can no longer use fastboot mode to flash some file.
If the first doesn´t result then your last resource would be to flash a rom through test point method (if you have Redmi 5 Plus-Vince)
Click to expand...
Click to collapse
Wipe data worked!
Thanks, and yes, i will enable USB debugging
thanks, Phil
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
UnequalB said:
Still very new to the community, so please bear with me if I miss something or make any mistakes.
Trying to flash havocOS
I flashed an unofficial version of twrp (for X657, made sure to disable verity on both vbmeta and vbmeta_system), then attempted to boot into twrp, with no luck (it just ended up booting into fastboot for some reason).
Click to expand...
Click to collapse
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
UnequalB said:
I then tried to boot into fastbootd, completely forgetting i had twrp still installed, to flash havoc from there (this is where i think i messed up, i remember reading somewhere that twrp prevents this)
Click to expand...
Click to collapse
You can flash the TWRP image through fastboot and then boot to it through commands.
UnequalB said:
Now my phone is stuck looping on the infinix logo
Tried the SP Flash Tool, but kept getting this error. Which I'm guessing is because the phone keeps restarting (mainly because "Disconnected!" shows up in the console between two instances of the same error).
Any advice?
Click to expand...
Click to collapse
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
SubwayChamp said:
Probably you haven´t to flash vbmeta to boot to TWRP but just when you are ready to boot to system.
You can flash the TWRP image through fastboot and then boot to it through commands.
Click to expand...
Click to collapse
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
SubwayChamp said:
This is the list of errors from SP Flash tool https://forum.hovatek.com/thread-439.html
Click to expand...
Click to collapse
Weirdly enough the error i got was not listed here..
SubwayChamp said:
Anyway, you have a tool specific for your device https://forum.hovatek.com/thread-9224.html
I guess this thread must be moved to Android General Questions.
Click to expand...
Click to collapse
This method doesn't work either since the phone won't stay off for more than 7 seconds.
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
UnequalB said:
I meant twrp prevents booting to fastbootd, it was after trying to boot into fastbootd using "fastboot reboot fastboot" that the bootloop started, right now I can't seem to get past the boot logo.
Click to expand...
Click to collapse
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
UnequalB said:
Weirdly enough the error i got was not listed here..
This method doesn't work either since the phone won't stay off for more than 7 seconds.
Click to expand...
Click to collapse
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
UnequalB said:
I'm not stuck in a bootloop as in the phone powers on, then gets stuck, or powers off again
The phone continuously powers on and off and nothing I do (apart from disconnecting the battery) stops it, even then, once the battery is back in it begins looping again...
Click to expand...
Click to collapse
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
SubwayChamp said:
You don't need to reboot to fastbootd, and you can't apply ADB commands either, because your device doesn't allow it due to random reboots and due to USB debugging is disabled right now.
Not true, this is the whole idea of this kind of tools either through SP Flash tool or Infinix tool you just have to GET device can be detected, this tiny portion of time will be enough for the tools can start its job, once the tool started the device get attached without a way to get out of it. To achieve this, prepare ALL that you need for tool to work even press flash/download, connect device with PC and apply the right combination key,
Prepare device manager on Windows and check which status of connection it is passing through to better understand which mode is lacking of.
You are not saying till now which model your device is, assuming that the bootloader is unlocked.
Click to expand...
Click to collapse
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
UnequalB said:
I tried again and that error seems to just be an issue with the linux version, it detected the phone fine and started writing to "super" on windows, but my laptop died, and now the phone isn't showing up on SP Flash, neither would it turn on at all.. but the charging indicator light comes on when I plug it in.
Click to expand...
Click to collapse
Well, if you interrupted the process, that's not good at all. The only you can do is keeping trying it, if your motherboard was not damaged.
hi guys i am DELTIERO from the Philippines did you allready solve the problem?
If not yet done message me on my facebook page https://www.facebook.com/del.villalobos.1/
and i will help you im here veltech san carlos negross occidental phil
Help please! I flashed a gapps zip file using flashify on my infinix smart 5 x657 (Running on lineageos gsi android 12) then the phone just went off. and it not turning on. but it shows the charging indicator light when i connect it to power.
I've tried disconnecting the battery still nothing
what possible solution is there for this?
Hello everybody,
I recently installed the Nokia X20 2022-08 update for Android 12 and rebooted my phone. Everything seemed fine, until I started to enter the PIN of my SIM card. After entering the 4th digit, the screen froze and nothing responded. I waited roughly 20 - 30 minutes, and the phone still did not respond. After that I gave my phone a reboot and it's been in a boot loop ever since hanging forever at the Nokia screen (it passes the Android One screen).
After a while, I rebooted my phone to the bootloader, unfortunately I do not have a recovery option (likely due to the fact that I've never enabled USB Debugging and Developer Options?) I only have the options:
- Reboot into bootloader
- Boot
- Power Off
- The command adb devices does not show the device while booting
- The command fastboot devices does not show the device while booting
- The command adb devices does not show the device in the bootloader
- The command fastboot devices does show the device in the bootloader
- Is there any way to get my phone into recovery mode in the current state?
- Is there any way I can get USB debugging enable, so that I can use adb (instead of just fastboot?)
- Is there a way that I can get the recovery option in the bootloader so that I can recover my phone?
Or is the situation hopeless and will I need to send in my phone for repair?
I've got the android-tools installed on my Linux machine?
Probably stupid question, but have you tried the keys: Power and Volume+ while powering up?
That should bring you into recovery mode as far as i know.
When I press the power and volume up it just keeps rebooting With the volume down combined it goes to the boot loader, but there's no recovery option there either.
Did you try to boot without any SIM card and SD card?
rtau said:
Did you try to boot without any SIM card and SD card?
Click to expand...
Click to collapse
Yes I did and did not resolve the issue.
nvaert1986 said:
Hello everybody,
I recently installed the Nokia X20 2022-08 update for Android 12 and rebooted my phone. Everything seemed fine, until I started to enter the PIN of my SIM card. After entering the 4th digit, the screen froze and nothing responded. I waited roughly 20 - 30 minutes, and the phone still did not respond. After that I gave my phone a reboot and it's been in a boot loop ever since hanging forever at the Nokia screen (it passes the Android One screen).
After a while, I rebooted my phone to the bootloader, unfortunately I do not have a recovery option (likely due to the fact that I've never enabled USB Debugging and Developer Options?) I only have the options:
- Reboot into bootloader
- Boot
- Power Off
- The command adb devices does not show the device while booting
- The command fastboot devices does not show the device while booting
- The command adb devices does not show the device in the bootloader
- The command fastboot devices does show the device in the bootloader
- Is there any way to get my phone into recovery mode in the current state?
- Is there any way I can get USB debugging enable, so that I can use adb (instead of just fastboot?)
- Is there a way that I can get the recovery option in the bootloader so that I can recover my phone?
Or is the situation hopeless and will I need to send in my phone for repair?
I've got the android-tools installed on my Linux machine?
Click to expand...
Click to collapse
YOU'RE OUT OF LUCK, IT'S EFFECTIVELY FULLY BRICKED UNLESS YOU BRING IT TO THEIR CUSTOMER SERVICE.
HMD's known for blocking people out of bootloader unlocking, and even if you beg them, they can't anyway (they released incomplete bootloaders for their retail units.) I'd say "call Hikari_Calyx" or something, but I don't think he can help with this issue.
nvaert1986 said:
Hello everybody,
I recently installed the Nokia X20 2022-08 update for Android 12 and rebooted my phone. Everything seemed fine, until I started to enter the PIN of my SIM card. After entering the 4th digit, the screen froze and nothing responded. I waited roughly 20 - 30 minutes, and the phone still did not respond. After that I gave my phone a reboot and it's been in a boot loop ever since hanging forever at the Nokia screen (it passes the Android One screen).
After a while, I rebooted my phone to the bootloader, unfortunately I do not have a recovery option (likely due to the fact that I've never enabled USB Debugging and Developer Options?) I only have the options:
- Reboot into bootloader
- Boot
- Power Off
- The command adb devices does not show the device while booting
- The command fastboot devices does not show the device while booting
- The command adb devices does not show the device in the bootloader
- The command fastboot devices does show the device in the bootloader
- Is there any way to get my phone into recovery mode in the current state?
- Is there any way I can get USB debugging enable, so that I can use adb (instead of just fastboot?)
- Is there a way that I can get the recovery option in the bootloader so that I can recover my phone?
Or is the situation hopeless and will I need to send in my phone for repair?
I've got the android-tools installed on my Linux machine?
Click to expand...
Click to collapse
Give it a try> Maybe this tool can help here
mvikrant97 said:
Give it a try> Maybe this tool can help here
Click to expand...
Click to collapse
is it really okay to use tools for a device on a whole different device though???
WilliamMike said:
Yeah! Its helpful whenever my phone got stuck or displaying black screen ..
Click to expand...
Click to collapse
what's your model, then? Those kinds of phones from Nokia/HMD are never able to enter fastboot/recovery mode though.
AltFantasy said:
is it really okay to use tools for a device on a whole different device though???
Click to expand...
Click to collapse
It is based on ADB commands you can use it
mvikrant97 said:
It is based on ADB commands you can use it
Click to expand...
Click to collapse
but I couldn't use ADB on my X10...