[HELP] Unbrick my Nokia 8! - Nokia 8 Questions & Answers

First sorry for my english.
My phone can only enter download mode now, the recovery mode has only "No command"
I've tried changing current slot to b but still the same, and now I can't change back to slot a
I've tried flash stock via NOST too, but it kept saying that battery voltage too low and my phone can't be charged either (I left the phone charging all night but when I discharged it for about 5 minutes, it turned off)
Pls help me :crying:

Appreciate any help... :"((

ghostwalkergamma said:
First sorry for my english.
My phone can only enter download mode now, the recovery mode has only "No command"
I've tried changing current slot to b but still the same, and now I can't change back to slot a
I've tried flash stock via NOST too, but it kept saying that battery voltage too low and my phone can't be charged either (I left the phone charging all night but when I discharged it for about 5 minutes, it turned off)
Pls help me :crying:
Click to expand...
Click to collapse
same problem as mine..... and bootloader is lock.

Related

Phone do not boot after Oreo update

As i installed update and clicked reboot to apply it, now my system do not boot. Phone always stuck on white NOKIA logo boot screen forever. I tried few times to restart it via VOL-UP + POWER, but it always have same result - never boots. Please give me advice how to deal with it
It happened to me too, in December already. Mobile is in service now.
They flashed original fw, tested and returned it with results no fault. Right after switch on and new Oreo update it starts to freeze and produce various mistakes again, so I have returned phone to service. Will complain with seller about exchange.
ravkhar said:
It happened to me too, in December already. Mobile is in service now.
They flashed original fw, tested and returned it with results no fault. Right after switch on and new Oreo update it starts to freeze and produce various mistakes again, so I have returned phone to service. Will complain with seller about exchange.
Click to expand...
Click to collapse
That really sucks. But what do you mean by various mistakes? Like your system boots, but some functionality is not working? As i said in my case it totally cannot boot and recovery mode i can't enter factory recovery mode by VOLUME UP + POWER on start.
gornex said:
That really sucks. But what do you mean by various mistakes? Like your system boots, but some functionality is not working? As i said in my case it totally cannot boot and recovery mode i can't enter factory recovery mode by VOLUME UP + POWER on start.
Click to expand...
Click to collapse
Ach yes, sorry. First it stucked in logo Nokia and rebooting again... VolumeUp+Power does not work normally on Nokia.
It helped procedure found here:
https://forum.xda-developers.com/showpost.php?p=74406267&postcount=34
Then I was able to make factory reset and mobile booted, but worked with various faults.
Did you unlock your bootloader , flashed TWRP and then changed the slot? Slot A to B or vice versa?
If so, then the solution is
How to solve!
I simply waited until the battery ran out
When battery was completely dead and no Nokia-logo appear any more >>
Then I charged the battery 3% juice without booting
and from there I entered recovery-mode with the help of a USB cable.
Holding the volume+ button while connecting the USB-cable
From TWRP-recovery I changed to the other inactive slot
and whooala, that's it!
Edit: I sucked the juice (mAh electric-capasity) out of the battery quicker with help of OTG-cable and an external USB-powerd fan.
Use almost any external max 5volt USB-powered devices available at home, even charging another phone unless the second phone doesn't reverse-charge, this Nokia can be used as a power-bank.

[HELP] Device Possibly HARD BRICKED

Hi all.
So yesterday, I flashed a modified version of the eRecovery and tried upgrading, but upon reboot my device goes into error mode and I think it might be hard bricked.
There's no fastboot. eRecovery, dload method doesn't work and I can't switch it off either because it always goes into error mode upon reboot. Luckily I've opened up my device and unplugged the battery to prevent it from draining.
Is there any hope of flashing back to stock? ANY help would be appreciated!
9bestenbier said:
Hi all.
So yesterday, I flashed a modified version of the eRecovery and tried upgrading, but upon reboot my device goes into error mode and I think it might be hard bricked.
There's no fastboot. eRecovery, dload method doesn't work and I can't switch it off either because it always goes into error mode upon reboot. Luckily I've opened up my device and unplugged the battery to prevent it from draining.
Is there any hope of flashing back to stock? ANY help would be appreciated!
Click to expand...
Click to collapse
Put the battery back in place and turn the phone on until battery drains. Then, connect it to the PC while pressing the volume button to access fastboot and reflash twrp. Good luck!
CarlosAG10 said:
Put the battery back in place and turn the phone on until battery drains. Then, connect it to the PC while pressing the volume button to access fastboot and reflash twrp. Good luck!
Click to expand...
Click to collapse
I've actually thought of that so I plugged the battery in again and switched on the phone and let it go into error mode. It'll probably take several hours for it to drain because it was around 60% before I bricked it. So I'll let it drain and see if something happens when I reconnect it. Hopefully it'll go to fastboot. If not, I'll probably have to save up for something new. But I'll try a few more times to see if I can unbrick my device.
9bestenbier said:
I've actually thought of that so I plugged the battery in again and switched on the phone and let it go into error mode. It'll probably take several hours for it to drain because it was around 60% before I bricked it. So I'll let it drain and see if something happens when I reconnect it. Hopefully it'll go to fastboot. If not, I'll probably have to save up for something new. But I'll try a few more times to see if I can unbrick my device.
Click to expand...
Click to collapse
Hi,
If your bootloader partition is safe, and that should be the case, then you will always be able to fix your phone. Just a matter of time/attempts.
Good luck ?

[HELP] Redmi 4x won't boot.

Hello,
my Redmi 4x won't boot. I tried to find some solution for this issue, but I can't find it anywhere, so I created this new thread to ask you for your help.
Last night I was out in the city and my phone died because of low battery, so after I came home I just wanted to charge it as usual. Battery logo showed up and it was behaving as always, but when I tried to turn it on it couldn't boot again.
After pressing the power button the splash screen flashes for a brief moment and then it just turn off again. This happens all the time from the moment my phone died. I'm not sure what went wrong here. I can't get it to recovery mode either. So I wanted to do a fresh start and flash it again with new ROM here (Ressurection Remix 6 is what I have now)
I'm able to get it on fastboot mode, but once I try to flash it with MiFlash I get error message like "error:FAILED (remote: Critical partition flashing is not allowed)"
So I looked up for a solution and I found that I need to get it in EDL mode with adb.exe
I tried this solution but with no luck. Phone is restarting but it won't turn on again and the fastboot mode is lost.
I'm not really sure if I have right drivers for it. Qualcomm HS-USB Diagnostics 900E is what I have now. I can't also change the usb debugging mode obviously, so I'm also trying to find some solution for this issue either (is there any chance how to turn it on with adb.exe?)
I think it's softbricked but i'm not really sure.
Thank you for your help
p3wp3w said:
Hello,
my Redmi 4x won't boot. I tried to find some solution for this issue, but I can't find it anywhere, so I created this new thread to ask you for your help.
Last night I was out in the city and my phone died because of low battery, so after I came home I just wanted to charge it as usual. Battery logo showed up and it was behaving as always, but when I tried to turn it on it couldn't boot again.
After pressing the power button the splash screen flashes for a brief moment and then it just turn off again. This happens all the time from the moment my phone died. I'm not sure what went wrong here. I can't get it to recovery mode either. So I wanted to do a fresh start and flash it again with new ROM here (Ressurection Remix 6 is what I have now)
I'm able to get it on fastboot mode, but once I try to flash it with MiFlash I get error message like "error:FAILED (remote: Critical partition flashing is not allowed)"
So I looked up for a solution and I found that I need to get it in EDL mode with adb.exe
I tried this solution but with no luck. Phone is restarting but it won't turn on again and the fastboot mode is lost.
I'm not really sure if I have right drivers for it. Qualcomm HS-USB Diagnostics 900E is what I have now. I can't also change the usb debugging mode obviously, so I'm also trying to find some solution for this issue either (is there any chance how to turn it on with adb.exe?)
I think it's softbricked but i'm not really sure.
Thank you for your help
Click to expand...
Click to collapse
Hi, most likely your battery is faulty. Current draw during Android kernel boot up phase is above 1A whereas only around 0.2A for a working OS, that's why neither OS nor recovery can start when the battery develops high ESR (internal resistance). Do the following test:
fully recharge the battery
do not disconnect the charger
turn it on
Your Android may now actually work again but you must use a short quality cable connected to a 2A+ charger, which will support the battery at boot time - and you can disconnect it later.
k23m said:
Hi, most likely your battery is faulty. Current draw during Android kernel boot up phase is above 1A whereas only around 0.2A for a working OS, that's why neither OS nor recovery can start when the battery develops high ESR (internal resistance). Do the following test:
fully recharge the battery
do not disconnect the charger
turn it on
Your Android may now actually work again but you must use a short quality cable connected to a 2A+ charger, which will support the battery at boot time - and you can disconnect it later.
Click to expand...
Click to collapse
Thank you, but the battery wasn't the main issue, because once I was able to flash it through EDL mode to the latest stable official ROM, the battery was on 93% already.
Now I'm stuck with MI logo and powered by android with 3 blinking dots above. I watched somewhere, that it could last for 7 minutes, but for me even the 15 minutes is not enough, so I guess i'm in bootloop.
For some reason my bootloader is locked again, even though I already made the unlocking process earlier before I flashed to Resurection remix 6. My phone doesn't even appear in device manager. I can't even use it as a storage, so I could try to flash it to custom ROM.
I'm not really sure wat happened and how is it possible to brick your phone by just draining your battery to 0%
Ok, phone is alive again. It booted up right after I inersted microSD card in slot. I didn't know this was necessary...

Bootloop and nonstop Restart Issue

Helllo,
My Mi A2 can't boot into the system it keeps restarting all the time. Even when I have tried go to fastboot mode, it goes it, but after several seconds it restarts, so I can'd do anything about it.
I have tried power+up, but "no command" error.
What can I do?
Is there any solution?
arshileus said:
Helllo,
My Mi A2 can't boot into the system it keeps restarting all the time. Even when I have tried go to fastboot mode, it goes it, but after several seconds it restarts, so I can'd do anything about it.
I have tried power+up, but "no command" error.
What can I do?
Is there any solution?
Click to expand...
Click to collapse
Open the phone with screwdriver and short the "test point" ...then when in edl flash the stock ROM ....and anyway after that ..in fastboot boot twrp and flash a zip from the global telegram group or my other posts to restore your persist
If after that your phone still fails to work it is a hardware problem causing this ....
Sent from my wayne using XDA Labs
KevMetal said:
Open the phone with screwdriver and short the "test point" ...then when in edl flash the stock ROM ....and anyway after that ..in fastboot boot twrp and flash a zip from the global telegram group or my other posts to restore your persist
If after that your phone still fails to work it is a hardware problem causing this ....
Sent from my wayne using XDA Labs
Click to expand...
Click to collapse
short the "test point" ...then when in edl flash
Can you share with me more details about it?
arshileus said:
short the "test point" ...then when in edl flash
Can you share with me more details about it?
Click to expand...
Click to collapse
It is a physical process not in software so just Google a video on YouTube so you can see the physical actions and copy it
Sent from my wayne using XDA Labs
Update:
I have replugged all the cables and while battery was drained I have turned it on again.
It worked!
I even make an update for android. But after some period of time, it started restarting and now I have the same loop.
I have unlocked the bootloader while it was working, but it doesn't help me right now at all.
Phone keeps restarting...
While it was working and charghing, some application was automatically opening and sensor started making some clicks.
When I had the same ecounter with other phones, it was battery fault.
What do you think guys?
I am also facing this issue. Sometime it reboots randomly but other times it works fine. Should I roll back to Android Pie?
arshileus said:
Update:
I have replugged all the cables and while battery was drained I have turned it on again.
It worked!
I even make an update for android. But after some period of time, it started restarting and now I have the same loop.
I have unlocked the bootloader while it was working, but it doesn't help me right now at all.
Phone keeps restarting...
While it was working and charghing, some application was automatically opening and sensor started making some clicks.
When I had the same ecounter with other phones, it was battery fault.
What do you think guys?
Click to expand...
Click to collapse
Hi! I am facing a similar issue: Suddenly my phone shut off. When I wanted to turn it on, it would shut itself off after ~3 seconds of the boot screen. If I plug it to charge, it would start rebooting every 3 seconds.
I have left it charging for a long time, and at a certain point it stops doing this and shows that it is fully charged. I have tried to unplug it and turn it on after this, but I am getting the same result. Once again, charged it, and tried to turn it on while connected. It turned on, but once I unplugged it (before unlocking it) it froze .
Recovery mode does not work (same result), but fastboot works. Unfortunately I can't flash it as I can't risk losing all my data.
Having said this, I want to know more details about what has worked for you. Did you drain the battery and then connected it to charge?
emee2k said:
Hi! I am facing a similar issue: Suddenly my phone shut off. When I wanted to turn it on, it would shut itself off after ~3 seconds of the boot screen. If I plug it to charge, it would start rebooting every 3 seconds.
I have left it charging for a long time, and at a certain point it stops doing this and shows that it is fully charged. I have tried to unplug it and turn it on after this, but I am getting the same result. Once again, charged it, and tried to turn it on while connected. It turned on, but once I unplugged it (before unlocking it) it froze .
Recovery mode does not work (same result), but fastboot works. Unfortunately I can't flash it as I can't risk losing all my data.
Having said this, I want to know more details about what has worked for you. Did you drain the battery and then connected it to charge?
Click to expand...
Click to collapse
same problem. i have gone to service center they are changing whole mother board and charging 500inr what to do?
Jeetesh00 said:
same problem. i have gone to service center they are changing whole mother board and charging 500inr what to do?
Click to expand...
Click to collapse
That seems quite cheap. It's up to you, I guess.
If you want to solve it yourself, you can give it a try to flash it in EDL mode. I have tried it with no success yet.

Question Redmi Note 10 Pro stuck in a boot loop

Today I left my phone in a cab and got it back in the evening. But after I got my phone it was stuck in a boot loop (after force restart - power button press and hold - it will go to battery icon and automatically restart after a few minutes and again goes to battery icon). Please see the video to understand the boot loop. Unfortunately, Developer options of the phone were not enabled.
Can boot to recovery but can boot to fastboot.
Can you please help me to boot my phone back to normal or sideload a ROM via adb.
tia
Was able to fix the issue. Followed below steps,
1. Kept phone until the battery fully drains
2. Plugged into the charger and charged the phone up to around 65% while the phone is switched off.
3. Switched on the phone when the cable is disconnected.
4. This time the phone was booted to recovery. No battery logo anymore
5. From recovery, rebooted the phone. But again it was booted to recovery.
6. Wiped all data and rebooted.
7. Phone was booted to MIUI os but had to set up the phone again from the beginning.
jayanath said:
Today I left my phone in a cab and got it back in the evening. But after I got my phone it was stuck in a boot loop (after force restart - power button press and hold - it will go to battery icon and automatically restart after a few minutes and again goes to battery icon). Please see the video to understand the boot loop. Unfortunately, Developer options of the phone were not enabled.
Can boot to recovery but can boot to fastboot.
Can you please help me to boot my phone back to normal or sideload a ROM via adb.
tia
Click to expand...
Click to collapse
Same problem bro, did u resolve it???
I think your battery is empty. Leave it on power for a while and check if its charging. Maybe the charginglevel is too low for booting up.
opg2000 said:
I think your battery is empty. Leave it on power for a while and check if its charging. Maybe the charginglevel is too low for booting up.
Click to expand...
Click to collapse
I hope it was that simple ..it seems probably like a bad update. My gfs phone did the similar today
The digitizer stopped working, I force reset the phone and boom ..recovery mode - Trying everything but it doesn't work. Wipe surely would work but she has pictures and videos so I'm trying to avoid that. Plug it to charging but she remembers it had like 75% of battery ...geez (hoping for a miracle)
EDIT: Probably this happen from the bad xiaomi update, anyway I did wipe the data and as expected it work without an issue, I'll unlock this phone and ditch MIUI (I mean I did it to my phone Xiaomi Mi Mix 2S from day 1 - I hate miui) ..now my gf has a reason to hate it too
A factory reset could be painful, since you would lose everything on the device. I saw a guy tap all over the back of the phone with two fingers, and boom! The Redmi Note 10 Pro boot normally! I tried it on a friend's phone, and it worked.
Hello,I had a kind of a similar thing.
I left my phone to charge and when I was back it seems to be stuck in a boot loop(MIUI14)
Well,I tried to force restart but the same.
Before I go to recovery mode,accidently,I putted the phone in fastboot mode.I restarted it in the try to go to recovery mode but the phone started normally.After boot,it's shows an update compete message,so te problem was from an android security path update whatever.
AlexfxDru said:
Hello,I had a kind of a similar thing.
I left my phone to charge and when I was back it seems to be stuck in a boot loop(MIUI14)
Well,I tried to force restart but the same.
Before I go to recovery mode,accidently,I putted the phone in fastboot mode.I restarted it in the try to go to recovery mode but the phone started normally.After boot,it's shows an update compete message,so te problem was from an android security path update whatever.
Click to expand...
Click to collapse
I have important apps on the phone and I wasnt thinking about a factory reset anyway but hopefully it worked in that way

Categories

Resources