Related
fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
sellength said:
fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
Click to expand...
Click to collapse
Wrong section, this is for development only.
As for your question, I do not understand what you are asking, what are you attempting to do with fastboot mode?
xIC-MACIx said:
Wrong section, this is for development only.
As for your question, I do not understand what you are asking, what are you attempting to do with fastboot mode?
Click to expand...
Click to collapse
the development section. only dev question ? ok
sellength said:
fastboot mode erase * and fastboot flash all image files。
in about system update.install ota file. restart error
:crying::crying::crying:
Click to expand...
Click to collapse
If you have the factory image, from Google (and nowhere else), just run the flash-all.bat file. You "may" have to unlock your bootloader prior to running it if you haven't already, and you'll need to have the device in fastboot mode prior to running the batch file too, but once those 2 simple tasks are done, the batch file takes care of the rest.
If your using a toolkit or some other method for flashing a factory image, I suggest stopping, and just doing the above.
This forum is not for any threads for questions... this needs to go to General or Q/A... just download the factory image from Google, reboot into fastboot and run the flash-all script... you don't need to be unlocked...
craigacgomez said:
This forum is not for any threads for questions... this needs to go to General or Q/A... just download the factory image from Google, reboot into fastboot and run the flash-all script... you don't need to be unlocked...
Click to expand...
Click to collapse
If im on 4.2 and my device fails to update to 4.2.1, saying me error on recovery, should I only unzip the image from google, put my n10 on fastboot mode and run the flash all script as you said? Will this erase my data? Im just root, haven't unlocked my bootloader.
Sorry for my english
lKBZl said:
If im on 4.2 and my device fails to update to 4.2.1, saying me error on recovery, should I only unzip the image from google, put my n10 on fastboot mode and run the flash all script as you said? Will this erase my data? Im just root, haven't unlocked my bootloader.
Sorry for my english
Click to expand...
Click to collapse
same question
I've unlocked & rooted & the OTA fails trying to flash the recovery (trying to flash from twrp, duh, can't overwrite).
How should I go about updating the system w/o wiping out everything I already have?
If I fastboot flash_image system will it only overwrite changes to my system partition & leave my data & apps alone?
I've got OTA Root Keeper installed, so I'm hopeful even if I lose root I can get it back easy enough (either way, no biggie; can always reroot, ain't no thang).
tia for any advice.
edit: f-bomb... no 4.2.1 img available for N10 yet...
Sent from my Nexus 10 using xda premium
dboftlp said:
same question
I've unlocked & rooted & the OTA fails trying to flash the recovery (trying to flash from twrp, duh, can't overwrite).
How should I go about updating the system w/o wiping out everything I already have?
If I fastboot flash_image system will it only overwrite changes to my system partition & leave my data & apps alone?
I've got OTA Root Keeper installed, so I'm hopeful even if I lose root I can get it back easy enough (either way, no biggie; can always reroot, ain't no thang).
tia for any advice.
edit: f-bomb... no 4.2.1 img available for N10 yet...
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
There is... i've seen a post in google + from a guy that links you to a google page with n10 4.2.1 img.
sikagoon7 said:
Nexus 10 hasn't gotten the (JOP40D) images yet which means the only way to get the 4.2.1 update is to get an OTA. I think the OTA link is floating around AndroidPolice and AndroidCentral somewhere but you'll have to look. Whatever images for 4.2.1 on the Nexus 10 are fake because Google hasn't even released them yet.
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
yep, & therein lies the problem. I can't seem to flash the OTA b/c I'm getting recovery errors...
when I tried flashing stock recovery I just get red exclamation
:-\
Sent from my Nexus 10 using xda premium
dboftlp said:
yep, & therein lies the problem. I can't seem to flash the OTA b/c I'm getting recovery errors...
when I tried flashing stock recovery I just get red exclamation
:-\
Sent from my Nexus 10 using xda premium
Click to expand...
Click to collapse
So what are you gonna do? I want to have the 4.2.1 and be able to update my n10 with the uncoming otas, I dunno what should I do now, im kinda stuck..
lKBZl said:
So what are you gonna do? I want to have the 4.2.1 and be able to update my n10 with the uncoming otas, I dunno what should I do now, im kinda stuck..
Click to expand...
Click to collapse
Flash stock recovery .... and get the OTA, then re-flash TWRP ....
You may have to re-root ...
Watcher64 said:
Flash stock recovery .... and get the OTA, then re-flash TWRP ....
You may have to re-root ...
Click to expand...
Click to collapse
I already have stock recovery... it's not about the recovery, I think it's because i put aosp browser instead of the default one, and when ota check system/apps, it finds something has changed. Also may be due to the root?
lKBZl said:
I already have stock recovery... it's not about the recovery, I think it's because i put aosp browser instead of the default one, and when ota check system/apps, it finds something has changed. Also may be due to the root?
Click to expand...
Click to collapse
I don't see how that would matter, I used the aosp browser as well, and all I did was put stock recovery back on ..
hmmmm
Maybe you should just flash one of the updated stock/rooted roms in the dev section.
I got a Nexus 4 today. It is currently on 4.3. I've rooted the phone and installed TWRP recovery. I tried flashing the 4.4 zip and I get a failed message. I can't figure out why. Can someone help?
Yes.
Don't even bother trying to figure out why. You just got the phone. Flash the factory images for 4.4.2.
Not sure why you would get a phone and root it / modify it first, instead of just updating.
But anyways. Your bootloader is already unlocked. Flash factory images. Reroot and do whatever you want after.
albundy2010 said:
Yes.
Don't even bother trying to figure out why. You just got the phone. Flash the factory images for 4.4.2.
Not sure why you would get a phone and root it / modify it first, instead of just updating.
But anyways. Your bootloader is already unlocked. Flash factory images. Reroot and do whatever you want after.
Click to expand...
Click to collapse
It wouldn't update. I thought about doing that first but it said the update was "waiting to download". Where can I get the factory image to 4.4.2?
ILowry282 said:
It wouldn't update. I thought about doing that first but it said the update was "waiting to download". Where can I get the factory image to 4.4.2?
Click to expand...
Click to collapse
The "factory image" from google is a tgz file. Not a zip file. WTF?
Factory images are flashed with fastboot, not a custom recovery or stock recovery.
Extract that file. Take everything that comes out and put it in your directory that has fastboot in it.
Put the phone in fastboot..... Run the flashall. Bat
That will wipe everything off the phone and put stock on it. If you don't want it to wipe your data ( not sure why you wouldn't since you just got it and probably don't have all your junk on it...) you can edit that script by removing the - w part in it.
It's very simple.
albundy2010 said:
Factory images are flashed with fastboot, not a custom recovery or stock recovery.
Extract that file. Take everything that comes out and put it in your directory that has fastboot in it.
Put the phone in fastboot..... Run the flashall. Bat
That will wipe everything off the phone and put stock on it. If you don't want it to wipe your data ( not sure why you wouldn't since you just got it and probably don't have all your junk on it...) you can edit that script by removing the - w part in it.
It's very simple.
Click to expand...
Click to collapse
Haha! Simple maybe for you. What exact commands to I type in terminal (I have a mac)? I know all commands need to start with ./fastboot-mac
ILowry282 said:
The "factory image" from google is a tgz file. Not a zip file. WTF?
Click to expand...
Click to collapse
Unzip the file with 7zip. Run the flash -all file. Let it do its magic.
Sent from my Nexus 4 using Tapatalk
badboy47 said:
Unzip the file with 7zip. Run the flash -all file. Let it do its magic.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I get a text file.
It's a script which is text. If it doesn't run automatically in terminal or bash ( whatever the hell they call it these days on osx) then make it run with it
As long as your fastboot file itself is there it will run.
I think you need to be completely stock (other than unlocked bootloader) to receive OTA updates.
I was on CM10.2 and needed to return the phone to stock. I flashed back to stock 4.3 and was able to update to 4.4.2 with no problems.
After attempt at installing software update to Nexus 10 tablet will not boot. Have wiped Cache and even then did a factory reset. Nothing. Google appears and then twirling colorful dots and nothing. For hours just twirling dots., Samsung and Google and Best Buy geeks says nothing they can do. No longer under warranty but very upset since tablet was working great until update. I am not very tech savvy but can anyone help or do I just have a new paperweight? Thanks for any advice.
I have not made any modifications to the tablet.
Just flash the newest factory image. Get it and the instructions to flash it from here:
https://developers.google.com/android/nexus/images
yes flash the newest image
After getting a notification of the latest update I went and rebooted for the update to install but it went to the twrp recovery and nothing happens, is there a way to install the update?
VivaErBetis said:
Just flash the newest factory image. Get it and the instructions to flash it from here:
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Gibbothegreat said:
After getting a notification of the latest update I went and rebooted for the update to install but it went to the twrp recovery and nothing happens, is there a way to install the update?
Click to expand...
Click to collapse
Still having proble? what is your recovery ? stock? did you update the bootloader? depending on your answer I should be able to help you out, thx
Khaon said:
Still having proble? what is your recovery ? stock? did you update the bootloader? depending on your answer I should be able to help you out, thx
Click to expand...
Click to collapse
Hi Khaon, I have stock lollipop version 5.1.1 . (LMY47V) and latest twrp version. When upgrading it restarts and goes to recoverys main screen.
BTW how can I check which version my bootloader is?
same problem
VivaErBetis said:
Just flash the newest factory image. Get it and the instructions to flash it from here:
as a newbie .I'm not allowed to reference your link !!
I rooted my nexus 10 using xda instructions., installed CWM. All good. I tried backup and recovery and screwed something up in recovery. Got stuck in recovery mode reboot loop. Many gyrations, no fix, so I tried factory reset. Still no fix.
I decided to install a new version of the OS using the Mantaray tar you reference above. UBS connecting and fastboot. All messages look good. Now I have the problem reported in this thread. Stuck with flying balls and no boot. Very interested in any suggestions you may have.
Click to expand...
Click to collapse
Gibbothegreat said:
Hi Khaon, I have stock lollipop version 5.1.1 . (LMY47V) and latest twrp version. When upgrading it restarts and goes to recoverys main screen.
BTW how can I check which version my bootloader is?
Click to expand...
Click to collapse
So you keep just boot looping into twrp, right ?
Did you try installing a custom ROM through adb or just connecting your device?
If it keeps boot looping you gotta to wipe the full storage.
Khaon said:
So you keep just boot looping into twrp, right ?
Did you try installing a custom ROM through adb or just connecting your device?
If it keeps boot looping you gotta to wipe the full storage.
Click to expand...
Click to collapse
No, on a normal reboot or a shutdown/restart it's fine no problems there but when I try to install the update via system update it reboots into twrp. I attach a pic of my system.
Gibbothegreat said:
No, on a normal reboot or a shutdown/restart it's fine no problems there but when I try to install the update via system update it reboots into twrp. I attach a pic of my system.
Click to expand...
Click to collapse
Oh I see, well, you should just flash a custom ROM or if you want to stay with official factory images, you should just follow instruction there:
https://developers.google.com/android/nexus/images
What you do need is just have fastboot executable once you are into the bootloader.
You can easily access the bootloader from twrp : shutdown > reboot into booatloader
Cool thx for your continued help :good:
The problem is due to your attempting an OTA update with a custom recovery (TWRP). You can only do OTA with stock recovery. Once you are in this situation, your easiest way out of it is to simply apply the latest factory image using "fastboot", but this will also wipe your user data so backup any photos, music, etc. before you start. You will also have to reload programs from Playstore once the new image is installed.
Does anyone have a clean flashable zip for Android 7.0 because I have tried to flash for Nexus 6P? because I tried to flash with the factory image that provided by google on this page :https://developers.google.com/android/nexus/images#angler
when I clicked on flash-all.bat keep getting waiting for devices no mater what I do reboot, re-plugged, nothing changed so i'm very desperate right now, I wiped everything in my phone. Please help. :crying::crying:
Edit: or if you can help me with the current problem, please help me.
thank you
HerySean said:
Does anyone have a clean flashable zip for Android 7.0 because I have tried to flash for Nexus 6P? because I tried to flash with the factory image that provided by google on this page :https://developers.google.com/android/nexus/images#angler
when I clicked on flash-all.bat keep getting waiting for devices no mater what I do reboot, re-plugged, nothing changed so i'm very desperate right now, I wiped everything in my phone. Please help. :crying::crying:
Edit: or if you can help me with the current problem, please help me.
thank you
Click to expand...
Click to collapse
There are no factory image flashable zips, as those have to be unpacked and flashed as individual partitions. However, there are OTA zips that you can sideload via ADB. If you're looking for a full Nougat factory image that you can flash with TWRP, you won't find it.
The index of all Nougat factory images and OTA updates are at http://www.xda-developers.com/facto...nexus-going-live-updated-with-nexus-6p-links/ and the OTA is listed down the page ... https://dl.google.com/dl/android/aosp/angler-ota-nrd90u-519758d5.zip
Finally, and most importantly for you, you need to be stock MM (right down to stock recovery) to apply a factory OTA via sideload. For a factory image update, you're actually much better off unpacking the factory image and flashing all partitions via fastboot, by following Heisenberg's guide. This would be the way to go right now, provided you have no problem booting into your bootloader.
The OTA can be quite normal flash with TWRP, without sideload
The simplest way out of your predicament would be to download nexus root toolkit here http://www.wugfresh.com/. This will let you flash stock, it will download all the files for you.
I am still trying to figure out what so urgent about it?!
You probably don't have ADB drivers installed or you're not in bootloader mode.
No need to make a big fuss about such tiny thing.
tommyg562000 said:
The simplest way out of your predicament would be to download nexus root toolkit here http://www.wugfresh.com/. This will let you flash stock, it will download all the files for you.
Click to expand...
Click to collapse
Can you tell me what to do with this application in bootloop situation? because right now my phone is in boot loop, I tried to restore the backup but when it goes to about 50% of progress it automatically reboot in went in boot loop. :crying:
wizardwiz said:
I am still trying to figure out what so urgent about it?!
You probably don't have ADB drivers installed or you're not in bootloader mode.
No need to make a big fuss about such tiny thing.
Click to expand...
Click to collapse
Actually I did install ADB driver, but it still doesn't work, right now my phone is in bootloop for 2 days and I can't do and don't know what to do about it
OK
1. Push the power button until your device is turned off.
2. after a minute or so, power on the device holding at the same time " Volum DOWN + POWER" until the device will turn on and you will see the FastBoot screen, then let go of the two buttons
3. While in Fastboot mode, make sure your PC manage to "see" your device. If it does, then move on . If it doesn't something is wrong with your ADB drivers and you need to fix this before moving on.
4. Assuming your ADB drivers are installed properly, you have three choices:
4.1 Make a clean install using the Google Factory Image Which will result in a lose of all user data and you will probably have a functioning device.
4,2 Use a toolkit such as Wugfresh's one and restore to a clean Install just as in section 4.1
4.3 You can try and change the flash-all.bat file that comes with Google factory images and remove the "-w" from the last line of the file. That will keep your data and will refresh your OS.
There you go.
HerySean said:
Does anyone have a clean flashable zip for Android 7.0 because I have tried to flash for Nexus 6P? because I tried to flash with the factory image that provided by google on this page :https://developers.google.com/android/nexus/images#angler
when I clicked on flash-all.bat keep getting waiting for devices no mater what I do reboot, re-plugged, nothing changed so i'm very desperate right now, I wiped everything in my phone. Please help. :crying::crying:
Edit: or if you can help me with the current problem, please help me.
thank you
Click to expand...
Click to collapse
Reinstall drivers again and see if the waiting for device issue is gone !
wizardwiz said:
OK
1. Push the power button until your device is turned off.
2. after a minute or so, power on the device holding at the same time " Volum DOWN + POWER" until the device will turn on and you will see the FastBoot screen, then let go of the two buttons
3. While in Fastboot mode, make sure your PC manage to "see" your device. If it does, then move on . If it doesn't something is wrong with your ADB drivers and you need to fix this before moving on.
4. Assuming your ADB drivers are installed properly, you have three choices:
4.1 Make a clean install using the Google Factory Image Which will result in a lose of all user data and you will probably have a functioning device.
4,2 Use a toolkit such as Wugfresh's one and restore to a clean Install just as in section 4.1
4.3 You can try and change the flash-all.bat file that comes with Google factory images and remove the "-w" from the last line of the file. That will keep your data and will refresh your OS.
There you go.
Click to expand...
Click to collapse
Worked, thank you.
HerySean said:
Worked, thank you.
Click to expand...
Click to collapse
Glad to hear you have managed to revive your device.
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
nhatminhng said:
Hey guys, I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Fastboot format your partitions and use flash-all.bat with a stock Google image.
nhatminhng said:
Hey guys,
This afternoon I tried to change my file system fo f2fs, I failed and got into bootloop. Follow some instructions, I flash the factory image (I was using stock 7.1.1 Feb and EX Kernel before trying f2fs) but I still face the bootloop. As I know this is a softbrick, because I can still boot into bootloader and flash recovery. But no matter how I try (flash stock, flash rom cook, flash older stock)...my 6P is still in the bootloop. I check in the TWRP that my phone is still in ext4, not f2fs anymore.
I really need some advice to wake him up. Really appreciate your help.
Click to expand...
Click to collapse
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
MidnightDevil said:
In all honesty bro, I never noticed much difference if any with ext4 vs f2fs. On another note, what kernel and ROM did you flash with f2fs? The the version that supports f2fs gives bootloops when you flash a custom kernel with that recovery. Try flashing the official version of recovery, reboot, then ROM and kernel if you wish and try again.
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
jhs39 said:
Why do you still have TWRP if you flashed stock? You need to flash the complete stock image including the stock recovery.
Click to expand...
Click to collapse
v12xke said:
Fastboot format your partitions and use flash-all.bat with a stock Google image.
Click to expand...
Click to collapse
Thanks guys for helping. I fixed it.
I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps
fastboot format system
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
nhatminhng said:
Thanks guys for helping. I fixed it. I always flashed the stock image step by step followed by heisenberg, and never use the flash-all.bat just because I dont understand how to run it. However a guy in the f2fs told me to add in some steps And it works. It seems like the step by step way is not clear enough. Any guys can tell me how to run the flash-all.bat please? When I run it always said fastboot is not etc...
Click to expand...
Click to collapse
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
v12xke said:
It's a good sign you formatted and received no errors in fastboot. Google provides instructions for flash-all.bat on the same page you download the images from. https://developers.google.com/android/images
If you are not comfortable using the command window in Windows, you could also use a toolkit like Wugfresh's NRT or Skipsoft's Toolkit to automate the whole process.
Click to expand...
Click to collapse
Yes sir of course I read it. But I dont understand this step.
Open a terminal and navigate to the unzipped system image directory.
Click to expand...
Click to collapse
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
nhatminhng said:
Yes sir of course I read it. But I dont understand this step.
Is it I open the fastboot cmd, use cd command to navigate to that directory? I already tried but failed to run :'( Although I have fixed it but I want to know just in case the next time. Thanks.
Click to expand...
Click to collapse
Hi... Here's a pretty good detailed process on how to unlock/flash, etc...
https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page549
Also, before using any toolkit, I suggest using manual commands and getting comfortable with it. At least, you learn exactly what command do what! Simply pressing a button in a program may result in a bricked device. Plus with command line you learn something. :good:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
tjchuot287 said:
@nhatminhng How did you get your phone fixed? is your phone unlocked?
Click to expand...
Click to collapse
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
nhatminhng said:
What do you mean "unlocked"? The bootloader is unlocked and I can flash recovery too. I use the command line in heisenberg thread and flash my phone to stock. Add in some more steps I mentioned above. Boom. It's back again.
Click to expand...
Click to collapse
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
tjchuot287 said:
@nhatminhng oh, im sorry, i mean unlocked bootloader. So my bootloader is locked, it still doesnt have any solutions yet.
Click to expand...
Click to collapse
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Do you have access to recovery or just boot loader?
Sent from my Nexus 6P using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes i can. I tried to sideload multiple version of OTA but all have failed.
tjchuot287 said:
Yes i can. I tried to sideload multiple version of OTA but all have failed.
Click to expand...
Click to collapse
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
v12xke said:
I'm guessing you've already tried a factory reset from the stock recovery. Because your bootloader is locked you are limited to sideloading OTA's. And yes, sideloading an older or equal version OTA will fail. You can try a newer revision OTA when available. The 7.1.2 beta may come out before the March security update.
Click to expand...
Click to collapse
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Sent from my Nexus 6P using XDA-Developers Legacy app
CyberpodS2 said:
Good point. It didn't occur to me that equal version would fail. Folks need to unlock their boot loaders! Lol
Click to expand...
Click to collapse
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
v12xke said:
I agree. Unless you absolutely cannot live without Android Pay or Wallet, work phone, etc., there is no reason to not unlock the bootloader as a safeguard. Of course it's no guarantee, but you just have a whole lot more tools at your disposal when SHTF, including restoring a recent backup or flashing a complete stock image. The initial pain of losing your data can be largely mitigated by pulling it off first, and eventually you even forget about the boot nag screen.
Click to expand...
Click to collapse
Now i have unlocked bootloader but the phone keep restart and stuck at logo again. i followed @Heisenberg thread but same result.