Hey all. When trying to install any custom rom on my xt2041-4, I can flash the boot image no problem, but flashing a system image gives me an error something along the lines of what I said in the title. This happens on any custom rom I try, despite definitely having an unlocked bootloader. I bought the phone unlocked, but Verizon is my carrier. Is the Verizon sim what's causing this, or is it something else? I daily drive Ubuntu, so restoring the phone to the stock rom is a massive hassle, and wanted to know if this is a common issue with an easy fix. I can recreate the error's exact wording if need be, but I'd prefer not to if I don't have to. Please let me know if there's anything I can or should be doing, or if there's any more information you'd need from me to help. Thanks!
_huck_ said:
Hey all. When trying to install any custom rom on my xt2041-4, I can flash the boot image no problem, but flashing a system image gives me an error something along the lines of what I said in the title. This happens on any custom rom I try, despite definitely having an unlocked bootloader. I bought the phone unlocked, but Verizon is my carrier. Is the Verizon sim what's causing this, or is it something else? I daily drive Ubuntu, so restoring the phone to the stock rom is a massive hassle, and wanted to know if this is a common issue with an easy fix. I can recreate the error's exact wording if need be, but I'd prefer not to if I don't have to. Please let me know if there's anything I can or should be doing, or if there's any more information you'd need from me to help. Thanks!
Click to expand...
Click to collapse
You need to be in fastbootd, not fastboot.
In the regular bootloader/fastboot screen, in a cmd window type fastboot reboot fastboot to enter fastbootd (Totally different screen to regular bootloader, says fastbootd in red at the top).
Then flash all the images from there.
Beetle84 said:
You need to be in fastbootd, not fastboot.
In the regular bootloader/fastboot screen, in a cmd window type fastboot reboot fastboot to enter fastbootd (Totally different screen to regular bootloader, says fastbootd in red at the top).
Then flash all the images from there.
Click to expand...
Click to collapse
That makes sense. I did try that, but it told me "Waiting for any device" when I tried.
Edit: Found this 8 year old Stack Overflow answer that says I could try just running everything as root, so follow all the same steps, but add "sudo" to the beginning. I'll try that after class, and let you know if I can get into fastbootd.
Edit 2: No luck. Could it be a driver issue? I don't know if the Motorola drivers are baked into the Linux kernel, or if the drivers are only available for Windows. I could set up a Windows VM if need be if that would be an issue.
Edit 3: Running "adb reboot fastboot" gets me into fastbootd! Should I still be concerned about the Fastboot "Waiting for any device" message before flashing?
_huck_ said:
That makes sense. I did try that, but it told me "Waiting for any device" when I tried.
Edit: Found this 8 year old Stack Overflow answer that says I could try just running everything as root, so follow all the same steps, but add "sudo" to the beginning. I'll try that after class, and let you know if I can get into fastbootd.
Edit 2: No luck. Could it be a driver issue? I don't know if the Motorola drivers are baked into the Linux kernel, or if the drivers are only available for Windows. I could set up a Windows VM if need be if that would be an issue.
Edit 3: Running "adb reboot fastboot" gets me into fastbootd! Should I still be concerned about the Fastboot "Waiting for any device" message before flashing?
Click to expand...
Click to collapse
Download the latest adb/fastboot platform tools file.
Extract that zip and run the command line terminal from that directory.
Cd Desktop/platform-tools, or wherever you have that folder extracted to.
Then flash the ROM image files. Just drag and drop them into the command prompt terminal.
Related
Okay, here we go. I am new to rooting and I have already unlocked the bootloader on my device (HTC Evo 4G LTE). It still has S-on. After I unlocked my bootloader, I continued on to flash TWRP Recvovery onto my phone using fastboot. My phone does not have an SD card. However, no matter how many times I download the newest version of TWRP or rename the file or change the directory in the command prompt...it says "error: cannot load recovery image". When I attempt to restart in recovery mode, I get this red triangle with an explanation point! I have tried over and over again, but since I cant flash this recovery, i have an unlocked bootloader for practically no reason. I need to get past this step in order to start flashing custom ROM's. I even used RegawMOD EVO 4G LTE Rooter. After i click "Root Me" it puts my device into fastboot and attempts to submit the unlock token to HTCDev.com even though I already did that! I am stuck :crying:
Go here and download the recovery to your ADB tools folder.
http://techerrata.com/file/twrp2/jewel/openrecovery-twrp-2.3.3.0-jewel.img
You can rename the file "twrp" without the quotation marks. Make sure the file doesn't have an extra img extension or it won't work. Once you do this reboot your phone to the bootloader. Connect your phone to your computer via USB cable. You should see the word Fastboot in red highlights change to Fastboot USB. Open up ADB and type "fastboot flash recovery twrp.img" (without quotation marks) then press enter. At this point TWRP recovery should be installed on your phone.
If these are the steps you have followed, disregard.
The advice is free....the bandwidth, not so much
Thank You for Replying Good Sir!
1)when i download any twrp file and try to open it on my computer, it says "the disc image file is corrupted"
2)when i attempt to open ADB , it flashes up then off. I cant read what it says
3)i entered the command in the command prompt and it just says waiting for device
gratealex8 said:
1)when i download any twrp file and try to open it on my computer, it says "the disc image file is corrupted"
2)when i attempt to open ADB , it flashes up then off. I cant read what it says
3)i entered the command in the command prompt and it just says waiting for device
Click to expand...
Click to collapse
Download this extract it to your desktop and run your commands from that folder by pressing shift and right clicking on an empty spot inside the folder and choose open cmd window here.
There is a readme.txt inside follow the instructions on how to fastboot flash twrp (Copy and paste is the easiest way to do this that way there are no typo's)
Use v2.4.1.0 if you are on the latest OTA
Use v2.3.1.0 otherwise
idk whats wrong!!
I did exactly as you said, yet the command prompt just says waiting for device. I'm not sure what to do anymore because regardless of following these instructions, I CANT FLASH TWRP RECOVERY TO MY PHONE. I believe the problem is with my phone but Im running out of options. its beginning to look like I unlocked my bootloader for nothing :/
gratealex8 said:
I did exactly as you said, yet the command prompt just says waiting for device. I'm not sure what to do anymore because regardless of following these instructions, I CANT FLASH TWRP RECOVERY TO MY PHONE. I believe the problem is with my phone but Im running out of options. its beginning to look like I unlocked my bootloader for nothing :/
Click to expand...
Click to collapse
Try these drivers.Install them and reboot your PC once rebooted go to add/remove programs and delete HTC Sync
Getting frustrated
bigdaddy619 said:
I did this and again all I get in the command prompt is waiting for device. No more ideas huh?
Click to expand...
Click to collapse
I'm working on rooting my very first android phone for the very first time, and I've run across a snag. I've been following Luckythirteen's guide to rooting found here, but so far I've been unable to flash the TWRP recovery. Here's what I posted in the original thread:
Help! I've followed the steps to the T, but I'm struggling with installing the recovery. I've unlocked my bootloader, downloaded the TWRPrecovery.img, put it in the right folder. As soon as I boot into the bootloader, my phone seems to disconnect from the computer. I still have fastboot usb selected, but my device no longer shows up under adb devices. When I try to >fastboot flash recovery TWRPrecovery.img, I get an error "error: cannot load 'TWRPrecovery.img' : Unknown error"
I've got the international HOX+ and a computer running Win7. Any assistance in the matter would be super appreciated.
I hope I've provided enough information for someone to help me out here. I'm a complete Android beginner so this is all a little overwhelming. Thanks.
It is normal that your device does not show using "under adb devices" when in fastboot. You have to use "fastboot devices" instead. Try and see if your dive shows up there.
Also did you try redownloading the recovery.img and/or reinstallung HTC Drivers?
reaper90 said:
It is normal that your device does not show using "under adb devices" when in fastboot. You have to use "fastboot devices" instead. Try and see if your dive shows up there.
Also did you try redownloading the recovery.img and/or reinstallung HTC Drivers?
Click to expand...
Click to collapse
Hey, thanks for the reply. You're right, I did end up finding it under fastboot devices, but it still wouldn't work. Since then I've tried flashing a recovery using the all in one kit found in this, and adb shows that the flash was successful, however when I select recovery under the HBOOT menu, it just shuts off my phone, and when I power up again it reboots normally. Any idea what's up now?
christmas_time said:
Hey, thanks for the reply. You're right, I did end up finding it under fastboot devices, but it still wouldn't work. Since then I've tried flashing a recovery using the all in one kit found in this, and adb shows that the flash was successful, however when I select recovery under the HBOOT menu, it just shuts off my phone, and when I power up again it reboots normally. Any idea what's up now?
Click to expand...
Click to collapse
Where exactly did you see that flashing process was successful? What about your HTC drivers? Are they up to date? What version of TWRP did you try to install?
reaper90 said:
Where exactly did you see that flashing process was successful? What about your HTC drivers? Are they up to date? What version of TWRP did you try to install?
Click to expand...
Click to collapse
The adb command window shows the flashing process just like the images in the initial tutorial. I've tried reinstalling the drivers a few times now, would it show me the device under fastboot devices if my drivers weren't working? I tried the latest TWRP, 2.5.0.0. Sorry for double-posting, I wasn't aware you were the same guy from the other thread!
christmas_time said:
The adb command window shows the flashing process just like the images in the initial tutorial. I've tried reinstalling the drivers a few times now, would it show me the device under fastboot devices if my drivers weren't working? I tried the latest TWRP, 2.5.0.0. Sorry for double-posting, I wasn't aware you were the same guy from the other thread!
Click to expand...
Click to collapse
did you see the following two things in the command window? "sending recovery.img" an then "done"?
and just to be sure: you picked the right recovery version for the One X+?
reaper90 said:
did you see the following two things in the command window? "sending recovery.img" an then "done"?
and just to be sure: you picked the right recovery version for the One X+?
Click to expand...
Click to collapse
I must admit to my embarrassment that yes, it turns out I was trying to flash the wrong recovery (HOX instead of HOX+) and now I feel like an idiot, but I've finally gotten it to work, and I'm finally rooted! Thanks so much!
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
also to note....you dont have to install linux to get s-off....if you follow my guide you can do it straight from a live disk rather than installing it....so it wont erase or mess up your windows partition at all
Solved!
Thank you, Mjones, I finally got it! I knew it was much easier than I was making it out to be. I was missing the kernel! Yeah, a crucial part in the process, I know
I first ran CWM and flashed the ROM over and ran the .zip through recovery (which I couldn't understand at first as I could never find it in the directory) but the installer would only go 50% and would fail... makes sense why now lol
I later flashed TWRP and backed up again after recovering from the fail. I flashed over the kernel and voila! So simple... Had to slap myself.
Thanks again! Case solved.
REV3NT3CH, that is sweet!! I have been hoping there is a way to gain s-off with Windows. I have 7 at work and 8.1 (which I can't get anything to work on) at home. I actually have to focus on work today haha so I'll look into the method and try it out tomorrow if I can. Thanks for all of the help.
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Sorry, don't know anything about that phone.
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Did you try this first? (Right from Moto's site)
Perform a factory reset using external keys
1. Power off the phone, press and hold volume down button, press power button
2. Screen will come up with "Fastboot", press Vol down key to cycle through choices until you get "Android Recovery", then press Vol up key
3. Wait for the "triangle ! / Android" screen then go on to step 4
4. Press both Vol up and Vol down key simultaneously. A menu will come up
5. Tap on Vol down key until "wipe data/factory reset" is highlighted, and tap Power key. Another Confirmation screen will come. Tap on Vol down key until coming to Yes and tap Power key
6. After userdata is cleared, the "reboot system now" option will be highlighted by Default. Tap Power key
7. Phone will reboot to initial setup screen.
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
not working
hariom.gupta11 said:
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
Click to expand...
Click to collapse
not working on my 4c. write successful but when reboot is completed it goes to previous state.
"the user data partition can no longer be used"
zb602kl_x00tdb
L0RDZ3RO said:
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
Click to expand...
Click to collapse
I have same problem on asus zenfone max pro m1 I bought it online said used and now working
can't boot into recovery.
can't boot into system.
Only EDL Mode and Fastboot Mode, but fastboot is Locked whic I cant unlock because I cannot boot into system to toggle USB Debugging and allow OEM unlocking
Qualcomm is harder to flash than MTK that can use SP FlashTool.
on this I use QFIL but keeps "sahara error". I tried searching and try moving firmware file to bin but no Luck. I'm currently trying different version of QFIL Tool.
If it FAILS my only HOPE is to use MUT-QCfire which will Require a "SmartCardReader" Which is a bit pricey and I don't even know if it will work on my device.
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Ok, I am an idgit. Could a mod move this to the Q&A forum? Apologies.
EqualOpportunityDork said:
So I need to appeal to the android gurus of the world. I have an issue that I am having a difficult time sussing out and I am hoping someone else can help me figure it out.
My device is an HTC One M7, rooted, running Insert Coin 3.0.2 (Android 4.4.2), S-On., Hboot 1.44, TWRP Recovery
My problem is I can not access my Recovery and Fastboot isn't seeing my device, so I can not flash a new one. I can get to my phone in adb, just fine, but using flash_image to flash a recovery threw up a -1 error, so flashing recovery through adb appears to be out, as well. If I go to my Bootloader, selecting Recovery simply dumps me back to Fastboot.
I haven't booted into recovery since I installed this Rom, months ago, so I don't know exactly when my Recovery broke. I do know that today, I tried updating TWRP through Flashify and I suspect that may be part of the issue, since Flashify insisted on pulling down the TWRP for the M8 instead of the M7. I didn't catch that little nugget till after I flashed it.
I am pretty well open to anything that might work, but I am not sure what my options are when I can't even get into recovery. A pre-emptive thank you to anyone attempting to help. It should be said that apart from this, the phone works fine. I simply can't get into recovery to update my ROM, anymore.
Click to expand...
Click to collapse
ADB works in an OS or in custom recovery and fastboot works in the bootloader. ADB doesn't work if the phone is in bootloader. I think you will have to run a RUU then go into stock recovery and do a factory reset. Let the phone boot normally then you can start the custom routine. You might also check to see if your ADB & fastboot are up to date. To run the RUU you will have to relock your bootloader since you are S-ON.
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
EqualOpportunityDork said:
Thanks. Yea, I've managed to figure out the difference between adb and fastboot through all this. so plus for learning! However, the only method I have found for relocking my bootloader is through fastboot, which I can't seem to be able to use.
I will see if there's a newer version of fastboot out there, though. hadn't thought of that.
Click to expand...
Click to collapse
Another quick thought, you wouldn't happen to be using Win 8 are you? If so, Win 8 doesn't see hboot 1.44 you are going to have to use a Win 7, Mac or Linux machine. Sorry, I didn't catch it earlier. Here is a how to for Linux and you don't have to install it permanently on your computer:
HOW TO USE LINUX FOR FASTBOOT & ADB VIA USB
This guide originally posted by @Danny201281
http://forum.xda-developers.com/showpost.php?p=54272479&postcount=219Linux is your friend; if your drivers are not working the chances of getting them working again without the phone booting are slim. But Linux doesn't need drivers to talk to your device.
Go here: http://www.pendrivelinux.com/ and download Universal USB Installer – Easy as 1 2 3
Then go here: http://releases.ubuntu.com/12.04/ and download Ubuntu from the first link at the top that says PC (Intel x86) desktop CD
Then use these files to create a bootable Linux USB drive with at least a 2 GB persistent file for storing files. You'll also probably need to change your boot settings in the computers bios to boot from USB.
MOVING YOUR FILES TO UBUNTU
Once booted you should be at a screen with options to "Try Ubuntu” or "Install Ubuntu". We don’t need to Install anything so just choose "Try Ubuntu" and the computer will boot to the Ubuntu Desktop (If you get a popup saying "system has encountered an error" or something similar just cancel and ignore it, it should have no effect on what we need to do as it is due to missing Linux OS updates we don’t need). On the left of the screen you'll see the Dock. Open the orange folder icon near the top this is the Home folder. It’s where we need to put any files we need to work with such as a rom.zip you want to push to the device or recovery.img files for flashing.
To get your files here is a simple drag and drop process. In the top left of the Home folder you'll see the drive structure of you pc under devices. Choose your PCs hard drive and Right-Click then" Open in a new window". Locate your .zip or .img files and drag them into the home folder. Now wait for the copy process to complete and rename them for easier typing later, e.g., rom.zip, firmware.zip or recovery.img etc.
USING ADB AND FASTBOOT
First you need to install adb fastboot; this is easy just 3 commands in the terminal. Thanks to Webupd8 team.
Code:
sudo add-apt-repository ppa:nilarimogard/webupd8
Code:
sudo apt-get update
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Make sure your connected to the internet and press Ctrl+Alt+T to open the terminal then type or copy and paste the above commands one at a time waiting for each to complete their output. It may seem to have stopped at times but be patient when the prompt returns to normal enter the next command and when there all done you’re ready to use adb and fastboot.
Once you've moved all the files you need to the home folder that’s it you’re ready to go. Close everything down on the desktop (optional) and press Ctrl+Alt+T this will open the terminal now connect your phone with the USB cable. All fastboot commands need to have the "sudo" prefix added at the start, e.g.
fastboot flash recovery recovery.img becomes sudo fastboot flash recovery recovery.img
fastboot devices becomes sudo fastboot devices
However, adb should work basically the same as on windows. If you do have problems with normal adb commands adding “sudo” can help here as well.
Click to expand...
Click to collapse
Dude, you are my hero. I couldn't get fastboot to work, because I had missed the part where I needed to preface it with sudo. I had adb and fastboot running a couple of days ago on my Mint install, but I didn't realize I was missing 4 freaking letters to get it right. Just flashed latest twrp and booted into recovery, no problem.
Thanks again, for the help, even if I should have found that on my own, sooner. I thought I had really hosed something on my phone. Now I can move on to hopefully not screwing something else up.
You could have used flashify to flash a recovery.IMG. free app from app store
I mentioned trying Flashify in the OP.
**XT2041-4**
hey folks,
i have the gpower/g8power (XT2041-4) and i was able to unlock the bootloader and i have been able to do the fastboot commands but it fails when i do the fastboot system, product, vbmeta commands for the crdroid, lineage and havok. i got into twrp and tried installing the zips for those roms but those failed too.
i got to the android OS start screen but the touchscreen is unresponsive. i have looked through a lot of the threads for this device and can't find anything that works.
any help will be much appreciated because this is my daily driver.
edit: title should be XT2041-4
your best option would be to connect an otg cable, ( best is to make sure you can have a double connection, one for mouse , on connected to the pc) then get into the phone with the non-touchscreen booted rom, connect it to LMSA , and extract the boot.img image that comes with the rom LMSA downloads. you should have a working touchscreen with the version LMSA downloads .
Reason you need a double connection: you need to accept the connection to your pc from the phone
you could also browse to the settings --> about this phone and take a look at the exact ROM that is installed, and find that image on lollinet , then extract and boot the boot.img from that rom.
Hey, I'm having the same problem but I found a workaround.
you can either go in fastboot mode and enter
fastboot set_active b
or go in TWRP and change the active slot to B then proceed to boot up the phone.
In my case, it showed warning saying "cannot boot into system......file maybe corrupted" etc etc, just choose "factory reset" on that screen and your phone should boot into slot B with stock ROM.
That way you can have a functional phone while waiting for the developers to figure out the kernel problem
Cheers
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
Chosimise said:
waiting for the developers to figure out the kernel problem
Cheers
Click to expand...
Click to collapse
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
uglyaf said:
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
Click to expand...
Click to collapse
I had a completely different issue with the exact same model. I made a post here asking if anyone had an easy fix, but my guess is that these are just growing pains. Give it a couple months and the roms will likely be much more stable. One of the reasons I bought this phone in the first place is because it usually gets official Lineage OS support at some point. With time, I'm sure things will work great. If you use Windows, going back to stock everything is pretty dead simple with the Lenovo Rescue and Recovery tool, so you can kind of experiment safely if you back everything up.
uglyaf said:
hey thanks guys for taking the time to respond much appreciated.
somehow, no idea, i magically got the phone back to stock and the touchscreen is working. the bootloader is still unlocked so i am not messing with it. that scared the crap out of me lol
this bugged me out. so are you saying if i did everything right, those ROMs i downloaded still wouldn't technically work? even if i do the slot B thing?
Click to expand...
Click to collapse
After some tinkering, I actually figured out my problem. There's a big difference between "fastboot mode" (the one you enter by pressing power and vol-) and "Fastbootd" mode.
I did all my flashing in "fastboot mode" and I got no touch screen afterward.
Then there's another hiccup for me (which is why I didn't go in "fastbootd" mode in the first place): When I type in the command in regular "fastboot mode"
Code:
fastboot reboot fastboot
I got an error message saying "reboot fastboot" is not a valid destination or something down those lines.
The problem being, they only added that option in fastboot version r30, so I had to update my ADB and fastboot environment.
And I ran into yet another problem, no matter what I do, the fastboot command is still run with the older version. I guess I messed up the previous installation and the pathing got messy. I ended up using my work laptop for a clean installation of all drivers and it finally solved my problem. I guess I'm saying you need to clean up previous adb and fastboot drivers before using the new ones, especailly if you installed it systemwise.
Anyways, after I booted into "fastbootd" mode and flashed everything with the latest version of fastboot driver, the phone worked flawlessly.
Hope it helps!
hey thanks again for the responses people!
i have managed to get root on stock but still cant get cutsom roms installed at all. they always fail with these 2 methods
a) twrp
unmounting system....invalid zip file format! error installing zip file '/external_sd/....zip' updating partition details....done'
b)using command line
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
i type fastboot devices and it finds my phone. it lists it there but i type fastboot reboot fastboot and it just spams a huge list of commands and nothing changes on the phone. ive seen videos and fastbootd looks just like the old school recovery from droid1 days but idk if thats the same skin look on all devices. i was able to switch the slot from a to b in twrp but that didnt help. i cant figure out how to get into fastboot'D' mode.
im really trying here and im sorry im dumb. as always, any suggestions would be much appreciated. thanks again!
uglyaf said:
hey thanks again for the responses people!
i have managed to get root on stock but still cant get cutsom roms installed at all. they always fail with these 2 methods
a) twrp
unmounting system....invalid zip file format! error installing zip file '/external_sd/....zip' updating partition details....done'
b)using command line
writing 'system'...
(bootloader) Preflash validation failed
FAILED (remote failure)
i type fastboot devices and it finds my phone. it lists it there but i type fastboot reboot fastboot and it just spams a huge list of commands and nothing changes on the phone. ive seen videos and fastbootd looks just like the old school recovery from droid1 days but idk if thats the same skin look on all devices. i was able to switch the slot from a to b in twrp but that didnt help. i cant figure out how to get into fastboot'D' mode.
im really trying here and im sorry im dumb. as always, any suggestions would be much appreciated. thanks again!
Click to expand...
Click to collapse
You have no stock recovery, so no fastbootd.
Reflash stock recovery to get fastbootd back
Beetle84 said:
You have no stock recovery, so no fastbootd.
Reflash stock recovery to get fastbootd back
Click to expand...
Click to collapse
thank you,
i downloaded "XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
is must be the wrong one?
i used the recovery.img from that and did fastboot devices and it showed up so i did "fastboot flash recovery recovery.img" and it had no errors, it worked just fine so i tried fastboot reboot fastboot but i still got that long list of commands (((
i dont get it, what am i doing wrong?
uglyaf said:
thank you,
i downloaded "XT2041-4_SOFIA_RETUS_10_QPMS30.80-51-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip"
is must be the wrong one?
i used the recovery.img from that and did fastboot devices and it showed up so i did "fastboot flash recovery recovery.img" and it had no errors, it worked just fine so i tried fastboot reboot fastboot but i still got that long list of commands (((
i dont get it, what am i doing wrong?
Click to expand...
Click to collapse
Like the other user did a couple of posts up, you probably have to update your adb/fastboot version.
Beetle84 said:
Like the other user did a couple of posts up, you probably have to update your adb/fastboot version.
Click to expand...
Click to collapse
ok thanks i did that and got version 1.4.3 it sees my device but when i did the fastboot reboot fastboot i got
fastboot: usage: unknown reboot target fastboot
and nothing happened. does anyone know what that means?
ok yes indeed im a huge idiot. i finally got into fastbootd because i downloaded ADB version R30. THATS the most recent adb version and that did the trick! now i got the fastbootd recovery screen!
regardless, thank you all SOOOOO much for taking the time to respond. much appreciated.
im so excited to get flashing!
peace and love
Boot twrp,( no need to flash) -fastboot boot (whatever you named the recovery img).img- then -adb reboot fastboot-
Should go to fastbootd. future reference
brucedroid031 said:
Boot twrp,( no need to flash) -fastboot boot (whatever you named the recovery img).img- then -adb reboot fastboot-
Should go to fastbootd. future reference
Click to expand...
Click to collapse
good look thank you