Related
I rarely use my Nexus 7, but today decided to update it to 4.2.2. I flashed everything from android sdk: bootloader, clockworkmod recovery, franco kernel, system, and userdata. Then I sideloaded the SuperSU zip to root the tablet before my first boot up. Now when it boots up, it asks me to type my password to decrypt the storage. I never set a password on the tablet and the other people that used the tablet in my home as far as I know, did not encrypt the storage. Now, I even wiped/factory reset the device from clockworkmod as well as reflashing system and userdata. Why is this occurring?
Bump.
Boot your device in the bootloader (fastboot) and type
Code:
fastboot format userdata
Or if this won't work you could format every partition and after formatting it you flash the images again
Sent from my Nexus 7 running Android 4.2.2
I woke up with the same problem. Tried to boot into recovery and got the "No Command" message. I ended up having to call Google Customer Care and they are sending me a new tablet for free. I just have to send the defective device back to them within days. May be helpful if you bought you device from the Google Play Store.
Hi guys,
I woke up to the same thing too, but I'm afraid to call customer service because my tablet is unlocked..(but it's running stock android and this issue just showed up the day after I updated it to 4.2.2...
P.S: I bought it from the Play Store as well.
Thanks!
mihahn said:
Boot your device in the bootloader (fastboot) and type
Code:
fastboot format userdata
Or if this won't work you could format every partition and after formatting it you flash the images again
Sent from my Nexus 7 running Android 4.2.2
Click to expand...
Click to collapse
I tried that before and it didn't work. Thanks.
Xavion2004 said:
I woke up with the same problem. Tried to boot into recovery and got the "No Command" message. I ended up having to call Google Customer Care and they are sending me a new tablet for free. I just have to send the defective device back to them within days. May be helpful if you bought you device from the Google Play Store.
Click to expand...
Click to collapse
I called up Nexus Support and they had setup for me to send it back to them; however, I fixed it after I got off the phone with them. Very strange bug; If I flash clockworkmod recovery, the tablet will boot into the type password to decrypt storage. The factory data reset on clockworkmod recovery doesn't fix it either. If I flash back to the stock recovery and factory data reset, the tablet works fine. I probably don't even need to factory data reset - it's stock recovery that fixes this. I didn't have the "No Command" message though which the Nexus Support guy thought I would have. So I guess I don't have to send my tablet back after all . I wanted to because it's an 8gb and I probably would of got upgraded to a 16gb since the 8gb model is no longer manufactured, haha.
Abhitha said:
Hi guys,
I woke up to the same thing too, but I'm afraid to call customer service because my tablet is unlocked..(but it's running stock android and this issue just showed up the day after I updated it to 4.2.2...
P.S: I bought it from the Play Store as well.
Thanks!
Click to expand...
Click to collapse
Download android sdk on your pc, go to platform-tools, open command prompt, boot tablet into the bootloader, type 'fastboot oem lock' to lock the tablet again.
Download android sdk on your pc, go to platform-tools, open command prompt, boot tablet into the bootloader, type 'fastboot oem lock' to lock the tablet again.
Click to expand...
Click to collapse
Thanks. I will try this when I get home today and post back after a call to customer support :good:
Download android sdk on your pc, go to platform-tools, open command prompt, boot tablet into the bootloader, type 'fastboot oem lock' to lock the tablet again.
Click to expand...
Click to collapse
Hm I tried locking the tablet as per your instructions, and it succeeded (at least according to the command prompt), however the unlocked symbol is still there. I called support and they told me they can't RMA is till I relock it...
EDIT:
I followed instructions at another post on XDA to flash back the stock 4.2.2 rom as well as perform another oem lock, however the unlocked symbol is still there on the Google splash screen, not to mention the encryption message is still there.
I just wanted to point out: in my experience, you can't sideload anything before first boot after reflashing userdata.img or doing a wipe from fastboot, because it doesn't initialize the data partition until you take it through a boot cycle into the ROM. This may be the cause of the erroneous encryption message in custom recovery.
If you boot the tablet, and then after boot and proper shutdown go into custom recovery, do you still get the same message?
Sent from my Nexus 7 using Tapatalk HD
Was there ever a resolution for this issue? I ran into the same thing today - I turned on my n7 after months of no use, and it asked for a decryption password which I never set.
jmusso said:
Was there ever a resolution for this issue? I ran into the same thing today - I turned on my n7 after months of no use, and it asked for a decryption password which I never set.
Click to expand...
Click to collapse
Resolution, I don't know. I do have a a few more tidbits of information, though.
I could reproduce the "enter password" symptom by doing a "fastboot erase userdata" followed by a boot of the custom recovery. That is, by not having any filesystem at all, I could produce the symptom with TWRP - even though I have never encrypted the /data partition. So, at least certain versions (2.4.1.0?) of that custom recovery seems to regard a mount failure to mean that "your data paritition is encrypted" - that certainly is a "red herring".
iirc, there is supposed to be a "crypto footer" in the last 16k bytes of the partition which lives outside of the end of the ext4 filesystem. I suppose that if you knew the exact size of your data partition, you could write zeros (dd if=/dev/zero ...) using the custom recovery to the last 16k of that partition and see if that clears anything up. Search the (above) link near the places where it mentions the "crypto footer". If that last 16k were all zeros, I would think that would cause "vold" to realize that there is no valid keys, etc in there. (But that's a little bit of a guess).
None of it explains why a device can sit on a shelf for months and suddenly start behaving differently on it's next boot, though. That smells a lot like bit rot or hardware failure in the eMMC flash memory.
But if the alternative is to throw the tablet out, it can't hurt to do a factory reset (stock devices) or a "fastboot erase userdata ; fastboot format userdata" (unlocked device). Both of those will nuke all data (including what's on the psuedo-SD card).
Anyhow, there's two ideas.
good luck
bftb0 said:
Resolution, I don't know. I do have a a few more tidbits of information, though.
I could reproduce the "enter password" symptom by doing a "fastboot erase userdata" followed by a boot of the custom recovery. That is, by not having any filesystem at all, I could produce the symptom with TWRP - even though I have never encrypted the /data partition. So, at least certain versions (2.4.1.0?) of that custom recovery seems to regard a mount failure to mean that "your data paritition is encrypted" - that certainly is a "red herring".
iirc, there is supposed to be a "crypto footer" in the last 16k bytes of the partition which lives outside of the end of the ext4 filesystem. I suppose that if you knew the exact size of your data partition, you could write zeros (dd if=/dev/zero ...) using the custom recovery to the last 16k of that partition and see if that clears anything up. Search the (above) link near the places where it mentions the "crypto footer". If that last 16k were all zeros, I would think that would cause "vold" to realize that there is no valid keys, etc in there. (But that's a little bit of a guess).
None of it explains why a device can sit on a shelf for months and suddenly start behaving differently on it's next boot, though. That smells a lot like bit rot or hardware failure in the eMMC flash memory.
But if the alternative is to throw the tablet out, it can't hurt to do a factory reset (stock devices) or a "fastboot erase userdata ; fastboot format userdata" (unlocked device). Both of those will nuke all data (including what's on the psuedo-SD card).
Anyhow, there's two ideas.
good luck
Click to expand...
Click to collapse
I'm just responding to say this fix worked for me. I only did a "fastboot erase userdata" from the adb terminal in Windows, however. Thanks for the help, and good luck to anyone else running into this problem.
Nexus 5, Flash write failure
Hey guys,
I am getting flash write errors whenever i try to fastboot stock images..
Nothing seems to be working.
I am able to temporarily boot into Philz recovery using the Nexus Rootkit and get adb functionality also.
But the phone doesn't boot into anything and i am forced to use TWRP recovery. Any other recovery doesn't work other than booting temporarily.
TWRP is also asking for a password i didnt set.
PLEASEEEE HELPPPP SOMEONEEE
Either your device is permanently bricked, or you have driver problems on the computer running fastboot. Try a different computer, different USB cable, etc.
Sent from my Nexus 7 using Tapatalk
i have done factory restore; data format full system, advanced wipes and reloads forever, but at the end of the day, that damn decrypt message is still there. at this point, i don't care about data. i just want the phone back up and running. i don't care which rom, even factory. i am on a htc evo 4g lte, with hboot 2.10.0000. and i have tried several recoveries.
As title suggests, my bootloader is locked and my N7 will not boot past the Google logo. If i try Recovery, it says "booting failed" so I can only assume that it was lost/erased. Is an RMA through Asus my only choice at this point?
If you can boot into bootloader mode (which you can) you can use fastboot to flash a stock image. Here is a fine guide. It seems like something on your data and/or recovery partition got corrupted. If you still have a warranty, you should send it to RMA. But it's your choice.
Erovia said:
If you can boot into bootloader mode (which you can) you can use fastboot to flash a stock image. Here is a fine guide. It seems like something on your data and/or recovery partition got corrupted. If you still have a warranty, you should send it to RMA. But it's your choice.
Click to expand...
Click to collapse
I can get to bootloader but I am unable to unlock it. When I try to unlock it, it gives me the prompt, I click YES and then it just goes back to bootloader but still locked.
Well, that's interesting. I don't know what could it be. I guess, RMA is your best option.
engagedtosmile said:
I can get to bootloader but I am unable to unlock it. When I try to unlock it, it gives me the prompt, I click YES and then it just goes back to bootloader but still locked.
Click to expand...
Click to collapse
Hi, engagedtosmile...
This seems to be a common problem... inability to unlock the bootloader... I've come across it a few times, both here on XDA and on other forums.
As I suggested a while ago with this guy who had a similar problem... it could potentially be an eMMC chip gone bad, a corrupted partition structure (very unlikely though, since both his and your Nexus 7 boots and works fine otherwise) or a corrupted bootloader (extremely unlikely, as the Nexus 7 wouldn't boot at all).
As a bit of a last ditch 'clutching-at-straws' suggestion, I advised him to try a different USB port on his PC and/or a different USB cable... my experiences of using fastboot, is that it can be remarkably fussy about such things at times.
Anyway, it appears to have worked for him.
So, it might be worth a shot... change to a different USB port, and/or maybe try a different USB cable.
Good luck... and hope you have as much success as the guy whose post I referenced above.
Rgrds,
Ged.
Hello Guys,
yesterday I restarted my Nexus 4, running the cm-13.0-20160520-NIGHTLY-mako. It stuck at the bootlogo, so I tried to reflash it in the twrp 2.8.7.0 recovery. But I got the error message "E:/ unable to mount /cache".
After that I was trying to solve this issue by wiping the cache, but I got the same error message -> The phone wasn't booting
From now on I did several things to solve my problem. I don't know the exact order.
- I've downloaded the Nexus Root Toolkit from WugFresh -> Tried to use the Flash Stock + Unroot Option with Soft-Bricked/Bootloop status enabled -> I choosed the 5.1.1 Factory Image -> In the cmd window, I get in every point the same error message "Falied (remote: flash write failure) -> I get the same message when I'm trying to manually flash each part of the factory image via fastboot
- Within the Toolkit I also tried to format cache, system and Userdata, but afther this I get the same error when trying to do the step before
- I think also used the Fastboot Flash options, but I'm not sure.
- After that I attempted to flash the cm13.zip via adb-sideload in TWRP. Here is a part from the error message I get:
"(...) could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid argument
unmount of /system failed: no such volume (...)
E: Error executing updater binary in zip 'sideload/package.zip'
E: Unable to mount '/data'
- In TWRP the Internal Storage is shown with 0mb
- Currently only the bootloader is working fine and I also can get a fastboot and adb connection to the phone
-> Loading the recovery is only possible by booting a recovery image in fastboot
Can somebody tell me if it is possible to restore my Nexus 4 and how to do it?
Thank you in advance :fingers-crossed:
PS: I hope I mentioned all the important points. If some information is missing, feel free to ask me.
Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?
audit13 said:
Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Thank you for your answer.
I tried to flash the newest cm13 in TWRP and with adb Sideload. I get the same error.
Also the 4.2 Stock rom doesn't work. Same problem as with the 5.1.1 factory image.
I also switched the cable and the USB ports, but it leads to the same error messages.
Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.
From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.
audit13 said:
Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.
Click to expand...
Click to collapse
I get the same error message as always: Falied (remote: flash write failure)
nerotNS said:
From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.
Click to expand...
Click to collapse
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:
Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.
audit13 said:
Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.
Click to expand...
Click to collapse
Unfortunately yes. After locking the bootloader via fastboot, the bootloader is marked as unlocked after rebooting.
Do I have to change the mainboard?
This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.
audit13 said:
This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.
Click to expand...
Click to collapse
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.
tobi.king said:
I get the same error message as always: Falied (remote: flash write failure)
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:
Click to expand...
Click to collapse
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
tobi.king said:
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.
Click to expand...
Click to collapse
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.
nerotNS said:
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.
Click to expand...
Click to collapse
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.
tobi.king said:
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.
Click to expand...
Click to collapse
Awesome, glad to be of service
hi, i have a problem with my N6P. it was unlocked, twrp flashed and running newest version of this ROM http://forum.xda-developers.com/nexus-6p/development/rom-debloated-prerooted-deoxeded-t3372600.
then, out of the blue, phone refused to work. when i'm trying to restart it, only option is boot to bootloader. i was trying to flash newest radio, bootloader, vendor and recovery - all failed with message "(remote: flash write failure)"
when i'm in bootloader mode, Andy Android is lying on his back, with no red exclamation point.
also there is written below Andy:
BL: K
Baseband: (empty)
Product/Variant: Angler-VN2
Serialn Number: (is present, but i think there is no need to write it)
CPU: MSM8994 0x20001
eMMC: 32GB Samsung
DRAM: 3072MB HYNIX LPDDR4
Console: NULL
Battery OK
Device is LOCKED
Qfuse Status: ENABLED
Off-Mode-charge: ENABLED
Download Mode: DISABLED
Connect USB Data Cable
strange thing is, that there is written "Device is LOCKED", because when wrote command "fastboot flashing unlock", there was a message:
...
(bootloader) Device already unlocked!
FAILED (remote failure)
I was able to fastboot boot boot.img, but it hanged on "Google" screen.
device is not visible after writing "adb devices", but is visible after writing "fastboot devices".
any ideas?
Might be a dumb question, but have you tried going back to stock Android N using Googles Factory Image in fastboot just to determine if your phone will still boot into os?
i'm downloading GFI, but 3 more hours left to finish download (unless there is a mirror server to download them). i'll probably try to do it, but i would like to avoid it because my backup is 2 months old :/
Fe Mike said:
Might be a dumb question, but have you tried going back to stock Android N using Googles Factory Image in fastboot just to determine if your phone will still boot into os?
Click to expand...
Click to collapse
tried this, no luck - still "remote flash write failure" message.
strange thing is, that i'm able to relock the bootloader (at least command "fastboot flashing lock" gave me possibility to do this {(YES/NO) message}, i didn't relocked it.
i've read, that this is probably fried emmc, but would it be possible to relock bootloader though?
miguelm75 said:
tried this, no luck - still "remote flash write failure" message.
strange thing is, that i'm able to relock the bootloader (at least command "fastboot flashing lock" gave me possibility to do this {(YES/NO) message}, i didn't relocked it.
i've read, that this is probably fried emmc, but would it be possible to relock bootloader though?
Click to expand...
Click to collapse
You might be right about fried emmc, have you tried placing a twrp.img in fastboot folder and run command fastboot boot twrp-x-x-x.img (not flash)? If it is fried can you rma?
Edit: I found this thread, second post has a link that may help. It is kinda advanced. The process can at least tell you if in fact emmc is bad and if it's not bad there may be a way of fixing it.
Fe Mike said:
You might be right about fried emmc, have you tried placing a twrp.img in fastboot folder and run command fastboot boot twrp-x-x-x.img (not flash)? If it is fried can you rma?
Edit: I found this thread, second post has a link that may help. It is kinda advanced. The process can at least tell you if in fact emmc is bad and if it's not bad there may be a way of fixing it.
Click to expand...
Click to collapse
1. i tried to flash recovery - no luck.
2. there will be problem with RMA, because i won this phone in a giveaway at AndroidAuthority.com and it has US warranty, so it would be rather expensive to send it to USA from Poland. but i will try to contact Huawei support in my country.
3. did you forgot to insert link to this thread?
miguelm75 said:
1. i tried to flash recovery - no luck.
2. there will be problem with RMA, because i won this phone in a giveaway at AndroidAuthority.com and it has US warranty, so it would be rather expensive to send it to USA from Poland. but i will try to contact Huawei support in my country.
3. did you forgot to insert link to this thread?
Click to expand...
Click to collapse
Yes I did, my bad.
https://www.google.com/amp/s/amp.re...here_a_way_to_check/?client=ms-android-google
Fe Mike said:
Yes I did, my bad.
https://www.google.com/amp/s/amp.re...here_a_way_to_check/?client=ms-android-google
Click to expand...
Click to collapse
thank you. unfortunatelly this is for LG devices. i can't find anything similiar for Huawei devices. i did tried Nexzus Root Toolki by Wug Fresh and i got the same error - "remote flash write failure"
so i think i will try to contact Huawei and local phone service to see, if they are able to fix it. thank you for your help.
Did you try to format data partition then flash the google image?
Iceburn1 said:
Did you try to format data partition then flash the google image?
Click to expand...
Click to collapse
i just did and received (remote: failed to erase partition) error.
miguelm75 said:
thank you. unfortunatelly this is for LG devices. i can't find anything similiar for Huawei devices. i did tried Nexzus Root Toolki by Wug Fresh and i got the same error - "remote flash write failure"
so i think i will try to contact Huawei and local phone service to see, if they are able to fix it. thank you for your help.
Click to expand...
Click to collapse
The op has an LG device but in second post there is a link (the one I'm posting now) for Qualcomm chipsets.
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
miguelm75 said:
tried this, no luck - still "remote flash write failure" message.
strange thing is, that i'm able to relock the bootloader (at least command "fastboot flashing lock" gave me possibility to do this {(YES/NO) message}, i didn't relocked it.
i've read, that this is probably fried emmc, but would it be possible to relock bootloader though?
Click to expand...
Click to collapse
Same thing just happened to me except I was just using my phone then it crashed and never came back tried for days to recover was able to re-lock bootloader but no other commands took. Had to RMA it back to Huawei took 3 weeks but it was covered by 12 month warranty so that's a plus
did you switch on find my phone in administer options before unlocking and flashing errors ?
rowihel2012 said:
did you switch on find my phone in administer options before unlocking and flashing errors ?
Click to expand...
Click to collapse
no, i didn't touch it.
Happened to me too while using it. I am still trying to save my data, but no luck for now.
Hello!
Now, I know this problem is in other threads. But the only reason why I'm posting a new one is if either that thread had died or the solution wasn't applicable to me (it didn't/doesn't work).
So! What happens is when I try to flash a file to the system or vendor I get this error.
Code:
failed to mount partition '/vendor' (invalid argument)
I've tried in TWRP and the bootloader fixes. And now, I currently have no OS.
What I've tried is as follows:
Flashing just the vendor (bootloader/TWRP) - ends with the vendor error.
Flashing .zip ROMs (bootloader/TWRP) - ends with the vendor error.
Trying the usual return to stock procedure - ends with the vendor error.
Repairing partition in TWRP - Says operation completed but the error is still persistent.
Basically. Nothing works because the Vendor partition is unmountable.
What should I do? I have no idea what a fix could be.
Alright, so i've tried some things. I guess I've fixed it but I got a new problem. In the end what fixed it was wiping every parition and rebooting TWRP and then flashing a system image then vendor image. When i say image i mean a manual .img flash instead of a .zip file.
The problem now it that because every was wiped, i no longer have a recovery. When i boot into recovery i get "No command". So now im stuck with stock android 8.1 and a unlocked bootloader that won't do anything. Every time i try and flash a partition i get
Code:
FAILED (data write failure (Too many links))
or
Code:
FAILED (command write failed (No error))
Any tips on getting a recovery installed so i can return to my custom ROM ways.
Thanks for any help in advance.
Nexus Radical said:
Alright, so i've tried some things. I guess I've fixed it but I got a new problem. In the end what fixed it was wiping every parition and rebooting TWRP and then flashing a system image then vendor image. When i say image i mean a manual .img flash instead of a .zip file.
The problem now it that because every was wiped, i no longer have a recovery. When i boot into recovery i get "No command". So now im stuck with stock android 8.1 and a unlocked bootloader that won't do anything. Every time i try and flash a partition i get
or
Any tips on getting a recovery installed so i can return to my custom ROM ways.
Thanks for any help in advance.
Click to expand...
Click to collapse
Try using Nexus root toolkit, I used that today to fix recovery,
jimbomodder said:
Try using Nexus root toolkit, I used that today to fix recovery,
Click to expand...
Click to collapse
Done some research and it seems to be a cable issue of all things with this errors. I bought a new one that should arrive by amazon tomorrow. Will see if that fixes it.
As the nexus toolkit ive been using that a lot. With that i don't even get an error but it never works.
Nexus Radical said:
Done some research and it seems to be a cable issue of all things with this errors. I bought a new one that should arrive by amazon tomorrow. Will see if that fixes it.
As the nexus toolkit ive been using that a lot. With that i don't even get an error but it never works.
Click to expand...
Click to collapse
That's something I have loads of, all seem to connect ok but least you should have it fixed soon.
jimbomodder said:
That's something I have loads of, all seem to connect ok but least you should have it fixed soon.
Click to expand...
Click to collapse
Yeah well, it seemed the cable wasn't the issue. I wouldn't of thought it was myself but yeah. Seems my initial thoughts were right as the cable didn't fix anything. Same errors, same problem. So all my research has lead to nothing. So how can I fix this? I'm out of solutions. I need xposed at least on my phone to be usefull since I can't disable the screen off during calls.
Nexus Radical said:
Yeah well, it seemed the cable wasn't the issue. I wouldn't of thought it was myself but yeah. Seems my initial thoughts were right as the cable didn't fix anything. Same errors, same problem. So all my research has lead to nothing. So how can I fix this? I'm out of solutions. I need xposed at least on my phone to be usefull since I can't disable the screen off during calls.
Click to expand...
Click to collapse
Have you tried wugfresh Nexus tool kit?
Just thought I'd let you know that I have fully restored stock and locked my bootloader, and if I boot recovery I get " no command" too. Seems latest recovery image does f*@k all.
jimbomodder said:
Have you tried wugfresh Nexus tool kit?
Click to expand...
Click to collapse
No, I haven't. BUT!!! I have fixed it...
So the issue that I was having is that I bought a replacement charging board (the PCB for the USB dock.) I replaced it because I had a faulty microphone on it but the USB port was fine. Putting in the old one fixed all the issues I was having. Its meant to be an OEM part so I didn't figure it would be the problem but it was *sigh*... So I take it where I got it from Replacement Base wasn't legit? Ah well, at least my problem is fixed and if anyone gets the same problems they might find this thread.
Thanks for your support thought dude! It was nice to have someone to ask.
Nexus Radical said:
No, I haven't. BUT!!! I have fixed it...
So the issue that I was having is that I bought a replacement charging board (the PCB for the USB dock.) I replaced it because I had a faulty microphone on it but the USB port was fine. Putting in the old one fixed all the issues I was having. Its meant to be an OEM part so I didn't figure it would be the problem but it was *sigh*... So I take it where I got it from Replacement Base wasn't legit? Ah well, at least my problem is fixed and if anyone gets the same problems they might find this thread.
Thanks for your support thought dude! It was nice to have someone to ask.
Click to expand...
Click to collapse
O crap, I got 2 "oem" replacement cameras for my 6p from them and both blurry and don't save pictures,. Glad you fixed it yet.