[Q] Accidentally wiped system and data partition - HTC One X+

Hello everyone.
In attempting to install a ROM using TWRP, I accidentally wiped the system and data partitions. So I now have no OS on the phone. I can still boot into recovery. adb is not seeing my device. fastboot is seeing my device however. How do I proceed from here to install an OS or is the phone bricked?
Is USB debugging required in order for adb to work?

Found problem
Spannercrank said:
Hello everyone.
In attempting to install a ROM using TWRP, I accidentally wiped the system and data partitions. So I now have no OS on the phone. I can still boot into recovery. adb is not seeing my device. fastboot is seeing my device however. How do I proceed from here to install an OS or is the phone bricked?
Is USB debugging required in order for adb to work?
Click to expand...
Click to collapse
I was trying to use a USB 3 port. It worked with a USB 2 port. Phone is installed and up and running.

Spannercrank said:
I was trying to use a USB 3 port. It worked with a USB 2 port. Phone is installed and up and running.
Click to expand...
Click to collapse
Hi, don't panic, it happened to me once and I followed this link http://forum.xda-developers.com/showthread.php?t=1667929 also there are some youtube videos on this .. (http://www.youtube.com/watch?v=ZTX5tq29xP8).

Related

htc one with os

I tried installing a rom on my HTC one and it messed everything up. I have no data and no OS on my phone. I i did not make a backup as well....
ive been trying to use twrp sideload but my device wont connect to adb. what do i doooo? i can only get into the fastboot menu and trwp recovery. can i use a otg cord and transfer another rom into my phone or do i have to wait for att ruu? please help me! thanks. adb wont connect at all even in fastboot.
Miilkman said:
I tried installing a rom on my HTC one and it messed everything up. I have no data and no OS on my phone. I i did not make a backup as well....
ive been trying to use twrp sideload but my device wont connect to adb. what do i doooo? i can only get into the fastboot menu and trwp recovery. can i use a otg cord and transfer another rom into my phone or do i have to wait for att ruu? please help me! thanks. adb wont connect at all even in fastboot.
Click to expand...
Click to collapse
if you can't get adb working then you need an OTG cable.

Twrp Swipe to wipe Crash -

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.

Driver problems on Recovery and Fastboot after trying magisk.

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

PLEASE HELP I BROKE MY PHONE

Last month I accidentally deleted twrp from my phone by flashing a corrupt file, so i was stuck in lineage os, today I when I wanted to factory reset my phone, it booted to fastboot mode, now when I connect it with my laptop, it says usb device not recognized and when I type fastboot device in cmd nothing happends. Please help.
Change usb port use usb 2.0 not 3.0, does it say fastboot in your device still?
redjavla said:
Last month I accidentally deleted twrp from my phone by flashing a corrupt file, so i was stuck in lineage os, today I when I wanted to factory reset my phone, it booted to fastboot mode, now when I connect it with my laptop, it says usb device not recognized and when I type fastboot device in cmd nothing happends. Please help.
Click to expand...
Click to collapse
Check the AMD Ryzen Fastboot Fix Guide and then Clean Install Custom ROM Guide in my POCO F1 Ultimate Collection & Guides thread.
Kenora_I said:
Change usb port use usb 2.0 not 3.0, does it say fastboot in your device still?
Click to expand...
Click to collapse
I used both nothing chqnges.
Yeah it still says fastboot.
Retrial said:
Check the AMD Ryzen Fastboot Fix Guide and then Clean Install Custom ROM Guide in my POCO F1 Ultimate Collection & Guides thread.
Click to expand...
Click to collapse
But my laptop is an intel.

Samsung A8 not being detected in download mode

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

Categories

Resources