Database Develop

Lumia 710 bricked. Any help?

Ok guys,
as the title says Lumia 710 is bricked.
It had last factory update and everything was working fine. Then i had to mess with it and to try to install Rataplan V9.1.
The process was working ok. By default, bootloader was in DLOAD mode, so in order to install custom ROM i needed to upgrade to Qualcomm. I have upgraded it and installed Rataplan .nb rom to the phone with NSSPro V0.54.
This is when my problems start.
The phone starts with one long vibration followed after few seconds with one short virbtation and thats it. No screen, no system, zip!
When i try to connect it again by usb to check it with NSSPro, it always starts in NAND disk mode. It does not matter do i start it normally on power button or with volume up. Its always in NAND. And it is always stuck. While the phone is connected to USB i can see Qualcomm CDMA Technologies MSM device in device manager but it has yellow mark like the driver is not installed.
I have tried several other roms, and NSS always shows that the rom is successfully installed, but the phone (other than vibration and NAND mode) is dead.
I have also tried all the solutions i could find on the net but no help. Tried, nokia recovery tool, WP recovery tool, Chimera e.t.c. Nothing works. Now i have a problem with NSS. It keeps stucking and beeing unresponsive for every option except Custom OS flash. Whatever else i click it either says tha phone is not detected or the app stucks and shuts itself down.
Is there other tool i can try?
Can i do anything to recover this phone or did i kill it?
PLEASE HELP!!!

Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.

droidzer1 said:
Well that sucks and it sucks no one has tried to help here. I'm fair with Android but too new to WP's to probably be much help. Can you pull the battery out of the phone? Might pull it and leave it out a couple minutes then retry. You also might try from a different computer in case something has gone wrong on your computer in terms of port communication or maybe even a virus of some sort. Good luck.
Click to expand...
Click to collapse
Tried allready every solution that i could find or think of, including things You described. Nothing. I was left with no other option but to send phone to service. They have a box unit with which they should be able to recover phone.
That was 2 days ago. today is third day so i am thinking that my phone has gone beyond repair. Only thing i can do is to wait and see...

Why not...?
Why not send it in real life to a windows phone expert. There should be a place to get phones repaired But, if they say that it isn't possible for them you may have rendered your phone useless. Google should be your mighty friend in this case :crying: I wish you very good luck.

Is there any hope? (hard bricked...)

Hello Moto,
So I got my Moto G5s Plus awhile back when it was still new and I tried to root it right off (I know...it was stupid, I realize I should've waited a little until the stock firmware was released and more guides were made), and basically I ended up hard bricking my device.
There are no lights, the screen is completely blank, and the power button does absolutely nothing.
I have heard of a way to revive it from level 0, however, and I was on the path to doing that until I realized that-for some reason-my laptop does not recognize my dead phone at all. In the guide (which I've long since lost the link to..) it said that my phone would appear in my device manager (>start>right click on Computer>manage) under the android tab after installing a bunch of ADB drivers and such, as "ADB-somethingsomething". No such thing happened; I couldn't even find the tab it was referencing. Even after uninstalling and reinstalling the drivers that it mentioned, I couldn't seem to get my laptop to recognize my phone.
Interestingly enough, or perhaps not, I plugged it into my brother's laptop and it recognized it just fine (note, he had the drivers already installed and has meddled quite a bit already in this area).
Anyway, so now I have a pretty much mint condition hardware Moto G5s Plus, and I kind of don't want to spent money on another phone unless I know for sure that I can't fix this one. Is there any way to revive it from the dead?
P.S. I've found the stock ROM for the phone...but there's several different packages. (like..NPS26.116-26; NPS26.116-45; NPSS26.116-45-5; etc...) This my be a very stupid question..but how should I know which one is the one I need to download?
Any and all advice/help would be appreciated.
Thank you
[SOLVED]
So I managed to get it working without using a virtual machine.
To address the first problem, my phone wasn't even charged. To solve this I took a rubber band and tied it around the power and volume down buttons and attached it to a wall outlet for about an hour. (The little white light was flashing to signal that it was receiving power...which was more than I had accomplished than..ever..really...)
The second problem was my computer. I still don't know why it worked out like this, but essentially my computer never recognized my phone as the HS-USB or anything. Instead, my computer recognized it as Motorola ADB Interface (even though it was technically off and hard bricked..). This made recovering it easy, as I simply could fastboot flash the correct stock rom to my phone and go from there.
After trying a few different stock ROMs, I finally got the right one, and could boot into bootloader. And thus, finally, I was able to install TWRP, the OS back, Xposed, and Magisk.
I've used my phone for a bit now and no problems have come up. Installing Xposed did take a bit longer than I thought it would, but other than that I got me phone back.

My moto g5s plus is completely dead even bootloader is not working nothing to show just blank how I can get the solution of this problem. Company is asking to change the motherboard. Help

jaura.mohit said:
My moto g5s plus is completely dead even bootloader is not working nothing to show just blank how I can get the solution of this problem. Company is asking to change the motherboard. Help
Click to expand...
Click to collapse
Are they charging u for the motherboard Change

Yes 18000 rupees
---------- Post added at 06:55 AM ---------- Previous post was at 06:29 AM ----------
yograjfire18 said:
Are they charging u for the motherboard Change
Click to expand...
Click to collapse
18000 rupees hel p me to recover my phone

Rooting is software based thing, which should not damage hardware to that level,, right?
The blank-flash stuff can be helpful for you guys, but we don't have blank-flash files for our device.
You can search, learn and manage how to do it.
EDIT: can you check what happens if you keep pressed powe key and volume- key for atleast 2 minuts ??

____Mdd said:
Rooting is software based thing, which should not damage hardware to that level,, right?
The blank-flash stuff can be helpful for you guys, but we don't have blank-flash files for our device.
You can search, learn and manage how to do it.
EDIT: can you check what happens if you keep pressed powe key and volume- key for atleast 2 minuts ??
Click to expand...
Click to collapse
Yea, no, this is 100% software damage. Like I said, I have a mint condition (hardware wise) phone. I'm pretty sure what I did to mess it up was overwrite the data files for the previous OS. I remember trying to get it back to stock ROM, but having a crap ton of trouble finding it...and then pretty much doing a fight or flight thing and trying a stupid and edgy alternative. (I also remember, even while the phone was still working, it only booted into TWRP once or twice, otherwise it would always come up with an error)
I feel like all I need to do is flash the stock ROM to the device...but without my laptop even recognizing it, I don't know how. Essentially, the question being, is there a way to flash the stock ROM to my device without TWRP, without bootloader, without using the device at all (just my laptop); and if there is...does anyone know how?
Pressing the power and volume buttons did nada.
[edit]
I did some searching and I actually found the two links that I used while trying to recover my phone from the dead.
http://www.aryk.tech/2017/09/moto-g5s-plus-unbrick-solutions.html
https://forum.xda-developers.com/g5-plus/help/moto-g5-plus-hard-bricked-recognized-t3636457
The difference for me is that I never got my laptop to recognize it as any of the "HS-USB Bulk, HS-USB QDLoad 9008, QHS-USB DLoad 9008"; that's where I stopped in the steps.
I'll be trying to follow the steps in the first link again, but this time through virtualbox (make sure there's no conflicting drivers and whatnot). I'll post back with results whenever I get around to it.

flash -61

Need Guide to Unbrick Moto X4 XT1900-1 - Android One

I just bought a new Moto X4 Android One model and was using it for about a day.
I have unlocked the bootloader, installed Magisk according to the forums and it was work 100% fine. I put it down and picked it up after about an hour, it froze, the screen went black and it has been unresponsive ever since. I have never seen behavior like this. I have tried every combination of buttons while plugged and unplugged and nothing happens. The only thing is when I plugged it into my PC i got a "Qualcomm HS-USB QDLoader" device to show up. So its not completely a doorstop but I do not know how to proceed recovering from this.
I am begging for any wizards who can help to please point me in the right direction. I also apologize if this is covered elsewhere and I missed the post. FYI I was on the latest Android One June 1 update.

https://forum.xda-developers.com/moto-x4/help/hard-bricked-how-enter-emergency-t3757472

Thanks. I attempted the blankflash but got an error. I posted it to that thread. Any further suggestions are welcome.
Update 7-29-2018:
OK so I screwed something up and I wanted to describe what happened in case anyone else runs into a similar issue. My situation was not a "hard brick" as I initially thought. My setup was the following:
- Unboxing
- Updating the Android One build to June 1 OTA
- Unlocking bootloader
- Following Instructions for installing TWRP and Magisk
- Installing/configuring/updating a bunch of apps
I think I went wrong with I allowed Magisk to not only update the Manager app, but to also update the underlying modules, even though I had just installed them and knew them to be current. I think that process had a silent error which caused my phone to crash so completely when left idle for some time. I initially left it idle for about 90mins and that was when it initially locked up. It was inert, unresponsive, no buttons did anything. All I could see was the "Qualcomm HS-USB QDLoader" device in Windows which lead me to my initial post.
I did a ton a research on saving hard brick phones which ultimately was unnecessary. After about 48 hours, the battery had died completely since it was not actually off, just hung at a low level. I was then able to charge and restart the phone, reflash the firmware and start over. So far so good.
I really, really miss removable batteries and since this was my resolution to an issue I thought was way worse than it was I just wanted to document that apparently you can crash your phone this badly and you may have to wait out the battery as a troubleshooting step.

Factory reset has not restored Auto-Rotate, Active Edge, and the "ear sensor" when making calls

Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)

aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Before restarting, I'm confident the "ear sensor" that turns the screen off when I'm on a call as functioning. I'm also confident the auto-rotate functionality of the phone was working perfectly.
After I tried to factory reset the phone from the power-volume reset options, I actually ran into a TON of trouble trying to get the phone to properly reset. It tooks me countless tries to eventually get the phone to start after resetting it over and over again. I was stuck trying to get the phone to actually move through the setup steps. SUPER frustrating. I actually went to sleep while the phone was somewhere in the middle of setting up and when I woke up the phone somehow eventually made it through some setup steps.
I'm now using the phone as I normally would, but it's very odd. The phone is a LOT more unstable. At least 3 of the sensors I had working have just completely stopped working.
The phone is in otherwise perfect condition. I'm genuinely confused about how I should go about trying to resetting this thing to a pure stock configuration and slowly installing apps again to make the experience what I'd want.
And no, I'm not a super power user. I am a strong engineer happy to do crazy things like flashing bootloaders and whatnot, but I'm honestly confused about where to start. I understand other versions of this device may have had corrupted persist partitions during updates -- those problems seem like my problems -- but I don't know how I should go about simply flashing my phone at the lowest level into something stock that I can try to build back from.
And obviously when talking to google support their suggsetion is that I mail them the device and wait 10 days without a phone. I'm confused about how that could EVER be a reasonable way to get a phone repaired, sigh -- phones are not toys, they're pretty critical to the day-to-day work of so many people including myself. I'm pretty disappointing with that approach from Google and I had always considered them much better than that before this experience.
Anyway, I'm really lost and I'd love to understand how to repair the software on my phone.
(You all kick ass!)
Click to expand...
Click to collapse
I would try flashing the latest factory image via fastboot.
[Guide] Root Pixel 4 XL with Magisk Android 13
[Guide] Root Pixel 4 XL With Magisk Android 13 Android Security Bulletin—Feburary 2023 Pixel Update Bulletin—Feburary 2023 Introduction This Guide is for Pixel 4 XL owners that want to Root their phone, and enjoy the benefits of rooting it. The...
forum.xda-developers.com
https://forum.xda-developers.com/t/guide-unlock-flash-root-for-the-pixel-2-xl-taimen.3702418/ (This is for a Pixel 2 XL but the process is the same. It's basically a condensed version of the one above.)

aliljet said:
Hi!,
I'm a long-time reader of this forum, but this is my first post. In the last few days, something happened (I wish I could pinpoint exactly what) where I ended up restarting my phone and it entered a continuous boot loop. The phone was receiving updates per normal and may have received an update not that long ago that required some kind of restart, but I'm not confident about that. Either way, the phone was restarted and it entered into a permanent boot loop.
Click to expand...
Click to collapse
You did not provide the most important information we need- whether your phone is bootloader unlocked. Probably not, otherwise you would have already flashed it with a full Google image, which returns the phone to "out of the box" condition. You need to determine whether you can unlock your bootloader. If you cannot unlock (allow oem unlock is off and or greyed out in Dev options) then you will not be able to fastboot flash ANYTHING. If that is your case, the next best thing is flashing a full OTA image (sometimes called a rescue OTA) from recovery mode using the OTA via ADB option. This means you need fastboot/adb installed and working on your PC. Instructions on how are on the same Google dev page for OTA's.

So, my phone's bootloader is not unlocked. But I have an update for the crowd that may one day find this. I know your frustration and I can report that my phone is once again fixed.
A day (or two) after I sent this, a set of updates came down to my phone. And WebView was updated. That restored all of my sensors and also restored most of my crashing applications. It was an incredibly odd experience.
My phone once again functions. And the nightmare of owning a Google phone and talking to Google support has ended.

Question [SOLVED] Pixel 7 Dead(?)

Was installing the new build using flash-all.sh (without wipe) as I was rooted with Magisk.
Installer got stuck halfway. Disconnected, tried booting, got an error message saying device may have been corrupted or something like that.
The phone doesn't boot at all now, not even to the bootloader. Literally nothing shows up on the screen.
Any help would be greatly appreciated.

Double-check your download and make sure you have panther for Pixel 7.
Depending on what is corrupted, it may be very difficult to recover. With Qualcomm SoCs you can use a low-level tool like QPST (Qualcomm Product Support Tool). For Exynos you can often use ODIN. For Pixel, ODIN doesn't work and there aren't any QPST files (prob never will be).
I don't know how it works on linux, but on Windows I open Device Manager and plug my phone in. Depending on what you see will determine next steps.

Hung0702 said:
Double-check your download and make sure you have panther for Pixel 7.
Click to expand...
Click to collapse
Yes, the images are for panther.
Hung0702 said:
I don't know how it works on linux, but on Windows I open Device Manager and plug my phone in. Depending on what you see will determine next steps.
Click to expand...
Click to collapse
It now doesn't show up on any system.
Even though the screen was off, the phone was probably on and it was a bit warm. So I let it stay like that and let the battery drain overnight. Today morning I tried various button combinations and it did show a low/empty battery icon for a second. Nothing really happened when I plugged it in to a charger. It did get warm, indicating the battery was probably getting charged, but nothing showed up on screen.

dewri21 said:
Yes, the images are for panther.
It now doesn't show up on any system.
Even though the screen was off, the phone was probably on and it was a bit warm. So I let it stay like that and let the battery drain overnight. Today morning I tried various button combinations and it did show a low/empty battery icon for a second. Nothing really happened when I plugged it in to a charger. It did get warm, indicating the battery was probably getting charged, but nothing showed up on screen.
Click to expand...
Click to collapse
Unfortunately your only option is repair. Find a Google certified repair center such as uBreakiFix. Your device should still be under warranty. The tools necessary to recover a device when the bootloader fails are not publicly available.

V0latyle said:
Unfortunately your only option is repair. Find a Google certified repair center such as uBreakiFix. Your device should still be under warranty. The tools necessary to recover a device when the bootloader fails are not publicly available.
Click to expand...
Click to collapse
I have had pixel phones disassembled and have hooked them up to the android flash tool and they were recognised , even though the screens were blank the tool knew what was connected. Its a shot it might beable to help .

hammered58 said:
I have had pixel phones disassembled and have hooked them up to the android flash tool and they were recognised , even though the screens were blank the tool knew what was connected. Its a shot it might beable to help .
Click to expand...
Click to collapse
The Android Flash Tool works via ADB, so if the bootloader is corrupted or fails for some reason, that isn't an option.
Pixel devices (at least Snapdragon ones) do have the Qualcomm USB mode, but Google's prescribed means of repair in this situation is to simply replace the mainboard; most repair stations do not have QPST or the necessary files to restore the bootloader.

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
I have not come across a pixel device that cannot be restore...Google basically made this phone indestructible from software stand point.
use the above link to restore phone.

In the future I would suggest removing magisk before updating, would save yourself a lot of trouble. Just backup your modules to a folder on your phone and you can get them back quickly

Is it possible for you to take a pic of what your phone says? I think i ran into a very similar situation but i was able to access fastboot, just want to see if it's the same error i got

Make sure that
1. The latest adb is saved to the folder you extracted the factory image file
2. There is enough disc drive space available
Then rerun the flashall.bat from that folder

dewri21 said:
Yes, the images are for panther.
It now doesn't show up on any system.
Even though the screen was off, the phone was probably on and it was a bit warm. So I let it stay like that and let the battery drain overnight. Today morning I tried various button combinations and it did show a low/empty battery icon for a second. Nothing really happened when I plugged it in to a charger. It did get warm, indicating the battery was probably getting charged, but nothing showed up on screen.
Click to expand...
Click to collapse
Yikes. I had that happen to two Pixel 5a phones.
They booted into Qualcomm mode. I checked windows device manager and saw that it was a device, using qcomm, and there is no way to repair this one was rooted, one wasn't rooted.
I ended up buying a pixel 6 and 7.
Also, I noticed this occurred during the monthly patch cycle.
There is no way to get into the bootloader, fastboot, recovery, or safe mode.
I hope that isn't the situation with the 7s as well.
Good luck, please post your findings!

Vio281 said:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers
developers.google.com
I have not come across a pixel device that cannot be restore...Google basically made this phone indestructible from software stand point.
use the above link to restore phone.
Click to expand...
Click to collapse
Not really. That’s how I broke it while updating. My phone wouldn’t boot at all and wasn’t even detected by my mac and windows pc. Had to send it to the service center.
t3chwizard said:
In the future I would suggest removing magisk before updating, would save yourself a lot of trouble. Just backup your modules to a folder on your phone and you can get them back quickly
Click to expand...
Click to collapse
Thanks, I will do that.
J0nhy said:
Is it possible for you to take a pic of what your phone says? I think i ran into a very similar situation but i was able to access fastboot, just want to see if it's the same error i got
Click to expand...
Click to collapse
It was just a black screen. It wouldn’t boot into any menu whatsoever.
Sui77 said:
Make sure that
1. The latest adb is saved to the folder you extracted the factory image file
2. There is enough disc drive space available
Then rerun the flashall.bat from that folder
Click to expand...
Click to collapse
Yes, that’s how I initially updated which somehow broke it. Anyway, got it repaired for free since it’s in warranty.
grandpajiver said:
Yikes. I had that happen to two Pixel 5a phones.
They booted into Qualcomm mode. I checked windows device manager and saw that it was a device, using qcomm, and there is no way to repair this one was rooted, one wasn't rooted.
I ended up buying a pixel 6 and 7.
Also, I noticed this occurred during the monthly patch cycle.
There is no way to get into the bootloader, fastboot, recovery, or safe mode.
I hope that isn't the situation with the 7s as well.
Good luck, please post your findings!
Click to expand...
Click to collapse
Hi, I had to send in the phone for a repair. It was a free repair since the phone’s in warranty.

That happened to me with Pixel 6 Pro. The screen only showed the charging icin and wouldn't respond and the phone was getting hot. I ended up rebooting it by holding the power key and one of the volume buttons (don't remember which one) for like 30-40 seconds and that rebooted it and from there I got to recovery mode and flashed the image via sideload.