Hi,
I try to boot my Nexus 7 (2013/wifi). I have access to :
a white google logo
a fastboot access
and a recovery mode (with a sideload option)
I was reading my email when the tablet suddenly reboot and stuck on the Google logo. Now, I don't know what can I do.
Code:
Fastboot oem unlock
doesn't work (FAILED <unknow error>).
I can flash a new bootloader (FLO-04.04) but can't unlock it.
Are you getting any specific error message ?
After recovery mode I have something like :
Code:
-- Wiping cache...
Formatting /cache..
Cache wipe complete.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_locale
I make a `fastboot oem unlock` right now and waiting after a error :angel:
Code:
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
edit : After 23000 s
FAILED (unknown status code)
May be my best choice is to waiting for 5.1 OTA (nexus 7 2013 wifi) and make a sideload ?
Any suggestion ?
jaiunxda said:
Any suggestion ?
Click to expand...
Click to collapse
Last chance : https://www.change.org/p/google-lg-...aign=share_twitter_responsive#petition-letter
Related
Hello!,
I got my nexus 4 on Tuesday this week. The first thing I did was to load francos kernel. Today I decided to go back to stock and downloaded fresh images from google. I added the image thru Fastboot and now the process after the files are loaded to the phone, goes REALLY slow.
The Google image stays there for 3 minutes then it goes to the Nexus logo. I erased everything like 5 times and same thing. Right now, its been about 10 minutes and it is still in the Nexus logo.
If it's the first boot it will go slow it should speed up after that.
Sent from my Nexus 4 using xda app-developers app
Ieatnoobs said:
Hello!,
I got my nexus 4 on Tuesday this week. The first thing I did was to load francos kernel. Today I decided to go back to stock and downloaded fresh images from google. I added the image thru Fastboot and now the process after the files are loaded to the phone, goes REALLY slow.
The Google image stays there for 3 minutes then it goes to the Nexus logo. I erased everything like 5 times and same thing. Right now, its been about 10 minutes and it is still in the Nexus logo.
Click to expand...
Click to collapse
Did you use the flash-all.bat file in the image from Google?
xda6969 said:
Did you use the flash-all.bat file in the image from Google?
Click to expand...
Click to collapse
I flashed everything.
Also, when I flashed clockworkmod recovery I get this
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
never seen this before
also, it looks like it is stuck at tne X logo ...
Ieatnoobs said:
I flashed everything.
Also, when I flashed clockworkmod recovery I get this
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
never seen this before
also, it looks like it is stuck at tne X logo ...
Click to expand...
Click to collapse
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Code:
fastboot flash bootloader bootloader-mako-makoz10o.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot-bootloader
fastboot –w update image-occam-jdq39.zip
Profit?
hello,
today i downloaded the Android 5.0 Image from Google and wanted to flash it.
i extraced the tgz file and flashed the boot.img and system.img via fastboot.
so far so good. i reboot the tabelt and it has a bootloop.
so i used the flash-all.bat included in the tgz file but it wont flash it (didnt copied the error message)
so i tried flashing 4.4.4. but when i flash anything it wont work (fastboot flash recovery recovery.img for example)
i tried differend usb ports and with fastboot devices it shows my device.i tried rebooting the laptop and the tablet. no changes
example
Code:
C:\Users\xxx\Desktop\nakasi-lrx21p>fastboot flash recovery recovery.img
sending 'recovery' (5682 KB)...
after 20 min of waiting nothing changes.
my setup:
a laptop with windows 8.1
all drivers installt
original nexus 7 usb cable
drivers are working fine. i often flashed something on the n7 and my m7 bevor on this laptop
Code:
C:\Users\xxx\Desktop\nakasi-lrx21p>fastboot flash boot boot.img
sending 'boot' (5146 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
thats a error message i get when something more happens then "sending 'xxx' (xxx kb)
Code:
FAILED (data transfer failure (Too many links))
finished. total time: 85.114s
now i managed to flash recovery (TWRP)
but i cant do anything there. in the pc its not listet (adb devices) and in the log of TWRP it says
Code:
E:Unable to mount '/data'
E:Unable to mount '/system'
E:Unable to mount '/cache'
E:Unable to mount '/data'
now i got in TWRP (changing to Clockworkmod Recovery doesnt change anything) and got to Wipe-> Advanced
there i tried to repair the partions . doesnt works. but if i format it that works and could be mounted again. (in system i have to format it in an different file format and back to ext4)
so now i flashed the rom (stock 5.0 from google) and it boots... waiting whats coming next....
etsch said:
now i got in TWRP (changing to Clockworkmod Recovery doesnt change anything) and got to Wipe-> Advanced
there i tried to repair the partions . doesnt works. but if i format it that works and could be mounted again. (in system i have to format it in an different file format and back to ext4)
so now i flashed the rom (stock 5.0 from google) and it boots... waiting whats coming next....
Click to expand...
Click to collapse
i have the same problem how did you format it and did it fix the problem
do you have TWRP ?
you go to wipe-> advanced
there you can choose which repair and format.
ive formated one by one and then it shows the size after formating.
now my tablet booted into android (i think its ugly) but iam afraid going in the recovery
So my Nexus 7 (2012, wifi only, 32 GB, Android 4.4.4, not rooted) is just over a year old, and I have had absolutely no problems with it until one fine day its battery was completely drained and even after charging it for over 3 hours, it refused to boot up. It was stuck at the 4 colored balls animation. I checked the bootloader and it said something like
Code:
unable to mount /cache (invalid <something>)
.
So I decided that since I will anyway have to do a complete wipe of the data on tablet, why not install Android 5.0.2 by getting the image from Google? But much to my chagrin, the command prompt has been stuck on
Code:
writing 'system' . . .
for almost an hour now. --Shouldn't the whole process be complete in 10 minutes tops?
Another thing is that adb does not detect my device, but fastboot does.
Also, the command,
Code:
fastboot flash bootloader bootloader-grouper-4.23.img
throws an error:
Code:
writing bootloader . . .
FAILED (remote: (InvalidState))
What could be the error? Is it an H/W issue? Or am I simply doing something wrong?
The commands I gave are:
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot -w update image-nakasi-lrx22g.zip
When I try to wipe internal it says
Code:
Wiping internal storage -- /data/media...
Error opening: '/data/media' (No such file or directory)
When I try to format instead - I get even more errors:
Code:
Formatting Data using make_ext4fs...
Failed to mount '/data' (Device or resource busy)
Failed to mount '/data' (Device or resource busy)
Unable to recreate /data/media folder.
You may need to reboot recovery to be able to use /data again.
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Is this because of encryption? And if so - this is weird because I never encrypted my device. I currently have no OS and just trying to unsoftbrick my phone.
specialk00 said:
...Is this because of encryption? And if so - this is weird because I never encrypted my device. I currently have no OS and just trying to unsoftbrick my phone.
Click to expand...
Click to collapse
Use fastboot and make sure you are using the latest binaries. Format system, userdata and cache. Upon booting for the first time, the 6P automatically defaults to encryption- unless you intervene and stop it from doing so.
v12xke said:
Use fastboot and make sure you are using the latest binaries. Format system, userdata and cache. Upon booting for the first time, the 6P automatically defaults to encryption- unless you intervene and stop it from doing so.
Click to expand...
Click to collapse
Yep, I just fixed it somehow, I think it was related to MTP in TWRP. However now I'm stuck with a different issue. No matter what I flash in fastboot - I get
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot flash recovery D:\Downloads\angler\twrp-3.1.1-0-angler.img
target didn't report max-download-size
sending 'recovery' (16948 KB)...
FAILED (command write failed (No error))
finished. total time: 0.003s
I always get this weird "No error" thing.
specialk00 said:
Yep, I just fixed it somehow, I think it was related to MTP in TWRP. However now I'm stuck with a different issue. No matter what I flash in fastboot - I get
Click to expand...
Click to collapse
Are you sure you are using the latest binaries? Hash checked the TWRP file? Put TWRP img in your fastboot folder? Format/erase recovery partition?
v12xke said:
Are you sure you are using the latest binaries? Hash checked the TWRP file? Put TWRP img in your fastboot folder? Format/erase recovery partition?
Click to expand...
Click to collapse
Yes I'm using the latest binaries - I got them via Android SDK and updated everything. I checked the ones you linked and they are exactly the same.
Regarding the hash check - this has nothing to do with the file being corrupted. This happens with ANY file I try to flash.
I tried putting the TWRP img in my fastboot folder and the results are the same.
Erasing the recovery partition gives the same error.
Code:
C:\Users\username\AppData\Local\Android\sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
FAILED (command write failed (No error))
finished. total time: 0.009s
specialk00 said:
Yes I'm using the latest binaries - I got them via Android SDK and updated everything. I checked the ones you linked and they are exactly the same. Regarding the hash check - this has nothing to do with the file being corrupted. This happens with ANY file I try to flash. I tried putting the TWRP img in my fastboot folder and the results are the same. Erasing the recovery partition gives the same error.
Click to expand...
Click to collapse
Were you able to successfully fastboot format userdata, system and cache with no errors? Did you get the same error using format as you did erase recovery? Is your phone bootlooping ? If yes, then your phone may have the BLOD. There are a few instances of users still having access to recovery mode, but not being able to flash anything. If you flash a full stock image with flash-all.bat, it finishes but the phone still loops then you likely have the BLOD.
v12xke said:
Were you able to successfully fastboot format userdata, system and cache with no errors? Did you get the same error using format as you did erase recovery? Is your phone bootlooping ? If yes, then your phone may have the BLOD. There are a few instances of users still having access to recovery mode, but not being able to flash anything. If you flash a full stock image with flash-all.bat, it finishes but the phone still loops then you likely have the BLOD.
Click to expand...
Click to collapse
I tried minimal adb & fastboot (bit older version) and got this.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.1.1-0-angler.img
target didn't report max-download-size
sending 'recovery' (16948 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.007s
Then I tried another old version of fastboot - got one from july 2016 (23.0.1) and nothing happened when executing flash or format commands.
Then I tried normal, latest fastboot and both (new & old) versions of fastboot gave me this error.
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
FAILED (command write failed (No error))
finished. total time: 0.023s
Then I tried to format (instead of erase)
Code:
C:\Users\Nexusflip\AppData\Local\Android\sdk\platform-tools>fastboot format userdata
FAILED (command write failed (No error))
I don't know if my phone is bootlooping because I don't have OS installed and my internal storage is squeaky clean. All this crap didn't just start out of nowhere - I flashed 8.0.0 dev preview 2 images through TWRP. I know I'm not the brightest. When I launch flash-all.bat it's just blank and does nothing at all.
specialk00 said:
I don't know if my phone is bootlooping because I don't have OS installed and my internal storage is squeaky clean. All this crap didn't just start out of nowhere - I flashed 8.0.0 dev preview 2 images through TWRP. I know I'm not the brightest. When I launch flash-all.bat it's just blank and does nothing at all.
Click to expand...
Click to collapse
It sounds to me like your internal storage (memory) is bad. Bottom line is that if you can't format your basic partitions successfully, you will not be able to flash a full ROM. If you don't believe your memory is bad, you can search the 6P forums for the Qualcomm Flash Image Loader (QFIL) & EDL mode. There is a rescue binary for the 6P floating around that some people have been successful in using restoring corrupt partitions, presumably because it works at the hardware level.
v12xke said:
It sounds to me like your internal storage (memory) is bad. Bottom line is that if you can't format your basic partitions successfully, you will not be able to flash a full ROM. If you don't believe your memory is bad, you can search the 6P forums for the Qualcomm Flash Image Loader (QFIL) & EDL mode. There is a rescue binary for the 6P floating around that some people have been successful in using restoring corrupt partitions, presumably because it works at the hardware level.
Click to expand...
Click to collapse
What should I do from now on? I have no idea what to do. The device has been bricked for 24 hours now.
This is the closest I've found to my problem. Also on a Nexus 6P. https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
I tried adb reboot edl and it says error: closed. So not even that works.
specialk00 said:
What should I do from now on? I have no idea what to do. The device has been bricked for 24 hours now. This is the closest I've found to my problem. Also on a Nexus 6P. https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
I tried adb reboot edl and it says error: closed. So not even that works.
Click to expand...
Click to collapse
Stock fastboot does not support boot to EDL. You need a modified fastboot, BUT getting to EDL mode won't help you until you have all the proper tools and 6P specific files. I don't want to get your hopes up. I think your device is not recoverable due to a hardware issue (bad memory). If you are looking for a learning project to keep you busy with very little hope of success, keep digging. If you need a working phone, you need to buy another one, or a 6P replacement motherboard from a screen damaged parts phone. Unfortunately, there have been many onboard memory failures on the 6P.
I fixed the problem. It turned out to be a faulty USB-C to USB-A cable. The only problems were with file transfer-related commands. I then tried transferring a 1 kb file, then 1 mb (failed) then 200kb, then 300kb (failed). So it turns out the cable is ****ty. Wow. And nothing is corrupted. I'm typing this from my phone now.
I bicked my P9 Lite and need some help with it. The main problem is, that I "accidentally" wiped my vendor and product partitions using TWRP and now I can't fix them anymore. Of course I created no recovery files before... I try to give you as much information as I can:
I have a european P9 Lite L31.
I think VNS-L31C432B130 but im not shure, because fastboot getvar returns just:
Code:
>fastboot oem gevar modelid
...
FAILED (remote: Command not allowed)
finished. total time: 0.008s
I also tried to flash the volumes from a Update.zip (I decompressed using HuaweiUpdateExtractor) via fastboot, but I get the following messages:
Code:
>fastboot flash product product.img
target reported max download size of 471859200 bytes
sending 'product' (112112 KB)...
OKAY [ 3.867s]
writing 'product'...
FAILED (remote: Command not allowed)
finished. total time: 3.889s
However flashing other images (like system or recovery) works.
I also tried to restore my phone by creating a ./dload directory on my sd-card containing the update.app (and other files from the zip) using the original recovery function. However this stops at 5% before my phone reboots.
Trying to repair the partitions by using TWRP > Wipe > Advanced Wipe > [Product/Vendor] > Repair or Change File System had also no success.
Clicking the repair-button gives the following output:
Code:
Updating parition details...
Failed to mount '/ventor' (Invalid argument)
Failed to mount '/product' (Invalid argument)
...done
Full SELinux support is present.
MTP Enabled
Repairing Product using e2fsck...
/sbin/e2fsck -fp process ended with ERROR: 16
Unable to repair Product
Trying to reformat a partition or installing a new OS also fails with the "Failed to mount /[vendor/product]" message.
I am using this Update.zip:
Huawei P9 Lite B382/B383 Nougat Update
(not allowed to post a link)
I really home you guys can help me...
Don't use B382/383 files if you have B130..
Same Problem
I have exactly the same Problem; exept my P9lite doesn't have the ability to "UPTAT.APP" anymore - caused of the stupid ish erecovery.
Did you find a solution?
I would be glad to hear a reply tnx
tmato12 said:
I have exactly the same Problem; exept my P9lite doesn't have the ability to "UPTAT.APP" anymore - caused of the stupid ish erecovery.
Did you find a solution?
I would be glad to hear a reply tnx
Click to expand...
Click to collapse
More info about your phone and FW version pls. Have you TWRP on board? What says bootloader about Phone/FRP ?
bozka1 said:
More info about your phone and FW version pls. Have you TWRP on board? What says bootloader about Phone/FRP ?
Click to expand...
Click to collapse
I have the Huawei p9 lite VNS-L31 with TWRP installed and accesable
it is in following state:
PHONE unlocked
FRP Unlock
but i cant fastboot anymore and this error appears:
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/product' (Invalid argument)
use the dload method via an external sdcard
Hi. I'm french. Have you resolved the problem ?
I'm atleast 51% sure that a flash of Service Repair ROM would fix that... But... Does such a ROM for MM exist?
Maybe the latest one (B381) will work...
Ofcourse flashing product and other partitions won't work. They get installed/updated through the UPDATE.APP (I think that also EliteROM is also doing that). They contain what model is the phone, how should everything be working and etc.