I'm having problems updating the OS on my unrooted, stock Nexus S I9020A, running on Straight Talk on an AT&T sim. When I purchased it, it was on 2.3.4. As soon as I turned it on (which was prior to the release ICS for this phone), it upgraded itself to 2.3.6 over WiFi via an OTA download. However when ICS came out, it did not upgrade itself OTA, despite waiting several weeks after the OTA appeared to be rolling out here in the US (since I got the 2.3.6 upgrade before I had even put the sim in, I assumed that the fact that I was on Straight Talk should not matter, but I'm not 100% clear on that). In any event, after getting tired of waiting, I updated the OS to ICS 4.0.4 manually by downloading the official OTA zip file manually, copying it to the phone, rebooting into recovery mode, and applying the update. Now that JB has been released, I've waited again for it to update automatically OTA, but no joy. So I again downloaded the official OTA zip file (android.clients.google.com/pa...a/P2lZDQWb.zip), and tried to do it manually. This time, however, I get the following error each time:
Finding update package . . .
Opening update package . . .
Verifying update package . . .
Installing update . . .
Verifying current system . . .
assert failed: apply_patch_space (16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted
As far as I can tell, I'm using the correct file. Currently, from the bootloader my Product Name is Herring; Hardware Version is Rev. 16; Bootloader is ver. I9020XXKL1; Baseband Ver. is I9020UCKJ1; and Carrier Info is AT&T. In Settings, About Phone, it says my baseband is I9020AUCKJ1, and Kernel is 3.0.8-g665123, [email protected] #1, Thus. Feb 2 16:56:02 PST 2012.
I've also tried doing a full reset on the phone, but that doesn't help. Asking it to check for updates doesn't do anything, and I get the same error message when I tried to do it manually as described above after resetting.
Any advice? Hate to be stuck on ICS. Many thanks.
DavRoc said:
I'm having problems updating the OS on my unrooted, stock Nexus S I9020A, running on Straight Talk on an AT&T sim. When I purchased it, it was on 2.3.4. As soon as I turned it on (which was prior to the release ICS for this phone), it upgraded itself to 2.3.6 over WiFi via an OTA download. However when ICS came out, it did not upgrade itself OTA, despite waiting several weeks after the OTA appeared to be rolling out here in the US (since I got the 2.3.6 upgrade before I had even put the sim in, I assumed that the fact that I was on Straight Talk should not matter, but I'm not 100% clear on that). In any event, after getting tired of waiting, I updated the OS to ICS 4.0.4 manually by downloading the official OTA zip file manually, copying it to the phone, rebooting into recovery mode, and applying the update. Now that JB has been released, I've waited again for it to update automatically OTA, but no joy. So I again downloaded the official OTA zip file (android.clients.google.com/pa...a/P2lZDQWb.zip), and tried to do it manually. This time, however, I get the following error each time:
Finding update package . . .
Opening update package . . .
Verifying update package . . .
Installing update . . .
Verifying current system . . .
assert failed: apply_patch_space (16570800)
E:Error in /tmp/sideload/package.zip
(Status 7)
Installation aborted
As far as I can tell, I'm using the correct file. Currently, from the bootloader my Product Name is Herring; Hardware Version is Rev. 16; Bootloader is ver. I9020XXKL1; Baseband Ver. is I9020UCKJ1; and Carrier Info is AT&T. In Settings, About Phone, it says my baseband is I9020AUCKJ1, and Kernel is 3.0.8-g665123, [email protected] #1, Thus. Feb 2 16:56:02 PST 2012.
I've also tried doing a full reset on the phone, but that doesn't help. Asking it to check for updates doesn't do anything, and I get the same error message when I tried to do it manually as described above after resetting.
Any advice? Hate to be stuck on ICS. Many thanks.
Click to expand...
Click to collapse
The patch you are trying to apply fails pre-requisite system check. Probably the wrong version.
Go to https://developers.google.com/android/nexus/images#sojuajzo54k, or get this full Google Factory Image, un-tar/7-zip and run flash-all.bat or flash-all.sh (linux).
Check this out for steps in detail.
Thanks. That's what I thought. And I thought the solution was what you suggested, but I'm afraid it feels over my head. I've been looking for more detailed instructions for someone at my skill level, but have not found them.
I see that the 1st step of the more detailed instructions is to download the Android SDK Tools, but the instructions are written for the Windows tools, and I'm on a Mac. I see that there appears to be a Mac version at developer.android.com/sdk/index.html. However that version appears to be for 64 bit systems, and my old Mini is a 32 bit (running 10.6.8), and, indeed, when I try to run Eclipse (which is what I gather is the program that allows access to the other tools), it says its not compatible with my system. While there doesn't appear to be a 32 bit version of the ADT bundle, I see that there's also a download link for "SDK Tools Only." I'm not clear if that's 32 bit.
So I'm stuck on step one, much less understanding how actually run SDK Manager, and where to put the factory image on a Mac system, and how to issue the linux commands to the phone (I'm guessing that once I'm running the right program on my Mac when I connect the phone via USB I can issue the commands).
So, any idea where there are detailed instructions for doing this on a Mac?
Many thanks.
UPDATE: Never mind, I figured it out. Your answer gave me the phrases to google.
Thought I'd post what worked for me in case it helps others, since I didn't find any tutorials that actually had all steps or all instructions accurate.
I more or less followed the instructions at forum.xda-developers.com/showthread.php?t=1917237 (can't post full links yet, so add the necessary http:// prefix to all links) to download and install ADB and fastboot on a Mac. But you don't need the full ADT Bundle (which is 64 bit so won't work on older Macs). If you scroll down to Download for Other Platforms, you can download the SDK only (I saw on other sites links to download just ADB and fastboot, but wanted to get my stuff directly from Google), and that worked on my 32 bit system. The instructions at the link above about what files you need, and where to put them worked for me (you can put your Android folder as described there anywhere). Key seems to be to have ADB and fastboot in the same directory as the unpacked factory image files that you'll also download. I did not bother with the nano editor steps (because I didn't fully understand what they were doing, and they turned out to be completely unnecessary).
Here's another set of instructions for getting ADB and fastboot only, but I didn't use these: android.stackexchange.com/questions/26612/doing-a-clean-install-of-android-on-nexus-s-galaxy-nexus-or-nexus-7.
I also downloaded the latest factory image from developers.google.com/android/nexus/images (see not above about placement of files).
I then put the phone is USB Debug mode in Settings/Developer Options/USB Debugging.
I then went into fastboot mode by turning off the phone, then press and hold Volume Up, then press and hold Power.
I then more or less followed the step by step instructions here: forums.androidcentral.com/nexus-4-rooting-roms-hacks/223923-guide-nexus-4-factory-image-restore.html, substituting the directories I had created with the downloads above, and the files I had downloaded (these instructions are for a Nexus 4). You'll note, however, that the factory image has batch and shell files with instructions that match those given, and you can see those instructions by opening the bat files or sh files with a text editor. None of the batch or shell files would execute for me though, so I had to do the steps manually as outlined in the link above. Also, the instructions at the link say that for Macs you have to add "-mac" (without the quotes) to each Linus command. That didn't work for me, and I just used the commands as written. I preceded all commands with ./ after having first using the ./ cd command to get to the right directory where the files were located, as noted above. Finallly, Instead of step 5, I did the command ./ fastboot oem unlock.
Hopefully this will help someone else.
Related
So I have read thoroughly and have exhausted every solution I can find, to no avail. That said, here is what I'm dealing with:
I am trying to flash my D2G with the .330 SBF file.
Just so there is no confusion. I am using full admin rights: I got to rsd.exe in the folder, shift-rgt click, etc.
For full discloser, on the bootloader screen (up arrow + power) it says:
Bootloader
D2.35
Battery OK
OK to Program
Connect to USB
Data Cable
Upon flashing I get this error:
ERROR: Phone[0000]: Error sending JUMP command Device API Error: 0xE0020047 Address: 0x82000000 Command: JUMP - on device ID 0.
I have tried putting the sbf file in every suggested folder (my docs, root, root/moto, etc) Nothing works.
My USB is 2.0 so that isn't the issue.
Can anyone help break through this wall? I have been reading and trying for hours. I wouldn't post here unless it was an absolute last resort. Thank you in advance for helping.
strakajagr said:
So I have read thoroughly and have exhausted every solution I can find, to no avail. That said, here is what I'm dealing with:
I am trying to flash my D2G with the .330 SBF file.
Just so there is no confusion. I am using full admin rights: I got to rsd.exe in the folder, shift-rgt click, etc.
For full discloser, on the bootloader screen (up arrow + power) it says:
Bootloader
D2.35
Battery OK
OK to Program
Connect to USB
Data Cable
Upon flashing I get this error:
ERROR: Phone[0000]: Error sending JUMP command Device API Error: 0xE0020047 Address: 0x82000000 Command: JUMP - on device ID 0.
I have tried putting the sbf file in every suggested folder (my docs, root, root/moto, etc) Nothing works.
My USB is 2.0 so that isn't the issue.
Can anyone help break through this wall? I have been reading and trying for hours. I wouldn't post here unless it was an absolute last resort. Thank you in advance for helping.
Click to expand...
Click to collapse
Confirm that your SBF file is not corrupt. Try downloading it from a different source and check hashes
I have tried 3 sbf's thus far. 2 .330's (from different locations) and 1 .290. The error message is always the same. I'm not sure if it matters, but I have clockword mod installed on my phone as well as Fission.
I'm not sure if having Mods and roms who affect your phone. But just incase have you tried clearing the cache,data,partition from the recovery menu?
I have... again, no luck. It just appears that rsd lite flat out can't communicate with my phone even though it definitely SEES the phone when it's connected. For the life of me I can't figure out why. I found ONE thread on another site where someone posted the same error and reported the same problem. Someone linked him to a boiler plate SBF installation instruction page, which obviously I have tried unsuccessfully several times. It's killing me knowing that there is so much more performance in my phone that I just can't get. My original Droid outperformed this POS. UGH
That certainly is frustrating. The only thing I can think of is trying a different USB cable that is shielded or otherwise, or another computer/OS maybe it's causing a error. If you've already tried that with no results, all I can say is sorry man and keep trying.
I was just reading this thread: http://forum.xda-developers.com/showthread.php?t=1236781 where the final poster said there are a couple of bad .330 sbfs circulating the web, and that the best way around it was to try to sbf a .29 and then ipdate from there.
BTW, op, I agree. My droid one can kick my D2G's ass blindfolded.
Good luck,
Dan
Hi mate, i have had this issue before, please try this as this is the way around my issue =
follow this link and download the rar file (http://www.multiupload.com/FIW8B8TJ7I), flash this file (using rdslite 4.9 , Make sure it is rds lite 4.9!) = http://www.mediafire.com/file/9c6u55c26e1h9y1/RSD Lite 4.9.rar
Being on clock work etc... wont make a differnce but to put your phone in boot loader mode, please do it this way and not the other loaders way.
turn off the phone, press and hold the up and down volume buttons together (make sure you are pressing and holding them down together keep them hold down and dont let go) press the power button while still holding the volume buttons and wait till bootloader comes and then let go, onces it says it in there
Launch RSDLite (make sure device appears in window)
Select SBF (doesnt matter where the file is, just point it to the right place)
click start.
Once it gets to 100% , pull it out and restart the phone (it should reboot it normally but I find it doesn't always do it) so either unplug and let it reboot or pull the battery out and reboot, fingers crossed it will boot in to stock and then you can upgrade from there.
"No such file or directory" help!
Hello,
I am having issues following these instructions as a part of the instructions from
droidforums' root-droid-1-regardless-os-version
after running this:
chmod +x sbf_flash
Then running
sudo ./sbf_flash update.zip
I get the following:
[email protected] ~ $ sudo ./sbf_flash update.zip
[sudo] password for gjohnhazel:
SBF FLASH 1.24 (mbm)
opticaldelusion
update.zip: No such file or directory
Usage: sbf_flash <filename>
My Droid is plugged in, with update.zip in the root of the SD Card and Bootloader 2C.7C with Transfer Mode set to USB.
Can anyone help?
Note: Where it says "opticaldelusion" it's actually the link, but I'm not allowed to have hyperlinks in this message.
sbf_flash is used to load an SBF image (which should be stored on your PC for sbf_flash to access it) into your phone.
It's not a tool to flash OTA/normal update packages.
To flash a normal update.zip you need to use either stock (for stock firmware updates) or ClockworkMod Recovery (for custom ROMs).
Need URGENT help............? Nexus S. Problem with Android Bootloader Interface or perhaps i don't have any idea what the problem is.
I am using nexus s 19020T, rooted, clockworkmod . My problem starts with ICS update. I got update and tried to install it. I got bellow error
"Opening update package...
Installing update...
Verifying current system...
failed to stat "/system/app/Gmail.apk": No such file or directory
file "/system/app/Gmail.apk" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/app/Gmail.apk", "94d64de3d567cb9205f52a734e95f9053e6e6e99", "e2a3cf5648dbfa057787610d3f35f557297ea6bb")
assert failed: apply_patch_check("/system/app/Gmail.apk", "94d64de3d567cb9205f52a734e95f9053e6e6e99", "e2a3cf5648dbfa057787610d3f35f557297ea6bb")
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/update.zip")
"
Then i reverted every thing back to 2.3.1 (nandroid backup). Now I am not able to become superuser. But I got 2.3.6 OTA. Again tried to update super user binaries. I am getting error "signature verification failed. Installation aborted."
I able to access the adb via command prompt whenever my mobile is power on but when I am in fastboot I am not able to access adb and fastboot commands. I can clearly see whenever device reboots under "devmgmt.msc" Android Phone - Android Bootloader Interface is disappearing.
It seems same problem faced here http://forum.xda-developers.com/archive/index.php/t-1304158.html. But in my case I don't have clockworkrecovery access also, My mobile is just unlocked without root access. I don't have any idea how to install image. At least I want to install clockwork recovery. Is there any other way around to do that?
Please let me know if you need further information.
Thanks in advance. Really not being a superuser sucks..........!
Earlier few days i tried [ROM][AOSP] ICS build for Nexus S - kwiboo for few days and back to 2.3.6 using rommanager. Is it got to do any thing with " ICS build for Nexus S"?
Try format /system, becareful not to format the wrong partition. Then flash a full ROM, eg. 4.0.3 full ROM (about 160MB). Apply root afterwards.
Si_NZ said:
Try format /system, becareful not to format the wrong partition. Then flash a full ROM, eg. 4.0.3 full ROM (about 160MB). Apply root afterwards.
Click to expand...
Click to collapse
May I know the procedure? Because I am not able to install any rooted application and I am not able to use adb/fastboot commands while I am in Fastboot mode.
My problem seems to be faced by one person http://forum.xda-developers.com/archive/index.php/t-1304158.html. But in my case I don't have clockworkrecovery access also, My mobile is just unlocked without root access.
229 views no reply...!
When in bootloader mode, does fastboot devices display the device ID correctly?
sorry i don't know how to solve it
suksit said:
When in bootloader mode, does fastboot devices display the device ID correctly?
Click to expand...
Click to collapse
yup we can see device serial number in fastboot mode.
sriharshavr.y said:
May I know the procedure? Because I am not able to install any rooted application and I am not able to use adb/fastboot commands while I am in Fastboot mode.
Click to expand...
Click to collapse
Try read the stickied thread for rooting carefully. You need to get at least fastboot working, so that you can flash CWM. I suspect you have a driver issue. Believe it or not, doing it in Linux is probably easier than you think... Most modern Linux distributions have drivers for these phones out of the box. When I was trying to resurrect my bricked phone, I used the Ubuntu live CD. It detected the phone on the live CD without me doing anything! If you want, you can read the stickied root guide for Ubuntu. Do it in a VM or install it on a spare computer, whatever you prefer.
You need to install stock rom from rom manager ver 2.3.3 then update to 2.3.6 then apply the update.zip from the stock recovery =] that worked for me
irizwan said:
You need to install stock rom from rom manager ver 2.3.3 then update to 2.3.6 then apply the update.zip from the stock recovery =] that worked for me
Click to expand...
Click to collapse
Hey irizwan thaks for giving reply. But here my problem is, I lost super user binaries and I am not able to install anything which requires root access.
sriharshavr.y said:
Hey irizwan thaks for giving reply. But here my problem is, I lost super user binaries and I am not able to install anything which requires root access.
Click to expand...
Click to collapse
Opps sorry ... i don't know how to help you here ... right now i'm on ICS completely stock waiting for a stable root =]
sriharshavr.y said:
yup we can see device serial number in fastboot mode.
Click to expand...
Click to collapse
If fastboot devices command works, then you shouldn't have any problem installing CWM recovery.
Put the downloaded recovery image in the same directory as fastboot.exe then use the command fastboot flash recovery your-downloaded-recovery.img to flash it.
Si_NZ said:
Try read the stickied thread for rooting carefully. You need to get at least fastboot working, so that you can flash CWM. I suspect you have a driver issue. Believe it or not, doing it in Linux is probably easier than you think... Most modern Linux distributions have drivers for these phones out of the box. When I was trying to resurrect my bricked phone, I used the Ubuntu live CD. It detected the phone on the live CD without me doing anything! If you want, you can read the stickied root guide for Ubuntu. Do it in a VM or install it on a spare computer, whatever you prefer.
Click to expand...
Click to collapse
Can I have link or some resource for more information to follow the above mentioned procedure because I am quiet new to linux.
I actually formatted my 'nexus s' with windows 7 operating system, because win 7 is prompting when ever I plugged in my mobile to access sdcard. My question is
"Is there any relation between formatting sdcard and corrupting bootloader"?
You can ROOT your device very easy...
first download : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your device and click run.bat
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
sriharshavr.y said:
Can I have link or some resource for more information to follow the above mentioned procedure because I am quiet new to linux.
Click to expand...
Click to collapse
If you have a 9020T, follow this guide http://forum.xda-developers.com/showthread.php?t=895545
If you have a i9023 or i9020A, follow this guide http://forum.xda-developers.com/showthread.php?t=1007782
Try that first, hopefully you can get fastboot working in Windows. Otherwise, I have to walk you through the steps to do it in Ubuntu.
Here is the OTA file thanks to the user: OTA update file from here http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
I have more instructions at the bottom but you take the OTA file and change the file type from .cfg to .zip and you use that (no other modifications to the file)
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked. I had to google how to run adb and where to get it. You can get adb from developer.google.com download the SDK (which will be in a zip). Extract the SDK and then run the sdkmanager.exe, after that choose the android SDK tools and platform tools. ADB will be in platform tools. Then you open up a command line window and you navigate to the folder that was created when you unzipped the SDK. Once you get there, you then navigate to the platform-tools folder (which is created when you run sdkmanager and install the androidsdk platform-tools). Once you get to platform tools use the command dir to see if adb.exe is there (which it should) then run adb devices (have your phone connected) and it should show a device connected. After that put your phone in recovery and then do the adb sideload and it will be waiting for you to run the command on the command line. Then on the computer you run the adb sideload blah.zip (it's posted on the first post also) and then.....wait everything should work.
I created this so we won't hijack the MJ6 to MJ9 thread and that way that can stay on topic for those users.
Good work, but you should fix your link to be http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
It's the truncated "..." version and doesn't work currently.
Ota link
raidel00 said:
Here is the OTA file thanks to the user: OTA update file from here http://forum.xda-developers.com/show...&postcount=325
I have more instructions at the bottom but you take the OTA file and change the file type from .cfg to .zip and you use that (no other modifications to the file)
Boot to recovery mode now and select Apply update from ADB.
Back on your computer... command: adb sideload whatever you named the OTA file you downloaded.zip
What I did was change the file type of the file for example it's blah.cfg I changed the .cfg to .zip and then I put the phone in recovery mode. When you get to recovery mode it gives you different options and you choose the one that says ADB sideload. You then run the command that was put in the first post (I also put the .zip file in the same folder as the folder that the adb is located in) and then I ran the sideload and it worked. I had to google how to run adb and where to get it. You can get adb from developer.google.com download the SDK (which will be in a zip). Extract the SDK and then run the sdkmanager.exe, after that choose the android SDK tools and platform tools. ADB will be in platform tools. Then you open up a command line window and you navigate to the folder that was created when you unzipped the SDK. Once you get there, you then navigate to the platform-tools folder (which is created when you run sdkmanager and install the androidsdk platform-tools). Once you get to platform tools use the command dir to see if adb.exe is there (which it should) then run adb devices (have your phone connected) and it should show a device connected. After that put your phone in recovery and then do the adb sideload and it will be waiting for you to run the command on the command line. Then on the computer you run the adb sideload blah.zip (it's posted on the first post also) and then.....wait everything should work.
I created this so we won't hijack the MJ6 to MJ9 thread and that way that can stay on topic for those users.
Click to expand...
Click to collapse
Your link is short. http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
Bimboy said:
Good work, but you should fix your link to be http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
It's the truncated "..." version and doesn't work currently.
Click to expand...
Click to collapse
silrosriv said:
Your link is short. http://forum.xda-developers.com/showpost.php?p=47452029&postcount=325
Click to expand...
Click to collapse
Ok...fixed it. Thanks for pointing it out!:good:
Help!
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
does this wipe the device? or does it keep all your apps / data?
Update
I just chatted with someone at Samsung. The OTA has been pulled for issues by AT&T.
silrosriv said:
I just chatted with someone at Samsung. The OTA has been pulled for issues by AT&T.
Click to expand...
Click to collapse
probably due to some users having some issues with mms
silrosriv said:
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Interesting....It worked so smooth for me I don't know what else to say.
jherring002 said:
does this wipe the device? or does it keep all your apps / data?
Click to expand...
Click to collapse
If you do it by sideloading it from the computer it will not wipe the device. If you do it by running it from the SD card....it will wipe the device.
silrosriv said:
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
I get the same error. At this point, I may odin to stock and try again. Or, just forget it and root again and stay on MF3.
dwanhala said:
I get the same error. At this point, I may odin to stock and try again. Or, just forget it and root again and stay on MF3.
Click to expand...
Click to collapse
You might want to hold off for a while. It has been reported that the S4 4.3 OTA has been pulled due to "problems". AT&T is supposed to offer the OTA again at a later unspecified date. I would wait until the "problems" are ironed out and try for the OTA when it is re-released...if you still want it.
scott14719 said:
You might want to hold off for a while. It has been reported that the S4 4.3 OTA has been pulled due to "problems". AT&T is supposed to offer the OTA again at a later unspecified date. I would wait until the "problems" are ironed out and try for the OTA when it is re-released...if you still want it.
Click to expand...
Click to collapse
Yup. I chatted with someone at Samsung. The OTA has been pulled for issues by AT&T.
I think I'll jist wait for it to come back.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
It's working pretty good on my phone. I quit using the lookout security app though. It's not really needed. I know they pulled galaxy s3 update.
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
silrosriv said:
Ok, I redownloaded the cfg file, didn't touch anything except changing the file extension from .cfg to .zip. Rebooted to recovery, adb sideload, I get E:Error in /tmp/update.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Had the same problem when I tried to sideload the update. I was on MF3 and was rooted. What worked for me was to delete all busybox files and unroot using SuperSU and odin back to stock, just in case. After that, I was able to sideload and the phone booted up with no problems.
It works pretty good on my phone also. Was on mj6 and it was having random FC's also random vibrating but now on mj9 I don't have those problems anymore.
Sent from my SAMSUNG-SGH-I337 using xda premium
Thanks
Sent from my SAMSUNG-SGH-I337 using Tapatalk
I was getting the same error. What I did was re-load mf3 (via odin) and then sideload this update.
scott14719 said:
You might want to hold off for a while. It has been reported that the S4 4.3 OTA has been pulled due to "problems". AT&T is supposed to offer the OTA again at a later unspecified date. I would wait until the "problems" are ironed out and try for the OTA when it is re-released...if you still want it.
Click to expand...
Click to collapse
Yeah, at this point I just rooted again (which of course set my device status back to official from the custom that it had changed to when I unrooted) and I'll wait to see if AT&T is going fix the problems before proceeding.
finally
I can't believe it
- Restore my S4 AT&T to 4.2.2 stock with Odin all the 4 files in MF3 using (download mode)
- Sideloaded to 4.3 ...MJ9 File with the Framework using (recovery mode)
Now my phone is even rooted with SuperSU (starting the root with vroot and converting it to SuperSU)
with the following sort video tutorial that found on youtube this morning
youtube.com/watch?v=isHYNqWCfSc
Hey All,
This is my first ever post on XDA ,So forgive me if I have not done a good job. I will try my best to provide sufficient details on how to upgrade LG urbane 2nd Edition Verizon model watch to Android wear 2.0 from Android wear 1.5
Known Issues : **********Android Pay is not working as reported by few users ***********
YOU FLASH THESE FILES AT THE RISK OF BRICKING YOUR DEVICE. I AM SIMPLY PROVIDING THEM AND BEAR NO RESPONSIBILITY FOR ANY SUBSEQUENT DAMAGE FROM FLASHING THESE FILES. ALL DATA ON THE PHONE WILL BE ERASED.
Prerequisites:
[*]LG Urbane 2nd Edition Verizon Model (W200V) for all other model you should have received a OTA by now , Please check OTA software updates on you watch.
[*]ADB tools ( Minimal is also sufficient) google for files and install in your computer , in my case I did it in "C:\adb".
[*]twrp-3.1.1.0 (twrp-3.1.1.0.img) recovery Image Copy of the file :- https://drive.google.com/drive/folders/0Bzk4DPXefDhrRzl3ckh6Uzhad1k
[*]Android Wear 2.0 OTA udpate Copy of the file :- [*]Modified file link http://www.filehosting.org/file/details/699795/lg2.zip or original file https://android.googleapis.com/pack.../af88cfbc96ad65e7b728e27c2decbdc6fb0e08e8.zip
[*]notepad++ (to edit updater-script), You can use Notepad as well.
1)perform factory reset on your watch just to be on safer side.
**update** Few users have reported that they have faced error while flashing due to buggy USB cable and they could successfully overcome the error by holding the cable to the watch and making sure the cable is fully in contact with the watch while flashing .**Update**
2)now we need to modify the OTA update file to work with Verizon model W200V ( skip this step if you have downloaded modified zip file and jump to 3rd step)
unzip the 'af88cfbc96ad65e7b728e27c2decbdc6fb0e08e8.zip" downloaded earlier and Browse the folder Edit file (updater-script) the file can be fount in the below path in my case."C:\ADB\af88cfbc96ad65e7b728e27c2decbdc6fb0e08e8\META-INF\com\google\android\updater-script". Use Notepad ++ and open the file and Remove 2 first rows,The file should start from "ui_print...", I used Note++ to edit the file and saved, as mentioned earlier you can use notepad as well.
Now Zip All files And name LG2.zip(Note : don't put all the files into a single folder and then zip, The zip should contain "META-INF" and other files) and place it in "C:\ADB\LG2.zip" for easier navigation in Cmd. (this file can be downloaded using above link Modified file")
3)next Connect your LG Urbane 2nd Edition watch to Computer and Enable ADB Debugging On watch (Settings-About-Tap about 8 times on "Build Number" and now go back to Setting and scroll down you should see new options "Developer Options" , Tap on "Developer Options" - and "ADB Debugging" select "Enable always from this computer" or something like that !!)
4)Now Check if your device has a connection to your computer using ADB tools
now on your computer under "Run" , type Cmd, this will bring windows command prompt.
Open Cmd in Windows and browse to ADB tools folder in my case I have placed ADB tools and all required files under "C:\abd"
Type "adb devices"
your device should show up under "List of devices attached"
Once device is found by computer we have to push the TWRP recover image to phone , To make life easy , I have downloaded all the above mentioned files to "C:\adb" folder
"adb push twrp-3.1.1.0 /sdcard/"
later boot into bootloader
"adb reboot bootloader"
Unlock bootloader
"fastboot oem unlock"
5)Now flash TWRP recovery (because we will be changing/modifying the original the OTA update file, stock recovery will fail to verify signature)
"fastboot flash recovery twrp-3.1.1.0.img"
boot to recovery to perform OTA side load
"fastboot reboot recovery"
Now you should see TWRP recovery welcome page,Allow read and write partition permission in TWRP.
6)now on your phone you should be in TWRP Main screen , press Install and you will find option to adb Sideload select that option and you will be presented with a option to wipe Dalvik and Wipe Cache , Select that and now go back to your cmd and type below code.
"adb sideload lg2.zip"
Now sit back and relax , The system will starts loading Android Wear2.0 to your verizon LG urbane 2nd edition watch (W200V) and once the process is finished , reboot to system.
1st boot will take some time , Have patience !! after all you have done ever thing right till now. (approx 5-10 mins, sometimes 15 mins)
Now your watch has Android wear 2.0 , enjoy.
Initially it might feel the OS is slow but allow the OS to settle down after that its snappy and the battery backup is also good in my opinion.
If you want to restore Stock recovery image just in case if you don't like TWRP, then
download the below targz file and extrat recovery.img file , LG Urbane 2 stock recovery image.
Link ,
enable ADB options under settings similar what we performed earlier.
1) Boot into bootloader
"adb reboot bootloader"
Stock Android wear 1.5 for LG Urbane 2nd Edition LTE(extract the file and copy recovery.img file to your folder , https://storage.googleapis.com/andr...wear-preview/nemo-mfd18l-factory-3faf6f2d.tgz (The file extension is */tgz(targz) , use 7zip application to extract the files and you will see recovery.img file .
Place a copy of recovery.img in "C:\adb\recovery.img"
"fastboot flash recovery recovery.img"
You can also Lock Bootloader to avoid the Notification at each boot.
"fastboot oem lock"
To get back to original android watch wear 1.5
if you don't like Android wear 2.0 use the below link and follow instruction to revert back to Android wear 1.5.
Stock Android wear 1.5 for LG Urbane 2nd Edition LTE , https://storage.googleapis.com/andr...wear-preview/nemo-mfd18l-factory-3faf6f2d.tgz (The file extension is */tgz(targz) , use 7zip application to extract the files.
Extract the *.tgz(targz) into your folder ("C:\adb")
Perform a "fastboot oem unlock", then run "flash-all.bat". Afterwards, you can "fastboot oem lock". This should restore you back to 1.5, where you need to take 1 OTA (from June 2016 Patch to December 2016 Patch).
Thanks All,
Missed something
Tried a thousand times. Not working **update** Looks like maybe It was just a buggy USB. I held it to the watch while flashing and it finally worked! I'm curious to hear anyone else's experiences with this cause it seems buggy but what would you expect? My apologies ty!
Has anyone other than the original poster tried this guide and been successful?
Thxfctr said:
Tried a thousand times. Not working
Click to expand...
Click to collapse
Are you getting any specific error ?
djdubd said:
Has anyone other than the original poster tried this guide and been successful?
Click to expand...
Click to collapse
It does work I had problems but I think holding the USB to the watch helps. I tried it a lot but it was worth it. Suck it verizon!
Thxfctr said:
Tried a thousand times. Not working **update** Looks like maybe It was just a buggy USB. I held it to the watch while flashing and it finally worked! I'm curious to hear anyone else's experiences with this cause it seems buggy but what would you expect? My apologies ty!
Click to expand...
Click to collapse
I am Glad finally it worked for you!!
suresh.chikkanna said:
I am Glad finally it worked for you!!
Click to expand...
Click to collapse
Ty! I think my USB connector is just a bit jinky.
I'm going to give this a try soon, everything working like lte, messages+, and phone?
Almost got it working
Followed all the directions and all seemed to work ok without errors. However, on startup now the watch is stuck on the startup splash screen (the animated google logo, has stayed there for hours). Can still access fastboot but unable to connect via ADB since the OS is not starting fully.
I also tried to restore back to 1.5 but since i can only access fastboot, my only option is to sideload but wont work with the TGZ link above.
Anyone have any ideas? or the zip file I could use to sideload the stock Wear1.5?
Thanks
Just making sure !! Try force restarting the watch by holding power button.
Did you reset the watch before sideloading ?
On android wear 1.5 use 7zip and unzip the tgz file and browse the folder till you see flashall bat file and run the same in bootloader. I have tried it and it works. Let us know if your still facing issues.
Locked /data won't allow sideload.
Hi, I've installed twrp, but it fails to sideload LG2.zip as the /data can't be mounted as it is encrypted. The TWRP doesn't have a format option for the /data partition so I can't reformat it to delete the encryption. So I'm stuck in TWRP.
Gphoton31 said:
Hi, I've installed twrp, but it fails to sideload LG2.zip as the /data can't be mounted as it is encrypted. The TWRP doesn't have a format option for the /data partition so I can't reformat it to delete the encryption. So I'm stuck in TWRP.
Click to expand...
Click to collapse
I had similar issue initially , had to restore back to 1.5 and then clean all the data and then sideload 2.0 back. Try that and let us know if that worked.
You are the man! That worked
Installed recovery.img bootloader, then ran the 1.5 bat file, then reinstalled twrp. /data unlocked and mounted, sideloaded 2.0. You turned my brick back into a watch. Thank you very much.
suresh.chikkanna said:
Just making sure !! Try force restarting the watch by holding power button.
Did you reset the watch before sideloading ?
On android wear 1.5 use 7zip and unzip the tgz file and browse the folder till you see flashall bat file and run the same in bootloader. I have tried it and it works. Let us know if your still facing issues.
Click to expand...
Click to collapse
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Solved flash-all not working
OzzieJez said:
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Click to expand...
Click to collapse
As with some other users the cable connection seemed to be causeing me some problems. I used a different USB port and held the connector against the watch and flashing to 1.5 worked this time.
---------- Post added at 06:37 PM ---------- Previous post was at 06:05 PM ----------
OzzieJez said:
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Click to expand...
Click to collapse
As with some other users the cable connection seemed to be causeing me some problems. I used a different USB port and held the connector against the watch and flashing to 1.5 worked this time.
Gphoton31 said:
Installed recovery.img bootloader, then ran the 1.5 bat file, then reinstalled twrp. /data unlocked and mounted, sideloaded 2.0. You turned my brick back into a watch. Thank you very much.
Click to expand...
Click to collapse
I am really happy for you.
OzzieJez said:
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Click to expand...
Click to collapse
Flash the original recovery.img extracted from the .tgz file and try again it should work.
For ADB access in TWRP use sideload using ADB option .
So will android pay work now with this
B
OzzieJez said:
Thanks.
I made sure to reset before force restart and reset before sideloading. Still having some trouble with the 1.5 reset though.
In bootloader, which option to I select for flashall to work? ADB Devices can't see it and if i just run from bootloader home screen i get , <waiting for any device>. Same thing in TWRP.
Thanks again for your help
[Note for other users unfamiliar with this process & having similar problems - you'll have to unzip the source file, then unzip "output" to extract all the files... tooke me a few attempts to realize i missed a step!]
Click to expand...
Click to collapse
I think I am having the same issue as you. I was sideloading 2.0 as instructed and I think I had a bad cable connection. I am now stuck with no wear operating system at all. When I start my phone it only stays on LG boot screen with the unlock icon on the bottom. My computer is now unable to recognize the device because I cannot get into settings to turn on ADB Debugging. If I follow the same steps as you can I sideload wear 1.5 and update via boot loader screen?
I think I am having the same issue as you. I was sideloading 2.0 as instructed and I think I had a bad cable connection. I am now stuck with no wear operating system at all. When I start my phone it only stays on LG boot screen with the unlock icon on the bottom. My computer is now unable to recognize the device because I cannot get into settings to turn on ADB Debugging. If I follow the same steps as you can I sideload wear 1.5 and update via boot loader screen?
For background, I have Verizon pixel 2 and am using a Mac.
I went down a massive rabbit hole last night reading through these forums and all the posts and was able to unlock bootloader, flash the January OTA and then root by doing the modified boot file with magisk. (interestingly enough the booting into recovery gives me red ! Over a dead Android and I could not load the OTA that way, nor did the adb sideload OTA comand work either, I had to push the extracted walleye img and then the zip file as discussed in one of the steps in some other thread here)
So anywho, in the end I now have a phone that gives me 2 errors when it reboots, one for unlocked bootloader and another for root telling me something is wrong with my phone and i should contact the manufacturer (which I read on here is normal), but my biggest issue is that my ADT alarm app doesn't work anymore (even if i check it off for hide in magisk). I feel like the root is just not worth it for me and I want to revert to completely stock image, even if it resets my phone and I have to re back everything up all over again like did when i had to do the unlocking of the boot loader.
So -- What are the steps I should take?
1)uninstall magisk from magisk manager?
2)delete magisk manager?
The above will unroot me, correct?
3)Do I push the stock boot image file onto the phone?
4) do I have to repush the latest OTA walleye image and zip file onto the phone again?
5) do I then do the adb reboot and do the flashing lock command (same command i did to unlock the boot loader) to lock up the bootloader and reset to stock?
If someone could be as explicit as possible in correctiong or validating my steps above it would be much, much appreciated.
I don't want to do any more unnecessary steps in flashing things than is needed so if I have extra steps above (perhaps 4 is not needed?) Let me know.
Thanks
Proceed with Caution
I am not an expert by any means, but can speak from personal experience. I was in the exact same situation as you. I followed the detailed steps to unlock the bootloader on my pixel 2, received similar issues, and the same prompt when the phone rebooted. All that to say proceed with caution.
My thoughts on questions 1 & 2: I personally wouldn't recommend you remove or delete magisk from the manager. When I did i had to reinstall it via twrp. My phone functioned fine, apart from the error at reboot.
My thoughts on questions 3 -5: When I followed the steps on XDA for your questions here I ended up bricking my Pixel 2 with locked bootloader from Verizon. Probably an error on my part, but wouldn't want someone else to go through the headache, hours of issues, and then an expensive paper weight.
My suggestion would be to:
1. Leave your phone as is and attempt to trouble shoot the app or apps you are having issue with
2. contact Google support on your phone and see if they would replace it
3. wait for an established method to unroot the pixel 2 here
Thankfully Google replaced my phone due to the error after rebooting, prior to me bricking it. I knew I had a replacement phone coming. So I attempted to go back to stock and that is when I messed it up.
Note sure this is exactly what you were looking for, but hope this helps you.
Dozens of posts with hundreds of pages on how to root but no advice on how to go back to stock cleanly?
iridium7777 said:
Dozens of posts with hundreds of pages on how to root but no advice on how to go back to stock cleanly?
Click to expand...
Click to collapse
Your version is Verizon which is making things more complicated. Generally when the bootloader is unlocked, you just hit flash-all.bat and then relock the phone. Given that the Verizon I'm not sure.
So you are on stock ROM with all these apks loaded ? If you go to settings, then do a factory data reset, you'll reset the phone back to stock and completely wipe the phone and return it to stock, at that point you can go into bootloader mode and relock.
Again your bootloader is unlocked, so the flash-all is your best option. If you see the red exclamation point with the error android laying on his back, you press power and up volume and toggle that and it will bring in the stock recovery which you can sideload the OTA however it may fail since you have magisk.
I bought my phone stock last year and have not rooted it or modified it in anyway. Too many problems and it only gets harder and harder as Google releases a new phone.
@mikeprius -- thank you for replying. after reading more on here, it seems like that's the way to go -- flash-all script, seems like i don't really need to do 1&2 that i wrote above as the flash-all will wipe that out by itself.
at that point i should be running the latest stock 8.1 but with an unlocked bootloader (and according boot up message screen) and i should be able to re-do the fastbook unlocking command to lock the phone back up.
(and yes, after reading even more now -- and i tried this yesterday -- i completely missed the portion about PWR + Vol Up button, that's why i think i had that issue, but still, i was able to push the update by pushing img and then the zip through).
iridium7777 said:
@mikeprius -- thank you for replying. after reading more on here, it seems like that's the way to go -- flash-all script, seems like i don't really need to do 1&2 that i wrote above as the flash-all will wipe that out by itself.
at that point i should be running the latest stock 8.1 but with an unlocked bootloader (and according boot up message screen) and i should be able to re-do the fastbook unlocking command to lock the phone back up.
(and yes, after reading even more now -- and i tried this yesterday -- i completely missed the portion about PWR + Vol Up button, that's why i think i had that issue, but still, i was able to push the update by pushing img and then the zip through).
Click to expand...
Click to collapse
If I were in your situation and the bootloader is unlocked, just use flash-all which has a wipe script then call it a day. I think trying to screw around even more is just a waste of time and I wouldn't even bother with the OTA, just erase and flash stock. You don't have to relock your bootloader if you don't want to, if you stay fully stock you may still be able to get OTA updates. I'm not sure if a bootloader locked is required someone can chime in as it has been awhile since I've done this, but over 1 yr ago, I just kept the bootloader unlocked, kept things stock and everything was good to go. Obviously there are security issues with an unlocked bootloader, but I'm sure you know this already
@mikeprius you keep saying reset/erase, do you suggest i re-set the phone and then flash the stock image?
i was just going to flash the stock image, i figured it already wipes the phone, and locking the bootloader would wipe it again, so what's the point of erasing all data prior?
Not to hijack this thread, but a question to add... I thought that there were kernels that would mask certain things to allow all of those apps to work, and get rid of the "problem with device" message.
Is that correct?
iridium7777 said:
@mikeprius you keep saying reset/erase, do you suggest i re-set the phone and then flash the stock image?
i was just going to flash the stock image, i figured it already wipes the phone, and locking the bootloader would wipe it again, so what's the point of erasing all data prior?
Click to expand...
Click to collapse
Just flash the stock images. It will auto reset.
Again, don't mess with anything just flash stock images, then go from there.
Also flash the newest version of the stock images out there. The pixel 2 will error if you try to downgrade any version.
here are all the steps to UNROOT and LOCK the boot loader on your Pixel 2 on a Mac (windblows users simply ignore all the "./" references).
1) download the latest ADB tools from google
2) download the latest factory Walleye image
3) unzip files from 1&2 into a common directory
4) edit flash-all.sh file and add "./" infront of every instance of "fastboot" in the script [windows users ignore this step]
5)hook up your phone to your computer in debug and file transfer mode. check that "./adb devices" loads your devide
6)type " ./adb reboot bootloader"
7) check that your device is still connected by typing "./fastboot devices"
8) type "./flash-all.sh"
===the script will run and your phone will be restored to stock, and UNROOTED. upon boot up skip through all of the setup steps and get to the phone settings as fast as you can. enable developer option, enable debug mode, set phone to data transfer ====
9) check that your phone is connect to your computer by "./adb devices"
10) type "./adb reboot bootloader"
11) check your devices is still connected by "./fastboot devices"
12) type "./fastboot flashing lock"
===== this will re-wipe your device again, you'll see the circle of death, and this will LOCK your boot loader back up again======
side note, feel free to skip over the steps where you check that your phone is still connected to the computer (./fastboot devices) if you're less paranoid and comfortable.
iridium7777 said:
here are all the steps to UNROOT and LOCK the boot loader on your Pixel 2 on a Mac (windblows users simply ignore all the "./" references).
1) download the latest ADB tools from google
2) download the latest factory Walleye image
3) unzip files from 1&2 into a common directory
4) edit flash-all.sh file and add "./" infront of every instance of "fastboot" in the script [windows users ignore this step]
5)hook up your phone to your computer in debug and file transfer mode. check that "./adb devices" loads your devide
6)type " ./adb reboot bootloader"
7) check that your device is still connected by typing "./fastboot devices"
8) type "./flash-all.sh"
===the script will run and your phone will be restored to stock, and UNROOTED. upon boot up skip through all of the setup steps and get to the phone settings as fast as you can. enable developer option, enable debug mode, set phone to data transfer ====
9) check that your phone is connect to your computer by "./adb devices"
10) type "./adb reboot bootloader"
11) check your devices is still connected by "./fastboot devices"
12) type "./fastboot flashing lock"
===== this will re-wipe your device again, you'll see the circle of death, and this will LOCK your boot loader back up again======
side note, feel free to skip over the steps where you check that your phone is still connected to the computer (./fastboot devices) if you're less paranoid and comfortable.
Click to expand...
Click to collapse
hey there. what is the command suppose to look like? every combination I try gives me an error:
first, I don't even enter the Fastboot command the same wayit given me an error:
Asads-MacBook:~ asad$ ./fastboot devices
-bash: ./fastboot: No such file or directory
so I try this: Asads-MacBook:~ asad$ fastboot devices
[serial #] fastboot
these are all the errors I get:
Asads-MacBook:~ asad$ cd /Users/asad/Desktop/walleye-opm1.171019.021
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: fastboot./: No such file or directory
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: ./fastboot: No such file or directory
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
fastboot: usage: unknown command ./flash
...
Asads-MacBook:walleye-opm1.171019.021 asad$ ./flash-all.sh
./flash-all.sh: line 21: fastboot./: No such file or directory
...
how is the command suppose to look that I can edit it the right way?
"fastboot: No such file or directory" means that you didn't do step 1, step 3 on the file you didn't download, and there should probably be a "cd /<whatever the 'common directory'>" is. (I just created a directory named adb. That's good enough for me to know what it's for.)
You have to download adb and fastboot (which come in the adb tools file), unzip them to whatever directory you're going to use for flashing the phone, and cd to that directory.
Then, since you're evidently on MacOS, each command has to have ./ in front of it (that says "the current directory"). Try all that, then see what happens.
Rukbat said:
"fastboot: No such file or directory" means that you didn't do step 1, step 3 on the file you didn't download, and there should probably be a "cd /<whatever the 'common directory'>" is. (I just created a directory named adb. That's good enough for me to know what it's for.)
You have to download adb and fastboot (which come in the adb tools file), unzip them to whatever directory you're going to use for flashing the phone, and cd to that directory.
Then, since you're evidently on MacOS, each command has to have ./ in front of it (that says "the current directory"). Try all that, then see what happens.
Click to expand...
Click to collapse
yayy! that worked!
so i had adb and fastboot in a folder (platform-tools) and i had the factory image in its own seperate folder (walleye-files). i was making the cd; walleye folder and trying to flash-all.sh there.
so i had to put the files from the walleye folder into the platform-tools folder. Then I made platform-tools the cd. now when . i could now follow all the steps from 4-12 and got the pixel 2 the way it was OTB.
thanks!
Great! I'm not a Mac expert (last time I used one was the 128K Mac in 1985), so I'm not sure how to export a path in MacOs, so I gave you the complicated way, but you got it done anyway. (If you ever find out how to add the platform-tools folder to your path, you can leave adb and fastboot in there and keep the ROMs [walleye] in their own folder, cd to it and adb and fastboot will still work.)