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...
Related
I have two identical nexus s phones.
Phone 1:
- has no usb connectivity, and thus can't be used with fastboot or adb
- unlocked bootloader
- stock jellybean
Phone 2:
- rooted
- has CWM 6.0.3.1 installed
- stock jellybean
I've taken a backup of phone 2 and want to flash it using the stock recovery on phone 1. I'm on OS X.
I've found a couple threads on this but they're all leading to dead ends. One used a utility called unyaffs, but the CWM file format has changed to use hashed blobs so that 's not going to work.
I've also seen a couple posts saying that CWM had a "soon to be released" option to create an update.zip file, but I don't see that option. Those posts are from last August. That sounds great if it existed and the image could be used with stock recovery.
All I really need to do is flash the bootloader from phone 2 on to phone 1 (I previously flashed the wrong bootloader on phone 1 which led to the loss of usb, which is what I'm trying to fix.) I tried zipping the correct bootloader image from the google download page and installing from stock recovery but it refuses to flash that image. (Not sure if fastboot images can be flashed in recovery mode?)
Argh, need a little help here.
Thanks in advance.
slide mon said:
I have two identical nexus s phones.
Phone 1:
- has no usb connectivity, and thus can't be used with fastboot or adb
- unlocked bootloader
- stock jellybean
Phone 2:
- rooted
- has CWM 6.0.3.1 installed
- stock jellybean
I've taken a backup of phone 2 and want to flash it using the stock recovery on phone 1. I'm on OS X.
I've found a couple threads on this but they're all leading to dead ends. One used a utility called unyaffs, but the CWM file format has changed to use hashed blobs so that 's not going to work.
I've also seen a couple posts saying that CWM had a "soon to be released" option to create an update.zip file, but I don't see that option. Those posts are from last August. That sounds great if it existed and the image could be used with stock recovery.
All I really need to do is flash the bootloader from phone 2 on to phone 1 (I previously flashed the wrong bootloader on phone 1 which led to the loss of usb, which is what I'm trying to fix.) I tried zipping the correct bootloader image from the google download page and installing from stock recovery but it refuses to flash that image. (Not sure if fastboot images can be flashed in recovery mode?)
Argh, need a little help here.
Thanks in advance.
Click to expand...
Click to collapse
ok your post isnt making sense. first of all how did you flash thethe wrong bootloader to phone 1? and when you compare the phones bootloaders, what is the bootloader version number for each one? so what youre saying is that phone 1 will never give you an adb connection at all, even when youre booted into android? when you plug phone 1 into the computer from within android what happens? and when you boot phone 1 into bootloader and execute fastboot mode then connect it to your computer do you see anything when you run the command ./fastboot devices? or ./adb devices when youre in adb mode on your phone? if your computer can see phone 2 and not phone 1 at all via usb then there is likely a problem with the usb port on your phone 1. you should be able to boot directly into fastboot mode by holding vol up and power button while powering on the phone, then it should take you straight to fastboot mode where you can then connect to the computer. remember to put the phone in fastboot mode then connect sometimes the computer wont see the phone if it was already plugged in upon entering fastboot mode/
haxin said:
ok your post isnt making sense. first of all how did you flash thethe wrong bootloader to phone 1? and when you compare the phones bootloaders, what is the bootloader version number for each one? so what youre saying is that phone 1 will never give you an adb connection at all, even when youre booted into android? when you plug phone 1 into the computer from within android what happens? and when you boot phone 1 into bootloader and execute fastboot mode then connect it to your computer do you see anything when you run the command ./fastboot devices? or ./adb devices when youre in adb mode on your phone? if your computer can see phone 2 and not phone 1 at all via usb then there is likely a problem with the usb port on your phone 1. you should be able to boot directly into fastboot mode by holding vol up and power button while powering on the phone, then it should take you straight to fastboot mode where you can then connect to the computer. remember to put the phone in fastboot mode then connect sometimes the computer wont see the phone if it was already plugged in upon entering fastboot mode/
Click to expand...
Click to collapse
I was trying to downgrade the phone to ICS using the factory image from google. I picked the wrong image from the google site (picked soju, needed sojus) and flashed it using fastboot. As soon as I flashed the wrong bootloader the USB connection stopped working so I didn't flash the radio or os. I no longer can connect to the phone using fastboot or adb, usb debugging stopped working. The USB debugging option is set in developer options. So, trying to get the phone working now without USB. Hope that makes sense now. :good:
My LG-E970 (AT&T) will not boot. What happened was FreeGee had an error part way though and I did not think anything of it. I had already successfully rooted my phone hours earlier and all seemed to be working well. I turned my phone off for the night and when I went to turn it back on it would not boot. It went into what it called "Demigod" mode, from which I can access Fastboot, but the recovery appears to be broken as well. I have tried accessing Fastboot to re-flash the recovery but neither Fastboot or ADB can even find the device. I've tried every USB driver I can find and nothing seems to help. Device Manager shows when it's connected under Unknown Devices and it names it Android, but ADB and Fastboot don't see it. All I can see on the Fastboot screen is the following information:
FASTBOOT MODE
PRODUCT_NAME - mako
VARIANT - mako 16GB
HW VERSION - rev_10 (168)
BOOTLOADER VERSION - MAKOZ10f
BROADBAND VERSION - N/A
CARRIER INFO - NONE
SERIAL NUMBER - 003fa9505095f3a5
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Any solutions would make me incredibly grateful. I have tried everything I can think of and I hate having to ask for help, but I see no other choice at this point.
fyrestorm90 said:
My LG-E970 (AT&T) will not boot. What happened was FreeGee had an error part way though and I did not think anything of it. I had already successfully rooted my phone hours earlier and all seemed to be working well. I turned my phone off for the night and when I went to turn it back on it would not boot. It went into what it called "Demigod" mode, from which I can access Fastboot, but the recovery appears to be broken as well. I have tried accessing Fastboot to re-flash the recovery but neither Fastboot or ADB can even find the device. I've tried every USB driver I can find and nothing seems to help. Device Manager shows when it's connected under Unknown Devices and it names it Android, but ADB and Fastboot don't see it. All I can see on the Fastboot screen is the following information:
FASTBOOT MODE
PRODUCT_NAME - mako
VARIANT - mako 16GB
HW VERSION - rev_10 (168)
BOOTLOADER VERSION - MAKOZ10f
BROADBAND VERSION - N/A
CARRIER INFO - NONE
SERIAL NUMBER - 003fa9505095f3a5
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Any solutions would make me incredibly grateful. I have tried everything I can think of and I hate having to ask for help, but I see no other choice at this point.
Click to expand...
Click to collapse
I hope you backed up your EFS. Mine was borked by the broken FreeGee that I ran the other night.
I was able to install a custom recovery from Linux by adding a udev rule and restarting the udev service. (Unlike Windows nonsense, this doesn't require a complete new packaging of the driver.)
If you're willing to tackle some Ubuntu (which is easy), I can give you a step-by-step to getting a custom recovery on your phone. It will probably work even from a live CD without even having to install Ubuntu to your harddrive.
Have you read and tried about the LGNPST method of flashing the TeenyBins and installing TWRP recovery ??
I think it should work , as I had the same issue as of today and with the help of those I was at least able to install TWRP recovery. Haven't tried flashing any ROM but I think it should work.
------------------------------------------------------;
http://forum.xda-developers.com/showthread.php?t=2230994
Please read it carefully.You'll find all the information in the thread , let me know if I can be of any help.
Here's my thread for the issue I had today , it seems similiar to your's.
http://forum.xda-developers.com/showthread.php?t=2557320
Hello
I think I've bricked my P760. When i want to run my phone it stuck on LG logo and can't boot to OS. Everything was fine but after installing fix to camera i could boot to OS my phone once and after reboot i can't boot to OS anymore. My phone has root, unlocked bootloader, custom recovery and custom ROM. I don't have acces to recovery. I have only acces to bootloader mode with fastboot (VOL+ + HOME + POWER). Then i have a note "Welcome to LG Fastboot Mode ". My computer detects it and automatically installs drivers (Fastboot interface (Google USB ID). But the problem is that in Device Manager it all time blinks. It's connected and immediately dissconects. I'm using original USB cable from LG charger. When i'm trying to use cmd in fastboot & adb files it's waiting for device all the time.
I don't know what I should do next :C
Pls help guys
SaRLaY said:
Hello
I think I've bricked my P760. When i want to run my phone it stuck on LG logo and can't boot to OS. Everything was fine but after installing fix to camera i could boot to OS my phone once and after reboot i can't boot to OS anymore. My phone has root, unlocked bootloader, custom recovery and custom ROM. I don't have acces to recovery. I have only acces to bootloader mode with fastboot (VOL+ + HOME + POWER). Then i have a note "Welcome to LG Fastboot Mode ". My computer detects it and automatically installs drivers (Fastboot interface (Google USB ID). But the problem is that in Device Manager it all time blinks. It's connected and immediately dissconects. I'm using original USB cable from LG charger. When i'm trying to use cmd in fastboot & adb files it's waiting for device all the time.
I don't know what I should do next :C
Pls help guys
Click to expand...
Click to collapse
I can help you. i just figured it out after walking away for a few weeks. pm me and ill tell you over google+ or skype and walk you through it.
i have same problem.
can someone solved it?
SaRLaY said:
Hello
I think I've bricked my P760. When i want to run my phone it stuck on LG logo and can't boot to OS. Everything was fine but after installing fix to camera i could boot to OS my phone once and after reboot i can't boot to OS anymore. My phone has root, unlocked bootloader, custom recovery and custom ROM. I don't have acces to recovery. I have only acces to bootloader mode with fastboot (VOL+ + HOME + POWER). Then i have a note "Welcome to LG Fastboot Mode ". My computer detects it and automatically installs drivers (Fastboot interface (Google USB ID). But the problem is that in Device Manager it all time blinks. It's connected and immediately dissconects. I'm using original USB cable from LG charger. When i'm trying to use cmd in fastboot & adb files it's waiting for device all the time.
I don't know what I should do next :C
Pls help guys
Click to expand...
Click to collapse
mirul_up said:
i have same problem.
can someone solved it?
Click to expand...
Click to collapse
pseudosane said:
I can help you. i just figured it out after walking away for a few weeks. pm me and ill tell you over google+ or skype and walk you through it.
Click to expand...
Click to collapse
Go through this thread http://forum.xda-developers.com/showthread.php?t=2292828 it will definitely solve your problem, from the screen-shot it seems that you are using windows 10, i'm not sure that omap4430 drivers will work on windows 10 or not, but you'll try otherwise do the process on windows 7, your phone will revive...
@Codeplex its to complicated thread.
before mine become like this my phone alway succes writing recovery via adb fastboot but now i try writing recovery via adb fastboot always filed.
flashing firmware with cmahendra method always get 15% error..
I think all dev not care anymore about our phone..,
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?
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