Related
So,I was pretty excited about the moto g5 plus, making sure I had it ordered and in my hands the day of it's U.S. release...........only to be disappointed by one issue after another.
Where to begin?
1.) Very disappointing camera(didn't expect much given the cost, but it's pretty bad)
2.) Sim Card will randomly stop reading while inside the device, thus requiring me to eject and re-insert it. Not a big deal, unless you don't have a sim tool or the equivalent on hand, then it's pretty inconvenient.
3.) Fingerprint reader is basically worthless, since it never saves the settings stored, or even requires it be my fingerprint to unlock it.
4.) Bluetooth and wi-fi decide when and where they will turn off/on.
5.) Call cutting in/out (with both parties)when I cannot hear the person I'm speaking with, and the person being unable to hear me.
Finally---About 6 weeks or so ago, my volume down button went, with the power on/off button going down about 2 weeks after that. That's ok, I can work around that. I could still lower the volume with the touch screen, and the phone would just wake up whenever I used the fingerprint scanner(the one anyone can use). Overall, things weren't bad.
Until my phone died.
So, i've been looking at a 100% fully charged, fairly shiny Moto G 5 plus.....that I can't turn on. I have tried all the usual tricks(i think?) Volume Down + power button and all its other variants don't seem to work. Tried plugging it in to my computer via usb, which will charge it, but won't read it as an MTP device. I can't go into the phone to change the settings so that it does read it correctly. I thought I had the updated driver downloaded, along with the adb program, but it probably doesn't mean much if the phone itself isn't being recognized, huh?(using PC with Windows 10).
Basically, I'm short on ideas. Is there some sort of way I can "jump start" my phone? It's a terrible device that will be replaced soon one way, or another, but if I can get it back to life long enough to retrieve my media and scout out a new phone, I would be ecstatic.
Any and all help would be very much appreciated!
Looks like you had a bad unit. Why are you not claiming warranty on this?
suhridkhan said:
Looks like you had a bad unit. Why are you not claiming warranty on this?
Click to expand...
Click to collapse
This is likely a very stupid question..
but how would I even go about doing so? Ideally i'd like to recover the files from the phone, but if that's not possible, then yes, claiming on its warranty would be my next preferred solution.
Very frustrated to push the volume UP button and see the phone at 100% battery.........yet not have any way of actually turning it on.
Hello friends,
My LeEco Le Pro3 (727) bricked two days ago and I haven't had any luck turning it back on. It was running LineageOS 8.1 latest official build with an unlocked bootloader, Magisk 16.0, TWRP 3.2.1, and OpenGapps ARM64 8.1 nano. Immediately prior to bricking I was setting it up for bluetooth with my car and was trying to run Google Maps through voice command. As I directed Google Maps to take me to a location, the phone froze, the screen got all "fuzzy" and I got the dreaded blue screen of death.
From that point on I have not been able to turn the phone back on. When I press the power button it will vibrate every 5-10 seconds as though it will turn on but it never does. Ive tried everything I can think of to get to work again including:
- Pressing power button for 2 min, 5 mins, 10 mins
- Pressing power button + vol up (recovery) for 2 min, 5 mins, 10 mins
- Pressing power button + vol down (fastboot) for 2 min, 5 mins, 10 mins
- Pressing power button + vol up + vol down (QFIL MODE) -> Installing Qualcomm driver, downloading "FlashOne2.0", flashing all versions of "qfil files" that I could find but still unable to boot up
- Pressing all different button combinations while plugged in to computer/charger
- Using different cords/chargers/usb ports
- Leaving it to charge overnight/full day then trying to boot up
- Leaving it sitting not charging for a full day then trying to boot up
At this point I'm starting to think it might be a hardware issue but who knows..
Any advice/suggestions would be greatly appreciated.
Thank you.
Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium
My one did the same, the issue was motherboard. You should send it back to repair.
mchlbenner said:
Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Thank you for the reply.
It was purchased from a local retailer here in the United States through Google Express. Fortunately I should still be able to return it for a full refund but I would rather have a working phone than my money back.
No flashboot either. It's like the phone just decided to quit working one day. Tried holding power while plugging in USB as well and no change.
marik1 said:
My one did the same, the issue was motherboard. You should send it back to repair.
Click to expand...
Click to collapse
The conclusion I'm reaching at this point too. I'll see what the return policy.
Well if it will not turn on it is hardware issue you should be able to return it.
Sent from my LEX727 using xda premium
That is so strange. The screen going fuzzy like that is indicative of a hardware issue, IMO. I saw that on my laptop once, but that was because I hit the screen too hard. Never seen a BSOD on an Android device before. TIL.
I assume you've already tried an adb logcat. Were you using the original LeEco cable? I heard it has issues since it's not up to spec. 99% hardware failure, but I can't help but think it has something to do with driver communication confusing the device and causing hardware failure (?) if that's even possible.
Just a final update for those curious.
After leaving the phone alone for two days I plugged it into the charger and low and behold it started vibrating and booted up by itself. It was running a Chinese developers editions 720 rom due to the QFIL File I had flashed in my earlier in my attempt to fix it. Battery was drained so I let it charge for a while and everything was fine until I attempted to restart the phone. As the boot animation was loading, I got the blue screen of death for a second time.
I took a quick picture, the phone shut off itself off, and same as before it wouldn't boot again. As other users have suggested it appears to be a hardware issue, likely with the motherboard. Fortunately I was still able to return the phone (purchased through Google Express via a local retailer) and received a full refund. I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.
shyboi122 said:
Just a final update for those curious.
I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.
Click to expand...
Click to collapse
You bought the same phone again? :good: You're courageous, lol.
i been experiencing the exact problem like your on my x720, as i boot up the system or enterting the recovery mode the screen go fuzzy on loading screen and shut itself off completly, i can still able access fastboot. As i left it for a while the phone will be able to almost finish the boot then ending it all with a blue screen.
Have anyone found a way to fix this DIY since my phone has past the guarantee plan ?
My screen broke 6 months ago, so it wasn't used/charged for 6 months. Now I've replaced the screen, but it won't start up anymore. First thing I saw was the warning "low battery", so I charged it for a while. Still, nothing. Charged it for several days, nothing. Checked the battery voltage, 3.80 volts, exactly what it should be I think?
The phone does do something though. When I hold the "on" button, after 5 seconds it buzzes and the screen shows the oneplus logo and android. Just for two seconds, then nothing. Same thing with "on" and volume down, the start-up screen for 2 seconds...
When I use "on" and volume up, I get the screen saying "fastboot mode". And that doesn't go away untill I press "on" for a while.
I can connect it to my laptop, but cant see it. But when I take the battery out while connected to the laptop, the phone will show the "low battery" warning. Connect the battery again, and the logo and android message come on for two seconds...nothing more.
So the screen works, the battery is charged, but no way to turn it on. Tried holding the "on" button for 15 seconds, same result. Just a 2 seconds oneplus logo visible...
I have no clue what this could be, I hope its not completely fubar...
Thanks in advance, Fred Doe
Hey Fred Doe,
I wouldn't like to hijack your post, but I seem to have run into the exact same issue here.
A friend of mine got his screen replaced, and the phone acts exactly the same as yours.
I have disassembled the phone and checked all connections, but everything seems to be correct on the inside.
The phone does seem to boot, and it does boot into recovery mode (it responds to the button presses by vibrating) but the screen just doesn't show anything.
Only when doing fastboot the screen stays on.
Hopefully someone here can point us in the right direction.
there's not much to hijack here...sure sounds like the same problem. At this moment I gave up, guess its a lost cause..
Guys, the exactly same thing here. I've tried to unbrick it but failed.... So far what I know is that bootloader is locked.
I would like to know what steps should us do in order unlock bootloader, get screen functioning while getting access back to bootloder (TWRP) so after that we can install a new ROM!
Any clue from the community of OnePlus 2? This phone is still a good phone! Thnx
Have you guys tried running the msm tool. It'll restore everything to stock if you can it to work. If either of you have magisk installed it can cause issues with charging while the phone is off I believe.
I mean honestly sounds more like hardware issue that a msm wouldn't fix, but it's weird that your screen works in fastboot.
If you do the msm tool though be aware it will wipe everything on your device, and relock the bootloader if it is unlocked.
Like I said doubt it will help, but just a thought.
Edit: Also make sure you use the correct one for your device.
Edit sorry guys wrong forum ignore everything I said. Apparently xda labs thought my OP6T was a OP2.
Sent from my ONEPLUS A6013 using XDA Labs
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
dajosova said:
@TheLogicalGamer
no problem. Thnx anyway. I'm still locked with my OP2.
Click to expand...
Click to collapse
But the screen does show up & stays on in fastboot?
I'm no expert but any stretch. I just jumped ship from lg my 6t is the 1st OP phone I've owned. But if the screen does work normally in fastboot then it wouldn't be illogical to entertain the idea that it was a software issue. So I mean this is a bit of a chin scratcher.
Sent from my ONEPLUS A6013 using XDA Labs
Thanks for replying.
IWhen I press Power + Vol. Up it shoes Fast Boot screen. Then I connect cable and sometimes I can use command line but can't unlock bootloader with command line. All methods found indicate to use Recovery but since my screen doesn't work on Recovery I'm stuck.
When I press Power + Vol. Down (for entering Recovery) screen it goes all black but the capacitive buttons and Volume button give back a vibration response, as if it have entered Recovery Mode but since I can't see nothing on screen I can do anything either.
My bootloader is locked because I see that info via command line.
Thanks anyway
PS: I think something is corrupted. My OP2 was unlocked much time ago. I frquently change ROM's and have also updated TWRP. The only thing I did was disassembling the phone in order to change a shattered screen glass.
I've also tried different methods and installed in my pc different Qualcomm drivers, ADB, etc.
I'm getting close to the point of testing with broken touch, buying a new touch screen but with frame or giving up completely and buy a new phone :|
The last option get me in doubt because I would like a phone wich is good and fast and decent battery but not with a premium price... and popular so I can unlock it without hassle in order to install root apk's.
In my persistent attempts to put a custom rom on this device, the following sequence occurred:
- Phone suddenly not recognized by PC in any mode: normal, recovery, or fastboot. It would not even charge from the USB port, no reaction at all from the phone or PC that the connection is made. Other devices using the same port and cable work correctly.
- Phone unresponsive to a wall charger while it is powered on. Similar to the above description, the phone does not recognize that it is pulled into a charger at all while it is powered on. However, at this point the
- Phone is responsive to a wall charger after turning it off. The screen shows the charging icon on screen and the LED is red, meaning the phone recognizes the micro-USB connection when it is powered off, but only via the wall charger, still sees nothing when connected to the PC.
With the above criteria I decide to let the device completely discharge its battery, hoping that a full empty to full charge will reset whatever is happening. It takes about 3 days to go completely dead ... moving from screen need-charging image, to only the red LED, to absolutely no response when pressing the power button.
Now I have a phone that is completely unresponsive to any button press, as expected since the battery is completely drained. Unfortunately, it no longer responds to the wall outlet at all. Meaning it won't charge in any way. Used multiple chargers, multiple wall sockets, multiple cables, gave it compliments, etc.
At this point the phone is totally and completely dead and unresponsive to any charging. Any thoughts or help?
apsommer said:
In my persistent attempts to put a custom rom on this device, the following sequence occurred:
- Phone suddenly not recognized by PC in any mode: normal, recovery, or fastboot. It would not even charge from the USB port, no reaction at all from the phone or PC that the connection is made. Other devices using the same port and cable work correctly.
- Phone unresponsive to a wall charger while it is powered on. Similar to the above description, the phone does not recognize that it is pulled into a charger at all while it is powered on. However, at this point the
- Phone is responsive to a wall charger after turning it off. The screen shows the charging icon on screen and the LED is red, meaning the phone recognizes the micro-USB connection when it is powered off, but only via the wall charger, still sees nothing when connected to the PC.
With the above criteria I decide to let the device completely discharge its battery, hoping that a full empty to full charge will reset whatever is happening. It takes about 3 days to go completely dead ... moving from screen need-charging image, to only the red LED, to absolutely no response when pressing the power button.
Now I have a phone that is completely unresponsive to any button press, as expected since the battery is completely drained. Unfortunately, it no longer responds to the wall outlet at all. Meaning it won't charge in any way. Used multiple chargers, multiple wall sockets, multiple cables, gave it compliments, etc.
At this point the phone is totally and completely dead and unresponsive to any charging. Any thoughts or help?
Click to expand...
Click to collapse
I had this issue when trying to flash GreenKernel. Turned out I messed up on a step and flashed it the wrong way. Check my posts in that topic.
Wenro said:
I had this issue when trying to flash GreenKernel. Turned out I messed up on a step and flashed it the wrong way. Check my posts in that topic.
Click to expand...
Click to collapse
Thank you for the response, I was about to throw the phone away. Can you be a little more specific? I see your post here regarding a rebooting loop with red light flashing. However, I don't have any response from the phone whatsoever ... nothing on the screen, or led in top right. It does not accept a charge from 1A or 2A source, it is literally a paper weight right now. I need to "jump start it" or something of this nature. It won't charge at all.
apsommer said:
Thank you for the response, I was about to throw the phone away. Can you be a little more specific? I see your post here regarding a rebooting loop with red light flashing. However, I don't have any response from the phone whatsoever ... nothing on the screen, or led in top right. It does not accept a charge from 1A or 2A source, it is literally a paper weight right now. I need to "jump start it" or something of this nature. It won't charge at all.
Click to expand...
Click to collapse
Probably the phone looks dead but does get charge - it's just not showing it with the LED.
I believe Snapdragons are close to impossible to hard-brick - the chip itself has a ROM with EDL burned into it and that can always be used to bring it back from zombieland, if you have the right tools. But if you are lucky enough, then service mode would still be available even without hunting for the EDL stuff.
First, power the phone off for real with the hidden button near the SIM tray - and leave it off.
Then, install Flashtool and use it to flash a stock ROM, as described for instance here. When flashing, choose flashmode instead of fastboot and follow the instructions.
HTH,
Antonio
antonio.galea said:
Probably the phone looks dead but does get charge - it's just not showing it with the LED.
I believe Snapdragons are close to impossible to hard-brick - the chip itself has a ROM with EDL burned into it and that can always be used to bring it back from zombieland, if you have the right tools. But if you are lucky enough, then service mode would still be available even without hunting for the EDL stuff.
First, power the phone off for real with the hidden button near the SIM tray - and leave it off.
Then, install Flashtool and use it to flash a stock ROM, as described for instance here. When flashing, choose flashmode instead of fastboot and follow the instructions.
HTH,
Antonio
Click to expand...
Click to collapse
Thank you for the response. I pressed the hidden button in the SIM tray for 10 seconds, 3 times in a row. Downloaded the latest "Emma" Sony Flashtool ... and nothing happens. The software does not recognize any Sony device plugged into the computer. Checked the USB cable, it's good. The computer, and the Sony flash software, do not recognize the device at all. It will not turn on in any way, and it does not appear (based on the screen and LED) to accept a charge at all. It truly seems bricked at this point. Any thoughts?
apsommer said:
Thank you for the response. I pressed the hidden button in the SIM tray for 10 seconds, 3 times in a row. Downloaded the latest "Emma" Sony Flashtool ... and nothing happens. The software does not recognize any Sony device plugged into the computer. Checked the USB cable, it's good. The computer, and the Sony flash software, do not recognize the device at all. It will not turn on in any way, and it does not appear (based on the screen and LED) to accept a charge at all. It truly seems bricked at this point. Any thoughts?
Click to expand...
Click to collapse
I don't know what method is used by Sony Emma, sorry. But simply connecting the phone won't surely be enough if there is no software on it that answers to USB requests from your PC.
How about trying with the tool I suggested you? Let the phone off, download a stock firmware and start the flashing in flashmode instead of the standard fastboot mode (just follow the on screen instructions).
If that does not work, the only thing that's left is EDL mode. I've found no documentation for Z5 Compact, unluckily - but any decent repair shop should be able to resurrect it.
Antonio
antonio.galea said:
I don't know what method is used by Sony Emma, sorry. But simply connecting the phone won't surely be enough if there is no software on it that answers to USB requests from your PC.
How about trying with the tool I suggested you? Let the phone off, download a stock firmware and start the flashing in flashmode instead of the standard fastboot mode (just follow the on screen instructions).
If that does not work, the only thing that's left is EDL mode. I've found no documentation for Z5 Compact, unluckily - but any decent repair shop should be able to resurrect it.
Antonio
Click to expand...
Click to collapse
I downloaded the flashtool you linked, and also the XperiFerm and latest Z5C drivers as mentioned in the tutorial. The drivers do not have an exe. I can not manually install the drivers because the device is not recognized by the PC at all, it does not show in the Device Manager. Moving forward ... downloaded and installed the Sony Xperia Companion software, it also does not recognize the device at all. The flashtool you linked also does not see the device at all.
23/016/2019 00:16:53 - INFO - Device disconnected
There is no flashmode or fastboot mode possible, the device does not respond to any buttons, any charge, or mean glances. Any last thoughts before I cut my losses and throw it away for a XZ1 compact?
apsommer said:
There is no flashmode or fastboot mode possible, the device does not respond to any buttons, any charge, or mean glances. Any last thoughts before I cut my losses and throw it away for a XZ1 compact?
Click to expand...
Click to collapse
Don't throw the phone away!
I fear I was not explicit enough:
1. keep the phone off and disconnected
2. click on the Flash icon, choose the firmware
3. choose flashmode
4. press volume down and only then connect it to the PC
If even this alternative service mode has been wiped, then the only possibility left is EDL. For that, I'd go to a repair shop.
Antonio
apsommer said:
I downloaded the flashtool you linked, and also the XperiFerm and latest Z5C drivers as mentioned in the tutorial. The drivers do not have an exe. I can not manually install the drivers because the device is not recognized by the PC at all, it does not show in the Device Manager. Moving forward ... downloaded and installed the Sony Xperia Companion software, it also does not recognize the device at all. The flashtool you linked also does not see the device at all.
23/016/2019 00:16:53 - INFO - Device disconnected
There is no flashmode or fastboot mode possible, the device does not respond to any buttons, any charge, or mean glances. Any last thoughts before I cut my losses and throw it away for a XZ1 compact?
Click to expand...
Click to collapse
Hi,
Power off the phone : press volume up and power button. Wait 3 vibrations (if not, the phone is powered off).
Press first the volume up and plug the phone with the usb cable into your computer. If you see the blue light you can use Flashtool, if not... it's dead (for me)...
How to use Flashtool is another thing, blue led is essential.
You'd rather throw it away for a Xz2 compact and install Omnirom. You can find some used ones for good prices.
antonio.galea said:
Don't throw the phone away!
I fear I was not explicit enough:
1. keep the phone off and disconnected
2. click on the Flash icon, choose the firmware
3. choose flashmode
4. press volume down and only then connect it to the PC
If even this alternative service mode has been wiped, then the only possibility left is EDL. For that, I'd go to a repair shop.
Antonio
Click to expand...
Click to collapse
Thanks, Antonio. Step #4 causes no reaction in the phone, or the Flashtool. The software does not recognize the device and the phone remains unresponsive. It truly seems hard bricked to me. I live in Mexico ... this device is rare even in the US, the guys will have never seen it, and their approach to EDL is as good as mine. I'm pretty frustrated with this dead phone, I think it's time for a new one and to mark this as a lesson learned.
Raphos said:
Hi,
Power off the phone : press volume up and power button. Wait 3 vibrations (if not, the phone is powered off).
Press first the volume up and plug the phone with the usb cable into your computer. If you see the blue light you can use Flashtool, if not... it's dead (for me)...
How to use Flashtool is another thing, blue led is essential.
You'd rather throw it away for a Xz2 compact and install Omnirom. You can find some used ones for good prices.
Click to expand...
Click to collapse
Thank you. No blue light under any button combination, charging cable, outlet, software, mean glances, etc. My next one is XZ1 or XZ2 ... I'll take your advice into consideration, the XZ2 has better specs but of course its +$100. I like to think of myself as a capable engineer, but destroying this Z5C has made me pretty hesitant to attempt the same process on a new phone. Everyone seems to agree that hard bricking this device is near impossible, however I beg to differ as look at this dead one on my desk.
apsommer said:
Thanks, Antonio. Step #4 causes no reaction in the phone, or the Flashtool. The software does not recognize the device and the phone remains unresponsive. It truly seems hard bricked to me. I live in Mexico ... this device is rare even in the US, the guys will have never seen it, and their approach to EDL is as good as mine. I'm pretty frustrated with this dead phone, I think it's time for a new one and to mark this as a lesson learned.
Click to expand...
Click to collapse
Ouch - a real pity.
It really seems you succeded in wiping out all possible accesses for the Sony bootloader. Do you mind me asking how you managed that? I'd like to avoid doing the same mistake.
Qualcomm EDL mode is surely there, but you will need to open the phone and the software for that approach is not freely available (or at least I was not able to find it).
Antonio
antonio.galea said:
Ouch - a real pity.
It really seems you succeded in wiping out all possible accesses for the Sony bootloader. Do you mind me asking how you managed that? I'd like to avoid doing the same mistake.
Qualcomm EDL mode is surely there, but you will need to open the phone and the software for that approach is not freely available (or at least I was not able to find it).
Antonio
Click to expand...
Click to collapse
I don't remember the exact sequence, but "fastboot erase" was used on the "bootloader" and "recovery" partitions, then the phone was unplugged. This left the system with no start sequence ... when I depleted all the battery charge it simply wouldn't respond to anything and has since been lifeless. I'll pry it open and take a look at the internals just for fun and to get one last squeeze of value from it. I also plan to bash it with a hammer which will be particularly satisfying.
apsommer said:
I don't remember the exact sequence, but "fastboot erase" was used on the "bootloader" and "recovery" partitions, then the phone was unplugged.
Click to expand...
Click to collapse
You can safely overwrite boot, but never ever touch the bootloader. The bootloader is responsible for starting all the various programming modes, as well as passing on execution onto the kernel start during normal boot.
BTW, I don't think there is any reason at all for erasing partitions - when you overwrite them with your own data they will end up being clean anyway.
I also plan to bash it with a hammer which will be particularly satisfying.
Click to expand...
Click to collapse
While I can understand your frustration, that would be quite silly. Even if it has no value to you, it's still recoverable for anyone with the skills and tools - try to sell it instead, if anything it could be used for spare parts.
Antonio
antonio.galea said:
You can safely overwrite boot, but never ever touch the bootloader. The bootloader is responsible for starting all the various programming modes, as well as passing on execution onto the kernel start during normal boot.
BTW, I don't think there is any reason at all for erasing partitions - when you overwrite them with your own data they will end up being clean anyway.
While I can understand your frustration, that would be quite silly. Even if it has no value to you, it's still recoverable for anyone with the skills and tools - try to sell it instead, if anything it could be used for spare parts.
Antonio
Click to expand...
Click to collapse
Yes, I learned my lesson with "fastboot erase bootloader". I'd be happy to sell it for parts, what website would you recommend for listing it?
apsommer said:
Yes, I learned my lesson with "fastboot erase bootloader". I'd be happy to sell it for parts, what website would you recommend for listing it?
Click to expand...
Click to collapse
I'm trying to find out more information about the emergency recovery mode for Z5C - I might be able to find out a way to recover your phone. If I'm successful (be warned, it's a big if - so please don't count on it), you could sell it as a working phone instead of as a brick.
First problem, I don't know how to enter EDL mode on the Z5C: but I hope an EDL cable could work. I've ordered one for testing, since it's an useful tool for recovering a lot of other phones too - it will take a while to deliver, so don't hold your breath. You could also join me in my experiments (after all, you have nothing to lose) by ordering one yourself (you can find cables for as low as 3$).
Second problem, the software tools. Given the ubiquity of Qualcomm chips, apparently there are quite a few available. In the opensource arena, I've found those:
https://github.com/96boards/documentation/blob/master/consumer/guides/qdl.md
https://github.com/openpst/sahara
https://github.com/bkerler/edl
Third problem, finding the signed binaries you have erased from your phone. I guess they can be extracted from my own device quite easily - they are on eMMC after all.
For an in-depth discussion of EDL mode, geared towards its (in)security, I've been reading Aleph Security articles here.
Antonio
apsommer said:
Thank you for the response, I was about to throw the phone away. Can you be a little more specific? I see your post here regarding a rebooting loop with red light flashing. However, I don't have any response from the phone whatsoever ... nothing on the screen, or led in top right. It does not accept a charge from 1A or 2A source, it is literally a paper weight right now. I need to "jump start it" or something of this nature. It won't charge at all.
Click to expand...
Click to collapse
Hey again, sorry for late reply. Work...
My issue seems totally unrelated to yours. My problem was that I was doing the flashing wrong, instead of just flashing the entire .zip I flashed boot file etc and this is what started the issues with not taking charge, BT wasn't working, wifi etc. But I had more juice in the phone since you want to have quite a bit before doing flashing, but I read your post about discharging it.
If you can't revive it, don't fear rooting and flashing, just make sure to read and to take all steps necessary. I kinda messed up my Z1C and I didn't do any changes to my Z5C until recently. Well, maybe a year now, just because of that occurrence.
antonio.galea said:
I'm trying to find out more information about the emergency recovery mode for Z5C - I might be able to find out a way to recover your phone. If I'm successful (be warned, it's a big if - so please don't count on it), you could sell it as a working phone instead of as a brick.
First problem, I don't know how to enter EDL mode on the Z5C: but I hope an EDL cable could work. I've ordered one for testing, since it's an useful tool for recovering a lot of other phones too - it will take a while to deliver, so don't hold your breath. You could also join me in my experiments (after all, you have nothing to lose) by ordering one yourself (you can find cables for as low as 3$).
Second problem, the software tools. Given the ubiquity of Qualcomm chips, apparently there are quite a few available. In the opensource arena, I've found those:
https://github.com/96boards/documentation/blob/master/consumer/guides/qdl.md
https://github.com/openpst/sahara
https://github.com/bkerler/edl
Third problem, finding the signed binaries you have erased from your phone. I guess they can be extracted from my own device quite easily - they are on eMMC after all.
For an in-depth discussion of EDL mode, geared towards its (in)security, I've been reading Aleph Security articles here.
Antonio
Click to expand...
Click to collapse
Wow, you're a true engineer, never give up! Consider my phone part of your testing devices. Please confirm this is the correct EDL cable to purchase for the Z5C: EDL cable for all Qualcomm phones ... It will take a few weeks to get in my hands.
apsommer said:
Wow, you're a true engineer, never give up!
Click to expand...
Click to collapse
Hello, got my cable - but I've not been able to make it work so far. It could be because I need Windows and specific drivers, I'll look into some more. But yes, when it's fun I never give up
Antonio
Hi all,
my Gylaxy M30s rebooted itself yestarday, and now is stuck at the very first screen (the one showing "SAMSUNG Galaxy M30s" in the center and "Powered by android" at the bottom).
Vol down + power results in a reboot attempt (screen goes black, vibration), but the phone is stopping at the same screen again.
I am not able to turn the phone off.
Switching from Vol down to Vol up immediately when screen goes black does not enter recovery mode.
Vol down + power while charging sometimes leads to the charging symbol being shown on the screen, but without the percentage in the middle.
Charging over night did not help.
The phone cannot be connected to a Win PC.
Any suggestions what I can try?
Thanks,
Alchemist
Try volume down+volume up and while pressing those buttons, plug your phone into your computer. Tell me the results of that.
Nothing happening...
I mean trying those combinations immediately after using power+ volume down to reboot.
What did you do with your phone? Died suddenly when normally using?
Yes, phone died during normal usage.
Ah, I see - a screen comes up warning me that downloading a custom OS might harm the phone.
Also, the PC makes this "USB connected" sound when I then press Vol up, but I do not see a new drive connected, I think.
I am slightly optimistic now?
Press volume up.Then install Samsung usb drivers(search on Google)
Ugh, just wanted to do this, but now the phone is completely dead. No response to any button or charging. Will hang it on the charger for a few hours, but my optimism is gone...
OK, now it works again. I am in the screen with the colourfull stuff and the phone waits for some download.
Driver is installed on PC. Is there anything supposed to happen - the phone is still not accessible via PC, or is it?
Install Odin (search in Google 'odin samsung' and download)
Download stock firmware(android os) at www.samfw.com , after downloading you will see files like AP-M505xxxxxxx.tar.
Select, from the stock ROM AP-M305xxxxx.tar for AP in odin CSC-M305xxxxx.tar for CSC, and so forth then click start .
OK. All data will be lost, right? Is there some way to access the internal storage to rescue some files before flashing the new firmware?
Sorry to tell you that you cannot have data restored bad news for you sorry
Sorry. If you only see one file(make sure it is .tar or .tar.md5 file) after you extracted the .zip firmware, install it to the AP slot.
Any chance I could fix this issue with tools like dr.fone, UltFOne, ReiBoot?
I do not have any experiences with these - no idea if the just want to make money with desparate customers? ...
These could possibly brick your phones even more ( anyways flashing with Odin could also brick your phone). However, it in some cases can fix your device.
If you HAVE to have your data back and you don't mind paying, visit a service center and tell them: 'Hey my phone died and i HAVE to have the data back '.(I know, your warranty is expired probably, but they might still do the things for you with paying.)(if those stores closed during lockdown then I don't know any way to fix it.)
OK, another thing I have observed: The screen goes black after about 30 sec to 5 min when not charged - the shorter it was charged, the quicker the screen goes black. Buttons do nothing when screen is black. When reattached to charger, phone tries to boot and is then stuck at said screen - no button pressing needed for the phone to try to start. The longer the phone has been without charger, the longer it takes until the phone tries to boot.
Maybe it's just the battery that is dead - or would the phone with a dead battery boot normally when attached to charger?
If that is the case, open up your phone, put in a replacement battery, and try to boot up(yes, you need to. it will be a frustrating process.). Your phone could be having a faulty battery and nothing else, to cause this issue.
Im having the same problem mentioned above. The samsung service centre says to replace the motherboard which costs almost half the price of the actual phone..
Mystic_Jamdam said:
Im having the same problem mentioned above. The samsung service centre says to replace the motherboard which costs almost half the price of the actual phone..
Click to expand...
Click to collapse
Truth to be told: The guy in the repair shop opened the phone and wanted to change the battery - when he saw that water must have come into the phone, corroding the motherboard. So yeah, all data lost, but... no backup, no mercy. I now have set up a NAS for all computers and devices in our family... ;-)
If it really is a hardware problem then the quality must have been really bad.