Related
Greetings!
First of all, I am sorry if this is on the wrong section of the forum. Nevertheless i've tried few rooting applications which are stated to be compatible with this ME103K model, but with no results.. Also many fake sites trying to lure you to purchase something.
Is there anyone who could provide me information on how to root my ASUS ME103K tablet? Should I also try every rooting application available out there or is this useless? Can I verify if they are compatible without all the way installing and running them on the device? (Sorry don't know much about this stuff =)! )
Thank you very much in advance
I rooted ME103K on my own - by compiling a custom kernel
Executive summary: Go to youtube and watch video with ID "gqubgQjqfHw" (I can't post links yet, sorry! ) - or search Youtube for "Rooting MemoPAD10 (ME103K) with my custom compiled kernel"
Analysis:
I hated the fact that my recently purchased MemoPAD10 (ME103K) tablet had no open process to allow me to become root. I don't trust the closed-source one-click root apps that use various exploits, and require communicating with servers in.... China. Why would they need to do that? I wonder...
I therefore decided this was a good opportunity for me to study the relevant documentation and follow the steps necessary to build an Android kernel for my tablet. I then packaged my custom-compiled kernel into my custom boot image, and the video shows how I boot from it and become root in the process.
Note that I didn't burn anything in my tablet - it's a 'tethered' root, it has no side-effects.
If you are a developer, you can read in detail about the steps I had to take to modify the kernel (and su.c) and become root - by reading the questions (and answers!) that I posted in the Android StackExchange forum ( can't post links yet, see the video description in Youtube ).
If you are not a developer, you can download my custom boot image from the link below - but note that this means you are trusting me to not do evil things to your tablet as my kernel boots and my /sbin/su is run
Honestly, I haven't done anything weird - I just wanted to run a debootstrapped Debian in my tablet, and succeeded in doing so. But I am also worried about the cavalier attitude I see on the web about rooting your devices - if you want to be truly safe, you must either do what I did (and recompile the kernel yourself) or absolutely trust the person that gives it to you. I do wish Google had forced a UI-accessible "become root" option in Android, just as Cyanogen does (sigh).
The image I created and used in the video to boot in rooted mode, is available from the link show in the Youtube video details.
Enjoy!
ttsiodras said:
Executive summary: Go to youtube and watch video with ID "gqubgQjqfHw" (I can't post links yet, sorry! ) - or search Youtube for "Rooting MemoPAD10 (ME103K) with my custom compiled kernel"
Analysis:
I hated the fact that my recently purchased MemoPAD10 (ME103K) tablet had no open process to allow me to become root. I don't trust the closed-source one-click root apps that use various exploits, and require communicating with servers in.... China. Why would they need to do that? I wonder...
I therefore decided this was a good opportunity for me to study the relevant documentation and follow the steps necessary to build an Android kernel for my tablet. I then packaged my custom-compiled kernel into my custom boot image, and the video shows how I boot from it and become root in the process.
Note that I didn't burn anything in my tablet - it's a 'tethered' root, it has no side-effects.
If you are a developer, you can read in detail about the steps I had to take to modify the kernel (and su.c) and become root - by reading the questions (and answers!) that I posted in the Android StackExchange forum ( can't post links yet, see the video description in Youtube ).
If you are not a developer, you can download my custom boot image from the link below - but note that this means you are trusting me to not do evil things to your tablet as my kernel boots and my /sbin/su is run
Honestly, I haven't done anything - I just wanted to run a deboot-strapped Debian in my tablet. But I am also worried about the cavalier attitude I see on the web about rooting your devices - if you want to be truly safe, you must either do what I did (and recompile the kernel yourself) or absolutely trust the person that gives it to you. I do wish Google had forced a UI-accessible "become root" option in Android, just as Cyanogen does (sigh).
The image I created and used in the video to boot in rooted mode, is available from the link show in the Youtube video details.
Enjoy!
Click to expand...
Click to collapse
Hello ttsiodras,
I had the same problem as OP and didn't want to go the "chinese route" either, especially since there seem to be conflicting reports on whether it works on the ME103k or not so I tried your solution - with mixed results...
Disclaimer: I'm totally new to Android (colour me unpleasantly surprised) and have little experience in Linux, so for further reference I would consider myself an advanced noob. Please keep this in mind when evaluating my claims or judging what I have done so far or am capable of doing by myself in the future.
What I did:
- become developer in the ME103k by tapping the system build repeatedly, then allowing debugging via USB
- use ADB to boot into the bootloader
- use fastboot to boot your boot.rooted.img
What happened:
- I did get root access
- the tab now always boots into the bootloader, even when told via ADB or fastboot to boot normally or into recovery. Pushing buttons etc doesn't seem to work either
- my attempts to do a recovery via the vanilla Asus method has failed due to the same fact that boot never gets past fastboot
Since you claimed in your description that there would be no side-effects since it is a tethered root I am somewhat puzzled as to what exactly happened. From what I understand - which admittedly isn't a lot - what should have happened is that your boot image is loaded, giving me root access until the next reboot without changing anything about the default boot process or image. I read somewhere else that this is how people test out different kernels with fastboot before deciding on which one they want to use on their devices. The whole boot process being changed and corrupted in a way that makes the tablet non-rebootable without having the cable and an adb- and fastboot-capable machine nearby is not really what I would have expected going by your description.
Of course it is entirely possible (and probably even rather likely) that I got something wrong along the way or there is a simple fix to my problem I am not aware of.
As for possible steps maybe you or someone else in the forum could point me to a way to return my tablet to factory settings before risking damaging it beyond repair. I'm assuming that it should be possible and rather straightforward to recover the original setup with the firmware provided by Asus (downloaded the newest version from the homepage) but to be honest I'm a bit scared to go ahead with it before knowing for sure how to do this safely.
One thing seems certain: I won't be able to do it the way Asus says I should unless I can somehow get into normal or recovery boot modes again. I do however still have root access and am able to run fastboot and ADB including shell on the tablet, so it should be possible.
I would certainly appreciate any help very much
Thanks
drsiegberterne said:
. . . From what I understand - which admittedly isn't a lot - what should have happened is that your boot image is loaded, giving me root access until the next reboot without changing anything about the default boot process or image. I read somewhere else that this is how people test out different kernels with fastboot before deciding on which one they want to use on their devices.
Click to expand...
Click to collapse
Your understanding is correct - that's exactly what should have happened.
I can assure you that the kernel I compiled is formed from the Asus sources with the 2 patches I made that have *nothing* to do with the bootloader - they patch the way that the kernel allows dropping privileges and thus allowing root level access.
Something else must have happened - did you by any chance "burn" the image? i.e. `(DONT DO THIS) fastboot flash boot boot.rooted.img` instead of `fastboot boot boot.rooted.img`?
I did not advocate for burning precisely because it is unpredictable - manufactures sometimes require signing images with their private keys before allowing a boot image to boot (AKA "locked bootloaders") which means that any attempt to burn may lead to weird configurations. . .
If you did burn it, maybe you can try burning the original "boot.img" from the Asus OTA (Over the Air) update .zip file (avaible as a big download at the ASUS site - "UL-K01E-WW-12.16.1.12-user.zip" )
I know of no way to help you with the current state of your tablet, except to "ease the pain" by saying that rebooting to fastboot is always "recoverable" - you can always boot into my own (rooted) kernel or the original (from the ASUS .zip file) with `fastboot boot <whatever_image>`. No "harm" can happen from this - as you correctly said, it's the way to try new kernels and images.
UPDATE - after more reverse engineering:
I had a look into the contents of the boot loader running inside the ME103K, and I am pretty sure that if you execute this at fastboot...
# fastboot oem reset-dev_info
# fastboot reboot
... you will get back to normal, un-tethered bootings of your ME103K.
Thanassis.
ttsiodras said:
Your understanding is correct - that's exactly what should have happened.
I can assure you that the kernel I compiled is formed from the Asus sources with the 2 patches I made that have *nothing* to do with the bootloader - they patch the way that the kernel allows dropping privileges and thus allowing root level access.
Something else must have happened - did you by any chance "burn" the image? i.e. `(DONT DO THIS) fastboot flash boot boot.rooted.img` instead of `fastboot boot boot.rooted.img`?
I did not advocate for burning precisely because it is unpredictable - manufactures sometimes require signing images with their private keys before allowing a boot image to boot (AKA "locked bootloaders") which means that any attempt to burn may lead to weird configurations. . .
If you did burn it, maybe you can try burning the original "boot.img" from the Asus OTA (Over the Air) update .zip file (avaible as a big download at the ASUS site - "UL-K01E-WW-12.16.1.12-user.zip" )
I know of no way to help you with the current state of your tablet, except to "ease the pain" by saying that rebooting to fastboot is always "recoverable" - you can always boot into my own (rooted) kernel or the original (from the ASUS .zip file) with `fastboot boot <whatever_image>`. No "harm" can happen from this - as you correctly said, it's the way to try new kernels and images.
Thanassis.
Click to expand...
Click to collapse
Hi Thanassis,
thanks for your quick reply and your efforts. I'm actually around 85% sure I did not flash the image but since I had no Linux on my computer at the time (I know shame on me) I used a Mac and the command line was a bit different. Since I had never used ADB or fastboot I relied on some guide that explained how to even get into the bootloader and might have gotten something wrong.
On the other hand I later read out the commands I used in the Mac shell and couldn't find anything other than the things I should have done and described earlier, so as far as I can tell this all should never have happened. It may be interesting to point out here that the "stuck in fastboot" mode happened immediately after the first time I loaded your kernel and I most definitely just wrote fastboot boot boot.rooted.img at that point.
As for fixing the problem now it's not only about the inconvenience of the whole thing. I also later (after I was already stuck in fastboot mode) installed some apps for helping me manage privileges of different apps (xposed framework and xprivacy) which turned out to not be compatible in some way or another. So now not only is my tablet not booteable in a normal way but its also cluttered with even more useless stuff than before and I would really like to just reset it before thinking about any other possibilities.
If I flash boot the original ASUS boot image found in the file you described and which i dowloaded already, shouldn't that fix the problem if I accidentally did flash your boot image? Or will there be even more trouble?
Alternatively isn't there a manual way to flash the whole zipped recovery image or am I misunderstanding what this ASUS file actually contains?
And which of the two options is safer to try first or in other words - which one might break the tablet once and for all?
Thanks again and sorry for my incompetence
drsiegberterne said:
Hi Thanassis,
If I flash boot the original ASUS boot image found in the file you described and which i dowloaded already, shouldn't that fix the problem if I accidentally did flash your boot image? Or will there be even more trouble?
. . .
Alternatively isn't there a manual way to flash the whole zipped recovery image or am I misunderstanding what this ASUS file actually contains?
. . .
Thanks again and sorry for my incompetence
Click to expand...
Click to collapse
No, don't be sorry We are all either choosing to learn in this world (i.e. make mistakes and learn from them), or choose to remain stuck in ignorance. I applaud your efforts in properly rooting the tablet. . .
To the point - remember, you are root now ; whatever apps you installed, you can definitely uninstall them. You don't necessarily need to wipe it.
If you do want to, I'd suggest booting in recovery and doing it the normal way that Asus recommends. Since you said "buttons don't work", you may want to try using the original recovery .img - i.e. "fastboot boot recovery.img". I'd love to suggest a link from ASUS, but they don't host it (which is bad - they really should) - so instead go to "goo" dot "gl" slash "noegkY" - this will point you to a discussion where a kind soul is sharing his ME103K recovery.img.
Booting from the recovery will allow you to install the ASUS OTA update - and probably try cleaning cache partition, etc
Good luck!
ttsiodras said:
No, don't be sorry We are all either choosing to learn in this world (i.e. make mistakes and learn from them), or choose to remain stuck in ignorance. I applaud your efforts in properly rooting the tablet. . .
To the point - remember, you are root now ; whatever apps you installed, you can definitely uninstall them. You don't necessarily need to wipe it.
If you do want to, I'd suggest booting in recovery and doing it the normal way that Asus recommends. Since you said "buttons don't work", you may want to try using the original recovery .img - i.e. "fastboot boot recovery.img". I'd love to suggest a link from ASUS, but they don't host it (which is bad - they really should) - so instead go to "goo" dot "gl" slash "noegkY" - this will point you to a discussion where a kind soul is sharing his ME103K recovery.img.
Booting from the recovery will allow you to install the ASUS OTA update - and probably try cleaning cache partition, etc
Good luck!
Click to expand...
Click to collapse
The problem here is that he doesn't seem to have the same version as on my tablet. I have the newest version with Lollipop while this seems to be at least a couple of patches earlier with a completely different version of Android. Won't I risk breaking things even more if I try to apply this - as in trying to recover a recovery that is not on my tablet since certainly the recovery.img doesn't contain all the information needed since it's only 10 MB.
As you can probably guess the whole discussion in your link about what part of the system is broken and how to fix it goes right over my head. It also seems like they did not find a satisfactory solution in the end (short of sending the tablet to ASUS). As you can imagine I'm at quite a loss what to try and what not out of fear to make things worse. At least for now I can still use the tablet to do the things I need it to do.
Thanks for your help anyway, I will try to read up more on the topic and decide what to do next.
drsiegberterne said:
The problem here is that he doesn't seem to have the same version as on my tablet. I have the newest version with Lollipop while this seems to be at least a couple of patches earlier with a completely different version of Android. Won't I risk breaking things even more if I try to apply this - as in trying to recover a recovery that is not on my tablet since certainly the recovery.img doesn't contain all the information needed since it's only 10 MB.
Thanks for your help anyway, I will try to read up more on the topic and decide what to do next.
Click to expand...
Click to collapse
I understand how you feel - your tablet is operational now (OK, with the annoyance that you need to boot it in "tethered mode") - so you rightfully fear that you may mess things up with further steps.
Just to clarify something - the recovery img is something that works on its own ; it has no dependency on what kind of Android image is installed in the /system partition.
If you do decide to do it, "fastboot boot recovery.img" will bring you to a spartan menu, showing options that allow you to apply an update (i.e. the ASUS update you downloaded!), clean the /cache partition, etc.
Choose "install update from SD card" (use volume up/down to choose, power btn to select), and navigate to your SD card, where you will have placed the big .zip file from ASUS.
The recovery process will begin, and your tablet will be "wiped" with the image from ASUS. Reboot, and be patient while the tablet boots up - it will be just like the first time you started it (i.e. install from scratch).
Whatever you decide - good luck!
ttsiodras said:
I understand how you feel - your tablet is operational now (OK, with the annoyance that you need to boot it in "tethered mode") - so you rightfully fear that you may mess things up with further steps.
Just to clarify something - the recovery img is something that works on its own ; it has no dependency on what kind of Android image is installed in the /system partition.
If you do decide to do it, "fastboot boot recovery.img" will bring you to a spartan menu, showing options that allow you to apply an update (i.e. the ASUS update you downloaded!), clean the /cache partition, etc.
Choose "install update from SD card" (use volume up/down to choose, power btn to select), and navigate to your SD card, where you will have placed the big .zip file from ASUS.
The recovery process will begin, and your tablet will be "wiped" with the image from ASUS. Reboot, and be patient while the tablet boots up - it will be just like the first time you started it (i.e. install from scratch).
Whatever you decide - good luck!
Click to expand...
Click to collapse
Okay, a little update from the battlefront:
I tried the recovery image and did get into the menu, however the recovery failed with the same two error messages as in your earlier link ("footer is wrong" and "signature verification failed"). My output from fastboot getvar all is also very similar to the one from that guy except I have a different bootloader version than him (3.03).
Another thing I noticed is that if I boot the standard boot.img found in the ASUS zip it will recognize the internal sdcard normally, however when I boot your rooted image the internal memory doesn't seem to be recognized, at least not through the pre-installed file manager. Downloading a file to the internal storage also failed while rooted but all the apps and the OS itself so far seem totally unaffected otherwise.
My last resort at the moment is the fastboot flash boot boot.img but I have little hope it would change anything since in the thread you linked they proposed just that and if it had worked they probably would have mentioned it.
Can it theoretically break the tablet even more? I would hate to have to send it in because I completely bricked it...
drsiegberterne said:
Okay, a little update from the battlefront:
Another thing I noticed is that if I boot the standard boot.img found in the ASUS zip it will recognize the internal sdcard normally, however when I boot your rooted image the internal memory doesn't seem to be recognized.
Click to expand...
Click to collapse
Not the case for me - everything works fine (including internal and external sdcard), so it's definitely not my kernel causing this.
drsiegberterne said:
My last resort at the moment is the fastboot flash boot boot.img but I have little hope it would change anything since in the thread you linked they proposed just that and if it had worked they probably would have mentioned it.
Can it theoretically break the tablet even more? I would hate to have to send it in because I completely bricked it...
Click to expand...
Click to collapse
Flashing is always dangerous (from what you've said, I actually theorize that you did, actually, flash already...)
I doubt this will solve the boot issue, to be honest - if I were you, I'd continue to boot tethered (with my image when you need root access, and (maybe) the Asus image when you don't). Myself, I always boot my own bootimage, since I have zero problems with it, and it allows me to run a complete Debian distro in a chroot (thus making my tablet a full-blown UNIX server - e.g. I run privoxy on it to filter all stupid ads in all apps on the tablet, etc).
No matter what you decide, good luck!
Thanassis.
ttsiodras said:
Not the case for me - everything works fine (including internal and external sdcard), so it's definitely not my kernel causing this.
Flashing is always dangerous (from what you've said, I actually theorize that you did, actually, flash already...)
I doubt this will solve the boot issue, to be honest - if I were you, I'd continue to boot tethered (with my image when I need root access, and (maybe) the Asus image when I don't). Myself, I always boot my own bootimage, since I have zero problems with it, and it allows me to run a complete Debian distro in a chroot (thus making my tablet a full-blown UNIX server - e.g. I run privoxy on it to filter all stupid ads in all apps on the tablet, etc).
No matter what you decide, good luck!
Thanassis.
Click to expand...
Click to collapse
I already tried to flash the original boot.img yesterday but it didn't change anything as you correctly assumed so I guess for now there is nothing more to do. I might write to the Asus support and maybe send the tablet in if it is free of charge for me (which I doubt). The only other option is to spend the next months to get sufficiently versed in Android to actually fix the problems myself but even for that I would probably need some files or source code from Asus. I find it rather disappointing the way these "closed" systems work nowadays, with the advancement of Linux and Open Source I really would have expected the opposite to be true but apparently people care more about convenience than actually being able to use the tools they buy in the way they want to.
Getting these Android devices like buying a hammer that can't hammer things in on Sundays.
drsiegberterne said:
I find it rather disappointing the way these "closed" systems work nowadays, with the advancement of Linux and Open Source I really would have expected the opposite to be true but apparently people care more about convenience than actually being able to use the tools they buy in the way they want to
Click to expand...
Click to collapse
I share the sentiment - it's really sad.
Undoing the tethered root
drsiegberterne said:
I already tried to flash the original boot.img yesterday but it didn't change anything as you correctly assumed so I guess for now there is nothing more to do. I might write to the Asus support and maybe send the tablet in if it is free of charge for me (which I doubt). The only other option is to spend the next months to get sufficiently versed in Android to actually fix the problems myself but even for that I would probably need some files or source code from Asus. I find it rather disappointing the way these "closed" systems work nowadays, with the advancement of Linux and Open Source I really would have expected the opposite to be true but apparently people care more about convenience than actually being able to use the tools they buy in the way they want to.
Getting these Android devices like buying a hammer that can't hammer things in on Sundays.
Click to expand...
Click to collapse
Hi drsiegberterne - I had a look into the contents of the boot loader running inside the ME103K, and I am pretty sure that if you execute this at fastboot...
# fastboot oem reset-dev_info
# fastboot reboot
... you will get back to normal, un-tethered bootings of your ME103K.
Hope this solves your problem!
Kind regards,
Thanassis.
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Jameswebb97 said:
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Click to expand...
Click to collapse
Use duces script to flash June google factory image.
jlokos said:
Use duces script to flash June google factory image.
Click to expand...
Click to collapse
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Make sure you are trying to open from the correct location, and put .\fastboot
EvilDobe said:
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Click to expand...
Click to collapse
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
simplepinoi177 said:
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Click to expand...
Click to collapse
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Jameswebb97 said:
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
Click to expand...
Click to collapse
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Jameswebb97 said:
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Click to expand...
Click to collapse
EvilDobe said:
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Click to expand...
Click to collapse
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
simplepinoi177 said:
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
Click to expand...
Click to collapse
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
Hey I'm so glad you got it working! Leave me a "Thanks!" would make it up to me ... I'm always happy to help out and get things figured out...yet I don't get the satisfaction of knowing if it does end up helping a lot of the time because a good number don't come back with their experience...so thanks for that! Glad you got it going...
EvilDobe said:
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Click to expand...
Click to collapse
And it's as @EvilDobe means.....
I remember back in the days of the Motorola Droids (OG Droid1, Droid 3, & Droid 4) where you could really mess things up and come out with a big ol' "brick" "paperweight" as there were many instances where you could not come back from (i.e. updating to a certain point, then attempting to downgrade when Google/Motorola/Verizon put blocks that breaks it). But this isn't the case these days. @Jameswebb97, at least with the Pixel 2's, Oreo and/or P(Android OS 9), it's actually more difficult than easy to get that too far gone. The only reason why I can help so many troubleshooting their issues is because I, myself, have wrecked my current device in some serious ways! So I can relate and have experience in helping in the same situations. I've gotten it to where it says "device is corrupt," (which isn't all that uncommon), BUT with the added desperate troubleshooting where I had to wipe/erase, changing partition types, format several partitions, even go about "resizing" the partition to match the "target extraction size" of the Full Factory flash, and even as far as learning to manually flash the various system partitions and that there are two (system_a & system_b) but, in Google's infinite wisdom(?), one flashes to system_a and the other to system_other!!! And I haven't even started on reading others' issues when going after the Slot A and Slot B complications -- I didn't even attempt to touch this in that troubleshooting story.
My point is: I think I've broken my device farther than most people and got it so close to the brink, and yet I was able to bring it back and am still using that same device today (most people would usually, at that point, go and get a RMA replacement). Honestly, as long as you have access to Bootloader Mode (which Google, in their infinite wisdom, seems to have placed it in the main board memory or separate memory rather than storage as to make it always accessible which makes it hard to "lose"), you have a really good (seemingly perfect) "safety net" in which you can always flash back to a working, stock state -- which is why it's the best policy to just make good backups before experimenting so, if anything, you get back to this state and restore all your data. I'm not trying to convince you to root or to try custom ROMs or anything -- even though there are many great reasons and capabilities of rooting -- I am simply appealingl to your sense of curiosity and reassure you so you aren't held back and you don't restrict and limit yourself if you don't want to, but are to fearful to experiment.
I hope you don't take this post as "lecturing" or anything, just some thoughts I hope you consider...
Glad it worked out in the end for you!
In other systems I have worked with there are sometimes ways to boot from a file other than the NVRAM that you ordinarily operate from. For some reason people
like to call this the ROM, even though it is writable.
I have an old tablet that has a recovery mode that is only a Chinese menu. I have seen a translation so I know what the items are but none of them
are helpful for re-flashing or booting from a file.
I have been able to connect the tablet using adb and run the shell, and I can get it into fastboot mode but the instructions for "unlocking" the boot loader do
not work so I am stuck with a fastboot prompt on the tablet with no way to proceed. I was able to upload a short file but not the TWRP (I did find one for this
phone). The failure was permission.
My questions:
I have rooted this phone using kingroot and promptly decided that was unsafe and did a full reset to manufacturer. But I am still trying to root. I suppose that the
rooting programs must have to run an exploit, perhaps a buffer overflow thing, but at any rate some series of commands to Android that cause elevation to
be accomplished. Where do I find the exploit documented in order to just do it manually?
Can I extract the su binary from the TWRP and jam it in there? Probably not but I thought I'd ask. Is the su binary in there just an ordinary program unless it
has a file bit set that elevates it?
What exactly is meant by the phrase "unlock the bootloader"? Can I unlock the bootloader manually in the adb shell?
Can I kingroot again and find an su binary, rename it, uninstall kingroot, rename it again? I don't suppose that re-named binary would survive a reflash?
How can I flash this tablet? The tools don't quite work. Even if I can back it up I can't reflash. Best would be the ability to boot a file separate from the ROM. I
read somewhere that sometimes after the flash the phone boots the old ROM once. How can that be true, and if it is true what does that say about the way
those images are actually stored and used?
OK so first of all, if this is the wrong place for this I'm sorry, it's quite late for me and I've been researching how to fix this for about two days and running up with nothing.
I recently upgraded to a Pixel 2XL, loving the device but unfortunately a couple of my apps save data into the data/data part of phone. The only way to then move that over and preserve the data is to use something like adb backup and restore. The backup seems to work fine, but so far every time I try to use restore on my pixel 2xl it 'ends' without actually adding the missing app data across.
I've tried using usb 2 and 3, no difference. I've made sure the usb debugging is on and that my phone is unlocked. I also made sure to try using the commands through both cmd and powershell and that both were in admin mode. I've also tried looking into other options like a friend suggested using es file explorer manager to change the download location, but I wasn't able to puzzle out a way to make something that was in data/data save elsewhere.
My phone isn't rooted, and I'd rather not go that far if I can help it. Any advice or ideas?
Aahhh,"...your phone isn't rooted..."that's probably it/key. I'm unsure whether any kind of "restore" works without root access -- backup of course works because that simply involves "copying" and "storing" files (essentially the basic process of backing up) and, as the system needs to be able to read and access the data, you pretty much have the "read access" to it. Restore on the otherhand, for those who are unaware, are essentially "copying" those stored files and "overwriting" the existing files -- which require "write access". The process of "rooting" is to acquire "root access" which allows both "read/write access" (therefore: "r/w access"). *again, for those who are unaware.
Sorry for just blabbering on about that, I guess I got carried away. In any case, basically (all in all, the reason why I blabbered on) I don't think you're going to go far without root access -- or "rooting" as you say -- but there is one thing I can suggest. When using adb, try running this command first before running any other adb command (i.e. restore):
Code:
adb root
It might just give you enough of that "root access" I was blathering about...
Also, among the all the things you made sure to do and include you made sure of, one thing you didn't mention is making sure you have the most up to date platform-tools (r28.0.1 *at least last I personally saw a few weeks ago).
Good luck to you, hope I made these things somewhat understandable, and hope this helped as well....
Thank you for the suggestions, tried it but no dice sadly. I kinda am hairy on rooting it too as I just got the phone and it's been a long time since I've done android dev work. If you have any other ideas I'd be welcome to hearing them but again thanks for trying.
simplepinoi177 said:
Aahhh,"...your phone isn't rooted..."that's probably it/key. I'm unsure whether any kind of "restore" works without root access -- backup of course works because that simply involves "copying" and "storing" files (essentially the basic process of backing up) and, as the system needs to be able to read and access the data, you pretty much have the "read access" to it. Restore on the otherhand, for those who are unaware, are essentially "copying" those stored files and "overwriting" the existing files -- which require "write access". The process of "rooting" is to acquire "root access" which allows both "read/write access" (therefore: "r/w access"). *again, for those who are unaware.
Sorry for just blabbering on about that, I guess I got carried away. In any case, basically (all in all, the reason why I blabbered on) I don't think you're going to go far without root access -- or "rooting" as you say -- but there is one thing I can suggest. When using adb, try running this command first before running any other adb command (i.e. restore):
Code:
adb root
It might just give you enough of that "root access" I was blathering about...
Also, among the all the things you made sure to do and include you made sure of, one thing you didn't mention is making sure you have the most up to date platform-tools (r28.0.1 *at least last I personally saw a few weeks ago).
Good luck to you, hope I made these things somewhat understandable, and hope this helped as well....
Click to expand...
Click to collapse
Where your bootloader is apparently unlocked, download a TWRP recovery image to the directory fastboot is in and boot it using the fastboot command "fastboot boot twrp.img". From there, take a nandroid backup of your device. Restoring is done in the same fashion. AND, since TWRP is memory resident when booting it this way, the stock recovery remains untouched.
Strephon Alkhalikoi said:
Where your bootloader is apparently unlocked, download a TWRP recovery image to the directory fastboot is in and boot it using the fastboot command "fastboot boot twrp.img". From there, take a nandroid backup of your device. Restoring is done in the same fashion. AND, since TWRP is memory resident when booting it this way, the stock recovery remains untouched.
Click to expand...
Click to collapse
Great idea! And that's why veterans and those with experience are the best to go to...!
OK so first, thank you so much for all the advice. I've taken awhile to get back to you because this took some time to parse. I'm admittedly kind of a novice at this. So I've used the instructions here https://www.xda-developers.com/how-to-install-twrp/ to try and install twrp. I think I did it right, had the zip contents and img file in the same directory that adb is in, then ran the command...and this is what I got back.
N:\platform-tools>fastboot flash recovery twrp-3.2.3-1-taimen.img
Sending 'recovery' (40960 KB) OKAY [ 1.203s]
Writing 'recovery' FAILED (remote: 'Flashing is not allowed in Lock State')
Finished. Total time: 1.219s
as the 'fastboot reboot' command appeared to bring me right back to normal operating for the phone I'm guessing the failed stopped me with that 'flashing not allowed in lock state' there. Am I missing a step?
close, but not exactly right...
you got the downloading platform tools right, and putting the necessary files in that same folder that fastboot.exe resides in also right (you wouldn't believe how many novices actually make the mistake of not doing this)...
but you don't ever (underlined and emphasized not really for you AshtonHunter, but for any who are under the wrong impression; it's caused endless headaches and has even been complained by developers on Twitter...) "fastboot flash" TWRP with Pixels (any; and AFAIK any a/b slotted devices). You boot the twrp .img file. Also, for those who do not know and for future reference, there is no "recovery" for fastboot to "flash" to on Pixels (any), as there no longer is a separate partition for recovery; recovery resides in the boot partition. All in all, the command should be exactly this:
Code:
fastboot boot twrp-3.2.3-1-taimen.img
Immediately afterwards, you'll see your Pixel 2 XL restart and load up TWRP...
Good luck to you and hope this helps...
Hey everyone. So I tried this but it also didn't work. Same error 'cannot in locked state' when trying to run the command. I do notice there's a green 'locked' on my phone when it's in the screen after the 'adb reboot bootloader' command. Any ideas?
simplepinoi177 said:
close, but not exactly right...
you got the downloading platform tools right, and putting the necessary files in that same folder that fastboot.exe resides in also right (you wouldn't believe how many novices actually make the mistake of not doing this)...
but you don't ever (underlined and emphasized not really for you AshtonHunter, but for any who are under the wrong impression; it's caused endless headaches and has even been complained by developers on Twitter...) "fastboot flash" TWRP with Pixels (any; and AFAIK any a/b slotted devices). You boot the twrp .img file. Also, for those who do not know and for future reference, there is no "recovery" for fastboot to "flash" to on Pixels (any), as there no longer is a separate partition for recovery; recovery resides in the boot partition. All in all, the command should be exactly this:
Code:
fastboot boot twrp-3.2.3-1-taimen.img
Immediately afterwards, you'll see your Pixel 2 XL restart and load up TWRP...
Good luck to you and hope this helps...
Click to expand...
Click to collapse
AshtonHunter said:
OK so first of all,
if this is the wrong place for this I'm sorry, it's quite late for me and I've been researching how to fix this for about two days and running up with nothing.
I recently upgraded to a Pixel 2XL, loving the device but unfortunately a couple of my apps save data into the data/data part of phone. The only way to then move that over and preserve the data is to use something like adb backup and restore. The backup seems to work fine, but so far every time I try to use restore on my pixel 2xl it 'ends' without actually adding the missing app data across.
I've tried using usb 2 and 3, no difference.
I've made sure the usb debugging is on and that my phone is unlocked. I also made sure to try using the commands through both cmd and powershell and that both were in admin mode. I've also tried
looking into other options like a friend suggested using es file explorer manager to change the download location, but I wasn't able to puzzle out a way to make something that was in data/data save elsewhere.
My phone isn't rooted, and I'd rather not go that far if I can help it. Any advice or ideas?
Click to expand...
Click to collapse
AshtonHunter said:
Hey everyone. So I tried this but it also didn't work. Same error 'cannot in locked state' when trying to run the command. I do notice there's a green 'locked' on my phone when it's in the screen after the 'adb reboot bootloader' command. Any ideas?
Click to expand...
Click to collapse
You would only get this error if your device isn't "unlocked"... I/we were all under the impression that (which is why I quoted) your device is "unlocked"... So maybe some clarification is in order...
There are two types of "unlocking" that can be attributed to the device; 1) your device can be "locked" to a carrier or global region, and it can be "unlocked" so the device can be used on any network anywhere, and 2) all Pixel's (and all smartphones AFAIK) have their bootloader in a locked state, and in order to do any kind of "rooting" or data restore/recovery or modification down to the system level you have to "unlock" the bootloader or have it in an "unlocked" state.
*BEWARE! Before running these commands, please note that running critical will erase/wipe EVERYTHING -- I am pretty sure running both will actually cause this to happen.
Considering all of this, when you said your "...phone is unlocked", you are speaking in terms of #2 I listed above, correct? Basically, you have run the command -- while in Bootloader Mode -- "fastboot flashing unlock" & (just as important, imho) "fastboot flashing unlock_critical", right? Because, if you haven't done these, then your device was never "unlocked" (in the sense that most relates to us and what you are intending) as well as without having one these commands, you had no chance at restoring your /data folder or partition "data" (pun not intended).
After clearing any misunderstanding and/or issues of these type, we might be able to better help after that point...but it is looking like you may need to root or at least do the same steps towards that end to accomplish what you are seeking...
So, get back to me/us on this, and hope this all helps...
Ok! So after confirming I could do it without any issue and having a day of time to work on it, my phone's bootloader is now unlocked and I've managed a backup using TWRP. Only thing now is I'm not entirely sure what I should be looking at and how in here. Advice is welcome but I'm going to be digging into it myself to see if I can puzzle it out with some friends of mine online. Also just again thank you all for all the assistance. I would have never gotten this far with it without you all!
AshtonHunter said:
Ok! So after confirming I could do it without any issue and having a day of time to work on it, my phone's bootloader is now unlocked and I've managed a backup using TWRP. Only thing now is I'm not entirely sure what I should be looking at and how in here. Advice is welcome but I'm going to be digging into it myself to see if I can puzzle it out with some friends of mine online. Also just again thank you all for all the assistance. I would have never gotten this far with it without you all!
Click to expand...
Click to collapse
What exactly are you wanting to do now that your bootloader is unlocked, and you have twrp? Can I assume you want to root it?
AshtonHunter said:
Ok! So after confirming I could do it without any issue and having a day of time to work on it, my phone's bootloader is now unlocked and I've managed a backup using TWRP. Only thing now is I'm not entirely sure what I should be looking at and how in here. Advice is welcome but I'm going to be digging into it myself to see if I can puzzle it out with some friends of mine online. Also just again thank you all for all the assistance. I would have never gotten this far with it without you all!
Click to expand...
Click to collapse
I'm glad you were successfully able to get it done! (clicking a "Thanks!" would be all I would welcome in return)
So, now, you might be able to successfully do what you originally did and restore through adb if you wish...I mean, if you simply have a /data folder that's been backed up, there might not be too many options available for you. Another thing you might try is running a custom recovery (TWRP I believe is the best or only) and restoring -- and/or backing up from your old device/phone, wiping everything, setting phone up, then use that TWRP backup to restore -- but you can only really run a restore if it was a TWRP backup to begin with... One other good way is running a Titanium Backup backup and restoring that way...
Good luck and hope this helps...
please help
simplepinoi177 said:
Aahhh,"...your phone isn't rooted..."that's probably it/key. I'm unsure whether any kind of "restore" works without root access -- backup of course works because that simply involves "copying" and "storing" files (essentially the basic process of backing up) and, as the system needs to be able to read and access the data, you pretty much have the "read access" to it. Restore on the otherhand, for those who are unaware, are essentially "copying" those stored files and "overwriting" the existing files -- which require "write access". The process of "rooting" is to acquire "root access" which allows both "read/write access" (therefore: "r/w access"). *again, for those who are unaware.
Sorry for just blabbering on about that, I guess I got carried away. In any case, basically (all in all, the reason why I blabbered on) I don't think you're going to go far without root access -- or "rooting" as you say -- but there is one thing I can suggest. When using adb, try running this command first before running any other adb command (i.e. restore):
Code:
adb root
It might just give you enough of that "root access" I was blathering about...
Also, among the all the things you made sure to do and include you made sure of, one thing you didn't mention is making sure you have the most up to date platform-tools (r28.0.1 *at least last I personally saw a few weeks ago).
Good luck to you, hope I made these things somewhat understandable, and hope this helped as well....
Click to expand...
Click to collapse
sorry in advance, I'm not very familiar with this webiste.
Im in a similar situation where it wont let me restore my adb backup, I am rooted and the bootloader is unlocked (though twrp is not installed). could you please help, i beg you.
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.