Evening all. I've done a very dumb thing. While wiping my device for a clean install in TWRP, I foolishly checked the "system" partition and wiped everything out.
Currently I have ADB set up correctly on my Mac, TWRP running on my phone but I'm stumped because I haven't used ADB in quite some time.
Can anyone help me with instructions (or a link to them) on how to restore my phone to it's former glory?
I should also tell you that I've tried following the instructions found with the Google Factory Images, but I'm unable to flash anything. I get "permission denied" messages. I'm thinking this is because I have no ROM and therefore no settings to allow me access to developer settings.
The bootloader is unlocked... but I'm stuck.
If you have TWRP, enter it. Connect your N6 to your Mac. Copy a custom ROM or one of the stock ROM flashable zips to internal storage, then install it using TWRP.
ADB isn't necessary.
What I'm doing and seeing...
I start the phone in the bootloader and plug it in. The phone sees that it's plugged in.
If I "adb devices" now, I get no results.
If I start TWRP and enter "adb devices", I see a serial and the word "recovery"
I can reboot the bootloader via adb, but that's it.
If I enter any action after that, like: "fastboot flashing unlock", or "flash-all", it returns < waiting for any device >, or permission denied.
Strephon Alkhalikoi said:
If you have TWRP, enter it. Connect your N6 to your Mac.
Click to expand...
Click to collapse
Thought about that earlier, of course. My phone isn't connecting to my Mac. I'm not seeing it as a drive in Finder.
nathanotis said:
My phone isn't connecting to my Mac.
Click to expand...
Click to collapse
I uninstalled and reinstalled android file manager. I'm pulling down a new rom, now. Fingers crossed.
That was easy...
nathanotis said:
What I'm doing and seeing...
I start the phone in the bootloader and plug it in. The phone sees that it's plugged in.
If I "adb devices" now, I get no results.
If I start TWRP and enter "adb devices", I see a serial and the word "recovery"
I can reboot the bootloader via adb, but that's it.
If I enter any action after that, like: "fastboot flashing unlock", or "flash-all", it returns < waiting for any device >, or permission denied.
Click to expand...
Click to collapse
In twrp Fastboot commands not work. And in bootloader adb commands not wotk
@nathanotis: It's for situations like this that I always store a copy of the ROM I use in internal storage. Perhaps you should do the same.
Strephon Alkhalikoi said:
Perhaps you should do the same.
Click to expand...
Click to collapse
Solid advice. Thank you.
If that ever happens again, you can always use NRT. I did that one time and used WUG's to flash a factory image and start over
Related
Hey guys,
First of all I'd like to apoligize for my english skills and a thread if I've posted in a wrong one category.
However, I have REALLY serious problem right now and I'll try to explain. Today I decided to reset my phone (settings - back up & reset). This didin't help me as I was expected therefore I wiped out all the data by using TWRP(yes, I'm a noob). Thought that it will erase everything but the ROM. I tried to do a reboot and the phone did the htc quietly brilliant logo but got caught at the beats audio logo screen and never advanced.
Went into recovery and tried to do a factory reset, and a whole bunch of other things (tried to reboot system, but is says that no os installed). The phone still gets stuck at the same screen. Also, I am unable to get it to be accessible on my computer again. it says that installing new device but nothing happens, so I have no way how to get into sdcard and mount a new ROM or something. Is there any way how to fix it?? How to install a new ROM when USB not working and there's no way to take off SD card.....?
Nelayme said:
How to install a new ROM when USB not working and there's no way to take off SD card.....?
Click to expand...
Click to collapse
TWRP has an option to enable adb sideload. Then you can adb push rom.zip
BenPope said:
TWRP has an option to enable adb sideload. Then you can adb push rom.zip
Click to expand...
Click to collapse
Nothing happens, actually. All I can see is " Usage: adb sideload filename.zip, Updating partition details... Starting ADB sideload feature" and that's it. Waited for 5 min and still nothing..
Nelayme said:
Nothing happens, actually. All I can see is " Usage: adb sideload filename.zip, Updating partition details... Starting ADB sideload feature" and that's it. Waited for 5 min and still nothing..
Click to expand...
Click to collapse
You go into TWRP and enable sideload mode, it will do nothing but say sideload is being started. Then copy whatever ROM you want into the same folder as fastboot and adb. Open up a new command window and type "adb sideload rom.zip", obviously name your ROM "rom.zip" and click enter ... In the command window you should see a percentage figure start to increase as it pushes it to your phone. When it's completed just flash the ROM like normal in TWRP.
AllAboutTheCore said:
You go into TWRP and enable sideload mode, it will do nothing but say sideload is being started. Then copy whatever ROM you want into the same folder as fastboot and adb. Open up a new command window and type "adb sideload rom.zip", obviously name your ROM "rom.zip" and click enter ... In the command window you should see a percentage figure start to increase as it pushes it to your phone. When it's completed just flash the ROM like normal in TWRP.
Click to expand...
Click to collapse
I tried doing that myself but never got a percentage showing me anything I freaked out at first ten I just like it do it's thing until it said it transferred
Sent from inside the T.A.R.D.I.S
joselv456 said:
I tried doing that myself but never got a percentage showing me anything I freaked out at first ten I just like it do it's thing until it said it transferred
Sent from inside the T.A.R.D.I.S
Click to expand...
Click to collapse
Another option is to just use an OTG cable and flash a ROM from a flash drive.
AllAboutTheCore said:
You go into TWRP and enable sideload mode, it will do nothing but say sideload is being started. Then copy whatever ROM you want into the same folder as fastboot and adb. Open up a new command window and type "adb sideload rom.zip", obviously name your ROM "rom.zip" and click enter ... In the command window you should see a percentage figure start to increase as it pushes it to your phone. When it's completed just flash the ROM like normal in TWRP.
Click to expand...
Click to collapse
Just tried what you said and still nothing. There're somekinda problems with USB, I'm even unable to connect my phone.. When I typed "adb sideload rom.zip" it was saying "error: device not found" only. Will try to reinstall htc sync drivers, but I think it won't help.. Any other ideas how to back my htc to life (didin't try with OTG cable yet)?
Nelayme said:
Just tried what you said and still nothing. There're somekinda problems with USB, I'm even unable to connect my phone.. When I typed "adb sideload rom.zip" it was saying "error: device not found" only. Will try to reinstall htc sync drivers, but I think it won't help.. Any other ideas how to back my htc to life (didin't try with OTG cable yet)?
Click to expand...
Click to collapse
OTG cable should work and is the easiest way to do it but if not you might want to check this thread .. http://forum.xda-developers.com/showthread.php?t=2363516
See this post, might help
http://forum.xda-developers.com/showpost.php?p=44730345&postcount=13
AllAboutTheCore said:
OTG cable should work and is the easiest way to do it but if not you might want to check this thread .. http://forum.xda-developers.com/showthread.php?t=2363516
Click to expand...
Click to collapse
Hey mate,
I just got OTG cable, moved a new Rom into USB stick and tried to mount on TWRP. All I got was "E: Unable to mount '/usb-otg'. Maybe I've missed couple of steps before?
FIXED: All I had to do is to format an USB stick in FAT32. Everything went well and now I can use my phone once again. Thanks a lot for your help, hope it will help to others as well.
Cheers!
Ok here is the skinny. I have the Sprint HTC 1. Currently rooted and running Beanstalk 4.3 and TWRP 2.5 ... I have read, re read, and read again how to update my TWRP to 2.6.3 and have no luck.
I have tried Terminal Emulator
I have tired Goo Manager. It actually down loads the file. Runs through the process. Never reboots or updates
I have tried Fastboot. For what ever reason my computer does not pick up and adb devices. It shows Fastboot USB
Any thoughts. I had some unlock this one for me and throw TWRP on. All my others I have done myself.
I love TWRP..but if I cannot fix...what is the easiest way to put Philz or CWM on instead?
Want to update a ROM to 4.4 Kitkat but cannot with out an updated recovery
jaykspokane said:
Ok here is the skinny. I have the Sprint HTC 1. Currently rooted and running Beanstalk 4.3 and TWRP 2.5 ... I have read, re read, and read again how to update my TWRP to 2.6.3 and have no luck.
I have tried Terminal Emulator
I have tired Goo Manager. It actually down loads the file. Runs through the process. Never reboots or updates
I have tried Fastboot. For what ever reason my computer does not pick up and adb devices. It shows Fastboot USB
Any thoughts. I had some unlock this one for me and throw TWRP on. All my others I have done myself.
I love TWRP..but if I cannot fix...what is the easiest way to put Philz or CWM on instead?
Want to update a ROM to 4.4 Kitkat but cannot with out an updated recovery
Click to expand...
Click to collapse
While in fastbootusb check your drivers
Device not recognized? (If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
BD619 said:
While in fastbootusb check your drivers
Device not recognized? (If you are using Windows 8.1 this will most likely not work)
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good
Click to expand...
Click to collapse
Updated the drives. In Fastboot now. on my cmd prompt c:\user\user wont tried typing and ADB Devices and nothiing
In fastbootusb type fastboot devices
BD619 said:
In fastbootusb type fastboot devices
Click to expand...
Click to collapse
Now I am thinking it it my computer. Just re enstalled the SDK packet. Changed path to all c:/Android-ADB and says not a recognizable internal or external file
At this point I need some sleep. Eyes are going crossed.
jaykspokane said:
Now I am thinking it it my computer. Just re enstalled the SDK packet. Changed path to all c:/Android-ADB and says not a recognizable internal or external file
At this point I need some sleep. Eyes are going crossed.
Click to expand...
Click to collapse
PM me tomorrow and I'll help you out
BD619 said:
PM me tomorrow and I'll help you out
Click to expand...
Click to collapse
Sorry been a crazy new year. Still need help.
So downloaded SDK pack. I have tried ADB shell. Fastboot ... etc etc. When in Fastboot I run ADB Devices and nothing is found. however if i have the phone on it works.
at this point...maybe a new recovery?
jaykspokane said:
Sorry been a crazy new year. Still need help.
So downloaded SDK pack. I have tried ADB shell. Fastboot ... etc etc. When in Fastboot I run ADB Devices and nothing is found. however if i have the phone on it works.
at this point...maybe a new recovery?
Click to expand...
Click to collapse
While in bootloader/fastbootusb type fastboot devices
adb devices =OS and recovery
fastboot devices = bootloader/fastbootusb
BD619 said:
While in bootloader/fastbootusb type fastboot devices
adb devices =OS and recovery
fastboot devices = bootloader/fastbootusb
Click to expand...
Click to collapse
Ok... recognized a device was attached. So type the following
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
and I got error cannot open 'openrecovery-twrp-2.6.3.0-m7wls.img'
This is TWRPS guidelines
Download the above file into your platform-tools dir. Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
Note that you will need to change the last part to match the name of the file that you just downloaded. This method requires that you have the drivers installed that come with the HTC Sync software that are available here. You will also need adb and fastboot for your computer.
jaykspokane said:
Ok... recognized a device was attached. So type the following
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
and I got error cannot open 'openrecovery-twrp-2.6.3.0-m7wls.img'
This is TWRPS guidelines
Download the above file into your platform-tools dir. Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list. Plug the device into your computer. If you have the right drivers installed, your screen should now say FASTBOOT USB. Run the following command via the command line:
fastboot flash recovery recoveryfilename.img
Note that you will need to change the last part to match the name of the file that you just downloaded. This method requires that you have the drivers installed that come with the HTC Sync software that are available here. You will also need adb and fastboot for your computer.
Click to expand...
Click to collapse
Try
fastboot erase cache <enter>
then
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img <enter>
You did install the android sdk right?
BD619 said:
Try
fastboot erase cache <enter>
then
fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img <enter>
You did install the android sdk right?
Click to expand...
Click to collapse
I did. Just to make certain the other night...I down loaded the Android SDK pack. i can run ADB and Fastboot. Pulls all the info etc.
Will try erase cache
jaykspokane said:
I did. Just to make certain the other night...I down loaded the Android SDK pack. i can run ADB and Fastboot. Pulls all the info etc.
Will try erase cache
Click to expand...
Click to collapse
What does this mean?
BD619 said:
What does this mean?
Click to expand...
Click to collapse
Sorry. Meant it just lists all the available command for each respectively...lists the commands etc.
So did the erase and still same error.
All my apps and data are backed up on Titanium. How hard would it be to just have a new recovery installed?
jaykspokane said:
Sorry. Meant it just lists all the available command for each respectively...lists the commands etc.
So did the erase and still same error.
All my apps and data are backed up on Titanium. How hard would it be to just have a new recovery installed?
Click to expand...
Click to collapse
Navigate to the platform tools folder
Press shift and right click inside the folder and choose open cmd here
jaykspokane said:
Sorry. Meant it just lists all the available command for each respectively...lists the commands etc.
So did the erase and still same error.
All my apps and data are backed up on Titanium. How hard would it be to just have a new recovery installed?
Click to expand...
Click to collapse
May be a moot point. I am upgrading to a Team Nocturnal_xR1 which is a 4.4 ROM. So far it has been loading and allowed the file on a TWRP 2.5.0.0 version. I still need to upgrade the TWRP version. Right now looks like it may work.
jaykspokane said:
May be a moot point. I am upgrading to a Team Nocturnal_xR1 which is a 4.4 ROM. So far it has been loading and allowed the file on a TWRP 2.5.0.0 version. I still need to upgrade the TWRP version. Right now looks like it may work.
Click to expand...
Click to collapse
back to square one. LOL.
and no opening cmd from there did not work either
Check PM
I had a similar issue where I needed the updated twrp. I ended up using the original AIO toolkit that I used to root the phone/unlock the phone to begin with.
I found the latest version of the AIO (made by Hasoon: http://www.hasoon2000.info/getdownl...obile,ATT,Sprint)/One_All-In-One_Kit_v3.1.rar) and the latest image of TWRP from here: http://teamw.in/twrp_view_all_devices.
After installing hasoon, stick the downloaded image in the data/recoveries folder w/in the folders from the AIO. Next use the "Your Own Recovery" option under the flash a recovery option and choose that image instead. Worked great for me several times. Hopefully it does for you. Let me know if you have question.
BD619 said:
Check PM
Click to expand...
Click to collapse
When I normally plug my htc one into my laptop that is running win 8.1 64 bit. It shows that my phone is connected and opens files for me to view What is on my phone. When I'm in boot loader and I plug it in (I'm trying to unlock it to root) I hear the notification sound that the phone is connected to computer but the file box doesn't open showing me what's on the phone. Is this normal? If so, how do I open cmd prompt to type in OEM command and what should the command initially say before I type my oem command? Thanks for any help you can give.
dcm1200 said:
When I normally plug my htc one into my laptop that is running win 8.1 64 bit. It shows that my phone is connected and opens files for me to view What is on my phone. When I'm in boot loader and I plug it in (I'm trying to unlock it to root) I hear the notification sound that the phone is connected to computer but the file box doesn't open showing me what's on the phone. Is this normal? If so, how do I open cmd prompt to type in OEM command and what should the command initially say before I type my oem command? Thanks for any help you can give.
Click to expand...
Click to collapse
You will not see you data in bootloader mode. What is your bootloader version? You will not be able to send fastboot commands using windows 8.1 with hboot 1.44.
open the cmd prompt from your adb/fastboot.exe folder and type
Code:
fastboot devices
and see if the device is recognized by your computer
and go see those video guide here: http://forum.xda-developers.com/htc-one#root
Be sure to use the latest htc drivers and latest android sdk (abd/fastboot)
And again, you will not be able to use fastboot with a win8.1 computer if your bootloader is 1.44
dcm1200 said:
When I normally plug my htc one into my laptop that is running win 8.1 64 bit. It shows that my phone is connected and opens files for me to view What is on my phone. When I'm in boot loader and I plug it in (I'm trying to unlock it to root) I hear the notification sound that the phone is connected to computer but the file box doesn't open showing me what's on the phone. Is this normal? If so, how do I open cmd prompt to type in OEM command and what should the command initially say before I type my oem command? Thanks for any help you can give.
Click to expand...
Click to collapse
Sorry mate but I will not troubleshoot via PM because its too much confusing and other members can't help you if you send me pm. Keep posting here it will be much easier. Hope you understand
QUOTE=alray;50379334]Sorry mate but I will not troubleshoot via PM because its too much confusing and other members can't help you if you send me pm. Keep posting here it will be much easier. Hope you understand [/QUOTE
But after flashing twrp recovery and copying supersu to internal storage I erased cache in cms before going into recovery mode then unzipped supersu and rebooted phone. I opened super su and said that there is no binary file or that it is not working. I also dl'ed a root checker and it said that I'm not rooted. Any ideas on what to do now?
dcm1200 said:
QUOTE=alray;50379334]Sorry mate but I will not troubleshoot via PM because its too much confusing and other members can't help you if you send me pm. Keep posting here it will be much easier. Hope you understand [/QUOTE
But after flashing twrp recovery and copying supersu to internal storage I erased cache in cms before going into recovery mode then unzipped supersu and rebooted phone. I opened super su and said that there is no binary file or that it is not working. I also dl'ed a root checker and it said that I'm not rooted. Any ideas on what to do now?
Click to expand...
Click to collapse
install superSU.zip the same as you install a rom in recovery
clsA said:
install superSU.zip the same as you install a rom in recovery
Click to expand...
Click to collapse
Please pardon my ignorance but I'm new to this. How? Is it the same basic way that I flashed twrp to my phone?
i was trying to root my onepluse 3t with nougat 7 update but i stuck in twrp asking for password and i cannot use twrp to install super su cuz of that
then after many Attempts i don't know what i did exactly i try to wipe and mount then the system was removed and phone is opening on twrp and bootloader only.
i download nougat 7 update file and i try to install it from twrp but i can't and i try from adb (sdk) more than 100 times but not work giving error (closed)
now my phone is not working and i don't know what to do
pls any one help
Try reformating your internal data (including sdcard) using twrp, plug it to a pc, use mtp to copy the latest full rom to it, flash that and voila.
Jo_Jo_2000 said:
Try reformating your internal data (including sdcard) using twrp, plug it to a pc, use mtp to copy the latest full rom to it, flash that and voila.
Click to expand...
Click to collapse
i try every thing i install stock recovery and i but nougat in internal storage but when trying to press install from internal storage nothing happens it is not active
i try also to install nougat using adb sideload but every time reach to 45% then stop and giving failed message
amrfoudaas said:
i was trying to root my onepluse 3t with nougat 7 update but i stuck in twrp asking for password and i cannot use twrp to install super su cuz of that
then after many Attempts i don't know what i did exactly i try to wipe and mount then the system was removed and phone is opening on twrp and bootloader only.
i download nougat 7 update file and i try to install it from twrp but i can't and i try from adb (sdk) more than 100 times but not work giving error (closed)
now my phone is not working and i don't know what to do
pls any one help
Click to expand...
Click to collapse
So it sounds like the phone had a problem with Encryption. Not a problem.. If you can get into the phone set the password for your screen lock and this will reset your encryption. However it seems like you can't get this far. Again no problem. The password issue is there probably isn't a password on TWRP. When it prompts you for a password hit cancel. If this is the case and you may notice your drive space is zero. If it is post here and I will try to help you through that.
DarqAnshin said:
So it sounds like the phone had a problem with Encryption. Not a problem.. If you can get into the phone set the password for your screen lock and this will reset your encryption. However it seems like you can't get this far. Again no problem. The password issue is there probably isn't a password on TWRP. When it prompts you for a password hit cancel. If this is the case and you may notice your drive space is zero. If it is post here and I will try to help you through that.
Click to expand...
Click to collapse
i try that too and when press cancel the drive space is showing zero i try every password i know and (default_password) too
then i try to install custom rom hydrogen from TWRP and i success but i was stupid to try to update it to official nougat again manually then every thing remain to the same again i am stuck in TWRP window or fastboot
i try to install hydrogen again from TWRB but not success again and i cannot use the phone
amrfoudaas said:
i try that too and when press cancel the drive space is showing zero i try every password i know and (default_password) too
then i try to install custom rom hydrogen from TWRP and i success but i was stupid to try to update it to official nougat again manually then every thing remain to the same again i am stuck in TWRP window or fastboot
i try to install hydrogen again from TWRB but not success again and i cannot use the phone
Click to expand...
Click to collapse
If you can get into TWRP after hitting cancel then this isn't a problem. These are the steps you need to take to load Nougat (or any OS) on to your phone.
Boot into your recovery (TWRP in your case).
You will slide to cancel then hit Advanced.
Wipe The phone of everything (System/cache/etc).
Click Sideload and then plug into your computer of choice.
On your computer open a command prompt and type the following:
ADB Devices
This should show you your devices if your phone is connected to the computer. If you do not see anything then install the drivers onto your computer (If it says that you don't have ADB then install Android Bridge onto your system).
Next type:
ADB Sideload <Name of your Nougat image>
Once this is done your phone should be able to boot into the system.
DarqAnshin said:
If you can get into TWRP after hitting cancel then this isn't a problem. These are the steps you need to take to load Nougat (or any OS) on to your phone.
Boot into your recovery (TWRP in your case).
You will slide to cancel then hit Advanced.
Wipe The phone of everything (System/cache/etc).
Click Sideload and then plug into your computer of choice.
On your computer open a command prompt and type the following:
ADB Devices
This should show you your devices if your phone is connected to the computer. If you do not see anything then install the drivers onto your computer (If it says that you don't have ADB then install Android Bridge onto your system).
Next type:
ADB Sideload <Name of your Nougat image>
Once this is done your phone should be able to boot into the system.
Click to expand...
Click to collapse
i try hundred times giving error: closed
amrfoudaas said:
i try hundred times giving error: closed
Click to expand...
Click to collapse
if you are getting error closed your adb bridge session might be the problem.
Unplug your phone from the USB
From your computer try these commands
Code:
adb kill-server
Code:
adb start-server
Then plug the phone back into the usb and put it into sideload on twrp and type
Code:
adb devices
Do you see a device then?
DarqAnshin said:
if you are getting error closed your adb bridge session might be the problem.
Unplug your phone from the USB
From your computer try these commands
Code:
adb kill-server
Code:
adb start-server
Then plug the phone back into the usb and put it into sideload on twrp and type
Code:
adb devices
Do you see a device then?
Click to expand...
Click to collapse
yes it is there and i start the sideload for nougat but it is stopped in 45% not reach 100 many times
amrfoudaas said:
yes it is there and i start the sideload for nougat but it is stopped in 45% not reach 100 many times
Click to expand...
Click to collapse
and sometimes giving error closed
Try this it should work
http://forum.xda-developers.com/one...k-unbrick-tutorial-oneplus-3t-t3515306/page10
This question seems to keep repeating itself due to missing information on TWRP post about the latest official version being incompatible with OOS 4 encryption method, but that is the explanation. There is a beta release of TWRP in post 550 in that thread that is supposed to fix this.
pitrus- said:
This question seems to keep repeating itself due to missing information on TWRP post about the latest official version being incompatible with OOS 4 encryption method, but that is the explanation. There is a beta release of TWRP in post 550 in that thread that is supposed to fix this.
Click to expand...
Click to collapse
Which thread is that? Can you link to it please?
m0d hipp¥ said:
Which thread is that? Can you link to it please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=70403073
I have ran into a bit of an odd problem due to me messing up a root and then messing my phone up even more while trying to fix it.
my phone is fully bricked and only boots into fastboot mode. i tried to fix it with the one-plus fixer (idk its official name) but i got an error 7. I now need to re flash an older version of TWRP and try a diffrent method but i cant as my phone no longer is recognized in fastboot using the ADB tool. I have the USB driver installed on Windows. On Linux i ran the .sh script as root and it still doesn't work.
I have both Ubuntu and Windows installed on my PC so i can do whatever you suggest me to do regardless of the os.
Thank you to anyone that can help in advanced
Malte
This is not a hardbrick; a hard one wouldn't boot at all and give no sign of life (except when plugged to PC).
Try an unbrick tool to revert to official OOS. On Windows 7+ remember to disable signed driver enforcement.
You mention fastboot and adb. Which one are you using?
Just to make sure: While in the bootloader (fastboot mode), adb does not work. You have to use the fastboot commands. Installing TWRP would be:
Code:
fastboot flash recovery <name-of-img-file>
If that's what you're already trying, just ignore this post.
I want to be able to do that but if i do adb devices it no longer finds my phone
Didgeridoohan said:
You mention fastboot and adb. Which one are you using?
Just to make sure: While in the bootloader (fastboot mode), adb does not work. You have to use the fastboot commands. Installing TWRP would be:
Code:
fastboot flash recovery <name-of-img-file>
If that's what you're already trying, just ignore this post.
Click to expand...
Click to collapse
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Ive done this but it didnt fix my phone.
przemcio510 said:
This is not a hardbrick; a hard one wouldn't boot at all and give no sign of life (except when plugged to PC).
Try an unbrick tool to revert to official OOS. On Windows 7+ remember to disable signed driver enforcement.
Click to expand...
Click to collapse
I did this last night but it never fixed my phone. it boots and then says "md5 checksum error" so im needing to try a diffrent approach but i cant because i cant flash anything onto it due to adb not finding my device now
Bandella said:
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Click to expand...
Click to collapse
Like I said, the adb commands won't work while in the booloader (that's why it's called fastboot mode). You need to use fastboot commands... The equivalent command would be:
Code:
fastboot devices
Bandella said:
I did this last night but it never fixed my phone. it boots and then says "md5 checksum error" so im needing to try a diffrent approach but i cant because i cant flash anything onto it due to adb not finding my device now
Click to expand...
Click to collapse
I had the same issues with md5, all you have to do is try a different USB port. I suggest the ones on your motherboard if you're on a PC. Then run the tool as administrator. I hope this helps, good luck!
P.S if it still doesn't work, try a different PC, I'm 100% sure it'll work
Bandella said:
I want to be able to do that but if i do "adb devices" in the cmd/terminal it no longer finds my phone. so my goal is to be able to execute that command. However, i may be mistaken that it doesnt need to find my phone i can just execute that command
Click to expand...
Click to collapse
As Didgeridoohan touched upon, adb and fastboot (while related) are different. They have different requirements and applications.
adb won't work while the device is in fastboot mode. Conversely, when the device is able to use adb, fastboot commands won't work.
adb: only works booted to OS or alternately in TWRP. Debugging must be enabled
fastboot: only works in bootloader-fastboot mode. Debugging is not required to be enabled.
For flashing TWRP, it's fastboot that you need. Well, there is a way to do it with adb, but fastboot is by far the more common way.
When in fastboot mode, adb command won't work, and there fore it is completely expected that "adb devices" yields not response. Try "fastboot devices" (no quotes) and if you get the phone's ID in response, you are in business.
Bandella said:
...
my phone ... only boots into fastboot mode...
Click to expand...
Click to collapse
I've had this happen to me when I've triggered dm-verity. Instead of getting the dm-verity warning display the phone would simply boot straight back to fastboot.
My solution was to:
- flash the latest TWRP using
Code:
fastboot flash recovery <recovery file. img>
- reboot into recovery (use the volume keys on the phone to select recovery and then press the power key)
-flash the full stock image I was using before the problem started
This would clean up any changes made to the boot and system images and allow me to boot the system normally.
Note: because this leaves you with a stock kernel you'll end up with the stock recovery after you boot the system.
Sent from my OnePlus3T using XDA Labs
boot your PC into Ubuntu and install adb/fastboot (tons of guides available off the 'net). then boot your 3t to dl mode and connect it to your PC. as mentioned already "fastboot devices" should list your 3t and you should now be able to flash to your heart's content. no need for drivers, unlike under Windows. i have a bootable linux usb drive primarily for this reason. curious what script you're trying to run though..