I've been attempting to recover my samsung galaxy A8 from a brick, by flashing the original firmware for 3 days. I successfully got TWRP flashed, and couldn't connect to the phone using MTP, so I ended up using an SD card to transfer the firmware zip. Long story short, I tried to treble it, and it completely bricked, leaving me without TWRP, or anything to boot.
I've put it in download mode, swapped through 10 different USB C cables, and still can't get my PC to recognize it. I've tried two computers, one running arch linux, and the other one through windows 10 and arch linux. Nothing. Whenever I run "lsusb" I can't see the phone. I also can't see it in device manager.
windowsagent said:
I've been attempting to recover my samsung galaxy A8 from a brick, by flashing the original firmware for 3 days. I successfully got TWRP flashed, and couldn't connect to the phone using MTP, so I ended up using an SD card to transfer the firmware zip. Long story short, I tried to treble it, and it completely bricked, leaving me without TWRP, or anything to boot.
I've put it in download mode, swapped through 10 different USB C cables, and still can't get my PC to recognize it. I've tried two computers, one running arch linux, and the other one through windows 10 and arch linux. Nothing. Whenever I run "lsusb" I can't see the phone. I also can't see it in device manager.
Click to expand...
Click to collapse
have you tried flashing it as update via sideload in adb ?
do you have the latest samsung drivers installed ?
try using my tool located here
gav83collins said:
have you tried flashing it as update via sideload in adb ?
do you have the latest samsung drivers installed ?
try using my tool located here
Click to expand...
Click to collapse
I'm stuck without TWRP, so I can't adb sideload. I did try it back when TWRP did boot, but it still didn't recognize it (I tried lsusb and adb devices)
windowsagent said:
I'm stuck without TWRP, so I can't adb sideload. I did try it back when TWRP did boot, but it still didn't recognize it (I tried lsusb and adb devices)
Click to expand...
Click to collapse
you dont need twrp to sideload, you can do it via adb, my tool above will guide you through the process
gav83collins said:
you dont need twrp to sideload, you can do it via adb, my tool above will guide you through the process
Click to expand...
Click to collapse
I'll try to do it then, while in download mode. Thanks!
windowsagent said:
I'll try to do it then, while in download mode. Thanks!
Click to expand...
Click to collapse
my tool will boot you into download mode when necessary. just follow the onscreen instructions
gav83collins said:
my tool will boot you into download mode when necessary. just follow the onscreen instructions
Click to expand...
Click to collapse
My device is just not listed. I see it's just running adb devices, and nothing shows up.
windowsagent said:
My device is just not listed. I see it's just running adb devices, and nothing shows up.
Click to expand...
Click to collapse
Plus I've already got all the drivers installed.
windowsagent said:
Plus I've already got all the drivers installed.
Click to expand...
Click to collapse
you havent got your phones settings for usb set to "charge only" have you ?
gav83collins said:
you havent got your phones settings for usb set to "charge only" have you ?
Click to expand...
Click to collapse
My phone doesn't boot. I deleted the system partition. It's on a bootloop, and the only thing I can do is access download mode.
I was able to plug it in. I used the sim card remover to try to clean up the port.. I'm seriously an idiot...
windowsagent said:
I was able to plug it in. I used the sim card remover to try to clean up the port.. I'm seriously an idiot...
Click to expand...
Click to collapse
so even in download mode, my tool doesnt detect it ? what about in device manager ? does it show up in there ? are you running a windows machine or windows via a virtual machine
Hi so im having a almost same situation here with my a8 2018 so it seems on the phone that it was doing an update and failed and cant boot to android (i think it got corrupted or something) i can access the samsung recovery but if i do reboot or any data deletion i cant get it to work i tried installing twrp recovery but im a biginer and well idk how to do it from the adb update option
ocasds said:
Hi so im having a almost same situation here with my a8 2018 so it seems on the phone that it was doing an update and failed and cant boot to android (i think it got corrupted or something) i can access the samsung recovery but if i do reboot or any data deletion i cant get it to work i tried installing twrp recovery but im a biginer and well idk how to do it from the adb update option
Click to expand...
Click to collapse
update: i managed to get twrp installed
also i found out i need to install new android so if you can link me something good for the a8 2018 i would be gratefull
Related
I really Need Help! My computer wont recognize my tablet in fastboot mode, and my tablet wont read my micro SD card, also when i turn it on normally it stays at splash screen and when its plugged in to the computer the computer starts installing the drivers and it fails to install each time. I go to troubleshooting options and it states code 10. which states device cannot start.
I Have looked for ways around this, like manually installing the drivers, and my computer wont let me. Also the tablet can go to both: bootloader, and Clockworkmod recovery.
I factory reset my tablet so I cannot install anything, untill i get it to connect to my computer.
I am running Windows 7 64-bit on my computer!
Any help is very much appreciated!
Thanks!
NewDev4IOS said:
I really Need Help! My computer wont recognize my tablet in fastboot mode, and my tablet wont read my micro SD card, also when i turn it on normally it stays at splash screen and when its plugged in to the computer the computer starts installing the drivers and it fails to install each time. I go to troubleshooting options and it states code 10. which states device cannot start.
I Have looked for ways around this, like manually installing the drivers, and my computer wont let me. Also the tablet can go to both: bootloader, and Clockworkmod recovery.
I factory reset my tablet so I cannot install anything, untill i get it to connect to my computer.
I am running Windows 7 64-bit on my computer!
Any help is very much appreciated!
Thanks!
Click to expand...
Click to collapse
Did you install the naked driver from here? http://forum.xda-developers.com/showthread.php?t=1426502 if not do that first once you get that working... then you should be able to fastboot to the pc... next thing I would concider is going to twrp recovery instead of cwm....either go for an older version or go the full gambit of nvflash then install the latest twrp... after that you should be set.....I can comment more on it if you need it....
Bricked Tablet Help
Gage_Hero said:
Did you install the naked driver from here? http://forum.xda-developers.com/showthread.php?t=1426502 if not do that first once you get that working... then you should be able to fastboot to the pc... next thing I would concider is going to twrp recovery instead of cwm....either go for an older version or go the full gambit of nvflash then install the latest twrp... after that you should be set.....I can comment more on it if you need it....
Click to expand...
Click to collapse
I tried installing those drivers but it didnt work
also i used WSG_Unbricker v.1.0.3
my system is wiped
is there any way to install the operating system on it
i need a link for an update.zip
thanks
i can now only go to fastboot mode and wipe data mode.
NewDev4IOS said:
I tried installing those drivers but it didnt work
also i used WSG_Unbricker v.1.0.3
my system is wiped
is there any way to install the operating system on it
i need a link for an update.zip
thanks
i can now only go to fastboot mode and wipe data mode.
Click to expand...
Click to collapse
What do you see in device manager with the tablet plugged into the pc and running in fastboot?
Maybe this helps
I had a similar issue but my tablet couldn't be identified by windows, at first i thought it was my drivers so i tried to install new ones but windows wouldn't let me stating the same code 10. At the end it was a defective usb cable, i bought a new one and everything worked all right the first time i plugged it in. And by the way i was stucked at the CWM loop. Hope this helps and sorry for my bad english.
Bricked tablet
sj010489 said:
I had a similar issue but my tablet couldn't be identified by windows, at first i thought it was my drivers so i tried to install new ones but windows wouldn't let me stating the same code 10. At the end it was a defective usb cable, i bought a new one and everything worked all right the first time i plugged it in. And by the way i was stucked at the CWM loop. Hope this helps and sorry for my bad english.
Click to expand...
Click to collapse
Thanks
Im not sure if it is a bad usb cable, i think it is my computer because my computer doesnt even recognize my iphone and i have itunes installed,
i think it is partially due to a funky computer for me.
BRICKED
Gage_Hero said:
What do you see in device manager with the tablet plugged into the pc and running in fastboot?
Click to expand...
Click to collapse
It says fastboot
I sent my tablet in to asus
just waiting on them to reply
Using Windows 10 x64 with drivers freshly installed
GT-I9001, Firmware 2.3, Factory reset performed and drivers unistalled/reinstalled
Been searching for hours on this and can't get it to work. Captivate will connect to computer normally and allow file transfers. But when I try to put in download mode, the computer won't recognize it. I get a popup window that says USB device not recognized.
I'm trying to restore back to complete stock because I'm having random shut downs and other misc issues. I was trying to us Odin to do it but it doesn't recognize the phone. So I powered up the phone, started Odin, then plugged the phone in...Odin sees the phone now but of course needs it in Download mode to work...so I get ADB and while the phone is connected, powered up, and recognized by Odin, I put it in download mode using "adb reboot download". The command put the phone into download mode but then Odin lost contact the the bubble appeared again saying it wasn't recognized.
I've completely removed all the samsung drivers, shut down computer, reinstalled all the drivers, shut down the computer, plugged the phone into the computer and watch to see that all drivers were installed correctly and the computer recognizes the phone...
So it all works EXCEPT while in download mode...any ideas?
I've tried different USB cords but don't have another computer to try on...
I would say you should try Samsung kies, let them install drivers. Then use download mode.
PalmCentro said:
I would say you should try Samsung kies, let them install drivers. Then use download mode.
Click to expand...
Click to collapse
i did, but doesn't work.
up...
Chouiyekh said:
up...
Click to expand...
Click to collapse
maybe the drivers aren't working.
Try downloading the driver from here
BatDroid said:
maybe the drivers aren't working.
Try downloading the driver from here
Click to expand...
Click to collapse
the link detected as a virus
Chouiyekh said:
the link detected as a virus
Click to expand...
Click to collapse
what?
its Androidmtk.com
BatDroid said:
what?
its Androidmtk.com
Click to expand...
Click to collapse
The link blocked by malwarebytes
BatDroid said:
what?
its Androidmtk.com
Click to expand...
Click to collapse
i've tried the driver from android mtk but also unhelpful
Chouiyekh said:
Using Windows 10 x64 with drivers freshly installed
GT-I9001, Firmware 2.3, Factory reset performed and drivers unistalled/reinstalled
Been searching for hours on this and can't get it to work. Captivate will connect to computer normally and allow file transfers. But when I try to put in download mode, the computer won't recognize it. I get a popup window that says USB device not recognized.
I'm trying to restore back to complete stock because I'm having random shut downs and other misc issues. I was trying to us Odin to do it but it doesn't recognize the phone. So I powered up the phone, started Odin, then plugged the phone in...Odin sees the phone now but of course needs it in Download mode to work...so I get ADB and while the phone is connected, powered up, and recognized by Odin, I put it in download mode using "adb reboot download". The command put the phone into download mode but then Odin lost contact the the bubble appeared again saying it wasn't recognized.
I've completely removed all the samsung drivers, shut down computer, reinstalled all the drivers, shut down the computer, plugged the phone into the computer and watch to see that all drivers were installed correctly and the computer recognizes the phone...
So it all works EXCEPT while in download mode...any ideas?
I've tried different USB cords but don't have another computer to try on...
Click to expand...
Click to collapse
Had the same problem spent hours trying to fix it, gave up and used windows 7
rpsweb said:
Had the same problem spent hours trying to fix it, gave up and used windows 7
Click to expand...
Click to collapse
do you mean using win7 you didn't get the problem, mean you solve it ?
Chouiyekh said:
do you mean using win7 you didn't get the problem, mean you solve it ?
Click to expand...
Click to collapse
I couldnt get the adb driver to work when in download mode, it was exclamated in device manager. So I used windows 7 instead worked fine, no this isn't the answer you want to hear but wasted hours trying to get it to work on windows 10
rpsweb said:
I couldnt get the adb driver to work when in download mode, it was exclamated in device manager. So I used windows 7 instead worked fine, no this isn't the answer you want to hear but wasted hours trying to get it to work on windows 10
Click to expand...
Click to collapse
thank you man i'll try with win 7, keep in touch
Chouiyekh said:
thank you man i'll try with win 7, keep in touch
Click to expand...
Click to collapse
I just read right clicking on the adb device in device manager when your phone is in download mode and choosing automatically update driver can fix the problem
When I "Swipe to wipe" in twrp, twrp instantly resets.
I can not swipe to wipe.
I successfully had rooted access and twrp installed with Slimroms on Nexus 9 running correctly.
I Tried to install an 8.0 Oreo rom but it crashes and resets on the google screen.
when i try to return to old roms I get "Error 7" in Twrp.
and I can no longer swipe to wipe or factory reset.
Anyone know how to fix this issue so I can return to 7.1.2 SlimRoms?
the nexus 9 no longer shows up in windows or under ADB Devices.
So i cant access adb functions.
did my bootloader have a problem?
it seems twrp is crashing when its trying to format or wipe mounts ?
Have you tried flashing the latest firmware from Google with fastboot? That's where I would start.
Sent from my SM-T820 using XDA-Developers Legacy app
Can i do that with only twrp?
Does flashboot require adb access from a pc? I cant seem to get the device to show under windows or adb.
Can i use a memory stick and twrp to install those ?
Ill try tonight if thats possible without pc adb acess.
RecIV said:
Can i do that with only twrp?
Does flashboot require adb access from a pc? I cant seem to get the device to show under windows or adb.
Can i use a memory stick and twrp to install those ?
Ill try tonight if thats possible without pc adb acess.
Click to expand...
Click to collapse
No, can't do it in TWRP. If you're having trouble, try wugfresh toolkit. It's no longer updated but you can use it to flash a factory image that you download yourself. Toolkit might help with your issue of not being recognized by your PC.
Wugflash cant recognize the device if windows cant also.
I tried.
I can get into twrp and fastboot. But i have no connection to pc, except for usb memory stick.
The device says unlocked inside of fastboot.
Why cant i connect to adb windows? Ive installed usb drivers many times for many different phones and pcs. I dont think thats the problem.
RecIV said:
Wugflash cant recognize the device if windows cant also.
I tried.
I can get into twrp and fastboot. But i have no connection to pc, except for usb memory stick.
The device says unlocked inside of fastboot.
Why cant i connect to adb windows? Ive installed usb drivers many times for many different phones and pcs. I dont think thats the problem.
Click to expand...
Click to collapse
I've had to do it few times to get it to recognize device. That's the only reason I suggested wugs. It has quick options to retry driver install. But manually is better of course. Windows 10 gave me a heck of a time with driver's.
Hi Guys,
I might have ****ed up something,
I was on B131-SP1, rooted with magisk, I wanted to install B137, so I ran the magisk uninstall, repacked the B137 update, and ran the OTA.bat, everything went ok.
I wanted a fresh install, so I went in the recovery and wiped data.
To get root back I booted the phone in fastboot, and ran the magisk installer, and it asked to disconnect the phone and boot in to recovery,
everything ok, booted the phone in to recovery, and when I connected the phone I got a error on Windows that the device malfunctioned.
And since then also when I'm in fastboot the system won't recognize the phone anymore.
When the phone is on, I can run adb commands without problems.
I've tired everything, uninstalling and reinstalling drivers, Hisuite, other USB ports....
When I wiped the system, before flashing magisk again, I forgot to enable USB debugging and OEM unlock in developer settings, (tho BL was unlocked from before).
When I connect the phone in recovery, it shows in Windows as a failed mass storage device.
In fastboot I got to the point to have the right driver (Android bootloader interface) shown up, but it fails to start.
Anyone has a clue of what is happening?
I freaked out for a while thinking I might have done something wrong.
Turned out that Windows is the problem, since adb and fastboot are both working well on Ubuntu.
Luinwethion said:
I freaked out for a while thinking I might have done something wrong.
Turned out that Windows is the problem, since adb and fastboot are both working well on Ubuntu.
Click to expand...
Click to collapse
There is a regfile fix in mankindtws hwota thread, see if that one helps.
Or you could Google how to completely uninstall drivers, then reinstall minimal adb & fastboot.
ante0 said:
There is a regfile fix in mankindtws hwota thread, see if that one helps.
Or you could Google how to completely uninstall drivers, then reinstall minimal adb & fastboot.
Click to expand...
Click to collapse
Thanks, I found this register hack, and also made sure to reinstall all drivers from 0 but somehow Windows still refuses to recognize my phone.
I guess a reinstall is the best way of solving it. Or using Ubuntu from now on....
Luinwethion said:
Thanks, I found this register hack, and also made sure to reinstall all drivers from 0 but somehow Windows still refuses to recognize my phone.
I guess a reinstall is the best way of solving it. Or using Ubuntu from now on....
Click to expand...
Click to collapse
I ran into this also and I un-installed HiSuite, then re-installed it and after that in device manager set up drivers as seen in screen copy in attachement.
I also refer to this page for more info: https://www.dc-unlocker.com/huawei-mate-10-fastboot-usb-device-not-recognised-fix
Luinwethion said:
Hi Guys,
I might have ****ed up something,
I was on B131-SP1, rooted with magisk, I wanted to install B137, so I ran the magisk uninstall, repacked the B137 update, and ran the OTA.bat, everything went ok.
I wanted a fresh install, so I went in the recovery and wiped data.
To get root back I booted the phone in fastboot, and ran the magisk installer, and it asked to disconnect the phone and boot in to recovery,
everything ok, booted the phone in to recovery, and when I connected the phone I got a error on Windows that the device malfunctioned.
And since then also when I'm in fastboot the system won't recognize the phone anymore.
When the phone is on, I can run adb commands without problems.
I've tired everything, uninstalling and reinstalling drivers, Hisuite, other USB ports....
When I wiped the system, before flashing magisk again, I forgot to enable USB debugging and OEM unlock in developer settings, (tho BL was unlocked from before).
When I connect the phone in recovery, it shows in Windows as a failed mass storage device.
In fastboot I got to the point to have the right driver (Android bootloader interface) shown up, but it fails to start.
Anyone has a clue of what is happening?
Click to expand...
Click to collapse
Hi, I have the same problem after upgrading to 137 version. If the phone is on works with debug usb, also in fastboot mode works. Only in recovery mode windows doesn't find driver. Have you solved?
AntoRei said:
Hi, I have the same problem after upgrading to 137 version. If the phone is on works with debug usb, also in fastboot mode works. Only in recovery mode windows doesn't find driver. Have you solved?
Click to expand...
Click to collapse
So I reinstalled my PC from scratch, and I could get adb working, but no fastboot, so I ended up using Linux live flash drive.
Luinwethion said:
So I reinstalled my PC from scratch, and I could get adb working, but no fastboot, so I ended up using Linux live flash drive.
Click to expand...
Click to collapse
You can use this guide with linux?
https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
I flashed TWRP which worked, rebooted into TWRP so that still worked then tried wiping but got a mount error, I tested if it would install the img anyway and still mount error, so I changed slot from A to B, since then its just black screen and not recognised on PC at all.
dekadude said:
I flashed TWRP which worked, rebooted into TWRP so that still worked then tried wiping but got a mount error, I tested if it would install the img anyway and still mount error, so I changed slot from A to B, since then its just black screen and not recognised on PC at all.
Click to expand...
Click to collapse
First of all, what did you wipe in TWRP? /data?
Have you ever installed an OTA update? If not, you can't boot into the other slot. Same if you restored via MSM. You need to do one local upgrade until the B slot is bootable.
That will be what it is, I didn't do a OTA update. Is there a way to get back to the original slot?
I tried deleting data.
dekadude said:
That will be what it is, I didn't do a OTA update. Is there a way to get back to the original slot?
I tried deleting data.
Click to expand...
Click to collapse
Mounting and formatting of /data is not supported on older TWRPs. Try the most recent one from mauronofrio here on XDA if you want to format it (at least for custom ROMs).
For Oxygen OS I would suggest using "fastboot -w" instead as OOS still can't be decrypted.
Probably either use the MSM tool or use "fastboot --set-active=a" and then try "fastboot -w" if it doesn't boot.
I can't currently get into TWRP though at the moment, after I changed slots its just powered off all the time and not recognised on pc I haven't used any tools though.
So I guess MSM tool might work, but would that work if currently the pc isn't recognising a usb device connected?
dekadude said:
I can't currently get into TWRP though at the moment, after I changed slots its just powered off all the time and not recognised on pc I haven't used any tools though.
So I guess MSM tool might work, but would that work if currently the pc isn't recognising a usb device connected?
Click to expand...
Click to collapse
It should automatically download the drivers if you connect it in EDL mode.
Macusercom said:
It should automatically download the drivers if you connect it in EDL mode.
Click to expand...
Click to collapse
Great, whats best guide for that, I will mention its the China version of phone think its HD1910
dekadude said:
Great, whats best guide for that, I will mention its the China version of phone think its HD1910
Click to expand...
Click to collapse
Download the correct version here and follow the instructions: https://forum.xda-developers.com/7t-pro/how-to/op7tpro-unbrick-tool-to-restore-device-t4002909
Macusercom said:
Download the correct version here and follow the instructions: https://forum.xda-developers.com/7t-pro/how-to/op7tpro-unbrick-tool-to-restore-device-t4002909
Click to expand...
Click to collapse
Thanks for help so far, one final thing I hope when I picked up phone it gave me the full screen battery power too low to turn on message so it gave me hope I can fix it, I charged it for about 10 minutes and it gave me the "bootloader unlocked press power to pause" screen.
What is best thing to do here? Let it fully charge then connect to PC and try the MSM tool or let it drain and then connect to pc instead of charger and let it charge till its recognised by pc?
dekadude said:
Thanks for help so far, one final thing I hope when I picked up phone it gave me the full screen battery power too low to turn on message so it gave me hope I can fix it, I charged it for about 10 minutes and it gave me the "bootloader unlocked press power to pause" screen.
What is best thing to do here? Let it fully charge then connect to PC and try the MSM tool or let it drain and then connect to pc instead of charger and let it charge till its recognised by pc?
Click to expand...
Click to collapse
Charge it for an hour with a wall plug and then follow the MSM tool instructions.
Macusercom said:
Charge it for an hour with a wall plug and then follow the MSM tool instructions.
Click to expand...
Click to collapse
Actually, I noticed I am able to now get into TWRP without connecting to pc, and switch back to slot A, but it said no OS installed.
Do I still need to flash via the MSM tool or can I just update TWRP then install stock rom, update then go back into TWRP and install custom? Or what is best way?
dekadude said:
Actually, I noticed I am able to now get into TWRP without connecting to pc, and switch back to slot A, but it said no OS installed.
Do I still need to flash via the MSM tool or can I just update TWRP then install stock rom, update then go back into TWRP and install custom? Or what is best way?
Click to expand...
Click to collapse
You can either flash OOS via the latest TWRP (and probably do fastboot -w) or I would just use the MSM tool which is much easier and gets you a fresh install
EDIT : Problem Solved!