Related
I know there is threads about this, but I am having troubles, I will be willing to donate $20 to anyone who can help me. I am hoping it will be relatively easy............. I shouldn't have said that.
I loaded a bad framework-res.apk on my phone, and now it won't boot.
I have read DG's thread on recovering from the brick, but I can't figure out how to make it work.
In order to get the framework loaded I used root explorer to copy it over, because I couldn't get ADB to push the file. (I know, if I couldn't get ADB to work why would I muck with it....)
Now the first step in his guide is to boot into fastboot and wait for adb to work, then use superoneclick and hit 'shell root'
well, I can load into fastboot, but adb consistently says "error: device not found" or it doesn't list anything when I check devices. The troubles I was having before with adb were with pushing files, I could still see the device and pull files.
When I did the superoneclick step it ended up freezing the program, and I am not sure what is supposed to happen with fastboot but all it said was starting fastboot protocol support then did nothing.
I would be very grateful to anyone who can help me with this problem, I do have a backup framework on my computer and on the external sd card in the phone.
One thing I should note is that I did originally boot into the recovery mode, but all i did from there was reboot the phone (and go into fastboot mode).
Please help me! I have learned my lesson.
does the phone turn on
Do you have USB debugging enabled?
If you do, its possible to use adb by selecting Early USB Enumeration from boot menu. If not, you'll need to reflash using an SBF.
Come to my gtalk id texasdude11 and I'll help you out on chat.
Sent from my MB860 using Tapatalk
brian2220 said:
does the phone turn on
Click to expand...
Click to collapse
from what i gather, it turns on, but won't fully boot into android.
by that token, early USB enumeration will allow ADB to work on the phone usually, but in this case i believe debugging was turned off before his device was bricked. so, he can't boot into full android UI, and also can't use ADB to push the restore files because debugging is off.
i've seen this problem with one person before, but i couldn't find a way to force debugging on without going into the UI, if someone can chime in with a way to turn debugging on without initial ADB access, or UI then this problem is solved and more than one person is helped.
Although - he can just reflash if he's on AT&T, if he's on Bell then he's SOL
brian2220 said:
does the phone turn on
Click to expand...
Click to collapse
Sorry, I obviously suck at giving info.
The phone boots but not past the moto screen, I get the flashing red lights and it reboots. I can get into recovery and fastboot (though I suspect fast boot isn't work right since it freezes almost instantly), I also cant see the device in adb while trying fast boot (or anything else for that matter). I could before it bricked.
raybond25 said:
from what i gather, it turns on, but won't fully boot into android.
by that token, early USB enumeration will allow ADB to work on the phone usually, but in this case i believe debugging was turned off before his device was bricked. so, he can't boot into full android UI, and also can't use ADB to push the restore files because debugging is off.
i've seen this problem with one person before, but i couldn't find a way to force debugging on without going into the UI, if someone can chime in with a way to turn debugging on without initial ADB access, or UI then this problem is solved and more than one person is helped.
Click to expand...
Click to collapse
I think debugging was on, but I was also in USB data mode (the one above none). And yes, I am the poor Bell SOL'er.
toughbax said:
Sorry, I obviously suck at giving info.
The phone boots but not past the moto screen, I get the flashing red lights and it reboots. I can get into recovery and fastboot (though I suspect fast boot isn't work right since it freezes almost instantly), I also cant see the device in adb while trying fast boot (or anything else for that matter). I could before it bricked.
Click to expand...
Click to collapse
hold the volume up and the power button together and see if u can get into RSD engineering screen
and just follow this and flash everything over
http://forum.xda-developers.com/showthread.php?t=991072
Id download RSD 5 and one of the sbf files 1.26 or 1.52 and boot phone into rsd(power button+volume up) and flash the sbf
lsxrx7 said:
hold the volume up and the power button together and see if u can get into RSD engineering screen
and just follow this and flash everything over
http://forum.xda-developers.com/showthread.php?t=991072
Click to expand...
Click to collapse
blaque72 said:
Id download RSD 5 and one of the sbf files 1.26 or 1.52 and boot phone into rsd(power button+volume up) and flash the sbf
Click to expand...
Click to collapse
the problem is that he's on Bell, so there's no sbf for us poor Bell users to flash to yet.
raybond25 said:
the problem is that he's on Bell, so there's no sbf for us poor Bell users to flash to yet.
Click to expand...
Click to collapse
Blah guess I should be more observate when trying to help my apologies hope someone on bell helps him
blaque72 said:
Blah guess I should be more observate when trying to help my apologies hope someone on bell helps him
Click to expand...
Click to collapse
yeah, i don't think he explicitly said that, but i just PM'ed him because i guessed that that was the case and it was, i'm on Bell and ima see what i can do
I HAVE BEEN SAVED. Thank you all for your quick help. I am now up and running again and I have learned from my mistakes.
Kudos to Kenneth for his amazingly quick response and supplying me with an idiot proof script to get my phone back to exactly where it was. YOU DA MAN!
Honorable mention to raybond25 for the quick response and solution as well, YOU DA CANADIAN MAN!
toughbax said:
I HAVE BEEN SAVED. Thank you all for your quick help. I am now up and running again and I have learned from my mistakes.
Kudos to Kenneth for his amazingly quick response and supplying me with an idiot proof script to get my phone back to exactly where it was. YOU DA MAN!
Honorable mention to raybond25 for the quick response and solution as well, YOU DA CANADIAN MAN!
Click to expand...
Click to collapse
What was the solution?
shawnbuck said:
What was the solution?
Click to expand...
Click to collapse
NO IDEA.
Kenneth made me a script that did it all for me all I did was hit the space bar a few times.
Basically the problem seemed to be on this side of the keyboard.....
Moved to Q&A
Please post this script so that we may use this in the future
yes, please post the script toughbax or kenneth so that all can benefit from it, i already bricked and returned one atrix and cant afford to brick another. thanks in advance toughbax and kenneth
erik10002 said:
yes, please post the script toughbax or kenneth so that all can benefit from it, i already bricked and returned one atrix and cant afford to brick another. thanks in advance toughbax and kenneth
Click to expand...
Click to collapse
The problem is that the script that ken wrote for the OP only restores the framework-res.apk file, and nothing else. If you really need this to recover from soft brick in the first place I'm not sure if you have the ability to edit it the way that is required.
Sent from my MB860 using XDA App
raybond25 said:
from what i gather, it turns on, but won't fully boot into android.
by that token, early USB enumeration will allow ADB to work on the phone usually, but in this case i believe debugging was turned off before his device was bricked. so, he can't boot into full android UI, and also can't use ADB to push the restore files because debugging is off.
i've seen this problem with one person before, but i couldn't find a way to force debugging on without going into the UI, if someone can chime in with a way to turn debugging on without initial ADB access, or UI then this problem is solved and more than one person is helped.
Although - he can just reflash if he's on AT&T, if he's on Bell then he's SOL
Click to expand...
Click to collapse
Freaking beautiful. Early USB enumeration was just what I needed to fix my f*ck up.
Hi all, it's my first post here
My Galaxy S II (stock ROM/recovery) has fallen into a reboot loop while I was texting and I'm positive I didn't install new apps recently, so I can't really tell it's an app bug. Last thing I did before texting was disabling Swype.
All I know is that TouchWiz now crashes after boot displaying its usual dialog window.
In addition to that, I've just broken the display, so I can't see anything going on screen...
How can I recover pictures from the internal storage? How can I stop the reboot loop long enough to back up everything with Kies?
I've tried booting in safe mode but the phone keeps on rebooting and I have no visual feedback of successful activation of safe mode. Prior to breaking the screen I could access the stock recovery, so I guess I can still do it, if needed.
TIA,
Andrea
Recovery should be enough if it works. So try getting into recovery and connecting it via ADB. Then you can get data with "adb pull <location-on-phone>"
Explorer23 said:
Recovery should be enough if it works. So try getting into recovery and connecting it via ADB. Then you can get data with "adb pull <location-on-phone>"
Click to expand...
Click to collapse
Thank you for your reply!
When you say "recovery", you mean stock recovery or a more advanced one (CWM, etc.)?
I've never used ADB, I'll try to set it up as per these instructions: http://forum.xda-developers.com/showthread.php?t=1917237
EDIT: Do I need to enable debugging on the phone? It's currently disabled and I can't do anything about it because of the reboot loop...
don't know
I don't think that it's possible to recover the data on your device's internal storage now. Rest if anything works do post your experience here with respective procedure or snapshots.
For more attractive deals "Just Dial":- +1 516 515 9871
lo_Spocchioso said:
Thank you for your reply!
When you say "recovery", you mean stock recovery or a more advanced one (CWM, etc.)?
I've never used ADB, I'll try to set it up as per these instructions: http://forum.xda-developers.com/showthread.php?t=1917237
EDIT: Do I need to enable debugging on the phone? It's currently disabled and I can't do anything about it because of the reboot loop...
Click to expand...
Click to collapse
Oh crap ... yes, i think you need to have debugging ON (never actually tried without it). Well, you can still check it. So set up ADB (hope those instructions are good, I can't help you there as I don't know how things work on Mac) and type in "adb devices". If everything's OK, you should get one device listed (some weird number). Then type in "adb pull <location on phone> <location on computer (optionally)>. If you want more info about commands, just type "adb" and you'll get everything listed. That should be it ... if it works in first place :fingers-crossed:
EDIT: Stock recovery should do fine.
Explorer23 said:
Oh crap ... yes, i think you need to have debugging ON (never actually tried without it). Well, you can still check it. So set up ADB (hope those instructions are good, I can't help you there as I don't know how things work on Mac) and type in "adb devices". If everything's OK, you should get one device listed (some weird number).
Click to expand...
Click to collapse
Yeah, I've tried with another (working) S II and it seems you really need debugging turned on...
Is it possibile to use a custom recovery to copy data from internal memory to the SD? I could try to do it blindfolded :cyclops:
lo_Spocchioso said:
Yeah, I've tried with another (working) S II and it seems you really need debugging turned on...
Is it possibile to use a custom recovery to copy data from internal memory to the SD? I could try to do it blindfolded :cyclops:
Click to expand...
Click to collapse
Possible ... maybe. But that would mean you need a recovery with file manager - and file managers are usually touch-based. So you can't do much if your screen is broken. I suggested ADB because it was the only option that would work for sure and you don't need screen for it ...
But ... maybe there still is a way ... You could try reinstalling ROM via ODIN and syncing with Kies. Download stock ROM for your country and carrier from www.sammobile.com/firmwares, get your phone into download mode and insatall via Odin. This should work. You're not doing any factory resets, wipes or anything - just "dirty flashing" the ROM over existing one, so data and (most) apps remain untouched. Then you can try connecting with Kies. From there I don't know exactly how stuff works (don't have a Samsung device), but hope it can launch without touching anything on the phone.
I suggest removing the SIM card before trying, so it doesn't get stuck on PIN unlock screen.
This is really your last chance ...
Your next option is changing the screen
Good luck
Explorer23 said:
Possible ... maybe. But that would mean you need a recovery with file manager - and file managers are usually touch-based.
Click to expand...
Click to collapse
You're right but, if I'm not mistaken, CWM "touch" file manager can also be used with the physical buttons. I've never tried that, can anybody please confirm?
You could try reinstalling ROM via ODIN and syncing with Kies.
Click to expand...
Click to collapse
That's actually an excellent idea! Now, I only need to be sure that, after re-flashing, the device will be immeditely accessible by Kies straight after boot without further intervention...
Your next option is changing the screen
Click to expand...
Click to collapse
True, but I'd rather grow brain cells than shell out money
What happened was I was trying to root my kindle fire HDX with this thread. http://forum.xda-developers.com/showthread.php?t=2689121
I put in "adb reboot bootloader" and it was fine.
After, I put in "fastboot -i 0x1949 flash boot boot.img" and that's where stuff went downhill. Basically my kindle just got stuck at the kindle fire logo, where the kindle is "silver" and the "fire" is orange with the gradient of light going across it.
It was stuck on waiting for device for 10 minutes, so I shut it down by holding the power for 30 seconds and disconnected it.
Ever since then, when I restart the kindle, it just shows the kindle fire shining logo and that's it. I can't do anything else.
I'm very new to this kind of stuff, was doing this with the help of my friend, but now we're both stumped.
Any help would be really helpful. If I could factory reset, I would, so there's a lot of stuff I'm willing to do and part with the info on this kindle. I just want it to be working again.
Thank you for reading this and any help at all would be greatly appreciated!
Edit: Oh, and if it helps, I was running 14.3.2.2 instead of 14.3.2.1.
I didn't think it would make that big of a difference, but I definitely learned my lesson.
uberiyer1 said:
What happened was I was trying to root my kindle fire HDX with this thread. http://forum.xda-developers.com/showthread.php?t=2689121
I put in "adb reboot bootloader" and it was fine.
After, I put in "fastboot -i 0x1949 flash boot boot.img" and that's where stuff went downhill. Basically my kindle just got stuck at the kindle fire logo, where the kindle is "silver" and the "fire" is orange with the gradient of light going across it.
It was stuck on waiting for device for 10 minutes, so I shut it down by holding the power for 30 seconds and disconnected it.
Ever since then, when I restart the kindle, it just shows the kindle fire shining logo and that's it. I can't do anything else.
I'm very new to this kind of stuff, was doing this with the help of my friend, but now we're both stumped.
Any help would be really helpful. If I could factory reset, I would, so there's a lot of stuff I'm willing to do and part with the info on this kindle. I just want it to be working again.
Thank you for reading this and any help at all would be greatly appreciated!
Edit: Oh, and if it helps, I was running 14.3.2.2 instead of 14.3.2.1.
I didn't think it would make that big of a difference, but I definitely learned my lesson.
Click to expand...
Click to collapse
If you can reboot into the bootloader again, it might be worth it to try the same commands, but with the boot.img pulled from 14.3.2.2.
S_transform said:
... but with the boot.img pulled from 14.3.2.2.
Click to expand...
Click to collapse
I don't think this matters... if the HDX 8.9 is anything like the HDX 7, the boot.img file is identical in both the 13.3.2.1 and 13.3.2.2 versions. I did a binary-compare when 13.3.2.2 was released, and they're bit-for-bit identical. FYI.
[Edit] However, there is significant difference in the boot.img between versions 13.3.1.0 and 13.3.2.1. [/Edit]
tl3 said:
I don't think this matters... if the HDX 8.9 is anything like the HDX 7, the boot.img file is identical in both the 13.3.2.1 and 13.3.2.2 versions. I did a binary-compare when 13.3.2.2 was released, and they're bit-for-bit identical. FYI.
[Edit] However, there is significant difference in the boot.img between versions 13.3.1.0 and 13.3.2.1. [/Edit]
Click to expand...
Click to collapse
I was not aware, thanks for the heads up!
No, the root method in my thread unfortunately is non-working. I intended for boot.img to be flashed when the "fastboot" screen is showing. Unfortunately, the hdx does not go into fastboot like its sister device the HD 2013. Reading earlier posts in the thread would show you that it does not work.
But this is puzzling. Did you use a fastboot cable? If not then it was not my root method that bootlooped your device, and you should be able to get a replacement. If you DID use a factory cable, I can help you fix it.
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Mineturtle33 said:
No, the root method in my thread unfortunately is non-working. I intended for boot.img to be flashed when the "fastboot" screen is showing. Unfortunately, the hdx does not go into fastboot like its sister device the HD 2013. Reading earlier posts in the thread would show you that it does not work.
But this is puzzling. Did you use a fastboot cable? If not then it was not my root method that bootlooped your device, and you should be able to get a replacement. If you DID use a factory cable, I can help you fix it.
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Click to expand...
Click to collapse
how can you help fix with a fastboot cable??
jjrizzelcincy said:
how can you help fix with a fastboot cable??
Click to expand...
Click to collapse
Did you use a fastboot cable or not. If you didnt, it wasnot my root method that killed your device, and if you did, it still might not have been. It depends on whether the tablet's "fastboot" screen appeared when you used the cable. If so, i can help you recover it.
So...
•did you use a fastboot cable?
If yes
•did a fastboot screen pop up?
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Mineturtle33 said:
Did you use a fastboot cable or not. If you didnt, it wasnot my root method that killed your device, and if you did, it still might not have been. It depends on whether the tablet's "fastboot" screen appeared when you used the cable. If so, i can help you recover it.
So...
•did you use a fastboot cable?
If yes
•did a fastboot screen pop up?
Sent from my KFSOWI, 11.3.2.1, rooted, Amazon stuff replaced with Google Services.
Click to expand...
Click to collapse
i am only asking how you might go about fixing his problem to learn something new about the device ,that is why i asked you how you would go about that with a fastboot cable your root method did not brick my device
jjrizzelcincy said:
i am only asking how you might go about fixing his problem to learn something new about the device ,that is why i asked you how you would go about that with a fastboot cable your root method did not brick my device
Click to expand...
Click to collapse
If you want me to fix it you need to answer the questions or I can't help you. I'm doing my best.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
If you want me to fix it you need to answer the questions or I can't help you. I'm doing my best.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
again i did not brick my device
using your root method
my device got bricked by an error in safestrap
i did a wipe data factory reset and this when i went to reflash the rom on the rom slot and it kept saying flash failed and that there were 0 mb on the sdcard i even pushed the rom back to the sdcard from adb but it would not flash and when i went to reboot it gave me a warning saying no os found or something like that so i tried and tried to make another rom slot and tried to restore a backup but it would not let me saying 0mb of storage available
so that's my story and now i dont have adb and im stuck at the gray kindle fire logo with only mtp showing but not fully installing but with a fastboot cable i got QHSUSB_BULK at first but after some booting over and over again i got it into QHSUSB_DLOAD with a driver installed on windows and i can see it connected to Linux as well with an id and everything in lsusb from a terminal that is about where my knowledge ends
but with the right devs we could get this working like the evo 3d and a bunch
of other HTC devices that were fixed that way and even get s-off through that QHSUSB_DLOAD mode but i dont have the knowledge to write something like that up or how to issue the proper commands in Linux or what partitions to write to or even the proper chmod to make so im stuck with a nice little paper weight as of now with no devs on board it's looking a bit grim for me
jjrizzelcincy said:
again i did not brick my device
using your root method
my device got bricked by an error in safestrap
i did a wipe data factory reset and this when i went to reflash the rom on the rom slot and it kept saying flash failed and that there were 0 mb on the sdcard i even pushed the rom back to the sdcard from adb but it would not flash and when i went to reboot it gave me a warning saying no os found or something like that so i tried and tried to make another rom slot and tried to restore a backup but it would not let me saying 0mb of storage available
so that's my story and now i dont have adb and im stuck at the gray kindle fire logo with only mtp showing but not fully installing but with a fastboot cable i got QHSUSB_BULK at first but after some booting over and over again i got it into QHSUSB_DLOAD with a driver installed on windows and i can see it connected to Linux as well with an id and everything in lsusb from a terminal that is about where my knowledge ends
but with the right devs we could get this working like the evo 3d and a bunch
of other HTC devices that were fixed that way and even get s-off through that QHSUSB_DLOAD mode but i dont have the knowledge to write something like that up or how to issue the proper commands in Linux or what partitions to write to or even the proper chmod to make so im stuck with a nice little paper weight as of now with no devs on board it's looking a bit grim for me
Click to expand...
Click to collapse
Oh my god I'm an idiot. I thought you were the op. *facepalm* sorry for the trouble.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
Oh my god I'm an idiot. I thought you were the op. *facepalm* sorry. For the trouble.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
NOPE you are stuck helping me now lol
jjrizzelcincy said:
NOPE you are stuck helping me now lol
Click to expand...
Click to collapse
I'll look into it. But as of now I'm a bit busy. Sorry.
Sent from my Galaxy Nexus using Tapatalk
Mineturtle33 said:
I'll look into it. But as of now I'm a bit busy. Sorry.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
the only way i see a fix for mine since the fastboot cable did not help me get into fastboot mode is if we some how manage to get some devs over here which seems unlikely at this point but i still have hope one falls on a devs lap sometime soon
Title explains it all, although the way I bricked it is honestly the dumbest way to brick a phone. Once upon a time, when cleaning this phone to be ready to sell, I was wiping it to clean it. I wanted to make sure it was all clean for the buyer, so I wiped USB-OTG I believe it's called (literally all storage). I immediately realized what a mistake I had made when I had no ROM, no backups, nothing at all. What is my best bet to go about fixing this now? I can reboot to bootloader and enter fastboot, but it seems like something integral is missing, because my computer no longer recognizes my DNA as a device. I still have TWRP 2.8.0.2 on my device, but I can do nothing with it because I have nothing to flash. I know there is an ADB sideload feature, but I cannot figure that one out either. Someone please help me unbrick this phone :crying:
grimpow said:
Title explains it all, although the way I bricked it is honestly the dumbest way to brick a phone. Once upon a time, when cleaning this phone to be ready to sell, I was wiping it to clean it. I wanted to make sure it was all clean for the buyer, so I wiped USB-OTG I believe it's called (literally all storage). I immediately realized what a mistake I had made when I had no ROM, no backups, nothing at all. What is my best bet to go about fixing this now? I can reboot to bootloader and enter fastboot, but it seems like something integral is missing, because my computer no longer recognizes my DNA as a device. I still have TWRP 2.8.0.2 on my device, but I can do nothing with it because I have nothing to flash. I know there is an ADB sideload feature, but I cannot figure that one out either. Someone please help me unbrick this phone :crying:
Click to expand...
Click to collapse
Boot to recovery
adb push NameOfRom.zip /sdcard
Flash rom
Sent from my HTC6535LVW using Tapatalk
grimpow said:
Title explains it all, although the way I bricked it is honestly the dumbest way to brick a phone. Once upon a time, when cleaning this phone to be ready to sell, I was wiping it to clean it. I wanted to make sure it was all clean for the buyer, so I wiped USB-OTG I believe it's called (literally all storage). I immediately realized what a mistake I had made when I had no ROM, no backups, nothing at all. What is my best bet to go about fixing this now? I can reboot to bootloader and enter fastboot, but it seems like something integral is missing, because my computer no longer recognizes my DNA as a device. I still have TWRP 2.8.0.2 on my device, but I can do nothing with it because I have nothing to flash. I know there is an ADB sideload feature, but I cannot figure that one out either. Someone please help me unbrick this phone :crying:
Click to expand...
Click to collapse
Did you ever get your issue resolved?
santod040 said:
Boot to recovery
adb push NameOfRom.zip /sdcard
Flash rom
Sent from my HTC6535LVW using Tapatalk
Click to expand...
Click to collapse
That was my plan, but the problem is that ever since accidentally wiping everything, my device will not be recognized.
Code:
adb devices
returns that no devices are connected.
strabo231 said:
Did you ever get your issue resolved?
Click to expand...
Click to collapse
Not yet. I'm still stuck trying to get my computer (or any computer for that matter) to recognize my device, but no luck. I'm afraid I've permanently bricked this thing.
grimpow said:
That was my plan, but the problem is that ever since accidentally wiping everything, my device will not be recognized.
Code:
adb devices
returns that no devices are connected.
Not yet. I'm still stuck trying to get my computer (or any computer for that matter) to recognize my device, but no luck. I'm afraid I've permanently bricked this thing.
Click to expand...
Click to collapse
Go into the bootloader and select fastboot. fastboot devices
strabo231 said:
Go into the bootloader and select fastboot. fastboot devices
Click to expand...
Click to collapse
Same problem, won't show up under devices. It's as if I deleted something essential to being recognized as an android device.
grimpow said:
Same problem, won't show up under devices. It's as if I deleted something essential to being recognized as an android device.
Click to expand...
Click to collapse
Kinda doubtful. I do see a usb communication issue though. You say you've tried this on several computers, and I'm assuming they weren't all yours, which leads me to believe that you have been missing drivers. From what you've described I highly doubt the connection issue is stemming from something you deleted off the phone. The DNA is almost impossible to brick to the point of not being able to get it back.
Go here and get HTC Sync. This will ensure that you have all the updated drivers including the proper fastboot drivers. Install the program, and then reboot after installation completes.
http://www.htc.com/us/support/software/htc-sync-manager.aspx
From here you'll want to go in and uninstall it. This will remove the program, which has been known to cause usb connection/communication issues with rooting procedures, but it will leave the drivers behind. Once that completes, restart again. This should fix your fastboot problem. I've had the same problem after reformatting computers and then trying to simply download a driver pack rather than htc sync.
Also be sure to try different usb ports. Sometimes the ones in the front or side will cause problems, but the ones in the back or on the other side work just fine.
If all else fails, mail it to me and i'll fix it for you :good:
Bricked phone, no usb
My dna droid stopped working, loaded htc sync and revoot but still not seen by explorer or adb. Suggestions appreciated.
Hey everyone, i'm sorry if this isn't the right section to post that kind of stuff in, i have a galaxy s7 edge with a broken screen, it's unresponsive and it shows nothing, so it's pointless for me to plug a mouse via an OTG cable in order to operate it, other than the screen, i think it still functions though, it's relatively expensive to repair here in my country so i figured i might as well recover my data and get rid of it altogether afterwards, i don't have usb debugging enabled, and i don't how how to enable it via recovery mode (if it's possible that is), is there some way to like cast its display to a computer and use the latter the interact with it ? or at least access its storage ? i really have important data in the device, so if there's no way to recover it, i'll be forced to repair the screen, i really appreciate any help
Have you asked this already - like a year ago?
https://forum.xda-developers.com/t/samsung-galaxy-s7-edge-cracked-screen.3995855
So, no TWRP. Then flash a modified stock recovery of your own. Enable adb in it. Pull stuff if not encrypted. If not, root with SuperSu. Then pull stuff...
That was just guesswork. Try yourself what can be done...
CXZa said:
Have you asked this already - like a year ago?
https://forum.xda-developers.com/t/samsung-galaxy-s7-edge-cracked-screen.3995855
So, no TWRP. Then flash a modified stock recovery of your own. Enable adb in it. Pull stuff if not encrypted. If not, root with SuperSu. Then pull stuff...
That was just guesswork. Try yourself what can be done...
Click to expand...
Click to collapse
Yes i did, i completely forgot about it however ! anyway, there's no custom recovery (i figured it's pretty much a must just in case something like that happens, but it was too late unfortunately), i didn't search thoroughly yet, but i can't find already modified stock recovery files for the device (assuming there's any of course), and i don't know how to modify such files if that's possible, can you walk me though some steps ? although i thought i knew a little bit about that stuff, apparently it's not enough ! and thanks a lot, i really appreciate your help
Sisine said:
although i thought i knew a little bit about that stuff, apparently it's not enough
Click to expand...
Click to collapse
Same here. And that guesswork went wrong too as I forgot that you said in that other thread that usb debugging isn't enabled...
CXZa said:
Same here. And that guesswork went wrong too as I forgot that you said in that other thread that usb debugging isn't enabled...
Click to expand...
Click to collapse
It looks like i'm out of luck