trmacdonal said:
How to Restore your phone on a Windows PC using a Nandroid backup
I am going to assume you already have a Nandroid backup created on your SD card using JF 1.31's recovery Alt-B feature. The backup will create a folder called nandroid on your SD.
What you need:
The Android SDK:
Fastboot Windows Binary in this post:http://forum.xda-developers.com/showpost.php?p=3083753&postcount=1
From your Nandroid backup you need three files:
data.img
system.img
boot.img
Steps to restore your phone
1) Put the files Adb and AdbWinApi.dll from the tools folder in the Android SDK into C:\WINDOWS\System32 folder on your PC. Substitute the correct drive letter if windows is not installed on you C: drive
2) Put the Windows Fastboot.exe into the C:\WINDOWS\System32 folder on your PC
3) Create a folder on the C: drive of your PC called android. The path should be C:\Android.
4) Copy the Nandroid backup files data.img, system.img, and boot.img from your SD card to the folder called Android you created by mounting your SD card as removable disk.
5) Unplug the USB cord and power off your phone
6) Power up your phone by holding CAMERA+POWER, you should see three androids on skateboards. If you don't see this go install the Engineering boot loader
7) Plug the USB cord back into your phone and press back. The screen on your phone should say fastboot.
8) Make sure your pc is using the correct driver. Open the device manager on your pc. It is helpfull to have all other USB storage devices besides your phone unplugged for this part. Look for a USB Mass Storage device in the list of the USB devices. Right click on it and update the driver. Pick the option to browse for a driver on your pc. The driver is located in the Android SDK your downloaded in the folder called usb_driver. If this is done right you will now see a device called HTC Dream
9) Press start, go to run and type cmd (If you are on Vista just type cmd in the search box and hit enter). The command prompt will pop up.
10) Type cd C:\android
then enter the following commands:
fastboot flash system system.img
it will say Sending, then writing and say OKAY if it was successful
then type
fastboot flash userdata data.img
wait for the second OKAY and type
fastboot flash boot boot.img
wait for the second OKAY and type
fastboot reboot
Your phone should now be restored exactly as you had it when it was backed up.
Click to expand...
Click to collapse
I'm young yet in my android/linux learnings and this guide here is great. I've been soaking in information for weeks now on the boards but still, my kungfu is weak.
Hence I'm having an issue today and I've been working on it almost all day so far. Something happened and I ended up having to factory restore my phone and I'm attempting to recover from my nandroid backup files.
I've followed the above instructions to the letter, but now that I'm ready to do the actual fastboot flash system system.img command, I keep getting a "FAILED <command write failed <Too many links>> error". And I've searched high & low looking for a solution to this.
My HTC is correctly running in Fastboot as an ADB Interface in WinXP Pro SP3, I've got my nandroid backup files placed in the C:\Android folder on my pc as directed. Fastboot is in the /system32 folder (and in cmd Fastboot devices lists my phone), but I keep banging my head into this error over & over. Its driving me pretty insane and any help would be appreciated. I know you guys aren't a support desk and I'm probably screwing up something elementary, but I just wanted to say that I'm finally asking as a last resort. I've been trying to figure this out myself for about 9 hours now. My thanks in advance.
Xeroproject said:
I've followed the above instructions to the letter, but now that I'm ready to do the actual fastboot flash system system.img command, I keep getting a "FAILED <command write failed <Too many links>> error". And I've searched high & low looking for a solution to this.
Click to expand...
Click to collapse
If it transfers the image to the phone but aborts halfway or at the end, try adding a ferrite core to your usb cable at the host side, or use one with an integrated ferrite core.
Unfortunately we don't have the source to the SPL so I'm mostly clueless what the "too many links" error means. Alternatively, try on a different pc.
infernix said:
If it transfers the image to the phone but aborts halfway or at the end, try adding a ferrite core to your usb cable at the host side, or use one with an integrated ferrite core.
Unfortunately we don't have the source to the SPL so I'm mostly clueless what the "too many links" error means. Alternatively, try on a different pc.
Click to expand...
Click to collapse
Thanks for the suggestion, I'll have to see if I can find a suitable USB cable, although from some inquires to linux buddies more in the know, I was told it was indicating a "a circular reference symlink" either in fastboot or in the command I used.
Considering I used exactly the commands in the guide, I'm puzzled. Also, I pulled the fastboot.exe for win32 from JF's own attachment.
Regarding another PC, yes, that would be ideal for troubleshooting this, however the pc I have at home is Vista 64bit (unfortunately), so shouldn't I run into issues there?
Xeroproject said:
Hrm, sorry about the few posts in here mods, it seems my issue isn't related to a mistype in the command line of trmacdonal's guide like I thought it was, so its most likely not related to this thread & needs to be split into a separate thread to prevent clutter.
I have noticed something regarding my situation: in command line when I type "fastboot devices" it recognizes & lists my phone. However when I type "adb devices" it does not list my phone. Might this be related?
Click to expand...
Click to collapse
ADB won't see your device till it has booted into android.
And send me a PM with the post numbers and a new thread title and I will move your posts and any posts related to them.
So unfortunately getting any work done on this on my Vista machine has been a total no-go. Vista won't take the 64-bit homebrewed driver, regardless of disabling driver authentication.
So I'm stuck. Day 2 here and I still get the "too many links" error. I've since retraced all my steps, redownloaded the SDK, JF's fastboot-win32, and completely removed all drivers from the system (including registry entiries) then reinstalled everything, and tried a shielded USB cable today. Still pulling up that error.
Is there any information I can include that would help pinpoint whats causing this issue?
Xeroproject said:
So unfortunately getting any work done on this on my Vista machine has been a total no-go. Vista won't take the 64-bit homebrewed driver, regardless of disabling driver authentication.
So I'm stuck. Day 2 here and I still get the "too many links" error. I've since retraced all my steps, redownloaded the SDK, JF's fastboot-win32, and completely removed all drivers from the system (including registry entiries) then reinstalled everything, and tried a shielded USB cable today. Still pulling up that error.
Is there any information I can include that would help pinpoint whats causing this issue?
Click to expand...
Click to collapse
Have you tried booting normally at least once?
Maybe try "fastboot erase cache", then try again?
JesusFreke said:
Have you tried booting normally at least once?
Maybe try "fastboot erase cache", then try again?
Click to expand...
Click to collapse
If you mean booting normally into Vista 64, yes, it sees the G1 as an "unknown device" in Device Manager and when I point it to the 64-bit driver, it won't take it. Same for when driver auth is disabled. (although the message changes from "no device drivers found" to "this driver is not compatible with your device)
If you mean the phone, yes, the phone works, its not bricked, but there's a lot of data I'm losing if I can't solve this issue & backup from my nandroid backups.
I'll give the erase cache thing a shot now and post results, thanks for the suggestion.
interesting, the "fastboot erase cache" command also returns a "FAILED <status read failed <Too many links>>" error
Perhaps the problem is with the fastboot.exe file?
Xeroproject said:
interesting, the "fastboot erase cache" command also returns a "FAILED <status read failed <Too many links>>" error
Perhaps the problem is with the fastboot.exe file?
Click to expand...
Click to collapse
I doubt it. I remember seeing this error once when I stopped a fastboot flash while it was doing it's thing. I don't remember exactly what I did to fix it. I thought I just rebooted or something.
It's a shot in the dark, but maybe take the battery out for a few seconds and put it back in and try again?
I would also try any and all of the fastboot commands
If nothing else, you could try reflashing the engineering SPL, or even the RC29 nbh.
JesusFreke said:
I doubt it. I remember seeing this error once when I stopped a fastboot flash while it was doing it's thing. I don't remember exactly what I did to fix it. I thought I just rebooted or something.
It's a shot in the dark, but maybe take the battery out for a few seconds and put it back in and try again?
I would also try any and all of the fastboot commands
If nothing else, you could try reflashing the engineering SPL, or even the RC29 nbh.
Click to expand...
Click to collapse
Yeah, I wish I knew the cause of it, but the initial use was uninterrupted (and everytime I reboot, I will get 5-10sec lag before getting the error, while after that the error will popup immediately)
I'm happy to try any of the fastboot commands, but being a little nubbin, I'm a little afraid of doing any damage. I did try fastboot reboot and fastboot reboot-bootloader and got no response from the phone. "fastboot devices" immediately sees my phone. "fastboot flashall" returns: "error: neither -p product specified nor ANDROID_PRODUCT_OUT set".
Removing the battery is something I've done a couple times the other day, just gave it another shot now, same result. I've noticed the too many links error will say it "failed to read" on the first attempt, after that it reverts to "failed to write".
Concerning reloading the phone back to RC29....you mean taking it back to RC29, then reflashing the Engineering SPL, then immediately trying to backup from my nandroid backups? (prior to installing any of the JF OS versions?)
I have also faced this error few time, what I do is disconnect the USB, restart both PC and G1, next time I get proper connection, once time I was able to resolve just by moving the ramdisk.img and kernel file from the directory, this was when I was using the fastboot -w flashall command!!
-Pramod
Might be onto something there JF, I just checked my SPL edition and I'm running the HardSPL not the EngineSPL.
Is the HardSPL not suited for this perhaps?
for fastboot -w flashall to work you need to set the ANDROID_PRODUCT_OUT variable, where boot.img, recovery.img and system.img file are, on window just use the set command
set ANDROID_PRODUCT_OUT=c:\<your directory where the files are>
and then run fastboot -w flashall
-Pramod
pramods said:
for fastboot -w flashall to work you need to set the ANDROID_PRODUCT_OUT variable, where boot.img, recovery.img and system.img file are, on window just use the set command
set ANDROID_PRODUCT_OUT=c:\<your directory where the files are>
and then run fastboot -w flashall
-Pramod
Click to expand...
Click to collapse
Alright, I'm with you, just returned "error: could not load android-info.txt"
The same directory also need to have android-info.txt file, this file just have a single entry as board=trout in it, if you don't have it create this file and then run fastboot again
-Pramod
pramods said:
The same directory also need to have android-info.txt file, this file just have a single entry as board=trout in it, if you don't have it create this file and then run fastboot again
-Pramod
Click to expand...
Click to collapse
Alright, so I did a search on my computer to see if I had an android-info.txt I could copy over, didn't have anything (including in the android-sdk files). So I went ahead and created one and just put "board=trout" in it like you said. New error: "getvar:version-bootloader FAILED <command write failed <Too many links>>"
Progress?
btw Pramod, you're a stud, thank you for all these suggestions
Xeroproject said:
I've noticed the too many links error will say it "failed to read" on the first attempt, after that it reverts to "failed to write"./QUOTE]
Do you mean on the first attempt after a reboot?
This makes me suspect usb issues. Do you happen to have any usb cords with a ferrite bead on them laying around that you could try?
Reboot, and then try flashing one of the splash images. They are relatively small, so if it is an issue with usb communication, there is less of a chance of it failing. Try it a couple of times.. if you can get it to work once, then I would say it's more than likely some sort of usb communication issue, bad cable, interference, etc.
Click to expand...
Click to collapse
JesusFreke said:
Xeroproject said:
I've noticed the too many links error will say it "failed to read" on the first attempt, after that it reverts to "failed to write"./QUOTE]
Do you mean on the first attempt after a reboot?
This makes me suspect usb issues. Do you happen to have any usb cords with a ferrite bead on them laying around that you could try?
Reboot, and then try flashing one of the splash images. They are relatively small, so if it is an issue with usb communication, there is less of a chance of it failing. Try it a couple of times.. if you can get it to work once, then I would say it's more than likely some sort of usb communication issue, bad cable, interference, etc.
Click to expand...
Click to collapse
Yeah, the first attempt after a reboot.
Yeah I actually picked a ferrite bead USB cable up the other day and then I also shut off my speakers (just in case a magnet or something was causing interference). Just checking around my desk at work, I don't really have anything else that would interfere to my knowledge. We deal with high speed check scanners at work and I haven't had any issues with the images they pull (also via USB, same computer).
I'll give the image deal a whirl, I believe I have all that software for converting them already on my computer.
Click to expand...
Click to collapse
Just try one more thing, creat a new directory and put all *.img files and *.txt file there and reboot your system(PC and G1[fastboot mode]) then set the ANDROID_PRODUCT_OUT variable and then fire the command fastboot devices , if the fastboot return the device identity then try fastboot -w flashall command
-Pramod
pramods said:
Just try one more thing, creat a new directory and put all *.img files and *.txt file there and reboot your system(PC and G1[fastboot mode]) then set the ANDROID_PRODUCT_OUT variable and then fire the command fastboot devices , if the fastboot return the device identity then try fastboot -w flashall command
-Pramod
Click to expand...
Click to collapse
All *img & *txt files off the SD card you mean?
I've ran a search and wasn't able to find anything that specifically outlined my issue.
to preface, I have a t-mobile Nexus One, and my PC is running Windows 7 64-bit.
I'm running into a bunch of trouble trying to root my Nexus One and add Cyanogen's latest ROM. My first problem was trying to get Android SDK setup to use adb. the instructions on adding the path were unclear (still unsure if I did that right), and then I couldnt get my device to show up becuase the drivers wouldnt install. I used this link http://forum.xda-developers.com/showthread.php?t=613217 (the adb devices command now worked fine at this point) and that installed the drivers and I was able to successfully unlock the bootloader.
Now, i've downloaded Amon_Ra's recovery image, changed the file name and placed it on the root of my SD card. Phone is in debug mode, rebooted to the bootloader, and did the "fastboot flash recovery recovery.img" command, but i get 'error: cannot load 'recovery.img' "
as a test, i used the adb devices command again, and it does not work. to test if it was a drivers issue, I used the same process as the link above. this time the Nexus One does not show, but i DO see Android Phone > Android Composite ADB Interface.
in "Eviroment Variables" in "Path" I have added "tools/C:\android-sdk-windows\tools" and (from a different link I have seen) i added a Custom User Variable called adb with the variable value "C:\android-sdk-windows\tools"
So.. what am I doing wrong? Is there something I may have missed?
Recovery
If you type in the "adb devices" command and see your device listed, you have set up your SDK properly.
I usually put the recovery.img on my computer where its easy to find. Once youre in bootloader try the command "fastboot devices" and once again make sure your device is shown. Then "fastboot flash recovery C:\Wherever\recovery.img"
so THATS probably what I was doing wrong. I would type in literally "fastboot flash recovery recovery.img" (cause hey, thats what it said to type!). I ended up using the "easy" clockwork method, and used his recovery image instead. had a few more hiccups, but about 5 hours later, I'm all rooted and running CM6.
thanks!
I spent about 6 hours yesterday trying to root my Kindle Fire HD 7" tablet using various methods. I've searched numerous posts and tried several ways with no success.
I believe my ADB drivers are working properly because I am able to reboot the tablet from adb successfully. And in the Windows Device Manager it shows the "Android Composite ADB Interface" as my driver. But the command "adb reboot bootloader" just reboots back into the standard Home screen. And any fastboot command just gives me the "waiting for device" response.
I am on Version 7.4.8 of the firmware so I am trying to find a way to downgrade. I purchased it in November 2012 so it is the 2012 tablet. But every method I try just fails for one reason or another. So my question is, do I need a factory cable in order to get anywhere with this? Is it even doable with this version firmware?
Thank you in advance.
It is doable without a factory cable, the known rooting utilities people typically use are kindle fire first aid or binary's root. If you still can't get it to root, you can technically use a fastboot cable and kffa to restore it to a earlier is that os pre-rooted.
Sent from my Amazon Kindle Fire HD using Tapatalk
pastorbob62 said:
I spent about 6 hours yesterday trying to root my Kindle Fire HD 7" tablet using various methods. I've searched numerous posts and tried several ways with no success.
I believe my ADB drivers are working properly because I am able to reboot the tablet from adb successfully. And in the Windows Device Manager it shows the "Android Composite ADB Interface" as my driver. But the command "adb reboot bootloader" just reboots back into the standard Home screen. And any fastboot command just gives me the "waiting for device" response.
I am on Version 7.4.8 of the firmware so I am trying to find a way to downgrade. I purchased it in November 2012 so it is the 2012 tablet. But every method I try just fails for one reason or another. So my question is, do I need a factory cable in order to get anywhere with this? Is it even doable with this version firmware?
Thank you in advance.
Click to expand...
Click to collapse
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct. The fact you see it in your device manager is a pretty good sign though.
The command you are looking for is (must be rooted to use this command otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
LinearEquation said:
First thing you need to do is download the SDK package and set the paths correctly. Here is a video guide https://www.youtube.com/watch?v=oaNM-lt_aHw
Once the paths are set then you go to where your tools folder is and hold shift and right click on your mouse and left click on "open command window here." Then type "adb devices" and enter. When you get a device number you will have proof your ADB is working correct. The fact you see it in your device manager is a pretty good sign though.
The command you are looking for is (must be rooted to use this command otherwise you do need a factory cord.)
adb shell su -c reboot bootloader
This is the command to check the whether fastboot is working
fastboot -i 0x1949 getvar product
This is the command to get you out of fastboot.
fastboot -i 0x1949 reboot
No fastboot commands will work until you download the SDK package and set the environment up. You should be able to get into the bootloader though.
Click to expand...
Click to collapse
I appreciate your reply and information very much. However, I downloaded the SDK package and installed it over a year ago and have used Fastboot for three other devices numerous times. I used Fastboot with my Asus TF300T to flash recoveries, and return to Asus Stock on more occasions than I can count. I am currently running CROMBi-kk 20140323 on that same tablet. Just to be certain, I connected it just now as I am typing this and verified several Fastboot commands. I also have a Huawei U8800-51 and a Samsung S4 Mini Duo GT-I9192 and have used Fastboot commands with them as well.
So I don't think it is an issue with the driver not being installed correctly, or the SDK not being present unless it is a version specific issue. But the Samsung phone is much newer than the Kindle so I don't think it is that either.
So I guess that puts me at an impasse until I get a factory cable. Or I can just forget customizing the Kindle.
pastorbob62 said:
I appreciate your reply and information very much. However, I downloaded the SDK package and installed it over a year ago and have used Fastboot for three other devices numerous times. I used Fastboot with my Asus TF300T to flash recoveries, and return to Asus Stock on more occasions than I can count. I am currently running CROMBi-kk 20140323 on that same tablet. Just to be certain, I connected it just now as I am typing this and verified several Fastboot commands. I also have a Huawei U8800-51 and a Samsung S4 Mini Duo GT-I9192 and have used Fastboot commands with them as well.
So I don't think it is an issue with the driver not being installed correctly, or the SDK not being present unless it is a version specific issue. But the Samsung phone is much newer than the Kindle so I don't think it is that either.
So I guess that puts me at an impasse until I get a factory cable. Or I can just forget customizing the Kindle.
Click to expand...
Click to collapse
You said you were using simply adb reboot bootloader right? Did you try the command I suggested? "adb shell su -c reboot bootloader" because if everything is set up right then this should work. CD from the tools folder.
LinearEquation said:
You said you were using simply adb reboot bootloader right? Did you try the command I suggested? "adb shell su -c reboot bootloader" because if everything is set up right then this should work. CD from the tools folder.
Click to expand...
Click to collapse
Okay, got it working. Not sure what the problem was but I reinstalled SDK-Tools and Platform-Tools using the latest version of SDK. I was then able to use KFFA to root the Kindle and do a full backup. Not sure why it didn't work before the reinstall since I used ADB and Fastboot with my TF300T as recently as a week and a half ago while testing CROMBi-kk. Also verified they still worked with that tablet yesterday. Whatever the problem, it was specific to the Kindle.
One more question. Is it necessary to downgrade from 7.4.8 before installing a second bootloader and custom ROM? Or is that just a precautionary step because some people have had issues.
pastorbob62 said:
Okay, got it working. Not sure what the problem was but I reinstalled SDK-Tools and Platform-Tools using the latest version of SDK. I was then able to use KFFA to root the Kindle and do a full backup. Not sure why it didn't work before the reinstall since I used ADB and Fastboot with my TF300T as recently as a week and a half ago while testing CROMBi-kk. Also verified they still worked with that tablet yesterday. Whatever the problem, it was specific to the Kindle.
One more question. Is it necessary to downgrade from 7.4.8 before installing a second bootloader and custom ROM? Or is that just a precautionary step because some people have had issues.
Click to expand...
Click to collapse
Its kinda just a precautionary measure, to put it plainly, your kindle will bootloop into recovery if you do the process on 7.4.8, so unless you know how to use "Adb push" its suggested to put the rom and gapps onto the kindle ahead of time so it will be there when you start to bootloop into recovery. On another note, you do need to downgrade the bootloader though, if you use hashcodes method, please check the md5sum on the bootloader file before flashing it to avoid a hardbrick. If you used the fireflash method i wouldnt worry about it, just make sure you check off the downgrade bootloader button above or beside the red warning text.
I had these same issues. The device wouldn't boot into fastboot while it was <waiting for device>.
I did this.
1. Used Many Root Tool to gain root. http://forum.xda-developers.com/showthread.php?t=1886460
2. Placed the Rom and Gapps file on my sd card to be safe.
3. Used Anonymous.123's Tool up until the fastboot <waiting for device> malfunction. http://forum.xda-developers.com/showthread.php?t=2685414
4. Opened the Batch File for the Flasher Tool and copied and pasted the fastboot commands into a terminal with the Kindle in Fastboot. The only way I could get it in fastboot was "adb shell su -c reboot bootloader"
This will install the 4.2 bootloader so you don't have to flash back.
5. Profit 2nd Bootloader and TWRP
Good luck. You'll get it.
Sorry I Keep using the quote reply wrong. Havn't been on XDA in a while.
Okay, following Hashcode's procedure, I have successfully completed all steps up to flashing CM 10.2. TWRP works great and I made a backup from it. Not really necessary since I had backed up my Kindle three different ways and also copied all of my data to my PC as well.
But when I went to copy the TWRP backup to my PC for safekeeping I discovered that now I no longer have access to my Kindle from my PC's file explorer when I am booted into my Kindle. Prior to doing any of the steps here I could swap files back and forth without any problem. So how do I get that feature back??
I am running WIndows 8.1. This worked before I followed the procedures here. Also, when I pull files in adb where do they get stored??? Can't seem to find them.
Check the storage settings in CM you have to turn MTP storage in.
Sent from my Galaxy Nexus using xda app-developers app
Hey all
Trying to install a stable/snapshot version of cyanogen mod for my xperia V (more specifically: http://download.cyanogenmod.org/?type=snapshot&device=tsubasa) and im following their guide to do it: http://wiki.cyanogenmod.org/w/Install_CM_for_tsubasa
However, when i get to 5th step on the "Installing Cyanogenmod on Sony Devices" telling me to "Open a terminal on the PC and enter the following: fastboot -i 0xfce flash boot boot.img ", it doesn't work because fastboot simply replies Access is denied and i have no idea why, i'm running my command promt (CMD) as administrator and i'm 100% sure that i own all the files and folders on my computer... anyone know why and have a solution?
And Yes my Bootloader is unlocked, however, my phone is NOT rooted, because of what i can see according to guide its not necessary to do so, or at least not yet, and if this is the case, please tell me and i will root my phone and try again.. aswell as writing to the authors of the wiki article and piss a bit on them for not saying that its required.
Hawake said:
Hey all
Trying to install a stable/snapshot version of cyanogen mod for my xperia V (more specifically: http://download.cyanogenmod.org/?type=snapshot&device=tsubasa) and im following their guide to do it: http://wiki.cyanogenmod.org/w/Install_CM_for_tsubasa
However, when i get to 5th step on the "Installing Cyanogenmod on Sony Devices" telling me to "Open a terminal on the PC and enter the following: fastboot -i 0xfce flash boot boot.img ", it doesn't work because fastboot simply replies Access is denied and i have no idea why, i'm running my command promt (CMD) as administrator and i'm 100% sure that i own all the files and folders on my computer... anyone know why and have a solution?
And Yes my Bootloader is unlocked, however, my phone is NOT rooted, because of what i can see according to guide its not necessary to do so, or at least not yet, and if this is the case, please tell me and i will root my phone and try again.. aswell as writing to the authors of the wiki article and piss a bit on them for not saying that its required.
Click to expand...
Click to collapse
Are you sure you're in fastboot mode? Try with flashtool and see if you get the same error.
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..