Hey everyone!
If you're reading this, you probably have the same problem as tens of people here: your phone reboots when you unlock it.
However, don't lose hope! It can be fixed easily and without wiping the system (which was the first way to fix this, but you'd lose your files ).
You need USB Debugging, which, if it isn't already active, can be a pain to enable (I know firsthand lol) but you can do it if you're fast enough (tip: use the settings icon in notifications to open settings faster).
I won't go into enabling it, you can find lots of tutorials online.
Here's how (computer with ADB needed, Google it if you don't know):
Plug your phone in your computer *before* unlocking it, then unlock it and accept connection.
For security reasons, I'll recommend you let the phone reboot now, as we don't want the phone to corrupt even more by trying what's next while the device is mid-reboot (that's the dangerous part).
Then, when the phone's on, don't unlock it, and:
-In a cmd prompt with ADB, type in:
adb shell
-Then:
pm uninstall -k --user 0 com.qualcomm.location
Now hopefully, your phone should work normally!
Thanks to pxbrz on Reddit for finding this:
https://www.reddit.com/r/Xiaomi/comments/ymr7yf/_/ivdu7z9
Hi AdonysGames,
Don't take this the wrong way.... but man I love you.... !!!! ;-) lol
---- thank you sooooooooo much, this has saved my life..... Was trying to find a way to back it up, using the ADB PULL commands.... as was expecting to wipe my phone when got in from work.
My phone is doing some weird things at mo, but its not rebooting... I think it needs to settle down, but at least it stays alive...
I tried looking for this too, but there was little info on it as of last night... but so so so glad you found it.
Cheers, Lister
Hi AdonysGames,
I am so surprised this hasn't got more hits/traction, and comments...
Even if you didn't create the fix, the fact you found, published it, and helped others (esp me) as I was so close to wiping my phone... and my brother told me to hold on, don't be so impatient...
Thankfully, got in from work... and this was here!!! - thanks again.
I'd just thought I'd raise it again, as surprised no one else has commented on it, and yet so many are wiping their phones and losing their data... lol
Cheers, Lister
I've tried enabling USB debugging well over a 100 times (in total I took about 4 hours of purely trying to enable debugging) however had no luck. Had to wipe my data out, but luckily, most of it was backed up.
vindit said:
I've tried enabling USB debugging well over a 100 times (in total I took about 4 hours of purely trying to enable debugging) however had no luck. Had to wipe my data out, but luckily, most of it was backed up.
Click to expand...
Click to collapse
wiping it out fixed the phone?
Hi all, I have the same problem, the phone keeps rebooting while i'm on the menu, waiting the counter to drop 0. Try everything then found a great solution. We want to slow down the faulty process. When the phone slows down? When it's hot. So i use my HOT/COLD GEL pack. Heat it up and put the phone on it. As slowly the phone gets warmer the reboot comes later. 6 sec, 4 sec, 3 sec, and i reach 0 and can turn on the debug mode! Great Success. Now i need to learn adb
the adb was simple just need to download a zip file, then open the powershell with SHIFT+rightclick and then need to access to phone and on the next reboot you can send the ./adb shell order and then the magic line written above
reddit source
https://www.reddit.com/r/Xiaomi/comments/ymr7yf/_/ivdu7z9
Howto adb: https://www.xda-developers.com/inst...56.635298822.1668193010-1753398863.1668193010
Thanks for everybody to save our honeymoon pictures
vindit said:
I've tried enabling USB debugging well over a 100 times (in total I took about 4 hours of purely trying to enable debugging) however had no luck. Had to wipe my data out, but luckily, most of it was backed up.
Click to expand...
Click to collapse
Took me an hour, managed to do it booting into safe mode, enabling battery saving mode, airplane mode and being quick and hitting the confirmation button like crazy.
AdonysGames said:
Hey everyone!
If you're reading this, you probably have the same problem as tens of people here: your phone reboots when you unlock it.
However, don't lose hope! It can be fixed easily and without wiping the system (which was the first way to fix this, but you'd lose your files ).
You need USB Debugging, which, if it isn't already active, can be a pain to enable (I know firsthand lol) but you can do it if you're fast enough (tip: use the settings icon in notifications to open settings faster).
I won't go into enabling it, you can find lots of tutorials online.
Here's how (computer with ADB needed, Google it if you don't know):
Plug your phone in your computer *before* unlocking it, then unlock it and accept connection.
For security reasons, I'll recommend you let the phone reboot now, as we don't want the phone to corrupt even more by trying what's next while the device is mid-reboot (that's the dangerous part).
Then, when the phone's on, don't unlock it, and:
-In a cmd prompt with ADB, type in:
adb shell
-Then:
pm uninstall -k --user 0 com.qualcomm.location
Now hopefully, your phone should work normally!
Thanks to pxbrz on Reddit for finding this:
https://www.reddit.com/r/Xiaomi/comments/ymr7yf/_/ivdu7z9
Click to expand...
Click to collapse
Hey!
I managed to enable USB Debugging but I can't seem to use ADB When I enter the commands as is In Powershell it gives me errors, I tried with ./ before the commands but it's says inaccessible or not found.
Please someone help me or guide me through what I'm doing wrong here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi All,
You don't need Powershell to run these commands, even a normal command prompt will do. That's how I did mine...
The important thing is to check you've installed ADB correctly, and that your device is being picked up / registered.
Easiest way to do that is to type "adb -devices" and if you see some random characters on the line below, it's found your device. If it says nothing below, it hasn't found it, and no matter what you type will have no effect.
If you're struggling to get commands working or using ADB, then use the attached program. Has quick access to certain features and will open a command line shell to ya phone...
Hope this helps,
Lister
I think it worked!!! You guys are amazing people thank you all!!!!!
Thank You, it work.
30min serach and 2 min to solve the Problem.
You save the day
iko.123 said:
Hey!
I managed to enable USB Debugging but I can't seem to use ADB When I enter the commands as is In Powershell it gives me errors, I tried with ./ before the commands but it's says inaccessible or not found.
Please someone help me or guide me through what I'm doing wrong here.
View attachment 5759109
Click to expand...
Click to collapse
did you solve it?
dcvvv said:
did you solve it?
Click to expand...
Click to collapse
Yes!
iko.123 said:
Yes!
Click to expand...
Click to collapse
How?, i have the same problem
iko.123 said:
Hey!
I managed to enable USB Debugging but I can't seem to use ADB When I enter the commands as is In Powershell it gives me errors, I tried with ./ before the commands but it's says inaccessible or not found.
Please someone help me or guide me through what I'm doing wrong here.
View attachment 5759109
Click to expand...
Click to collapse
i think i solve it, anyways thank you
Hi AdonysGames
I had fallen into despair, but thanks to you I was able to recover my phone and save my graduation photos
I hope more people can find this post so that they don't have to lose all the data on their phones, because even deleting the data, the problem persisted.
Your solution is the best, thank you very much
Can confirm this works for the Redmi 10c (Codename Fog) too!
It was a bit tricky enabling developer options between reboots but it was worth it as I was close to performing a wipe before I found this!
Thanks for sharing!
Gallgyerekugye said:
Hi all, I have the same problem, the phone keeps rebooting while i'm on the menu, waiting the counter to drop 0. Try everything then found a great solution. We want to slow down the faulty process. When the phone slows down? When it's hot. So i use my HOT/COLD GEL pack. Heat it up and put the phone on it. As slowly the phone gets warmer the reboot comes later. 6 sec, 4 sec, 3 sec, and i reach 0 and can turn on the debug mode! Great Success. Now i need to learn adb
Click to expand...
Click to collapse
This here saved my life, my phone, and all my data in it. It was very difficult for me to turn on USB debugging in small window of time, before it reboots again. But then I heated up my phone with my laptop charger, basically it's compartment that's get hot when it's charging laptop. I held that part with my mobile, which eventually heated it up. LEGIT giving me 3-4 seconds extra, to turn on USB debugging, and once it turned on. Phone rebooted, and then the USB debugging was already on. I ran those two commands on CMD. AND VOILA. IT WORKED LIKE CHARM
THANKS TO ALL PEOPLE ON THIS THREAD. YOU GUYS ARE REAL CHAMP <3
vindit said:
I've tried enabling USB debugging well over a 100 times (in total I took about 4 hours of purely trying to enable debugging) however had no luck. Had to wipe my data out, but luckily, most of it was backed up.
Click to expand...
Click to collapse
I literally cried after I finished the 10 sec-usb debugging challenge. I did it by placing my phone near a boiling kettle since im preparing my coffee. The heat from boiling kettle + airplane mode + battery saver did it for me! So crazy, just for my precious files :<
Related
I attempted to root my Galaxy S (Ohh, i live en Denmark and it's not branded but my provider is "3") but i somehow got some links mixed up, so instead of getting the right firmware for my SGS for 2.2 i got one which is 2.2 BUT, when it starts/shuts down it takes 2-3 times longer because there's an "AT&T" logo/bootscreen.
So i thought i would just flash it to "I9000XXJE2" so it would be 2.1 and i could start over. But here comes the biggest problem, is that when i just connect it to my PC it shut's down
And since it got the personality disorder where it thinks it's from the US and AT&T i can't get into download mode either, have literally searched since 11 PM last night (10 PM here now..) i'm so freaking tired and annoyed, been using a "Nokia 3310" to make calls.
So i don't now what the hell to do!..
Is there some how a way to root/something/fix whatever from the phone? Cause i can start it, but download mode/recovery doesn't work, and it i connect USB it shuts down immediately.
Hope you Android masterminds can help me!.. I'm going to bed now and see if there's answers later...
Theres no way to fix it, Send it to repair shop or search in the site for Galaxy S JIG as its hardware device that forces the SGS into download mode.
The JIG method would work fine. Give it a shot!
just encase you're not sure about the JIG thread:
http://forum.xda-developers.com/showthread.php?t=819551
Hope you get it working
Thanks very much! I will try the jig thingy for a final try!.. Hope it works!
Okaay.. So apparently it's VERY difficult to get those resistors if you live in a small town in Denmark, and your mom denies to buy ANYTHING on the net..
And now the phone almost died, apparently it won't charge (Didn't notice at topic start) any other advice?.. I'm guessing Samsung/"3" won't help since
root=no warranty?..
EDIT: If it wasn't clear i can start the phone, but can't connect to pc get into DL mode, but i can access SD card from phone, so is there maybe something i can put on that? To help?..
Anyone?... I wrote to "3" and Samsung, but they say something about root and they can't help.
So i guess i somehow gotta find that resistor or=no phone?.. I mean, if it would just charge, i could see if i could make it work.. But now there's only very little battery, and i've tried SO many things from this forum!
DanielBoeVen said:
Anyone?... I wrote to "3" and Samsung, but they say something about root and they can't help.
So i guess i somehow gotta find that resistor or=no phone?.. I mean, if it would just charge, i could see if i could make it work.. But now there's only very little battery, and i've tried SO many things from this forum!
Click to expand...
Click to collapse
I'm also from Denmark which software have you flashed and how?
You still have the white "Galaxy S" logo, not the AT&T logo, as the first thing on the screen when you boot up, right? It sounds like you have the AT&T CSC loaded, which is not the same as having the AT&T bootloader, which is what happened to a few people.
You still have the phone booting so you probably don't need the jig solution. Have you tried Terminal Emulator app with the commands "su" + "reboot download" (root required)?
It is rooted and i can start it up, and it won't recharge.
When i press powerbutton there is a white AT&T logo and then the normal Galaxy S start-up.
I rooted with "Doc Froyo" and then by accident in "SGS tools" from market pressed, and i'm not totally sure here, cause it was an accident. But something that said something about changing the lockscreen? and i either pressed JM6 "Eclair"
Or JE6 "Eclair" by accident (Stupid fat fingers..) and then it froze, and would'nt do anything so i rebooted it, and then it said AT&T and won't charge now/connect to PC both things shut it down, and it divides numbers weird..
I mean, it says for example: 123-45-1234 or something, ya know.. The US style, and it is like i'm driving at 9000 mp/h with the noise when i call someone (Tried it a couple of times)
(The number should be along the lines of 12345678)
Not sure what "Terminal Emulator" is, is there a guide/video to it?--
Tingen: I used something called "Odin v1.3" i think it was called and "Doc Froyo's"
And it was perfect, but cause of my fat fingers/clumsy self, i pressed "Apply" instead of the homebutton, and then it got "You're a moron" disease -.-'
And now the homebutton don't work either (Guess Captivate (Which it thinks it is now in menu, but when i start it, it says Galaxy S) has a touch homebutton or something?.. And back button which used to go one back, e.g. If i was in "some setting in settings menu" and pressed back it would go one back, now it goes back to desktop, back is kinda what "home" was before..
There's not much battery left, 25-30% but i can start it quick to see what it says in settings (The kernel/something/something) if that would help?..
Last time i turned everything off and connections of and no live wallpaper and airplane-mode and brightness down so hopefully, i can try something without it dying.. But just say if it can help and i will post those data
Thank you both, for answering my post, thought i was going to get no replies and end up with a new paperweight..
EDIT!!!: I think i'll post a video in a couple of hours (It's the middle of the night in Denmark right now)
DanielBoeVen said:
Not sure what "Terminal Emulator" is, is there a guide/video to it?--
Click to expand...
Click to collapse
It's the "Android Terminal Emulator" app from the market. Running it and entering the commands "su" and "reboot download" should get into download mode.
It's really risky flashing with so little battery left, you could end up bricking it much worse. If possible find someone with the same phone or a store who will let you charge the battery.
Because you've replaced the bootloader with the AT&T version you need to flash a full ROM that includes the standard bootloaders. Don't flash a 3-button fix or an update ROM. To check you have a full ROM make sure the PDA .tar file that you're flashing includes boot.bin and sbl.bin. You can open it to check with WinRAR.
I just very quickly tried that.. I got the thing downloaded, but when i wrote
SU it said not found.
So back again. I guess i need to see if others have a Galaxy which will let my put my battery in theirs so it can charge.
EDIT: Ohh, and also got the data from setting:
Model: SAMSUNG-SGH-I879
Firmware: 2.2
Baseband: I897UCJI6
Kernel: 2.6.32.9
[email protected] 11 #1
Build: FROYO.UCJI6
EDIT2: And the charger is in, and i noticed (Still can't see battery logo or anything) that from the M-USB (Cover is off) and to where the hole is (Where the battery sits) it's warm, but battery even now after 10-15 minutes isn't warm at all, it's like it goes all the way to the little gold thingys that connect the phone to the battery, and then stops there just before the battery.
The battery is getting SLITHGLY warmer in the top, but i think it's just from the top part of the phone being warm.
I'll post some pics/video with description later.
OH! If it helps, it seems it was not SGS tools! But "Galaxy S Tweaker" or GST from market, it has a white logo with a wrench on it, if you search on appstore and download the app you can see what i did.
DanielBoeVen said:
when i wrote
SU it said not found.
Click to expand...
Click to collapse
It needs to be "su" in lowercase, did you try that? If it still doesn't work in lowercase it means your root didn't work, or isn't installed properly. Try the z4root app to fix it.
Tried lowercase, don't work.
What is "z4root" for?
I see it says root/unroot, but which should i choose?
Ok. downloaded it and i could choose root, so i did. now it says
"Please wait while root completes and you
device is rebooted..."
been like that for 3 minutes, how long does it usually takes?..
OMG I ****ING LOVE YOU! LOOK LOOK LOOK!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It's been like that for a long time, but at least the pc recognizes it now, and DL mode is working! THANK YOU! If you lived in Denmark you'd be getting a case of beers now!
Even if this won't work, i at least can charge it and get into DL mode, the Z4 thing solver the root, and Terminal worked after that! Thanks!
Hmm it seems that it get's stuck in odin (tried odin v1.3 and on-click) at "SetupConnection"
But i'm going to see if i can maybe charge my phone now
EDIT: Aaaaaand now there's a weird
"mobile phone - - triangle with ! - - computer"
icon, hard to explain..
Hmm. Seems now i'm really screwed..
So if hairdryer heat thing won't work, i'm sending it to support, and hope they don't say "screw you, you broke it" (In sciency terms of course) and send a bill.
I hate this, right now until this work, my phone is an old Nokia which can make calls and won't send text messages.
I've been using smartphones for 5-6 years. I feel so "trapped" or "claustrophobic" with this Nokia.
Mailed Samsung a week ago, they said i should talk to my provider first, so i mailed "3" 3 days ago, and they said i should contact Samsung.. :S
So wrote to "3" again that they said i should contact Samsung. But they haven't answered yet, god it's frustrating!
Hey guys
Last night I broke my SGS's screen. The phone is rooted and I know it still works as can hear it get texts and boot up correctly.
I wanted to just swap the phones out but I have a lot of valuable pictures etc on the phone that I hadn't backed up yet.
Is there any way to access the hard drive from the computer w/o being able to access the phone?
I tried the "Screencast" app but I cant seem to get it to work. I tried doing some searches on here but I'm not exactly sure what to look up.
I have insurance on my phone so I can get a replacement, I'd jsut like to get my pictures and any text messages i may have missed (but mainly the pics)
Any insight you guys have would be much appreciated.
Thanks in advance!
Reboot in recovery mode. That would give you adb access to the phone and you can adb pull your pictures with "adb pull sdcard/DCIM/Camera".
thanks for the reply.
sorry i'm kind of new at this stuff. my friend rooted my phone and did all the dirty work. i have no idea how to use adb or w/e
do i need a linux machine? also, how can i reboot in recovery mode if the screen is completely disabled?
do get via ADB you need to ADB kit or the Android SDK kit, theres a helpful section on how to do ADB but it shouldnt be a problem, i also recall that after ADB is installed you might be able to use Android explorer to go to the phones pciture directory and get them like that?
i'm having a horrible time trying to get this setup lol
i think a problem i'm having is i dont know if USB debugging is enabled on my phone, and since the screen is broken i can't turn it on.
anyone else have any other suggestions?
redstar2k said:
Reboot in recovery mode. That would give you adb access to the phone and you can adb pull your pictures with "adb pull sdcard/DCIM/Camera".
Click to expand...
Click to collapse
it seems i can get it into what i ~think~ is recovery mode (it didnt make the typical noise it makes when booting up, and my bottom row buttons light up if i press the power button then one of the buttons)
not sure what screen im in honestly... but even still, the computer doesnt detect that anything is plugged in and ADB doesnt detect any devices...
maybe with usb cable?
thats what im doing is using USB cable.. problem is i cant mount my usb from my phone as the screen is broken.
i cannot do it blind either i dont believe, i dont think the screen is detecting my fingerpresses at all
I can toggle the option in the developer menu, but it don't show on the PC.
If I exit that menu and go back in, USB debugging is off again.
I've tried a restart without affect. Any ideas?
I've had the same issue. I've simply turned it on, went back one step, then into the developer settings again and checked if it was still on. It wasn't, so I did this repeatedly until it stayed on. Since then it never turned off again.
Also, disconnect it from the PC. As far as I can remember it only stayed on if it was activated while disconnected. I couldn't activate it before when it was connected.
Still having problems with this. Thought it may have been a bug with 106 firmware, but upgraded to 107 last night and issue persists.
Any help or ideas please? I've tried activating it several times in a row and can't get it to stick at all
I have just come across this issue. I suddenly lost root, and any time I try to open an app that requires root it just closes.
Then I noticed that USB debugging wasn't on. It had been fine for over a week, now it just won't stick no matter what I try.
Anyone found a solution yet?
Also turn on the option for allow debugging only in charge mode. That should fix it
AaronAverage said:
I've had the same issue. I've simply turned it on, went back one step, then into the developer settings again and checked if it was still on. It wasn't, so I did this repeatedly until it stayed on. Since then it never turned off again.
Also, disconnect it from the PC. As far as I can remember it only stayed on if it was activated while disconnected. I couldn't activate it before when it was connected.
Click to expand...
Click to collapse
I did the same as i was getting frustrated adb couldn't get it but at the end i made it work, even if sometimes adb devices don't get the device so i have to switch between transfer files and charge only mode, after a couple of time adb recognize the device and I'm good to go
Still having trouble with this. Still unable to turn the setting on.
Also discovered today I couldn't select the transfer files button when connected to the PC, kept going back to charge only.
I found the setting only sticks when the USB is connected and if you visit the dev settings while it is unplugged it will be switched off again.
mushtafa said:
Still having trouble with this. Still unable to turn the setting on.
Also discovered today I couldn't select the transfer files button when connected to the PC, kept going back to charge only.
Click to expand...
Click to collapse
I have the same problem. I am VERY glad when someone knows how to fix this truely but I have a tip for you: Charge the p20 pro to 100% and then plug it in the usb port. You can then enable usb debugging and for me it then does the trick and works as long as i dont unplug it. If I unplug it, I need full charge (100%) first and then can debug again.
For my Laptop with which I am debugging, windows 10 displays "current overvoltage at the usb connection" and I can neither access my normal data on the phone (just charging modus is enabled) nor debugging. MTP connection is enabled but it still does not work.
Have the same issue myself, could this be a logic problem as indicated here ?
https://forum.xda-developers.com/mate-9/help/udb-debugging-wont-stay-t3711939
mrabcx said:
Have the same issue myself, could this be a logic problem as indicated here ?
https://forum.xda-developers.com/mate-9/help/udb-debugging-wont-stay-t3711939
Click to expand...
Click to collapse
Just tried it out with so much hope that this would work. Unfortunately it does not work. I have the "Allow ADB debugging in charge only mode"-switch on and the "Always prompt when connecting to USB"-switch off. Does it work for all of you if the phone is charged 100%
I updated the firmware to .128 and the fault persists. Was hoping it was just a bug
Same problerm here. Worked fine for 4 weeks, stopped working yesterday. FW .120. Tried all the hints, no luck. Other suggestions?
I have same problem.... I use debug mode for connect p20 to pc and use it from remote.... damn now i'm ****ed with tis BIG BUG. Version .128
adivorandroid said:
I have same problem.... I use debug mode for connect p20 to pc and use it from remote.... damn now i'm ****ed with tis BIG BUG. Version .128
Click to expand...
Click to collapse
Did you managed to remote debug successfully?
NO, same bug in last .128
Does someone know how to reach out to huawei so they fix it? Because it seems to be a major problem for several devices, not just one.
I'm very angry for this... i can't use my phone during my job at pc, all for a stupid BUG !!!!
I'm writing to Huawei ... I hope to receive a reply soon
.131 will be available soon ... we hope for the solve bug problem
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I found a workaround except from waiting for 100% charge: Use a usb c to usb c cable, on my laptop and with my cable the energy drain is not higher than allowed then
Hi everyone!
I'm new here, I don't know if this is the right place to post this but I am having some serious issues now with my Nokia 8 of just only 11 months!
Still in pretty good condition, yes it may have had a drop here and there with a rubber casing
Just a couple nights ago I decided to go on my phone (3:30am pprox.) unplug from charger and was just scrolling through facebook via. Chrome and noticed it the whole app froze, and none of the buttons/touchscreen was responsive, didn't even want to lock. Just thought casually to force power off by holding the power/lock button for maybe 10 seconds and thus it did turn off. Straight afterwards I tried turning it on and to my surprise it didn't turn on, even holding the power button for a good length of time, to no avail.
No lights on the panel and didn't even recognise the charger.
I researched here and there and tried the different "holding down" button combos (Volume Up/Down and Power Button) but absolutely nothing!
I thought it was probably stuck on a boot or something, thus I went ahead and removed the screen (will need replacing unfortunately) and disconnected the battery ribbon cable, and after a minute and plugged it back in, hoping that it will finally power on. Nothing changed.
I am now left absolutely scratching my head and almost exhausted my options as I have been left without a phone, missing out on calls and messages for work and now really worried doing the button combos might've erased my phone's data/memory! :crying:
I am either wanting to repair my phone (getting out of its bricked state) or backing up or dumping the memory containing my contacts and SMS messages!
I have not come across anything like this exactly from other users, everyone seems to have been able to get the screen working and enter recovery/safe mode(s). But for this to just happen right on front of me is just bizarre and un-explainable!
Does anyone know if they may have experienced this whatsoever? And if anyone can help me on this??
I would really really appreciate it! ?
The phone burned out
([emoji3590]09-09-18[emoji3590])
Wow, are you very sure? How did you come to that conclusion may I ask?? :crying:
I have read elsewhere people with overheating problems where the phone hangs and they had to force power off. But they manage to power it back on with the button combos
Hi everyone,
A recent discovery and I thought it was worth mentioning, after having the phone connected to my PC, maybe after 30-60mins a device recognition sounds off, and in the device manager it originally comes up as QUSB_BULK. I see this related to the usual QHSUSB_BULK that people gets in other places on the internets, thus I installed the Qualcomm drivers and now I get this everytime I leave my Nokia 8 connected after that amount of time.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Does anyone know what this could mean perhaps?
Is there anything I could do from here??
If the phone is still disassembled, check the battery if not damaged or swollen or seems like a big pack of air inside. Maybe the battery is gone. Else flash a stock rom. You'll surely lose all data.
I have disassembled the phone and looked at the battery, it doesn't seem to have swollen or deformed at all. I've even checked the voltage with a multimeter on the ribbon cable for it and it reads on average 3.7v to 4.1V (depending if I've left the USB cable for awhile, like as if it was charging.
I really really don't want to loose my data, there are very important SMS messages that I need to keep!
Is there any way to backup any of this? Maybe through this Qualcomm?
Try to install a few android manager apps on your computer to read from the phone, available from different phone makers, htc, samsung. Unfortunately nokia didn't make one. Try to boot start your phone in safe mode if you can, even though it doesn't light up, maybe it will vibrate. Connect with your computer and try them all. Sometimes holding power and volume down and connecting usb might work.
If not, its probably gone. Your warranty must have been void by now, since you already opened it.
Your'e right, Nokia didn't make one, but like I said before it DOESN'T recognise to access the storage, the phone is dead, doesn't vibrate, doesn't lit up when power (or any) button is pressed.
However, as I've stated in my previous post, leaving it plugged for 30+ minutes will bring up an unspecified device (QUSB_BULK or QHSUSB_BULK) known as Qualcomm (I'll attach screenshot here again).
The warranty expire before I even removed the screen.
There's a very good chance that it's boot is corrupted (I didn't even do ANYTHING...no flashing, modification...Nothing!), and that it's stuck in a bootloop or cycle. I've only read people suggesting (like yourself here) to flash the rom which would bring it out of it's current state (only IF this is the scenario, but we're not too sure) but this would definitely erase everything, which needs to be avoided.
I've also been doing some more research, in regards to Qualcomm, is there no way to retrieve the data through this "Unspecified Device"?
Apparently I've read rumblings of people doing a full dump of their storage. Does anyone know more about this perhaps??
Try putting it on charge for 20 minutes, even if it doesnt show anything. Then with charging connected, hold down power vol + and - together for 3 minutes. Good luck.
There is Miracle Box tool available online for retrieving data off most phones. Look for it. That qualcomm unspecified device has been attributed to corrupted motherboard. Only option would be to replace it. Try your best with softwares before letting go.
Best of luck and hope for the best...
angellorex said:
Try putting it on charge for 20 minutes, even if it doesnt show anything. Then with charging connected, hold down power vol + and - together for 3 minutes. Good luck.
Click to expand...
Click to collapse
I have perfectly described this in my original post. Even with the charger intact...nothing!
djunk said:
There is Miracle Box tool available online for retrieving data off most phones. Look for it. That qualcomm unspecified device has been attributed to corrupted motherboard. Only option would be to replace it. Try your best with softwares before letting go.
Best of luck and hope for the best...
Click to expand...
Click to collapse
Wooaahh...don't luck me off (get it?) just yet! Still hoping we can all work together to not only benefit me but many others who has gone through this torment and to hopefully come across this in search for a solution.
In regards to your post, when you say it's attributed to a corrupted motherboard, do you possibly mean that the system files or partition or software or whatever got screwed up?
Previous poster PoochyX stated "The phone burnt out", but if this was the case wouldn't the PC not pickup the unspecified Qualcomm device? The fact that it is would indicate that this is not the case perhaps??
Looking forward to your thoughts everyone! ?
Pretty sure its a software issue, since its able to get power after some time. Found this on nokia forums
https://community.phones.nokia.com/discussion/51807/hardbricked-nokia-8-ta-1012
Maybe that can help. Try to use the miracle box tool to recover some data if you can. Then try to flash a firmware.
Hi everyone,
Sorry for my late reply, life has been pretty busy and very slow since I am using my backup phone (HTC One S) which even after hard resetting is running tremendously slow, battery draining really quickly (even after replacing a year ago when I thought it was a battery problem) and keeping communication to a minimum since I've lost all contacts and messages
I've checked the Nokia forums, they are not very helpful at all. And there is nothing of them to support retrieving your lost files and more of encouraging to just get the phone booting again (which results is data wiping).
I've looked into the Miracle Box tool, and whilst it looks really handy, I'm just not too keen on having to purchase a piece of device inorder to use the software and hoping it'll access or recognise my phone. I was really wanting it to be done as simply as possible.
Please do correct me if I am missing anything on this matter.
One thing I have came across are these "Qualcomm Phone Dumper Flash Tool"
- One variant here: https://youtu.be/JXbax7t42J0?t=128
- Phone rescue++: https://youtu.be/kSUZXnFnvUU?t=18
Both apparently shows the dumping of the EMMC, can anyone verify this or have any experience anything like these?
Also, if they are dumped, can the data be accessed to retrieve and backup contacts, sms messages and other important bits perhaps??
Apologies for the long post, there was a lot to get off my chest too but I hope we all can solve this matter, always appreciative! ?
Also I forgot to mention!
Despite the phone being in a unresponsive state, me doing the button combinations, like Power+Vol Up/Down, what are the chances that I could've hard reset or wiped my data completely???
Additionally, if I am able to do a full dump of the EMMC, how will I be able to extract my contacts and messages from this?
Hi everyone, I am still without my Nokia 8 and have been in discussing and trying different things!
So I thought it was worth to update you where I am and if you can still help me at the point I am at!
As you're all aware my device is recognised through Qualcomm 9008 by just using standard USB connection. Remember I can't see anything on the screen (it is also broken) so I can't tell what mode the phone is exactly in, but I am at the stage of using emmc Software Download app from QPST. I am doing this in order to access the internal storage and make a backup of my userdata.
Now according to emmc software download app, sometimes it is in "Download mode". What does this mean?
Also, I previously mentioned that my phone is freshly recognised in device manager in 15 minutes after connected by USB, I get this happening in emmc software download app:
I have tried this again and after leaving it for more than 2 hours it's still the same and gives me that error message after selecting Okay.
However, if I unplug and re-plug USB, then open again emmc software download app, and then click DLOAD button to select phone, I get this:
The State is now Enabled but no more Q/QCP-XXX (Sahara Download), it just says No Phone.
Any idea what this means???
there is a fix for that if ur phone detected as qloader 9008, means ur phone is in emergency state. u need a proper driver for ql9008 and a
multi functional/edl boot cable. once detected use QFIL tool to flash ur "nokia 8 firmware(must qfil), dont use normal cable it wont flash the qfil firmware. or see tutorials how to use it. that might solve ur phone problem and make it alive again.
but this might erase all ur data.
JinbrianZ said:
there is a fix for that if ur phone detected as qloader 9008, means ur phone is in emergency state. u need a proper driver for ql9008 and a
multi functional/edl boot cable. once detected use QFIL tool to flash ur "nokia 8 firmware(must qfil), dont use normal cable it wont flash the qfil firmware. or see tutorials how to use it. that might solve ur phone problem and make it alive again.
but this might erase all ur data.
Click to expand...
Click to collapse
@JinbrianZ Kumusta friend!
Thanks so much for replying here, it truly is like having a gift for Christmas!
I have already installed the Qualcomm drivers (manually), hence why I get QDLoader 9008 in device manager.
I have read somewhere on the internet that the Nokia 8 doesn't work with any EDL cable, as it has it's own button combination to access the different modes. Please correct me if I am wrong.
At the moment I am not trying to flash my phone, I am merely trying to gain access to the eMMc so I can make a backup of my userdata partition. After I have done this, then I will make attempts to flash. However none of this can happen since I am experiencing the problems I have posted
Might you know why the software ifs giving me this error? Have you got a Nokia 8 too??
@Nokia_8_fan
ur chances of dumping the data is very low since ur phone state is bad, u might able to dump it if ur phone is able to bootup atleast, but seems thats not the point.
now its either u keep trying to find a way to backup ur data till u succeed. (doing this u might not able to achieve both by recovering the data & making ur phone usable again).
or
try to make ur device able to boot again. (atleast* if this works u have a working phone again). regardless of data restoring.
but i guess it cant be help. im sorry.
@JinbrianZ
Well I just bought an EDL cable, maybe the standard USB isn't just communicating well enough? Even for it to enter EDL mode?
I really hope my device isn't in such a bad state as you've put it, I mean it's still recognising as QLOADER 9008 at the very least. In fact, at this time point of the video this is almost exactly how my phone looks like in eMMC software: https://youtu.be/vkUv5Wmor8Q?t=42
The difference is when I try switching to DLOAD, I get the error 0x80004005.
I also don't know if the fact that I don'[t have an XML file loaded is part of the reason why it's not working?
I don't quite understand this and I wouldn't know what file to put in there exactly, or where it can be obtained.
Could this be a reason why its not working for me?
@Nokia_8_fan
have u downloaded nokia 8 qfil firmware? it might be included there, something called like "flash_local.xml". and also ur phone should be detected as COMxx. as u posted before.
if u able to do that again then.
follow this guide. u might u already seen it.
https://forum.xda-developers.com/ge...w-to-backup-qualcomm-phone-root-t3570178/amp/
p.s.
emmc download is a old flash tool for all qualcomm based, just like qfil/miflasher.
u wont be able to backup from it.
I have a Moto G6 XT1925-5 (64GB version) which doesn't want to start up. It's all totally stock, been updated to Android Pie.
It gets as far as the boot animation, and does that for about 2 minutes, then it boot loops and starts all over again. When it bootloops it gets stuck at the first Moto logo screen (not the animated one) for about 3 minutes before carrying on to the boot animation...
This happened once or twice before, we left it overnight and eventually it started up normally. But it's now been five days and it still hasn't started.
I'm not very experienced with Android hacking/modding, etc but willing to try anything. I managed to get into recovery mode and at the top it says (I presume this indicates the firmware version):
motorola/ali_retail/ali
9/PPSS29.55-37-7-6/16c5a7
Unfortunately USB debugging is not enabled. Is there anything that we can do to recover the data that was on the phone before we wipe it - or is there another method we can try to get it to start up? I saw there's a command adb logcat which looks like it might be useful to diagnose the problem but that also requires USB debugging.
Thanks in advance for any suggestions
There is no chance for you to recover your data in this mode.
WoKoschekk said:
There is no chance for you to recover your data in this mode.
Click to expand...
Click to collapse
Thanks for getting back to me so quickly.
There are several other modes available from the bootloader BP Tools, QCOM, etc but I can't work out how any of them are supposed to work.
One question - on the recovery menu, there is an option 'Mount /system'.
I pressed it and it says at the bottom /system mounted, but then there don't seem to be any obvious ways to access anything.
Is there a way to use this to access OS/kernel logs which might give a clue as to what is going wrong?
Thanks again
Step by step...
The first level of the system, which is accessible for you, is called bootloader menu (fastboot menu). From here you can boot into recovery, system, bootloader itself and some other options you mentioned in your post.
None of these options would help you to solve your problem. These are developer's options.
This level is more or less a one way data connection. The main advantage of this menu is to flash single partitions of your device. But there is no way to get a data output of any partition.
In recovery menu you find the options to wipe your data and to mount /system. Mounting /system won't help you, too. This partition doesn't store anything of personal data. It's read only and not writable for anyone. To be honest, nobody knows exactly the meaning of it in this context. Also you won't access any logs from here.
Generally you can't access the system logs. These informations are only buffered data which is cleared with every reboot. The error message of e.g. the kernel log produced by your system when having a bootloop, is only accessible while your device is looping/freezing. The next reboot erases the logs. They aren't stored somewhere on your device. Even for developers it's very tricky to view the log in such cases.
But what would you do if you get the reason for looping? You are not able to access any system partition. You need root user permissions for that. But rooting your phone will erase all data.
Apart from all that your data is encrypted and remains encrypted until you unlock your screen by fingerprint, PIN or password. No chance to get any useful data as a "third person" outside. It would take several years to decrypt it without the matching key for it.
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
phone5774 said:
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
Click to expand...
Click to collapse
No problem!
Maybe you'll find some of your personal data in your Google Drive account...
How the story ended
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
phone5774 said:
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
Click to expand...
Click to collapse
When I read this last post, I immediately think of a sticky power button, because if you keep holding the power button after the phone has booted it will turn off again, and start up again. And it would also explain the weird behavior you just described of not turning off but rebooting straight away. I'd say: see if you are able to clean de button with a very thin needle or a crafts- or surgical knife around the edges, is might just solve your problem...
mcremco said:
When I read this last post, I immediately think of a sticky power button...
Click to expand...
Click to collapse
Thanks for that suggestion. Interesting, not something I'd thought of.
For now the phone is working perfectly, provided that have to restart it (i.e. we make sure not to shut it down or let the battery run out) but I'll definitely bear this in mind if the issue happens again.
The power button is working normally to turn the screen on or off meanwhile.
Thanks again for your input which is really appreciated.
First time trying to restart after the above
Since posting the above messages the phone has been kept on all the time and not restarted.
Today for the first time we accidentally let the battery run out and the phone shut itself down.
We nervously plugged it in and tried to switch it back on... and it started properly first time, so perhaps the underlying problem was simply that the storage somehow got too full (in the meanwhile we have transferred many photos and other media to the computer and deleted them off the phone to free up space).
Posting this in case it helps someone else experiencing a similar problem.