Hello.
I ran fastboot oem unlock on my N10 and then ran superboot. However it would not boot up again. I keep trying to flash the factory system.img but it just gets stuck for hours, not doing anything.
I can flash recovery, boot perfectly fine, just not system.
I can however access /system if I format it via recovery, but the factory image format is not in a flashable zip so I can't flash it via recovery. Have i bricked my N10?
EDIT: Managed to fix it, my Mac Fastboot did not have fastboot format, but my Windows fastboot did, and running fastboot format system seemed to fix it. Please close.
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
I was using 5.0.1, with stock bootloader, stock recovery, actually stock everything except SuperSU added.
I downloaded the 5.1 image from Google, and tried flashing it:
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.06.img
fastboot reboot-bootloader
fastboot update image-occam-lmy47o.zip
Got some missing sig errors, and "failed to allocate xxxxxxxxx bytes" error. Thus after searching for more information I ended up unpacking image-occam-lmy47o.zip and running:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
Then rebooted. The result is an endless boot animation, regardless of anything I try. Tried restoring my TWRP backup, reflashing 5.1, reflashing 5.0.1, always the same. Last logcat line at boot:
E/kickstart( 233): Sahara protocol completed
Then it's just stuck there. For minutes. For tens of minutes. Looks like forever. Anyone else ever seen this problem, and happens to have a solution? (Preferably without losing my data)
Edit: After a few hours I restored the original (or so I hope) state, by wiping, then flashing 5.0.1, then restoring my backup. But now I don't dare to try flashing 5.1 again. Still would love to hear ideas from who might have seen this problem and knows a solution.
After you've flashed the factory image boot into the stock recovery and do a factory reset.
Sent from my Nexus 9 using XDA Free mobile app
IVBela said:
I was using 5.0.1, with stock bootloader, stock recovery, actually stock everything except SuperSU added.
I downloaded the 5.1 image from Google, and tried flashing it:
fastboot flash bootloader bootloader-mako-makoz30f.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.06.img
fastboot reboot-bootloader
fastboot update image-occam-lmy47o.zip
Got some missing sig errors, and "failed to allocate xxxxxxxxx bytes" error. Thus after searching for more information I ended up unpacking image-occam-lmy47o.zip and running:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cache cache.img
Then rebooted. The result is an endless boot animation, regardless of anything I try. Tried restoring my TWRP backup, reflashing 5.1, reflashing 5.0.1, always the same. Last logcat line at boot:
E/kickstart( 233): Sahara protocol completed
Then it's just stuck there. For minutes. For tens of minutes. Looks like forever. Anyone else ever seen this problem, and happens to have a solution? (Preferably without losing my data)
Edit: After a few hours I restored the original (or so I hope) state, by wiping, then flashing 5.0.1, then restoring my backup. But now I don't dare to try flashing 5.1 again. Still would love to hear ideas from who might have seen this problem and knows a solution.
Click to expand...
Click to collapse
You only really need to flash the following (unless there is a new bootloader and radio):
fastboot flash boot boot.img
fastboot flash recovery recovery.img (if you are running custom recovery you can skip flashing this)
fastboot flash system system.img
metpage said:
You only really need to flash the following (unless there is a new bootloader and radio):
fastboot flash boot boot.img
fastboot flash recovery recovery.img (if you are running custom recovery you can skip flashing this)
fastboot flash system system.img
Click to expand...
Click to collapse
There was a new radio, but that worked (I accidentally booted normally after flashing it). The rest is the same that I did, except the cache, guess next time I'll try doing it without flashing that one. Do I not have to wipe the cache partition either? (And no custom recovery here, I boot TWRP from my PC via fastboot.)
Edit: Who understands this.... I tried it again tonight, flashed radio, then fastboot update image-occam-lmy47o.zip worked, no error this time, no unpacking, nothing. Just a successful update this time.
Guess that wipe was needed, maybe something was already corrupted before I tried flashing the first time.
Case closed.
I just try to root my new nexus player and I don't know what happened there.
After success installation tried to install SuperSu and rebooted it. And device still loading I don't know why?
I did it in MAC OSX Yosemite
I have this screen already 4 hours
What should I do here
Not dead, it just bootloops (softbrick)
Get familiar with fastboot and bootloader mode
google or youtube on how to start the nex player in bootloader mode.
Download the latest image from Google here https://developers.google.com/android/nexus/images#fugu
Untar and unzip the .img files. You should be able to flash the system via fastboot
Command is:
fastboot flash system "path/to/system.img"
I tried Chainfires root method and the same thing happened to me, I don't think he's updated root for 5.1.1 yet. Using ADB
Download the image from above and follow the commands in terminal. They all start with ./
fastboot flash bootloader <drag bootloader image from finder to here>
fastboot reboot-bootloader
sleep 5
fastboot -w update <drag image zip from finder here>
tomalak007 said:
fastboot -w update <drag image zip from finder here>
Click to expand...
Click to collapse
You can do this command without the -w flag and it'll leave your /data/ partition intact. That usually fixes things. Then you can boot chainfire's root image to get root back. But updating the binaries will get you stuck at the boot screen. I actually had to go through this myself when I flashed the 5.1.1 factory image.
Right after booting from the root image, i had a similar problem. I turned it off and turned it back on and it worked. Chances are you either flashed boot.img or system.img so i don't think you should have a problem reflashing if you still can't boot after restarting. Also you may need to wipe in recovery.
i am having same problem also please tell us how to fix this .
Not dead. Which guide did you follow?
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.
I recently updated to 5.2 and everything seemed to be fine andworked. A few days later, the device was in a boot loop. I downloaded the Stock Rom from nVidia site (NVIDIA SHIELD ANDROID TV Recovery OS Image 5.2.0 2017/06/15) and flash it using the following commands:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
Everything flashed fine, but the device is still in a boot loop. Any suggestions?
Thanks!
vuser74 said:
I recently updated to 5.2 and everything seemed to be fine andworked. A few days later, the device was in a boot loop. I downloaded the Stock Rom from nVidia site (NVIDIA SHIELD ANDROID TV Recovery OS Image 5.2.0 2017/06/15) and flash it using the following commands:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
Everything flashed fine, but the device is still in a boot loop. Any suggestions?
Thanks!
Click to expand...
Click to collapse
Flash TWRP, make a Full Wipe, Restart to the bootloader and flash the Stock Rom again.
LM209 said:
Flash TWRP, make a Full Wipe, Restart to the bootloader and flash the Stock Rom again.
Click to expand...
Click to collapse
Thanks for the great suggestion. I'll remember this for next time. I ended up RMA the device.