Hi guys
So I was doing some tinkering with my phone and tried to extend the system partition using the guides I found for my phone, and they all went off successfully according to the logs. However, upon rebooting I'm greeted with an "android is locked screen" and even when I enter my correct password and it accepts it, it reboots and goes back to that screen. The recovery (TWRP) and fastboot are still operational and I can quite easily get into them.
In TWRP is says the /data partition is not present. And every attempt at mounting them simply fails. But, when I try and restore the partition table using MiFlash, after getting the correct rom and everything, MiFlash tool simply does not detect my phone, no matter what I do.
I've tried searching this forum to see if there are any solutions, but since I can't seem to find any, please guide me if possible and point me in the correct direction should there be something which I should be looking at.
Please help me urgently
Related
Hey guys I need some help. I'm usually able to find answers to all my problems because they've already been answered, but for once, I'm stumped.
I can't seem to get my One S out of CWM recovery. Every time I try to reboot, the screen will flash briefly a couple times, and will come right back to cwm. I can't access the bootloader screen, and cant mount my sd card (error given is: "Unable to open ums lunfile (No such file or directory"). I think I may have caused this by not first flashing boot.img via fastboot before flashing trickdroid. I followed all steps to root without a problem.
I'm not quite sure what else to try at this point. Since I can't access bootloader screen, I can't use fastboot. I can adb push files to my device, though.
Any help/suggestions you may be able to provide would be greatly appreciated. Thanks in advance.
UPDATE: After what seemed like the 100th time I tried to restart the device, it finally booted normally. Not sure what caused it, but the device works fine now.
Hello,
I have a Nexus S that was encrypted because one of the Exchange servers I connect to requires it.
The unit has since failed to boot into CM9. It enters into the "Google" start screen, flashes once, and stays at the "Google" start screen with the soft buttons activated. I assume this is what is called "soft bricked". Recovery still works, and so does Download mode.
Mounting from recovery has failed. I've tried CWM and TWRP, but neither can mount, nor can they format the SD card. I've attempted load stock rom through flashboot, but of course that fails because it doesn't have access to the SDcard.
Attempting to mount Internal SDCard and Data through TWRP as hinted in Cyanogen forums have failed as well.
I can't seem to find Odin files for Nexus S either. I may be wrong, but there might not be Odin files for the vanilla non-4G Nexus S.
Can someone offer advice on what to try next?
Bumping back up. Has anyone tried to restore an encrypted device that isn't booting past the Google screen?
amadaeus said:
Bumping back up. Has anyone tried to restore an encrypted device that isn't booting past the Google screen?
Click to expand...
Click to collapse
I have the same problem. Can't do anything with my phone since it can't mount the internal sd... I'm currently searching for the files to restore the phone, so if I find anything, I'll post it here.
Hello Everyone,
I have searched this forum and followed many useful threads which seemed related to my issue, alas none have actually been able to fix my phone.
I am using a stock ROM which upgraded to marshmallow not too long ago. The other day my phone rebooted for no reason got it's self into a boot loop. Since them I have tried the following:
1) I have used recovery mode and cleared the cache/performed a factory reset. I just the get the can't mount/cache line pop up.
2) Tried to use ADB to boot an image over the USB but couldn't get much from this (so I may have missed something with this).
3) Tried to use fastboot to move flash back to a version of marshmallow downloaded. When I go to flash files in I get failed messages on command prompt. (Failed, remote flash write error).
additional info
1) the device was encrypted from the settings menu when functional.
Any advice or help would be good at this point. Let me know if additional information is needed.
Thanks!
Hi, I've made a couple posts about this in both the One M9 and Sprint One M9 forums seeking some help with this phone that signs point to not being a lost cause but I myself am very lost. Neither of those forums seem particularly active at this point in the phone's lifespan so I decided to try posting here. I'll explain what happened and how the phone is behaving and refusing, despite my best efforts, to go back to normal.
I had my Sprint M9 rooted, unlocked, S-Off running Leedroid with TWRP. Last Tuesday, some sort of cascading failure happened causing google services to crash, everything else started crashing and I kept getting crash notifications over and over so I eventually rebooted the device. However, it didn't boot. I eventually got into TWRP, probably jumped the gun on wiping data and system after wiping cache failed to yield any results, but I had a rom on my sd card so I figured I'd just reflash because it was obvious there was something seriously wrong. I couldn't get into download mode.
Cut to now. I have bootloader access, I have TWRP access, none of the main partitions will mount in TWRP (invalid argument). I didn't have any encryption on these partitions but I get the error "Unable to find crypto footer". The solution I see most often touted for the mounting issues is to "Format Data" in TWRP but oddly, I type "yes", I swipe, and I'm met with the exact same errors. This is where it gets weird. As I mentioned, I'm S-Off and unlocked. You'd think I could flash hosd via fastboot, head to download mode and just get a clean RUU install going. And it looks like I can do that, the command line messages I get from fastboot flashing are "OKAY", not "FAILED", and yet, nothing actually flashes! I confirmed this via trying to flash the stock recovery over the TWRP image via fastboot, then booting recovery and still finding TWRP. I'm VERY confused about all of this.
I've seen some info in my searches that indicates some of this stuff can happen if your emmc is faulty (hardware failure), but I've pulled the dmesg log and can't find any errors that would be indicative of emmc failure. Anyone have any idea where to go next? Because I'm stumped.
I've attached a recovery.log and dmesg if anyone wants to take a look. Any suggestions would be greatly appreciated because I'm frankly out of ideas.
If I'd prefer not to purchase a new phone, is there much risk a rootkit is installed? Or, is this certainly random device corruption that doesn't seem to be harming anything?
Is there anything I can do to fix the problem? (Yes, I could turn dm-verity off through adb, but that hides the error without fixing it.)
TL;DR
I have an Asus Zenfone V Verizon edition, which is the V520KL A006.
When I was using my phone a few days ago, it suddenly rebooted and since then shows:
Your device is corrupt. It can't be
trusted and may not work properly.
Visit this link on another device:
g.co/ABH
If power key is not pressed:
Your device will poweroff in 30 seconds
Click to expand...
Click to collapse
Fastboot shows:
TARGET PROJECT : V520KL
IMAGE VERSION : V5.6.0
BUILD VARIANT : USER
SECURE BOOT : enabled
DEVICE STATE : locked
Software status : Official
Click to expand...
Click to collapse
After a few days, I finally tried the power button, and it boots up just fine, and seems perfectly stable. I performed complete backups, and for what it's worth, I ran a bunch of droid virus/malware/rootkit scanners, and they found nothing. (Obviously, a good rootkit will hide itself.)
I eventually did a factory reset. This went well, but the red error message remains. So, I believe the corruption must be in a partition that a reset doesn't replace.
MORE DETAILS
I've never unlocked, rooted, or installed a custom ROM onto this phone. The only "beyond typical user" thing I'd previously done is to install adb sourced directly from Google, to be able to run Genymobile's scrcpy, which is an extremely fast open source program that allows me to remotely control my phone from my linux PC, via USB or wireless. I've been using this for many months without any issues.
This appears to mean dm-verity is detecting corruption, and is the "red" version of it which many have described as the death of their device. I believe this means the phone is able to verify the signature on the bootloader and it's able to verify the signature on the kernel, but that the kernel is finding an invalid block(s) on one of the many partitions being read right at turning on (detected because the hash for the block is not as expected.) When this happens, an I/O error is given indicating the block cannot be read.
I have been quite concerned if this might indicate a rootkit had been installed. I haven't done anything that I would suspect could let one in. After spending a lot of time learning about adb, fastboot, TWRP, and having the ultimate goal of discovering which partition has an unexpected hash, determining if this meant a rootkit or file corruption, and fixing the error, I've hit many brick walls.
For a day or two, I avoided seeing if the power button would allow it to boot, because if there was a rootkit, I didn't want it to run. I was disappointed to learn that through fastboot (specifically, I mean the fastboot PC program that connects to the droid when in fastboot mode), there is no way to do something like a full bitwise image of the internal storage, and analyze the situation in linux. Or, any type of backup whatsoever. I was frustrated to learn from another XDA thread about a lot of problems others have had rooting and/or installing TWRP on this device. I was frustrated to see there is no prebuilt version of TWRP for my device. (There is an image for the Asus ZenFone 5z 2018 ZS620KL which is very different than my Zenfone V520KL V.)
I realized with my particular device, I think, the only way I was going to take any next step required hitting the power button. (As I mentioned way above, that's when I found it appears to work fine, and I eventually did a factory reset.)
I attempted using the TWRP recovery.img posted by game #1 in that XDA thread about my device, but like he encountered, fastboot boot recovery.img doesn't work, and just reboots instead.
Without being able to extract the original recovery.img, I'm not sure that I'm willing to install his and see if it works for me. I was frustrated to find there appears to be no way to extract the original recovery.img without first having root access. All non-root methods I later found to do this didn't work. Notably, su can't run anymore through adb, and adb root can't run with a user build.
I've looked a bit at custom compiling TWRP myself, but haven't done that yet. In part, because if my version doesn't work through fastboot boot recovery.img, I'd have the same concern about overwriting the original one before getting some feedback here. Also in part, because I haven't looked enough to find how someone goes about making a BoardConfig.mk and the device tree from scratch.
Hey. I tried installing TRWP on my device, Asus Zenfone 5Z (ZS620KL) but I also got the same message. "This phone is corrupted and cannot be trusted." It also said it won't boot. Now I am stuck in Fastboot mode.
I tried installing a stock rom. Downloaded the firmware. i even downloaded python so I can extract the payload.bin file. Followed the steps but still to no avail.
Is there anyone who could help me?
If you could attach the files that I would be needing, that would be a great help.
Thanks.