Hey.
I come from the Rogers forums. The reason I am making this thread here is because I went over the thread multiple times, including the min-guide and the video-guide for GSM Nexus.
However, myself, as well as a few others, have been having a bit of a problem doing this because it just seems too overwhelming (and complicated) for us, and we were wondering if there is a possibility of getting a "layman's terms" sort of tips, hinters, etc. for it, especially when it comes to backing user data up (like sync accounts, contacts, etc.), and whatnot.
Thanks in advance.
Sorry if I come off as a noob/newb/n00b/whatever. I am a Multimedia student, not a developer or programmer, so I am not familiar at all with Linux programming.
AdelaisAer said:
Hey.
I come from the Rogers forums. The reason I am making this thread here is because I went over the thread multiple times, including the min-guide and the video-guide for GSM Nexus.
However, myself, as well as a few others, have been having a bit of a problem doing this because it just seems too overwhelming (and complicated) for us, and we were wondering if there is a possibility of getting a "layman's terms" sort of tips, hinters, etc. for it, especially when it comes to backing user data up (like sync accounts, contacts, etc.), and whatnot.
Thanks in advance.
Sorry if I come off as a noob/newb/n00b/whatever. I am a Multimedia student, not a developer or programmer, so I am not familiar at all with Linux programming.
Click to expand...
Click to collapse
Its probably better to ask a single particular question when you get stuck, What you have asked is very general.
Go as far as you can with the tool kit and when you have a problem give as much detail as you can so someone can help you.
Tool kits can be fast and easy but you won't learn anything and when you have a bit of trouble its all panic stations.
It's better to learn adb/fastboot, try this guide http://forum.xda-developers.com/showthread.php?t=1529058
gpfnzl said:
Its probably better to ask a single particular question when you get stuck, What you have asked is very general.
Go as far as you can with the tool kit and when you have a problem give as much detail as you can so someone can help you.
Tool kits can be fast and easy but you won't learn anything and when you have a bit of trouble its all panic stations.
It's better to learn adb/fastboot, try this guide http://forum.xda-developers.com/showthread.php?t=1529058
Click to expand...
Click to collapse
Oh. Sorry about that. Well, my main question is how to back user data up using the toolkit. I see options for applications and nandroid and stuff, but I don't see userdata such as contacts, sync accounts, etc. The most important stuff.
That's my main concern first and foremost. Also, I'm checking the guide right now; thanks.
I've just checked the tool kit briefly and don't see an option for what you want to do.
How ever:
contacts will sinc to your google account. On your phone go into
settings>accounts and sync>select your google account and check sync contacts.
"Titanium backup" can save accounts, wifi and alot of other stuff.
gpfnzl said:
I've just checked the tool kit briefly and don't see an option for what you want to do.
How ever:
contacts will sinc to your google account. On your phone go into
settings>accounts and sync>select your google account and check sync contacts.
"Titanium backup" can save accounts, wifi and alot of other stuff.
Click to expand...
Click to collapse
Ah. Alright, contacts, browser, and Google+ are now synced. In terms of user data, what would I really need to back up? I mean, if I flash, I can just redownload Google+, sign in, sync, and get my contacts back and browser data back, right?
EDIT: Also, it says that we need to locate the rom, which has to be .zip. I downloaded it from the Google Developers website, where they have factory images, but they are all .tgz. Is that fine?
EDIT2: Also, under ADB Mode, it never shows my phone's serial, so I can't do backups. :S I have Windows 7 64 bit. Fastboot mode shows the serial, though.
AdelaisAer said:
Ah. Alright, contacts, browser, and Google+ are now synced. In terms of user data, what would I really need to back up? I mean, if I flash, I can just redownload Google+, sign in, sync, and get my contacts back and browser data back, right?
EDIT: Also, it says that we need to locate the rom, which has to be .zip. I downloaded it from the Google Developers website, where they have factory images, but they are all .tgz. Is that fine?
EDIT2: Also, under ADB Mode, it never shows my phone's serial, so I can't do backups. :S I have Windows 7 64 bit. Fastboot mode shows the serial, though.
Click to expand...
Click to collapse
I sync contacts, browser, calendar and gmail with google.
Apps with there user data I save with titanium backup so they can be restored to how they where with the last rom.
The paid version has batch mode so you can do them all at once. After installing a new rom you will have to down load titanium backup again, open it and then restore all your apps.
Factory image: will return your phone to out of the box stock. I personally find stock a bit boring and not so user friendly. Custom roms can be personalized, and the UI easier to use. But thats personal preference.
I have AOKP build 40 that can be down loaded from the xda GNEX development page. use .ZIP roms only
you need to unlock your phone
root
install clockworkmod recovery. the flashing of a new rom is done with clockworkmodrecovery
No serial?
on your PC, go into the"android-sdk-windows" folder, then the "platform-tools folder" and open a command prompt window (shift+right click in the folder then select open command window here)
type in
adb devices
if your serial number does not show up, reinstall the samsung drivers.
gpfnzl said:
I sync contacts, browser, calendar and gmail with google.
Apps with there user data I save with titanium backup so they can be restored to how they where with the last rom.
The paid version has batch mode so you can do them all at once. After installing a new rom you will have to down load titanium backup again, open it and then restore all your apps.
Factory image: will return your phone to out of the box stock. I personally find stock a bit boring and not so user friendly. Custom roms can be personalized, and the UI easier to use. But thats personal preference.
I have AOKP build 40 that can be down loaded from the xda GNEX development page. use .ZIP roms only
you need to unlock your phone
root
install clockworkmod recovery. the flashing of a new rom is done with clockworkmodrecovery
No serial?
on your PC, go into the"android-sdk-windows" folder, then the "platform-tools folder" and open a command prompt window (shift+right click in the folder then select open command window here)
type in
adb devices
if your serial number does not show up, reinstall the samsung drivers.
Click to expand...
Click to collapse
For the rom, can I extract the tgz and re-extract it as a zip?
For the serial/adb stuff - I can't find that folder; where is it supposed to be? Also, do I unlock my phone after this or before? Also how? @[email protected] I totally got lost...
AdelaisAer said:
For the rom, can I extract the tgz and re-extract it as a zip?
For the serial/adb stuff - I can't find that folder; where is it supposed to be? Also, do I unlock my phone after this or before? Also how? @[email protected] I totally got lost...
Click to expand...
Click to collapse
I've never tried the .tgz to .zip so i can't give a accurate opinion.
Have you installed SDK from the guide? or you can google search it and down load it.
It should be in
C:\android-sdk-windows\platform-tools
Titanium backup is only available to root users, so no good for you at the moment.
you can back up apps to google
settings>backup and restore but ive never done it that way, and dont know how well it works.
---------- Post added at 03:06 PM ---------- Previous post was at 03:02 PM ----------
gpfnzl said:
I've never tried the .tgz to .zip so i can't give a accurate opinion.
Have you installed SDK from the guide? or you can google search it and down load it.
It should be in
C:\android-sdk-windows\platform-tools
Titanium backup is only available to root users, so no good for you at the moment.
you can back up apps to google
settings>backup and restore but ive never done it that way, and dont know how well it works.
Click to expand...
Click to collapse
back your sd card up to PC, from memory i think the unlock part wipes your phone
gpfnzl said:
I've never tried the .tgz to .zip so i can't give a accurate opinion.
Have you installed SDK from the guide? or you can google search it and down load it.
It should be in
C:\android-sdk-windows\platform-tools
Titanium backup is only available to root users, so no good for you at the moment.
you can back up apps to google
settings>backup and restore but ive never done it that way, and dont know how well it works.
Click to expand...
Click to collapse
Oh. Well, I downloaded it from the Google Developers (official) website, and they don't offer it in any other file-type. :S I can look it up on Google and see if anyone else says anything about it.
Wait, what? I didn't see SDK in the guide. o___o;
-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-
EDIT:
Okay, let's try again. xD
-I have GNex Toolkit 7.6.
-I installed it.
-I used option 1. to install drivers.
-Fastboot mode works fine. Serial displays.
-ADB mode doesn't (no serial). Apparently, as you say, I need SDK? Didn't see SDK anywhere in the guide, or the video, or the Toolkit software.
ALSO, decided to open the .TGZ file up (that I got from here: https://developers.google.com/android/nexus/images), and here are two screenshots:
http://i49.tinypic.com/2rzb30h.png
http://i47.tinypic.com/96dqo3.png
I tried following this thread and you seem to be talking about two different things. The factory images you downloaded from Google developers, or the .tgz file is what you would use to restore your phone to the factory state, also the state I believe your phone is currently in. Unzipping the appropriate tgz file for your phone will yield the radios and another zip file that will be flashed to restore - do not unzip that file.
As far as your confusion with the android sdk, is your phone currently still locked? It sounds like it is. When I learned to customize my phone I did everything the long way without using a kit - which I highly recommend. That way you not only learn much more, but you'll be able to answer most of the questions you have on your own. Unlocking your phone, fast boot mode, the android platform tools folder, etc have to be properly configured before you can flash anything. You can also do all this via Windows/command prompt, Linux isn't necessary, it's just easier in some respects, ie driver installation and such.
I really would recommend some more research before you jump in and start playing with system/root files.
Sent from my Galaxy Nexus using xda app-developers app
ttahatt said:
I tried following this thread and you seem to be talking about two different things. The factory images you downloaded from Google developers, or the .tgz file is what you would use to restore your phone to the factory state, also the state I believe your phone is currently in. Unzipping the appropriate tgz file for your phone will yield the radios and another zip file that will be flashed to restore - do not unzip that file.
As far as your confusion with the android sdk, is your phone currently still locked? It sounds like it is. When I learned to customize my phone I did everything the long way without using a kit - which I highly recommend. That way you not only learn much more, but you'll be able to answer most of the questions you have on your own. Unlocking your phone, fast boot mode, the android platform tools folder, etc have to be properly configured before you can flash anything. You can also do all this via Windows/command prompt, Linux isn't necessary, it's just easier in some respects, ie driver installation and such.
I really would recommend some more research before you jump in and start playing with system/root files.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Oh. Derp. Well, I edited my post before yours, and I saw it has two images in it (one of them is radio) and a zip file. So yeah, I guess that contributed a lot to my confusion.
Also, I think my phone is still locked. I have done literally nothing to it yet.
Also, I want to flash it because it's currently in a Rogers/Samsung-type OS, where updates aren't pushed because it takes them months to get the A-Okay, for whatever reason. I want to flash it to the Google-line so I can get regular updates without waiting. :S
AdelaisAer said:
Oh. Well, I downloaded it from the Google Developers (official) website, and they don't offer it in any other file-type. :S I can look it up on Google and see if anyone else says anything about it.
Wait, what? I didn't see SDK in the guide. o___o;
-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-
EDIT:
Okay, let's try again. xD
-I have GNex Toolkit 7.6.
-I installed it.
-I used option 1. to install drivers.
-Fastboot mode works fine. Serial displays.
-ADB mode doesn't (no serial). Apparently, as you say, I need SDK? Didn't see SDK anywhere in the guide, or the video, or the Toolkit software.
ALSO, decided to open the .TGZ file up (that I got from here: https://developers.google.com/android/nexus/images), and here are two screenshots:
http://i49.tinypic.com/2rzb30h.png
http://i47.tinypic.com/96dqo3.png
Click to expand...
Click to collapse
LOL i'm starting to see the confusion :s
skd is for manual input, better for you in the long run.
You want to use the tool kit to unlock,root & flash CWM? the sdk install is not needed.
If using the tool kit and you have selected your device type and can see your serial number....
you just need to select from the list what you want to do. there is a choice to do all = the one click method available in the list of options.
the only other thing to do is to have your phone in the right mode, either android or adb.
Is your goal to be able to flash new roms/kernels/radio?
Plug your phone in to pc....reboot your phone into fastboot (vol+/vol- and power) see if drivers install (should see bottom right hand side of computer)
gpfnzl said:
LOL i'm starting to see the confusion :s
skd is for manual input, better for you in the long run.
You want to use the tool kit to unlock,root & flash CWM? the sdk install is not needed.
If using the tool kit and you have selected your device type and can see your serial number....
you just need to select from the list what you want to do. there is a choice to do all = the one click method available in the list of options.
the only other thing to do is to have your phone in the right mode, either android or adb.
Is your goal to be able to flash new roms/kernels/radio?
Click to expand...
Click to collapse
My goal is to back my contacts and app data up, and then flash my phone with the new factory os that I got from Google Developer. :S But this whole guide is ajfkjsdkjfksjfkwejfkjsdkjfakw. Also, sorry for ranting. >___<;
See, if Samsung had just pushed updates to Canadian Android phones in the first place like normal people, I wouldn't be here. But instead, they hold onto updates until they (and Rogers) can stamp their names all over it and then takes a few more months just to approve it a second time, for whatever reason. :S
Instead, I have to come here, try to do this whole thing, and then install that factory Google-line OS so I can get regular updates.
Go look in the Rogers community forums - nothing but threads complaining about it. I'm one of very few who actually came to a forum like this.
OP, have a read of the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
OP, have a read of the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Alright, will do.
Also, sorry if my replies get a bit slow now - eating.
EDIT: Ugh, this is getting reaaly confusing now. o-o; Especially the part where you make a backup of the phone build. @[email protected];
When I get home,
If you haven't found a solution,
I will install ToolKit 7.6 and try to do what you are trying to do, then walk you through it.
gpfnzl said:
When I get home,
If you haven't found a solution,
I will install ToolKit 7.6 and try to do what you are trying to do, then walk you through it.
Click to expand...
Click to collapse
Alright. Thank you. :3
So far, I synced my contacts, browser, etc. up with my Google+ account, so that's backed up, and I can go into fastboot no problem and have the toolkit detect it.
I just wanna make sure that there's nothing else that needs backing up (if there is, then what do I backup, and how?), and then just flash my phone with the new 4.1.1, and be done.
Also, thank you so much for actually putting up with me. A lot of people would normally be rather mean/hateful towards new-comers like me, so thank you.
EDIT: Why must this be so complicated... @[email protected] Curse you, Samsung.
Just for the hell of it, back up your SD card.
We all need a bit of help getting started.
Good luck.
gpfnzl said:
Just for the hell of it, back up your SD card.
We all need a bit of help getting started.
Good luck.
Click to expand...
Click to collapse
Er, how do? o-o;
Plug your phone into your PC
open *my computer* select the *galaxy nexus*, select *internal storage* and copy every thing to your computer.
unlock your lock screen on the phone or your computer wont see the internal storage
Hi everyone,
Complete and total noob with Android / ROM's, just converted from iphone to a nexus 5x. So naturally, I've begun hacking this device. Figured out how get TWRP 2.8.7.2 onto the phone, and I've used ADB (macbook pro, El Capitan 10.11.4) to get the file image-bullhead-mhc19q.zip onto the phone.
When I select this zip, and swipe to confirm Flash, it throws the error in red: Could not find 'META-INF/com/google/android/update-binary' in the zip file
I've downloaded the following tar file, 6.0.1 (MHC19Q), direct from the Google Factory Images web page. When it downloads to my mac downloads folder, I open it, and then compress it into a .zip file. Then, I push it over to the device using ./adb. Am I doing something wrong with the tar to zip conversion?
Can not seem to figure out how to get over this hump, and any guidance is gratefully appreciated!
Thanks, Craig
Read the flashing instructions at the top of the factory images page. You're supposed to flash the factory images with fastboot from the bootloader, not from recovery.
googlenoose said:
Hi everyone,
Complete and total noob with Android / ROM's, just converted from iphone to a nexus 5x. So naturally, I've begun hacking this device. Figured out how get TWRP 2.8.7.2 onto the phone, and I've used ADB (macbook pro, El Capitan 10.11.4) to get the file image-bullhead-mhc19q.zip onto the phone.
When I select this zip, and swipe to confirm Flash, it throws the error in red: Could not find 'META-INF/com/google/android/update-binary' in the zip file
I've downloaded the following tar file, 6.0.1 (MHC19Q), direct from the Google Factory Images web page. When it downloads to my mac downloads folder, I open it, and then compress it into a .zip file. Then, I push it over to the device using ./adb. Am I doing something wrong with the tar to zip conversion?
Can not seem to figure out how to get over this hump, and any guidance is gratefully appreciated!
Thanks, Craig
Click to expand...
Click to collapse
Delete that zip from your phone because it is taking up space. Like the above user said, you need your computer to flash the latest factory image. Here is a guide walking you through each of the steps:
http://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk
Thanks for all of the help - I had missed on step and that threw me. I've managed to get the original stock 5x image back on the phone, and I will [follow][the directions]
http://forum.xda-developers.com/showthread.php?t=3206930
Sent from my Nexus 5X using Tapatalk[/QUOTE]
Anyone else get an error when trying to flash system image 63L? Says boota doesn't exist. I know some partitions are doubled but I assume the image should work. Just wondering if it's my PC drivers or an actual issue with the image itself. Not comfortable pulling it apart and flashing the pieces until there is more info on it. Not that I need it. I just like to play:laugh:
Gizmoe said:
Anyone else get an error when trying to flash system image 63L? Says boota doesn't exist. I know some partitions are doubled but I assume the image should work. Just wondering if it's my PC drivers or an actual issue with the image itself. Not comfortable pulling it apart and flashing the pieces until there is more info on it. Not that I need it. I just like to play:laugh:
Edit: Just realized I posted in wrong section. Mods please move to q&a if you see fit.
Click to expand...
Click to collapse
I had to update adb and fastboot
jaythenut said:
I had to update adb and fastboot
Click to expand...
Click to collapse
I updated through SDK and it says it's urrent but maybe my PC drivers are not playing nice. So it works for you though. That's good to know. It's probably my PC then. I should check if I added a static platform tools folder to my path instead of the updated one. Thanks for the reply
I have same problem as OP. Check out this post. I haven't tested, but I think this might solve the problem. http://forum.xda-developers.com/showpost.php?p=69239012&postcount=27
ADB sideload worked for me, but flashing factory images did not.
Golf c said:
ADB sideload worked for me, but flashing factory images did not.
Click to expand...
Click to collapse
Android studio updated the next time I opened it up. SDK tools version 25 is what it updated too and it works fine. Only fails on the first reboot bootloader command but then it flashes the rest no problem.
i just sideloaded with adb.
just open up the factory firmware files downloaded. within the folder there is a file named:flash-all.bat. i just clicked that after unlocking bootloader and it flashed the images. it did gives some slot error, but i haven't have any issues. im on the 63P image now as some claim it improves signal and wifi connectivity
Now that I've successfully unlocked my bootloader, I'm having an issue trying to flash the 8.1.0 system image. When I try to execute the flash-all.bat, it acts as if it's flashing the bootloader, and then I get an error message saying it failed. Here's a screenshot. Thanks in advance
Did you extract the zip file that's in the factory image zip? There's another zip in there that has the boot, recovery, etc image files.
Sent from my [device_name] using XDA-Developers Legacy app
I did. I'm wondering if it's an SDK issue...the Android API 27 SDK keeps failing to download via SDK manager because of a mismatched size. I tried downloading it in Android Studio, too, and while it says it's installed there, it says it isn't in SDK manager. Weird. I wish there was a way I could get it to download and install properly.
Google 15 seconds adb xda. That's the easiest way to get Fastboot and adb set up. It don't matter where the image files as it sets it up system wide. But it sounds more like you might have a corrupted file. Try download the factory image again.
Sent from my [device_name] using XDA-Developers Legacy app
Thanks! I tried that, however it still keeps failing I'm at a total loss. I just want to get onto Oreo 8.1 so I can flash the AOSP and root! This really has me baffled. Thanks again for your help
I did also try to redownload the file, and that wasn't the answer, either :/
Are you using Type C to C? I had this issue on my Pixel C and Pixel XL unable to flash a factory img with C to C only when I use A to C
It was indeed the SDK platform! I tried looking for where the API 27 had successfully installed in Android Studio, and found that it was under App Data>SDK. I looked there and voila! There was the downloaded platform. I extracted it and moved it to where the other platforms were located under SDK Tools, and success! I'm flashing the 8.1.0 factory image now
Ok, I spoke too soon The factory image files AREN'T flashing, and I got a data write failure....go figure. When I go to restart my tablet, I get the classic Android with the exclamation point. Here are some pics of what I got:
So I got it working! After a LOT of trial and error, and moving files to the platforms folder and flashing them that way, plus changing which USB port I was using, I was able to manually flash all files! I'm now on 8.1.0!
Hello guys,
I have been trying to get this to work on my own for a while now. I am trying to use deuces script and it is not working for the life of me. I have formatted user data entirely and killed all encryption. I have tried to install the factory image numerous times and numerous ways but nothing seems to be working. I have tried to use deuces script, from fastboot and it isnt working (log attached).
Here is what is currently going on and the current setup. No ROM installed currently (I do not believe). Device is UNLOCKED. TWRP is installed, version 3.3, latest version.
I can get into fastboot and the computer can see fastboot with fastboot devices command.
I can get into recovery from the device, which is TWRP. I can sideload things from there and run any commands that twrp can natively run.
I can NOT get deuces script to run with either the latest android 9 factory image, or the latest android 10 image.
I am putting all of the factory image files, unzipped, in the platform tools folder, along with the deuces script files in the same folder... then running the script. It is kicking back an error, which is attached as an image.
Additionally the log is attached as well.
ANY insight on how to get my phone back to stock would be great. Really getting anything installed on it would be great at this point, currently I can only get to fastboot and recovery.
Thank you so much!
Try a different cable or USB port if you haven't already.
Also you can try putting everything into C:\platform-tools, instead of having everything a few directories deep.
All my files just get extracted into C:\platform-tools
ilal2ielli said:
Try a different cable or USB port if you haven't already.
Also you can try putting everything into C:\platform-tools, instead of having everything a few directories deep.
All my files just get extracted into C:\platform-tools
Click to expand...
Click to collapse
I always do the same thing with good results!
Sent from my Pixel 2 XL using XDA Labs
wdarea51 said:
Hello guys,
I have been trying to get this to work on my own for a while now. I am trying to use deuces script and it is not working for the life of me. I have formatted user data entirely and killed all encryption. I have tried to install the factory image numerous times and numerous ways but nothing seems to be working. I have tried to use deuces script, from fastboot and it isnt working (log attached).
Here is what is currently going on and the current setup. No ROM installed currently (I do not believe). Device is UNLOCKED. TWRP is installed, version 3.3, latest version.
I can get into fastboot and the computer can see fastboot with fastboot devices command.
I can get into recovery from the device, which is TWRP. I can sideload things from there and run any commands that twrp can natively run.
I can NOT get deuces script to run with either the latest android 9 factory image, or the latest android 10 image.
I am putting all of the factory image files, unzipped, in the platform tools folder, along with the deuces script files in the same folder... then running the script. It is kicking back an error, which is attached as an image.
Additionally the log is attached as well.
ANY insight on how to get my phone back to stock would be great. Really getting anything installed on it would be great at this point, currently I can only get to fastboot and recovery.
Thank you so much!
Click to expand...
Click to collapse
Do it without unzipping the factory image. The script unzips it itself and you're causing an error by doing it for it.
Title
Forget about recovery and unzipping files or scripts.
If you xan boot into the bootloader google gives you precise instructions to follow to just flash everything executing flashall.bat here: developers.google(dot)com/android/images.
If you followed the exact steps and it's not working show the full final terminal output to help you.
JuanG2 said:
Forget about recovery and unzipping files or scripts.
If you xan boot into the bootloader google gives you precise instructions to follow to just flash everything executing flashall.bat here: developers.google(dot)com/android/images.
If you followed the exact steps and it's not working show the full final terminal output to help you.
Click to expand...
Click to collapse
Just for reference, dueces script is use 99% of the time AFTER Google's flash-all.bat had failed to give the desired results. Not saying this is the case here but it is a likely reality.
Sent from my Pixel 2 XL using XDA Labs
CyberpodS2 said:
Just for reference, dueces script is use 99% of the time AFTER Google's flash-all.bat had failed to give the desired results. Not saying this is the case here but it is a likely reality.
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
I (myself *my opinion*) really wouldn't use that script becouse it's just an incredibly verbose way of forcing the flashing of the images and it's way more tedious to find errors using it.
If google's flash-all script is not working it should be analized why as it only is running 5 fastboot commands to flash all the images and if the phone can't run fastboot commands it's somewhat worring.
In his case the script can be failing for a million reasons like the script cant create the work directory to unzip the factory zip becouse it's only for admin use, or maybe has conflicts of directories, can also not be using an appropiate file for it as the naming scheme does not make sense. In any case the problem here is with the way the dueces script is decompressing the .zip as it can't find the image.zip when it's allocated to the variable here: $imgzipname = (Get-ChildItem _work/*/*.zip).fullname.
This script code is really not prepared to correct it self and is not great, HOWEVER it should work without much of a problem if no naming scheme of the images, partitions, directories changes or so I understand why people use it when they really screw something up.
---------- Post added at 09:30 AM ---------- Previous post was at 09:06 AM ----------
JuanG2 said:
I (myself *my opinion*) really wouldn't use that script becouse it's just an incredibly verbose way of forcing the flashing of the images and it's way more tedious to find errors using it.
If google's flash-all script is not working it should be analized why as it only is running 5 fastboot commands to flash all the images and if the phone can't run fastboot commands it's somewhat worring.
In his case the script can be failing for a million reasons like the script cant create the work directory to unzip the factory zip becouse it's only for admin use, or maybe has conflicts of directories, can also not be using an appropiate file for it as the naming scheme does not make sense. In any case the problem here is with the way the dueces script is decompressing the .zip as it can't find the image.zip when it's allocated to the variable here: $imgzipname = (Get-ChildItem _work/*/*.zip).fullname.
This script code is really not prepared to correct it self and is not great, HOWEVER it should work without much of a problem if no naming scheme of the images, partitions, directories changes or so I understand why people use it when they really screw something up.
Click to expand...
Click to collapse
Actually I just realized why the script is not working for you. You are running it against the incorrect file. You shouldn't be running it against the images.zip that's inside of the factory.zip but rather to the factory.zip itself don't unzip it, just paste the whole zip downloaded from developers.google.com and run the script against it.