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?
Related
Wanting to go back to stock on the nexus 7. I have downloaded the factory image but for the life of me cannot figure out how to flash it. I am in the bootloader and i've extracted the image to my adb and fastboot directory. there is a "flash-all.sh" file but I'm unsure what to do with it. Any help would be appreciated. Thanks.
I personally don't remember how to use the .sh files.
But open the file with a text editor such as Notepad++, and you'll see the commands the script will run. You can run them manually.
sh files are purely for Linux users (it's the equivalent of batch files in Windows). Just run the commands in the sh file in your command prompt (or alter them so that it matches your fastboot).
I downloaded the images and looked at the script. Here is what it does.
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
<Wait for it to reboot>
fastboot -w update image-nakasi-jrn84d.zip
And you're done.
Thanks to all three of you. I am now back to stock. I appreciate the help at this crazy hour in the morning.
chris.wueste said:
Thanks to all three of you. I am now back to stock. I appreciate the help at this crazy hour in the morning.
Click to expand...
Click to collapse
Help asap....trying to flash stock file... in adb, I've typed all fast boot commands...I get an error at the " boot loader boot loader grouper" command. It says error, cannot load etc.
gmen78 said:
Help asap....trying to flash stock file... in adb, I've typed all fast boot commands...I get an error at the " boot loader boot loader grouper" command. It says error, cannot load etc.
Click to expand...
Click to collapse
Are you still stuck? What is going on at the moment? What have you tried? PM me if you would rather.
Ya I'm still stuck....tried using wugfresh toolkit to get back to stock but drivers ain't working correctly. I'd rather just flash stock Google image if possible and be done.
Sent from my Galaxy Nexus using Tapatalk 2
Can you use ADB and Fastboot???
Do you know how to use ADB and Fastboot???
If you are stuck returning to stock, I have just posted a full guide in the development section. I just did it myself to make sure that it works. Enjoy.
How to get Stock kernel back to get nexus 7 ota updates
i once used DR BEATS audio mod it is not installed now but still i cannot install OTA update which i still repent installing that mod
The easiest way for you would be to do the update manually:
- Get the factory image and extract the following files:
- bootloader-grouper-4.23.img
- boot.img
- system.img
If you want to keep root, get
- UPDATE-SuperSU-v1.51.zip
and copy it to /sdcard and be sure, that you have a custom recovery installed.
Do a nandroid backup before starting and then do a
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
reboot into recovery and flash UPDATE-SuperSU-v1.51.zip
Do a reboot system and, congrats, you should be on Android 4.3 without loosing any data.
AndDiSa said:
The easiest way for you would be to do the update manually:
- Get the factory image and extract the following files:
- bootloader-grouper-4.23.img
- boot.img
- system.img
If you want to keep root, get
- UPDATE-SuperSU-v1.51.zip
and copy it to /sdcard and be sure, that you have a custom recovery installed.
Do a nandroid backup before starting and then do a
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash system system.img
reboot into recovery and flash UPDATE-SuperSU-v1.51.zip
Do a reboot system and, congrats, you should be on Android 4.3 without loosing any data.
Click to expand...
Click to collapse
Can you guide me how to fastboot flash is it in cwm custom recovery or i need to do that with wugfresh toolkit
Sent from my Nexus 7 using Tapatalk HD
Neither you need a PC to do it. Read about both adb and fastboot instead of having everything spoon fed. That way when something goes wrong you have some idea what to do.
Sent from my Nexus 7 using Tapatalk 4 Beta
I used the WonderHowTo site incorrectly to flash a nexus 5 version of twrp unto my nexus 4.
My device at this point booted to a blank screen. It could still boot the boot loader at this point.
To "fix" this I found the correct version of twrp for my device and proceeded to flash that unto my device.
This has appeared to work since I can access twrp on my device but it is only thing I can access on the phone. When I attempt to boot to system through twrp I am sent back into twrp.
I have attempted to use the wugfresh root tool kit to unroot and return to stock using both soft bricked and phone is still working normally options with no success.
It can still boot to the boot loader currently.
I have logs from the toolkit if these can shed more light on my issue.
Is there anyway I can return my device to stock? Thanks for any response
Flash factory image
https://developers.google.com/android/nexus/images#occam
attempted
attempted to flash stock and got the following error message
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
Seems like you flashed TWRP to /boot. Easy fix is to download your ROM zip. Extract the boot.img and "fastboot flash boot boot.img". Then flash TWRP with "fastboot flash recovery twrp.img"
The locations and filenames of the files may vary. But hopefully you get the idea.
codebam said:
Seems like you flashed TWRP to /boot. Easy fix is to download your ROM zip. Extract the boot.img and "fastboot flash boot boot.img". Then flash TWRP with "fastboot flash recovery twrp.img"
The locations and filenames of the files may vary. But hopefully you get the idea.
Click to expand...
Click to collapse
I flashed a boot image for mako_KTU84P and flashed recovery again with twrp but I'm still system booting into twrp.
My bootloader version is MAKOZ30f if that is any help
I probably flashed the incorrect boot image. Could you point me in the direction of reliable ROM zip's if that is the case.
MrTalk said:
I flashed a boot image for mako_KTU84P and flashed recovery again with twrp but I'm still system booting into twrp.
My bootloader version is MAKOZ30f if that is any help
I probably flashed the incorrect boot image. Could you point me in the direction of reliable ROM zip's if that is the case.
Click to expand...
Click to collapse
Okay adb push a cyanogenmod zip from here and flash it in recovery. It should automatically install a working boot image. You should also flash the latest bootloader in the factory image with "fastboot flash bootloader bootloader.img" if you're using an outdated bootloader.
used the advice
I pushed the zip file using cmd and it appears to have been successful since I was given the summary of data transferred and how long it took once the process was finished.
I can't find the zip file in twrp to attempt to flash it.. Is there any reason the file name would change inside the device once it has been pushed?
Is there a way to flash the zip in question without pushing it unto the device?
as the tittle says... i am soft-bricked, stuck on google animation.. I did a install of the full android rom 1.4 from zulu99 and everything worked like a champ but i wanted to go back to stock for the kids and now i am stuck
I can access fastboot and recovery on the device and compute recognizes it also..
I downloaded the stock image for marsh 3.2.0 and i flashed all the required files:
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
it reboots and goes to the google animation and it just stays there!!!(left it there for a day!!!) i also tried to flashing fastboot flash tegra210-foster-e-p2530-0930-e02-00.dtb and did not fix it..
also tried to flash 3.1.0 same steps and no go... i know my adb files are up to date... any ideas?
I was able to flash full android 1.4 from zulu again and works like a champ but i need stock for the kiddos.
try flashing twrp recovery from there wipe system and data partition then reboot into fastboot flash 3.2 again
i was stuck at the boot animation about a month ago after the 3.2 update.... see my post in this thread:
http://forum.xda-developers.com/shi...ion-screen-t3263143/post67564062#post67564062
please note: i used the 3.1 recovery image because the 3.2 image had not been released yet. have not tried it with the newer 3.2 image
also, if you follow my post and install the 3.1 image....be sure to flash the files in the order posted! some will flash quickly, but one or two took awhile to complete, so be patient and wait for each step to finish before moving on to the next.
yes, i saw ur post and how you solved it and i did try the same thing and it did not fix it.. it just gets me to the animation screen... i am gonna try to load twrp from fastboot, wipe.. then re install everything and once done, i will try to fastboot -w and see if that helps me...
foomanjackel said:
i was stuck at the boot animation about a month ago after the 3.2 update.... see my post in this thread:
http://forum.xda-developers.com/shi...ion-screen-t3263143/post67564062#post67564062
please note: i used the 3.1 recovery image because the 3.2 image had not been released yet. have not tried it with the newer 3.2 image
also, if you follow my post and install the 3.1 image....be sure to flash the files in the order posted! some will flash quickly, but one or two took awhile to complete, so be patient and wait for each step to finish before moving on to the next.
Click to expand...
Click to collapse
lalord69 said:
yes, i saw ur post and how you solved it and i did try the same thing and it did not fix it.. it just gets me to the animation screen... i am gonna try to load twrp from fastboot, wipe.. then re install everything and once done, i will try to fastboot -w and see if that helps me...
Click to expand...
Click to collapse
if you un pack the nvidia recovery image there is a scipt inside caled flashall.bat one of the steps run in there is a reboot to fastboot after you flash the boot.image
flash staging blob
fastboot flash boot boot.img
fastboot reboot
adb wait-for-device
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
echo Press any key to exit...
pause >nul
exit
I have Oreo 27-12-2017 installed on my mi a1, I downloaded the official update.zip file to be installed via adb sideload
I was having TWRP recovery installed but i changed it to Stock recovery to install oreo via adb sideload, but I an't do it it always give me error and phone keep restarting, anyone have an idea how to install it via adb sideload ?
Sideload din't work for me with any OTA update, but I got also at a ceratin point a bootloop. It was solved by downloading the latest fastboot ROM from the xiaomi site. Download the tgz, extract it and use the flash_all_except_storage.sh (mac/linux) or the .bat for windows.
You will then have nougat but at least it solved the issue without data loss. I think that articles about updating via stock recovery and adb are not working at all. Also a lot of articles found via google are kind of fake. A lot say to flash the boot.img via "fastboot flash boot boot.img" but the official .bat and .sh file say that its done via:
fastboot flash boot_a boot.img and fastboot flash boot_b boot.img
pmmtch said:
Sideload din't work for me with any OTA update, but I got also at a ceratin point a bootloop. It was solved by downloading the latest fastboot ROM from the xiaomi site. Download the tgz, extract it and use the flash_all_except_storage.sh (mac/linux) or the .bat for windows.
You will then have nougat but at least it solved the issue without data loss. I think that articles about updating via stock recovery and adb are not working at all. Also a lot of articles found via google are kind of fake. A lot say to flash the boot.img via "fastboot flash boot boot.img" but the official .bat and .sh file say that its done via:
fastboot flash boot_a boot.img and fastboot flash boot_b boot.img
Click to expand...
Click to collapse
fastboot flash boot boot.img is the same as fastboot flash boot_a boot.img and fastboot flash boot_b boot.img. You would use the two commands to flash different boot images to different partitions because as you know our device is divided into 2 partitions because of the seamless update