I'm selling my Nexus 7 and I think I got a little click happy while clearing it out.
I had reinstalled 4.3 and then for some reason I formatted the data. Got stuck in a boot loop.
When I try to install the image again I get the following:
Updating partition details...
E:error opening '/data/media'
E:error: no such file or directory
Any help would be appreciated!
"90% of the time, when someone says something's bricked, the only brick is their head." - Koush
All this means is that your userdata partition got all jacked up. It's restored when you boot into a rom, but of course you can't boot into a rom cause something else must have also went awry. So I suggest you wipe everything and start over. Follow along with me, this will be fun!
Boot into fastboot, send fastboot unlock command if your bootloader isn't already unlocked "fastboot oem unlock." Accept on screen. Reboot back into bootloader/fastboot. Issue FASTBOOT ERASE USERDATA, FASTBOOT ERASE RECOVERY, FASTBOOT ERASE CACHE, FASTBOOT ERASE SYSTEM. Then flash TWRP recovery using FASTBOOT FLASH RECOVERY [NAME OF TWRP GROUPER IMG]. Then adb push your rom and gapps back to your tablet using ADB PUSH [FILE] /SDCARD, then flash your rom and enjoy a fresh clean tablet!
That's why I prefixed with 'possible'...
Thanks - I followed this guide later in the evening and got it all up and going again.
http://goo.gl/BsiewY
0vermind said:
"90% of the time, when someone says something's bricked, the only brick is their head." - Koush
All this means is that your userdata partition got all jacked up. It's restored when you boot into a rom, but of course you can't boot into a rom cause something else must have also went awry. So I suggest you wipe everything and start over. Follow along with me, this will be fun!
Boot into fastboot, send fastboot unlock command if your bootloader isn't already unlocked "fastboot oem unlock." Accept on screen. Reboot back into bootloader/fastboot. Issue FASTBOOT ERASE USERDATA, FASTBOOT ERASE RECOVERY, FASTBOOT ERASE CACHE, FASTBOOT ERASE SYSTEM. Then flash TWRP recovery using FASTBOOT FLASH RECOVERY [NAME OF TWRP GROUPER IMG]. Then adb push your rom and gapps back to your tablet using ADB PUSH [FILE] /SDCARD, then flash your rom and enjoy a fresh clean tablet!
Click to expand...
Click to collapse
Turned my Nexus 10 on today and it had an update to 5.02 so I let it download and install it.
Bearing in mind my Nexus 10 is as standard from when I got it completely stock non rooted.
It rebooted and a blank screen was all that appeared. I left it for several minutes and still nothing.
Then i got an android laying on its back with an exclamation mark..
I read about flashing the full image on another thread to resolve this issue
So i went ahead and unlocked my bootloader,
erased everything and flashed everything as below:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-manta-mantamf01.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot erase userdata
fastboot flash userdata userdata.img
echo Press any key to exit...
Now i rebooted it and got the android opened up cog spinning on his back the data sort of dna web thing spinning too for a short while. however after a few minutes the device rebooted and is now stuck with the Nexus boot animation.
any ideas what i can do?
Seeing as you already to have wiped everything on the N10... Try running the factory restore image from Google while in fastboot mode: https://dl.google.com/dl/android/aosp/mantaray-lrx22g-factory-81af84cb.tgz
This will flash a clean image of 5.0.2 onto your N10 for you without needing to know any fastboot commands.
KiraYahiroz said:
Seeing as you already to have wiped everything on the N10... Try running the factory restore image from Google while in fastboot mode: https://dl.google.com/dl/android/aosp/mantaray-lrx22g-factory-81af84cb.tgz
This will flash a clean image of 5.0.2 onto your N10 for you without needing to know any fastboot commands.
Click to expand...
Click to collapse
Thanks for this although i reflashed the Nexus 10 through a USB 2.0 port instead of a USB3 and it came up on its own after a minute or so of the boot animation.
So now i can manually keep my Tablet up to date and backed up.
Hello all,
I left a similar post in a couple other threads, and thought maybe someone here might have some insight into my problem.
Been running AICP rom (no custom kernel except the one that comes with AICP) with f2fs on /data and /cache for several months on 16GB grouper. About a month or so ago, the wife installed a game that wouldn't run on this hardware (King's Paradise Bay), and I uninstalled it. It left a file in /data/data/....etc that couldn't stat in TWRP, so no nandroid backups since then. I figured I'd just backup user data with TiBkp and wipe with fresh install of latest AICP when time permitted.
The other night I noticed the N7 was boot looping, getting to the stage where the boot animation dims. The boot anim would hang and after several seconds the Google unlock splash screen would come up and the N7 would try to boot again.
I can get into TWRP and bootloader with no problem. However, when TWRP comes up, the log shows the red entries for 2 files that can't stat, which has been this way since that game was uninstalled. I cannot seem to wipe *any* partition, and when I attempt to format or wipe userdata in TWRP, the N7 spontaneously reboots. Manually attempting to wipe/format/etc. via FastBoot doesn't work, with error message showing after trying to flash bootloader. Also, I can't change /data or /cache back to ext4. I am able to successfully read, write, and delete files on the N7 via computer USB MTP connection.
If the N7's flash memory has somehow become corrupted, is there a way to completely erase/format/whatever so that this wonderful device can become usable again? Any help would be greatly appreciated.
Thanks in advance.
Hello,
don't flash Bootloader via Fastboot. You should do this commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot erase boot
Trafalgar Square said:
Hello,
don't flash Bootloader via Fastboot. You should do this commands:
Code:
fastboot erase cache
fastboot erase userdata
fastboot erase system
fastboot erase boot
Click to expand...
Click to collapse
Yes, I have attempted all these commands, followed by flashing with either fastboot or TWRP with no success. Fastboot reports success, but partitions are not erased.
I have the same problem. The Nexus Root Toolkit can not flashign. It succeeds only boot TWRP. In TWRP computer sees the files from the tablet.I could not rename and delete. Wipe the TWRP and stock recovery displays the status OK, and the files are deleted. Fastboot shows that uploads, but all files remain unchanged.
Hello!
My nexus 4 started to optimize app on each reloading few days ago. At last reload it stucked on "starting apps". I flashed factory 5.1 rom by default guide("run flash-all"). It not helped, starting apps stuck again. I flashed 4.4, it not helped too.
I find few tips.I tried.
(4.4) lock, unlock bootloader, flash
(4.4) flash twrp, change filesystem of cache to fat, return to ext4, flash
(4.4) flash by update without -w
(4.4) erase all particles by fastboot, flash manually each particle
(4.4) flash by update, go to default recovery and do factory reset
it not helped.
what could happen? What I can do?
Sorry for bad english
Boot into fastboot, issue the commands "fastboot erase userdata", "fastboot erase cache", "fastboot flash userdata usedata.img", use volume button to boot into recovery, perform a factory wipe using stock recovery, and reboot.
The userdata.img file needs to be extracted from the stock ROM.
Hope this helps get the phone booted.
audit13 said:
Boot into fastboot, issue the commands "fastboot erase userdata", "fastboot erase cache", "fastboot flash userdata usedata.img", use volume button to boot into recovery, perform a factory wipe using stock recovery, and reboot.
The userdata.img file needs to be extracted from the stock ROM.
Hope this helps get the phone booted.
Click to expand...
Click to collapse
Thanks, but did not effective: it stuck on boot animation(flying ovals)
It could be a possible hardware problem in that the memory chip is defective.
Try flashing stock ROM with Nexus Root kit. If that ROM fails to start then there is a likely hardware issue
Sent from my Nexus 4 using Tapatalk
Hi,
I have a Nexus 4 which was flashed with Lollipop 5.1.1.
My problem started when, after letting the battery completely drain and then trying to turn the phone on again, I got stuck on the message "Android is starting... optimizing apps" for days. I tried rebooting and factory format with no success.
I also tried formatting it through TWRP, but I got the message "Unable to mount /cache". After that, I tried flashing older factory images but only got my phone to work with the oldest version of jelly bean available by google developers page (4.2.2). After I got it to work, I tried to OTA update it to 4.3, but the same message "Android is starting ... optimizing apps" came back.
I had no other choice but to fastboot format it and flash it again with 4.2.2.
Any ideas on what could possibly be causing this? I thought it might be some problem in the cache partition but haven't found a way to fix it or if it's even possible to. Apparently everything's working with 4.2.2 but I'd love to go back to 5.1.1!
Thanks in advance!
dont dirty flash the factory image. make a clean factory image flash
After flashing stock KK or LP, are you also flashing userdata.img and then booting into stock recovery to format/wipe data before booting the ROM for the first time?
audit13 said:
After flashing stock KK or LP, are you also flashing userdata.img and then booting into stock recovery to format/wipe data before booting the ROM for the first time?
Click to expand...
Click to collapse
Haven't tried that, I'll give it a go and post the results here!
I've also noticed the phone isn't receiving any signal and it doesn't display the IMEI anymore..
The lack of an imei is a definite problem. Try flashing the stock LP or KK ROM and check for the imei.
audit13 said:
The lack of an imei is a definite problem. Try flashing the stock LP or KK ROM and check for the imei.
Click to expand...
Click to collapse
Did a clean factory image flash of Lollipop 5.1.1, booted into twrp recovery (I'm not sure how to go back to stock recovery) to wipe the data and got the following message:
E: UnMount: Unable to find partition for path '/sdcard'
E: Mount: Unable to find partition for path '/sdcard'
Updating partition details...
E: Unable to mount '/cache'
...done
E: Unable to mount '/cache'
Full SELinux support is present
E: Unable to mount '/cache'
E: Unable to mount '/cache'
MTP Enabled
Formatting Data using make_ext4fs function.
Ypu may need to reboot recovery to be able to use /data again.
Updating partition details...
E: Unable to mount '/cache'
...done
After that I rebooted the phone and it's been stuck on bootloop again since then.
When you flash a stock ROM, did you flash the recovery.img? Sometimes, I find that only stock recovery can properly format the cache. When flashing my Nexus 5 to stock from a custom ROM, I get an error message when I boot into stock recovery that the cache has an invalid format. Once I perform a factory wipe, the cache is properly formatted and wiped.
audit13 said:
When you flash a stock ROM, did you flash the recovery.img? Sometimes, I find that only stock recovery can properly format the cache. When flashing my Nexus 5 to stock from a custom ROM, I get an error message when I boot into stock recovery that the cache has an invalid format. Once I perform a factory wipe, the cache is properly formatted and wiped.
Click to expand...
Click to collapse
Yeah, I flashed the images for boot, recovery, system, userdata and cache separately. I'll look up how to get back into stock recovery now and I'll try what you've said!
If recovery.img was flashed, the phone should not have TWRP, it should be a stock recovery. If stock recovery cannot be flashed, this leads to me believe that something is wrong with the memory chip.
audit13 said:
If recovery.img was flashed, the phone should not have TWRP, it should be a stock recovery. If stock recovery cannot be flashed, this leads to me believe that something is wrong with the memory chip.
Click to expand...
Click to collapse
I tried it again, flashed everything including recovery, went into stock recovery mode and wiped the data. Apparently its back to being stuck on bootloop
Use fastbot commands to erase cache and userdata. Then use fastboot to flash the userdata.img file, boot directly to recovery, and wipe again.
audit13 said:
Use fastbot commands to erase cache and userdata. Then use fastboot to flash the userdata.img file, boot directly to recovery, and wipe again.
Click to expand...
Click to collapse
Did it, still stuck on bootloop... Not sure if it can be somehow related but I got this message when I booted into recovery
The recovery screen looks correct because, after flashing userdata.img, you must format in stock recovery.
I am at a loss as to why 4.2.2 works while kk and LP do not.
audit13 said:
The recovery screen looks correct because, after flashing userdata.img, you must format in stock recovery.
I am at a loss as to why 4.2.2 works while kk and LP do not.
Click to expand...
Click to collapse
Ah, thanks for the help, anyway!
If someone else knows what to do.. The phone is now back to the initial message "android is starting... optimizing apps". Kinda of losing hope now
I've done this to my Nexus 5 once, too.
You basically screwed your cache partition.
Boot into the bootloader. Hook the phone up to your pc and open the command prompt.
Enter these commands:
fastboot erase cache
fastboot format cache
fastboot reboot-bootloader
When successful boot into recovery and the errors should be gone.
You should be able to flash a new rom now.
playitlouder said:
I've done this to my Nexus 5 once, too.
You basically screwed your cache partition.
Boot into the bootloader. Hook the phone up to your pc and open the command prompt.
Enter these commands:
fastboot erase cache
fastboot format cache
fastboot reboot-bootloader
When successful boot into recovery and the errors should be gone.
You should be able to flash a new rom now.
Click to expand...
Click to collapse
This got rid of the unable to mount cache error, flashed the rom again but it's still stuck on bootloop :/
thafuchs said:
This got rid of the unable to mount cache error, flashed the rom again but it's still stuck on bootloop :/
Click to expand...
Click to collapse
Okay. Progress
You have probably already nuked all your data. So I would suggest erasing and formatting everything again and then flash the newest factory image.
Enter bootloader again, on your pc do the following:
fastboot erase system
fastboot format system
fastboot erase data
fastboot format data
fastboot reboot-bootloader
Then grab the factory image, open the flash_all.bat file in an text editor (either use windows notepad, or grab notepad++).
You have to "cd" to the directory of your factory image. I would suggest to type "c:" *press enter* then cd *pull the folder that contains the factory image into the command prompt* *press enter*.
If you type "dir" now you should get your factory image directory.
Now just type in every command from the flash_all.bat one by one. Report, if there are any errors.
playitlouder said:
Okay. Progress
You have probably already nuked all your data. So I would suggest erasing and formatting everything again and then flash the newest factory image.
Enter bootloader again, on your pc do the following:
fastboot erase system
fastboot format system
fastboot erase data
fastboot format data
fastboot reboot-bootloader
Then grab the factory image, open the flash_all.bat file in an text editor (either use windows notepad, or grab notepad++).
You have to "cd" to the directory of your factory image. I would suggest to type "c:" *press enter* then cd *pull the folder that contains the factory image into the command prompt* *press enter*.
If you type "dir" now you should get your factory image directory.
Now just type in every command from the flash_all.bat one by one. Report, if there are any errors.
Click to expand...
Click to collapse
Okay, got some errors on the way... trying to erase data failed (Remote: partition table doesnt exist), format data failed too (formatting is not supported for filesystem with type ' '.)
Also, on the last command:
.\fastboot -w update .\image-occam-lmy48t.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
[...]
checking version-bootloader
FAILED
Device version-bootloader is 'MAKOZ10o'
Update requires 'MAKOZ30f'
Rebooted and its now stuck on google logo
Sorry, you should have typed: (it obviously cannot format something that is not there )
fastboot erase userdata
fastboot format userdata
Have you flashed the bootloader?
Have you rebooted after flashing the bootloader?
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
Don't forget to also flash the radio.
These "does not contain" errors are normal.
playitlouder said:
Sorry, you should have typed: (it obviously cannot format something that is not there )
fastboot erase userdata
fastboot format userdata
Have you flashed the bootloader?
Have you rebooted after flashing the bootloader?
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
Don't forget to also flash the radio.
These "does not contain" errors are normal.
Click to expand...
Click to collapse
Okay, I've flashed bootloader, rebooted, flashed radio, rebooted, typed the update command but the checking of bootloader version failed again.. rebooted and its back to being stuck on google logo