Database Develop

[Q] Unable to flash recovery - error

I am trying to flash twrp through fastboot, but am not having any luck. Here is what I've done so far:
Flashed cm10.1. This flashed fine using nvflash, it also booted fine...could not, however,boot to fastboot or recovery at all. Using nvflash I restored to stock using images p2-p14 in another thread. After flashing I rebooted into a bootloop. Powered it off and booted into recovery and did factory reset, then rebooted. Now currently back on stock 2.2.2 boots fine. I then hopped into fastboot and attempted to flash twrp using "fastboot flash recovery recoveryname.img" This is where I'm recieving the following error:
Code:
Failed to process command getvar:partition-type:recovery error(0x2)
Any ideas on what has happened here?
Thanks
devx

devastatorx said:
I am trying to flash twrp through fastboot, but am not having any luck. Here is what I've done so far:
Flashed cm10.1. This flashed fine using nvflash, it also booted fine...could not, however,boot to fastboot or recovery at all. Using nvflash I restored to stock using images p2-p14 in another thread. After flashing I rebooted into a bootloop. Powered it off and booted into recovery and did factory reset, then rebooted. Now currently back on stock 2.2.2 boots fine. I then hopped into fastboot and attempted to flash twrp using "fastboot flash recovery recoveryname.img" This is where I'm recieving the following error:
Code:
Failed to process command getvar:partition-type:recovery error(0x2)
Any ideas on what has happened here?
Thanks
devx
Click to expand...
Click to collapse
Why are you flashing TWRP? As there is no version for Android 2.2 available. Android 2.2. has a different layout than any TWRP setup I have created.

giveen said:
Why are you flashing TWRP? As there is no version for Android 2.2 available. Android 2.2. has a different layout than any TWRP setup I have created.
Click to expand...
Click to collapse
I've now got it on Honeycomb, and booting into fastboot to flash recovery presents an identical error
Code:
Failed to process command getvar:partition-type:recovery error(0x2)
Any ideas?
Update: I figured I'd try booting from the image file rather than try to flash just to see, oddly enough this works using: fastboot boot recoveryname.img. Now if I could get it to flash...

Again, I will ask you.
Why are you flashing a recovery on stock Android 2.2¿
Sent from my Nexus 7 using Tapatalk 2

giveen said:
Again, I will ask you.
Why are you flashing a recovery on stock Android 2.2¿
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm don't intend to be condescending, but I clearly state in my last post that I had since successfully flashed Honeycomb and was no longer working with 2.2. Since then I have attempted to flash both cwm and twrp with no success. I am able to boot either of them from fastboot and have flashed ics-b5 cm9 which is what I am currently running. So I'm working around by booting the image from fastboot rather than flashing. I'm curious as to why it is throwing the error and what the error means exactly.

Okay, where did you get the copy of fastboot.
And I don't mean to be condescending but i made the twrp port. I know exactly what it needs.
Sent from my Nexus 7 using Tapatalk 2

giveen said:
Okay, where did you get the copy of fastboot.
And I don't mean to be condescending but i made the twrp port. I know exactly what it needs.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using fastboot from the android sdk

devastatorx said:
I'm using fastboot from the android sdk
Click to expand...
Click to collapse
If you got it from the SDK, thats your problem.
Recently in the Android 4.2.2 update Google decieded to add ADB signing. This required an update to the ADB and fastboot program. This resulted in total breaking of our devices ability to flash with the updated program. I am still researching a work around.
Please go to the Streak 7 Android Development section, and at the top of the forum is a link to drivers. In that pack of drivers is a copy of ADB/Fastboot that will work.

giveen said:
If you got it from the SDK, thats your problem.
Recently in the Android 4.2.2 update Google decieded to add ADB signing. This required an update to the ADB and fastboot program. This resulted in total breaking of our devices ability to flash with the updated program. I am still researching a work around.
Please go to the Streak 7 Android Development section, and at the top of the forum is a link to drivers. In that pack of drivers is a copy of ADB/Fastboot that will work.
Click to expand...
Click to collapse
I'll give that a go, thanks giveen.

error getvarartition-type:userdata user(0x2)
Hi !
My DS7 dosn´t boot.
I did a master reset, factory reset (User data only), factory reset (user data and Internal tablet storage), but the table didn`t boot.
I download the fastboot + driver from http://forum.xda-developers.com/showthread.php?t=1484406, but when I run the command "fastboot -w", it doesn´t work.
Please help me!
Thanks!

santi1928 said:
Hi !
My DS7 dosn´t boot.
I did a master reset, factory reset (User data only), factory reset (user data and Internal tablet storage), but the table didn`t boot.
I download the fastboot + driver from http://forum.xda-developers.com/showthread.php?t=1484406, but when I run the command "fastboot -w", it doesn´t work.
Please help me!
Thanks!
Click to expand...
Click to collapse
1. Start your own thread, don't hijack others
2. Need more info , as in logs, more description on what happens when you press power, charge status, did you install the drivers after downloading them, did you put the device in fastboot mode, what color of underwear are you wearing etc etc etc

****deleted*****

[Q] Tried Cyanogen and Pacman both freeze at boot screen

Okay, so I have tried Cyanogen and Pacman (both latest ROMs.) So far, I have tried to factory reset, format cache/dalvik. I have the phone unlocked and rooted with Super User and I also have gapps installed as well as Clockwork. Unfortunately, I for some reason didn't manage to get a recovery file like an idiot. I know I am S-On unsure how to get S-Off at this point. Any suggestions are tremendously appreciated.

rdavenport83 said:
Okay, so I have tried Cyanogen and Pacman (both latest ROMs.) So far, I have tried to factory reset, format cache/dalvik. I have the phone unlocked and rooted with Super User and I also have gapps installed as well as Clockwork. Unfortunately, I for some reason didn't manage to get a recovery file like an idiot. I know I am S-On unsure how to get S-Off at this point. Any suggestions are tremendously appreciated.
Click to expand...
Click to collapse
Lose clockworkmod...
You need to fastboot the boot.img...
You need Ubuntu and the stock rooted ROM to s-off...
Sent from my Vivid 4G using Tapatalk 4 Beta

I tried to do it from the cmd window, I did:
fastboot flash boot boot.img which is the one I extracted from the Cyanogen .zip file and it still boots me into Pacman, I am not sure what I am doing wrong?
C:\Android>fastboot flash boot boot.img
< waiting for device >
sending 'boot' (3588 KB)...
OKAY [ 0.780s]
writing 'boot'...
OKAY [ 4.586s]
finished. total time: 5.370s
That's what I got

Finally got the phone booted into Pacman, now I am getting the AOSD error so I'm guessing I have the wrong gapps:silly:
Well, it's not GAPPS, download the listed GAPPS in the Rom post and I still get the AOSD error <_< Any ideas?
I am extremely stuck with this problem. I can't log into the Play Store for another keyboard, I can't install an .apk via terminal because I don't have a keyboard to input commands. Any advice?

rdavenport83 said:
Finally got the phone booted into Pacman, now I am getting the AOSD error so I'm guessing I have the wrong gapps:silly:
Well, it's not GAPPS, download the listed GAPPS in the Rom post and I still get the AOSD error <_< Any ideas?
Click to expand...
Click to collapse
AOSD?
Sent from my Vivid 4G using Tapatalk 4 Beta

Apparently the wiping of all of the previous data fixed the problem Thanks for your help.

Help, in need of system image

So I was messing with some kernel stuff when after flashing something I noticed I no longer was connecting to Sprint, It just would say "No Service" I figured that restoring a NAND backup would correct this issue but it hasn't. The issue has been persistent with any rom I tried. Another issue i noticed is that I couldn't connect my phone do a PC and transfer files, I soon came to the realization the reason was that when the system booted the sd card wouldn't mount. If i tried to "cd /sdcard" it would say "no such file or directory" So unsure of what to do I began to start the process of restoring stock with RUU. But unfortunately I couldn't make it through the process. Unfortunately my sdcard got formatted when I Re-unlocked my bootloader, this means I don't have any roms to flash, and when I try to use ADB from TWRP it says there is no device connected.
I really must have screwed something up and it seems to me this won't be a quick fix. to start off I was wondering if anybody could donate a system.img from their cyanogenmod installation just so I can flash via fastboot and get started or could point me in the direction of getting one.
Thanks for the help everyone, I hope I can get my One working again.

CyrodiilSavior said:
So I was messing with some kernel stuff when after flashing something I noticed I no longer was connecting to Sprint, It just would say "No Service" I figured that restoring a NAND backup would correct this issue but it hasn't. The issue has been persistent with any rom I tried. Another issue i noticed is that I couldn't connect my phone do a PC and transfer files, I soon came to the realization the reason was that when the system booted the sd card wouldn't mount. If i tried to "cd /sdcard" it would say "no such file or directory" So unsure of what to do I began to start the process of restoring stock with RUU. But unfortunately I couldn't make it through the process. Unfortunately my sdcard got formatted when I Re-unlocked my bootloader, this means I don't have any roms to flash, and when I try to use ADB from TWRP it says there is no device connected.
I really must have screwed something up and it seems to me this won't be a quick fix. to start off I was wondering if anybody could donate a system.img from their cyanogenmod installation just so I can flash via fastboot and get started or could point me in the direction of getting one.
Thanks for the help everyone, I hope I can get my One working again.
Click to expand...
Click to collapse
First, you need to Relock your bootloader, Unroot, then S-ON your devide , Then flash RUU rom via Command in PC ( fastboot , ADB )
Finaly : if you want Flash a custom Rom , you should unlock bootloader , Root your HTC ONE , Flash recovery and then Flash custom Rom
Hope this can help you , sorry for my bad in english , I'm VietNamese

I attempted to relock unroot RUU etc. via this method, but the process got stuck at Checking Headers.
Is there another way of doing this?

CyrodiilSavior said:
I attempted to relock unroot RUU etc. via this method, but the process got stuck at Checking Headers.
Is there another way of doing this?
Click to expand...
Click to collapse
Make sure you're running it on a Windows 7 PC.

I did use a windows 7 64bit machine yesterday when it got stuck on Checking headers. I also tried on my Ubuntu system using the manual Decrypted method. Upon typing "sudo fastboot flash /system newimage.img" it returned :
Code:
target reported max download size of 1520349184 bytes
Invalid sparse file format at header magi
sending sparse '/system' (1456350 KB)...
FAILED (status read failed (Bad file descriptor))
finished. total time: 33.855s
Any ideas as to why it cant do this?

I'm sorry for not being more descriptive, I have a pretty strong background in linux and android but this issue has really stumped me.

CyrodiilSavior said:
I did use a windows 7 64bit machine yesterday when it got stuck on Checking headers. I also tried on my Ubuntu system using the manual Decrypted method. Upon typing "sudo fastboot flash /system newimage.img" it returned :
Code:
target reported max download size of 1520349184 bytes
Invalid sparse file format at header magi
sending sparse '/system' (1456350 KB)...
FAILED (status read failed (Bad file descriptor))
finished. total time: 33.855s
Any ideas as to why it cant do this?
Click to expand...
Click to collapse
The decrypted version won't work; it's for developer use only (making ROMs etc). Try using a USB-OTG cable in TWRP to flash a ROM.

StormyNight said:
The decrypted version won't work; it's for developer use only (making ROMs etc). Try using a USB-OTG cable in TWRP to flash a ROM.
Click to expand...
Click to collapse
Last night I finally managed to flash a ROM through recovery. I booted into the os and everything works fine aside from the network. I still am unable to connect to the sprint network, It just says "No Service". I've done some research and it seems to me the best/only way to fix this issue is to flash it back to stock. Which I have been unable to succeed in doing.
Let me know what you think my next step would be, either if I should continue trying to go back to stock or to fix the network issue with my current ROM.

CyrodiilSavior said:
Last night I finally managed to flash a ROM through recovery. I booted into the os and everything works fine aside from the network. I still am unable to connect to the sprint network, It just says "No Service". I've done some research and it seems to me the best/only way to fix this issue is to flash it back to stock. Which I have been unable to succeed in doing.
Let me know what you think my next step would be, either if I should continue trying to go back to stock or to fix the network issue with my current ROM.
Click to expand...
Click to collapse
Flash the latest radio/baseband founf HERE

BD619 said:
Flash the latest radio/baseband founf HERE
Click to expand...
Click to collapse
I didn't notice this till now but the sdcard is not mounting. I have the ability to mount it in recovery but when booted into system no luck. I am thinking reflashing a new boot.IMG would correct the issue.

Good news, I did an adb push and flashed the radio and that fixed it, I now can connect to sprint and my Sdcard is now mounting.
Thanks so much to everyone for the help. I really appreciate it!

Seemingly endless string of issues while trying to root

Hey guys, I've decided I'm going to root my Moto X Unlocked Edition. I've been following this guide: http://www.theandroidsoul.com/2014-moto-x-2nd-gen-marshmallow-root-86348/ (as well as many others) and I'm running into issue after issue.
I've managed to unlock my bootloader. I'm on step 8: "fastboot flash boot boot.img" and have tried with so many techniques but keep getting this "mismatched partition size (boot)" error after each attempt. I've tried using .img files from CMod, from the guide that I'm following, etc. I've googled the error with no useful result coming up. I'm at a loss here and really hoping someone is able to help me out. Searching is turning up nothing and I'm about to start tugging at my hair. If anyone has a one click installer that would work, please pass it along!
Thank you all very much!
Edit 4/29/16 13:01 ET: I've switched from trying to use the 'fastboot flash boot' command and started trying to use 'fastboot update <romname.zip >' with various different ROMs. I'm getting this error.
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Click to expand...
Click to collapse
I'm not sure what to do now. I feel like I'm getting reckless in trying an overwhelming amount of solutions to no avail. I'm going to wait, now. I'm starting to think that these phones can't be rooted or flashed with a new ROM.

What phone version do you have, XT1095? I just tried to root my device without reading carefully and ended up softbricked...had to use fastboot to wipe everything and flash stock to recover. Seems this devices is tricky to root on Marshmallow, much harder than ones I've had in the past.
Have you tried the method here? http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Or, if you install TWRP you could just flash a pre-rooted ROM instead of rooting stock.

Thank you for the help @viper74656!
I'm struggling to even get the TWRP installed. When I try to install TWRP-3.0.0-0-victara.img, I get
cmd: getvar: partition-type:recovery
cmd: getvar:max-download-size
cmd: download:0096c000
cmd: flash:recovery
Mismatched partition size (recovery)
Click to expand...
Click to collapse
I was having this problem earlier too when I was trying to work around that. I'm going to try an alternate way of installing TWRP.
Really, all I want to do is get CMod. When I rooted my HTC Inspire 4G, it was a cakewalk... I didn't expect all this LOL

viper74656 said:
What phone version do you have, XT1095? I just tried to root my device without reading carefully and ended up softbricked...had to use fastboot to wipe everything and flash stock to recover. Seems this devices is tricky to root on Marshmallow, much harder than ones I've had in the past.
Have you tried the method here? http://forum.xda-developers.com/moto-x-2014/development/root-root-moto-x-2014-android-t3249105
Or, if you install TWRP you could just flash a pre-rooted ROM instead of rooting stock.
Click to expand...
Click to collapse
Yeah, btw, I have an xXT1095

So I managed to get TWRP installed on my XT1095 using the "WinDroid" toolkit I found somewhere on XDA. It seems to push the right fastboot commands, but I had to manually download and select an older TWRP version. Read something about our recovery partition not working with the newer versions. I still got the mismatch error, but when I rebooted into recovery TWRP was there.
I haven't ventured back to try it again after having to wipe and start over...bleh.

Twrp manager (from the playstore) is what I had to use to install recovery. Windroid wouldn't push it for some reason.
Sent from my XT1096 using XDA-Developers mobile app

Fastboot Strangeness, Having Issues Rooting/Installing ROMS

Hello!
I've been enjoying my rooted Pixel 5 but today I saw that the first Pixel 5 ROM is available so I went to go try it. Just like the instructions asked I tried to flash the ROM like it was a standard stock image since we don't have TWRP yet. Everything was going fine until it got to the part where it sent boot.img, it would fail at that point saying the partition doesn't exist. The exact error was...
HTML:
FAILED (remote: Failed to write to partition Not Found)
I also did the 'fastboot -w' to wipe user data before rebooting as instructed, it just booted back into fastboot with the reason listed as "no valid slot to boot". After a while I figured out I could use 'fastboot flash boot_a /path/to/boot.img' to flash the slots manually and that booted me into stock Android, not the ROM. Even though I used the boot.img from the ROM, no ROM was installed.
After this I decided to go back to stock and flash Magisk again and wait until we have some more stable ROMs. annnnnnd that's where I realized I was in trouble. I tried doing 'flash-all.bat' like normal and it gave me the same error the ROM did. I then manually flashed the stock boot.img and set up the phone, once I was at the home screen I turned it off, flashed my prepared 'magisk_patched.img', all seemed to go just fine, but upon trying to reboot its stuck at fastboot again. I can get back to my homescreen by just flashing the stock boot.img but no matter what I try I cannot get it to reboot after flashing the patched image.
Things I have tried:
Updating ADB/Fastboot
Reinstalling ADB/Fastboot
Updating USB Drivers
Flash to Stock and Retry
Repatch a new image using Magisk Canary
Lots and Lots of reboots
Several attempts at all of the above (last time I rooted it gave me errors and then just worked for no reason after some reboots and tries)
Above steps in Linux Terminal (Ubuntu WSL)
For the night I'm just going to flash the Stock boot.img so I can have my alarms and receive messages, but I'd really like to return to stock as I use Tasker frequently as well as some other applications that require root access. If anyone has any tips for how to get more consistent results when rooting, I have no idea why it works sometimes and not other times. If anyone knows how to solve these errors please let me know.
Thanks y'all
***EDIT - FIXED, NOT SOLVED***: I'm still unsure what caused it in the first place, but I was able to regain root by flashing the October update, patching a new boot.img from that update, and then flashing. I was previously using the latest November update. I think that when I tried to flash the ROM something went wrong and it left things behind, and I don't think my original flash back to stock worked completely because flashing the October update took about 4 times as long. I used Pixel 5 unlocked stock images from Google's website for both attempts so im not sure why one worked and the other didn't, but I am rooted. If anyone else is experiencing similar issues, try flashing to a previous software update and rooting that.

this may be a stupid question but did you enable "Developer Options" and "OEM Unlocking"?
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-5-easy-follow-guide-0329550/

grisly grizzly said:
Hello!
I've been enjoying my rooted Pixel 5 but today I saw that the first Pixel 5 ROM is available so I went to go try it. Just like the instructions asked I tried to flash the ROM like it was a standard stock image since we don't have TWRP yet. Everything was going fine until it got to the part where it sent boot.img, it would fail at that point saying the partition doesn't exist. The exact error was...
HTML:
FAILED (remote: Failed to write to partition Not Found)
I also did the 'fastboot -w' to wipe user data before rebooting as instructed, it just booted back into fastboot with the reason listed as "no valid slot to boot". After a while I figured out I could use 'fastboot flash boot_a /path/to/boot.img' to flash the slots manually and that booted me into stock Android, not the ROM. Even though I used the boot.img from the ROM, no ROM was installed.
After this I decided to go back to stock and flash Magisk again and wait until we have some more stable ROMs. annnnnnd that's where I realized I was in trouble. I tried doing 'flash-all.bat' like normal and it gave me the same error the ROM did. I then manually flashed the stock boot.img and set up the phone, once I was at the home screen I turned it off, flashed my prepared 'magisk_patched.img', all seemed to go just fine, but upon trying to reboot its stuck at fastboot again. I can get back to my homescreen by just flashing the stock boot.img but no matter what I try I cannot get it to reboot after flashing the patched image.
Things I have tried:
Updating ADB/Fastboot
Reinstalling ADB/Fastboot
Updating USB Drivers
Flash to Stock and Retry
Repatch a new image using Magisk Canary
Lots and Lots of reboots
Several attempts at all of the above (last time I rooted it gave me errors and then just worked for no reason after some reboots and tries)
Above steps in Linux Terminal (Ubuntu WSL)
For the night I'm just going to flash the Stock boot.img so I can have my alarms and receive messages, but I'd really like to return to stock as I use Tasker frequently as well as some other applications that require root access. If anyone has any tips for how to get more consistent results when rooting, I have no idea why it works sometimes and not other times. If anyone knows how to solve these errors please let me know.
Thanks y'all
Click to expand...
Click to collapse
And you have usb debugging on

swangjang said:
this may be a stupid question but did you enable "Developer Options" and "OEM Unlocking"?
https://android.gadgethacks.com/how-to/unlock-bootloader-your-pixel-5-easy-follow-guide-0329550/
Click to expand...
Click to collapse
Hey, Yes OEM Unlocking is on and greyed out. It was giving me the option to turn it off again before, not sure why it isn't now.

jaythenut said:
And you have usb debugging on
Click to expand...
Click to collapse
I actually did not have USB debugging enabled, but after doing so I have the same problem. Just tried to flash magisk with the two custom .img files I made last night, and my last confirmed working one, same problem as before. It successfully flashes, then bootloops til I reflash the stock boot.img.

grisly grizzly said:
I actually did not have USB debugging enabled, but after doing so I have the same problem. Just tried to flash magisk with the two custom .img files I made last night, and my last confirmed working one, same problem as before. It successfully flashes, then bootloops til I reflash the stock boot.img.
Click to expand...
Click to collapse
Don't know if it will work but flash magisk on slot a and b
And just checking you done
fastboot flash boot magisk_patched.img

jaythenut said:
Don't know if it will work but flash magisk on slot a and b
And just checking you done
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
I think I tried that last night, but I tried again just now with a new patched.img just in case. Flashed successfully but same problem. Here's my exact powershell input/output. For powershell I gotta use ./fastboot but its the same as running 'fastboot' in cmd. And I've using powershell with and without admin access.
HTML:
PS C:\platform-tools> ./fastboot flash boot_a ".\patched.img"
Sending 'boot_a' (98304 KB) OKAY [ 0.469s]
Writing 'boot_a' OKAY [ 1.993s]
Finished. Total time: 2.725s
PS C:\platform-tools> ./fastboot flash boot_b ".\patched.img"
Sending 'boot_b' (98304 KB) OKAY [ 0.469s]
Writing 'boot_b' OKAY [ 1.981s]
Finished. Total time: 2.713s
Just gets me back to the fast boot menu saying boot partition not found, just flashed the stock boot.img and I'm back at my home screen again. If its of any importance, I only had to flash the stock boot.img to slot a in order to get back to my home screen. Slot B should still be flashed with the patched.img, no root access on slot a though.
Edit: Do you think it would be helpful to relock the bootloader (since it returns everything to stock) and then re-unlock and re-root? Nevermind I forgot that re-locking makes it so you can't re-unlock. Won't do that.

how exactly did you flash the stock rom bc im lost on this process.... Heres where im at bc i cant get any help from the ProtonAOSP thread or anywhere. ive never flashed a rom without twrp and im lost now:
BC This is what ive been getting:
C:\Users\james\AppData\Local\Android\Sdk\platform-tools>fastboot flash C:\Users\james\AppData\Local\Android\Sdk\platform-tools\proton-aosp_redfin_11.3.1.zip
unknown partition 'C:\Users\james\AppData\Local\Android\Sdk\platform-tools\proton-aosp_redfin_11.3.1.zip'
fastboot: error: cannot determine image filename for 'C:\Users\james\AppData\Local\Android\Sdk\platform-tools\proton-aosp_redfin_11.3.1.zip'
and now this fof Fastboot boot ZipFile
C:\Users\james\AppData\Local\Android\Sdk\platform-tools>fastboot boot C:\Users\james\AppData\Local\Android\Sdk\platform-tools\proton-aosp_redfin_11.3.1-gapps.zip
creating boot image...
terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
but what im not understanding is do u unzip it to platform-tools and use flash-all, like reverting back to stock? bc this is what i get when i dont unzip it and just copy it to platform-tools directory from my downloads folder. this is my first time flashing a custom rom and i just cant seem to get anyone to tell me exactly what i need to do or what im doing wrong. PLEASE HELP