I'll start off with an apology, as well as a thank you to anyone willing to read this
Google Pixel XL: bootloader has been successfully unlocked and I had TWRP installed successfully at one point but I wiped data/factory reset from Android Recovery as an attempt to get any where beyond this only to make things worse. I've downloaded factory images, OTA, etc and tried a few different commands with ADB but only get the return error message "error: device '(null)' not found"; I think that started occurring after updating 'latest_usb_drivers_windows'. Even tried uninstalling those drivers and re-installing, no luck but it's possible I messed something else up at some point.
Sorry for the lack of information, I'll be happy to provide any pertinent information if anyone is free to assist. First rooted device was a Nexus 6P and that went well and instantly fell in love, probably shouldn't have attempted the systemless root method this early in my career lol.
P.s. I did look through some forums and there were some similar but I haven't been able to replicate any of those with success; there may not be hope for me after all.
Update: I was somehow able to get back into TWRP, but when I attempt to install a recovery image I get the following error message: "Failed to mount '/vendor' (Invalid argument). Maybe now that I'm back in TWRP someone has some ideas?
Update: I'm back in, this can be closed.
Related
So I sent in a request for a replacement phone because my vibration motor stopped working. The replacement phone I received basically does not work, I have done several factory resets and flashed the factory image I downloaded from google. This phone has multiple system app crashes right at the initial welcome screen. Most of the Gapps crash constantly, and the initial updates to these apps fails. It sometimes boots up and barely works for a few hours, and one of these times I got a notification about the 4.4.2 update. I tried installing this update and had an error which said "E:failed to verify whole-file signature". When I try to manually update the device to 4.4.1, I get the same error. I also get these errors during factory resets.
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Click to expand...
Click to collapse
So it seems like the /cache/ partition is messed up, or there is some kind of hardware issue. I'm afraid to unlock the bootloader and try any of the other recoveries and end up bricking it, unless there is a sure-fire way to fix it that I can understand.
The phone with the vibrator motor issue is currently my only phone and I do not want to send it back to google and keep the broken replacement. I called customer support and they say that I must send the original phone back and keep the replacement phone. This really pisses me off because I called CS before I even placed the RMA request to find out whether I would be obligated to accept a replacement phone that might be defective as well. They told me that the phones are inspected and defects are so rare that I probably wouldn't get two defective phones. Obviously defects are NOT rare. What can I do?
I'm fairly certain you need to be unlocked to flash anything through fastboot including factory images.
Following this guide exactly should help you out... http://forum.xda-developers.com/showthread.php?t=2513701
I would definitely unlock the bootloader and then root it and flash a ROM to it.
I recommend:
Guide: http://forum.xda-developers.com/showthread.php?t=2507905
Or
Toolkit (some people are not fans of them but I am): http://forum.xda-developers.com/showthread.php?t=2525026
ROM: http://forum.xda-developers.com/showthread.php?t=2557523
Let us know how it goes
Edit: after re-reading your post if it has a vibration motor issue I would RMA it and Not unlock the bootloader if it is your only phone ask around for a cheap throw-away phone from a friend or something until you can get a new Nexus 5
mistahseller said:
I would definitely unlock the bootloader and then root it and flash a ROM to it.
I recommend:
Guide: http://forum.xda-developers.com/showthread.php?t=2507905
Or
Toolkit (some people are not fans of them but I am): http://forum.xda-developers.com/showthread.php?t=2525026
ROM: http://forum.xda-developers.com/showthread.php?t=2557523
Let us know how it goes
Edit: after re-reading your post if it has a vibration motor issue I would RMA it and Not unlock the bootloader if it is your only phone ask around for a cheap throw-away phone from a friend or something until you can get a new Nexus 5
Click to expand...
Click to collapse
Well I have 2 nexus 5's right now. I have the original one that works fine except for the motor, and this new one that does not work. Google says I must send back the original phone with the vibration issue and keep the broken phone. I'd really like to just fix this one with issues if it's at all possible. I'm at a loss in determining what exactly is wrong with it though.
This is the error I am most concerned with:
E: failed to mount /cache (Invalid argument)
This happens when I try to format cache in stock recovery mode, I also sometimes see a string of other /cache/ related errors. I think that the cache partition is somehow screwed up and is causing all my other issues.
edit: I am going to try flashing the stock image with this skipsoft toolkit. I've unlocked the bootloader. I feel like there has to be some way to fix this phone.
I can see Google's point, you have two nexus 5's. They will charge you for two nexus 5 unless you send the one back which makes sense.
cwd said:
Well I have 2 nexus 5's right now. I have the original one that works fine except for the motor, and this new one that does not work. Google says I must send back the original phone with the vibration issue and keep the broken phone. I'd really like to just fix this one with issues if it's at all possible. I'm at a loss in determining what exactly is wrong with it though.
This is the error I am most concerned with:
E: failed to mount /cache (Invalid argument)
This happens when I try to format cache in stock recovery mode, I also sometimes see a string of other /cache/ related errors. I think that the cache partition is somehow screwed up and is causing all my other issues.
edit: I am going to try flashing the stock image with this skipsoft toolkit. I've unlocked the bootloader. I feel like there has to be some way to fix this phone.
Click to expand...
Click to collapse
Flashing a factory image with skipsoft did not fix the issue. Nor did installing TWRP and flashing beanstalk rom.
mistahseller said:
I can see Google's point, you have two nexus 5's. They will charge you for two nexus 5 unless you send the one back which makes sense.
Click to expand...
Click to collapse
Right, I definitely am sending one of them back, but I certainly do not want to send them the one that works. What kind of ****ty RMA program replaces your device with one that is MORE BROKEN?
I would send the other one back, and then this one as well after that one is processed. That is ridiculous that it came from the factory and took a dump on itself before you could even break it (haha). If you aren't satisfied get the g2 potentially unless you are set on the nexus 5 (I would be) or another phone but it would break my trust with them. Apparently I was one of the lucky ones that did not get a defective Nexus.
Yea this does suck. Though you're only another RMA from potentially having a good one. If not return them both and pick up a Moto G for $200 if you're in the US.
I managed to fix it somehow. Between several factor image restores and about 20 factory resets it now seems to be working correctly.
edit: nope, not fixed. still can't install my update.
e:failed to verify whole-file signature
My friend gave me his bricked Xoom, which I accepted as a challenge, because I've been rooting and flashing my phones for years, but after 10+ hours of searching in the last couple weeks, I have been unable to locate coherent information on how to un-brick a Xoom that has had its internal storage wiped. My friend was trying to do a thorough wipe, and he succeeded in that, if nothing else.
My first obstacle was finding a driver, because Motorola Device Manager wants nothing to do with the Xoom, and whenever I finally found a link to a driver, it was at developer.motorola.com, and there apparently is no such domain, because every link takes me straight to motorola.com/us/home, where all that's waiting for me is the bloody Moto Device Manager.
The only post I found that seemed like it was aiming at where I want to get is at http://forum.xda-developers.com/showthread.php?t=2317986, but I ran into problems that weren't foreseen by the author, and I haven't been able to find anything pertinent that doesn't direct me to developer.motorola.com again.
The Xoom has TWRP v.2.6.3.0(runandhide05 edition) for a recovery; and I'm aware that there is a 3.3 version, but I'm nervous about flashing a recovery update when there is no OS on the tablet. It was running EOS 4.2.2 I think, before the bricking.
According to the guide I found, I put TWRP into adb sideload and was able to get my PC to communicate by installing a universal adb driver from https://github.com/koush/UniversalAdbDriver, so in my system Device Manager, the Xoom is listed as a GOOGLE GALAXY NEXUS ADB INTERFACE.
When TWRP is in adb sideload, I can interface with the Xoom via cmd.exe, but when I try to push a ROM, I keep getting an error on TWRP:
Code:
file_getprop:failed to stat "/system/build.prop" no such file or directory
...whatever that means. Another thing that kind of worries me is that when I type adb devices, it shows my device as 1234567890ABCDEF, which doesn't seem right.
I have yet to try fastboot, because I don't know what .img files I need to flash, and I don't think blind flashing is going to make things any better.
I think I have all the pieces, SDK and JDK are installed and updated, and I have the stock rom (HWI69.zip). I reckon if I can get the stock 3.x OS running, I'll have a jumping-off point, and be good to go; the process from there is well-documented.
Can anyone give me a nudge in the right direction, please?
~Fake
Status 7 errors
Those are usually caused by either a not-so-compatible recovery image. Some TWRP versions have issues with certain ROMs. I had this happen to me with my Asus TF300, ended up trying a few different TWRP versions before I found one that worked right.
The other cause is an invalid ROM image, if you open the ROM.zip file on your PC, does it look ok, did you check its MD5sum???
Were you able to wipe the Xoom from TWRP without error???
-Mike
When I got it, it had been wiped completely, so I presume that twrp wiped okay.
Not sure about the MD5sum, just that twrp didn't find one during the adb installation. Do you think flashing cwm might help?.
I got it worked out, opened up the HWI69.zip stock image and fastboot flashed the individual .img files, and it booted right up. Thanks!
By the title, you can assume the situation is not very pretty and this poor individual needs some help. You would be correct in your assessment. This was me yesterday, freaking out after the new OTA update crippled my device and made me fear the worst (bricking). As a new Rom developer/flasher, I certainly worry about bricking my device, but have luckily not…yet. I certainly won’t deny the amount of tinkering that I do with my phone and flashing custom Roms, which might have assisted in my near meltdown, however, I thought it may be a good idea to share this experience (issue + solution) with the rest of the community, to hopefully save someone long periods of stress and research.
Note: I am only assuming the OTA is what caused the problem, but this could be incorrect, feel free to correct me.
Key Factors:
Custom Recovery: TWRP
Custom Rom (at the time of meltdown): Google Play Edition
Device: Verizon HTC One m8
OTA update ran.
Decided I wanted to go back to something closer to Sense and noticed that the ViperOne rom was getting some awesome reviews.
Downloaded Rom
Attempted to go into Recovery, but was greeted by the following error message:
HBoot
Model ID incorrect
Update failed
Press power to reboot
Downloaded Flashify and was able to get into recovery.
I knew I would need to deal with this error eventually, but thought maybe flashing the new Rom would assist in that area.
Flashed ViperOne rom, flash failed.
I swiped to unlock and the phone rebooted…
Then the real fun began.
My phone would boot to HTC logo with the read development disclaimer at the bottom:
“This build is for development purposes only. Do not distribute outside of HTC without HTC’s written permission. Failure to comply may lead to legal action.”
I freaked out for a bit, researched a ton and finally began to put the bits and pieces together:
At this screen it is possible to reboot, but then you will just boot into Hboot error, so pretty pointless (from what I know, feel free to chime in If you know of a way to get into recovery/fastboot from here).
I downloaded the latest version of TWRP
While on the HTC One screen, I plugged my phone into the computer and entered: adb devices.
At first, the command yielded no results, but after about 3 minutes, the device was recognized, but offline.
After 4 minutes, the device was recognize and looked to be available.
I then issued the following command:
Adb reboot bootloader
Success! This booted me into the fastboot usb method, which gave me a huge glimpse of hope.
Next, I ran the command to reflash the custom recovery:
Fastboot flash recovery [insert recovery file name here].
I received a successful message flash, however, after a reboot, I experienced the same problem as before.
I attempted to boot into recovery from the menu UI, but the option was not available. The journey continues:
I attempted the steps outlined above and then flashed the TWRP recovery image to boot instead of as recovery:
Fastboot flash boot [insert recovery file name here].
reboot-bootloader
This time, I was able to select “Recovery”, and booted into TWRP.
I then installed the GPE Rom again.
After the GPE rom installed, I rebooted into TWRP and checked to see if my restores were available, and luckily enough they were still in the same place (phew!).
This little article will hopefully help someone, as all the information I found for this issue was scattered throughout the web and I was luckily able to piece it together for my specific issue.
Ultimately, typing the ADB and Fastboot by themselves and reading through the commands in the CMD prompt, helped me figure out the commands needed to be successful in my endevours.
This would have been deeply helpful for me a week and a half ago. I actually bricked my device during the process of S-Off and unlocking the bootloader, after which, my device wouldn't be recognized on my computer (I missed a step in the process). Luckily for me, Verizon gave me an exchange, even though the phone was rooted and the only screen that'd boot up was TWRP. Apparently since I was in the 14-day return window, rooting or unlocking your device doesn't disqualify you from doing an exchange.
The first ROM I flashed after getting the new device and unlocking it was the same Google Play Edition. I had some issues getting in to recovery. I reflashed TWRP and have been fine ever since. I'm thinking it may be a bug in that ROM that causes devices to lose discoverability or for recovery to fail.
Hey there,
I got cocky and tried to enable encryption on my vs980 after successfully installing CM12. It failed for some reason and now I'm more or less bricked. CM12 tries to boot & says my data is inaccessible (ok, whatever), but when I get it to boot into recovery, TWRP 2.8.1.1 asks for my pin to try to decrypt, but can't mount storage.
Can someone please help me out?
I appreciate anyone who's willing to take the time to help me out & I'm willing to return the favor in various ways. Maybe I can paypal a few $ for help to get it running again?
Thank you in advance.
/M
Update: I appear to be able to open an ADB shell to the phone but the su command doesn't give me a # prompt, so, evidently I no longer have root perms. I'm not sure what to do from this point.
Update 2: LGMobile Support Tool finally connected to the dang thing and updated the system image to 4.4.2 and wiped what I assume is the data partition & flashed KitKat on it. I now appear to have a brand new phone. I guess now I have to jump through all the hoops to get back to CM12. lol.
Awesome! Good luck! Thread closed.
OK, been searching for a week, obsessively, to find a fix for this. No luck.
I tried flashing the aosp ROM from official miui v5 through twrp and have been left with this.
1. Bootloader locked, Tamper bit engaged, and running stock recovery with a signature that cannot verify anything. (I mean anything, cannot even reflash the same ROM, factory signed, nothing)
2. What's this? It starts up? It can't be bricked? Oh wait why did it just reboot upon network connection? Right! Persistent has been destroyed/corrupted! Fun stuff.
3. SDD called internal? Sdd gone? Yes, yes it is. Everything has changed which is why I can't DD/ the persistent!!
4. Tried every toolkit (except the mac os one which resets tamper) and been through every internet page ever. Before i embarked upon this mission to unbrick the unbrickable id never heard of a data dump, persistant, or .tar. Now I never want to hear of them again. I have tried everything except the backdoor adb route because the Qualcomm drivers won't install on my 64bit win8.1.
If anyone, anywhere, knows how I can put back to stock, aosp, caulkins, anything, have a heart, help a man!
jpilch said:
OK, been searching for a week, obsessively, to find a fix for this. No luck.
I tried flashing the aosp ROM from official miui v5 through twrp and have been left with this.
1. Bootloader locked, Tamper bit engaged, and running stock recovery with a signature that cannot verify anything. (I mean anything, cannot even reflash the same ROM, factory signed, nothing)
2. What's this? It starts up? It can't be bricked? Oh wait why did it just reboot upon network connection? Right! Persistent has been destroyed/corrupted! Fun stuff.
3. SDD called internal? Sdd gone? Yes, yes it is. Everything has changed which is why I can't DD/ the persistent!!
4. Tried every toolkit (except the mac os one which resets tamper) and been through every internet page ever. Before i embarked upon this mission to unbrick the unbrickable id never heard of a data dump, persistant, or .tar. Now I never want to hear of them again. I have tried everything except the backdoor adb route because the Qualcomm drivers won't install on my 64bit win8.1.
If anyone, anywhere, knows how I can put back to stock, aosp, caulkins, anything, have a heart, help a man!
Click to expand...
Click to collapse
This honestly is very confusing. I had to read what you wrote a couple of times to try and comprehend what the problem is.
Have you tried using fastboot without any toolkit? I ask because you haven't mentioned it anywhere. Persist can be fixed by fastbooting back to pure stock, and Mike's fix on the OnePlus forums, and/or updating to 44S.
Can you tell us what errors you get when you try to reflash the same rom? What recovery are you running? Which rom were you trying to reflash?
I have to agree with @nicholaschum, your post is very vague and confusing in its present form, and I'm a pretty seasoned troubleshooter on XDA.
What's needed? Less emotion, less comic type speech, less sarcasm, more specifics and facts.
Transmitted via Bacon
1328
If I try to sideload, it says either signature failed or whole signature failed.
Anything i push does not get pushed and I have tried multiple drivers from the galaxy ones that come in the reflash.zip from the one plus tech support to the Google ones I am using now.
If I try to fastboot through toolkit it says failed, not unlocked can't flash/erase. If I fastboot through cmd it says error: closed. I do all my checks, and it shows up in fastboot and adb but won't let me send anything.
The phone boots up for about 15 in is before restarting, the only way to get files on are to drop them in explorer within these 15secs, to internal storage, which used to be my sdcard.
I have tried flashing/side loading multiple ROMs from miui, 44s, 33r all signed to caulkins and mahdi. Nothing has worked (and the aosp OTA).
I cannot unlock bootloader, cannot reset tamper, cannot load GUI for more than 15 secs, and cannot root (although kermal already says it is, I suspect su needs to be in place).
I have also tried fastboot -c boot recovery.IMG (and recovery recovery.IMG) but no luck still. Is there a PC version of the Mac toolbox that can reset tamper? At least then I could unlock bootloader and install twrp and flash.
Thanks for the help
Josh
Still sounds like a driver issue imo.
First uninstall ALL previous drivers you have tried from device manager.
Installing one driver after another often causes conflicts.
Then download the official Android SDK and install Google USB driver. Google for instructions if needed but everything is pretty much straight forward.
This driver has the biggest chance of success.
After that you're off to start fixing your phone using fastboot and adb.
OK have done this on both a 32 and 64 bit win 8.1 systems. Exact same result. Error: closed or not unlocked no flash/erase for everything fastboot, and e: can't verify signature/whole-signature e: verification failed. I tried adb explorer through adb sideload and error:closed again. Does this mean the adb protocol for accepting is closed? No idea.
I have a feeling it is something on the phone rather than computer now? Done everything on a 32 bit now and everything is the same and had no drivers previously. And just to be clear when I say stock recovery, I don't mean cwm I mean
android system recovery 3e
KTU84P. 1.2.0 dev-keys
jpilch said:
OK have done this on both a 32 and 64 bit win 8.1 systems. Exact same result. Error: closed or not unlocked no flash/erase for everything fastboot, and e: can't verify signature/whole-signature e: verification failed. I tried adb explorer through adb sideload and error:closed again. Does this mean the adb protocol for accepting is closed? No idea.
I have a feeling it is something on the phone rather than computer now? Done everything on a 32 bit now and everything is the same and had no drivers previously. And just to be clear when I say stock recovery, I don't mean cwm I mean
android system recovery 3e
KTU84P. 1.2.0 dev-keys
Click to expand...
Click to collapse
For the fastboot bit, I've seen this happen a lot. Many people used this to solve their issue: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912