Related
So last night I was rooting a Kindle Fire 2. It's running 10.2.6. I was following a tutorial on this forum and I succeeded in rooting it. I flashed TWRP on it, but for some reason that didn't work. I tried booting to recovery and got a red triangle with an exclamation point inside it. It said it failed to boot. The device still worked at that point during the install. It was low on battery, though I had it plugged into my laptop. I was in fastboot and the device stopped receiving commands from it for some reason (I wasn't able to figure out why). Then the battery died. I guess a laptop usb port doesn't properly charge a tablet. But anyways, I plugged it into a wall charger for a couple hours and now it won't turn on. When I plugged it in, a charging light never came on. I used this same charger earlier in the evening and it charge the Kindle with no issues whatsoever, so I know it isn't the charger or cable failing to charge the device.
So here is where I stand:
When it died, it would still successfully boot
I was in fastboot when it died
Fastboot would not take commands from my laptop, whereas it had before I tried flashing TWRP (by that I mean when I try to send commands via the command line, it would simply say <waiting for device>)
The device is successfully rooted and bootloader unlocked
I've tried pulling the battery; I've tried holding the power button for 20 seconds, for 30 seconds and for short periods of time; I've tried any possible command from the computer. I haven't tried a factory cable because I don't have one. What do I do now?
philip1192 said:
So last night I was rooting a Kindle Fire 2. It's running 10.2.6. I was following a tutorial on this forum and I succeeded in rooting it. I flashed TWRP on it, but for some reason that didn't work. I tried booting to recovery and got a red triangle with an exclamation point inside it. It said it failed to boot. The device still worked at that point during the install. It was low on battery, though I had it plugged into my laptop. I was in fastboot and the device stopped receiving commands from it for some reason (I wasn't able to figure out why). Then the battery died. I guess a laptop usb port doesn't properly charge a tablet. But anyways, I plugged it into a wall charger for a couple hours and now it won't turn on. When I plugged it in, a charging light never came on. I used this same charger earlier in the evening and it charge the Kindle with no issues whatsoever, so I know it isn't the charger or cable failing to charge the device.
So here is where I stand:
When it died, it would still successfully boot
I was in fastboot when it died
Fastboot would not take commands from my laptop, whereas it had before I tried flashing TWRP (by that I mean when I try to send commands via the command line, it would simply say <waiting for device>)
The device is successfully rooted and bootloader unlocked
I've tried pulling the battery; I've tried holding the power button for 20 seconds, for 30 seconds and for short periods of time; I've tried any possible command from the computer. I haven't tried a factory cable because I don't have one. What do I do now?
Click to expand...
Click to collapse
you dont have to do this if you dont have a factory cable man! try pressing it for 2 minutes and then release and press again
Pulled the battery!?!?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
persano said:
you dont have to do this if you dont have a factory cable man! try pressing it for 2 minutes and then release and press again
Click to expand...
Click to collapse
I'll try that and see if it'll help.
mindmajick said:
Pulled the battery!?!?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Is that a problem?
Other than voiding the warranty since you opened the device... And removed a battery not meant to be removed? Naaaah
You should NEVER have to pull the battery on ANY android device.
Edit: couple more things
1. As long as you are USING the device it won't charge on USB to PC. Always better to charge off a wall outlet. MUCH faster charging too.
2. NEVER flash a ROM if your battery is low.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
When the bootloader was unlocked, the warranty was voided. That's not an issue to me.
I've found that pulling a battery is a perfectly valid way to reboot a device, if nothing else will work, but I always consider it a last resort.
Ah ok. I didn't know that. I'm familiar with phones, so tablets are still new to me.
philip1192 said:
When the bootloader was unlocked, the warranty was voided. That's not an issue to me.
I've found that pulling a battery is a perfectly valid way to reboot a device, if nothing else will work, but I always consider it a last resort.
Ah ok. I didn't know that. I'm familiar with phones, so tablets are still new to me.
Click to expand...
Click to collapse
But the bootloader wasn't technically unlocked AND you could restore back to stock or whatever for replacement if necessary.
Phones are the same way. You can always hold the power button for a hard shutdown or reboot. The only reason i don't recommend it on the kf is that its a sealed device. Sure, if the battery dies, replace it. But anyway.. Not trying to be argumentative bro lol. Sorry cant really help though.
--
Sent from my Kindle Fire 2, CM 10.1
mindmajick said:
But the bootloader wasn't technically unlocked AND you could restore back to stock or whatever for replacement if necessary.
Phones are the same way. You can always hold the power button for a hard shutdown or reboot. The only reason i don't recommend it on the kf is that its a sealed device. Sure, if the battery dies, replace it. But anyway.. Not trying to be argumentative bro lol. Sorry cant really help though.
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
How was it not actually unlocked?
Hopefully someone can...
philip1192 said:
How was it not actually unlocked?
Hopefully someone can...
Click to expand...
Click to collapse
Not likely
http://forum.xda-developers.com/showthread.php?t=1887163
philip1192 said:
How was it not actually unlocked?
Hopefully someone can...
Click to expand...
Click to collapse
Well. I'm pretty sure the FFF boot loader is inserted AFTER the actual boot loader by using the stack exploit. If this isn't 100% correct, please correct me of I'm wrong.
I would try the factory cable though.. See if you can get one from SKORPN.
It sounds like your only option
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
soupmagnet said:
Not likely
http://forum.xda-developers.com/showthread.php?t=1887163
Click to expand...
Click to collapse
Well, they're lame. I like HTC better.
mindmajick said:
Well. I'm pretty sure the FFF boot loader is inserted AFTER the actual boot loader by using the stack exploit. If this isn't 100% correct, please correct me of I'm wrong.
I would try the factory cable though.. See if you can get one from SKORPN.
It sounds like your only option
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I guess I'll see if I can make that work. If not, I guess I have an expensive paperweight on my hands...
While I was using SM-N910P 5.1.1 N910PVPU4COG5_Deodexed Rom, I changed SecContacts_Note_USA.apk file and it turned into Hard Brick.
It's a typical Hard Brick Hard Brick symptom in which nothing shows up on a screen even I pressed a power button and there is no vibration on the phone.
If I connect it to a computer, QHSUSB_BULK pops up.
After I setup a driver, it connects to Qualcomm HS-USB QDLoader 9008.
As I was searching for some information, I could find a solution for Note3 Hard Brick.
However,I do not have unbric.img file as it says on the solution.
I need unbric.img file.
Help Me
Can you get into download mode? Vol down+home+power. Seems odd that just changing that apk would brick your device, trust me I swap files in and out all the time but never had that issue.
Could be your battery is dead too
Rom issues
bcxv said:
While I was using SM-N910P 5.1.1 N910PVPU4COG5_Deodexed Rom, I changed SecContacts_Note_USA.apk file and it turned into Hard Brick.
It's a typical Hard Brick Hard Brick symptom in which nothing shows up on a screen even I pressed a power button and there is no vibration on the phone.
If I connect it to a computer, QHSUSB_BULK pops up.
After I setup a driver, it connects to Qualcomm HS-USB QDLoader 9008.
As I was searching for some information, I could find a solution for Note3 Hard Brick.
However,I do not have unbric.img file as it says on the solution.
I need unbric.img file.
Help Me
Click to expand...
Click to collapse
Just install the ROM again it wont change anything besides having to reinstall xposed if you use that, or audio mods like viper.
ianmb said:
Can you get into download mode? Vol down+home+power. Seems odd that just changing that apk would brick your device, trust me I swap files in and out all the time but never had that issue.
Could be your battery is dead too
Click to expand...
Click to collapse
Impossible
battery full
Iceburn1 said:
Just install the ROM again it wont change anything besides having to reinstall xposed if you use that, or audio mods like viper.
Click to expand...
Click to collapse
recovery mode, download mode Impossible
Ok, for one thing, changing that file will not hard brick your phone.
You either did something else to cause this issue or your battery is drained or kaput... It's not unheard of around here.
Just out of curiosity how do you know the battery is full if you can't get anything from the screen?
jhill110 said:
Ok, for one thing, changing that file will not hard brick your phone.
You either did something else to cause this issue or your battery is drained or kaput... It's not unheard of around here.
Just out of curiosity how do you know the battery is full if you can't get anything from the screen?
Click to expand...
Click to collapse
Charging the spare battery
bcxv said:
Charging the spare battery
Click to expand...
Click to collapse
Ahh...
How old is the phone?
jhill110 said:
Ok, for one thing, changing that file will not hard brick your phone.
You either did something else to cause this issue or your battery is drained or kaput... It's not unheard of around here.
Just out of curiosity how do you know the battery is full if you can't get anything from the screen?
Click to expand...
Click to collapse
I would definitely agree with this. That file alone wouldn't brick your phone. Trust me, as many different files I swap in and out on a daily basis I've never had that happen.
jhill110 said:
Ahh...
How old is the phone?
Click to expand...
Click to collapse
Production date April 2015
ianmb said:
I would definitely agree with this. That file alone wouldn't brick your phone. Trust me, as many different files I swap in and out on a daily basis I've never had that happen.
Click to expand...
Click to collapse
No charge to phone
Charged with a charger
Same problem here,any solutions? Throw it away?
Hard bricked Note 4
Same as above. No power, nothing. Get the Qualcomm when connected to pc. Any ideas?
sshea72 said:
Same as above. No power, nothing. Get the Qualcomm when connected to pc. Any ideas?
Click to expand...
Click to collapse
Check if this helps...
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
Having problems with mine too please help
I have a note 4 from sprint....i havent used it in years but i try to turn it on and it dose and restarts when ba k up aging on the sprint spark screen and keeps doing that i changed batteries and nothing....i try going to recovery mode but just flickers on and off where the android picture but cant do nothin.......i cant rememeber if i was trying to root it or unroot it bt i think i was tryin to root it when the problem started......i try to connect it to the computer to root it and den unroot it but the computer cant get the drivers to find it....so i 2ant to know what can i do
texasrejects91 said:
I have a note 4 from sprint....i havent used it in years but i try to turn it on and it dose and restarts when ba k up aging on the sprint spark screen and keeps doing that i changed batteries and nothing....i try going to recovery mode but just flickers on and off where the android picture but cant do nothin.......i cant rememeber if i was trying to root it or unroot it bt i think i was tryin to root it when the problem started......i try to connect it to the computer to root it and den unroot it but the computer cant get the drivers to find it....so i 2ant to know what can i do
Click to expand...
Click to collapse
If you are for sure that your drivers are installed. (Double check our reinstall ). Plus make sure your using a Samsung usb cord (musty be a good one)
But if all that stuff is correct. Then you might have a failing battery or phone. That's about all the help i can provide.
If you could at least get the phone booted into download mode and pc to reconize it. Then i would Odin a stock firmware.
I'm quite perplexed. I was using my p600 today, and it worked fine like normal. Tonight I took it out to do some reading, and noticed some flickering streaks across the screen. I thought nothing of it, and did a reboot.
It turned off, but never rebooted. The back and menu buttons flashed once, and then went dark.
I've been trying without success to get it to boot for a half hour, nothing. There is no response to plugging it into a charger, and my computer does not recognize it as being plugged in. (Currently have no access to windows, so unsure of ODIN).
I was running Tamasek's unnoficial 18.1 build at the time.
Any ideas. Would greatly appreciate any help, even just to get some notes off if it is indeed dead.
while plugged into charger (to rule out it hasnt died while youve been messing with it) long hold power button... i forget if its 10 seconds or 30 seconds. same sorta thing happened to me on temasek, flicker screen but then it died itself, and i got a response from my tablet by long power button hold. not sure if we had same cause but thats what worked for me
diabl0w said:
while plugged into charger (to rule out it hasnt died while youve been messing with it) long hold power button... i forget if its 10 seconds or 30 seconds. same sorta thing happened to me on temasek, flicker screen but then it died itself, and i got a response from my tablet by long power button hold. not sure if we had same cause but thats what worked for me
Click to expand...
Click to collapse
Doesn't seem to work for me.
Update:
Holding the power button gives no response, no matter the length of press. However, apparently randomly it will turn on, as the back and menu buttons will light up. If this happens I am able to successfully connect to a computer and view files. I was able to connect to ODIN, however since I am unable to get into download mode I am unable to do anything.
If it is in the state where the buttons are lighting up and I then try to boot it it turns off and is completely unresponsive.
Any ideas? Is there a way to remotely boot into download mode?
Cheers
greenmatrix said:
Update:
Holding the power button gives no response, no matter the length of press. However, apparently randomly it will turn on, as the back and menu buttons will light up. If this happens I am able to successfully connect to a computer and view files. I was able to connect to ODIN, however since I am unable to get into download mode I am unable to do anything.
If it is in the state where the buttons are lighting up and I then try to boot it it turns off and is completely unresponsive.
Any ideas? Is there a way to remotely boot into download mode?
Cheers
Click to expand...
Click to collapse
When lights come on, attach to computer and run the command adb devices... if you dont know about adb then there is plenty of info on the net about it. If adb devices gives you a response (which it will if yoi are able to view files on yoir device then that means you will get and adb response as long as you set up the adb program correctly) then run adb reboot download and then youll be in download mode and flash with odin
diabl0w said:
When lights come on, attach to computer and run the command adb devices... if you dont know about adb then there is plenty of info on the net about it. If adb devices gives you a response (which it will if yoi are able to view files on yoir device then that means you will get and adb response as long as you set up the adb program correctly) then run adb reboot download and then youll be in download mode and flash with odin
Click to expand...
Click to collapse
Thanks, I'll let you know how it goes.
diabl0w said:
When lights come on, attach to computer and run the command adb devices... if you dont know about adb then there is plenty of info on the net about it. If adb devices gives you a response (which it will if yoi are able to view files on yoir device then that means you will get and adb response as long as you set up the adb program correctly) then run adb reboot download and then youll be in download mode and flash with odin
Click to expand...
Click to collapse
I am unable to get the p600 to show under adb devices. However, adb does work successfully for my nexus 6 so it appears to be generally working.
This is on mac, so I don't believe it could be a driver issue. I spent a good while trying to get adb working on windows with no success for either device (killed and restarted adb server, tried reinstalling drivers, different cables, etc).
Frustrating, because the p600 will connect fine to the computer, and I can view files and interact with it. Odin also recognizes it.
I appreciate the help, and any further ideas.
if odin recognizes it then why dont you just try to flash stock again?
diabl0w said:
if odin recognizes it then why dont you just try to flash stock again?
Click to expand...
Click to collapse
I've tried, every time it gets hung up on SetupConnection. Running Odin 3.07. Perhaps a different version of Odin?
greenmatrix said:
I've tried, every time it gets hung up on SetupConnection. Running Odin 3.07. Perhaps a different version of Odin?
Click to expand...
Click to collapse
what version did you use last time... hold on ill get you a link to a dif one you should use 3.07 is kinda old
diabl0w said:
what version did you use last time... hold on ill get you a link to a dif one you should use 3.07 is kinda old
Click to expand...
Click to collapse
Thanks, can't remember what I used when I last flashed with odin, I want to say it was around 1.8x.
greenmatrix said:
Thanks, can't remember what I used when I last flashed with odin, I want to say it was around 1.8x.
Click to expand...
Click to collapse
i meant what did you use to flash twrp so that you were able to flash temasek's? ... use 3.10.7
http://forum.xda-developers.com/showthread.php?t=2711451
diabl0w said:
i meant what did you use to flash twrp so that you were able to flash temasek's? ... use 3.10.7
http://forum.xda-developers.com/showthread.php?t=2711451
Click to expand...
Click to collapse
Yeah, when I flashed TWRP a few weeks ago I believe i used odin 1.8x, can't remember. However I know that it wasn't 3.10.7. I'll see how 3.10.7 works.
It appears to still be hanging on SetupConnection.
greenmatrix said:
It appears to still be hanging on SetupConnection.
Click to expand...
Click to collapse
Hmm i guess its not in download mode then... the only thing i could think of is that for some reason it keeps booting to recovery mode which would make both adb and odin not work. Although idk why youd have a blank screen cuz that doesnt tend to happen for recovery. When the menu buttons light up, do they give you haptic feedback (do they vibrate)? If so, maybe you recently dropped it and the ribbon cable for screen beca,e disloged. Id stilll see if you get any responses from ppl who know more than me before you go pulling your tablet apart tho.
The only other thing i could think of to tell you to do is to keep trying to access download mode by holding the appropriate buttons during boot and then try to flash stock with odin. Sorry, i dont know enough to give any more advice from here
diabl0w said:
Hmm i guess its not in download mode then... the only thing i could think of is that for some reason it keeps booting to recovery mode which would make both adb and odin not work. Although idk why youd have a blank screen cuz that doesnt tend to happen for recovery. When the menu buttons light up, do they give you haptic feedback (do they vibrate)? If so, maybe you recently dropped it and the ribbon cable for screen beca,e disloged. Id stilll see if you get any responses from ppl who know more than me before you go pulling your tablet apart tho.
The only other thing i could think of to tell you to do is to keep trying to access download mode by holding the appropriate buttons during boot and then try to flash stock with odin. Sorry, i dont know enough to give any more advice from here
Click to expand...
Click to collapse
ITS ALIVE!!
Thanks man, you may have just solved it, I feel like an idiot. I hadn't considered that the ribbon cable might be loose, and as I was examining it with a bright light I could see items on the screen. Was successfully able to boot into download mode and flash the stock rom, the screen issue was not solved, but I think it flashed alright.
When I have some time I'm going to take off the back and check out the ribbon cable.
greenmatrix said:
ITS ALIVE!!
Thanks man, you may have just solved it, I feel like an idiot. I hadn't considered that the ribbon cable might be loose, and as I was examining it with a bright light I could see items on the screen. Was successfully able to boot into download mode and flash the stock rom, the screen issue was not solved, but I think it flashed alright.
When I have some time I'm going to take off the back and check out the ribbon cable.
Click to expand...
Click to collapse
im glad you were able to figure it out
greenmatrix said:
ITS ALIVE!!
Thanks man, you may have just solved it, I feel like an idiot. I hadn't considered that the ribbon cable might be loose, and as I was examining it with a bright light I could see items on the screen. Was successfully able to boot into download mode and flash the stock rom, the screen issue was not solved, but I think it flashed alright.
When I have some time I'm going to take off the back and check out the ribbon cable.
Click to expand...
Click to collapse
The ribbon cable coming loose is a very common issue on this tablet (even without dropping it) as it's connected rather poorly. Fortunately it's also relatively easy to fix as per the below:
Fixing Note 10.1 2014 ribbon cable
Especially the screen flickering when it "died" sounds familiar.
epithetic said:
The ribbon cable coming loose is a very common issue on this tablet (even without dropping it) as it's connected rather poorly. Fortunately it's also relatively easy to fix as per the below:
Fixing Note 10.1 2014 ribbon cable
Especially the screen flickering when it "died" sounds familiar.
Click to expand...
Click to collapse
This was exactly it. 15 minute fix and everything was golden.
sooo, I gues something went wrong... since the new marshmallow images was posted today, there was a thread on reddit on how I can just download the image and rename it and flash it as OTA. The phone reconginzed the image and went half way through the install and then went black. now it wont even buzz or register the charger. Does nothing when connected to the computer either so I assume there is nothing that could be done. Quite a shame, the phone worked quite nicely until is killed it . Anything I can do?
Did you install it thru TWRP?
thekingestkong said:
sooo, I gues something went wrong... since the new marshmallow images was posted today, there was a thread on reddit on how I can just download the image and rename it and flash it as OTA. The phone reconginzed the image and went half way through the install and then went black. now it wont even buzz or register the charger. Does nothing when connected to the computer either so I assume there is nothing that could be done. Quite a shame, the phone worked quite nicely until is killed it . Anything I can do?
Click to expand...
Click to collapse
There is one thing I recommend trying as there is a bug in official firmware where the phone when connected to a computer can turn off randomly and not charge or boot. What you need to do is disassemble the phone and unplug the connector at the top of the phone to disconnect the battery and then plug it in.
krazy23 said:
Did you install it thru TWRP?
Click to expand...
Click to collapse
no, the phone picked up the update from the internal storage
dc959 said:
There is one thing I recommend trying as there is a bug in official firmware where the phone when connected to a computer can turn off randomly and not charge or boot. What you need to do is disassemble the phone and unplug the connector at the top of the phone to disconnect the battery and then plug it in.
Click to expand...
Click to collapse
thanks, I'm aware of that. Some folks experiencing the same issue tried that with no success. My phone is still under warranty and the screw securing the backplate has a seal on it that I dont want to tamper with.
I guess I'll be sending the phone for to Asus for repair...
Don't lose hope.
My phone was in a similar predicament.
No response to any buttons, nothing on screen, no buzzing or LED's at all.
I was able to get it recognized in the xFSTK Downloader and showing up in windows device manager as a Moorefield device.
I tried many times to get it to put the images on the phone through the xFSTK tool and it failed many times.
I was about to give up and tried again this morning and miraculously the writing succeeded and now my phone is in a bootloop (I think the battery may have been completely drained with my attempts to save it's life.)
I have it on charge currently so hopefully when there is enough juice I should be able to flash the raw file and be back up and running.
I see, you can follow the unbricking tutorial in the general section. Works fine for me and saved me from sending it to the service center.
krazy23 said:
Did you install it thru TWRP?
Click to expand...
Click to collapse
I did! And now my phone is dead! But it buzzes when I press the power button for some seconds.. But it's always black
galagala2 said:
I did! And now my phone is dead! But it buzzes when I press the power button for some seconds.. But it's always black
Click to expand...
Click to collapse
That's what happened to my phone, you can follow this thread this worked for me. Unbricking Method
krazy23 said:
That's what happened to my phone, you can follow this thread this worked for me. Unbricking Method
Click to expand...
Click to collapse
do you lose the data this way?
thekingestkong said:
do you lose the data this way?
Click to expand...
Click to collapse
Unfortunately, yes. Because I ticked the "wipe data" checkbox in the ASUS Flash Tool. Not sure what will happen if I don't. :fingers-crossed:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfon
I also bricked my phone and used the method to fix my phone. Make sure you have all the required drivers installed in your pc/laptop before doing this. I took help of DriverMax to solve the drivers related issues. Make sure before installing and running the XFTSK tool all the drivers and everything is installed otherwise you will see blank forms in the Tool.
Inorder to install OTA (not installed yet), i switched to slot B via booting TWRP, then i reboot but blank screen. Even not starting the botloader, not charging, Just its like a dead phone. Please Help ASAP!
smartybro7788 said:
Inorder to install OTA (not installed yet), i switched to slot B via booting TWRP, then i reboot but blank screen. Even not starting the botloader, not charging, Just its like a dead phone. Please Help ASAP!
Click to expand...
Click to collapse
When you have your device connected to your Laptop or PC, can you see it connected in the Device Manager? Mayne it shows up next to the yellow question mark as "other" possibly? It might say something like QSB9008.
Do you hear your PC make the notification sound when you connect it?
fast69mopar said:
When you have your device connected to your Laptop or PC, can you see it connected in the Device Manager? Mayne it shows up next to the yellow question mark as "other" possibly? It might say something like QSB9008.
Do you hear your PC make the notification sound when you connect it?
Click to expand...
Click to collapse
I'm having the same issue and for me and my PC doesn't detect my phone
fast69mopar said:
When you have your device connected to your Laptop or PC, can you see it connected in the Device Manager? Mayne it shows up next to the yellow question mark as "other" possibly? It might say something like QSB9008.
Do you hear your PC make the notification sound when you connect it?
Click to expand...
Click to collapse
nope its just dead. If its even on i can do something but its just dead. I tear down phone and ejected battery on pure power source tried to switch it on again but no luck.
No detection by PC no notification sound. Now it is a device like of hardware without any softwares in it.
Marcowe said:
I'm having the same issue and for me and my PC doesn't detect my phone
Click to expand...
Click to collapse
Yup still waiting for some help!!!
Switching to another slot might solve the problem, but how to make it detect by pc.
Unfortunately no one has a solution to this problem yet. I'm not sure if it caused by a blank slot, or anti-rollback, avd. I just know that it has happened to a couple of people even @Uzephi and there's no fix yet. Sorry to be the bearer of bad news.
Might try plugging into a 2.0 port, then holding different button combos while plugging in to the phone to see if that'll at least jump it to edl, but apart from that I don't know.
41rw4lk said:
Unfortunately no one has a solution to this problem yet. I'm not sure if it caused by a blank slot, or anti-rollback, avd. I just know that it has happened to a couple of people even @Uzephi and there's no fix yet. Sorry to be the bearer of bad news.
Might try plugging into a 2.0 port, then holding different button combos while plugging in to the phone to see if that'll at least jump it to edl, but apart from that I don't know.
Click to expand...
Click to collapse
It is serious problem which is unsolvable till date, i already tried different combos while plugging to PC, but no luck.
But in my case it is due to blank slot for sure.
Still waiting for help!
As it could occur on another devices too, a solution should be invented, as of now we are not qualified but the senior experienced members could help to resolve the issue as this is the case of A/B empty slot switching.
smartybro7788 said:
It is serious problem which is unsolvable till date, i already tried different combos while plugging to PC, but no luck.
But in my case it is due to blank slot for sure.
Still waiting for help!
As it could occur on another devices too, a solution should be invented, as of now we are not qualified but the senior experienced members could help to resolve the issue as this is the case of A/B empty slot switching.
Click to expand...
Click to collapse
Anybody can help regarding how to force phone to enter into edl mode when phone is completely dead.
41rw4lk said:
Unfortunately no one has a solution to this problem yet. I'm not sure if it caused by a blank slot, or anti-rollback, avd. I just know that it has happened to a couple of people even @Uzephi and there's no fix yet. Sorry to be the bearer of bad news.
Might try plugging into a 2.0 port, then holding different button combos while plugging in to the phone to see if that'll at least jump it to edl, but apart from that I don't know.
Click to expand...
Click to collapse
Bro please can you provide me with emmc dump image file, i'm in dire need, thanks.