Nexus 5 (D821) latest OTA release (OTA-15) issue
-
Hi all, have quite a few D821's that I am testing UBports with (easy phone to split apart and mess around with). I have come across an issue (I think) with OTA-15 bricking the phone. I run the upgrade through the update system and it reboots to install, then sits at the Nexus UBports boot splash screen and that's it. When I enter recovery and wipe the cache partition, it throws up: E: failed to mount /cache (Invalid Argument). I cannot install any other recovery, it won't allow a full recovery and will sit at the splash screen. I know they are old phones and have varied usage, but why would an upgrade do this. I have some other things to try, the last resort is using a reflow machine for the CPU and the RAM. Has anyone else experienced this, or am I just unlucky with some of the phones (OTA-14 and below is absolutely fine)?
Xiaomi Redmi Note 7.... And more...
I have too many devices... -
@mrt10001 said in Nexus 5 (D821) latest OTA release (OTA-15) issue:
ade through the update system and it reboots to install, then sits at the Nexus UBports boot splash screen and that's it. When I enter recovery and wipe the cache partition, it throws up: E: failed to mount /cache (Invalid Argument). I cannot install any other recovery, it won't allow a full recovery and will sit at the splash screen. I know they are old phones and have varied usage, but why would an upgrade do this. I have some other things to try, the last resort is using a reflow machine for the CPU and the RAM. Has anyone else experienced this, or am I just unlucky with some of the phones (OTA-14 and below is absolutely fine)?
Its very strange indeed, nobody worked on the device image for N5, so this is the same since almost a year. You might need to flash TWRP recovery to wipe all partitions correctly though. The UBports recovery is unfortunately of little use
-
@mrt10001 I don't know if is related, but I'll leave it here: before the official release of OTA 15 stable, I was on RC channel, but was the same image since I was testing it. The day with the official OTA 15 release, I've switched to stable channel and the phone started downloading the image of OTA11 !!!! After this, it didn't want to go back to OTA15 whatsoever. The only thing that solved it was booting in recovery mode, but you said you are not able so...
-
Hi thanks for the reply. Unfortunately I am a "weekend warrior", work commitments leave me with little time to tinker with it, but when I get some at weekends , I will try again. I have now some non fully working phones to test (bad motherboards etc) against and I will try another version of TWRP (I tried the latest) to see if that works better. I am just hoping it is not coincidence and either the RAM or (not CPU) eMMC has failed (I have access to a reflow machine, but with COVID I don't know when. Thanks for all your suggestions, when I have some spare cash I will start donating to UBports as I think it is a really worthwhile cause, anything to stop hardware going into a rubbish tip.
