OK, so I was rolling along just fine...
Got Fastboot up and running, got myself an unlocked bootloader, got myself the latest TWRP image, and no matter WHAT I DO, I can not get TWRP to flash to my device, and it is driving me absolutely INSANE. Below is what i am getting from command prompt. Any help is GREATLY appreciated.
Code:
C:\Users\saltam\Downloads\TWRP>fastboot flash recovery recovery.img
sending 'recovery' (13186 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I am pulling what little hair I have out over here, and I am no beginner when it comes to this stuff. Please help if you can.
Only a couple of things I can think, which I'm sure you've already done. Have you re-downloaded the image file and you have renamed it recovery.img?
Edit, is your bootloader unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Boot loader is unlocked, tried everything besides a different computer. Tried different cord, different USB port, everything. It's like once I unlocked the boot loader the tablet stopped communicating with fast boot. Anything I try to do hangs until I hit reboot fast boot then it fails. Irritating the hell out of me...
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
blakeslee14 said:
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Click to expand...
Click to collapse
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
craig.buckie said:
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
Click to expand...
Click to collapse
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
SwoRNLeaDejZ said:
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
Click to expand...
Click to collapse
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Going to give this a shot now..
Worth mentioning, I ran an OEM Lock command, and successfully relocked the bootloader, so it appears fastboot is at least partially working. Going to attempt to flash the bootloader in the image from Google, because that is all there is. Just bootloader and image, no recovery image. I will post results here. I don't know why fastboot commands are broken after unlocking bootloader, but there is one thing that seems odd to me:
When I run fastboot devices, it returns the following (has been like this from the beginning):
Code:
C:\Users\saltam\Downloads\TWRP>fastboot devices
???????????? fastboot
Thoughts?
Something's not right. Do you have the newest fastboot?
di11igaf said:
Something's not right. Do you have the newest fastboot?
Click to expand...
Click to collapse
Yes, recently updated it via the minimalist fastboot/adb tool. This is REALLY irritating the hell out of me at this point... Been trying to get recovery on this stupid tablet all damn day...
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
SwoRNLeaDejZ said:
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
Click to expand...
Click to collapse
To your first edit, twrp is probably working correctly. Lollipop forces the stock recovery. There are two files, one in /system and one in /system/bin that force the stock recovery upon boot. You can remove those files or first
fastboot boot twrp.img
Then flash supersu in twrp, then
fastboot flash recovery twrp.img
Sent from my Nexus 9 using XDA Free mobile app
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
xtcdk said:
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
Click to expand...
Click to collapse
Kind of mystified with your response... Had nothing to do with the USB drivers. Found out afterward that the problem was the security that my company had setup on my laptop (was using my company thinkpad). Switching laptops solved the problem.
Related
hello I used the Revolutionary to achieve s-off and install clockwork recovery, then my phone booted up and update the prl and hands free and such. now when i boot into the bootloader if i select recovery it goes to the HTC logo screen and does nothing and if i even just try to power on my device same screen HTC logo only thing i can do is volume down and power to access bootloader
spinx1337 said:
hello I used the Revolutionary to achieve s-off and install clockwork recovery, then my phone booted up and update the prl and hands free and such. now when i boot into the bootloader if i select recovery it goes to the HTC logo screen and does nothing and if i even just try to power on my device same screen HTC logo only thing i can do is volume down and power to access bootloader
Click to expand...
Click to collapse
recovery didnt flash, you arent bricked. just flash team win project recovery
Definitely not bricked, you probably just scared a whole bunch of people.
Follow this i had the same issue http://forum.xda-developers.com/showthread.php?t=1192245
when i open the fastboot.exe the adb shell windows (dos) opens and closes extremly fast no idea what it said
some people need to learn the definition of Bricked.
Bricked= exactly that the phone is now good for. a brick. (A.K.A: paperweight, doorstop, etc.) lol
yeah, just do what the others of told you, you'll get it squared away.
smokin1337 said:
Follow this i had the same issue http://forum.xda-developers.com/showthread.php?t=1192245
Click to expand...
Click to collapse
i followed instructions and flashed the recovery thru fastboot usb in the bootloader but still nothing
http://imageshack.us/photo/my-images/52/18712672.jpg/
spinx1337 said:
i followed instructions and flashed the recovery thru fastboot usb in the bootloader but still nothing
http://imageshack.us/photo/my-images/52/18712672.jpg/
Click to expand...
Click to collapse
Take out flash_image and replace with just "flash" <---No Quotes!
did you download fastboot from htc site? do you have sdk downloaded? i had same issue. cwm didnt take. i flashed teamwins no issues at all.
HSadler93 said:
Take out flash_image and replace with just "flash" <---No Quotes!
Click to expand...
Click to collapse
if i do that i get
unknown partition 'recovery-twrp-shooter-1.0.0.img'
error: cannot determine image filename for 'recovery-twrp-shooter-1.0.0.img'
spinx1337 said:
if i do that i get
unknown partition 'recovery-twrp-shooter-1.0.0.img'
error: cannot determine image filename for 'recovery-twrp-shooter-1.0.0.img'
Click to expand...
Click to collapse
Is your file called "recovery-twrp-shooter-1.0.0.img"? Also is it in the same folder as ADB/Fastboot?
okay finally got the image to flash start to send once on writing image fails remote partition does not exist
had to type
fastboot flash image recovery-twrp-shooter-1.0.0.img in the cmd prompt
HSadler93 said:
Is your file called "recovery-twrp-shooter-1.0.0.img"? Also is it in the same folder as ADB/Fastboot?
Click to expand...
Click to collapse
yes same directory
spinx1337 said:
okay finally got the image to flash start to send once on writing image fails remote partition does not exist
had to type
fastboot flash image recovery-twrp-shooter-1.0.0.img in the cmd prompt
Click to expand...
Click to collapse
It is
fastboot flash recovery recovery-twrp-shooter-1.0.0.img
that you need to type in cmd. You have to tell it where to flash (in this case the recovery partition).
Let me know if that works for you.
thanks for your help now i have recovery working my phone still wont boot up ill have to find a factory rom on the web
Your welcome. Glad I could help!
There is a rom in the development section. Not sure if it works though. You could run the RUU and then redo everything now that you know exactly how.
Have you tried a factory reset from the bootloader after getting the recovery to work?
just did a factory reset thru TWRP and its stuck on the HTC logo screen trying to boot up same issue as earlier Im not sure why my phone will not boot up. seems like only thing i can do is access the bootloader
How long do you wait before you decide it wont boot?
10-15 minutes should i wait longer?
Nah, that should be good. http://forum.xdadevelopers.com/showthread.phpt=1092957&highlight=ruu
Do this then the whole process over.
Ok, so wanting to give a rom a try I have to flash it with fastboot but fastboot is behaving weird... I can boot to fastboot mode and using fastboot reboot the device, so the device IS seen.
When I want to flash an img, using this command: fastboot-windows -i 0x0b05 flash system system.img, I get a 'FAILED (data transfer failure (Unknown error))' message.
On my prime I see a message: "Failed to process command download:2000000 error (0x120003)'
I tried various USB ports and 2 different cables, all leading to the same error.
ADB works fine (used it to push a rom before), and as mentioned I can reboot using fastboot... ANyone with any clue?
It's a windows7x64 machine btw, tried 2 different versions of adb and fastboot as well...
dagrim1 said:
Ok, so wanting to give a rom a try I have to flash it with fastboot but fastboot is behaving weird... I can boot to fastboot mode and using fastboot reboot the device, so the device IS seen.
When I want to flash an img, using this command: fastboot-windows -i 0x0b05 flash system system.img, I get a 'FAILED (data transfer failure (Unknown error))' message.
On my prime I see a message: "Failed to process command download:2000000 error (0x120003)'
I tried various USB ports and 2 different cables, all leading to the same error.
ADB works fine (used it to push a rom before), and as mentioned I can reboot using fastboot... ANyone with any clue?
It's a windows7x64 machine btw, tried 2 different versions of adb and fastboot as well...
Click to expand...
Click to collapse
Can you flash a recovery? Go from there.
bk201doesntexist said:
Can you flash a recovery? Go from there.
Click to expand...
Click to collapse
I already have CWM recovery since the beginning, do you suggest flashing it again? Thanks for the suggestion and sorry bout the late reply
do you have the AndroidMobi nvflash bootloader or the asus bootloader?
The reason being, the ASUS version requires the flashed images to be packaged as .blob whilst the AndroidMobi supports direct flash of .img.
kokopuphz said:
do you have the AndroidMobi nvflash bootloader or the asus bootloader?
The reason being, the ASUS version requires the flashed images to be packaged as .blob whilst the AndroidMobi supports direct flash of .img.
Click to expand...
Click to collapse
Hmmm, good one... given the fact I get the Asus splash screen I guess I have the asus one? I'll look deeper into this later on... thanks for the suggestion!
dagrim1 said:
Hmmm, good one... given the fact I get the Asus splash screen I guess I have the asus one? I'll look deeper into this later on... thanks for the suggestion!
Click to expand...
Click to collapse
Why are you flashing using fastboot? You can flash roms using CWM. It's much easier.
Parastie said:
Why are you flashing using fastboot? You can flash roms using CWM. It's much easier.
Click to expand...
Click to collapse
Lol, I know... started with a CM10 preview wich was only flashable through fastboot. After that it was a matter of principle (I hate it when things don't work as they should ).
dagrim1 said:
Lol, I know... started with a CM10 preview wich was only flashable through fastboot. After that it was a matter of principle (I hate it when things don't work as they should ).
Click to expand...
Click to collapse
Why? I had no problem flashing it with TWRP.
*Fixed*
uppon2 said:
I just go the phone today and I have unlocked it and it all went well. I was looking at installing ViperDNA on to my phone. So I started to follow instructions in the Viper thread
1. I "tried" to install TWRP through the Goo method and after downloading the file it told me that recovery was no installed.
2. I rebooted in to bootloader and hit power button to enter fastboot then I scrolled down to where it says recovery and I hit power again. Phone displayed a message up the top that it was now entering recovery. The phone did not go to recovery it simply rebooted all the way back to my phones home screen.
I then though hmm well maybe I didn't install it properly so I follwed the instructions using Goo again but still nothing happened.
I noticed there was an alternative method to flash recovery by using ADB. I put the file in to the same directory as where my adb/fastbood reside and I booted in to fastboot again and in cmd prompt I entered "flash recovery openrecovery-twrp-2.4.0.0-dlx.img"
It seemed to flash and gave me a response which I can't remember now but it said OK!.
I then proceeded to try and enter recovery again but this time it has sent my phone in to a bootloop. It will not pass the Droid splashscreen. I can however still access bootloader mode.
I also noticed now in my Bootloader above where it says Unlocked it also says Tampered?
Phone doesn't seem to be recognised by ADB anymore neither. adb devices returns with a blank space
I'm a long time Samsung user so usually in this situation I would use Odin and flash a stock firmware but I don't know the process with HTC
I don't have a backup because I hadn't got to this stage yet!
Any advice as to what to do now
Click to expand...
Click to collapse
if you can still get the phone into fastboot mode then you should be fine.. when in fastboot mode the command "adb devices" will not return any entries.. when in fastboot you should use the command
fastboot devices
and see if your phone shows up there.. also the command for flashing a recovery in fastboot is:
fastboot flash recovery "your recovery filename.img" without the quotations though..
so the exact command would be the fastboot flash recovery openrecovery-twrp-2.4.0.0-dlx.img if that is what the recovery file on your computer is named.
then hit enter it should say sending etc...
I always then do the command
fastboot reboot-bootloader then the phone will reboot into the fastboot screen, then manually select recovery and see that it worked that time.
lazarus2297 said:
if you can still get the phone into fastboot mode then you should be fine.. when in fastboot mode the command "adb devices" will not return any entries.. when in fastboot you should use the command
fastboot devices
and see if your phone shows up there.. also the command for flashing a recovery in fastboot is:
fastboot flash recovery "your recovery filename.img" without the quotations though..
so the exact command would be the fastboot flash recovery openrecovery-twrp-2.4.0.0-dlx.img if that is what the recovery file on your computer is named.
then hit enter it should say sending etc...
I always then do the command
fastboot reboot-bootloader then the phone will reboot into the fastboot screen, then manually select recovery and see that it worked that time.
Click to expand...
Click to collapse
After attempting this it hangs here:
C:\Android-adb>fastboot flash recovery openrecovery-twrp-2.4.0.0-dlx.img
< waiting for device >
EDIT* Rookie mistake for it hanging. I was only in bootloader not Fastboot. However, this worked and I love you. I will now flash Viper. Do I still need to flash the Kernel Modules?
uppon2 said:
After attempting this it hangs here:
C:\Android-adb>fastboot flash recovery openrecovery-twrp-2.4.0.0-dlx.img
< waiting for device >
EDIT* Rookie mistake for it hanging. I was only in bootloader not Fastboot. However, this worked and I love you. I will now flash Viper. Do I still need to flash the Kernel Modules?
Click to expand...
Click to collapse
flashing the modules for the kernel is always a good idea just flash that after you flash your ROM..
and you are welcome just glad I could help!!
lazarus2297 said:
flashing the modules for the kernel is always a good idea just flash that after you flash your ROM..
and you are welcome just glad I could help!!
Click to expand...
Click to collapse
lol. Now Aroma is being a pain in the ass. It won't let me click Next to install. haha
EDIT* Maybe because of the smaller TWRP or maybe not but I had to try again and then click next but about 2" higher than where it says it :S
I am not a huge fan of aroma... i had issues when i tried to flash my DNA the first time.. that is something that you just have to keep trying unfortunately it seems... i have seen where people had to aroma freeze on them multiple times before finally completing the flash... some tips i have seen is keep the phone flat... also keep it plugged in.. I can't vouch for any of these being actual fixes but hey "it's only weird if it doesn't work"
Do you know the load time on a ROMs first boot after flash?
The ROM said it was installing and at about 8% the screen went all grey and then rebooted in to the HTC splash screen and hasn't changed for about 15 minutes. Tried it twice
EDIT* Would only flash using CWM
uppon2 said:
Do you know the load time on a ROMs first boot after flash?
The ROM said it was installing and at about 8% the screen went all grey and then rebooted in to the HTC splash screen and hasn't changed for about 15 minutes. Tried it twice
EDIT* Would only flash using CWM
Click to expand...
Click to collapse
glad to hear it sorry for the slow response.. i was away for a bit..
lazarus2297 said:
glad to hear it sorry for the slow response.. i was away for a bit..
Click to expand...
Click to collapse
All good. Thanks for your assistance
I am usually the guy helping other people. It's quite an unusual change going from Samsung to HTC!
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
I once bricked my lg g2 pretty badly, couldn't use adb or recovery.
I managed to repair it by booting a linux and manually overwrite the partitions with the factoy image.
There is a thread with instructions here on xda in the g2 forum, could work with the nexus to.
nexus 9
DoeBoi said:
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
Click to expand...
Click to collapse
just look for the image for your device on recovery. as long as you have fastboot it can be saved. just look for your version flounder custom recovery and it should work
MoooN said:
I once bricked my lg g2 pretty badly, couldn't use adb or recovery.
I managed to repair it by booting a linux and manually overwrite the partitions with the factoy image.
There is a thread with instructions here on xda in the g2 forum, could work with the nexus to.
Click to expand...
Click to collapse
I don't have a Linux system and looking through thread seems too advance for me. I can't relate it to the N9. However, there seems to be something wrong partition, because I can't mount storage.
matt4787 said:
just look for the image for your device on recovery. as long as you have fastboot it can be saved. just look for your version flounder custom recovery and it should work
Click to expand...
Click to collapse
I can flash custom recovery, but I can't push files or adb sideload, therefore I can't do anything in recovery anyway.
Did you try to use the nexus toolkits flying around here?
Maybe they could be of some help..
@DoeBoi you need to flash the factory image. This should help http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 5 using XDA Free mobile app
Does the Google Logo flash for a second or so before it goes to bootloader?
nexus 9
Try to get into bootloader by holding power and volume down.
MoooN said:
Did you try to use the nexus toolkits flying around here?
Maybe they could be of some help..
Click to expand...
Click to collapse
I will look in to it, thank you.
jd1639 said:
@DoeBoi you need to flash the factory image. This should help http://forum.xda-developers.com/showthread.php?p=58956577
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I already tried one version of the image, which didn't work, will try to flash the others.
scrosler said:
Does the Google Logo flash for a second or so before it goes to bootloader?
Click to expand...
Click to collapse
restart - sometimes yes and sometimes no, if plug into computer - no, if not plugged - yes,
matt4787 said:
Try to get into bootloader by holding power and volume down.
Click to expand...
Click to collapse
you mean power + volume up, but yes, no problem getting there, also adb is working
thanks for all your help, I will try different factory image and flashing from OTG
The problem is your kernel is not loading or mismatched to the operating system. I have experienced this a lot on HTC devices when I screw something up... I mean "experiment"
You need to flash the boot system and vendor image from the latest factory ROM.
You need to do it manually...
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
Then reboot to recovery and wipe data. Not factory rest but actually wipe all of /data partition.
That should get you back. If not post back results.
If you are not familiar with fastboot then state so and I will help you.
Yes! I got it booting again, thank you everyone for helping. Apparently, the problem was, I think, wiping manually, that is, system, cache, recovery, boot, user data, and vendor didn't erase everything. What did the trick was [fastboot -w], I did this instead of erasing one by one. Thank you so much guys!
DoeBoi said:
Hey guys, I think I've bricked my N9. What happened was I rooted it successfully, but then on flashing a custom recovery, I used the wrong image file. Instead of using the flounder image, I mistakenly flashed the volantis one. And then I flashed twrp for flounder. But after that, the recovery could not mount anything and ADB Sideload did not work. After that, I when and restore everything back to stock with factory image, however I cannot boot into system. I am effectively stuck in bootloader, and that's where I am. I tried rooting and flashing twrp recovery, and again, it could not mount and ADB Sideload is not working. I tried everything. Is my N9 done for? Or can someone point me in the right direction and get my N9 back?
Click to expand...
Click to collapse
First question - Did you flash a bad bootloader? If no, then you cannot have possibly bricked your nexus 9. I do believe this is the ONLY way you could brick a nexus. If you still have access to fastboot mode, you are totally fine. I would recommend flashing the factory images and just starting fresh. Depending on which nexus 9 you have, either the wifi only or LTE variant, you can download the appropriate packages at https://developers.google.com/android/nexus/images . Basically, you need to extract the package into a folder, boot your device into fastboot mode, and run the flashall.bat (windows) or flashall.sh(linux). As long as you have fastboot and ADB properly installed into your $PATH or atleast have fastboot and adb in your working folder, everything should be ok. If you run into any problems, contact me via PM or I can be found on IRC (Network freenode, #android, #cyanogenmod, #android-root). Good luck
bynarie said:
First question - Did you flash a bad bootloader? If no, then you cannot have possibly bricked your nexus 9. I do believe this is the ONLY way you could brick a nexus. If you still have access to fastboot mode, you are totally fine. I would recommend flashing the factory images and just starting fresh. Depending on which nexus 9 you have, either the wifi only or LTE variant, you can download the appropriate packages at https://developers.google.com/android/nexus/images . Basically, you need to extract the package into a folder, boot your device into fastboot mode, and run the flashall.bat (windows) or flashall.sh(linux). As long as you have fastboot and ADB properly installed into your $PATH or atleast have fastboot and adb in your working folder, everything should be ok. If you run into any problems, contact me via PM or I can be found on IRC (Network freenode, #android, #cyanogenmod, #android-root). Good luck
Click to expand...
Click to collapse
Um, he's got it fixed.
Sent from my Nexus 5 using XDA Free mobile app
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
sototallycarl said:
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
Click to expand...
Click to collapse
Thanks for paying it forward.
I have a similar problem my nexus 9 wont turn on and would freeze in the optimizing apps screen after going past the nexus logo but i can get to the fastboot and recovery. But i cannot flash the factory image because my bootloader is locked and i didn't enable developer options prior to the problem. I'm thinking about sideloading the latest ota would that help me ? And is there anyway to unlock bootloader if i can't boot the device?
---------- Post added at 10:10 PM ---------- Previous post was at 10:07 PM ----------
sototallycarl said:
I too thought I bricked my device and found this thread. Using the recovery from Google I was getting "sending sparse 'system' FAILED (status read failed (Protocol error))" until I used "fastboot -w" like the post above mentioned. Leaving this here in case someone else runs into the problem.
Click to expand...
Click to collapse
Can you please explain to me what fastboot w- command means ?
It erases userdata and cache. Often needed if you run into bootloops. But it does wipe your data so backup off your device first.
Bricked N9
Hi everyone, well my problem is that i was trying to flash Android 6.0 but i accidentally execute the flash-all.bat file while i was trying to open it in the note block. It was booting normally but it seems that my N9 was encrypted, so it said that the Unencrypted was incorrect so it forced me to hard reset my tablet. i did this but it was taking like 20 min to erase my file (the android appeared and it was over a message that was "Wiping" -it was in spanish borrando-) so i turn it off and now my tablet is on a bootloop, after it appears the Google logo the 4 dots start to move but then the tablet turn off and repeat that cycle. Apparently i dont have recovery (appears the android laid down with a red triangle with an exclamation mark) and when i try to enter the hard reset the bootloop happens, the same if i try to reboot, i cant activate usb debugging i can only use the fastboot mode, my pc doesnt reconize my N9.
Thanks
PD: Sorry about my english, im from mexico, but i expect i had explained myself.
emi.guego said:
Hi everyone, well my problem is that i was trying to flash Android 6.0 but i accidentally execute the flash-all.bat file while i was trying to open it in the note block. It was booting normally but it seems that my N9 was encrypted, so it said that the Unencrypted was incorrect so it forced me to hard reset my tablet. i did this but it was taking like 20 min to erase my file (the android appeared and it was over a message that was "Wiping" -it was in spanish borrando-) so i turn it off and now my tablet is on a bootloop, after it appears the Google logo the 4 dots start to move but then the tablet turn off and repeat that cycle. Apparently i dont have recovery (appears the android laid down with a red triangle with an exclamation mark) and when i try to enter the hard reset the bootloop happens, the same if i try to reboot, i cant activate usb debugging i can only use the fastboot mode, my pc doesnt reconize my N9.
Thanks
PD: Sorry about my english, im from mexico, but i expect i had explained myself.
Click to expand...
Click to collapse
I had the same problem... I had to manually flash each image through fastboot starting with the recovery img
Sent from my HTC One M9 using XDA Free mobile app
But how can I do it if I can't enable USB debugging?
Enviado desde mi Moto MAXX mediante Tapatalk
**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