On Wednesday, I enrolled my Nexus 5X in the Android O Beta program. Upon doing so and installing the update, I lost all data connectivity. The device said it had both a strong WiFi connection as well as strong cell signal, but I could not access the internet. After posting about the issue in on Google+, my only option was to flash Android N to the device. Therefore, I unlocked the bootloader, and attempted to flash the factory image provided by Google to the device. However, in the process of doing so, I get an error saying
Code:
error: update package missing system.img
After doing some looking around, I discovered that sometimes it's necessary to manually flash some or all of the files by executing one of the following commands:
Code:
fastboot flash system system.img
or
Code:
fastboot -S 512M flash system system.img
However, both of these commands return the following
Code:
error: cannot load 'system.img'
At this point, I'm completely out of ideas for how to fix this, and when I try to boot the phone, it just hangs at the white Google logo. My concern is that I've somehow bricked my phone. Is it necessary to turn off encryption to flash an update? I did not think of doing this before I started. I've never unlocked the bootloader, flashed an update, or rooted a device before, so all of this is quite new to me (as you may have guessed), so any suggestions anyone might have would be quite welcome.
tlewis3348 said:
On Wednesday, I enrolled my Nexus 5X in the Android O Beta program. Upon doing so and installing the update, I lost all data connectivity. The device said it had both a strong WiFi connection as well as strong cell signal, but I could not access the internet. After posting about the issue in on Google+, my only option was to flash Android N to the device. Therefore, I unlocked the bootloader, and attempted to flash the factory image provided by Google to the device. However, in the process of doing so, I get an error saying
After doing some looking around, I discovered that sometimes it's necessary to manually flash some or all of the files by executing one of the following commands:
or
However, both of these commands return the following
At this point, I'm completely out of ideas for how to fix this, and when I try to boot the phone, it just hangs at the white Google logo. My concern is that I've somehow bricked my phone. Is it necessary to turn off encryption to flash an update? I did not think of doing this before I started. I've never unlocked the bootloader, flashed an update, or rooted a device before, so all of this is quite new to me (as you may have guessed), so any suggestions anyone might have would be quite welcome.
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
This is the thread you need to read.
tlewis3348 said:
On Wednesday, I enrolled my Nexus 5X in the Android O Beta program. Upon doing so and installing the update, I lost all data connectivity. The device said it had both a strong WiFi connection as well as strong cell signal, but I could not access the internet. After posting about the issue in on Google+, my only option was to flash Android N to the device. Therefore, I unlocked the bootloader, and attempted to flash the factory image provided by Google to the device. However, in the process of doing so, I get an error saying
Code:
error: update package missing system.img
After doing some looking around, I discovered that sometimes it's necessary to manually flash some or all of the files by executing one of the following commands:
Code:
fastboot flash system system.img
or
Code:
fastboot -S 512M flash system system.img
However, both of these commands return the following
Code:
error: cannot load 'system.img'
At this point, I'm completely out of ideas for how to fix this, and when I try to boot the phone, it just hangs at the white Google logo. My concern is that I've somehow bricked my phone. Is it necessary to turn off encryption to flash an update? I did not think of doing this before I started. I've never unlocked the bootloader, flashed an update, or rooted a device before, so all of this is quite new to me (as you may have guessed), so any suggestions anyone might have would be quite welcome.
Click to expand...
Click to collapse
1. Did you flash it with bootloader unlocked?
2. Did you try redownloading Factory Image?
3. Did you unzip it?
4. Are you using newest Android Tools (fastboot on PC)?
Well, not sure what did it, but I redownloaded everything (including the device drivers) on a new computer (which was kind of necessary to do anything because I was doing everything on my work computer yesterday, and now I'm at home), and it worked just fine.
Related
hi all,
i've managed to get my g-nex (vz lte) pretty badly bricked and am hoping that someone here will be able to help. here's what i did initially on the phone:
1. ran 4.0.2 update from carrier
2. installed adb sdk etc on win 7, verified connectivity and function
3. oem unlock
4. rooted phone
5. installed apps, etc.
6. used phone for a few days, rebooted at will, all working as expected, no issues
7. fully charged phone and in the settings kicked off the encryption process, entered PIN, everything looked good.
8. this morning i woke up to a failed encryption (unfortunately i didn't catch the error message) which needed to be rebooted to move on.
9. after choosing reboot, the screen went very strange - it had grainy horizontal lines that shifted in color somewhat and got dim
10. after waiting for a bit without anything happening, pulled the power and battery
11. the phone rebooted into fastboot, couldn't get into recovery to restore cwm backup, couldn't really do anything
phone shows the following:
fastboot mode - no boot or recovery img
product name - tuna
variant - toro
hw version - 9
bootloader version - primekkk15
baseband version - i515.ek02 cdma - i515.ek05
carrier info - none
serial number - XX_redacted_XX
signing - production
lock state - unlocked
here's what i've tried:
adb commands - doesn't show as there from adb devices
fastboot commands - shows up with fastboot devices, flash commands seem to start but never stop
ODIN mode - connects but writes fail to complete
different usb ports/cables, doesn't seem to make a difference
what i've found to somewhat work - but not really do much - is to oem lock and unlock the phone, once there i can fastboot flash boot boot.img, etc. but if i do a recovery and try and boot into it, it just hangs at the google screen (with the lock unlocked).
i would like maybe reformat the phone completely and reinstall, i've tried the fastboot -w and erase boot / recovery thinking that i could write a clean image to them once they had been cleared, no dice.
if anyone has some suggestions, i'd really appreciate it.
take care,
philo
Have you tried a clean install of the factory image found here? http://code.google.com/android/nexus/images.html#mysidicl53f
i have tried going back to factory, unfortunately that set of images didn't work either. i was able (after an oem lock/unlock) to flash the img files, but it errored on the fastboot reboot-bootloader command with the oddly lined screen. i've attached a picture of the screen for reference.
philo_enyce said:
i have tried going back to factory, unfortunately that set of images didn't work either. i was able (after an oem lock/unlock) to flash the img files, but it errored on the fastboot reboot-bootloader command with the oddly lined screen. i've attached a picture of the screen for reference.
Click to expand...
Click to collapse
I hope you flashed the LTE version and not the GSM
You need this one https://dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz and you must first flash bootloader then radio and then the update img
i have been using the lte, same as your link. i can get the bootloader on, but a reboot-bootloader gives that weird screen, if i try and flash the radio without rebooting i get:
unknown partition 'radio'
philo_enyce said:
i have been using the lte, same as your link. i can get the bootloader on, but a reboot-bootloader gives that weird screen, if i try and flash the radio without rebooting i get:
unknown partition 'radio'
Click to expand...
Click to collapse
Check here http://forum.xda-developers.com/showthread.php?t=1392336
Its the cwm for cdma edition.Check if you can flash it and in this way have access to cwm recovery
i've tried that as well, same lines even if i use the menu to go to recovery after flashing rather than reboot to bootloader first.
So long as it's back to stock, and you've locked the bootloader, it's off for a replacement you go if it was me
EddyOS said:
So long as it's back to stock, and you've locked the bootloader, it's off for a replacement you go if it was me
Click to expand...
Click to collapse
+1 to this
interestingly, i can't get the fastboot oem lock to take either. it reverts back to unlocked after the reboot fails and i have to pop the battery.
does anyone know how to straight up repartition/reformat the flash? i'm assuming that the failed encryption of the flash has put it into an unusable state and would be happy enough just wiping the damn thing clean...
It looks the encryption screwed up because of the different recovery partition which might of also messed up the partition table.
Best bet is to plead ignorance and get a replacement phone.
problem "solved"
i called samsung and pleaded for the pit + factory image with no luck, so i went over to my local vzw and had them replace the phone for me.
i'm not going to try and encrypt this one, hopefully this was just a fluke and won't affect anyone else...
nice work... let them try to fix that shiz!
Darn, I was hoping for a solution...
I am having a similar issue with a Nexus 5. Phone was working fine, started the encryption process and went to bed and woke up with a bricked phone. I can get into the Bootloader and had figured no problem, I'll just do a factory wipe. Whether trying to boot the phone or get it to do the factory restore it sits there and bootloops with the Google logo. Wish programmers would put in status messages the way we did in the 'old days.'
I was able to get a little further was able to reflash, format the partitions etc. but no luck. I am wondering if perhaps the user data may have an indicator or flag that states it is encrypted even though it isnt at this point encrypted. Figured the factory restore would have been more than enough. WUG makes a nice Root Toolkit that automates a lot of the process but even letting do what I already didnt help.
philo_enyce said:
i called samsung and pleaded for the pit + factory image with no luck, so i went over to my local vzw and had them replace the phone for me.
i'm not going to try and encrypt this one, hopefully this was just a fluke and won't affect anyone else...
Click to expand...
Click to collapse
philo_enyce said:
interestingly, i can't get the fastboot oem lock to take either. it reverts back to unlocked after the reboot fails and i have to pop the battery.
does anyone know how to straight up repartition/reformat the flash? i'm assuming that the failed encryption of the flash has put it into an unusable state and would be happy enough just wiping the damn thing clean...
Click to expand...
Click to collapse
Yep , if you can get into recovery , you can adb shell , then list the partitions with "cat proc/mounts" , from there you'll have a list of your partitions and you can use the ext4 tools to manually repartition . I believe the command is makefs_ext4 <whatever partition you wanna do > I'll try to find the exact command but you can do it .
Also if you simply type "fastboot " when at the bootloader it'll give you the help text and it should tell you how to wipe partitions from fastboot
Hack The Tuna
The same issue here ! memory locked
I ve got the same scenario on a phone i just got , brand new but with the same issue , this one boots up but its impossible to factory reset it , odin , cyanogenmod , fastboot adb flashes .... everything fails somehow .... once you reboot the phone everything comes back ! stock software with the applications and old data .... theres no way to erase it ... it seems the previous owner of the phone encrypted it and then used clockworkmod or something like that ..... the nand on the device is like hardlocked .... doesnt let you do anything !
Earlier today I used the Nexus Root Tool Kit to flash stock and flash the factory image for 5.0.
At erasing User Data it seemed to get stuck, it was there for over 40 minutes. While looking at the device I accidentally knocked the USB cable out and it said failed. Upon rebooting the device I got the Google logo and the bootloader unlocked icon and then the bugdroid with the gear like it's doing an update (THIS: http://scottiestech.info/wp-content/uploads/2013/03/Android_Update_Screen.jpg[1] ). It stayed like this for another 40 minutes. I forced it to shut down and tried to get into the bootloader but holding down vol up+vol down+power for almost 60 seconds did nothing.
I then booted it up normally again to the gear bugdroid and left it like that before I went out for almost 6 hours. When coming home it was the same and still stuck on that.
I rebooted again and held down to boot into the bootloader but again it did not boot in over 60 seconds.
So am I hard bricked and should toss this out with the trash tonight or can this be restored somehow.
Are you able to connect to your device using fastboot?
Assuming you have fastboot installed and the drivers installed, open a command prompt and from the directory where your SDK files are (unless you added the directory to your system PATH), type "fastboot devices" without the quotes. What do you get back? If you get back a serial#, you should be able to flash the individual files manually
(Download the factory image from google's site, and extract the files into a folder, and run the flash-all.bat This will wipe all your data out, and assumes your bootloader is already unlocked)
Edit: follow the instructions here - http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
These are for Nexus 5, but the same steps apply for Nexus 7 as well. Just make sure you download the right factory image for your Nexus 7. Use Method 1
jj14 said:
Are you able to connect to your device using fastboot?
Assuming you have fastboot installed and the drivers installed, open a command prompt and from the directory where your SDK files are (unless you added the directory to your system PATH), type "fastboot devices" without the quotes. What do you get back? If you get back a serial#, you should be able to flash the individual files manually
(Download the factory image from google's site, and extract the files into a folder, and run the flash-all.bat This will wipe all your data out, and assumes your bootloader is already unlocked)
Edit: follow the instructions here - http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
These are for Nexus 5, but the same steps apply for Nexus 7 as well. Just make sure you download the right factory image for your Nexus 7. Use Method 1
Click to expand...
Click to collapse
Well I can get it into fastboot but I'm getting errors when it tries to flash the bootloader or boot.
what's the error message?
jj14 said:
what's the error message?
Click to expand...
Click to collapse
originally there was none, it just said failed and completed. now i'm getting invalid arguments.
I'm still in fastboot mode but literally nothing will flash.
*edit* just tried to use tookit again and
writing 'bootloader'
FAILED <remote: flash write failure>
finished.
Seeing a couple people mention that they fixed errors like this just from using a different usb port or cable. going to try that.
Why didn't you use adb to flash factory image from the get-go? It's the safest way to flash. I would be so mad on your place if device would render useless. But that might be just me since i'm poor. I really hope you manage to fix it.
neo5468 said:
Why didn't you use adb to flash factory image from the get-go? It's the safest way to flash. I would be so mad on your place if device would render useless. But that might be just me since i'm poor. I really hope you manage to fix it.
Click to expand...
Click to collapse
I knew of that way but the Nexus Tool Kit has always been perfect and I've never had any issues with it so I figured I'd just do it that way to make it easier and well, it didn't happen.
I'm hoping because I can get into fastboot that it's not actually bricked yet but if so then oh well i guess.
So I completely bricked my tablet, cant even get my PC to recognize the tablet, and the only screen i have up is the Google and the unlock padlock. and if i try a hard reset, all i get is android on his back and the red triangle. I have decided to buy a used motherboard, I see from ifixit.com that they are easy to repair, will this solve my dilema? I found used mobo's on ebay, made sure to get the correct one, is this the answer to not buying a new tablet?
My nexus 7 lte is in the exact same state(that's why I've posted here instead of starting new thread)...by using nrt to try updating to marshmellow as per site's instructions...wondering if anyone can offer a solution???
(bought at google play almost 2 years ago and they already sent me a free refurb replacement...but I still wanna try getting the old one going before sending it back if possible...worth a try before buying a replacement mobo)
here some details of my situation:
ran this on my nexus 7 2013 lte...failed on the first try...tried again..it wiped everything and then failed on install...now I have bootloader (accessible by volume down and power button simultaneously) only and no functional recovery(get the android with red triangle and asterisk when I select Recovery)...the only Android device listed in Device manager is Android Bootloader Interface.
If I start from fastboot mode:
gives a driver failed to load error from windows" and also, now in Device Manager my Android Device Listed changed from "Android Bootloader Interface" to "Android Composite ADB Interface", as well, there is now a Portable Device listed also but it's the driver that failed to load I guess "MTP USB Device" with a yellow asterisk.
If I run the flash-all.bat in the image download that the NRT got on the first attempt, everything goes fine until I get to "sending system"...this fails with unknown data transfer error...
when I download the latest image from developers google.com and extract it I get just one big file with no extension...shouldn't there be a bunch of files including a flashhall.bat file?
^Yes, inside the main image zip is the bootloader (+ radio in your case) and another zip of the actual partition images.
Run fastboot devices from the bootloader just to be sure it's detected. If not uninstall all traces from your pc and start fresh.
Flash the new bootloader, reboot bootloader, flash the radio, reboot bootloader then flash each .img individually with fastboot. Don't use any toolkits.
You should get the "OKAY" after flashing each image. Is it only system that fails? Do you get the okay with boot and recovery? If system only I don't know.
ronf1011 said:
So I completely bricked my tablet, cant even get my PC to recognize the tablet, and the only screen i have up is the Google and the unlock padlock. and if i try a hard reset, all i get is android on his back and the red triangle. I have decided to buy a used motherboard, I see from ifixit.com that they are easy to repair, will this solve my dilema? I found used mobo's on ebay, made sure to get the correct one, is this the answer to not buying a new tablet?
Click to expand...
Click to collapse
The android with the red triangle with exclamation is what happens with stock recovery, you need to press power, volume up and down quickly all at the same time to get in. Usually takes a few tries. If you can get into recovery you could factory reset. It could be another problem though. You have to describe what you previously did to it if you really wan't help.
rma
Thanks for the reply...was never able to get the system image to load...google play is supposed to reemburse me once they receive my original nexus 7 (already got a pristine refurb from them..updated to marshmellow..will be staying away from NRT with this one...)
Thanks again for the reply and suggestions!
system image can't be written
Exactly the same happened to me. After a successful update to MM with Wugfresh's NRT 2.0.5 (with no root) I tried to root my device with 2.0.6 which was released in the meantime.
But that failed because NRT thinks my bootloader is locked, while in fastboot mode I can see that it is unlocked. With fastboot commands I can relock and re-unlock but for NRT it makes no difference.
It seemed to me that a manual reflash of bootloader (FLO-04.05), kernel, cache, system and data should solve this, but no way. The flashall. bat reports a write error of the system.img. A direct fastboot flash system system.img command leads to FAILED (remote: unknown chunk type).
I couldn't find any information about chunk types. I am afraid that somewhere in the process the partitioning was affected. Is that a possibility and can anything be done to fix this? Or are there other solutions for the chunk type error?
HI everyone,
I updated "successfully" from Kitkat to 5.0.2 on my rooted (stock ROM) Nexus 7 second gen.
Unfortunately, when I tried to upgrade to 5.1 everything seem to be normal until the device rebooted and it went through the "update process". 3/4 the way through, the green droid went on his back and the "ERROR" message appeared.
I wiped the cache partition but that doesn't help. I tried to download the update in safe mode, but no success. I also find it odd that each time I reboot my device, I get a message from Android that it is "updating my apps".
If I didn't have any apps and a lot of data on my Nexus, I would wipe the device clean but I'd rather avoid this, if at all possible.
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Thanks
Michael Carleone said:
Is there a way to upgrade to 5.1 or reinstall 5.0.2 without losing everything?
Click to expand...
Click to collapse
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img
k23m said:
No problem. As you rooted it before then presumably it is unlocked and equipped with custom recovery, so all you have to do is:
boot TWRP
connect PC
transfer data and APKs to PC
flash OS
If you don't have TWRP installed, then boot it like this fastboot boot twrp-3.0.2-0-flo.img
Click to expand...
Click to collapse
Hi,
Thanks for the reply. I rooted with Kingroot. I don't believe I have a custom recovery. The bootloader is locked as shown when I boot into recovery mode.
I want to avoid transferring my data and APK files to my PC.
Should I assume there is no way of reinstalling the OS without wiping out the device?Also, there is no link in the above quote: fastboot boot twrp-3.0.2-0-flo.img
Since I got no other replies, I went and restored to factory image. I do have another question. I hope I get a better response there: http://forum.xda-developers.com/nex...a/nexus-7-2013-wifi-root-marshmallow-t3515072
Thanks for the reply.
Can we compare using fastboot flashing TWRP vs Nexus Root Tool Kit: http://www.wugfresh.com/nrt/? I ended up using this utility instead because it was pretty much one click and it didn't require command lines and for whatever reason, I found instructions using fastboot a bit confusing. Which method is better or has more advantages? I left my bootloader unlocked.
Incidentally, I think there was something wrong with my Nexus image. As a result, I did use Google's instructions on how to flash etc. the OEM image. Instructions weren't ideal but I managed to figure things out: https://developers.google.com/android/images
The instructions are here which I assume would be similar if I wanted to fastboot TWRP?
To flash a system image:
Download the appropriate system image for your device below, then unzip it to a safe directory.
Connect your device to your computer over USB.
Start the device in fastboot mode with one of the following methods:
Using the adb tool: With the device powered on, execute:
adb reboot bootloader
Using a key combo: Turn the device off, then turn it on and immediately hold down the relevant key combination for your device. For example, to put a Nexus 5 ("hammerhead") into fastboot mode, press and hold Volume Up + Volume Down + Power as the device begins booting up.
If necessary, unlock the device's bootloader by running:
fastboot flashing unlock
or, for older devices, run:
fastboot oem unlock
The target device will show you a confirmation screen. (This erases all data on the target device.)
Open a terminal and navigate to the unzipped system image directory.
Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system.
Once the script finishes, your device reboots. You should now lock the bootloader for security:
Start the device in fastboot mode again, as described above.
Execute:
fastboot flashing lock
or, for older devices, run:
fastboot oem lock
Locking bootloader will wipe the data on some devices. After locking the bootloader, if you want to flash the device again, you must run fastboot oem unlock again, which will wipe the data.
Click to expand...
Click to collapse
Also, I could've sworn that when I rooted KitKat on my Nexus, my data wasn't wiped out. I don't recall doing anything to the bootloader. I can't recall which method I used, but I know for certain I didn't use the Nexus Root Toolkit. I should've recorded my steps when I rooted.
i rooted my nexus 7 using towel root on kitkat .. i unrooted using supersu... and ota untill marhsmallow with out a problem never use kingroot as its so un stable.
Hi,
Here is fix for those, who have problem with bootloop on 5X with locked bootloader and OEM unlock disabled.
This tutorial works for Beta Android O bootloop too.
You will need:
ADB + drivers installed: https://forum.xda-developers.com/showthread.php?t=2588979
Nexus toolkit: DL.- http://www.wugfresh.com/nrt/
STOCK image archive, older than you have now - https://developers.google.com/android/images#bullhead
Latest OTA image archive : https://developers.google.com/android/ota#bullhead
-------------------
Extract stock image (NOT OTA)
install Nexus toolkit and restart your phone in Bootloader mode
connect phone to pc.
In nexus toolkit click on : advanced utilities > launch
look at: fastboot flash
screen: https://postimg.org/image/kkk9h92oz/
click on all buttons and flash all partition files from extracted archive - except recovery ,userdata and cache.
Copy downloaded OTA ROM archive in ADB folder.
reboot in recovery
now select apply update from adb.
open ADB
flash latest OTA package via command : adb sideload <packagename>.zip
I hope, this tutorial is useful for you, if yes, please hit thanks button.
And sorry for my english.
GREAT!!! Saved my phone. Thank you very much!
I've run into the issue by running the Factory reset from the Settings on my Nexus 5x and ran into this bootloop, is there a way to get this fixed if I didn't have USB debugging on? As I was just plain Factory reseting my phone.
I am getting this error when trying to sideload OTA via adb command
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Nevermind I was doing it wrong. It is fixed now. Thanks for the guide.
Ins1d3r said:
I've run into the issue by running the Factory reset from the Settings on my Nexus 5x and ran into this bootloop, is there a way to get this fixed if I didn't have USB debugging on? As I was just plain Factory reseting my phone.
Click to expand...
Click to collapse
You not need usb debugging enabled in system.
Communication with pc is working in fastboot and recovery.
Redmi Note 3 - Tapatalk
any idea how to do it in mac?
What do you mean with: "Copy downloaded OTA ROM archive in ADB folder."
Just sideloading doesn't work.
ADB cant find my 5x...
Thank you OP for this i am need of help and it appears your solution has found me. Im on holiday atm and my nexus 5x just got the dreaded bootloop! Alll i see is the spinning colors for android logo after pin code is inputted.
Im very anxious to backup my photos of my son and family, so want to ask is this method safe? I dont want to risk losing data.. i can get into recovery mode and my phone is boot locked and not rooted, so can someone also tell me if adb backup will allow me to backup my pictures and video reliably? I will do a full backup and then try and flash the OTA.
serving: 'bullhead.zip' (~47%) * failed to read command: No error , what im doing wrong ?
ok succeed after dozen attempts , phone booted to main desktop work for like 5 mins and then frozen , looks like it went back to bootlooping ;(
Hi guys, same situation, since yesterday I could boot with a bit of effort (like waiting 15 minutes of bootloop) but now the 5x doesn't boot at all and so neither in recovery. My phone is locked and never modded so I will send in warranty when I will be back home ( 10 days). So now I would like to fix it to use it at least in this week, but how can I do if I can't boot in recovery?
I can just boot in the bootloader so use fastboot command...if I unlock the bootloader I will get the little lock in the bottom part of the screen, when I will lock it to send it to LG will it disappear?
How exactly is this toolkit's fastboot flashing supposed to work if you have a locked bootloader?
How is using this toolkit any different from running the "flash-all.bat" that's included with factory images?
This did nothing at least in my case.
I get the feeling that the flash operations are failing and the toolkit just disregards this.
Cannot enter recovery
I completed the first step in fastboot but when i try to enter recovery it goes to bootloop again....what should i do?
Nope, not working. Rebooting again and again. Issue not resolved. Please help!
Hi I need help,
what do i choose when i click 'system' tab?
[/QUOTE]
rockhardy said:
I am getting this error when trying to sideload OTA via adb command
adb server version (32) doesn't match this client (39); killing...
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
Nevermind I was doing it wrong. It is fixed now. Thanks for the guide.
Click to expand...
Click to collapse
Hi,
I'm having the same problem.
Cannot enter recovery since the device just stays in bootloop, and I get the same message error if I try to sideload.
What were you doing wrong and how did you fixed it?
Tks
jcfortunato said:
Hi,
I'm having the same problem.
Cannot enter recovery since the device just stays in bootloop, and I get the same message error if I try to sideload.
What were you doing wrong and how did you fixed it?
Tks
Click to expand...
Click to collapse
It's been a while since I tried it. But as far as I remember it was due to phone not being in recovery mode. I hold the power button until the phone screen went off. And while holding the power button I instantly pressed volume down button to bring back the fastboot mode and then recovery mode.
i'm sorry but i don't see my latest build (currently running on 7.1.2)
i've tried using 'any build', it said that i have to choose one of the build listed :/
thank you
-----
edit
found them!
but it says that my OTA is out ouf date
I downloaded the latest one though (August)
where did I go wrong? :/
Anyone still doing this ha? I've just run into this issue with my wife's phone, and there are things on there she needs..
The ones with issue with the big cores causing bootloops, use this guide to unlock device then proceed with following guide
https://forum.xda-developers.com/showthread.php?t=3641199
Sent from my Nexus 5X using Tapatalk
Hello, I've done all the procedure until reboot recovery, but I've didn't find the button for select apply update from adb in NRT.