I have a Xiaomi Redmi Note 4X, which I started using around March. Lately, I have been facing an issue which has left me troubled a lot. My Note 4X seems to be in a bootloop.
Around two weeks ago, I was casually using my phone in college. I had put around 25 apps on download from Google playstore. Alongside, whatsapp was running. I usually take pics of my lectures, so when the teacher had written on the board, and was about to erase, I quickly attempted to go to the home screen, by clicking the home button ( middle button), so I could launch the camera app, and take the pic. But, the phone didn't go to the home screen, and stayed at the app being used. However clicking on the recent apps (the left button), the two running apps showed. However, as I didn't have much time, I did what came in my mind. Reboot the phone. Unfortunately, as soon as it booted back, the screen remained black.
Its been like this for two weeks now. Whenever I turn it on, It will show the Mi logo, then the Android logo simultaneously below it ( Like usual when it boots), but after that, the screen goes black. Touching the three buttons at the bottom of the phone make the back-lit underneath light up along with a vibration(Like usual). Clicking the touchscreen gives a vibration. If a sim card is put inside, and a call made to the inserted sim card's phone number, the phone starts ringing as usual, however, still with a black screen. Another major issue I experience other than the black screen, is that the top right of the phone becomes really really hot as time progresses( within minutes)(This never happened before), and the battery drains really fast too. I get freaked out because of this( I think it might explode or catch fire), so I quickly turn off the device, after some tinkering.
I have been trying to find a solution since the past two weeks. Hard pressing the Volume Up+ Start button takes me into MiRecovery 3.0, which offers 3 options, 1.Reboot, 2. Wipe Data, 3. Connect To MiSuite. Going into 2 gives the option " Wipe All data" only, and 3 is seemingly useless the MiSuite doesn't support new versions of Android. Hard pressing the Volume Down+Start button takes me to FastBoot. It should be noted, that in both MiRecovery 3.0, and Fastboot, the phone doesn't warm up really fast, as it does when booted normally, and rather remains cool even if left for quite sometime in these modes (approx 30 minutes atleast).
The main thing I'm trying to achieve is to backup the data on my phone, mainly the photos (lecture notes), and whatsapp data. The rest of the app-data isn't that much important, albeit if also savable, it would be a bonus.
I haven't tried flashing any ROMs, recovery, or anything else, as I'm afraid the data may be erased, and as I have never done anything like this before. Also, my phone isn't rooted, as I didn't feel the need for it to be.
Help is highly appreciated. I hope to be able to safely extract my data, and be able to start using my phone again.
Thanks to advance to all those who reply.
Guys?
:/
Try Redmi NOTE 4X forum.
I Have the same problem,
I Have the same problem, did you solve the issue?
Related
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
efan3719 said:
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
Click to expand...
Click to collapse
I had a similar situation where I was toggling my nexus 4s brightness settings and when you have it at the darkest setting it is pitch black. Like there's no light on at all. I just had to hit the spot that I did before and bring the light settings back up. So maybe you can boot it up unlock it on the blank screen and two finger pull down and try pressing the light toggle?
apollohay said:
I had a similar situation where I was toggling my nexus 4s brightness settings and when you have it at the darkest setting it is pitch black. Like there's no light on at all. I just had to hit the spot that I did before and bring the light settings back up. So maybe you can boot it up unlock it on the blank screen and two finger pull down and try pressing the light toggle?
Click to expand...
Click to collapse
it was at ten percent brightness and the screen was completely unresponsive as far as i could tell. doing the power + volume up press made it reboot and return to normal.
efan3719 said:
Left my phone plugged in over night like a I always do. Woke up today and tried to turn the screen on but there was nothing. It wouldn't come on. Pressed the power button over and over but nothing. Tried a three finger reboot. Felt it vibrate signalling it rebooted. Still no screen.
Removed my bumper case to make sure I was pressing the button all the way down. Was able to get the little vibrate signal that the power menu prompt popped up but still no screen. Held the power button for 30 seconds. Still nothing.
Finally held down power button + volume up and the device rebooted and the boot animation came up. Screen works fine again.
So I guess the point of this post is to let people know my sets in case the encounter this problem. Hopefully it works for you as well and you don't have to send your device back.
Click to expand...
Click to collapse
Mine did that once too. Exact same thing happened. I was starting to get the feeling in my stomach where my phone had just died and then I hit a random set of buttons and saw the Google logo appear. Must be a software bug.
kingwaffle said:
Mine did that once too. Exact same thing happened. I was starting to get the feeling in my stomach where my phone had just died and then I hit a random set of buttons and saw the Google logo appear. Must be a software bug.
Click to expand...
Click to collapse
exactly the same here. felt like i had dropped a baby on it's head haha. i wish i knew a way to figure out what caused it.
My wife and I have been having the same issue, and I'm surprised that there's not more reports of this behavior The worst part is that I use my phone as an alarm, and the alarm won't go off if this happens in the night.
It has happened to me 3 times now, and 2 times in one day for my wife. Holding down the power button for ~20 seconds will cause the reboot, which is the good news. This morning after holding down the power button I noticed the notification light flashing red.
The phone appears to be still on, because if it happens overnight I will still see the white notification light flashing even though the screen won't turn on.
I had this problem on faux123 kernel on the second day after I got my Nexus 4.
Doesn't encounter it on franco.Kernel...
Sleep of death brozillas! Happens to all android phones. Happened to all my phones listed in my signature. You can reboot the device and you should be good. For the dude that's missing his alarm you should do a factory reset if you are stock or if you have root do not set your min cpu values to less than 3xx MHz.
Sent from my Nexus 4 using xda app-developers app
Same thing happened to me on my N4. Did a hard reboot and it came back on. Has happened at least twice since then, usually after being plugged in.
Sent from my Nexus 10 using XDA Premium HD app
Change chargers, cables. Make sure the charger is 5v 1.2a. Factory reset to stock.
If all that fails, RMA if you can.
Sent from my Nexus 4 using xda
I observed the same issue (going to standby, then cannot switch on within an hour) with my [just bought] Nexus 4 (latest 4.2.2 firmware OTA updated, nothing special in setup, second day of use).
Certainly must be difficult to say if it's hardware of software (that is, JB/drivers, since I cannot see how such issue can be caused by any virtual machine application) and when/if the latter will be fixed. I have another such great device already -- ASUS TF700 transformer, with similar "everything works, just reboots occasionally", which I think is enough for me
As with the ASUS Transformer case, I have trouble understanding: if it's the issue with all devices/firmware, although not too frequent -- then why everybody does not complain/return the units massively: the phone is pretty unusable if it cannot be relied upon. If it's just some isolated cases with particular units -- then what happened to QA/testing at LG...
So I guess I am going to return it while I can.
Too bad, good model otherwise, will have to see other phones or wait/observe.
My point is, I understand: fairly new device, can have quite a few faults to be fixed later -- now everybody seem to work that way, for better or worse.
It can have more or less beautiful (or ugly) designs, more or less features, larger or smaller batteries/working time; it can have problems with data connectivity, it can have better or worse browser (or the lack thereof completely). I'm fine with the lack of text reflow in Chrome although that was surprising.
One thing a phone/communicator/PDA absolutely cannot do, provided its battery is not empty, is going into "sleep of death"-like states -- it just cannot serve its purpose then, I cannot see how people sell it at all...
I have had a similar issue before, but i have experienced it when my phone has been through one of 2 sets of scenarios.
1 - It gets really warm and the screen becomes unresponsive, dead if you will. The hard reboot fixes this.
2 - When the signal to my phone is sporadic. An example of this would be my recent trip to London. I was on the underground quite a lot, and I'd lose signal quite often whilst travelling. On a couple of occasions i had to reboot my phone the hard way to get it going again.
Hope this helps?
In my case the device was lying near me on the sofa, the time between its going to standby and my attempt to switch it on was something within 1 hour. Nothing especially intensive had been done before.
BTW, while the phone was in that state, trying to call it resulted in long tones, i.e., apparently the radio/cell was online.
Hope this will help somebody, I returned mine.
Good evening. First post but long time lurker. My N4 is unrooted and on 4.2.2. I'm troubled with this as well especially so when the alarm doesn't ring in the morning after it's crashed overnight and I'm late for work!
Not sure if this is relevant though. I don't listen to music frequently on my N4 but the 3 times it had crashed overnight I had been listening to music before going to bed. Twice using Google music being streamed via my home wifi and once using poweramp with music on internal memory. I remember on 2 occasions the phone feeling rather hot as I was plugging the charger in as I was about to turn in.
I suspect there's a process that's causing the the phone to overload/ overheat and then switch off as a result. Because it's plugged in, it'll just continue to charge overnight and present you with a 100% battery in the morning once you've got it to reset again.
I have also found that doing a soft reset before going to bed prevents this from happening.
Just my observations.
Hi all, I got my Nexus 4 a week ago to replace a broken HTC One X (The cost of repairs was almost equal to the cost of a new Nexus 4). Since I got it, SoD happened twice, both times when I left it to charge overnight. The weird thing is that I have this LED application that blinks the notification light when charging with screen off. When I unplugged the phone, the LED was still blinking as if charging, so the phone is definitely not dead. I will try to set it to day-dream while charging and see if it helps. If it does, it might be considered a way of Google encouraging developers (like myself) to create more daydream apps .
Good morning from beyond the pond,
had the same thing happening as described in the first post solution (pressing POWER+VOL UP) helped to reboot my device.
Only thing that was showing was the led, flashing a blueish white light.
Now runs again on rasbeanjelly. Thanks to OP.
EDIT: since this happened the first time, I thought about what I had altered in my setup.
Only thing that was new was "Greenify". Maybe it sent the APEX launcher into standby?!
Having same problem on my 1 week older n4, my friend having the same problem . only thing in commune we have is the WHATSAPP app that once the phone restart it give a notification that the phone date is wrong,once I look at the date settings yes it is wrong, it says 1970 ,so I have to reset it. It does it every time the problem happens ,can this be a clue???
Sent from my Nexus 7 using xda app-developers app
guinnes.s said:
it says 1970
Click to expand...
Click to collapse
UNIX equivalent of Pol Pot's year zero
I'm having similar problems.
The first time I believe it was just an issue of slight overheating. I turned off the screen but left Google Maps running & put it in my bag. It didn't actually turn off, but the screen didn't want to come on when I took it out later. I did notice it was hot, and after it cooled for a couple mins, it worked fine again. I haven't done this again, and so far, so good.
However, now, on occasion the phone won't respond to the power button. I've never had to actually do a reset - it will eventually decide to work after a couple of presses.. but when it does, it will be slow to come on. The screen will be backlit (but black) for a few seconds, then it will load and respond as normal.
Since the light comes on prior to the screen, it seems like a software rather than hardware issue to me. If the screen was damaged, I don't think it would act that way. I don't know phones, but that's my intuition. I'm going to try and remember to turn it off on occasion and see if that helps. I don't think it's been reset since the last push update.
(I'm rooted, but stock)
Hello, I have my moto G 2014 for about 2 weeks now (full stock, never even connected it to the PC). A few days ago sometimes when I lock my phone by pressing the power button the touchscreen becomes unresponsive. The side buttons both work but nothing happens as I tap the screen, I can't unlock it or shut down. Then, out of nowhere it starts to work briefly, and I can shutdown only, not unlock.
But this time it rebooted and remained unresponsive, I can input 2 of the pin numbers and then it goes unresponsive... RMA?
Thank you
This dont look like a problem before..... You seem to be the first one with this problem. Have you ever dropped your phone? Or installed something wierd? Can you also tell what you did before when this problem came?
The phone is imaculated, never droped it. The first signs were after I installed Swiftkey, the key to change between numbers and symbols was not responding. Now sometimes the screen is all unresponsive, other times the top bar can be accessed, other times the menu keys don't work. I did a factory reset, after much struggle to get to the Config. menu, rebooted to the same issue.
Mebseven said:
I did a factory reset, after much struggle to get to the Config. menu, rebooted to the same issue.
Click to expand...
Click to collapse
I wouldn't loose to much time, trying to hunt down the problem. Sounds like the digitizer is broken. Unless you use your phone only while connected to the charger. Most chargers will emit a low electrical field that makes it almost impossible to operate the touchscreen. If this is not the case, replace the device.
It's not connected to anything right now, the top bar and 3 menu buttons are working but the rest is dead, can't swipe the screen or select any app, not even the app drawer. I guess it's RMA time.
Yea seems like a good idea, its a great device. I hope your warranty is still working
I have a Note 8 that i have never dropped, had this phone since release haven't rooted. However it is running one of the early Oreo Beta builds CQLB the phone is on Sprint. This has happened once before about 2 months ago and i can almost guarantee it happened in the same fashion as the most recent time a few days ago. It seems while receiving a call i go to reach in my pocket and hit several buttons pulling it out (because of the bulky case) then my screen goes completely black.
(This is where it starts to sound like the normal black screen issue that there are a thousand YouTube videos for)
The phone still makes noises for notifications, rings when calling and other noises like emails and low battery alarm. The screen however doesn't display anything whatsoever and has a blue led blinking.
(This is where it differs)
I've done every button combination i can think of with no avail.
-The regular restart button combination Vol Up + Power and hold for 7-10 secs,
-I've tried to boot into Recovery mode by guessing at what time the Samsung logo should be on the screen and pressing the vol button down several times
-I've tried to boot into safe mode by pressing the Bixby button, power and Vol Up and without the screen displaying anything i can of course not see if i was in Recovery or not.
The screen doesn't display a Samsung Logo, No sprint splash screen NOTHING. The last time this only lasted for about 3 hours and it suddenly came back up when being on the charger and restarted several times. This is now day 3 and after dozens of restarts nothing has worked, on or off the charger. I mentioned the Oreo build because maybe it's linked to that? i haven't had this issue on regular Nougat. ANY help is appreciated and thanks in advance
Try turning off Always on Display. It worked for me..
Actually your problem seems different, so doubt it will work
..
WizP said:
Try turning off Always on Display. It worked for me..
Actually your problem seems different, so doubt it will work
Click to expand...
Click to collapse
nope, i cant get anything to show on the screen at all
winol said:
How did you get an Oreo firmware?
Click to expand...
Click to collapse
By flashing the Oreo beta builds via Odin etc..
go back to a stable build.
bober10113 said:
go back to a stable build.
Click to expand...
Click to collapse
Kinda hard to do without anything displaying on the screen whatsoever, anyway i mailed it off yesterday for repair from Samsung. It was either that or a 2 hour drive to 12 Mile (Detroit) to bring it to the Ubreakifix store.
Unfortunately Sprint doesn't offer loner phones and can't activate any phone that is non sprint outside of some iPhones which sound a bit strange but now I'm out a phone for 9-11 days :silly:
Have you solved this issue? I have the same issue with my phone. It started happening to me even when I was on Nougat. Happens to me several times already. It goes black screen for about an hour to 3 hours then randomly get back to normal (get notification sounds, can receive call, etc). I am now on Oreo. Everything is stock. Never rooted my device as well.
Tried to bring to Samsung but all they did is 'Software Update' the device which is basically reinstalling the firmware and wipe everything. Service Center sucks and doesn't want to claim it is a defective unit.
My note 8 began experiencing this yesterday and after some frustrations and work around, I managed to pinpoint the issue.
Work around was go unlock phone and drag down taskbar, then click on systems and the system interface would open, after which I could press buttons on lower part of phone and clearscfeen to get back to homepage.
Problem was with Google. In my case I realised when I opened Google maps, the screen went black, so I went into applications and cleared the Google cache and Google maps cache. No 0roblems since.
Is it something with Snapdragon?
My wife Nokia 7 Plus was found in download mode (white screen with Android One logo) and is stuck in this mode. I've never done any unlock bootloader or root or anything on it (thus I did on other phones so I'm not totally stranger to it) and I'm 100% sure she didn't tried anything strange either. The phone is completely stock and probably with the last update as it went back new from repair a few months ago (for screen brightness issue) and I did update everything possible before she used it again.
The phone start automatically and immediately I see the white screen with AndroidOne logo and after a few ms it refresh and it's the same screen with the back text "Download mode" at the top.
I've tried to force shutdown and reboot by long pressing power. I cannot keep it shutdown, it goes back to Download Mode screen.
I've tried to restart start with power + vol up or power + vol down, power + vol up + vol down. Same.
I've tried to let it die on battery, charge it, and here it's a black screen with the large battery logo and a white text at the top saying: Download mode. After a few minute I try to boot and it's back to the white screen.
What can I tried next before I send it back for repair and it will be probably wiped again...
Side story, I've almost force her to switch from iPhone to Android because of price of the devices, and so far she is not converted at all with all the trouble we got with this Nokia.
As last before send to service try wipe in recovery, if not boot to recovery via buttons, try if your download mode is recognised by fastboot and reboot to recovery using: fastboot reboot AND IMMEDIATELY HOLD BUTTONS POWER and VOLUP until show "green android icon with no command
k3dar7 said:
As last before send to service try wipe in recovery, if not boot to recovery via buttons, try if your download mode is recognised by fastboot and reboot to recovery using: fastboot reboot AND IMMEDIATELY HOLD BUTTONS POWER and VOLUP until show "green android icon with no command
Click to expand...
Click to collapse
Thanks for your help, unfortunately none of this work. I've tried adb device and nothing is seen, fastboot reboot neither. I'll send it to repair now.
Suffering the same problem.
Eluc said:
My wife Nokia 7 Plus was found in download mode (white screen with Android One logo) and is stuck in this mode. I've never done any unlock bootloader or root or anything on it (thus I did on other phones so I'm not totally stranger to it) and I'm 100% sure she didn't tried anything strange either. The phone is completely stock and probably with the last update as it went back new from repair a few months ago (for screen brightness issue) and I did update everything possible before she used it again.
The phone start automatically and immediately I see the white screen with AndroidOne logo and after a few ms it refresh and it's the same screen with the back text "Download mode" at the top.
I've tried to force shutdown and reboot by long pressing power. I cannot keep it shutdown, it goes back to Download Mode screen.
I've tried to restart start with power + vol up or power + vol down, power + vol up + vol down. Same.
I've tried to let it die on battery, charge it, and here it's a black screen with the large battery logo and a white text at the top saying: Download mode. After a few minute I try to boot and it's back to the white screen.
What can I tried next before I send it back for repair and it will be probably wiped again...
Side story, I've almost force her to switch from iPhone to Android because of price of the devices, and so far she is not converted at all with all the trouble we got with this Nokia.
Click to expand...
Click to collapse
I'm having the same problem. Exactly what you said. I didn't root my device or even attempt to do anything. I bought Nokia because they were purely stock and delivered some quality mobile phones. I've got only this phone as my daily driver. So tell me if you have got the issue fixed and how much did it cost and how long it took. It's been stuck with that 'android one' logo and a small message that reads 'Download mode' on top. I've tried everything. And what I'm worried about is, my phone's out of warranty and I'm a student. I hope you got it fixed for some reasonable cost. Please reply to me ASAP.
My wife's phone also has had this exact same problem.
I have tried all the tricks mentioned above including ADB mode (it could not find the phone).
The phone is supposed to be under warranty. So I took it back to the place of purchase.
However, the phone has a tiny crack in the corner of the screen which my wife and I were not aware of. So Nokia have indicated that unless I get the crack fixed, the warranty is voided and they will not fix the boot problem.
Because the broken crack is not covered by warranty, Nokia want $270 for a new screen before they will look at the software problem caused by the pie update.
I took it to a third party repair shop to see if there is a cheaper option. They cannot fix it either.
So the 5 month old Nokia phone is now useless.
But if anyone can comes across a solution for this, can they please post it here.
Thanks.
Same here. I told the guy on the phone about the crack. But he told me it should not be a problem. Now I got an email that I needed to pay 185 euro's to repair the screen.
Because of their FW-update, my phone became unuseful.
When I get it back (not repaired) I will try a OST on it.
I solved my issue via this procedure:
https://www.techmesto.com/possible-fix-nokia-smartphone-stuck-on-download-mode-after-ota-update/
I solved it via drivers: https://github.com/StollD/nokia-driver-installer/raw/master/out/Phone_Nokia_USB_Driver_v1.4.0.exe
WTF Finally I fix it!!!
Pibroens said:
I solved my issue via this procedure:
before, i can't got the phone connect to the pc.
So every way have failed...
After install the driver he supply,I still cant.. but!
I keep connect it,and press the power,volume up down all three button.
After it power on again pc find the phone. And i use the way he supply.
Click to expand...
Click to collapse
My Nokia 7 Plus got stuck in download mode after accidently pressing all buttons simu
Yes I know that sounds like a weird title and maybe you are wondering why did I do that? notice the word accidently.
I was just trying to fly my newly bought drone x pro for the first time and the controller has a little pull out extendable cradle to hold the phone in
if you want to view what the FPV camera is viewing while in flight and because of the bad design with all buttons on the same side of the Nokia 7 plus, unbeknownst to me all 3 buttons were being pressed at the same time and before I knew it my phone was shutting down and rebooting to this ridiculous download mode and the rest is history!
So I just thought I would mention this to anyone who happened to or happens to land in the same situation as me to be aware that you should probably put a little bit of sponge taped to the side of your phone over the volume buttons to possibly prevent it from being pressed simultaneously when flying your fpv drone.
If all else fails you could always connect the drone to your phone and then just put your phone in your pocket and fly blind by simply walking with the drone or rather running since they are pretty nippy. I am a bit bummed as this would have been a very convenient way of checking how full my guttering is of leaves without having to climb a ladder every time to check!?
Anyway I also used the fix here: https://www.techmesto.com/possible-fix-nokia-smartphone-stuck-on-download-mode-after-ota-update/
after downloading the nokia phone drivers from github.
If you are on windows 10 pro you may get a screen protector warning not to proceed further?
Ignore it and continue installing the drivers!
So far I got the Nokia Logo back and then it just hung there for several minutes without being recognised by the pc.
So I simply disconnected the phone from the pc and suddenly got the familiar nokia tone start up but then black screen again.
I realised it had been on the download mode so long it had completely drained the battery so now I am charging it.
Fingers crossed when I power up again I will at least have my phone back, sadly minus the data. (I will of course at least have all my google notes and contacts etc backed up to google servers at least they are useful for something!!)
I can't recall the last time I used it but I am pretty sure I had the SD card set as the main download so hopefully fingers crossed that data should have remained untouched, not sure how Android sets this up anymore?
Long time since gingerbread when you could still install and run apps as a completely separate partition.
All became a bit confusing after that so rooting became something I did hesitantly and as a definite last resort!
Anyway I am rambling on. If I find the fix works I will let you know.
Thanks for reading and thanks in advance if the fix works !!:good::good:
---------- Post added at 05:50 PM ---------- Previous post was at 05:23 PM ----------
leahcimewol said:
Yes I know that sounds like a weird title and maybe you are wondering why did I do that? notice the word accidently.
I was just trying to fly my newly bought drone x pro for the first time and the controller has a little pull out extendable cradle to hold the phone in
if you want to view what the FPV camera is viewing while in flight and because of the bad design with all buttons on the same side of the Nokia 7 plus, unbeknownst to me all 3 buttons were being pressed at the same time and before I knew it my phone was shutting down and rebooting to this ridiculous download mode and the rest is history!
So I just thought I would mention this to anyone who happened to or happens to land in the same situation as me to be aware that you should probably put a little bit of sponge taped to the side of your phone over the volume buttons to possibly prevent it from being pressed simultaneously when flying your fpv drone.
If all else fails you could always connect the drone to your phone and then just put your phone in your pocket and fly blind by simply walking with the drone or rather running since they are pretty nippy. I am a bit bummed as this would have been a very convenient way of checking how full my guttering is of leaves without having to climb a ladder every time to check!?
Anyway I also used the fix here: https://www.techmesto.com/possible-fix-nokia-smartphone-stuck-on-download-mode-after-ota-update/
after downloading the nokia phone drivers from github.
If you are on windows 10 pro you may get a screen protector warning not to proceed further?
Ignore it and continue installing the drivers!
So far I got the Nokia Logo back and then it just hung there for several minutes without being recognised by the pc.
So I simply disconnected the phone from the pc and suddenly got the familiar nokia tone start up but then black screen again.
I realised it had been on the download mode so long it had completely drained the battery so now I am charging it.
Fingers crossed when I power up again I will at least have my phone back, sadly minus the data. (I will of course at least have all my google notes and contacts etc backed up to google servers at least they are useful for something!!)
I can't recall the last time I used it but I am pretty sure I had the SD card set as the main download so hopefully fingers crossed that data should have remained untouched, not sure how Android sets this up anymore?
Long time since gingerbread when you could still install and run apps as a completely separate partition.
All became a bit confusing after that so rooting became something I did hesitantly and as a definite last resort!
Anyway I am rambling on. If I find the fix works I will let you know.
Thanks for reading and thanks in advance if the fix works !!:good::good:
Click to expand...
Click to collapse
So it worked, I have my phone back! Thank you so much for this solution!
Sadly my SD card was wiped too!!!!! super pissed off about this, many photos and notes and other files that I will never get back unless if I recall I may have made a manual backup of at least some of the earlier stuff I put on here a few months back on my pc?
Nokia will be hearing from me for sure!!!!! I want a 50% refund for messing with my life and my time. How can they send an update that essentially breaks a phone for a bit!???!!!!!!
Hello everyone, I hope some of you may be able to help me out with a "sick" HTC Desire 12 smartphone. Hopefully this is the correct place to post this question?
I recently purchased a HTC Desire 12 which had been used briefly (still looks pristine) and came fully charged and sitting at the initial set up screen, this I paired with my exaiting phone to transfer my apps, etc. over. The pairing started fine and apps starting moving along with whatever else. However as the phone was doing this suddenly white rings appeared on the screen which I believe indicates a factory reset? It stated it was erasing all data anyhow. I let this go and it continued for a very long time then the phone switched off during this as the battery ran out due to the time it was taking.
Now when I switch it one, it is basically stuck at the HTC initial black screen with HTC text, if I try to shut it off by holding the power key in, sometimes it will shut down, but instantly restart to the same place. I have been Google'ing different things before deciding to raise the white flag and post here. The phone can go into different menus / modes, but again seems to get stuck. For example as I type this it is at => FASTBOOT mode... but again just stuck there, it will not proceed past.
It also can get to the No command screen and then holding down the power button and then pressing the up button for a second will take it to the Android Recovery options.
Top of this screen states:
Android Recovery
htc/htc_bre_dug1_00401/htc_breeze_dug1
7.1.1/N6F26Q/181016
Bottom states:
Supported API: 3
No .zip file in internal sdcard
I have tried some of these such as Wipe cache and also Wipe data/factory reset, however no matter what it does after that (going through its processes - which only last seconds), the phone then returns to the black screen with the HTC text, basically the initial boot up screen and thats where it hangs. The only way to get it to do something is to use the volume up/down and power buttons.
Would any of you kind folk have any answers, help or assistance for this "sick" smartphone? I can get into the a
Any help would be greatly welcomed. Please be aware though, that I am not overly technical minded in the Android operating system, but have a bit of an idea. I have also repaired hardware on a couple of my previous smartphones, so will give anything a go.
Cheers,
N-I
Bgb
ات7غ
POOR HTC SUPPORT , HTC COMPANY