Related
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
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
Ideas on what is going on?
I have heard that maybe doing a
Code:
fastboot flash recovery "twrp 3.0.0-1".img
fastboot format userdata
fastboot reboot recovery
might work but i am just wanting to boot it and not wipe my data.
JustusIV said:
Ideas on what is going on?
I have heard that maybe doing a
Code:
fastboot flash recovery "twrp 3.0.0-1".img
fastboot format userdata
fastboot reboot recovery
might work but i am just wanting to boot it and not wipe my data.
Click to expand...
Click to collapse
It should be - fastboot flash recovery twrp-3.0.0-0-angler.img
and, fastboot reboot recovery, is not a command under fastboot.
Don't you have a TWRP backup? Why's it matter if it wipes the data?
Im on stock N.
I just want to boot twrp without flashing but it hangs. I am starting to think its a known issue and will be resolved later.
http://forum.xda-developers.com/apps/supersu/wip-android-n-preview-t3335726
But as TWRP isn't working yet on all N Preview devices either
Click to expand...
Click to collapse
It started acting weirdly after shutting down while it was updating some apps. First, it would only function normally when on the charger (it was really erratic off it, shutting down when turning on the data/wifi).
After one day it got briefly stuck in a bootloop, and afterwards it would just display the Google logo and shutdown (or, if on charger, reaching the "Optmizing apps.." screen, and shutdown).
I attempted a "wipe cache", "Factory Reset", and flashed different stock ROMs using the Skipsoft Toolkit, all for no avail.
Is there anything else that can be done?
I suggest manually flashing each partition, including the userdata.img file. After flashing the userdata.img file, boot directly into recovery from fastboot, factory wipe, reboot. Hopefully, this will allow the phone to boot.
audit13 said:
I suggest manually flashing each partition, including the userdata.img file. After flashing the userdata.img file, boot directly into recovery from fastboot, factory wipe, reboot. Hopefully, this will allow the phone to boot.
Click to expand...
Click to collapse
Thanks. I flashed each partition manually, but it then gives mount erros on mount/cache/recovery/log and the boot never ends. These are the steps I took:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
fastboot flash radio "name of radio"
fastboot reboot-bootloader
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
I also tried directly fastboot -w update "zipfile", but it then shutdowns after booting.
After flashing userdata.img, you boot straight to recovery without trying to boot the rom? For mine phones, it's normal for there to be an cache mount error in recovery. After performing a factory wipe in the stock recovery, everything gets formatted and the phone is able to boot.
audit13 said:
I suggest manually flashing each partition, including the userdata.img file. After flashing the userdata.img file, boot directly into recovery from fastboot, factory wipe, reboot. Hopefully, this will allow the phone to boot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2160124 try this, but be careful
I am not the person having a problem with the nexus 4.
ftkg said:
It started acting weirdly after shutting down while it was updating some apps. First, it would only function normally when on the charger (it was really erratic off it, shutting down when turning on the data/wifi).
After one day it got briefly stuck in a bootloop, and afterwards it would just display the Google logo and shutdown (or, if on charger, reaching the "Optmizing apps.." screen, and shutdown).
I attempted a "wipe cache", "Factory Reset", and flashed different stock ROMs using the Skipsoft Toolkit, all for no avail.
Is there anything else that can be done?
Click to expand...
Click to collapse
oh sorry, bump op
always first post is full-sized so I didn't see
mesaj said:
http://forum.xda-developers.com/showthread.php?t=2160124 try this, but be careful
Click to expand...
Click to collapse
Thanks, but maybe you intended to refer to this? http://forum.xda-developers.com/showthread.php?t=2099784
I'm not sure of the purpose of converting from 8G to 16G of internal storage
ftkg said:
Thanks, but maybe you intended to refer to this? http://forum.xda-developers.com/showthread.php?t=2099784
I'm not sure of the purpose of converting from 8G to 16G of internal storage
Click to expand...
Click to collapse
This is the same, I posted for N4 which is basically the same as G but G is more detailed. Try it it should format your device, helped me after similar brick issue. Btw. I used NRT instead Skipsoft.