Been trying for hours now to try and sort out an issue I am having. My S4 is damaged, the phone works but the screen and digitizer is broken. I want to check a few sms messages, access and control the phone from my PC and basically make a complete clone/image of my phone. I cannot for the life of my figure out how to do this.
I use windows 7, I have installed SDK tools, have ADB/fastbook etc. Device isn't found with ADB. Spent hours reading information about installing correct drivers, which I have done. No luck what so ever. The phone is not rooted, developers tools is not on, usb debugging is not on either.
I am starting to think this is a lost battle as I cannot sort this out.
Any ideas?
Thanks
Bump.
Anyone? Is there no way to solve this problem? Tearing my hair out.
Best bet (given ADB doesn't work) would be to root the phone & get a custom recovery on (via Odin; this is might be very difficult if you can't somehow have the phone & PC recognise each other - you don't need to have had debugging on though) then do a nandroid backup (someone using the same recovery/version might be able to walk you through the button presses.
What S4 variant (model number) are we talking about ?
MistahBungle said:
Best bet (given ADB doesn't work) would be to root the phone & get a custom recovery on (via Odin; this is might be very difficult if you can't somehow have the phone & PC recognise each other - you don't need to have had debugging on though) then do a nandroid backup (someone using the same recovery/version might be able to walk you through the button presses.
What S4 variant (model number) are we talking about ?
Click to expand...
Click to collapse
GT-I9505 is the model number that is displayed behind the battery. The screen is broke and so is the touchscreen (completely black). I tried to figure out via ODIN but that wouldn't recognise the phone either. I assumed you'd need to boot in recovery/download mode but because I cannot see anything on screen, when I do the volume down, home and power thing I do not know what to do next so the phone boots up normally. I know this because I have unread SMS and when phone loads my SMS tone goes off.
Really not sure how to get around this.
You're going to have to get it into DL mode somehow (don't need to use home button on S4, just vol down/power); try a jig. Once you've done that, then you need to get the phone & PC to recognise each other. If you're having problems with that, prepare to continue to do a lot more reading/trying stuff if you're having PC-side driver issues (there's a lot of threads on here re: the issue). There's also an 'Odin troubleshooting' guide in S2 General by Hopper8 which is worth looking at as much of the stuff he suggests also holds true for the S4 (except the firmware stuff, which is obviously different).
There's not going to be any quick & easy in this instance, I'm afraid. It's going to be hard work.
Edit - Also..USB board/port on the phone might also be damaged, so when you reach the point of having tried everything on the PC-side & everything you can possibly try on the phone-side, replace the USB board/port on the phone. This is quick/easy/cheap (<US$20) to do & might just enable you to get things done where everything else has failed.
Extra edit - And...A jig working (getting you into DL mode) or not is probably a good test of whether the USB board/port on the phone is still good; I.E if the jig works, the board/port is probably still good, if it doesn't, the board/port might be shot as well.
The USB is fine because when I plug the phone in when in normal boot it recognises the data storage. I will try to boot in DL mode. Are there any gestures my S4 will do when booting in DL? Vibrations? As I cannot see anything on screen that will indicate it's worked. I think that once I can get the phone to work with ODIN/ADB I will be good to go as I am relatively tech savvy.
Nope. You're going to by flying blind so far as having no screen/no vibrations in DL mode goes. You're going to be relying on the jig working, and once you hook it up to the PC & fire up Odin, you'll know straight away whether you've got a successful connection up & running (as screenshots in the many Odin guides on here will show you).
I see, will just have to keep trying.
So on the S4 it's hold power and volume up, then wait? or do I need to press anything else afterwards? Or is it power and volume down?
Thanks
No luck with download mode. Girlfriend has a note 2, and her method is Vol down, home and power button. Screen comes up almost immediately with confirmation. Volume up needs to be pressed to confirm. Tried to replicate with S4, no avail.
No luck with starting S4 in download mode. I have followed video on youtube. Supposed to be Vol Down, Home and Power button. Wait till vibrate and warning screen, then press up. Because I cannot see the screen I cannot see the warning screen. But I Hold for 4 seconds, release just after vibrate and then press up, but phone seems to boot up in normal mode.
Ok, finally in download mode, now what? I know it works because it installed new drivers and device manager states a samsung modem. Need to try and clone and do what I need to do ASAP and taking to store tomorrow to exchange for new one.
Any last minute ideas?
Thanks
ODIN3 v1.85 shows a yellow box, this is good right? I downloaded CWM from http://galaxys4root.com/clockworkmodtwrp-recoveries/
What do I need to do next, do not want to make this worse, I just need to enable usb debugging or at least be able to use adb, I am good to go from there
Only a few hours left? Surely someone knows what Flash I need to do to allow me adb access???
Right, go into recovery mode...adb now works.
What do I need to do to enable debugging?
Edit:
I can't get adb to work... error: closed
any ideas
If you cant get adb to work in recovery then youre out of luck.
Incase this happens with new phone, always have a remote access app like Cerberus installed. MightyText is a pretty nice app too.
I see, ok no worries. Thank you anyways
I think I'm bricked. My shield is stuck in a simple bootloop and should be considered a softbrick. I can't seem to get into fastboot. Forget adb, that's not responding, but I'm still getting the android boot logo. I've tried so many ways. Holding the button, mashing the bettenbetter, plugging at the brick, power at the console, just about everything. Anyone figure out how to get into fastboot with hardware? If so, please let me know or I'll be throwing this out. It just won't seem to respond to fastboot. Such a shame.
EDIT: Android figured it out somehow and just booted, but I'd still like to know how to get into fastboot for when I'm not so lucky next time. Or any other way to get into recovery.
EDIT 2: Thought I posted this in troubleshooting. My mobile data was lagging somethinf fearce. Sorry.
It can be tricky mate. The way I did it was to unplug the device and then put the power cable back it. As soon as you plug the power cable back in hold the power button down until the fastboot menu appears. It took me a few tries. Of course if you have adb working the easiest way is "adb reboot bootloader"
baileyjr said:
It can be tricky mate. The way I did it was to unplug the device and then put the power cable back it. As soon as you plug the power cable back in hold the power button down until the fastboot menu appears. It took me a few tries. Of course if you have adb working the easiest way is "adb reboot bootloader"
Click to expand...
Click to collapse
I have done it once before, but it didn't work the way that their confusing instructions said. I'll give that a shot though. When android just flat out won't boot enough to access ADB, it can be problematic.
kdb424 said:
I have done it once before, but it didn't work the way that their confusing instructions said. I'll give that a shot though. When android just flat out won't boot enough to access ADB, it can be problematic.
Click to expand...
Click to collapse
It certainly doesn't help that there isn't a physical button on the Sheild, so your not absolutely sure your pressing in the right place after re-inserting the power cable.
In my experience the whole button is sensitive, bit that's still a pain. I have no problems booting my phone to recovery or fastboot, but that's just nuts. Oh well. Hopefully teh learned something as I'm sure their techs are complaining too. It is a consumer device, so I guess I can't be too mad, but still, they expect us to reflash before an RMA when needed sometimes, and that's not fair to ask with thes device lol.
I have the same issue here. I was able to get in fastboot hardware wise a bunch of times before. Now I think the device is done. I've tried every combination. What's weird is I did get a flicker of the bootloader continuing once. What could have changed that the bootloader is not responding anymore? How did you get lucky, let it sit there loading for a day? I've tried to see if fastboot commands can reboot the bootloader when I plug it in timing it correctly. So frustrating.
Yesterday from many many trying times I did it only once and don't wanna go cross again and don't ask me how I don't know how and still don't know how. I did everything by "book/instructions" finally give up and just randomly (panicly ) pressing / holding finger on it, power on / off...and then somehow bootloader screen appear. That should be fix by Nvidia
Sent from my SM-G925K using XDA Free mobile app
---------- Post added at 09:58 AM ---------- Previous post was at 09:49 AM ----------
I hope some developers out there will create some magic solution how enter easily in bootloader mode, like using micro sd ports some modded scripts or usb ports where in plugged in mode console entering bootloader mode or recovery etc.
Sent from my SM-G925K using XDA Free mobile app
Glad I'm not the only one having issues. I've been trying everything with no luck. I'll give it a few more tries and then It's going back. Following Nvidia's instructions is BS. There is obviously an issue going on here that needs to be fixed.
mow4cash said:
Glad I'm not the only one having issues. I've been trying everything with no luck. I'll give it a few more tries and then It's going back. Following Nvidia's instructions is BS. There is obviously an issue going on here that needs to be fixed.
Click to expand...
Click to collapse
It will definately go into fastboot, it's just a matter of timing. It's really tight. In the end I stopped following their directions and just tried a bunch of random stuff. I tried so much I don't know what worked, but doing what they said wasn't working for me.
kdb424 said:
It will definately go into fastboot, it's just a matter of timing. It's really tight. In the end I stopped following their directions and just tried a bunch of random stuff. I tried so much I don't know what worked, but doing what they said wasn't working for me.
Click to expand...
Click to collapse
Same here - finally haotic random pressing / unplugging and at the end done only once
Sent from my SM-G925K using XDA Free mobile app
Im also in the same boat
Just tried to flash stock 2.1 and Full android 2.1 and now the shield wont boot into anything
Im trying the hardware bootloader method but thats not working so far.........ive just unplugged everything, and giving it a while before i keep trying.........i suspect i might have to try rma......that'll be fun...........(im implying, that it wont)
Same here, mine is stuck on on screen and stating production fused , and couple of options like recovery kernel forced recovery, none works fallowed nvidia instructions , tried downloading SDKS And followed commands nothing working , as well tried holding power button , and unplugging and nothing works, I will try what you guys did and see maybe I get lucky somehow
I have a Shield TV power device but the screen is black and I can not go to the Hardw
I have a Shield TV power device but the screen is black and I can not go to the Hardware Bootloader Access:crying::crying::crying:
Same here - when I plug int he power the green light comes on for about half a second then goes off.
Quite infuriating really.
I get a screen that sasys "continue booting..." and then it loads normally do I need to let go once it says this or should I continue to hold?
Good evening and thank you for taking the time to help people in need,
This will surely be my last thread if there is a solution.
After chaining problems related to root, my Oneplus 6t makes a blackscreen with each complicated queries like downloading 13 applications or loading an icon in good quality (sarcasm) and I have to restart it by pressing vol + and power when the black screen appears to block my phone.
I do not think that clarifying the cause would help you.
I hope I have been quite understandable and avoid the wrong answers, I add that I have already reset the phone..... twice in the phone settings.
My final questions are as follows.
How to reintroduce my OnePlus 6t to 100%?,
Will removing the root will stop this performance bug? If yes, how ?,
How the unroot magisk if I can't open the app ?
There is a message for a update and if I accept or if I refuse nothing happens there is only a big black line honrizontal that passes quickly from bottom to top.
I have already tried to unroot with supersu it does not work and magisk stays with his app that cocmes back whatever happens.
Thank you in advance.
EDIT:
I have a new problem. I managed to press uninstall and now I have black screen and the power bouton makes vibrate.
I should never have rooted and I refrain from screaming with rage as it was based on a stupid idea.
If anyone can help me I would be extremely grateful.
NOW:
Now it's bricked up on the screen where there is the warning that the phone is rooted and that it can not guarantee the integrity of the phone.
The buttons have no effect and there is not vibration.
For now, I'm waiting for him to discharge.
I think I have found the solution.
You have to hold all buttons simultaneously and if it does not work you still have to try, I tried 3 three before succeeding and I'm sure it's off and it's not a black screen. And I press the buttons of volumes simultaneously and I connect the phone at the same time to my pc normally a message appears on the pc and the phone is visibly off but it is in EDL mode. Then download the program 6T_MsmDownloadTool on the pc. But for the rest .... there is the message that has appeared but it is not recognized on the software but I think it's because my pc because he did not recognize my OP6T when ordering when I rooted my phone so I tried the other pc more powerful and it worked. So I'll let you know if it works for the other pc more powerful and thanks for the help (sarcasm).
And it works on my most powerful computer.
After several panic attacks and rage, I tell myself that the root is useless except for ads. For the rest of the applications it is only used to save time but there is other way.
I would like to publish insults because this is the last time I visit this type of site, except to download the Gcam APK, but my thread could be useful for those who wish to reintroduce their OnePlus 6T to 100%.
I think you should use the msm tool to download full stock room and flash it..I don't know the details but look in the general forum that should take care of your problem.sorry you are having trouble
It's okay you need to read.
Thanks for the tip, + kudos for such polite. Good day
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
a) phone stuck on the screen as seen here
b) pressing volume down and power button for eight seconds or so simply restarts and brings me back to this same screen
c) I'm not getting the pink circle LG logo thing in the interim (between screen going blank and coming back up). The phone just boots up to this particular screen without anything in between, except for black screen for brief second
d) The phone does not have an unlock bootloader because this model HD870DS is not unlockable
Does anybody know how to force shut this phone down? Do I have any other alternatives to make this phone running again?
My only hope is that if I can somehow, with the help from the good folks here, shutdown the handset so that I can use the LGUP to flash the original KDZ file.
Any help would be appreciated.
Try vol down + power for about 5-6 seconds. Longer will soft reboot. Else wait for battery to run out.
Fixed! I had to force into download mode and then automatically have the LG Bridge detect an 'update' and download it. LGUP does not and did not work and neither did/does Uppercut in trouble shooting, if anyone is interested in February of 2020. I know what I am talking about. With so much development here at XDA and this phone not aging so well (sporadic Pie updates around the world, etc), all the DLL files, LGUP versions, and Uppercut versions vary from 1.0 to 1.14 to 1.16 on the web (combined). With no dedicated developer/maintainer of pooling these resources AND updating them periodically, it is pretty much up to one's own, on which combo of LGUP-DLL--UPPERCUT to use and which kdz to download, etc. Lot of misinformation exists out there as to which file you should or should not use. That is my two cents on the situation involving LG G6, here at XDA and elsewhere. Those that got updated to Pie (India was latest) are in luck. Others, you can go to hell, as far as LG is concerned.
Anyways, for those who might/can/could end up EXACTLY in my position, here is how to troubleshoot
a) if you are on bootloop like I did, when on that screen, press Vol down and power simultaneously for eight to ten seconds until the screen turns black. Then...
b) AS SOON AS IT TURNS BLACK, let go of both buttons and simply keep the Vol Up button pressed
c) you will see the blue dotted 'download mode' start
d) connect your cable to the lappy or desktop
e) here is the most imp part--you DO NOT need anything other than LG Bridge to restore your phone the correct manner i.e. if you are a noob and don't want to spend more than 72 hrs seeking the right amount of info and right type of issue pertaining to you
f) how to do it: https://www.youtube.com/watch?v=JNAvoq3Dr6U. Follow this guy's instructions. He explains well and to the tee. LG bridge will automatically download the requisite kdz file for you. You do not have to download anything.
Finally, worth mentioning, a certain junior member here at XDA (with three posts since 2018; my bad that I did not read up on his reputation before following his/her instructions on how to recover my bootloop) on this very forum, managed to slip in an .msi file extension that was actually a malicious malware that crashed my computer. Fortunately, I have a backup system to work with, so I got away with that. Keep your eyes peeled for your best solution. Keep reading and researching and never give up. It takes time but there is rarely a thing as hard brick these days...