Hello,
I bought an Nvidia schield tablet, but cant seen to find the factory image or an working custom rom to flash trough fastboot.
I have the Nvidiai shield experience iamges from 3.1 to 5.1 and flashed them with fastboot flash recovery ,boot,system and user data even flashed the blob but with every image it just hangs after reboot on the bleu android logo.
can someone please help.
Device
Nvidia shield 8 wifi
no SD card
newest minimal adb fastboot package installed.
Can somebody please help me get pased the iritating bleu android head, i already found the factory image and fastboot flashed it but did not fix it
even did fastboot format system and format userdata but evne that did not help
i want to get this fixed
I got TWRP booting but cant seen to erase or format data and cache partitions , it keeps saying failed to mount /data and /cache (inailid argrument).
Already tried to fastboot erase userdata and cache. did not help
Even in the nvdia recovery i get errors failed to mount /cache (invalid argument) can someone please help me with this i want to get my tablet back up and running.
tread can be clossed by moderator.
Related
Hi there
I wanted to install the Android L developer preview on my Nexus 5. For this I had to unlock the bootlader because it was still locked. That worked fine.
I then downloaded the Android L image for my Nexus 5 tried to install it, got stuck at the google logo and then thought to just roll back to Android 4.4. So I downloaded the factory image from google, switched into fastboot mode, and executed the flash-all.sh script (running on Ubuntu). That seemed to work, device restarted a few times but got stuck on the boot animation logo again.
I wanted to switch into recovery mode to wipe the cache, but the red triangle appears. As quick solution, I just downloaded the clockworkmod-recovery and installed it using the fastboot flash recovery clockworkmod.img command. That worked, I was able to get into the clockworkmod recovery, wiped everything and restarted, but I'm still stuck at the boot animation.
While wiping I had the following messages in the log:
Code:
Formatting /data
Error mountin /data
Skipping format
Formatting /cache
Formatting /sd-ext
E: unknown volume for path [/sd-ext]
Formatting /sdcard/.android_secure
Error mounting /sdcard/.android_secure !
Skipping format..
Data wipe complete.
When rebooting from clockworkmod it asks me if I want to root my device because it seems to be unrooted. I've tried accepting and declining that message, but I can't still boot up my device. Anyone got any idea what might be wrong here?
Thanks alot!
Edit: Allright, somehow, after hours of spending with reflashing, it seemed to work. I can't remember to have done anything special. Only thing I did different was that I executed every command from the flash-all.sh by hand instead of executing the flash-all script.
I at first had a bootloop, when I tried to fix it using adb and fastboot, I by mistake cleared its boot partition, cache partition as well as its system partition also. that means my phone has no os, no CMW no fastboot mode. When i prss power keys and volume combination. nothing happens. I repeat NO OS beacause boot partition wiped, no system partition as system partition has also been wiped..and hence no fastboot mode.....
How to recover from this problem???
Is there any chance to recover????
Hi,
We need to know your device make and model number to point you towards help.
Thanks!
I've had many problems with my cache partition. I was going to try and install a new ROM since my phone was working fine for a while. So I installed TWRP and rooted it. I noticed inside TWRP it said
E:\ Unable to mount cache".
I tried to mount it in TWRP and it wouldn't let me select it. I tried formatting/wiping the cache and it seemed to complete but then it displayed the same error message. After I tried to wipe the cache partition my phone was unable to boot. It was stuck on the swirling balloons before the android logo displays. So I downloaded the cache.img for 5.1 and flashed it. When I gave the command fastboot flash cache.img it starts erasing the cache and gets stuck there. The phone freezes and doesn't do anything until I power it off. So I am unable to flash the cache.img. My phone was stuck in a boot loop and doesn't get fixed into I going into TWRP and input this command from shell:
mkfs.ext2 /dev/block/mmcblk0p27
After I use that command the phone boots fine and everything seems okay. So now my question(s) is, does anyone know what is up with my cache partition? Why doesn't TWRP mount it? And when I do anything with the cache partition my phone stops working.....
I am on stock 5.1 with no custom kernels.
Exactly the same problem , the phone works, but does not wipe the cache , please help:crying:
Anyone have any ideas what is up with my cache partition?
Same here, phone working with no prob, but can't flash anything on twrp: fail with message Unable to mount /cache
Already tried:
-flash cache.img
-fastboot erase/format cache
Curiously, twrp can wipe the cache.
Go into Recovery and do a wipe cache again and wait for it to finish, it could last like 5~30mins so i recommend connecting the charger just in case then you'll be fine. If it doesn't work try with another custom recovery or go back to stock recovery.
This happened to me a while back and to a friend of mine a few weeks back thank god he called me since we both got a N5. :good::highfive:
It's a bug in the latest TWRP... Go back to 2.8.5.3 for the while.
I solved this problem in such a way:
write to the console on the PC or TWRP
PHP:
adb shell
make_ext4fs /dev/block/mmcblk0p27
exit
Now , the cache is working , you can put whatever you want, but do not wipe cache dies again , this command is essentially wipe . Good luck
ZloKira said:
I solved this problem in such a way:
write to the console on the PC or TWRP
PHP:
adb shell
make_ext4fs /dev/block/mmcblk0p27
exit
Now , the cache is working , you can put whatever you want, but do not wipe cache dies again , this command is essentially wipe . Good luck
Click to expand...
Click to collapse
I have been able to boot into TWRP, however my pc doesnt detect the phone. Whats the solution ? No way to backup my data also now.
Hi everyone,
I have a XT1032 with a loop boot (It hangs everytime on the Motorola logo).
First of all I was unable to enter into the recovery mode. And I've unlocked the mobile with the motorola code and flashed with the stock recovery. After that I was able to enter into recovery mode.
I've tried to install a ROM via adb sideload but at the 60% always failed and says me that the package couldn't be validated.
I've tried to wipe the data/cache, also I tried to format the partitions (with cache It has gone OK but formatting the userdata partition tolds me that was unsuccessful due blkdiscard errors)
After that I've tried to flash a new recovery (TRWP and CWM) but unfortunately always said the mismatched partition size error, and It's impossible to flash any recovery (only worked with the stock).
Any idea to recover my XT1032?
Thank you!
Hi i have Moto Maxx 64 GB.... Today i was trying to flash newly released RR rom. When i booted my phone to TWRP Recovery.... it gives an error in logs that
unable to mount /data
unable to mount /cache
unable to mount /firmware
unable to mount /system
Now after erasing cache and userdata from fastboot and then reboot in to recovery data and cache partitions are back but firmware and system partitions are same saying unable to mount /system....
Help needed please
Hi,
Flash stock brazil 5.0.2 firmware with rsd lite, it will be fine.
Can you please give the download link???
https://drive.google.com/file/d/0B8ENz9WTAsk_WFprNVF1RFRFSUk/view
http://forum.xda-developers.com/droid-turbo/development/moto-maxx-moto-turbo-xt1225-factory-t3078274
Stilll no solution... rsd lite fails on 10% and when i flash twrp recovery its now saying unable to mount /firmware........Seems any expert opinion is required or maybe last solution is jtag.....
You cant boot twrp on read-only mode, just swipe when it starts (dont click on read-only option)
You will need to be more specific with the RSD error - it should have no problem fully recovering the phone with stock firmware.