Related
re: 2.3.6 Upgrade issue.
I may have made a mistake.
I recently updated my atrix to 2.3.6. It installed successfully but I decided to flash it back to 2.3.4, which I'm currently regretting.
When I turn my Atrix 4G on, It says 'failed to boot 1'.
If I hold the Volume up and power buttong it says:
'Failed to boot 1, PwrReason: Power_cut, Starting fastboot protocol support'.
Im tried to flash the roms using RSDLite:
att-2.3.4_pudding_preroot and also the
official 2.3.6
The error is:
Failed flashing process. Unable to retrieve interface handle.
I tried to unlock bootloader cmd, but wasn't successful.
Any ideas guys?
As an update, i tried to use fastboot to load images.
Instructions to root Atrix 4G running Gingerbread:
-----------------
Download and Extract Fastboot Files to your C: drive (Download Link)
Connect your phone to the computer via USB
Put your phone in fastboot mode (restart phone holding volume down button)
Open a command prompt and navigate to C:/moto-fastboot-win32
type “moto-fastboot.exe flash preinstall preinstall.img” press enter
---------------
it says:
sending preinstall OK
writing preinstall... Failed remote 00180004.
I can't see to write to boot, system or any component?
Do I need to unlock the bootloader? Sorry this stuff is all new to me, and trying to piece it together.
Please use the search, I faced the same issue, you will have to create a factory cable and using RSDLite, flash the 2.3.6, you cannot flash the 2.3.4
Sent from my MB860 using Tapatalk
Hi Tommy,
I saw you're thread but it wasn't clear what steps you took.
Did you modify the Atrix USB Cable in order to install a 2.3.6 sbf file using rsdlite?
I'm wondering if there is another way.
OP - Flash the 2.3.6 sbf file with RSD lite 5.6 - should get you back up and running just fine...
I tried flashing the:
1FF-olympus-user-2.3.6-4.5.141-111212-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P012
and got this error in rsdlite
internal error while programming phone.
Then after that if I try it again, or try the pudding 2.3.4 one the error changes to:
Failed flashing process. Unable to retrieve interface ahndle 0x7027.
re: 2.3.6 Upgrade issue
First off let me say I know absolutely nothing of development but I figured I'd be brave enough to experiment any way. So I tried upgrading yesterday with partial success, there was no separate .img files at the time though . I'm rooted and have an unlocked bootloader; what I did was extract the zip file from the cache folder onto my PC then removed ap20bl.img seeing that I read all the horrors of possibly re-locking bootloader and bricking I then zipped the file and named it update.zip and booted the phone to CWM Recovery and tried installing that way. I realized after failing the install since it prompted that it couldn't find the ap20bl.img that there must me a script. Knowing that there'd probably be a size check I did this any way....used a bl.img from the 2.3.4 fruitcake and renamed it to ap20bl.img still failing therefore I assume that it really did check the file size. I then located the updater script and removed references to the ap20bl.img file. I tried install again this time saying something about E:\ unfortunately I don't recall exactly what.....so to take care of that I deleted the cache (probably a bad idea). That got rid of that error but from that point I got an error 6 ever since. I decided to reboot the phone which booted fine. Checked "About Phone" and it said the current version was 4.5.141, I was very happy about that; checked that the phone was still rooted and it was. Calls worked, bluetooth worked.....BUT ....it came time to check the wireless....."ERROR". Yip, no more WiFi. I rebooted to CWM and did a factory reset...rebooted again checked WiFi...now said "Turning on, Turning off, Error". So.......I rebooted to fastboot and sent the 2.3.4 radio (.91), rebooted and still got the error. I decided even though I read not to, to go back to 2.3.4 so I rebooted CWM, did the necessary wipes and reinstalled the 2.3.4 fruitcake then checked WiFi which now worked (or so I thought)....the connection dropped after a while then said error when I checked its status so I rebooted and it worked fine only to have the same issue again. I then did necessary wipes and tried Neutrino 2.1 EE seeing that it was the only ROM I had with me at work still having the same WiFi issue. At this time I haven't done anything else with the phone but hopefully this information will help developers or anyone else
Your only hope is the Motorola Factory Cable, yes it is configured differently, in it the red and brown cable are joined, please see my thread for reference, also you will find lot of articles on the internet, you will not be able to flash without it, been there, done that
Sent from my MB860 using Tapatalk
Hi folks,
I'm an adroid 1st timer and chose a Nexus 7 two weeks ago to begin with. I was pretty happy with it (i have a faultless device) except some slugginess issues when scrolling. Thats why i tried to use a custom ROM to adress this. Well, i kind of regret this now ... I enabled USB Debugging then downloaded an utility to boot into FastBoot and wipe my device data in order to flash the new ROM. It is an vanilla device (meaning i didnt modified anything) and i am using Windows 7. I got error messages during the wiping process:
- About formating system, userdata and cache partitions (command write failed)
- About erasing "boot" and "recovery" (command write failed)
Since then, i cannot reboot into Android itself, just access FastBoot mode. I did manage to unlock the bootloader with the Nexus 7 toolkit though, but i'm not sure if it is any help.
So my question is : did i just definitively ruined my Nexus 7 ? Pleeeeease tell me there is something i can do to boot again ... I'm really not a newbie at tweaking stuff, but as this is my 1st android device please go the slow way I cannot upload screenshots until i wrote 10 messages FYI.
To me it sounds like you could get your Nexus 7 up and running just by flashing stock ROM using this.
Even if I am no help, the situation doesn't sound too bad.
Thants Tonttunator ! Sadly, i have the same issue with the Nexus 7 toolkit: It fails to wipe data and continue with flashing the stock ROM. I'm still investigating to be sure my ADB/Fastboot drivers are as regular as can be, but i still cant go through the procedure.
EDIT: I finally found out that i just had to try on anotther computer with another cable. Did this using the nexus 7 toolkit and the procedure 9/1/1/y/y, it worked flawlessly.
stats;
n7,
unlocked,
rooted
running JB
user level: android noob, but have a good grasp of comp stuff (I used to kill my own viruses when limewire was the defacto way to get download)...
comp, Win 7, old athlon dual core 64 4600, 3gb ram...
My n7 hasnt loaded kitkat, and I was getting annoyed with the constant "update ready".
I tried several times to install it, but each time it turned up an error....
Today I thought I would force an update with Skipsoft toolkit.
All seemed to go well, then....
things froze.....both comp and tablet and toolkit
I walked away, I didnt touch anything...for 2 hours. I literally went outside to do some errands, hoping things would "fix themselves".
I came back and disconnected, the tablet but the computer was still frozen...so I waited a few then, restarted the comp...
Now my tablet was stuck on the "google" screen.
I figured out how to get into the fastboot screen,
then the CWM screen.
from there, Ive tried,
Skipsoft toolkit,
Nexus Root Toolkit,
ADB manager (still not sure what this does except for downloads files, none of the apps in the toolkit file do anything)
fastboot.exe,
pdaNet drivers...
a couple of various tutorials (http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/) this one requires the tablet to be awake, but Ill be darned if I can get it to do anything...
On the good side of things, the Skipsoft toolkit, recognizes it, it displays the serial so theres hope. I hope.
But its never recognized in my computer, it did make the beep boop, when ever its dis/connected, until the I was trying the nexus root kit (they ask to remove drivers etc).
99% of the tutorials ask for the debugging to be activated. well it was but now...who knows.
with the skipsoft I get:
insecure boot image found
stock recovery image found
cwm image found
twrp image found
^^^^^^^^^^^^^^are these on the tablet or the comp?
once Im into the cwm screen, Ive cleared cache, and partition etc, nothing seems to help.
can someone help me before I brain my damage?
fixed it..wooooohoooooo
Vishnuisgod said:
stats;
n7,
unlocked,
rooted
running JB
user level: android noob, but have a good grasp of comp stuff (I used to kill my own viruses when limewire was the defacto way to get download)...
comp, Win 7, old athlon dual core 64 4600, 3gb ram...
My n7 hasnt loaded kitkat, and I was getting annoyed with the constant "update ready".
I tried several times to install it, but each time it turned up an error....
Today I thought I would force an update with Skipsoft toolkit.
All seemed to go well, then....
things froze.....both comp and tablet and toolkit
I walked away, I didnt touch anything...for 2 hours. I literally went outside to do some errands, hoping things would "fix themselves".
I came back and disconnected, the tablet but the computer was still frozen...so I waited a few then, restarted the comp...
Now my tablet was stuck on the "google" screen.
I figured out how to get into the fastboot screen,
then the CWM screen.
from there, Ive tried,
Skipsoft toolkit,
Nexus Root Toolkit,
ADB manager (still not sure what this does except for downloads files, none of the apps in the toolkit file do anything)
fastboot.exe,
pdaNet drivers...
a couple of various tutorials (http://www.droid-life.com/2013/02/1...date-a-nexus-without-root-or-custom-recovery/) this one requires the tablet to be awake, but Ill be darned if I can get it to do anything...
On the good side of things, the Skipsoft toolkit, recognizes it, it displays the serial so theres hope. I hope.
But its never recognized in my computer, it did make the beep boop, when ever its dis/connected, until the I was trying the nexus root kit (they ask to remove drivers etc).
99% of the tutorials ask for the debugging to be activated. well it was but now...who knows.
with the skipsoft I get:
insecure boot image found
stock recovery image found
cwm image found
twrp image found
^^^^^^^^^^^^^^are these on the tablet or the comp?
once Im into the cwm screen, Ive cleared cache, and partition etc, nothing seems to help.
can someone help me before I brain my damage?
Click to expand...
Click to collapse
I think I got it!!!!!!!!!!
using the skipsoft,
first i did option 1, install usb settings; then
I used option #6 force recovery.. I think i did stock rom.
now Im updating with kitkat and it updating to 4.4.2
Vishnuisgod said:
I think I got it!!!!!!!!!!
using the skipsoft,
first i did option 1, install usb settings; then
I used option #6 force recovery.. I think i did stock rom.
now Im updating with kitkat and it updating to 4.4.2
Click to expand...
Click to collapse
thank you for the tips ! the tool kit actually worked i had no os (deleted everything).
and used the 9 option (flashing stock) it worked !
Hi hope I have come to the right place for help. My Nexus 7 16GB 2012 wifi is freezing after the google logo during the boot animation of the spinning circles and stays like this. I have done some reading and I can get into recovery mode and would like to retrieve pictures/personal data but I have not enabled USB debugging, have a stock rom kitkat, but not sure which version, and have a locked bootloader, not rooted. Is it possable to still get the data off of the device. If someone could point me in the right direction it would be much appreciated.
Thanks in advance for a response
Sent from my GT-I9100 using XDA Free mobile app
alscott51 said:
High hope I have come to the right place for help. My daughters Nexus 7 16GB 2012 wifi is freezing after the google logo when booting at the spinning circles and stays like this. I have done some reading and I can get into recovery mode and would like to retrieve pictures/personal data but I have not enabled USB debugging, have a stock rom kit kat, but not sure which version, and have a locked bootloader, and not rooted. Is it possable to still get the data off of the device. If someone could point me in the right direction it would be much appreciated.
Thanks in advance for a response
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
Use adb pull command
Ok Im not familiar with this programme but have read a bit about it. I will try and venture into this alien world of abd and see what happens.
Sent from my GT-I9100 using XDA Free mobile app
Installed Minimal ADB and Fastoot, connected the Nexus installed the ADB driver from Asus in device manager. Booted into the bootloader and when I used "Fastboot devices" I can see my devices seial number. When I try "ADB devices" nothing is seen. I have read I need USB debugging selected and the device booted to use ADB, both of which I can not do as I am stuck in a boot loop.
Sent from my GT-I9100 using XDA Free mobile app
You can't use adb in fastboot mode. It seems possible to pull files with fastboot, but it isn't fun.
Maybe you can flash something via fastboot to make it boot again? That would be the best way imho.
alscott51 said:
Installed Minimal ADB and Fastoot, connected the Nexus installed the ADB driver from Asus in device manager. Booted into the bootloader and when I used "Fastboot devices" I can see my devices seial number. When I try "ADB devices" nothing is seen. I have read I need USB debugging selected and the device booted to use ADB, both of which I can not do as I am stuck in a boot loop.
Sent from my GT-I9100 using XDA Free mobile app
Click to expand...
Click to collapse
Go to recovery and try adb commands. In bootloader you can use only fastboot commands.
Ok I booted to the bootloader, from here selected recovery where the little Android is laying on its back. Now device manager showed nothing connected. Used the power + volume-up combo to get to the four recovery options, still nothing in device manager. Selected side load adb option and bingo welcome sound of device being connected. Windows didn't find a driver so downloaded adb driver from Asus but device manager refused to use it. Did some reading and downloaded Koush's universal driver and now device manager showed device connected and driver installed. The ADB devices command now shows the Nexus info. Now to learn the pull command. ....
Sent from my GT-I9100 using XDA Free mobile app
Done lots if reading on this and think I am beat. From what I have read the with the Nexus 7 in its current state (stock, locked bootloader, unrooted, no usb debugging) the sdcard is not reachable through the stock recovery sideload option in any way. I had a ray of hope from the above link to pull files via fastboot but I have read the thread and it seems the person says it was misleading information that they posted. I followed information in another thread and tried extracting boot, recovery and system files from a nexus factory image and flash them via fastboot but it fails stating the bootloader is locked. If I unlock the bootloader I will lose the sdcard data I want, as I will have to perform a factory reset. So as suggested I could install a CWM/TWRP recovery, but to do this via fastboot I need to unlock the bootloader......
I am thankful for people taking the time to help and for all suggestion posted but unfortunately I can not find a fix. I would be sooo grateful if someone could prove my finding wrong....
Off to do some reading about mounting the sdcard via adb shell but don't think this will work via stock recovery
Sent from my GT-I9100 using XDA Free mobile app
Install and configure any ftp/sftp/ssh server from Google play and download data wireless.
jkkk88 said:
Install and configure any ftp/sftp/ssh server from Google play and download data wireless.
Click to expand...
Click to collapse
Can't get the nexus to boot up, just bootloader and recovery accessible so don't think I'll be able to do this.
Sent from my GT-I9100 using XDA Free mobile app
Fixed it and saved all data.
Sent from my GT-I9100 using XDA Free mobile app
Sideload fix
Managed to fix this without losing anything (sdcard, docs, pictures, apps, setting etc). Took a while mostly due to lack of understanding of fastboot and ADB sideload from the recovery options.
Lots of posts advising to boot into the bootloader and use adb and fastboot. Everything I read to do with using fastboot commands via the nexus bootloader (insatalling boot/system/recovery etc) involved having an unlocked bootloader or having to unlock it as in my situation. This of course involves a factory reset of the Nexus resulting in a loss of the data that I was trying to retrieve, so i ruled this option out.
As suggested I should try the ADB pull command, but because I had not previosly enabled the USB debugging option via the setting menu everything I read said this was not an option. Read in one forum post something like "As you have not enabled USB debugging ADB is dead to you, just flash a factory image via recovery".... and lose all your data... this is not what I wanted to hear so I abandoned this option aswell.
Then I discovered sideloading. With this you can manually install an OTA update (the ones that pop up in your notification window saying something like "System update available") via the Nexus recovery option "apply update from adb". This does not invlove wiping any data , apps etc as it would just install the differences between what you are currently running eg. 4.4.2 and the updated android you want to go to eg 4.4.3. This is different to flashing a full factory image via fastboot were everything would be erased/formatted and an entirely new install would be flashed. Of course... simple when you know what the option is for and what you are doing. Of course I had had no clue what sideloading was all about.
So with my new knowledge I downloaded an OTA update from here:
http://forum.xda-developers.com/showthread.php?t=1745781&highlight=4+23
but wasnt sure what version of KitKat was running prior to the bootloop. I knew it was somewhere around 4.4.2.. so took a chance and tried KTU48L from KOT49H (4.4.3 from 4.4.2) and copied it to the Minimal ADB folder.
I booted the Nexus to the recovery mode and selected "apply update from adb". The tablet then conected to the PC (windows) as shown by Device manager. (I used Koush's universal ADB driver as windows failed to find anything of use). https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I opened Minimal ADB downloaded from here
http://forum.xda-developers.com/showthread.php?t=2317790
and typed "adb devices" which showed the Nexus was connected.
I then typed "adb sideload nexus OTA file name.zip"
Lots of sending files messages appeared in the adb window the Nexus disconnected from the PC and showed this...
Finding update package...
Opening update package...
Verifying update package...
Insatlling update...
Verifying current system...
Removing unneeded files...
Patching system files...
Patching boot image....
Unpacking new files...
Unpacking new recovery...
Symlinks and permissions..
Patching remaining system files...
script succeeded: result was [/system]
Install fromADB complete.
All looked good so I rebooted the Nexus but I was still stuck in a bootloop at the four spinning circles. I tried clearing the cache from the recovery menu several times powering it down and leaving it to boot but after half an hour accepted failure.
So I tried downloading KTU84P from KTU84L (4.4.4 from 4.4.3) and repeated the procedure. this time not as much files seemed to be sent to the Nexus, I guess this was just a small update. Again it showed "script succeeded" but still failed to get past the spinning circles of the boot animation.
Thinking I was defeated again I was going to give up but tried downloading LRX21P from KTU84P (5.0 from 4.4.4). This time when I sideloaded a mass of files were sent to the Nexus much much more then the other two updates, obviously KitKat 4.4.4 to lollipop 5.0 was a big update. Again I got the "script succeeded" but this time I got the new Lollipop boot animation and the Nexus fully booted.
I can only guess that the big update to Lollipop removed or replaced files or did something to replace the faultly part of my install that other OTA updates did not change.
Anyway I did not find any other fix that advised sideloading an OTA update to fix a bootloop, maybe I just looked in the wrong places. I tried to write this in laymans terms for non techie people in the hope that it may help someone else in the same situation who like me knows very little about android.
Thanks to the forum for the information...
Also link here with some info about half way down page on effects of usb debugging being enabled for sideloading, and near the bottom of the page a good link to a sideload pdf guide.
https://productforums.google.com/forum/#!topic/nexus/Fhl6VVb0kio
Backstory I'm running PureNexus rom with Experimental kernel. Yesterday out of nowhere the phone started bootlooping, usually this is fine and i'll just restart the phone. Well after trying this the bootloop stayed for 15mins. I cleared cache and dalvik and still the same results. I ended up trying to restore a previous nandroid and nothing changed. Frustrated I backuped my titanium backups to my PC and cleared everything, factory reset and data format from twrp. I tried flashing the PureNexus rom clean and still bootloops. It just hangs on the white Google screen with the black background.
I'm following Heisenberg's tutorial (section 10) and after using fastboot and following the directions, i'm getting stuck on flashing the system. I'll get, "load_file: could not allocate 2014388768 bytes
error: cannot load 'C:\angler\images\system.img'
I read restarting the computer might help and i tried that and nothing has changed. It seems this is not rom related, since I downloaded a couple different ones and pushed it to my phone/flashed and it still bootloops. Any suggestions or help? Thanks!
Subiegsr said:
Backstory I'm running PureNexus rom with Experimental kernel. Yesterday out of nowhere the phone started bootlooping, usually this is fine and i'll just restart the phone. Well after trying this the bootloop stayed for 15mins. I cleared cache and dalvik and still the same results. I ended up trying to restore a previous nandroid and nothing changed. Frustrated I backuped my titanium backups to my PC and cleared everything, factory reset and data format from twrp. I tried flashing the PureNexus rom clean and still bootloops. It just hangs on the white Google screen with the black background.
I'm following Heisenberg's tutorial (section 10) and after using fastboot and following the directions, i'm getting stuck on flashing the system. I'll get, "load_file: could not allocate 2014388768 bytes
error: cannot load 'C:\angler\images\system.img'
I read restarting the computer might help and i tried that and nothing has changed. It seems this is not rom related, since I downloaded a couple different ones and pushed it to my phone/flashed and it still bootloops. Any suggestions or help? Thanks!
Click to expand...
Click to collapse
Just download NexusRoot Toolkit to flash back to stock or boot into recovery TWRP and flash PN rom again. It should work fine after that.
luckyfate said:
Just download NexusRoot Toolkit to flash back to stock or boot into recovery TWRP and flash PN rom again. It should work fine after that.
Click to expand...
Click to collapse
Just updated the SDK tool and it actually did let me install the system.img file now after it allocated some. But phone still boot looped.
Downloading the NexusRoot Toolkit now! Thank you for the suggestion, I'll update with the results.
So I installed the toolkit and did the flash stock + Unroot and checked soft-bricket/bootloop and phone is still bootlooping 30 mins later. It's doing the same bootloop as before. Just the black and white Google logo and then the orange pause boot screen. Although, as I type this the Google is not just there and it doesn't flash back to the orange screen..
Not sure if this helps but the live log said:
"Nexus Root Toolkit v2.1.6
Masterlists:
- LatestToolkitFiles.ini 3124
- AndroidDeviceListFull.ini 3124
- AndroidDeviceListFlash.ini 3124
ANGLER-ANGLER: Android 6.0.0 - Any Build
Live log initiated [2016-07-31]:
Further extracting contents of factory image package for use in 'Force Flash Mode'...
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
5VT7N15A25003518 fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
fastboot getvar product
product: angler
finished. total time: 0.012s
Launching flashstock.bat"
Subiegsr said:
So I installed the toolkit and did the flash stock + Unroot and checked soft-bricket/bootloop and phone is still bootlooping 30 mins later. It's doing the same bootloop as before. Just the black and white Google logo and then the orange pause boot screen. Although, as I type this the Google is not just there and it doesn't flash back to the orange screen..
Not sure if this helps but the live log said:
"Nexus Root Toolkit v2.1.6
Masterlists:
- LatestToolkitFiles.ini 3124
- AndroidDeviceListFull.ini 3124
- AndroidDeviceListFlash.ini 3124
ANGLER-ANGLER: Android 6.0.0 - Any Build
Live log initiated [2016-07-31]:
Further extracting contents of factory image package for use in 'Force Flash Mode'...
Checking ADB/FASTBOOT Connectivity
adb devices
fastboot devices
5VT7N15A25003518 fastboot
Connectivity Status: Fastboot Device Connected
+ Confirmed: Bootloader Unlocked.
fastboot getvar product
product: angler
finished. total time: 0.012s
Launching flashstock.bat"
Click to expand...
Click to collapse
Have you tried just downloading the nexus6p IMG and using the flash-all command? I've always been able to recover that way. It restores everything to stock and wipes everything. If it still doesn't work then I would assume a hardware issue. Unless your PC drivers are messing with the process. Some USB hardware can have issues.
Gizmoe said:
Have you tried just downloading the nexus6p IMG and using the flash-all command? I've always been able to recover that way. It restores everything to stock and wipes everything. If it still doesn't work then I would assume a hardware issue. Unless your PC drivers are messing with the process. Some USB hardware can have issues.
Click to expand...
Click to collapse
Could you tell me where I could find the nexus6p img file at and how to flash all command? Seems like most are files I come across are zip files.
*edit: I downloaded the latest version from https://developers.google.com/android/nexus/images did the flash all command and it still hangs on the white Google screen. Although, it did say it couldn't flash boot.sig, recovery.sig, vendor.sig, and etc.. but still completed the flash? I did have all the files unzipped in the same folder of the platform-tools. I just held shift + right clicked the folder and opened the run command window. Am I missing something?
duplicate*
Subiegsr said:
Could you tell me where I could find the nexus6p img file at and how to flash all command? Seems like most are files I come across are zip files.
Click to expand...
Click to collapse
You should try to flash by choosing different stock rom N
Except any stock rom. I will try to flash any android N stock rom by checking Device is normal or no soft brick. If phone boots up fine, u can flash back any to different stock rom like 19X....
luckyfate said:
You should try to flash by choosing different stock rom N
Except any stock rom. I will try to flash any android N stock rom by checking Device is normal or no soft brick. If phone boots up fine, u can flash back any to different stock rom like 19X....
Click to expand...
Click to collapse
doesn't seem any rom is working when booting clean from twrp.
Subiegsr said:
Could you tell me where I could find the nexus6p img file at and how to flash all command? Seems like most are files I come across are zip files.
*edit: I downloaded the latest version from https://developers.google.com/android/nexus/images did the flash all command and it still hangs on the white Google screen. Although, it did say it couldn't flash boot.sig, recovery.sig, vendor.sig, and etc.. but still completed the flash? I did have all the files unzipped in the same folder of the platform-tools. I just held shift + right clicked the folder and opened the run command window. Am I missing something?
Click to expand...
Click to collapse
Usually you would want to run it from an elevated command prompt and navigate to folder and just type flash-all.bat, as long as adb tools are in environment variables it will work. But if it made it all the way to flashing vendor, wiping data and then rebooting it should have worked. This seems like the symptoms of a bad chip. Bad luck I'm guessing. You could try another PC just to be sure but I would trade it in if it was me.
Gizmoe said:
Usually you would want to run it from an elevated command prompt and navigate to folder and just type flash-all.bat, as long as adb tools are in environment variables it will work. But if it made it all the way to flashing vendor, wiping data and then rebooting it should have worked. This seems like the symptoms of a bad chip. Bad luck I'm guessing. I would try another PC just to be sure but I would trade it in if it was me.
Click to expand...
Click to collapse
Yeah, the command prompt installed everything successfully. The only other computer I have is a MacPro that I could try to use, but honestly I spent 7 hours today trying to fix the phone and 4 last night.. i think my eyes are done lol. Good call on the bad chip, probably was too hot over the weekend for it. I did talk to Google and they're sending me a replacement. Sucks though, I took care of my battery life crazy to preserve the life, hopefully the refurb one is just as good. Thanks for the help anyways. :good:
Subiegsr said:
Yeah, the command prompt installed everything successfully. The only other computer I have is a MacPro that I could try to use, but honestly I spent 7 hours today trying to fix the phone and 4 last night.. i think my eyes are done lol. Good call on the bad chip, probably was too hot over the weekend for it. I did talk to Google and they're sending me a replacement. Sucks though, I took care of my battery life crazy to preserve the life, hopefully the refurb one is just as good. Thanks for the help anyways. :good:
Click to expand...
Click to collapse
The exact same thing happened to me over the weekend, and I've tried all the steps you did. I'm now at the same conclusion of hardware failure, so will be calling google today for an RMA.
zamula said:
The exact same thing happened to me over the weekend, and I've tried all the steps you did. I'm now at the same conclusion of hardware failure, so will be calling google today for an RMA.
Click to expand...
Click to collapse
That's crazy it happened to you too. Good luck with the replacement. I hope the replacement doesn't have scratches/scuffs. Mine is seriously immaculate.