Database Users

[Q] Nexus 7 Bricked, can't access Bootloader or Fastboot

I think I may have my Nexus 7 (2012) in a badly bricked state.
I was running Android 4.3, unlocked and rooted with stock recovery. The tablet froze while using GMail. Pressing the home or back buttons just gave me a black screen with the buttons "highlighted" by circles. I waited several minutes and decided to just power off the tablet. When I looked over about a half hour later I saw that the tablet was frozen on the white Google screen. Two more reboots produced the same result.
I did some research and determined that it might be a good idea to try a cache wipe. I booted into the bootloader and selected Recovery. The tablet rebooted to an android on his back with a red triangle and the words "No command" underneath. Attempting to boot back into the bootloader (Power, Vol+, Vol-) produced the same results - red triangle and the words "No command". I could no longer boot into the bootloader. Powering off and powering on normally also takes me to "No command".
I discovered that I can press Power & Vol+ while in the "No command" state. Doing so produces the following text at the bottom of the screen:
E:Can't open /cache/recovery/log
E: Can't open /cache/recovery/last_log
E: Can't open /cache/recovery/last_install
E: failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC
(I/O error)
I get a menu at the top with the options to reboot, apply update from ADB, wipe data/factory reset and wipe cache. Attempting to wipe cache produces:
-- Wiping cache...
Formatting /cache..
Cache wipe complete.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_locale
After a few minutes I boot back to the red triangle android.
Attempting a factory reset produces:
--Wiping data...
Formating /data...
Formatting /cache...
Date wipe complete.
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
E: failed closing /dev/block/platform/sdhci-tegra.3/by-name/MSC
(I/O error)
E:failed to mount /cache (Invalid argument)
I've tried using the apply update from ADB option. I can use adb devices to see the serial number. Fastboot doesn't seem to respond and won't list the device. Flashing the factory 4.3 image (downloaded from Google and unzipped) using adb sideload uploads the image and then produces the error:
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
...followed by all of the "cache mount / open errors shown previously"
Not sure what else to try. (I'm learning all of this as I go from reading posts on this site.) Is there a way to adb sideload the recovery partition as I suspect that it is corrupt?
Sorry to be so long winded. I figured that too much info was better than not enough. Any help would be greatly appreciated.

So you can still access the recovery menu? That surely means that your tablet isn't bricked and if you can access the recovery, then you too must be able to access the bootloader. Power off your tablet and try to boot into fastboot by using power and volume -, volume + isn't necessary. Are you sure you have also installed the drivers for fastboot mode? Then try to flash the factory images using the guide here
http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using xda app-developers app

Remcotjuuh said:
So you can still access the recovery menu? That surely means that your tablet isn't bricked and if you can access the recovery, then you too must be able to access the bootloader. Power off your tablet and try to boot into fastboot by using power and volume -, volume + isn't necessary. Are you sure you have also installed the drivers for fastboot mode? Then try to flash the factory images using the guide here
http://forum.xda-developers.com/showthread.php?t=1907796
Click to expand...
Click to collapse
First - thanks for responding.
To answer your questions. No, I can't access the recovery menu. It doesn't matter how I boot - power button only, power button and vol-, vol+ or power, vol- only --- the device immediately boots to the android on his back with the red triangle. I don't get the normal "menu" where I can use the buttons to choose and select recovery mode. Sometimes there are the words "No command" under the android, sometimes there isn't. I can't get the tablet into fastboot mode.
When the device boots to the android + red triangle, the only thing I have been able to do is push power, Vol+ which gets me to the menu with
reboot system now
apply update from ADB
wipe date/factory reset
wipe cache partition
The "wipe" options fail with the text shown in my original post. If I select "apply update from ADB" it puts the device into ADB Sideload mode. (Not normal ADB mode.) My only option here is to ADB sideload images. I have tried sideloading the factory image. The image transferes, but it fails with a signature error and won't install. I have downloaded the image several times directly from google.
I have uninstalled and reinstalled the drivers a few times. I've used the article that you referenced, another article on this site and used the Wugs Nexus Root Toolkit to install the drivers. I know that my drivers were good originally as I used them to root the device.
Could the errors that I am seeing when I attempt the wipe options indicate a hardware issue? The device seems to be attempting to mount the cache and other partitions and can't.
Additional help is greatly appreciated. Thanks.

awhite2600 said:
First - thanks for responding.
To answer your questions. No, I can't access the recovery menu. It doesn't matter how I boot - power button only, power button and vol-, vol+ or power, vol- only --- the device immediately boots to the android on his back with the red triangle. I don't get the normal "menu" where I can use the buttons to choose and select recovery mode. Sometimes there are the words "No command" under the android, sometimes there isn't. I can't get the tablet into fastboot mode.
When the device boots to the android + red triangle, the only thing I have been able to do is push power, Vol+ which gets me to the menu with
reboot system now
apply update from ADB
wipe date/factory reset
wipe cache partition
The "wipe" options fail with the text shown in my original post. If I select "apply update from ADB" it puts the device into ADB Sideload mode. (Not normal ADB mode.) My only option here is to ADB sideload images. I have tried sideloading the factory image. The image transferes, but it fails with a signature error and won't install. I have downloaded the image several times directly from google.
I have uninstalled and reinstalled the drivers a few times. I've used the article that you referenced, another article on this site and used the Wugs Nexus Root Toolkit to install the drivers. I know that my drivers were good originally as I used them to root the device.
Could the errors that I am seeing when I attempt the wipe options indicate a hardware issue? The device seems to be attempting to mount the cache and other partitions and can't.
Additional help is greatly appreciated. Thanks.
Click to expand...
Click to collapse
Is it under warranty?

xbt- said:
Is it under warranty?
Click to expand...
Click to collapse
No. It's about 10 months old.

Your cache partition is corrupt. Because cache is corrupt, your N7 probably can't boot anything but recovery. Did your N7 turn off while you were wiping cache or something?
Sent from my Nexus 7 using Tapatalk 4

Looks to me as if your boot / system is not working or corrupt. But you are writing you boot always to the dead Android, that's the bootloader mode and from there you should be able to flash a new system by fastboot. As long as you can go to bootloader there is hope for your device unless some hardware defect prevents you from flashing the system images. Try to install the fastboot drivers for your OS and then try to flash the system images. Probably you need to unlock your bootloader first.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Looks to me as if your boot / system is not working or corrupt. But you are writing you boot always to the dead Android, that's the bootloader mode and from there you should be able to flash a new system by fastboot. As long as you can go to bootloader there is hope for your device unless some hardware defect prevents you from flashing the system images. Try to install the fastboot drivers for your OS and then try to flash the system images. Probably you need to unlock your bootloader first.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
He has already said he can only boot into stock recovery, not bootloader.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 12:08 PM ---------- Previous post was at 12:07 PM ----------
Now I got myself thinking, the factory images fail, but what about an image for a custom recovery? Try to adb sideload yours from www.clockworkmod.com/rommanager. Is your bootloader unlocked?
Sent from my Nexus 7 using xda app-developers app

cmason37 said:
Your cache partition is corrupt. Because cache is corrupt, your N7 probably can't boot anything but recovery. Did your N7 turn off while you were wiping cache or something?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
The tablet froze during normal operation. (Checking GMail.) I simply turned it off...or so I though. When I looked over about 30 minutes later it was stuck on the white "Google" screen. I was able to boot into the normal bootloader at this point. My thoughts were to then select stock recovery and just wipe the cache. It's been in the "red triangle" and "No command" since then.

AndDiSa said:
Looks to me as if your boot / system is not working or corrupt. But you are writing you boot always to the dead Android, that's the bootloader mode and from there you should be able to flash a new system by fastboot. As long as you can go to bootloader there is hope for your device unless some hardware defect prevents you from flashing the system images. Try to install the fastboot drivers for your OS and then try to flash the system images. Probably you need to unlock your bootloader first.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The bootloader is unlocked. I was rooted with stock recovery. I have uninstalled and reinstalled drivers several times. I know for certain that the ADB drivers are installed. I don't have an easy way to confirm that the fastboot drivers are installed - but they should be.

Remcotjuuh said:
He has already said he can only boot into stock recovery, not bootloader.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 12:08 PM ---------- Previous post was at 12:07 PM ----------
Now I got myself thinking, the factory images fail, but what about an image for a custom recovery? Try to adb sideload yours from www.clockworkmod.com/rommanager. Is your bootloader unlocked?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I can try sideloading a custom recovery. I may have already tried this...I've tried so many things. I will try again.
The link that you provided points to .img downloads. I thought that ADB Sideload only worked with .zip images. Am I wrong?

awhite2600 said:
I can try sideloading a custom recovery. I may have already tried this...I've tried so many things. I will try again.
The link that you provided points to .img downloads. I thought that ADB Sideload only worked with .zip images. Am I wrong?
Click to expand...
Click to collapse
Remcotjuuh said:
He has already said he can only boot into stock recovery, not bootloader.
Sent from my Nexus 7 using xda app-developers app
---------- Post added at 12:08 PM ---------- Previous post was at 12:07 PM ----------
Now I got myself thinking, the factory images fail, but what about an image for a custom recovery? Try to adb sideload yours from www.clockworkmod.com/rommanager. Is your bootloader unlocked?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I tried sideloading the clockwork recovery. The .img file transfers. The Nexus 7 then displays:
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted.
:
followed by all of the E: can't mount/open cache/recovery messages as mentioned in my initial post.

Then I'm getting to a dead end here too. I guess you have tried flashing the bootloader too? And how about using the "flash-all.bat" in the factory images package?
Edit:
Maybe sideloading the zip from the images package that contains boot, system and recovery?
Sent from my Nexus 4 using xda app-developers app

Remcotjuuh said:
Then I'm getting to a dead end here too. I guess you have tried flashing the bootloader too? And how about using the "flash-all.bat" in the factory images package?
Edit:
Maybe sideloading the zip from the images package that contains boot, system and recovery?
Click to expand...
Click to collapse
I'm pretty sure that I've tried flashing the bootloader. When I try again (using adb sideload) I get the same signature verification failed message on the N7 that I did when attempting to sideload recovery images. I then get failed to mount cache messages.
I tried the flash-all.bat. Unfortunately that requires fastboot mode and the tablet won't go into fastboot mode. The batch file just sits waiting for the device to respond. Manually typing fastboot devices fails to list anything.
The only "response" that I seem to be able to get is when I put the tablet into sideload mode. I can type adb devices from a command prompt and get a reply with the serial number. The only other adb command that responds is adb sideload - which always reports signature failed on the tablet. Do you think this is a hardware issue?

awhite2600 said:
I'm pretty sure that I've tried flashing the bootloader. When I try again (using adb sideload) I get the same signature verification failed message on the N7 that I did when attempting to sideload recovery images. I then get failed to mount cache messages.
I tried the flash-all.bat. Unfortunately that requires fastboot mode and the tablet won't go into fastboot mode. The batch file just sits waiting for the device to respond. Manually typing fastboot devices fails to list anything.
The only "response" that I seem to be able to get is when I put the tablet into sideload mode. I can type adb devices from a command prompt and get a reply with the serial number. The only other adb command that responds is adb sideload - which always reports signature failed on the tablet. Do you think this is a hardware issue?
Click to expand...
Click to collapse
I have no idea whether this is a hardware issue, could be, could not be. I remember a thread in which someone had a similar problem, only he had only access to fastboot mode. He eventually fixed it by running the flash-all.bat dozens of times, very strange. So how about sideloading the zip containing boot, recovery and system? I haven't read you tried that. And how about adb pushing flashable zip to your device and flash them in recovery? You can try all kinds of zip, ROMs, recoveries. They do need to be signed because you only have access to the stock recovery I guess.

Remcotjuuh said:
I have no idea whether this is a hardware issue, could be, could not be. I remember a thread in which someone had a similar problem, only he had only access to fastboot mode. He eventually fixed it by running the flash-all.bat dozens of times, very strange. So how about sideloading the zip containing boot, recovery and system? I haven't read you tried that. And how about adb pushing flashable zip to your device and flash them in recovery? You can try all kinds of zip, ROMs, recoveries. They do need to be signed because you only have access to the stock recovery I guess.
Click to expand...
Click to collapse
I've tried sideloading the full factory image. That contains all of the boot, recovery and system images. Just like every other sideload that I've tried the file transfers from the PC. The tablet then reports that the signature verification fails. I've downloaded the factory image three times. I've done FC (file compare) from a command prompt and confirmed that none of the downloads are corrupt - they all match each other.
EDIT: I can't push a flashable zip as I can only adb sideload. I can't adb to just transfer a file. I also can't get into the recovery menu so I can't select a file to flash.
I agree that this is very strange. I've tried Googling the various "can't open / mount cache" message that I keep getting. I can't find anything about them. So this may be a very uncommon issue.
I appreciate your help. I'll keep trying different things. If anyone can think of anything else to try I would appreciate any advice. :fingers-crossed:

awhite2600 said:
I've tried sideloading the full factory image. That contains all of the boot, recovery and system images. Just like every other sideload that I've tried the file transfers from the PC. The tablet then reports that the signature verification fails. I've downloaded the factory image three times. I've done FC (file compare) from a command prompt and confirmed that none of the downloads are corrupt - they all match each other.
EDIT: I can't push a flashable zip as I can only adb sideload. I can't adb to just transfer a file. I also can't get into the recovery menu so I can't select a file to flash.
I agree that this is very strange. I've tried Googling the various "can't open / mount cache" message that I keep getting. I can't find anything about them. So this may be a very uncommon issue.
I appreciate your help. I'll keep trying different things. If anyone can think of anything else to try I would appreciate any advice. :fingers-crossed:
Click to expand...
Click to collapse
No problem. Just be persistent and try sideloading, and maybe adb pushing, the different kinds of images/.zips. Maybe you'll be lucky and magically succeed just like the other guy did. I guess this is everything I could advise you. Good luck.

Fastboot is working only when you are in bootloader mode, when you are in recovery or in "normal" operating mode only adb will work. The command is normally located in the sdk/platform-tools directory of the sdk and I suppose you have the latest android SDK installed.
Btw. for me it makes absolutely no sense that the tablet is booting to recovery directly, because the bootloader is loaded and started before, Only from there you are able to go to recovery, i.e. if recovery mode is working, bootloader must work, too.
To recover your system: go to bootloader mode and get fastboot running, then get the system image and extract all files and do the following:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot erase system -w
fastboot flash system system.img
fastboot reboot
this should be sufficient. If you want to be sure you can also do
fastboot reboot recovery
and do a system wipe from there. And after that reboot into your system. Good luck!
@Remcotjuuh: it's better to use fastboot instead of adb, because you are one level below, i.e. if your recovery is not working correctly, adb will fail while fastboot does not depend on a working adb process.

AndDiSa said:
and do a system wipe from there. And after that reboot into your system. Good luck!
@Remcotjuuh: it's better to use fastboot instead of adb, because you are one level below, i.e. if your recovery is not working correctly, adb will fail while fastboot does not depend on a working adb process.
Click to expand...
Click to collapse
I know, but he has clearly said multiple times that he cannot access the bootloader, although I find this very strange too...

Sony xperia s bricked
Remcotjuuh said:
So you can still access the recovery menu? That surely means that your tablet isn't bricked and if you can access the recovery, then you too must be able to access the bootloader. Power off your tablet and try to boot into fastboot by using power and volume -, volume + isn't necessary. Are you sure you have also installed the drivers for fastboot mode? Then try to flash the factory images using the guide here
http://forum.xda-developers.com/showthread.php?t=1907796
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
i'm experiencing a similar problem with my phone. i rooted my phone today (using http://forum.xda-developers.com/showthread.php?t=2327473) and it was running fine, but i installed an application from the play store called [Root] Developer tools to allow me to load up recovery boot. i gave it permission but when i tried turning my phone on it just stays blank. ive tried the hard reset (up+power button) but all that happens is my phone vibrates 3 times and a green light flashes. please help

Cannot flash TWRP. Stock recovery is persistent

Hi,
In order to update my phone to oxygenOS 2.2. I flashed oxygenOS 2.1.1 full rom and installed the OTA update for 2.2. Because of this the phone switched back to stock recovery. So I tried to install TWRP recovery through fastboot. The installation was successful but after reboot, it looks like the phone is keep switching back to stock recovery. I have tried this many times but same result everytime.
Note1: I did turned on the USB debugging before this.
Note2: Bootloader is unlocked.
Any help would be great. Thanks in advance!!

When TWRP asks you to modify system partition give it permission to do so at the start of booting to recovery

Akhil701 said:
When TWRP asks you to modify system partition give it permission to do so at the start of booting to recovery
Click to expand...
Click to collapse
The problem is that I dont see TWRP even once after flashing it. After flashing when I reboot to recovery, it directly shows me default recovery. When I said its switching back to stock recovery, because the flashing of twrp was successful, I am assuming that it is switching back to stock recovery.

Dreckk said:
The problem is that I dont see TWRP even once after flashing it. After flashing when I reboot to recovery, it directly shows me default recovery. When I said its switching back to stock recovery, because the flashing of twrp was successful, I am assuming that it is switching back to stock recovery.
Click to expand...
Click to collapse
I also experienced this the first time. But I just ran fastboot flash recover openrecover-twrp-2.8.7.0.img one more time and then rebooted the phone and pressed volume down until it entered TWRP.

pitrus- said:
I also experienced this the first time. But I just ran fastboot flash recover openrecover-twrp-2.8.7.0.img one more time and then rebooted the phone and pressed volume down until it entered TWRP.
Click to expand...
Click to collapse
Did that many times, but it keeps getting entering in the default recovery.

What happens when you boot twrp with fastboot instead of flashing?
Also probably shouldn't flash an ota 2 versions different than the full. If that was the full version you already had, should have flashed 2.1.2 ota then the 2.2.0 ota.

I'm having the same issue. I was able to boot into TWRP once from Fastboot, flashed SuperSU it said it was successful, then I rebooted. Root was not available, and stock recovery was back.

Chris_el said:
I'm having the same issue. I was able to boot into TWRP once from Fastboot, flashed SuperSU it said it was successful, then I rebooted. Root was not available, and stock recovery was back.
Click to expand...
Click to collapse
Don't know if will work... but boot to twrp from fastboot then flash twrp from within twrp.

khaos64 said:
Don't know if will work... but boot to twrp from fastboot then flash twrp from within twrp.
Click to expand...
Click to collapse
Hmm i'll give that a shot when I get home from work. Thanks.

Chris_el said:
Hmm i'll give that a shot when I get home from work. Thanks.
Click to expand...
Click to collapse
fastboot boot /path/to/twrp
then Swipe to allow modifications!

Yash98 said:
fastboot boot /path/to/twrp
then Swipe to allow modifications!
Click to expand...
Click to collapse
I get the error "FAILED remote: dtb not found'

Remove device encryption

Hi everybody, i would like to remove the devices encription under Security-Encryption
Under Encrypt device i've got Encrypted.
I've tried to restore to factory default, from recovery, from fastboot using format userdata, but, no way.
How i can remove the encryption?
My device is ZE552KL
Thanks

swet90 said:
Hi everybody, i would like to remove the devices encription under Security-Encryption
Under Encrypt device i've got Encrypted.
I've tried to restore to factory default, from recovery, from fastboot using format userdata, but, no way.
How i can remove the encryption?
My device is ZE552KL
Thanks
Click to expand...
Click to collapse
I had a same issue with this device, but I had some experiment.
If your device is unlocked, you can flash TWRP, boot to recovery, wipe, format data.
Backup your data first! It will erase all of your data (Very noob answer)
Totally careful, don't do this if you didn't want a unexpected things. Or something...

The ASUS Zenfone 3 comes shipped encrypted by default. This is required by Google's Play Services agreement for phone OEMs. You cannot remove decryption on the Zenfone 3 without using a custom ROM.

sensi277 said:
The ASUS Zenfone 3 comes shipped encrypted by default. This is required by Google's Play Services agreement for phone OEMs. You cannot remove decryption on the Zenfone 3 without using a custom ROM.
Click to expand...
Click to collapse
Thanks!

TWRP isn't allowing me to Mount my Storage because it's asking for a password I don't know.

ZeldaLinkAaron said:
TWRP isn't allowing me to Mount my Storage because it's asking for a password I don't know.
Click to expand...
Click to collapse
I'm having the same issue. I just got my daughter this phone (the 552KL?), downloaded the official Asus bootloader unlocker APK and ran it, then rebooted to the bootloader to flash TWRP.
TWRP installed, but wants a password to unlock it. Before the bootloader unlock, I did put her Google account on the phone, but the tool said it would completely wipe the phone. Either way, I tried her google account password, but it just says wrong password. Same thing when I tried to boot to system.
Any tips?

@Flapjack
Format through twrp

wang1chung said:
@Flapjack
Format through twrp
Click to expand...
Click to collapse
That's what I ended up doing. I got some help on another thread. The problem I'm having now is that I can't format /cache. It's really weird. If I do a full wipe on the phone, it says it can't format it. I even tried formatting it through fastboot ("fastboot erase cache" then "fastboot format cache"), which says "OKAY finished", but doesn't fix the issue when trying to wipe cache inside of TWRP.
This phone is flat out weird compared to other phones. I don't get the bootloader unlock screen. It doesn't seem to want to boot system... it just keeps going to TWRP. On the few times I have gotten to boot into system (after flashing Carbon 6.1 unofficial), it ends up hanging on a blank screen. Windows makes a sound that a new device is connected, so I'm guessing it's connecting in EDL mode or something (no devices show with a "fastboot devices" or a "adb devices").
I really don't know where to go from here. I'm used to working with Axons, Motorolas, and OnePlus phones. They just work.

@Flapjack
The cache issue is a glitch with the build of twrp, it's not a big deal. There's a workaround posted somewhere, can't remember. Just use the file browser and delete the files on it. I think there's only one file that isn't 0 bytes.
Have you flashed magisk?
Sometimes a full wipe (system/data) and then flashing the raw firmware helps. Try magisk first.

wang1chung said:
@Flapjack
The cache issue is a glitch with the build of twrp, it's not a big deal. There's a workaround posted somewhere, can't remember. Just use the file browser and delete the files on it. I think there's only one file that isn't 0 bytes.
Click to expand...
Click to collapse
So you're saying it doesn't need to be actually wiped, I just need to go into cache and delete all the files in there? How about getting it to boot to system? It just keeps booting to recovery. Not sure when it started that, as after the first time I flashed the ROM, I was able to get it to boot to system by pressing the power button when the "bootloader unlocked" screen came up. That isn't working now.
Have you flashed magisk?
Sometimes a full wipe (system/data) and then flashing the raw firmware helps. Try magisk first.
Click to expand...
Click to collapse
For my first non-stock ROM flash, I flashed the Oreo modem, Carbon 6.1 unofficial ROM, ARM64 Gapps nano, and Magisk 16.0... all at once. I tried booting and it looked like it was setting up... but as I mentioned, it just went to a blank screen. After trying a full wipe and seeing the "couldn't wipe cache" message, I figured that was why.
How will flashing Magisk help me with wiping the cache partition or getting the thing to boot right? Sorry for my ignorance.

Flapjack said:
So you're saying it doesn't need to be actually wiped, I just need to go into cache and delete all the files in there?
Click to expand...
Click to collapse
wiping/formatting cache is the same as deleting all the files. Wiping is easier but as I said, doesn't work at the moment.
Flapjack said:
How will flashing Magisk help me with wiping the cache partition or getting the thing to boot right? Sorry for my ignorance.
Click to expand...
Click to collapse
magisk won't help with cache, but it will remove the verity flag that is tripped from having twrp. From my experience, if I don't flash magisk, it'll bootloop.

Yeah.... absolutely nothing I do will get it to boot to system now. I've flashed the ROM and Magisk, but no matter what, it keeps booting to recovery.
There were two folders under /cache... "Lost&Found" and "recovery". I deleted both, but that didn't help.
---------- Post added 5th July 2018 at 12:40 AM ---------- Previous post was 4th July 2018 at 11:44 PM ----------
wang1chung said:
wiping/formatting cache is the same as deleting all the files. Wiping is easier but as I said, doesn't work at the moment.
Click to expand...
Click to collapse
So I take it I did it right? I would say it's "pretty much" the same. Formatting a partition is different than deleting files/folders in an existing partition. Still, if deleting the files/folders is good enough, then that rules out why the system wouldn't boot after the first ROM install attempt. It would also explain why "fastboot erase cache" seems to work, but TWRP still throws an error. Fastboot erase is probably working just fine.
magisk won't help with cache, but it will remove the verity flag that is tripped from having twrp. From my experience, if I don't flash magisk, it'll bootloop.
Click to expand...
Click to collapse
Is there a custom version of Magisk for this phone? I'm just installing the usual magisk 16.0 zip file you can get on their site, but it doesn't seem to be helping with the phone continuously booting into recovery. Is there a way to remove that verity flag via adb?

@Flapjack
Magisk modifies one of the partitions to get around the flag (I believe), not doable through adb.
Standard magisk off their site is fine
Try this:
Format system/data
Flash custom Rom
Flash magisk
"Wipe" cache and davlik
Reboot
OR
Flash the raw firmware
Flash twrp
Flash whichever custom Rom & gapps where needed
Flash magisk
Factory reset and "Wipe" cache and dalvik
Reboot

wang1chung said:
@Flapjack
Magisk modifies one of the partitions to get around the flag (I believe), not doable through adb.
Standard magisk off their site is fine
Try this:
Format system/data
Flash custom Rom
Flash magisk
"Wipe" cache and davlik
Reboot
Click to expand...
Click to collapse
No go. Still just boots into recovery. Here's what the boot screen looks like (then the Asus logo pops up, then recovery loads)
Code:
< More information :
Dm-Verity in EIO mode
Your device software can't be
checked for corruption. Please
lock the bootloader.
Visit this link on another device:
g.co/ABHg.co/placeholder
Your device will shutdown in 10 seconds
I can press the power button to boot immediately, or wait the 10 seconds... which just boots anyway (doesn't shut down). If I press the volume buttons, I get the following options menu:
Power off
Restart
Recovery
Fastboot
Back to previous page
Flash the raw firmware
Flash twrp
Flash whichever custom Rom & gapps where needed
Flash magisk
Factory reset and "Wipe" cache and dalvik
Reboot
Click to expand...
Click to collapse
I haven't tried this yet. Would this be the best guide to follow?
HOW-TO: Go back to Stock Rom on ZE552KL/ZE520KL
https://forum.xda-developers.com/zenfone-3/how-to/how-to-to-stock-rom-recovery-zenfone-3-t3666223

@Flapjack
That is the correct screen for an unlocked bootloader.
Try this guide for the raw firmware instead, and verify it boots to the OS. Then flash twrp and the rom again.

wang1chung said:
@Flapjack
That is the correct screen for an unlocked bootloader.
Try this guide for the raw firmware instead, and verify it boots to the OS. Then flash twrp and the rom again.
Click to expand...
Click to collapse
Grrr... no matter what I do, it won't flash. The guide says to put it in fastboot mode, but the flash tool won't detect it (even though "fastboot devices" shows it just fine). If I boot it to recovery, it'll show up in the tool, but never actually flashes (see screenshot).

Flapjack said:
Grrr... no matter what I do, it won't flash. The guide says to put it in fastboot mode, but the flash tool won't detect it (even though "fastboot devices" shows it just fine). If I boot it to recovery, it'll show up in the tool, but never actually flashes (see screenshot).
Click to expand...
Click to collapse
This is why I stopped using Windows. Maybe try disabling "driver signature verification"? Swap USB ports? My computer has some high power and low power USB ports, certain devices won't work properly in the low power ones. A couple of guides mentioned unplugging and re-plugging the USB.

wang1chung said:
This is why I stopped using Windows. Maybe try disabling "driver signature verification"? Swap USB ports? My computer has some high power and low power USB ports, certain devices won't work properly in the low power ones. A couple of guides mentioned unplugging and re-plugging the USB.
Click to expand...
Click to collapse
That's a good idea. I'm going through a powered hub right now, but who knows...
I'll try that as soon as I get home.

Ok, different computer. This is my laptop I normally use to flash.
This time, I can get it it to start to flash, but with a second or two, it throws an error (see attached).

Flapjack said:
Ok, different computer. This is my laptop I normally use to flash.
This time, I can get it it to start to flash, but with a second or two, it throws an error (see attached).
Click to expand...
Click to collapse
are you running ASUS flash tool with admin privileges?

A6000 Plus stuck on Bootloader

I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.

If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!

kamesh_kraken said:
I may or may not have TWRP installed. Because, it's stuck on the bootloader when it switches on. I can only get into fastboot. Not more than that. No more Recovery mode. All the tutorials I see online for flashing with QFIL is only for A6000 (not Plus). I have A6000 Plus. What do I have to get it back on the track?
I've searched on other topics about this. But, they're all for A6000. I don't wanna brick more. So, any help would be appreciated.
Click to expand...
Click to collapse
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query

StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
I was like why didn't I try this before.
You know what happened? The boot process on "Command Prompt" screen went fine. I heard the unplugging the device and replugging the device sound very well. But during all these process it stays on Fastboot mode forever.
I have the latest TWRP loaded for temporary boot process. (3.2.1)
Besides from that
I was finally able to flash with QFIL tool. But still stucks at Lenovo POWERED BY android logo. QCom Downloader didn't work. But QFIL tool did work. I was able to finally come over the "sahara error" by quickly clicking "Download" button after connecting the cable. Then it flashed all the files. Then it finished downloading. But then if I try to switch it on, it wouldn't boot. Still stucks at the screen that I mentioned earlier.

StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry!
I tried it with Stock Recovery of A6000 (not plus). It booted into recovery.
Now, I can boot into TWRP. Looks like all the partitions are gone. How do I recover that?

StillrunsKK said:
Most tutorials for A6000 work for the "Plus" variant and vice versa, so it might be worth checking them out.
Also if you had usb debugging on and can send commands to your device from ADB, you can boot into recovery by this command:
fastboot boot recovery xxxx.img
Where "xxxx" is the name of the recovery file which must be in the adb folder.
Feel free to ask if any query
Click to expand...
Click to collapse
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?

kamesh_kraken said:
Sorry for previous post.
I tried to boot with Stock Recovery. It booted to recovery. But then I tried with TWRP again. It worked.
Looks like all the partitions are gone. How do I retain it?
Click to expand...
Click to collapse
Just flash a new ROM

StillrunsKK said:
Just flash a new ROM
Click to expand...
Click to collapse
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.

jameeljb6 said:
If u can enter into fast boot then flash the twrp
U can watch at YouTube about flashing twrp
If u cant flash the twrp or get into the twrp !!!
Then flash the stock ROM ...!!!
Click to expand...
Click to collapse
Haha. I know how to do that. Thing is, I can't boot into System or Recovery normally even if I flash via Fastboot. I can only boot to recovery by "fastboot boot recovery.img" Then in TWRP there, I can't flash any roms as it shows Failed to mount /system /data /cache all the time. Tried fixing with "repair file system" option in TWRP. Still doesn't work.

kamesh_kraken said:
Nope. Doesn't work. Tried that too. Ends up with Error 7 and Error 6. Modified Updater Scripts. Still same problem. Shows Failed to mount /system /data /cache.
Click to expand...
Click to collapse
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?

StillrunsKK said:
What os version were you previously upon? what TWRP version are you using?
Which ROM are you trying to flash?
Click to expand...
Click to collapse
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5

kamesh_kraken said:
This one had 5.0.2. The latest stock ROM provided by Lenovo. I used both 3.2.1-0 and 3.1.0 both seems to provide same "Failed to mount /system /data /cache" error. Even stock recovery shows that.
Trying to flash RR 5.8.5
Click to expand...
Click to collapse
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)

StillrunsKK said:
Use the TWRP provided in the RR thread.
Wipe everything except MicroSD, if it shows any error while wiping, repair the partition in which the error arises and then wipe. After that flash the HEX firmware in RR thread and then flash ROM.
(Side Question : how did you land up in this situation?)
Click to expand...
Click to collapse
The TWRP I mentioned 3.1.0 was obtained from RR forum only where dev mentions "F2FS" support. It does show the same error that I mentioned earlier. I did repair, resize, format, change file system. What ever I do, I always get the mount error on 3 partitions. Can't flash any ROMs either. Shows that error 7 and 6. I even deleted the assert line. It would only land me on error 6. I even googled and tried to get rid of that error. But after the error 6 or 7, it shows the same "mount failed".
Not my device. One of my client's. Received as not working.

Mi A1 Hard Brick

Hi, friends please help me
My phone is dead, I am trying to flash via miflash tool. It takes more than 4000 seconds, it's stuck in userdata.img flashing,I disconnected USB from my pc. Now it's booted in Mi logo and it's shows erasing

Wait till erasing logo vanishes , try to boot into fastboot mode and then reflash the IMG i.e stock ROM if logo doesn't erases , try to force the rebooting into fastboot mode

Custom rom 243 said:
Wait till erasing logo vanishes , try to boot into fastboot mode and then reflash the IMG i.e stock ROM if logo doesn't erases , try to force the rebooting into fastboot mode
Click to expand...
Click to collapse
Trying to flash via miflash tool, it take time more than 4500 seconds

fasilpoochengal said:
Trying to flash via miflash tool, it take time more than 4500 seconds
Click to expand...
Click to collapse
Stuck in userdata.img flashing
What do, Plz help

fasilpoochengal said:
Stuck in userdata.img flashing
What do, Plz help
Click to expand...
Click to collapse

fasilpoochengal said:
Click to expand...
Click to collapse
Go into EDL mode from Fastboot using command:
Code:
fastboot oem edl
Then flash stock ROM from there using Mi Flash and choose Clean all and Lock option
If by any chance your bootloader is locked because of flashing stock rom before, please unlock your bootloader as it works only on unlocked bootloaders.
Warning: This will erase all your data.

Try selecting clean all and lock option located at bottom of the mi flash tool . But data will be lost . Period

I had that problem too once. Definitely unlock your OEM via fastboot command:
Code:
fastboot oem unlock
And try again. If no result fastboot boot TWRP by Deadman
Code:
fastboot boot „name of the TWRP” .img
and go to wipe»advanced wipe»select all beside otg and USB (system, dalvik, cache, internal storage) and try again. If no result either do the same but flash some custom ROM following the guide on the ROM's thread and stay on it or try again.
If nothing helped just go to service center they will do it sometimes even that same day.
If I've helped, please press that "Thanks" button!
Best regards

The tool is changing the device name after the first reboot it makes, you only have to close the tool, re open it and then start the process again.

fasilpoochengal said:
Click to expand...
Click to collapse
just update/repair usb driver or try with other pc

DaveCZ said:
I had that problem too once. Definitely unlock your OEM via fastboot command:
And try again. If no result fastboot boot TWRP by Deadman and go to wipe»advanced wipe»select all beside otg and USB (system, dalvik, cache, internal storage) and try again. If no result either do the same but flash some custom ROM following the guide on the ROM's thread and stay on it or try again.
If nothing helped just go to service center they will do it sometimes even that same day.
If I've helped, please press that "Thanks" button!
Best regards
Click to expand...
Click to collapse
Unable to mount storage

fasilpoochengal said:
Unable to mount storage
Click to expand...
Click to collapse
:crying:

fasilpoochengal said:
:crying:
Click to expand...
Click to collapse
Unable to mount storage

fasilpoochengal said:
Unable to mount storage
Click to expand...
Click to collapse
Then use the option next to advanced wipe. Ignore any errors it may give you as long as there is "success" on top of the screen! Then proceeded to installation of the ROM. Also remember to after the wipe and any flash reboot to bootloader and boot TWRP again. The process is anoying but it may fix your problem.