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
Related
Hi, I am new to all of this, but Im a quick learner. I rooted my phone and have superuser permission. I have installed multiple applications that will help me to perform ROM installs all of which still do not help. I even tried the three button solution, however I am still getting the same message when I go into recovery mode. It is as follows: E: failed to varify whole-file signature then under that I get: E: signature verification failed, instalation aborted.
I tried applying sdcard update. zip, wiped out cache partition, factory reset, etc...
I have tried everything. I tried using Mod Manager, I get the downloads but then when i try to install after I make sure to click backup rom and clear cache, it boots to the rom screen, (not really sure what you guys call it, sorry) and I get that same message, the signature failed, et...
my phone info is as follows: SCH-I500, I500 Commercial Package_DL9 To EA28 (I think verizon automaticly updated for the emergency dial) code 200
hardware version i500.04 firmware version 2.1update.1, baseband version S:i500.04 V.EA28, kernel version 2.6.29 and last but not least build number SCH-I500.EA28
Now saying all of that, I tried all of the above steps prior to this automatic update and it still did not work. I still received the signature message.
I even tried Voodoo, as well as DL30, Superclean, none of which will pass the signature autentacation. I want to try to get past this as I am having my phone replaced due to burn in and want to get the steps right so I do not BRICK my phone after it has been replaced. If this one bricks, it wont matter to much because I will have the new one on Monday.
Any help would be greatly appreciated. I love this tecky stuff and want to be knowagable on how to get past this message so I can go full force on Monday.
Thanks,
EssyG
Also I checked the site and tried everything but still won't work.
Sent from my SCH-I500 using XDA App
You will need to flash a new Recovery via ODIN which you can find below for your Samsung Fascinate:
http://forum.xda-developers.com/showthread.php?t=782204
&
Also read this http://forum.xda-developers.com/showthread.php?t=790004
Thank you, up and running 2.2, will post screen latter! Now I need to get my old phone back to stock so I can send it back to veriazon. YOU ARE THE BEST!!
P.S. I love your idea about the 10 post allowence to post on other forums.
Essy G
If o.k. I will post what I did and that way new users will be able to follow directions. I am a newbe but have become addicted to this stuff. THANKS!!
now I bricked my phone... lol
Now let me start by saying I loved 2.2, no problems with it at all. but when battery ran out I wanted to clean stats in cwm green and the screen would not come up, sd would not mount any how I tried to start over, flashing oden, all the steps, but my drivers will not stay for some reason after flashing I need to uninstall the reinstall drivers or they are not recognized, really sucks, any how I got frustrated so while in odin I pulled the plug, lol literally, and now have a pic of a "phone" then ".." then triangle with (like my icon here)"!" then ".." picture of "computer". I called verizon and there sending me yet another phone. lol my question is, will they be able to unlock it and see that I had 2.2 on it? does anyone know what they do with the phones we send back? Basicly I want to know if they can unlock that being I can't. and if so, will they see the 2.2? Any sugestions?
Anyone there?
Any one there? Also I am debating, do I wait for official release. I heard it was coming out 2/22/11. If I put dl30 on new phone again and they release the update, will I still get the automatic update via verizon? If so will I lose root? Any comments on post #5? I can't believe I had it running I totally messed it up. Thank goodness when I called verizon I got two girls at tec support, lol while I am a girl, I am a tech lover, I acted like I had no idea what happened, well they didn't either, lol So just waiting on new phone to come in, yet again so I am getting everything ready to quickly install dl30 to new phone again. Hopefully I do not lose drivers again, as it seems that once I flash in odin, the hardware icon disappers as if drivers are not installed. any how, I was just wondering if anyone had an answer to post #5 so that when I return the phone, I am not caught, lol that would really stink! Plus I am board, took off of work because my kids are sick and now I have a bad cold also, so any comments would be great!! Besides I need to be here to sign for new phone.
Thanks,
Essy g
So I was running the may 5 nscollab for a few days and experienced a lot of reboots, then eventually boot loops or whatever we call the reboot leaving you with backlights on and black screen. I usually pulled the battery and things were fine for a while. I was not over clocking or using bln. The last time, about a week ago, my 9020t couldn't reboot. I was able to get in to recovery, but cwr was unable to mount any partitions but /cache. All wipes failed, and so did permission fix because of this.
Next, I fired up adb. No problem there. Started fastboot and locked then unlocked but the problem remained. So I tried flashing IMgs from a stock recovery. Recovery.img worked fine. System, boot failed after 30 seconds with write errors. I also got an error on the fastboot screen that two addresses were exceeded. I didn't write them down as I don't know that they are important, having googled these.
Next came Odin with a 2.3.1 set of tars for 9020. It hung trying to flash system.img. I tried a few times with the same results.
Last, I checked what was up with adb shell. I found out I can manually mount /dev/block/mmcblk1 as /sdcard and could read and write to it. I pushed a rom zip and flashed it using cwr with no errors, but on reboot I saw it was nothing but the recovery.
Any ideas. It seems the other partitions are not mounting. Can't I just wipe everything and repartition then flash with Odin? I don't know why Odin didn't work. Do I need a pic file for the nexus s? Bah! It is frustrating that a brick is not a brick.
Really, any ideas? Sucks to have a 600 dollar phone that spontaneously combusted like this.
it seems i am missing /dev/block/platform/s3c-sdhci.0/by-name/system
and /dev/block/platform/s3c-sdhci.0/by-name/userdata
so they wont mount. Also, the mtdblock files in /dev/block aren't even listed in fstab. is there any way i can wipe this base system? Odin won't do it. Nothing I have tried can overwrite whatever is royally messed up in the filesystem. It seems that even for any recovery to work properly, the mounts must be correct!!!!
Unfortunately, sometimes as a brick is a brick. I have similar symtoms as you - I cannot mount /system and cannot get past the google splash screen. I cannot write or read to storage.
http://forum.xda-developers.com/showthread.php?t=993403
I've already called Samsung to send the phone in, just lagging putting it in the mail. I've been using my g1 for past couple of weeks.
irishrally said:
Unfortunately, sometimes as a brick is a brick. I have similar symtoms as you - I cannot mount /system and cannot get past the google splash screen. I cannot write or read to storage.
http://forum.xda-developers.com/showthread.php?t=993403
I've already called Samsung to send the phone in, just lagging putting it in the mail. I've been using my g1 for past couple of weeks.
Click to expand...
Click to collapse
Thank goodness for my g1 also!
What did they say to you? I do not like the idea of having to pay. Bah!
PM's sent to both of you. I can fix this issue with JTAG...
Samsung didn't say much, just send it in. I'm hoping it won't cost anything but if it does I may consider the jtag services mentioned above.
connexion2005 said:
PM's sent to both of you. I can fix this issue with JTAG...
Click to expand...
Click to collapse
How much for the instructions to do this? We have a device at work that the EEs use to jtag TI micro-controllers. Not sure if that would work. If Samsung gets all crazy and tries to charge me ridiculous amounts of money I may go your route.
irishrally said:
Samsung didn't say much, just send it in. I'm hoping it won't cost anything but if it does I may consider the jtag services mentioned above.
How much for the instructions to do this? We have a device at work that the EEs use to jtag TI micro-controllers. Not sure if that would work. If Samsung gets all crazy and tries to charge me ridiculous amounts of money I may go your route.
Click to expand...
Click to collapse
I doubt it would work. Does it support ARM 8 architecture? YouTube search "nexus s jtag" and you can see my video.
Please let me know, either method. I can wait a little while. Thanks.
* There are plenty of useless infocontext, but I feel like it may be necessary so you can tell me where I went wrong.
Okay, first of all, I've been dedicating some time to this issue already, and have searched everywhere but no solutions so far.
I have a XT1033, I gave it to my sis when I got a new phone, but now it is back in my hands, because she managed (unsurprisingly) to 'break' it, or so I thought.
First thing that came into my mind was to hard reset, oh boy, as soon as the phone starts up, when it does, i get plenty of popups saying X and Y stopped working, many, many times, gapps happens to appear 1 second after i tap OK, every time. After I managed to get into the "starter" I've seen plenty of pointless apps, which I think may be the reason behind my headache and lost weekend, easy to solve, right? Wrong.
As I went into the "Settings/Configurations", after gapps and some other stuff stopped working for the 100th time, a window prompted me to enter a pass (It was CM Security), I swear, I almost threw the phone on the ground right there, please, someone tell me why would you do that? Anyway, after some name calling she gave the pass, but then another problem arises, the "Settings/Configurations" like everything else, stops working as soon as I click it, long story short, I cannot reset from the OS or turn on USB debugging.
Oh, and I tried to uninstall an app, CM Security to be more exact, it says uninstalled but when I start the phone again there it is.
Next step, Recovery (I'll try as I type to give you accurate info), when I go into wipe data/factory reset I get this msg (I should just take a photo...)
[...]E:
blkdiscard on partition /dev/block/pla
form/msm_sdcc.1/by-name/userdata failed
E: [...]
by-name/cache failed
-- Wiping clogo...
Data wipe complete.
Click to expand...
Click to collapse
Needless to say that nothing was erased.
Now comes the funny part, from my not so experienced reasoning, I think, hey I should flash another ROM, and that is what I try to do, I should also say that my sister lives in another city and that my brother tried to flash another ROM before I did, I don't know much but he knew NOTHING, and so he could have messed something up.
I try to downgrade it and install a 4.4.2 Stock ROM, because lollipop was not really good when I updated, and that might help in the long way, okay
(m)fastboot flash partition gpt.bin fails (preflash validation failed/remote failure) something else also failed, but I read that it is normal when you try to downgrade, and it may be true because it only went okay when I tried to flash another 5.0.2 ROM, but everything else went "Okay"
Why "Okay"? Because all the commands that had to do with 'erase' were okay but all of them were instant(0.016s), and when I turned the phone on, not only it was still lollipop, all the data was still there, and all the problems. Pretty much the same happens when I try to flash a 4.4.4 and a 5.0.2 ROM, nothing changes.
Then I think that may be something wrong with the "disk" be it the partition or the system file, I try a couple of fastboot commands, everything "Okay", but again nothing changes, still can't wipe any data.
I read that Custom Recovery might help my case, there I go, I download and flash TWRP and CWM multiples versions of each, whichever works, just to see the default recovery screen over and over.
Okay I could try to install it from the SD card, but the pc does not recognize the phone, and I can't transfer files, I also tried "BP tools" so I had a forced USB debugging, but then I just can't get it to be authorized on ADB, I followed the steps from another posts, and a only once i managed to get it to work, only for the phone screen to go blank after a dozen errors popups, so I might try it later again, not very hopeful though. Maybe I left some stuff out, but will include later if I remember/is relevant.
Edit: As soon as I turn on the phone if i go into the "Running Apps" tab(you know, the bottom right button), there is always whatsapp, facebook, and something else, I don't think that should happen when you turn on your phone, anyway, same apps, every time. Some of the names are "quoted" because my android is in another language and I am literally translating it, so things may be named differently for you.
From what you hear what would you do different, or is the phone a goner and I am wasting my time?
It sounds like you have a failed eMMC.
If that is the case, and I believe so, she'll need a new phone. It's non recoverable.
Sent from my XT1031
ATTACK said:
It sounds like you have a failed eMMC.
If that is the case, and I believe so, she'll need a new phone. It's non recoverable.
Click to expand...
Click to collapse
Hmm... I see, I was suspecting that it could be the hardware, but saying eMMC ringed a bell,
my brother followed a guide that told him to use this command: fastboot flash aboot emmc_appsboot.mbn
Is there a possibility this caused some problems?
I choose to believe you at this point, after all the work I had, I am just looking for closure
There are many different possibilities for a failed eMMC. Typically - it's caused by flashing the phone to much, or its just a bad eMMC.
Sent from my XT1031
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.
I downloaded the December factory image and updated the same way I always do:
fastboot flash bootloader bootloader-walleye-mw8998-002.0073.02.img
fastboot reboot-bootloader
fastboot flash radio radio-walleye-g8998-00253-1809191716.img
fastboot reboot-bootloader
fastboot update image-walleye-pq1a.181205.002.zip
After the standard update flow, the device rebooted and gave me the usual verified boot Orange warning screen, then I pressed power twice to move past it and the device loaded into the bootloader with "ERROR: LoadImageAndAuth Failed: Load Error" at the bottom.
Now when I try to boot, I don't get the verified boot screen, just the bootloader with "ERROR: Slot Unbootable: Load Error"
The bootloader no longer enumerates as a USB device, so I can't try reflashing the bootloader or flashing it to slot B (I am on slot A) or anything else. It does still say "Device State: unlocked" but I can't seem to do anything else.
I have tried multiple USB A->C cables and a USB C->C cable and multiple host machines, but none of them will get the Pixel 2 to show up in Device Manager.
Have I had a hardware failure? Is this any kind of known issue and is there any way to recover it?
Thanks.
same here. found any fix?
I also had the same issue. I have not yet been able to find a solution, tried multiple PCs and even tried booting into Linux and still got nothing. I talked to google support and they are cross-shipping me a replacement device right now. However, if anyone found a fix that would be great so I don't lose the data on my old phone (yes I know I should've been doing backups).
Edit: Was on a Google Pixel 2, going from September to December security patch. Tried updating using the flash-all.bat without the -w flag set. Completely stock except for a Magisk install.
Never found a fix, but once I described the symptoms Google was very quick to offer a warranty replacement. I was upgrading from the August image to the December image.
Hi! Just for info - I got to same situation, but I was able to fix it but I don't know, how I did it I was trying to fix it all evening, but without success. So I let phone turned on till morning. Phone was totally discharged at morning, only notification LED was blinking red, when I was trying to turn phone on. So I chared it with original charger about half hour, then connect it to PC and it was detected, so reflash update and my phone is alive again...
Maybe this will help to someone
To successfully root on the Dec update you must use Magisk v18.0
[2018.12.8] Magisk v18.0 - Root & Universal Systemless Interface [Android 5.0+]
If you've used an older version, you'll get a boot loop into Recovery.
Side load / install the uninstaller from @topjohnwu's page linked above.
Then side load / install again with v18.0
Use the uninstaller first.
I'm in the same boat, tried flashing dec factory image over my october install (failed on step 4/5) now fastboot is broken and I have the same "ERROR:Slot unbootable: Load Error".
drmason said:
I'm in the same boat, tried flashing dec factory image over my october install (failed on step 4/5) now fastboot is broken and I have the same "ERROR:Slot unbootable: Load Error".
Click to expand...
Click to collapse
Does your desktop/ laptop recognize your Pixel 2 in bootloader mode?
If it does, then there is almost 99% chance you can get it to boot up with some flashing.
If it doesn't there's literally no way for us to recover it.
yuva_cool said:
Does your desktop/ laptop recognize your Pixel 2 in bootloader mode?
If it does, then there is almost 99% chance you can get it to boot up with some flashing.
If it doesn't there's literally no way for us to recover it.
Click to expand...
Click to collapse
yeah i guessed so, so i initiated a replacement with the google support, went without an issue. Flashing stuff for years, but this is the first that went down.
Also tried to deplete the battery, didn't work for me... won't turn on at all anymore.
I too have been flashing since the last 2 years. But this was the first time everything went to hell. I mean this is ridiculous. And as far as I have noticed many people are facing this issue after flashing the December patches. I'm guessing something on the Google's end messed up things.
I applied for a repair and they picked up my device. Will know in a few days if they are kind enough to repair it for free.
yuva_cool said:
I too have been flashing since the last 2 years. But this was the first time everything went to hell. I mean this is ridiculous. And as far as I have noticed many people are facing this issue after flashing the December patches. I'm guessing something on the Google's end messed up things.
I applied for a repair and they picked up my device. Will know in a few days if they are kind enough to repair it for free.
Click to expand...
Click to collapse
Kind? I hope it's not a thing of kindness. As far as I know a unlocked bootloader doesn't void warranty... and they provide 24 month of warranty so I expect a free replacement.
My replacement should be arriving soon and if they will charge me the full price again this will be my last pixel I guess. Also they didn't argue or asked more questions at all on the hotline after I told them it died after flashing december patch. I guess they know whats going on...
See here:
https://forum.xda-developers.com/pixel-2/help/bricked-pixel-2-locked-bootloader-t3876792
or here:
https://forum.xda-developers.com/pixel-2/help/slot-unbootable-load-error-device-locked-t3842095
my mobile is bricked too! This seems to be a horrible problem for a few of us
I got mine completely repaired for free. They couldn't recover my data but they did get it up amd running. They even changed my display as it was very muched burned in and also changed the smi tray. I didn't even report these 2 issues. Im actually very happy with their response. Got the device back in 8 days. Loving the Pixel team.
same thing happen to me just now, currently my pc cant detect the phone, seems like dead end.
koax88 said:
same thing happen to me just now, currently my pc cant detect the phone, seems like dead end.
Click to expand...
Click to collapse
Claim for an RMA. They are approving for bootloop issues. I guess December patches screwed up things for a lot of us.
yuva_cool said:
Claim for an RMA. They are approving for bootloop issues. I guess December patches screwed up things for a lot of us.
Click to expand...
Click to collapse
the thing is, i bought it from 3rd party seller, because google not selling pixel in my country. is there any other way for me to fix this phone? or let google fix it for me?
tried linux, and multiple setup of usb cables, still nothing.. and i havent sleep yet.. any advice? is there any other way to force pc to recognized pixel bootloader? im at lost now
I have the same problem after flashing the Dec factory image on my pixel 2.
And Here is a detail that is not mentioned above. The 'flash-all' script failed and show：
Sending 'vendor_a' (359956 KB) FAILED (Write to device failed in SendBUffer() (Unknown error))
and now your phone still can be recognized by windows or not?
koax88 said:
the thing is, i bought it from 3rd party seller, because google not selling pixel in my country. is there any other way for me to fix this phone? or let google fix it for me?
Click to expand...
Click to collapse
They do rma even you dont bought it in Google store.
In my case they asked me several things about the failure, rooting and all that stuft. After proofing my words with my imei and online logged in data the gave me a RMA.
Thanks to Google. Best support for me.