Related
My HTC Hero was a dream to mod. I plugged it in, ran some ADB, and it worked like a charm. I flashed whatever I wanted whenever I wanted, and it worked fine with my computer which is running 64bit Win7.
Now the Samsung Epic... this is disappointing. ADB doesn't work any more. It says there are no devices attached and I can't mount my SD Card through the phone to my computer. I can't get the drivers to work properly. I've tried reinstalling the "proper" ones from the clockwork mod thread and also reinstalling the ones that windows update wants to install.
Nothing works. Modding this phone is a nightmare and now it doesn't work with my computer at all. ADB used to work, kind of. Now it doesn't even detect the phone.
Samsung did a bad job. I love the screen and the blazing fast hardware, but the difficulty with modding is ridiculous.
If anyone has any suggestions, I'm game. But if I can't get full control over my phone via command prompt like I could with my Hero, I'm going back to HTC before next week.
Leon H said:
My HTC Hero was a dream to mod. I plugged it in, ran some ADB, and it worked like a charm. I flashed whatever I wanted whenever I wanted, and it worked fine with my computer which is running 64bit Win7.
Now the Samsung Epic... this is disappointing. ADB doesn't work any more. It says there are no devices attached and I can't mount my SD Card through the phone to my computer. I can't get the drivers to work properly. I've tried reinstalling the "proper" ones from the clockwork mod thread and also reinstalling the ones that windows update wants to install.
Nothing works. Modding this phone is a nightmare and now it doesn't work with my computer at all. ADB used to work, kind of. Now it doesn't even detect the phone.
Samsung did a bad job. I love the screen and the blazing fast hardware, but the difficulty with modding is ridiculous.
If anyone has any suggestions, I'm game. But if I can't get full control over my phone via command prompt like I could with my Hero, I'm going back to HTC before next week.
Click to expand...
Click to collapse
Every time someone on here says that ADB doesn't work it has ended up being their computer that is the problem. Either they didn't install the drivers correctly or there is something else wrong. I suggest you try it on a different computer. The majority of us have never had a problem with ADB and as an ex-Hero user I think the epic works just as well over command line.
richse said:
Every time someone on here says that ADB doesn't work it has ended up being their computer that is the problem. Either they didn't install the drivers correctly or there is something else wrong. I suggest you try it on a different computer. The majority of us have never had a problem with ADB and as an ex-Hero user I think the epic works just as well over command line.
Click to expand...
Click to collapse
I'm working on getting a fresh install of 32bit WinXP, but I don't see why it doesn't just work on my Win7 install. I've tried it on XP before with similar (non-working) results, but I'll give it a foolproof trial and try to troubleshoot if it's the computer end or the phone end.
Leon H said:
I'm working on getting a fresh install of 32bit WinXP, but I don't see why it doesn't just work on my Win7 install. I've tried it on XP before with similar (non-working) results, but I'll give it a foolproof trial and try to troubleshoot if it's the computer end or the phone end.
Click to expand...
Click to collapse
ADB worked on my Win 7 64bit laptop when I was rooting my Epic. Had 0 problems.
PEBKAC imo.
Leon H said:
My HTC Hero was a dream to mod. I plugged it in, ran some ADB, and it worked like a charm. I flashed whatever I wanted whenever I wanted, and it worked fine with my computer which is running 64bit Win7.
Now the Samsung Epic... this is disappointing. ADB doesn't work any more. It says there are no devices attached and I can't mount my SD Card through the phone to my computer. I can't get the drivers to work properly. I've tried reinstalling the "proper" ones from the clockwork mod thread and also reinstalling the ones that windows update wants to install.
Nothing works. Modding this phone is a nightmare and now it doesn't work with my computer at all. ADB used to work, kind of. Now it doesn't even detect the phone.
Samsung did a bad job. I love the screen and the blazing fast hardware, but the difficulty with modding is ridiculous.
If anyone has any suggestions, I'm game. But if I can't get full control over my phone via command prompt like I could with my Hero, I'm going back to HTC before next week.
Click to expand...
Click to collapse
Ahh.. Why blame Samsung for having a phone that that is "difficult to mod". They never wanted you mod it, funny how you mentioned the awesome screen and "blazing fast hardware" in the same paragraph though, but still call it a bad phone.
ADB works just fine if you install the correct drivers.
Not insulting your decision to choose the Evo, they are both awesome, but the Evo won't save you from not knowing what you're doing.
PEBCAK.
First google search of the day = pebkac; good one!
TheDub said:
Not insulting your decision to choose the Evo, they are both awesome, but the Evo won't save you from not knowing what you're doing.
Click to expand...
Click to collapse
But maybe the Evo will save me from this driver fiasco. I've tested the phone on WinXP and Ubuntu now, and ADB works on both. But for whatever reason, the drivers on Windows 7 are not working. I've uninstalled them and reinstalled drivers from three or four different venues now.
Leon H said:
My HTC Hero was a dream to mod. I plugged it in, ran some ADB, and it worked like a charm. I flashed whatever I wanted whenever I wanted, and it worked fine with my computer which is running 64bit Win7.
Now the Samsung Epic... this is disappointing. ADB doesn't work any more. It says there are no devices attached and I can't mount my SD Card through the phone to my computer. I can't get the drivers to work properly. I've tried reinstalling the "proper" ones from the clockwork mod thread and also reinstalling the ones that windows update wants to install.
Nothing works. Modding this phone is a nightmare and now it doesn't work with my computer at all. ADB used to work, kind of. Now it doesn't even detect the phone.
Samsung did a bad job. I love the screen and the blazing fast hardware, but the difficulty with modding is ridiculous.
If anyone has any suggestions, I'm game. But if I can't get full control over my phone via command prompt like I could with my Hero, I'm going back to HTC before next week.
Click to expand...
Click to collapse
I had a similar problem but instead, I blamed Windows 7
Install PDAnet.. pick the appropriate device, then you can have full control over your "blazing fast hardware" P.O.S.
PEBKAC .. LMFAO...
Leon H said:
But maybe the Evo will save me from this driver fiasco.
Click to expand...
Click to collapse
yeeeeeaaaahh... that'll happen...
I've tested the phone on WinXP and Ubuntu now, and ADB works on both.
Click to expand...
Click to collapse
But for whatever reason, the drivers on Windows 7 are not working. I've uninstalled them and reinstalled drivers from three or four different venues now.
Click to expand...
Click to collapse
To kinda go along with my previous post, it appears as though ITS NOT THE DAMN PHONE...
Did you read what you posted ??? seriously... honestly ???.. it's not ur phone.
daddymikey1975 said:
yeeeeeaaaahh... that'll happen...
Click to expand...
Click to collapse
It did with the Hero. My experience with HTC drivers has been much better than Sammy drivers so far.
daddymikey1975 said:
To kinda go along with my previous post, it appears as though ITS NOT THE DAMN PHONE...
Did you read what you posted ??? seriously... honestly ???.. it's not ur phone.
Click to expand...
Click to collapse
I get that now, I was in the process of installing a new OS to test this. I blamed the phone at first, before I got around to testing it properly, but now I know where the problem lies.
I'm not blaming the phone anymore. It seems to work fine (besides the sd card mount, that will only work on linux). I'm blaming Samsung for their Windows 7 drivers. You can throw acronyms around all you want, but I think the problem is actually somewhere in how Samsung develops for 64 bit.
Also, I can praise the phone's hardware and curse the software. That's perfectly logical, by the way.
algorhythm said:
ADB worked on my Win 7 64bit laptop when I was rooting my Epic. Had 0 problems.
PEBKAC imo.
Click to expand...
Click to collapse
Thanks for your anecdote. Unfortunately, my setup is not working the same as yours. If you'd like to be helpful and tell me how you installed the working drivers, I'd appreciate it.
to OP, what you should know is, that even without any modding, and running on 2.1 , my epic will always be WAY faster than any evo.
now imagine how fast it is for me now, with my Quantum froyo...
I had the same problem with my phone not showing up on the computer, i know this may sound stupid but it works. I have 2 usb ports in the front of my computer and thats what i tired using for the phone it wouldn't work, so i plugged it in the back of the computer and now it works fine shows up everytime on my computer.. So i just bought a extra usb cord off ebay and have it constantly plugged in the back of the computer.
ericizzy1 said:
to OP, what you should know is, that even without any modding, and running on 2.1 , my epic will always be WAY faster than any evo.
now imagine how fast it is for me now, with my Quantum froyo...
Click to expand...
Click to collapse
I agree, that's why I bought the Epic in the first place. I just wish I could ADB into it with my Windows 7 machine that I'm using 99% of the time. The posters in this thread don't seem to understand that I like the phone, I just don't like the way it interacts with my computer.
Maybe their installation of 64 bit windows 7 can ADB fine, but that doesn't help me any. I wish I could get some help instead of being called an idiot. From my experiences, these Samsung drivers are worthless.
Phone good, drivers bad.
my intention was not to insult, just to convince you to keep it, and try to find the solution, which is what youre doing. wish i could help
ericizzy1 said:
my intention was not to insult, just to convince you to keep it, and try to find the solution, which is what youre doing. wish i could help
Click to expand...
Click to collapse
Haha, not to worry, you've been one of the most helpful in this thread. It's nice to be reaffirmed that my choice to go with a Samsung phone for the first time wasn't a mistake.
I'm just put off by all of the suggestions in this thread that the problem lies between the chair and keyboard instead of anything helpful about how to get these absurd drivers ironed out. Never had problems with HTC drivers, just sayin'.
You can get drivers to install better with one of 2 ways:
1) Use device manager to go to manually load the drivers in the 16_Shrewberry folder
2) Install Kies..even if it doesnt work it seems to install the drivers better
-------------
also if your using a desktop..back ports are more efficient.
gTen said:
You can get drivers to install better with one of 2 ways:
1) Use device manager to go to manually load the drivers in the 16_Shrewberry folder
2) Install Kies..even if it doesnt work it seems to install the drivers better
-------------
also if your using a desktop..back ports are more efficient.
Click to expand...
Click to collapse
That's what I'm talking about. Awesome information, I'll do some driver wiping and see how these methods work out from a clean slate. Thanks a lot.
SamsungEpic86 said:
I had the same problem with my phone not showing up on the computer, i know this may sound stupid but it works. I have 2 usb ports in the front of my computer and thats what i tired using for the phone it wouldn't work, so i plugged it in the back of the computer and now it works fine shows up everytime on my computer.. So i just bought a extra usb cord off ebay and have it constantly plugged in the back of the computer.
Click to expand...
Click to collapse
Good point! My 2 front USB ports are useless for connecting my Epic as well.
I installed the Samsung drivers for win 7 x64 from Sammys site and no driver issues here. Maybe try uninstalling the drivers you already installed and start from scratch?
bullet2300 said:
I installed the Samsung drivers for win 7 x64 from Sammys site and no driver issues here. Maybe try uninstalling the drivers you already installed and start from scratch?
Click to expand...
Click to collapse
I just got that step done through the driver program that Samsung installed, next I'm going to delete every trace in the Device Manager and try again with gTen's new methods.
I have a quick question. It seems that my tablet has lost its ability to connect through USB recently. I was unable to send pictures to the pc one day and have bought numerous cables to no avail. Looks as if, somehow, it just wont connect through usb. The original cable was acting up during charging anyway. My main question is, how do I root without the ability to connect to a pc? Is this at all possible? I was rooted before but since installing the newest update, 10.6.1.27.5-20130902, i noticed it wasn't rooted anymore.Am I pretty much SOL? BTW, nowadays the tablet wakes up and beeps like every other minute while charging. Dont know if its related. I wish I didnt do the update altogether.
Updating to the latest firmware (at last check) hides the developer options from the settings. Your problem might be that USB debugging was disabled or never was enabled.
To add developer settings back into the settings, you need to go into the "about tablet" in settings and tap the build number 5 or so times and then developer options should show up.
tayden812 said:
I have a quick question. It seems that my tablet has lost its ability to connect through USB recently. I was unable to send pictures to the pc one day and have bought numerous cables to no avail. Looks as if, somehow, it just wont connect through usb. The original cable was acting up during charging anyway. My main question is, how do I root without the ability to connect to a pc? Is this at all possible? I was rooted before but since installing the newest update, 10.6.1.27.5-20130902, i noticed it wasn't rooted anymore.Am I pretty much SOL? BTW, nowadays the tablet wakes up and beeps like every other minute while charging. Dont know if its related. I wish I didnt do the update altogether.
Click to expand...
Click to collapse
If its a cable problem, the cable only costs 5$ on amazon.
I'm on my third replacement cable already. Also, developer options are turned on. USB debugging is on as well. They charge fine but connecting them directly to any computer i have does nothing, almost like not plugging it in at all. Have tried on three different setups that worked before, Win 7 X64, Win 8 X64, Win XP X86.
tayden812 said:
I'm on my third replacement cable already. Also, developer options are turned on. USB debugging is on as well. They charge fine but connecting them directly to any computer i have does nothing, almost like not plugging it in at all. Have tried on three different setups that worked before, Win 7 X64, Win 8 X64, Win XP X86.
Click to expand...
Click to collapse
Disable the developer options and USB debugging. Windows may be trying to recognize the ADB instead of trying to mount partitions.
cmendonc2 said:
Disable the developer options and USB debugging. Windows may be trying to recognize the ADB instead of trying to mount partitions.
Click to expand...
Click to collapse
Tried that too. Doesn't seem to work either way.
Which worries me severely.
If you haven't already, install the google sdk adb drivers and see if that works, though from what it sounds like that's not the problem.
I'm thinking bad usb port on computer... try wireless adb if you can...
Sent from my TF300T
might be that the plug at your tablet got damage some how? maybe not fully damaged but partialy, do u have a dock? if you have you have any problem with it?
sorry for my bad english
Greetings!
Don't have the dock. Went to the Best Buy out here and they don't got it. Worst case scenario, my port is jacked up, can I still root without it? If so what steps can I take to do so?
depends on if you have a custom recovery like twrp if you do, then you should ok flashing supersu package, otherwise you are in the worst case scenario...
Sent from my TF300T using Tapatalk
Drahric said:
depends on if you have a custom recovery like twrp if you do, then you should ok flashing supersu package, otherwise you are in the worst case scenario...
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
THought so. The update completely killed my recovery as well. Doh! Thanks for the help guys.
If your still under warranty then you could get it fixed but from what sound like that wont help...
Take care.
Sent from my TF300T using Tapatalk
Hello all!
I'm just guna say, this might get long winded so, TLDR, Nexus 7 has no OS, I can get into the boot loader, the only thing I can actually do is get into TWRP v2.8.01, computer doesn't recognize it, can't get it to even see a flash drive that I've formatted to Fat32, now what?
For those who want some background. I got my N7 refurbished from ebay, if that matters at all. First thing I did was update it to Kitkat and root it. Installed some apps and was happy with it for a few months. About a month or so ago it stopped connecting to the Google Play Store. I wasn't bothered by it too much. But as time goes on, I find new apps and would like to use them. But obviously can not.
So, just to be safe, I wrote down all the apps I still had on it just in case they didn't want to load back up. Did a factory reset, still couldn't connect. Looked online and cleared caches and stopped services. Still didn't work. When I went onto the GPS, heh, on my computer it said that I had no devices so that was a clue of some sort. I could still go onto Youtube and log in and use it just fine. Just nothing in the store. So I decided to try something else.
What that was was to clear all my data with TWRP. Went to put in my email and password, couldn't connect, tried another wifi connection, still no go. I was able to use it, but the Play Store still didn't want to play nice. So in a bit of, "rage" we'll call it. I formatted it and now I'm where I am now. With a tablet that won't boot, just sit at the Google logo for up to 5 mins, as long as I've let it sit there for anyway. I have downloaded the Nexus Root Kit and tried to use that, but my computer won't even see my N7 now. In the bootloader or TWRP. So I can't even get anything onto it now.
So, what now? Do I have a bricked tablet that won't do anything or is there something an Android Guru out there can help me with? I'd like to keep it. I mainly used it to read and for various videos.
I have posted on forums.androidcentral but after a week and almost 300 views, no one has made any comments. I'm sorry for my ignorance if I'm missing something.
Thanks! I shall be hoping for good news.
So, does ADB recognize your tablet or not when you type "fastboot devices"?
I take it you mean shift+right clicking in the platform tools folder, open command window here, and typing that into the command prompt? If so, then no, it doesn't show up.
Waslow said:
I take it you mean shift+right clicking in the platform tools folder, open command window here, and typing that into the command prompt? If so, then no, it doesn't show up.
Click to expand...
Click to collapse
Can you go into the bootloader? Did you install the right drivers?
I can get into the boot loader just fine. Recovery sends me to TWRP 2.8.01. I've got the drivers from the Android SDK Manager, Rev. 11 apparently. Would that be any different from the standard drivers that get installed when you hook up the N7? Well, when it works?
Waslow said:
I can get into the boot loader just fine. Recovery sends me to TWRP 2.8.01. I've got the drivers from the Android SDK Manager, Rev. 11 apparently. Would that be any different from the standard drivers that get installed when you hook up the N7? Well, when it works?
Click to expand...
Click to collapse
That is correct. Use this: http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
And if doesn't work check in device manager.
If it works flash the latest factory image and then you will be good to go
I've already had that installed and set up and nothing pops up in the device manager. I've also tried all the usb ports on my computer to no avail.
Waslow said:
I've already had that installed and set up and nothing pops up in the device manager. I've also tried all the usb ports on my computer to no avail.
Click to expand...
Click to collapse
Then try the driver manual in nexus root toolkit
I can follow the instructions, but that doesn't resolve the fact that my computer can't see the Nexus .
go into device manager and delete every single entry that suggests anything to do with a phone, tablet, google device, nexus device, ETC. if you dont do that first, this will probably not work.
once you delete every single entry in there, go to the top command bar and somewhere in those menus is an option to show disconnected devices. delete everything again as above.
now, does your tablet still charge on the AC plugged into the wall? does it still charge when plugged into the computer usb? drivers are NOT required for usb to supply power. if so, the usb connector is probably OK. if not, your usb connector may be toast.
next, connect to the computer. does windows show any device connected? if not, try a different usb cable. report your findings back.
Sorry for the late reply.
There is nothing in the device manager related to my Nexus, which is odd, it had entries for flash drives, a camera, and my phone. All of which were in the disconnected devices. I got rid of just for the sake of it. Nexus charges just fine, either from the wall or any of my usb ports. If there is no way to make ANY computer see my Nexus, is it safe to say it's bricked?
I do have a cousin who's fluent in Linux if that means anything. I know that Android is a flavor of it. Might work better if both devices speak the same language. Grasping for straws I know.
Again, thanks for the help fwayfarer, GtrCraft, and Fobos531!
If I am reading right, you did NOT try a new USB CABLE yet, did you?
Try a known good USB cable, what I mean by that is try a cable you KNOW works for data transfer on another device and report back.
Connecting it to a Linux machine isn't going to make any difference in my opinion.
I have 2 cables and they transfer things just fine with my phone and my Kindle. I just downloaded everything off of both things, and transferred them back. No issue with the cables. I just popped open my Nexus and it looks like the usb connector and ribbon are fine. I did wiggle them a little but to no avail.
Pull the battery cable, smash the power button for a few minutes, reconnect and try again. It won't recognize a USB thumb drive in bootloader or recovery to my knowledge, BTW. I noticed you mentioned it not seeing one.
I unplugged the battery, hit the power switch for a while, plugged the battery back in, plugged the usb back in, nothing. Still nothing. I had read before that you can put the version of android you wanted on a flash drive. With an otg cable you could use that to update/install what you wanted.
You're probably right, I haven't tried using one in recovery for a long time. You didn't change the battery or anything recently did you?
Nope, haven't replaced anything in the Nexus. The only thing that I could think of that could be wrong is the usb connector. But for it to "fail" at the same time I formatted everything, too much of a coincidence.
Over a week bump
I ran into a similar problem about a year ago. Unless your tablet is connected to the computer you will not see it show up it the windows device manager. You should be able to connect your N7 to a work computer & it should go out for the drivers. If not, then you are Sol. You might have a blown main board.
The only thing my N7 does when I plug it in, is that it charges. That's the only thing I can get it to do. Well, this sucks. If I really have a bricked, or worse, tablet, it's still good for its screen and other bits.
Wondering where I was? me too.
Long time has passed since the start of this post (almost 4 years to be exact), so I decided to finalize this finally and release the fully fledged guide. Interesting how this all got here just because me, a dumbass, formatted his Lumia 920 in Mass-Storage Mode in 2016.
So let's start.
First of all, make sure your device isn't in QHSUSB_DLOAD. After all if it is, you can just flash with WDRT or Thor2, and not spend so much time on that (see my video on how to recover from QHSUSB_DLOAD).
Step 1
Disassemble your Lumia. You can use online video guides or just a service manual, doesn't really matter.
Step 2
Find the schematics of your device, most if not all are available online, afterwards, find R3209 resistor, yes, that legendary resistor which will force the device to QHSUSB_DLOAD.
Step 3
After finding it in schematics, find it on your device, approximately, since it is most likely under a metal shield, once found the approximate location, remove the shielding with heat, or if you are like me, start cutting it like death is coming.
Step 4
Now the interesting part, reconnect your phone's battery, this will ensure the phone isn't in any sort of state and is powered off. After, short the resistor to ground and connect your phone to PC while shorting, wait 2 seconds and remove the short.
Step 5
Voila!
Take a look at my video on how to recover from QHSUSB_DLOAD, and recover your Lumia using it.
Can you explain why you think this works?
I do this to Lumias that don't get detected but without cutting my USB cable. Pop the battery cable off the board and plug the cable into the phone. Then plug the battery cable ribbon back into the motherboard. Worked for me that way...
nate0 said:
Can you explain why you think this works?
I do this to Lumias that don't get detected but without cutting my USB cable. Pop the battery cable off the board and plug the cable into the phone. Then plug the battery cable ribbon back into the motherboard. Worked for me that way...
Click to expand...
Click to collapse
Sorry, but there are Lumias in the wild that doesn't support that way of connection.
They just don't get connected.
gmirz2005 said:
Sorry, but there are Lumias in the wild that doesn't support that way of connection.
They just don't get connected.
Click to expand...
Click to collapse
Right, I get that.
My question is more about if you understand what is happening when you trigger it to cycle on this way?
nate0 said:
Right, I get that.
My question is more about if you understand what is happening when you trigger it to cycle on this way?
Click to expand...
Click to collapse
When you make the edl cable and hold the button while turning the lumia on, the cable works like a short jig. As in every device, the CPU is "starting" first, there's command that is implemented in the CPU that switches the device to EDL mode but in this case, as the boot is dead, it switches to Qualcomm F006 Mode in other words, Qualcomm Modem Mode, which is normal for hard bricked devices.
I read a guide about unbricking a DragonBoard 410c but it's done using some base firmware files which we don't have.
gmirz2005 said:
When you make the edl cable and hold the button while turning the lumia on, the cable works like a short jig. As in every device, the CPU is "starting" first, there's command that is implemented in the CPU that switches the device to EDL mode but in this case, as the boot is dead, it switches to Qualcomm F006 Mode in other words, Qualcomm Modem Mode, which is normal for hard bricked devices.
I read a guide about unbricking a DragonBoard 410c but it's done using some base firmware files which we don't have.
Click to expand...
Click to collapse
Perfect! This is what I needed. Thanks.
My next question would be, how does this change for USB type c windows phone hardware or is it even applicable?
I'm assuming it should be in some way applicable, but it might depend on the device. So what might work for Lumias might not apply to Alcatel hardware etc. or vice versa.
I ask this because I have a few hard bricked devices either in QC USB modem mode or the like.
Another question would be can this method be used to boot a device into edl/USB modem mode even if it is not hard bricked yet?
nate0 said:
Perfect! This is what I needed. Thanks.
My next question would be, how does this change for USB type c windows phone hardware or is it even applicable?
I'm assuming it should be in some way applicable, but it might depend on the device. So what might work for Lumias might not apply to Alcatel hardware etc. or vice versa.
I ask this because I have a few hard bricked devices either in QC USB modem mode or the like.
Another question would be can this method be used to boot a device into edl/USB modem mode even if it is not hard bricked yet?
Click to expand...
Click to collapse
Answering to your Question 1:
No, this is not applicable for USB Type C hardware Windows Phones, as they run completely differently (which I didn't do research about).
Answering to your Question 2:
No, this only works with Lumias with Bootloader Spec A, and not with other brand manufactured Lumias.
Answering to your Question 3:
Yes you can enter the QHUSB_DLOAD mode if the device is not even bricked.
hi dude, i have a problem my computer detects the phone as QHSUSB_BULK, do you think this tutorial can work? regards
Finsther said:
hi dude, i have a problem my computer detects the phone as QHSUSB_BULK, do you think this tutorial can work? regards
Click to expand...
Click to collapse
I don't know at this moment as I really screwed up my Lumia (battery blown).
But I think it will...
Could this work without disconnecting the battery? What is the reason for that?
I have a Lumia 1020 with the problems listed in this link: https://forum.xda-developers.com/showpost.php?p=78640119&postcount=830
thor2 seems to be useless with the same "authentication error" and WDRT also doesn't work.
Edit: Also, why is your battery blown? Is it because of this process?
Tiago117 said:
Could this work without disconnecting the battery? What is the reason for that?
I have a Lumia 1020 with the problems listed in this link: https://forum.xda-developers.com/showpost.php?p=78640119&postcount=830
thor2 seems to be useless with the same "authentication error" and WDRT also doesn't work.
Edit: Also, why is your battery blown? Is it because of this process?
Click to expand...
Click to collapse
My Battery is blown due to incorrect removing (it was glued)
Yes you need to disconnect the battery so the device looses full power so then you can enter to DLOAD mode
gmirz2005 said:
My Battery is blown due to incorrect removing (it was glued)
Yes you need to disconnect the battery so the device looses full power so then you can enter to DLOAD mode
Click to expand...
Click to collapse
Do you happen to know how to get the RDC files for Lumia phones? It looks like if I get that, I can fix my 1020 without openning it up.
Tiago117 said:
Do you happen to know how to get the RDC files for Lumia phones? It looks like if I get that, I can fix my 1020 without openning it up.
Click to expand...
Click to collapse
Umm...
I don't know
gmirz2005 said:
Umm...
I don't know
Click to expand...
Click to collapse
This is as far as I've went: https://protobetatest.com/2018/08/2...ust-got-a-prototype-what-do-i-need-to-do-now/
Would my Lumia 1020 with JTAG eFuse blown and without RnD certification (UEFI secure boot is enabled) work with this method? Could this circumvent these issues and still flash my phone back to its original FFU?
Thanks.
Tiago117 said:
Would my Lumia 1020 with JTAG eFuse blown and without RnD certification (UEFI secure boot is enabled) work with this method? Could this circumvent these issues and still flash my phone back to its original FFU?
Thanks.
Click to expand...
Click to collapse
Yes
nate0 said:
few hard bricked devices
Click to expand...
Click to collapse
Ah, geez, man!.. No comment, heh; but, had to -just- comment!! Pfft.
kgbme said:
Ah, geez, man!.. No comment, heh; but, had to -just- comment!! Pfft.
Click to expand...
Click to collapse
[emoji16]
Not anymore though. Sold every one of them . Except one. Even sold all my prototypes...
Trying it but not working. Phone still boots to same message of "Unable to find a bootable option".
Laptop not recognizing anything. Maybe the cable connections aren't correct.
Will try to directly short the green and black cables to one another with hands.
Also bought a new battery so should probably charge it fully first.
Edit: not working. Phone continues to boot to "Unable to find a bootable option".
The only difference is that with the short circuit between green and black, the laptop doesn't detect the phone.
Flash efiesp.bin partition from another phone using wpinternals.
Hi all,
Have just started to connect my device so i can pull the patched boot image for my thread and it won't see the computer, tried on several laptops and nothing, no adb, no fastboot.
It charges just fine but does not show the android usb system notification.
Really annoyed by this as i'm kind of stuck.
I'm on 7.7 but on a custom ROM / Evo X 5.9.1, doesn't look like anyone else has this issue besides me, have seen the odd user complaining about the same thing but haven't seen any fixes come up], if anyone has any ideas then i'd be grateful to get your two cents.
Will test MSM but it's not looking good, fearing a return to oneplus as i do have a good unit with none of the issues anyones ever listed like green screen and overheating problems.
It's usually me helping others but this time i need you guys help
Check USB cable / clean the Charging port? sometimes it helps.
dewa5227 said:
Check USB cable / clean the Charging port? sometimes it helps.
Click to expand...
Click to collapse
Aye I've cleaned it up mate.
Tried different cables, I think EDL mode is working.
Means I could maybe return to OOS but it wouldn't let me back up..
Shame, I'm just downloading MSM now... Really annoyed..will give the usb socket another clean
dladz said:
Tried different cables, I think EDL mode is working.
Click to expand...
Click to collapse
well, it's a good sign , hopefully, it will be resolved out.
dewa5227 said:
well, it's a good sign , hopefully, it will be resolved out.
Click to expand...
Click to collapse
Yea I'm dreading it being hardware. Never had this issue on OOS.
I think it may be Evo X but I don't know.
Bad luck I guess
Cheers anyway.
So MSM did indeed work, it's booting now, obviously couldn't back up any of the info on the device so i'm super annoyed at that but so long as usb connectivity works then i'll be happy with that.
USB Connectivity does NOT work now so i CAN connect to EDL mode but not normal usb conenctivity.
Anyone have any ideas???
Cannot root, install anything via ADB or even delete apps via ADB. Shocking problem to have man
I'm RMA'ing my phone, just getting it set up now.
Very painful process, they absolutely need the purchase order for warranty, things have changed with 1+
3-10 days apparently, used to be 5 when i've sent it in the past.
On connecting a USB hub i can read USB sticks and i can control my phone with an xbox pad??
Am i missing something? How is all this working yet i can't mount my phone?
Best bet, probably you broke the charging port. did you by any chance use like force usb charging like that?
dewa5227 said:
Best bet, probably you broke the charging port. did you by any chance use like force usb charging like that?
Click to expand...
Click to collapse
I did use the force USB charging yes.. wishing I hadn't now..
I also connected to a usb-c to hub to connect a screen.
Issues kind of started after that.
Physically I haven't damaged it from movement. But could be from the forced charging
UPDATE:
Erm ok this is confusing???
I just connected my phone to a charger that is clearly not rated for it, in the hope it would shock the device, i then connected my phone and made a cup of tea, when i got back my phone showed me this (screenshot attached)
??? Lol what the hell? I've already booked my RMA lmfao
anyway, i shall keep an eye on it, i'll thoroughly test it and get it back up and running.
Strange, very strange.