Develop Bugs

[Q] Need help ASAP! CWM problem.

Hey guys, this is my first post on XDA forum.
So I've recently bought a nexus 7, I used wugfresh's root kit to root my nexus but then it didn't work... so I've tired the auto root by chainfire. Then I was able to get root. So then I went to playstore and downloaded rom manager to install CWM. I went to recovery then I get this message:
E : Cant mount /cache/recovery/log etc.....
I've tried everything I can do such as researching, changing recovery, and watching a youtube tutorial but nothing helped.
Thanks.

I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.

nhizzat said:
I would start over from scratch using fastboot to flash a factory image and stock recovery. If your bootloader isn't unlocked already, unlock it.
Click to expand...
Click to collapse
I tried to format using wugfresh couple times but still not working...

DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- https://developers.google.com/android/nexus/images
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.

_MetalHead_ said:
DO NOT USE TOOLKITS. They cause too many problems. Learn to do things the proper way using fastboot. I agree with the poster above, you should flash a factory image to start over. Download the system image from here- Link Removed
You need to unlock your bootloader-
Code:
fastboot OEM unlock
Then run the flash_all.bat. That will automatically wipe and reflash everything to get you back to square one.
Then you need to flash TWRP (don't use CWM)
Code:
fastboot flash recovery recoveryname.img
TWRP will automatically prompt you to flash SU when you reboot. Choose yes, reboot, then install SuperSU from play store, update the SU binaries, reboot again, and then you're done.
Click to expand...
Click to collapse
I tried to flash TWRP but its still the same error code

z3r0c311 said:
I tried to flash TWRP but its still the same error code
Click to expand...
Click to collapse
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.

_MetalHead_ said:
I highly advise you start from scratch so do what I told you to do in my last post. I promise if you do it the correct way (ie. without using toolkits) it will work.
Click to expand...
Click to collapse
It would be great if u could tell me the commands, im nubby with this fastboot thing.

z3r0c311 said:
It would be great if u could tell me the commands, im nubby with this fastboot thing.
Click to expand...
Click to collapse
I gave you the commands in my first post in this thread.
Here's a guide to get you started-
http://forum.xda-developers.com/showthread.php?t=2277112

Sorry for another nubby question but how do I get flash_all.bat?

z3r0c311 said:
Sorry for another nubby question but how do I get flash_all.bat?
Click to expand...
Click to collapse
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.

_MetalHead_ said:
It's in the file that you should have downloaded from the link I posted in my first post. The instructions are at that link as well.
Click to expand...
Click to collapse
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.

z3r0c311 said:
Hey I tried the following:
oem lock
oem unlock
flash-all/flash_all.bat
flash recovery(TWRP)
but then when I reboot into TWRP I don't get a message saying you to install SU... And when I go to 'Install' in TWRP I don't see any internal storage available(0mb). With this error I cant install any roms which is boring.
Click to expand...
Click to collapse
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?

_MetalHead_ said:
Hmm... Can you even boot into the stock ROM at this point? Try formatting /data (done in TWRP). Did the system image flash successfully?
Click to expand...
Click to collapse
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...

z3r0c311 said:
I can boot into my stock rom which is 5.0.2, when I try to format /data the error codes comes out...
Click to expand...
Click to collapse
Did the system image flash successfully?

_MetalHead_ said:
Did the system image flash successfully?
Click to expand...
Click to collapse
using flash-all command, yeah

z3r0c311 said:
using flash-all command, yeah
Click to expand...
Click to collapse
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.

_MetalHead_ said:
Well then I don't know what to tell you at this point. I know Lollipop has been causing issues for some N7 users, but I also know that wugs toolkit causes problems too so honestly I'm not sure what the root of your issue is. I think someone with more experience with Lollipop is gonna have to chime in here, I'm still on 4.4.4 on all of my devices. Sorry I couldn't be of more help.
Click to expand...
Click to collapse
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...

z3r0c311 said:
Thanks for helping me I appreciate it. I hope someone else can help me with this problem... btw can I flash roms with the stock recovery? The stock recovery seems to be working fine...
Click to expand...
Click to collapse
No, you can only flash custom ROMs if you have a custom recovery.

Help！i can‘t flash anything into my tablet. fastboot failed, remote: unsupported comm

Help！i can‘t flash anything into my tablet. fastboot failed, remote: unsupported comm
Good day everyone. Please help me. I am in Unicorn rom and I want to go back factory rom. I tried Nexus Tookit and ABD fastboot, but all of them errored out Fastboot failed, remote:unsupported command.
I cannot get into recovery.
Help me please.

Sway327 said:
Good day everyone. Please help me. I am in Unicorn rom and I want to go back factory rom. I tried Nexus Tookit and ABD fastboot, but all of them errored out Fastboot failed, remote:unsupported command.
I cannot get into recovery.
Help me please.
Click to expand...
Click to collapse
Are you sure that you can't reboot in twrp ..did you already try to do it manually ?
anyway if you want go back stock and you aren't able to use again NRT you need to flash manually a factory image from Google .Here is a the link with instructions ;
https://developers.google.com/android/nexus/images

if fastboot flash doesn't work you probably have fastboot locked.

brando56894 said:
if fastboot flash doesn't work you probably have fastboot locked.
Click to expand...
Click to collapse
Thanks mate. Do you know how to unlock fastboot?

ilpolpi65 said:
Are you sure that you can't reboot in twrp ..did you already try to do it manually ?
anyway if you want go back stock and you aren't able to use again NRT you need to flash manually a factory image from Google .Here is a the link with instructions ;
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Thanks mate. Thanks for your reply. I tried mini ADB tool to flash it and got same result.
FAIL remote: unsupported command

Sway327 said:
Thanks mate. Thanks for your reply. I tried mini ADB tool to flash it and got same result.
FAIL remote: unsupported command
Click to expand...
Click to collapse
Are you able to get back into system? If so, run this command with an active ADB connection.
Code:
fwtool vbnv write dev_boot_fastboot_full_cap 1

Sway327 said:
Good day everyone. Please help me. I am in Unicorn rom and I want to go back factory rom. I tried Nexus Tookit and ABD fastboot, but all of them errored out Fastboot failed, remote:unsupported command.
I cannot get into recovery.
Help me please.
Click to expand...
Click to collapse
Hi, I was wondering if you were able to fix your tablet. I have this problem right now and haven't found any way of fixing it.

NYCHitman1 said:
Are you able to get back into system? If so, run this command with an active ADB connection.
Click to expand...
Click to collapse
Hi. I was wondering if you know how to fix this only through fastboot. I get the same "remote: unsupported command" message when flashing partitions and "remote: image verification failed" when using "fastboot boot twrp.img" command. Right now, I have no recovery and cannot boot to system. Locking and reunlocking bootloader doesn't change a thing and I do have the latest drivers.

viii_xvi said:
Hi. I was wondering if you know how to fix this only through fastboot. I get the same "remote: unsupported command" message when flashing partitions and "remote: image verification failed" when using "fastboot boot twrp.img" command. Right now, I have no recovery and cannot boot to system. Locking and reunlocking bootloader doesn't change a thing and I do have the latest drivers.
Click to expand...
Click to collapse
Did you get your tablet to work? I have the same problem

qAnAthemA said:
Did you get your tablet to work? I have the same problem
Click to expand...
Click to collapse
No, I haven't gotten it to work. As far as I know, there is only one way to fix it and it involves opening up the tablet, as per this post.

viii_xvi said:
No, I haven't gotten it to work. As far as I know, there is only one way to fix it and it involves opening up the tablet, as per this post.
Click to expand...
Click to collapse
Have you tried to ask Google for a USB bootable recovery + ZIP file ?

Can't downgrade from Android 8.1.

I installed the 8.1 dp on my pixel 2 xl and I have decided to go back to android 8.0. I signed out of the beta and the OTA showed up as it was supposed to, from there I tried to install the downgrading OTA but it came up with a generic error (update was not able to be installed) from there I decided to try flashing the factory image and this error came up
writing 'bootb'...
FAILED (remote: No such partition.)
and when I rebooted it booted fine but was still on android 8.1. I also tried manually flashing the system partition as I noticed the script made no mention of flashing system, it came up with the error
sending sparse 'systemb' 1/4 (524284 KB)...
OKAY [ 16.552s]
writing 'systemb' 1/4...
FAILED (remote: No such partition.)
and once again after a reboot it went back to android 8.1. Any help is appreciated, thanks.

Download and flash the entire Factory image from Google's factory image page. That should work. However, this will wipe your phone.

I did flash the factory image which is what resulted in the partition error.

If you updated OTA, you can opt out of the beta, then go back to Software updates on your phone, and it will downgrade you back to 8.0.

Make sure you have the latest version of fastboot and flash the entire factory image using the flashall script. Should work.

Moostafa29 said:
If you updated OTA, you can opt out of the beta, then go back to Software updates on your phone, and it will downgrade you back to 8.0.
Click to expand...
Click to collapse
I already tried downgrading through the OTA, it came up with a generic error.
clnzx2 said:
Make sure you have the latest version of fastboot and flash the entire factory image using the flashall script. Should work.
Click to expand...
Click to collapse
It's been a while since i've updated adb, that might be the issue. I'll try it when i get home.

I think you're missing underscores. The partitions that you are flashing to should be boot_b and system_b. Also, it is crucial to use the latest version of fastboot (adb is not used).

I always open the flash all script to read the text then I do exactly that manually, and of course I skip the -w (which will wipe) through fastboot. Usually works great but I haven't tried yet on the Pixel 2 XL,

TheSt33v said:
I think you're missing underscores. The partitions that you are flashing to should be boot_b and system_b. Also, it is crucial to use the latest version of fastboot (adb is not used).
Click to expand...
Click to collapse
I'll update fastboot, maybe the flash-all script that is provided is incorrectly formatted so I'll try editing it to have underscores.
TheDonXR said:
I always open the flash all script to read the text then I do exactly that manually, and of course I skip the -w (which will wipe) through fastboot. Usually works great but I haven't tried yet on the Pixel 2 XL,
Click to expand...
Click to collapse
I tried doing this somewhat, I'll try going through this all the way but with the underscores as suggested above.

Afriendlytrashcan said:
I'll update fastboot, maybe the flash-all script that is provided is incorrectly formatted so I'll try editing it to have underscores.
I tried doing this somewhat, I'll try going through this all the way but with the underscores as suggested above.
Click to expand...
Click to collapse
I just downloaded the most recent factory image and the flash-all script doesn't mention flashing the boot image at all. It uses the update command to flash all of the necessary images. If you are looking at a script that flashes things differently, it's probably the wrong script.
If I had to take a guess, I'd say that the new version of fastboot knows to flash things differently with the new Pixels than with other devices, so the update command means something different to the old version than it does to the new version. When you tried the flash-all script initially, you were using the old version of fastboot so it tried to flash the image in a way that is not correct for the current pixels. My bet is that if you use the flash-all script with the newer fastboot, things will go better for you.

Afriendlytrashcan said:
I already tried downgrading through the OTA, it came up with a generic error.
It's been a while since i've updated adb, that might be the issue. I'll try it when i get home.
Click to expand...
Click to collapse
That is your problem. Update to latest tools and it will work. :good:

TheSt33v said:
I just downloaded the most recent factory image and the flash-all script doesn't mention flashing the boot image at all. It uses the update command to flash all of the necessary images. If you are looking at a script that flashes things differently, it's probably the wrong script.
If I had to take a guess, I'd say that the new version of fastboot knows to flash things differently with the new Pixels than with other devices, so the update command means something different to the old version than it does to the new version. When you tried the flash-all script initially, you were using the old version of fastboot so it tried to flash the image in a way that is not correct for the current pixels. My bet is that if you use the flash-all script with the newer fastboot, things will go better for you.
Click to expand...
Click to collapse
clnzx2 said:
That is your problem. Update to latest tools and it will work. :good:
Click to expand...
Click to collapse
Sounds good! I'll try it a bit later, my fingers have never been more crossed.

It worked! After updating fastboot the flash-all zip worked perfectly. Thanks everyone for your help!

Hey everyone. Just tried 9 DP1 and wanted to revert to 8.1 and just ran into this.
Since it can be overread easily: for the next one who's searching for this:
Edit the "flash-all.bat" (or .sh on Linux) and delete the "-w" after the fastboot command that flashes the ZIP.
You can wipe with fastboot or within recovery. If the system dows not boot, the Pixel 2 XL starts the recovery automatically and asks if you want to wipe.
Wasten over an hour, it's f*late and I'm tired, it's 1:16 AM here right now.
EDIT: You of course need to unlock and relock twice on the 2 XL
fastboot flashing unlock_critical
fastboot flashing unlock
fastboot flashing lock_critical
fastboot flashing lock

TimeTurn said:
Hey everyone. Just tried 9 DP1 and wanted to revert to 8.1 and just ran into this.
Since it can be overread easily: for the next one who's searching for this:
Edit the "flash-all.bat" (or .sh on Linux) and delete the "-w" after the fastboot command that flashes the ZIP.
You can wipe with fastboot or within recovery. If the system dows not boot, the Pixel 2 XL starts the recovery automatically and asks if you want to wipe.
Wasten over an hour, it's f*late and I'm tired, it's 1:16 AM here right now.
EDIT: You of course need to unlock and relock twice on the 2 XL
fastboot flashing unlock_critical
fastboot flashing unlock
fastboot flashing lock_critical
fastboot flashing lock
Click to expand...
Click to collapse
Sooooo....you were able to get back to 8.1 and then locked then unlocked the bootloader???

Badger50 said:
Sooooo....you were able to get back to 8.1 and then locked then unlocked the bootloader???
Click to expand...
Click to collapse
He said he was tired...

galaxys said:
He said he was tired...
Click to expand...
Click to collapse
Well shucks! ???

so actualy there is option to go back in versions?
that's nice!

I7210I said:
so actualy there is option to go back in versions?
that's nice!
Click to expand...
Click to collapse
It should be possible since the PDP1 is not yet official. More than likely, you'll need to do a full wipe, and clean flash to get back to 8.1 ?

Badger50 said:
It should be possible since the PDP1 is not yet official. More than likely, you'll need to do a full wipe, and clean flash to get back to 8.1 [emoji50]
Click to expand...
Click to collapse
so it's not quite works now?
in nexus it was worked right away
Sent from my Pixel 2 XL using Tapatalk

After clean flash the January factory image my pixel 2 xl doesn't start

It says Your device is corrupt. It can't be trusted and may not work properly.And i press power button to continue, it's stuck in google' logo with an unlock below.
Please!Someone help me!

How did you do the "clean flash"? To do a complete clean flash, you need to install the latest factory image for your device (make sure you get the right one; there is a Verizon one thats different). Extract all the files into your folder containing adb and fastboot. Boot your device into the bootloader then run the flash-all.bat file. This process with completely wipe your device (including data). But if it doesn't boot from that clean of a flash then there is something seriously wrong.

Ericarthurc said:
How did you do the "clean flash"? To do a complete clean flash, you need to install the latest factory image for your device (make sure you get the right one; there is a Verizon one thats different). Extract all the files into your folder containing adb and fastboot. Boot your device into the bootloader then run the flash-all.bat file. This process with completely wipe your device (including data). But if it doesn't boot from that clean of a flash then there is something seriously wrong.
Click to expand...
Click to collapse
Ty. I used the right factory image.Should i add platsorm-tools to taimen-opm1.171.1019.013 folder?

tierslhq said:
Ty. I used the right factory image.Should i add platsorm-tools to taimen-opm1.171.1019.013 folder?
Click to expand...
Click to collapse
Yeah head here and give this a shot; good luck. Try posting your issue in that sub forum for help from those guys. I have no experience with that tool, sorry.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

Ericarthurc said:
Yeah head here and give this a shot; good luck. Try posting your issue in that sub forum for help from those guys. I have no experience with that tool, sorry.
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Thanks!!!She is alive now!!!Oh my goodness!!! Thank you! Love you!

tierslhq said:
Thanks!!!She is alive now!!!Oh my goodness!!! Thank you! Love you!
Click to expand...
Click to collapse
Haha, no problem. But thank the guy who made that tool!

Not sure what steps you followed but what I did was; factory reset device from settings, rebooted, once start screen showed I rebooted to bootloader, fastboot unlocked device, fastboot unlocked critical, extracted image to my adb folder and clicked flash all, I saw the same screen you did so I rebooted to bootloader again, fastboot locked critical, fastboot locked device, rebooted and I'm back to it running like it's new out the box. I was having battery issues.

Need help manually flashing factory image

Due to limitations with my chromebook i am force to flash a factory image manually. flash all causes an I/O error. can someone list all the commands to flash it all manually. was on dp3 and tried to boot a custom rom.
i would like to go back to most current june update if possible.
everything i have found online is for older devices

motcher41 said:
Due to limitations with my chromebook i am force to flash a factory image manually. flash all causes an I/O error. can someone list all the commands to flash it all manually. was on dp3 and tried to boot a custom rom.
i would like to go back to most current june update if possible.
everything i have found online is for older devices
Click to expand...
Click to collapse
How did you get to DP3? Did you enroll in the beta program?

Badger50 said:
How did you get to DP3? Did you enroll in the beta program?
Click to expand...
Click to collapse
yes and weirdly using a factory image on my Mi A1 gave no error

motcher41 said:
yes
Click to expand...
Click to collapse
Then just unenroll from the beta program. You'll then get an OTA that will wipe your phone, and put you back on 8.1 :good:

Badger50 said:
Then just unenroll from the beta program. You'll then get an OTA that will wipe your phone, and put you back on 8.1 :good:
Click to expand...
Click to collapse
i would but i am currently soft bricked. have access to bootloader only

even tried to sideload an ota image but no luck there either. either have to flash it all manually or buy a real pc

motcher41 said:
even tried to sideload an ota image but no luck there either. either have to flash it all manually or buy a real pc
Click to expand...
Click to collapse
Oh boy, your in pickle then! Then I suppose you'll have to....
fastboot format userdata
Then fastboot each image, which I think there are 21 of them if memory serves.
The command lines aren't that hard, just a lot of them. Start with the bootloader, then radio, then just start going down the list, ie.......
fastboot flash bootloader bootloaderxxxxx.img
fastboot reboot bootloader
fastboot flash radio radioxxxxxxx.img
fastboot reboot bootloader
Then just start flashing all the images from the secondary zip you'll find in the factory image.

but are they all the same target as the .img name

Badger50 said:
Oh boy, your in pickle then! Then I suppose you'll have to....
fastboot format userdata
Then fastboot each image, which I think there are 21 of them if memory serves.
The command lines aren't that hard, just a lot of them. Start with the bootloader, then radio, then just start going down the list, ie.......
fastboot flash bootloader bootloaderxxxxx.img
fastboot reboot bootloader
fastboot flash radio radioxxxxxxx.img
fastboot reboot bootloader
Then just start flashing all the images from the secondary zip you'll find in the factory image.
Click to expand...
Click to collapse
wow that actually worked....the flashing of everything to slot by name except the system_other
format userata command gave an error too

motcher41 said:
wow that actually worked....the flashing of everything to slot by name except the system_other
format userata command gave an error too
Click to expand...
Click to collapse
Hey, as long as it worked your good. Welcome :good:
Yeah my format userdata may have been off. I was going by memory from my 6p. P2XL might be different. Sorry.